Peter Šurda PeterSurda
0 Followers · 0 Following
  • Joined on 2020-04-27
Repositories
12
 Projects
1
 Packages Public Activity Starred Repositories
2
PeterSurda opened issue Sysdeploy/ansible-modules-syncthing#7 2024-05-18 07:22:38 +02:00
Edit folder settings
PeterSurda opened issue Sysdeploy/ansible-modules-syncthing#6 2024-05-18 07:15:39 +02:00
Add support for listing currently configured folders
PeterSurda commented on pull request Sysdeploy/WaitForSyncthing#1 2024-05-07 16:17:28 +02:00
syncthing sync completed or not

One more thing, we can filter the events and then the code looks nicer:

PeterSurda suggested changes for Sysdeploy/WaitForSyncthing#1 2024-05-07 16:17:28 +02:00
syncthing sync completed or not
PeterSurda commented on pull request Sysdeploy/WaitForSyncthing#1 2024-05-07 16:14:24 +02:00
syncthing sync completed or not

I think we only need GET.

PeterSurda commented on pull request Sysdeploy/WaitForSyncthing#1 2024-05-07 16:14:24 +02:00
syncthing sync completed or not

It unnecessarily queries and sleeps. I'd prefer something like this:

PeterSurda commented on pull request Sysdeploy/WaitForSyncthing#1 2024-05-07 16:14:24 +02:00
syncthing sync completed or not

Check here:

collection/plugins/module_utils/syncthing_api.py Line 27 in 31c955c5b9
def _get_key_from_filesystem(self):

PeterSurda suggested changes for Sysdeploy/WaitForSyncthing#1 2024-05-07 16:14:24 +02:00
syncthing sync completed or not

Overall it appears to be correct, but it could be nicer.

PeterSurda pushed to master at Bitmessage/bitmessage-js 2024-05-07 07:52:07 +02:00
7c8b28f451 Add ACK data generation into the feature matrix in readme
PeterSurda merged pull request Bitmessage/bitmessage-js#4 2024-05-07 07:52:06 +02:00
Add ACK data generation into the feature matrix in readme
PeterSurda approved Bitmessage/bitmessage-js#4 2024-05-07 07:51:57 +02:00
Add ACK data generation into the feature matrix in readme
PeterSurda approved Bitmessage/MiNode#1 2024-05-07 07:51:14 +02:00
Enable python 3.11 and resolve TLS issues
PeterSurda pushed to v0.3 at Bitmessage/MiNode 2024-05-07 07:27:33 +02:00
c9a3877b92 Lower logging level for connection error messages in I2PDialer
PeterSurda merged pull request Bitmessage/MiNode#3 2024-05-07 07:27:32 +02:00
Lower logging level for connection error messages in I2PDialer
PeterSurda approved Bitmessage/MiNode#3 2024-05-07 07:27:21 +02:00
Lower logging level for connection error messages in I2PDialer
PeterSurda pushed to master at Sysdeploy/ansible-modules-syncthing 2024-05-06 07:05:05 +02:00
31c955c5b9 Added device_defaults
PeterSurda merged pull request Sysdeploy/ansible-modules-syncthing#2 2024-05-06 07:05:03 +02:00
Added device_default
PeterSurda approved Sysdeploy/ansible-modules-syncthing#2 2024-05-06 07:04:50 +02:00
Added device_default
PeterSurda commented on pull request Sysdeploy/ansible-modules-syncthing#2 2024-05-03 05:58:25 +02:00
Added device_default

Also I would rather use device_defaults, not device_default.

PeterSurda commented on pull request Sysdeploy/ansible-modules-syncthing#2 2024-05-03 05:56:44 +02:00
Added device_default

does this work correctly on lists? e.g. allowedNetworks, igoredFolders?