20% CPU Usage - Uptime Kuma running in a docker container on UNRAID

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Love this program but I'm not sure why but even with no monitors running it immediately starts using 20-25% CPU on the host machine.  I switched to statping-ng but that had some serious DB issues that made it quirky.  Any ideas? I can provide logs etc but I need to know where to look.

📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.4
💻 Operating System and Arch
Unraid 6.12.4
🌐 Browser
Chrome 119.0.6045.125
🐋 Docker Version
20.10.24, build 297e128
🟩 NodeJS Version
18.18.2

no monitors running

That's weird. It should not use much cpu power.
Logs:
docker logs uptime-kuma --follow --tail 100

uptime-kuma is your container name.

Does any of this help diagnose?
(If this doesn't could we use some sort of Node.JS tracing to figure it out?)
root@BleachBox:~# docker logs 1bd4ac075d61 --tail 1000
==> Performing startup jobs and maintenance tasks
changed ownership of '/app/data' from 99:users to 0:0
==> Starting application with user 0 group 0
Welcome to Uptime Kuma
Your Node.js version: 18.18.2
2023-11-16T10:31:05-04:00 [SERVER] INFO: Welcome to Uptime Kuma
2023-11-16T10:31:05-04:00 [SERVER] INFO: Node Env: production
2023-11-16T10:31:05-04:00 [SERVER] INFO: Inside Container: true
2023-11-16T10:31:05-04:00 [SERVER] INFO: Importing Node libraries
2023-11-16T10:31:05-04:00 [SERVER] INFO: Importing 3rd-party libraries
2023-11-16T10:31:07-04:00 [SERVER] INFO: Creating express and socket.io instance
2023-11-16T10:31:07-04:00 [SERVER] INFO: Server Type: HTTP
2023-11-16T10:31:07-04:00 [SERVER] INFO: Importing this project modules
2023-11-16T10:31:07-04:00 [NOTIFICATION] INFO: Prepare Notification Providers
2023-11-16T10:31:07-04:00 [SERVER] INFO: Version: 1.23.4
2023-11-16T10:31:07-04:00 [DB] INFO: Data Dir: ./data/
2023-11-16T10:31:07-04:00 [SERVER] INFO: Copying Database
2023-11-16T10:31:07-04:00 [SERVER] INFO: Connecting to the Database
2023-11-16T10:31:07-04:00 [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-11-16T10:31:07-04:00 [DB] INFO: SQLite Version: 3.41.1
2023-11-16T10:31:07-04:00 [SERVER] INFO: Connected
2023-11-16T10:31:07-04:00 [DB] INFO: Your database version: 0
2023-11-16T10:31:07-04:00 [DB] INFO: Latest database version: 10
2023-11-16T10:31:07-04:00 [DB] INFO: Database patch is needed
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch1.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch1.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch2.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch2.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch3.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch3.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch4.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch4.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch5.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch5.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch6.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch6.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch7.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch7.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch8.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch8.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch9.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch9.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch10.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch10.sql
2023-11-16T10:31:07-04:00 [DB] INFO: Database Patch 2.0 Process
2023-11-16T10:31:07-04:00 [DB] INFO: patch-setting-value-type.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-setting-value-type.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-setting-value-type.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-improve-performance.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-improve-performance.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-improve-performance.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-retry-interval-monitor.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-retry-interval-monitor.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-retry-interval-monitor.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-incident-table.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-incident-table.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-incident-table.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-group-table.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-group-table.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-group-table.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-push_token.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-push_token.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-push_token.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-monitor-method-body-and-headers.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-monitor-method-body-and-headers.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-monitor-method-body-and-headers.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa-invalidate-used-token.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa-invalidate-used-token.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa-invalidate-used-token.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-notification_sent_history.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-notification_sent_history.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-notification_sent_history.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-basic-auth.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-basic-auth.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-basic-auth.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-docker-columns.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-docker-columns.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-docker-columns.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-proxy.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-proxy.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-proxy.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-expiry-notification.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-expiry-notification.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-expiry-notification.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page-footer-css.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page-footer-css.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page-footer-css.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-added-mqtt-monitor.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-added-mqtt-monitor.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-added-mqtt-monitor.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-clickable-status-page-link.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-clickable-status-page-link.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-clickable-status-page-link.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-sqlserver-monitor.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-sqlserver-monitor.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-sqlserver-monitor.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-other-auth.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-other-auth.sql need parents
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-other-auth.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-other-auth.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-grpc-monitor.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-grpc-monitor.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-grpc-monitor.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-radius-monitor.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-radius-monitor.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-radius-monitor.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-add-resend-interval.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-add-resend-interval.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-add-resend-interval.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-ping-packet-size.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-ping-packet-size.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-ping-packet-size.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-maintenance-table2.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-maintenance-table2.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-maintenance-table2.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-gamedig-monitor.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-gamedig-monitor.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-gamedig-monitor.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-google-analytics-status-page-tag.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-google-analytics-status-page-tag.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-google-analytics-status-page-tag.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-body-encoding.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-body-encoding.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-body-encoding.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-description-monitor.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-description-monitor.sql is patching
2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-description-monitor.sql was patched successfully
2023-11-16T10:31:07-04:00 [DB] INFO: patch-api-key-table.sql is not patched
2023-11-16T10:31:07-04:00 [DB] INFO: patch-api-key-table.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-api-key-table.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-tls.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-tls.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-tls.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-maintenance-cron.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-maintenance-cron.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-maintenance-cron.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-parent-monitor.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-parent-monitor.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-parent-monitor.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-invert-keyword.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-invert-keyword.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-invert-keyword.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-json-query.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-json-query.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-json-query.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-kafka-producer.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-kafka-producer.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-kafka-producer.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-certificate-expiry-status-page.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-certificate-expiry-status-page.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-certificate-expiry-status-page.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-oauth-cc.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-oauth-cc.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-oauth-cc.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-timeout-monitor.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-timeout-monitor.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-timeout-monitor.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-gamedig-given-port.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-gamedig-given-port.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-gamedig-given-port.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-notification-config.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-notification-config.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-notification-config.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: patch-fix-kafka-producer-booleans.sql is not patched
2023-11-16T10:31:08-04:00 [DB] INFO: patch-fix-kafka-producer-booleans.sql is patching
2023-11-16T10:31:08-04:00 [DB] INFO: patch-fix-kafka-producer-booleans.sql was patched successfully
2023-11-16T10:31:08-04:00 [DB] INFO: Database Patched Successfully
2023-11-16T10:31:08-04:00 [SERVER] INFO: JWT secret is not found, generate one.
2023-11-16T10:31:08-04:00 [SERVER] INFO: Stored JWT secret into database
2023-11-16T10:31:08-04:00 [SERVER] INFO: No user, need setup
2023-11-16T10:31:08-04:00 [SERVER] INFO: Adding route
2023-11-16T10:31:08-04:00 [SERVER] INFO: Adding socket handler
2023-11-16T10:31:08-04:00 [SERVER] INFO: Init the server
2023-11-16T10:31:08-04:00 [SERVER] INFO: Listening on 3001
2023-11-16T10:31:08-04:00 [SERVICES] INFO: Starting nscd
2023-11-16T10:31:08-04:00 [SERVICES] INFO: Failed to start nscd
2023-11-16T10:32:23-04:00 [SERVER] INFO: Redirect to setup page
2023-11-16T10:32:23-04:00 [AUTH] INFO: Login by token. IP=<IP_ADDRESS>
2023-11-16T10:32:23-04:00 [AUTH] ERROR: Invalid token. IP=<IP_ADDRESS>
2023-11-16T10:32:23-04:00 [AUTH] ERROR: invalid signature
2023-11-16T10:32:23-04:00 [RATE-LIMIT] INFO: remaining requests: 19
2023-11-16T10:32:35-04:00 [AUTH] INFO: Login by username + password. IP=<IP_ADDRESS>
2023-11-16T10:32:35-04:00 [RATE-LIMIT] INFO: remaining requests: 19
2023-11-16T10:32:35-04:00 [AUTH] INFO: Successfully logged in user root. IP=<IP_ADDRESS>

Does any of this help diagnose? (If this doesn't could we use some sort of Node.JS tracing to figure it out?)
root@BleachBox:~# docker logs 1bd4ac075d61 --tail 1000 ==> Performing startup jobs and maintenance tasks changed ownership of '/app/data' from 99:users to 0:0 ==> Starting application with user 0 group 0 Welcome to Uptime Kuma Your Node.js version: 18.18.2 2023-11-16T10:31:05-04:00 [SERVER] INFO: Welcome to Uptime Kuma 2023-11-16T10:31:05-04:00 [SERVER] INFO: Node Env: production 2023-11-16T10:31:05-04:00 [SERVER] INFO: Inside Container: true 2023-11-16T10:31:05-04:00 [SERVER] INFO: Importing Node libraries 2023-11-16T10:31:05-04:00 [SERVER] INFO: Importing 3rd-party libraries 2023-11-16T10:31:07-04:00 [SERVER] INFO: Creating express and socket.io instance 2023-11-16T10:31:07-04:00 [SERVER] INFO: Server Type: HTTP 2023-11-16T10:31:07-04:00 [SERVER] INFO: Importing this project modules 2023-11-16T10:31:07-04:00 [NOTIFICATION] INFO: Prepare Notification Providers 2023-11-16T10:31:07-04:00 [SERVER] INFO: Version: 1.23.4 2023-11-16T10:31:07-04:00 [DB] INFO: Data Dir: ./data/ 2023-11-16T10:31:07-04:00 [SERVER] INFO: Copying Database 2023-11-16T10:31:07-04:00 [SERVER] INFO: Connecting to the Database 2023-11-16T10:31:07-04:00 [DB] INFO: SQLite config: [ { journal_mode: 'wal' } ] [ { cache_size: -12000 } ] 2023-11-16T10:31:07-04:00 [DB] INFO: SQLite Version: 3.41.1 2023-11-16T10:31:07-04:00 [SERVER] INFO: Connected 2023-11-16T10:31:07-04:00 [DB] INFO: Your database version: 0 2023-11-16T10:31:07-04:00 [DB] INFO: Latest database version: 10 2023-11-16T10:31:07-04:00 [DB] INFO: Database patch is needed 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch1.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch1.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch2.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch2.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch3.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch3.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch4.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch4.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch5.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch5.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch6.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch6.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch7.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch7.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch8.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch8.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch9.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch9.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patching ./db/patch10.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Patched ./db/patch10.sql 2023-11-16T10:31:07-04:00 [DB] INFO: Database Patch 2.0 Process 2023-11-16T10:31:07-04:00 [DB] INFO: patch-setting-value-type.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-setting-value-type.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-setting-value-type.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-improve-performance.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-improve-performance.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-improve-performance.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-retry-interval-monitor.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-retry-interval-monitor.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-retry-interval-monitor.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-incident-table.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-incident-table.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-incident-table.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-group-table.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-group-table.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-group-table.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-push_token.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-push_token.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-push_token.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-monitor-method-body-and-headers.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-monitor-method-body-and-headers.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-monitor-method-body-and-headers.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa-invalidate-used-token.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa-invalidate-used-token.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-2fa-invalidate-used-token.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-notification_sent_history.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-notification_sent_history.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-notification_sent_history.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-basic-auth.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-basic-auth.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-basic-auth.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-docker-columns.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-docker-columns.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-docker-columns.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-proxy.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-proxy.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-proxy.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-expiry-notification.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-expiry-notification.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-expiry-notification.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page-footer-css.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page-footer-css.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-status-page-footer-css.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-added-mqtt-monitor.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-added-mqtt-monitor.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-added-mqtt-monitor.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-clickable-status-page-link.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-clickable-status-page-link.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-clickable-status-page-link.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-sqlserver-monitor.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-sqlserver-monitor.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-sqlserver-monitor.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-other-auth.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-other-auth.sql need parents 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-other-auth.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-other-auth.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-grpc-monitor.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-grpc-monitor.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-grpc-monitor.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-radius-monitor.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-radius-monitor.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-radius-monitor.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-add-resend-interval.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-add-resend-interval.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-monitor-add-resend-interval.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-ping-packet-size.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-ping-packet-size.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-ping-packet-size.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-maintenance-table2.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-maintenance-table2.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-maintenance-table2.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-gamedig-monitor.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-gamedig-monitor.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-gamedig-monitor.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-google-analytics-status-page-tag.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-google-analytics-status-page-tag.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-google-analytics-status-page-tag.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-body-encoding.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-body-encoding.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-http-body-encoding.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-description-monitor.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-description-monitor.sql is patching 2023-11-16T10:31:07-04:00 [DB] INFO: patch-add-description-monitor.sql was patched successfully 2023-11-16T10:31:07-04:00 [DB] INFO: patch-api-key-table.sql is not patched 2023-11-16T10:31:07-04:00 [DB] INFO: patch-api-key-table.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-api-key-table.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-tls.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-tls.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-tls.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-maintenance-cron.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-maintenance-cron.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-maintenance-cron.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-parent-monitor.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-parent-monitor.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-parent-monitor.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-invert-keyword.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-invert-keyword.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-invert-keyword.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-json-query.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-json-query.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-json-query.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-kafka-producer.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-kafka-producer.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-added-kafka-producer.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-certificate-expiry-status-page.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-certificate-expiry-status-page.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-certificate-expiry-status-page.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-oauth-cc.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-oauth-cc.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-monitor-oauth-cc.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-timeout-monitor.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-timeout-monitor.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-timeout-monitor.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-gamedig-given-port.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-gamedig-given-port.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-add-gamedig-given-port.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-notification-config.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-notification-config.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-notification-config.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: patch-fix-kafka-producer-booleans.sql is not patched 2023-11-16T10:31:08-04:00 [DB] INFO: patch-fix-kafka-producer-booleans.sql is patching 2023-11-16T10:31:08-04:00 [DB] INFO: patch-fix-kafka-producer-booleans.sql was patched successfully 2023-11-16T10:31:08-04:00 [DB] INFO: Database Patched Successfully 2023-11-16T10:31:08-04:00 [SERVER] INFO: JWT secret is not found, generate one. 2023-11-16T10:31:08-04:00 [SERVER] INFO: Stored JWT secret into database 2023-11-16T10:31:08-04:00 [SERVER] INFO: No user, need setup 2023-11-16T10:31:08-04:00 [SERVER] INFO: Adding route 2023-11-16T10:31:08-04:00 [SERVER] INFO: Adding socket handler 2023-11-16T10:31:08-04:00 [SERVER] INFO: Init the server 2023-11-16T10:31:08-04:00 [SERVER] INFO: Listening on 3001 2023-11-16T10:31:08-04:00 [SERVICES] INFO: Starting nscd 2023-11-16T10:31:08-04:00 [SERVICES] INFO: Failed to start nscd 2023-11-16T10:32:23-04:00 [SERVER] INFO: Redirect to setup page 2023-11-16T10:32:23-04:00 [AUTH] INFO: Login by token. IP=<IP_ADDRESS> 2023-11-16T10:32:23-04:00 [AUTH] ERROR: Invalid token. IP=<IP_ADDRESS> 2023-11-16T10:32:23-04:00 [AUTH] ERROR: invalid signature 2023-11-16T10:32:23-04:00 [RATE-LIMIT] INFO: remaining requests: 19 2023-11-16T10:32:35-04:00 [AUTH] INFO: Login by username + password. IP=<IP_ADDRESS> 2023-11-16T10:32:35-04:00 [RATE-LIMIT] INFO: remaining requests: 19 2023-11-16T10:32:35-04:00 [AUTH] INFO: Successfully logged in user root. IP=<IP_ADDRESS>

That information does not provide us much details. Maybe is it because it is the first time uptime kuma started on the host? Try restarting the uptime kuma.


Added a City

Issue #8 :-
I have added a city for just checking

You must need to add at-least 5 -10 cities to make this a valid PR. @AK-codingmaniac

Ok I will add more cities @Rajdip019

Now check @Rajdip019
If it is correct then please merge it as soon as possible for HacktoberFest 2022

Hey @AK-codingmaniac
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

SignIn / SignUp in ClueLess Website .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


CIR TASK doesn't work

          > > you're right. However, the part using the target description was omitted, and only fitb was evaluated. Unlike the original paper, since it was learned with information in a large batch size, the performance will probably be good. Please let me know if you evaluate it.

…
-----Original Message----- 보낸사람: @.> 받는사람<EMAIL_ADDRESS>참조<EMAIL_ADDRESS>@._> 날짜: 2024. 6. 12 오후 3:56:00 제목: Re: [owj0421/OutfitTransformer] CP task (Issue #6) After modifying the code, I updated the required checkpoints for CP and CIR. We ask for your interest! Hi~is CIR checkpoint named fitb_acc0.64.pth ? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID<EMAIL_ADDRESS>
OK.I am evaluating and reply. I find that you change Resnet-18 to Fashion-clip when backbone. I wonder the performance when using Fashion-clip.
Thank you~

Hi!
I examed no CIR task. But it doesn't work even though using target discription.
I suspect there are two potential reasons: 1) negative samples, 2) image-text fusion
Looking forward to your response!
Originally posted by @zztMermory in https://github.com/owj0421/OutfitTransformer/issues/6#issuecomment-2258452173

Hello, thank you for your interest in my repository.
Sorry for the late reply.
I corrected all errors and uploaded them into code.
Please refer to the various methods of learning and evaluation along with the demo file on the readme.
In the case of CIR
Using the description of the Target Item is called Data leakage, and we learned that it is not used,
Although we are looking for suitable items that are currently an alternative, we are planning to add a function to filter the items to be searched through "category".
Thank you.
Please let me know if there is anything strange.


Project Bitcode issue

In out project, we setting the OTHER_CFLAGS to -fembed-bitcode but it show error:
Showing All Errors Only
ld: bitcode bundle could not be generated because '.../Build/Products/Debug-iphoneos/APNGKit/APNGKit.framework/APNGKit' was built without full bitcode. All frameworks and dylibs for bitcode must be generated from Xcode Archive or Install build for architecture arm64

Is any setting missing or APNGKit didn't support bitcode?

@marcuswu0814
APNGKit supports bitcode. If you are using Carthage to build the framework, it might be related to this issue. https://github.com/Carthage/Carthage/issues/535
I'll try to add it now and please let me know the result.

@marcuswu0814
Oh, after some further investigating, it seems that Carthage has resolved it already: https://github.com/Carthage/Carthage/pull/839
Maybe you are using a very old version of Carthage? Could you try to upgrade your Carthage and try again?

Sorry, I using cocoapod to install APNGKit, so if I try to using Carthage, maybe I can fix this issue?

Maybe, I am not sure about it since there is no such report before. But it's worth to try.

@onevcat Thanks you very much and I will try to using Carthage to build framework later. 👍

I try to using Carthage to add framework to our project. (In workplace's another framework project)
But face this issue:

dyld: Library not loaded: @rpath/APNGKit.framework/APNGKit
  Referenced from: /private/var/containers/Bundle/Application/.../Frameworks/our.framework/our
  Reason: no suitable image found.  Did find:

/private/var/containers/Bundle/Application/F41A8098-E806-4847-AA08-3E37F0218788/.../Frameworks/our.framework/Frameworks/APNGKit.framework/APNGKit: required code signature missing for '/private/var/containers/Bundle/Application/.../my.app/Frameworks/our.framework/Frameworks/APNGKit.framework/APNGKit'

Could you give me some tips? I try lots of ways to solve this issue. :(
Like copy framework, adding Runpath Search Paths... etc.

It means you are not copying the framework to app bundle. You need to follow the Carthage instruction to add a framework copy phase (with carthage's copy framework command line) to use it.

I think I already did that, like following setting:

In project build phases tab
Adding a run script phases
Adding /usr/local/bin/carthage copy-frameworks
Input files $(SRCROOT)/Carthage/Build/iOS/APNGKit.framework

and

In project build phases tab
Adding a copy files phases
Destination set value to Frameworks
Name adding a APNGKit.framework and Code sign on copy is on

I'm sure a follow the step to set all of these setting but it still not work and I don't know how to check if above setting is setting successful.

Just had another read of your error message. It seems that you are trying to use APNGKit in your own framework target, instead of an application target?
I believe it is not the correct way to "embed" a dynamic framework into another framework. The depended framework should also be loaded dynamically, by the final application target.

Finally, my team leader try to add APNGKit into another share framework target (in our Workplace’s another project) by CocoaPod, which didn’t be used by Share extension target.
I didn’t know why and can’t ensure is that the key point cause this issue. But I think if I add it into above frameworks by Carthage, it may also work.
If you need much more information about this issue, I can try to provide it.
Anyway, it working very well now. 👍
I'm really thanks for your help and so sorry spend lots of your time. 😭

@marcuswu0814 Thank you for your feedback. Glad to hear that.
Since there is no other report on this, I think I would just close it now. If anyone else encountered the similar issue, just reopen it and I will dig into it deeper.


Prompt before removal

@teto gave some great feedback in https://github.com/NixOS/nixpkgs/pull/238858#issuecomment-1600786398
I did have some thoughts on autoremoval

https://github.com/mccurdyc/gitrs/blob/eef037029b4667561efecfad59055e6d5504f4a6/src/fs.rs#L37
"sync --archive - archives repositories, to $GITRS_ROOT/.archived"

But I agree there is still a missing case where maybe instead of the specificity of the first point checking for uncommitted changes, you could set a --always-prompt-before-removal flag or the equivalent!

I think the default should be non-destructive: that's the least surprising and less troublesome (if people use sync and get their repo removed, you can be sure they wont ever use gitrs again). I dunno if there is a config file but setting autoremoval could go there for  advanced users.


#3 - Laravel cache contractor

Hi,
You should at least provide a short description. That would make the things easier to understand.
From what I see, that PR doesn't resolve the issue #3 . It only bypasses the exists() method for topics and subscriptions (and so it will reduce the number of calls to the google API). But if they ever get deleted (from the dashboard or any other script), the lib won't be able to re-create them until the cache expires. I'm ok with that, but it needs to be specified in the documentation and should be optional.
Regarding the code, it lacks test and there are other things that could be improved. I will suggest some improvement tomorrow (in case you want to use it in your fork). But sorry I don't think that such a feature is needed for now (and definitely not by default) so I will not merge it.


Request: add dailydevsblog.com to the filter

Evidence: https://dailydevsblog.com/troubleshoot/resolved-in-avro-schema-how-to-wrap-the-array-to-an-object-and-put-it-as-a-union-instead-of-putting-just-array-as-union-102643/
Original: https://stackoverflow.com/questions/71216862/in-avro-schema-how-to-wrap-the-array-to-an-object-and-put-it-as-a-union-instead

Thanks a lot!


Variable explorer : multiple windows open and impossible to close them with shortcuts

Description
What steps will reproduce the problem?

In the variable explorer pane multiple windows open when clicking on a variable (say a list) but they do not update whenever we run the code again, nor get closed automatically. This results in a lot of windows open and no shortcut to clear all of that. Thanks for your help.
 You said:

In the variable explorer pane multiple windows open when clicking on a variable (say a list) but they do not update whenever we run the code again

This will change in Spyder 6 because we added a refresh button to our viewers. So users will be able to update them without closing and reopening variables.
Unfortunately, we can't refresh our viewers automatically after every run because viewing a variable requires making a copy in memory of it. So, if you have a lot of variables open, Spyder will start consuming a lot of memory.

nor get closed automatically. This results in a lot of windows open and no shortcut to clear all of that. Thanks for your help.

We haven't considered this use case before, so thanks for bringing it to our attention. I understand this can be a nuisance with many viewers open. And I like the idea of having a shortcut to close them all at once (which shouldn't be that hard to implement).
What do you think about also adding a shortcut to close the current viewer? Would you find that useful?

If there was a shortcut to clear all the windows I think that would be a huge improvement already! :)

I totally agree. Since we're wrapping up Spyder 6.0, it's probably not going to be available for that version. But I hope we'll have time to implement it for 6.1, to be released during the second half of the year.

For the shortcut to close the current viewer, I am sorry but not so sure what you’re referring to. Might you clarify and I can let you know? Thanks!

I meant the following:

Click on a variable to quickly check its contents.
A viewer is open for it.
Since I just needed that for a quick peek, I don't want to keep that viewer open. So perhaps it'd be useful to simply press a shortcut (say Ctrl+W) to close the viewer and go back to Spyder to keep working on it.

Thanks for the extra input @JulietteCx! We'll take it into account when implementing this feature.


nav_exclude also removes TOC entry

As updating from 0.2.8 to 0.3.2 my items vanished in the Table of Contents (TOC) list, when the children sites were creates with the setting nav_exclude.
In my opinion the expected behavior would be that the navigation list and the TOC decouple: nav_exclude should only exclude the site from the navigation. If I do not want the site to appear in the TOC I would assign another parent (or none).
Screenshots  (see gh-pages repo)
v0.2.8

v0.3.2

Desktop (please complete the following information):

OS: Linux
Browser: Firefox
Version: 80

@Z3NOX indeed, the documentation for excluding pages refers to the main navigation, and does not mention any side-effect on the auto-generated TOC for child pages. Moreover, your screenshots illustrate a sensible use of the auto-generated TOC together with nav_exclude, which is not currently included in the theme regression tests.
As a quick fix for your site, you can pin it to v0.2.8 in _config.yml:
remote_theme<EMAIL_ADDRESS>
It should be possible to fix this issue in the next release.

@Z3NOX thanks for confirming that the updated _includes/nav.html fixes the reported issue.
@pmarsceill if you agree with the fix, I'll submit a PR for it – also adding regression tests where child pages have both nav_exclude: true and parent fields. BTW, when such a page is selected, its parent is still visible in the main navigation and in the breadcrumbs.
Perhaps the documentation for Excluding pages should point out that nav_exclude: true does not exclude pages from the auto-generated TOC? It may then be good to move that section so that it comes after Pages with children.

@Z3NOX, @pmarsceill, the changes in PR #443 are somewhat different from those in the updated _includes/nav.html that I attached in a previous comment. The aim of the PR is to limit the effect of nav_exclude to the main navigation: the auto-generating lists of child pages and the breadcrumbs are to be completely independent of nav_exclude parameters.
@Z3NOX, if you would like to check (locally) before the next release that PR #443 fixes the bug you reported, try temporarily changing to:
remote_theme: pdmosses/just-the-docs@nav-exclude

and remove/hide  _includes/nav.html.

I used jekyll offline and added
gem 'just-the-docs', :git => "git://github.com/pdmosses/just-the-docs.git", :branch => "nav-exclude"

to my Gemfile and removed _includes/nav.html. With this change I can confirm that the reported bug from above seems to be solved - at least for my use case. Thank you!

@Z3NOX thanks for testing, and glad to know that the PR indeed fixes that bug.
Thanks also for showing me how to test a PR by editing the Gemfile without changing _config.yml – I'm a novice with Git and Ruby, and I wasn't aware of that.
BTW, it appears that the breadcrumb links in children of excluded pages were broken in v0.3.1 (and probably all previous versions) but I guess nobody has been using pages with the combination of nav_exclude and has_children.

This issue is fixed in v0.3.3, I hope.


加速yolov8-sahi推理速度

感谢你的工作，我把你的代码替换进去后，推理速度有提升，请问你是对切分的子图堆叠成batch输入网络来加速的吗？我看在SAHI库中还有包含batch_num等后处理加速操作，在你的代码中有体现吗？ultralytics库的代码跳转实在太乱了，跳转找不到对应代码。

Hello, sorry for the late reply.
Indeed the SAHI code is quite hard to follow and this repository is too because I mostly copied and pasted their inference code.
The main addition of this library is this line:
https://github.com/dceluis/sahi_batched/blob/5b050bcb7e12ed086e0d10b38edaa0ef555ac5f3/sahi_batched/main.py#L458
where, instead of passing a single image, we send the whole list of slices. YoloV8 supports sliced inference from a list of images but the original SAHI does not make use of this feature.
I did not modify or include any post-processing code from the original SAHI.


[nebula] Support playlist downloads

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm requesting a site-specific feature
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Global (Europe at least)
Example URLs
https://nebula.tv/jetlag?tab=playlists
Provide a description that is worded well enough to be understood
Hi there !
On nebula, some shows are split into seasons using the playlist feature. Playlist can be queried in the nebula API using something like the following :

Get all playlists from https://content.api.nebula.app/content/CHANNEL_NAME/?include=lessons (yt_dlp already calls that). The returned json contains a ['playlists'] key that can be used to get all the information needed about available playlists

{
   "id":"video_channel:9cea6296-223e-4c7e-a245-d96db75de32f",
   "type":"video_channel",
   "slug":"jetlag",
   ...
   "title":"Jet Lag: The Game",
   "published_at":"2022-05-25T17:53:15Z",
   "description":"We play games where the world is our board.",
   ...
   "playlists":[
      {
         "id":"video_playlist:f5316a93-a773-4bd8-9621-67f091fac8cd",
         "type":"video_playlist",
         "slug":"jetlag-season8weracedfromamericasnorthernmosttosouthernmosttown",
         "title":"Season 8 — We Raced From America’s Northernmost to Southernmost Town"
      },
      {
         "id":"video_playlist:b431b143-9ccf-4011-87d0-8e08830f9ba8",
         "type":"video_playlist",
         "slug":"jetlag-season1connect4acrossamerica",
         "title":"Season 1 — Connect 4 Across America"
      },
      {
         "id":"video_playlist:5cb7ee38-b2b8-4f48-a2fe-d1890973cd4e",
         "type":"video_playlist",
         "slug":"jetlag-season2circumnavigation",
         "title":"Season 2 — Circumnavigation"
      },
      {
         "id":"video_playlist:554a7d6e-1720-4f63-93d4-0499f805c344",
         "type":"video_playlist",
         "slug":"jetlag-season3weplayedtagacrosseurope",
         "title":"Season 3 — We Played Tag Across Europe"
      },
      {
         "id":"video_playlist:1a8cabdd-6771-4588-af52-701cb19d53d6",
         "type":"video_playlist",
         "slug":"jetlag-season4battle4america",
         "title":"Season 4 — Battle 4 America"
      },
      {
         "id":"video_playlist:ef48e0a0-35b3-40d2-9982-e8825ebf4c8f",
         "type":"video_playlist",
         "slug":"jetlag-season5racetotheendoftheworld",
         "title":"Season 5 — Race to the End of the World"
      },
      {
         "id":"video_playlist:9a174855-d592-4556-9179-883f3a342ef6",
         "type":"video_playlist",
         "slug":"jetlag-season6capturetheflag",
         "title":"Season 6 — Capture the Flag"
      },
      {
         "id":"video_playlist:706760c0-eca1-4600-9dcc-5b8634a1abdf",
         "type":"video_playlist",
         "slug":"jetlag-season7weplayedtagacrosseuropeagain",
         "title":"Season 7 — We Played Tag Across Europe (again)"
      }
   ],
   ...
}

You can then request playlist videos using the following link : https://content.api.nebula.app/video_playlists/video_playlist:PLAYLIST_ID/video_episodes/
For example, requesting https://content.api.nebula.app/video_playlists/video_playlist:f5316a93-a773-4bd8-9621-67f091fac8cd/video_episodes/ would give you the following:
{
   "next":null,
   "previous":null,
   "results":[
      {
         "id":"video_episode:c929b040-c8ce-450c-bf8d-408c9e27e6d4",
         "type":"video_episode",
         "slug":"jetlag-season-eight-trailer",
         "title":"Jet Lag Season Eight — Official Trailer",
         "description":"Premieres December 13.\r\n\r\nDiscuss the trailer on [Reddit.](https://www.reddit.com/r/Nebula/comments/18c6gcj/jet_lag_season_eight_official_trailer/)\r\n\r\nWatch new episodes a week early only on Nebula at https://nebula.tv/jetlag",
         "short_description":"Premieres December 13 on Nebula.",
         "duration":140,
         "duration_to_complete":130,
         "published_at":"2023-12-06T15:30:08Z",
         "channel_id":"video_channel:9cea6296-223e-4c7e-a245-d96db75de32f",
         "channel_slug":"jetlag",
         "channel_slugs":[
            "jetlag"
         ],
         "channel_title":"Jet Lag: The Game",
         "category_slugs":[
            "entertainment",
            "travel"
         ],
         ...
      },
      {
         "id":"video_episode:dbcc8c86-4d28-4023-98f9-8042503f5227",
         "type":"video_episode",
         "slug":"jetlag-we-raced-from-americas-northernmost-to-southernmost-town",
         "title":"We Raced From America’s Northernmost to Southernmost Town",
         "description":"Discuss the season premiere on [Reddit.](https://www.reddit.com/r/Nebula/comments/18hjcm9/jet_lag_season_8_begins_now_we_raced_from/)\n\nListen to The Layover: https://nebula.tv/thelayover\n\nOur other channels:\nWendover Productions - https://nebula.tv/wendover\nHalf as Interesting - https://nebula.tv/hai\n\nFollow us on Twitter: http://twitter.com/wendoverpro\n\nCreated by Adam Chase, Sam Denby, and Ben Doyle\n\nFeaturing Sam Denby, Michelle Khare, Adam Chase, Ben Doyle\n\nEditing by Adam Chase, Ben Doyle, Jack MacColl, , Tyson Kroening, Henry Ariza\n\nExecutive Producer Sam Denby\n\nCo-Executive Producer Graham Haerther\n\nSupervising Producer Tyson Kroening\n\nMotion Graphics by Lili Pereira, João Pessegueiro,  Elise Heersink, Sara Stoltman, Mikaila Blackburn, Dom Burgess,  Derek Brown\n\nAudio by Manni Simon, Donovan Bullen\n\nArtwork by Simon Buckmaster\n\nAdditional Game Design by Amy Muller",
         "short_description":"We Raced From America’s Northernmost to Southernmost Town",
         "duration":1368,
         "duration_to_complete":1341,
         "published_at":"2023-12-13T15:30:08Z",
         "channel_id":"video_channel:9cea6296-223e-4c7e-a245-d96db75de32f",
         "channel_slug":"jetlag",
         "channel_slugs":[
            "jetlag"
         ],
         "channel_title":"Jet Lag: The Game",
         "category_slugs":[
            "entertainment",
            "travel"
         ],
         ...
      },
      {
         "id":"video_episode:6fe5ab3f-548b-48be-8391-573967149deb",
         "type":"video_episode",
         "slug":"jetlag-ep-2-we-raced-from-americas-northernmost-to-southernmost-town",
         "title":"Ep 2 — We Raced From America’s Northernmost to Southernmost Town",
         "description":"Discuss this episode on [Reddit.](https://www.reddit.com/r/Nebula/comments/18mx9lt/jet_lag_we_raced_from_americas_northernmost_to/)\n\nListen to The Layover: https://nebula.tv/thelayover\n\nOur other channels:\nWendover Productions - https://nebula.tv/wendover\nHalf as Interesting - https://nebula.tv/hai\n\nFollow us on Twitter: http://twitter.com/wendoverpro\n\nCreated by Adam Chase, Sam Denby, and Ben Doyle\n\nFeaturing Sam Denby, Michelle Khare, Adam Chase, Ben Doyle\n\nEditing by Adam Chase, Ben Doyle, Jack MacColl, , Tyson Kroening, Henry Ariza\n\nExecutive Producer Sam Denby\n\nCo-Executive Producer Graham Haerther\n\nSupervising Producer Tyson Kroening\n\nMotion Graphics by Lili Pereira, João Pessegueiro,  Elise Heersink, Sara Stoltman, Mikaila Blackburn, Dom Burgess,  Derek Brown\n\nAudio by Manni Simon, Donovan Bullen\n\nArtwork by Simon Buckmaster\n\nAdditional Game Design by Amy Muller",
         "short_description":"Ep 2 — We Raced From America’s Northernmost to Southernmost Town",
         "duration":1987,
         "duration_to_complete":1948,
         "published_at":"2023-12-20T15:30:02Z",
         "channel_id":"video_channel:9cea6296-223e-4c7e-a245-d96db75de32f",
         "channel_slug":"jetlag",
         "channel_slugs":[
            "jetlag"
         ],
         "channel_title":"Jet Lag: The Game",
         "category_slugs":[
            "entertainment",
            "travel"
         ],
         ...
      },
      {
         "id":"video_episode:591eba25-b820-405a-a463-291b633772bd",
         "type":"video_episode",
         "slug":"jetlag-ep-3-we-raced-from-americas-northernmost-to-southernmost-town",
         "title":"Ep 3 — We Raced From America’s Northernmost to Southernmost Town",
         "description":"Discuss this episode on [Reddit.](https://www.reddit.com/r/Nebula/comments/18s3a6p/jet_lag_we_raced_from_americas_northernmost_to/)\n\nListen to The Layover: https://nebula.tv/thelayover\n\nOur other channels:\nWendover Productions - https://nebula.tv/wendover\nHalf as Interesting - https://nebula.tv/hai\n\nFollow us on Twitter: http://twitter.com/wendoverpro\n\nCreated by Adam Chase, Sam Denby, and Ben Doyle\n\nFeaturing Sam Denby, Michelle Khare, Adam Chase, Ben Doyle\n\nEditing by Adam Chase, Ben Doyle, Jack MacColl, , Tyson Kroening, Henry Ariza\n\nExecutive Producer Sam Denby\n\nCo-Executive Producer Graham Haerther\n\nSupervising Producer Tyson Kroening\n\nMotion Graphics by Lili Pereira, João Pessegueiro,  Elise Heersink, Sara Stoltman, Mikaila Blackburn, Dom Burgess,  Derek Brown\n\nAudio by Manni Simon, Donovan Bullen\n\nArtwork by Simon Buckmaster\n\nAdditional Game Design by Amy Muller",
         "short_description":"Ep 3 — We Raced From America’s Northernmost to Southernmost Town",
         "duration":2474,
         "duration_to_complete":2425,
         "published_at":"2023-12-27T15:30:08Z",
         "channel_id":"video_channel:9cea6296-223e-4c7e-a245-d96db75de32f",
         "channel_slug":"jetlag",
         "channel_slugs":[
            "jetlag"
         ],
         "channel_title":"Jet Lag: The Game",
         "category_slugs":[
            "entertainment",
            "travel"
         ],
         ...
      },
      {
         "id":"video_episode:5c7b25e7-effa-41da-a225-2dd7f70bfa69",
         "type":"video_episode",
         "slug":"jetlag-ep-4-we-raced-from-americas-northernmost-to-southernmost-town",
         "title":"Ep 4 — We Raced From America’s Northernmost to Southernmost Town",
         "description":"Discuss this episode on [Reddit.](https://www.reddit.com/r/Nebula/comments/18xm1m0/jet_lag_we_raced_from_americas_northernmost_to/)\n\nListen to The Layover: https://nebula.tv/thelayover\n\nOur other channels:\nWendover Productions - https://nebula.tv/wendover\nHalf as Interesting - https://nebula.tv/hai\n\nFollow us on Twitter: http://twitter.com/wendoverpro\n\nCreated by Adam Chase, Sam Denby, and Ben Doyle\n\nFeaturing Sam Denby, Michelle Khare, Adam Chase, Ben Doyle\n\nEditing by Adam Chase, Ben Doyle, Jack MacColl, , Tyson Kroening, Henry Ariza\n\nExecutive Producer Sam Denby\n\nCo-Executive Producer Graham Haerther\n\nSupervising Producer Tyson Kroening\n\nMotion Graphics by Lili Pereira, João Pessegueiro,  Elise Heersink, Sara Stoltman, Mikaila Blackburn, Dom Burgess,  Derek Brown\n\nAudio by Manni Simon, Donovan Bullen\n\nArtwork by Simon Buckmaster\n\nAdditional Game Design by Amy Muller",
         "short_description":"Ep 4 — We Raced From America’s Northernmost to Southernmost Town",
         "duration":2276,
         "duration_to_complete":2231,
         "published_at":"2024-01-03T15:30:08Z",
         "channel_id":"video_channel:9cea6296-223e-4c7e-a245-d96db75de32f",
         "channel_slug":"jetlag",
         "channel_slugs":[
            "jetlag"
         ],
         "channel_title":"Jet Lag: The Game",
         "category_slugs":[
            "entertainment",
            "travel"
         ],
         ...
      },
      {
         "id":"video_episode:9f8ea5c5-78a6-4c16-aa64-3e6f56d5156d",
         "type":"video_episode",
         "slug":"jetlag-ep-5-we-raced-from-americas-northernmost-to-southernmost-town",
         "title":"Ep 5 — We Raced From America’s Northernmost to Southernmost Town",
         "description":"Discuss this episode on [Reddit.](https://www.reddit.com/r/Nebula/comments/193awvj/jet_lag_we_raced_from_americas_northernmost_to/)\r\n\r\nListen to The Layover: https://nebula.tv/thelayover\r\n\r\nOur other channels:\r\nWendover Productions - https://nebula.tv/wendover\r\nHalf as Interesting - https://nebula.tv/hai\r\n\r\nFollow us on Twitter: http://twitter.com/wendoverpro\r\n\r\nCreated by Adam Chase, Sam Denby, and Ben Doyle\r\n\r\nFeaturing Sam Denby, Michelle Khare, Adam Chase, Ben Doyle\r\n\r\nEditing by Adam Chase, Ben Doyle, Jack MacColl, , Tyson Kroening, Henry Ariza\r\n\r\nExecutive Producer Sam Denby\r\n\r\nCo-Executive Producer Graham Haerther\r\n\r\nSupervising Producer Tyson Kroening\r\n\r\nMotion Graphics by Lili Pereira, João Pessegueiro,  Elise Heersink, Sara Stoltman, Mikaila Blackburn, Dom Burgess,  Derek Brown\r\n\r\nAudio by Manni Simon, Donovan Bullen\r\n\r\nArtwork by Simon Buckmaster\r\n\r\nAdditional Game Design by Amy Muller",
         "short_description":"Ep 5 — We Raced From America’s Northernmost to Southernmost Town",
         "duration":2668,
         "duration_to_complete":2615,
         "published_at":"2024-01-10T15:30:11Z",
         "channel_id":"video_channel:9cea6296-223e-4c7e-a245-d96db75de32f",
         "channel_slug":"jetlag",
         "channel_slugs":[
            "jetlag"
         ],
         "channel_title":"Jet Lag: The Game",
         "category_slugs":[
            "entertainment",
            "travel"
         ],
         ...
   ]
}

I'd love to be able to download a specific playlist or all videos from a channel in a playlist folder. However, as far as I know, there is no way to get playlist information in yt-dlp right now on nebula.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
> I don't thing there is yet a command for what I want to do, but here is the output of yt-dlp -vU for reference anyways.

yt-dlp -vU
[debug] Command-line config: ['-vU']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [f10589e34] (pip)
[debug] Python 3.11.6 (CPython arm64 64bit) - macOS-14.2.1-arm64-arm-64bit (OpenSSL 3.2.0 23 Nov 2023)
[debug] exe versions: ffmpeg 6.0 (setts), ffprobe 6.0, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.47.0, requests-2.31.0, sqlite3-3.44.2, urllib3-2.1.0, websockets-12.0
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1798 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp)

How exactly would you expect this to work?
These playlists don't have dedicated URLs, so you could not easily tell yt-dlp to only download a single playlist.
Currently, https://nebula.tv/jetlag?tab=playlists is treated as https://nebula.tv/jetlag and downloads all videos of the channel.

In a perfect world, and I know it might not be as discoverable as you'd like, it could be something like :
https://nebula.tv/jetlag?tab=playlists#playlist_name:Season%208%20%E2%80%94%20We%20Raced%20From%20America%E2%80%99s%20Northernmost%20to%20Southernmost%20Town (using the URL encoded playlist name as the hash, or a playlist_id: for program use)
Alternatively, maybe just forget about downloading a single playlist and just expose the playlist names in the naming variables, if that's possible?

I believe that the added complexity would not be worth it. Trying to smuggle the playlist name in the URL would be janky and probably never used. Even if one knew about this feature, I would guess that most people would at that point just prefer to manually download the episodes instead of having to URL encode the title.
Providing what playlist an individual video is in (through tags/categories), would come with a bunch of overhead and additional logic. Each playlist of a channel would need to be queried to check if the video is in that playlist. For jetlag that would be at least 8 additional HTTP requests per video, plus the added complexity to the extractor.
There maybe is the option of using nested playlists for the playlists tab, but even there I am not entirely convinced that it is worth it. If someone feels like this is something worthwhile pursuing, there is always the option of modifying the extractor with plugins or making a PR.
If Nebula ever adds dedicated URLs for playlists, this would be a lot less awkward to implement/use.


Remove the 2 lines fix to set the theme.

Properly sort out "hotfix" related to issue #180  in the HomeActivity onResume()

Should be fixed. Closing!


pomotroid: init at 0.13.0

Motivation for this change
Closes #131264
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Uses Electron 9, which is EOL.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/435


Failure to create a record or spreadsheet for GSE183904

Attached a screeshot:

Interestingly, when project is created by DOI, I attempted the spreadsheet generation as well.
The error is now very curious in terms of text:


refactor(linter): Use parsed patterns for unicorn/prefer-string-replace-all rule

part of https://github.com/oxc-project/oxc/issues/5416

Replaces the is_simple_string method with a more robust check against the parsed terms from the regular expression.

#5949
#5943  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @camchenry and the rest of your teammates on  Graphite

@Boshen do you know why this isn't mergeable? I'm not too experienced with Graphite, could we just merge this with GitHub?

@ Boshen do you know why this isn't mergeable? I'm not too experienced with Graphite, could we just merge this with GitHub?

probs bug in graphite or an error in the GH api "couldn't merge this PR because it failed for an unknown reason."
i just added the merge lable again and it was successful


Substitute special runtime-defined properties like 'shared.config.dir' in copyDependencies

Signed-off-by: Scott Kurz<EMAIL_ADDRESS>Fixes #1324
This isn't complete .. just wanted to get something out there to continue the discussion.

I'm going to close this.   As noted in https://github.com/OpenLiberty/ci.maven/issues/1324#issuecomment-1049911160   this is a solution with some serious gaps.


yt.streams.get_highest_resolution() is not able to get me the highest resolution available video

Describe the bug
I am trying to download the highest quality video available for the video but yet its just downloading a 360p or 480p video everytime even.
My code:
from pytubefix import YouTube
from pytubefix.cli import on_progress
from pytubefix.exceptions import *

try:
    url = "https://www.youtube.com/watch?v=-pSf9_MgsZ4"

    yt = YouTube(url, on_progress_callback = on_progress)
    print(yt.title)

    ys = yt.streams.get_highest_resolution()
    ys.download()
except Exception as e:
    print("Error: ",e)

To Reproduce
Steps to reproduce the behavior:

Try to copy-paste and run it on your machine, it would give the same result.

Expected behavior
Whatever highest quality video is available should have been downloaded.
Screenshots
If applicable, add screenshots to help explain your problem.
For the video in the above code link, has the highest video availability of 4k

but still its downloading in 360p quality:

Desktop (please complete the following information):

OS: Arch Linux
Python Version 3.12.3
Pytubefix Version 6.7.0

See this issue #128


Add better error messages for unavailable swarm commands

Add more descriptive error messages to swarm control commands depending on the current state of the node.
fixes #23845
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>

LGTM 🐯

LGTM


ProductAttribute.code should be a unique field

Issue Summary
The product attribute should have a unique code.
You can only assign one attribute with that code in the dashboard-product anyway.
Steps to Reproduce

In dashboard, go to product-type - product attributes page: /dashboard/catalogue/product-type/1/update/
Add two product attributes with the same name. (I use name att1 and type text.)
Save the form. Both attributes with the same code are saved and shown on the page.
Go to one dashboard/products page for that product class, /dashboard/catalogue/products/8/?upc=&title=shirt, only one attribute name is shown on the form.
Note that even I create attributes with different types, only one attribute of that code will be shown on the dashboard/products page.

Expected result:

Give Exception when saving the attribute - "Duplicate product attributes code / attributes with this code already exists."
Enforce the uniqueness of AbstractProductAttribute.code. This is a SlugField.
Another way is to enforce the unique_together of (code, type), while the data retrieval part needs to be updated as well.
I can work on the PR for this issue, please let me know.

Cause
Here have the assumption that attribute.code should be unique.
File: src/oscar/apps/dashboard/catalogue/forms.py
    def set_initial_attribute_values(self, product_class, kwargs):
        ...
        for attribute in product_class.attributes.all():
            try:
                value = instance.attribute_values.get(
                    attribute=attribute).value
            except exceptions.ObjectDoesNotExist:
                pass
            else:
                kwargs['initial']['attr_%s' % attribute.code] = value

Technical details

Python version: 3.9.7
Django version: 3.2.7
Oscar version: master

We cannot globally enforce uniqueness of attribute codes, because Oscar permits reusing the same attribute code on different product types (and this can be useful to be able to do). I think the solution here would be to add validation on the formset for any given product class, to ensure that a code isn't repeated for that product class. PR welcome for this - note that it will be a bit messy to properly handle validation of deleted rows etc.

Can't we just addunique_together = ('code', 'product_class',) on the ProductAttribute model?

No, for the reason I mentioned in my comment: Oscar permits reusing the same attribute code on different product types. Imagine you have 20 product types which all share one attribute - Oscar currently allows that and it is (from my experience) a common use case.

Not sure if I'm misunderstanding you, but I understand the reusing the same attribute code on multiple product types is common. However, if you add unique_together = ('code', 'product_class',) on the ProductAttribute model's Meta class, it prevents you from using the same code for the product type you're editing. You can still use the same code on other product types.

My apologies, you're right and I misunderstood - unique_together as you describe would work.


[live] <= [master]

Docs Build status updates of commit 16d84b1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

advocates/index.html.yml
:warning:Warning
View
Details

advocates/david-smith.yml
:white_check_mark:Succeeded
View

advocates/map.yml
:white_check_mark:Succeeded
View

validation/Program.cs
:white_check_mark:Succeeded

advocates/index.html.yml

Line 10, Column 8: [Warning-file-not-found] Invalid file link: './map'.
Line 12, Column 8: [Warning-file-not-found] Invalid file link: './tweets'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[CONTP-535] optimise tagger server chunking function by processing chunks in place

What does this PR do?
This PR optimises tagger server chunking logic by processing chunks in place instead of duplicating them in memory.
Motivation
Memory and CPU optimisation.
Results of benchmarks:
goos: linux
goarch: arm64
pkg: github.com/DataDog/datadog-agent/comp/core/tagger/server
                               │    old.txt    │               new.txt               │
                               │    sec/op     │    sec/op     vs base               │
ProcessChunks/100-items-10       2399.5n ± 47%   239.8n ±  4%  -90.01% (p=0.002 n=6)
ProcessChunks/1000-items-10      35.072µ ± 13%   2.344µ ± 11%  -93.32% (p=0.002 n=6)
ProcessChunks/10000-items-10     365.19µ ±  5%   22.56µ ± 18%  -93.82% (p=0.002 n=6)
ProcessChunks/100000-items-10    3435.1µ ±  7%   222.5µ ± 16%  -93.52% (p=0.002 n=6)
ProcessChunks/1000000-items-10   29.059m ±  9%   2.219m ± 31%  -92.36% (p=0.002 n=6)
geomean                           314.3µ         22.87µ        -92.72%

                               │   old.txt    │                 new.txt                  │
                               │     B/op     │     B/op      vs base                    │
ProcessChunks/100-items-10       2.969Ki ± 0%   0.000Ki ± 0%  -100.00% (p=0.002 n=6)
ProcessChunks/1000-items-10      29.02Ki ± 0%    0.00Ki ± 0%  -100.00% (p=0.002 n=6)
ProcessChunks/10000-items-10     370.7Ki ± 0%     0.0Ki ± 0%  -100.00% (p=0.002 n=6)
ProcessChunks/100000-items-10    4.165Mi ± 0%   0.000Mi ± 0%  -100.00% (p=0.002 n=6)
ProcessChunks/1000000-items-10   44.65Mi ± 0%    0.00Mi ± 0%  -100.00% (p=0.002 n=6)
geomean                          362.1Ki                      ?                      ¹ ²
¹ summaries must be >0 to compute geomean
² ratios must be >0 to compute geomean

                               │   old.txt   │                 new.txt                 │
                               │  allocs/op  │  allocs/op   vs base                    │
ProcessChunks/100-items-10        81.00 ± 0%     0.00 ± 0%  -100.00% (p=0.002 n=6)
ProcessChunks/1000-items-10       759.0 ± 0%      0.0 ± 0%  -100.00% (p=0.002 n=6)
ProcessChunks/10000-items-10     7.514k ± 0%   0.000k ± 0%  -100.00% (p=0.002 n=6)
ProcessChunks/100000-items-10    75.02k ± 0%    0.00k ± 0%  -100.00% (p=0.002 n=6)
ProcessChunks/1000000-items-10   750.0k ± 0%     0.0k ± 0%  -100.00% (p=0.002 n=6)
geomean                          7.638k                     ?                      ¹ ²
¹ summaries must be >0 to compute geomean
² ratios must be >0 to compute geomean

Describe how you validated your changes

Unit tests and E2E are sufficient.
As long as remote tagger still works, then everything is good.
Possible Drawbacks / Trade-offs
None.
Additional Notes

I have added benchmark tests and included all details in the README.md file

/merge


Support for Swarm Intelligence and Evolutionary Algorithms

I am interested in using Flow for VANETs (Vehicular Ad hoc NETworks) routing protocols, which play a key role in the design and development of Intelligent Transportation Systems. Besides RL,
genetic algorithms, particle swarm, ant and bee colony optimization based routing algorithms for VANETs already exists in literature. Does Flow supports these algorithms? If not, how difficult would it be to integrate these algorithms from python or C++ libraries.

Definitely! Flow is abstractly written to support the gym interface so you can always write a wrapper environment that calls the step and reset methods of Flow and then performs training around it. Essentially all Flow cares about is that you have a method that computes actions and passes it to Flow's step function, and then a method for resetting the environment when a rollout is done.
We do not however, have these algorithms built in. If you have a more specific use case in mind we're happy to help sketch out in detail what that might look like.

I know Flow is integrated with SUMO. For VANET experiments, I need wireless communication networks simulator such as OMNeT++ (https://omnetpp.org/intro/) alongside of road traffic network simulator like SUMO. Does Flow supports any wireless communication networks simulator?

Hi @BHGEdeveloper we haven't put any work into integrating those wireless communication simulators; if you're interested in building out or testing such support I can't imagine it'll be a ton of work and we're happy to help you sketch out how the integration would look like!


feat: Add support for eslint@8

Upgrade devDependencies
Update peerDependencies to include both ESLint v7 and v8
Add workflow to CircleCI to run the tests against all the supported versions of ESLint.

Fixes #34

@trevor-bliss Please review this PR. It resolves issues with npm dependencies.


Fill in OIDC test gaps

#772 The OIDC test coverage isn't as bad as I remembered, we've filled in a lot of the gaps already. Here are a few touch-ups I added in the process.

@Tratcher,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Perpetual crash back to menu

multiplayer menu appears now in mod menu
selecting multiplayer from mod crashes after brief loading popup back to menu
zero multiplayer mod play
single player only
aka, zero change besides the MPPatch version subtitle at the bottom of the menu screen

Likely duplicate of #79


build/install fails from AUR/yay (setuptools-scm can't detect version from source tarball)

I have to admit I have no idea what to do with the following error when updating (yay gcalcli on manjaro)
    _Distribution.__init__(self, dist_attrs)
  File "/usr/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 284, in __init__
    self.finalize_options()
  File "/usr/lib/python3.12/site-packages/setuptools/dist.py", line 658, in finalize_options
    ep(self)
  File "/usr/lib/python3.12/site-packages/setuptools_scm/_integration/setuptools.py", line 123, in infer_version
    _assign_version(dist, config)
  File "/usr/lib/python3.12/site-packages/setuptools_scm/_integration/setuptools.py", line 58, in _assign_version
_version_missing(config)
  File "/usr/lib/python3.12/site-packages/setuptools_scm/_get_version_impl.py", line 117, in _version_missing
    raise LookupError(
LookupError: setuptools-scm was unable to detect version for .cache/yay/gcalcli/src/gcalcli-4.5.0.

Make sure you're either building from a fully intact git repository or PyPI tarballs. Most other sources (such as GitHub's tarballs, a git checkout without the .git folder) don't contain the necessary metadata and will not work.

For example, if you're using pip, instead of https://github.com/user/proj/archive/master.zip use git+https://github.com/user/proj.git#egg=proj
==> ERROR: A failure occurred in build().
    Aborting...

Manjaro builds from aur.archlinux.org/packages/gcalcli, correct? It's designed to get the version number from git labels, but I guess this is using a source snapshot that's missing .git dir.
Might be possible to force the version number somehow, but obviously workarounds shouldn't be needed to just yay update.

Commented on https://aur.archlinux.org/packages/gcalcli. I think it needs SETUPTOOLS_SCM_PRETEND_VERSION_FOR_GCALCLI=$pkgver in the AUR package to be able to build from a source tarball like that. Not sure if that's ideal or there's a better way for the AUR package to fetch the sources without losing attribution, but I did find another package https://aur.archlinux.org/packages/python-cmcrameri doing the same.
I'm not sure you can or should override that directly in your yay command but if you like you could try it in the meantime.

(I didn't see SETUPTOOLS_SCM_PRETEND_VERSION_FOR_GCALCLI added in the PKGBUILD yet so I still want to keep this open until we can verify it's fixed for pacman/yay without any workarounds.)

Should be fixed in the 4.5.0-3 update I just pushed!

FYI also just verified the fix takes care of yay (probably obvious, but I wasn't familiar with yay or manjaro before this)...


ImportError: No module named 'utils'

I'm new to the Python and Django world so excuse me if this doesn't make the most sense. But I don't think this works with the latest version of Django or Django CMS. I'm not sure how to tell where this is breaking.
But I did not see an installation guide of how to install this manually. Yesterday I tried to add it to my project with pip install. That worked fine but when I tried to make migrations it exploded. I wasn't sure if I did this wrong or maybe this app wasn't meant to be installed this way so I tried adding it the way it was meant to by adding the app to a project I created in the Divio control page.
However, I'm getting the same error. My site is setup with Python 3.5 and the latest version of Django CMS. Is this a known issue? There shouldn't be any dependencies I need since those should have been added along with this, right?

Hi @pinksharpii
We also ran into this problem. Have you resolved it somehow?
Thx

I forget exactly. Something wasn't included properly. Try looking through installed apps and making sure everything is included properly. And make sure you makemigrations. If all else fails maybe try uninstalling and reinstalling in case something got missed on install. I know that's not a lot to go off but I hope it helps. I ended up not using this plugin in the end.


[Bug]: Home page is not much attractive and the page is not redirecting.

Bug Description
Home page is not much attractive and the page is not redirecting.
Provide a detailed description of the bug
Images related to movies can be added to make the page more alluring and a logo can be added to enhance the page.
A directory link can be added to redirect the home page.
Expected Behavior
Will be adding images on the home page making it look more attractive.
A link for re directing the home page.
Please assign me these issues under Hacktoberfest and gssoc'24 extended.
What browsers are you seeing the problem on?
Chrome
Put here any screenshots or videos (optional)

By submitting this issue, you agree to

[X] I agree to follow this project's Code of Conduct
[X] I’ve read all the issues in the issue section, and this has not been reported yet.

Other Information

[X] I'm a GSSoC '24 Extended contributor
[X] I'm a Hacktoberfest '24 contributor
[X] I am willing to work on this issue (optional)

Please assign me these issues under Hacktoberfest and gssoc'24 extended.

Please assign it to me.I want to work on it

@akansha-02 This is not the issue. You have to first login to access home page.

duplicate


tBTC dApp: UI/UX Suggestion - Homepage/Back button

From my observation, it is needed for tBTC dApp to have home button(back).
It is necessary to have it in case of someone misclick the Deposit button while he is trying to Redeem or vice versa.
Not to mention we might have some more menus in the future, and what should we do if we do not have home button if we want to get back to the home page?

Yep, a lot of this is going to be handled as we roll out the changes to the information architecture outlined in #222. Going to close this issue in the meantime.


Update MD file on new branch 2017-11-21_13-26-50

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


💡 Feature Idea: Support combo style grouping of nodes & links for the data visualization

Guidelines
Is your feature request related to a problem? Please describe.
As a user rendering lots of data on a graph, specifically related data, a combo feature would help visually simplify the complexity of  of the graph by :

hiding large sets of related nodes initially
allow the user to click (drilldown) into the node combo to reveal the information, this can happen for any number of levels
offering a way for users to explore the graph following the principle of progressive disclosure (give details when I need it, hide it when i dont)

Describe the solution you'd like

An addition of a "combo" API into the library, offering user's another way of visualizing data

Describe alternatives you've considered
The only 2 libraries that I am aware of that offer this functionality are:

[Open Source] - Ant Visualization group's G6 Typescript library (Graphin, a react wrapper around G6)
[PAID license] - Cambridge Intelligence's Keylines JS library & Regraph (React wrapper around Keylines library)
[Unmaintained since 2017-ish] -- Cisco NextUI Node sets

example

Question(s)

Is this combo feature something that's worth including into Sigma.js itself, or is it better to talk with the graphology ?
Seems like this would be a great base feature to have in Graphology so that any library (including this or other) can take advantage of the benefits

Demo Idea (references from other libraries)

https://user-images.githubusercontent.com/6743796/148876265-8cda468d-0d67-4afc-857e-667673b8676e.mp4
https://user-images.githubusercontent.com/6743796/148875939-d1ca9d20-7fcd-42e5-bf37-3a0a9f85fcc6.mp4

References

G6 Overview of combos
Combo article by Cambridge intelligence 1
Combo article by Cambridge intelligence 2
Combo article by Cambridge Intelligence 3

I think this is a great idea and it has a lot of use cases. In my own project, I've implemented a version of this by selectively hiding and revealing nodes according to an underlying tree structure, but it's not quite as fancy as the examples given. If this were a native feature, it would certainly make this task a lot simpler.

In my own project, I've implemented an approximate version of this by selectively hiding and revealing nodes according to an underlying tree structure, but it's not quite as fancy as the examples given

though this certainly won't be a simple feature to implement.
I figured

@avenzi -  seeing some examples would be awesome. I'd be curious to learn how different people have approached this problem. Is there a github repo or codesanbox.io you could share? 🙏

Unfortunately I don't have anything simple that isn't part of a much larger project, but I can share how I've been trying to do it. Essentially I've created a separate tree structure that holds all the information about nodes and their parents/children. A parent node can be expanded through some user trigger (I chose double-clicking), which immediately hides that parent node and un-hides the children. Then you can add some things like animating the children nodes expanding outwards and visual stuff like that. That's pretty much the gist of it, and it doesn't look as nice as the examples given because it doesn't really implement that nice "grouping" behavior.
Ultimately, I would assume that if this were to be implemented in Sigma, it would require much more than just my hacky method of using existing features to emulate it. Things like displaying edges between groups and determining node placement within groups would need to be figured out.

Hello @avenzi and @cliffordfajardo,
this idea is clearly a legitimate UX concern but, as demonstrated by @avenzi, this feature can very well be implemented from userland. I think, and @jacomyal will chime in to infirm what I am telling you if necessary, that sigma.js' scope is a bit less high-level. What I mean is that we think sigma.js, as a library, should enable you to realize this UX feature, but we also think this idea is too complex and too opinionated (also you need to make plenty of design choice to adapt this kind of feature to your own needs, and we could not be able to make those choice for you or remain generic enough) to be part of sigma.js' core. This said, this would be a very good use case for some kind of external sigma plugin/module/library/package that anyone could maintain.
So I will currently close this issue but feel free to reopen it if you feel sigma's current state does not allow you to develop this feature on your end. Don't hesitate to still discuss on the closed issue if you want some advice if you endeavor to implement this and have a hard time grasping some details.
In the same spirit, feel free to reopen the graphology issue if you feel some clever generic indexation scheme could help you achieve your goal from graphology-indices or graphology-utils for instance.

Thanks for adding context - thanks!

Update G6 now supports the combos I illustrated above

https://github.com/antvis/G6/discussions/3435


[example] Gatsby sandbox link doesn't work out-of-the-box

The gatsby example sandbox link doesn't run because sandbox defaults to node 10. It's simple to fork the base codesandbox in order to bump the version with a configuration file, and the readme for the gatsby example should be updated.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Build fails while following the codesandbox link in examples/gatsby
Expected Behavior 🤔
Build succeeds when following the codesandbox link
Steps to Reproduce 🕹
Steps:

Base codesandbox link goes here: https://codesandbox.io/s/github/mui-org/material-ui/tree/HEAD/examples/gatsby
If you follow it, you will get a node version error.

Context 🔦
https://codesandbox.io/s/github/mui-org/material-ui/tree/HEAD/examples/gatsby is my fork that changes nothing except bumping the version in a config file. I can't commit to maintaining an image to keep it up to date, so I haven't put in a PR to redirect the link there.

The gatsby examples (examples/gatsby, examples/gatsby-theme), nextjs (examples/nextjs, examples/nextjs-with-typescript) and other SSR examples (examples/ssr need to use node 12 via creating a  sandbox.config.json with
{
  "container": {
    "node": "12"
  }
}

The file needs to be next to the corresponding package.json.

I would like to take this issue

A bit related https://github.com/mui-org/material-ui/pull/27331#issuecomment-898443080


PF-1173: CLI command for GCS object reference type

Add CLI command for reference type GCS object.
add-ref: It could be a reference to a gcs folder foo/ or a specific file in the folder  foo/bar.txt or every objects in the folder foo/*. If the user have folder level access, they will be able to add a reference to all objects in that folder and a reference to that folder. If the user have only partial access to the folder, they will only be able to add reference to the object that they have access to.
update: a user can only update the reference if they have access to the referencing target. If they want to update the reference to point to another GCS object, they must also have access to that gcs object.
describe: if the user has no access to the gcs object, they won't be able to see the detailed gcs blobinfo such as size.
resolve: will resolve to gs://bucketName/path/to/blob or bucketName/path/to/blob depending on whether the gs:// prefix is needed.

Added test for the case when the user have partial access to a folder/ and test when the user ahve access to the folder due to it being a uniform access bucket.

Almost.
WSM will check that the user has at least READ access to the object (if it exists) or the path contains a folder object that the user has READ access to (e.g. foo/bar/*) where the user may have no full access to the bucket but access to foo/bar/.
added description in README


temporal: enable tests

temporal: enable tests

I think if it takes that much to get the tests to pass it is better to keep them disabled.

I think if it takes that much to get the tests to pass it is better to keep them disabled.

Integration tests and databases are disabled. But A LOT of tests are running. It is not skipping that much as you might think.

I'm referring to the size of postPatch. Anything more than a couple of lines (either substituteInPlace or rm) doesn't seem like a good idea, more of a maintainability burden. Are you going to add yourself as a maintainer for this package to ensure that doCheck/postPatch continue to work with new versions?

I also don't think this is worth it, better to upstream a patch that skips all of these if the -short flag is used.

I also don't think this is worth it, better to upstream a patch that skips all of these if the -short flag is used.

Are you going to do it then? And make tests work?
Realize the solution I'm offering here is working now. We are going from 0 tests to lots of tests.
It can be improved later.

Realize the solution I'm offering here is working now. We are going from 0 tests to lots of tests.

Tests aren't useful if they break with every new release, which is what will happen with this approach. In order for this to be maintainable, the constraints need to be enforced upstream, by creating a limited test set run with -short that is checked in their CI.


Edit Awesome List

There are some repositories that host readme.md instead of README.md which results in Page not found error on Github.
For example
https://github.com/sindresorhus/awesome-nodejs/edit/master/README.md
which should be
https://github.com/sindresorhus/awesome-nodejs/edit/master/readme.md
Maybe a query could be done beforehand to verify that this file exists?

Maybe a query could be done beforehand to verify that this file exists?

I was thinking of how I can solve this.
In near future, what I want to do is go inside each of the awesome lists and parse results to save to cache for all lists. So you search a list in Alfred, press enter and then inside Alfred again search for result you need (super fast as everything is cached). Alternatively you could press cmd + return and open the list in browser.
For opening CONTRIBUTING.md page I am not quite sure how to solve it. I wish GitHub solved it on their end so contributing.md and CONTRIBUTING.md are the same but since that's not the case your solution seems to be the only choice. It just seems kind of expensive to do it. But maybe I am wrong.

There are some repositories that host readme.md instead of README.md which results in Page not found error on Github.

Can you explain a case where this happens and is an issue?

I randomly stumbled upon this. When trying to open awe node with edit list command.
It's not a serious issue, since the workflow itself works.

I'm wondering if it's possible to do a GraphQL query on the root of a repository, parse the result for needed file and then use the provided name. Or show an error that the file doesn't exist.
Something like this:
{
  repository(owner: "sindresorhus", name: "awesome-nodejs") {
    defaultBranchRef {
      target {
        ... on Commit {
          tree {
            entries {
              name
              type
            }
          }
        }
      }
    }
  }
}

Which returns:
{
  "data": {
    "repository": {
      "defaultBranchRef": {
        "target": {
          "tree": {
            "entries": [
              {
                "name": ".editorconfig",
                "type": "blob"
              },
              {
                "name": ".gitattributes",
                "type": "blob"
              },
              {
                "name": ".github",
                "type": "tree"
              },
              {
                "name": "code-of-conduct.md",
                "type": "blob"
              },
              {
                "name": "contributing.md",
                "type": "blob"
              },
              {
                "name": "media",
                "type": "tree"
              },
              {
                "name": "readme.md",
                "type": "blob"
              }
            ]
          }
        }
      }
    }
  }
}

This might work. Will try it in a bit.


Tag the source

Could you please tag the source? This allows distributions to get the complete source from GitHub if they want.
Thanks

Hi,
I don't understand what you mean by this?


[DSA]: Graph Terminologies and Representations

Description
Discuss about various Graph Terminologies and How it is represented?
Domain
DSA
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


SH3 doesn't run on Windows 10

Hi. I've installed SH3 on my Windows 10 machine and unfortunately game starts randomly. It is not related with this fix however, happens also on vanilla game. Sometimes it runs in windowed mode.
Is there a possibility to try to fix it? If you need additional data about my OS or PC components, please ask.
Also CRC32 of my version is 7E6C991C.

Have you tried any other version of sh3.exe? I do not recall any specific compatibility issues with Windows 10, but I should re-test this.

Welp, that's the retail version from Europe I have. But now I believe I know the problem - it runs smoothly when game options (not from your proxy) are set to default. Unfortunately, game overrides it after every run, so I have to manually reset them every time before launch. But it's not a big issue, as with your fix the game just uses proxy settings.

You could try locking the config file to make the game unable to write it

That wasn't the case actually. I've downloaded exe you're using and now everything works. I recall Microsoft removed support for SecuROM and other tools like that, so I believe that was a case. Anyway, thanks and sorry for bothering!


reimplement bond / unbond

Signed-off-by: Gregory Hill<EMAIL_ADDRESS>Added

payload.BondTx
payload.UnbondTx

As BondTx reuses spec.TemplateAccount, we have the required fields of IdentifyTx. In this scenario, a known validator should be able to submit an empty bond with the NodeAddress set.

Considerations
Delegated Bonding
Currently, there is no persistent mapping between input account(s) and a validator. Once bonded, only the validators respective account can update it's power or fully unbond. This is probably fine for the initial implementation, but we may want to consider more advanced mechanisms in the future whereby the respective accounts are credited based on their investment in a particular validator.
Add / Remove Dynamics
Once an account with the right permission sends a BondTx, the target validator is immediately created and joins consensus after the following EndBlock. Similarly, an UnbondTx, signed by the submitting validator, is executed immediately. Hence I believe it is important to consider how we want to manage validators, from which this should be part of a larger discussion. For instance, upon completion of IdentifyTx (#960) we may want validators who leave the network to be automatically unbonded after a designated period of time.

After a discussion with @silasdavis we've opted to more tightly bind the input account to the target validator, meaning less to go wrong. This also paves the way for economic primitives embedded in smart contracts for more advanced features such as delegated bonding.

I'm happy with all of this except the edge case we have idenitfied on Bucket - will try and come up with resolution to this next week. I think we should probably fix it now.