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

fix: allow activation of atSigns without requiring teapot state #1670

Merged
merged 2 commits into from
Jan 21, 2025

Conversation

XavierChanth
Copy link
Member

@XavierChanth XavierChanth commented Jan 20, 2025

- What I did

  • Detect both teapot (code 1) state & initial atServer (code 3) state as "not activated" in the controller
  • ignore visual studio files

- How I did it

- How to verify it

  • I tested activation of an atSign and the atSign management screen
    • Did not test the rest, but that area should be unchanged, other than updating the bundled binaries

- Description for the changelog
fix: allow activation of atSigns without requiring teapot state

@XavierChanth XavierChanth merged commit ff626e0 into trunk Jan 21, 2025
9 checks passed
@XavierChanth XavierChanth deleted the windows-installer-5-8-2 branch January 21, 2025 12:08
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

Successfully merging this pull request may close these issues.

3 participants