PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding-SimpleGraphic
"# chromium/5414" "ANGLE_THIRDPARTY_ZLIB_COMMIT 44d9b490c721abdb923d5c6c23ac211e45ffb1a5" Fetching failed.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 22
- Forks
- 62
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 4
Description
Can you add a file and package it as "/zlib 44d9b490c721abdb923d5c6c23ac211e45ffb1a5".
Put it in the Assets list of the PathOfBuilding SimpleGraphic project.
Network latency issues lead to CMake Error: "-- Fetching https://chromium.googlesource.com/chromium/src/third_party/zlib 44d9b490c721abdb923d5c6c23ac211e45ffb1a5... "Download failed.
Thanks.
Error， Network latency.
File：git-fetch-x64-windows-err.log
Context：fatal: unable to access 'https://chromium.googlesource.com/chromium/src/third_party/zlib/': Failed to connect to chromium.googlesource.com port 443 after 21196 ms: Couldn't connect to server
CMake print out.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CMake output and the referenced git-fetch-x64-windows-err.log, then inspect the PathOfBuilding SimpleGraphic project's Assets list and third-party dependency handling. Reproduce the chromium.googlesource.com zlib fetch failure and confirm that the requested zlib revision is packaged as an asset and the build completes without that network fetch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, git
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100