-
Notifications
You must be signed in to change notification settings - Fork 85
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
NO-JIRA: only save graph data if it's valid json #1069
Conversation
If we save the graph data to disk before checking it's valid, we can run into unmarshaling errors later like: ``` 2025/02/05 02:14:36 [ERROR] : [GetReleaseReferenceImages] error list [APIRequestError: channel "stable-4.16": ResponseInvalid: invalid character 'a' after top-level value] ```
Just returning unmarshaling errors is not very useful information: ``` ResponseInvalid: invalid character 'a' after top-level value ``` Let's add more context to that error when reading graph data from the working dir so we know which is the offending file.
@r4f4: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: r4f4, sherine-k The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/label acknowledge-critical-fixes-only |
/retitle NO-JIRA: only save graph data if it's valid json |
@r4f4: This pull request explicitly references no jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Description
If we save the graph data to disk before checking it's valid, we can run into unmarshaling errors later like:
Just returning unmarshaling errors is not very useful information:
Let's add more context to that error when reading graph data from the
working dir so we know which is the offending file.
Github / Jira issue:
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
Expected Outcome
Please describe the outcome expected from the tests.