github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-08 13:49:15 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #941] [MINOR BUG] Trailing whitespace in email fields #8467

New Issue
Closed
opened 2026-04-30 04:19:27 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-30 04:19:27 -05:00
Owner
Copy Link

Originally created by @yellowsnow3 on GitHub (Jun 19, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/941

Originally assigned to: @miloschwartz on GitHub.

What happened: I invited a user and put in their email address, on the invite page the user autofilled the email with their clipboard, but with a space behind it. This caused Pangolin to reject the signup, they were only allowed to sign up when the field contained only the email without the space.

A fix would be just cutting out any whitespace before and after email addresses or other fields.

This issue would be eliminated by implementing the Email autofill in #923, but the issue may still be present in other fields across the whole project that I did not check.

Originally created by @yellowsnow3 on GitHub (Jun 19, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/941 Originally assigned to: @miloschwartz on GitHub. What happened: I invited a user and put in their email address, on the invite page the user autofilled the email with their clipboard, but with a space behind it. This caused Pangolin to reject the signup, they were only allowed to sign up when the field contained only the email without the space. A fix would be just cutting out any whitespace before and after email addresses or other fields. This issue would be eliminated by implementing the Email autofill in #923, but the issue may still be present in other fields across the whole project that I did not check.
GiteaMirror added the needs investigatingnon-critical bug labels 2026-04-30 04:19:27 -05:00
GiteaMirror commented 2026-04-30 04:19:29 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 4, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:3034007904 --> @github-actions[bot] commented on GitHub (Jul 4, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
GiteaMirror commented 2026-04-30 04:19:29 -05:00
Author
Owner
Copy Link

@yellowsnow3 commented on GitHub (Aug 24, 2025):

Issue fixed in #1129 (merged in 1.9.0).

<!-- gh-comment-id:3218352113 --> @yellowsnow3 commented on GitHub (Aug 24, 2025): Issue fixed in #1129 (merged in 1.9.0).
GiteaMirror commented 2026-04-30 04:19:30 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Aug 24, 2025):

Thanks :}

<!-- gh-comment-id:3218352648 --> @oschwartz10612 commented on GitHub (Aug 24, 2025): Thanks :}
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label needs investigating non-critical bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#8467
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?