We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the problem: Sync token field missed:
To Reproduce: [Steps to reproduce the behavior]
The text was updated successfully, but these errors were encountered:
It literally explains the reason on the screenshot, also see the pinned issue.
Sorry, something went wrong.
Do you mean this? #9131
I've deployed tabby-web myself, but I can't put sync token from it
Oh right, sorry, I'm just swarmed by users posting the same question daily in regard to the shutdown.
I'll fix it in a bit, but you can set the token through the configSync.token config file option directly as a workaround
configSync.token
345e90c
No branches or pull requests
Describe the problem:
![Знімок екрана 2023-11-16 о 02 19 03](https://private-user-images.githubusercontent.com/1798483/283284129-40a1648e-b08a-4f4a-9cca-d30dbed21b15.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQzODU5NTEsIm5iZiI6MTcyNDM4NTY1MSwicGF0aCI6Ii8xNzk4NDgzLzI4MzI4NDEyOS00MGExNjQ4ZS1iMDhhLTRmNGEtOWNjYS1kMzBkYmVkMjFiMTUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgyMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MjNUMDQwMDUxWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MjJmNjM5ZGJkNzI3NzZjNTc3MmU4M2I3MTJiYTM2OTY0YzgyODY0ZmJkYTljZmJhOWNiZDQ2NWI1ODQ0ZTVjMSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.LeaG-pZ4ntcw-Br7Cc58K1pzdb1laHZwj5jLPr5H-s0)
Sync token field missed:
To Reproduce:
[Steps to reproduce the behavior]
The text was updated successfully, but these errors were encountered: