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

BundleComponent.isValidBundle() should no throw if reading manifest fail #1303

Merged
merged 1 commit into from
Jun 21, 2024

Conversation

laeubi
Copy link
Contributor

@laeubi laeubi commented Jun 16, 2024

Currently BundleComponent.isValidBundle() is used to check if a bundle is valid and should be considered for the baseline. If the location points to something that chase no manifest at all (or an invalid manifest) this currently an exception even though the API doc clearly states that "Validity is determined via the existence of a readable manifest file"

This now adds two checks

  1. the location points to a file that exits and is larger than zero bytes
  2. parsing the manifest from the location do not throw an exception

This error can be seen for example here:
https://ci.eclipse.org/equinox/job/p2/job/PR-524/8/console

@laeubi
Copy link
Contributor Author

laeubi commented Jun 16, 2024

/request-license-review

Copy link

github-actions bot commented Jun 16, 2024

Test Results

   291 files  ±0     291 suites  ±0   1h 1m 20s ⏱️ + 2m 2s
 3 578 tests ±0   3 502 ✅ +2   76 💤 ±0  0 ❌ ±0 
11 031 runs  ±0  10 800 ✅ +2  231 💤 ±0  0 ❌ ±0 

Results for commit 2773e25. ± Comparison against base commit 93f76cf.

♻️ This comment has been updated with latest results.

Copy link

/request-license-review

License review requests:

After all reviews have concluded, re-run the license-vetting check from the Github Actions web-interface to update its status.

Workflow run (with attached summary files):
https://github.com/eclipse-pde/eclipse.pde/actions/runs/9536767493

@laeubi laeubi force-pushed the api_tools_fix_valid_bundle branch 2 times, most recently from 0c9b4b5 to 2c10a35 Compare June 17, 2024 04:24
Currently BundleComponent.isValidBundle() is used to check if a bundle
is valid and should be considered for the baseline. If the location
points to something that chase no manifest at all (or an invalid
manifest) this currently an exception even though the API doc clearly
states that "Validity is determined via the existence of a readable
manifest file"

This now adds two checks

1) the location points to a file that exits and is larger than zero
bytes
2) parsing the manifest from the location do not throw an exception
@laeubi laeubi force-pushed the api_tools_fix_valid_bundle branch from 2c10a35 to 2773e25 Compare June 21, 2024 15:53
@laeubi laeubi merged commit 0359821 into eclipse-pde:master Jun 21, 2024
17 checks passed
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 this pull request may close these issues.

1 participant