Filipe Azevedo
Filipe Azevedo
@maoueh from a near substreams I get the following on the proto Clock.id: ``` number: 9820431 id: 886d431b0ff918e8f21e38af93952176b8d0d3f14c85aab2941c386b0ea945dd hash(base64 decoded) f3ce9de37d5bd1f7fdd7c7bc7f6d5edfc69ff77f79db5efa6fc7747777f5e1cf3969a6f6f78d5cdfce9bd1e6bde3975d, ``` How is this encoded? The block hash should...
Is there some additional context on this PR? Was there an issue where this was previous discussed?
@lutter is this ready for review?
From a security perspective, I think there are a couple of concerns that come to mind, this could be "easily" leveraged with malicious intent, for instance, an unprotected node endpoint...
Do we still want this PR @lutter ?
Can we merge this PR then and if there are more changes we can fix forward?
As I understand it this integration was taken in a different direction, I'll close the PR for now, re-open if needed. Also if not needed anymore would be great to...
For me, moving `(tool-bar-mode -1)` to the window setup hook worked: ``` (add-hook 'window-setup-hook (lambda () (tool-bar-mode -1) (inhibit-startup-message t) (toggle-frame-maximized t) )) ``` After this it stopped leaving phantom...
I think I have the same issue as well. Any chance we could get this into a release version? I pushed a minimal reproducible setup [here](https://git.sr.ht/~fazevedo/lsp-go-min-repro)
We currently don't have this information surfaced through the GRPC types. The current Error definition looks like this: ``` message Error { string module = 1; string reason = 2;...