HSEARCH-3091 Search 6 groundwork - Add to the predicate DSL the missing per-predicate options compared to Search 5

https://hibernate.atlassian.net/browse/HSEARCH-3091
The assessment of missed predicate options is here: Hibernate Search 6 - Query Predicates Comparison
I know I did too many commits, if you want, we could merge: done!

HSEARCH-3091 Test predicate-level * with range predicate ( as one )
HSEARCH-3091 Handle constantScore in multi field predicates with the previous one.

Pull Request Test Coverage Report for Build 1

65 of 72 (90.28%)  changed or added relevant lines in 12 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 88.475%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

engine/src/main/java/org/hibernate/search/engine/search/dsl/predicate/impl/BooleanJunctionPredicateContextImpl.java
0
2
0.0%

engine/src/main/java/org/hibernate/search/engine/search/dsl/predicate/impl/MatchAllPredicateContextImpl.java
0
2
0.0%

backend/lucene/src/main/java/org/hibernate/search/backend/lucene/search/predicate/impl/AbstractLuceneSearchPredicateBuilder.java
4
7
57.14%

Totals

Change from base Build 155:
0.01%

Covered Lines:
15599

Relevant Lines:
17631

💛  - Coveralls

Hi @yrodiere, thanks for the review. I think I've addressed to the most of your comments,
Furthermore, I created the issue HSEARCH-3505 in order to have more tests with constant score option.

I closed the follow-up HSEARCH-3505 as duplicate. Since tests on constant scoring are implemented here.
Furthermore, I've just update the Query Predicates Comparison document.
Removing .withConstantScore option from predicates:

Range
Spacial
MatchAll

And keeping it in the predicates:

Match
Bool

The changes are reflected in the main and test code.

Merged, thanks!

Thank you!!


Use a shorter check for a Rails app on deploy

In 17448e9 we added a check to determine if the application was running
Rails (specifically whether the app had access to Rake and a
db:migrate task) through Rake's "dry-run" functionality. This approach
produces some noisy output and adds a non-trivial amount of time to the
deploy process.
Rather than start Rake and execute the dry run on every deploy, we'll
instead check for a Rakefile and the presence of db/migrate in the
application's folder structure, which will take less time and produce
less noise in STDOUT.

Makes sense to me.


Non-deterministic missing contracts in forking

At times there are some false-positives when trying to retrieve/interact with contracts, namely:
Got an exception while executing a hint: Hint Error: Requested contract address ContractAddress(PatriciaKey(StarkFelt("0x00000005dd3d2f4429af886cd1a3b08289dbcea99a294197e9eb43b0e0325b4b"))) is not deployed.

(mainnet)
Hint: might be related to a caching issue

Another error that might be related:
[FAIL] unruggable::tests::fork_tests::test_ekubo::test_ekubo_launch_meme_with_pool_1percent

Failure data:Failed to read from state: Unable to get block with tx hashes from fork, err: StarknetError(StarknetErrorWithMessage { code: Known(BlockNotFound), message: "Block not found" }).
[FAIL] unruggable::tests::fork_tests::test_ekubo::test_ekubo_launch_meme

Failure data:Failed to read from state: Unable to get block with tx hashes from fork, err: StarknetError(StarknetErrorWithMessage { code: Known(BlockNotFound), message: "Block not found" }).
[PASS] unruggable::tests::fork_tests::test_ekubo::test_ekubo_launch_meme_token1_price_below_1, gas: ~1762.88
Number of the block used for fork testing = 495876

Some fork tests pass, some other have a "Block not found" error

Over the last 10 tests 8 of them have failed because of issues due to the forking feature. When running two very similar tests, forking the same block of the same network and calling the same contracts, one of the succeeds and one of them fails with Contract not deployed

@enitrat have you been experiencing it since?
I have not been able to reproduce this unfortunately, perhaps there is a problem with specific kinds of contracts , could you share the address?
Also, what node provider are you using? (so that i could perhaps test that possibility out) (or is it self-hosted node?)

You can probably try multiple runs of  these tests with the Blocktag.Latest. I was using nethermind-rpc, but since it was working fine for some tests and not for others I guess this must be a problem of caching (unless the same requests are duplicated multiple times and not cached?)
https://github.com/keep-starknet-strange/unruggable.meme/pull/147


Whether to include pre-trained models

Thanks for such a great job
does the repository include pre-trained models, which I am not seeing at the moment, or should I set up my own dataset to start training based on the implemented code?

Hi @KawaiiAsh , were you able to find pretrained weights for the implementation in this repo? Or are we to look into https://github.com/rwightman/pytorch-image-models


Cannot assign prisoner beds.

BUG DESCRIPTION
Prisoner beds are unable to be assigned as such when using Rimthreaded <IP_ADDRESS>
To Reproduce
Steps to reproduce the behavior:

Create a new colony or load up an existing one.
Attempt to assign a bed as a prisoner bed.
Try again and again as it does not work...
......
Contemplate your life choices.

Error Log
None to speak of
Harmony
Core
HugsLib
RimThreaded

seemed to work fine for me in <IP_ADDRESS>. Can you confirm issue still exists?

Can confirm, no longer occurs.


Who is the author of open-methane prior?

In the pyproject.toml we mention the authors of the repository. There should be at least one author in the form name and email.
Originally posted by @lewisjared in https://github.com/openmethane/openmethane-prior/pull/10#discussion_r1616879037

This repo is an original work by Gerard Mason and Peter (see the initial commit here: https://github.com/openmethane/openmethane-prior/commit/63c4f59b3fb21fcb00058087852646d72d74efd3).
If there's room for multiple authors I would definitely mention them both, and definitely add yourself and Jared.

Added a suggestion: https://github.com/openmethane/openmethane-prior/pull/10/files/450d0fccecaa096cb2f4d929410e3226a93ccb14#r1618046538

Added a suggestion: https://github.com/openmethane/openmethane-prior/pull/10/files/450d0fccecaa096cb2f4d929410e3226a93ccb14#r1618046538

Thank you. I will integrate this in the next pull request

Authors are now in pyproject.toml


[JENKINS-31153] Rename Workflow to Pipeline

As part of JENKINS-31153
@reviewbybees, specially @abayer

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

:bee:

:bee:

@reviewbybees done, Thank @tfennelly and @amuniz

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.


Create base authentication service

Firebase for Single Sign On authentication has been deployed
API Key is not hidden yet. Planned to hide the API key in another pull request. If anyone does not agree with allowing the API Key to be visible in this pull request, please let me know and I'll hide them in this pull request.
Users can only sign in and create an account with email and password at the moment.
Other SSO functions will be done is separate pull requests.

Currently the sign in button is used to sign up and vice versa. Maybe you could swap so that the sign in button is used to sign in and similarly for the sign up. :)

Thanks for spotting that UX flaw! Will improve on it in another branch!


Access entry for aws console

Description
Trying out a basic kms + karpenter setup (copy pasted from the ./examples folder), in eu-west-3 (in case it matters). Everything works fine, besides the access/visibility of resources within the control plane within the aws console.

✋ I have searched the open/closed issues and my issue is not listed. -> But it is totally unclear to me if the behaviour is normal (am i wrong to think it should work out of the box?)

Versions

Module version [Required]:
20.13.1

Terraform version:
v1.5.7

Provider version(s):
hashicorp/aws :  5.53.0
hashicorp/helm : 2.13.2
alekc/kubectl : 2.0.4

Reproduction Code
N/A, copy pasted the eks + karpenter from example
Steps to reproduce the behavior:
Creates a cluster in eu-west-3. Once finished, go to aws console, enter the cluster, view the no access messages :

at the top : "Your current IAM principal doesn't have access to Kubernetes objects on this cluster."
under the kubernetes resources : This cluster does not have any xxx, or you don't have permission to view them.

Create the access entry manually for arn:aws:iam:xxx:root with AmazonEKSViewPolicy, save it : everything is then okay. kubernetes resources appears, so does the node groups and all; no more "no access messages"
Expected behavior
Having everything configured for the control plane to be fully available with no extra manual steps within the aws console's eks cluster pages
Actual behavior
Having to create the access entry manually to view the resources within the aws console's cluster pages

I'm having the same issue with the 20.13.1 version in eu-west-2 region. I'm not able to see the resources, and also not able to access the cluster via CLI using kubectl.
In my case I just used a previous working version in 19.15.4 and it did work.
By the way @bryantbiggs, where did you create the manual entry?

I don't know what you mean by a "manual entry" - the issue you are experiencing is that you haven't given your IAM identity access to the cluster

I don't know what you mean by a "manual entry" - the issue you are experiencing is that you haven't given your IAM identity access to the cluster

Sorry the question was for @benbonnet :)  ... And I'm using the same user who created the cluster. It did work with 19.15.4, but not with 20.13.1

Thats because in v19.x the cluster creator was automatically added to the cluster as admin, but that is no longer the case now that cluster access entry is available. you will need to opt in to providing your IAM entity access to the cluster


xbr:jinja2 missing dependency

missing dependency for xbr dist flavor:
(cpy390_5) oberstet@intel-nuci7:~$ xbrnetwork version
Traceback (most recent call last):
  File "/home/oberstet/cpy390_5/bin/xbrnetwork", line 5, in <module>
    from autobahn.xbr._cli import _main
  File "/home/oberstet/cpy390_5/lib/python3.9/site-packages/autobahn/xbr/_cli.py", line 33, in <module>
    from jinja2 import Environment, FileSystemLoader
ModuleNotFoundError: No module named 'jinja2'

fixed via https://github.com/crossbario/autobahn-python/pull/1448

fixed via https://github.com/crossbario/autobahn-python/pull/1448


Duplicate RegisteredService

Closes #1581
This adds a duplicate button to the CAS management UI. This allows quick configuration of a new service off of a pre-existing service.
I had to update AbstractRegisteredService because the TreeSet used in DefaultServicesManagerImpl eliminates any services that compare as equal (same eval order, name, & serviceId).
This corner case in a properly configured CAS server should never exist, but the duplicate service functionality exposed the corner case when those values aren't updated in the new duplicate service definition. This led to the new duplicate service not appearing on the admin UI.

Looks great. Could you also attach a screenshot?

Very nice!
:+1:


Text on the translation page does not match the choices in the add modal

The single-choice option is labelled as a radio button on the translation page. Change one to be consistent,
Private Zenhub Image

** Review all copy in EN and FR for all question types and blocks

@anikbrazeau now is probably a good time to look at this since we've made some language adjustments to the modal

@anikbrazeau can you review the copy on the translation page to ensure alignment with the new add modal?


make ui interactions

cancel interaction when tests are re-run

Don't need to cancel as during await test runs the watch listener is paused


Unable to build Angular app with ServiceHub package

Package Name: service-bus
Package Version: 1.1.0
Operating system: Windows 10
[ ] nodejs

version: 12.10.0

[ ] browser

name/version: Chrome

[ ] typescript

version: 3.5.3

Describe the bug
I am trying to implement receiving Service Bus messages in an angular app. Upon running 'ng serve' I get the following exceptions:
ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve 'dns' in 'D:\_src_\NotificationsClient\app\node_modules\@azure\amqp-common\dist-esm\src' ERROR in ./node_modules/rhea/lib/connection.js Module not found: Error: Can't resolve 'fs' in 'D:\_src_\NotificationsClient\app\node_modules\rhea\lib' ERROR in ./node_modules/rhea/lib/container.js Module not found: Error: Can't resolve 'net' in 'D:\_src_\NotificationsClient\app\node_modules\rhea\lib' ERROR in ./node_modules/rhea/lib/connection.js Module not found: Error: Can't resolve 'net' in 'D:\_src_\NotificationsClient\app\node_modules\rhea\lib' ERROR in ./node_modules/rhea/lib/container.js Module not found: Error: Can't resolve 'tls' in 'D:\_src_\NotificationsClient\app\node_modules\rhea\lib' ERROR in ./node_modules/rhea/lib/connection.js Module not found: Error: Can't resolve 'tls' in 'D:\_src_\NotificationsClient\app\node_modules\rhea\lib'
To Reproduce
Steps to reproduce the behavior:

Create new angular app
Import ServiceBus packages
Try to create SBClient using:
ServiceBusClient.createFromConnectionString(this.connectionString);

For now, the below needs to be stubbed when using Service Bus in web apps

dns
fs
net
tls

See #5364 for more details which tracks this issue.
Please let us know if you can use the workaround specified there

@ramya-rao-a I am sorry, I am not very proficient with Angular. Could you please elaborate on how do I create those stubs? I can't seem to find anything related to webpack config in my app.

@joheredi is looking into this and will post his findings soon

Thanks for reporting this @ncksolcan, can you please try adding the following to your package.json and let me know if the build error goes away?
"browser": {
    "dns": false,
    "fs": false,
    "net": false,
    "tls": false
  }

@ncksol We have to close this issue as we havent heard back from you in over 4 months now. Please try the workaround @joheredi mentioned above. If you continue to see this issue, please drop in a comment and we can re-open the issue for further investigation.


feat: Add lifecycle hook support to ingress container

What this PR does / why we need it:
Lifecycle hooks on the ingress-controller container can help in several cases, like:

Race conditions with the Istio sidecar container. As described in kong/kubernetes-ingress-controller#4603, also in Istio's istio/istio#11130 and the proposed solution in this comment.
May help in wait for network situations like the one described in kong/kubernetes-ingress-controller#4207
Stop conditions like the one described in kong/charts#868

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #868

Special notes for your reviewer:
Modified the ingress-controller container template, the value file and the readme.
Thank you for considering the option to add lifecycle hooks to the ingress-controller container.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the main branch.
[x] New or modified sections of values.yaml are documented in the README.md

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Per https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks

PostStart
This hook is executed immediately after a container is created. However, there is no guarantee that the hook will execute before the container ENTRYPOINT. No parameters are passed to the handler.

so lifecycle wouldn't actually block the entrypoint (the part that's failing), just run something around the same time. Were you actually seeing different behavior in practice?
AFAICT the Istio workarounds do block other parts of the lifecycle. It looks like adding the PostStart hook would block the Pod from entering the running state, and presumably keep it out of a Service's endpoints, but that doesn't matter for the controller, since it's not used for a Service.
First-class support for sidecar containers looks like a better solution, since the sidecars become a special sort of initContainer and do block main container startup, though that's only recently become available. Do you have access to  Kubernetes 1.28 instance where you can enable feature flags to try adding a sidecarContainers injection point instead?

I have been testing the lifecycle workaround for a day with mixed results. I will try to answer the best I can.

Per https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks

PostStart
This hook is executed immediately after a container is created. However, there is no guarantee that the hook will execute before the container ENTRYPOINT. No parameters are passed to the handler.

so lifecycle wouldn't actually block the entrypoint (the part that's failing), just run something around the same time. Were you actually seeing different behavior in practice?

Correct, the hook runs asynchronously so it does not stop the container to start. However, upon failure of the hook the container is restarted. The idea behind the workaround is to keep restarting the container until the Envoy sidecar is ready.
Sadly, that asynchronicity also allows for a scenario in which it doesn't work as intended. I have seen the following happen under heavy load:

The container starts and begins running the code (the setup with the api discovery that fails when there is control plane outage)
The envoy sidecar becomes ready
The postStart hook executes

In this order the container becomes ready but the ingress is in a bad state since the setup run with no control plane access.

AFAICT the Istio workarounds do block other parts of the lifecycle. It looks like adding the PostStart hook would block the Pod from entering the running state, and presumably keep it out of a Service's endpoints, but that doesn't matter for the controller, since it's not used for a Service.

Indeed, while the ingress container is restarted the Pod can't become ready. But this is the desired behavior. Without the hook the Pod becomes ready immediately after the containers are running but the proxy is not configured because the ingress setup failed and the users receive the "No routes matched" error. We are trying to avoid that.

First-class support for sidecar containers looks like a better solution, since the sidecars become a special sort of initContainer and do block main container startup, though that's only recently become available. Do you have access to Kubernetes 1.28 instance where you can enable feature flags to try adding a sidecarContainers injection point instead?

I don't currently have access to a 1.28 cluster. I'm working with 1.23 soon to be updated to 1.26 clusters. The feature looks interesting though.
With all this being said, I understand if you don't want to add the lifecycle config to the ingress controller. It is not a definitive solution, just a partial workaround to some problems.
The introduction of the new controller logic in the 2.8.x release is preventing us from upgrading our Kong installations as there is no way we can guarantee network availability upon pod start (specially under heavy load) and the controller does not retry nor checks for control plain availability before setup.
At this point I am thinking of maintaining a custom KIC image and add some check script at the entrypoint.
Anyway, thanks for reading and for all the help.

https://github.com/Kong/kubernetes-ingress-controller/pull/4641 will just exit if the API server is unreachable, which should resolve the Istio issue.


Loaded scripts in command pallete does not show parent resources

Refs: #62093
Since we now show parent resources in the loaded scripst view I would expect that we also show parent resources in the loaded scripts in the command palette.

@isidorn what do you mean "in command palette"?

@isidorn do you mean the quick pick base loaded scripts?

Yes I mean the quick pick, sorry for the wrong wording.


flaky: TestE2E/GatewayInfraResourceTest/create_gateway

https://github.com/envoyproxy/gateway/actions/runs/8682049913/job/23807045173

lets disable this ? long term we need to move infra tests into k8s integration tests similar to what we have for the provider

@ardikabs PTAL

lets disable this ? long term we need to move infra tests into k8s integration tests similar to what we have for the provider

let me try to move on k8s integration tests, can you assign it to me @zirain ?

/assign ardikabs

The problem has receded recently


Spawn cargo add in the new command

Fixes #204
cargo component add now spawns cargo add cargo-component-bindings . This has a few implications:

It makes the command a bit slower as it needs to fetch the metadata from the network
It uses the latest version by default.
When in a workspace, and cargo-component-bindings is already defined as a workspace dependency, it uses the workspace version.

cargo component upgrade was not changed. I believe this command does too much and should be reconsidered.
Tests did not have to be changed, but checking a specific cargo-component-bindings version in tests might be problematic.

Hi @tomasol. Thanks again for tackling this issue!
If we merge #212, the bindings crate has been removed entirely; however, it adds a dependency on wit-bindgen to pull in the runtime functions (disables the macro generation code, so it only has one additional transitive dependency).
So I think we should keep this change but update it for adding the dependency on wit-bindgen with --no-default-features and --features realloc.
That way we can remove the hardcoded version added by #212 and automatically pull it from a workspace if it's already there.

I've pushed up the proposed change and fixed a bug where we weren't checking the returned status for a non-successful exit (the workspace related tests should have failed as it wasn't adding the dependency because the workspace was setup before the subprojects were created; just had to fix the ordering in the tests).

@peterhuene Thanks for improving and merging the PR!


How to output subtitle files when converting text to speech?

How to output subtitle files when converting text to speech?

we have wordboundary events, you can construct the subtitle file based on it. e.g., https://github.com/Azure-Samples/cognitive-services-speech-sdk/blob/master/samples/java/jre/console/src/com/microsoft/cognitiveservices/speech/samples/console/SpeechSynthesisSamples.java#L704

thanks.

Closed as answered, please open a new issue if more support is needed.

we have wordboundary events, you can construct the subtitle file based on it. e.g., https://github.com/Azure-Samples/cognitive-services-speech-sdk/blob/master/samples/java/jre/console/src/com/microsoft/cognitiveservices/speech/samples/console/SpeechSynthesisSamples.java#L704

Thanks！


5661 statistics to badges

Description (required)
Fixes #5661
What changes did you make and why?
Transformed the statistics of achievement into badges. Each badge changes to gray and hides its count if the value is 0.

Added badgeRender(Map<ImageView, TextView> badgeMap) function, used to render badges with a filter, and the GrayFilter(ImageView imageView) function applies the gray filter.

Used Google’s FlexboxLayout to enable badges to wrap automatically in the layout.

Added String Badges in Strings.xml, drawable badge_number_background.xml in drawable for displaying.

Tests performed (required)
Tested AchievementsFragmentUnitTests on Medium Phone API 33 (Android 13.0 "Tiramisu" | arm64 emulator).
Screenshots (for UI changes only)
Set badges numbers to 0

None 0 badges

[x] I've read CONTRIBUTING.md

Looks great! :-)

Hi  @nicolas-raoul what should I do with the failing check? or just leave it there?

I will check whether unit tests fail in master. If yes then don't worry.

Please do not worry about unit tests, this is tracked at #5921
But do you have time to check https://github.com/commons-app/apps-android-commons/pull/5917#pullrequestreview-2412011916 ? :-)

@YujingZHG Did you get a chance to check? A small conflict must also be fixed. Is it OK for someone else to continue your work? Thanks! :-)

@nicolas-raoul  Yes. Thanks :)

Thanks all! :-)


setting _error in submit handler without SubmissionError

I know that the async submission handler I can use SubmissionError to signal any validation errors found during submission. The documentation states that SubmissionError should only for validation errors and not for low-level AJAX errors:

SubmissionError
A throwable error that is used to return submit validation errors from onSubmit. The purpose being to distinguish promise rejection because of validation errors from promise rejection because of AJAX I/O problems or other server errors.

In my case I'd like to use _error to show the user that it was not possible to submit the form and that he shall try again.
I cannot (should not) use SubmissionError for that, especially because the form cannot be resubmit unless a field is changed (see also #1884).
But then, how can I set _error in my submit handler?

+1

I cannot (should not) use SubmissionError for that, especially because the form cannot be resubmit unless a field is changed

I'm on redux-form 6.1.0 and SubmissionErrors with only an _error key do not prevent repeated form submission, even without touching any fields. Only field-specific errors prevent submission as you described.
Even though using _error works, the documentation's description of SubmissionError (as you mentioned) does make it feel dirty using an _error for non-validation issues. It would be a nice enhancement to have a built-in method of communicating those types of errors from within a handleSubmit function!
I have a workflow that avoids this problem, with the trade-off of more complexity for more control. onSubmit receives the redux dispatch function as a second parameter. So, I place async form submission code inside of a redux-thunk action creator which I dispatch from onSubmit (always returning a promise from all functions). I then dispatch actions from the thunk to track the state of the request myself, and connect the form (or higher-level component) to that state. This allows dispatching non-validation errors and many other types of information to influence rendering.
For simple forms it feels like overkill. For more complex forms it can be convenient. It's probably too much code to post examples, but hopefully that paints a proper picture of one workaround.

I'm on redux-form 6.1.0 and SubmissionErrors with only an _error key do not prevent repeated form submission, even without touching any fields. Only field-specific errors prevent submission as you described.

You're right. I'm using 6.2.0 and the problem seems to have disappeared. :)

I'm closing this based off @jampy's comment.


Fixed issue #16762 change the color of text challenge

Changed the   to

Hi @renisalcedo thanks for making the pull request. As we are interested in welcoming more contributions to the code-base from first timers, we would like them to follow our Guidelines for Contributing.
Please go through it, and fill in the pull request template presented to you while creating this PR.
Update the PR title, using the edit button on top left and editing the description to use the template linked above using the pencil icon button.
Let us know if you need help.


Timeout on 200+ followings

Using the command in iTerm does the job but it timeouts so you will have to relaunch it till it's done
OS: macOS Monetary
Chip: Apple M1
Total Number of Cores:	8 (4 performance and 4 efficiency)
Memory:	16 GB
oops. an error occured: Error: read ETIMEDOUT
    at module.exports.sendError (/opt/homebrew/lib/node_modules/github-unfollow-everyone/node_modules/github/api/v3.0.0/index.js:30:19)
    at /opt/homebrew/lib/node_modules/github-unfollow-everyone/node_modules/github/api/v3.0.0/user.js:728:29
    at callCallback (/opt/homebrew/lib/node_modules/github-unfollow-everyone/node_modules/github/index.js:743:17)
    at ClientRequest.<anonymous> (/opt/homebrew/lib/node_modules/github-unfollow-everyone/node_modules/github/index.js:809:17)
    at ClientRequest.emit (node:events:527:28)
    at TLSSocket.socketErrorListener (node:_http_client:442:9)
    at TLSSocket.emit (node:events:527:28)
    at emitErrorNT (node:internal/streams/destroy:164:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  defaultMessage: 'Internal Server Error',
  code: '500'
}

This could be caused by the github API request rate limits.


Cannot write a unit test to make sure that it is not possible to drag some draggable

Describe the bug
I am trying to write a unit test to verify that some useDrag cannot be dragged under some conditions however the way that I have found to test throws an Invariant Violation: Cannot call hover while not dragging. error.
Reproduction
This is how I do the test
const firstItem = discover.getSingleElement("slot-index", "1").discovered; // This item has `canDrag: false`
const secondItem = discover.getSingleElement("hotbar-item-id", "some-id").discovered;

fireEvent.dragStart(firstItem);
fireEvent.dragEnter(secondItem);
fireEvent.dragOver(secondItem);
fireEvent.drop(firstItem);

Expected behavior
Nothing to been thrown but also not calls drop.

FYI I have found a workaround for the time being
import type { Backend, BackendFactory } from "dnd-core";
import { HTML5Backend } from "react-dnd-html5-backend";

const HotbarBackend: BackendFactory = (manager, globalContext, configuration) => {
  const base = HTML5Backend(manager, globalContext, configuration) as Backend & {
    handleTopDrop: (e: DragEvent) => void;
  };
  const internalHandleTopDrop = base.handleTopDrop;

  base.handleTopDrop = (e: DragEvent) => {
    try {
      internalHandleTopDrop(e);
    } catch (error) {
      if (process.env.JEST_WORKER_ID) {
        if (process.env.DEBUG) {
          console.warn(error);
        }
      } else {
        throw error;
      }
    }
  };

  return base;
};


fix: Use environment CXX to configure fastjet-contrib .Makefile.inc

fastjet-contrib's .Makefile.inc is created at ./configure time, which means that is the environment's CXX is accessible inside of setup.py it can be passed in as an argument to configure. Use this to set CXX for fastjet-contrib/.Makefile.inc and use a default value of g++ if no environment value is set.
Remove g++ from build requirements.

Example of this working in a local build: CXX is set to use x86_64-conda-linux-gnu-c++
$ cat $(find build_artifacts/*/work/fastjet-contrib/ -type f -iname ".Makefile.inc")
# contrib-wide Makefile include file, generated automatically with
# ./configure --fastjet-config=/home/conda/staged-recipes/build_artifacts/fastjet_1708158057057/work/fastjet-core/fastjet-config CXX=/home/conda/staged-recipes/build_artifacts/fastjet_1708158057057/_build_env/bin/x86_64-conda-linux-gnu-c++ CXXFLAGS=-O3 -Bstatic -Bdynamic -std=c++17
CXX=/home/conda/staged-recipes/build_artifacts/fastjet_1708158057057/_build_env/bin/x86_64-conda-linux-gnu-c++
CXXFLAGS=-O3 -Bstatic -Bdynamic -std=c++17
FASTJETCONFIG=/home/conda/staged-recipes/build_artifacts/fastjet_1708158057057/work/fastjet-core/fastjet-config
PREFIX=/home/conda/staged-recipes/build_artifacts/fastjet_1708158057057/work/src/fastjet/_fastjet_core
install_script = $(SHELL) ../utils/install-sh
check_script = ../utils/check.sh

...this sadly doesn't fix the overlinking, but we're getting there!

@lgray this is ready for review (though this would be easier to read then a suggested change on https://github.com/conda-forge/staged-recipes/pull/21052)


Unable to concatenate Keras Tensor and Eager Tensor using tf.keras.layers.Concatenate

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
2.13
Custom code
Yes
OS platform and distribution
Ubuntu 20.04
Mobile device
No response
Python version
3.8
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I want to pad the Keras Tensor without using tf.pad or tf.concat.
My approach is to create an empty tensor with zeros and concatenate the last layer with the Keras Tensor.
I have successfully saved the model. But when I try to load the model, I am getting errors, I have attached code to recreate the error and logs as well.
The expected output is concatenated Keras tensor on the last axis.
Standalone code to reproduce the issue
import tensorflow as tf
from tensorflow.keras.models import Model, save_model, load_model
from tensorflow.keras.layers import Input, Concatenate, Conv2D, ReLU

# Define the input shape
input_shape = (128, 128, 3)  # Replace with your input dimensions

# Create the input layer
input_layer = Input(shape=input_shape)

# Create empty channels
empty_channels = tf.zeros((input_shape[0], input_shape[1], 4))

# Expand the dimensions of empty_channels to match input_shape
empty_channels = tf.expand_dims(empty_channels, axis=0)

# Concatenate the input with the empty channels
concatenated = Concatenate(axis=-1)([input_layer, empty_channels])

# Create the model
model = Model(inputs=input_layer, outputs=concatenated)

# Display model summary
model.summary()

# Save the model to a file
model.save("concatenated_model.h5")

print("Model has saved.")
# Now, to load the saved model
loaded_model = load_model("concatenated_model.h5")
print("Model has loaded.")

Relevant log output
python3 testPython.py                                                               1 ✘
2023-09-20 13:14:52.746990: I tensorflow/core/util/port.cc:110] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2023-09-20 13:14:52.777548: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
Model: "model"
_________________________________________________________________
 Layer (type)                Output Shape              Param #
=================================================================
 input_1 (InputLayer)        [(None, 128, 128, 3)]     0

 concatenate (Concatenate)   (1, 128, 128, 7)          0

=================================================================
Total params: 0 (0.00 Byte)
Trainable params: 0 (0.00 Byte)
Non-trainable params: 0 (0.00 Byte)
_________________________________________________________________
/home/hitech/.local/lib/python3.8/site-packages/keras/src/engine/training.py:3000: UserWarning: You are saving your model as an HDF5 file via `model.save()`. This file format is considered legacy. We recommend using instead the native Keras format, e.g. `model.save('my_model.keras')`.
  saving_api.save_model(
WARNING:tensorflow:Compiled the loaded model, but the compiled metrics have yet to be built. `model.compile_metrics` will be empty until you train or evaluate the model.
Model has saved.
Traceback (most recent call last):
  File "testPython.py", line 33, in <module>
    loaded_model = load_model("concatenated_model.h5")
  File "/home/hitech/.local/lib/python3.8/site-packages/keras/src/saving/saving_api.py", line 238, in load_model
    return legacy_sm_saving_lib.load_model(
  File "/home/hitech/.local/lib/python3.8/site-packages/keras/src/utils/traceback_utils.py", line 70, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/home/hitech/.local/lib/python3.8/site-packages/keras/src/layers/merging/concatenate.py", line 119, in build
    raise ValueError(err_msg)
ValueError: A `Concatenate` layer requires inputs with matching shapes except for the concatenation axis. Received:
input_shape=[(None, 128, 128, 3), [[[[(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], [(), (), (), ()], .....

chk

@SuryanarayanaY I was able to replicate the issue reported here. Thank you!

Hi @Prashant-THRSL ,
Apologies for the delayed response.The issue got fixed with keras3 and tf-keras 2.15v. Please refer attached gist.
Since Keras3 is now multi backend supporting and for TF specific you need to install tf-keras package.


Do not duplicate extra_info into text when saving Node into vector store

Summary

Previously, we were using Node.get_text() to save Node text into vector store, while also saving the extra info, this means that after loading the Node back, calling Node.get_text() would have the metadata injected twice into the Node text.
This fixes the bug, by saving the Node.text to avoid duplicating the metadata.

Yea this makes sense. It might also work to have a different function to get just the node text, or maybe an option in the existing get_text() function?
Either way, looks good 👍

Yea, I think the proper fix here is to have get_text return just text (whether if it's document or node), and have a different function like get_text_with_metadata to be more explicit.


Update main.py

in line 45 this command line is not working correctly replace with:_options.add_experimental_option('prefs', {'intl.accept_languages': 'en,en_US'})
see in this post at stackoverflow for more information:
https://stackoverflow.com/questions/55150118/trouble-modifying-the-language-option-in-selenium-python-bindings

Thanks 👍


Double Tap opens/closes NavigationBar

In the current (podfile) version a double tap also opens/closes the NavigationBar. To ignore the single tap if there is a double tap I altered your code the following way:
Inside PDFPageView.swift:
internal final class PDFPageView: UIScrollView {

    ...

    init(frame: CGRect, document: PDFDocument, pageNumber: Int, pageViewDelegate: PDFPageViewDelegate?) {

        ...

        let doubleTapOne = UITapGestureRecognizer(target: self, action:#selector(handleDoubleTap))
        doubleTapOne.numberOfTapsRequired = 2
        doubleTapOne.cancelsTouchesInView = false
        addGestureRecognizer(doubleTapOne)

        let singleTapOne = UITapGestureRecognizer(target: self, action:#selector(handleSingleTap))
        singleTapOne.numberOfTapsRequired = 1
        singleTapOne.cancelsTouchesInView = false
        addGestureRecognizer(singleTapOne)

        singleTapOne.require(toFail: doubleTapOne) // New Line

        ...
    }
    ...
}

feel free to adopt this behaviour ;)

Thanks! Single tapping toggles the nav bar, and initially I assumed double tapping, in addition to zooming in and out of the document, should also toggle the nav bar, but now I'm having my doubts whether this is the right approach. I think we should keep it simple: single tap to toggle the nav bar, double tap to zoom in and out. Feel free to open a pull request if you're interested in getting credit for the commit :) I'll also leave this issue open a while longer in case anybody has any strong opinions one way or another.

Thanks, but it would be nice, if you could change that. A Fork for this little line is overkill in my opinion ;)


Syntax errors given for valid extensions

The AWS Tools extension for Azure Pipelines (https://marketplace.visualstudio.com/items?itemName=AmazonWebServices.aws-vsts-tools) allows tasks like this to be specified in azure-pipelines.yml:
Deploy to AWS Elastic Beanstalk

task: BeanstalkDeployApplication@1
inputs:
awsCredentials: 'AWS'
regionName: 'eu-west-2'
applicationName: 'HelloWorld'
environmentName: 'Helloworld-env'
applicationType: 'aspnetCoreWindows'
logRequest: true
logResponse: true

However, this generates 13 syntax errors as the plug-in is evidently not aware of this task type.  A similar thing happens with the SonarQube extension (https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarqube).  I can't find any way to turn these syntax errors off; therefore the tool is not much use to me at the moment.

Thanks for the report. It's not obvious, but this is a dupe of #226.


Add notary binary requirement for tests

This PR adds the "notary" binary requirement for tests.
Previously, NotaryHosting was checking for the "notary-server"
binary under the name notaryBinary. This renames that reference to
notaryServerBinary, so that notaryBinary can rightly refer
to the actual "notary" binary.
Currently only one test actually uses the notary binary, so it's been
updated accordingly.
Signed-off-by: Christopher Jones<EMAIL_ADDRESS>Here are some cute Russian Navy Seals:

LGTM

LGTM


Clean up log4j2 conf and enhance surefire plugin conf

Why are the changes needed?

THRIFT-4805 has been fixed in thrift 0.13.0, we can remove the workaround of log4j2 configurations because we use thrift 0.16.0 now, the change also removes the following warnings.
2022-03-01 23:18:16,530 main ERROR Filters contains invalid attributes "onMatch", "onMismatch"
2022-03-01 23:18:16,543 main ERROR Filters contains invalid attributes "onMatch", "onMismatch"

maven-surefire-plugin is only used in kyuubi-hive-jdbc, we should disable it in other modules.
[INFO] --- maven-surefire-plugin:2.22.0:test (default-test) @ kyuubi-ctl_2.12 ---
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
2022-03-01 23:18:16,530 main ERROR Filters contains invalid attributes "onMatch", "onMismatch"
2022-03-01 23:18:16,543 main ERROR Filters contains invalid attributes "onMatch", "onMismatch"
[INFO] Running org.apache.kyuubi.ctl.ServiceControlCliSuite
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 s - in org.apache.kyuubi.ctl.ServiceControlCliSuite
[INFO] Running org.apache.kyuubi.ctl.ServiceControlCliArgumentsSuite
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.apache.kyuubi.ctl.ServiceControlCliArgumentsSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Thanks, merging to master


Better wordlist

Remove "not exist files" (because of the initial creation, which auto added .%EXT% to the end of folders) and add some good (with extensions) files.

Thank you!


[Bug report]

Documentation check
If the bug manifests in unexpected behavior (as opposed to a crash), confirm that you have consulted the
API documentation

[x ] I have checked the API documentation.
[ x] I could not locate relevant information in the documentation or information is missing.

Describe the bug
I just installed scqubits-1.2.1 and can't import it in python (neither jupyter nor command line). The first issue was that I needed to do from ipywidgets import widgets before the import scqubits as scq statement. After I resolved that, I still couldn't load the package and received the following error:
~/anaconda3/lib/python3.6/site-packages/scqubits/ui/gui.py in <module>()
    46
     47 import scqubits as scq
---> 48 import scqubits.utils.misc as utils
    49
     50 from scqubits.core.qubit_base import QubitBaseClass
AttributeError: module 'scqubits' has no attribute 'utils'
Expected behavior
I would have expected scqubits to load after installation.
OS and version used (please complete the following information):

OS: macOS 10.15.7
scqubits version 1.2.1
Python version 3.6.5 (Anaconda)

Additional context
Thanks for the great package! It works well in Binder, just not on my own machine.

I got scqubits to load after commenting out most of the gui.py file (which probably disabled some functionality but I don't need the GUI for what I want to try). See attached.
gui.py.zip

Thank you for filing your issue. We will be looking into it. The problem is puzzling since that release passed all pytests with Python 3.6 on macOS (not sure which macOS version, though - this ran via Azure).

Thanks for the prompt reply! It's possible that this is a rare case related to my combination of Anaconda version, macOS version etc. Just wanted to flag it in case others also experience it. I got everything that I needed to work after all (just not the GUI, which is not crucial for me). Thanks again for the great package!

It's quite possible that this is a rare case (at least it is the first we encounter, with a several people in our group using macOS and anaconda as well). Would be good to understand the origin, so we can minimize rare cases. If you would not mind: could you please post the result from conda list so we have an even better understanding of your environment? Thanks!

 Based on anaconda's docs that seems to be discouraged and they claim it can lead to problems.
I can reproduce the wonky gui related widgets errors when i do that on my machine... (i.e.  when install scqubits via pip that conda sets up.... on the other hand when i install scqubits with conda install -c conda-forge scqubits, everything works fine):
(test4) pgroszko@laptop7~$ python
Python 3.8.10 (default, Jun  4 2021, 15:09:15)
[GCC 7.5.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import scqubits as scq
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/pgroszko/anaconda3/envs/test4/lib/python3.8/site-packages/scqubits/__init__.py", line 51, in <module>
    from scqubits.ui.gui import GUI
  File "/home/pgroszko/anaconda3/envs/test4/lib/python3.8/site-packages/scqubits/ui/gui.py", line 53, in <module>
    class GUI:
  File "/home/pgroszko/anaconda3/envs/test4/lib/python3.8/site-packages/scqubits/ui/gui.py", line 671, in GUI
    def energy_scan_interactive(self) -> widgets.interactive:
NameError: name 'widgets' is not defined

Maybe the first thing to try (in case you haven't already) would be to:
(1) update your conda distribution
(2) create a clean conda environment
(3) install scqubits via conda install -c conda-forge scqubits (this is the crucial step - do not use pip that anaconda sets up)
If that doesn't work, perhaps setting a conda environement with a newer python version would also by worthwhile.
(Finally, the scqubits that you are getting should not be 1.2.1, but instead 2.1)

Thanks, @petergthatsme !
I realize that both our README and documentation say something along the lines of "Alternatively, you can install scqubits via pip." Should I insert a parenthetical remark about pip install being discouraged while using a conda environment?

Thanks a lot for the answers and for reproducing the issue. This is extremely helpful. I will upgrade my anaconda distribution accordingly (I have been having issues with the conda install command, which is why I used pip). From my user perspective, a parenthetical note about not using pip within a conda environment would be great. That concludes the issue, thanks so much!

Thanks for the follow up @Timmenke.
Yes, I agree with both of you, some mention of this should be in our docs, which I will add.


Add starter code for prework project

Added starter code and fixed bug in header

This PR adds all of the HTML we need for the prework study guide application.
And also, some Nier Automata GIFS.


fix: adding Hardhat Dockerfile in GitHub Workflow

Fixes #692
What

Added a hardhat step to the GitHub workflow to build and push a Docker image for the Hardhat service.
Configured the step to use the docker-build-and-push-image.yml reusable workflow with appropriate parameters:

docker_build_context: .
dockerfile: docker/Dockerfile.hardhat
dockerhub_repo: yeagerai/simulator-hardhat
dockerhub_username: ${{ vars.DOCKERHUB_USERNAME }}
dockerhub_token: ${{ secrets.DOCKERHUB_TOKEN }}

Why

To address the issue of missing Hardhat Docker images in the registry.
To ensure the Hardhat service is available for CLI and dependent services, aligning it with other Studio services.

Testing done

Verified workflow syntax locally.
Confirmed similar jobs for other services (e.g., jsonrpc, frontend) function as expected using the reusable workflow.

Decisions made

Used the existing reusable workflow for consistency across services.
Chose not to add additional Dockerfile-specific testing in this PR, as the reusable workflow already ensures proper image building.

Checks

[x] I have tested this code.
[x] I have reviewed my own PR.
[x] I have created an issue for this PR.
[x] I have set a descriptive PR title compliant with conventional commits.

Reviewing tips

Focus on the added hardhat step in the workflow and confirm the parameters are correct.
Check the reusable workflow configuration for consistency with other services.

User facing release notes

Added a Hardhat Docker image to the CI/CD workflow. The image is now published to Docker Hub, making it available for use in Studio and CLI-related services.

Studio is the whole product. Local net is the backend which can be used on its own

Studio is the whole product. Local net is the backend which can be used on its own

@cristiam86 so do you think the images should be studio-frontend and then localnetwork-image-name for all the rest?

Studio is the whole product. Local net is the backend which can be used on its own

@cristiam86 so do you think the images should be studio-frontend and then localnetwork-image-name for all the rest?

Makes sense, not sure it should be done on this PR though.

@epsjunior we just merged this PR, which had failing tests. This is no longer allowed unless we manually take a look and discuss the issue that is making the tests fail.
The issue seems to be building the frontend, which was addressed in the last PR. I wonder if this is due to not having the branch updated with main before merging

@epsjunior we just merged this PR, which had failing tests. This is no longer allowed unless we manually take a look and discuss the issue that is making the tests fail. The issue seems to be building the frontend, which was addressed in the last PR. I wonder if this is due to not having the branch updated with main before merging

Ok, got it
And yes, the branch wasn't updated with main, because of that some tests failed


"Run All" builds projects again, even immediately after a build.

Description
When a user has just built their solution to discover tests, upon running a test (or all tests) another build occurs. Why?
Steps to reproduce
Pull any repo with tests - I'm using MiniProfiler right now: https://github.com/MiniProfiler/dotnet

Open MiniProfiler.sln in VS 2017 15.1
Build solution (Ctrl+Shift+B)
Open Test Explorer
Click "Run All"

Expected behavior
The tests run, without performing an additional, unnecessary build.
Actual behavior
All projects with tests and all dependencies are built again.
Environment
VS 2017 15.1 (26403.0)
cc @davkean

@NickCraver test explorer depends on "Build" to provide knowledge of test projects (and test containers - the output binaries that have tests) added/removed/updated. It expects "Build" to be a no-op if the solution was just built. My understanding is https://github.com/dotnet/project-system/issues/62 is making "Build" do a full solution build again.
Will this be good idea to let the user decide if they want to "just" run or always use the latest binaries (i.e. Build) for running tests? My 2 cents: when I am coding, this decision point to "build" or "not build" is an interrupt to my flow.

@codito Ideally? There'd be no prompt at all, Visual Studio should just be aware that it just built. But that doesn't work, so at the moment? Yes a prompt would be much better.
I used to think people abandoning the Test Explorer and running all of their stuff from the CLI even when inside Visual Studio working were nuts, but I've just become one of them because it's so much faster. I'm very disappointed the fixes for this are pushed out months now, from 15.1 to 15.3 - so it looks like I'm at the command line for a while now. For large projects, this set of bugs is a huge time sink and regression from VS 2015.
Remember that those of us who helped with project.json and such are forced to change IDEs when updating the project type - we can't just continue using VS 2015. We're stick with the situation of exactly one IDE or the other...so these bugs which greatly affect efficiency are more important than ever.

@NickCraver appreciate your feedback. Sorry for the pain this is causing. I already see that dotnet/project-system#62 is scheduled for next VS update, we will update this issue once it's fixed.
In the context of scaling test explorer for big solutions, there's a proposal at https://github.com/Microsoft/vstest/issues/674. Please do vote and share your thoughts.

@NickCraver Are you saying that VS 2015 was faster in this regard? It didn't even have incremental build support in dotnet build...

@NickCraver Can you do the following and I can quickly see if there's something else running during this second build that shouldn't be:

Open Solution
Tools -> Options -> Project and Solutions -> Build and Run -> MSbuild project build output verbository -> Diagnostic
Build the solution
Clear the Output window -> build category
Build the solution (not rebuild)
Copy that Output, put it in a file and share it out to me

This will tell me if there are targets that are running that shouldn't be slowing down your up-to-date build.

@davkean I'm trying to do this, but I can't get the output window to capture it, it's obviously exceeding the buffer capacity. Is there a way to up it, or redirect the output?
The log I captured is 62MB with an unknown amount missing from the front - happy to email that (1.3MB zipped), or preferably: the above - is there a any way to get the output from the way VS invokes it?

@NickCraver There's no way I know to increase the buffer. Instead of the solution, just build one of the projects.

MiniProfiler was a beast here, but I have the exact same behavior with a far simpler solution: StackExchange.Exceptional (current commit link). When re-running tests (or any build - not rebuild), I get the following behavior:

For some reason, these projects always build:

StackExchange.Exceptional.Tests
StackExchange.Exceptional.Tests.AspNetCore
Samples.Console
Samples.AspNetCore

Maybe noteworthy: some of these have embedded resources in the project and copies, e.g.:
  <ItemGroup>
    <None Update="*.json" CopyToOutputDirectory="Always" />
    <EmbeddedResource Include="*Config.json" />
    <EmbeddedResource Include="..\..\DBScripts\*.sql" />
  </ItemGroup>

...but changing Always to PreserveNewest doesn't have any effect.
A build of everything is too large, but here's a build log of StackExchange.Exceptional.Tests, using the instructions above for building a single project:
StackExchange.Exceptional.Tests.build.log.zip

In case it helps save some time analyzing, here's a structured log as well (entire solution this time since it's compact): StackExchange.Exceptional.Tests.buildstructured.zip

According to a blog post I read recently, an Always copy is designed to cause a rebuild by design.  But the MVCE above shows that even a non-always copy is doing this?
https://blog.oz-code.com/visual-studio-keeps-rebuilding-projects-no-good-reason/

@NickCraver @wpostma I suspect you are running into this: https://github.com/dotnet/project-system/pull/2786.

This fix should be in 15.4 Preview 2.

@davkean I'm afraid I'm already on 15.4 Preview 2 and seeing the same behavior as the logs above, upgraded soon as it came out last week or so :(

If this still occurs when changing Always -> PreserveNewest on 15.4 Preview 2, can you open an issue over on http://github.com/dotnet/project-system? I suspect it's our issue not test.

Turn on Tools -> Options -> Project and Solutions -> .NET Core -> Logging Level -> Verbose
Build StackExchange.Exceptional.Tests once
Clear Output window
Build StackExchange.Exceptional.Tests again
Attach that log. We need the up-to-date log, not build log to figure out what's going on.

This is being tracked external to this repo here:
https://developercommunity.visualstudio.com/content/problem/145920/run-all-builds-projects-again-even-immediately-aft.html


Reducer: reduce double brackets (( )) to simple ones ( ) after final GLF macro replacement

This:
if ( _GLF_BLAH((X)) ) {}
may lead to this at the very end of reduction, when GLF macros are replaced by their expension:
if ((X)) {}
But this double brackets could be reduced to:
if (X) {}

In #471 I have added a test to illustrate this problem.  When the issue is fixed, that test should pass.  (It would be worth adding a few others like it.)

Fixed by #489.


Streamline and parallelize pLS cross cleaning

This PR streamlines the logic for x-cleaning of pLS: Instead of having 3 loops (1 over TCs for x-cleaning vs. T5, 1 over pT3 and 1 over pT5), only one loop is performed (over TCs) to x-clean vs. all objects. This is a natural consequence of using the isDup arrays to mark x-cleaned objects.
Moreover, instead of the serial loops of the previous implementation, this PR parallelizes the loop over TCs.
Timing before change (0b7a492):

Timing after change (50ce8af):

Validation before change (0b7a492):
https://www.classe.cornell.edu/~evourlio/www/SDL_GPU/parallelpLSCrossCleaning/eff_plots__GPU_explicit_cache_0b7a492_PU200_beforeParallelpLSCrossCleaning/
Validation after change (50ce8af):
https://www.classe.cornell.edu/~evourlio/www/SDL_GPU/parallelpLSCrossCleaning/eff_plots__GPU_explicit_cache_50ce8af_PU200_afterParallelpLSCrossCleaning/

PR rebased (after other recent PRs) and retested (updated description).


How to get errors

I want to catch certain errors like duplicate key value violates unique constraint and I am not sure how this error would look from Objection.js. What class are the DB errors?

Objection doesn't touch the db errors. It simply passes through anything that knex throws (which passes through anything the db clients throw). So basically you have to consult the db client docs to see what kind of objects get thrown.
This is something I would like to change though. See this issue


[RSDK 4187] Custom Base Example

This PR adds a custom base model within the 'examples' subdirectory as a guide/template for users to follow. The new additions are loosely based on the file 'my_base.py' found at the bottom of this webpage, and also the parallel example in the Go SDK here.
This is a draft for now due to a local bug that I've been unable to fix.. stay tuned!

@njooma @cheukt pulling this out of draft status! Everything was locally tested using a local viam-server instance and the script found in viam-python-sdk/examples/complex_modules/client.py.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Incompatibility of grape 1.5.3 with Rails 6.1

Rails version : <IP_ADDRESS>
Grape version: 1.5.3, (also tried with version 1.3.3)
Following is the error whenever a grape api endpoint is hit
12:08:45 web.1         | ArgumentError (missing keyword: :header):
12:08:45 web.1         |
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/request_id.rb:18:in `initialize'
12:08:45 web.1         | rack (2.2.3) lib/rack/builder.rb:158:in `new'
12:08:45 web.1         | rack (2.2.3) lib/rack/builder.rb:158:in `block in use'
12:08:45 web.1         | rack (2.2.3) lib/rack/builder.rb:235:in `block in to_app'
12:08:45 web.1         | rack (2.2.3) lib/rack/builder.rb:235:in `each'
12:08:45 web.1         | rack (2.2.3) lib/rack/builder.rb:235:in `inject'
12:08:45 web.1         | rack (2.2.3) lib/rack/builder.rb:235:in `to_app'
12:08:45 web.1         | grape (1.5.3) lib/grape/endpoint.rb:323:in `build_stack'
12:08:45 web.1         | grape (1.5.3) lib/grape/endpoint.rb:355:in `block in lazy_initialize!'
12:08:45 web.1         | grape (1.5.3) lib/grape/endpoint.rb:351:in `synchronize'
12:08:45 web.1         | grape (1.5.3) lib/grape/endpoint.rb:351:in `lazy_initialize!'
12:08:45 web.1         | grape (1.5.3) lib/grape/endpoint.rb:224:in `call'
12:08:45 web.1         | grape (1.5.3) lib/grape/router/route.rb:58:in `exec'
12:08:45 web.1         | grape (1.5.3) lib/grape/router.rb:116:in `process_route'
12:08:45 web.1         | grape (1.5.3) lib/grape/router.rb:72:in `block in identity'
12:08:45 web.1         | grape (1.5.3) lib/grape/router.rb:91:in `transaction'
12:08:45 web.1         | grape (1.5.3) lib/grape/router.rb:70:in `identity'
12:08:45 web.1         | grape (1.5.3) lib/grape/router.rb:55:in `block in call'
12:08:45 web.1         | grape (1.5.3) lib/grape/router.rb:132:in `with_optimization'
12:08:45 web.1         | grape (1.5.3) lib/grape/router.rb:54:in `call'
12:08:45 web.1         | grape (1.5.3) lib/grape/api/instance.rb:167:in `call'
12:08:45 web.1         | grape (1.5.3) lib/grape/api/instance.rb:71:in `call!'
12:08:45 web.1         | grape (1.5.3) lib/grape/api/instance.rb:66:in `call'
12:08:45 web.1         | grape (1.5.3) lib/grape/api.rb:68:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/mapper.rb:20:in `block in <class:Constraints>'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/mapper.rb:49:in `serve'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:50:in `block in serve'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:32:in `each'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:32:in `serve'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:842:in `call'
12:08:45 web.1         | rack (2.2.3) lib/rack/tempfile_reaper.rb:15:in `call'
12:08:45 web.1         | rack (2.2.3) lib/rack/etag.rb:27:in `call'
12:08:45 web.1         | rack (2.2.3) lib/rack/conditional_get.rb:27:in `call'
12:08:45 web.1         | rack (2.2.3) lib/rack/head.rb:12:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/http/permissions_policy.rb:22:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/http/content_security_policy.rb:18:in `call'
12:08:45 web.1         | rack (2.2.3) lib/rack/session/abstract/id.rb:266:in `context'
12:08:45 web.1         | rack (2.2.3) lib/rack/session/abstract/id.rb:260:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/cookies.rb:689:in `call'
12:08:45 web.1         | activerecord (<IP_ADDRESS>) lib/active_record/migration.rb:601:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
12:08:45 web.1         | activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:98:in `run_callbacks'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/callbacks.rb:26:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/executor.rb:14:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/actionable_exceptions.rb:18:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/debug_exceptions.rb:29:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
12:08:45 web.1         | railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:37:in `call_app'
12:08:45 web.1         | railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:26:in `block in call'
12:08:45 web.1         | activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:99:in `block in tagged'
12:08:45 web.1         | activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:37:in `tagged'
12:08:45 web.1         | activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:99:in `tagged'
12:08:45 web.1         | railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:26:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/request_id.rb:26:in `call'
12:08:45 web.1         | rack (2.2.3) lib/rack/method_override.rb:24:in `call'
12:08:45 web.1         | rack (2.2.3) lib/rack/runtime.rb:22:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/executor.rb:14:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/static.rb:24:in `call'
12:08:45 web.1         | rack (2.2.3) lib/rack/sendfile.rb:110:in `call'
12:08:45 web.1         | actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/host_authorization.rb:119:in `call'
12:08:45 web.1         | railties (<IP_ADDRESS>) lib/rails/engine.rb:539:in `call'
12:08:45 web.1         | passenger (5.3.2) src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:97:in `process_request'
12:08:45 web.1         | passenger (5.3.2) src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:149:in `accept_and_process_next_request'
12:08:45 web.1         | passenger (5.3.2) src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:110:in `main_loop'
12:08:45 web.1         | passenger (5.3.2) src/ruby_supportlib/phusion_passenger/request_handler.rb:415:in `block (3 levels) in start_threads'
12:08:45 web.1         | passenger (5.3.2) src/ruby_supportlib/phusion_passenger/utils.rb:113:in `block in create_thread_and_abort_on_exception'

Any hints what could be going wrong here?

I don't remember seeing this one. We do have integration tests for Rails 6.1 (see https://github.com/ruby-grape/grape/blob/master/Appraisals), so this is something more specific to your application. See what's being initialized in lib/action_dispatch/middleware/request_id.rb? I usually just do something as dumb as bundle show action_dispatch and just add some puts above that call locally :)

@dblock, Thanks for the hints. I realised what was going wrong. We were using ActionDispatch::RequestId middleware in the api.rb file. So, one of the statements in our api.rb is :
use ActionDispatch::RequestId

Apparently, the middleware has changed its implementation from rails 6.0 to 6.1 and expects you to also pass in header name that will be used to add request id. So, the statement in the api.rb file needs to be changed to something like:
use ActionDispatch::RequestId, header: "X-Request-Id"

I think we missed this out and ended up opening this ticket.
So, this is not a bug on Grape, we were using ActionDispatch middleware incorrectly.


Move decapitate to garrosh. Up mana cost, reduce cooldown

Give garrosh ultimate to saurfang
Give saurfang ultimate to grom
Rework bladestorm to last a short while and do more damage

Give field of blood ultimate to garrosh

Nerf Execute values on heroes


Add meilisearch for docs search

Added search functionality.
Two api keys are exposed, with limited scope.
The search api, which is normal and required for basic search functionality.
An additional key allows for getting the list of indexes. This allows for checking if an index matching the release exists.
If no index exists, the default doc search is used.
Known issues: as a limit to the number of indexes/releases will eventually present itself, older indexes will need to be deleted. As Sphinx is static, this presents a bit of an issue. However, once version selection is implemented, older versions will be rebuilt, meaning older releases with deleted search indexes will fallback to using the default Sphinx search.
Additionally, local/PR CI builds will use a "dev" index. This will eventually be configured to use the most recent commit, however for now the index was created by scrapping "latest".
Note this commit does NOT cover the creation of indexes, which at this time will be handled manually, and requires private keys.
QA: Checked rendered output, and tested a number of cases by modifying the variables used.

Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness

[x] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
DOC SEARCH
Checklist

[x] Avoid changing any header associated with a link/reference.
[x] Step through instructions (or ask someone to do so).
[x] Match tone and style of page/section.
[x] Run make linkcheck.
[x] View HTML in a browser to check rendering.
[x] Use semantic newlines.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Comments
Additional styling and configuration will be added in the future.
I also do not do Python, so code in conf.py is not optimized or pretty in anyway.

Docs for 527816b49c21c601dbc3f3efffea2996d00e9cff are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2695/docs/artifacts/html/index.html

How would meilisearch work in development mode locally? Since the docs are public, I suppose we want to limit its use only to us, not to external contributors.
Can it be disabled and default to old-search for local dev?
dev currently just uses results from "latest" rather than actual results. And yes, I will include a comment in conf.py for switching it to use default.

Docs for 9bba9ee8d268adc8fc5b05ca81f6217188b2a913 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2698/docs/artifacts/html/index.html


Rework options

This makes the name column UNIQUE so that you can't have 2 rows with the same name and seeds all options whenever the plugin is activated or the options page is viewed. This way people updating their builds can install the new options easily. The seeding uses INSERT IGNORE, so existing options will be retained.
Closes #31.

Thanks again @john-shaffer!


Debugger on a website when disable ignore list in first time , the devtools will freeze for seconds or miniutes.

This problem has been exist for a long time.
in this repo,it just freeze for few seconds, but in another repo, it will freeze 1~2 minutes.
And i used devtool's feedback several months ago, and it has no response.
reproduce steps:

Download this repo
归档.zip

execute pnpm install then when it's done execute pnpm run dev

open browser and goto http://localhost:5173 and open devtools

Open devtools' setting and Disable Ignore List

5. refresh page and there will have a error like this

6. click warning.js and add a breakpoint on this line
7. re-open devtools and refresh page immediately. The DevTool will hang for seconds.

Thank you for filing. Will flag this on our team's backlog.

Any progress, or is this just a place to collect questions without actually solving anything?

No progress on this particular issue to report at this time unfortunately. Rest assured that our team is very busy with many other things. Getting to this issue, as with any other issue, is unfortunately subject to hard prioritization decisions.


[Bug]: After upgrade to 1.1

Adapter version
1.1
JS-Controller version
5.0.11
Node version
18.17.0
Operating System type
Docker
Operating system version
buanet/iobroker:latest-v8
Describe the bug
in iobroker log i receive follow error:

eusec.0
2023-08-09 06:58:07.935
error
Generic Error [{}]

eusec.0
2023-08-09 06:58:07.932
error
JSON parse error [{"data":"\u0006�f�\r�Ht�T�\u0006-�\u00075�a��Y\n�>\u001fb��%~d|��U+��\u001a!��R\u0005z������533�\u0016I�:f�\u0013���Z��\u0014\u0002\u0015�a��I�0�ˡA�\u0016o7n�у\u000e\u001f�FS\u000e\u0015ω\u0017M;r�cü�;yvɤ�%��8��W�SA�Q{n��eh�\u0001b\u0018;�aP�F�~\u0010%�\"v\r\u001a���ִ�Y��rya��C�N�8�t��>�𶄶���搫\u0012��'!��څ�<�JR\u001c\u0015�\u0010(\u0010��o-ў0\ng�@����tfW��$�s̋ٙ%�5���0�%T��3t1��f��k��7(�YY���","error":{}}]

To reproduce

Go to '...'
Click on '...'
Scroll down to '....'
See error

Screenshots & Logfiles
No response
Additional context
No response

There should be another log line here that tells me which parameter is causing this error.
Unfortunately, it happens that the values received from the cloud are not always JSON compliant.

Seems to be solved with 1.1.1. Thnx

Can confirm


Mweb – Split Bill – Emoji doesn't open on click

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

Action Performed:

Click on the plus (+) sign to initiate the "Split Bill" process.
Navigate to the "Split Bill" section.
Enter the desired amount.
Click on "Next."
Select the members involved in the bill splitting.
Click on "Next."
Proceed to the Owe chat conversation with User B, with whom the bill has been split, and exchange some messages with emojis.
Return to the chat conversation with User A, who initiated the bill splitting, and exchange some messages with emojis.
Notice that after a few messages in User A's chat, the emoji stops opening when clicked.

Expected Result:
The emoji should open and display properly in all cases.
Actual Result:
In the case of split bills, the emoji is not opening when clicked.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

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

[ ] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number:
Reproducible in staging?: Needs reproduction (applause can't reproduce)
Reproducible in production?: needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/58b913bd-0583-4fa1-a08a-cf8ed40fa2cc
Expensify/Expensify Issue URL:
Issue reported by: @usmantariq96
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686548484252989
View all open jobs on GitHub

Reviewing today!

Cannot reproduce @usmantariq96 can you confirm if this is occurring on the latest build?

closing, feel free to reopen if you can repro @usmantariq96 cc @kavimuru

@dylanexpensify thanks for consideration, now it is not reproducable.


Some definitions show up as curated even though they are not

The following definitions show up as curated with undeclared license even though these specific versions aren't curated. Is there a problem with Curated badge?
https://clearlydefined.io/definitions/nuget/nuget/-/System.Net.Http.WinHttpHandler/4.5.0
https://clearlydefined.io/definitions/nuget/nuget/-/Bond.Runtime.CSharp/8.0.0
https://github.com/clearlydefined/curated-data/blob/master/curations/nuget/nuget/-/System.Net.Http.WinHttpHandler.yaml
https://github.com/clearlydefined/curated-data/blob/master/curations/nuget/nuget/-/Bond.Runtime.CSharp.yaml

The Curated badge is shown if the definition has at least one merged contribution.
In these cases, I see multiple merged contributions so it looks to be fine from my point of view.
Maybe the condition should check for something else?

At this point a specific version must be matched for a curation to be applied. In the future this logic may change if and when it is decided to use apply curations from other versions.
It should be checked whether the version matches in the curations list. For example see curations array in
https://api.clearlydefined.io/curations/nuget/nuget/-/System.Net.Http.WinHttpHandler/4.5.0?expand=prs

I'm wondering why that endpoint is returning contributions from other versions since the needed version has been specified in the request.
Thoughts?

I made some tests over the API results:
If I call https://api.clearlydefined.io/curations/nuget/nuget/-/System.Net.Http.WinHttpHandler/?expand=prs (just removing the version from the request) I get the same results that I get by specifying the version.
If I call https://api.clearlydefined.io/curations/nuget/nuget/-/System.Net.Http.WinHttpHandler I get the same results, again.
But if I call https://api.clearlydefined.io/curations/nuget/nuget/-/System.Net.Http.WinHttpHandler/4.5.0 without expand=prs, then the API returns a Not Found message.
I'm not sure about why this is happening, since in the curations array actually is present a curation over the 4.5.0 version, which ends to be considered a curated component.

4.5.0 version is present for other components, not this one. Does it make sense?

Sorry, I missed it.
I still don't get why the endpoint  https://api.clearlydefined.io/curations/nuget/nuget/-/System.Net.Http.WinHttpHandler/4.5.0?expand=prs returns a list of all the curations from different versions if a specific version has been requested.

Any clues from the code? @ignacionr Do you know if that's expected?

@geneh I think that the best option, for now, is to add a revision param into the contributions objects, in order to allow the client to filter the values.

I've tried to come up with a solution to the client, but I think that the best solution is to filter the results with contents that are related to the requested version.
Otherwise, the second option is to search into all the Prs retrieved, and match the same coordinates / revision.
Thoughts?


Install command is missing.

I'm unsure as to why, but does anybody know why the install/uninstall commands are simply missing?
pyenv 1.0.4-11-ga73d90b
Usage: pyenv <command> [<args>]

Some useful pyenv commands are:
   commands    List all available pyenv commands
   local       Set or show the local application-specific Python version
   global      Set or show the global Python version
   shell       Set or show the shell-specific Python version
   rehash      Rehash pyenv shims (run this after installing executables)
   version     Show the current Python version and its origin
   versions    List all Python versions available to pyenv
   which       Display the full path to an executable
   whence      List all Python versions that contain the given executable

See `pyenv help <command>' for information on a specific command.
For full documentation, see: https://github.com/yyuu/pyenv#readme

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40037965-install-command-is-missing?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github).

install is a command from python-build plugin. It may not be available if your pyenv installation is not configured properly into your shell. Typically you need to add 'eval "$(pyenv init -)"' in your shell's initialization script.

Thanks, that at least gives me a starting point.

To help others, I had this issue and found that in the .bashrc rather than as documented I need to add 'export' to the PYENV_ROOT and PATH variable creation.
e.g.
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"

if command -v pyenv 1 > /dev/null 2>&1; then
  eval "$(pyenv init -)"
fi

I think this is something to do with the way the login shell is being created.

To help users in the future who might have this problem, regardless of shell:
I was receiving:
taylor@taylor-Precision-M6600  ~  pyenv install 3.5.3                                                                 ✔  8229  09:05:09
pyenv: no such command `install'

...after adding the required lines to my .zshrc file one-at-a-time (copying them from some tutorial or w/e), and then re-initialized my shell
What caused this?
Turns out I had not copy-pasted the entirety of the required line each time, leaving off the final " of each. After leaving this file malformed in this way I was still able to run source ~/.zshrc with no complaints from the shell. This lack of complaint from the shell upon re-initialization left me dumbfounded for a solution to this for some time.
TL;DR, by Chance?
The error pyenv: no such command 'install' can be caused (or was in my case, at least) by malformed Path export commands in your shell's configuration. Checking this is minimally invasive. If you copy the except posted by @the-moog (above) and use that to replace the malformed lines you might find your solution.


decouple LetsEncrypt custom-domain broker and cdn broker provisioning

The cdn broker and custom domain broker share a lot of code, but the code is managed separately. The way the brokers are written mashes the AWS interactions and LetsEncrypt interactions into the same functions, objects, and tables. By separating the LetsEncrypt logic from the AWS logic, we can make this more maintainable, and maybe make it easier to bring HTTP-01 challenges back

obsoleted by new broker


Is it possible add a global @SingleUse for spring boot application?

Hope add global definition for spring-boot application. For example, if I add annotation at spring boot launch class, will guard all task execute once in nodes:
@SpringBootAppliction
@EnableScheduling
@SingleUse

Thanks for any reply

Hi, thanks for feedback and sorry for the delay. If I understand you correctly, you want to add one annotation which would automatically put lock on all scheduled tasks?  It is quite easy to implement but I am afraid that it's a bit dangerous. We need a name for each lock and the only way to generated it automatically is to use method signature - ClassName.methodName(). In my opinion it's quite fragile since you can rename the class or the method and when you deploy the change only to part of the cluster, the task will be executed twice. That's why I hesitate to add it.

17:42:19.732 1796972 [ThreadPoolTaskScheduler-1] ERROR o.s.s.s.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task.
net.javacrumbs.shedlock.support.LockException: Can not remove node
at net.javacrumbs.shedlock.provider.redis.spring.RedisLockProvider$RedisLock.unlock(RedisLockProvider.java:107)
at net.javacrumbs.shedlock.core.DefaultLockingTaskExecutor.executeWithLock(DefaultLockingTaskExecutor.java:44)
at net.javacrumbs.shedlock.core.DefaultLockManager.executeWithLock(DefaultLockManager.java:51)
at net.javacrumbs.shedlock.core.LockableRunnable.run(LockableRunnable.java:35)
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
at java.base/java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:305)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: org.springframework.data.redis.RedisConnectionFailureException: Cannot get Jedis connection; nested exception is redis.clients.jedis.exceptions.JedisConnectionException: java.net.ConnectException: Address already in use (connect failed)
at org.springframework.data.redis.connection.jedis.JedisConnectionFactory.fetchJedisConnector(JedisConnectionFactory.java:286)
at org.springframework.data.redis.connection.jedis.JedisConnectionFactory.getConnection(JedisConnectionFactory.java:469)
at net.javacrumbs.shedlock.provider.redis.spring.RedisLockProvider$RedisLock.unlock(RedisLockProvider.java:104)
... 11 common frames omitted
Caused by: redis.clients.jedis.exceptions.JedisConnectionException: java.net.ConnectException: Address already in use (connect failed)
at redis.clients.jedis.Connection.connect(Connection.java:207)
at redis.clients.jedis.BinaryClient.connect(BinaryClient.java:93)
at redis.clients.jedis.BinaryJedis.connect(BinaryJedis.java:1767)
at org.springframework.data.redis.connection.jedis.JedisConnectionFactory.fetchJedisConnector(JedisConnectionFactory.java:281)
... 13 common frames omitted
Caused by: java.net.ConnectException: Address already in use (connect failed)
at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:400)
at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:243)
at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:225)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:402)
at java.base/java.net.Socket.connect(Socket.java:591)
at redis.clients.jedis.Connection.connect(Connection.java:184)
... 16 common frames omitted

Hi, thanks for you reply. As you said, you use a method name as lock signature.  Some time we deploy for change part of the cluster in AB test, I think job or task as AB test in application is not suitable. So, if you check some method have specific annotation you automatically disable global annotation. Of course, it's just my opinion.

@ivaylo5ev This would mean only one task would run, which isn't the desired behavior no?
@zhengfc Maybe as a fallback, check if the class has a Component annotation and a name set? That should be unique enough.

@zHaytam , yes it would and this is NOT the desired behaviour indeed. I have misread / misunderstood the initial request, so ignore my comment above.


Adds disabling Edge's desktop search bar

Creates entry WebWidgetAllowed as 0 in regedit: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge (Restart required for changes to apply)

awesome. thanks


How to deploy on CI host?

I can use mrsk depoy on local machine, and deploy success .but I also want to use mrsk on
a CI host,who can give me some suggestions.Thanks very much.

Checkout https://github.com/mrsked/mrsk/discussions/188


API Improvements

Moved encoder/decoder related stuff to the Dotx64Dbg.Disassembly namespace (name might not be ideal, but I think it's reasonably discoverable)
Added some aliases to improve discoverability

What is the reason to move it to a different namespace?

Mostly because Label is colliding with the Label concept inside x64dbg. It also makes it more difficult to discover the API. Now you can write DotX64Dbg.Disassembly. and quickly see the related classes.
The only downside seems to be that you have to add a new using statement in existing scripts.


Nothing happens, playlist link pasted, program doesn't recognize any input

I paste any link, would it be a public playlist or my own private playlist, and would it be a Search tab or Bulk Download, it does nothing. Search tab has all buttons unavailable, and Bulk Download does nothing after pressing a button. Program is ran as administrator. Pasting single video in search after couple of minutes allows to download, but playlists are unavailable after an hour at least, would it be a share link or browser address link.

I don't fully understand, you're saying that it works, and after a couple of hours stops working? or, its not working but after a couple of hours it starts working?

Single video link enables download button occasionally (not always) after few minutes passed, but only in Search tab. Playlist links never available for download, even after waiting for an hour, in all tabs.

I have the same problem - nothing happens when i paste playlist link ;(

Buttons aren't active

I don't know if I will be able to solve it, for now try using alternative downloaders like youtube-dlp


${prefix}/lib/cmake//Config.cmake not detected

OMPL moved their cmake configuration files to ${prefix}/lib/cmake/ompl/omplConfig.cmake in their first melodic release, but catkin does not find them there. This is a blocker for a MoveIt release to melodic at the moment (see here).
@mamoll said he is willing to change it again, but the problem will likely pop up again for another library at some point.
https://cmake.org/cmake/help/v3.11/command/find_package.html lists a number of locations where cmake configurations are looked up by default. Citing
<prefix>/(lib/<arch>|lib|share)/cmake/<name>*/
<prefix>/(lib/<arch>|lib|share)/<name>*/
<prefix>/(lib/<arch>|lib|share)/<name>*/(cmake|CMake)/
<prefix>/<name>*/(lib/<arch>|lib|share)/cmake/<name>*/
<prefix>/<name>*/(lib/<arch>|lib|share)/<name>*/
<prefix>/<name>*/(lib/<arch>|lib|share)/<name>*/(cmake|CMake)/

catkin does not support all of them.
Why not?

@dirk-thomas, this is where the paths are hard-coded:
https://github.com/ros/catkin/blob/kinetic-devel/cmake/catkinConfig.cmake.in#L68-L69

Oh right, since all passed COMPONENTS are expected to be catkin packages it is only checking in this locations since that is where catkin_package installs the generated CMake config files.
There are multiple options:

Change the location of the CMake config file to match that path. That will make it work right away.
Uses could use find_package(ompl) instead of using find_package(catkin COMPONENTS ompl).
catkin could be modified to also consider those locations. The first "downside" of this is that it can the be used to find arbitrary CMake packages which might not adhere to the conventions used in catkin packages (for all the expected variable names). The second one is that whatever change would be proposed would need to go through some testing and will not be ready to be release in time for the melodic release next week.

Therefore I would suggest proceeding with the first option.

Therefore I would suggest proceeding with the first option.

Yes, that is what I am planning to do for OMPL, since I don't have a strong preference one way or the other. @v4hn's point is that the problem will likely pop up again for other packages.

Uses could use find_package(ompl) instead of using find_package(catkin COMPONENTS ompl).

I believe this is the correct way to do it either way and personally if that works I don't see a bug in catkin.
@mamoll As far as I can see we don't use COMPONENTS ompl anywhere, but we use find_package(OMPL REQUIRED).
Could this be an artifact because we don't use find_package(ompl REQUIRED) instead?

Could this be an artifact because we don't use find_package(ompl REQUIRED) instead?

Since your CMake config file is named omplConfig.cmake the name is case sensitive. If you would like it to be case insensitive it would need to be ompl-config.cmake as far as I recall.

@v4hn, yes, case matters. You should use find_package(ompl REQUIRED). There is also an extended discussion about find_package(catkin COMPONENT ompl) vs. find_package(ompl) here: https://github.com/ros-planning/moveit/issues/169

Ok, I consider this problem resolved for MoveIt after we changed to find_package(ompl)
One thing I still wonder about is whether there is a way to avoid this kind of confusion altogether by not generating the cmake config for OMPL / any third party module in the first place if the maintainers don't want them and distribute their own configs. The config is generated through bloom I guess?
@dirk-thomas Would be great if you could comment on that point, afterwards feel free to close this issue.

The CMake config file is generated by the catkin_package call. If you want to have one for your package you call it, if you don't you don't call the function. Then the package should probably have a build type of cmake instead of catkin.

In the case of ompl, it generates its own cmake config file using standard cmake macros:
if (NOT ${CMAKE_VERSION} VERSION_LESS 2.8.8)
    include(CMakePackageConfigHelpers)
    set(INCLUDE_INSTALL_DIR ${CMAKE_INSTALL_INCLUDEDIR})
    set(LIB_INSTALL_DIR ${CMAKE_INSTALL_LIBDIR})
    configure_package_config_file(omplConfig.cmake.in
        ${CMAKE_CURRENT_BINARY_DIR}/omplConfig.cmake
        INSTALL_DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/ompl/cmake
        PATH_VARS INCLUDE_INSTALL_DIR LIB_INSTALL_DIR
        NO_CHECK_REQUIRED_COMPONENTS_MACRO)
    write_basic_package_version_file(
        ${CMAKE_CURRENT_BINARY_DIR}/omplConfigVersion.cmake
        VERSION ${OMPL_VERSION}
        COMPATIBILITY SameMajorVersion)
    install(FILES ${CMAKE_CURRENT_BINARY_DIR}/omplConfig.cmake
        ${CMAKE_CURRENT_BINARY_DIR}/omplConfigVersion.cmake
        DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/ompl/cmake
        COMPONENT ompl)
endif()

I will go ahead and close this since there seems to be nothing to be done within catkin. Please feel free to continue commenting.


fix virustotal send file to analysis

There is option "scan" for VirusTotal in current version of Cuckoo, but it does not work, always return "No antivirus signatures available." if file is new.
These changes fix it, returning url for analysis

Did anyone test this PR? Looks good to me!

Actually, yeah, that sounds about right. Merging it. Thanks for the contribution!


packaging_tools.change_log doesn't work correctly

I am creating this issue for myself.
While working with datafactory pr, I have noticed that several models were added, and two models were removed and this change didn't appear in generated changelog.
I have checked json files that were compared, and they were generated correctly.
I will include them here.

reports.zip