Alex Coleman

This is from https://github.com/facebook/sapling/pull/718; you can downgrade the extension in the meantime to unblock too (just released in the latest version). To fix I think it would have to retry...

Hey @quark-zju, we're running into the same intermittent issue (timestamps all say "now" in ISL / inline blame). I have no issues on versions: extension 0.1.34, sapling 0.2.20231113-145254+995db0d6. However, a...

I've filed a ticket with Github about this, but would it be possible to change anything on the Sapling side to prevent the double-synchornization? It seems the PR is first...

> @quark-zju : It went away for me after a reboot. > > It's been a bit so my memory is fuzzy but I do remember working on and doing...

This is also now causing the VSCode extension's "Shelved Changes" feature to not work for me: 

> Does this only happen, if you make changes to your GraphQL definitions after you've started the LSP? Maybe it's related to #4447 I've tried reloading window (which should restart...

Seems like https://github.com/facebook/relay/pull/4275 has some context maybe fwiw

Looks good to me, general functionality seems working and the new feature from https://github.com/facebook/relay/pull/4434 that I was looking forward to is looking good. Thanks so much!

The "Relay" output included above is the full output for that channel. Here's the full output from "Relay LSP Logs": ``` [DEBUG] Initialized stdio transport layer [DEBUG] < {"jsonrpc":"2.0","id":0,"method":"initialize","params":{"processId":52943,"clientInfo":{"name":"Visual Studio...

> @alex-statsig Do you think it would be possible to create a minimum repro repo so I could take a look and inspect further? @tbezman Yeah, here's a minimal reproduction:...