[Bug]: Polyscope breaks herd nginx file when generating a workspace
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- macos, nginx
- Domain
- infrastructure
Research direction
Reproduce the first workspace assignment on macOS and inspect ~/Library/Application Support/Herd/config/valet/Nginx/silver-lobster.test, especially the malformed rewrite and placeholder values reported in the issue. Validate the generated vhost with nginx and confirm that Herd .test domains remain reachable while the Polyscope workspace works.
Written by the indexing model from the issue text.
Description
Platform
macOS
Operating system version
macos 15.6
System architecture
ARM64 (M1, M2, etc)
PolyScope Version
latest
Bug description
All of herds .test domains refused to connect after opening polyscope for the first time and assigning it to a Sites/Repo on my mac. claude helped me track the root cause to a malformed vhost written by polyscope.
~/Library/Application\ Support/Herd/config/valet/Nginx/silver-lobster.test
1 server {
2 listen 127.0.0.1:80;
3 #listen 127.0.0.1:80; # valet loopback
4 server_name silver-lobster.test www.silver-lobster.test *.silver-lobster.test;
5 return 301 httpspasted10:36 AMClaude responded: Confirmed — line 27 rewrite ^ "" last; (and line 70).Identified broken placeholder configuration and prescribed remedial stepsIdentified broken placeholder configuration and prescribed remedial stepsConfirmed — line 27 rewrite ^ "" last; (and line 70). nginx 1.25.4 rejects the empty "" replacement, and that's fatal for the whole config. This whole file is a Polyscope placeholder vhost — root /, fastcgi_index "", SCRIPT_FILENAME "", the blank rewrite — it's a skeleton for a workspace that never got a real document root wired in. Broken as written, and it's been taking all of Herd down with it.
I fixed it by removing the file
mv ~/Library/Application\ Support/Herd/config/valet/Nginx/silver-lobster.test
However that gets herd working but not polyscope. I'm unsure why its causing a malformed vhost?
Steps to reproduce
No response
Relevant log output
- Dominant language
- No language data
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from beyondcode/polyscope-community
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
beyondcode/polyscope-community#198 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
All issues in beyondcode/polyscope-community
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
vicharanashala/fln#564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
haskell-actions/setup#152 ·
-
feature-request helm
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gravitational/teleport#69785 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
TencentCloud/Octop#1007 ·