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

Fix undefined behaviour for GestaltId when starting agent #840

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

aryanjassal
Copy link
Member

@aryanjassal aryanjassal commented Nov 11, 2024

Description

When starting the agent after approximately 1 hour, an error is thrown like such:

WARN:polykey.PolykeyAgent.task v0ppdq4uibpo01417n072jft4io:Failed - Reason: ErrorUtilsUndefinedBehaviour("failed to decode vertex GestaltId "undefined"")

This is caused due to a minor typo in the discovery domain. This has been resolved in this PR, and similar messages should no longer happen.

Issues Fixed

Tasks

  • 1. Fix the undefined behaviour error

Final checklist

  • Domain specific tests
  • Full tests
  • Updated inline-comment documentation
  • Lint fixed
  • Squash and rebased
  • Sanity check the final build

@aryanjassal aryanjassal self-assigned this Nov 11, 2024
Copy link

linear bot commented Nov 11, 2024

@aryanjassal
Copy link
Member Author

This PR depends on #838.

After that PR has been merged, this can be too.

@CMCDragonkai
Copy link
Member

That's great how can we prevent regressions of this nature in the future? Types or fast check tests?

@aryanjassal
Copy link
Member Author

That's great how can we prevent regressions of this nature in the future? Types or fast check tests?

#797 (comment)

@aryanjassal aryanjassal force-pushed the feature-undefined-gestalt-id branch from 4663ad5 to efbd2d0 Compare November 11, 2024 07:07
@aryanjassal
Copy link
Member Author

I ran manual sanity checks for this change by printing the status of the actual task in TaskManager.startTask() and by setting the time interval to 1 second so it will trigger continuously. That resulted in zero errors and the rediscovery triggering each second.

This means that the changes made was successful in fixing this issue.

@aryanjassal
Copy link
Member Author

Now that the CI is passing and the changes are approved, I will be merging this and making a release.

@aryanjassal aryanjassal merged commit fd46374 into staging Nov 11, 2024
36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Fix undefined behaviour error message coming from background tasks
3 participants