Internal Server Error: /app/hjelp/issues/get_next_properties/ [Ticket#75418] #45
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Hjelp#45
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
moved from AlekSIS/AlekSaaS#17
changed title from {-Fwd: [Django] ERROR (EXTERNAL IP): -}Internal Server Error: /app/hjelp/issues/get_next_properties/ [Ticket#75418] to Internal Server Error: /app/hjelp/issues/get_next_properties/ [Ticket#75418]
changed the description
assigned to @yuha
made the issue visible to everyone
@yuha Can you please take a look at this issue?
yes
Actually, I wasn't able to reproduce this misbehavior in my own testing environment. Could you please further describe the scenario in which it occured? @hansegucker
With some trying, it seems to appear if you clear a Select2 field:
oh I see where the issue is
created merge request !154 to address this issue
mentioned in merge request !154
mentioned in commit
c2a3e8c9d0