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

Url decode the resourceId supplied to store.getResourceInternal to fix filenames containing spaces. #8581

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

ianwallen
Copy link
Contributor

@ianwallen ianwallen commented Dec 24, 2024

Url decode the resourceId supplied to store.getResourceInternal to fix filenames containing spaces.

Without this fix, filename containing spaces may not be indexed in the data url as the file will not be found due to %20 in the filename.

Checklist

  • I have read the contribution guidelines
  • Pull request provided for main branch, backports managed with label
  • Good housekeeping of code, cleaning up comments, tests, and documentation
  • Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
  • Clean commit messages, longer verbose messages are encouraged
  • API Changes are identified in commit messages
  • Testing provided for features or enhancements using automatic tests
  • User documentation provided for new features or enhancements in manual
  • Build documentation provided for development instructions in README.md files
  • Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

@ianwallen ianwallen added this to the 4.4.7 milestone Dec 24, 2024
@ianwallen ianwallen added the bug label Jan 7, 2025
Copy link
Member

@josegar74 josegar74 left a comment

Choose a reason for hiding this comment

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

Tested with thumbnail files containing spaces in the file name and seems working fine.

@ianwallen ianwallen merged commit eab5c1b into geonetwork:main Jan 10, 2025
9 checks passed
@geonetworkbuild
Copy link
Collaborator

The backport to 4.2.x failed:

The process '/usr/bin/git' failed with exit code 1
stderr
error: could not apply b16dd58565... Url decode the resourceId supplied to store.getResourceInternal to fix filenames containing spaces.
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"

stdout
Auto-merging core/src/main/java/org/fao/geonet/util/XslUtil.java
CONFLICT (content): Merge conflict in core/src/main/java/org/fao/geonet/util/XslUtil.java

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.2.x 4.2.x
# Navigate to the new working tree
cd .worktrees/backport-4.2.x
# Create a new branch
git switch --create backport-8581-to-4.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick b16dd585656a30d5c42a97fcecd841e7e3000d65
# Push it to GitHub
git push --set-upstream origin backport-8581-to-4.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.2.x

Then, create a pull request where the base branch is 4.2.x and the compare/head branch is backport-8581-to-4.2.x.

wangf1122 pushed a commit to wangf1122/core-geonetwork that referenced this pull request Jan 10, 2025
@wangf1122
Copy link
Collaborator

4.2 Backport conflict fixing pull request available #8587

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants