oar-p2p/src, branch v0.2.24 Unnamed repository; edit this file 'description' to name the repository. feat: added --version flag 2025-11-09T18:54:58+00:00 diogo464 diogo464@d464.sh 2025-11-09T18:53:44+00:00 74fbf3e1c719edbce69e34ad31484e4c2ad23c74 






fix: added --force flag to docker swarm leave
2025-11-09T18:42:41+00:00

diogo464
diogo464@d464.sh

2025-11-09T18:42:41+00:00

e98d7f5bcdcb60e575e6df35a961ede5024bc09e












fixed clippy warnings
2025-10-30T20:28:06+00:00

diogo464
diogo464@d464.sh

2025-10-30T20:28:06+00:00

647c0c95fd1bfd47f810547742e1b9f0832a48db












warn if running from job machine
2025-10-30T20:27:13+00:00

diogo464
diogo464@d464.sh

2025-10-30T20:27:13+00:00

4082e97c42f77f97db0269c0454c4b12d8877089












added support for the shelder machine
2025-10-30T20:22:53+00:00

diogo464
diogo464@d464.sh

2025-10-30T20:22:53+00:00

5cdb0c8876c22d8fada79cbc82645d840e0d27eb












added support for snorlax machines
2025-10-30T20:21:13+00:00

diogo464
diogo464@d464.sh

2025-10-30T20:21:13+00:00

685107d2fcab5d3d5e3166c2e33777768cb1e6cc












fix: compile warning
2025-10-30T20:12:12+00:00

diogo464
diogo464@d464.sh

2025-10-30T20:12:12+00:00

c298456429259225c5caa6061385e5e7cf9e2be7












fix: improve error message when job has 0 machines
2025-10-30T20:09:56+00:00

diogo464
diogo464@d464.sh

2025-10-30T20:09:56+00:00

ed0a8b8e0acaf6eb402e4a8626d23c9b8b924f26

when a job is not yet in running state the program runs but the function
that lists the job's machines returns zero machines which can cause a
panic from division by 0 which is not a very helpful message. this
commit improves the error/warn messages when no machines are listed for
a job.





when a job is not yet in running state the program runs but the function
that lists the job's machines returns zero machines which can cause a
panic from division by 0 which is not a very helpful message. this
commit improves the error/warn messages when no machines are listed for
a job.







fix: dont panic when unable to obtain hostname
2025-10-30T20:03:37+00:00

diogo464
diogo464@d464.sh

2025-10-30T20:03:37+00:00

2bfd274bf31ed74f690bb5d4087c6a433ab83a06

if we are unable to obtain the hostname of the local machine from the
/etc/hostname file or HOSTNAME env var then an empty string is used as
the hostname and a warning is shown instead of a panic. since the
hostname is just used to determine if we are executing on the cluster,
and the cluster machines all have their hostnames set, then using the
empty string should not be a problem.





if we are unable to obtain the hostname of the local machine from the
/etc/hostname file or HOSTNAME env var then an empty string is used as
the hostname and a warning is shown instead of a panic. since the
hostname is just used to determine if we are executing on the cluster,
and the cluster machines all have their hostnames set, then using the
empty string should not be a problem.







remove docker networks and leave swarm on setup
2025-10-17T16:35:38+00:00

diogo464
diogo464@d464.sh

2025-10-17T16:35:38+00:00

8f60ce71eddb39c6580f7cc58a83c99a0c53418f

some docker networks and the swarm can create routing rules that
conflict with the ones we create leading to errors such as:

59:2025-10-15T15:07:33.745853Z  WARN Failed to connect to 10.0.1.243:4000: No route to host (os error 113)
89:2025-10-15T15:08:30.197646Z  WARN Failed to connect to 10.0.1.32:4000: No route to host (os error 113)
92:2025-10-15T15:08:30.837360Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
95:2025-10-15T15:08:33.905356Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
98:2025-10-15T15:08:36.981419Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
101:2025-10-15T15:08:40.049335Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
104:2025-10-15T15:08:43.121680Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
107:2025-10-15T15:08:46.197394Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
110:2025-10-15T15:08:49.265514Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
113:2025-10-15T15:08:52.337454Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
116:2025-10-15T15:08:55.409444Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
119:2025-10-15T15:08:58.481471Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
1





some docker networks and the swarm can create routing rules that
conflict with the ones we create leading to errors such as:

59:2025-10-15T15:07:33.745853Z  WARN Failed to connect to 10.0.1.243:4000: No route to host (os error 113)
89:2025-10-15T15:08:30.197646Z  WARN Failed to connect to 10.0.1.32:4000: No route to host (os error 113)
92:2025-10-15T15:08:30.837360Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
95:2025-10-15T15:08:33.905356Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
98:2025-10-15T15:08:36.981419Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
101:2025-10-15T15:08:40.049335Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
104:2025-10-15T15:08:43.121680Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
107:2025-10-15T15:08:46.197394Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
110:2025-10-15T15:08:49.265514Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
113:2025-10-15T15:08:52.337454Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
116:2025-10-15T15:08:55.409444Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
119:2025-10-15T15:08:58.481471Z  WARN Failed to connect to 10.0.1.91:4000: No route to host (os error 113)
1