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

Cannot set properties of undefined (setting 'sentryEventId') #2125

Open
4 tasks
Warxcell opened this issue Dec 22, 2023 · 2 comments
Open
4 tasks

Cannot set properties of undefined (setting 'sentryEventId') #2125

Warxcell opened this issue Dec 22, 2023 · 2 comments
Labels
kind/bug Something isn't working stage/0-issue-prerequisites Needs more information before we can start working on it

Comments

@Warxcell
Copy link

Warxcell commented Dec 22, 2023

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

  • 1. The issue provides a
    minimal reproduction available on
    Stackblitz.
    • Please install the latest @envelop/* packages that you are using.
    • Please make sure the reproduction is as small as possible.
  • 2. A failing test has been provided
  • 3. A local solution has been provided
  • 4. A pull request is pending review

Describe the bug
sometimes this error appears

Cannot set properties of undefined (setting 'sentryEventId')

with no stack or whatsoever.

To Reproduce Steps to reproduce the behavior:

🤷

Expected behavior

No error.

Environment:

  • OS:
  • NodeJS:
  • @envelop/ versions:
    • @envelop/core: 5.0.0
    • @envelop/sentry: 8.0.0

Additional context

@Warxcell
Copy link
Author

@EmrysMyrddin EmrysMyrddin added kind/bug Something isn't working stage/0-issue-prerequisites Needs more information before we can start working on it labels Dec 22, 2023
@EmrysMyrddin
Copy link
Collaborator

EmrysMyrddin commented Dec 22, 2023

Hi @Warxcell and thank you for the report!

Sorry but I'm not adding a lot here but just labeling it according to our new Contribution Guide and issue flow.

One way of pushing this forward would be to add an example of the input and the output you expect to get.
Maybe even adding a failing test so we could get this into stage 2!

Thank you and sorry that this comment is not a complete solution (yet).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working stage/0-issue-prerequisites Needs more information before we can start working on it
Projects
None yet
Development

No branches or pull requests

2 participants