Skip to content
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

Joseki Explorer Editor is broken #2894

Open
cloud-tinkerer opened this issue Dec 15, 2024 · 3 comments
Open

Joseki Explorer Editor is broken #2894

cloud-tinkerer opened this issue Dec 15, 2024 · 3 comments

Comments

@cloud-tinkerer
Copy link

cloud-tinkerer commented Dec 15, 2024

The attached image happens after I enter a new sequence, only 1 stone new, and press save, safari.

image

@GreenAsJade
Copy link
Contributor

Thanks - I'll take a look.

@GreenAsJade
Copy link
Contributor

Something strange went wrong for you to get the screenshot above.

When I arrive at Q16,R17,R16,Q17,P17,P18,S17 and press "edit", I see this:

Screenshot 2024-12-17 at 8 12 15 PM (2)

There are lots of differences. Can you check it out to see if your situation can be reproduced?

@activestidle
Copy link

activestidle commented Dec 30, 2024

@GreenAsJade updating from OGS convo to keep a consistent log:

If the node you mentioned joseki 22537 (that I may have created?) already exists, then why don't we see a letter d here joseki 22536 ?
Furthermore, assuming this is correct, this current state, which seems buggy, is still a different state the system theoretically could have been in when I filed the bug, I'm genuinely curious if my test submit to understand how the system works created the node in question, or if it existed before me, regardless of the reason why, I believe the state of the UI does
not reflect the data in the database.

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

No branches or pull requests

3 participants