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

FirstChanceException when no metadata #310

Closed
StevenBlair123 opened this issue Jun 6, 2024 · 3 comments · Fixed by #311
Closed

FirstChanceException when no metadata #310

StevenBlair123 opened this issue Jun 6, 2024 · 3 comments · Fixed by #311
Assignees

Comments

@StevenBlair123
Copy link

Describe the bug
If an event has no metadata, or one of the followign properties missing $traceId | $spanId the method ExtractTracingMetadata throws an Exception. It is handled silently, so the Event isn't rejected, but means each Event being processed has an Exception thrown for it.

To Reproduce

Replicated code

Steps to reproduce the behavior:

  1. Hookup AppDomain.CurrentDomain.FirstChanceException
  2. Write an event with no metadata
  3. Persistent subscription to newly created stream
  4. Observe the FirstChanceException being thrown

Expected behavior

I think we should check if the proeprties are present in the metadata, and if not, cleanly return the TracingMetadata.None.

Actual behavior
Exception is thrown, silently handled and TracingMetadata.None returned.

Config/Logs/Screenshots
If applicable, please attach your node configuration, logs or any screenshots.

EventStore details

  • EventStore server version: 24.2

  • Operating system: Windows 11

  • EventStore client version (if applicable): 23.3.2

Additional context
None at this time.

@josephcummings
Copy link
Contributor

Hi @StevenBlair123

Thanks for bringing this to our attention.

I have prepared a fix in #311 and will get it out as patch v23.3.3 once merged.

@StevenBlair123
Copy link
Author

Thanks for the quick turnaround.

@josephcummings
Copy link
Contributor

Hi @StevenBlair123

Patch v23.3.3 is now up on NuGet :)

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

Successfully merging a pull request may close this issue.

2 participants