Skip to content

44 feature request add explanation what went wrong - #50

Merged
dgraf-gh merged 5 commits into
mainfrom
44-feature-request-add-explanation-what-went-wrong
Jul 29, 2026
Merged

44 feature request add explanation what went wrong#50
dgraf-gh merged 5 commits into
mainfrom
44-feature-request-add-explanation-what-went-wrong

Conversation

@dgraf-gh

Copy link
Copy Markdown
Contributor

No description provided.

dgraf-gh added 5 commits July 29, 2026 15:24
…nused JAR logic

- Updated `upload-h3-bundle.sh` to support optional .env file paths via CLI, removing default value enforcement.
- Simplified error handling and improved argument parsing for better usability.
- Removed unused JAR logic from `update-h3.sh` and cleaned up redundant script sections.
- Refined Docker commands for improved consistency in handling PBF input files and imports.
…se geocoding endpoint

- Updated `/reverse` endpoint to return specific error messages when `lat` or `lon` parameters are missing.
- Adjusted method signature to accept nullable `Double` for `lat` and `lon`.
- Improved request validation and error handling logic for better API robustness.
- Replaced "no-store, no-cache" directive with "max-age=86400" for improved client-side caching.
…ess in ImportService

- Moved `incrementActiveThreads` to ensure accurate thread activity tracking within asynchronous tasks.
- Added `resetCompactionProgress` to initialize compaction progress tracking before shard compaction begins.
- Adjusted `startProgressReporter` to dynamically set sleep duration based on terminal availability.
- Enabled longer intervals for non-TTY environments to reduce resource usage.
@dgraf-gh
dgraf-gh merged commit 593ef7a into main Jul 29, 2026
2 checks passed
@dgraf-gh
dgraf-gh deleted the 44-feature-request-add-explanation-what-went-wrong branch July 29, 2026 14:01
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.

[Feature Request] Respect TTY when logging status updates [Feature Request] add explanation what went wrong [Bug] Status Update is not correct

1 participant