lukedukeus

How is this still an issue after four years? please fix it.

Here is the workaround I came up with: I have a class `Entity.cs` that my make up the nodes of my treeview: ``` public abstract class Entity : ObservableRecipient {...

I just ran into the same issue, but was unable to fix it, so I just mocked the component. ``` jest.mock('allotment', () => ({ Allotment: jest.fn().mockImplementation(({ children }) => {children}),...

> Update: cache, created on the self-hosted windows runner with mentioned zstd hack, cannot be used somehow. When I try to retrieve it, I get `Error: Failed to restore cache...

> > Update: cache, created on the self-hosted windows runner with mentioned zstd hack, cannot be used somehow. When I try to retrieve it, I get `Error: Failed to restore...

Still would love to see this / use it.

No, I found that the extension still works as expected, just shows the error at startup

on `[...nextauth].tsx`, line 56: coment this out: ``` // pages: { // signIn: "auth/sigin", // }, ``` then try again

what does your refresh token look like?

try modifying your backend to give the client a refresh token that is base64 encoded and also a valid JWT like `eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c` Tool for testing if a token is a...