Improved requeue behaviour

Summary
We have quite a few workflows which have many short (often <1s, small images) steps. These seem to run slower than they should.
From reading previous issues (particularly https://github.com/argoproj/argo-workflows/issues/6262 and https://github.com/argoproj/argo-workflows/pull/9729) and docs/code (https://github.com/argoproj/argo-workflows/blob/master/workflow/controller/rate_limiters.go#L17) it seems that the DEFAULT_REQUEUE_TIME config variable controls how often Argo checks to see whether steps have completed. So if this is set to the default of 10s, a pod that completes in 1s will take an additional 9s to be registered as completed by Argo so that the next step can begin. The trade-off is that lower values cause more load on the k8s API.
Rather than just a simple "check every X seconds" policy, would it make sense to have a rate limiter that checks frequently when pods are young and backs off as they run longer? This would mean that workflows with lots of short steps would complete snappily while avoiding spamming the API for longer steps.
An example policy could be something like "requeue every elapsed_time/5 seconds, up to a maximum of 30s". This would guarantee that <20% of the runtime of a step is spent waiting for Argo to register that it has finished.
If there is agreement on what a better policy would look like then I'd be happy to submit a PR to implement it.
Thanks!

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
Beyond this issue:

I think you misunderstood the purpose of the DEFAULT_REQUEUE_TIME configuration, Workflow Controller relies on the PodInformer to determine if the steps are completed.
DEFAULT_REQUEUE_TIME is likely intended to slow down the scheduling of workflows in scenarios where the cluster contains a large number of workflows with short steps, in order to reduce the load of the API Server and Workflow Controller.

I think you misunderstood the purpose of the DEFAULT_REQUEUE_TIME configuration, Workflow Controller relies on the PodInformer to determine if the step is completed, rather than detecting it periodically. DEFAULT_REQUEUE_TIME is likely intended to slow down the scheduling of workflows in scenarios where the cluster contains a large number of workflows with short steps, in order to reduce the load of the API Server and Workflow Controller.

I see, thanks for the clarification. So this means that if 100 steps for a workflow complete within the same 10s window, the workflow only gets queued once, 10s after the completion event was received for the first step.
https://github.com/kubernetes/client-go/blob/master/util/workqueue/delaying_queue.go#L310-L313
If I'm understanding correctly this still seems like it will often slow down workflows unnecessarily. In an extreme case, a workflow with 10 steps that are sequentially dependent and each take 1s to run will wait 10s to requeue after the completion of each step, giving a total runtime of 100s rather than 10.
For my use case I think it makes sense to drop the default requeue time to 1s, since we are not running many workflows in parallel and API load is not a huge concern.

I think you misunderstood the purpose of the DEFAULT_REQUEUE_TIME configuration, Workflow Controller relies on the PodInformer to determine if the step is completed, rather than detecting it periodically. DEFAULT_REQUEUE_TIME is likely intended to slow down the scheduling of workflows in scenarios where the cluster contains a large number of workflows with short steps, in order to reduce the load of the API Server and Workflow Controller.

I see, thanks for the clarification. So this means that if 100 steps for a workflow complete within the same 10s window, the workflow only gets queued once, 10s after the completion event was received for the first step.
https://github.com/kubernetes/client-go/blob/master/util/workqueue/delaying_queue.go#L310-L313
If I'm understanding correctly this still seems like it will often slow down workflows unnecessarily. In an extreme case, a workflow with 10 steps that are sequentially dependent and each take 1s to run will wait 10s to requeue after the completion of each step, giving a total runtime of 100s rather than 10.
For my use case I think it makes sense to drop the default requeue time to 1s, since we are not running many workflows in parallel and API load is not a huge concern.

It is a good choice to reduce the default requeue time in your scenario, because the default configuration will ensure that each step takes at least 10 seconds.

Actually, I also faced the challenge of accelerating workflow execution. I'm curious about how you achieved each step completing in less than 1 second. When I use the Container Template, it takes around 6 seconds just to start the pod.

Actually, I also faced the challenge of accelerating workflow execution. I'm curious about how you achieved each step completing in less than 1 second. When I use the Container Template, it takes around 6 seconds just to start the pod.

The 1s figure was based on intuition about the size of the image (a few megabytes for Alpine) and the amount of work the steps are doing rather than any rigourous profiling. I just did a quick test using kubectl run and it looks like the lower bound for pod execution is about 3-4s on my cluster.
$ time kubectl run alpine-test --image=alpine --restart=Never --rm -it --command -- sh -c 'echo hello'
hello
pod "alpine-test" deleted
kubectl run alpine-test --image=alpine --restart=Never --rm -it --command --   0.21s user 0.07s system 7% cpu 3.512 total

Did you find any other ways of improving the execution time of workflows other than DEFAULT_REQUEUE_TIME?

Actually, I also faced the challenge of accelerating workflow execution. I'm curious about how you achieved each step completing in less than 1 second. When I use the Container Template, it takes around 6 seconds just to start the pod.

The 1s figure was based on intuition about the size of the image (a few megabytes for Alpine) and the amount of work the steps are doing rather than any rigourous profiling. I just did a quick test using kubectl run and it looks like the lower bound for pod execution is about 3-4s on my cluster.
$ time kubectl run alpine-test --image=alpine --restart=Never --rm -it --command -- sh -c 'echo hello'
hello
pod "alpine-test" deleted
kubectl run alpine-test --image=alpine --restart=Never --rm -it --command --   0.21s user 0.07s system 7% cpu 3.512 total

Did you find any other ways of improving the execution time of workflows other than DEFAULT_REQUEUE_TIME?

Using HTTP/Plugin Template instead of Container Template is a feasible solution. Steps of HTTP/Plugin Template will execute in one same agent pod which can save a lot of pod creation time. By the way, DEFAULT_REQUEUE_TIME is still extremely important because the default value of ARGO_AGENT_PATCH_RATE is also DEFAULT_REQUEUE_TIME.

I think you misunderstood the purpose of the DEFAULT_REQUEUE_TIME configuration, Workflow Controller relies on the PodInformer to determine if the step is completed, rather than detecting it periodically. DEFAULT_REQUEUE_TIME is likely intended to slow down the scheduling of workflows in scenarios where the cluster contains a large number of workflows with short steps, in order to reduce the load of the API Server and Workflow Controller.

Hi @jswxstw,
I have a similar question. I have a workflow with only one step. It took about 20s to complete the step, but the duration of the workflow is 30s. It's 10 seconds delay. If I reduce DEFAULT_REQUEUE_TIME to 5 seconds, and the workflow duration will become 25s.
As you mentioned, "Workflow Controller relies on the PodInformer to determine if the step is completed", looks like workflow controller didn't reconcile the corresponding workflow when the pod is complete according to the below logs with 5s DEFAULT_REQUEUE_TIME:
time="2024-06-26T01:27:12.148Z" level=info msg="Created pod: carol-ws.exec-script-exe-main-s8q6w[1].execute-script (carol-ws.exec-script-exe-main-s8q6w-1061060677)" namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:12.148Z" level=info msg="Workflow step group node carol-ws.exec-script-exe-main-s8q6w-2536539054 not yet completed" namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:12.148Z" level=info msg="TaskSet Reconciliation" namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:12.149Z" level=info msg=reconcileAgentPod namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:12.163Z" level=info msg="Workflow update successful" namespace=canal-flow phase=Running resourceVersion=569838 workflow=carol-ws.exec-script-exe-main-s8q6w

// --> 5s later (DEFAULT_REQUEUE_TIME)
time="2024-06-26T01:27:17.152Z" level=info msg="Processing workflow" namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:17.153Z" level=info msg="Task-result reconciliation" namespace=canal-flow numObjs=0 workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:17.153Z" level=info msg="node changed" namespace=canal-flow new.message= new.phase=Running new.progress=0/1 nodeID=carol-ws.exec-script-exe-main-s8q6w-1061060677 old.message= old.phase=Pending old.progress=0/1 workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:17.154Z" level=info msg="SG Outbound nodes of carol-ws.exec-script-exe-main-s8q6w-2414852609 are [carol-ws.exec-script-exe-main-s8q6w-2414852609]" namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:17.155Z" level=info msg="Workflow step group node carol-ws.exec-script-exe-main-s8q6w-2536539054 not yet completed" namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:17.155Z" level=info msg="TaskSet Reconciliation" namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:17.155Z" level=info msg=reconcileAgentPod namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:17.166Z" level=info msg="Workflow update successful" namespace=canal-flow phase=Running resourceVersion=569858 workflow=carol-ws.exec-script-exe-main-s8q6w

// during this period, the pod was completed at 01:27:34
// but there is no any reconcile log.. until 5 seconds later

time="2024-06-26T01:27:39.294Z" level=info msg="Processing workflow" namespace=canal-flow workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:39.294Z" level=info msg="Task-result reconciliation" namespace=canal-flow numObjs=1 workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:39.294Z" level=info msg="task-result changed" namespace=canal-flow nodeID=carol-ws.exec-script-exe-main-s8q6w-1061060677 workflow=carol-ws.exec-script-exe-main-s8q6w
time="2024-06-26T01:27:39.294Z" level=info msg="node changed" namespace=canal-flow new.message= new.phase=Succeeded new.progress=0/1 nodeID=carol-ws.exec-script-exe-main-s8q6w-1061060677 old.message= old.phase=Running old.progress=0/1 workflow=carol-ws.exec-script-exe-main-s8q6w

The version I'm using is v3.4.8
Did I misunderstand anything? What should I do if I want to reduce this 10 seconds gap?

Did I misunderstand anything? What should I do if I want to reduce this 10 seconds gap?

If the workflow or its pod is changed, informer will get this update event and put the workflow into wfQueue using wfc.wfQueue.AddRateLimited.
If DEFAULT_REQUEUE_TIME is config to 5s, the same workflow can only be put into queue every 5s.
Additionally, there will be an interval of time, which is uncontrollable, before the informer truly perceives the update of the pod status.

Hi @jswxstw , thanks for your prompt reply. I'd like to confirm whether, once the workflow is put into queue, it will be reconciled immediately? (Assuming there is only one workflow in the environment.)
Or is there any possible latency between the workflow being added to the queue and being reconciled?

Hi @jswxstw , thanks for your prompt reply. I'd like to confirm whether, once the workflow is put into queue, it will be reconciled immediately? (Assuming there is only one workflow in the environment.) Or is there any possible latency between the workflow being added to the queue and being reconciled?

wfWorkers is responsible for processing the workflow in wfQueue, it will be processed immediately if there is only one workflow.


User Search fails to find certain substrings

Describe the bug
This is a bug that is apparently not always reproducible, meaning it might occur or it might not, but it does happen.
This was experienced on test server 2 while testing the following pull request (see discussion): https://github.com/ls1intum/Artemis/pull/7789#issuecomment-1859089163
All users in the test servers have the format Test User X Artemis, whereas X is a number. Searching for Test or User did not yield any results, but searching for Artemis worked.
To Reproduce

Use the search functionality anywhere on a test server, preferably when creating a group chat
Search for different substrings
Have (bad) luck that it breaks

Expected behavior
Searching for any substring of a user should return the respective users, i. e. the search should work.
Screenshots

Which version of Artemis are you seeing the problem on?
6.7.3
What browsers are you seeing the problem on?
Chrome, Safari, Microsoft Edge, Firefox
Additional context
Copied from the discussion in the PR: I guess it has something to do with MySQL/Postgres and the way the search queries are written
Relevant log output
No response

Have you ever checked the network response? Whether a request was sent and what the result was?


Error with LSP on empty line

I am getting this error here in combination with the vim-language-server when I execute the omni complete mapping without any preceding characters, seems like it tries to send some empty variables to the LSP.
Error(LSP): request textDocument/completion failed (Request textDocument/completi... arguments[[object Object], [object Object], undefined, undefined], code = -32603)

This looks like a bug in the vim-language-server.  You should open a issue with the vim-language-server.  The error code "32603" refers to an internal error.  I am also able to reproduce the same error with the vim-lsp language server.


stack-based vm

updated readme
stack-based bytecode evaluation

(Typically it makes the job of the reviewer easier if there are no merge commits.  It's best to rebase them away prior to raising a PR. Don't worry for this PR though)

please squash.

bors r+


Error in transfer of large cupy objects

@TomAugspurger Looks like wrong detection of buffer type because rma_get protocol shouldn't be used for cuda buffers. Will update more with possible causes.
akvenkatesh@prm-dgx-22:~/ucx-py-tom$ python3 benchmarks/recv-into-client.py -o cupy --n-iter=100 -s <IP_ADDRESS> -p 13337
[1551808150.700639] [prm-dgx-22:64514:0]         parser.c:1370 UCX  WARN  unused env variables: UCX_PY_CUDA_PATH, UCX_PY_UCX_PATH (set UCX_WARN_UNUSED_ENV_VARS=n to suppress this warning)
[prm-dgx-22:64514:0:64514] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x28)
==== backtrace ====
    0  /home/akvenkatesh/ucx-github/build/lib/libucs.so.0(+0x25003) [0x2b7e57ea1003]
    1  /home/akvenkatesh/ucx-github/build/lib/libucs.so.0(+0x25161) [0x2b7e57ea1161]
    2  /home/akvenkatesh/ucx-github/build/lib/libucp.so.0(ucp_rkey_destroy+0x10) [0x2b7e579b90d6]
    3  /home/akvenkatesh/ucx-github/build/lib/libucp.so.0(ucp_rndv_progress_rma_get_zcopy+0x24b) [0x2b7e579f5595]
    4  /home/akvenkatesh/ucx-github/build/lib/libucp.so.0(+0x639f2) [0x2b7e579fd9f2]
    5  /home/akvenkatesh/ucx-github/build/lib/libucp.so.0(ucp_rndv_rtr_handler+0x440) [0x2b7e579fe259]
    6  /home/akvenkatesh/ucx-github/build/lib/libuct.so.0(+0x7d346) [0x2b7e583b5346]

closing this because I don't see this error with up to 4GB size


foward port rel/7.4 to foward/orbit

fixes from rel/7.4

PR has been updated. Reviewers, please be cautious.

CONFLICT (add/add): Merge conflict in tests/unit/utils/setPartRanges.js
CONFLICT (add/add): Merge conflict in tests/unit/utils/responseStreamData.js
CONFLICT (add/add): Merge conflict in tests/unit/utils/aclUtils.js
CONFLICT (add/add): Merge conflict in tests/unit/metadataswitch.js
CONFLICT (add/add): Merge conflict in tests/unit/helpers.js
CONFLICT (add/add): Merge conflict in tests/unit/healthchecks/healthcheckResponse.js
CONFLICT (add/add): Merge conflict in tests/unit/encryption/kms.js
CONFLICT (add/add): Merge conflict in tests/unit/bucket/bucket_mem_api.js
CONFLICT (add/add): Merge conflict in tests/unit/bucket/bucketCreation.js
CONFLICT (add/add): Merge conflict in tests/unit/auth/V4Transform.js
CONFLICT (add/add): Merge conflict in tests/unit/api/transientBucket.js
CONFLICT (add/add): Merge conflict in tests/unit/api/serviceGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectPutACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectPut.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectHead.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectGetACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectACLauth.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multipartUpload.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multipartDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/listParts.js
CONFLICT (add/add): Merge conflict in tests/unit/api/listMultipartUploads.js
CONFLICT (add/add): Merge conflict in tests/unit/api/deletedFlagBucket.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketPutACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketPut.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketHead.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketGetACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketACLauth.js
CONFLICT (add/add): Merge conflict in tests/unit/DummyRequest.js
CONFLICT (add/add): Merge conflict in tests/unit/Config.js
CONFLICT (add/add): Merge conflict in tests/performance/s3standard.js
CONFLICT (add/add): Merge conflict in tests/functional/s3curl/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/s3cmd/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/jaws/src/test/java/com/scality/StreamV4AuthTest.java
CONFLICT (add/add): Merge conflict in tests/functional/fog/tests.rb
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/support/withV4.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/support/config.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/service/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/rangeTest.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/putPart.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/putObjAcl.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectOverwrite.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectHead_compatibleHeaders.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectHead.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectCopy.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/mpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/listParts.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/getRange.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/getMPU_compatibleHeaders.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/deleteObject.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/deleteMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/copyPart.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/compluteMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/bigMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/mocha.opts
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/authV4QueryTests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/authV2QueryTests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/index.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/testBucketVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/testBucketStress.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/putAcl.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/listingCornerCases.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/head.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/utility/provideRawOutput.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/utility/bucket-util.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/json/mem_credentials.json
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/fixtures/project.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/index.js
CONFLICT (add/add): Merge conflict in package.json
CONFLICT (add/add): Merge conflict in lib/utilities/logger.js
CONFLICT (add/add): Merge conflict in lib/utilities/healthcheckHandler.js
CONFLICT (add/add): Merge conflict in lib/utilities/collectResponseHeaders.js
CONFLICT (add/add): Merge conflict in lib/utilities/aclUtils.js
CONFLICT (add/add): Merge conflict in lib/utilities/RelayMD5Sum.js
CONFLICT (add/add): Merge conflict in lib/utapi/utilities.js
CONFLICT (add/add): Merge conflict in lib/utapi/utapi.js
CONFLICT (add/add): Merge conflict in lib/services.js
CONFLICT (add/add): Merge conflict in lib/server.js
CONFLICT (add/add): Merge conflict in lib/metadata/wrapper.js
CONFLICT (add/add): Merge conflict in lib/metadata/bucketfile/backend.js
CONFLICT (add/add): Merge conflict in lib/metadata/acl.js
CONFLICT (add/add): Merge conflict in lib/metadata/ModelVersion.md
CONFLICT (add/add): Merge conflict in lib/kms/wrapper.js
CONFLICT (add/add): Merge conflict in lib/kms/utilities.js
CONFLICT (add/add): Merge conflict in lib/kms/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/kms/file/backend.js
CONFLICT (add/add): Merge conflict in lib/kms/common.js
CONFLICT (add/add): Merge conflict in lib/data/wrapper.js
CONFLICT (add/add): Merge conflict in lib/data/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/data/file/backend.js
CONFLICT (add/add): Merge conflict in lib/auth/vault.js
CONFLICT (add/add): Merge conflict in lib/auth/streamingV4/constructChunkStringToSign.js
CONFLICT (add/add): Merge conflict in lib/auth/streamingV4/V4Transform.js
CONFLICT (add/add): Merge conflict in lib/auth/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/api/serviceGet.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutCopyPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutACL.js
CONFLICT (add/add): Merge conflict in lib/api/objectPut.js
CONFLICT (add/add): Merge conflict in lib/api/objectHead.js
CONFLICT (add/add): Merge conflict in lib/api/objectGetACL.js
CONFLICT (add/add): Merge conflict in lib/api/objectGet.js
CONFLICT (add/add): Merge conflict in lib/api/objectDelete.js
CONFLICT (add/add): Merge conflict in lib/api/objectCopy.js
CONFLICT (add/add): Merge conflict in lib/api/multipartDelete.js
CONFLICT (add/add): Merge conflict in lib/api/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in lib/api/listParts.js
CONFLICT (add/add): Merge conflict in lib/api/listMultipartUploads.js
CONFLICT (add/add): Merge conflict in lib/api/initiateMultipartUpload.js
CONFLICT (add/add): Merge conflict in lib/api/completeMultipartUpload.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutVersioning.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutACL.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPut.js
CONFLICT (add/add): Merge conflict in lib/api/bucketHead.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGetVersioning.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGetACL.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGet.js
CONFLICT (add/add): Merge conflict in lib/api/bucketDelete.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/setUpCopyLocator.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/removeAWSChunked.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/createKeyForUserBucket.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketShield.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketDeletion.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketCreation.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/authorization/prepareRequestContexts.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/authorization/aclChecks.js
CONFLICT (add/add): Merge conflict in lib/api/api.js
CONFLICT (add/add): Merge conflict in lib/Config.js
CONFLICT (add/add): Merge conflict in index.js
CONFLICT (add/add): Merge conflict in docker-entrypoint.sh
CONFLICT (add/add): Merge conflict in constants.js
CONFLICT (add/add): Merge conflict in config.json
CONFLICT (add/add): Merge conflict in conf/authdata.json
CONFLICT (add/add): Merge conflict in circle.yml
CONFLICT (add/add): Merge conflict in bin/list_bucket_metrics.js
CONFLICT (add/add): Merge conflict in bin/create_encrypted_bucket.js
CONFLICT (add/add): Merge conflict in README.md
CONFLICT (add/add): Merge conflict in LICENSE
CONFLICT (add/add): Merge conflict in DockerfileMem
CONFLICT (add/add): Merge conflict in Dockerfile
CONFLICT (add/add): Merge conflict in DESIGN.md

@ironman-machine try

Hello @alexanderchan-scality
"try": Failure: trigger_ci_build error: request failed with status code: 400

@ironman-machine
DEFAULT_BRANCH=master
try

Hello @alexanderchan-scality
"DEFAULT_BRANCH=master": Success
"try": Failure: trigger_ci_build error: request failed with status code: 400

@ironman-machine
DEFAULT_BRANCH=masater
SCALITY_INTEGRATION_BRANCH=master
SCALITY_FEDERATION_BRANCH=master
SCALITY_S3_BRANCH=fwdport/7.4-orbit
try

Hello @alexanderchan-scality
"DEFAULT_BRANCH=masater": Success
"SCALITY_INTEGRATION_BRANCH=master": Success
"SCALITY_FEDERATION_BRANCH=master": Success
"SCALITY_S3_BRANCH=fwdport/7.4-orbit": Success
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/20331' with the following env. args:
{
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "masater",
    "SCALITY_INTEGRATION_BRANCH": "master",
    "SCALITY_FEDERATION_BRANCH": "master",
    "SCALITY_S3_BRANCH": "fwdport/7.4-orbit"
}

PR has been updated. Reviewers, please be cautious.

CONFLICT (add/add): Merge conflict in tests/unit/utils/setPartRanges.js
CONFLICT (add/add): Merge conflict in tests/unit/utils/responseStreamData.js
CONFLICT (add/add): Merge conflict in tests/unit/utils/aclUtils.js
CONFLICT (add/add): Merge conflict in tests/unit/metadataswitch.js
CONFLICT (add/add): Merge conflict in tests/unit/helpers.js
CONFLICT (add/add): Merge conflict in tests/unit/healthchecks/healthcheckResponse.js
CONFLICT (add/add): Merge conflict in tests/unit/encryption/kms.js
CONFLICT (add/add): Merge conflict in tests/unit/bucket/bucket_mem_api.js
CONFLICT (add/add): Merge conflict in tests/unit/bucket/bucketCreation.js
CONFLICT (add/add): Merge conflict in tests/unit/auth/V4Transform.js
CONFLICT (add/add): Merge conflict in tests/unit/api/transientBucket.js
CONFLICT (add/add): Merge conflict in tests/unit/api/serviceGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectPutACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectPut.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectHead.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectGetACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectACLauth.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multipartUpload.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multipartDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/listParts.js
CONFLICT (add/add): Merge conflict in tests/unit/api/listMultipartUploads.js
CONFLICT (add/add): Merge conflict in tests/unit/api/deletedFlagBucket.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketPutACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketPut.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketHead.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketGetACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketACLauth.js
CONFLICT (add/add): Merge conflict in tests/unit/DummyRequest.js
CONFLICT (add/add): Merge conflict in tests/unit/Config.js
CONFLICT (add/add): Merge conflict in tests/performance/s3standard.js
CONFLICT (add/add): Merge conflict in tests/functional/s3curl/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/s3cmd/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/jaws/src/test/java/com/scality/StreamV4AuthTest.java
CONFLICT (add/add): Merge conflict in tests/functional/fog/tests.rb
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/support/withV4.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/support/config.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/service/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/rangeTest.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/putPart.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/putObjAcl.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectOverwrite.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectHead_compatibleHeaders.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectHead.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectCopy.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/mpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/listParts.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/getRange.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/getMPU_compatibleHeaders.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/deleteObject.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/deleteMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/copyPart.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/compluteMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/bigMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/mocha.opts
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/authV4QueryTests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/authV2QueryTests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/index.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/testBucketVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/testBucketStress.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/putAcl.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/listingCornerCases.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/head.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/utility/provideRawOutput.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/utility/bucket-util.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/json/mem_credentials.json
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/fixtures/project.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/index.js
CONFLICT (add/add): Merge conflict in package.json
CONFLICT (add/add): Merge conflict in lib/utilities/logger.js
CONFLICT (add/add): Merge conflict in lib/utilities/healthcheckHandler.js
CONFLICT (add/add): Merge conflict in lib/utilities/collectResponseHeaders.js
CONFLICT (add/add): Merge conflict in lib/utilities/aclUtils.js
CONFLICT (add/add): Merge conflict in lib/utilities/RelayMD5Sum.js
CONFLICT (add/add): Merge conflict in lib/utapi/utilities.js
CONFLICT (add/add): Merge conflict in lib/utapi/utapi.js
CONFLICT (add/add): Merge conflict in lib/services.js
CONFLICT (add/add): Merge conflict in lib/server.js
CONFLICT (add/add): Merge conflict in lib/metadata/wrapper.js
CONFLICT (add/add): Merge conflict in lib/metadata/bucketfile/backend.js
CONFLICT (add/add): Merge conflict in lib/metadata/acl.js
CONFLICT (add/add): Merge conflict in lib/metadata/ModelVersion.md
CONFLICT (add/add): Merge conflict in lib/kms/wrapper.js
CONFLICT (add/add): Merge conflict in lib/kms/utilities.js
CONFLICT (add/add): Merge conflict in lib/kms/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/kms/file/backend.js
CONFLICT (add/add): Merge conflict in lib/kms/common.js
CONFLICT (add/add): Merge conflict in lib/data/wrapper.js
CONFLICT (add/add): Merge conflict in lib/data/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/data/file/backend.js
CONFLICT (add/add): Merge conflict in lib/auth/vault.js
CONFLICT (add/add): Merge conflict in lib/auth/streamingV4/constructChunkStringToSign.js
CONFLICT (add/add): Merge conflict in lib/auth/streamingV4/V4Transform.js
CONFLICT (add/add): Merge conflict in lib/auth/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/api/serviceGet.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutCopyPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutACL.js
CONFLICT (add/add): Merge conflict in lib/api/objectPut.js
CONFLICT (add/add): Merge conflict in lib/api/objectHead.js
CONFLICT (add/add): Merge conflict in lib/api/objectGetACL.js
CONFLICT (add/add): Merge conflict in lib/api/objectGet.js
CONFLICT (add/add): Merge conflict in lib/api/objectDelete.js
CONFLICT (add/add): Merge conflict in lib/api/objectCopy.js
CONFLICT (add/add): Merge conflict in lib/api/multipartDelete.js
CONFLICT (add/add): Merge conflict in lib/api/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in lib/api/listParts.js
CONFLICT (add/add): Merge conflict in lib/api/listMultipartUploads.js
CONFLICT (add/add): Merge conflict in lib/api/initiateMultipartUpload.js
CONFLICT (add/add): Merge conflict in lib/api/completeMultipartUpload.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutVersioning.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutACL.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPut.js
CONFLICT (add/add): Merge conflict in lib/api/bucketHead.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGetVersioning.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGetACL.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGet.js
CONFLICT (add/add): Merge conflict in lib/api/bucketDelete.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/setUpCopyLocator.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/removeAWSChunked.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/createKeyForUserBucket.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketShield.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketDeletion.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketCreation.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/authorization/prepareRequestContexts.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/authorization/aclChecks.js
CONFLICT (add/add): Merge conflict in lib/api/api.js
CONFLICT (add/add): Merge conflict in lib/Config.js
CONFLICT (add/add): Merge conflict in index.js
CONFLICT (add/add): Merge conflict in docker-entrypoint.sh
CONFLICT (add/add): Merge conflict in constants.js
CONFLICT (add/add): Merge conflict in config.json
CONFLICT (add/add): Merge conflict in conf/authdata.json
CONFLICT (add/add): Merge conflict in circle.yml
CONFLICT (add/add): Merge conflict in bin/list_bucket_metrics.js
CONFLICT (add/add): Merge conflict in bin/create_encrypted_bucket.js
CONFLICT (add/add): Merge conflict in README.md
CONFLICT (add/add): Merge conflict in LICENSE
CONFLICT (add/add): Merge conflict in DockerfileMem
CONFLICT (add/add): Merge conflict in Dockerfile
CONFLICT (add/add): Merge conflict in DESIGN.md

CONFLICT (add/add): Merge conflict in tests/unit/utils/setPartRanges.js
CONFLICT (add/add): Merge conflict in tests/unit/utils/responseStreamData.js
CONFLICT (add/add): Merge conflict in tests/unit/utils/aclUtils.js
CONFLICT (add/add): Merge conflict in tests/unit/metadataswitch.js
CONFLICT (add/add): Merge conflict in tests/unit/helpers.js
CONFLICT (add/add): Merge conflict in tests/unit/healthchecks/healthcheckResponse.js
CONFLICT (add/add): Merge conflict in tests/unit/encryption/kms.js
CONFLICT (add/add): Merge conflict in tests/unit/bucket/bucket_mem_api.js
CONFLICT (add/add): Merge conflict in tests/unit/bucket/bucketCreation.js
CONFLICT (add/add): Merge conflict in tests/unit/auth/V4Transform.js
CONFLICT (add/add): Merge conflict in tests/unit/api/transientBucket.js
CONFLICT (add/add): Merge conflict in tests/unit/api/serviceGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectPutACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectPut.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectHead.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectGetACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectACLauth.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multipartUpload.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multipartDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/listParts.js
CONFLICT (add/add): Merge conflict in tests/unit/api/listMultipartUploads.js
CONFLICT (add/add): Merge conflict in tests/unit/api/deletedFlagBucket.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketPutACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketPut.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketHead.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketGetACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketACLauth.js
CONFLICT (add/add): Merge conflict in tests/unit/DummyRequest.js
CONFLICT (add/add): Merge conflict in tests/unit/Config.js
CONFLICT (add/add): Merge conflict in tests/performance/s3standard.js
CONFLICT (add/add): Merge conflict in tests/functional/s3curl/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/s3cmd/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/jaws/src/test/java/com/scality/StreamV4AuthTest.java
CONFLICT (add/add): Merge conflict in tests/functional/fog/tests.rb
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/support/withV4.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/support/config.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/service/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/rangeTest.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/putPart.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/putObjAcl.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectOverwrite.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectHead_compatibleHeaders.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectHead.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectCopy.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/mpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/listParts.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/getRange.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/getMPU_compatibleHeaders.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/deleteObject.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/deleteMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/copyPart.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/compluteMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/bigMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/mocha.opts
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/authV4QueryTests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/authV2QueryTests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/index.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/testBucketVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/testBucketStress.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/putAcl.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/listingCornerCases.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/head.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/utility/provideRawOutput.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/utility/bucket-util.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/json/mem_credentials.json
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/fixtures/project.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/index.js
CONFLICT (add/add): Merge conflict in package.json
CONFLICT (add/add): Merge conflict in lib/utilities/logger.js
CONFLICT (add/add): Merge conflict in lib/utilities/healthcheckHandler.js
CONFLICT (add/add): Merge conflict in lib/utilities/collectResponseHeaders.js
CONFLICT (add/add): Merge conflict in lib/utilities/aclUtils.js
CONFLICT (add/add): Merge conflict in lib/utilities/RelayMD5Sum.js
CONFLICT (add/add): Merge conflict in lib/utapi/utilities.js
CONFLICT (add/add): Merge conflict in lib/utapi/utapi.js
CONFLICT (add/add): Merge conflict in lib/services.js
CONFLICT (add/add): Merge conflict in lib/server.js
CONFLICT (add/add): Merge conflict in lib/metadata/wrapper.js
CONFLICT (add/add): Merge conflict in lib/metadata/bucketfile/backend.js
CONFLICT (add/add): Merge conflict in lib/metadata/acl.js
CONFLICT (add/add): Merge conflict in lib/metadata/ModelVersion.md
CONFLICT (add/add): Merge conflict in lib/kms/wrapper.js
CONFLICT (add/add): Merge conflict in lib/kms/utilities.js
CONFLICT (add/add): Merge conflict in lib/kms/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/kms/file/backend.js
CONFLICT (add/add): Merge conflict in lib/kms/common.js
CONFLICT (add/add): Merge conflict in lib/data/wrapper.js
CONFLICT (add/add): Merge conflict in lib/data/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/data/file/backend.js
CONFLICT (add/add): Merge conflict in lib/auth/vault.js
CONFLICT (add/add): Merge conflict in lib/auth/streamingV4/constructChunkStringToSign.js
CONFLICT (add/add): Merge conflict in lib/auth/streamingV4/V4Transform.js
CONFLICT (add/add): Merge conflict in lib/auth/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/api/serviceGet.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutCopyPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutACL.js
CONFLICT (add/add): Merge conflict in lib/api/objectPut.js
CONFLICT (add/add): Merge conflict in lib/api/objectHead.js
CONFLICT (add/add): Merge conflict in lib/api/objectGetACL.js
CONFLICT (add/add): Merge conflict in lib/api/objectGet.js
CONFLICT (add/add): Merge conflict in lib/api/objectDelete.js
CONFLICT (add/add): Merge conflict in lib/api/objectCopy.js
CONFLICT (add/add): Merge conflict in lib/api/multipartDelete.js
CONFLICT (add/add): Merge conflict in lib/api/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in lib/api/listParts.js
CONFLICT (add/add): Merge conflict in lib/api/listMultipartUploads.js
CONFLICT (add/add): Merge conflict in lib/api/initiateMultipartUpload.js
CONFLICT (add/add): Merge conflict in lib/api/completeMultipartUpload.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutVersioning.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutACL.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPut.js
CONFLICT (add/add): Merge conflict in lib/api/bucketHead.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGetVersioning.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGetACL.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGet.js
CONFLICT (add/add): Merge conflict in lib/api/bucketDelete.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/setUpCopyLocator.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/removeAWSChunked.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/createKeyForUserBucket.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketShield.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketDeletion.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketCreation.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/authorization/prepareRequestContexts.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/authorization/aclChecks.js
CONFLICT (add/add): Merge conflict in lib/api/api.js
CONFLICT (add/add): Merge conflict in lib/Config.js
CONFLICT (add/add): Merge conflict in index.js
CONFLICT (add/add): Merge conflict in docker-entrypoint.sh
CONFLICT (add/add): Merge conflict in constants.js
CONFLICT (add/add): Merge conflict in config.json
CONFLICT (add/add): Merge conflict in conf/authdata.json
CONFLICT (add/add): Merge conflict in circle.yml
CONFLICT (add/add): Merge conflict in bin/list_bucket_metrics.js
CONFLICT (add/add): Merge conflict in bin/create_encrypted_bucket.js
CONFLICT (add/add): Merge conflict in README.md
CONFLICT (add/add): Merge conflict in LICENSE
CONFLICT (add/add): Merge conflict in DockerfileMem
CONFLICT (add/add): Merge conflict in Dockerfile
CONFLICT (add/add): Merge conflict in DESIGN.md

PR has been updated. Reviewers, please be cautious.

:broken_heart: :umbrella: circleCI test failed.

