Workaround for geo-blocking #3
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#2 Messages isn’t a valid keyword (anymore?)
profitroll/PythonRMV
Reference: profitroll/PythonRMV#3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Since the first russian attacks on RMV, their services are being blocked by location, including all Ukrainian IPs (probably infected machines were involved during botnet attacks).
Because of that, workaround needs to be built in order for Actions and some of the test projects, using pyrmv on this machine, to run.
Contact with RMV is being established as well in order to unblock all uninvolved machines or at least whitelist the one used by current Act runners on this Gitea instance.