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

Certain toast messages cause an error until server restart #1451

Open
KeithALane opened this issue Nov 12, 2024 · 1 comment
Open

Certain toast messages cause an error until server restart #1451

KeithALane opened this issue Nov 12, 2024 · 1 comment
Labels

Comments

@KeithALane
Copy link

Describe the Bug

Certain toast messages cause an error until server restart

Steps To Reproduce

New-PodeWebSelect -Name 'SQLServer:' -Options @($Servers) | Register-PodeWebEvent -Type Click -ScriptBlock {Show-PodeWebToast -Title "Unsupported" -Icon "message-alert-outline" -Message "This value is hard-coded to SPN-SC1D-SQL.nacloud.ecihosting.com for this example"}

Expected Behavior

Toast message wouldn't update unit the next restart, but it shouldn't produce an error.

Screenshots

20241111 -Pode Error

Platform

  • OS: Windows Server 2019 Standard
  • Browser: Edge Version 130.0.2849.46
  • Versions:
    • Pode: v2.9.0
    • Pode.Web v0.8.3
    • PowerShell v7.4.5

Additional Context

I noticed this issue when I changed the name of the server from "SCN-SC1-CVSQL1" to "SPn-SC1d-SQL.NACloud.ecihosting.com"
I'm guessing based on the error message and the reference to Utilities.ps1 lines ~530 that the issue has to do with the periods in the message. It seems to work fine once the server restarts, but I thought it was weird enough to look into.

@KeithALane
Copy link
Author

KeithALane commented Nov 12, 2024

Sorry I should have put his on the Pode.Web repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

No branches or pull requests

1 participant