[Bug Report] Failed to Start on Developer Build

npmplus_logs.txt
Here are the Logs, you can see after:
"2024/09/20 11:07:25 [notice] 1715#1715: ModSecurity-nginx v1.0.3 (rules loaded inline/local/remote: 0/21/0)"
Failed:
/app/lib/utils.js:19
					reject(new error.CommandError(stderr, isError));
					       ^
CommandError
    at /app/lib/utils.js:19:13
    at ChildProcess.exithandler (node:child_process:430:5)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at Socket.<anonymous> (node:internal/child_process:457:11)
    at Socket.emit (node:events:519:28)
    at Pipe.<anonymous> (node:net:338:12) {
  previous: undefined,
  code: Error: Command failed: certbot-ocsp-fetcher.sh -c /data/tls/certbot -o /data/tls/certbot/live --quiet --no-reload-webserver

      at genericNodeError (node:internal/errors:984:15)
      at wrappedFn (node:internal/errors:538:14)
      at ChildProcess.exithandler (node:child_process:422:12)
      at ChildProcess.emit (node:events:519:28)
      at maybeClose (node:internal/child_process:1105:16)
      at Socket.<anonymous> (node:internal/child_process:457:11)
      at Socket.emit (node:events:519:28)
      at Pipe.<anonymous> (node:net:338:12) {
    code: 1,
    killed: false,
    signal: null,
    cmd: 'certbot-ocsp-fetcher.sh -c /data/tls/certbot -o /data/tls/certbot/live --quiet --no-reload-webserver'
  },
  public: false
}

Node.js v20.15.1

Hi, can you please execute this inside the container please:
certbot-ocsp-fetcher.sh -c /data/tls/certbot -o /data/tls/certbot/live --no-reload-webserver; echo $?

/app # certbot-ocsp-fetcher.sh -c /data/tls/certbot -o /data/tls/certbot/live --no-reload-webserver; echo $?
Running in stand-alone mode...

LINEAGE RESULT  REASON
npm-10  not updated     valid staple file on disk
npm-11  not updated     valid staple file on disk
npm-12  not updated     valid staple file on disk
npm-14  not updated     valid staple file on disk
npm-15  not updated     valid staple file on disk
npm-16  not updated     valid staple file on disk
npm-17  not updated     valid staple file on disk
npm-18  not updated     valid staple file on disk
npm-2   failed to update        leaf certificate expired
npm-20  not updated     valid staple file on disk
npm-21  not updated     valid staple file on disk
npm-23  not updated     valid staple file on disk
npm-25  not updated     valid staple file on disk
npm-26  not updated     valid staple file on disk
npm-27  not updated     valid staple file on disk
npm-3   not updated     valid staple file on disk
npm-34  not updated     valid staple file on disk
npm-36  not updated     valid staple file on disk
npm-37  not updated     valid staple file on disk
npm-6   not updated     valid staple file on disk
npm-7   not updated     valid staple file on disk
npm-8   not updated     valid staple file on disk
npm-9   not updated     valid staple file on disk

Install the BSD utility `column` for properly formatted output.
If the version of `column` supports the `--output-separator` flag,
the output will be formatted as TSV.

Here are the Output

/app # openssl x509 -enddate -noout -in /data/tls/certbot/live/npm-2/fullchain.pem
notAfter=Aug 26 07:18:15 2024 GMT

?

Did you removed a number at the end of the output?

Weird npm-6 is pm.clawsucht.de (Nginx Proxy Manager) and the npm-2 is the pm.clawsucht.de (Expired Certificate).
After i deleted npm-2 Folder in certbot, it give no more Failures.

So it works with npm-2 deleted?

Yes but now i have another Problem: ```
2024-09-20 13:16:29,906:DEBUG:certbot._internal.main:certbot version: 2.11.0
2024-09-20 13:16:29,907:DEBUG:certbot._internal.main:Location of certbot entry point: /usr/local/bin/certbot
2024-09-20 13:16:29,907:DEBUG:certbot._internal.main:Arguments: ['--logs-dir', '/tmp/certbot-log', '--work-dir', '/tmp/certbot-work', '--config-dir', '/data/tls/certbot', '--config', '/data/tls/certbot/config.ini', '--cert-name', 'npm-39', '--domains', 'analytics.clawsucht.de', '--authenticator', 'dns-cloudflare', '--dns-cloudflare-credentials', '/data/tls/certbot/credentials/credentials-39', '--email'<EMAIL_ADDRESS>2024-09-20 13:16:29,907:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#dns-cloudflare,PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2024-09-20 13:16:29,917:DEBUG:certbot._internal.log:Root logging level set at 30
2024-09-20 13:16:29,918:DEBUG:certbot._internal.plugins.selection:Requested authenticator dns-cloudflare and installer None
2024-09-20 13:16:29,918:DEBUG:certbot._internal.plugins.selection:Single candidate plugin: * dns-cloudflare
Description: Obtain certificates using a DNS TXT record (if you are using Cloudflare for DNS).
Interfaces: Authenticator, Plugin
Entry point: EntryPoint(name='dns-cloudflare', value='certbot_dns_cloudflare._internal.dns_cloudflare:Authenticator', group='certbot.plugins')
Initialized: <certbot_dns_cloudflare._internal.dns_cloudflare.Authenticator object at 0x7fe979df8110>
Prep: True
2024-09-20 13:16:29,918:DEBUG:certbot._internal.plugins.selection:Selected authenticator <certbot_dns_cloudflare._internal.dns_cloudflare.Authenticator object at 0x7fe979df8110> and installer None
2024-09-20 13:16:29,918:INFO:certbot._internal.plugins.selection:Plugins selected: Authenticator dns-cloudflare, Installer None
2024-09-20 13:16:30,622:DEBUG:acme.client:Sending GET request to https://acme.zerossl.com/v2/DV90.
2024-09-20 13:16:30,623:DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): acme.zerossl.com:443
2024-09-20 13:16:30,833:DEBUG:urllib3.connectionpool:https://acme.zerossl.com:443 "GET /v2/DV90 HTTP/11" 200 645
2024-09-20 13:16:30,833:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Fri, 20 Sep 2024 11:16:30 GMT
Content-Type: application/json
Content-Length: 645
Connection: keep-alive
Access-Control-Allow-Origin: *
Strict-Transport-Security: max-age=15724800; includeSubDomains
{
"newNonce": "https://acme.zerossl.com/v2/DV90/newNonce",
"newAccount": "https://acme.zerossl.com/v2/DV90/newAccount",
"newOrder": "https://acme.zerossl.com/v2/DV90/newOrder",
"revokeCert": "https://acme.zerossl.com/v2/DV90/revokeCert",
"keyChange": "https://acme.zerossl.com/v2/DV90/keyChange",
"meta": {
"termsOfService": "https://secure.trust-provider.com/repository/docs/Legacy/20230516_Certificate_Subscriber_Agreement_v_2_6_click.pdf",
"website": "https://zerossl.com",
"caaIdentities": ["sectigo.com", "trust-provider.com", "usertrust.com", "comodoca.com", "comodo.com"],
"externalAccountRequired": true
}
}
2024-09-20 13:16:30,833:DEBUG:certbot._internal.main:
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/main.py", line 741, in _determine_account
acc, acme = client.register(
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/client.py", line 209, in register
regr = perform_registration(acme, config, tos_cb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/client.py", line 248, in perform_registration
raise errors.Error(msg)
certbot.errors.Error: Server requires external account binding. Please use --eab-kid and --eab-hmac-key.
2024-09-20 13:16:30,834:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/main.py", line 741, in _determine_account
acc, acme = client.register(
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/client.py", line 209, in register
regr = perform_registration(acme, config, tos_cb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/client.py", line 248, in perform_registration
raise errors.Error(msg)
certbot.errors.Error: Server requires external account binding. Please use --eab-kid and --eab-hmac-key.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/certbot", line 8, in
sys.exit(main())
^^^^^^
File "/usr/local/lib/python3.12/site-packages/certbot/main.py", line 19, in main
return internal_main.main(cli_args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/main.py", line 1894, in main
return config.func(config, plugins)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/main.py", line 1582, in certonly
le_client = _init_le_client(config, auth, installer)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/main.py", line 833, in _init_le_client
acc, acme = _determine_account(config)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/certbot/_internal/main.py", line 754, in _determine_account
raise errors.Error(
certbot.errors.Error: Unable to register an account with ACME server. Server requires external account binding. Please use --eab-kid and --eab-hmac-key.
2024-09-20 13:16:30,835:ERROR:certbot._internal.log:Unable to register an account with ACME server. Server requires external account binding. Please use --eab-kid and --eab-hmac-key.

Okay, i must Register on ZeroSSL and now i have the 2 Things i need. ^^
Now the Ticket can Close

Perfect ^^

This certificate expires on 2024-12-19.
These files will be updated when the certificate renews.
NEXT STEPS:

The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https://certbot.org/renewal-setup for instructions.

If you like Certbot, please consider supporting our work by:

Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
Donating to EFF:                    https://eff.org/donate-le

[Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/23.conf
[Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/23.conf
[Nginx    ] › ⬤  debug     Could not delete file: {
"errno": -2,
"code": "ENOENT",
"syscall": "unlink",
"path": "/data/nginx/proxy_host/23.conf"
}
[Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/23.conf.err
[Nginx    ] › ⬤  debug     Could not delete file: {
"errno": -2,
"code": "ENOENT",
"syscall": "unlink",
"path": "/data/nginx/proxy_host/23.conf.err"
And the next error when i create new certificate, the old npm not deleted and when i manually delete it give the error

for your last commt, what is the issue exactly?

@Zoey2936 How can i fix it?

If you tell me what the issue is

Working on file: /data/nginx/proxy_host/3.conf
Working on file: /data/nginx/proxy_host/30.conf
Working on file: /data/nginx/proxy_host/4.conf
Working on file: /data/nginx/proxy_host/5.conf
Working on file: /data/nginx/proxy_host/6.conf
Working on file: /data/nginx/proxy_host/7.conf
Working on file: /data/nginx/proxy_host/8.conf
Working on file: /data/nginx/proxy_host/9.conf
Success.

| \ || . |  \  \ ___ | | _ _  ___
|   ||  /|     || . | || | |[-[
|_|||  |||||  /|| _|/__/
|_|
Version:  2.11.3+8dfb3d2
Date:     Sat Sep 28 08:42:57 CEST 2024
User:     root
PUID:     0
User ID:  0
PGID:     0
Group ID: 0
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [emerg] cannot load certificate "/data/tls/certbot/live/npm-40/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/data/tls/certbot/live/npm-40/fullchain.pem, r) error:10000080:BIO routines::no such file)
nginx: configuration file /usr/local/nginx/conf/nginx.conf test failed

When i issue a new certifricate NPM restart and it give offline Failure when i click on it it has the old config and not renew the Config?

when i click save a new config will use, but it not clear the config right, now i have a failure a removed certificate are missing?

and another: when i renew the Certificate it not revoke a old certificate before

your error description are very bad...

please don't understand that wrong, it is good that your are repüorting errors, but "when i click save a new config will use, but it not clear the config right, now i have a failure a removed certificate are missing?" is something, where I don't understand what the error is

Sorry for Bad Request, i have now setting up NPMPlus and reset it.
2024/09/28 09:30:17 [warn] 586#586: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 09:30:17 [warn] 586#586: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 09:30:17 [warn] 586#586: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 09:30:17 [warn] 586#586: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 09:30:17 [warn] 586#586: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 09:30:17 [warn] 586#586: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 09:30:17 [notice] 586#586: ModSecurity-nginx v1.0.3 (rules loaded inline/local/remote: 0/14/0)
[Certbot  ] › ▶  start     Installing cloudflare...
[Certbot  ] › ☒  complete  Installed cloudflare
[SSL      ] › ℹ  info      Requesting Certbot certificates via Cloudflare for Cert #1: adguard.clawsucht.nrw
[SSL      ] › ℹ  info      Command: certbot --logs-dir /tmp/certbot-log --work-dir /tmp/certbot-work --config-dir /data/tls/certbot certonly --config "/data/tls/certbot/config.ini" --cert-name "npm-1" --domains "adguard.cl-----cht.nrw" --authenticator dns-cloudflare --dns-cloudflare-credentials "/data/tls/certbot/credentials/credentials-1" --email<EMAIL_ADDRESS>[SSL      ] › ℹ  info      Renewing Certbot certificates via Cloudflare for Cert #1: adguard.clawsucht.nrw
[SSL      ] › ℹ  info      Command: certbot --logs-dir /tmp/certbot-log --work-dir /tmp/certbot-work --config-dir /data/tls/certbot renew --force-renewal --config "/data/tls/certbot/config.ini" --cert-name "npm-1" --preferred-challenges "dns,http" --no-random-sleep-on-renew
I try to use ZeroSSL but it make not a Certificate.
It give a Timeout.

The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https://certbot.org/renewal-setup for instructions.

If you like Certbot, please consider supporting our work by:

Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
Donating to EFF:                    https://eff.org/donate-le

[Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf
[Nginx    ] › ⬤  debug     Could not delete file: {
"errno": -2,
"code": "ENOENT",
"syscall": "unlink",
"path": "/data/nginx/proxy_host/1.conf"
}
[Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf
[Nginx    ] › ⬤  debug     Could not delete file: {
"errno": -2,
"code": "ENOENT",
"syscall": "unlink",
"path": "/data/nginx/proxy_host/1.conf"
}
[Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf.err
[Nginx    ] › ⬤  debug     Could not delete file: {
"errno": -2,
"code": "ENOENT",
"syscall": "unlink",
"path": "/data/nginx/proxy_host/1.conf.err"
}
[Nginx    ] › ℹ  info      Reloading Nginx
2024/09/28 10:06:59 [warn] 602#602: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 10:06:59 [warn] 602#602: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 10:06:59 [warn] 602#602: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 10:06:59 [warn] 602#602: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 10:06:59 [warn] 602#602: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
2024/09/28 10:06:59 [warn] 602#602: "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
Here i have created conf withoud SSL and i would add SSL and it give me the SSL Certificate but not update the Config. I must manual update by clicking on Edit an Save

Now with the new Build i have the Following Start Error:
OK: 95 MiB in 97 packages
'/usr/local/nginx/conf/conf.d/include/goaccess.conf' -> '/usr/local/nginx/conf/conf.d/goaccess.conf'
'/usr/local/nginx/conf/conf.d/include/goaccess-no-server-name.conf' -> '/usr/local/nginx/conf/conf.d/goaccess-no-server-name.conf'
Working on file: /data/nginx/custom/events.conf
Working on file: /data/nginx/custom/http.conf
Working on file: /data/nginx/custom/http_top.conf
Working on file: /data/nginx/custom/root_top.conf
Working on file: /data/nginx/custom/server_dead.conf
Working on file: /data/nginx/custom/server_proxy.conf
Working on file: /data/nginx/custom/server_redirect.conf
Working on file: /data/nginx/custom/server_stream.conf
Working on file: /data/nginx/custom/server_stream_tcp.conf
Working on file: /data/nginx/custom/server_stream_udp.conf
Working on file: /data/nginx/custom/stream.conf
Working on file: /data/nginx/custom/stream_top.conf
Working on file: /data/nginx/default.conf
Working on file: /data/nginx/proxy_host/1.conf
Working on file: /data/nginx/proxy_host/10.conf
Working on file: /data/nginx/proxy_host/11.conf
Working on file: /data/nginx/proxy_host/12.conf
Working on file: /data/nginx/proxy_host/13.conf
Working on file: /data/nginx/proxy_host/14.conf
Working on file: /data/nginx/proxy_host/15.conf
Working on file: /data/nginx/proxy_host/16.conf
Working on file: /data/nginx/proxy_host/18.conf
Working on file: /data/nginx/proxy_host/19.conf
Working on file: /data/nginx/proxy_host/2.conf
Working on file: /data/nginx/proxy_host/3.conf
Working on file: /data/nginx/proxy_host/4.conf
Working on file: /data/nginx/proxy_host/5.conf
Working on file: /data/nginx/proxy_host/6.conf
Working on file: /data/nginx/proxy_host/7.conf
Working on file: /data/nginx/proxy_host/8.conf
Working on file: /data/nginx/proxy_host/9.conf
Success.
-------------------------------------
 _ _  ___  __ __       _
| \ || . \|  \  \ ___ | | _ _  ___
|   ||  _/|     || . \| || | |[_-[
|_\_||_|  |_|_|_||  _/|_| \__|/__/
                 |_|
-------------------------------------
Version:  2.11.3+a770b35
Date:     Mon Sep 30 21:00:23 CEST 2024
User:     root
PUID:     0
User ID:  0
PGID:     0
Group ID: 0
-------------------------------------
nginx: [emerg] "ssl_stapling" directive is duplicate in /usr/local/nginx/conf/conf.d/goaccess-no-server-name.conf:17
nginx: configuration file /usr/local/nginx/conf/nginx.conf test failed

can you please retry?

OK: 95 MiB in 97 packages
'/usr/local/nginx/conf/conf.d/include/goaccess.conf' -> '/usr/local/nginx/conf/conf.d/goaccess.conf'
'/usr/local/nginx/conf/conf.d/include/goaccess-no-server-name.conf' -> '/usr/local/nginx/conf/conf.d/goaccess-no-server-name.conf'
Working on file: /data/nginx/custom/events.conf
Working on file: /data/nginx/custom/http.conf
Working on file: /data/nginx/custom/http_top.conf
Working on file: /data/nginx/custom/root_top.conf
Working on file: /data/nginx/custom/server_dead.conf
Working on file: /data/nginx/custom/server_proxy.conf
Working on file: /data/nginx/custom/server_redirect.conf
Working on file: /data/nginx/custom/server_stream.conf
Working on file: /data/nginx/custom/server_stream_tcp.conf
Working on file: /data/nginx/custom/server_stream_udp.conf
Working on file: /data/nginx/custom/stream.conf
Working on file: /data/nginx/custom/stream_top.conf
Working on file: /data/nginx/default.conf
Working on file: /data/nginx/proxy_host/1.conf
Working on file: /data/nginx/proxy_host/10.conf
Working on file: /data/nginx/proxy_host/11.conf
Working on file: /data/nginx/proxy_host/12.conf
Working on file: /data/nginx/proxy_host/13.conf
Working on file: /data/nginx/proxy_host/14.conf
Working on file: /data/nginx/proxy_host/15.conf
Working on file: /data/nginx/proxy_host/16.conf
Working on file: /data/nginx/proxy_host/18.conf
Working on file: /data/nginx/proxy_host/19.conf
Working on file: /data/nginx/proxy_host/2.conf
Working on file: /data/nginx/proxy_host/3.conf
Working on file: /data/nginx/proxy_host/4.conf
Working on file: /data/nginx/proxy_host/5.conf
Working on file: /data/nginx/proxy_host/6.conf
Working on file: /data/nginx/proxy_host/7.conf
Working on file: /data/nginx/proxy_host/8.conf
Working on file: /data/nginx/proxy_host/9.conf
Success.
-------------------------------------
 _ _  ___  __ __       _
| \ || . \|  \  \ ___ | | _ _  ___
|   ||  _/|     || . \| || | |[_-[
|_\_||_|  |_|_|_||  _/|_| \__|/__/
                 |_|
-------------------------------------
Version:  2.11.3+a6c1c06
Date:     Mon Sep 30 21:30:21 CEST 2024
User:     root
PUID:     0
User ID:  0
PGID:     0
Group ID: 0
-------------------------------------
nginx: [emerg] "ssl_stapling" directive is duplicate in /usr/local/nginx/conf/conf.d/goaccess-no-server-name.conf:17
nginx: configuration file /usr/local/nginx/conf/nginx.conf test failed

No its the same Issue.

please retry again

-------------------------------------
 _ _  ___  __ __       _
| \ || . \|  \  \ ___ | | _ _  ___
|   ||  _/|     || . \| || | |[_-[
|_\_||_|  |_|_|_||  _/|_| \__|/__/
                 |_|
-------------------------------------
Version:  2.11.3+cba0ccd
Date:     Mon Sep 30 22:06:04 CEST 2024
User:     root
PUID:     0
User ID:  0
PGID:     0
Group ID: 0
-------------------------------------
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
reading config file /etc/logrotate
acquired lock on state file /data/etc/logrotate.statusReading state from file: /data/etc/logrotate.status
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Handling 1 logs
rotating pattern: /data/nginx/*.log  after 1 days (7 rotations)
empty log files are not rotated, old logs are removed
considering log /data/nginx/access.log
  Now: 2024-09-30 22:06
  Last rotated at 2024-09-30 06:32
  log does not need rotating (log has been rotated at 2024-09-30 06:32, which is less than a day ago)
considering log /data/nginx/stream.log
  Now: 2024-09-30 22:06
  Last rotated at 2024-09-28 09:00
  log does not need rotating (log is empty)
not running postrotate script, since no logs were rotated
 [SETTING UP STORAGE -] {0} @ {0/s}
[30-Sep-2024 22:06:04] NOTICE: fpm is running, pid 1144
[30-Sep-2024 22:06:04] NOTICE: ready to handle connections
[Global   ] › ℹ  info      Using Sqlite: /data/etc/npm/database.sqlite
 [PARSING /data/nginx/access.log] {4956} @ {0/s}
 [PARSING /data/nginx/access.log] {9683} @ {0/s}
 [PARSING /data/nginx/access.log] {14344} @ {0/s}

WebSocket server ready to accept new client connections
[Migrate  ] › ℹ  info      Current database version: none
[Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
node:internal/fs/rimraf:60
    callback(err);
    ^
TypeError: callback is not a function
    at CB (node:internal/fs/rimraf:60:5)
    at node:internal/fs/rimraf:91:14
    at FSReqCallback.oncomplete (node:fs:187:23)
Node.js v20.15.1
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/community/x86_64/APKINDEX.tar.gz
  0%                                             OK: 95 MiB in 97 packages
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/community/x86_64/APKINDEX.tar.gz
  0%                                             OK: 95 MiB in 97 packages
sed: /data/nginx/default.conf: No such file or directory
sed: /data/nginx/default.conf: No such file or directory
'/usr/local/nginx/conf/conf.d/include/coreruleset/plugins/README.md' -> '/data/etc/modsecurity/crs-plugins/README.md'
'/usr/local/nginx/conf/conf.d/include/coreruleset/plugins/empty-after.conf' -> '/data/etc/modsecurity/crs-plugins/empty-after.conf'
'/usr/local/nginx/conf/conf.d/include/coreruleset/plugins/empty-before.conf' -> '/data/etc/modsecurity/crs-plugins/empty-before.conf'
'/usr/local/nginx/conf/conf.d/include/coreruleset/plugins/empty-config.conf' -> '/data/etc/modsecurity/crs-plugins/empty-config.conf'
no DEFAULT_CERT_ID set, using dummycerts.
sed: /data/nginx/default.conf: No such file or directory
sed: /data/nginx/default.conf: No such file or directory
sed: /data/nginx/default.conf: No such file or directory
sed: /data/nginx/default.conf: No such file or directory
'/usr/local/nginx/conf/conf.d/include/default.conf' -> '/data/nginx/default.conf'
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/community/x86_64/APKINDEX.tar.gz
  0%                                             OK: 95 MiB in 97 packages
Working on file: /data/nginx/custom/events.conf
Working on file: /data/nginx/custom/http.conf
Working on file: /data/nginx/custom/http_top.conf
Working on file: /data/nginx/custom/root_top.conf
Working on file: /data/nginx/custom/server_dead.conf
Working on file: /data/nginx/custom/server_proxy.conf
Working on file: /data/nginx/custom/server_redirect.conf
Working on file: /data/nginx/custom/server_stream.conf
Working on file: /data/nginx/custom/server_stream_tcp.conf
Working on file: /data/nginx/custom/server_stream_udp.conf
Working on file: /data/nginx/custom/stream.conf
Working on file: /data/nginx/custom/stream_top.conf
Working on file: /data/nginx/default.conf
Working on file: /data/nginx/proxy_host/1.conf
Working on file: /data/nginx/proxy_host/10.conf
Working on file: /data/nginx/proxy_host/11.conf
Working on file: /data/nginx/proxy_host/12.conf
Working on file: /data/nginx/proxy_host/13.conf
Working on file: /data/nginx/proxy_host/14.conf
Working on file: /data/nginx/proxy_host/15.conf
Working on file: /data/nginx/proxy_host/16.conf
Working on file: /data/nginx/proxy_host/18.conf
Working on file: /data/nginx/proxy_host/19.conf
Working on file: /data/nginx/proxy_host/2.conf
Working on file: /data/nginx/proxy_host/3.conf
Working on file: /data/nginx/proxy_host/4.conf
Working on file: /data/nginx/proxy_host/5.conf
Working on file: /data/nginx/proxy_host/6.conf
Working on file: /data/nginx/proxy_host/7.conf
Working on file: /data/nginx/proxy_host/8.conf
Working on file: /data/nginx/proxy_host/9.conf
Success.
removed '/usr/local/nginx/logs/nginx.pid'
removed '/run/php83.sock'

Here are the next error

-------------------------------------
 _ _  ___  __ __       _
| \ || . \|  \  \ ___ | | _ _  ___
|   ||  _/|     || . \| || | |[_-[
|_\_||_|  |_|_|_||  _/|_| \__|/__/
                 |_|
-------------------------------------
Version:  2.11.3+40b59be
Date:     Mon Sep 30 23:17:40 CEST 2024
User:     root
PUID:     0
User ID:  0
PGID:     0
Group ID: 0
-------------------------------------
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
nginx: [warn] "ssl_stapling" ignored, issuer certificate not found for certificate "/data/tls/dummycert.pem"
reading config file /etc/logrotate
acquired lock on state file /data/etc/logrotate.statusReading state from file: /data/etc/logrotate.status
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Handling 1 logs
rotating pattern: /data/nginx/*.log  after 1 days (7 rotations)
empty log files are not rotated, old logs are removed
considering log /data/nginx/access.log
  Now: 2024-09-30 23:17
  Last rotated at 2024-09-30 06:32
  log does not need rotating (log has been rotated at 2024-09-30 06:32, which is less than a day ago)
considering log /data/nginx/stream.log
  Now: 2024-09-30 23:17
  Last rotated at 2024-09-28 09:00
  log does not need rotating (log is empty)
not running postrotate script, since no logs were rotated
 [SETTING UP STORAGE -] {0} @ {0/s}
[30-Sep-2024 23:17:40] NOTICE: fpm is running, pid 1172
[30-Sep-2024 23:17:40] NOTICE: ready to handle connections
[Global   ] › ℹ  info      Using Sqlite: /data/etc/npm/database.sqlite
 [PARSING /data/nginx/access.log] {4811} @ {0/s}
 [PARSING /data/nginx/access.log] {9440} @ {0/s}
 [PARSING /data/nginx/access.log] {14261} @ {14261/s}

WebSocket server ready to accept new client connections
[Migrate  ] › ℹ  info      Current database version: none
[Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
migration file "20240921100301_regenerate_default_host.js" failed
migration failed with error: err is not defined
[Global   ] › ✖  error     err is not defined
[Migrate  ] › ℹ  info      Current database version: none
[Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
migration file "20240921100301_regenerate_default_host.js" failed
migration failed with error: err is not defined
[Global   ] › ✖  error     err is not defined
[Migrate  ] › ℹ  info      Current database version: none
[Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
migration file "20240921100301_regenerate_default_host.js" failed
migration failed with error: err is not defined
[Global   ] › ✖  error     err is not defined
[Migrate  ] › ℹ  info      Current database version: none
[Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
migration file "20240921100301_regenerate_default_host.js" failed

The Failure is in loop

please retry, it should now be fixed

And you pulled the develop tag again?

Can you please pull it again?

Yes i close the Ticket now!
The Issue is Resolved. Thanks @Zoey2936

Please look at this Issue

please retry


Fortran Language Server outdated

Language server
fortls
Requested feature
The fortls link that is listed in the documentation see is quite outdated (and presumed abandoned). I have taken over the work for some time now, for developing and maintaining a Fortran Language Server https://github.com/gnikit/fortls.
The server is mostly backwards compatible with the old one  (hence why the binary name is fortls) so it should break people's workflows.
I am opening the issue because I am not sure if the old reference to fortls should be removed or a new entry should be added with fortls referring to the new server and fortran-language-server to the old one.
I am also having a look at the setup instructions listed for the server because I am not convinced they are correct.
Other clients which have this feature
No response

I am not sure if the old reference to fortls should be removed or a new entry should be added with fortls referring to the new server and fortran-language-server to the old one.

Just remove the old one. PR welcome.
These configs are not intended to be backwards-compatible. People need to either upgrade, or use a custom config. nvim-lspconfig is just a starting point. We can't maintain zillions of backwards-compatible configs.
PR very welcome and appreciated!

Thanks for the info @justinmk I will open a PR soon with the correct info.


when ALL players select the real hashtag and NO players select fake hashtags, the game gets confused and displays it this way

I think this has to do with the game thinking its a player generated hashtag, but it isn't


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In 1f2d9c3, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 10724 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in 15ab70e after 12 hours, 40 minutes.


Memoize some objects for timer processing to reduce overhead.

About 1% total of cpu on google internal benchmark, .8% for allowedLateness

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @lukecwik

Thanks for the benchmark suggestion. Since there isn't a huge rush, I'm going to try to add that before submitting this.

Didn't get around to adding a benchmark, but might as well get this in since it's going stale.


Build issue with the default template & shadow-cljs

[:app] Build completed. (113 files, 2 compiled, 2 warnings, 2.95s)

------ WARNING #1 - :undeclared-var --------------------------------------------
 Resource: clojure/tools/cli.cljc:126:17
--------------------------------------------------------------------------------
 123 |          (recur options (into extra-args (vec (rest args))) nil)
 124 |
 125 |          (and (opt? opt) (nil? spec))
 126 |          (throw (Exception. (str "'" opt "' is not a valid argument")))
-----------------------^--------------------------------------------------------
 Use of undeclared Var clojure.tools.cli/Exception
--------------------------------------------------------------------------------
 127 |
 128 |          (and (opt? opt) (spec :flag))
 129 |          (recur ((spec :assoc-fn) options (spec :name) (flag-for opt))
 130 |                 extra-args
--------------------------------------------------------------------------------

------ WARNING #2 - :undeclared-var --------------------------------------------
 Resource: clojure/tools/cli.cljc:228:25
--------------------------------------------------------------------------------
 225 |   (when *assert*
 226 |     (let [unknown-keys (keys (apply dissoc map spec-keys))]
 227 |       (when (seq unknown-keys)
 228 |         (binding [*out* *err*]
-------------------------------^------------------------------------------------
 Use of undeclared Var clojure.tools.cli/*err*
--------------------------------------------------------------------------------
 229 |           (println (str "Warning: The following options to parse-opts are unrecognized: "
 230 |                         (s/join ", " unknown-keys)))))))
 231 |
 232 |   (select-keys map spec-keys))
--------------------------------------------------------------------------------

I'm running npm -v 6.8.0 and node -v 11.10.0.

This is due to cli tools not fully supporting ClojureScript. However, the core parsing functionality still works in my testing.
If you would like to remove the warnings the best option would be to remove the org.clojure/tools.cli dependency and the code that depends on it. If you still want arg parsing you may be able to use one of the many npm offerings and call (js->clj parsed-js-obj :keywordize-keys true) to get a Clojure hash-map.
Let me know if I can help further. Thanks for reporting this.

That works great. Thank you!

That works great. Thank you!


Remove double encryption (TLS + RSA) of the direct requests

Our tls server used to be in the untrusted world, which is why we had to asymmetrically encrypt the request for encryption. However, now that the TLS server is inside the enclave, TLS encryption is enough. Hence, we should remove the asymmetric encryption in this case to be more efficient and ergonomic.
Edit, maybe we should do this rather soon because SGX uses some fancy params with the RSA encryption, which makes is hard to integrate it in non-rust clients.

I think the RPC can in general be reworked, but removing the encryption of direct requests should be a low-hanging fruit:

Remove encryption in direct requests everywhere in the CLI
Lift decryption of the direct request to one layer above the top-pool-author, to one level above.

There is a minimal caveat, as this means that whatever calls author.submit_top/watch_top must be able to decrypt the trusted operation. As a first step, I think it suffices to expose the shielding_key_repository of the top-pool-author. So the caller that needs to decrypt now (which is only offchain-worker executor or indirect-calls-executor currently) can simply decrypt the request before adding it to the top-pool. I think this low-hanging fruit should be implemented asap, as SDK users do currently need to fiddle with the sgx-rsa crypto with its fancy params.

Yes, I have been considering your thoughts, and our design can handle case differentiation without any issues.


L2VPN gets deleted during link down handler

L2VPN gets deleted when link goes down and there is not alternative path

Changed the subject of this issue because I ended up hitting this issue again when there are alternative paths!!
so what is happening is that during the link failure procedure, the connection is deleted! If SDX-COntroller is able to place another connection, that new connection will NOT be inserted again on database! if no alternative path is found, the Connection is also removed..


how do I save settings now that we don't use the main local.dat?

Now that launchbuddy saves the local.dat per account, I'm unable to have it save the settings. Because every launch of the game runs with -shareArchive, the client can't make changes to the local.dat file permanent.
How do I launch the game in a way that lets me save the settings for that account?

There really isn't a way. Any setting saved within local.dat is impossible to change when running with LB at the moment. It's possible we may look into having specific accounts boot up without -shareArchive for simple settings changes, but that's going to be a weird workflow compared to anything we currently have,

It would be nice to have a way to launch a single account without -shareArchive, as I currently have to manually copy the X.dat file into place of local.dat, load, edit and save settings, and then exit.
It's definitely a very weird workflow right now.


[Feature Request] Method aliases skipping "injector" argument (default injector)

Service register
func ProvideNamedValue[T any](i *Injector, name string, value T) {
func Provide[T any](i *Injector, provider Provider[T]) {

Service lookup
func InvokeNamed[T any](i *Injector, name string) (T, error) {

for these two group method, it can accept a nil Injector, in this case then it will use system default Injector.
can we supply another group of API without the ** Injector* parameter to make a simpler API?

If it supports this set of API then
	do.Provide(nil, config) 	do.Provide(nil, datasource) 	do.Provide(nil, db)
can be writtern as
	do.Provide(config) 	do.Provide(datasource) 	do.Provide(db)
it's much more clean

Thanks for your suggestion, but I'm not sure we will add these shortcuts to the repository.
Using default injectors is basically a bad idea since it makes your code very hard to test. Adding 18 more helpers without the i *do.Injector argument seems excessive to me.
Anyway, you can use a simple alias in your projects:
// utils/do.go
func Provide(provider do.Provider[T]) {
    return do.Provide(nil, provider)
}

I keep this issue open for further discussion. If anybody wants to expose a PoV, please answer this issue!

Thanks for your suggestion, but I'm not sure we will add these shortcuts to the repository.
Using default injectors is basically a bad idea since it makes your code very hard to test. Adding 18 more helpers without the i *do.Injector argument seems excessive to me.
Anyway, you can use a simple alias in your projects:
// utils/do.go
func Provide(provider do.Provider[T]) {
    return do.Provide(nil, provider)
}

I keep this issue open for further discussion. If anybody wants to expose a PoV, please answer this issue!

Using default injectors is basically a bad idea since it makes your code very hard to test

Agree with you about this point. in fact I think about this issue.  right now for me I just use the DefaultInjector directly for unit test. from the respect of API user he need to know the detail design of the library.
another benefit of Method aliases is that we dont need  to pass around the variable around. I can get it just when I want.
might be a global function is better than a global variable.
change
var DefaultInjector = New()
to
func DefaultInjector() *Injector {}

Closing, since it has been added to the project under do.DefaultInjector


Support registries other than docker hub

Would love to see support for registries such as quay.io and gcr.io

yes, support for other registries would be useful

Thanks for the feedback but we don't have any plans to add additional repository support into imagelayers at the moment. The codebase for the repository data is in the imagelayers project if you have the desire to add it yourself. I should have responded sooner. Sorry to leave everyone hanging.


[Question] instalatlion instructions

i'm looking for an headless cms on aws, api's would be great. Are there more details how to deploy to aws? and details wich service and how to setup?

Helo @lblabr!
Thank you for showing interest on the project. Watch out as we wil be releasing a Youtube video on how to install KlaudSol CMS on AWS soon :)

great!


Leverage stdout from starknet-devnet provider process

Overview
Get the output from the starknet-devnet process and put it somewhere
Specification

Grab the stdout and stderr of the starknet-devnet process and put it in file (like in .ape/starknet/provider/stdout.logs)

Might be a way to use Popen
Dependencies
Might need to update  core ape: https://github.com/ApeWorX/ape/blob/main/src/ape/api/providers.py#L1021

just to be extra clear on the use case, storing devnet stdout locally is fine, but the most common use case remains to stream it to Ape/Pytest standard loggers during test runs or deployments

@0xSidius With these changes, you can run with -v debug and the output from the process will be included in Ape's normal logger's output.
The filtering useful logs feature in test runs may be a little more complicated. Might be in the form of a pytest hook implementation.

That got done in Core Ape!
The logs can be found i your .ape data directory


Fix train_test_split docs

I saw that stratify is added to the train_test_split method as per #4322, hence the docs can be updated.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


fix config not cloned

Configs were not being cloned in wasm. This results in +limit=1 not working properly

fixes #302


electron-vite dev redirects

Describe the bug
Whenever I run npm run dev it works initially, but once I update a file it then redirects the http address to the development server to https. This causes the HMR update to fail, so how can I disable the http -> https redirect?
My application does reach put to some https backend endpoints, which I think is why it fails when reaching out to an http endpoint after it begins trusting my systems CAs.
Electron-Vite Version
2.0.0
Electron Version
28.3.3
Vite Version
5.0.12
Validations

[X] Follow the Code of Conduct.
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

https://vitejs.dev/config/server-options.html#server-https
A plugin @vitejs/plugin-basic-ssl may be able to help you.

I was able to get this to work


Grouped workspace language settings don't override non-grouped user language settings

Does this issue occur when all extensions are disabled?: N/A (no extensions means this can't be configured)

Version: 1.76.1 (user setup)
Commit: 5e805b79fcb6ba4c2d23712967df89a089da575b
Date: 2023-03-08T16:32:00.131Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No
Steps to Reproduce:

This in .vscode/settings.json:

{
  "[json][jsonc][javascript][javascriptreact][typescript][typescriptreact][markdown][dockerfile]": {
    "editor.defaultFormatter": "dprint.dprint"
  },
}

Does not override this in %appdata%\Code\User\settings.json:

{
    "[typescript]": {
      "editor.defaultFormatter": "vscode.typescript-language-features"
    }
}

Originally discovered on a colleague's computer because the project was not being correctly autoformatted for them.
I've replicated with the above configuration.

/duplicate
https://github.com/microsoft/vscode/issues/168411

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


SyncBot: it has been suggested that more inboxes should #summary

https://www.flowdock.com/app/rulemotion/r-architecture/threads/EknivTWIqDh1YYD73oI7XhfgGQG
lekkas
@sqweelygig can we enable archiving of #summary threads in the Architecture Front inbox?
Hubot
sqweelygig is on leave today, returning to work tomorrow, the 11th
sqweelygig
I think this is a great example of why this reaction-within-a-service is a polluting stain upon the sync-between-services purpose of SyncBot, and is why I pushed back on implementing the feature in the scope of the existing bot.
At the moment SyncBot does not react to messages in Architecture, because they should not be synced to anywhere.
To implement this feature I'd want create a reaction-bot as either a procbot or a hubot.

With regards to #summary for architecture calls in particular, i think we're much better of not archiving the summarized threads. So unless this comes up for another inbox, I think we can close the issue.


RTL support

You're so good at what you do, But I wander if there's any plan to add more support to RTL languages and re-organize elements like side nav-bar and some  ?

This should already be supported


Persistent files (that have been removed from the repo) between build

I've setub a binder on https://github.com/rougier/numpy-100 and between two builds, I've removed some files from my repo but they still appear in the binder.
Not critical at all though but I wonder how they end up in the docker file.

Fixed in https://github.com/binder-project/binder-build/commit/c8be8151a86790bde2b881a6331fe098739c8ba6. Thanks for opening the issue @rougier!


Setting omnisharp.path to latest results in 404 error

Environment data
dotnet --info output:
.NET Core SDK (reflecting any global.json):
Version:   2.2.101
Commit:    236713b0b7
Runtime Environment:
OS Name:     Windows
OS Version:  6.1.7601
OS Platform: Windows
RID:         win7-x64
Base Path:   C:\Program Files\dotnet\sdk\2.2.101\
Host (useful for support):
Version: 2.2.0
Commit:  1249f08fed
.NET Core SDKs installed:
2.1.500 [C:\Program Files\dotnet\sdk]
2.2.100 [C:\Program Files\dotnet\sdk]
2.2.101 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
VS Code version: 1.30.2 (user)
C# Extension version: 1.17.1
Steps to reproduce
Added     "omnisharp.path": "latest" to my user settings file
Watched output window
Expected  behavior
Latest beta of omnisharp plugin to download and be installed in VS Code
Actual behavior
New version of omnisharp fails to download.
Output window reports as follows.
Error occured in loading omnisharp from omnisharp.path
Could not start the server due to Error: 404

I just tried "latest" and it works now.
Getting latest OmniSharp version information
Downloading package 'Latest OmniSharp Version Information' (1 KB).................... Done!
Installing OmniSharp Version = 1.32.11-beta.1...
Platform: win32, x86_64
Downloading package 'OmniSharp for Windows (.NET 4.6 / x64), Version = 1.32.11-beta.1' (30604 KB).................... Done!
Installing package 'OmniSharp for Windows (.NET 4.6 / x64), Version = 1.32.11-beta.1'
Finished
I will close this issue now

I have the same issue:
The following flashes by in the output window:

Getting latest OmniSharp version information
Downloading package 'Latest OmniSharp Version Information' (1 KB).................... Done!
Installing OmniSharp Version = 1.32.12-beta.51...
Platform: win32, x86_64
Downloading package 'OmniSharp for Windows (.NET 4.6 / x64), Version = 1.32.12-beta.51' Failed to download from https://roslynomnisharp.blob.core.windows.net/releases/1.32.12-beta.51/omnisharp-win-x64.zip. Error code '404')
Failed at stage: downloadAndInstallPackages
404

Followed by:

Error occured in loading omnisharp from omnisharp.path
Could not start the server due to Error: 404

vscode environment:

Version: 1.32.3 (user setup)
Commit: a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4
Date: 2019-03-14T23:43:35.476Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17134

I have the same issue:
Getting latest OmniSharp version information
Downloading package 'Latest OmniSharp Version Information' (1 KB).................... Done!
Installing OmniSharp Version = 1.32.12-beta.53...
Platform: win32, x86_64
Downloading package 'OmniSharp for Windows (.NET 4.6 / x64), Version = 1.32.12-beta.53' Failed to download from https://roslynomnisharp.blob.core.windows.net/releases/1.32.12-beta.53/omnisharp-win-x64.zip. Error code '404')
Failed at stage: downloadAndInstallPackages
404

I have the same problem , uninstalling VS2017 Ent fixed it. I suspect that OmniSharp is getting confused by different build versions across .NetCore 3.0 Preview and that installed by VS.;
C:\dev\src\scratch\NetCore\myApp>dotnet --info
.NET Core SDK (reflecting any global.json):
Version:   3.0.100-preview3-010431
Commit:    d72abce213
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.17763
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\
Host (useful for support):
Version: 3.0.0-preview3-27503-5
Commit:  3844df9537
.NET Core SDKs installed:
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.504 [C:\Program Files\dotnet\sdk]
3.0.100-preview3-010431 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0-preview3-19153-02 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0-preview3-27503-5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0-preview3-27504-2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

on my laptop, it say 1.32.12-beta.57
Getting latest OmniSharp version information
Downloading package 'Latest OmniSharp Version Information' (1 KB).................... Done!
Installing OmniSharp Version = 1.32.12-beta.57...
Platform: win32, x86_64

Downloading package 'OmniSharp for Windows (.NET 4.6 / x64), Version = 1.32.12-beta.57' Failed to download from https://roslynomnisharp.blob.core.windows.net/releases/1.32.12-beta.57/omnisharp-win-x64.zip. Error code '404')
Failed at stage: downloadAndInstallPackages
404

> dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview3-010431
 Commit:    d72abce213

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17763
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\

Host (useful for support):
  Version: 3.0.0-preview3-27503-5
  Commit:  3844df9537

.NET Core SDKs installed:
  3.0.100-preview3-010431 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview3-19153-02 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview3-27503-5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview3-27504-2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Environment data
dotnet --info output:
.NET Core SDK (reflecting any global.json):
Version: 2.2.101
Commit: 236713b0b7
Runtime Environment:
OS Name: Windows
OS Version: 6.1.7601
OS Platform: Windows
RID: win7-x64
Base Path: C:\Program Files\dotnet\sdk\2.2.101\
Host (useful for support):
Version: 2.2.0
Commit: 1249f08fed
.NET Core SDKs installed:
2.1.500 [C:\Program Files\dotnet\sdk]
2.2.100 [C:\Program Files\dotnet\sdk]
2.2.101 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
VS Code version: 1.30.2 (user)
C# Extension version: 1.17.1
Steps to reproduce
Added "omnisharp.path": "latest" to my user settings file
Watched output window
Expected behavior
Latest beta of omnisharp plugin to download and be installed in VS Code
Actual behavior
New version of omnisharp fails to download.
Output window reports as follows.
Error occured in loading omnisharp from omnisharp.path
Could not start the server due to Error: 404

I was getting this issue too. For now i have commented out //"omnisharp.path": "latest",
Hopefully theres a fix for this soon. i will enable it then.

i have same problem
https://github.com/OmniSharp/omnisharp-vscode/issues/2949


Itg3200 py

Python sample along with swig python pointer changes

Can you please do a quick rebase and squash these into a single commit?

Actually, I think it's better to keep them separated.

One of the commits has to do with fixing the Python bindings, the other is a new example.  For previous PRs like this (with a new example and also a fix for the bindings), we've been separating them into multiple commits.  Only when the entire sensor library is new have we been squashing commits into just one commit.

merged and closing


Update metrics docstrings.

#1478 Correcting the argument descriptions for metrics.
Let me know if there's any issues.

Real term as used in the litterature is "ground truth" and not "predicted", but I'm ok to update, if this looks more understandable. LGTM!


Clangd server path needs to be explicitly stated in the config

Hi,
It seems that the ServerPath config needs to be specifically filled in the config of this plugin, with the absolute path for the clangd binary.
This is the case, even if clangd is present in one of the $PATH directories, and executes just fine when typing clangd in the terminal, without having to type the full absolute path.
Would it be possible to have Lapce use Clangd from the path by leaving the config empty ?
Cheers !

It seems that the ServerPath config needs to be specifically filled in the config of this plugin, with the absolute path for the clangd binary.

Not correct. It can be relative or just binary name.

Would it be possible to have Lapce use Clangd from the path by leaving the config empty ?

I don't see any reason to do that.

Thx.
I might have missed something when I was testing just with the binary name, but it works indeed.
Closing this


Redeploy does not update commit id of deployment

Redeploy an app and the commit ID and selected commit shown in the UI are not refreshed.

@nwmac Couldn't reproduce this one. Can we have a bash together tomorrow?


Enhancement made for the Search Bar

Description
With this enhancement, the placeholder of the Search bar will not vanish on click/typing, rather it will shift itself above the search text, eventually giving a better user experience in the page.
Checklist

[x] I am making a proper pull request, not spam.
[x] I've checked the issue list before deciding what to submit.
[x] I've made the enhancement both for light as well as dark modes
[x] I ensured that the page remains responsive after the addition of the custom CSS

Related Issues or Pull Requests
#168
Add relevant screenshot or video (if any)

good but the current search bar ui looks better to me. so raise the pr in hacktoberfest branch, i'll merge your pr.

Sure, Thank you so much sir @wasimreja


Font size should have minimam and maximum bars

Font size grows way bigger for small text and goes too much little for longer texts. Font shouldn't grow after maximum size and shrink after minimum size.

The issue is mitigated now


[FEATURE] Add commit hook to avoid pushing keys

Description

https://github.com/pre-commit/pre-commit-hooks/blob/main/pre_commit_hooks/detect_private_key.py
Expected behavior with the suggested feature

Other Comments

This is now supported automatically by GitHub. Enabled in Settings, Code Security, Secret scanning
,


Added feature to control http body behavior

Added a flag to allow synchronous IO

I assume there is more to this PR than just this?

I was expecting a global flag on KestrelOptions, not a per request flag. Or do you plan to do both?

Both.

I assume there is more to this PR than just this?

This is just adding the feature. I don't plan to push all at once. Feature first, then Kestrel change once it goes in.

@Tratcher Is HttpSysServer going to the same global flag?
It would be pretty simple to disallow sync IO using some middleware to wrap the request and response body streams. The perf hit won't be too bad if the wrapping stream is pooled and lazily initialized. It would also ensure that a server switch doesn't suddenly cause a bunch of Read/Write calls to fail.

Still don't like the naming, but functionally it's fine.

@DamianEdwards do you have any naming suggestions?

IHttpBodyIOControlFeature
IHttpIOControlFeature
IHttpBodyIOFeature
IHttpBodySyncIOControlFeature
IHttpRequestResponseBodySynchronousIOControlFeature
IHttpIOIOIOItsOffToWorkWeGoFeature


ISPN-11001 Get config templates

https://issues.jboss.org/browse/ISPN-11001

@karesti I though you'd filter the templates out of /v2/cache-managers/{name}/cache-configs by having a parameter, like /v2/cache-managers/{name}/cache-configs?ignore-templates or something similar, but this PR instead created another method to bring only the templates?

@karesti hey, added a commit with suggested edit. hope that's ok. cheers!

@gustavonalle yes, I was thinking more on the cache-configs/templates like a filter instead a parameter.
I can change that if you want definetly

@oraNod thanks for the doc Don!

ok, I was confused with the purpose of the PR, but @karesti has clarified.

@gustavonalle I will ping you when the build is over for merge, thnaks!!

@gustavonalle you can merge, failures are unrelated

merged, thanks @karesti


Feat: Add iroh runtime wrapper and actually use thread per core

The exact place where we switch on a single threaded io runtime is TBD, but this at least seems to work...

/netsim

/netsim

Tbh this is about 2-3x slower than it used to be.
Also I don't think this works as intended. I might be reading things wrong so I'll dump some thoughts.

This seems all to be run from a single runtime with 2 worker threads. AFAIK this will limit your whole runtime to two threads and every spawn will just take a share of those two.
Spawning per connection might or might not be good overall. I think it's a good strategy to have N threads and then spawn tasks within those but will probably need more finesse than just doing a spawn.
I don't see that we do any SO_REUSEPORT. Without it (and this goes also for all platforms which don't support load balancing across the reused port) what happens is that the last bind to be executed takes all the traffic (or the first depending on the platform restrictions) but either way, you basically end up with a single threaded runtime, rest is just idling. (this only works on Linux kernels 3.something+ afaik, and otherwise you need to do you own multiplexer on top of the port and load balance internally - not too bad but is ugly code)
Here https://github.com/n0-computer/beetle/pull/312/files is a very dirty example of some of the tests I've ran where each of these is actually a fully separate run time (which worked better for the tests I've run than just threads in a single runtime)

Another note, once we get to ~same level of perf we had, I think 1 to 1 might still cap out at some point but 1 to N to start improving.

Tbh this is about 2-3x slower than it used to be. Also I don't think this works as intended. I might be reading things wrong so I'll dump some thoughts.

This seems all to be run from a single runtime with 2 worker threads. AFAIK this will limit your whole runtime to two threads and every spawn will just take a share of those two.
Spawning per connection might or might not be good overall. I think it's a good strategy to have N threads and then spawn tasks within those but will probably need more finesse than just doing a spawn.
I don't see that we do any SO_REUSEPORT. Without it (and this goes also for all platforms which don't support load balancing across the reused port) what happens is that the last bind to be executed takes all the traffic (or the first depending on the platform restrictions) but either way, you basically end up with a single threaded runtime, rest is just idling. (this only works on Linux kernels 3.something+ afaik, and otherwise you need to do you own multiplexer on top of the port and load balance internally - not too bad but is ugly code)
Here https://github.com/n0-computer/beetle/pull/312/files is a very dirty example of some of the tests I've ran where each of these is actually a fully separate run time (which worked better for the tests I've run than just threads in a single runtime)

Are you sure? I did some manual checks by running the new cli_provide_one_file_large test and looking at the time, and it was identical to x-hp. Or did you mean main?
So, the way this works is that there is a main runtime, which runs accept as well as all the various tasks and timers of the hole punching. Then, once you have a stream pair you move to one of the thread per core runtimes to do the actual IO (reading from the file system and writing to the socket in this case).
Here is where this happens:
            rt.spawn_tpc(|| {
                async move {
                    let _x = NonSend::new(); // this is just to make the future non send, it does nothing
                    if let Err(err) = handle_stream(db, reader, writer, custom_get_handler).await {
                        warn!("error: {err:#?}",);
                    }
                }
                .instrument(span)
            })

Yes, I am aware that this is not fully thread per core since the accept part is still done on a multi threaded tokio runtime. To do real thread per core you would have to basically have an entire quinn endpoint per core. But while that might have worked before we did the hp stuff, now it would be really a can of worms because all the complexity of the magicsocket would have to be duplicated per core.

Right, I was comparing to main!
Yeah tpc is messy if you want to convert and dont start out with that architecture.
Thx for the overview, this might actually be a good approach to get accept/load balancing from a single port easily.
Think there still is benefit to having dedicated threads as eventually we might want to do 2 threads for hairpinning, one for disk io 5 for network etc. This is mostly dumbspeak without backup at this point, but still think it's a valid observation long term.
I'll try to do some more testing on this over the next few days just to get a better feel on the behavior & perf.

Right, I was comparing to main! Yeah tpc is messy if you want to convert and dont start out with that architecture. Thx for the overview, this might actually be a good approach to get accept/load balancing from a single port easily. Think there still is benefit to having dedicated threads as eventually we might want to do 2 threads for hairpinning, one for disk io 5 for network etc. This is mostly dumbspeak without backup at this point, but still think it's a valid observation long term. I'll try to do some more testing on this over the next few days just to get a better feel on the behavior & perf.

Thanks. I would really like to know if this is at least roughly on par with what we had before in x-hp. If yes I would like to merge this since it opens up the API design space a lot because now we have a way to spawn non send futures.
Whatever happens with the exact architecture later, this is essential since a lot of high perf storage impls just don't do Send...


Style inheritance not allowing overrides.

I've started styling my Core components and everything was perfect until I started to Extend them.
The extended component inherits all the core styles BUT with a priority, so I am not able to override them. This is a fundamental issue and a total blocker when you have a component composition and inheritance which we have in any React project nowadays.
Broken example is provided here: https://codesandbox.io/s/k5oLQ4YZY
My expectation is the MenuIcon to be a lot bigger, nothing happens.
If I move the <Icon /> component 1 line above, so it is rendered before the <MenuIcon /> - it works but I do not want the Icon at all on this page - that makes it break.
If I implement the same example with only styled-components it works, so the issue comes from Styletron implementation for sure.

I have a suspicion that the way you parse the styles could be wrong if you are traversing through all the components in the order they are declared. Then the issue will be present for sure because a Core component will be seen after it's derived components and the core styles will be defined after the ones you want to prioritize. So this would not be easy to fix though. All the parsing logic needs to be reworked I guess.

Hey Shent,
From your example, you have this:
const GenericIcon = styled('div', {
  width: '1em',
  height: '1em',
  border: '1px solid blue',
  color: 'red'
})

class Icon extends Component {
  render() {
    return (
    	<GenericIcon className={this.props.className}>Icon</GenericIcon>
    )
  }
}

const MenuIcon = styled(Icon, {
  width: '150px',
  height: '150px'
});

For composition of styled elements, you need to pass in another styled element. So you would need to do something like this instead:
const GenericIcon = styled('div', {
  width: '1em',
  height: '1em',
  border: '1px solid blue',
  color: 'red'
})

const MenuIcon = styled(GenericIcon, {
  width: '150px',
  height: '150px'
});

Hello Ryan -
I think you did not the idea of the issue I was having there.
If I am using Pure Functions as Input it is all fine, I got that.
The problem is I have no pure functions in my project due to its specificity but Components that have functions I need to extend.
As in the example, I have a GenericIcon that has certain functions and I have to extend from it to make MenuIcon, SocialIcon, FooterIcon etc.
Is there any way to accomplish this with Styletron or I should simply stick with StyledComponents because the concept works there, although the outputted CSS will be 30 times bigger?

It seems to me that maybe your stateful class components should take your stateless, single-element styled components as props.

Thanks for the feedback!
However, if anyone is struggling with it this is how I've solved it on my end while discussing it here in styletron.
Implementation with Styled-Components instead:
#skin.js
import styled from 'styled-components';
export default getSkin => target => styled(target)`${props => getSkin(props)}`;

Usage:
#YourReduxContainer.js
import skin from './skin';
import {plainTheme as theme} from './themes';
...
export default connect(
    mapStateToProps,
    mapDispatchToProps
)(
    skin(theme)(YourContainer) || YourContainer
);

Or even without Redux:
#YourContainer.js
skin(theme)(YourComponent);

If somehow we could change the Styletron implementation of the styled() method to act like in Styled-Components - would be awesome.
I will try to figure out what and how to help on this one.
Cheers

Composition is much more flexible in v4, I think this is resolved in https://github.com/rtsao/styletron/pull/217 https://github.com/rtsao/styletron/issues/215


MSDKUI-2301: Update examples

Signed-off-by: Krzysztof Hubaczek<EMAIL_ADDRESS>

Codecov Report

Merging #182 into master will decrease coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #182      +/-   ##
==========================================
- Coverage   87.41%   87.27%   -0.14%
==========================================
  Files          89       59      -30
  Lines        5155     3199    -1956
==========================================
- Hits         4506     2792    -1714
+ Misses        649      407     -242

Flag
Coverage Δ

#ios
87.27% <ø> (-0.14%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

MSDKUI_Demo/GuidanceDashboardTableViewCell.swift

MSDKUI_Demo/AppDelegate.swift

MSDKUI_Demo/OptionsViewController.swift

MSDKUI_Demo/IconButton.swift

MSDKUI_Demo/GuidanceViewController.swift

MSDKUI_Demo/WaypointViewController.swift

MSDKUI_Demo/RouteOverviewViewController.swift

MSDKUI_Demo/ExtensionNMAGeocoder.swift

MSDKUI_Demo/RouteViewController.swift

MSDKUI_Demo/OptionPanelViewController.swift

... and 20 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7507a51...cc4635b. Read the comment docs.


improve mopidy

connect to inotify to get notifications about new songs (wanted? can always turn off...)
start automatically as systemd service (should start after desktop-manager.service and after acquiring internet connection, however those are performed)

i've had lots of issues getting this to work and honestly spotify serves my purposes just fine most of the time. i'll reopen this if i end up actually needing this, but i think starting mopidy manually rather than automatically on boot is for the best anyways #


Updating Images

What does this PR do? Please provide some context
Updated images which now supports IE Browser as well.
Where should the reviewer start?
Open /faq page in IE Browser and you can see the updated images.
How can this be manually tested? (brief repro steps and corpnet-URL with change)
Open /faq page in IE Browser and you can see the updated images.
What are the relevant TFS items? (list id numbers)
Definition of done:

[x] Title of the pull request is clear and informative
[ ] Add pull request hyperlink to relevant TFS items
[ ] For large or complex change: schedule an in-person review session
[x] This change has appropriate test coverage
[x] Get at least two approvals

Reminders DURING merge

If you're merging from a short-term (feature) branch into a long-term branch (like dev, release, or master) then "Squash and merge" to keep our history clean.
If merging from two longterm branches (like cherry picks from upstream, dev to release, etc) then "Create merge commit" to preserve individual commits.

I just cropped the old image and saved it as .png format and it worked. May be some issue with the old image.


fix: support repo urls without git terminator

Addresses https://github.com/relekang/python-semantic-release/issues/109#issuecomment-531053386

Thanks 👍


Investigate why Playground2 and PassiveSTSSampleApp web apps not getting deployed

Description:
Playground2 and PassiveSTSSampleApp web apps are not deploying in tomcat when running IS scenario tests in TestGrid prod. There are many test-case failures due to this issue. We need to investigate why those apps are not getting deployed. According to the QA-Tomcat instance tomcat logs, travelocity & avis webapps are successfully deployed. But there is no sign of a failure for Playground2 and PassiveSTSSampleApp web apps.
Affected Product Version:
0.9.0-m26

@charithag , @kasunbg , @harshanL
Tried to upload playground app from local machine to the instance where tomcat is deployed using a curl command similar to identity-test-integration scripts, but it is failing due to connection timeout.
With recent security improvement in tomcat instance, I think the curl has to be updated as to use the relevant certificate with it.
Will check further.

Hi all,
The above suspect was wrong and I was able to do Curl from both localhost and TestGrid Home instance successfully to QA-Tomcat instance and deploy playground2 app.
Then from TestGrid Prod, I've triggered a build for WSO2 IS 5.4.1 - LTS and observed the log relates to a scenario where playground2 app is supposed to be deployed.
The log reveals that it is being successfully deployed.
Please refer the log:
(basesetup.log of scenario01/jmeter))
 [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ playground2 ---
[INFO] Installing /testgrid/testgrid-home/jobs/wso2is-5.4.1-LTS/workspace/identity-test-integration/scenario01/temp/playground2/target/playground2.war to /home/ubuntu/.m2/repository/org/wso2/is/playground2/5.5.0/playground2-5.5.0.war
[INFO] Installing /testgrid/testgrid-home/jobs/wso2is-5.4.1-LTS/workspace/identity-test-integration/scenario01/temp/playground2/pom.xml to /home/ubuntu/.m2/repository/org/wso2/is/playground2/5.5.0/playground2-5.5.0.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.739 s
[INFO] Finished at: 2018-05-31T10:09:26+00:00
[INFO] Final Memory: 38M/545M
[INFO] ------------------------------------------------------------------------
OK - Deployed application at context path /playground2
OK - Deployed application at context path /travelocity.com

Please refer the JenkinsLog = https://testgrid-live.private.wso2.com/admin/job/wso2is-5.4.1-LTS/32/console
Search term:  playground2 and you will find logs of successfully undeployment of the app as
OK - Undeployed application at context path /playground2
(log about deployment is not included in jenkins log, but it is in basesetup.log in above)
However one previous build of the same job had mentioned that playground2 app is Fail at undeployment.
https://testgrid-live.private.wso2.com/admin/job/wso2is-5.4.1-LTS/31/consoleFull
[main] INFO org.wso2.testgrid.common.util.TestGridUtil - Execution result : working directory : /testgrid/testgrid-home/jobs/wso2is-5.4.1-LTS/workspace/identity-test-integration/scenario01/jmeter
OK - Undeployed application at context path /travelocity.com
FAIL - No context exists named /playground2
post-steps are done...

Since the issue is not observable with the latest builds, we can close the issue.

You can also refer the TestGrid dashboard link : https://testgrid-live.private.wso2.com/wso2is-5.4.1-LTS/is-single-node-deployment/test-plans/1bc2571e-72be-42c2-bd7e-c465233924e2#Single Sign On between a legacy web app, which cannot change the user interface and service providers, which support standard SSO protocols

The passing 2 scenarios (scenario01 and scenario22) are using Playground2 apps and which means the app is successfully deploying.

As per above comments close the issue.


Unexpected RPC error, error: Transport("Unexpected response status code: 502 Bad Gateway"), component: BlockStream

I have deployed pancakeswap subgraph. but syncing is failed.

Please help me and solve this problem.
Thanks.

This is an issue with our BSC provider; we are working with them to get it resolved, but it might take a little longer before that is available.

What is the status of this issue?
I'm getting the same issue and just want to know when it gets fixed, or are there any workaround?

This is an issue with our BSC provider; we are working with them to get it resolved, but it might take a little longer before that is available.

I'm the same here, I'm facing this error right now.


Need to get the keyboard back in detox after it hides in ios

Hi, I have a problem typing the text fields in detox. where I hide the keyboard in the first field and then in the 2nd field keyboard is not appearing. could you please help me with this?
I have used functions like  this
static async addContentFandomEnter() {
await newPostPage.lbl_title.atIndex(0).typeText('\n');     //keyboard hides after the 1st filed
}
static async addContentFandom() {
await newPostPage.lbl_content.atIndex(0).tap();
const {fandom_handle: fandom_handle} = getCredentials();
await newPostPage.lbl_content.atIndex(0).replaceText(fandom_handle);
Log =========
Test Failed: First responder “(null)” does not conform to “UITextInput” protocol

  29 |     await newPostPage.lbl_content.atIndex(0).tap();
  30 |     const { handle: handle } = getCredentials();
> 31 |     await newPostPage.lbl_content.atIndex(0).replaceText(handle);
     |                                              ^
  32 |   }
  33 |   static async addContentFandomEnter() {
  34 |     await newPostPage.lbl_title.atIndex(0).typeText('\n');

  at Function.<anonymous> (../pages/new-post.page.ts:31:46)
  at fulfilled (../../../node_modules/tslib/tslib.js:112:62)

closed


Multi-Region Failover Module

Adding another module demonstrating multi-region serverless failover. This module will be used for SRV-331 Workshop at Re:Invent 2017.

Requesting review and squash merge


关于支付宝的 0 元支出记录

想问下 0 元的记录是不是没啥意义，可以直接忽略吗？
例子：
2022-09-02 * "哈啰出行" "哈啰单车骑行"
	category: "交通出行"
	merchantId: "CPR220902160932501179xxxxD"
	method: "单车骑行卡抵扣"
	orderId: "202209022200149456144204xxxx"
	payTime: "2022-09-02 16:09:32 +0800 CST"
	source: "支付宝"
	status: "交易成功"
	txType: "支出"
	Expenses:Unknown 0.00 CNY
	Assets:FIXME -0.00 CNY

Personally, I prefer keeping the record since it is also an event that happened.

You can think your ledger as a journal.

Ok, that sounds like it. I'll add a rule for it.


missing auth retry in _retry_request

I just hit the following error out of the blue
  File "/Users/amohr/dev/Operations2/google-services/google_utils.py", line 109, in __next__
    response = self._request.execute(num_retries=NUM_RETRIES)
  File "/Users/amohr/.pyenv/versions/3.6.4/lib/python3.6/site-packages/oauth2client/util.py", line 137, in positional_wrapper
    return wrapped(*args, **kwargs)
  File "/Users/amohr/dev/thehesiod/google-api-python-client/googleapiclient/http.py", line 843, in execute
    method=str(self.method), body=self.body, headers=self.headers)
  File "/Users/amohr/dev/thehesiod/google-api-python-client/googleapiclient/http.py", line 170, in _retry_request
    resp, content = http.request(uri, method, *args, **kwargs)
  File "/Users/amohr/.pyenv/versions/3.6.4/lib/python3.6/site-packages/oauth2client/transport.py", line 153, in new_request
    credentials._refresh(orig_request_method)
  File "/Users/amohr/.pyenv/versions/3.6.4/lib/python3.6/site-packages/oauth2client/client.py", line 765, in _refresh
    self._do_refresh_request(http_request)
  File "/Users/amohr/.pyenv/versions/3.6.4/lib/python3.6/site-packages/oauth2client/client.py", line 834, in _do_refresh_request
    raise HttpAccessTokenRefreshError(error_msg, status=resp.status)

with valid credentials, so it seems like a google backend auth issue.  This brought to light that retries for auth errors are missing
simple fix is adding to the exception cases:
    except AUTH_RETRY_EXCEPTIONS as auth_error:
      exception = auth_error

Hrm, so oauth2client already retries (and refreshing the token) requests when auth fails. This error happens when it can't refresh the token when retrying and we can't safely retry this - in the failure case we'd end up with infinitely retrying.
This is working as intended, although I'm curious if this same issue appears when using google-auth?

well the next retry it worked so obviously it can in fact retry it.  I don't see how you'd get infinite retries when there's a fixed number of retries.  Further, nowhere in that stack does it try to do a retry on this  particular exception.

That's because this exception is raised by a part of the stack that is in the process of retrying.

it's not retrying, its refreshing and expired token

sorry, missed that impl where it's retrying as well, which means something very strange is going on

actually, I don't see "sleep" happening in the logs so I bet _should_retry_response is causing it to not retry

hah, indeed the check in _should_retry_response will only retry 'userRateLimitExceeded' and 'rateLimitExceeded' reasons for the error, which doesn't cover token refresh


Can't use with NPM because there is no package.json

I'm trying to move my project completely from bower to npm, and because this repo doesn't have a package.json with name and version fields, npm fails to install it. I would much rather not fork the project just to put a package.json in, so it would be nice to have that.

NPM has another purpose. It is a nodejs package manager. This means, that each package should contain only js code to use in nodejs apps. And this is not applicable for fonts and stylesheets.

@achugaev93 There's also a discussion in #7 . Thank you for your contribution ;)

#7 was also closed. Thank you, @lastmjs and @achugaev93 , for your contribution.

#7 was reopened

Closed by #7


Space after comma in object expression while retaining bracket white space

I'd like to have this:
var x = {key: 123,more: 456}

turn into this
var x = {key: 123, more: 456}
                  ^
__________________|

But also keep the existing white space for the opening/closing brackets, so this would also be untouched when formatted:
var g = { name: f, data: fs.readFileSync(f).toString() }

Is there any way to force white space after the comma between properties?

@Flet you should take a look to https://github.com/wbinnssmith/esformatter-collapse-objects A PR is open to let/remove the whitespace after & before the braces https://github.com/wbinnssmith/esformatter-collapse-objects/issues/1

the space after the comma is handled by whiteSpace.before.Property = 1 or whiteSpace.before.PropertyName = 1. the space before the comma is handled by whiteSpace.after.PropertyValue = 0 or whiteSpace.after.Property = 0  (PropertyName and PropertyValue overrides the global Property setting since they are more specific)
to really leave the {} untouched is tricky since the after.Property(Value) and before.Property(Name) will conflict with after.ObjectExpressionOpeningBrace = -1 and before.ObjectExpressionClosingBrace = -1... you probably need to keep it consistent and set the value to 1.
I'll submit a pull request to esformatter-collapse-objects soon with the changes required to follow the default esformatter settings.

Thanks @millermedeiros
I'm not exactly looking to collapse object literals, I just want a space after the commas without affecting the braces :)

@Flet I guess that we would need a new setting (maybe ObjectExpressionComma to match ArrayExpressionComma) and set Property, PropertyValue and PropertyName to -1... but there are always ways to introduce conflicts (if last property is an Array and you have after.ArrayExpressionClosing = 1 it won't work as you expect since ArrayExpressionClosing will limit the amount of spaces)
we can't deprecate the Property[Name|Value] because there are probably a lot of people using these settings.. If we add the ObjectExpressionComma I would need to submit another PR for the esformatter-collapse-objects...
I think we will have to live with the current logic, if you always want to have 1 space inside {} set it to 1, if you always want to remove the spaces set it to 0.
it's really hard to make a formatter that keeps the original formatting.

going to ignore this since there isn't a clear way to solve the problem without causing conflicts.

Thanks, makse sense to do this.


Added host header injection vulnerability module

The current version of the nettacker lacks with host header injection search. This module will try to detect host header injections vulnerabilities.

Checklist

[X] I have followed the Contributor Guidelines.
[X] I have added the relevant documentation.
[X] My branch is up-to-date with the upstream master branch.

Changes proposed in this pull request

[X] Added the host header injection vulnerability module: The module will try to find: host, x-forwarded-for, x-forwarded-host header injection.
[X] Tested on the localhost with PHP code for host header injections.
[X] Uses useargents from lib/payload/wordlist library.

Your development environment

OS: Linux
OS Version: Ubuntu 18.04
Python Version: 3.6.9

this can't be supported anymore. modules are yaml #440


[Bug Report] ... reshape does not work with bfloat8_b

Describe the bug
reshape does not work with bfloat8_b

Resolved in #15747 PR


Enhance background-styles of UI

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Styles.css added to Login and register page


Take ownership of pins instead of mutable borrows

The use of &mut ref for gpio and clk pins makes it difficult to use this crate in any way other than creating pin instances as local variables in main (as you show in your example code).
I want to hold pins and tm1637 in a struct, using the struct impl to create the pins and instantiate the tm1637 instead of doing it in main. Because you have mutable refs for the pins, it is difficult to do this. I've tried various ugly ways to do this without success (There may be a way, but I haven't found it). I'm now thinking of rewriting your code to take ownership of the pins
Is there a reason why you have used &mut for the clk and dio pins, rather than taking ownership?

Well, there's actually no much reason at all, coz, this is just one of my first tries to use Rust)
To be honest I researched over the Internet but didn't happen to figure out how "take ownership" would be better than the current approach. So, it would be great if you outline your idea in code (a draft).
Anyway, you're welcome to open a PR.

Well, I must apologize. I didn't understand the issue properly. Please feel free to close it.
I forked your repository, and changed the tm1637 code to use moves for clk and dio.  But when I came to use it, I had the same problem in creating clk and dio, behind mutable references. all that did is highlight that the hal uses mutable borrows for pins.  So it didn't solve the issue.
I'll have to work out another way to get what I want.

Yeah, HAL needs mutable refs.
When you'll figure out a more convenient way to use the code, please, lemme know.


add ref to version parameter from each swagger operation

@tedchamb,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Requirements and minimum hold for drops

auto-teleport and confirm modal
for some reason, our confirmation dialog for paid mint is gone

in this dialog/modal, there was also an option to auto-teleport

since we operate on an asset hub, it's important to have the option to teleport as most of the users that come don't have funds there

probably without the orange box

Required balance

if the required balance = mint price, we don't have to show it as a requirement - the user does not get to the modal where we can teleport, and its confusing
i think we agreed internally that having an additional balance requirement on top is not super useful as it's hard to explain.

:wave:

helo sir @pbkompasz, do you have any eta for the pr? Its a important feature for our drops

👋


Invalid read in fmtstr() with precision and non-terminated string

In BIO_snprintf, fmtstr() calls strlen(value) unconditionally.
If the value string is non-terminated, this will read further in the array than the caller expected. This could affect padding in the output, or even result in crashes.
The attached example shows how padding can be affected by this bug. The two output lines are expected to be the same.
bad-BIO_snprintf.c.txt
.

It's a C string and must be NUL-terminated.

Even if it's terminated (like the example) you can get incorrect results.

I just ran the test program, and yeah, the result isn't correct.

PR #1104 contains a fix, please try it out.

#1104 has now made it to master.  This issue considered fixed, I'm closing it.


Design Spring Security integration

We need to figure out in what way we are going to support Spring security out of the box.

@peholmst is this still active in relation to the progress of integration of Spring-Security ?

Nah, I think we can close it. From now on, we'll create more fine grained tickets for specific security features.


unable to scan row for SHOW ORGANIZATION ACCOUNTS

Provider Version
provider registry.terraform.io/snowflake-labs/snowflake v0.56.0
Terraform Version
Terraform v1.3.6
Describe the bug
terraform plan crashes with this error:
│ Error: error reading account: unable to scan row for SHOW ORGANIZATION ACCOUNTS LIKE 'ABC12345' err = missing destination name is_org_admin in *[]snowflake.Account
│
│   with module.snowflake_accounts.snowflake_account.account["SOMEACCOUNT"],
│   on ../../modules/aws/snowflake_accounts/main.tf line 28, in resource "snowflake_account" "account":
│   28: resource "snowflake_account" "account" {

Expected behavior
No error message.
Code samples and commands
  accounts = [
    "SOMEACCOUNT",
    "SOMEOTHERACCOUNT",
  ]

resource "snowflake_account" "account" {
  for_each             = toset(var.accounts)
  provider             = snowflake.orgadmin
  admin_name           = "AUTOMATION"
  admin_rsa_public_key = replace(trimprefix(trimsuffix(data.tls_public_key.public_key.public_key_pem, "-----END RSA PRIVATE KEY-----\n"), "-----BEGIN RSA PRIVATE KEY-----\n"), "\n", "")
  comment              = "SNOWFLAKE"
  edition              = "BUSINESS_CRITICAL"
  email                =<EMAIL_ADDRESS>  first_name           = "First"
  last_name            = "Last"
  name                 = upper(each.value)
  region               = "AWS_US_EAST_1"

  lifecycle {
    ignore_changes = [
      comment
    ]
  }
}

Additional context
Note that when I run the same query as described in the error message (SHOW ORGANIZATION ACCOUNTS LIKE 'ABC12345') in the Snowflake console, it returns the expected results (1 row). And the is_org_admin column evaluates to false.
And this Terraform code has been working fine for us for many months, this seemingly just broke randomly.

I am having the same problem.
Came in this morning to add some more roles to an existing account and ran into the same issue.
Terraform version:
1.3.9 and 1.1.9
Providers:
0.56.4 and 0.58.0

Same issue started today for me after the code has been working for weeks.  Error is:
Error: error reading account: unable to scan row for SHOW ORGANIZATION ACCOUNTS LIKE 'ACCT1234' err = missing destination name is_org_admin in *[]snowflake.Account
Terraform: v1.2.1
Provider versions:  0.56.3 and 0.58.0

I've opened a support case with Snowflake and pointed them at this issue for some extra context.

I just noticed that according to QUERY_HISTORY_BY_USER in Snowflake the "SHOW ORGANIZATION ACCOUNTS..." statement was working until this morning.  I also noticed that according to QUERY_HISTORY_BY_USER the RELEASE_VERSION went from 7.6.4 to 7.7.4 between the time the query worked and now when it does not.
I will open a ticket with Snowflake support as well.

Per this link, this issue was introduced in the 2023_01 bundle:  SHOW-ORGANIZATION-ACCOUNTS-New-Column-in-Output
Snowflake support gave us this as a temporary workaround until a fix for the provider can be made:
SELECT SYSTEM$DISABLE_BEHAVIOR_CHANGE_BUNDLE('2023_01');

Hitting this same issue. I suspect the fix is adding
	IsOrgAdmin                        sql.NullString `db:"is_org_admin"`

to this account struct: https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/d62b1b4d6352e7d2dc99e4603370a1f3de3a4624/pkg/snowflake/account.go#L179

Hi everyone, as you suspected this bug was introduced by the addition of the is_org_admin column in SHOW ORGANIZATION ACCOUNTS in this month's behavior change release of Snowflake. The fix is in main and will be available in the next release of the provider.
We're looking at ways to detect these API changes earlier internally so we can keep the provider up to date with the future Snowflake releases and prevent this type of issues in the future.


Issue 274: Add continuous benchmark structure

This PR closes #274.
It adds infrastructure for benchmarking using BenchmarkTools, BenchmarkCI, and PkgBenchmark. I have also added proposed structure for future benchmarks but this is not set in stone. When I originally looked at this I kind of wanted to integrate this with TestItemRunner (and so use out test suite for benchmarks) but I couldn't work out how to do this and also potentially it is better to have more targetted benchmarks?
The action CI for this should:

Run on all PRs
Cancel currently running benchmarks
Run benchmarks on the PR code and on main
Post a comment comparing these two sets of benchmarks.
It only runs on Ubuntu on the latest Julia version. BenchmarkCI doesn't appear to support a build matrix hence this decision (plus saving compute). This means we won't catch platform-specific performance regressions.

This could potentially get a bit noisy/slow so may need to watch how this is working out and go from there.
This can be tested locally in the benchmark environment using:
using PkgBenchmark
benchmarkpkg(Rtwithoutrenewal)

You should also be able to use BenchmarkCI locally to compare commits but I haven't tested this.

[!NOTE]
This PR does not add an actual benchmark suite. I don't really have a great handle on BenchmarkTools yet and I think this should probably be done in a few issues once we have an idea of the sorts things we want to benchmark (to discuss here). Initially I would propose doing an issue per submodule and benchmarking each generative model + a few combinations and then also have a few integrated models that we benchmark in more detail (in another module/issue?).

This looks a really good move.

This now works i think but needs testing from main. As it doesn't touch any other code going to merge based on previous partial review