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
Allow parsing long GISDBASE paths #1376
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
attilaolah
pushed a commit
to attilaolah/wasm
that referenced
this pull request
Feb 19, 2021
Inline the patch for OSGeo/grass#1376 until it gets merged.
marisn
approved these changes
Feb 19, 2021
Use a larger buffer when parsing the `.gisrc` file. Use `GPATH_MAX` to fit whatever would fit in the path value, plus the length of the key. Fixes OSGeo#1373.
attilaolah
pushed a commit
to attilaolah/wasm
that referenced
this pull request
Feb 19, 2021
Inline the patch for OSGeo/grass#1376 until it gets merged.
nilason
approved these changes
Feb 19, 2021
neteler
pushed a commit
that referenced
this pull request
Mar 1, 2021
Use a larger buffer when parsing the `.gisrc` file. Use `GPATH_MAX` to fit whatever would fit in the path value, plus the length of the key. Fixes #1373.
marisn
pushed a commit
to marisn/grass
that referenced
this pull request
Mar 22, 2021
Use a larger buffer when parsing the `.gisrc` file. Use `GPATH_MAX` to fit whatever would fit in the path value, plus the length of the key. Fixes OSGeo#1373.
ninsbl
pushed a commit
to ninsbl/grass
that referenced
this pull request
Oct 26, 2022
Use a larger buffer when parsing the `.gisrc` file. Use `GPATH_MAX` to fit whatever would fit in the path value, plus the length of the key. Fixes OSGeo#1373.
ninsbl
pushed a commit
to ninsbl/grass
that referenced
this pull request
Feb 17, 2023
Use a larger buffer when parsing the `.gisrc` file. Use `GPATH_MAX` to fit whatever would fit in the path value, plus the length of the key. Fixes OSGeo#1373.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use a larger buffer when parsing the
.gisrc
file. UseGPATH_MAX
to fit whatever would fit in the path value, plus the length of the key, plus 2 for newline character and null byte.Fixes #1373.