pixiebrix / pixiebrix-extension

PixieBrix browser extension
https://www.pixiebrix.com
GNU Affero General Public License v3.0
83 stars 22 forks source link

Datadog sourcemaps not working in RainforestQA release builds #7362

Open twschiller opened 8 months ago

twschiller commented 8 months ago

Context

Discussion

Screenshots

image image
johnnymetz commented 8 months ago

Both the mv2 and mv3 build logs show sourceMapPublicUrl is set:

So not sure how it's nullish here: https://github.com/pixiebrix/pixiebrix-extension/blob/13f0d366dc040a5b7ddac0e2e1562981c00501c8/webpack.config.mjs#L218-L219

twschiller commented 8 months ago

cc @fregante

fregante commented 8 months ago

There is no dynamichost string in the zip file produced by that run (build-production.zip). Did you upload that bundle?

https://github.com/pixiebrix/pixiebrix-extension/actions/runs/7563418803

The error specifically mentions that string, so it must be present in the bundle, but which bundle? This isn't a Datadog config/upload issue yet

fregante commented 8 months ago

build-production.zip includes sourcemaps URLs like this one, which is valid and it exists:

//# sourceMappingURL=https://pixiebrix-extension-source-maps.s3.amazonaws.com/sourcemaps/build/c0e5cacc39b865790973c99cac04ebc523db8ecf/mv2/browserActionInstantHandler.js.map
twschiller commented 8 months ago

Hmm, not sure how these could get out of sync:

There is no dynamichost string in the zip file produced by that run (build-production.zip). Did you upload that bundle?

Hmm, that's odd - that's a good place to dig into first. We'd expect to see that string somewhere in there

johnnymetz commented 7 months ago

Re-opening because this is still broken

johnnymetz commented 7 months ago

Running the rainforest qa job manually didn't work. The {{ github.sha }} value is b120c2a2470da2f478201204e8f878137a7361e9 which is not present in datadog (see here).

We may need to run the rainforest qa job as part of the release pipeline because the sha is dependent on the event that triggered the workflow, see docs:

The commit SHA that triggered the workflow. The value of this commit SHA depends on the event that triggered the workflow. For more information, see "Events that trigger workflows." For example, ffac537e6cbbf934b08745a378932722df287a53.

fregante commented 7 months ago

which is not present in datadog

Isn't that a matter of uploading the sourcemaps in the rainforest.yml workflow?

twschiller commented 7 months ago

Isn't that a matter of uploading the sourcemaps in the rainforest.yml workflow?

We could if we wanted too. I'm not aware there's any problems with uploading extra source maps to Datadog (e.g., if there's a max size across all maps/if we were to get billed for them)

johnnymetz commented 7 months ago

Still not working

fregante commented 7 months ago

Is their support helping? They can probably see what information they're missing and what we're doing wrong

grahamlangford commented 7 months ago

Is their support helping? They can probably see what information they're missing and what we're doing wrong

We've got an email chain with them that's been going on for a few weeks now. Most of the changes have been at their suggestion.

twschiller commented 5 months ago

Unassigning because it's in the icebox

github-actions[bot] commented 2 months ago

This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.