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

NO-JIRA: only save graph data if it's valid json #1069

Merged
merged 2 commits into from
Feb 11, 2025

Conversation

r4f4
Copy link
Contributor

@r4f4 r4f4 commented Feb 7, 2025

Description

  • 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.

Github / Jira issue:

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Code Improvements (Refactoring, Performance, CI upgrades, etc)
  • Internal repo assets (diagrams / docs on github repo)
  • This change requires a documentation update on openshift docs

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.

r4f4 added 2 commits February 7, 2025 20:49
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.
@openshift-ci openshift-ci bot requested review from aguidirh and sherine-k February 7, 2025 20:10
Copy link

openshift-ci bot commented Feb 7, 2025

@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.

Copy link
Contributor

@sherine-k sherine-k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 10, 2025
Copy link

openshift-ci bot commented Feb 10, 2025

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2025
@lmzuccarelli
Copy link
Contributor

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Feb 11, 2025
@lmzuccarelli
Copy link
Contributor

/retitle NO-JIRA: only save graph data if it's valid json

@openshift-ci openshift-ci bot changed the title v2/release/cincinnati: only save graph data if it's valid json NO-JIRA: only save graph data if it's valid json Feb 11, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 11, 2025
@openshift-ci-robot
Copy link

@r4f4: This pull request explicitly references no jira issue.

In response to this:

Description

  • 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.

Github / Jira issue:

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Code Improvements (Refactoring, Performance, CI upgrades, etc)
  • Internal repo assets (diagrams / docs on github repo)
  • This change requires a documentation update on openshift docs

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.

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 81db147 into openshift:main Feb 11, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants