renaming /data/logs/proxy-host-32_error.log.9.gz to /data/logs/proxy-host-32_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-32_error.log.9.gz does not exist
renaming /data/logs/proxy-host-32_error.log.8.gz to /data/logs/proxy-host-32_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-32_error.log.8.gz does not exist
renaming /data/logs/proxy-host-32_error.log.7.gz to /data/logs/proxy-host-32_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-32_error.log.7.gz does not exist
renaming /data/logs/proxy-host-32_error.log.6.gz to /data/logs/proxy-host-32_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-32_error.log.6.gz does not exist
renaming /data/logs/proxy-host-32_error.log.5.gz to /data/logs/proxy-host-32_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-32_error.log.5.gz does not exist
renaming /data/logs/proxy-host-32_error.log.4.gz to /data/logs/proxy-host-32_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-32_error.log.4.gz does not exist
renaming /data/logs/proxy-host-32_error.log.3.gz to /data/logs/proxy-host-32_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-32_error.log.3.gz does not exist
renaming /data/logs/proxy-host-32_error.log.2.gz to /data/logs/proxy-host-32_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-32_error.log.2.gz does not exist
renaming /data/logs/proxy-host-32_error.log.1.gz to /data/logs/proxy-host-32_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-32_error.log.1.gz does not exist
renaming /data/logs/proxy-host-32_error.log.0.gz to /data/logs/proxy-host-32_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-32_error.log.0.gz does not exist
log /data/logs/proxy-host-32_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-33_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-33_error.log.10.gz to /data/logs/proxy-host-33_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-33_error.log.10.gz does not exist
renaming /data/logs/proxy-host-33_error.log.9.gz to /data/logs/proxy-host-33_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-33_error.log.9.gz does not exist
renaming /data/logs/proxy-host-33_error.log.8.gz to /data/logs/proxy-host-33_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-33_error.log.8.gz does not exist
renaming /data/logs/proxy-host-33_error.log.7.gz to /data/logs/proxy-host-33_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-33_error.log.7.gz does not exist
renaming /data/logs/proxy-host-33_error.log.6.gz to /data/logs/proxy-host-33_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-33_error.log.6.gz does not exist
renaming /data/logs/proxy-host-33_error.log.5.gz to /data/logs/proxy-host-33_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-33_error.log.5.gz does not exist
renaming /data/logs/proxy-host-33_error.log.4.gz to /data/logs/proxy-host-33_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-33_error.log.4.gz does not exist
renaming /data/logs/proxy-host-33_error.log.3.gz to /data/logs/proxy-host-33_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-33_error.log.3.gz does not exist
renaming /data/logs/proxy-host-33_error.log.2.gz to /data/logs/proxy-host-33_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-33_error.log.2.gz does not exist
renaming /data/logs/proxy-host-33_error.log.1.gz to /data/logs/proxy-host-33_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-33_error.log.1.gz does not exist
renaming /data/logs/proxy-host-33_error.log.0.gz to /data/logs/proxy-host-33_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-33_error.log.0.gz does not exist
log /data/logs/proxy-host-33_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-34_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-34_error.log.10.gz to /data/logs/proxy-host-34_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-34_error.log.10.gz does not exist
renaming /data/logs/proxy-host-34_error.log.9.gz to /data/logs/proxy-host-34_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-34_error.log.9.gz does not exist
renaming /data/logs/proxy-host-34_error.log.8.gz to /data/logs/proxy-host-34_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-34_error.log.8.gz does not exist
renaming /data/logs/proxy-host-34_error.log.7.gz to /data/logs/proxy-host-34_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-34_error.log.7.gz does not exist
renaming /data/logs/proxy-host-34_error.log.6.gz to /data/logs/proxy-host-34_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-34_error.log.6.gz does not exist
renaming /data/logs/proxy-host-34_error.log.5.gz to /data/logs/proxy-host-34_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-34_error.log.5.gz does not exist
renaming /data/logs/proxy-host-34_error.log.4.gz to /data/logs/proxy-host-34_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-34_error.log.4.gz does not exist
renaming /data/logs/proxy-host-34_error.log.3.gz to /data/logs/proxy-host-34_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-34_error.log.3.gz does not exist
renaming /data/logs/proxy-host-34_error.log.2.gz to /data/logs/proxy-host-34_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-34_error.log.2.gz does not exist
renaming /data/logs/proxy-host-34_error.log.1.gz to /data/logs/proxy-host-34_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-34_error.log.1.gz does not exist
renaming /data/logs/proxy-host-34_error.log.0.gz to /data/logs/proxy-host-34_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-34_error.log.0.gz does not exist
log /data/logs/proxy-host-34_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-35_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-35_error.log.10.gz to /data/logs/proxy-host-35_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-35_error.log.10.gz does not exist
renaming /data/logs/proxy-host-35_error.log.9.gz to /data/logs/proxy-host-35_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-35_error.log.9.gz does not exist
renaming /data/logs/proxy-host-35_error.log.8.gz to /data/logs/proxy-host-35_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-35_error.log.8.gz does not exist
renaming /data/logs/proxy-host-35_error.log.7.gz to /data/logs/proxy-host-35_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-35_error.log.7.gz does not exist
renaming /data/logs/proxy-host-35_error.log.6.gz to /data/logs/proxy-host-35_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-35_error.log.6.gz does not exist
renaming /data/logs/proxy-host-35_error.log.5.gz to /data/logs/proxy-host-35_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-35_error.log.5.gz does not exist
renaming /data/logs/proxy-host-35_error.log.4.gz to /data/logs/proxy-host-35_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-35_error.log.4.gz does not exist
renaming /data/logs/proxy-host-35_error.log.3.gz to /data/logs/proxy-host-35_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-35_error.log.3.gz does not exist
renaming /data/logs/proxy-host-35_error.log.2.gz to /data/logs/proxy-host-35_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-35_error.log.2.gz does not exist
renaming /data/logs/proxy-host-35_error.log.1.gz to /data/logs/proxy-host-35_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-35_error.log.1.gz does not exist
renaming /data/logs/proxy-host-35_error.log.0.gz to /data/logs/proxy-host-35_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-35_error.log.0.gz does not exist
log /data/logs/proxy-host-35_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-3_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-3_error.log.10.gz to /data/logs/proxy-host-3_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-3_error.log.10.gz does not exist
renaming /data/logs/proxy-host-3_error.log.9.gz to /data/logs/proxy-host-3_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-3_error.log.9.gz does not exist
renaming /data/logs/proxy-host-3_error.log.8.gz to /data/logs/proxy-host-3_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-3_error.log.8.gz does not exist
renaming /data/logs/proxy-host-3_error.log.7.gz to /data/logs/proxy-host-3_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-3_error.log.7.gz does not exist
renaming /data/logs/proxy-host-3_error.log.6.gz to /data/logs/proxy-host-3_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-3_error.log.6.gz does not exist
renaming /data/logs/proxy-host-3_error.log.5.gz to /data/logs/proxy-host-3_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-3_error.log.5.gz does not exist
renaming /data/logs/proxy-host-3_error.log.4.gz to /data/logs/proxy-host-3_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-3_error.log.4.gz does not exist
renaming /data/logs/proxy-host-3_error.log.3.gz to /data/logs/proxy-host-3_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-3_error.log.3.gz does not exist
renaming /data/logs/proxy-host-3_error.log.2.gz to /data/logs/proxy-host-3_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-3_error.log.2.gz does not exist
renaming /data/logs/proxy-host-3_error.log.1.gz to /data/logs/proxy-host-3_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-3_error.log.1.gz does not exist
renaming /data/logs/proxy-host-3_error.log.0.gz to /data/logs/proxy-host-3_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-3_error.log.0.gz does not exist
log /data/logs/proxy-host-3_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-40_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-40_error.log.10.gz to /data/logs/proxy-host-40_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-40_error.log.10.gz does not exist
renaming /data/logs/proxy-host-40_error.log.9.gz to /data/logs/proxy-host-40_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-40_error.log.9.gz does not exist
renaming /data/logs/proxy-host-40_error.log.8.gz to /data/logs/proxy-host-40_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-40_error.log.8.gz does not exist
renaming /data/logs/proxy-host-40_error.log.7.gz to /data/logs/proxy-host-40_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-40_error.log.7.gz does not exist
renaming /data/logs/proxy-host-40_error.log.6.gz to /data/logs/proxy-host-40_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-40_error.log.6.gz does not exist
renaming /data/logs/proxy-host-40_error.log.5.gz to /data/logs/proxy-host-40_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-40_error.log.5.gz does not exist
renaming /data/logs/proxy-host-40_error.log.4.gz to /data/logs/proxy-host-40_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-40_error.log.4.gz does not exist
renaming /data/logs/proxy-host-40_error.log.3.gz to /data/logs/proxy-host-40_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-40_error.log.3.gz does not exist
renaming /data/logs/proxy-host-40_error.log.2.gz to /data/logs/proxy-host-40_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-40_error.log.2.gz does not exist
renaming /data/logs/proxy-host-40_error.log.1.gz to /data/logs/proxy-host-40_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-40_error.log.1.gz does not exist
renaming /data/logs/proxy-host-40_error.log.0.gz to /data/logs/proxy-host-40_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-40_error.log.0.gz does not exist
log /data/logs/proxy-host-40_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-41_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-41_error.log.10.gz to /data/logs/proxy-host-41_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-41_error.log.10.gz does not exist
renaming /data/logs/proxy-host-41_error.log.9.gz to /data/logs/proxy-host-41_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-41_error.log.9.gz does not exist
renaming /data/logs/proxy-host-41_error.log.8.gz to /data/logs/proxy-host-41_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-41_error.log.8.gz does not exist
renaming /data/logs/proxy-host-41_error.log.7.gz to /data/logs/proxy-host-41_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-41_error.log.7.gz does not exist
renaming /data/logs/proxy-host-41_error.log.6.gz to /data/logs/proxy-host-41_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-41_error.log.6.gz does not exist
renaming /data/logs/proxy-host-41_error.log.5.gz to /data/logs/proxy-host-41_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-41_error.log.5.gz does not exist
renaming /data/logs/proxy-host-41_error.log.4.gz to /data/logs/proxy-host-41_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-41_error.log.4.gz does not exist
renaming /data/logs/proxy-host-41_error.log.3.gz to /data/logs/proxy-host-41_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-41_error.log.3.gz does not exist
renaming /data/logs/proxy-host-41_error.log.2.gz to /data/logs/proxy-host-41_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-41_error.log.2.gz does not exist
renaming /data/logs/proxy-host-41_error.log.1.gz to /data/logs/proxy-host-41_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-41_error.log.1.gz does not exist
renaming /data/logs/proxy-host-41_error.log.0.gz to /data/logs/proxy-host-41_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-41_error.log.0.gz does not exist
log /data/logs/proxy-host-41_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-4_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-4_error.log.10.gz to /data/logs/proxy-host-4_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-4_error.log.10.gz does not exist
renaming /data/logs/proxy-host-4_error.log.9.gz to /data/logs/proxy-host-4_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-4_error.log.9.gz does not exist
renaming /data/logs/proxy-host-4_error.log.8.gz to /data/logs/proxy-host-4_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-4_error.log.8.gz does not exist
renaming /data/logs/proxy-host-4_error.log.7.gz to /data/logs/proxy-host-4_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-4_error.log.7.gz does not exist
renaming /data/logs/proxy-host-4_error.log.6.gz to /data/logs/proxy-host-4_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-4_error.log.6.gz does not exist
renaming /data/logs/proxy-host-4_error.log.5.gz to /data/logs/proxy-host-4_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-4_error.log.5.gz does not exist
renaming /data/logs/proxy-host-4_error.log.4.gz to /data/logs/proxy-host-4_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-4_error.log.4.gz does not exist
renaming /data/logs/proxy-host-4_error.log.3.gz to /data/logs/proxy-host-4_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-4_error.log.3.gz does not exist
renaming /data/logs/proxy-host-4_error.log.2.gz to /data/logs/proxy-host-4_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-4_error.log.2.gz does not exist
renaming /data/logs/proxy-host-4_error.log.1.gz to /data/logs/proxy-host-4_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-4_error.log.1.gz does not exist
renaming /data/logs/proxy-host-4_error.log.0.gz to /data/logs/proxy-host-4_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-4_error.log.0.gz does not exist
log /data/logs/proxy-host-4_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-5_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-5_error.log.10.gz to /data/logs/proxy-host-5_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-5_error.log.10.gz does not exist
renaming /data/logs/proxy-host-5_error.log.9.gz to /data/logs/proxy-host-5_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-5_error.log.9.gz does not exist
renaming /data/logs/proxy-host-5_error.log.8.gz to /data/logs/proxy-host-5_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-5_error.log.8.gz does not exist
renaming /data/logs/proxy-host-5_error.log.7.gz to /data/logs/proxy-host-5_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-5_error.log.7.gz does not exist
renaming /data/logs/proxy-host-5_error.log.6.gz to /data/logs/proxy-host-5_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-5_error.log.6.gz does not exist
renaming /data/logs/proxy-host-5_error.log.5.gz to /data/logs/proxy-host-5_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-5_error.log.5.gz does not exist
renaming /data/logs/proxy-host-5_error.log.4.gz to /data/logs/proxy-host-5_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-5_error.log.4.gz does not exist
renaming /data/logs/proxy-host-5_error.log.3.gz to /data/logs/proxy-host-5_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-5_error.log.3.gz does not exist
renaming /data/logs/proxy-host-5_error.log.2.gz to /data/logs/proxy-host-5_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-5_error.log.2.gz does not exist
renaming /data/logs/proxy-host-5_error.log.1.gz to /data/logs/proxy-host-5_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-5_error.log.1.gz does not exist
renaming /data/logs/proxy-host-5_error.log.0.gz to /data/logs/proxy-host-5_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-5_error.log.0.gz does not exist
log /data/logs/proxy-host-5_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-6_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-6_error.log.10.gz to /data/logs/proxy-host-6_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-6_error.log.10.gz does not exist
renaming /data/logs/proxy-host-6_error.log.9.gz to /data/logs/proxy-host-6_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-6_error.log.9.gz does not exist
renaming /data/logs/proxy-host-6_error.log.8.gz to /data/logs/proxy-host-6_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-6_error.log.8.gz does not exist
renaming /data/logs/proxy-host-6_error.log.7.gz to /data/logs/proxy-host-6_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-6_error.log.7.gz does not exist
renaming /data/logs/proxy-host-6_error.log.6.gz to /data/logs/proxy-host-6_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-6_error.log.6.gz does not exist
renaming /data/logs/proxy-host-6_error.log.5.gz to /data/logs/proxy-host-6_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-6_error.log.5.gz does not exist
renaming /data/logs/proxy-host-6_error.log.4.gz to /data/logs/proxy-host-6_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-6_error.log.4.gz does not exist
renaming /data/logs/proxy-host-6_error.log.3.gz to /data/logs/proxy-host-6_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-6_error.log.3.gz does not exist
renaming /data/logs/proxy-host-6_error.log.2.gz to /data/logs/proxy-host-6_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-6_error.log.2.gz does not exist
renaming /data/logs/proxy-host-6_error.log.1.gz to /data/logs/proxy-host-6_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-6_error.log.1.gz does not exist
renaming /data/logs/proxy-host-6_error.log.0.gz to /data/logs/proxy-host-6_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-6_error.log.0.gz does not exist
log /data/logs/proxy-host-6_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-7_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-7_error.log.10.gz to /data/logs/proxy-host-7_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-7_error.log.10.gz does not exist
renaming /data/logs/proxy-host-7_error.log.9.gz to /data/logs/proxy-host-7_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-7_error.log.9.gz does not exist
renaming /data/logs/proxy-host-7_error.log.8.gz to /data/logs/proxy-host-7_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-7_error.log.8.gz does not exist
renaming /data/logs/proxy-host-7_error.log.7.gz to /data/logs/proxy-host-7_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-7_error.log.7.gz does not exist
renaming /data/logs/proxy-host-7_error.log.6.gz to /data/logs/proxy-host-7_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-7_error.log.6.gz does not exist
renaming /data/logs/proxy-host-7_error.log.5.gz to /data/logs/proxy-host-7_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-7_error.log.5.gz does not exist
renaming /data/logs/proxy-host-7_error.log.4.gz to /data/logs/proxy-host-7_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-7_error.log.4.gz does not exist
renaming /data/logs/proxy-host-7_error.log.3.gz to /data/logs/proxy-host-7_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-7_error.log.3.gz does not exist
renaming /data/logs/proxy-host-7_error.log.2.gz to /data/logs/proxy-host-7_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-7_error.log.2.gz does not exist
renaming /data/logs/proxy-host-7_error.log.1.gz to /data/logs/proxy-host-7_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-7_error.log.1.gz does not exist
renaming /data/logs/proxy-host-7_error.log.0.gz to /data/logs/proxy-host-7_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-7_error.log.0.gz does not exist
log /data/logs/proxy-host-7_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-8_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-8_error.log.10.gz to /data/logs/proxy-host-8_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-8_error.log.10.gz does not exist
renaming /data/logs/proxy-host-8_error.log.9.gz to /data/logs/proxy-host-8_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-8_error.log.9.gz does not exist
renaming /data/logs/proxy-host-8_error.log.8.gz to /data/logs/proxy-host-8_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-8_error.log.8.gz does not exist
renaming /data/logs/proxy-host-8_error.log.7.gz to /data/logs/proxy-host-8_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-8_error.log.7.gz does not exist
renaming /data/logs/proxy-host-8_error.log.6.gz to /data/logs/proxy-host-8_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-8_error.log.6.gz does not exist
renaming /data/logs/proxy-host-8_error.log.5.gz to /data/logs/proxy-host-8_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-8_error.log.5.gz does not exist
renaming /data/logs/proxy-host-8_error.log.4.gz to /data/logs/proxy-host-8_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-8_error.log.4.gz does not exist
renaming /data/logs/proxy-host-8_error.log.3.gz to /data/logs/proxy-host-8_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-8_error.log.3.gz does not exist
renaming /data/logs/proxy-host-8_error.log.2.gz to /data/logs/proxy-host-8_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-8_error.log.2.gz does not exist
renaming /data/logs/proxy-host-8_error.log.1.gz to /data/logs/proxy-host-8_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-8_error.log.1.gz does not exist
renaming /data/logs/proxy-host-8_error.log.0.gz to /data/logs/proxy-host-8_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-8_error.log.0.gz does not exist
log /data/logs/proxy-host-8_error.log.11.gz doesn't exist -- won't try to dispose of it
rotating log /data/logs/proxy-host-9_error.log, log->rotateCount is 10
dateext suffix '-20230927'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /data/logs/proxy-host-9_error.log.10.gz to /data/logs/proxy-host-9_error.log.11.gz (rotatecount 10, logstart 1, i 10),
old log /data/logs/proxy-host-9_error.log.10.gz does not exist
renaming /data/logs/proxy-host-9_error.log.9.gz to /data/logs/proxy-host-9_error.log.10.gz (rotatecount 10, logstart 1, i 9),
old log /data/logs/proxy-host-9_error.log.9.gz does not exist
renaming /data/logs/proxy-host-9_error.log.8.gz to /data/logs/proxy-host-9_error.log.9.gz (rotatecount 10, logstart 1, i 8),
old log /data/logs/proxy-host-9_error.log.8.gz does not exist
renaming /data/logs/proxy-host-9_error.log.7.gz to /data/logs/proxy-host-9_error.log.8.gz (rotatecount 10, logstart 1, i 7),
old log /data/logs/proxy-host-9_error.log.7.gz does not exist
renaming /data/logs/proxy-host-9_error.log.6.gz to /data/logs/proxy-host-9_error.log.7.gz (rotatecount 10, logstart 1, i 6),
old log /data/logs/proxy-host-9_error.log.6.gz does not exist
renaming /data/logs/proxy-host-9_error.log.5.gz to /data/logs/proxy-host-9_error.log.6.gz (rotatecount 10, logstart 1, i 5),
old log /data/logs/proxy-host-9_error.log.5.gz does not exist
renaming /data/logs/proxy-host-9_error.log.4.gz to /data/logs/proxy-host-9_error.log.5.gz (rotatecount 10, logstart 1, i 4),
old log /data/logs/proxy-host-9_error.log.4.gz does not exist
renaming /data/logs/proxy-host-9_error.log.3.gz to /data/logs/proxy-host-9_error.log.4.gz (rotatecount 10, logstart 1, i 3),
old log /data/logs/proxy-host-9_error.log.3.gz does not exist
renaming /data/logs/proxy-host-9_error.log.2.gz to /data/logs/proxy-host-9_error.log.3.gz (rotatecount 10, logstart 1, i 2),
old log /data/logs/proxy-host-9_error.log.2.gz does not exist
renaming /data/logs/proxy-host-9_error.log.1.gz to /data/logs/proxy-host-9_error.log.2.gz (rotatecount 10, logstart 1, i 1),
old log /data/logs/proxy-host-9_error.log.1.gz does not exist
renaming /data/logs/proxy-host-9_error.log.0.gz to /data/logs/proxy-host-9_error.log.1.gz (rotatecount 10, logstart 1, i 0),
old log /data/logs/proxy-host-9_error.log.0.gz does not exist
log /data/logs/proxy-host-9_error.log.11.gz doesn't exist -- won't try to dispose of it
renaming /data/logs/fallback_error.log to /data/logs/fallback_error.log.1
creating new /data/logs/fallback_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-10_error.log to /data/logs/proxy-host-10_error.log.1
creating new /data/logs/proxy-host-10_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-11_error.log to /data/logs/proxy-host-11_error.log.1
creating new /data/logs/proxy-host-11_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-12_error.log to /data/logs/proxy-host-12_error.log.1
creating new /data/logs/proxy-host-12_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-13_error.log to /data/logs/proxy-host-13_error.log.1
creating new /data/logs/proxy-host-13_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-15_error.log to /data/logs/proxy-host-15_error.log.1
creating new /data/logs/proxy-host-15_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-16_error.log to /data/logs/proxy-host-16_error.log.1
creating new /data/logs/proxy-host-16_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-17_error.log to /data/logs/proxy-host-17_error.log.1
creating new /data/logs/proxy-host-17_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-18_error.log to /data/logs/proxy-host-18_error.log.1
creating new /data/logs/proxy-host-18_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-19_error.log to /data/logs/proxy-host-19_error.log.1
creating new /data/logs/proxy-host-19_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-1_error.log to /data/logs/proxy-host-1_error.log.1
creating new /data/logs/proxy-host-1_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-20_error.log to /data/logs/proxy-host-20_error.log.1
creating new /data/logs/proxy-host-20_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-21_error.log to /data/logs/proxy-host-21_error.log.1
creating new /data/logs/proxy-host-21_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-22_error.log to /data/logs/proxy-host-22_error.log.1
creating new /data/logs/proxy-host-22_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-23_error.log to /data/logs/proxy-host-23_error.log.1
creating new /data/logs/proxy-host-23_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-24_error.log to /data/logs/proxy-host-24_error.log.1
creating new /data/logs/proxy-host-24_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-25_error.log to /data/logs/proxy-host-25_error.log.1
creating new /data/logs/proxy-host-25_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-26_error.log to /data/logs/proxy-host-26_error.log.1
creating new /data/logs/proxy-host-26_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-28_error.log to /data/logs/proxy-host-28_error.log.1
creating new /data/logs/proxy-host-28_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-29_error.log to /data/logs/proxy-host-29_error.log.1
creating new /data/logs/proxy-host-29_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-2_error.log to /data/logs/proxy-host-2_error.log.1
creating new /data/logs/proxy-host-2_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-30_error.log to /data/logs/proxy-host-30_error.log.1
creating new /data/logs/proxy-host-30_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-31_error.log to /data/logs/proxy-host-31_error.log.1
creating new /data/logs/proxy-host-31_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-32_error.log to /data/logs/proxy-host-32_error.log.1
creating new /data/logs/proxy-host-32_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-33_error.log to /data/logs/proxy-host-33_error.log.1
creating new /data/logs/proxy-host-33_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-34_error.log to /data/logs/proxy-host-34_error.log.1
creating new /data/logs/proxy-host-34_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-35_error.log to /data/logs/proxy-host-35_error.log.1
creating new /data/logs/proxy-host-35_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-3_error.log to /data/logs/proxy-host-3_error.log.1
creating new /data/logs/proxy-host-3_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-40_error.log to /data/logs/proxy-host-40_error.log.1
creating new /data/logs/proxy-host-40_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-41_error.log to /data/logs/proxy-host-41_error.log.1
creating new /data/logs/proxy-host-41_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-4_error.log to /data/logs/proxy-host-4_error.log.1
creating new /data/logs/proxy-host-4_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-5_error.log to /data/logs/proxy-host-5_error.log.1
creating new /data/logs/proxy-host-5_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-6_error.log to /data/logs/proxy-host-6_error.log.1
creating new /data/logs/proxy-host-6_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-7_error.log to /data/logs/proxy-host-7_error.log.1
creating new /data/logs/proxy-host-7_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-8_error.log to /data/logs/proxy-host-8_error.log.1
creating new /data/logs/proxy-host-8_error.log mode = 0644 uid = 3011 gid = 3000
renaming /data/logs/proxy-host-9_error.log to /data/logs/proxy-host-9_error.log.1
creating new /data/logs/proxy-host-9_error.log mode = 0644 uid = 3011 gid = 3000
running postrotate script
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip
compressing log with: /bin/gzip