CONFLICT (add/add): Merge conflict in tests/unit/utils/setPartRanges.js
CONFLICT (add/add): Merge conflict in tests/unit/utils/responseStreamData.js
CONFLICT (add/add): Merge conflict in tests/unit/utils/aclUtils.js
CONFLICT (add/add): Merge conflict in tests/unit/metadataswitch.js
CONFLICT (add/add): Merge conflict in tests/unit/helpers.js
CONFLICT (add/add): Merge conflict in tests/unit/healthchecks/healthcheckResponse.js
CONFLICT (add/add): Merge conflict in tests/unit/encryption/kms.js
CONFLICT (add/add): Merge conflict in tests/unit/bucket/bucket_mem_api.js
CONFLICT (add/add): Merge conflict in tests/unit/bucket/bucketCreation.js
CONFLICT (add/add): Merge conflict in tests/unit/auth/V4Transform.js
CONFLICT (add/add): Merge conflict in tests/unit/api/transientBucket.js
CONFLICT (add/add): Merge conflict in tests/unit/api/serviceGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectPutACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectPut.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectHead.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectGetACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectACLauth.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multipartUpload.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multipartDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/listParts.js
CONFLICT (add/add): Merge conflict in tests/unit/api/listMultipartUploads.js
CONFLICT (add/add): Merge conflict in tests/unit/api/deletedFlagBucket.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketPutACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketPut.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketHead.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketGetACL.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketACLauth.js
CONFLICT (add/add): Merge conflict in tests/unit/DummyRequest.js
CONFLICT (add/add): Merge conflict in tests/unit/Config.js
CONFLICT (add/add): Merge conflict in tests/performance/s3standard.js
CONFLICT (add/add): Merge conflict in tests/functional/s3curl/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/s3cmd/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/jaws/src/test/java/com/scality/StreamV4AuthTest.java
CONFLICT (add/add): Merge conflict in tests/functional/fog/tests.rb
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/support/withV4.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/support/config.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/service/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/rangeTest.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/putPart.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/putObjAcl.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectOverwrite.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectHead_compatibleHeaders.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectHead.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/objectCopy.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/mpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/listParts.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/getRange.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/getMPU_compatibleHeaders.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/deleteObject.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/deleteMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/copyPart.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/compluteMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/object/bigMpu.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/mocha.opts
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/tests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/authV4QueryTests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/legacy/authV2QueryTests.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/index.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/testBucketVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/testBucketStress.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/putAcl.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/listingCornerCases.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/head.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/utility/provideRawOutput.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/utility/bucket-util.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/json/mem_credentials.json
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/fixtures/project.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/index.js
CONFLICT (add/add): Merge conflict in package.json
CONFLICT (add/add): Merge conflict in lib/utilities/logger.js
CONFLICT (add/add): Merge conflict in lib/utilities/healthcheckHandler.js
CONFLICT (add/add): Merge conflict in lib/utilities/collectResponseHeaders.js
CONFLICT (add/add): Merge conflict in lib/utilities/aclUtils.js
CONFLICT (add/add): Merge conflict in lib/utilities/RelayMD5Sum.js
CONFLICT (add/add): Merge conflict in lib/utapi/utilities.js
CONFLICT (add/add): Merge conflict in lib/utapi/utapi.js
CONFLICT (add/add): Merge conflict in lib/services.js
CONFLICT (add/add): Merge conflict in lib/server.js
CONFLICT (add/add): Merge conflict in lib/metadata/wrapper.js
CONFLICT (add/add): Merge conflict in lib/metadata/bucketfile/backend.js
CONFLICT (add/add): Merge conflict in lib/metadata/acl.js
CONFLICT (add/add): Merge conflict in lib/metadata/ModelVersion.md
CONFLICT (add/add): Merge conflict in lib/kms/wrapper.js
CONFLICT (add/add): Merge conflict in lib/kms/utilities.js
CONFLICT (add/add): Merge conflict in lib/kms/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/kms/file/backend.js
CONFLICT (add/add): Merge conflict in lib/kms/common.js
CONFLICT (add/add): Merge conflict in lib/data/wrapper.js
CONFLICT (add/add): Merge conflict in lib/data/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/data/file/backend.js
CONFLICT (add/add): Merge conflict in lib/auth/vault.js
CONFLICT (add/add): Merge conflict in lib/auth/streamingV4/constructChunkStringToSign.js
CONFLICT (add/add): Merge conflict in lib/auth/streamingV4/V4Transform.js
CONFLICT (add/add): Merge conflict in lib/auth/in_memory/backend.js
CONFLICT (add/add): Merge conflict in lib/api/serviceGet.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutCopyPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutACL.js
CONFLICT (add/add): Merge conflict in lib/api/objectPut.js
CONFLICT (add/add): Merge conflict in lib/api/objectHead.js
CONFLICT (add/add): Merge conflict in lib/api/objectGetACL.js
CONFLICT (add/add): Merge conflict in lib/api/objectGet.js
CONFLICT (add/add): Merge conflict in lib/api/objectDelete.js
CONFLICT (add/add): Merge conflict in lib/api/objectCopy.js
CONFLICT (add/add): Merge conflict in lib/api/multipartDelete.js
CONFLICT (add/add): Merge conflict in lib/api/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in lib/api/listParts.js
CONFLICT (add/add): Merge conflict in lib/api/listMultipartUploads.js
CONFLICT (add/add): Merge conflict in lib/api/initiateMultipartUpload.js
CONFLICT (add/add): Merge conflict in lib/api/completeMultipartUpload.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutVersioning.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutACL.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPut.js
CONFLICT (add/add): Merge conflict in lib/api/bucketHead.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGetVersioning.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGetACL.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGet.js
CONFLICT (add/add): Merge conflict in lib/api/bucketDelete.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/setUpCopyLocator.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/removeAWSChunked.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/createKeyForUserBucket.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketShield.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketDeletion.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketCreation.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/authorization/prepareRequestContexts.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/authorization/aclChecks.js
CONFLICT (add/add): Merge conflict in lib/api/api.js
CONFLICT (add/add): Merge conflict in lib/Config.js
CONFLICT (add/add): Merge conflict in index.js
CONFLICT (add/add): Merge conflict in docker-entrypoint.sh
CONFLICT (add/add): Merge conflict in constants.js
CONFLICT (add/add): Merge conflict in config.json
CONFLICT (add/add): Merge conflict in conf/authdata.json
CONFLICT (add/add): Merge conflict in circle.yml
CONFLICT (add/add): Merge conflict in bin/list_bucket_metrics.js
CONFLICT (add/add): Merge conflict in bin/create_encrypted_bucket.js
CONFLICT (add/add): Merge conflict in README.md
CONFLICT (add/add): Merge conflict in LICENSE
CONFLICT (add/add): Merge conflict in DockerfileMem
CONFLICT (add/add): Merge conflict in Dockerfile
CONFLICT (add/add): Merge conflict in DESIGN.md

PR has been updated. Reviewers, please be cautious.


RAD Board motor operation

Validate that RAD can control stepper motor

Issue: no continuity between A+ and BMA 1 or Q1 drain

Issue: no continuity between A+ and BMA 1 or Q1/Q4 drain

Resolved by reflowing solder on header

Issue: Motor does not respond in standalone mode with very basic software. Have probed continuity and relevant pins to attempt to determine issue with no success. Motor is just 'freewheeling' which suggests no current passing through coils as well as minimal current draw from power supply.

Issue: Motor does not respond in standalone mode with very basic software. Have probed continuity and relevant pins to attempt to determine issue with no success. Motor is just 'freewheeling' which suggests no current passing through coils as well as minimal current draw from power supply.

Manually jumped PA15 to 3V with careful placement of a jumper wire. Motor makes noises but does not seem to step.
For future revisions, recommendation is swap PA15 with PA8.

Confirmed RAD motor control by setting registers over SPI and using step/dir for operation. Torque is low, but this should be resolved by figuring out what the appropriate motor control settings are.

Reopening because motor spins but only when the step size register MRES is set to an undefined state of 1111

Issue was that the LSB (least significant byte) was being sent to the stepper driver first. Should be MSB first. Fixed and now the motor works great


[Annoying Bug!!!] The Settings "window" doesn't fit and breaks when next to another windows in the same workspace

Describe the bug
When I have the settings "window" open next to another application like my terminal or the web browser, I can't access the side that is at the edge of my screen. So if the "window" is on the left side, I can't access the left side of it. And if it's on the right, I can't access the right side.
To Reproduce
Open settings "window" next to another app
Expected behavior
To have the app work and shrink according to the space available.
Screenshots
I can't do any right now, since I'm on my phone.
Desktop (please complete the following information):

Distribution: Arch Linux
Window Manager: Hyprland

Additional context
Nothing to add.

Until I get around to making the settings window float, you can add this rule in your hyprland.conf to force the settings to float on top of other windows.
windowrulev2 = float, class:^(.*com.github.Aylur.ags*)$

Hopefully that resolves some irritation for you in the meantime.

I've noticed this too. Can probably change the minimum width of the window

i believe the settings window now floats, so closing this


Update node version in Requirement section

:nut_and_bolt: Description: What code changed, and why?
The current version being return from .nvmrc is 10.15.2.  Updated requirements section to reflect.

I'm not sure what this CI failure means...

I see a few occurences of that failure ^^ in slack, but no discussion or solutions. If it doesn't clear itself up I'd try rebasing on master to see if a new commit fixes it.

@phiggins - Gave it another commit and also tried rebasing as well - seems to be no dice so far.  Do you know who would be right person to tag in this case?

is this weird? .. the content before the : in the branch names?

I initially made these commits before I had access to Chef’s Github.  I
think that’s why the repo was forked first.
Since this is such a small branch, I’m wondering if it might make sense to
close the PR, then I can cut a new branch from master and make the changes
there.  That way we can avoid using a forked repo.  Not sure if that’s the
issue but I haven’t had problems with my other branches and the fork here
is the only difference.
On Mon, Sep 16, 2019 at 2:43 PM susan evans<EMAIL_ADDRESS>wrote:

is this weird? .. the content before the : in the branch names?
[image: github-branch-names]
https://user-images.githubusercontent.com/5489125/64995502-4241a780-d890-11e9-8a17-73ac617ebdf0.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chef/automate/pull/1621?email_source=notifications&email_token=AD7WJTFZWTVRD6VC2A2N5M3QJ74X5A5CNFSM4IXFTSXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD62TPWQ#issuecomment-531970010,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD7WJTFYGFIPAQXWHVKAJ53QJ74X5ANCNFSM4IXFTSXA
.

--
Jamie Degnan — Software Development Engineer
<EMAIL_ADDRESS>CHEF
chef.io http://www.chef.io/   Blog https://blog.chef.io/   Facebook
https://www.facebook.com/getchefdotcom   Twitter
https://twitter.com/chef   Youtube https://www.youtube.com/getchef
619 Western Ave Suite 400, Seattle, WA 98104

I pinged #releng-support who are the Expeditor experts.

Closed in favor of a non-forked version: https://github.com/chef/automate/pull/1631


Add more fields in clinVar

Add variation id and rcv to myVariantInfo - clinVar. Make clinVar available in response.

Codecov Report

Merging #283 into master will increase coverage by 0.06%.
The diff coverage is 50%.

@@             Coverage Diff              @@
##             master     #283      +/-   ##
============================================
+ Coverage     18.76%   18.82%   +0.06%
  Complexity      135      135
============================================
  Files           161      163       +2
  Lines          2009     2013       +4
  Branches        258      258
============================================
+ Hits            377      379       +2
- Misses         1599     1601       +2
  Partials         33       33

Impacted Files
Coverage Δ
Complexity Δ

...vice/mixin/my_variant_info_mixin/ClinVarMixin.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ixin/my_variant_info_mixin/MyVariantInfoMixin.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../web/mixin/my_variant_info_mixin/ClinVarMixin.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ixin/my_variant_info_mixin/MyVariantInfoMixin.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...exus/web/mixin/my_variant_info_mixin/RcvMixin.java
0% <0%> (ø)
0 <0> (?)

.../service/mixin/my_variant_info_mixin/RcvMixin.java
0% <0%> (ø)
0 <0> (?)

...s/service/config/ExternalResourceObjectMapper.java
100% <100%> (ø)
1 <0> (ø)
:arrow_down:

...ortal/genome_nexus/web/config/ApiObjectMapper.java
100% <100%> (ø)
1 <0> (ø)
:arrow_down:

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 b9bad1c...f5ca90b. Read the comment docs.


Invalid datetime values in delivery json metadata in v0.2.0

GUNW products generated using DockerizedTopsApp v0.2.0 have invalid sensing_start and sensing_stop values in their .json metadata files. This causes these products to be rejected when attempting to ingest them into the ASF archive.
For example, from https://hyp3-a19-jpl-contentbucket-1wfnatpznlg8b.s3.us-west-2.amazonaws.com/819086fb-3fb1-4294-8cb2-c1effb453f52/S1-GUNW-D-R-087-tops-20221204_20221122-161627-00157W_00020N-PP-37a3-v2_0_6.json :
"sensing_start": "2022-12-04T16:16:12.000ZZ",
"sensing_stop": "2022-12-04T16:16:42.000ZZ",

This is due to a change in asf_search v5.0.0:

Timestamps in geojson fields now include an explicit Z time zone indicator.

The new build of DockerizedTopsApp pulled in the new version of asf_search, but also still appends an additional Z to the timestamps  at https://github.com/ACCESS-Cloud-Based-InSAR/DockerizedTopsApp/blob/main/isce2_topsapp/delivery_prep.py#L134

Thank you for basically solving this!


Mixture of Versions 0.1.0 and 0.1.1-SNAPSHOT Packages

Expected Behaviour
When building the "all" project from the source I expect some consistency in versions of packages that get built. I.e everything in the project is a SNAPSHOT build or everything is a release.
Actual Behaviour
When building the connector from master there seem to be inconsistencies in the versions that get created:

Look at: https://github.com/adobe/commerce-cif-connector/blob/master/all/pom.xml
I can see versions of 0.1.2, 0.1.1-SNAPSHOT, AND 0.1.0.  Is this intentional?
<parent>
        <groupId>com.adobe.commerce.cif</groupId>
        <artifactId>cif-connector-parent</artifactId>
        <version>0.1.2</version>
        <relativePath>../parent/pom.xml</relativePath>
    </parent>
...
<modelVersion>4.0.0</modelVersion>
    <artifactId>cif-connector-all</artifactId>
    <version>0.1.1-SNAPSHOT</version>
    <packaging>content-package</packaging>
...
 <dependency>
            <groupId>${project.groupId}</groupId>
            <artifactId>cif-connector-content</artifactId>
            <version>0.1.0</version>
            <type>zip</type>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>${project.groupId}</groupId>
            <artifactId>cif-virtual-catalog-content</artifactId>
            <version>0.1.0</version>
            <type>zip</type>
            <scope>provided</scope>
        </dependency>

Steps to Reproduce

clone the repo
checkout master branch
from the root directory perform: mvn clean install -PautoInstallAll

Hi, @godanny86 yes this is intentional the master branch has snapshot versions of all packages & bundles. But you don't need to build this project if you just use it, you can get the released all package from https://github.com/adobe/commerce-cif-connector/releases.
We will add that to the readme. Building it is only needed if you work on the project or going to customize it.

hi @mhaack I'm still a little confused. Yes I understand the master branch has snapshot versions of all packages & bundles... my point is that when you build on master it does not deploy all Snapshot versions, there is a mixture of snapshot and release packages.
https://github.com/adobe/commerce-cif-connector/releases just has zips of the source files. A user still needs to build them in order to get an installable package to AEM:

@godanny86 good point the release versions are on Maven Central, like described on the readme. See https://search.maven.org/search?q=com.adobe.commerce.cif we should add that to the readme. While this is transparent for developers using it as a dependency of their projects it might not be the first place to look to download a package directly.

@godanny86 We cannot constantly release each little change, so yes we will have some SNAPSHOT dependencies between releases. Also the project is not meant to have consistent release versions, each module has its own release cycle. See the README:

Important: do not trigger releases from the reactor (top-level) project because we release each module independently.

We are not doing any "reactor" releases, because this implies that a release triggers a release for each sub-module, even if it doesn't have any change. We don't want to do that, so yes the version numbers will diverge. It's not very important because the all package always has the "right" versions at any time.

BTW, just use the "maven" badge/link on the main page to download the latest released all package.

Thanks @cjelger for the clarification!


VisualVM component not available for GraalVM 21

I have been using GraalVM 17 with Java 17 for a long time without any problems. I have been able to use the visualVM integration for a long time. This seems to not work with GraalVM 21:

Even with the installation active, I do not have the option to even install visualVM as a component.

With GraalVM 17 you can see the difference, as it finds the GraalVM Core and Native Image portions of the JDK. (Ignore the Could not resolve components as I'm using a snap version of vscode that doesn't have the GLIBCXX_3.4.29 installed)
In this case, I am able to attach a VisualVM component to the GraalVM instance.
Looks like the GraalVM 21 is not being recognized as a GraalVM JDK

This is intentional change in GraalVM 21. GraalVM 17 still contains Graal Updater (GU) lists the components from GDS. GraalVM 21 does not contain GU, does not have components on GDS. The intent of GraalVM team was it is like JDK. So this is as designed.

So the documentation for graalvm + visualVM integration for vscode is wrong? There is no way to add visualVM to the vscode using this extension?

Seems like documentation there is out dated. Or it has to mention that this feature is available for GraalVM JDK 17 and older.


Windows GUI: Sheet view improvements

Change sheet view default split ratio and make it resizable. Now it shows more of the bottom contents by default and also after maximizing window.
Also change default monospaced font to match other views. Missed this page when changing the default monospaced font the other day.
Resolves #500

Amended to fix the text view string bug that turns out to also affect this view.


As a User I want to receive a clear error message if a smart contract function has not been executed successfully so that I can react accordingly.

Closing as shipped.


Error: Could not find Cypress test run results

Following the instruction in the docs to can't run the specs.
When I run node test.js I get the following error:
The support file is missing or invalid.

Your `supportFile` is set to `/var/folders/lp/m1rj3k112s1bvqgxsy9ysm840000gp/T/ckan-uat-TBzyzH/support/index.js/index.js`, but either the file is missing or it's invalid. The `supportFile` must be a `.js` or `.coffee` file or, if you're using a preprocessor plugin, it must be supported by that plugin.

Correct your `cypress.json`, create the appropriate file, or set `supportFile` to `false` if a support file is not necessary for your project.

Or you might have renamed the extension of your `supportFile` to `.ts`. If that's the case, restart the test runner.

Learn more at https://on.cypress.io/support-file-missing-or-invalid
{ failures: 1, message: 'Could not find Cypress test run results' }

I have Cypress installed and setup with it's default folder structure.
//test.js
import cypress from "cypress";
import { CKANIntegrationTests } from "ckan-integration-tests/index.js";

const assets = new CKANIntegrationTests();
assets.addAllSpecs();

cypress
  .run(assets.options)
  .then(console.log)
  .catch(console.error)
  .finally(() => assets.cleanUp());

package.json
{
  "name": "test-int-tests",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "type": "module",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "ckan-integration-tests": "git+https://github.com/datopian/ckan-integration-tests.git",
    "ckanClient": "git+https://github.com/datopian/ckan-client-js.git#bfa869866c3bf50ada2bbc30376e0191c9c263c7",
    "cypress": "4.9.0",
    "frictionless": "git+https://github.com/frictionlessdata/frictionless-js.git#1e48a2d0c545e4294107197fa6100308ab8488e1"
  }
}

cypress.json
{
  "chromeWebSecurity": false,
  "baseUrl": "https://ckan.myserver.org/",
  "pageLoadTimeout": 120000,
  "env": {
    "FRONTEND_URL": "https://ckan.myserver.org/",
    "API_KEY": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "CKAN_USERNAME": "joanne.doe",
    "CKAN_PASSWORD": "joannes-very-secret-password",
    "ORG_NAME_SUFFIX": "_organization_test",
    "DATASET_NAME_SUFFIX": "_dataset_test"
  }
}

Environment
Cypress: 4.9.0
Node: v14.15.1
Tried also with Cypress v6.0.0 but didn't work.

By this file path /var/folders/lp/m1rj3k112s1bvqgxsy9ysm840000gp/T/ckan-uat-TBzyzH/support/index.js/index.js I would say it might be a bug in creating the supportFile path — wouldn't it make sense to be ``/var/folders/lp/m1rj3k112s1bvqgxsy9ysm840000gp/T/ckan-uat-TBzyzH/support/index.js` instead?
Maybe we can review the code that handles this to check whether the functions and methods have changed behavior in recent versions:
https://github.com/datopian/ckan-integration-tests/blob/main/index.js#L46-L65

@cuducos great catch! I also noticed that and it's really weird. On line 52 if I change "index.js" to lets say "index1.js" then output in the error will be: watever/index1.js/index1.js I think this might be OS level issue, as @cotts tried at his end he didn't have this error.
I use Mac OS, version 11.0.1

I think this might be OS level issue

Makes sense. As far as I can remember, @cotts and I are running on Linux, so if you're on macOS, there is a chance that this behavior is OS-related…


Extend example_dag for Dataproc Batch operators

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

looks good, please send PR to the community


ValueError: The condensed distance matrix must contain only finite values

Hello,
This is error is related to #1. Once that issue was solved and @fbeghini closed it, I reinstalled hclust2 in a conda environment, as follows:
conda create -n hclust
conda activate hclust2
conda config --env --add channels bioconda
conda install --yes hclust2

Using the same merged abundance file mentioned in #1 (created using metaphlan3), I ran the following command:
$ hclust2.py --in merged_abundance_table.txt -l --out heatmap.png
And got the following error:
Traceback (most recent call last):
  File "/opt/conda/envs/hclust2/bin/hclust2.py", line 825, in <module>
    hclust2_main()
  File "/opt/conda/envs/hclust2/bin/hclust2.py", line 805, in hclust2_main
    cl.fhcluster()
  File "/opt/conda/envs/hclust2/bin/hclust2.py", line 386, in fhcluster
    self.fhclusters = sph.linkage(self.f_dm, method=self.args.flinkage)
  File "/opt/conda/envs/hclust2/lib/python3.8/site-packages/scipy/cluster/hierarchy.py", line 1057, in linkage
    raise ValueError("The condensed distance matrix must contain only "
ValueError: The condensed distance matrix must contain only finite values.

This being a different error than before, I assume that hclust2 on bioconda channel had been updated to fix issue #1. In case I was wrong, I followed the advise @fbeghini posted in #1 to manually remove the first line  (containing the string #mpa_v30_CHOCOPhlAn_201901) and the column, NCBI_tax_id, but got the same error.
Looking over the matrix in the merged abundance file, it is not immediately clear why the matrix would contain non-finite values.

There're a couple of combinations of rows having lot of 0s and when calculating the correlation both of the numerator and denominator being 0 will result in NaN.

I'd filter out only the entries on the species level first, and then maybe try a different method for species/feature distance calculation

Hi there,
I'm having the exact same issue as nitishnih when trying to generate a heat map (using hclust2) from a merged abundance table generated by metaphlan3. I also followed the step for altering the abundance table by removing the header and the NCBI_tax_id column. I was just wondering if this issue had been fixed or resolved? Or is the recommended advice to use an alternative species/feature distance calculation method?

Kindly Respond to the issue on biobakery help forum regarding the same issue or please explain here itself that how to resolve the error when rows are having 0 values ? how to remove them from the merged_abundance_table_species_table.txt ?

I'm having this issue too. What's the fix?
Thank you,
Rene

I am also having this issue

It confused me many days.
Does someone have any solutions?
Thanks,
Bai

I also encountered this error.
I was able to run successfully when I turned off clustering (--no_fclustering and --no_sclustering).
This error may occur if the samples contain mostly 0's.
You can avoid this by adding a very small value (e.g. 0.01) to all samples compared to the data.

maybee you want to check: https://forum.biobakery.org/t/hclust2-py-error-distance-matrix-finite-values/1732/2
I would appreciate if somebody can tell me if the change is valid or not.
Eric

Just a note that I also see this, including with the example data that comes with this repo using the run.sh script.    Please pass vmin/vmax directly to the norm when creating it.

I have the same problem, I am using it in a cluster whose system is similar to Linux, do you know how to solve it?


Tags - Unable to disable ""Members must tag all spend" after renaming multilevel tag

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.72-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Precondition:

Workspace has multilevel dependant tags (csv file below)
"Are these independent tags?" is unchecked when setting up dependant tags on OD (important)

Go to staging.new.expensify.com
Go to workspace settings (workspace with multilevel dependant tags)
Go to Tags
Click Settings
Enable "Members must tag all spend"
Click on the tag
Rename the tag and save it
Click Settings
Disable "Members must tag all spend"
Refresh the page
Click Settings

Expected Result:
"Members must tag all spend" will remain disabled
Actual Result:
"Members must tag all spend" is enabled again after refreshing the page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/9db62108-7037-4d34-a205-abb14fe47475
Bug6475924_1715260443757!Dependent_-_Multi_Level_tags_NEW.csv
View all open jobs on GitHub

@trjExpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #wave-collect - Release 1

@lanitochka17, why are they testing manually uploaded multiTags on Collect in NewDot? We don't intend to support that in NewDot, only via an accounting integration and the PR for that is in development.
It looks like you're seeing some flakiness around that. Going to close this.


Finished first working version for elm 0.19 (only small css is missing).

Thank you for the great work!

:) Thanks for writing it, in the first place!


Fixes #153 Change to page fragment caching.

Also switches to database caching by default
Adds settings export to get the TTL

I talked to Maggie, currently we'll just cache the partial fragment for student list.
In testing this, fragment caching has to be applied to the lowest level, so it could not be on a high template page, it seemed like nothing was cached. Also it is configured to cache differently per advisor.username.

Did you change
DJANGO_LOGGING_LEVEL=INFO
There is a bug with Django Debug Toolbar when the logging level is debug. I only was looking to see what was cached.
The second one is a good question. Yes what I tested was the /advisors/ route (now the My Students page)
Currently the cached in this change is the student_list_partial. Looking at this it's included from more places than I thought. I'm only varying on advisor.username which might not be the only value to vary on.

advisor_detail (AdvisorView /advisors/)

This is from the advisors link

class_site_detail (ClassSiteView /classes/)

I think this view was removed back in #115

student_list (StudentsListView /students/)

This is used when searching, need to verify that this is working, might need to vary on the search parameter

cohort_detail (CohortView /cohorts/)

I'm not sure where this path is linked from but it is active if you have cohorts loaded. I don't have any locally but this may also need to vary on something else.

Doh, okay, I had forgotten to update my .env. I can now see better how this all works. Let me know if you want me to do more testing.

Thanks, @jonespm!


Issue with running Windows 10 App after deploying on device - Blank white screen on startup

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

I have deployed an ionic app to a windows 10 surface pro using visual studio 2017 build option. On starting the app, a blank white screen shows up and the app is stuck without proceeding further.
Expected behavior:

I would expect the app to start normally as its happening without any issues in other platforms. have deployed the same app on Android device ( Android phone and tablet ) and Apple device ( IPAD )
Steps to reproduce:

Did a git clone of the repository on the actual device where I have installed the app.
Installed all dependencies ( node, npm install, visual studio 2017 installed )
Ionic Cordova add platform windows
Then launch Visual studio 2017 to open the .vs2013.sln file, create app package and run the Add-AppDevPackage in windows PowerShell to install the app on the device.
Try to run the app. The app gets stuck at this point. If I try to serve it locally on the windows device, it works fine. However, the actual app doesn't run as expected.
Could you please provide some pointers to help fix this issue as we have chosen the Ionic framework for a POC and have to demo the use of this framework on all platforms. Its working fine on Android and IOS devices.

Related code:

insert short code snippets here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here
@ionic/cli-utils : 1.14.0
ionic ( Ionic CLI ) : 3.14.0

global packages:
cordova ( Cordova CLI) : 7.1.0

local packages:

@ionic/app-scripts : 2.1.4
Cordova Platform : windows 5.0.0
Ionic Framework : ionic-angular 3.6.1

System:

Node: v6.11.4
npm: 3.10.10
OS: Windows 10

Misc:

backend:pro

Hello! Thank you for opening an issue with us!
The Ionic Framework issues list is designated for the reporting of bugs with the Ionic Framework or for requesting new features. As this seems like more of a support question I am going to close this issue after asking around a bit to see if one of our (very few) Windows users has any pointers.
I urge that you ask this question on our forum or on our slack channel. You are much more likely to reach a far wider audience on either of those forums, including people who have run Ionic apps on a Windows platform.
Thanks for using Ionic!

Please be sure to ask this question on our forum or on our slack channel. Closing now since this is not an Ionic Framework related issue.


Problem connecting to Android

Hello Nelderson. Only the desktop version works and on localhost. If you try to use it on your mobile phone with wi-fi it is not working and it will be locked on the screen of the image that I sent. I await your help.
In the image below you have an error example using the Droid4X android emulator.
The error only happens if you try to use with android.
https://i.imgur.com/DpMveXt.png

Have you enabled outside connections to your local machine? If not connections such as the Android phone (even an emulator) won't be able to connect. The best situation to test this is to host externally on something like Heroku or DigitalOcean and try to connect from both devices again.

Hi. Could you tell me how to activate the external connection.
Maybe I'm doing it wrong or I do not know how to do it.

Unfortunately this isn't a simple explanation as I would need to know your current network setup, the relevant part of the readme would be the last section if you have this in theory the server will allow outside connections but unless your machine the server is running on allows external connections is a separate thing.
I'd advise reading up on how to allow external connections to your machine, maybe follow a tutorial on how to connect to a simple node.js server from your phone and then the knowledge should be transferable to this situation.

You need simply add my script on your server ;)

var allowCrossDomain = function(req, res, next) {
res.header('Access-Control-Allow-Origin', '*');
res.header('Access-Control-Allow-Methods', 'GET,PUT,POST,DELETE');
res.header('Access-Control-Allow-Headers', 'Content-Type, x-access-token');
if (req.method === "OPTIONS")
res.send(200);
else
next();
}
//----------------------------------
// SET ROUTES FOR EXPRESS API HERE:
//----------------------------------
// allow url
app.use(allowCrossDomain);

OK. I was able to tidy up and connect now.
Thanks a lot for the help.


Laravel UI

Laravel Version
11.3.1
PHP Version
8.3.2
Database Driver & Version
No response
Description
Sorry, I have to report a bug in this repository because the Laravel UI repository does not open discussions for existing issues. I am experiencing a problem where I cannot install Laravel UI when I use PHP 8.3. The following is a problem that I experienced, I hope it can help me without having to downgrade the php version that I am using

Steps To Reproduce

Install laravel 11
Choose php 8.3.xx
Run composer require laravel/ui
In my case, error like this

Hi there,
Thanks for reporting the problem you are encountering, but it looks like this is a question which may be better suited for a support channel. We only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repository you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


web page header text/ links barely visible in dark mode

Uhh, so I have a vivid recollection of when I wrote this issue it was grey color text on yellow background... but we don't seem to have that in dark mode, it's just light grey on dark grey so... I dunno, must have been some rendering bug or so? Can't reproduce, so closing.

Ah, now I know. Other pages (not index page) has a yellow top menu bar, like https://www.acton-lang.org/learn/ - that's where this happens! Need to fix!

Fixed in https://github.com/actonlang/www.acton-lang.org/commit/288e27c816ee032fbeeb998a972994c9b99152bb. Closing.


Confirmation windows width ("approve" and "transaction" windows)

Motivation
I'v exp. in Ui/Ux dev, so will be glad to help you if needed ;)
Usage example
All of this "confirmation", "approve" and "transaction" windows are so wide on full screen.
Possible implementations
Just make it much narrow, like 300-400px width and centered.

Can you explain better what you mean? I think could be related to this issue: #201


Add keychain plugin

This plugin integrates the Keychain tool[1] in to the project.
[1] keychain

Thanks for this, @jbenden! I hadn't seen Keychain before...looks like a useful tool


Invalid assets via /apy

There seems to be assets that are not valid and not available in the Beefy app, e.g. FORTRESS-BNB
Can you double check to ensure these are correct?

yes, there could be APYs of unimplemented platforms, probably not a big deal


Cursor looks strange when it is in certain area under the title bar

VSCode Version:1.41.1 (language: Chinese simplified)
OS Version: Windows 10, Enterprise LTSC, 1809, 17763.914

Steps to Reproduce:

Open VSC
Open at least one file with VSC
Move your cursor to the area under the title bar and behind the files' labels
You see this, which is different from the usual hand-like icon (significantly rougher):

(sorry for photographing the screen. It seems that I can't catch this one using the screenshot tool... I have no other way but to photograph.)

Does this issue occur when all extensions are disabled?: Yes
(Probably the image is not loaded properly? ...If this is a feature instead of a bug please ignore me... )

The cursor indicates that you can pick the entire group and move it around in the editor grid.


test-branch/execute-job/wrong-comment-on-pr/9e0ca2a7-3386-4d8c-9cd0-329dbf626763

PR for testing 44679a59c2a484ba29cbdd9272152caefb440923

comment 1


How can I use Pandomium on javafx

I want to use Pandomium on javafx, so I used SwingNode, my code is as follows.
package org.panda_lang.pandomium;

import javafx.application.Application;
import javafx.embed.swing.SwingNode;
import javafx.scene.Scene;
import javafx.scene.layout.BorderPane;
import javafx.stage.Stage;
import org.panda_lang.pandomium.settings.PandomiumSettings;
import org.panda_lang.pandomium.wrapper.PandomiumBrowser;
import org.panda_lang.pandomium.wrapper.PandomiumClient;

import javax.swing.*;

public class PandomiumFXTest extends Application {

    public static void main(String[] args) {
        launch(args);
    }

    @Override
    public void start(Stage primaryStage) throws Exception {
        PandomiumSettings settings = PandomiumSettings.getDefaultSettings();

        Pandomium pandomium = new Pandomium(settings);
        pandomium.initialize();

        PandomiumClient client = pandomium.createClient();
        PandomiumBrowser browser = client.loadURL("https://panda-lang.org");

        // create swing node
        SwingNode swingNode = new SwingNode();
        JPanel jpanel = new JPanel();
        jpanel.add(browser.toAWTComponent());
        swingNode.setContent(jpanel);

        // create a border pane
        BorderPane parent = new BorderPane();
        parent.setCenter(swingNode);
        Scene scene = new Scene(parent, 400, 400);
        primaryStage.setScene(scene);
        primaryStage.setOnCloseRequest(windowEvent -> {
            pandomium.dispose();
            System.exit(0);
        });
        primaryStage.show();
    }
}

But I failed, I get a empty app and look like it

Is there any way to solve the proplem?
Thanks!

Unfortunately it works only with AWT/Swing because JCEF is too complicated to embed in SwingNode :(
You'd have to change the structure of your application. It's not as hard as you think, and remember - you can also embed JavaFX components in Swing using JFXPanel.

Thanks very much！


trigger custom events in addition to jquery events

According to the discussion in #180 the first step to removing the jquery events is to trigger native events in addition to the jquery ones.
This PR triggers native events everywhere that jquery events are triggered. All events are also renamed, since they would trigger duplicates otherwise (jquery listens to both jquery and native events alike, but only triggers jquery events).
In order to drop the jquery events, it is also needed to change all listeners, since the event data looks slightly different.
I'm willing to take on converting all the listeners as well, since it solves some bugs I've had with running multiple instances of jQuery, and events not triggering properly.

Now I feel a bit silly, considering that #97 already exists, which is a much more complete approach than mine. Leaving this up for now, but merging #97 is probably better.

Please note I've applied the Promise/event related changes from #97 on top of master in https://github.com/chafey/cornerstone/compare/master...zachasme:removejquery. It implements part of the EventTarget interface for non-element events.

@zachasme Cool! What's the status on merging that into the main repo? Anything I can do to help out?

Merged manually! Thanks!


Documentation bug: ZoneComponent

The documentation for pc.Entity.addComponent refers to something called a "zone", and provides the broken link https://developer.playcanvas.com/en/api/pc.ZoneComponent.html.
Either the documentation page for ZoneComponent is indeed missing, or the documentation for addComponent is wrong or outdated. I suspect that the latter.
Is this the right way to report this? I'll apologize and try another way if not.

I'm confused. I don't see any reference to pc.ZoneComponent. Can you reload that page after clearing your browser cache?

I cleared the browser cache and reloaded the page, and the reference is indeed gone now. Problem solved.
Here's how it looked earlier today: