Cannot POST /invoicing/createStripeInvoices

Hi Team, i got the below error when issueing a curl command to test the deployment with stripe integration. Please advise what is missing. Thanks, Ferry
ferrymul@909c4acf1983 cron-job % kubectl --namespace=default run curl --image=curlimages/curl -i --tty -- sh
If you don't see a command prompt, try pressing enter.
~ $ curl -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices' \

--header 'Content-Type: application/json'
--data-raw '{
"month": "11",
"year": "2024"
}'

Error

Cannot POST /invoicing/createStripeInvoices

~ $

Hi @ferrymul7 - we will need the pod logs from your deployed application to troubleshoot this. Please attach them here.

@jmsrpp , i got 2 pods, curl pods give this log:
~ $  ~ $  ~ $ curl -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "month":"11", "year":"2024" }'

Error

Cannot POST /invoicing/createStripeInvoices

the other btp-invoicing-srv-7c48d874f7-4fr59 pod, doesn't have any logs generated.
Please advise.

hi @jmsrpp , I deleted the pod and recreating them in trial using command "npm run build-deploy:kyma --image_name=ferrymul/btp-invoicing --namespace=trial" with success build and deploy

<EMAIL_ADDRESS>deploy:kyma
cross-var helm upgrade --install btp-invoicing ./chart --namespace=$npm_config_namespace

Release "btp-invoicing" does not exist. Installing it now.
NAME: btp-invoicing
LAST DEPLOYED: Tue Nov 19 10:20:01 2024
NAMESPACE: trial
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Thank you for installing btp-invoicing version 1.0.0.
The release "btp-invoicing" is installed in namespace "trial".
Your services are available at:

https://btp-invoicing-srv-trial.

Now i see the following problems in the pod events. The pod status is "ContainerCreating"
Successfully assigned trial/btp-invoicing-srv-7c48d874f7-xlfz7 to ip-10-250-1-13.ec2.internal
MountVolume.SetUp failed for volume "auth-secret" : secret "btp-invoicing-srv-auth" not found
MountVolume.SetUp failed for volume "destinations-secret" : secret "btp-invoicing-srv-destinations" not found
Please advise.

The secrets should be mounted from the helm chart. Please double check that the helm matches what we have in the repo, aside from the version changes we implemented earlier in this issue.

@jmsrpp , i re-clone the stripe branch and re-run all the fixes to make the build phase successful, but still have the same problem. Can you help to point out which files within helm chart that need to be fixed ? Thank you.

Hi @ferrymul7 - sorry you're encountering all these issues.
this values.yaml has the service entries. It should result in xsuaa and destination service being created in your namespace. Please confirm.
the binding is defined here
If this still fails, you can try to recreate the helm chart using cds add helm which should pick up the bindings from the package.json
Also adding my colleague, @kay-schmitteckert in case he has any idea?

@jmsrpp , i realized now that the secrets are always deployed in default namespace. I tried with trial namespace, it always fails as above.
Anyway, i have now successfully deployed to default namespace, and below are the POD logs
******* btp-invoicing-srv-7c48d874f7-lw7q5 pod
{"level":"info","logger":"cds","timestamp":"2024-11-24T22:55:08.949Z","msg":"loaded model from 1 file(s):\n","type":"log"}
srv/csn.json
{"level":"info","logger":"cds","timestamp":"2024-11-24T22:55:15.188Z","msg":"using auth strategy {\n kind: 'xsuaa',\n impl: '../layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/auth/jwt-auth'\n} \n","type":"log"}
{"level":"info","logger":"cds","timestamp":"2024-11-24T22:55:19.786Z","msg":"serving InvoicingService { impl: 'srv/invoicing-service.js', path: '/odata/v4/invoicing' }","type":"log"}
{"level":"info","logger":"cds","timestamp":"2024-11-24T22:55:19.788Z","msg":"server listening on { url: 'http://localhost:8080' }","type":"log"}
[cds] - launched at 11/24/2024, 10:55:05 PM, version: 7.9.5, in: 14.044s
******* curl pod
~ $  ~ $  ~ $ curl -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "1
1", "year": "2024" }'

Error

Cannot POST /invoicing/createStripeInvoices()

I tried with the followings, but no luck:
curl -X POST 'btp-invoicing-srv:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
curl -X POST 'localhost:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
curl -X POST 'http://btp-invoicing-srv.default:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
curl -X POST 'http://btp-invoicing-srv.:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
curl -X POST 'http://localhost:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
Please advise.

@kay-schmitteckert , Tried that and it still the same error. The problem here is that there is no log, and the error messages is unhelpful to point out what is the problem.
~ $ curl -X POST 'btp-invoicing-srv:8080/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year"
: "2024" }'

Error

Cannot POST /invoicing/createStripeInvoices

The error message isn’t helpful because it’s never making it to the Pod. CURL is succinctly telling us it cannot resolve the hostname you’re trying. It means you need to try some basic DNS, ping, etc. Check this stack thread for a similar problem. They do some lookups, use a verbose option when running CURL, and so on. Unable to use curl and service name from inside kubernetes podstackoverflow.comJim @.*** Nov 25, 2024, at 12:20 AM, Ferry Mulyadi @.***> wrote:
@kay-schmitteckert , Tried that and it still the same error. The problem here is that there is no log, and the error messages is unhelpful to point out what is the problem.
~ $ curl -X POST 'btp-invoicing-srv:8080/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year"
: "2024" }'
Error
Cannot POST /invoicing/createStripeInvoices
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@jmsrpp , i added -v in curl, and i see the following. It seems that it can connect, however it returns HTTP 404. i saw the build & deploy was successfully executed. Is there anything missing here ?
~ $ curl -v -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month":
"11", "year": "2024" }'
Note: Unnecessary use of -X or --request, POST is already inferred.

Host btp-invoicing-srv.default:8080 was resolved.
IPv6: (none)
IPv4: <IP_ADDRESS>
Trying <IP_ADDRESS>:8080...
Connected to btp-invoicing-srv.default (<IP_ADDRESS>) port 8080
using HTTP/1.x

POST /invoicing/createStripeInvoices() HTTP/1.1
Host: btp-invoicing-srv.default:8080
User-Agent: curl/8.11.0
Accept: /
Content-Type: application/json
Content-Length: 33

upload completely sent off: 33 bytes
< HTTP/1.1 404 Not Found
< X-Powered-By: Express
< Content-Security-Policy: default-src 'none'
< X-Content-Type-Options: nosniff
< Content-Type: text/html; charset=utf-8
< Content-Length: 172
< Date: Mon, 25 Nov 2024 18:22:16 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
<

Error

Cannot POST /invoicing/createStripeInvoices()

* Connection #0 to host btp-invoicing-srv.default left intact

It’s an action (not a function) so please remove the () from the URL and try again. Jim @.*** Nov 25, 2024, at 11:27 AM, Ferry Mulyadi @.***> wrote:
@jmsrpp , i added -v in curl, and i see the following. It seems that it can connect, however it returns HTTP 404. i saw the build & deploy was successfully executed. Is there anything missing here ?
~ $ curl -v -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices()' --header 'Content-Type: application/json' --data-raw '{ "month":
"11", "year": "2024" }'
Note: Unnecessary use of -X or --request, POST is already inferred.
Host btp-invoicing-srv.default:8080 was resolved.
IPv6: (none)
IPv4: <IP_ADDRESS>
Trying <IP_ADDRESS>:8080...
Connected to btp-invoicing-srv.default (<IP_ADDRESS>) port 8080
using HTTP/1.x
POST /invoicing/createStripeInvoices() HTTP/1.1
Host: btp-invoicing-srv.default:8080
User-Agent: curl/8.11.0
Accept: /
Content-Type: application/json
Content-Length: 33
upload completely sent off: 33 bytes
< HTTP/1.1 404 Not Found
< X-Powered-By: Express
< Content-Security-Policy: default-src 'none'
< X-Content-Type-Options: nosniff
< Content-Type: text/html; charset=utf-8
< Content-Length: 172
< Date: Mon, 25 Nov 2024 18:22:16 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
<
Error
Cannot POST /invoicing/createStripeInvoices()

Connection #0 to host btp-invoicing-srv.default left intact

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@jmsrpp , here is without the (). the service seems not available (404) ?
~ $ curl -v -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "month": "
11", "year": "2024" }'
Note: Unnecessary use of -X or --request, POST is already inferred.

Host btp-invoicing-srv.default:8080 was resolved.
IPv6: (none)
IPv4: <IP_ADDRESS>
Trying <IP_ADDRESS>:8080...
Connected to btp-invoicing-srv.default (<IP_ADDRESS>) port 8080
using HTTP/1.x

POST /invoicing/createStripeInvoices HTTP/1.1
Host: btp-invoicing-srv.default:8080
User-Agent: curl/8.11.0
Accept: /
Content-Type: application/json
Content-Length: 33

upload completely sent off: 33 bytes
< HTTP/1.1 404 Not Found
< X-Powered-By: Express
< Content-Security-Policy: default-src 'none'
< X-Content-Type-Options: nosniff
< Content-Type: text/html; charset=utf-8
< Content-Length: 170
< Date: Tue, 26 Nov 2024 00:16:41 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
<

Error

Cannot POST /invoicing/createStripeInvoices

* Connection #0 to host btp-invoicing-srv.default left intact

sorry to bother you with all those tests, but could you try this:
'/odata/v4/invoicing/createStripeInvoices'

No worry @kay-schmitteckert , i moved to the next phase now with new error in the srv pod log "Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function" .. Look forward for your advise. Thx
********* The request ******
~ $ curl -v -X POST 'btp-invoicing-srv.default:8080/odata/v4/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "
month": "11", "year": "2024" }'
Note: Unnecessary use of -X or --request, POST is already inferred.

Host btp-invoicing-srv.default:8080 was resolved.
IPv6: (none)
IPv4: <IP_ADDRESS>
Trying <IP_ADDRESS>:8080...
Connected to btp-invoicing-srv.default (<IP_ADDRESS>) port 8080
using HTTP/1.x

POST /odata/v4/invoicing/createStripeInvoices HTTP/1.1
Host: btp-invoicing-srv.default:8080
User-Agent: curl/8.11.0
Accept: /
Content-Type: application/json
Content-Length: 33

upload completely sent off: 33 bytes
< HTTP/1.1 204 No Content
< X-Powered-By: Express
< x-correlation-id: 5aaa1c22-dd33-4760-84f1-81b974a50423
< OData-Version: 4.0
< content-type: application/json;odata.metadata=minimal
< Date: Tue, 26 Nov 2024 06:46:09 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
<
Connection #0 to host btp-invoicing-srv.default left intact

*************** SRV Pod Logs ****
{"level":"info","logger":"odata","correlation_id":"5aaa1c22-dd33-4760-84f1-81b974a50423","host":"btp-invoicing-srv.default:8080","user_agent":"curl/8.11.0","accept":"/","content_type":"application/json","content_length":"33","request_size_b":"33","x_correlation_id":"5aaa1c22-dd33-4760-84f1-81b974a50423","timestamp":"2024-11-26T06:46:08.026Z","msg":"POST /odata/v4/invoicing/createStripeInvoices ","type":"log"}
{"level":"warn","logger":"remote","correlation_id":"5aaa1c22-dd33-4760-84f1-81b974a50423","host":"btp-invoicing-srv.default:8080","user_agent":"curl/8.11.0","accept":"/","content_type":"application/json;IEEE754Compatible=true","content_length":"33","request_size_b":"33","x_correlation_id":"5aaa1c22-dd33-4760-84f1-81b974a50423","timestamp":"2024-11-26T06:46:09.018Z","msg":"Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function","stacktrace":["Error: Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function","at run (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_r
process.processTicksAndRejections (node:internal/process/task_queues:95:5)","at async RemoteService.on_handler (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:265:20)","at async next (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:68:17)","at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:66:10)","at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:277:20)"],"statusCode":502,"reason":{"request":{"method":"GET","url":"/apiportal/api/1.0/Management.svc/Developers","headers":{"accept":"application/json,text/plain","x-correlation-id":"5aaa1c22-dd33-4760-84f1-81b974a50423"}},"correlationId":"5aaa1c22-dd33-4760-84f1-81b974a50423"},"type":"log"}
Error: Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function
at run (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/utils/client.js:234:31)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async RemoteService.on_handler (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:265:20)
at async next (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:68:17)
at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:66:10)
at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:277:20) {
statusCode: 502,
reason: TypeError: Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function
at /layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap-cloud-sdk/http-client/dist/http-client.js:87:66
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async run (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/utils/client.js:223:16)
at async RemoteService.on_handler (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:265:20)
at async next (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:68:17)
at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:66:10)
at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:277:20) {
request: {
method: 'GET',
url: '/apiportal/api/1.0/Management.svc/Developers',
headers: [Object]
},
correlationId: '5aaa1c22-dd33-4760-84f1-81b974a50423'
}

No worry @kay-schmitteckert , i moved to the next phase now with new error in the srv pod log "Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function" .. Look forward for your advise. Thx
********* The request ****** ~ $ curl -v -X POST 'btp-invoicing-srv.default:8080/odata/v4/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ " month": "11", "year": "2024" }' Note: Unnecessary use of -X or --request, POST is already inferred.

Host btp-invoicing-srv.default:8080 was resolved.
IPv6: (none)
IPv4: <IP_ADDRESS>
Trying <IP_ADDRESS>:8080...
Connected to btp-invoicing-srv.default (<IP_ADDRESS>) port 8080
using HTTP/1.x

POST /odata/v4/invoicing/createStripeInvoices HTTP/1.1
Host: btp-invoicing-srv.default:8080
User-Agent: curl/8.11.0
Accept: /
Content-Type: application/json
Content-Length: 33

upload completely sent off: 33 bytes
< HTTP/1.1 204 No Content
< X-Powered-By: Express
< x-correlation-id: 5aaa1c22-dd33-4760-84f1-81b974a50423
< OData-Version: 4.0
< content-type: application/json;odata.metadata=minimal
< Date: Tue, 26 Nov 2024 06:46:09 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
<
Connection #0 to host btp-invoicing-srv.default left intact

*************** SRV Pod Logs ****
{"level":"info","logger":"odata","correlation_id":"5aaa1c22-dd33-4760-84f1-81b974a50423","host":"btp-invoicing-srv.default:8080","user_agent":"curl/8.11.0","accept":"/","content_type":"application/json","content_length":"33","request_size_b":"33","x_correlation_id":"5aaa1c22-dd33-4760-84f1-81b974a50423","timestamp":"2024-11-26T06:46:08.026Z","msg":"POST /odata/v4/invoicing/createStripeInvoices ","type":"log"} {"level":"warn","logger":"remote","correlation_id":"5aaa1c22-dd33-4760-84f1-81b974a50423","host":"btp-invoicing-srv.default:8080","user_agent":"curl/8.11.0","accept":"/","content_type":"application/json;IEEE754Compatible=true","content_length":"33","request_size_b":"33","x_correlation_id":"5aaa1c22-dd33-4760-84f1-81b974a50423","timestamp":"2024-11-26T06:46:09.018Z","msg":"Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function","stacktrace":["Error: Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function","at run (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_r process.processTicksAndRejections (node:internal/process/task_queues:95:5)","at async RemoteService.on_handler (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:265:20)","at async next (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:68:17)","at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:66:10)","at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:277:20)"],"statusCode":502,"reason":{"request":{"method":"GET","url":"/apiportal/api/1.0/Management.svc/Developers","headers":{"accept":"application/json,text/plain","x-correlation-id":"5aaa1c22-dd33-4760-84f1-81b974a50423"}},"correlationId":"5aaa1c22-dd33-4760-84f1-81b974a50423"},"type":"log"} Error: Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function at run (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/utils/client.js:234:31) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async RemoteService.on_handler (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:265:20) at async next (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:68:17) at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:66:10) at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:277:20) { statusCode: 502, reason: TypeError: Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function at /layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap-cloud-sdk/http-client/dist/http-client.js:87:66 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async run (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/utils/client.js:223:16) at async RemoteService.on_handler (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:265:20) at async next (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:68:17) at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/lib/srv/srv-dispatch.js:66:10) at async RemoteService.handle (/layers/paketo-buildpacks_npm-install/launch-modules/node_modules/@sap/cds/libx/_runtime/remote/Service.js:277:20) { request: { method: 'GET', url: '/apiportal/api/1.0/Management.svc/Developers', headers: [Object] }, correlationId: '5aaa1c22-dd33-4760-84f1-81b974a50423' }

Actually the request with /odata/v4 looks successful with 204 as status code. This confirms my assumption that there was an update of CAP to a version which involves the protocol in the path (/odata/v4). This means that all further requests to CAP will not work unless either
a) /odata/v4/ is added everywhere
or
b) the service path (in srv/*.cds modules) is set absolutely to e.g. “/invoicing” etc.

Hi @kay-schmitteckert , i did option b, rebuild and deploy to kyma, but it still fails as below. Now i would like to try with Option A. can you help to point out what are the changes required ? Thanks.

~ $ curl -v -X POST 'btp-invoicing-srv.default:8080/invoicing/createStripeInvoices' --header 'Content-Type: application/json' --data-raw '{ "month": "11", "year": "2024" }'
Note: Unnecessary use of -X or --request, POST is already inferred.

Host btp-invoicing-srv.default:8080 was resolved.
IPv6: (none)
IPv4: <IP_ADDRESS>
Trying <IP_ADDRESS>:8080...
Connected to btp-invoicing-srv.default (<IP_ADDRESS>) port 8080
using HTTP/1.x

POST /invoicing/createStripeInvoices HTTP/1.1
Host: btp-invoicing-srv.default:8080
User-Agent: curl/8.11.0
Accept: /
Content-Type: application/json
Content-Length: 33

upload completely sent off: 33 bytes
< HTTP/1.1 404 Not Found
< X-Powered-By: Express
< Content-Security-Policy: default-src 'none'
< X-Content-Type-Options: nosniff
< Content-Type: text/html; charset=utf-8
< Content-Length: 170
< Date: Wed, 27 Nov 2024 11:57:31 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
<

Error

Cannot POST /invoicing/createStripeInvoices

* Connection #0 to host btp-invoicing-srv.default left intact

Hi @kay-schmitteckert , May i know the status of this ? I would like to understand if there is any estimated timeline so i can workaround this with our partner. Thanks

Hi @ferrymul7 - The updated URL with /odata/v4 is the one you will need to use unless you specifically change the @path annotation in the CAP cds. The Error: Error during request to remote service: (0 , internal_1.getTenantIdWithFallback) is not a function is almost certainly the root cause, but please provide the results of the CURL with the updated URL. It seems like one of your project dependencies is now out of date:
https://github.com/SAP/cloud-sdk-js/issues/4982
Can you also post the dependencies from your package.json? It might be also worth deleting your package-lock.json and reinstalling the dependencies, or running npm update to ensure everything is aligned.
If the @sap-cloud-sdk/http-client and @sap-cloud-sdk/openapi have been updated from 3.4.0 respectively you would also need to regenerate the corresponding API clients:
https://sap.github.io/cloud-sdk/docs/js/v1/guides/upgrade-to-version-2
I'll also look for @kay-schmitteckert to provide his input when available.


fix(ChatbotHeaderSelectorDropdown): Try to fix onSelect problem in RHDH

onSelect doesn't trigger appropriately in RHDH Lightspeed and only RHDH Lightspeed. I'm wondering if this isn't the cause - I'm hoping to pull this in there and see if this fixes their problems.

Preview: https://virtual-assistant-pr-virtual-assistant-172.surge.sh


Add older MMTEB baselines

I was aggregating models for a different project and realized there are a couple of older multilingual baselines we should try.  facebook/mcontriever-msmarco (Contriever multilingual) and castorini/mdpr-tied-pft-msmarco (DPR-based with tied encoders). I don't think they're going to be very strong, but they're potentially worth having since they're baselines people may have heard of. Both can be run with sentence-transformers out of the box.
cc @KennethEnevoldsen and @Muennighoff

Great ran nthakur/mcontriever-base-msmarco (facebook one did not work with ST for me) & castorini/mdpr-tied-pft-msmarco - Results are here: https://github.com/embeddings-benchmark/results/pull/40
Are we good on bge-m3 & gte-multilingual-base or are results still missing? I think we should also have them
https://huggingface.co/BAAI/bge-multilingual-gemma2 also seems worth running but not in MTEB yet I think 🤔


I-beam cursor should auto-switch between black/white on MacOS

Atom added a mixin that automatically switches the I-beam cursor from black to white & back based on the background color of the theme, but for whatever reason, it doesn't work with this syntax theme unless you're running Atom in developer mode. It seems to stick with whatever color cursor matched the syntax theme that was selected when atom started up (white if you were on a dark theme, black if you were on a light theme) regardless of how much you change it. Reloading the window is necessary to get the cursor to change color.
Perhaps @lee-dohm can help out since he created the mixin.
Here's a screen recording to illustrate the incorrect behavior with this theme:

Here's a screen recording to illustrate the correct behavior with built-in themes:

The white-cursor support is in the cursors.less file in Atom:
https://github.com/atom/atom/blob/master/static/cursors.less
To my understanding, when the theme is changed, Atom does something to reinitialize the styles loaded in the DOM. This package probably doesn't do whatever that is when swapping between the light and dark backgrounds.

Thank you for the detailed report, and the pointer. I can confirm this issue is not limited to MacOS, I can duplicate it on Windows too. I'll take a look to see if I can find (and fix) the problem.


Implements inputs validator

Implements Null and String validator for inputs.
inputs : ('feature_flag_key', 'experiment_key', 'user_id', 'variation_key', 'variable_key' and 'variable_type')
Methods:
-> Activate
-> get_variation
-> Track
-> set_forced_variation through project_config-> set_forced_variation
-> get_forced_variation through project_config-> get_forced_variation
-> is_feature_enabled
-> get_enabled_features
-> get_feature_variable_for_type

Coverage remained the same at 100.0% when pulling 0d687ebe0509bf59a816fe13ee45d3f15dc92e28 on rashid/inputs-validator into 619f3bca6e655b43123105e7bed245081bc508c0 on master.

Will be looking at this soon. Wanted to see if maybe we could run this through the compat suite


No such option:

I have an untagged test inside a file which I want to run (but exclude some other tests)
pybot --exclude bootloaderORapplication -n noncritical .

However I get the output:
==============================================================================
Pu4-Test
==============================================================================
Pu4-Test.Bootloader 2G4 Interface
==============================================================================
The bootloader should have a radio interface 0x200000
Usage: pybot [options] [filename]

pybot: error: no such option: --exclude
[ ERROR ] Execution stopped by user.

As you can see, the tests begin, and the  0x200000 is a keyword executing which makes a command line call st-info --flash which writes that hex value to stdout.
Another person seemed to have a similar problem here:
http://stackoverflow.com/questions/31593743/no-such-option-include-for-pybot
pybot --version
Robot Framework 2.9.1 (Python 2.7.3 on linux2)

#Also reproduced after update:
pybot --version
Robot Framework 2.9.2 (Python 2.7.3 on linux2)

My special case seems to be that I was swapping an application over to being used as a library and python optparse was being used and raising the error, which is silly, but Robot is interpreting that error as its own I think, and so not generating any reports etc for any of the test cases.

Sorry, I dont really understand what is going on here. What do you mean when you say that "you were swapping an application over to being used as a library"?
If you could provide an executable example that would replicate this issue, that would be great.

Hi, I mean the code I was working with was supposed to be called directly from the command line, i.e. it had a main() implementation and therefore used the optparse library to parse the command line arguments that were coming in.
I then modified it for the function to be called via another module, however it was still creating an OptionParser() and calling the parse_args() method.
I just looked into the source located at http://svn.python.org/projects/python/trunk/Lib/optparse.py . It looks like optparse prints the error and calls sysexit itself, so I think if that's the case there's nothing the Robot Framework could do to indicate that the developer is being a numpty.

ok, thanks for the clarification


bar.ShowBar undefined (type *pb.ProgressBar has no field or method ShowBar)

import "github.com/cheggaaa/pb/v3"

...
bar := new(pb.ProgressBar)
bar.ShowBar = false
...

I don't know exactly what the problem is

The problem is you import v3, but code from v1.
You can import v1 import "github.com/cheggaaa/pb"
Or use v3 and disable bar via template

Oh well, thanks.


Bad error message for IDL syntax errors

I got:
FATAL ERROR: IDL SYNTAX ERROR LINE: 2 - skipped: "dictionary SignInStatusOptions {
    boolean idp;
  }"

I don't know yet what the error is, but this message is not super helpful in figuring it out.

Unfortunately I only get what information is given to me by widlparser; since it's grammar-based, all it gets is "this isn't valid grammar for the current spot".
Without implementing my own WebIDL parser, I don't think I can improve these meaningfully.


Clarify documentation on "Upload SharePoint Workbench" (Page: Setup SharePoint Tenant)

It took me some time to get workbench.aspx up and running on my Dev-Tenant. The current documentation chapter "Upload SharePoint Workbench" (Page: Setup SharePoint Tenant) could be more clear in how to handle the file.
I suggest changing the above mentioned paragraph to read as follows:
"While we will introduce and talk about the SharePoint Workbench in the tutorials, to get set up, download the workbench.aspx to your local machine. Open the file from our GitHub repo in your browser, switch the view to RAW format, then right click, choose Save As option to save as workbench.aspx to your local computer, and upload it to the Documents library in the dev site collection."

Thanks for the feedback.  I've reworked it a bit.  Unfortunately IE doesn't have a "save as" context item on a page. :(  Instead, I simply said "right click on the raw link and select save target as".  Hope that makes it more clear.


PIP 37-Follow up: Chunk message with batching enabled

Motivation
#4400 provides client to publish large size message into chunks. However, it requires producer-client to disable batching explicitly. Enhance pulasr-client lib to chunk message without disabling the batching.

@rdhabalia is this issue still relevant? It seems stale and no one works on it yet.


[Remote Store] Add method in BlobContainer to fetch the keys in sorted order

Description

Currently, BlobContainer supports two methods to list keys in the blob store:

Map<String, BlobMetadata> listBlobs() throws IOException
Map<String, BlobMetadata> listBlobsByPrefix(String blobNamePrefix) throws IOException

These methods do not provide any ordering guarantees. Even though underlying blob store supports listing down keys in some specific order (for example, AWS S3 supports listing keys in Lexicographic order), that ordering would be lost as listBlobs* methods return a map.
In remote store feature, we store segment and translog metadata in different path of the same blob store which contains actual data. These metadata files are created frequently (translog files are created at each translog fsync and segment metadata files are created at each refresh).
Whenever we need to read/download data from remote store, we read the latest metadata file first and then download the actual data. As number of metadata files grow, reading latest metadata file will become slower as listBlobs* returns everything and we need to sort the result in OpenSearch process.
To have predictable performance in reading metadata files, we need to use blob store support to provide keys in sorted order. This also means we need to name metadata files in such a way that the first file name from the sorted results will always be latest metadata file.
In this change, we add a method to BlobContainer which supports ordering keys of a given prefix in Lexicographic sort. It also supports limiting the size of result by providing a limit parameter.
The default implementation calls listBlobsByPrefix() internally and sort the results after fetching list of keys.
This change also overrides the new method in S3BlobContainer. As AWS S3 always returns list of keys in lexicographic sorted order, we don't have to fetch all the keys. This makes it more performant than the default implementation.

Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Following test is failing, taking a look.
[org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=snapshot.restore/10_basic/Create a snapshot and then restore it}](https://build.ci.opensearch.org/job/gradle-check/18822/testReport/junit/org.opensearch.backwards/MixedClusterClientYamlTestSuiteIT/test__p0_snapshot_restore_10_basic_Create_a_snapshot_and_then_restore_it_/)

Following test is failing, taking a look.
[org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=snapshot.restore/10_basic/Create a snapshot and then restore it}](https://build.ci.opensearch.org/job/gradle-check/18822/testReport/junit/org.opensearch.backwards/MixedClusterClientYamlTestSuiteIT/test__p0_snapshot_restore_10_basic_Create_a_snapshot_and_then_restore_it_/)

Got fixed after re-basing main

Test failures:
[org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testNodeDropWithOngoingReplication](https://build.ci.opensearch.org/job/gradle-check/18866/testReport/junit/org.opensearch.remotestore/SegmentReplicationUsingRemoteStoreIT/testNodeDropWithOngoingReplication/)
[org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testDropPrimaryDuringReplication](https://build.ci.opensearch.org/job/gradle-check/18866/testReport/junit/org.opensearch.remotestore/SegmentReplicationUsingRemoteStoreIT/testDropPrimaryDuringReplication/)
[org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testNodeDropWithOngoingReplication](https://build.ci.opensearch.org/job/gradle-check/18866/testReport/junit/org.opensearch.remotestore/SegmentReplicationUsingRemoteStoreIT/testNodeDropWithOngoingReplication_2/)
[org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testNodeDropWithOngoingReplication](https://build.ci.opensearch.org/job/gradle-check/18866/testReport/junit/org.opensearch.remotestore/SegmentReplicationUsingRemoteStoreIT/testNodeDropWithOngoingReplication_3/)
[org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testNodeDropWithOngoingReplication](https://build.ci.opensearch.org/job/gradle-check/18866/testReport/junit/org.opensearch.remotestore/SegmentReplicationUsingRemoteStoreIT/testNodeDropWithOngoingReplication_4/)


updating migration rollback command for accepting step parameter as n…

Description
This request will enable support of negative value for step parameter in migration rollback command. Earlier we couldn't use negative value.
Usage
Now using  php artisan migrate:rollback --step=-10 will rollback migration except the initial 10 migrations.

It will add one extra feature to existing command.
Won't break any existing functionality.

No plans to add this right now.


Get image object from collection

Hi there,
I have created a multi collection "galleries" with an image and some text fields. As I noticed the image field returns the foreign key for the optimized images. But I am not sure how to get the actual image object out of it like if I would use the imageField in a block, so I can use it with the PruviousPicture component.
Since I am a beginner, I have no clue on how to move on.
Any help is greatly appreciated, thank you.
Michael

Hey @Michael201401! You need to chain .populate() in the query builder to get the relational fields.

https://pruvious.com/docs/fields#population
https://pruvious.com/docs/query-builder#populate


Allow GitHub tags matching a pattern to be excluded from latest tag

I have submitted a pull request for this - comments welcome and appreciated.

Hello. We have just shipped a new feature which allows you to pass an arbitrary filter to the github tag and release badges. For example
The filter param can be used to apply a filter to the project's tag or release names before selecting the latest from the list.


Title: More Mobile Responsive Website

Is your feature request related to a problem? Please describe.
Mobile Users need a responsive website. You will lose them if they see bigger text and if they have to scroll a lot.
Describe the solution you'd like.
Your website is already a lot responsive. But, it is not responsive for mobile with under 320px max-width.
So, I have to add responsiveness for that using media queries in CSS.
Describe alternatives you've considered.
I have already checked which media queries need to be updated in order to get a better & enhanced user experience & user interface.
Add any other context or screenshots about the feature request here.
Also, your CodeSetGo logo also gets hidden when the device's max-width is less than 300px.
So, I will also correct it while making the website mobile responsive.

Kindly Assign this to me so that I can raise PR.

Hello. I can work on this. You can assign it to me if no one has already requested it. Thankyou.

I had already raised a Pull Request for this issue #51
That's the solution -> #53

hey i would like to work on this


Octal literals, e.g. 'int i = 010;' are arguably evil

Original issue created by<EMAIL_ADDRESS>on 2014-01-16 at 07:09 PM

I just finished swearing up and down that the integer literal 010 would equal ten, not eight.  How embarrassing.
If we have managed to get the 'l' suffix error to work, it might be worth considering a check that forbids all octal literals as well.

/cc @kevinb9n
I revived this and wrote a prototype checker.  My first pass flagged all octal literals, and of the ~50 instances I looked at, all were correct.  The usages fell into 2 buckets:

Specifying months and days in dates, e.g. 'new Date("2014", "10", "01")'.  These are OK because they parse as the same value whether they are octal or decimal.  The only concern here is if you modify the date to either "08" or "09", you will get a compile error as those are not valid octal values.  So you might waste some time understanding the error message, but they are not strictly a correctness issue.

Filesystem permissions, e.g. 'chmod(file, 0755)'.  These are also OK because filesystem permissions are octal.

I'm going to update the prototype check to only flag octal values that are not of length 2 or 4.  That should weed out these legitimate cases.

I special cased my prototype checker to flag octal values that are not of length 2 or 4, to avoid the date and filesystem permissions false positives, but most of the hits were still false positives.  I think octal literals may not actually be evil.  Closing as will not fix.

Okay then. Good to know. Thanks for digging into it.
On Tue, Jan 27, 2015 at 9:16 PM, Eddie Aftandilian<EMAIL_ADDRESS>
wrote:

I special cased my prototype checker to flag octal values that are not of
length 2 or 4, to avoid the date and filesystem permissions false
positives, but most of the hits were still false positives. I think octal
literals may not actually be evil. Closing as will not fix.
—
Reply to this email directly or view it on GitHub
https://github.com/google/error-prone/issues/227#issuecomment-71782383.

--
Kevin Bourrillion | Java Librarian | Google, Inc. |<EMAIL_ADDRESS>


method to fetch Commentary for the match

I am trying to see if I can get the full ball-by-ball commentary of the match.
With match ID - I thought get_comms_json() will do the trick. But, unfortunately, it doesn't return any value.
>>> from espncricinfo.match import Match
>>> m = Match('1175356')
>>> m.match_url
'http://www.espncricinfo.com/matches/engine/match/1175356.html'
>>> m.comms_json
>>>

Is it possible/feasible to get the full commentary in json format? If not, guess I ll have to start working on a scraper. Thanks for your work.

@prasanna-sk They may have changed the structure of the json, so let me check and report back. From what I recall the commentary json was paginated.

@dwillis the json is indeed paginated. But there's an issue over there. I cannot find a way to detect when there was a stoppage in play and the number of overs got reduced.

@nayangarg Were you able to pull the commentary though?

@prasanna-sk Yes, I did. I didn't use this package though.

@nayangarg Could you share how you did it?

Way too long, but I've fixed the get_comms_json method.


Preload entrypoint

I have an entry point that I'd like to preload before use and would like to not block render to load the css for it. This adds a top level tag that will drop the preload statements into the dom for a given vite asset

This seems like very useful improvement. Can I help somehow to get it merged?

bump

Happy to make any changes!

bump

bump - Happy to make any changes!

This PR seems an extended version of #56, is that right? If so, could you close #56?

Rebased, and updated to use the logic in #52 for preloading

Out of interest - would this stop the situation where the page loads, then CSS is loaded in afterwards?
My current fix for this has been adding the CSS to the <head> manually, but I'm guessing that means I might be applying the CSS twice?

Looks good to me! I'll merge it, and I'll create a new release with this feature in it next week.


http_server: Set error header, persist OCSP.

When proxying unsigned, set a response header indicating the error. This could
include Accept not preferring SXG, but normal usage should avoid forwarding
such traffic to this server.
Use the filesystem for persistent and replicated storage of OCSP and ACME
state.

Addresses #250.


Special case value deletion with a leading decimal

This maybe fixes #740
Leading decimals are handled by createNumberMask to substitute a placeholder of 0.
This works fine for new values, and most edits. But if I replace a value with a dot, the field remains empty for one update cycle. Another dot and it's back on track.
The likelier UX scenario for a non-prefixed decimal value is going to be dot → number. Entering this with just one dot and we end up with a whole number. 9% versus the user's intent of 0.9% — huge difference in most contexts!

I tried my best to track down where this behavior is implemented and the issue seems to be the result of assumptions around character-for-character placeholders versus two characters for one raw value in this case.
Specifically:
https://github.com/text-mask/text-mask/blob/master/core/src/adjustCaretPosition.js#L25
. means this goes negative, so isAddition is false and the caret moves to the beginning. So I set the previousConform value to '' as it is effectively an empty value in this scenario.
https://github.com/text-mask/text-mask/blob/master/core/src/conformToMask.js#L211-L216
The 0._ placeholder is longer than the conformed 0. value, so we stop short of the placeholder character index.
I'm not sure the leading decimal case is special enough to warrant these exceptions, but I couldn't think of another case where a placeholder would be expanded like this.
If this is the wrong direction I can make another attempt with some feedback, thanks!

This fix is too naive, not considering a configurable decimal symbol. A better fix is brewing in #740.


Support for From::from on the items of iterator

Hello
I find myself writing iterator method chains that contain map(From::from) ‒ I need to convert all the elements from one type to another. I was wondering, if there are convenience methods like cloned (I think that one is actually in std already) and collect_vec, would it make sense to have some kind of convenience method for this? I could send a pull request, but I want to ask first if it makes sense to anyone else and if someone has a good name for such method.

.map_from()? ;)

I thought about that one, but it felt… unsatisfying. What I mean is:

For example, we have cloned, not map_clone.
I wonder if map_into (or somethingelse_into) would be better, because if I want to convert things, I can either do Result::from(source) or source.into() ‒ and in case of the iterator it would be in the postfix method notation.
I also thought about converted (either intoed or fromed sounds silly), but I don't know if people would reasonably find that one.


requestAnimationFrame

Hi
Thanks for sharing your work.
I'm creating a small project based on it and I made a couple of changes you might find useful?
Cheers

Hello!
Great changes, this code needed some attention.


upgrade to react 16

as this is potentially a breaking change, there are two options:

maintain a pre-release branch with react 16 and release dev versions from it, allowing the components team a chance to test it out

make a cross-project decision and commit to it synchroneously

decisions need to be made @idoros @nadavwix

It's definitely a breaking change for us, no? The fact that renders can return multiple children hits that nail straight on the head.

I think supporting multiple roots will require some code changes on our part, yes.
I was referring more to the potential of breaking this library's API backward-compatibility.

Can we have the library being agnostic to the version?
What conflicts do we have between 15 and 16?
Auto add of root, inline style, data-* shouldn't mind if there is 1 elements or more.
Are there any conflicting types that we can't be agnostic about?

@idoros I don't know what conflicts we may have, I didn't spend time on this task yet.
Being version agnostic is possible. do you think we need to test this library against two different react versions?

I made a branch for react 16. It's failing when trying to load browser tests.
Maybe it will be worth debugging after it's out of beta.

I think we should definitely support both. no other way around it..

in the upcoming version 4, support for react 16 seems trivial


Remove unused io module

Use std::io instead of crate::io re-exports.

LGTM, assuming CI is green of course.


How to use with a keyboard shortcut?

Hey! Currently cleave only screenshots when I enter cleave in the terminal. I wanted to know how I might be able to bind it to a keyboard shortcut.
Thanks.

It should be as easy as throwing the contents of fn main into another function and using a crate like global_hotkey to listen for the hotkey that you want, or if you didnt wanna change the application at all you can just use something like autohotkey to launch the program on a keybind

It should be as easy as throwing the contents of fn main into another function and using a crate like global_hotkey to listen for the hotkey that you want, or if you didnt wanna change the application at all you can just use something like autohotkey to launch the program on a keybind

I don't know rust so I'll use the auto hot key bind


Encode CLIMAT BUFR sequence (307073)

User story
As a data provider I wish to publish CLIMAT data using the BUFR sequence 307073, by either uploading a CSV file containing the data or by uploading the TAC encoded message.
Acceptance criteria

[ ] CSV data uploaded, automatically converted to BUFR and published on WIS2.0
[ ] FM 71-XII CLIMAT encoded data uploaded, converted to BUFR and published on WIS2.0

Definition of done

[ ] unit/functional tests added/updated
[ ] documentation updated
[ ] live demonstration provided

2024-07-24

in progress (@david-i-berry)

2024-11-21: we can defer to after the initial 1.0 release for further clarification / requirements elicitation.


Dev

Codecov Report

Merging #9 (862dd90) into main (ebd065f) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #9   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           17        20    +3
  Branches         9        12    +3
=========================================
+ Hits            17        20    +3

Impacted Files
Coverage Δ

src/index.ts
100.00% <100.00%> (ø)

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 ebd065f...862dd90. Read the comment docs.


How to retrieve subsequent pages of result with context?

I'm using getPersonSearch which returns only 15 people and a parm called context. Docs say:
context - the search context token, which is returned from search requests and allows requests for subsequent pages
So how do I use context to get the additional people in my result?
Like:
        fsClient.getPersonSearch({
                    context: theContext
                })
                .then(function (response) {

does not work!
Is this documented anywhere?
Thanks,
Debbie Holtzendorff

You're doing it the correct way. When you say it doesn't work, what happens?

I found the above only returns the first 15 items over and over again. After some creative suffering I discover that I needed to add the index of the next 15 items desired like:
fsClient.getPersonSearch({
context: theContext
Index: theIndex // Previously calculated item number to start with
})
.then(function (response) {
Is there any documetation out there?
Thanks.

@DebbieHoltzendorff That actually makes some sense.
The only docs we have are http://familysearch.github.io/familysearch-javascript-sdk/2.5/#/api/searchAndMatch.functions:getPersonSearch and https://familysearch.org/developers/docs/api/tree/Person_Search_resource


Mods for DMA NeoPixel on GPIO3 and classic wifi connect

Mods for DMA NeoPixel on GPIO3
and classic wifi connect

Thanks @krulkip unfortunately it's not building:
In file included from ESP8266HueEmulator.ino:10:0:

/home/travis/arduino_ide/libraries/NeoPixelBus/src/NeoPixelBus.h:78:5: note: NeoPixelBus<T_COLOR_FEATURE, T_METHOD>::NeoPixelBus(uint16_t, uint8_t) [with T_COLOR_FEATURE = NeoRgbFeature; T_METHOD = NeoEsp8266DmaMethodBase<NeoEsp8266DmaSpeed800Kbps>; uint16_t = short unsigned int; uint8_t = unsigned char]

     NeoPixelBus(uint16_t countPixels, uint8_t pin) :

     ^

/home/travis/arduino_ide/libraries/NeoPixelBus/src/NeoPixelBus.h:78:5: note:   candidate expects 2 arguments, 1 provided

/home/travis/arduino_ide/libraries/NeoPixelBus/src/NeoPixelBus.h:72:61: note: constexpr NeoPixelBus<NeoRgbFeature, NeoEsp8266DmaMethodBase<NeoEsp8266DmaSpeed800Kbps> >::NeoPixelBus(const NeoPixelBus<NeoRgbFeature, NeoEsp8266DmaMethodBase<NeoEsp8266DmaSpeed800Kbps> >&)

 template<typename T_COLOR_FEATURE, typename T_METHOD> class NeoPixelBus

/home/travis/arduino_ide/libraries/NeoPixelBus/src/NeoPixelBus.h:72:61: note:   no known conversion for argument 1

I use arduino IDE 1.6.8 and esp8266 version 2.3.0 and latest makuna NeoPixel.
krulkip
On Sunday, November 20, 2016 5:59 PM, probonopd<EMAIL_ADDRESS>wrote:

Thanks @krulkip unfortunately it's not building:In file included from ESP8266HueEmulator.ino:10:0:
/home/travis/arduino_ide/libraries/NeoPixelBus/src/NeoPixelBus.h:78:5: note: NeoPixelBus<T_COLOR_FEATURE, T_METHOD>::NeoPixelBus(uint16_t, uint8_t) [with T_COLOR_FEATURE = NeoRgbFeature; T_METHOD = NeoEsp8266DmaMethodBase; uint16_t = short unsigned int; uint8_t = unsigned char]
 NeoPixelBus(uint16_t countPixels, uint8_t pin) :

 ^

/home/travis/arduino_ide/libraries/NeoPixelBus/src/NeoPixelBus.h:78:5: note:   candidate expects 2 arguments, 1 provided
/home/travis/arduino_ide/libraries/NeoPixelBus/src/NeoPixelBus.h:72:61: note: constexpr NeoPixelBus<NeoRgbFeature, NeoEsp8266DmaMethodBase >::NeoPixelBus(const NeoPixelBus<NeoRgbFeature, NeoEsp8266DmaMethodBase >&)
template<typename T_COLOR_FEATURE, typename T_METHOD> class NeoPixelBus
/home/travis/arduino_ide/libraries/NeoPixelBus/src/NeoPixelBus.h:72:61: note:   no known conversion for argument 1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks @krulkip please check the build log at https://travis-ci.org/probonopd/ESP8266HueEmulator/builds/177455181
If needed, feel free to change the .travis.yml

blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex !important; background-color:white !important; }  Sorry not sure how to do that. Pretty sure it is in the neopixelbus version.  It makes the code more complex.My aim is to make the hue emulator talk to milight bulbs using a NRF24L01.I have done quite a bit of work on this as you can see here.http://arduino-projects4u.com/milight-rf-control/ What do you think could that be interesting or is it too far away from your ideas.
Krulkip
On Monday, November 21, 2016, 10:21, probonopd<EMAIL_ADDRESS>wrote:
Thanks @krulkip please check the build log at https://travis-ci.org/probonopd/ESP8266HueEmulator/builds/177455181
If needed, feel free to change the .travis.yml
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@krulkip great work on using the NRF24L01. I will accept pull requests that don't break existing functionality and Travis CI builds.

Yes its the makuna Neopixel version. You are using 2.1.4 and you need to update to 2.2.4

I get "This branch has conflicts that must be resolved" - can you send a new PR that does not have the conflicts? Thanks

Sorry i am not used to travis. Lot of messing around. now it works.

@krulkip thanks for your valuable contribution. Can you please open a new Pull Request with all of your changes in one go? I hope that this way, your new Pull Request will not show the "This branch has conflicts that must be resolved" error and will build on Travis CI just fine, in which case I will be happy to merge it.

Hope this finally works

Hey, just my review of the changes:
The SPI.h include shouldn't be necessary in the .ino.
The strip now consumes the RX pin interfering with serial I/O over USB, but to be fair the base project doesn't accept serial input anyway (this is likely to confuse people trying to play with this example project). The modified strip configuration doesn't use DMA which slows things down and is setup for RGB WS2812 color ordering instead of the much more common (unless you have a stockpile of old strips) GRB WS2812 color ordering.
The wifi changes are probably a net improvement in that the example won't stick itself if it doesn't connect fast enough.
The ArduinoOTA handler is probably a bit out of place.
In README.md, the initial link shouldn't be modified to point to @krulkip's repository, but the text update should be incorporated (tweaked based on what is decided on the above).
All in all, it looks like most of these changes are focused on making sacrifices to this generic example project to adapt to a highly constrained board and should probably just live in @krulkip's fork.

The idea of using dma is that the timings of the neopixel data is controlled by hardware and hence more accurate and also consuming less cpu power. RGB or GRB does not matter you can use either. The dma is only available on the later releases of makuna neopixelbus, i use 2.2.4. On my system it was only possible to compile this by adding SPI.h.
Maybe we should be able to select either method.
The ArduinoOTA was already incorporated and OTA will not work without it.
README.md agree. Just wanted to show it now compiles on travis. 😀

How do we want to proceed with this?


Outdated documentation on disk-limits

We are currently running into disk full issues during deployment (see our question and setup description here: https://docs.microsoft.com/en-us/answers/questions/827223/actual-disk-space-requirements-for-azure-appservic.html)
I believe the information on quotas is outdated, as I cannot find our currentl SKU and am confused, if our limit is still 15 GB with a P2V3 plan or if it is (hopefully) a bit higher than that:
https://github.com/projectkudu/kudu/wiki/Understanding-the-Azure-App-Service-file-system
Thanks for checking (and possibly updating) the docs.

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


Dao cont prettified

Overall this change looks really good to me.  Nice clean U2 code and data binding.  Mostly minor comments about documentation and naming in a few places.


Fix Kyma Environments Cleanup Job database connection

Description
Changes proposed in this pull request:

extend db connection retry interval,
fix logs.

Related issue(s)

/test-all

/test all

/retest

/test all


[253] Duplicate filter for arxiv updates task

Closes #253

@bishax ah, sorry that's related to PR #244 and https://github.com/gregversteeg/corex_topic/pull/39
just bumped the corextopic version in the requirements to pick up the joblib fix

Ah, so don't forget to run pip install --upgrade corextopic (or alternatively a new conda env from requirements.txt)

Good to merge.


Clean up Docker instructions

Hey! I ended up running into an couple of issues when using the provided Docker command
since it was using a) an old version of the Celestia node and b) not forwarding the port
used by the JSON-RPC API.
I've updated the README accordingly.

On a sidenote, what's the difference between port 26657 and 26658. In the docs it says
both are for RPC but I don't see 26657 used anywhere.
Thanks!

@HCastano thanks for the contribution!

On a sidenote, what's the difference between port 26657 and 26658. In the docs it says
both are for RPC but I don't see 26657 used anywhere.

26657 is for celestia-app in this setup https://docs.celestia.org/nodes/celestia-app/#ports

@jcstein are the ports documented anywhere? which port is for which purpose?
Even though it might be duplication, I think it is worthwhile also documenting in this repo why we are using the ports we do.

@jcstein The Celestia docs don't explain the difference between 26657 and 26658 though. Even in the troubleshooting docs the the text body mentions *57 while the table has info for *58 🤷♂
Personally, my attempts to use port *57 for JSON-RPC requests fail, so I image there must be some difference.

to clarify, the troubleshooting page is for celestia-node
26658 is RPC for celestia-node https://docs.celestia.org/nodes/celestia-node-troubleshooting/#ports
26657 is RPC for celestia-app https://docs.celestia.org/nodes/celestia-app/#ports

it sounds like a Celestia-wide description of different ports would make sense both in this readme and in celestia docs

@jcstein gotcha, didn't realize they were for different node types. I've added a column with the node type for each port, let me know what you think

amazing! thank you again for the PR and contribution @HCastano 😄

Thank you for your contribution! :)


Make entity-creation error messages easier to find

Backend issue https://github.com/getodk/central-backend/issues/729 describes a scenario on the forum where there is a "Problem creating Entity" message with no explanation. The message is in the audit log JSON, but weirdly not showing up.
Two fixes should be made:

Double-check that the error message is getting extracted from the audit log details in the right way, especially for this situation
Add "entity.create.error" as an option in the audit log filter menu.

Add "entity.create.error" as an option in the audit log filter menu.

Since we don't don't show entity.create or submission.create events in the main server audit log, my instinct is that we also shouldn't show entity.create.error events. Then again, maybe we can expect that there won't be many entity.create.error events, so including that action wouldn't dramatically increase the size of the audit log.
Whether or not we include entity.create.error in the main audit log, I do think it'd be nice to surface those three actions in Frontend somewhere. Maybe in a project-specific audit log?

That's true. I'm willing to wait for a project (or even dataset) -specific audit log!

But I did make a small PR to address the first part - of showing entity create error messages when they're not in the main error message location.

I'm willing to wait for a project (or even dataset) -specific audit log!

Ooh a dataset-specific audit log, that sounds helpful!
I just merged #717. 🚀 What do you think about closing this particular issue? And possibly filing a new issue about the idea of another audit log to surface entity.create.error and other events? (Or it could be noted in the parking lot.)

Note to QA:
We're fixing the backend issue behind this error so it won't be possible to fresh errors of this case appear, but here is a link to a submission from an earlier version that has an entity error and should show the error message.

Tested with Success!

Tested with Success!


Setup formalities

Come with official name (maybe also a logo), ownership, license and create standard repository files that we should have:

[x] README.md
[x] LICENSE.md (also NOTICE file for Apache License)
[x] CONTRIBUTING.md

Files prepared, please revisit & close issue if done for now.


emacs-package updates: No propagation of pname as default to ename for self-declared packages

Issue description
After upgrading to https://github.com/NixOS/nixpkgs/blob/0015c34f9c1be8776a3ca86d2ce86b3304c34525/pkgs/build-support/emacs/melpa.nix#L16, i get the following error message for self-declared packages like find-file-in-project and pdf-tools:
builder for '/nix/store/k0j7g3n0dn8mfvsa0qckzrqm49h33jbb-emacs-find-file-in-project-3.5.drv' failed with exit code 25
5; last 9 log lines:
  unpacking sources
  unpacking source archive /nix/store/cnlff99n4dq6l3kfrqxil67vcjxgvi38-source
  source root is source
  patching sources
  configuring
  no configure script, doing nothing
  building
  installing
  Opening input file: No such file or directory, /private/tmp/nix-build-emacs-find-file-in-project-3.5.drv-0/packages
/-3.5.tar

Technical details
nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-darwin"`
 - host os: `Darwin 17.6.0, macOS 10.13.5`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.0.4`
 - channels(root): `"nixpkgs-18.03pre116939.d7d774deea"`
 - channels(ptsirakidis): `""`
 - nixpkgs: `/Users/ptsirakidis/projects/ptsirakidis/nix-config/nixpkgs`

cc @ttuegel & @Mic92

Closed by #44060


nixos/kdeconnect: Added programs.kdeconnect option

Motivation for this change
KdeConnect requires to open TCP and UDP ports to work properly
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

On 16/09/19 13:50, Bjørn Forsman wrote:
@bjornfor requested changes on this pull request.
add an "...openFirewall" boolean option that defaults to false.
Kdeconnect won't work at all without those ports open,and it won't even give any error message

Kdeconnect won't work at all without those ports open,and it won't even give any error message

Right. But most nixos options don't automatically open the firewall, even though opening the firewall is the "correct" thing to do in many cases.
I guess this is a bit different than running a webserver, since that can be accessed via localhost, whereas for this program that doesn't make sense.
On the other hand, you're pretty likely to see the openFirewall option when you search for kdeconnect in nixos config options.
Let's get input from other community members.
Please fix git history so that it's ready to merge.

I guess another reason to not open ports by default is that users might be running other things on those ports already, which would then be open for anybody. An openFirewall option is like a warning sign to the user that ports are being opened, they should make sure those aren't used by something else already (the ports should ideally be mentioned in the description).
You could also add
{
  assertions = [{
    assertion = cfg.openFirewall;
    message = "You need to enable `programs.kdeconnect.openFirewall` to use KDEConnect, which opens ports ${portRange}.";
  }];
}

to make sure it's enabled.

@Infinisil I don't like that a module needs 2 flags set to true when any other module only requre 1,with maybe some other more specific configuration.
I have clarified that the module will open the given port

Still waiting on @infinisil 'S review

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/331

@pasqui23 you still have some typos mentioned in the reviews not fixed in current state of the PR.

I didn't mean to remove @Infinisil >.> I'll try and get around to making the changes sometime if it's still open later

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/465

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/485

Does this have any integration with plasma? Should enabling plasma also enable this option?

I don't think so, I'm using it on windows too and there is gsconnect for GNOME. This is mostly so it opens the right ports.

I guess this looks good after a squash

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/540

@Infinisil I've squashed all the commits in one. Are there any other blockers?

Let's merge this old PR :).


Getting rid of the RECORD_AUDIO permission ?

What

Users that have APKs with version codes [271, 580] may need to accept the android.permission.RECORD_AUDIO permission, which may result in them not upgrading to this version of the app.
I got this when preparing the beta release. Any way we can get rid of that permission ?

As I have forked the repo, I can indeed remove this permission.

Applied on the fork: https://github.com/g123k/plugins/commit/e38826f0ca92ff55cdb55f00f957787f1c537629
Nothing to do here, except a pub upgrade


SwiftSupport L63

When building, I get: 'Cannot convert value of type 'String' to expected argument type 'StaticString''
I have installed FBSnapshotTestCase 2.0.7 via CocoaPods, and have also tried commit ee57dee37aa5be6ee6b307670a37f9bcce69e2e4. I build with Xcode 7.3-beta3.
In my CococaPods file I have the following defined:
use_frameworks!
platform :ios, '8.0'

If I remove that line I get three errors for the following lines in FBSnapshotTestController.m:
#import <FBSnapshotTestCase/UIImage+Compare.h>
#import <FBSnapshotTestCase/UIImage+Diff.h>
#import <FBSnapshotTestCase/UIImage+Snapshot.h>

The error I get is: "Use of private header from outside its module"
When I build with Xcode 7.2.1 I don't get the StringLiteral error, but I do get the three last errors.

After reading through [this pull request](https://github.com/facebook/ios-snapshot-test-case/pull/141), I see you already have got the solution for the three import errors. Please accept that pull request. :-) So it's just the line 63 error remaining. I don't know the correct solution for this, but if someone else has the same problem, my workaround for now was to comment out that lie and just write a generic XCTFail in its place.

@niklassaers I am waiting for cocoapods 1.0 to go thru with the open PR.

Same issue. Waiting for cocoapods update I guess

The entire thing does not build for me. Maybe there should be a guide how to setup a Swift project?

I am hitting this problem, too. Any progress or update?

I'm hitting this problem as well.

Still waiting on cocoapods I am afraid

I was able to successfully install FBSnapshotTestCase with Carthage last night for a Swift project.  I wrote it up here if anyone is interested: http://cleanswifter.com/fbsnapshottestcase-installation-carthage/

So CocoaPods 1.0 is live what is the issue it was supposed to fix? I'm getting the same problem using it.

great @fcy! I am going to close this one.


[mieb] InfoSeekIT2ITRetrieval & InfoSeekIT2TRetrieval fail with BAAI/bge-visualized

Running the tasks with BAAI/bge-visualized-base-base/m3 and getting errors like below
ERROR:mteb.evaluation.MTEB:Error while evaluating InfoSeekIT2TRetrieval: The size of tensor a (516) must matc
h the size of tensor b (512) at non-singleton dimension 1
Traceback (most recent call last):
  File "/data/niklas/mieb/mteb/scripts/run_mieb.py", line 82, in <module>
    results = evaluation.run(model, output_folder="/data/niklas/mieb/results-mieb-final", batch_size=1)
  File "/data/niklas/mieb/mteb/mteb/evaluation/MTEB.py", line 464, in run
    raise e
  File "/data/niklas/mieb/mteb/mteb/evaluation/MTEB.py", line 425, in run
    results, tick, tock = self._run_eval(
  File "/data/niklas/mieb/mteb/mteb/evaluation/MTEB.py", line 300, in _run_eval
    results = task.evaluate(
  File "/data/niklas/mieb/mteb/mteb/abstasks/Image/AbsTaskAny2AnyRetrieval.py", line 269, in evaluate
    scores[hf_subset] = self._evaluate_subset(
  File "/data/niklas/mieb/mteb/mteb/abstasks/Image/AbsTaskAny2AnyRetrieval.py", line 278, in _evaluate_subset
    results = retriever(corpus, queries)
  File "/data/niklas/mieb/mteb/mteb/evaluation/evaluators/Image/Any2AnyRetrievalEvaluator.py", line 290, in _
_call__
    return self.retriever.search(
  File "/data/niklas/mieb/mteb/mteb/evaluation/evaluators/Image/Any2AnyRetrievalEvaluator.py", line 173, in s
earch
    sub_corpus_embeddings = self.model.get_text_embeddings(
  File "/data/niklas/mieb/mteb/mteb/models/vista_models.py", line 130, in get_text_embeddings
    batch_embeddings = self.encode(texts=batch_texts)
  File "/data/niklas/mieb/mteb/mteb/models/vista_models.py", line 121, in encode
    return self.encode_text(texts.to(self.device))
  File "/data/niklas/mieb/mteb/mteb/models/vista_models.py", line 65, in encode_text
    embedding_output = self.bge_embeddings(
  File "/env/lib/conda/gritkto4/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1553, in _wrap
ped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/env/lib/conda/gritkto4/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1562, in _call
_impl
    return forward_call(*args, **kwargs)
  File "/env/lib/conda/gritkto4/lib/python3.10/site-packages/transformers/models/bert/modeling_bert.py", line
 217, in forward
    embeddings += position_embeddings
RuntimeError: The size of tensor a (516) must match the size of tensor b (512) at non-singleton dimension 1

and the below
/opt/conda/conda-bld/pytorch_1724789122112/work/aten/src/ATen/native/cuda/Indexing.cu:1284: indexSelectLargeI
ndex: block: [845,0,0], thread: [126,0,0] Assertion `srcIndex < srcSelectDimSize` failed.
/opt/conda/conda-bld/pytorch_1724789122112/work/aten/src/ATen/native/cuda/Indexing.cu:1284: indexSelectLargeI
ndex: block: [845,0,0], thread: [127,0,0] Assertion `srcIndex < srcSelectDimSize` failed.
 31%|████████████████████▍                                              | 6110/20000 [01:38<03:43, 62.08it/s]
ERROR:mteb.evaluation.MTEB:Error while evaluating InfoSeekIT2ITRetrieval: CUDA error: device-side assert trig
gered
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be
incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Traceback (most recent call last):
  File "/data/niklas/mieb/mteb/scripts/run_mieb.py", line 81, in <module>
    results = evaluation.run(model, output_folder="/data/niklas/mieb/results-mieb-final", batch_size=1)
  File "/data/niklas/mieb/mteb/mteb/evaluation/MTEB.py", line 464, in run
    raise e
  File "/data/niklas/mieb/mteb/mteb/evaluation/MTEB.py", line 425, in run
    results, tick, tock = self._run_eval(
  File "/data/niklas/mieb/mteb/mteb/evaluation/MTEB.py", line 300, in _run_eval
    results = task.evaluate(
  File "/data/niklas/mieb/mteb/mteb/abstasks/Image/AbsTaskAny2AnyRetrieval.py", line 269, in evaluate
    scores[hf_subset] = self._evaluate_subset(
  File "/data/niklas/mieb/mteb/mteb/abstasks/Image/AbsTaskAny2AnyRetrieval.py", line 278, in _evaluate_subset
    results = retriever(corpus, queries)
  File "/data/niklas/mieb/mteb/mteb/evaluation/evaluators/Image/Any2AnyRetrievalEvaluator.py", line 290, in _
_call__
    return self.retriever.search(
  File "/data/niklas/mieb/mteb/mteb/evaluation/evaluators/Image/Any2AnyRetrievalEvaluator.py", line 194, in s
earch
    sub_corpus_embeddings = self.model.get_fused_embeddings(
  File "/data/niklas/mieb/mteb/mteb/models/vista_models.py", line 169, in get_fused_embeddings
    all_embeddings.append(batch_embeddings.cpu())
RuntimeError: CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be
incorrect.
[

also getting this for OVENIT2ITRetrieval ; maybe a problem with our bge implementation

strangely not able to reproduce the error on the two datasets. Can this be transformers and tokenizers version? Looks like it's relevant to max length not truncated.
On my end, I am able to run:
import mteb
model = mteb.get_model(
    "BAAI/bge-visualized-m3"
)
model.get_text_embeddings(texts = ["s"*10000,"s"*1])

with transformers==4.44.2 tokenizers=0.19.1

Hm Im running with the below and still getting the 2nd error with BAAI/bge-visualized-base-base
(/env/lib/conda/gritkto4) niklas@dojo-a3-ghpc-61:/data/niklas/mieb/mteb$ pip show transformers
pip show toName: transformers
Version: 4.46.2
Summary: State-of-the-art Machine Learning for JAX, PyTorch and TensorFlow
Home-page: https://github.com/huggingface/transformers
Author: The Hugging Face team (past and future) with the help of all our contributors (https://github.com/huggingface/transformers/graphs/contributors)
Author-email<EMAIL_ADDRESS>License: Apache 2.0 License
Location: /data/env/lib/conda/gritkto4/lib/python3.10/site-packages
Requires: filelock, huggingface-hub, numpy, packaging, pyyaml, regex, requests, safetensors, tokenizers, tqdm
Required-by: FlagEmbedding, peft, salesforce-lavis, sentence-transformers
k(/env/lib/conda/gritkto4) niklas@dojo-a3-ghpc-61:/data/niklas/mieb/mteb$ pip show tokenizers
Name: tokenizers
Version: 0.20.1
Summary:
Home-page: https://github.com/huggingface/tokenizers
Author: Anthony MOI<EMAIL_ADDRESS>Author-email: Nicolas Patry<EMAIL_ADDRESS>Anthony Moi<EMAIL_ADDRESS>License:
Location: /data/env/lib/conda/gritkto4/lib/python3.10/site-packages
Requires: huggingface-hub
Required-by: transformers


Broken switch case fixer

This should break the fixer:
        switch ($json['type']) {
            case 'zikula-module':
            case 'zikula-theme':
            case 'zikula-plugin':
                break;
            default;

                return false;

maybe put this case in the test of the fixer and into a PR and we all see it break ;)

I didn't have much time so I just dumped it into an issue. Later on, I'll add a test case and look into why it's actually failing.

To put some more valid code:
switch($foo) {
    case '123';
    case '456';
        return 1;
    default;
        return 2;
}

the problem is that case may be followed by ; as well, and we look for : only

can be closed :)

thx


EC3K

Hi SevenWatt,
sorry to bother you, but can any of these be used with a Jeelink v3c (RFM69) to receive EC3K data ?
Thanks in advance!

This implementation is specific for the LPC8xx micro-controllers. It would require some coding in the jeelib environment to get this done. One would need to reinitialize several RFM69 registers to start receiving EC3K. The settings can be taken from this git, file rf69cc.h
Jean-Claude already had a EC3K sketch for the jeenode. With a little adaptation of configuring the RFM69 it should work.
Maybe you can seek help on the jeelabs forum.
SevenW


entity meta data error?

What version of ViaVersion are you using? Type /ver viaversion
0.4.7
What version of Spigot are you using? Type /ver
1.8.8
What plugins are you using? /plugins
Plugins (44): CleanroomGenerator, HubBasics, WorldEdit, HealthBar, SimpleElevator, Essentials, GroupManager, TuxTwoLib, Buycraft, BetterChairs, Lockette, Votifier, LaggRemover, WorldGuard, HugeItems, EssentialsChat, BossBarAPI, EssentialsGeoIP, TimeIsMoney, ViaVersion, CustomJoinItems, GAListener, Vault, RealTime, DrugMeUp, TitleManager, MultiInv, PlotSquared, ProtocolLib, LibsDisguises, AAC, ASkyBlock, ChestCommands, AgarMC, SexyMotd, Autorank, Multiverse-Core, Shopkeepers, GriefPrevention, SkyWarsReloaded, ItemSlotMachine, HolographicDisplays, WarpPortals, InfoBoardReborn
How does this error happen? login? using an item?
Is there an error in the console? Use pastebin.com. Is there a kick message?
http://pastebin.com/PkAYrDb2

Don't use bossbar.

Sure :-)


Rename action to kepler-action

As mentioned in this review comment, here is my suggestion:

I suggest renaming the action to sustainable-computing-io/kepler-action so that it's lowercase, kebab-case, and a bit simplified, to follow the naming pattern of other GitHub Actions such as release-drafter, create-pull-request, etc.

This would require renaming the repo's title and any mentions of the action in this and other repos.
Happy to discuss this further :)

done

@rootfs , I am not sure if we should rename as kepler-action or kepler-k8s-action or k8s-action?
this repo is just a github action for sustainable-computing-io org's repos usage to create k8s cluster in kind for CI usage.
if we name as kepler-action? does it misunderstanding for external user?


Module strawman 3: Implicitly defined imports

Now that #106 is implemented, Wren supports implicitly defined names at the top level. Given that, I think we can use that to simplify how modules could handle circular imports. This proposal would supercede #79, and fix #46.
The basic idea borrows heavily from Python. There, to resolve circular imports, you push some of the imports down later in the file. As long as you don't use the imported modules until after the imports execute, everything works.
Here's an example (as usual, syntax is just made up at this point):
// main.wren
export class Main {
  static inMain {
    IO.print("inMain")
  }
}

import Other
Other.inOther

First, we define a class Main. The export modifier says, "make this object the object exported by this module". In this case the object is the class object for the Main class.
Then we import some object from Other. This defines a top-level variable Other whose value is an object—an instance of some class—exported by the Other module.
Finally, we invoke a method on the object it imported from Other.
Here's the other module:
// other.wren
export class Other {
  static inOther {
    IO.print("inOther")
    Main.inMain
  }
}

import Main

This also exports a class. That defines a static method. In that method, we use Main, which hasn't been defined yet. Since it's a capitalized name, that's OK. It just gets implicitly declared.
After the class body, we execute the import and now Main has a real definition.
Executing this program starting from Main proceeds like so:

Start executing Main.
Define the Main class and store it as the export object for the module.
Get to the import Other statement. Since Other has not been loaded yet, pause executing Main and start loading and executing Other.
Execute the Other class definition and store it as the export object.
Execute the import Main. We've already started loading Main, so look it up and get its current export object. That's the Main class, so we bind Main to the Main class.
Other is done executing, so resume Main.
Get the object exported from Other (the Other class) and bind that to Other in Main.
Execute Other.inOther. We've got a reference to the Other class, so that's fine.
That in turn calls Main.inMain. Likewise, we've got that wired up now too, so it works as well.

Of course, in most cases, you won't have circular dependencies and you can have the imports up at the top where they naturally would go.
The basic pieces we need to support this are:

The VM keeps a map of module names to the previously-loaded code for that module. For each, we also store a reference to the object the module is exporting.

An import statement that loads a module and binds its exported object to a variable. (We don't technically need syntax for this, but it would probably be nice to have.) It needs to be able to pause executing one module while the other module is loaded.

A way to specify which object should be exported from a module. Again, syntax isn't strictly needed, but would probably help.

Unlike #79, this doesn't require any sort of monkey-patching of existing classes, and I think the resulting syntax and semantics are simpler.
Thoughts?

Does this handle duplicate exports, i.e. the Other class is exported from two places?

Yes, it should. Think of it like the distinction between variables and values. A module exports an object, some value in memory. Another module imports that object and binds it to a variable with some name. There's also another "name", which is the identifier you use to specify which module you want to import.
Conceptually, each of these is independent. You could have a module physically stored in foo.wren that exports a class named Bar that you import into a variable in your module named Baz. Of course, we'll have to decide to what degree the syntax lets you control each of these, but in principle they're decoupled.
So, it's entirely possible to have two modules that both export a class whose name happens to be Other. As long as those modules themselves have different ways of being identified/located, it shouldn't cause any problems.

Any update on this and related bugs around importing code? Would love to help where I can to move this along as it'd be really awesome to finally have in Wren :)

No useful update yet. I started tinkering around with it some but I realized it's going to be more complex to implement than I originally thought.
Modules means instead of a single global scope, each module has its own top-level scope distinct from every other modules. That's a key feature, but it makes the implementation harder.
Right now, there are bytecode for loading and storing a global variable. The compiler generates those when it encounters usage of a top-level name. Interpreting those is pretty simple: we just look up the variables by index in the VM's global variable array.
When each module has its own globals, which module we look in depends on where the function being executed was defined. This naïvely means each function would have to have a pointer to its module. I really don't want to add another pointer to functions if I can avoid it since it impacts performance.
Fortunately, functions already have a convenient way to access variables defined outside of their scope: closures! We could just make functions close over the top-level variables they use. They would then end up in the upvalue array like any other outer variable. Swell.
That may have a negative performance impact, but at least it's only in the functions that do actually access top-level stuff. I'd need to experiment to see how bad it is.
But closing over them means a lot of changes in the compiler. What's particularly tricky is figuring out how it interacts with the REPL. Right now, the VM keeps around an array of the names of all global variables. This makes it much easier for the REPL to use variables defined in previous lines of code.
If those become more like regular scoped local variables, the compiler will "forget" about them after it's done compiling a line of code in the REPL, and being able to access them later gets trickier.
I don't think these problems are insurmountable at all, but it's going to be a bit of work, and I have to carve out a larger block of free time for that. Right now, it's easier for me to work on some smaller scale stuff. I totally agree this is hugely important, though.

...and this is done!


Some layers are missing from klayout/sky130.lyp

The following fill layers are missing:
23/28 is fom.fill
28/28 is poly.fill
56/28   li1.fill
36/28   met1.fill
41/28   met2.fill
34/28   met3.fill
51/28   met4.fill
59/28   met5.fill

Hi @urish! I think this belongs in the sky130_klayout_pdk repo. There is already an open issue about the missing layers  and I opened a PR to fix them, although I am not quite sure which naming is correct 🤔


Add Sonos device attribute with grouping information

Description:
This PR replaces the Sonos is_coordinator boolean attribute with a more useful attribute sonos_group that reveals the actual speaker group arrangement.
Related issue (if applicable): suggested in forum
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
BREAKING CHANGE NOTE: The media_player.sonos attribute is_coordinator has been removed; the new attribute sonos_group (listing all group members, coordinator first) can be used instead.
Example template:
This will list the players that used to have is_coordinator == True:
{% for player in states.media_player -%}
{% if player.attributes.sonos_group | first == player.entity_id -%}
{{ player.entity_id }}
{% endif -%}
{% endfor -%}

Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

I think we should implement the group/snapshot feature on core to generalize the handling

So I'm fine with storing this in the state machine. I am a bit confused as to why we would make it more difficult to find who is the coordinator? Isn't it that we can only send commands to the coordinator?

Sending commands to slaves works without this, the platform will redirect the command to the coordinator.
The attribute in this PR was hashed out in this forum thread after the original solution with is_coordinator turned out to not provide enough information for the intended use (building a UI for groups).
I think it is okay to be a bit verbose because it is not used much.


bookmarks-persistence only init.lua

Thanks for this. Do you also have the README and the LICENSE file? At least those would be very important to preserve. The .gitignore would be nice to have, but probably not so important.

nah sorry, I dont git clone, I directly copy the init.lua, sorry

Okay, I'll take it for now. Any preservation effort is good. Thanks so much for sending it here!


Add spacing and background to people.

Adding 10px between all peoples.
adding grey background when unfolded.
removing blue border that appeared when clicked on a person.

We currently don't have the concept of filled out "boxes" (the old website also hadn't any filled out boxes) and I'm not sure how we can keep a "sleek" design.
I'm not sure whether

might look better.
on the old site we had:

So when using the yellow border, the content itself jumped, because the border forces it to rescale a bit. I think the separator line is quite nice? Sorry for the indents !


Document does not match the given filename after replacing the file

Issue Summary
After changing the file of an existing document the given file path via api won't update to the knew destination. And still return the file path of the old file which throws an page not found error with the message: "This document does not match the given filename".
Steps to Reproduce

open the documents tab in wagtail admin and start to edit a existing document
replace the existing file by choose a new file
save the changes
open the file path that is given by the api

Please delete this issue. We found a solution for that.