[OPIK-1639] Vercel Integration TS SDK metadata and tags config params docs

[awkoy]

trafficstars

Details

This pull request enhances the documentation for the Vercel AI SDK integration by introducing advanced configuration options for adding custom tags and metadata to traces.

Issues

Resolves #

Testing

Documentation

[X-pech]

Came here today to report the same issue. Want to add some details:

1. It is also not possible for me to import certificates in Flatpak Zen.

2. It is possible in Flatpak Firefox to see system certificates and import certificates.

3. There is also an error in Browser Console when opening "View Certiifcates" menu in Flatpak Zen:

   ReferenceError: ZenWorkspaces is not defined
   set selectedIndex chrome://global/content/elements/tabbox.js:612
   baseConnect chrome://global/content/elements/tabbox.js:559
   connectedCallback chrome://global/content/elements/tabbox.js:961
   <anonymous> chrome://global/content/customElements.js:211
    customElements.js:214:19
   <anonymous> chrome://global/content/customElements.js:214
   
   

4. Certificates Manager also does not allow you to switch tabs in it so it basically does not work at all in Flatpak Zen.

[mr-cheffy]

Has been fixed with https://github.com/zen-browser/desktop/pull/7126

[rhoot]

I don't see how that PR could fix system certs not being trusted by the browser. It looks like just a UI fix? Did you just mean it fixed the issue @X-pech mentioned, but not the one in the issue post?

That said, I made a PR against the flatpak manifest repo yesterday that definitely does fix system cert trust: https://github.com/flathub/app.zen_browser.zen/pull/24

[mr-cheffy]

Oh right sorry, when I saw the comment I thought it was what this issue was talking about

[rhoot]

It seems libnssckbi.so is no longer used by the Zen browser for some reason, causing both my flatpak PR and the workaround mentioned above to no longer work. It's unclear to me why that library is no longer loaded though. Firefox still loads it.

You can see the difference if you go to Settings -> Privacy & Security -> Security Devices. If you click Builtin Roots Module in Firefox 137.0 its Path says libnssckbi.so. If you do the same thing in Zen (1.11.1b or 1.11b) running in flatpak it says null.

[dosubot[bot]]

Hi, @rhoot. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• Zen browser on Flatpak doesn't trust system-wide certificates.
• You suggested a workaround involving the NSS library replacement.
• X-pech noted issues with importing certificates and errors in the certificate manager.
• Mauro-balades mentioned a UI fix, but you clarified it wasn't related to the cert trust issue.
• You found that libnssckbi.so is not used by Zen, affecting the workaround.

Next Steps:

• Please let me know if this issue is still relevant to the latest version of the desktop repository by commenting here.
• If there is no further activity, I will automatically close this issue in 7 days.

Thank you for your understanding and contribution!

[rhoot]

This is still a problem.

[dosubot[bot]]

Hi, @rhoot. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• Zen browser on Flatpak doesn't trust system-wide certificates, identified as a packaging issue.
• Additional problems with importing certificates and errors in the certificate manager were noted.
• A pull request was mentioned but only addresses UI issues, not the certificate trust problem.
• The library libnssckbi.so is not being used by Zen, affecting the proposed workaround.
• The issue remains unresolved.

Next Steps:

• Could you confirm if this issue is still relevant to the latest version of the desktop repository? If so, please comment to keep the discussion open.
• If there is no further activity, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

[peteruithoven]

For my understanding, is this about Zen not picking up certificated made using mkcert -install? If so this is still a problem. In contrast, Firefox also installed through Flatpak, seems to pick the certificate up just fine.