Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Datadog sourcemaps not working in RainforestQA release builds #7362

Open
twschiller opened this issue Jan 18, 2024 · 13 comments · Fixed by #7366
Open

Datadog sourcemaps not working in RainforestQA release builds #7362

twschiller opened this issue Jan 18, 2024 · 13 comments · Fixed by #7366
Labels

Comments

@twschiller
Copy link
Contributor

Context

  • Observed on 1.8.7-alpha.4

Discussion

Screenshots

image image
@johnnymetz
Copy link
Collaborator

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

So not sure how it's nullish here:

SOURCE_MAP_PUBLIC_PATH:
sourceMapPublicUrl ?? "extension://dynamichost/",

@twschiller
Copy link
Contributor Author

cc @fregante

@fregante
Copy link
Collaborator

fregante commented Jan 18, 2024

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
Copy link
Collaborator

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
Copy link
Contributor Author

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
Copy link
Collaborator

Re-opening because this is still broken

@johnnymetz johnnymetz reopened this Jan 19, 2024
@johnnymetz
Copy link
Collaborator

johnnymetz commented Jan 19, 2024

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
Copy link
Collaborator

which is not present in datadog

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

@twschiller
Copy link
Contributor Author

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)

@twschiller twschiller changed the title Datadog sourcemaps not working in release builds Datadog sourcemaps not working in RainforestQA release builds Jan 22, 2024
@johnnymetz johnnymetz reopened this Feb 8, 2024
@johnnymetz
Copy link
Collaborator

Still not working

@fregante
Copy link
Collaborator

fregante commented Feb 9, 2024

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

@grahamlangford
Copy link
Collaborator

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
Copy link
Contributor Author

Unassigning because it's in the icebox

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants