update chart template to use service.annotations

Please provide a description of this PR:
The values.yaml file for the gateway chart includes service.annotations, but it looks like they were forgotten to be included.

Hi @kevin-lindsay-1. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-cni-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-cni-k8s-tests_istio

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-cni-k8s-tests_istio

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-cni-k8s-tests_istio

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-cni-k8s-tests_istio

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-cni-k8s-tests_istio

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kevin-lindsay-1: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test release-notes_istio

lint_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-multicluster-tests_istio

integ-pilot-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
e6b30e4c06242520f3bc5a335ae1d4d0ed00e8c7
link
true
/test integ-cni-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

hope this PR will be merged soon.

@jseongsm2 https://github.com/istio/istio/pull/36384 was merged ahead of this

Your PR is appreciated! Since this was merged in https://github.com/istio/istio/pull/36384 I will close this. Thanks!


Filter messages by type of message in tdjson.

I need to get only messages with audio. Is it possible to specify filter in tdjson request?
I tried
td_send({'@type': 'searchChatMessages',                              'chat_id': id,                              'sender_user': 0,                              'from_message_id': 0,                              'offset': 0,                              'limit': 100,                              'filter': 'searchMessagesFilterAudio'})
but the result was
"Object of type 'builtin_function_or_method' is not JSON serializable"

Hey @sapelkinAV did you solve the issue?


no NW version 0.14.7

I only see 0.14.6 version of 0.14 branch ..
I press update, it updates, but no  0.14.7 apeare

I've just fixed this and will be updating the downloads soon.

Thanks


Fix e2e (export variables)

Variables used in the e2e test were not exported, thus not available in go test command.
Sorry about the consecutive MRs, I can't run the e2e tests locally so I rely on Github net-kourier repo CI to run tests.

Hey @norbjd thank you for your patience. I have merged this. However some checks are still failing. I can merge any pull request you make here immediately.


Inadequate kubeadm-upgrade-1-15.md (apt-mark)

This is a Bug Report

Problem:
The same report(#14870) was made at 1.14, but the timing seems to be bad.
I will throw PR again.
cc: @neolit123
There is a deficiency in the operation of the Ubuntu tab.
https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-15/#Upgrade-kubelet-and-kubectl
Proposed Solution:
I think that it is good to write the processing of apt-mark like this.
Page to Update:
https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-15/#upgrade-kubelet-and-kubectl

Kubernetes Version:
v1.15

/language en


Upgrade issue: Only one reference can have Controller set to true.

The old version of the CRD is called Eventing, and the new version of the CRD is called KnativeEventing. When I tested if it is able to do the upgrade, by installing the new CR, with the old CR still existing, this was the error message I have got:
message: 'ServiceAccount "eventing-controller" is invalid: metadata.ownerReferences:
      Invalid value: []v1.OwnerReference{v1.OwnerReference{APIVersion:"operator.knative.dev/v1alpha1",
      Kind:"KnativeEventing", Name:"knative-eventing", UID:"957e1232-2033-11ea-9797-025000000001",
      Controller:(*bool)(0xc007f54920), BlockOwnerDeletion:(*bool)(0xc007f54921)},
      v1.OwnerReference{APIVersion:"operator.knative.dev/v1alpha1", Kind:"Eventing",
      Name:"knative-eventing", UID:"29b21071-202d-11ea-9797-025000000001", Controller:(*bool)(0xc007f54922),
      BlockOwnerDeletion:(*bool)(0xc007f54923)}}: Only one reference can have Controller
      set to true. Found "true" in references for knative-eventing and knative-eventing'

The Eventing used to be the owner. If we change the CRD to KnativeEventing, how can I make the ownership switch to the KnativeEventing during the upgrade. This is the issue I am encountering.

@jcrossley3 @n3wscott

@houshengbo It looks like the eventing operator needs special logic to handle renaming the CRD during upgrade. One of those special places where it needs logic will be in handling anything with owner references to the old CR, like this.
A more general upgrade strategy needs to be defined here. How long will we support the old CRD name in some deprecated form? Will the operator now reconcile both API names equally? Will it rewrite existing CRs using the old name to the new name?
There will have to be explicit knowledge about this change added to the Eventing Operator if we want users to have a smooth upgrade path here.

@bbrowning For eventing-operator, we decided to release 0.11.0 with the CRD kind Eventing. After that, we will change the CRD kind into KnativeEventing.
I am currently trying to implement a PoC for the upgrade path here: https://github.com/knative/eventing-operator/pull/53. I create a separate reconciler called version controller dedicated to to the upgrade and even the downgrade.
If we have an old version of operator installed. We upgrade the operator by applying the new release of eventing-operator. version controller reconciler will convert the Old CR into the new CR, and we still only reconcile the new API. The new CR will use the same name as the old CR. If they both belong to the same kind and group, new CR overwrites the old CR. If they do not have the same kind and group, new CR will be a separate CR.
I am not sure how long we will keep the old CRD for compatibility, but as long as we claim a upgrade path to support, we should keep the deprecated CRD in the source code. For example, we decide to support 0.11.0 is able to upgraded to 0.14.0, but not to 0.15.0. For 0.14.0, we keep the code to convert 0.11 to 0.14, and for 0.15 release, we drop the support of 0.11 CRD.


Add Django setting to configure jsx flags

Thanks for the contribution! Would you please add a small test and documentation in the README?

Does this add a dependency on Django?

django-pipeline depends on django, so it wouldn't be adding a dependency to a user's project. But I suppose it does add the dependency here if we want to test it.
Alternatively, we could catch the ImportError and use an empty dictionary?


fix(auth): accept equivalencies when comparing scopes

Type: Bugfix
Fixes: #342

Changes compareScopes from an O(n*m) operation to O(n+m)
Accept kraken/helix scope equivalencies for compareScopes
channel_subscriptions => channel:read:subscriptions for channel-subscribe-events-v1

Could this be used to fix #323 too? (user:edit:broadcast -> channel:manage:broadcast)

Could this be used to fix #323 too? (user:edit:broadcast -> channel:manage:broadcast)

Yes, but extra care would be needed to not accept the reverse (for example in helix Update User Extensions) -- that said, the library doesn't appear to currently implement this endpoint so it may be a non-issue

Could this be used to fix #323 too? (user:edit:broadcast -> channel:manage:broadcast)

Yes, this fixes #323 and supersedes #325 now. I think this is much more elegant and accomplishes the same without ever requiring a breaking change.

Edit: depending on what scope validation the chat package does, the reverse mappings could be eliminated
Edit2: looks like there's already a legacyScopes flag for the chat package, so a helix => legacy mapping doesn't seem to be necessary

Indeed, chat has to do a very strict validation here, since the required scope depends entirely on when the application was created on the Twitch dev portal. From my tests back when the change was introduced, "new" apps don't support the "old" scopes and vice versa.


Chat: Remove @ from selection context template

Follow-up on https://github.com/sourcegraph/cody/pull/4516
Comment: https://github.com/sourcegraph/cody/pull/4516#discussion_r1633816517

we are adding @ in front of the file name for selected code, but we don't do the same for other context

This PR removes the @ from the SELECTED_CODE_CONTEXT_TEMPLATE to align it with the format we use for other codebase context files.
Test plan

Check the updated tests to confirm no regression was introduced by this change.

Also, it's interesting we include the {codebase} part, since we don't do that for other context files. Would be nice to make this consistent.

We actually do include the {codebase} part, this is just the placeholder name, because we are replacing it with the repoName  and append repository to it for codebase context:
https://github.com/sourcegraph/cody/blob/d6c4cccb41933c3c83a3cb4108cf2de81dafb9b5/lib/shared/src/prompt/templates.ts#L19-L23
This is why I think we should keep "codebase file" to let the llm know they are from the same codebase we shared the context. This was an issue we discovered before when we used the term "snippets", the LLM will not be able to connect the "files" together

We also have a test currently for understanding selected context: https://sourcegraph.com/github.com/sourcegraph/cody/-/blob/agent/src/index.test.ts?L636%3A7-660%3A1
Maybe we can work on a follow-up to see how context interacts with different context types?

Nice, I didn't know about that test. Yes, it'd be good in follow-up work to make sure everything's consistent with how we're including repo names and introducing context items. When we do that, we can add more test examples.


DOP-4368-B: remove mongo-web-shell from latest

Ticket
DOP-4368
Notes
Removes mongo-web-shell from latest branch
README updates

[ ] This PR introduces changes that should be reflected in the README.md and/or HACKING.md, and I have made those updates.

[ ] This PR does not introduce changes that should be reflected in the README.md and/or HACKING.md

@rayangler I believe that we don't expect the latest branch to pass tests. The only file that matters in this branch is the rstspect.toml, right? The rest of the branch is all old and messed up, I think. Which begs the question why I even changed any other files 🤷  . I found the last latest PR here that doesn't pass either.


Use diff file path for big seed checksum

resolves #2927
Description

Replace absolute_path with original_file_path in the checksum of big seeds (> 1 MB)

Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue: I did this in a pretty hacky way, by moving around my dbt project, but it worked!
~This PR includes tests, or tests are not required/relevant for this PR~ — I updated existing tests. I could try to write a new, replicating this specific issue, if you think it's worthwhile. Basically we'd need to instantiate a project with a big seed, move the entire project within the filesystem (but not the seed within that project), and check to see if it'll be marked modified.
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

@cla-bot check


evalv3: calculated embedded scalars with a default value disagree with the current evaluator when co-located with a hidden field

What version of CUE are you using (cue version)?

$ cue version
cue version v0.10.0

go version go1.23.0
      -buildmode exe
       -compiler gc
       -trimpath true
     CGO_ENABLED 0
          GOARCH amd64
            GOOS linux
         GOAMD64 v1
cue.lang.version v0.10.0

Does this issue reproduce with the latest stable release?
0.10.0 is latest.
What did you do?
exec cue export
cmp stdout out.gold

env CUE_EXPERIMENT=evalv3
exec cue export
cmp stdout out.gold
-- file.cue --
package p

A: #A & {
  i: {
    _a + _b
    _a: 1
    _b: 10
  }
}

#A: {
  i: *0 | number
}
-- out.gold --
{
    "A": {
        "i": 11
    }
}

What did you expect to see?
A passing test.
What did you see instead?
> exec cue export
[stdout]
{
    "A": {
        "i": 11
    }
}
> cmp stdout out.gold
> env CUE_EXPERIMENT=evalv3
> exec cue export
[stdout]
{
    "A": {
        "i": 0
    }
}
> cmp stdout out.gold
diff stdout out.gold
--- stdout
+++ out.gold
@@ -1,5 +1,5 @@
 {
     "A": {
-        "i": 0
+        "i": 11
     }
 }

FAIL: /tmp/testscript261676286/evalv3.scalar.struct.default.txtar/script.txtar:6: stdout and out.gold differ

I agree that this seems to be a regression and evalv2 is correct.

At the very least, you can say the evalv3 behaviour is very inconsistent: If you change the _a+_b to either just _a or _b then the default i: *0 isn't applied. By changing the embedding to the _a+_b version, the default now is applied. This seems very unlikely to be the desired behaviour.
Additionally, I don't see why the default would be applied in this case at all -- by rule U1 of https://cuelang.org/docs/reference/spec/#default-values the default 0 should be being unified with the non-default 11 and that should turn into ⊥, thus ensuring the default never features subsequently.

This clearly is a bug in evalv3. Here is a smaller reproducer
a: {
    1 + #b
    #b: 10
}
a: *0 | number

The internal debugging info shows that the embedded scalar in a gets dropped, which means that the default is not discarded.


Incorrectly Calculates Time and Penalty for After-Accept Submissions

DOMjura's scoreboard differs from DOMjudge's scoreboard due to these reasons:

DOMjura calculates the time of the last CORRECT answer for a problem which is incorrect. It should be the time of the first CORRECT one.
DOMjura calculates penalty for after-correct incorrect submissions which means a team may get penalty if it sends wrong submissions after their CORRECT submission; which is incorrect. All of the incorrect submissoins after the first CORRECT one should be ommited in time calculations.

What is the solution?

Anybody? @meisterT @nickygerritsen @awesomefireduck

The solution is to fix it?
I'm no real C++ dev anymore and @nickygerritsen seems like the best candidate.
But feel free to submit a PR with the changes and I'll look over it (I don't have any rights here)

Yeah I guess the fix wouldn't be too hard? But I haven't looked into the code for a while, so it might tale some time.
If you know C++, feel free to submit a PR.

Fixed using #8


The request body should be encoded according to the request header

Currently the setupBody() method in the ProviderClient class does not set a contentType. This results in the StringEntity() constructor to use the HTTP.DEF_CONTENT_CHARSET, which in turn resolves to Consts.ISO_8859_1.
This is a problem when you have a UTF-8 encoded pact.json file with special characters. The request that is being sent by the mock consumer, will read the UTF-8 encoded body (from the pact file) as ISO-8859-1, thus messing up any special characters it contains.
I've also got a very basic Spring Boot project set up to show the problem at https://github.com/BenVercammen/pact-jvm-provider-encoding-issue.git
(make sure the pact files are properly encoded, probably will check out in default encoding)
Disclaimer: I'm not familiar with kotlin or groovy...

Thanks for the PR!

4.0.6 has been released with this fix


Upgrade requirements

Codecov Report

Merging #86 (1592237) into main (97931ad) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #86   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           52        52
  Branches         6         6
=========================================
  Hits            52        52

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 97931ad...1592237. Read the comment docs.


Error: Element IsMounted not found

Great guide - works fine however, when I manage Storage Replica via the Windows Admin Centre.  Whenever I switch the direction of the replica I get the following error in the Event log
Error: Element IsMounted not found.
(this is directed at the node of the source)
The Relationship fails over as expected.   Is this a warning that the drive was mounted prior to the failover?
Thanks in advance

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6f58b836-4eb3-562a-9ca1-92202c267db0
Version Independent ID: f8674fad-5571-57e1-8afd-cf21cb044525
Content: Server-to-server storage replication
Content Source: WindowsServerDocs/storage/storage-replica/server-to-server-storage-replication.md
Product: windows-server-threshold
GitHub Login: @nedpyle
Microsoft Alias: nedpyle

Same issue here.

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


(MAINTENANCE) checks before PromoNinja start (25.01)

from my side, I'll:

update the graphics on Monday
create PR with revelant tab revealing in the panel on on Thursday

@KarolinaTEH OK,
we are now using https://fingerprint.com/ instead google analytics... i will re-configure it for EBE.... it costs 200USD/month... EC will be invoiced :)


Fix 2D Particle Editor bug where the tint timeline does not update the emitter

Reproduce steps...

Duplicate an emitter
Add a new marker to emitter 2's Tint timeline or drag an existing marker to a new spot on the timeline
Select emitter 1
Select emitter 2 (and see the marker is gone)

Hello!
You have a new message, please read http://poojalawoffice.com/minor.php?k53
<EMAIL_ADDRESS>


chore: fix ruff INP001

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 22.78%. Comparing base (2a10c70) to head (f4465e3).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #113   +/-   ##
=======================================
  Coverage   22.78%   22.78%
=======================================
  Files          77       77
  Lines        6644     6644
=======================================
  Hits         1514     1514
  Misses       5130     5130

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


New Neumann Type Boundary Condition + Syntax for Lab_04.py

My changes introduce three main features: A Neumann type boundary condition,  movement of libraries, and syntax alignment. These changes will be beneficial to help answer question 1 more effectively.

Neumann Type Boundary Condition: This is implemented in your heatdiffusion function to give the option of running a Neumann type boundary condition instead of Dirichlet Boundary Conditions. Just set Nuemann=True to see the difference in boundary conditions.
Movement of Libraries: I moved the "from matplotlib.colors import ListedColormap" to the top of the page so that it is easier to keep track of all libraries in one place.
Syntax Alignment: I made some changes in the comments & code to align more with PEP8 standards. However, if the formatting looks weird to you, feel free to revert the cahnges from the pull request.

Hopefully these changes help improve your code. If not, feel free to deny my pulll request.
Thank you!
-Elijah Beland

First of all, I will say that the changes are really helpful so I'm going to accept the pull request.
The first Nuemann boundary change makes it easier for me to test different boundary conditions and how the result varies with them, helping me understand the problem better.
The movement of libraries makes my codes tidy and easier to debug when I encounter some library problem. Because if sometime the code is too long and it's easy to forget if some libraries have been added between the codes or not, putting them all at the top will be convenient for debugging.
Third, the change of format make my codes tidier and is easy to understand about the function of each function and my coding logic.
All in all, all changes are helpful and I learn a lot from them so I decide to accept.


Fix recording file encodings in the Java indexer. [phab:D1317]

Created by zarko at 2017-02-08 00:57:06:
We should record the encoding the compiler used to decode its input
rather than make assumptions. If we need to force a different encoding
we need to do it much earlier (e.g., when the file content is read
from the compilation unit) or else lexing will fail.

salguarnieri accepted this revision at 2017-02-08 00:58:25

zarko wrote at 2017-02-08 00:59:01:
We need better tests in general for non-UTF-8 encoded data. I'll track this in #1706.

zarko closed via commit 5f589e58dc749e1ba58bef89f3437dd92424f168 at 2017-02-08 00:59:30


iOS version crash

When I want to start recognizing, ios version crashed.
the error:
** Terminating app due to uncaught exception 'com.apple.coreaudio.avfaudio', reason: 'required condition is false: IsFormatSampleRateAndChannelCountValid(format)'

@betterpro try with this : https://github.com/ssttonn/flutter_shazam_kit/pull/4


Save / retrieve coordinates

Save / retrieve coordinates from local storage so if you just go to openparkingmap.com it'll remember your last spot

Thanks for the contribution @CurtisGreen. When you're ready for me to review convert it to an active PR.

Thanks for the contribution @CurtisGreen. When you're ready for me to review convert it to an active PR.

@brandonfcohen1 This is ready whenever


ImportError: numpy.core.multiarray failed to import

I am trying to use matplotlibcpp with python 3.6, and after a bit of a battle, I managed to get the program to compile. The problem is that now when I run it it, the file starts to run and then it terminates and I get ImportError: numpy.core.multiarray failed to import. I am using numpy 1.15.2. Any suggestions?

I am also getting this error, any updates?


az extension add has an Unicode display issue

Describe the bug
A clear and concise description of what the bug is.
az extension add has an Unicode display issue
To Reproduce
Steps to reproduce the behavior.
az extension add --name azure-devops
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
has an Unicode display issue

I will add this command was an issue on the command prompt

What is the python version?

This is duplicate of #9140
I haven't been able to get to it. I will try to debug and raise a fix soon.
FYI.. The issue is on Windows only.

add to S164.

Fixed by #9660


Inform about the known issue with Firefox, recommend Chrome

closes #40

I'm not sure about this one. The mentioned error should be related to the GPT-4 usage limit (25 per 4 hrs), not the Firefox cookie. Will try to debug in the next few days.

Let's bench this for now then. Thanks for the review.


Reformat to package

Reformatting code to

[x]  run as package
[ ] dataset reformat to store standardisation with model
[ ] add validation step

Closing as stale branch.


Updated to work with Electra Release 1

Electra requires entitlements to be added. I've added the required entitlements as entitlements.xml and modified the Makefile to run ldid against these specified entitlements. The current version is hosted on my repo for testing purposes and works for me on iOS 11.0.3, Electra Release 1.0.1.
I don't have a 32-bit device with a compatible jailbreak to test, but theoretically, the app should be compiled correctly and run on 32-bit platforms.
This update should be ready to push to BigBoss.

Wonderful job ! Just noticed, the .deb is missing, could you check ? Thanks !

It's located in packages. Sorry, I forgot to move it.

Oh okay ! The update has been pushed to BigBoss, should be live in 48 hours max !

Thanks!


Led start

sample code to get up and running using PI4J and led strip, just have to get the pi4j api included into project

I'll merge this since we currently have nothing in the dev branch but future pull requests please create a seperate feature branch.

Roger that, and then I pull request the dev branch (with the feature branch)?

correct
On Wed, Sep 13, 2023 at 10:52 PM MichaelAndrew22 @.***>
wrote:

Roger that, and then I pull request the dev branch (with the feature
branch)?
—
Reply to this email directly, view it on GitHub
https://github.com/Cxrdary/RGBLightController/pull/21#issuecomment-1718803579,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5JFKNZQP7NYWVRCH4ZFX23X2KLQHANCNFSM6AAAAAA4T4BCSE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


keyserver

The keyserver in install_prerequisites.py does not seem to work. I replaced it with hkp://keyserver.ubuntu.com which does not result in that error.

I'm guessing you're trying to build externals using the irods/externals repo.
If so, use the changes from the following PR: https://github.com/irods/externals/pull/122
These changes will most likely be merged within a few weeks.

closing


support excluding directories

I'd like to make a PR to exclude certain directories when archiving.
So we just need to pass down a slice of excluded paths to filepath.Walk, then return filepath.SkipDir if the path matches any of the excluded path?
What do you think?

Sure this is easy, but the purpose of archiver is to mimic your OS's file explorer's "right-click and click Compress" functionality, and I really like the simplicity of its API as-is. Can this be done without changing the function signatures or simple usage?

I also like the simplicity. And I don't want to pollute that. Seems that there's no way of passing additional options without changing Make(destination string, sources []string) error. Making a new function e.g. sth like MakeAdvance(), is not very elegant to me. So I just fallback to use tar, anyway. Thanks.

Okay. Sorry about that. I'd rather keep the scope of this project narrow. I invite others to create other applications that build on it if they wish!

Should be possible now after #99 is in. Each archiver will have a configuration struct that could potentially be used to exclude files.


Uncaught ReferenceError: global is not defined

I can't seem to actually import this into a worker. Here's the error I see:
✘ [ERROR] Error on remote worker: ParseError: A request to the Cloudflare API (/accounts/fb15ed8606dd6b410e7876fbcfd3b4b7/workers/scripts/worker-typescript-template/edge-preview) failed.

      at throwFetchError
  (/Users/max/Projects/costbeacon/node_modules/wrangler/wrangler-dist/cli.js:141293:17)
      at fetchResult
  (/Users/max/Projects/costbeacon/node_modules/wrangler/wrangler-dist/cli.js:141262:5)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async createPreviewToken
  (/Users/max/Projects/costbeacon/node_modules/wrangler/wrangler-dist/cli.js:141555:29)
      at async createWorkerPreview
  (/Users/max/Projects/costbeacon/node_modules/wrangler/wrangler-dist/cli.js:141575:17)
      at async start
  (/Users/max/Projects/costbeacon/node_modules/wrangler/wrangler-dist/cli.js:142271:34) {
    text: 'A request to the Cloudflare API
  (/accounts/fb15ed8606dd6b410e7876fbcfd3b4b7/workers/scripts/worker-typescript-template/edge-preview)
  failed.',
    notes: [
      {
        text: 'Uncaught ReferenceError: global is not defined\n' +
          '  at index.js:336:7 in<EMAIL_ADDRESS>+
          '  at index.js:11:50 in __require\n' +
          '  at index.js:781:36\n' +
          ' [code: 10021]'
      }
    ],
    location: undefined,
    kind: 'error',
    code: 10021
  }

Apologies, this library is built to be used both for Cloudflare Workers and Node.js (for which we need globals). I added a note about the node_compat flag in README.md and published v0.0.55.
If you have any thoughts on how to fix this issue (and still make it work for both envs) please let me know.


Transfer className alias patch to Object class, update db

Today, Roblox changed the base class of Instance to a new abstract base class called Object. As part of this change, the ClassName and className properties now belong to Object, which currently causes rbx_reflector generate to exit with an error due to an alias patch for className:
     Running `target/debug/rbx_reflector generate rbx_reflection_database/database.msgpack rbx_dom_lua/src/database.json --patches patches`
[INFO  rbx_reflector::cli::defaults_place] Installing Studio plugin
[INFO  rbx_reflector::cli::defaults_place] Starting Roblox Studio...
[INFO  rbx_reflector::cli::defaults_place] Waiting for Roblox Studio to re-save place...
[INFO  rbx_reflector::cli::defaults_place] Uninstalling Studio plugin
[INFO  rbx_reflector::cli::defaults_place] Place saved, killing Studio...
Error: Property Instance.className modified in patch file does not exist in database

This PR changes the className alias patch so it's appropriately on the Object class, and updates the reflection database.
(does this change need a more specific changelog entry beyond "updated to Roblox 647")?

Brittle test :(
hold on....


cargo-insta: 1.15.0 -> 1.18.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cargo-insta/versions.
meta.description for cargo-insta is: "A Cargo subcommand for snapshot testing"
meta.homepage for cargo-insta is: "https://github.com/mitsuhiko/insta"
meta.changelog for cargo-insta is: ""
Updates performed

Rust version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.16.0 with grep in /nix/store/szwibasislfdd1k5cp743mggbz4qzwa7-cargo-insta-1.16.0
found 1.16.0 in filename of file in /nix/store/szwibasislfdd1k5cp743mggbz4qzwa7-cargo-insta-1.16.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cargo-insta

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/szwibasislfdd1k5cp743mggbz4qzwa7-cargo-insta-1.16.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/szwibasislfdd1k5cp743mggbz4qzwa7-cargo-insta-1.16.0
ls -la /nix/store/szwibasislfdd1k5cp743mggbz4qzwa7-cargo-insta-1.16.0/bin

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

1 package built:

cargo-insta

Maintainer pings
cc @oxalica for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cargo-insta/versions.
meta.description for cargo-insta is: "A Cargo subcommand for snapshot testing"
meta.homepage for cargo-insta is: "https://github.com/mitsuhiko/insta"
meta.changelog for cargo-insta is: ""
Updates performed

Rust version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.18.1 with grep in /nix/store/b4bcn8544z51vyjkcvlc2xc3lgsri5b6-cargo-insta-1.18.1
found 1.18.1 in filename of file in /nix/store/b4bcn8544z51vyjkcvlc2xc3lgsri5b6-cargo-insta-1.18.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cargo-insta

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b4bcn8544z51vyjkcvlc2xc3lgsri5b6-cargo-insta-1.18.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b4bcn8544z51vyjkcvlc2xc3lgsri5b6-cargo-insta-1.18.1
ls -la /nix/store/b4bcn8544z51vyjkcvlc2xc3lgsri5b6-cargo-insta-1.18.1/bin

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

1 package built:

cargo-insta

Maintainer pings
cc @oxalica for testing.

cargo insta review works properly.

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

1 package built:

cargo-insta


Adding additional reporting and refactoring existing setup.

Coverage decreased (-0.08%) to 68.127% when pulling 79dcf430879c24b036b22c7c66bc42b6dbc3b78e on kevgliss:reporting into 9ac10a97ce592cf8edff67725cc201380da605c1 on Netflix:master.


KeyboardOverlap TabbedPage bug

TabbedPage:

white space (it seems tab height) appears:

I have the same problem. No one found a solution?


Socialite Twitter

I have search the web. followed all the "step guides" and posted to all the forums (Laracasts, StackOverflow, Google, etc.) out there with no luck. It seems like many people are struggling with setting up twitter.
It would be great if someone can post working twitter code.
I have google, FB, Github, LinekdIn and others working. The oauth 2 works drivers work great, but twitter is oauth 1 and does some weird redirecting. Seems like many are struggling with the same issue. I've tried all the online guides but seems like most struggle with the same issues:
The issue with twitter is as follows:

you make the initial call $this->socialite->driver('twitter')->redirect();  // I've also tried ->with
this then sets temp 'oauth.temp' value with temp credentials. You then redirected to the twitter app authorize page. If you, as the user, authorize it will return a 'oauth_token' && 'oauth_verifier'
however, it seems that when it returns the auth tokens and it does another request and rewrites the temp values in session memory.
so when you execute an auth user() call $this->socialite->driver('twitter')->user();  and it calls the getTokenCredentials method the temp values no longer match and you end up with a mismatch error or I get a null passed through to temp i.e. it clears out Session:

so you end up with one of the two exceptions:
a. the temp and return dont match exception
"Temporary identifier passed back by server does not match that of stored temporary credentials. Potential man-in-the-middle."
b. it clears session and you end up with an invalidargument exception with null passed
Example of code:
Auth Controller
    public function social(SocialAuthManager $socialAuthManager, Request $request, $provider = null)
    {
        return $socialAuthManager->execute($request->all(), $this, $provider);
    }

Route
Route::get('social/{provider?}', 'Auth\AuthController@social');

Basic service class
use Laravel\Socialite\Contracts\Factory as Socialite;

class SocialAuthManager {

    /**
     * @var Socialite
     */
    private $socialite;
    /**
     * @var SocialUserEloquent
     */
    private $socialUserEloquent;

    /**
     * @param Socialite $socialite
     */
    public function __construct(Socialite $socialite)
    {
        $this->socialite = $socialite;
    }

    /**
     * @param $request
     * @param $listener
     * @param $provider
     * @return \Laravel\Socialite\Contracts\User|\Symfony\Component\HttpFoundation\RedirectResponse
     */
    public function execute($request, $listener, $provider)
    {
        if (!$request)
        {
            return $this->getAuthorizationFirst($provider);
        }

        $user = $this->getSocialUser($provider);

        return $user;
    }

    /**
     * @param $provider
     * @return \Symfony\Component\HttpFoundation\RedirectResponse
     */
    private function getAuthorizationFirst($provider)
    {
        return $this->socialite->driver($provider)->redirect();
    }

    /**
     * @param $provider
     * @return \Laravel\Socialite\Contracts\User
     */
    private function getSocialUser($provider)
    {
        return $this->socialite->driver($provider)->user();
    }

}

Please ask on the forums.

@GrahamCampbell very helpful. I suppose the "I have searched the web. followed all the "step guides" and posted to all the forums (Laracasts, StackOverflow, Google, etc.) out there with no luck." was a little cryptic. Maybe I should have added "and other forums".  What a joke

Searched is not the same thing as having asked.

@onbjerg I've asked so many times. I've posted to numerous forums. I have yet to find someone who actually has twitter working. On laracasts, disqu, reddiit and google forums the standard response has been "I've given up on twitter". In fact I don't know of one person that has it up and running.
Like Is said, I have the rest  of the social integrations working. Socialite is a great, just twitter  or maybe it is oauth 1.0 that just keeps failing.  Just looking for one, "here its working example".
I posted this to Taylor and Jeffery around the time of the launch - crickets:
https://laracasts.com/discuss/channels/requests/anyone-have-socialite-working-with-linkedin-twitter

@nolros Have you found any solution to this? I am having the same problem as well.

@GrahamCampbell : I strongly believe this issue needs re-opening. I extensively debugged the Twitter Socialite provider class and there is a bug in there:
oauth.temp session variable set at:
https://github.com/laravel/socialite/blob/2.0/src/One/AbstractProvider.php#L45
is not available once Twitter redirects you back to the app. The line at:
https://github.com/laravel/socialite/blob/2.0/src/One/AbstractProvider.php#L81
can't find oauth.temp session variable. I dumped whole session at that point: it's just not there. Its clearly a bug! Could you guys please look into this?
CC: @taylorotwell

P.P.S.: I switched my session location to file. Everytime I renew a page, new session file is being created. Shouldn't framework use working session file instead of creating new session every time? What am I missing here?

@shehi no, never got it work. ll the others work fine, but twitter not. Every person on laracasts and other forums that have posted the same issue gave up in the end. As I said as the temp session credentials don't match the returning credentials that it doing a 2nd redirect, but none of my traces indicate that is the case, but you get a
Temporary identifier passed back by server does not match that of stored temporary credentials.
Potential man-in-the-middle." error

OR as you said there are cases where it does flush the session, again cannot trace why, but then you get a
Argument 1 passed to League\OAuth1\Client\Server\Server::getTokenCredentials() must be an instance of League\OAuth1\Client\Credentials\TemporaryCredentials, null given

yet another example or people struggling ... another perspective is that the url in the twitter provider is wrong https://laracasts.com/discuss/channels/general-discussion/laravel-boilerplate-20/?page=2

I believe my problem was related to #8172. That being fixed, Twitter OAuth via Socialite is working just fine.

I had the same issues. I came up with this solution: https://www.victorangelier.com/laravel51-laravel-5-1-socialite-twitter/ It's very dirty but it works so.

@digitalhuman : You sure you weren't losing Session there?

I am sure it is Session but I can't seem to get Session to work.
I can change .env or /config/session.php to whatever I want. It doesn't matter. Laravel keeps using files and keep regenerating session at every refresh or redirect.

Do you have domain for Session set in config/session.php?

yes

 "database",

    /*
    |--------------------------------------------------------------------------
    | Session Lifetime
    |--------------------------------------------------------------------------
    |
    | Here you may specify the number of minutes that you wish the session
    | to be allowed to remain idle before it expires. If you want them
    | to immediately expire on the browser closing, set that option.
    |
    */

    'lifetime' => 1200,

    'expire_on_close' => false,

    /*
    |--------------------------------------------------------------------------
    | Session Encryption
    |--------------------------------------------------------------------------
    |
    | This option allows you to easily specify that all of your session data
    | should be encrypted before it is stored. All encryption will be run
    | automatically by Laravel and you can use the Session like normal.
    |
    */

    'encrypt' => true,

    /*
    |--------------------------------------------------------------------------
    | Session File Location
    |--------------------------------------------------------------------------
    |
    | When using the native session driver, we need a location where session
    | files may be stored. A default has been set for you but a different
    | location may be specified. This is only needed for file sessions.
    |
    */

    'files' => storage_path('framework/sessions'),

    /*
    |--------------------------------------------------------------------------
    | Session Database Connection
    |--------------------------------------------------------------------------
    |
    | When using the "database" or "redis" session drivers, you may specify a
    | connection that should be used to manage these sessions. This should
    | correspond to a connection in your database configuration options.
    |
    */

    'connection' => "mysql",

    /*
    |--------------------------------------------------------------------------
    | Session Database Table
    |--------------------------------------------------------------------------
    |
    | When using the "database" session driver, you may specify the table we
    | should use to manage the sessions. Of course, a sensible default is
    | provided for you; however, you are free to change this as needed.
    |
    */

    'table' => 'sessions',

    /*
    |--------------------------------------------------------------------------
    | Session Sweeping Lottery
    |--------------------------------------------------------------------------
    |
    | Some session drivers must manually sweep their storage location to get
    | rid of old sessions from storage. Here are the chances that it will
    | happen on a given request. By default, the odds are 2 out of 100.
    |
    */

    'lottery' => [2, 100],

    /*
    |--------------------------------------------------------------------------
    | Session Cookie Name
    |--------------------------------------------------------------------------
    |
    | Here you may change the name of the cookie used to identify a session
    | instance by ID. The name specified here will get used every time a
    | new session cookie is created by the framework for every driver.
    |
    */

    'cookie' => 'euroid_session',

    /*
    |--------------------------------------------------------------------------
    | Session Cookie Path
    |--------------------------------------------------------------------------
    |
    | The session cookie path determines the path for which the cookie will
    | be regarded as available. Typically, this will be the root path of
    | your application but you are free to change this when necessary.
    |
    */

    'path' => '/',

    /*
    |--------------------------------------------------------------------------
    | Session Cookie Domain
    |--------------------------------------------------------------------------
    |
    | Here you may change the domain of the cookie used to identify a session
    | in your application. This will determine which domains the cookie is
    | available to in your application. A sensible default has been set.
    |
    */

    'domain' => "localhost",

    /*
    |--------------------------------------------------------------------------
    | HTTPS Only Cookies
    |--------------------------------------------------------------------------
    |
    | By setting this option to true, session cookies will only be sent back
    | to the server if the browser has a HTTPS connection. This will keep
    | the cookie from being sent to you if it can not be done securely.
    |
    */

    'secure' => false,

];

Noooo... That won't work :) Browsers are inconsistent when you set bogus domain there. Let me get you the link...

Read this: https://github.com/laravel/framework/issues/8172#issuecomment-103019015

I can change session.php to whatever i wan't Laravel doesn't do anything with these settings.

If file doesn't exist, it might be loading its own defaults. Don't rely on that. Set correct values.

Please continue this on the forums.

https://laracasts.com/discuss/channels/laravel/sessions-in-51-regenerates-on-every-refreshredirect

Please join me cuz this is so annoying. I read more people have issues with this and the documentation fails at this point.

@nolros
I got the same error here, and it was fixed..
the error is because on the callback url setting.
example :
if first auth request is on : http://domain.com/auth/twitter
and callback to : http://domain.com/auth/twitter/callback
it will not return an error
but if your callback is http://www.domain.com/auth/twitter/callback
that will return error.
hope it's help

I've added some info about this in the forms (user @ mmz)https://laracasts.com/discuss/channels/requests/temporary-token-issues-with-socialitetwitter

Received HTTP status code [401] with message "{"errors":[{"code":32,"message":"Could not authenticate you."}]}" when getting temporary credentials.

I worked for me, following this tut:
https://medium.com/@krunallathiya/laravel-5-twitter-login-tutorial-6e0f99213787

@chintanvadi you might be reloading. If it fails, you have to start again the login process.

To fix the error
throw new CredentialsException(
"Received HTTP status code [$statusCode] with message "$body" when getting temporary credentials."
);
in TWITTER_ID, put API key)
in TWITTER_SECRET Put API secret key
this will solve the problem.

One note to be aware of, if you set your 'same_site' => 'strict', in config/session.php, it'll cause twitter to fail.
It took me days to narrow it down to this setting. I currently have it set to 'same_site' => null, and it works. Sorry to bump this issue, but I've seen similar issues posted, but nothing about the same_site variable in sessions.
I hope this helps.

 Thanks man

Solved by regenerating Twitter API keys & tokens, updating .env & config/services.php

'same_site' => null needs to be added to the socialite docs. That was quite a wild goose chase for me until I found this. Thanks @LorenzoSapora

This was changed to default to lax with new L7 installations.
Do you might be able to quickly test if lax also works or breaks? thanks!

2015 and now in 2020 people are still having the same issues with this horrific "product". Stop adding Laravel products if you cannot support the existing products.  Sanctum, Socialite, etc. all should be alpha products ... NOT FOR PRODUCTION USE.


ESM example

Adds fileImport util method for importing files outside blob context
Adds Rotator script

Cool. I assume this Rotator script when dropped to the Editor will work without any changes needed?

Yes it should do.

the fileImport feels a little awkward. Is this just to resolve relative to the utils.mjs?

the fileImport feels a little awkward. Is this just to resolve relative to the utils.mjs?

Yea its to do with the path resolution for import inside blobs being different


EM-3512--Check-&-Update-PACT/Jupiter-Unit-tests-related-Dependencies

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Not required


db2dita plugin doesn't support segmentedlist

docbook2dita/dbdita/ditaWriter/topicOutput.xsl have no writer code for topic.segmentedlist.out
A simple hack is below but it only dumps out the content (incl. child nodes) as a lump of text.
Any fix/upgrade should also iterate through all child nodes and process accordingly.
  <xsl:template match="*" mode="topic.segmentedlist.in">
    <!-- <p> -->
      <!-- drive the list by outputting each segtitle in turn -->
      <xsl:for-each select="segtitle">
        <p>
        <b>
          <xsl:value-of select="."/>
        </b>
        <xsl:text>: </xsl:text>
        <!-- record the current position in the list (1,2,3...) -->
        <xsl:variable name="thispos" select="position()"/>
        <!-- output the relevant item from the seglistitem child
             of the parent element (segmentedlist) -->
        <xsl:value-of select="../seglistitem/seg
                              [position()=$thispos]"/>
        <!-- add a linebreak to all except the last -->
	<!-- <xsl:if test="position()!=last()">-->
	  </p>
	<!--   <lines/> -->
       <!--  </xsl:if>-->
      </xsl:for-each>
   <!--  </p> -->
  </xsl:template>

I don't think this issue is related to any code maintained by DITA-OT. It appears this is related to the following file in another github project that is not maintained by this team:
https://github.com/jmourelos/doconv/blob/master/doconv/plugin/docbooktodita/ditaWriter/topicOutput.xsl
If so, then the issue should be opened against that project: https://github.com/jmourelos/doconv/issues


Attempted import error: 'LexicalErrorBoundary' is not exported from<EMAIL_ADDRESS>(imported as 'It').

Link to reproduction
No response
Payload Version
3.0.0-beta.91
Node Version
v20.11.0
Next.js Version
15.0.0-canary.104
Describe the Bug
I get the following error after migration
Reproduction Steps

Adapters and Plugins
richtext-lexical

Hey, I will need a reproduction in order to look into this. E.g. a repository I can clone down and run a command on, which will give me this error

@AlessioGr Hi! I have just created a new project using your template for beta and copied all project files into this new project and everything works as expected) sorry for interruption


separate_compiler: Write errors to stderr

Signed-off-by: Jean-Christophe Beaupré<EMAIL_ADDRESS>

These are internal errors closer to debug prints than anything else. Updating them to use a rather new service is not worth a PR, and much less two.
Considering the three PR you published today, I would advise you to only submit PRs that either: (a) fix a software bug or (b) add a feature.


misc xslt fixes

Here are five tiny commits. I hope that combining them into a single PR is not a burden. If so, just let me know and I can split them apart.
a58291a simply makes clear which template should apply to paragraphs within header footnotes (suppressing an "ambiguous rule match" warning)
a58291a calls the "inline" template from the link template, in order to capture inline formatting within links
2b4ac1a adds some ad hoc spacing around certain numbers that don't currently have an appropriate CSS class
3d28938 triggers the judgment header and judgment body templates for the preface and body of press summaries
696fe9c allows for text alignment within the preface of a press summary, in the same way that it can occur within a judgment header

 a few small XSLT fixes


Fix Bulk Insert: Single Column and MySQL earlier upsert syntax

This change handle the case of using single column in "VALUES(...)".
And allow using VALUES in "INSERT ... ON DUPLICATE KEY UPDATE ..." kind of queries,  e.g issue https://github.com/jmoiron/sqlx/issues/722
Possible fixes for https://github.com/jmoiron/sqlx/issues/701 https://github.com/jmoiron/sqlx/issues/695 https://github.com/jmoiron/sqlx/issues/694

Pull Request Test Coverage Report for Build 237

25 of 25 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 74.166%

Totals

Change from base Build 224:
0.3%

Covered Lines:
1223

Relevant Lines:
1649

💛  - Coveralls

This solves issues I was having with the new batch insert feature, which was generating statements with unbalanced parentheses, eg INSERT (id) VALUES (coalesce(:a,:b)) compiled to INSERT (id) VALUES (coalesce(1,2)
Many thanks @QuangTung97

Thanks @QuangTung97!
Was about to create similar PR that does away with this brittle regex)
By the way, this should also fix some additional cases:

Functions inside values: INSERT INTO foo (a,b,c,d) VALUES (:name, cast(:age as int), :first, :last)
Some strange regex indentation failure I was having on multi-line queries (regex failed on some levels of indentation and not the others, go figure).

Could you add those test cases as well, please? Here's the gist of the ones I added: https://gist.github.com/w1ck3dg0ph3r/cfbce1590fdce1ce54a179b6cb74f6a4.

Thanks @QuangTung97!
Was about to create similar PR that does away with this brittle regex)
By the way, this should also fix some additional cases:

Functions inside values: INSERT INTO foo (a,b,c,d) VALUES (:name, cast(:age as int), :first, :last)
Some strange regex indentation failure I was having on multi-line queries (regex failed on some levels of indentation and not the others, go figure).

Could you add those test cases as well, please? Here's the gist of the ones I added: https://gist.github.com/w1ck3dg0ph3r/cfbce1590fdce1ce54a179b6cb74f6a4.

Thanks. I added test for the multiple lines query case. But the case of function calls might be redundant with the test case two level depth function call I already added.

This looks great;  this regex has seen a lot of authors and is difficult to get right, but this looks great and more tests are also welcome.  Going to cut a new dot release w/ this sometime this weekend, triaging more in the backlog.


#5 Error: Cannot find module '../build/default/daemon'

Went a different route here. Fixed in ca738da792a189a62f43da9f281d23ad599070ff and published in<EMAIL_ADDRESS>


upgrade alpine base image to latest version

This pull request upgrades the alpine base image used for drone-server and drone-agent,
since 3.7 is the latest released version with updated ca-certificates.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Markus Schölzel seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


playfair cipher in python

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
I have implemented Playfair cipher in python.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
This PR resolves #2676

@all-contributors bot please add @nandinib1999 for code


[SPIKE] Prepare fallback repository to handle missing packages, files and images

Is your feature request related to a problem? Please describe.
In rare situations when some package version is gone missing from public repositories our customers are blocked because installation process will fail on download requirements step. This also applies to other types of dependencies (archive files and Docker images).
Describe the solution you'd like
Proposed solution would include following elements:

download requirements step should handle error situation that a package/file/image is missing
in such scenario it should try to access our fallback repository machine to obtain this binary and then retry download process
in case of binary missing in our fallback repo we should get alert that some package request got not found response
it means that we need instance in our subscription to host those binary files
address of the fallback repository should be configurable

NOTE: Packages that are downloaded from RHEL repositories cannot be shared publicly.
Describe alternatives you've considered
Current situation when we need to release patch version in described scenario it's very problematic.
Additional context
n/a

DoD checklist

[ ] Changelog updated
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Idempotency tested
[ ] Documentation added / updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license
[ ] Backport tasks created / doesn't need to be backported

@to-bar please add comment about possibility to support multiple repositories.

We need to decide:

Whether the fallback repository should be public - if yes how to secure it properly
Which files we cannot share because of license limitations (such as packages from RHEL repos)
How we want to refresh (update) the fallback repo

We have two main parts todo in case of this issue:

Preparing environment as a fallback repository
Adjust Ansible role (repository) to handle fallback repository

The first part:
I was taking the following software under consideration:  ProGet from Inedo, Nexus Repository OSS from Sonartype and Pulp from Redhat.
The Nexus free version is under GPL v3. The ProGet has its own license agreement.
However, both free versions are really limited (ProGet Free, Nexus free) in comparison to Pulp.
The Pulp project is open source (GPLv2) and it has the following features:

Fetch, upload, distribute content and secure via Conent Plugins (available by default):

Certguard
RPM
File
Container
Ansible
Debian
Python
Ruby Gem
Chef Cookbook
Maven
Important: We can write our own plugin for the content type we want to manage. Example for Helm Charts  written in Python

Every plugin has its own extra options eg. container has token authentication
Scalable architecture
Available as Docker image
Has CLI
Manage Pulp via Ansible ( Ready-to-go Ansible role for installation and plugins installation)
Repository versioning (Pulp creates an immutable repository version)
Support for cloud storage (S3, Azure)
Optimizing disk storage and speed during remote synchronization (see here)
Authentication:

Basic: user/pass
via Keycloak
via Webserver

Kubernetes operator for Pulp (not yet production ready, see here)

The second part - Ansible role:
As discussed with @to-bar the repository role is going to be refactored entirely, so during task #805 we should keep in mind that we have to support at least user/pass authentication for the extra repository ( additional entries in configuration manifest?)
But I believe it will be a different task to implement such feature.

Nice, I think that we should try design some simple PoC version with Pulp.

Reviewed thoughts that @rafzei found and seems that Pulp has more features for free than any other tools.
In Nexus there is a "proxy" repo that can be used as an entry point for multiple private hosted or public repositories. So If one of them fails, package will be searched in all other ones. Is there something similar in Pulp?

As far as I saw, we are able to use the proxy approach in Pulp via creating and synchronize the remote repository and it's also possible to specify synchronization time.

LGTM. I believe Pulp PoC should be created in separate task.


Fix some maven issues

Warning : with the latest maven assembly plugin (2.2.1), setting an empty <id></id> will not work anymore (I will submit a pull request later for that). So we have to set to the default maven assembly plugin (2.2-beta5).
Update also to ES 0.19.0.RC3 to fix maven dependencies issues (see https://github.com/elasticsearch/elasticsearch/issues/1691)

I fixed the assembly problem differently and pushed, thanks for bringing it up.


Rename Tachyon project with Alluxio.

Since the project is renamed, we need to update it.
When visiting http://tachyon-project.org/, you will visit http://www.alluxio.org/ now.

Thank you for merging, @onurakpolat .


exception=ManagerNotFound('Manager messages not found'

Now we this issue when application load; none new message can be sent, please your kindly help i am in a urgency: thanks in advanced
2019-09-30 17:19:53,236 ERROR    Task exception was never retrieved
future: <Task finished coro=<Minibot.monitor_new_messages() done, defined at /root/webwhatsappinterface/worker/webWhatsappinterface_python3.py:270> exception=ManagerNotFound('Manager messages not found',)>
Traceback (most recent call last):
File "/root/webwhatsappinterface/worker/webWhatsappinterface_python3.py", line 276, in monitor_new_messages
async for message in it:
File "/usr/local/lib/python3.6/dist-packages/whalesong/results.py", line 195, in anext
evt: T = await super(MonitorResult, self).anext()
File "/usr/local/lib/python3.6/dist-packages/whalesong/results.py", line 137, in anext
raise item
whalesong.errors.ManagerNotFound: Manager messages not found
2019-09-30 17:19:53,237 ERROR    Task exception was never retrieved
future: <Task finished coro=<Minibot.monitor_message_acks() done, defined at /root/webwhatsappinterface/worker/webWhatsappinterface_python3.py:103> exception=ManagerNotFound('Manager messages not found',)>
Traceback (most recent call last):
File "/root/webwhatsappinterface/worker/webWhatsappinterface_python3.py", line 105, in monitor_message_acks
async for ack in it:
File "/usr/local/lib/python3.6/dist-packages/whalesong/results.py", line 195, in anext
evt: T = await super(MonitorResult, self).anext()
File "/usr/local/lib/python3.6/dist-packages/whalesong/results.py", line 137, in anext
raise item
whalesong.errors.ManagerNotFound: Manager messages not found

Please have a look at https://github.com/alfred82santa/whalesong/issues/121#issuecomment-536587381

Thanks @vasani-arpit

@alfred82santa, You may close this one.


HOTFIX: disable flaky system tests

\cc @enothereska @ijuma @guozhangwang @dguy @bbejeck

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5933/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5918/
Test FAILed (JDK 8 and Scala 2.12).

Is the jenkins failure related?
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5918/testReport/junit/org.apache.kafka.streams.integration/QueryableStateIntegrationTest/shouldAllowToQueryAfterThreadDied/

Also could you point me to the JIRA ticket tracking this flaky test? Do we know / have any theory about its flakiness?

And also is it related to this commit? https://github.com/apache/kafka/commit/0046a881d389878bbb673c2591c06fd667923964, if yes do we still need this?

Test failure is not related (I created a new JIRA for the failing test -- happened on many build already: https://issues.apache.org/jira/browse/KAFKA-5566
We don't have a JIRA for the flaky system tests.
It's not related to https://github.com/apache/kafka/commit/0046a881d389878bbb673c2591c06fd667923964 that is about unit tests (not system tests)

Btw: this should also go into 0.11.0 -- it's also flaky there.

Retest this please.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5942/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5927/
Test FAILed (JDK 8 and Scala 2.12).

@dguy @guozhangwang we need to disable and check. It's failing pretty much every night for a week now.

Merged to trunk & cherry-picked to 0.11.0


Correct description in Sum All Primes challenge

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #8938

Description

Changed the description of the Sum All Primes challenge from:
"A prime number is defined as having only two divisors, 1 and itself. For example, 2 is a prime number because it's only divisible by 1 and 2. 1 isn't a prime number, because it's only divisible by itself."
to:
"A prime number is defined as a number greater than one and having only two divisors, one and itself. For example, 2 is a prime number because it's only divisible by one and two."

@agparadiso LGTM! 👍  Thanks for your contribution to FreeCodeCamp! ✨ 🎉 ✨


Offhand item usage feels clunky

Heya! First of all, thank you for your hard work!
Now to my question/problem:
I cannot for the life of me figure out how to hold a majority of items in the left hand/offhand.
I like using torches/Lanterns in my offhand to light up the area around me (using another mod for lighting) and quick-place torches when mining/exploring caves, dungeons, and the like.
Maybe I'm missing something but no matter what I do, the player model is not holding anything in the left hand outside of vanilla weapons and shields, which feels really unnatural and causes issues with combat involving dual-wielding non-vanilla weapons.
I already tried editing the config ["are_hand_items_restricted_to_item_tags": false,], but it doesn't seem to do anything, but maybe I did it wrong.
Alternatively, is there a way to simply disable the Main Hand/Off-Hand stuff and use Vanilla Off-Hand, but retain the Inventory+Spell Slots?
Any assistance on this would be much appreciated!
Loving the rest of the Mod though and I'm excited for more updates!
(Using 1.21.1 + Fabric + Better Combat)

Hi!
Adding items to the "rpginventors:offhand_items" item tag via a data pack should allow those items to be put into the offhand slot.
Setting the config option "are_hand_items_restricted_to_item_tags" to false is not recommended.
An option to completely disable the new mechanics around the hand items is a good idea. I'll add it to my todo list.
Thanks for the feedback!


Prepare for Gatsby 5 launch

Gatsby 5 is currently in beta phase and will be released any day. I've done some initial investigation and the website seems to run just fine with the update (albeit with several other dependencies updates and a few warnings).
Once it's launched I will create a PR to migrate.
See https://www.gatsbyjs.com/blog/gatsby-v5-alpha-is-here-and-its-pretty-exciting/ for possible features that we may be interested in.
See migration guide here https://github.com/gatsbyjs/gatsby/blob/v5-docs/docs/docs/reference/release-notes/migrating-from-v4-to-v5.md

Current package.json diff:
diff --git a/package.json b/package.json
index 728c909..e95e581 100644
--- a/package.json
+++ b/package.json
@@ -16,27 +16,27 @@
     "@react-icons/all-files": "^4.1.0",
     "bootstrap": "^5.2.2",
     "flexsearch": "^0.7.31",
-    "gatsby": "^4.24.5",
-    "gatsby-plugin-gatsby-cloud": "^4.24.1",
-    "gatsby-plugin-google-gtag": "^4.24.0",
-    "gatsby-plugin-google-tagmanager": "^4.24.0",
-    "gatsby-plugin-image": "^2.24.0",
+    "gatsby": "^5.0.0-next.10",
+    "gatsby-plugin-gatsby-cloud": "^5.0.0-next.2",
+    "gatsby-plugin-google-gtag": "^5.0.0-next.1",
+    "gatsby-plugin-google-tagmanager": "^5.0.0-next.3",
+    "gatsby-plugin-image": "^3.0.0-next.4",
     "gatsby-plugin-local-search": "^2.0.1",
-    "gatsby-plugin-manifest": "^4.24.0",
-    "gatsby-plugin-netlify": "^5.0.1",
+    "gatsby-plugin-manifest": "^5.0.0-next.3",
+    "gatsby-plugin-netlify": "^4.0.0-next.0",
     "gatsby-plugin-offline": "^5.24.0",
     "gatsby-plugin-react-i18next": "^2.0.4",
-    "gatsby-plugin-react-svg": "^3.1.0",
-    "gatsby-plugin-sass": "^5.24.0",
-    "gatsby-plugin-sharp": "^4.24.0",
-    "gatsby-plugin-sitemap": "^5.24.0",
+    "gatsby-plugin-react-svg": "^2.0.0-beta1",
+    "gatsby-plugin-sass": "^6.0.0-next.3",
+    "gatsby-plugin-sharp": "^5.0.0-next.4",
+    "gatsby-plugin-sitemap": "^6.0.0-next.4",
     "gatsby-plugin-use-query-params": "^1.0.1",
-    "gatsby-remark-autolink-headers": "^5.24.0",
+    "gatsby-remark-autolink-headers": "^6.0.0-next.3",
     "gatsby-remark-code-titles": "^1.1.0",
-    "gatsby-source-filesystem": "^4.24.0",
-    "gatsby-transformer-asciidoc": "^3.24.0",
-    "gatsby-transformer-remark": "^5.24.0",
-    "gatsby-transformer-sharp": "^4.24.0",
+    "gatsby-source-filesystem": "^5.0.0-next.2",
+    "gatsby-transformer-asciidoc": "^4.0.0-next.2",
+    "gatsby-transformer-remark": "^6.0.0-next.5",
+    "gatsby-transformer-sharp": "^5.0.0-next.4",
     "highlight.js": "^11.6.0",
     "html-to-text": "^8.2.1",
     "i18next": "^21.10.0",

Gatsby 5 goes GA tomorrow (8th November)


Crash after add Flutter to existing Android app with productFlavors in production build.

Steps to Reproduce

Add flutter to existing android app (page revision 38517ba). The existing android app contains two productFlavors inside its app/build.gradle.
Run in debug mode on actual device (hit run button in Android Studio), app is be able to run and show Flutter view as expected.
Build signed apk in release mode using Android studio.
Run the output apk on actual device, navigate to page contains flutter view then the app crash.

Logs

F/flutter (24195): [FATAL:flutter/runtime/dart_vm.cc(416)] Error while initializing the Dart VM: Snapshot not compatible with the current VM configuration: the snapshot requires 'product use_bare_instructions no-"asserts" causal_async_stacks arm64-sysv' but the VM has 'product use_bare_instructions no-"asserts" causal_async_stacks arm-eabi softfp'

Flutter Doctor result
[✓] Flutter (Channel master, v1.3.10-pre.29, on Mac OS X 10.14.3 18D109, locale en-TH)
    • Flutter version 1.3.10-pre.29 at /Users/dewparins/Developer/libs/flutter
    • Framework revision 89a51272d5 (8 hours ago), 2019-03-12 18:32:42 -0700
    • Engine revision 5ccee95373
    • Dart version 2.2.1 (build 2.2.1-dev.1.0 674fd0e060)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/dewparins/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 33.3.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] IntelliJ IDEA Ultimate Edition (version 2018.2.4)
    • IntelliJ at /Users/dewparins/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 31.3.3
    • Dart plugin version 182.5215

[!] VS Code (version 1.31.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

Additional Information
I found a workaround for this issue. By copying the same name of flavorDimensions and productFlavors specified in existing app app/build.gradle to some/path/my_flutter/.android/Flutter/build.gradle.
For example.
// inside some/path/my_flutter/.android/Flutter/build.gradle
...
flavorDimensions "version"
productFlavors {
        demo {
        }
        full {
        }
    }
...

Then the result apk is working fine with no crash.
The problem with this solution is .android/ is added to .gitignore file by flutter create -t module command. It seems that this .android/Flutter/build.gradle file is not intended to be modified; therefore, this solution might not be the right way to fix this problem.

Described workaround works perfectly, thanks!

Flutter v1.12.13 add-to-app supports flavors, so this shouldn't be an issue anymore.


Fix checkpoint compatibility for remove fields

Description
NOTE: This PR targets the writer-map-support branch. The affecting fields of the remove action are map types, so they are not present or testable on main.
We discovered a production bug in which delta-rs checkpoints that include remove actions added by DBR 7.x (OPTIMIZE), are not readable by DBR cluster versions >= 8.x. The log corruption is due to null extended file metadata fields in the checkpoint schema for remove actions. DBR 7.x does not write extended file metadata for removes. Since they are always included in the checkpoint schema written by delta-rs, we write them as nulls, and DBR 8.x cannot read them back.
This PR addresses the issue by conditionally selecting the remove schema to use. If all remove actions in the checkpoint include extended file metadata, we include extended file metadata in the remove schema. Otherwise, we do not.
Four fields are related to remove action extended file metadata. extendedFileMetadata specifies whether partitionValues, size and tags are included. Following comments in the reference implementation, new writers should always write this field. The other three fields should be omitted from the schema if extendedFileMetadata is false.
Documentation

Delta PROTOCOL add/remove fields section
Reference implementation comments on remove action

So am I correct that  DBR 8.x is still trying to read these extension fields even though extendedFileMetadata is set to false for a particular remove action? This seems to contradict with the comment in the reference code base.

@houqp So from the testing, it seems like at some of DBR 8.x, if extendedFileMetadata is false then there's should not be any of size, partitionValues and tags columns. Otherwise, even if they're null, spark fails. Although, I see that BDR 9.0 succeeds with it. But I feel like for the compability purposes we should omit them writing if  extendedFileMetadata is false.

@xianwill btw, wouldn't the easier hotfix will be a just write a extended_file_metadata=false ?

So am I correct that DBR 8.x is still trying to read these extension fields even though extendedFileMetadata is set to false for a particular remove action? This seems to contradict with the comment in the reference code base.

@houqp - here is comment from reference code base with emphasized portion:

Note that for protocol compatibility reasons, the fields partitionValues, size, and tags
are only present when the extendedFileMetadata flag is true. New writers should generally be
setting this flag, but old writers (and FSCK) won't, so readers must check this flag before
attempting to consume those values.

So I am reading this to mean - if extendedFileMetadata is false, you must completely omit the fields. Setting them to null is not good enough. The tests bear that out as well.

@houqp So from the testing, it seems like at some of DBR 8.x, if extendedFileMetadata is false then there's should not be any of size, partitionValues and tags columns. Otherwise, even if they're null, spark fails. Although, I see that BDR 9.0 succeeds with it. But I feel like for the compability purposes we should omit them writing if extendedFileMetadata is false.

@mosyp - i tested w/ 9.0 and that failed as well when fields are present.


getAuthCodeUrl without redirect but instead show loginPopup?

Core Library
MSAL Node (@azure/msal-node)
Core Library Version
^1.14.6
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
^1.4.0
Public or Confidential Client?
Confidential
Description
Hello,
I'm using 4-sign-in-hybrid model, where Im trying to obtain an athCode.
Everything works ok, and I even managed to add this code to my redirect_uri, but I have a question regarding redirection for login.
Can you please show me how to use popup instead of redirection? and is it possible to have non-refreshing actions on successful login? to stay on the same page, but just to obtain authCode?
Thanks
MSAL Configuration
const msalInstance = new msal.ConfidentialClientApplication({
  auth: {
    clientId: process.env.CLIENT_ID,
    authority: `https://login.microsoftonline.com/${process.env.TENANT_ID}`,
    clientSecret: process.env.CLIENT_SECRET,
    navigateToLoginRequestUrl: true,
    postLogoutRedirectUri: "http://localhost:3000"
  },
  system: {
    loggerOptions: {
      loggerCallback: (loglevel, message, containsPii) => {
        console.log(message);
      },
      piiLoggingEnabled: false,
      logLevel: msal.LogLevel.Verbose,
    }
  }
});

Relevant Code Snippets
No response
Identity Provider
Azure AD / MSA
Source
Internal (Microsoft)

getAuthCodeUrl only returns a url, it is up to you to implement how that url is opened, that is not within the scope of msal-node


Commands from works when namespaced

A test for #201 and a more general fix.  Not sure if this is what I want to do

old


:zap: Unify name for Child oriented events

For magical reasons there are four events and two of them has different name for collection.

Continue as #38


Is not possible to create legacy token anymore

Is project abandonware?
If so, unfortunate, looks pretty cool ...

Thanks for reporting the issue! I was a bit busy and had no time to fix it...
If I have a chance in this new year holidays, I'll try fixing them and supporting a new OAuth flow.

Is it already fixed? Can I help somehow?


Update README.md for installation

go get will get all dependancies, so there is no need for a second step

The problem is that there are no sources in the root of the package github.com/aws/aws-xray-sdk-go so go get will not follow the packages it contains automatically. To do so, either see my commit that references this PR or add  go get -u github.com/aws/aws-xray-sdk-go/... to the instructions.

Ah OK I see, that's an awkward one. But I agree dfb09e1 seems to be the suitable way round it.


Auth CustomMessage Lambda not building correctly

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
Amplify CLI is not building the Custom message/ Verification link lambda function that comes standard when you set up verification link with amplify auth. It is only including the verification-link.js and excluding the index.js file that is required to make the function work.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
v4.18.0
To Reproduce
Using amplify add auth. follow the path to add email verification with redirect link

Then you get default source tree:

Then run Amplify function build . the created package only include verification-link.js

Expected behavior
The created package should include index.js as the entry point for Lambda otherwise it fails to execute when invoked. Alternative would be to change the cloud watch template to target verification-link.js instead of index.js
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Node Version v12.16.0

@magjack This should be fixed with the latest release. Do you still see this when using v4.18.1?

Please comment if this issue persists with the latest version of the cli.


Remove asterisk, use tooltip to indicate data source

Current asterisk has a lot of visual weight & takes up more room than needed.
Currently:

Update: Removing asterisk from design and adding a tooltip instead that shows source on hover.

Per @r-czajkowski

We are going to remove the asterisk and footnote because the APY will be calculated based on the real time data.
https://github.com/keep-network/keep-core/pull/2252
On the other hand, the asterisk is a good option to indicate data source. Or tooltip? We use the uniswap subgraph API to fetch the total pool value and KEEP token in USD.

Removing asterisk from design and adding a tooltip instead that shows source on hover.

Tooltip will change depending on what pool it is associated with. For the KEEP pools:
KEEP-TBTC and KEEP-ETH:

Pool APY is calculated using the Uniswap subgraph API ↗ to fetch the total pool value and KEEP token in USD.

Uncertain for the TBTC pool what the text should read @r-czajkowski

Small update to this that moves the information icon into the corner instead of trying to align it by the label.

cc/ @michalsmiarowski


Don't get nginx access logs

Rancher versions:
rancher/server: v1.6.0
rancher/agent: v1.2.2
Infrastructure Stack versions:
healthcheck: Up to date
ipsec: Up to date
network-services: Up to date
scheduler: Up to date
Docker version: (docker version,docker info preferred)
Docker version 17.05.0-ce, build 89658be
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
NAME="Ubuntu"
VERSION="16.10 (Yakkety Yak)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.10"
VERSION_ID="16.10"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="http://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=yakkety
UBUNTU_CODENAME=yakkety
Type/provider of hosts: (Bare-metal)
Setup details: (single node rancher, internal DB)
Environment Template: (Cattle)
Steps to Reproduce:

start nginx container behind rancher lb
visit website
check logs from rancher ui

Results:

i just see the nginx error logs but not the access logs

nginx.conf
daemon off;

user www-data;
worker_processes  1;

events {
  worker_connections  1024;
}

http {
  include       /etc/nginx/mime.types;
  default_type  application/octet-stream;

  log_format          main  '$remote_addr - $remote_user [$time_local] "$request" '
                            '$status $body_bytes_sent "$http_referer" '
                            '"$http_user_agent" "$http_x_forwarded_for"';

  access_log          stdout main;
  error_log           stderr warn;

  sendfile            off;
  keepalive_timeout   65;

  server {
    listen       80;

    client_max_body_size	100M;

    root /var/www/html/web;
    index index.html index.php;

    charset utf-8;

    location / {
      try_files $uri $uri/ /index.php?$query_string;
    }

    location ~* ^.+\.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf)$ {
      root /var/www/html/web;
    }

    location ~ [^/]\.php(/|$) {
      fastcgi_split_path_info ^(.+?\.php)(/.*)$;
      if (!-f $document_root$fastcgi_script_name) {
          return 404;
      }

      fastcgi_pass php:9000;
      fastcgi_index index.php;
      include conf.d/fastcgi_params;
      fastcgi_read_timeout 900;
    }

    gzip                on;
    gzip_min_length     1000;
    gzip_proxied        any;
    gzip_types          text/plain
                        application/xml
                        text/css
                        text/js
                        application/javascript
                        application/x-javascript;
  }
}

docker-compose
version: '2'

services:
  web:
    image: myNginxImage:latest
    volumes_from:
      - php
    command: nginx -c /etc/nginx/nginx.conf
    logging:
      options:
        max-size: "25m"
        max-file: "4"
    labels:
      io.rancher.container.pull_image: always
      io.rancher.sidekicks: php
...

🤦♂ my nginx config is wrong. is must be /dev/stdout