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.

Sign up for GitHub

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

Jump to bottom

NASA moved the Example Imagery files #7380

Closed
3 of 7 tasks
ozyx opened this issue Jan 17, 2024 · 2 comments · Fixed by #7374
Closed
3 of 7 tasks

NASA moved the Example Imagery files #7380

ozyx opened this issue Jan 17, 2024 · 2 comments · Fixed by #7374
Labels
not_viper Temporary label to define bugs that won't affect viper deployments severity:blocker type:bug verified Tested or intentionally closed
Milestone
Target:3.2.1

Comments

@ozyx
Copy link
Member

ozyx commented Jan 17, 2024 •
edited by unlikelyzero
Loading

Summary

Example Imagery loads its images from NASA's image archives. These images now 404, likely due to NASA's recent work on web consolidation and migration to WordPress. These URLs likely just need to be updated.

Expected vs Current Behavior

The image urls should not 404

Steps to Reproduce

  1. Load example imagery
  2. Images no loady

Impact Check List

  • Data loss or misrepresented data?
  • Regression? Did this used to work or has it always been broken?
  • Is there a workaround available?
  • Does this impact a critical component?
  • Is this just a visual bug with no functional impact?
  • Does this block the execution of e2e tests?
  • Does this have an impact on Performance?

Additional Information

We reference images hosted by nasa hq like 'https://www.hq.nasa.gov/alsj/a16/AS16-117-18748.jpg' in our example imagery plugin. This changed to 'https://www.nasa.gov/wp-content/uploads/static/history/alsj/a16/AS16-117-18731.jpg'
@ozyx ozyx added the type:bug label Jan 17, 2024
@ozyx ozyx added this to the Target:4.0.0 milestone Jan 17, 2024
@ozyx ozyx self-assigned this Jan 17, 2024
@ozyx ozyx mentioned this issue Jan 17, 2024
Merged
15 tasks
@unlikelyzero unlikelyzero added severity:blocker not_viper Temporary label to define bugs that won't affect viper deployments labels Jan 17, 2024
@unlikelyzero
Copy link
Collaborator

Candidate for backport since this is technically a blocker for a default plugin

@rukmini-bose
Copy link
Contributor

Testathon Verified locally on 1/18/2024

@unlikelyzero unlikelyzero added the verified Tested or intentionally closed label Jan 19, 2024
@ozyx ozyx modified the milestones: Target:4.0.0, Target:3.2.1 Feb 28, 2024
ozyx added a commit that referenced this issue Feb 28, 2024
@ozyx
fix(#7380): update example imagery urls (moved after NASA wordpress m…
25c4ab9 
…igration)
@ozyx ozyx mentioned this issue Feb 28, 2024
Merged
unlikelyzero pushed a commit that referenced this issue Feb 28, 2024
@ozyx
fix(#7380): update example imagery urls (moved after NASA wordpress m… (
36d9c5a 
#7532)

fix(#7380): update example imagery urls (moved after NASA wordpress migration)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
not_viper Temporary label to define bugs that won't affect viper deployments severity:blocker type:bug verified Tested or intentionally closed
Projects
None yet
Milestone
Target:3.2.1
Development

Successfully merging a pull request may close this issue.

feat(#7367): ProgressBar for ExportAsJSONAction nasa/openmct
3 participants
@ozyx @unlikelyzero @rukmini-bose