Unable to pull image by tag v2.11.1: no match for platform in manifest: not found

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
Setting up Dockerfile with latest Traefik image (v2) with release v2.11.1:
Testing with Public ECR:
FROM public.ecr.aws/docker/library/traefik:v2.11.1
Testing with DockerHub:
FROM traefik:v2.11.1
What did you see instead?
Although I'm able to pull the latest v2 Docker image via traefik:v2.11, I'm not able to pull the image via tag v2.11.1.  This is the case for both Dockerhub and AWS Public ECR:
Public ECR:
 > [traefik internal] load metadata for public.ecr.aws/docker/library/traefik:v2.11.1:
------
failed to solve: public.ecr.aws/docker/library/traefik:v2.11.1: no match for platform in manifest: not found

DockerHub:
 > [traefik internal] load metadata for docker.io/library/traefik:v2.11.1:
------
failed to solve: traefik:v2.11.1: no match for platform in manifest: not found

What version of Traefik are you using?
Trying to access v2.11.1
What is your environment & configuration?
# (paste your configuration here)

Add more configuration information here.
If applicable, please paste the log output in DEBUG level
No response

TIL, thank you @ldez!


[ADD] thecage_data: search_default_uninvoiced in booking lines tree view

"Not invoiced" filter shouldn't be by default. It needs to be set optionally.

We need to add  right after <filter name="uninvoiced" ...... />


ARROW-10163: [Rust] [DataFusion] Add DictionaryArray coercion support

This PR  adds:

Basic DictionaryArray coercion (not cast) support in DataFusion
A test in sql.rs demonstrating basic operations using DataFusion on DictionaryArray arrays

Note that the performance operating on DictionaryArrays is likely to leave a lot to be desired -- specifically almost any operation will cause the DictionaryArray to get unpacked to a normal array reducing most/all of any performance gains.
I plan to add additional performance improvements over time -- but I felt getting queries to run was the first important step.

LGTM, there's a comment from Jorge @alamb, let us know if you'd like to address it, otherwise we can merge this

Thanks @nevi-me  -- I responded to @jorgecarleitao  and I have rebased this PR against master. I think it is good to go, but I will wait for @jorgecarleitao 's response


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

AWS CodeBuild CI Report

CodeBuild project: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: bd23960c7ba7a7142397aa9709ce883df7cf0408
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Adding perses minimum spanning graph edges

Fixes #69

While trying to run all the edges in the data set I detected the current issues in some of the targets
Target pfkfb3 references non-existing ligand in edge edge_lig_38_lig_36.
Target pfkfb3 references non-existing ligand in edge edge_lig_54_lig_38.
Target pfkfb3 references non-existing ligand in edge edge_lig_46_lig_24.
Target pfkfb3 references non-existing ligand in edge edge_lig_59_lig_30.
Target pfkfb3 references non-existing ligand in edge edge_lig_53_lig_38.
Target pfkfb3 references non-existing ligand in edge edge_lig_67_lig_24.
Target thrombin references non-existing ligand in edge edge_lig_7a_lig_5.
Target cdk8 references non-existing ligand in edge edge_lig_14_lig_23.
Target cdk8 references non-existing ligand in edge edge_lig_17_lig_23.
Target cdk8 references non-existing ligand in edge edge_lig_42_lig_23.
Target cdk8 references non-existing ligand in edge edge_lig_45_lig_23.
Target cdk8 references non-existing ligand in edge edge_lig_43_lig_23.
Target cdk8 references non-existing ligand in edge edge_lig_44_lig_23.
Target cdk8 references non-existing ligand in edge edge_lig_18_lig_23.
Target p38 references non-existing ligand in edge edge_lig_p38a_3fmk_lig_p38a_2m.
Target tyk2 references non-existing ligand in edge edge_lig_jmc_30_lig_ejm_48.
Target shp2 references non-existing ligand in edge edge_lig_E14_lig_E26.

It's not specially easy from my script which ligands exactly are missing or being referenced in the edges but not in the ligands.sdf. But by just inspection I could check that for tyk2 the ligand lig_jmc_30 doesn't exist in https://github.com/openforcefield/protein-ligand-benchmark/blob/issues_75_and_81/data/tyk2/02_ligands/ligands.sdf (this is the revision for the latest changes with fixes).
Hence it does seem that there are some edges referencing ligands that do not exist in the latest revision for https://github.com/openforcefield/protein-ligand-benchmark/pull/82 . Now, I see some ligands.sdf were changed in that PR, so it might be that the network of transformations just needs to be updated with the changes on that branch/revision.

@ijpulidos - Am I correct in understanding you're using the new graph edges from this PR but applying it to the branch from #82?
If that's the case then it's partly expected, once #82 is merged then I'll re-generate the edges here to match that (I didn't want to make this depend on the other branch if we're going to squash merge things).

@ijpulidos - Am I correct in understanding you're using the new graph edges from this PR but applying it to the branch from #82?

Yes, I merged both branches because I needed the changes in both for my test to make sense.

If that's the case then it's partly expected, once #82 is merged then I'll re-generate the edges here to match that (I didn't want to make this depend on the other branch if we're going to squash merge things).

Alright! That sounds good to me. My test will still check things run on perses, so this is not a blocking issue. I just wanted to mention it in case we weren't expecting it. All good!

Actually, on a second thought, I realize that we do need the branches to be merged for me to be able to test this correctly, since the data for the edges and the ligands is correlated.

Ready for review!

@IAlibay please merge when satisfied! Thanks!

From @IAlibay : not getting minimum-spanning graphs from perses, but starmaps instead. Can't use latest perses since it doesn't have openff-toolkit 0.11.0 support.

From @IAlibay : not getting minimum-spanning graphs from perses, but starmaps instead. Can't use latest perses since it doesn't have openff-toolkit 0.11.0 support.

On my side of things I also need to work out what was happening with the 0.4 version of openfe (which works with off-tk 0.10.x), e.g. if it's an issue about how we're ingesting perses score.

Blocked by: https://github.com/choderalab/perses/pull/1128

Just FYI. From today's meeting I would be trying to merge the directory structure from this PR to the main branch, such that we can continue working on the transformation networks with the correct directory structure.

The idea is that we would be dropping the current edges yaml file in this PR and just leave the directories for @IAlibay and other to build on top of it from the main branch.

Actually, I think I prefer to have some edges files merged, even if they are really bad ones. Because that way we can still run the simulations against this branch or the main one with he same scripts, and it would also give us placeholders that we can use for future PRs, whereas if we leave the directories empty they won't even appear in the repo. I am going to revert the latest commit for now, such that we can still use this branch for some benchmarks if needed. @IAlibay thoughts?

Actually, I think I prefer to have some edges files merged, even if they are really bad ones. Because that way we can still run the simulations against this branch or the main one with he same scripts, and it would also give us placeholders that we can use for future PRs, whereas if we leave the directories empty they won't even appear in the repo. I am going to revert the latest commit for now, such that we can still use this branch for some benchmarks if needed. @IAlibay thoughts?

Yeah sure, I think that makes sense.


use gain for sklearn feature_importances_

gain is a better feature importance criteria than the currently used weight. I have updated the XGBModel class with a importance_type parameter which is gain by default and instantiating an instance with importance_type of weight gives the original behaviour.

[x] fix tests
[x] perhaps add an option to select importance type

@kashif yes please! Thanks! 🙇


add round trip testing for all column types (postgres module)

This should use zio-sql to insert values into the database, then read them back out, and ensure they're the same as the ones that went in.
This is dependent on InsertModule.

Types that we are inserting to db and types that we are reading back are depending on the description of the table. If metamodel is wrongly defined, inserts and read fail at runtime. @robmwalsh  Can you please clarify what this would test?


[Question] - Unable to deploy - aries-mediator-proxy

I'm unable to deploy aries-mediator-proxy.  Attaching the logs below. Not sure what it is complaining about.

Proxy Logs
{"level":"info","ts":1667960581.3709834,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
{"level":"warn","ts":1667960581.372367,"msg":"Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
{"level":"info","ts":1667960581.3740005,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//<IP_ADDRESS>:2019"]}
{"level":"info","ts":1667960581.374437,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00077a930"}
{"level":"info","ts":1667960581.374893,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/data/caddy"}
{"level":"info","ts":1667960581.3749568,"logger":"tls","msg":"finished cleaning storage units"}
{"level":"info","ts":1667960581.3750381,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
{"level":"info","ts":1667960581.3751032,"logger":"http.log","msg":"server running","name":"srv1","protocols":["h1","h2","h3"]}
{"level":"error","ts":1667960581.3751423,"msg":"unable to autosave config","file":"/config/caddy/autosave.json","error":"open /config/caddy/autosave.json: permission denied"}
{"level":"info","ts":1667960581.3751543,"msg":"serving initial configuration"}
{"level":"error","ts":1667960611.3367467,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"51760","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.002791207,"status":502,"err_id":"a5gu6wqan","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960611.336786,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"51760","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.002791207,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960641.3367486,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"52220","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.002910097,"status":502,"err_id":"j4ii4tiwn","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960641.3367574,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"52218","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.002900021,"status":502,"err_id":"4k32smfrh","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960641.3367925,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"52220","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.002910097,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960641.3368034,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"52218","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.002900021,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960671.3367636,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"52762","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"Accept":["*/*"],"Connection":["close"],"User-Agent":["kube-probe/1.21"]}},"duration":3.002604068,"status":502,"err_id":"ab77eu2xn","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960671.336799,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"52762","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.002604068,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960701.334774,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"53224","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.000633547,"status":502,"err_id":"vjut971d1","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960701.3348262,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"53224","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.000633547,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960701.3349478,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"53222","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.000792186,"status":502,"err_id":"zmxen47pn","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960701.334985,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"53222","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.000792186,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960731.336322,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"53760","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.002089469,"status":502,"err_id":"wfxbz77j4","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960731.3363717,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"53760","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"Connection":["close"],"User-Agent":["kube-probe/1.21"],"Accept":["*/*"]}},"user_id":"","duration":3.002089469,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960761.3362923,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"54218","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"Connection":["close"],"User-Agent":["kube-probe/1.21"],"Accept":["*/*"]}},"duration":3.002885291,"status":502,"err_id":"t21in3ee3","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960761.3363373,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"54218","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.002885291,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960761.3365238,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"54220","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.002883255,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960761.3362923,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"54220","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"Accept":["*/*"],"Connection":["close"],"User-Agent":["kube-probe/1.21"]}},"duration":3.002883255,"status":502,"err_id":"bisb9ahi8","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960791.3352334,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"54732","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.000914276,"status":502,"err_id":"e57qhk1rb","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960791.3352768,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"54732","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.000914276,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960821.337624,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"55210","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.003094166,"status":502,"err_id":"rr7yyvbfy","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960821.3376474,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"55208","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.003104326,"status":502,"err_id":"fy5b7v17x","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960821.3376758,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"55210","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"Connection":["close"],"User-Agent":["kube-probe/1.21"],"Accept":["*/*"]}},"user_id":"","duration":3.003094166,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960821.3376803,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"55208","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"Accept":["*/*"],"Connection":["close"],"User-Agent":["kube-probe/1.21"]}},"user_id":"","duration":3.003104326,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960851.3478,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"55716","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.001954389,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960851.3477511,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"55716","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.001954389,"status":502,"err_id":"yrhqcp88m","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960881.3367229,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"56198","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.002927889,"status":502,"err_id":"r66nzx0qx","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"error","ts":1667960881.3367736,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"56198","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.002927889,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960881.3368516,"logger":"http.log.access.log0","msg":"handled request","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"56200","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"user_id":"","duration":3.002854863,"size":0,"status":502,"resp_headers":{"Server":["Caddy"]}}
{"level":"error","ts":1667960881.3367226,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"56200","proto":"HTTP/1.1","method":"GET","host":"<IP_ADDRESS>:4000","uri":"/","headers":{"User-Agent":["kube-probe/1.21"],"Accept":["*/*"],"Connection":["close"]}},"duration":3.002854863,"status":502,"err_id":"pynfpgpg2","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}
{"level":"info","ts":1667960881.354809,"msg":"shutting down apps, then terminating","signal":"SIGTERM"}
{"level":"warn","ts":1667960881.3548503,"msg":"exiting; byeee!! 👋","signal":"SIGTERM"}
{"level":"info","ts":1667960881.3550413,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc00077a930"}
{"level":"info","ts":1667960881.355158,"logger":"admin","msg":"stopped previous server","address":"localhost:2019"}
{"level":"info","ts":1667960881.3551738,"msg":"shutdown complete","signal":"SIGTERM","exit_code":0}

ConfigMap -> caddy-conf
kind: ConfigMap
apiVersion: v1
metadata:
  name: caddy-conf
  namespace: mediator-dev
  uid: 0a7613c2-b2ec-42ca-b994-9d9f4b2f1a4a
  resourceVersion: '1274316675'
  creationTimestamp: '2022-11-09T02:08:27Z'
  managedFields:
    - manager: Mozilla
      operation: Update
      apiVersion: v1
      time: '2022-11-09T02:08:27Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:data':
          .: {}
          'f:Caddyfile': {}
          'f:example.property.1': {}
          'f:example.property.2': {}
          'f:example.property.file': {}
data:
  Caddyfile: |-
    :{$CADDY_AGENT_HTTP_IN_PORT} {
        @websockets {
            header Connection *Upgrade*
            header Upgrade websocket
        }

        handle @websockets {
            reverse_proxy http://{$AGENT_HOST}:{$MEDIATOR_AGENT_WS_IN_PORT}
        }

        handle {
            reverse_proxy http://{$AGENT_HOST}:{$MEDIATOR_AGENT_HTTP_IN_PORT}
        }

        log {
                # errors stdout
                output stdout
                # format single_field common_log
                level DEBUG
        }
    }
    :{$CADDY_AGENT_ADMIN_IN_PORT} {

        handle {
            reverse_proxy http://{$AGENT_HOST}:{$MEDIATOR_AGENT_HTTP_ADMIN_PORT}
        }

        log {
                # errors stdout
                output stdout
                # format single_field common_log
                level DEBUG
        }
    }

It looks like the readiness and and liveness probes are causing the proxy to terminate.  To debug try removing them and see if the proxy stays running.  https://github.com/bcgov/openshift-aries-mediator-service/blob/main/openshift/templates/aries-mediator-proxy/aries-mediator-proxy-deploy.yaml#L164-L179
If it stays running at that point there is an issue with your mediator agent, such as it's not running.  The default route for the proxy is to the agent.  The proxy's readiness and and liveness probes depend on the agent responding with a 200 success code.  To make this dependency a little more explicit you could change the probes to call the health endpoints on the agent like this; https://github.com/bcgov/dts-endorser-service/blob/main/openshift/templates/aries-endorser-proxy/aries-endorser-proxy-deploy.yaml#L199-L214

After removing the readiness & liveness probes, the proxy stays up and running. And, I don't see any issues with the agent either. I was able to port-forward and access the HTTP & WS endpoints. I can't figure out why the proxy is not able to talk to the agent pod. Also, I think it's worth mentioning I had to manually create the ConfigMap - caddy-conf. The template does not create them. I am not sure if I am missing anything. :(
Here is what we have so far:
Pods:
NAME                            READY   STATUS      RESTARTS   AGE    IP             NODE                     NOMINATED NODE   READINESS GATES
aries-mediator-agent-1-6hglx    1/1     Running     0          22h    <IP_ADDRESS>   ext-8pnxv-worker-pp4mj   <none>           <none>
aries-mediator-db-1-trjr8       1/1     Running     0          46h    <IP_ADDRESS>   ext-8pnxv-worker-pp4mj   <none>           <none>
aries-mediator-proxy-2-6s7bm    1/1     Running     0          22h    <IP_ADDRESS>   ext-8pnxv-worker-pp4mj   <none>           <none>

SVC:
NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE    SELECTOR
aries-mediator-agent   ClusterIP   <IP_ADDRESS>   <none>        3002/TCP,3000/TCP,3001/TCP   39h    name=aries-mediator-agent
aries-mediator-db      ClusterIP   <IP_ADDRESS>     <none>        5432/TCP                     2d1h   name=aries-mediator-db
aries-mediator-proxy   ClusterIP   <IP_ADDRESS>     <none>        4000/TCP,4002/TCP            41h    name=aries-mediator-proxy

Routes:
NAME                         HOST/PORT                                               PATH   SERVICES               PORT                         TERMINATION     WILDCARD
aries-mediator-proxy         aries-mediator-agent-dev.xxx.xxx.novascotia.ca                aries-mediator-proxy   aries-mediator-proxy         edge/Redirect   None
aries-mediator-proxy-admin   aries-mediator-agent-admin-dev.xxx.xxx.novascotia.ca          aries-mediator-proxy   aries-mediator-proxy-admin   edge/Redirect   None

ConfigMap:
NAME                                DATA   AGE
aries-mediator-agent-2-ca           1      40h
aries-mediator-agent-2-global-ca    1      40h
aries-mediator-agent-2-sys-config   0      40h
aries-mediator-db-3-ca              1      2d1h
aries-mediator-db-3-global-ca       1      2d1h
aries-mediator-db-3-sys-config      0      2d1h
caddy-conf                          1      39h

Proxy Logs:
{"level":"error","ts":1668083993.8181558,"logger":"http.log.error.log0","msg":"dial tcp <IP_ADDRESS>:3000: i/o timeout","request":{"remote_ip":"<IP_ADDRESS>","remote_port":"38476","proto":"HTTP/1.1","method":"GET","host":"aries-mediator-agent-dev.xxx.xxx.novascotia.ca","uri":"/","headers":{"Forwarded":["for=<IP_ADDRESS>;host=aries-mediator-agent-dev.xxx.xxx.novascotia.ca;proto=https"],"Upgrade-Insecure-Requests":["1"],"Accept":["text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9"],"Accept-Language":["en-CA,en;q=0.9,en-GB;q=0.8,en-US;q=0.7,fr;q=0.6"],"X-Forwarded-Proto":["https"],"X-Forwarded-Host":["aries-mediator-agent-dev.xxx.xxx.novascotia.ca"],"Sec-Ch-Ua":["\"Google Chrome\";v=\"107\", \"Chromium\";v=\"107\", \"Not=A?Brand\";v=\"24\""],"Sec-Ch-Ua-Mobile":["?0"],"Sec-Ch-Ua-Platform":["\"macOS\""],"User-Agent":["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"],"Accept-Encoding":["gzip, deflate, br"],"X-Forwarded-Port":["443"],"Dnt":["1"],"Sec-Fetch-Mode":["navigate"],"Sec-Fetch-User":["?1"],"Sec-Fetch-Dest":["document"],"Sec-Fetch-Site":["same-site"],"X-Forwarded-For":["<IP_ADDRESS>"]}},"duration":3.003224416,"status":502,"err_id":"sgjhdnpyq","err_trace":"reverseproxy.statusError (reverseproxy.go:1272)"}

Ok turns out the network policy was actually blocking the requests. When I removed them the request was able to get through.

Good find.  Sorry I did not get back to you yesterday.  All good now?

@WadeBarnes  - Oh no worries at all Wade. I know you have a million things going on there. I appreciate all your responses. I got everything working now. Let me know if you want me to submit a pull request for creating the configMap as part of the template. I certainly can.
On a completely side note - Currently, the mediator service is running in "Auto-Accept" mode. It generates a new token/invitation URL every time the agent is restarted. This is causing the wallet to lose the connection to the mediator service. Then I have to manually update the new MEDIATOR_URL in the wallet to re-establish the connection.  I am wondering how to make the wallet and mediator service always stay connected.
.env
MEDIATOR_URL=[https://myapp.mydomain.ca?c_i=eyJAdHlwZSI6Imh0dHBzOi8vZGlkY29tbS5vcmcvY29ubmVjdGlvbnMvMS4wL2ludml0YXRpb24iLCJAaWQiOiIwODI2NDliNC0zODdhLTRhZTctYTExYi1lOTJlMTQzOTkwYTQiLCJyZWNpcGllbnRLZXlzIjpbIkdYNlNyM0RKYmRKNm1DODJQNU5ZS1ZjSGhpMTQ0eDNFVXZkZjFubmYyQVprIl0sInNlcnZpY2VFbmRwb2ludCI6Imh0dHBzOi8vYXJpZXMtbWVkaWF0b3ItYWdlbnQueHh4Lnh4eC54eHh4IiwibGFiZWwiOiJNZWRpYXRvciIsImFsZyI6IkhTMjU2In0](https://myapp.mydomain.ca/?c_i=eyJAdHlwZSI6Imh0dHBzOi8vZGlkY29tbS5vcmcvY29ubmVjdGlvbnMvMS4wL2ludml0YXRpb24iLCJAaWQiOiIwODI2NDliNC0zODdhLTRhZTctYTExYi1lOTJlMTQzOTkwYTQiLCJyZWNpcGllbnRLZXlzIjpbIkdYNlNyM0RKYmRKNm1DODJQNU5ZS1ZjSGhpMTQ0eDNFVXZkZjFubmYyQVprIl0sInNlcnZpY2VFbmRwb2ludCI6Imh0dHBzOi8vYXJpZXMtbWVkaWF0b3ItYWdlbnQueHh4Lnh4eC54eHh4IiwibGFiZWwiOiJNZWRpYXRvciIsImFsZyI6IkhTMjU2In0)

Glad you got everything working.  The configMap gets autogenerated by the aries-mediator-proxy-deploy.overrides.sh script as part of the lifecycle of genDepls.sh if you use the openshift-developer-tools to manage the configurations as mentioned here.

@jleach, @wadeking98, Do either of you have any advice on the wallet-mediator connection question?

On a completely side note - Currently, the mediator service is running in "Auto-Accept" mode. It generates a new token/invitation URL every time the agent is restarted. This is causing the wallet to lose the connection to the mediator service. I have to manually update the new MEDIATOR_URL in the wallet to re-establish the connection. I am wondering how to make the wallet and mediator service always stay connected.

@WadeBarnes - Maybe it was something related to an earlier Ngrok connection that was causing the wallet to disconnect. After doing a fresh build of the wallet + mediator (openshift hosted). The wallet and mediator stayed always connected. Even when the mediator was restarted the wallet was able to connect once the mediator came back up.
Thank you for all the help!!


Bing Maps imagerySets AerialWithLabels and Road are deprecated

Making a note of this since I happened to stumble across this.
https://msdn.microsoft.com/en-us/library/ff701716.aspx

AerialWithLabels (Deprecated): Aerial imagery with a road overlay, using the legacy static tile service. This service is deprecated and current data will not be refreshed. New applications should instead use AerialWithLabelsOnDemand.

Road (Deprecated): Roads without additional imagery, using the legacy static tile service. This service is deprecated and current data will not be refreshed. New applications should instead use RoadOnDemand.

I quickly tested locally and simply changing the imagerySet string (which is taken from the values of the BingMapsStyle enum) works correctly.  I have not done any side-by-side comparisons.

@mramato and @OmarShehata

Is this why click "Bing Maps Road" in this Sandcastle is failing to load? @mramato
https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/?src=Imagery Layers Manipulation.html

I might be having a similar issue. Bing Aerial displays with a cesium key but Bing Aerial wihth Labels On Demand and Road On Demand don't. Was there any further discussion on this? I couldn't find anything more. Maybe you can point me in the right direction? Thanks!

There's actually a bug in that demo.  Cesium does not ship with a Bing key so you can't use Bing directly, it has to be via the ion asset identifier. If you have your own Bing key, everything works fine.  If you load Bing via ion, it also works fine.
I was about to write up an issue, but it turns out we have one #7524, I'll bump it and hopefully someone will get to it.


Fixed aspect ratio on client images

https://trello.com/c/vUDG21oI/105-clients-area-firefox

:+1:


[Bug] [connector-jdbc] ChunkSplitter class generateSplits method: The catalogTable in the JdbcSourceTable table object does not obtain the primary key

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
debug find that method [getCatalogTable(ResultSetMetaData metadata,BiFunction<ResultSetMetaData, Integer, Column> columnConverter,String sqlQuery)):CatalogTable]
The TableSchema in the created CatalogTable object does not assign a PrimaryKey object value, resulting in the ChunkSplitter class generateSplits method JdbcSourceTable object having no primary key value

SeaTunnel Version
2.3.8
SeaTunnel Config
env {
  job.mode = BATCH
  job.name = "SeaTunnel"
  spark.executor.instances = 1
  spark.executor.cores = 1
  spark.executor.memory = "1g"
  spark.master = local
}

source{
jdbc {
  driver = "com.mysql.cj.jdbc.Driver"
  url = "jdbc:mysql://xxxxxx:3307/xxxxx?useUnicode=true&characterEncoding=UTF-8&allowMultiQueries=true&autoReconnect=true&useSSL=false"
  user = "xxxxxxx"
  password = "xxxxxxxx"
  query = "select id,xxxx from xxx.xxxxxxx"
#   partition_column = "id"
  split.size = 8096
 }
}
transform {
}
sink {
  Console {
      parallelism = 2
    }
}

Running Command
seatunnel-spark-connector-v2-example
SeaTunnelApiExample class

Error Exception
no exception

Zeta or Flink or Spark Version
spark
Java or Scala Version
java 1.8
scala 2.11.12
Screenshots

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Not use query = "select id,xxxx from xxx.xxxxxxx", use table_path


refactor null safety http method resolving for non standard method

There was a null unsafely execution in process of mapping org.springframework.http.HttpMethod to io.netty.handler.codec.http.HttpMethod. The case is to proxy non standard methods (like PROPFIND or custom).  Execution of request.getMethod().toString() for http method which is not value of org.springframework.http.HttpMethod enum produces NullPointerException in cause of request.getMethod() returns null.
This fix should help to prevent such cases.

@artemMartynenko Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@artemMartynenko Thank you for signing the Contributor License Agreement!

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@4f34127). Click here to learn what that means.
The diff coverage is 60%.

@@            Coverage Diff            @@
##             master     #741   +/-   ##
=========================================
  Coverage          ?   69.18%
  Complexity        ?      969
=========================================
  Files             ?      134
  Lines             ?     3927
  Branches          ?      277
=========================================
  Hits              ?     2717
  Misses            ?     1062
  Partials          ?      148

Impacted Files
Coverage Δ
Complexity Δ

...ework/cloud/gateway/filter/NettyRoutingFilter.java
90.62% <60%> (ø)
16 <1> (?)

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 4f34127...7137414. Read the comment docs.


Fix versions storing attributes as nil while manually creating a version

Fixes #1047
The @record.attribute_before_last_save(attr_name.to_s) is giving me nil but if I try @record.attribute_was('name') in my console it gives me the correct value of the record. Adding @record.attribute_in_database(attr_name.to_s) worked for me.

Hi Abhinav, thanks for the contribution.

Tests are failing.
Please add new test(s) for your changes.

Hi Abhinav, are you still working on this? Want me to keep it open?

This solution does pass the existing tests. Please:

Fix the linter offense
Add at least one new test specific to https://github.com/airblade/paper_trail/issues/1047
Add an entry to the changelog under 9.0.0 -> Fixed

Thanks!

Closing due to inactivity, and does not pass CI.

Fixed by https://github.com/airblade/paper_trail/pull/1060, will release as 9.0.0.


Added possibility to exclude items in search results

One thing that bothered me a bit is the disconnection between common.js and builder.js. Specifically for displaying an item row. It's a bit awkward as now the excluded state has to be passed onto common.js, that should technically not have to know about it.

regarding common.js, I think you shouldn't push the "exclude state" to it.
The methods to display items in common.js are the part that are common to all pages of FFBE Equip. There are use in the Encyclopedia and in the item inventory. Only changes that should be put there are changes intended to impact all those pages.
You can take a look at the getItemLine function of builder.js. It is the function used to display the build lines. It uses the methodes from common.js for the shared column type (like image and name columns), but adds its own column before them for the various buttons on the left.


Fixes for #34 and #39

Implemented a shutdown mechanism as Poison Pill
Made all threads shut down slowly and cleanly when calling shutdown

This includes making the Query Thread run as daemon thread to keep him out of the shutdown process
Cleaned up Program by allowing the injection of ChatInterface (which has to be logged in already)
Updated gitignore a little to accomodate javadoc zip-files

This will have to wait until #35 and #36 are integrated into master
Additionally I have  some more rather minor changes for a later pull-request in stash

After clearing this with Uni, I've decided to adapt this to the latest changes by Michael. Then a review will follow

http://chat.stackoverflow.com/transcript/message/21278153#21278153


Use Zendesk for support tickets [DO NOT MERGE Karl to create new agents]

This PR removes the current Deskpro integration, switching to use Zendesk instead, in line with the 'GDS Way'. It does include support to be able to determine whether the ticket creation process was a success or not, so that we have the option to indicate this to the user after they hit submit (the current code doesn't tell the user if a problem occurred, the new code continues doing this).

Ship it 🚢


Add a LICENSE

This project is public but does not have any LICENSE.
I propose to use the MIT one like for the other Nexylan's public projects.
I'll make a PR if you agree.

Agreed


Broken links

There are a number of broken links, including:

https://sci-data.greensoftware.foundation/

referenced from the en and ko landscape pages. What should we replace that link with? Maybe: https://greensoftware.foundation/articles/software-carbon-intensity-sci-specification-project?

All links in website pages are now valid, except for the one mentioned in the opening comment above. Someone from the TAG will need to confirm what the replacement link should be.

Good catch! cc @catblade


starter template index.html has incorrect materialize.js reference

Directory issue
The script calls at the bottom has the incorrect directory for materialize.js. It should be updated to
js/materialize.js
Materialize.js
Needs added function call for sidenav support.

Fixed in 0e8955b


Api call that uses mongomock causes 500 INTERNAL SERVER ERROR but works with Mongodb

The following code causes an error when using mongomock, but not when using mongodb:
    result = self.logs_engine.LogCollection.objects(
        __raw__={'app_id': app_id, "results": {
    "$gt": [{"$size": "results"}, 0]}}).only(
        "user_input", "app_id", "results", "date_time")
    **print(result)**

The error is: TypeError: '>' not supported between instances of 'dict' and 'dict'

Hi @daniellepintz , your code contains a lot of keywords I'm not familiar with that are probably linked to your own framework (LogCollection, objects, 'app_id). Can you try to untangle it and give an example that would illustrate the issue with a direct call to pymongoormongomock` please? Alternatively can you give us more details on what LogCollection is?

OK got it, I think you are using mongoengine and that the equivalent is simply:
db.a.find({
  "app_id": app_id,
  "results": {
    "gt": [{"$size": "results"}, 0],
  }
})

And I was indeed able to reproduce having an error in mongomock but not using pymongo + MongoDB.

Note that the initial query probably does not work as the author intended: the $size is not computed as an operator at all, however it should not crash. Working on a fix.

A more legitimate use of a query that indeed fail would be:
db.a.insert_many([
 {'_id': 1, 'field': {'subfield': 1}},
 {'_id': 2, 'field': {'subfield': 2}},
])

db.a.find({'field': {'$gt': {'subfield': 1}}})

In pymongo + MongoDb, this returns the second element, whereas it crashes today with mongomock.

Thanks so much for the fix!


Check ResolvedRefs condition in Gateway conformance tests

What type of PR is this?

/kind test
/area conformance
What this PR does / why we need it:
Checks the ListenerConditionResolvedRefs value. This is needed to ensure that its value is always set, no matter if the ConditionStatus is true, or false.
Which issue(s) this PR fixes:

Fixes #1315
Does this PR introduce a user-facing change?:

None

/ok-to-test

/cc

I might be missing something, but if are adding these conditions here and not changing https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/utils/kubernetes/helpers.go#L708-L711
It must say that either our tests fail now or this change will cause them to fail.
What am I missing?

The check only asserts on conditions explicitly listed in the test, so the existing or missing ResolvedRefs condition was ignored

The check only asserts on conditions explicitly listed in the test, so whether existing or missing, the ResolvedRefs condition was ignored

But it looks like it compares the number of actual conditions vs the expected conditions before.
So if we add another condition the length should be different

The check only asserts on conditions explicitly listed in the test, so whether existing or missing, the ResolvedRefs condition was ignored

But it looks like it compares the number of actual conditions vs the expected conditions before. So if we add another condition the length should be different

Have a look at https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/utils/kubernetes/helpers.go#L721
Only if the number of expected conditions is larger than the actual the test will fail.
Up until now, the number of expected was lower, hence the tests passed.
Right now we are adding another condition, which should have already been in the actual conditions list (this is what the modification is verifying). So, len(actual) will equal len(expected) at most, and if not - the test should fail

Right, thats what I was missing, long day ...😅
Thanks!
/lgtm

/assign @sunjayBhatia

/cc

Thanks for this PR @levikobi!
I think we should check that all the gateways used in the tests have actually set such a condition to true (Even the gateways used in the HTTPRoute tests). To do so, we could change this helper to check that the resolvedRefs is enforced as well.

That's a great suggestion, thanks @mlavacca!

/unhold

Thanks @levikobi!
/lgtm


ContentDialog example using XAML

Issue type
sample request
Which version of the app?
WinUI 3 Gallery
Description
There used to be an example of using a ContentDialog defined with XAML.
Now there is only one example that creates a ContentDialog entirely in code.
Please add back the ContentDialog XAML example. It is instructive and important for people to see that it can be done.
Screenshots
No response
Windows version
Windows 11 22H2 (22621)
Additional context
No response

Version 1.3.15 has some XAML:
<Page
    x:Class="AppUIBasics.ControlPages.ContentDialogContent"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">

    <StackPanel VerticalAlignment="Stretch" HorizontalAlignment="Stretch">
        <!-- Content body -->
        <TextBlock Text="Lorem ipsum dolor sit amet, adipisicing elit." TextWrapping="Wrap" />
        <CheckBox Content="Upload your content to the cloud."/>
    </StackPanel>

</Page>

Does that suffice?

Close. :) See: https://github.com/microsoft/WinUI-Gallery/blob/main/WinUIGallery/ControlPages/ContentDialogExample.xaml


Linux shell commands not working on remote VM

Bug: Notebook Editor, Interactive Window, Python Editor cells

Steps to cause the bug to occur

Connect to a remote linux VM

Actual & Expected behavior
Expected: !ls lists the files in the images folder
Actual:

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running:                       Remote
Extension version:                               2019.10.41019
VS Code version:                               1.39
Setting python.jediEnabled:               false
Python and/or Anaconda version:     3.6
OS:                                                     Remote: Linux, Local: Windows
Virtual environment:                         N/A.

Developer Tools Console Output

What is the remote server you're attached to? That command works on my local machine.

Hm interesting, this is on a Linux (Ubuntu 16.04) DSVM

Katherine, please setup a machine that demos this. We can take a look. Doesn't seem like something we can fix.


Login not working anymore

YASB (First Edition) Bug Report
This bug report filer is for First Edition X-Wing only!
Note: If you are experiencing problems with the permalink URL when you have Maul or Bomblet Generator in your list, this is a known issue.  For more information please see https://www.reddit.com/r/XWingTMG/comments/7c4q6h/yet_another_squad_builder_problems_with_maul/
Expected Behavior
Login process starting via facebook, or else
Actual Behavior
Login not working anymore, no reaction at all
Language
german, english

Duplicate of #608
Still not able to figure out why this is happening.


[SPARK-47435][SQL] Fix overflow issue of MySQL UNSIGNED TINYINT  caused by SPARK-45561

What changes were proposed in this pull request?

SPARK-45561 mapped java.sql.Types.TINYINT to ByteType in MySQL Dialect, which caused unsigned TINYINT overflow. As regardless of signed or unsigned types, the TINYINT is used for java.sql.Types.
In this PR, we put the signed info into the metadata for mapping TINYINT to short or byte.
Why are the changes needed?

bugfix
Does this PR introduce any user-facing change?

Uses can read MySQL UNSIGNED TINYINT values after this PR like versions before 3.5.0 which has breaked since 3.5.1
How was this patch tested?

new tests
Was this patch authored or co-authored using generative AI tooling?
no

Thank you @dongjoon-hyun. Yes, this is a 3.5.1 regression.

Merged to master.
Could you make a backporting PR, @yaooqinn ?

Thank you, @yaooqinn and @cloud-fan .

Thank you, @dongjoon-hyun and @cloud-fan . I will make a backport


Update guide installation command for v4

The command is copied from
https://github.com/labstack/echo#installation

Completes updated versions in PR #144 and #137. Thanks!


Bug: kube-rbac-proxy is not pulled from quay.io

Contact Details
<EMAIL_ADDRESS>Describe bug
Hi,
The  kube-rbac-proxy is pulled from grc.io/kubebuilder/. In our semi restricted environment "grc.io/kubebuilder/" is not enabled at the moment. This breaks the update to operator version 0.5.1.
Is it possible to use a kube-rbac-proxy hosted on quay.io instead. for example https://quay.io/repository/redhat-cop/kube-rbac-proxy ?
Best  Regards,
Thomas
What happened?
Upgrade to 0.5.1 not possible
Failed to pull image "gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0": rpc error: code = Unknown desc = Source image rejected: Running image docker://gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0 is rejected by policy.
OADP Version
0.5.x (Stable)
OpenShift Version
4.8
Velero pod logs
No response
Restic pod logs
No response
Operator pod logs
No response
New issue

[X] This issue is new

I believe that this will be fixed in the next release of OADP as we actually don't need kube-rbac-proxy, it was added erroneously.
removing it here: https://github.com/openshift/oadp-operator/pull/504


Make OmniBase and STS work with Unicode strings

Omnibase and STS will need some work to fix them up to work with UTF
encoded strings. I'm not sure that anyone is using STS, but if you are
hopefully you will be motivated to fix it.
OmniBase and STS were removed in:
19fba6804f8aa964e15b1dee8258f89cf6a675db

I think these should be hosted externally, if anybody wants to fix them up and keep them them going. I'll be deleting them out of the main Dolphin repo at some point.

To the extent anyone remembers, what are the actual issues with STS/OmniBase in Dolphin 7.1? I was able to revert the removal, boot an image, create a repository, and everything seems to work as normal. I saved a method with non-ASCII characters in the source and that worked fine, and was able to version and compare packages as well. I guess I can imagine reading from a repository created by an older version of Dolphin and containing methods with non-ASCII characters in the source being a problem, since they would have been in ANSI format, but that can be worked around.

I don't recall whether it was real or imagined. If it works, great, but it should be put in a separate repo.

Ok, i just replay @blairmcg comments on 19fba6804f8aa964e15b1dee8258f89cf6a675db
So if there is no problem with OmniBase and STS it will be cool to have them in a separate repo


Web sites behind proxy companion

I need some help to understand the entire system here.
I understand that the front-end is the proxy companion and behind are the the other web sites. As example is docker-wordpress-letsencrypt.

How do I setup 2 web sites?
Do I use a directory for each web site with a docker-compose.yml customized for each web site? That would make the .env clear for each site. Or do I use one docker-compose.yml for all web sites and add sections for each web site (services)?
What is the best directory structure for multiple web sites? I am thinking on backup, or moving to other hosts.

I have my web sites now running with nginx. These are web sites with different domain names, for which I do have different nginx config files. Some of the sites use authentication and some have a connection to a trading bot or chat bot, where I listen for incoming information.

How is the link between the proxy companion and the web site. I assume with:
networks: default:    name: ${NETWORK}

Can anybody help, please?

I will post a video soon on that... but basically you can check the repo wordpress... it should be on folder/repo for each site, change settings in env file and service name in the docker-compose file.

@Elmit2015 As I understand it:
How do I setup 2 web sites?

Do I use a directory for each web site with a docker-compose.yml customized for each web site?
Yes.  For a two-site setup, I have three folders each with docker-compose.yml.  Two for the websites, one for nginx-proxy (a fork of this repository in case I make changes)

What is the best directory structure for multiple web sites? I am thinking on backup, or moving to other hosts.
As I use three separate folders/repositories, the directory structure looks something like this in production:

/home/foo
|__ website1.com
|__ website2.com
|__ nginx-proxy

I have my web sites now running with nginx. These are web sites with different domain names, for which I do have different nginx config files. Some of the sites use authentication and some have a connection to a trading bot or chat bot, where I listen for incoming information.

Not a problem.  In website1.com and website2.com, set the VIRTUAL_HOST to match the domain name of the website.  If you happen to be running subdomains or multiple domains pointing to the same instance, I can't help you there.

How is the link between the proxy companion and the web site?

nginx-proxy creates a separate docker network when you run ./start.sh.  The name of this network is defined in ${NETWORK} environment variable, and by default is named webproxy.
So, in your website docker-compose, add the network and set it to external:
version: "3"

services:
  app:
    image: nginx:latest
    environment:
      VIRTUAL_HOST: "website1.com"
    networks:
      - webproxy

networks:
  webproxy:
    external: true

Hope that helps, as a disclaimer I'm still learning about the project so may have a few points wrong.

@cwilby I'm having some issues on making more than one website to work. If you got the time, could you kindly give me some insights? Thanks a lot!
#174

@Darksoulsong  sure, I’m traveling at the moment but can share more later.  I have a solution running several websites on a single docker host using this repo: https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion

@cwilby this project uses the same companion you have mentioned just atuomate things for you, I mention that in the readme.

Why not use a discussion for such? Not an issue, could be closed again :)


Add support for providing user-custom-secret for authEncryptSecretKey

Hi
In AWS CloudFormation CDK we do not want to expose the authEncryptSecretKey in CloudFormation when we instantiate the values yaml in code (this is available in AWS CloudFormation webpage and visible by many with only read-only permissions).
Right now in my code I have (which is exposed both in repos and in cloudformation):
yaml_lakefs = yaml.safe_load(
    f"""
    secrets:
        authEncryptSecretKey: 72e5515097c7adsazczxczxcxzasdasdasd....
    serviceAccount:
        create: false
        name: "{unique_sevice_name}"

Helm Chart will create a Secret named "lakefs" (actually lakefs.fullname) with that value and use it from lakeFS pods. It would be great if users could provide "authEncryptSecretRef" in order for LakeFS to use a user-provided secret (which user can register beforehand using more CDK-friendly mechanisms).
The current approach is still the most developer-friendly for many deployment methods so its still valid, but for AWS CDK its not "valid" in my opinion.

I'm less familiar withe AWS CloudFormation CDK capabilities.
As a temporary workaround I suggest to check any secerts mechanism you have access to load the secret value and render values.yaml for the chart with the value and not hard coded it into the code itself.
Will look into possible alternatives (possible PR associated) to this issue as part of the chart.

@TinoSM please try the latest chart v0.10.1 - use existingSecret to control the name of the secret lakeFS will use.

Sorry, was on vacation, tested in 0.12.0 and it works perfect, thanks @nopcoder !


Switch to Poetry for Dependency Management

We're currently using a requirements.txt file - these do not scale well. Virtual environment systems offer a self-contained Python environment for development and building which is less prone to issues.
Unfortunately our PySide dependency hasn't been updated in 8 years and is holding everything else back with an implicit Python 3.4 maximum version limit - 3.12 is current.

PySide 2 is now PySide 6: https://wiki.qt.io/Qt_for_Python

I can't regenerate images_rc.py, because most of the resources it refers to don't exist.

This is working, but needs to be tested:

to ensure the migration to PySide6 was done correctly
to ensure it works on Linux

I can't regenerate images_rc.py, because most of the resources images.grc refers to don't exist.

This has been resolved by 7a4a40abb125fd48dd2caab664a542538d607bb7 upstream.

With the requirements mentioned in the latest commit, the application runs on Debian bookworm: it opens, and closes, without issue. No further testing has been done as of this writing.

Highlight exploring and exporting is working on Debian linux.
Archive features have not been tested on Windows or Linux.


doc: add benchmarking section in contribution page

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #3702

/retest


fix:  dashboard full screen layout

SUMMARY
This pr possibly fixes an issue where user enter full screen and the page errors out. This could be possibly because of an outdated param passed into the getdashboardurl util.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

🏷 2022.1


pyfasta extract KeyError

Hi there,
I am trying to run pyfasta as follows:

pyfasta extract --header --fasta 081315KT27F_pr.fasta 081315KT27F_pr_Chlorella_BG11_ids_test.txt > no_space.txt
My header lines looked like this:
1::M01522:27:000000000-AHFRY:1:2107:16064:6322 1:N:0:7
I received the following error:
Traceback (most recent call last):
File "/usr/bin/pyfasta", line 9, in
load_entry_point('pyfasta==0.5.2', 'console_scripts', 'pyfasta')()
File "/usr/lib/python2.7/site-packages/pyfasta-0.5.2-py2.7.egg/pyfasta/init.py", line 38, in main
globals()action
File "/usr/lib/python2.7/site-packages/pyfasta-0.5.2-py2.7.egg/pyfasta/init.py", line 134, in extract
seq = f[seqname]
File "/usr/lib/python2.7/site-packages/pyfasta-0.5.2-py2.7.egg/pyfasta/fasta.py", line 128, in getitem
c = self.index[i]
KeyError: '>3::M01522:27:000000000-AHFRY:1:2112:23391:15014 1:N:0:7'

I then tried just looking for one of the ids in the ids list:
pyfasta extract --header --fasta ~/Documents/Data/081315KT27F_pr.fasta 20::M01522:27:000000000-AHFRY:1:2106:17777:11432 1:N:0:7 subset.fa
Traceback (most recent call last):
File "/usr/bin/pyfasta", line 9, in
load_entry_point('pyfasta==0.5.2', 'console_scripts', 'pyfasta')()
File "/usr/lib/python2.7/site-packages/pyfasta-0.5.2-py2.7.egg/pyfasta/init.py", line 38, in main
globals()action
File "/usr/lib/python2.7/site-packages/pyfasta-0.5.2-py2.7.egg/pyfasta/init.py", line 134, in extract
seq = f[seqname]
File "/usr/lib/python2.7/site-packages/pyfasta-0.5.2-py2.7.egg/pyfasta/fasta.py", line 128, in getitem
c = self.index[i]
KeyError: '20::M01522:27:000000000-AHFRY:1:2106:17777:11432'
I removed whitespace from header lines in both the ids list and fasta file, so they look like this:

4::M01522:27:000000000-AHFRY:1:2103:12609:208751:N:0:7

... but I'm still getting
[chc@pmpc1451 test]$ pyfasta extract --header --fasta 081315KT27F_pr.fasta 081315KT27F_pr_Chlorella_BG11_ids_test.txt > no_space.txt
Traceback (most recent call last):
File "/usr/bin/pyfasta", line 9, in
load_entry_point('pyfasta==0.5.2', 'console_scripts', 'pyfasta')()
File "/usr/lib/python2.7/site-packages/pyfasta-0.5.2-py2.7.egg/pyfasta/init.py", line 38, in main
globals()action
File "/usr/lib/python2.7/site-packages/pyfasta-0.5.2-py2.7.egg/pyfasta/init.py", line 134, in extract
seq = f[seqname]
File "/usr/lib/python2.7/site-packages/pyfasta-0.5.2-py2.7.egg/pyfasta/fasta.py", line 128, in getitem
c = self.index[i]
KeyError: '081315KT27F_pr_Chlorella_BG11_ids_test.txt'
Thanks for any help in advance!

please use pyfaidx: https://github.com/mdshw5/pyfaidx

Apologies but I've limited experience of Python and was wanting to run from the command line. I can't see an option to give a text file of sequence identifiers to run as a query against a fasta file?

instead of 3::M01522:27:000000000-AHFRY:1:2112:23391:15014 1:N:0:7 as the key, use 3::M01522:27:000000000-AHFRY:1:2112:23391:15014

@mdshw5 does pyfaidx have a command-line utility to extract by name?

I've just successfully extracted my list of sequences by using the --regex option on the command line. Thank you for your advice. My command was as follows:

faidx 081315KT27F_pr.fasta --regex "\b[123]\b::" -o 081315KT27F_pr_ChlorellaBG11.fasta

Where 081315KT27F_pr.fasta is the file containing all my sequencing reads, the parentheses define my regex search terms and 081315KT27F_pr_ChlorellaBG11.fasta is my defined output file containing just the sequences that matched the regex search term.

@mdshw5 does pyfaidx have a command-line utility to extract by name?

@brentp yes, it does: https://github.com/mdshw5/pyfaidx#cli-script-faidx
I should probably add a link at the top of the README since it's gotten sort of buried at the end. @chc284: I'm glad you found a solution using the faidx script. Nice use of the --regex option as well - I'm glad to see it was worthwhile to implement.


requests wasn't on the requirements lists, I had to install manually

OK looks fine, but try to keep your PRs smaller in the future


python310Packages.pytorch-lightning: 1.8.6 -> 1.9.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pytorch-lightning is: Lightweight PyTorch wrapper for machine learning researchers
meta.homepage for python310Packages.pytorch-lightning is: https://pytorch-lightning.readthedocs.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.9.0 with grep in /nix/store/r6dk5bw9gkilz6frak13zljndrj645sj-python3.10-pytorch-lightning-1.9.0
found 1.9.0 in filename of file in /nix/store/r6dk5bw9gkilz6frak13zljndrj645sj-python3.10-pytorch-lightning-1.9.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
larynx-train
python310Packages.larynx-train
python310Packages.pytorch-lightning

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r6dk5bw9gkilz6frak13zljndrj645sj-python3.10-pytorch-lightning-1.9.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pytorch-lightning https://github.com/r-ryantm/nixpkgs/archive/a48603ca4091d81d752f610c1bf85d2aa6bc5d3f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r6dk5bw9gkilz6frak13zljndrj645sj-python3.10-pytorch-lightning-1.9.0
ls -la /nix/store/r6dk5bw9gkilz6frak13zljndrj645sj-python3.10-pytorch-lightning-1.9.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

python310Packages.pytorch-lightning

Maintainer pings
cc @tbenst for testing.

Result of nixpkgs-review pr 211826 run on x86_64-linux 1

2 packages built:

larynx-train (python310Packages.larynx-train)
python310Packages.pytorch-lightning


Move authentication.go to model.

Git does a poor job :). There are already 2 copies of the authentication.go and test (under v1, and under networking/v1alpha3), Git detect authentication.go is moved from v1alpha3, but thest is moved from v1. The others marked deleted.


2FA validation

Submitted a wrong code:

Can you check your composer.lock file and see which version of Auth you have installed. This message should not be in the latest version.
I've searched the codebase for that error in the latest release and on main and I'm not seeing it in there.
You should be able to search your composer.lock for devdojo/auth and see which version is installed. LMK. Thanks!

Let me know which version this is. I'm really interested in figuring out how you got that message and which version you're seeing that in. Thanks.

@divdax I'm closing this issue for now, but if you can check that version and get back to me if this is still happening in the latest version we can re-open.
Thanks!


fix: wait after setting the refresh token

This is a nasty way to handle this, but we will remove this code soon anyway.

Testing on Brave is enough?

Brave and Firefox with private mode are the reported browsers with issues.

It think it works but I'm not 100% sure if 100ms will not be hit

I works on Brave and Firefox- My machine is quite fast and due to resolution depending on processing I would recommend to test it on the machine that is slower to see if 100ms will be enough.

EDIT

Tried on firefox mobile in private mode - it works

I think it's the other way around - the faster the machine, the worse the problem. If the machine is slow, the execution of the updateToken call will be later than on a fast machine, thus meaning the value has time to be set. This is, I think, why it shows on Brave and not Chrome (Brave is lighter weight but same engine) and Firefox Private mode (less junk running) and why you can't reproduce this in a debugger.

Approving


Error runing vscode

I have Debian 10.4
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
Trace/breakpoint trap (core dumped)

checkout #350

I'm running Debian 11 and have set the user namespace to enabled but still getting this error.


v1.0.0-beta.4 seems to break mock/stub/spy with sinonjs

version
v1.0.0-beta.4
What is expected ?
When using sinonjs to mock/stub/spy $store's functions, these $store's function should have the provided behavior by mock/stub/spy.
What is actually happening ?
When I use sinon.stub(...) to provide a behavior on $store's function, it seems like sinon can't do the function replacement. No error is thrown and tests failed because $store's functions behavior do not change.
Unit tests were running well until npm update from vue-test-utils v1.0.0-beta.2 to v1.0.0-beta.4
Here is an example of unit test with described behavior :
import ...

describe('Component...', () => {
  let vm

  beforeEach(() => {
    vm = createComponentInstance()
  })

  it('Should do something when $store dispatch call throw an error.', done => {
    sinon.stub(vm.$store, 'dispatch').rejects(new Error('Something bad happens here'))

    vm.storeDispatchCallFunction()

    Vue.nextTick(() => {
      expect(vm.$toastr.called).to.be.true
      done()
    })
  })

  function getMockedStore () {
    return {
      dispatch: () => {},
      watch: sinon.spy(),
      commit: sinon.spy()
    }
  }

  function createComponentInstance () {
    const localVue = createLocalVue()
    const $store = getMockedStore()
    const $toastr = sinon.spy()
    return shallow(Component, {
      localVue,
      mocks: {
        $store,
        $toastr
      }
    }).vm
  }
})

and the component implementation :
import ...

export default {
  // ...
  methods: {
    storeDispatchCallFunction () {
      this.$store.dispatch('SOME_ACTION').catch(error => {
        this.$toastr('error', error.message)
      })
    }
  }
}

Now my unit test fail because an error is thrown during its runtime : TypeError: Cannot read property 'catch' of undefined
Which is true because by default my mocked store dispatch function returns nothing. But I stub it just before the function call and with version change stubbing do nothing.
I fixed this by returning to previous v1.0.0-beta.2 version.
Any ideas ?

Hi, thanks for the bug report.
v1.0.0-beta.4 fixed a bug where mocks were not editing the localVue prototype, which meant child components weren't receiving mocks correctly. https://github.com/vuejs/vue-test-utils/issues/127
I'm not sure exactly why using the sinon.stub() method to, but you can fix the tests by using this pattern. I'm going to look into why, because I'm curious what the difference is!
Replace this line:
sinon.stub(vm.$store, 'dispatch').rejects(new Error('Something bad happens here'))

With this:
vm.$store.dispatch = sinon.stub()
vm.$store.dispatch.rejects(new Error('Something bad happens here'))

This behavior won't be changed, but I'll try and find out why stubbing using the method is failing.


Add why? to README

Would be nice a little explanation about why using listen is better.
Does spring run faster?
Does it use less machine resources?

Thanks - I added a small note in the README. Let me know if it's enough.

Thanks. that means it's not perceptible in small projects?

@neves - best to test for your situation, since there are too many variables. E.g. certain setups on OSX can be very slow. You can check out the Listen doc/wiki about performance issues to get more info.


list tables not working

Hello,
First of all I wanted to thank you for this cool work ! The web interface looks great and it is a very useful tool.
I followed all the installation process (but with nginx) and I'm able to display the tables structure and to add new data inside tables but I can't list this data. Whatever I try I always get this message :
No matching records found.
The SQL user has read and write rights and all may databases are not empty. Does somebody know what could be wrong here ?

have you take a look at this https://github.com/jonseg/crud-admin-generator/issues/57 about Nginx config ?
if you open your browser log console, do you get any error ? in the network tab, what happen to the ajax call ?

Something is wrong i enter in http://test.local:8080 (is my virtual host for /web) click in list this redirect example to http://test.local /nametable and error 404 no found but i comment the firts line of file /admingenerator/web/controllers/.htaccess and can acces to http://test.local/controller/base.php work fine.... Sorry for my bad english...

@Thedemon007 please, make your own issue, I don't think you are on Nginx ?
Btw, have you tried this http://stackoverflow.com/questions/24952846/how-do-i-remove-the-web-from-my-url/24953439#24953439 ?

Hello,
Sorry for the delay. I will try the recommended NGINX Config in #57 and keep you updated if this works

Hello,
I tried many NGINX conf but I still have the problem.
I can create new entries in my databases without any problem. But I can't see the content of the bases on the web ui.
I have no Ajax errors on my browser

As mentioned by author, the system is based in silex.
I've solve this issue. Follow the silex config guide:
https://silex.symfony.com/doc/2.0/web_servers.html

This is a nice project but I think the developer has stopped working on it. Please try this new project: https://github.com/Muhammadinaam/speed-admin


Add configuration for travis ci deploy to heroku

@caseyhelbling I tested this setup with my personal account.
Not sure how travis is setup for this repo, but I also had to add the following to get postgres to actually run.
services:
- postgresql

AFAICT it's probably because it's running on an old ubuntu trusty image and has postgres running by default and the new xenial images require the configuration.
There's also one part that whoever has credentials needs to do
# install travis cli and heroku cli first, then run at the root of the repo, commit and push the changes
travis encrypt $(heroku auth:token) --add deploy.api_key

Also, if the app in heroku isn't named sessionizer it's necessary to add app: <app-name> to the deploy configuration block.

Coverage remained the same at 53.263% when pulling 3efb94cc80f69cd2da077c1f28735d44c382ddce on aackerman:aackerman/travis-deploy into 9df671dcee458bafb04c5c962ac4b2b943135ee8 on minnestar:master.

:+1: -- I'll let someone who has access to the credentials set it up and merge this PR. Nice work though!

We're still using that vagrant setup that requires git subtree push --prefix src heroku master to deploy, instead of just a simple push. Will this mechanism handle that properly?


Migrate CI to github actions

This PR migrates the CI to GitHub Actions.
Note: this is deliberately done on a branch on the main project, not from a fork; this is needed to test the first instance of github actions.

@GregoryAshton, I think this is ready to go, the lint job is failing because there's lint, which can be fixed another time.

Looks good, I will merge this in.


Not able to insert dimensions and expression in Qliksense Heatmap

Hi
We have developed our own qlik sense heatmap chart.
I am new to javascript.Could you please share how to insert our own dimensions and expressions in below code.
Thanks

Sorry, I am not able to answer this question without further details. I recommend that you post your question to the branch slack channel: http://qlikbranch-slack-invite.herokuapp.com/


How to use plugin in browser

I'm not using node.js, I have an old-fashioned server, but I would like to use markdown-it in the browser.
I have succeeded to use the core:
<script src="/markdown-it.js"></script>
...
<script>
    var md = window.markdownit(); // Can be found in https://markdown-it.github.io/markdown-it/ "Simple"
</script>

However, I fail to get the plugins running. From the documentation, It seems that the only way to get a plugin is "require", This, however, fails in the browser (require is node.js specific, right?).
Could please anybody give me a hint how to get the plugin-objects that I need as parameter for md.use without using require?

Hello, @mnlipp.
The require part that you mention is equivalent to the window.markdownit() initialization in browser. The plugin loading is the same in both (browser and node). Most of the plugin READMEs have examples on how to load them in browser.
emoji plugin example (Read Differences in browser):
var md = window.markdownit().use(window.markdownitEmoji);

Okay, thanks. I didn't think of looking in the plugins' documentations (assuming that there should be some general explanation in the core documentation).

I'm sorry, but there must be a bit more to it. I now have:
<script src="/markdown-it.js"></script>
<script src="/markdown-it-abbr.js"></script>
...
<script>
    var md = window.markdownit(); // Fails now!
</script>

I.e. I have added the source for the abbr plugin (but haven't even tried to use it). This makes the core module fail. I get: TypeError: window.markdownit is not a function.
This clearly depends on including the plugin script. Removing it again fixes things. I took markdown-it-abbr.js directly from the dist directory ("Raw", of course).

It's better to read browserify documentation. That's general things, not specific to this project.

@puzrin: Thanks, but having had a short look at it, I disagree. I don't need another build system in my project (and I really don't want to start developing with node.js), I just want to use this great library with its plugins on the client side (i.e. in the browser).
(And though I made a silly mistake in the beginning (deleted comment) and I'm not through with all the plugins yet, @Odyseus approach seems to work fine.)

@mnlipp i mean we have some time constrains and avoid spending it for general programming questions. Browserify is used here to build browser sources for markdown-it and plugins. It worth to learn principle once, and reuse this knowledge many times later :).


device update release

The PR conflict will be resloved in merging.

/check-enforcer evaluate

Changes look good. Please update the recorder to use the new recorder tool and we should be good.

@joheredi I think the new recorder asks me to re-record the test recordings. However, I cannot do it now because the instance for our test is deleted by service team. It's complex to setup a new test environment and service team hopes to release this package as soon as possible, so I prefer to use this previous recorder in this PR.

/azp run

/azp run js - deviceupdate - ci, js - core - ci

/azp run js - core - ci

Looks great! Would you mind filing an issue to remove the ignore entries you added?
Thanks for taking the time to migrate to the new recorder /cc: @HarshaNalluru @timovv

ignore links are removed


_boundIronOverlayCanceledListener event listener

Adding _boundIronOverlayCanceledListener event listener for preventing iron-overlay-canceled event to fix issue of vaadin-combo-box inside paper-dialog.
Connects to https://github.com/vaadin/vaadin-combo-box/issues/405

This change is

Rebase needed. Other than that

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


Bash command missing.

What type of installation are you running?
Desktop
Which Linux OS are you using?
Ubuntu 23.10
Which version of LNXLink has the issue?
2024.9.0
Describe the problem
I was using Bash command module and not it's not available through MQTT:

I still have it in config:
update_interval: 30
modules:
- bash
- battery
- cpu
- memory
- network
- required_restart
- restart
- screenshot
- shutdown
- suspend
- sys_updates
- update
custom_modules: null

Additional context
No response
Configuration
No response
Logs
No response

Could you also provide the log files from the moment it starts?
These are located at the same directory as your config file under the name lnxlink.log


Remove round button

Remove the round button and set this to default

@rachel-labri-tipton and @braddf this could be a good task for you both to do. Either work together or seperate, and see if you come up with the same solution


animate a line

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
at this moment the line above the inverter remains static and one color
Expected behaviour
it could move and color like other flows
Possible Solutions
Is it possible to color it with the flow of use like that little piece that goes towards the grid?
Mode
full
Context / Reason
improve visualization

Sure, let me see what I can do

Great!


FundamentalWave: orientation of rotor currents

Reported by ahaumer on 30 Jul 2013 09:15 UTC
The orientation of rotor currents is wrong:
AIMC.rotorCage, AIMS.rotor, SMxx.rotorCage
Should be fixed together with #1223.
Should be fixed for MSL 3.2, too.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1226

Comment by christiankral on 30 Jul 2013 11:00 UTC
Bug fixed for Machines and FundamentalWave library in MSL 3.2.1 in 9491140b162caf281ce137a40f815a711c96f777.

Comment by christiankral on 30 Jul 2013 11:27 UTC
Fixed problem for MSL 3.2 in 979ede3bb0dac532711e0668884c11ebac118dcb.

Modified by christiankral on 30 Jul 2013 11:27 UTC

Comment by christiankral on 21 Jul 2014 18:57 UTC
There are still issues open:
The rotor currents

ir
rotorCage.i
of the induction and synchronous machines are NOT equal but shall be equal. This is a bug and shall be corrected.

Changelog modified by christiankral on 21 Jul 2014 18:57 UTC
Fixed wrong signs of rotor currents of all cage models

Comment by christiankral on 21 Jul 2014 20:46 UTC
Unification of implementations with correct signs of all rotor currents. This applies to induction and synchronous machines. Changes have been applied to the transient and the quasi static FundamentalWave library. A backwards compatible alias variable has been added for the rotor currents of the squirrel cage model of the Machines library.
The applied changes 9bbd031656f75e8e330c6589feacb7af4b53d5b2 in the transient and quasi static FundamentalWave packages are bug fixes.


Jan release 2021

Docs Build status updates of commit 8edc333:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8edc333:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Should we mention the IQ# bug we fixed and how to update your installation to fix it?
dotnet tool uninstall -g Microsoft.Quantum.IQSharp
dotnet tool install -g Microsoft.Quantum.IQSharp --version 0.15.2101125897

Then installing the new qsharp version:
conda update qsharp

Verify new version is installed:
conda list iqsharp

Should we mention the IQ# bug we fixed and how to update your installation to fix it?
dotnet tool uninstall -g Microsoft.Quantum.IQSharp
dotnet tool install -g Microsoft.Quantum.IQSharp --version 0.15.2101125897

Then installing the new qsharp version:
conda update qsharp

Verify new version is installed:
conda list iqsharp

Should we mention the IQ# bug we fixed and how to update your installation to fix it?
dotnet tool uninstall -g Microsoft.Quantum.IQSharp
dotnet tool install -g Microsoft.Quantum.IQSharp --version 0.15.2101125897

Then installing the new qsharp version:
conda update qsharp

Verify new version is installed:
conda list iqsharp

I think strictly speaking those are two distinct ways of getting the IQ# fix; a conda user shouldn't need to run the first two steps, as the version installed by the .NET Core SDK is hidden by the conda environment with qsharp and iqsharp installed.

Should we mention the IQ# bug we fixed and how to update your installation to fix it?
dotnet tool uninstall -g Microsoft.Quantum.IQSharp
dotnet tool install -g Microsoft.Quantum.IQSharp --version 0.15.2101125897

Then installing the new qsharp version:
conda update qsharp

Verify new version is installed:
conda list iqsharp

I think strictly speaking those are two distinct ways of getting the IQ# fix; a conda user shouldn't need to run the first two steps, as the version installed by the .NET Core SDK is hidden by the conda environment with qsharp and iqsharp installed.

Docs Build status updates of commit f005877:
:clock10: Pending: waiting for processors (23 builds ahead of you)
:warning: Docs Build is busy, currently there are 23 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit f005877:
:clock10: Pending: waiting for processors (23 builds ahead of you)
:warning: Docs Build is busy, currently there are 23 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 1f6178b:
:clock10: Pending: waiting for processors (14 builds ahead of you)
:warning: Docs Build is busy, currently there are 14 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 1f6178b:
:clock10: Pending: waiting for processors (14 builds ahead of you)
:warning: Docs Build is busy, currently there are 14 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit f005877:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f005877:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1f6178b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1f6178b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3f8f588:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3f8f588:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3d2e9e1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3d2e9e1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Convert tree-sitter to Lezer trees for CodeMirror 6 support

I always wanted to upgrade the ReScript online playground to the newest CodeMirror version, but CM transitioned from regex based language parsers to a more sophisticated parser system called Lezer.
If the tree-sitter is stable enough to reflect all parts of the language, I thought it would be interesting to try to use the tree-sitter parser as a shim until I figured out how to proceed writing a dedicated Lezer parser.
https://discuss.codemirror.net/t/mapping-tree-sitter-trees-to-lezer-trees/2362

Yes, the grammar is stable enough and covers most quirky cases, so anyone can try to port to Lezer.
With this issue, are we trying to summon someone to do this? :)

Yeah, I kinda put this note here in case someone feels inspired to try it.


max time in pending queue

would be good to have a setting like maxSecondsInPendingQueue: 300
so that workflows that are pending for more than this time are auto deleted
this can prevent a denial of service attack where someone submits too many and overwhelms etcd

activeDeadlineSeconds may partly suffice for this, but you can't specify "pending" Workflows specifically with it

its not suitable as that time includes actual runtime

Maybe can be combined with kueue in some way.

https://github.com/argoproj/argo-workflows/pull/12762 is similar but at node instead of workflow level


Moved config load to init_app()

Constant initialization now waits for the config.pypackage initializations.
Refactored constant names for consistency

I will go ahead an merge this.


Implement parallelism, custom data and custom metrics

Work in progress. Closes #2, closes #4.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6b1f222). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #7   +/-   ##
=========================================
  Coverage          ?   91.18%
=========================================
  Files             ?        4
  Lines             ?      669
  Branches          ?        0
=========================================
  Hits              ?      610
  Misses            ?       59
  Partials          ?        0

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 6b1f222...2ac6236. Read the comment docs.


Simplify graph of single-chunk reductions

Whenever a reduction operates on a single chunk, it needlessly creates two nodes:
>>> dict(da.arange(2, chunks=2).sum().dask)
{
    ('sum-aggregate-ec0e68db6f32b6093d94c7b17d2bfe45',): (<toolz.functoolz.Compose at 0x7fd7d00962e8>, ('sum-880c178b66ab4131ea200c3a6dbf37a3', 0))
    ('sum-880c178b66ab4131ea200c3a6dbf37a3', 0): (<function dask.compatibility.apply(func, args, kwargs=None)>, functools.partial(<function sum at 0x7fd7f0307b70>, dtype=dtype('int64')), [('arange-9478255fa17899194839c85832cf613a', 0)], {'axis': (0,), 'keepdims': True}),
    ('arange-9478255fa17899194839c85832cf613a', 0): (<function dask.array.chunk.arange(start, stop, step, length, dtype)>, 0, 2, 1, 2, dtype('int64')),
}

This should be changed so that:

if the chunk and aggregate kernel are the same, instead of aggregate(chunk(..., keepdims=True), keepdims=False) we should just call chunk(..., keepdims=False)
if the chunk and aggregate kernel differ, they should be compose'd into a single node.

Out of curiosity is this causing performance degradation somewhere, or is it just for general cleanliness?

@mrocklin @jakirkham sorry for the long silence.
As of dask 1.2, I can see there is still a good deal of space for optimization:
from functools import partial
from toolz.functoolz import compose
import dask.array as da
import numpy as np

a = da.arange(2, chunks=2).sum()

b = da.Array(
    da.Array.__dask_optimize__(
        a.__dask_graph__(),
        a.__dask_keys__()
    ),
    a.name, a.chunks, a.dtype)

c = da.Array(
    dask={('c', ): (compose(np.sum, partial(np.arange, 0, 2, dtype='int64')), )},
    name='c', shape=(), chunks=(), dtype='int64')

%timeit a.compute(optimize=False, scheduler='sync')
463 µs ± 3.46 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)
%timeit b.compute(optimize=False, scheduler='sync')
350 µs ± 3.63 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)
%timeit c.compute(optimize=False, scheduler='sync')
237 µs ± 19.2 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

The difference between b and c is broken down as follows:

b contains 2 keys, of which 1 is redundant:

dict(b.dask)
Out[44]:
{('sum-aggregate-19caf639b954cf81fcb0e7267949198a',): ('arange-sum-sum-aggregate-19caf639b954cf81fcb0e7267949198a',),
 ('arange-sum-sum-aggregate-19caf639b954cf81fcb0e7267949198a',): (<toolz.functoolz.Compose at 0x10aa2f8d0>,
  (subgraph_callable,
   (<function dask.array.chunk.arange(start, stop, step, length, dtype)>,
    0,
    2,
    1,
    2,
    dtype('int64'))))}
b2 = da.Array(b.dask,
              name='arange-sum-sum-aggregate-19caf639b954cf81fcb0e7267949198a',
              shape=(), chunks=(), dtype='int64')

%timeit b2.compute(optimize=False, scheduler='sync')
275 µs ± 2.17 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

The computation of the innermost value could be sped up:

b3 = b.dask['arange-sum-sum-aggregate-19caf639b954cf81fcb0e7267949198a',]
c3 = compose(np.sum, partial(np.arange, 0, 2, dtype='int64'))

%timeit b3[0](b3[1][0](b3[1][1][0](*b3[1][1][1:])))
29.9 µs ± 300 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)
%timeit c3()
4.59 µs ± 93.2 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)


cors support for route rules

Context: https://github.com/nuxt/framework/issues/4009
Proposal:
routes: {
  '/public': { cors: true }
}

We probably need an h3 utility for this as well: https://github.com/unjs/h3/issues/82

@pi0 What about enabling cors in general? I created another thread under Nuxt and the suggested approach was to create a Nitro plugin. I could however not get it to work the same way it works for express.
This is the code that works with an express server (notice the origin value set to localhost:3100). The client can access the end points just fine:
app.use(
  cors({
    origin: 'http://localhost:3100',
    credentials: true,
  })
)
app.use(function(req, res, next) {
  res.header('Access-Control-Allow-Origin', 'http://localhost:3100')
  res.header('Access-Control-Allow-Credentials', true)
  res.header('Access-Control-Allow-Methods', 'GET,PUT,POST,DELETE,OPTIONS')
  res.header(
    'Access-Control-Allow-Headers',
    'Origin,X-Requested-With,Content-Type,Accept,content-type,application/json'
  )
  next()
})

The corresponding Nitro plugin does not work. Maybe I messed up somewhere? The client app compains that the origin is set to '*' even though I set it to localhost:
import cors from 'cors'

export default defineNitroPlugin(({ h3App }) => {
  h3App.use(
    cors({
      origin: 'http://localhost:3100',
      credentials: true,
    })
  )
  h3App.use(function (req, res, next) {
    res.header('Access-Control-Allow-Origin', 'http://localhost:3100')
    res.header('Access-Control-Allow-Credentials', true)
    res.header('Access-Control-Allow-Methods', 'GET,PUT,POST,DELETE,OPTIONS')
    res.header(
      'Access-Control-Allow-Headers',
      'Origin,X-Requested-With,Content-Type,Accept,content-type,application/json'
    )
    next()
  })
})

Any help would be appreciated.

We can globally enable it with routing rules too:
routes: {
  '/**': { cors: true }
}

Hey, is there any development on this?
I am also struggling with cors and the options method.