Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
RSDK-8595 Unhealthy resource state #4257
RSDK-8595 Unhealthy resource state #4257
Changes from all commits
fa57f43
3592bc8
9751ccd
e2e139d
a5d2eef
be10ef0
b0f7d16
11f6031
498ea0a
0d2c485
5c03dea
d90c854
828f8b9
02dee8e
b1b30db
f78133e
f51341e
a9fb365
443048b
dc565ad
f7527fb
7f320f0
ff43ecc
b228237
46345a2
438b333
4f9e5bf
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[q] Any idea when this happens? Just want to get a sense of when resources are logging in the absence of a logger. Seems like a violation of my mental model of graph node loggers...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i forgot the specifics but there is a lag between when a node is first created and when it receives an initial logger. if we remove the
w.logger == nil
guards from this file then we will get a nil-access panic pretty quickly.I suppose we should use this function through the file instead of relying on the guard to get more uniform behavior -- happy to do this as a follow-up.
EDIT: something tells me the lag is specific to modular resources, since we pass logging configs to them over a unix socket after startup.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.