mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-26 02:25:52 +03:00
[GH-ISSUE #45] Check for Updades not show or check the new update on the node. #36
Labels
No labels
Approved
Q2-3 2026 Development
bug
documentation
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/project-pegaprox-PegaProx#36
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?
Originally created by @ThibautBascoulergue on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/45
Hi,
It seems there is a bug with the ‘Check for update’ feature. After verification, the nodes do not display any new updates to install. You have to force it and go directly to the node to perform a refresh, and only then do the updates become visible in PegaProx.
@mkellermann97 commented on GitHub (Feb 10, 2026):
Hi @ThibautBascoulergue ,
would be great if you can send us now the support bundle so we can investigate. support@pegaprox.com
Regards,
Marcus
@mkellermann97 commented on GitHub (Feb 10, 2026):
Thanks @ThibautBascoulergue ,
we would recommend you to send it to us via email. support@pegaprox.com This support bundle can be seen and downloaded currently by everyone which isn't great.
Regards,
Marcus
@mkellermann97 commented on GitHub (Feb 10, 2026):
Thanks @ThibautBascoulergue ,
we would recommend you to send it to us via email. support@pegaprox.com This support bundle can be seen and downloaded currently by everyone which isn't great.
Regards,
Marcus
@ThibautBascoulergue commented on GitHub (Feb 10, 2026):
Send by email.
@ThibautBascoulergue commented on GitHub (Feb 11, 2026):
You can closed this issue :)
@MrMasterbay commented on GitHub (Feb 11, 2026):
Oki doki thank you :) .
In the next update we fixed the issue then :) @ThibautBascoulergue