quarto-hub: Cannot use new empty project set when cannot connect to sync server
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 255
- Forks
- 17
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 109
Description
Today I checked out main and ran npm run dev:fresh to get started with quarto-hub development again. I was greeted by the "create new project set" screen, clicked on "create new project set", and it brought me to the projects list. Under "your projects" it says "Connecting to project set..." and there are no actions I can take to use the application. After 15 seconds or so I get booted back to the "create new project set" screen.
This seems to be happening because sync.automerge.org is down.
I think @shikokuchuo's PR https://github.com/quarto-dev/q2/pull/397 may address this.
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
Reproduce the flow with npm run dev:fresh: create a new project set, open the projects list, and wait while sync.automerge.org is unavailable. Review PR #397 and the project-set connection path; done means a new empty project set remains usable when the sync server cannot connect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100