npm@1394d9770a85:/app$ ls -al /data/logs
total 16368
drwxr-xr-x 2 npm npm    8192 Sep 27 07:51 .
drwxrwx--- 7 npm npm     137 Sep 27 07:45 ..
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 default-host_access.log
-rw------- 1 npm npm   15340 Sep 27 06:47 default-host_access.log.1.gz
-rw------- 1 npm npm       0 Sep 24 18:11 default-host_error.log
-rw------- 1 npm npm     897 Sep 21 13:34 default-host_error.log.1
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 fallback_access.log
-rw-r--r-- 1 npm npm   90825 Sep 27 05:46 fallback_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 fallback_error.log
-rw------- 1 npm npm    2776 Sep 27 07:45 fallback_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-10_access.log
-rw-r--r-- 1 npm npm     257 Jun 12 09:36 proxy-host-10_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-10_error.log
-rw-r--r-- 1 npm npm     248 Jun 12 09:36 proxy-host-10_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-11_access.log
-rw-r--r-- 1 npm npm 2620581 Sep 27 07:43 proxy-host-11_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-11_error.log
-rw-r--r-- 1 npm npm 1132372 Sep 27 04:17 proxy-host-11_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-12_access.log
-rw-r--r-- 1 npm npm  317472 Sep 23 07:38 proxy-host-12_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-12_error.log
-rw-r--r-- 1 npm npm   10377 Sep 18 09:06 proxy-host-12_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-13_access.log
-rw-r--r-- 1 npm npm   62854 Sep 19 15:46 proxy-host-13_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-13_error.log
-rw-r--r-- 1 npm npm    2365 Sep 19 15:45 proxy-host-13_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Jun 14 10:24 proxy-host-14_access.log
-rw-r--r-- 1 npm npm       0 Jun 14 10:24 proxy-host-14_error.log
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-15_access.log
-rw-r--r-- 1 npm npm  406215 Sep 27 04:15 proxy-host-15_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-15_error.log
-rw-r--r-- 1 npm npm   38741 Sep 24 10:08 proxy-host-15_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-16_access.log
-rw-r--r-- 1 npm npm  143839 Sep 19 16:03 proxy-host-16_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-16_error.log
-rw-r--r-- 1 npm npm    4648 Sep 19 15:40 proxy-host-16_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-17_access.log
-rw-r--r-- 1 npm npm   84609 Sep 23 09:42 proxy-host-17_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-17_error.log
-rw-r--r-- 1 npm npm    2018 Sep 23 09:41 proxy-host-17_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-18_access.log
-rw-r--r-- 1 npm npm 3985501 Sep 27 04:10 proxy-host-18_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-18_error.log
-rw-r--r-- 1 npm npm    1652 Sep 24 07:55 proxy-host-18_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-19_access.log
-rw-r--r-- 1 npm npm     778 Jun 16 08:49 proxy-host-19_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-19_error.log
-rw-r--r-- 1 npm npm     416 Jun 16 08:42 proxy-host-19_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-1_access.log
-rw-r--r-- 1 npm npm 1281814 Sep 27 07:51 proxy-host-1_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-1_error.log
-rw-r--r-- 1 npm npm   18760 Sep 26 22:56 proxy-host-1_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-20_access.log
-rw-r--r-- 1 npm npm   24942 Jun 16 11:50 proxy-host-20_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-20_error.log
-rw-r--r-- 1 npm npm    3143 Jun 16 11:35 proxy-host-20_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-21_access.log
-rw-r--r-- 1 npm npm  890917 Sep 27 07:40 proxy-host-21_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-21_error.log
-rw-r--r-- 1 npm npm  190656 Sep 27 07:40 proxy-host-21_error.log.1.gz
-rw------- 1 npm npm       0 Sep 14 19:42 proxy-host-22_access.log
-rw-r--r-- 1 npm npm     209 Sep 13 03:09 proxy-host-22_access.log.1
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-22_error.log
-rw-r--r-- 1 npm npm    2467 Sep 13 03:10 proxy-host-22_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-23_access.log
-rw-r--r-- 1 npm npm     565 Jun 21 14:44 proxy-host-23_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-23_error.log
-rw-r--r-- 1 npm npm     354 Jun 21 14:23 proxy-host-23_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-24_access.log
-rw------- 1 npm npm    9379 Sep 25 11:27 proxy-host-24_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-24_error.log
-rw-r--r-- 1 npm npm    4200 Sep 25 11:27 proxy-host-24_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-25_access.log
-rw-r--r-- 1 npm npm    1203 Jun 27 15:11 proxy-host-25_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-25_error.log
-rw-r--r-- 1 npm npm     373 Jun 27 15:04 proxy-host-25_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-26_access.log
-rw------- 1 npm npm 1466618 Sep 20 04:03 proxy-host-26_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-26_error.log
-rw------- 1 npm npm  249275 Sep 20 03:59 proxy-host-26_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-27_access.log
-rw-r--r-- 1 npm npm  248344 Aug 16 15:52 proxy-host-27_access.log.1.gz
-rw------- 1 npm npm       0 Aug 18 02:53 proxy-host-27_error.log
-rw------- 1 npm npm    1444 Aug 16 15:50 proxy-host-27_error.log.1
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-28_access.log
-rw-r--r-- 1 npm npm    4728 Sep 12 15:05 proxy-host-28_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-28_error.log
-rw-r--r-- 1 npm npm     751 Sep 12 15:05 proxy-host-28_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-29_access.log
-rw-r--r-- 1 npm npm    8646 Sep 25 13:41 proxy-host-29_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-29_error.log
-rw-r--r-- 1 npm npm     851 Sep 25 13:41 proxy-host-29_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-2_access.log
-rw-r--r-- 1 npm npm  223224 Sep 27 07:48 proxy-host-2_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-2_error.log
-rw-r--r-- 1 npm npm   21436 Sep 27 07:48 proxy-host-2_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-30_access.log
-rw-r--r-- 1 npm npm 2349776 Sep 27 07:51 proxy-host-30_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-30_error.log
-rw-r--r-- 1 npm npm    7073 Aug 10 10:46 proxy-host-30_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-31_access.log
-rw-r--r-- 1 npm npm  177024 Sep 27 07:42 proxy-host-31_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-31_error.log
-rw-r--r-- 1 npm npm   36928 Sep 26 10:16 proxy-host-31_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-32_access.log
-rw------- 1 npm npm    5093 Sep 25 05:35 proxy-host-32_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-32_error.log
-rw------- 1 npm npm    1046 Sep 25 05:35 proxy-host-32_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-33_access.log
-rw------- 1 npm npm     506 Sep  5 05:50 proxy-host-33_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-33_error.log
-rw-r--r-- 1 npm npm     603 Sep  5 05:50 proxy-host-33_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-34_access.log
-rw-r--r-- 1 npm npm   18507 Sep 24 07:48 proxy-host-34_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-34_error.log
-rw-r--r-- 1 npm npm     490 Sep  5 15:31 proxy-host-34_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-35_access.log
-rw-r--r-- 1 npm npm   21704 Sep 26 10:18 proxy-host-35_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-35_error.log
-rw-r--r-- 1 npm npm    1002 Sep  5 05:41 proxy-host-35_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep  9 10:33 proxy-host-36_access.log
-rw-r--r-- 1 npm npm       0 Sep  9 10:33 proxy-host-36_error.log
-rw-r--r-- 1 npm npm       0 Sep  9 10:45 proxy-host-37_access.log
-rw-r--r-- 1 npm npm       0 Sep  9 10:45 proxy-host-37_error.log
-rw-r--r-- 1 npm npm       0 Sep  9 10:48 proxy-host-38_access.log
-rw-r--r-- 1 npm npm       0 Sep  9 10:48 proxy-host-38_error.log
-rw------- 1 npm npm       0 Sep 20 11:15 proxy-host-39_access.log
-rw-r--r-- 1 npm npm    9234 Sep 11 15:14 proxy-host-39_access.log.1
-rw------- 1 npm npm       0 Sep 20 11:15 proxy-host-39_error.log
-rw-r--r-- 1 npm npm     426 Sep 11 15:06 proxy-host-39_error.log.1
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-3_access.log
-rw-r--r-- 1 npm npm  219654 Sep 26 11:35 proxy-host-3_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-3_error.log
-rw-r--r-- 1 npm npm    2912 Sep 26 11:35 proxy-host-3_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-40_access.log
-rw-r--r-- 1 npm npm   16277 Sep 25 06:17 proxy-host-40_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-40_error.log
-rw-r--r-- 1 npm npm    6062 Sep 25 00:53 proxy-host-40_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-41_access.log
-rw-r--r-- 1 npm npm    6930 Sep 23 09:04 proxy-host-41_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-41_error.log
-rw-r--r-- 1 npm npm     686 Sep 23 08:57 proxy-host-41_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-4_access.log
-rw-r--r-- 1 npm npm   31990 Sep 25 14:54 proxy-host-4_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-4_error.log
-rw-r--r-- 1 npm npm     635 Sep 25 14:54 proxy-host-4_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-5_access.log
-rw-r--r-- 1 npm npm    2453 Sep 25 14:54 proxy-host-5_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-5_error.log
-rw-r--r-- 1 npm npm    1164 Sep 18 14:09 proxy-host-5_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-6_access.log
-rw-r--r-- 1 npm npm   30489 Sep 27 07:47 proxy-host-6_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-6_error.log
-rw-r--r-- 1 npm npm     332 Sep  4 04:16 proxy-host-6_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-7_access.log
-rw-r--r-- 1 npm npm    2200 Sep  4 19:45 proxy-host-7_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-7_error.log
-rw-r--r-- 1 npm npm     369 Jun 12 06:12 proxy-host-7_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-8_access.log
-rw-r--r-- 1 npm npm   12147 Sep 17 06:19 proxy-host-8_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-8_error.log
-rw-r--r-- 1 npm npm     260 Jun 12 09:26 proxy-host-8_error.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-9_access.log
-rw-r--r-- 1 npm npm    3037 Jun 12 09:34 proxy-host-9_access.log.1.gz
-rw-r--r-- 1 npm npm       0 Sep 27 07:51 proxy-host-9_error.log
-rw-r--r-- 1 npm npm     502 Jun 12 09:34 proxy-host-9_error.log.1.gz

If testing, remember to exec into the container with --user npm to simulate how the command will actually be run.

It will also work when running as root, as when a PUID and PGID is not set, the npm:npm user/group will have the uid/gid of 0.

using latest version ,i have permissions issue in ubuntu with root user:

@masterwishx Please create a discussion about this issue. Include your compose file and a screenshot of the output of the command docker exec <npm-container-id> ls -al /data/logs, and tag me in it.

@FibreTTP
https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/3400


How can I make a Menu button which opening a web app?

I tried to do something like that, but it doesn`t work:
class AppCommand extends CommandHandler
{
    protected static $aliases = ['/app'];
    protected static $description = 'Run application';

    public function handle()
    {
        $webAppInfo = WebAppInfo::create([
            'url' => 'https://example.com/app',
        ]);

        $menuButtonWebApp = MenuButtonWebApp::create([
            'type' => 'web_app',
            'text' => 'App',
            'web_app' => $webAppInfo,
        ]);

        return $menuButtonWebApp;
    }
}

or
return $this->setChatMenuButton([
    'chat_id' => env('TELEGRAM_CHAT_ID'),
    'menu_button' => $menuButtonWebApp
]);

Laravel 9

There is Discussions tab for questions. Issues are for reporting bugs and proposing new features.
I never personally worked with web apps yet, but according to the Telegram Bot API, your code should be something like this:
$this->setChatMenuButton([
    'menu_button' => [
        'type' => 'web_app',
        'text' => 'My App',
        'web_app' => [
            'url' => '<your web app url>'
        ]
    ]
]);

There is a Discussions tab for questions. Issues are for reporting bugs and proposing new features.

My bad.

From my investigations, this works well.

Yes, works perfectly! Thank you very much!


Extend npm run package:* context deadline to 60m

Summary
The mac_installer build is taking a lot longer than expected, likely due to some issues with Apple during notarization.
I've extended the time to 60 minutes to hopefully cover this.
NONE

The file .circleci/config.yml is in the blocklist for external contributors. Hence, these changes are not tested by the CI pipeline active until the build is re-triggered by a core committer or the PR is merged. Please be careful when reviewing it.
/cc @mattermost/core-security @mattermost/core-build-engineers

Cherry pick is scheduled.


Fix lint

Fixes #5

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Could you please use conda-smithy 0.9.2 to re-render?

Could you please use conda-smithy 0.9.2 to re-render?

I am. What change are you missing?

Oh I see. I was with a dev version without the brew cleaning. But that is not important here. (In fact I am not sure we have a case where that will be important.).

Oh, maybe there was a change after the diff I looked at. It now looks fine.

Some of the more memory intensive builds worry me a bit as they could hang. Like FFTW I have had to restart sometimes.

Thanks @ocefpaf.


Suggestion: specifying non mandatory variants in packages.yaml

https://github.com/LLNL/serac/blob/553f454f821d74ab032655d7f03ecb6eb1f10ee9/scripts/uberenv/packages/serac/package.py#L91
@white238 I think it would be better to specify variants that are not mandatory in the packages.yaml (EDIT: not host-config files). This way it does not force the installation of a new axom if one is already present for example, and developer can still install the blessed configuration with uberenv.

Did you mean the packages.yaml? Variants don't go in host-configs. Variants can go in the packages file but then they have to be duplicated in everyone we have.
I think it would be better to step back and figure out what are you trying to accomplish with this?  The serac package is very specialized to us and we want to build our libraries as a whole package.  If we want, we can push a more generic version up to Spack but optimizations are going to be common in this file going forward.  If we remove, for example, raja and umpire from that list, we would be solving your problem but requiring all of our developers to build at least two packages we don't currently use.

Sorry, yes, packages.yaml of course... And yes, there would be a bit of a duplication.
Taking the example of raja and umpire, don’t you think it is "enough" to put those variant in the packages.yaml?
I understand you are looking at this from a specific application. But in my experience in Spack, it’s always best to allow the package to be built in the most configuration possible. It does not prevent from having optimized or specific variants even defined in the package.

This is not about what is best for Spack, it is what is best for this project.  This specific serac package.py is ours and will be tuned to our needs.
In fact, I ran into a just problem today with the versions being in the packages.yaml. So this is already a problem.

So be it. I didn’t mean best for Spack. I guess we will see with time.
Having a "public" serac package with a generic configuration sounds appealing, but I think it will bring a lot of issues because of the coexistence of a two packages.

@jamiebramwell @white238 should we close this one?

I'll leave that to @white238 ! I think we do want to have a hard lock on our dependencies in general, so I vote for closing it.

We can readdress this when the new concretizer is more stable/widely used.


Background Color Animation

Hey there,
Im having an issue with the IFTTTColorAnimation

    var gradientBarColorAnimation: IFTTTColorAnimation!

    public override func viewDidLoad() {
        super.viewDidLoad()

        var myView = UIView(frame: CGRectMake(0, 0, 100, 100));
        myView.backgroundColor = UIColor.blackColor()
        self.view.addSubview(myView)

        self.gradientBarColorAnimation = IFTTTColorAnimation(view: myView)
        self.gradientBarColorAnimation.addKeyframeForTime(0, color: myView.backgroundColor)
        self.gradientBarColorAnimation.addKeyframeForTime(64, color: UIColor.redColor())
    }

    public func scrollViewDidScroll(scrollView: UIScrollView) {

        self.gradientBarColorAnimation.animate(scrollView.contentOffset.y)
    }

The problem is: when it pass the 64 time, it just changes the color to red, isn't an animated transition.
I tried to change the colors alpha chanel as the example uses, it doesn't work either.
Aditional info:
iOS 8.4,
Xcode 6.4
Swift 1.2

I have the same issue with JazzHands 2.0, although the demo app works fine.
scrollViewDidScroll uses the default implementation from IFTTTAnimatedPagingScrollViewController.

The issue is in IFTTTFilmStrip.m here (see the commented out line):
- (id<IFTTTInterpolatable>)valueAtTime:(CGFloat)time
{
    NSAssert(!self.isEmpty, @"At least one KeyFrame must be set before animation begins.");
    id value;
    NSUInteger indexAfter = [self indexOfKeyframeAfterTime:time];
    if (indexAfter == 0) {
        value = ((IFTTTKeyframe *)self.keyframes[0]).value;
    } else if (indexAfter < self.keyframes.count) {
        IFTTTKeyframe *keyframeBefore = (IFTTTKeyframe *)self.keyframes[indexAfter - 1];
        IFTTTKeyframe *keyframeAfter = (IFTTTKeyframe *)self.keyframes[indexAfter];
        CGFloat progress = [self progressFromTime:keyframeBefore.time toTime:keyframeAfter.time atTime:time withEasingFunction:keyframeBefore.easingFunction];
        if ([keyframeBefore.value respondsToSelector:@selector(interpolateTo:withProgress:)]
//            && [keyframeAfter.value isKindOfClass:[keyframeBefore.value class]]
        ) {
            value = [keyframeBefore.value interpolateTo:keyframeAfter.value withProgress:progress];
        } else {
            value = keyframeBefore.value;
        }
    } else {
        value = ((IFTTTKeyframe *)self.keyframes.lastObject).value;
    }
    return value;
}

This is because [UIColor blackColor] has a class of UIDeviceWhiteColor, where as any other non white / black / grey colour will have a class of UIDeviceRGBColor. This makes the if statement fail, and hence the interpolation not to work.
See here for more info: https://marksands.github.io/2013/07/11/fixing-uicolor.html

@RodolfoAntonici Thanks for pointing out the issue, and @gazsp thanks for the super helpful detective work on the cause!


Remove Superfluous [] in Decoded Logs

The decoded logs currently look like the following:
[0][][04:09:46.599785][time][0x5623db075208] Updating Connection 0x7fd550000b20.
[0][][04:09:46.599786][time][0x5623db075208] Next Expiration = {1412964260, 0x7fd550000b20}.
[0][][04:09:46.599787][conn][0x7fd550000b20] Flush complete flags=0x0
[0][][04:09:46.599788][conn][0x7fd550000b20] Scheduling: 0

Notice the extra [] after the [0].  This should be removed.

This bug is located https://github.com/microsoft/CLOG/blob/master/src/clogutils/CLogConsoleTrace.cs#L106 and is actually 2 bugs
First is without a PID or TID, the brackets should not be printed
2nd is why are those not there.

Turns out this is not actually a bug in anything CLOG is doing. PID and TID must be explicitly enabled, and this does not look like it can be done from the lttng headers clog itself generates. To add this, the following line must be added before lttng starts.
lttng add-context --userspace --type=vpid --type=vtid

I'm going to close this, as its not a clog issue. I have opened #68 to make CI builds have this extra context, and am working on updating msquic to fix this too.


[development]

Pull Request Test Coverage Report for Build 4fb8fe3c-69c0-4d2e-94f2-1d19bba3d750

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 59.985%

Totals

Change from base Build 0aec05d2-bfd3-4082-8860-4958498dc200:
0.0%

Covered Lines:
443

Relevant Lines:
535

💛  - Coveralls


added Ngroups doc

@shivg7795 - This PR can't be merged here in the public repo. Either you or @tomvcassidy will need to move the content to the private repo (azure-compute-docs-pr).
Here in the public repo, the PR Review team can't process this PR further until you sign the CLA.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@shivg7795
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.
We'll close this PR. Thank you.


tasks.js has syntax error

There is a syntax error in tasks.js that prevents building with gulp ...
return del(directories).then(() => done(null, blobs));
node_modules/highlight.js/tools/tasks.js:15
return del(directories).then(() => done(null, blobs));
^
SyntaxError: Unexpected token )
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (rtail/node_modules/highlight.js/tools/build.js:65:17)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
/home/tpci/rtail/gulpfile.js:86
if (0 !== code) throw new Error('node tools/build.js exited with ' + cod
^
Error: node tools/build.js exited with 8
at ChildProcess. (rtail/gulpfile.js:86:29)
at ChildProcess.emit (events.js:98:17)
at maybeClose (child_process.js:766:16)
at Process.ChildProcess._handle.onexit (child_process.js:833:5)

If I rewrite the line as:
return del(directories).then(done(null, blobs));
it compiles without error

We recently switched our toolchain to node 4.x, which version are you using?

ubuntu-trusty:~$ node --version
v0.10.37

This is probably the reason of it misbehaving. You might want to upgrade node.js to a contemporary release from a supported repository: https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

Closing this since it isn't really a syntax error, at least for the new versions of node, but rather the build script using an ES6 feature called arrow functions.


add source publication

For using in a maven repository. We only need to add this line to publish the artefacts. It the line is not present, only the pom is published, leading to missing classes (i.e. in btleplug/droidplug)

My mistake, I seem to struggle with creating the PR


"Open in Terminal" is not multiselect-aware

Testing https://github.com/Microsoft/vscode/issues/41473 on Linux

Select multiple things in the file explorer
Right click, "Open in Terminal"
Only opens one terminal, corresponding to whichever item was actually right clicked

I think it makes sense for multiselect because it's similar to "open containing folder"

I would like to have a go at this if its fine.

I have a question with respect to implementation. Say two files(or folder) selected are from same folder, should we still open two instances in the terminal ?  Or should we check to ensure that same folder isnt duplicated ?

I can verify that it's not working on MacOS as well. My 2 cents-

I think it makes sense to have multiple terminals for multiple item selection.
@sriram-dev It makes sense to have multiple terminals for multi-folder selection, but for files within the same <root> folder, it makes sense to have only one terminal with the <root>folder.

Details -

VSCode Version: 1.20.0-insider (1.20.0-insider) (3f8cf)
OS Version:  High Sierra 10.13.2

@sriram-dev by all means :smiley:
I think only opening a terminal for each once would probably be best personally.

Fixed via https://github.com/Microsoft/vscode/pull/43552

Does not work for me:

@isidorn I see. Seems to work nicely. I still think if the selection is all from the same root you could just reveal that parent in the terminal.

Oh I misunderstood your original comment. Yes if they all have the same parent it should open. Pushed a fix now. Thanks


Want to contribute in the Image Smoothing Repo

Hi Saptarshee here,
I am a participant of GSSOC,21 and want to work and contribute in the Image Smoothing repo.
Could you please assign me the job so that I start working on it ?

Awesome. Assigning Gaussian Filtering to you @Saptar001.


[166] missing deposit amount parameter in Near.call

Descrivi il problema:
Hello i have used  near.call bos api below, but how to add deposit amount paraneter in it? I can't find an example to better explain.
Near.call(messagelist, "add_message", {
text: state.greeting,
});
Info
Reported by: Unknown<EMAIL_ADDRESS>- Open in Gleap
Location: FR
Type: 🚨 BUG
🔗 Open share link
🌍 Open ticket in Gleap
Metadata
browserName: Chrome(111.0.5563.116)
userAgent: Mozilla/5.0 (Linux; Android 13; SAMSUNG SM-A326B) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/22.0 Chrome/111.0.5563.116 Mobile Safari/537.36
browser: Chrome
systemName: Android
sessionDuration: 120
devicePixelRatio: 2
screenWidth: 360
screenHeight: 800
innerWidth: 380
innerHeight: 456
currentUrl: https://docs.near.org/bos/api/near
language: it-IT
mobile: true
sdkVersion: 10.1.0
sdkType: javascript
environment: prod

The documentation now clearly states there is a deposit attribute: https://docs.near.org/bos/api/near#nearcall


feat(alignment): Add responsive text alignment

Looks good to me! Bummer about the lack of metaprogramming it but c'est la wunder


Use icon from memory?

This would be very useful for small self contained apps.

If you are still working on your project. you can make icon path name to file.ico to trayexecutable.exe and it will automatic extract your image from executable


Cow: Watch ladensitaehairwig.com

Cow requests the watch of the watch_keyword ladensitaehairwig\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

ladensitaehairwig\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Increment versions for security releases

Increment package versions for security releases

API change check
API changes are not detected in this pull request.


Separate CSS

Hi, is it possible to produce a separate CSS file for npm distribution?

I'm working on SSR support right now and having a separate css file is a side-effect of supporting SSR. So after I'm done, the css file will be available on npm.

@ecmel beta.14 released and should fix this problem. Sorry you had to wait. Please read: https://github.com/monterail/vue-multiselect/blob/2.0/README.md
Breaking change regarding the styles.


[DUOS-826][risk=no] Update Home page with Researcher link

Addresses several tickets in one: https://broadinstitute.atlassian.net/browse/DUOS-826, https://broadinstitute.atlassian.net/browse/DUOS-829, https://broadinstitute.atlassian.net/browse/DUOS-828.
DUOS-826:

Make the grey section constant when logged in or not
Replace text under 'Are you a Researcher?' column
Replace link under 'Are you a Researcher?' column from 'REGISTER' to 'LEARN MORE' and link to new Researcher Info page

DUOS-829

Create new Researcher Info page

DUOS-828

Move Register link underneath Sign In component on Home page

Have you read Terra's Contributing Guide lately? If not, do that first.
I, the developer opening this PR, do solemnly pinky swear that:

[x] PR is labeled with a Jira ticket number and includes a link to the ticket
[x] PR is labeled with a security risk modifier [no, low, medium, high]
[x] PR describes scope of changes

In all cases:

[ ] Get a minimum of one thumbs worth of review, preferably 2 if enough team members are available
[ ] Get PO sign-off for all non-trivial UI or workflow changes
[ ] Verify all tests go green
[ ] Squash and merge; you can delete your branch after this
[ ] Test this change deployed correctly and works on dev environment after deployment

Looks great, thanks @lindojong !


Noob: Starting Up PGvector and Post

Hi,
Might be a trivial question, but I am having issues setting up PGVector and Postgres. I would like to work locally, I have everything installed, but I am not sure how to start PGVector and Postgres to store the documents.

Hey @chozillla! Setting up PGVector and Postgres can definitely be intimidating the first time around. I'd recommend using the docker in that case—this will create a containerized environment including a PGVector database with no manual set up needed. The docs should be helpful with getting started.
If you're unable to use Docker for whatever reason, you could look at setting up a Postgres db with a cloud provider like Supabase, adding the PG vector extension, and connecting that way.
I'll wait to close this to see if you're able to get up and running. Let me know if you run into anything else!

Got it running nvm doing some CLI commands. No need for docker. Thanks!


Akamai CDN irregular responses !

I found some subdomains that look like this:
Server: edgesuite and akadns (Akamai)
I found some different 404 responses for those subdomains
look like :
1>File not found."
2>Service Unavailable - DNS failure
The server is temporarily unable to service your request. Please try again later.
3>An error occurred while processing your request.
This is what I getting from that Akamai CDN service
which is different from the last one
Invalid URL
The requested URL "[no URL]", is invalid.
Does anyone know if this vulnerable to a takeover?

I believe not, but it has been some months since I initially tested this. Will flag this as help wanted in case somebody would like to reproduce and add further detail to this issue.

I don't have Akamai CDN account that's why I wasn't able to check them all if you have I will provide you the subdomains whick contains irregular responses.


docs: ldap support

docs: ldap supports

connect #293

connect #293

Refer to this documentation to link a pull request to an issue.

LGTM

https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue

Thanks I will


Stray sentence re release branch

Describe the bug
Under "Branching strategy" after the Design Considerations bullets there seems to be some stray text re "release branch with a subsequently deployment". This should probably be deleted or edited to make sense.
To Reproduce
Go to https://github.com/Azure/AlwaysOn/blob/de4e489a8af6013210b71e73e17af0e6a4383085/docs/design-methodology/Deployment-Testing.md?plain=1#L238

Thank you for your feedback. We'll update and clarify that shortly.


fix: remove events handler when ResponsiveAccordionTabs is destroyed #10901

Closes https://github.com/zurb/foundation-sites/issues/10901

This looks good to me.


Inconsistent Type definition for Components. E.g Typography

Describe the bug
The TypographyProps definition is causing type extension issues due to its implementation as a type union of HTML node types, specifically HTMLElement and HTMLAnchorElement. This use of a type union introduces inconsistency at the type level, which is particularly evident when attempting to extend TypographyProps with an interface.
Attempted interface extension results in the TypeScript error:
An interface can only extend an object type or intersection of object types with statically known members.ts(2312)

I understand the goal, which is to achieve type safety for attributes such as href or rel related to HTMLAnchorElement. But there is a mix between type definitions and the usage of styled-components as property. This application creates a dichotomy at the type level that's not visually apparent, and it intermingles capabilities of styled-components without aligning them properly with the type definitions.

EDS should allow extensions no matter if a user decides to use type or interface, it should not be forced to use one or another.
As EDS is using styled-components, which allows to change dynamically the component HTML node element, it should also offers typesafety around that node. I should not have all the attributes no matter the html node i decide to use as that will bring a lot of confusion.

Steps to reproduce the bug
import type { TypographyProps } from '@equinor/eds-core-react';

interface Typography2Props extends TypographyProps {
/** New props ... */
}

Expected behavior
I should at least be able to extend the TypographyProps using interface.
Ideal solution, if i use as="a" then i will have autocomplete for the properties that are for an anchor element.
Possible solutions
An easy fix to allow extensions of the TypographyProps unsing interfaces is to instead of using type change it to interface which will force you to have double extension instead of a type union:
export interface TypographyProps extends extends HTMLAttributes<HTMLElement>, AnchorHTMLAttributes<HTMLAnchorElement>  {
  /** Typography variants, specifies which variant to use. */
  variant?: TypographyVariants
  /** Typography groups, specifies which group to use. */
  group?: TypographyGroups
  /** Bold text. */
  bold?: boolean
  /** Italic text. */
  italic?: boolean
  /** Link. */
  link?: boolean
  /** Typography colors. */
  // eslint-disable-next-line @typescript-eslint/no-redundant-type-constituents
  color?: ColorVariants | string
  /** Token. */
  token?: Partial<TypographyType>
  /** Number of lines. */
  lines?: number
}

Unsure if that change will produce other type errors.

A "more" correct fix as it will add inference arround the render engine (styled-components) is to allow autocomplete based on the as propert. A way to achive it is to create a wrapper around the forwardRef which will infer the types based on the as property.
A possible implementation, is just an example I think is quite correct but im using some deprecated types, but to test the idea should be good (Also keep in mind react 19 will remove the need for forwardRef, which then this code will need some refactor):
import {
  forwardRef as forwardReactRef,
  type ComponentProps,
  type ComponentPropsWithoutRef,
  type ElementType,
  type ExoticComponent,
  type ForwardRefRenderFunction,
  type PropsWithoutRef,
  type ValidationMap,
  type WeakValidationMap,
} from "react";

type As = ElementType;

type PropsOf<T extends As> = ComponentPropsWithoutRef<T>;

type RightJoinProps<
  SourceProps extends object = {},
  OverrideProps extends object = {},
> = OmitCommonProps<SourceProps, keyof OverrideProps> & OverrideProps;

type OmitCommonProps<
  Target,
  OmitAdditionalProps extends keyof any = never,
> = Omit<
  Target,
  "transition" | "as" | "color" | "translate" | OmitAdditionalProps
> & {
  htmlTranslate?: "yes" | "no" | undefined;
};

// ! If you plan to use this implementation keep in mind that this type must be called "ForwardRefExoticComponent" or storybook will not autogenerate the argTypes
type ForwardRefExoticComponent<
  ET extends As,
  P extends object = {},
> = ExoticComponent<P> & {
  <AsComponent extends As = ET>(
    props: MergeWithAsProp<
      ComponentProps<ET>,
      ComponentProps<AsComponent>,
      P,
      AsComponent
    >
  ): JSX.Element;
  displayName?: string;
  defaultProps?: Partial<P>;
  propTypes?: WeakValidationMap<P>;
  contextTypes?: ValidationMap<any>;
  id?: string;
};

type MergeWithAsProp<
  CP extends object,
  AsProps extends object,
  AdditionalProps extends object = {},
  AsComponent extends As = As,
> = (
  | RightJoinProps<CP, AdditionalProps>
  | RightJoinProps<AsProps, AdditionalProps>
) & {
  as?: AsComponent;
};

/**
 * Creates a forward ref for a React functional component that adds the "as" property.
 *
 * @typeParam P - The Component props type.
 * @typeParam ET - The React.ElementType.
 *
 * @param component - The functional component.
 * @returns Forwarded React component.
 */
export function forwardRefWithAs<P extends object, ET extends As>(
  component: ForwardRefRenderFunction<
    any,
    RightJoinProps<PropsOf<ET>, P> & {
      as?: As;
    }
  >
) {
  return forwardReactRef(component) as ForwardRefExoticComponent<
    ET,
    PropsWithoutRef<P>
  >;
}

Usage:
const BaseTypography = styled.p``

interface TypographyProps extends HTMLAttributes<HTMLParagraphElement> {
  /* ... */
}

 const Typography= forwardRefWithAs<TypographyProps, "p">(function Typography({children, ...others}, ref) {
  return <BaseTypography {...others} ref={ref}>{children}</BaseTypography>
 })

 const Test = () => {
  return <Typography as="a" href="...">Test</Typography>
 }
....

Now You should have autocomplete for href only if you use as="a"

Just an update for the easy solution, as what i wrote is incomplete.
Is not possible to extend from both HTMLAttributes<HTMLElement> and AnchorHTMLAttributes<HTMLAnchorElement> at the same time as there is properties with the same name but not identically on those types.
A solution for that could be:
export interface TypographyProps
  extends HTMLAttributes<HTMLElement>,
    Omit<
      AnchorHTMLAttributes<HTMLAnchorElement>,
      keyof HTMLAttributes<HTMLElement>
    > {
  /** Typography variants, specifies which variant to use. */
  variant?: TypographyVariants;
  /** Typography groups, specifies which group to use. */
  group?: TypographyGroups;
  /** Bold text. */
  bold?: boolean;
  /** Italic text. */
  italic?: boolean;
  /** Link. */
  link?: boolean;
  /** Typography colors. */
  color?: ColorVariants | string;
  /** Token. */
  token?: Partial<TypographyType>;
  /** Number of lines. */
  lines?: number;
}


Merge user stdout & stderr

What would you like to be added:
A merged log
Why is this needed:
v0.13 seperates user stdout and stderr, it brings two bad experience:

Python logging module write log to stderr, user might be confused why stdout is empty.
Without a merged log, it's hard to get a clear command timeline

Without this feature, how does the current module work:
Users add timestamp in their output module
Components that may involve changes:
runtime

Close this issue, further progress please refer to #3246


Added a fix for a user problem

(Fixes #38)
Thanks, please also bump the version number in pytos/__init__.py to 1.2.9, and also update CHANGELOG.rst.


Test and validate the HTTP(s) request handling framework

The framework itself is working as expected, but there is a significant limitation in the connector-level implementation:
The retry counter on associated message objects is successfully incremented when a message fails, but the value is lost/reset to 0 during regular operation. The connector manages data using payload objects, separate from the message objects that are built at each request. As such, failed messages will be retried as expected, but the fail/retry counter will always be 0 since a fresh message object was created for the specific attempt/try.
Due to this limitation, the connector cannot accurately track the number of times a payload/message has been retried. This means there is no upper limit on retries and no time-based backoff mechanism. While it has not been encountered during testing, it is reasonable to assume that an infinite retry condition could be experienced, where the connector would be unable to recover without restart.
Note: This condition has existed since v1.0.0/v1.0.1 of the connector and is not introduced by any ongoing development changes for v1.0.2.)


warning: Mail.Message.put_header/3 is undefined

I have just started working with swoosh. I have added swoosh and gen_smtp to the dependencies.
When I run mix compile, I get this warning:
===> Compiling gen_smtp
==> swoosh
Compiling 34 files (.ex)
warning: Mail.Message.put_header/3 is undefined (module Mail.Message is not available or is yet to be defined)
  lib/swoosh/adapters/gmail.ex:152: Swoosh.Adapters.Gmail.prepare_custom_headers/2

Generated swoosh app

For gmail https://hex.pm/packages/mail is also required.

Thanks for the info. Then it is just a bit annoying warning, as I am currently not using gmail.

I'll look into it
On Wed, 12 May 2021, 16:34 Peter de Boer, @.***> wrote:

Thanks for the info. Then it is just a bit annoying warning, as I am
currently not using gmail.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/swoosh/swoosh/issues/596#issuecomment-839500958, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKEUNB2ATW6GTTMYISHB5TTNIOOVANCNFSM44X4QJCA
.

What version are you on? We have this in mix.exs, which suppresses warnings. There shouldn't be warnings when compiling swoosh, even if some modules don't exist.

You can see in my one of my own projects
...
#11 80.76 ==> plug
#11 80.76 Compiling 1 file (.erl)
#11 81.00 Compiling 41 files (.ex)
#11 81.83 warning: System.stacktrace/0 is deprecated, use __STACKTRACE__ instead
#11 81.83   lib/plug/conn/wrapper_error.ex:23
#11 81.83
#11 84.82 warning: MIME.valid?/1 is deprecated. Use MIME.extensions(type) != [] instead
#11 84.82   lib/plug/mime.ex:32: Plug.MIME.valid?/1
#11 84.82
#11 84.97 Generated plug app
#11 85.04 ==> plug_cowboy
#11 85.04 Compiling 5 files (.ex)
#11 85.32 Generated plug_cowboy app
#11 85.39 ==> phoenix
#11 85.39 Compiling 66 files (.ex)
#11 90.91 Generated phoenix app
#11 90.99 ==> swoosh
#11 90.99 Compiling 34 files (.ex)
#11 93.43 Generated swoosh app
#11 93.47 ==> phoenix_ecto
#11 93.47 Compiling 7 files (.ex)
#11 93.91 Generated phoenix_ecto app
#11 DONE 94.0s

I don't have :mail either.

Actually, I think it was introduced by a recent feature addition. https://github.com/swoosh/swoosh/pull/587

Should be good now in 1.3.6
Thanks for the report!

Thanks to you, for the quick support!


Update UserGuide to fit SOCompiler

Add new functions to UG
Update command syntax of add, list and delete for contact
Remove traces of AB3
Fix yingming's profile pic naming

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (a3e37d9) compared to base (4f312f1).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #36   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

LGTM


quick sort added

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR
QUICK SORT ADDED FOR JAVASCRIPT
Other information:

Hi @Hemangpandey,
Please fix the linter error for quick-sort.js
Error:    2:44  error  Missing space before opening brace                 space-before-blocks
Error:    3:1   error  Expected indentation of 2 spaces but found 4       indent
Error:    3:5   error  Unexpected var, use let or const instead           no-var
Error:    4:1   error  Expected indentation of 2 spaces but found 4       indent
Error:    5:1   error  Expected indentation of 2 spaces but found 4       indent
Error:    8:1   error  Expected indentation of 2 spaces but found 4       indent
Error:    8:5   error  Split 'var' declarations into multiple statements  one-var
Error:    8:5   error  Unexpected var, use let or const instead           no-var
Error:    8:14  error  Multiple spaces found before '='                   no-multi-spaces
Error:    8:58  error  Expected space or tab after '//' in comment        spaced-comment
Error:    9:1   error  Expected indentation of 4 spaces but found 8       indent
Error:    9:10  error  Multiple spaces found before '='                   no-multi-spaces
Error:    9:25  error  Expected space or tab after '//' in comment        spaced-comment
Error:   10:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   10:10  error  Multiple spaces found before '='                   no-multi-spaces
Error:   10:26  error  Expected space or tab after '//' in comment        spaced-comment
Error:   11:1   error  Expected indentation of 2 spaces but found 4       indent
Error:   12:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   13:1   error  Expected indentation of 6 spaces but found 12      indent
Error:   14:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   15:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   16:1   error  Expected indentation of 6 spaces but found 12      indent
Error:   17:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   18:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   19:1   error  Expected indentation of 6 spaces but found 12      indent
Error:   19:32  error  Expected space or tab after '//' in comment        spaced-comment
Error:   20:1   error  Expected indentation of 6 spaces but found 12      indent
Error:   21:1   error  Expected indentation of 6 spaces but found 12      indent
Error:   22:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   23:1   error  Expected indentation of 2 spaces but found 4       indent
Error:   24:1   error  Expected indentation of 2 spaces but found 4       indent
Error:   28:1   error  Expected indentation of 2 spaces but found 4       indent
Error:   28:5   error  Unexpected var, use let or const instead           no-var
Error:   29:1   error  Expected indentation of 2 spaces but found 4       indent
Error:   30:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   30:48  error  Expected space or tab after '//' in comment        spaced-comment
Error:   31:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   31:33  error  Expected space or tab after '//' in comment        spaced-comment
Error:   32:1   error  Expected indentation of 6 spaces but found 12      indent
Error:   33:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   34:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   34:30  error  Expected space or tab after '//' in comment        spaced-comment
Error:   35:1   error  Expected indentation of 6 spaces but found 12      indent
Error:   36:1   error  Expected indentation of 4 spaces but found 8       indent
Error:   37:1   error  Expected indentation of 2 spaces but found 4       indent
Error:   38:1   error  Expected indentation of 2 spaces but found 4       indent
Error:   41:1   error  Unexpected var, use let or const instead           no-var
Error:   41:15  error  A space is required after ','                      comma-spacing
Error:   41:17  error  A space is required after ','                      comma-spacing
Error:   41:19  error  A space is required after ','                      comma-spacing
Error:   41:21  error  A space is required after ','                      comma-spacing
Error:   41:23  error  A space is required after ','                      comma-spacing
Error:   42:1   error  Unexpected var, use let or const instead           no-var
Error:   43:27  error  Expected space or tab after '//' in comment        spaced-comment


Empty SQL query hangs forever

I was testing something and by mistake had a variable with a query string empty. Executing it (or rather parsing the results) hangs forever until killed by the OS.
How to reproduce
var foo []struct {
	Bar string `json:"bar"`
}
if err := app.Dao().DB().NewQuery("").All(&foo); err != nil {
	panic(err)
}

fmt.Printf("%+v\n", foo)

Output:
[1.00ms] SELECT {{_params}}.* FROM `_params` WHERE `key`='settings' LIMIT 1
[0.00ms] SELECT {{_collections}}.* FROM `_collections`
[0.00ms]
signal: killed
go run ./cmd/server/main.go sql test-stuck  254.63s user 64.77s system 109% cpu 4:51.43 total

Expected behaviour

Return error for empty query
Add timeout to func (r *Rows) all(slice interface{}) error

Versions, etc
MacOS, arm64
	github.com/pocketbase/dbx v1.10.1
	github.com/pocketbase/pocketbase v0.22.17

This happens with both CGo enabled or disabled.

I'm not able to reproduce it with CGO disabled (aka. CGO_ENABLED=0 go run . serve).
I think it is an issue with the CGO driver (eg. https://github.com/mattn/go-sqlite3/issues/950) but I'll consider applying eventually a workaround for it in the dbx repo (there is also https://github.com/mattn/go-sqlite3/issues/1284 that I'll have to experiement how to workaround but other tasks are with higher priority right now).

It is the same issue as above, here is a minimal reproducible:
package main

import (
	"database/sql"
	"log"
	"os"

	_ "github.com/mattn/go-sqlite3"
	// _ "modernc.org/sqlite"
)

func main() {
	os.Remove("./foo.db")

	// modernc driver name is "sqlite"
	db, err := sql.Open("sqlite3", "./foo.db")
	if err != nil {
		log.Fatal(err)
	}
	defer db.Close()

	println("start")

	r, err := db.Query(``)
	for r.Next() {
		println("row...")
	}

	println("end")
}

In any case, this is is easy to workaound and I'll consider skipping the empty query execution from the dbx repo.


Manta to Strelka default values

We utilize primarily the default config options for manta, this includes minScoredVariantSize = 50, which is used "after candidate identification, only score and report SVs/indels at or above this size". Yet we tell Strelka to only look at variants smaller than 50. Need to check if strelka is actually doing anything.

Still need to investigate

COLO genome manta --> strelka VERSUS strelka alone
Compare VCF outputs


Added Node/npm version plugin

This is version 1. it is still missing the enhancements talked out in the last commit. #57

Looks great to me :+1:. Just gonna add a few comments.

I am sorry that I have not committed anything towards this in the last few days. I have been very busy. I will work on the code from tonight.

@castellanprime awesome. Don't worry. Keep up the good work!

I have fixed the errors in the pull request.

Added your changes

Added your changes. I wonder if you looked at my earlier suggestion about the .nmvrc/yarn.lock files?  Is that what you wanted? Thanks.

@castellanprime Regarding yarn.lock I think it's a great addition to put us ahead of other prompts. If you are up for it we can work on this on another PR. :)


Multiple input and multiple output

Hi, I am a new user of nextflow. I have test1.bed, test1.bim, test1.fam files. I want to do some qc using plink in nextflow. How can I import those three files in nextflow and get output test2.bed, test2.bim, test2.fam which will be used in the next step to generate test3.bed, test3.bim, test3.fam and so on? I also need to save all the intermediate files in a directory. Any help with example?
Kind regards, Zillur

Closing since this is a general Nextflow question rather than a new pattern suggestion. Feel free to ask your question on the Discussions page.


HTTPClient's queryParams are not added to requests that have no query parameters (aka nil)

Hi I've noticed that even if I set a bunch of query parameters on my HTTPClient instance, they are not added on the requests that don't have query parameters (i.e. request.queryItems is nil, not an empty dict) :
In HTTPRequest.swift line 536,  if newComps.queryItems is nil, then the .append(contentsOf:) will not occur.
if let commonQueryParams = client?.queryParams, commonQueryParams.isEmpty == false {
    newComp.queryItems?.append(contentsOf: commonQueryParams)
 }

Not sure if it's an expected behaviour or a bug 🤔
Feel free to close this issue directly if this is intentional 😉

Hi @nashfive , it was an issue. I've fixed it and added related unit test. I'll release it with 1.3.2.


Added outPath attribute to self' and flakeModules to inputs'

Very straightforward. Was needed for clojix.

Both changes could perhaps be implemented more cleanly with an attribute such that self'.flake == self, as suggested in #152

Yes, good points. Forgot I also was adding flakeModules afterwards. I'll be more careful with my PR branches! Thanks.


Shellv2

There were probably some interesting changes in this very old branch from 2009 but it is really outdated so we won't merge it without any new recent code


Lab 5 - broken link

Link to cell

Now let's get the context vector for the start token. We'll want to use some of the Pytorch tensor slicing that we learned at the end of the Tokenization section.link text

Link leads to nowhere.

Removed. Thanks. 1 point.


:valid proper use..?

Hi, not sure if this is a bug or I'm not using the :valid prop correctly..
I'm doing:
<md.. :valid="someComputedBoolean">
It seems the prop only receives the inital value but never
changes according to the computed value.. what am i doing wrong?
thanks!

It works in live demo http://appcomponents.org/material-components/#!/forms/showcase
src: https://github.com/appcomponents/material-components/blob/master/src/docs/forms/input-fields/input.html

You could point similar issue as I had, you are not passing boolean

Sorry for delay in reply.
I see it working in the demo, but for me it's still not working.
I'm using a computed property to return a boolean, something like this:
computed: { lastNameValid() { return !!this.lastName } }
Only the initial value seems to have an effect.
I tested to see if a CSS class would change according to boolean:
<md-input :class="[validName ? 'valid-class' : '']" :valid.sync="validName">First name</md-input>
The class changes just fine according to the computed boolean, but the valid prop
never does. What am i doing wrong?
thanks for your time.


Fix benchmark database wipe for child tries.

wipe didn't reset child key tracker, this PR fix it and add a test.

bot merge

bot merge


Pin SwiftSyntaxBuilder version for generate-swiftsyntaxbuilder

This pretty much re-opens https://github.com/apple/swift-syntax/pull/580 on top of current main.
This resolves a bootstrapping issue that running generate-swiftsyntaxbuilder might modify SwiftSyntaxBuilder, which in turn makes it impossible to build and run generate-swiftsyntaxbuilder.

@swift-ci Please test

https://github.com/apple/swift/pull/61226
@swift-ci Please test

https://github.com/apple/swift/pull/61226
@swift-ci Please test macOS

https://github.com/apple/swift/pull/61226
@swift-ci Please test macOS

https://github.com/apple/swift/pull/61226
@swift-ci Please test Linux

https://github.com/apple/swift/pull/61226
@swift-ci Please test

https://github.com/apple/swift/pull/61226
@swift-ci Please test


Fix error messages for private properties

Q
A

Fixed Issues?
N/A

Patch: Bug Fix?
Yes

Major: Breaking Change?
No

Minor: New Feature?
No

Tests Added + Pass?
Yes

Documentation PR
No

Any Dependency Changes?
No

License
MIT

These were changed when implementing the lexical topic parsing.

Thanks. Were these test cases previously modified by #1, or did #1 accidentally make these test cases fail where they had been passing?

Looks the like the answer is both. I wonder how I missed this; https://github.com/valtech-nyc/babel/pull/1/files#diff-8a085ee7dd168acc87717463e6269953 and below were changed by #1, but it looks like the message was wrong…?

My assumption was that these tests were introduced later on master and weren't present while you were developing, but who knows.


Inference.py

Hi,
Thanks for the code.
I have two questions on inference.py.

What should be cached_data.pickle? Should it be cached_data_train.pickle or cached_data_val.pickle?
Model is saved with help of 5 parameters "field, candidate, words, positions, masks". However, inference is using only 4 parameters (field_ids, candidate_cords, neighbours, neighbour_cords). This is resulting in error while executing inference.py. Can you guide me if I am missing something?

Below is the error that I am getting.
forward() missing 1 required positional argument: 'masks'
Thanks in advance

It needs to be cached_data_train.pickle
You need to pass in masks=None for it as it is used for self-attention. It's an optional arg, so you can pass in None there and it should work


Caesar cipher Algorithm

Ma'am i have done caesar cipher algorithm before assigning the issue. And i have sent the pull request to you. So please assigning the caesar cipher algorithm. And check my pull request of caesar cipher.

Title: Caesar Cipher
Language: Python
Directory: Cipher
Name: Manthan Nagpurkar

☑Hacktoberfest
☑Contributor
Description
To implement the algorithm of Caesar Cipher in python language. This algorithm is used for Encrypt and Decrypt the message.
@prathimacode-hub Please assign this issue to me.

Issue assigned to @manthan0227


fix: improve reliability of test_tekton_task script

This script runs as part of PR checks on Github
and sometimes it gets stuck on this command:
tkn pr logs $PIPELINERUN -f
"-f" stands for follow. It seems sometimes it has issues following the logs - it does and then gets stuck.
This should avoid the issue, but at the price
of not being able to see the log live as
the PR runs. It will be spit out once the PR finishes.
This came up during review of https://github.com/redhat-appstudio/release-service-bundles/pull/169

If we cancel in progress because it is stuck for some reason, we no longer see the logs now, right? Not sure how important that is... I just know it is frustrating when you just see them hanging and don't know why

If we cancel in progress because it is stuck for some reason, we no longer see the logs now, right? Not sure how important that is... I just know it is frustrating when you just see them hanging and don't know why

Yeah, that's a good point. Right now the limited evidence I have says that this getting stuck is only happening with the -f option. And in this case the actual PipelineRun was not stuck, just the command following the logs. But if we ever see a PipelineRun actually get stuck, we wouldn't know how far it got.
I guess I'd say that we can tackle that once/if that ever happens. We could for example wait only a certain time for the PR to finish and if it's still not done, we would print the logs and fail.

If we cancel in progress because it is stuck for some reason, we no longer see the logs now, right? Not sure how important that is... I just know it is frustrating when you just see them hanging and don't know why

Yeah, that's a good point. Right now the limited evidence I have says that this getting stuck is only happening with the -f option. And in this case the actual PipelineRun was not stuck, just the command following the logs. But if we ever see a PipelineRun actually get stuck, we wouldn't know how far it got.
I guess I'd say that we can tackle that once/if that ever happens. We could for example wait only a certain time for the PR to finish and if it's still not done, we would print the logs and fail.

I suppose the behavior isn't changed in the case the name doesn't match the file name. That is the case I am most concerned about. This seems to not change that, so we can tackle that in another PR. Good to merge this

I suppose the behavior isn't changed in the case the name doesn't match the file name. That is the case I am most concerned about. This seems to not change that, so we can tackle that in another PR. Good to merge this

OK, merging, thanks. I think we should add a check that will verify that the filename and name match.


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
14 seconds
deprecated-base-image-check

✅ Succeeded
14 seconds
inspect-image

✅ Succeeded
20 seconds
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
10 seconds
label-check

✅ Succeeded
10 seconds
optional-label-check

✅ Succeeded
5 seconds
show-summary

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
14 seconds
deprecated-base-image-check

✅ Succeeded
14 seconds
inspect-image

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
20 seconds
clair-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
10 seconds
label-check

✅ Succeeded
10 seconds
optional-label-check

✅ Succeeded
5 seconds
show-summary


Don’t forget about keyEncoder & keyDecoder within initializer.

          1 Warning

:warning:
Any source code changes should have an entry in CHANGELOG.md or have #trivial in their title.

  Generated by :no_entry_sign: Danger