[WIP] Add templating of Google credentials file

Google Cloud does things differently in that you must have a credentials file to be able to authenticate with their API. This causes a problem as while we can provide a file to use for authentication, we want to ensure that when people run the Jenkins job they are passing in some form of authentication, because otherwise they could potentially cause serious impact in deployment of DNS.
This looks to template this credentials file, in which we can store most of the secrets of the file in encrypted hiera, but also prompt for a couple of parts of the file in the Jenkins job itself, and pass these in as environment variables. These secrets can be stored in our password store to use.

We've discussed this PR and we're going to change the approach to use a group and limit the job to only admin users.


[Eco Pass KIT v2.0.0] Update main readme

What needs to be done?

[ ] Add logos to the main readme
[ ] Add Documentation of Interest (in reference implementation)
[ ] Add readme headers like the reference implementation

@matbmoser review done in PR fpr #26


GDDP INTERGRATION WHERE???

why can't you change the difficulty for gddp intergration? like beginner demon, etc?

Because I am busy with other stuff. This is planned

Added in v1.4.0


Update repository location in docs

Hi! I'm starting to use this library, and I've found a few things that I can fix. Here's the first.

Thanks, this is really handy. Also what is this pip-selfcheck.json file?

Not sure, it was generated after I did make test or make docs. Seems to be related to the virtualenv.


feat: support attached shadow dom elements

PR Checklist
Please review the guidelines for contributing to this repository.

[X] I am requesting to pull a topic/feature/bugfix branch (right side). In other words, not main.
[X] I have run yarn test against my changes and tests pass.
[X] I have added tests to prove my fix is effective or my feature works. This can be done in the form of unit tests in test/unit/ or a new or altered demo in demo/.
[X] I have added or edited necessary types and generated documentation (yarn docs), or no docs changes are needed.

Description

Updates the isAttached helper to handle shadow dom elements. If the passed element's root node is a ShadowRoot, it sets parent to the ShadowRoot's host and subsequently checks if the host is attached; otherwise it falls back to the pre-existing functionality.
With additional testing, I found that the prior change was not sufficient to handle multiple nested shadow dom elements. The logic has been updated to manually traverse through the dom (handling both regular & shadow nodes) to ensure that any nesting is properly accounted for.
Fixes: #536

Hey @timmywil, just wanted to ping again to see if you're able to review and merge or provide feedback. Thanks!

@timmywil, can you please take a look at this and merge if acceptable (or provide guidance if you have any issues).  I'd rather not permanently fork the project for this, but it's been quite a while with no movement.

@timmywil, can you please take a look at this and merge if acceptable (or provide guidance if you have any issues). I'd rather not permanently fork the project for this, but it's been quite a while with no movement.

@timmywil any chance of this being merged? It all works for me. Thanks!

Yes, this looks good. Sorry I haven't gotten to it sooner.

Thanks!!
A great library -- it just works and works well, compared to some others out there...

Hey @timmywil, any chance we could get a new release with this feature? It's been over two years since the last release and almost two years since this PR was merged.  I'd love to go back to using the base library in my projects instead of my fork.


@JuliaRegistrator register

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/103677
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.8 -m "<description of version>" e53f73af0c0dd6ee26f470d7b8b5f07118adab0e
git push origin v0.4.8

Also, note the warning: This looks like a new registration that registers version 0.4.8.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

done


Layer2 dev

@Noorts: this points to our L2 development backend and is available at https://volcano.onramper.dev
Also check out https://github.com/onramper/widget/pull/201.

Hey @nyshthefantastic! Could we close this PR?


Ruby: Fix ToC links

Updates GoogleCloudPlatform/google-cloud-ruby#1181

Codecov Report

Merging #1566 into master will decrease coverage by <.01%.
The diff coverage is 87.5%.

@@             Coverage Diff              @@
##             master    #1566      +/-   ##
============================================
- Coverage     87.03%   87.02%   -0.01%
  Complexity     4207     4207
============================================
  Files           408      408
  Lines         16882    16883       +1
  Branches       1834     1835       +1
============================================
  Hits          14693    14693
  Misses         1697     1697
- Partials        492      493       +1

Impacted Files
Coverage Δ
Complexity Δ

...ansformer/ruby/RubyGapicSurfaceDocTransformer.java
93.44% <100%> (-0.11%)
13 <0> (ø)

...ansformer/ruby/RubyPackageMetadataTransformer.java
97.87% <83.33%> (-0.69%)
25 <2> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fdf0648...2c90f4d. Read the comment docs.


git.rancher.io being down shouldnt cause server to not start

Rancher versions:
rancher/server: preview
Docker version: (docker version,docker info preferred)
Docker version 17.03.2-ce, build f5ec1e2
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
OVH Baremetal
Steps to Reproduce:
Run rancher/server:preview while https://git.rancher.io/community-catalog.git is unavailable
Results:
Rancher Server wont start

Loops while logging this:
time="2017-10-14T00:23:32Z" level=error msg="Catalog refresh failed for community (https://git.rancher.io/community-catalog.git): Remote commit check failed: Repo [https://git.rancher.io/community-catalog.git] is not accessible: Get https://git.rancher.io/repos/community-catalog/commits/v2.0-release: dial tcp: lookup git.rancher.io on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:46543-><IP_ADDRESS>:53: i/o timeout"
time="2017-10-14T00:23:32Z" level=error msg="Catalog refresh failed for library (https://git.rancher.io/rancher-catalog.git): Remote commit check failed: Repo [https://git.rancher.io/rancher-catalog.git] is not accessible: Get https://git.rancher.io/repos/rancher-catalog/commits/v2.0-release: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"

Did you actually try to go to it?  The catalog service and various other things are separate processes, the server is already up and listening on 8080 before catalog service is even started.
The server is up when  Startup Succeeded, Listening on port 8081 is printed (8080 is a proxy that routes requests around, so the actual server is on 8081).

I did, but i might have been having some other DNS issues at the time.

Can close


Evaluate parallelization

The current implementation of EqPolynomial::evaluate is not parallelized. Using rayon's into_par_iter reduces the function's performance.
The following time benchmarks show the performance of the function with and without parallelization:

In my machine, a speedup of roughly 4x is achieved when parallelizing the function, which is already quite significant.

What's up with the jumps in running time in the parallel case? E.g. it's non-increasing between 2^5 and 2^6

The speed up seems great! As Marcin says, there are some steps with unexpected time jumps.  A possible explanation is some degree of parallelisation only activating if some runtime threshold is reached (just guessing).
Another thing to take into account: when benchmarking such low-work code as the first few entries of the table, it is best to run that code many times (say N) inside a loop, and only measure the elapsed time before and after the loop (not inside each iteration), then divide that total time by N. Sometimes that's the only way to get reasonably accurate measurements for e.g. code in the order of a few microseconds. Even for the higher-cost entries further down the table, it is also good to use that procedure (perhaps reducing N, since individual iteration will be more consistent time-wise anyway).
Two questions:

Was the above table produced with that kind of total-then-divide averaging method? Otherwise that would be another possible reason for the unexpected time jumps.
Since the i in the loop is only used to index two arrays, perhaps you can have a look at this rayon function and zip the two arrays. I'm curious if the runtime will change at all (and in which direction), likely not. But in any case the code would be a bit cleaner in my opinion. Also note that the current code indexes each array at the same position twice for each iteration, which doesn't look great (although the compiler likely optimises that away).

The measurements are produced in a single round; I assumed these results already show a clear speedup for large input instances. I can run multiple rounds to have more significant results though.

@Antonio95 you are right, It definitely makes sense to zip the arrays for readability.

New benchmarks with respect to the original implementation, computed using criterion:
     Running benches/bench.rs (target/release/deps/bench-507167fb87136d31)
[...]
evaluate_incremental/2^1
                        time:   [11.974 µs 11.997 µs 12.021 µs]
                        change: [+3566.1% +3600.1% +3631.2%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 10 outliers among 100 measurements (10.00%)
  2 (2.00%) low mild
  5 (5.00%) high mild
  3 (3.00%) high severe
evaluate_incremental/2^3
                        time:   [15.089 µs 15.245 µs 15.372 µs]
                        change: [+1233.8% +1274.4% +1313.5%] (p = 0.00 < 0.05)
                        Performance has regressed.
evaluate_incremental/2^5
                        time:   [18.728 µs 18.848 µs 18.979 µs]
                        change: [+348.19% +360.39% +372.67%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 5 outliers among 100 measurements (5.00%)
  1 (1.00%) low mild
  2 (2.00%) high mild
  2 (2.00%) high severe
evaluate_incremental/2^7
                        time:   [28.957 µs 29.187 µs 29.460 µs]
                        change: [+99.432% +103.98% +108.28%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 2 outliers among 100 measurements (2.00%)
  2 (2.00%) high mild
evaluate_incremental/2^9
                        time:   [51.231 µs 51.524 µs 51.848 µs]
                        change: [-18.139% -16.317% -14.388%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 5 outliers among 100 measurements (5.00%)
  3 (3.00%) high mild
  2 (2.00%) high severe
evaluate_incremental/2^11
                        time:   [111.06 µs 112.03 µs 113.14 µs]
                        change: [-52.575% -51.008% -48.892%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 9 outliers among 100 measurements (9.00%)
  6 (6.00%) high mild
  3 (3.00%) high severe
evaluate_incremental/2^13
                        time:   [315.19 µs 316.68 µs 318.05 µs]
                        change: [-66.222% -65.011% -63.865%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 13 outliers among 100 measurements (13.00%)
  8 (8.00%) low mild
  3 (3.00%) high mild
  2 (2.00%) high severe
evaluate_incremental/2^15
                        time:   [927.52 µs 935.10 µs 943.68 µs]
                        change: [-75.439% -74.528% -73.713%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 8 outliers among 100 measurements (8.00%)
  5 (5.00%) high mild
  3 (3.00%) high severe
evaluate_incremental/2^17
                        time:   [3.2199 ms 3.2313 ms 3.2434 ms]
                        change: [-76.511% -76.253% -76.017%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 13 outliers among 100 measurements (13.00%)
  11 (11.00%) high mild
  2 (2.00%) high severe
evaluate_incremental/2^19
                        time:   [13.064 ms 13.172 ms 13.299 ms]
                        change: [-77.693% -77.435% -77.149%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 3 outliers among 100 measurements (3.00%)
  1 (1.00%) high mild
  2 (2.00%) high severe

I wonder if there are any tricks that would allow you to use the non-parallel case for <2^7.
IDK if it matters that much, since the absolute cost is small anyway - but would be good to at least investigate if maybe rayon allows for that.

Also make sure that the poly definition used here is the one that is not redundant (due to https://github.com/microsoft/Spartan2/issues/9)

The obsolete poly definition is in polynomial.rs: https://github.com/HungryCatsStudio/Spartan2/blob/main/src/spartan/polynomial.rs

Cool. You can remove the obsolete definition in this PR or a follow up, up to you.

Yeah looks good. Could you repost the updated benches?

Cool. You can remove the obsolete definition in this PR or a follow up, up to you

Alright, I guess it does make sense to do it here.

Yeah looks good. Could you repost the updated benches?

Sorry, I didn't mean to re-request review. The benchmarks did not change much; I'm running them again, though.

Right, so it's as we all thought. Thanks for pointing to a source for this!

New benches:
evaluate_incremental/2^1
                       time:   [13.666 µs 13.717 µs 13.768 µs]
                       change: [+6812.6% +6937.9% +7055.6%] (p = 0.00 < 0.05)
                       Performance has regressed.
Found 6 outliers among 100 measurements (6.00%)
 3 (3.00%) low mild
 2 (2.00%) high mild
 1 (1.00%) high severe
evaluate_incremental/2^3
                       time:   [14.974 µs 15.108 µs 15.262 µs]
                       change: [+1966.1% +2019.2% +2074.8%] (p = 0.00 < 0.05)
                       Performance has regressed.
Found 11 outliers among 100 measurements (11.00%)
 4 (4.00%) high mild
 7 (7.00%) high severe
evaluate_incremental/2^5
                       time:   [18.359 µs 18.562 µs 18.785 µs]
                       change: [+545.64% +552.71% +559.60%] (p = 0.00 < 0.05)
                       Performance has regressed.
Found 3 outliers among 100 measurements (3.00%)
 3 (3.00%) high mild
evaluate_incremental/2^7
                       time:   [28.191 µs 28.402 µs 28.628 µs]
                       change: [+145.80% +148.43% +151.12%] (p = 0.00 < 0.05)
                       Performance has regressed.
Found 4 outliers among 100 measurements (4.00%)
 3 (3.00%) high mild
 1 (1.00%) high severe
evaluate_incremental/2^9
                       time:   [55.980 µs 57.917 µs 60.159 µs]
                       change: [+21.740% +23.970% +26.544%] (p = 0.00 < 0.05)
                       Performance has regressed.
Found 8 outliers among 100 measurements (8.00%)
 4 (4.00%) high mild
 4 (4.00%) high severe
evaluate_incremental/2^11
                       time:   [112.90 µs 114.63 µs 116.48 µs]
                       change: [-38.754% -37.528% -35.992%] (p = 0.00 < 0.05)
                       Performance has improved.
Found 2 outliers among 100 measurements (2.00%)
 2 (2.00%) high mild
evaluate_incremental/2^13
                       time:   [277.95 µs 282.42 µs 287.06 µs]
                       change: [-62.248% -61.689% -61.053%] (p = 0.00 < 0.05)
                       Performance has improved.
Found 2 outliers among 100 measurements (2.00%)
 1 (1.00%) high mild
 1 (1.00%) high severe
evaluate_incremental/2^15
                       time:   [953.95 µs 986.72 µs 1.0333 ms]
                       change: [-69.195% -68.426% -67.543%] (p = 0.00 < 0.05)
                       Performance has improved.
Found 3 outliers among 100 measurements (3.00%)
 2 (2.00%) high mild
 1 (1.00%) high severe
evaluate_incremental/2^17
                       time:   [3.4105 ms 3.4747 ms 3.5640 ms]
                       change: [-71.229% -70.680% -69.911%] (p = 0.00 < 0.05)
                       Performance has improved.
Found 5 outliers among 100 measurements (5.00%)
 2 (2.00%) high mild
 3 (3.00%) high severe
evaluate_incremental/2^19
                       time:   [11.854 ms 12.042 ms 12.241 ms]
                       change: [-75.035% -74.632% -74.186%] (p = 0.00 < 0.05)
                       Performance has improved.
Found 1 outliers among 100 measurements (1.00%)
 1 (1.00%) high mild

Top.
Two remaining things then:

resign commits
remove duplicated files

Then we can PR directly to upstream I think


fix a small oversight in request class

where lowercase method name does not trigger type error

Codecov Report

Merging #362 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #362   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           6      6
  Lines         423    424    +1
  Branches      133    133
=====================================
+ Hits          423    424    +1

Impacted Files
Coverage Δ

src/request.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d1a3b1e...35a2c3f. Read the comment docs.

FYI, the travis failure is due to: https://github.com/nodejs/node/issues/16649
the latest stable npm is not compatible with latest stable node.js;
(also reminds me we need to add node 8 lts test in travis too...)


Add ppc64le/s390x support to generate operators from the testdata samples

Feature Request
Describe the problem you need a feature to resolve.
On ppc64le or s390x architectures, we have issues when trying to generate the operator-sdk Ansible/Helm testdata samples or building Ansible/Go/Helm-based operators using operator-sdk and these testdata samples:

The kustomize binary v3.8.7 doesn't exist for ppc64le/s390x failing the make generatecommand.

$ make generate
Error generating the memcache_operator example for helm & ansible:
Command ‘make bundle IMG=quay.io/example/memcached-operator:v0.0.1’ run in testdata/helm/memcached-operator and in testdata/ansible/memcached-operator fails:
running: make bundle IMG=quay.io/example/memcached-operator:v0.0.1
time="2022-03-15T09:14:55-07:00" level=error msg="error creating the bundle: make bundle IMG=quay.io/example/memcached-operator:v0.0.1 failed with error: (exit status 2) make[1]: Entering directory '/home/gquillar/Github/operator-sdk/testdata/helm/memcached-operator'\n\ngzip: stdin: not in gzip format\ntar: Child returned status 1\ntar: Error is not recoverable: exiting now\nmake[1]: *** [Makefile:113: kustomize] Error 2\nmake[1]: Leaving directory '/home/gquillar/Github/operator-sdk/testdata/helm/memcached-operator'\n"
exit status 1
make: *** [Makefile:43: generate] Error 1

The manager binary inside the Golang manager images is built using the amd64 arch. So the Go-based operator
created following operator-sdk quick-start can not be installed on ppc64 or s390x cluster.

# cd testdata/go/v3/memcached-operator
# make docker-build
docker build -t controller:latest .
[1/2] STEP 1/9: FROM golang:1.17 AS builder
[1/2] STEP 2/9: WORKDIR /workspace
--> Using cache ec866082b1fb0d6ac1a1c9fa8bfed85aa63d9d9f5d098a363f8622aca647823d
--> ec866082b1f
[1/2] STEP 3/9: COPY go.mod go.mod
--> 8a4c8a242db
[1/2] STEP 4/9: COPY go.sum go.sum
--> b0ab8bd26cb
[1/2] STEP 5/9: RUN go mod download
--> a62d158aa81
[1/2] STEP 6/9: COPY main.go main.go
--> 8fcaf69e413
[1/2] STEP 7/9: COPY api/ api/
--> 567acaa4099
[1/2] STEP 8/9: COPY controllers/ controllers/
--> d8b13c7fa76
[1/2] STEP 9/9: RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -a -o manager main.go
--> 623ddb3e071
[2/2] STEP 1/5: FROM gcr.io/distroless/static:nonroot
[2/2] STEP 2/5: WORKDIR /
--> Using cache d7d80c0ada6f1b22a8866c93c00581c2477041e63a1b2606ee5c44a288c9f8cf
--> d7d80c0ada6
[2/2] STEP 3/5: COPY --from=builder /workspace/manager .
--> febcaac6651
[2/2] STEP 4/5: USER 65532:65532
--> 59c5696b614
[2/2] STEP 5/5: ENTRYPOINT ["/manager"]
[2/2] COMMIT controller:latest
--> f8ad1ed24df
Successfully tagged localhost/controller:latest
f8ad1ed24df5b068980339b9af0cece40039fa99b559694417e7d6959af87658
# docker run --rm -it localhost/controller:latest version    # try to run the embedded manager binary
standard_init_linux.go:228: exec user process caused: exec format error

The opm binary v1.19.1 used to build the catalog images for the Ansible/Go/Helm samples doesn't exist for ppc64le/s390x.
So the curl command to get the opm binary will create a bin/opm file containing 'Not Found'.

# cd testdata/ansible/memcached-operator
# make catalog-build
./bin/opm index add --container-tool docker --mode semver --tag example.com/memcached-operator-catalog:v0.0.1 --bundles example.com/memcached-operator-bundle:v0.0.1
./bin/opm: line 1: Not: command not found
make: *** [Makefile:197: catalog-build] Error 127
# ls -l bin/opm
-rwxr-xr-x 1 root root 9 May 20 05:55 bin/opm
# cat bin/opm
Not Found

Describe the solution you'd like.

Concerning the kustomize binary,

ppc64le/s390x is supported in v4.5 but v4 is a breaking change.
a new plugin kustomize/v2-alpha is in development to use kustomize v4 (PR-2583), but not yet available and will be an alpha version
so to support ppc64le/s390x, the proposed solution is to build locally the kustomize binary from 3.8.7 source tarball (see PR-4612)
since the testdata samples are generated, the changed would be done in
kubebuilder for Go, in
pkg/plugins/golang/v3/scaffolds/internal/templates/makefile.go and in
operator-sdk for Ansible & Helm in
internal/plugins/ansible/v1/scaffolds/internal/templates/makefile.go and in
internal/plugins/helm/v1/scaffolds/internal/templates/makefile.go.

Concerning the manager binary in the Go manager image, since the the testdata Go samples are generated from kubebuilder, the change could be done in kubebuilder in pkg/plugins/golang/v3/scaffolds/internal/templates/makefile.go and pkg/plugins/golang/v3/scaffolds/internal/templates/dockerfile.go to pass the GOARCH to the Dockerfile in order to build the managerbinary with the correct arch. Currently, we have:
RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -a -o manager main.go
Concerning the opm binary, the version could be upgraded to a version 1.20+ which supports both ppc64le and s390x.
operator-framework/operator-sdk#5674, operator-framework/operator-sdk#5736 and operator-framework/operator-sdk#5676 were initially opened to fix these issues on P and Z, but the proposed changes were wrong since they were done directly in the testdata directory of operator-sdk, which is a generated directory. So the change has to be made in kubebuider or in the operator-sdk generating the testdata content.

/language go
/language ansible
/language helm

Hi @gquillar,
The samples under the testdata are projects scaffolded with the code source/SDK tool. We cannot make the samples support ppc64le or s390x. Instead, we need Kubebuilder and SDK producing projects that support these architectures. Also, probably plugins that indeed have the source code outside of the SDK repo.
Note that is not only about changing the Makefile. (https://github.com/operator-framework/operator-sdk/pull/5736/files) it is also about producing images and binaries that can be used with. Please, see, for example, the task open to Kubebuilder support darwin/arm64: https://github.com/kubernetes-sigs/kubebuilder/issues/1932.
In this way:
Regards the proposed changes in the Dockerfile
if you want to change the Dockerfile for further releases, then the change needs to be done in the templates,
For Golang, it must be done in: https://github.com/kubernetes-sigs/kubebuilder/blob/master/pkg/plugins/golang/v3/scaffolds/internal/templates/dockerfile.go
For Ansible/Helm and any other language plugin, we need to update the Dockerfile of the specific plugin.
In this way, I'd recommend you push a PR against Kubebuilder, and then after that gets merged, we need to update all language plugins inside of SDK and those used by it and have the code on other repos.
Regards the proposed changes to use an upper version of OPM
The PR https://github.com/operator-framework/operator-sdk/pull/5676. It shows fine. I just added small nits to it.
Regards upgrade kustomize to v4
I do not think that we can move with this one: https://github.com/operator-framework/operator-sdk/pull/5674
When we bump the next Kubebuilder release we will be able to check if we need to begin to use the new kustomize/v2-alpha to have the version v4. See: https://github.com/kubernetes-sigs/kubebuilder/pull/2583
Also, we need to evaluate if we can make the helm/ansible plugins begin to use kustomize.v2-alpha directly or if we need new versions of these plugins as well.

PR #2697 has been opened on kubernetes-sigs/kubebuilder to fix the arch used to build the binary in the go/v3 scaffold templates.

Since this is now an upstream issue, I think we are good to close here? Please reopen if necessary.


Release notes for 0.13.1

Signed-off-by: Mike Kolesnik<EMAIL_ADDRESS>

Applied Daniel's suggestions, let's make sure to squash when merging.

Squashed and merged, thanks Mike!


How can we do for keep action on button execute

Hello,
My subject :
I use YASQE and I configure a auto-completion pluging with Gosparqled.
And use Symfony 2.8 for my project
My question :
The plug-in Yasqe is configure with the button execute and I have no control on this, the query is execute directly on sparql endpoint.
But I want to keep the button and I retrieve the query when I click on.
My purpose is generate method Ajax for example call controler symfony with the final query.
I know how to get query but the action I don't know where she is.
I want a query for execute directly (with method PHP) on controler Symfony and send the result at yars.
Thank in advance,

@art-tom Can you rephrase the title and description a bit?  It is currently not so clear what your question is about.  E.g., what is a controller in this context?  And what do you mean with another endpoint; do you mean federation using a service clause?

Hello @wouterbeek ,
Thank for the answer.
I have explain my problem.
It is more clear ?
Thank

Hello,
Has you have an idea ?
Thank

Hi @art-tom,
If I understand you correctly, you don't want to query a sparql endpoint via YASQE, but send a different (non-sparql) request to another API when a user is clicking the query button.
To do so, you can overwrite the 'executeQuery' function of YASQE:
YASQE.executeQuery = function(yasqe, config) {
  console.log('Just pressed the query button. The current value is: ', yasqe.getValue());
  //YASQE.updateQueryButton(yasqe, "busy"); //Set the query button to loading status
  //YASQE.updateQueryButton(yasqe, "valid"); // Set the query button to non-loading and valid-query status
  //YASQE.updateQueryButton(yasqe, "error"); //set the query button to error status
  //YASQE.updateQueryButton(yasqe); //Automatically detect (based on the current query), whether the status is valid or invalid
}

Added, in comments, some functions you can use in the callback to your API to change the query button state according to the response you receive

Hello,
Many thanks for answer.
I modified the method, but I have a last problem for fetch the result into yasr.
My on yars is a tableau and it's not possible to change.
My function is :
 YASQE.executeQuery = function(yasqe, config) {                 $.ajax({                         url:       path,                         type:       'post',                         dataType:   'json',                         async:      true,                         data : {"request" : yasqe.getValue()},                         success: function(data, status, response) {                             yasr.setResponse({response: data});                         },                         error : function(xhr, textStatus, errorThrown) {                         alert('Ajax request failed.');                         }                 });                 }
Can you help me ?

And in my controller the code is :
if ($request->isXmlHttpRequest()) {
            $req = $request-> get('request');
            switch($req){
                case stripos($req, 'select') !== false:
                    $req = $this->deleteSelect($req);
                    $qb->select($req);
                    $result = $qb->getQuery()->execute();
                    return new JsonResponse(json_encode($result));
                break;

                case stripos($req, 'construct') !== false:
                    $req = $this->deleteConstruct($req);
                    $qb->construct($req);
                    $result = $qb->getQuery()->execute();
                    return new JsonResponse(json_encode($result));
                break;

                default :
                    return new Response(json_encode("Query is not authorize"));
                break;
            }

Hello,
Sorry for my insisted.
I have a question, it's possible to execute a normal function query with Yasqe bundle in my callback function Jquery.
I explain, when I retrieve my query in my control and check a differents think, I return the Query and in callback on success I call the method developped in Yasqe for execute query normaly and pass the result at yasr.
Like this :
yasqe.options.sparql.handlers.success =  function(data, status, response) {
	yasr.setResponse({response: data, contentType: response.getResponseHeader("Content-Type")});
};

And my function for example :
YASQE.executeQuery = function(yasqe, config) {
    $.ajax({
            url: path, // initialize in index
            type: 'post',
            dataType: "json",
            data : {"request" : yasqe.getValue()},
            success: function(data, status, response) {
               /// CALL NORMAL EXECUTION QUERY
            },
            error : function(xhr, textStatus, errorThrown) {
                yasr.setResponse({exception: textStatus, contentType: response.getResponseHeader("Content-Type")});
            },
            beforeSend: function(){
                YASQE.updateQueryButton(yasqe, "busy");
            },
            complete: function(){
                YASQE.updateQueryButton(yasqe);
            }

        });
}

I find the solution.
I save the original function and I call when I have need
` var _old = YASQE.executeQuery;
YASQE.executeQuery = function(yasqe, config) {
$.ajax({
url: path, // initialize in index
type: 'post',
dataType: "json",
data : {"request" : yasqe.getValue()},
success: function(data, status, response) {
//               yasr.setResponse({response: data});
console.log(data);
// prototype.yasqe.query();
console.log(_old);
_old(yasqe,config);
//YASQE.executeQuery(yasqe.getValue());
},
error : function(xhr, textStatus, errorThrown) {
yasr.setResponse({exception: textStatus, contentType: response.getResponseHeader("Content-Type")});
},
beforeSend: function(){
YASQE.updateQueryButton(yasqe, "busy");
},
complete: function(){
YASQE.updateQueryButton(yasqe);
}
        });
}`


JSON returned by json_repair is not in expected format

Describe the bug
Returned json by json_repair is not in correct format which was expected.
To Reproduce
Steps to reproduce the behavior:
Run the file in python environment with langchain and json_repair installed
Expected behavior
I expected the repair_json to repair the output json.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Browser Chrome
Version 123.0.6312.106

Additional context
OpenAI has returned incomplete json due to limit in completion prompt. The json is missing ":" after 'answer40' at the end of the response. I expected json_repair to fix the issue but it has created unexpected json.
Code to get the json:
import json_repair
from langchain_core.messages.ai import AIMessage

response = AIMessage(content='', additional_kwargs={'function_call': {'arguments': '{""answer"":[{""traits"":""Female aged 60+"",""answer1"":""5"",""answer2"":""Labrador Retriever"",""answer3"":""75"",""answer4"":""Buddy"",""answer5"":""It was my late husband\'s nickname"",""answer6"":""Bud"",""answer7"":""Before 2020"",""answer8"":""yes"",""answer9"":""6"",""answer10"":""Instant connection"",""answer11"":""It\'s taught me more about unconditional love"",""answer12"":""5"",""answer13"":""Family Member"",""answer14"":""Because he\'s part of the family"",""answer15"":""Paw shake, about a week"",""answer16"":""14, in a dog bed by my bedside"",""answer17"":""yes"",""answer18"":""$1200"",""answer19"":""20%"",""answer20"":""60%"",""answer21"":""$100"",""answer22"":""Spent less in March"",""answer23"":""Monthly"",""answer24"":""Dry food"",""answer25"":""I know a lot about the brand"",""answer26"":""5"",""answer27"":""3"",""answer28"":""5"",""answer29"":""4"",""answer30"":""5"",""answer31"":""4"",""answer32"":""2"",""answer33"":""Blue Buffalo"",""answer34"":""High quality, my dog loves it, good value"",""answer35"":""5"",""answer36"":""4"",""answer37"":""5"",""answer38"":""4"",""answer39"":""5"",""answer40"":""4"",""answer41"":""3"",""answer42"":""3"",""answer43"":""I interact more"",""answer44"":""The ongoing pandemic"",""answer45"":""No"",""answer46"":""Yes"",""answer47"":""Car"",""answer48"":""Female"",""answer49"":""63"",""answer50"":""1"",""answer51"":""Graduate degree"",""answer52"":""Retired"",""answer53"":""Less than $25,000"",""answer54"":""Sarasota"",""answer55"":""Florida""},{""traits"":""Female aged 60+"",""answer1"":""3"",""answer2"":""Beagle"",""answer3"":""20"",""answer4"":""Scout"",""answer5"":""To Kill a Mockingbird is my favorite book"",""answer6"":""Scooty"",""answer7"":""After 2020"",""answer8"":""no"",""answer9"":""8"",""answer10"":""Overwhelmed with joy"",""answer11"":""I\'ve become more active"",""answer12"":""5"",""answer13"":""Best Friend"",""answer14"":""We do everything together"",""answer15"":""Stay, a couple of days"",""answer16"":""16, on the living room couch"",""answer17"":""yes"",""answer18"":""$800"",""answer19"":""30%"",""answer20"":""50%"",""answer21"":""$70"",""answer22"":""Spent more in March"",""answer23"":""Bi-weekly"",""answer24"":""Mix"",""answer25"":""I know just the basics about the brand"",""answer26"":""5"",""answer27"":""4"",""answer28"":""5"",""answer29"":""3"",""answer30"":""5"",""answer31"":""2"",""answer32"":""4"",""answer33"":""Purina"",""answer34"":""Affordable, accessible, and Scout enjoys it"",""answer35"":""4"",""answer36"":""5"",""answer37"":""4"",""answer38"":""3"",""answer39"":""5"",""answer40"":""2"",""answer41"":""4"",""answer42"":""2"",""answer43"":""No change"",""answer44"":""The pandemic, but we\'ve adapted"",""answer45"":""Yes"",""answer46"":""No"",""answer47"":""N/A-I\'m not planning to travel with my dog this Spring"",""answer48"":""Female"",""answer49"":""68"",""answer50"":""2"",""answer51"":""Bachelor\'s degree"",""answer52"":""Retired"",""answer53"":""$50,000 to $74,999"",""answer54"":""Boise"",""answer55"":""Idaho""},{""traits"":""Female aged 60+"",""answer1"":""7"",""answer2"":""Golden Retriever"",""answer3"":""65"",""answer4"":""Sunny"",""answer5"":""Her cheerful personality"",""answer6"":""Sun"",""answer7"":""Before 2020"",""answer8"":""yes"",""answer9"":""10"",""answer10"":""Pure happiness"",""answer11"":""I appreciate the simple joys more"",""answer12"":""5"",""answer13"":""Loyal companion"",""answer14"":""Sunny is always by my side"",""answer15"":""Open doors, took about a month"",""answer16"":""12, on her plush bed in the sunroom"",""answer17"":""yes"",""answer18"":""$1500"",""answer19"":""25%"",""answer20"":""40%"",""answer21"":""$130"",""answer22"":""Spent about the same in March"",""answer23"":""Weekly"",""answer24"":""Dry food"",""answer25"":""I know a lot about the brand"",""answer26"":""5"",""answer27"":""2"",""answer28"":""5"",""answer29"":""4"",""answer30"":""5"",""answer31"":""5"",""answer32"":""1"",""answer33"":""Royal Canin"",""answer34"":""Superb quality, vet recommended"",""answer35"":""5"",""answer36"":""3"",""answer37"":""5"",""answer38"":""4"",""answer39"":""5"",""answer40"":""5"",""answer41"":""2"",""answer42"":""2"",""answer43"":""I interact more"",""answer44"":""Pandemic, we\'re staying home more"",""answer45"":""Not Sure"",""answer46"":""Yes"",""answer47"":""Car"",""answer48"":""Female"",""answer49"":""65"",""answer50"":""1"",""answer51"":""Some college, no degree"",""answer52"":""Employed part-time"",""answer53"":""$25,000 to $49,999"",""answer54"":""Tucson"",""answer55"":""Arizona""},{""traits"":""Female aged 60+"",""answer1"":""9"",""answer2"":""Dachshund"",""answer3"":""14"",""answer4"":""Frankie"",""answer5"":""His long body reminds me of a hotdog"",""answer6"":""Frank"",""answer7"":""In 2020"",""answer8"":""no"",""answer9"":""48"",""answer10"":""Amused by his quirky attitude"",""answer11"":""Laughs are a daily occurrence now"",""answer12"":""5"",""answer13"":""Protector"",""answer14"":""Fearless despite his size"",""answer15"":""Dance, surprisingly one weekend"",""answer16"":""10, in my bed"",""answer17"":""yes"",""answer18"":""$500"",""answer19"":""20%"",""answer20"":""40%"",""answer21"":""$40"",""answer22"":""Spent less in March"",""answer23"":""Monthly"",""answer24"":""Wet food"",""answer25"":""I\'m not very familiar with the brand"",""answer26"":""5"",""answer27"":""3"",""answer28"":""4"",""answer29"":""3"",""answer30"":""4"",""answer31"":""3"",""answer32"":""3"",""answer33"":""Hill\'s Science Diet"",""answer34"":""Recommended by my vet, Frankie\'s health"",""answer35"":""4"",""answer36"":""4"",""answer37"":""4"",""answer38"":""3"",""answer39"":""4"",""answer40"":""4"",""answer41"":""3"",""answer42"":""4"",""answer43"":""I interact more"",""answer44"":""Retirement, I have more time"",""answer45"":""Yes"",""answer46"":""No"",""answer47"":""N/A-I\'m not planning to travel with my dog this Spring"",""answer48"":""Female"",""answer49"":""70"",""answer50"":""1"",""answer51"":""Associate degree"",""answer52"":""Retired"",""answer53"":""Less than $25,000"",""answer54"":""Springfield"",""answer55"":""Missouri""},{""traits"":""Female aged 60+"",""answer1"":""2"",""answer2"":""Poodle"",""answer3"":""10"",""answer4"":""Coco"",""answer5"":""Her fur\'s chocolate color"",""answer6"":""Cokes"",""answer7"":""After 2020"",""answer8"":""yes"",""answer9"":""3"",""answer10"":""Adoration"",""answer11"":""I feel less lonely"",""answer12"":""5"",""answer13"":""Best Friend"",""answer14"":""Coco follows me everywhere"",""answer15"":""Fetch, just a few sessions"",""answer16"":""18, on a designer doggy bed"",""answer17"":""yes"",""answer18"":""$2000"",""answer19"":""10%"",""answer20"":""70%"",""answer21"":""$160"",""answer22"":""Spent more in March"",""answer23"":""Weekly"",""answer24"":""Mix"",""answer25"":""I know a lot about the brand"",""answer26"":""5"",""answer27"":""2"",""answer28"":""5"",""answer29"":""5"",""answer30"":""5"",""answer31"":""3"",""answer32"":""5"",""answer33"":""Orijen"",""answer34"":""Coco\'s improvement, natural ingredients"",""answer35"":""5"",""answer36"":""3"",""answer37"":""5"",""answer38"":""5"",""answer39"":""5"",""answer40"":""3"",""answer41"":""5"",""answer42"":""3"",""answer43"":""I interact more"",""answer44"":""Having moved to a pet-friendly community"",""answer45"":""Yes"",""answer46"":""Yes"",""answer47"":""Car"",""answer48"":""Female"",""answer49"":""61"",""answer50"":""1"",""answer51"":""Graduate degree"",""answer52"":""Self-employed"",""answer53"":""$100,000 to $149,000"",""answer54"":""San Diego"",""answer55"":""California""},{""traits"":""Female aged 60+"",""answer1"":""11"",""answer2"":""Yorkshire Terrier"",""answer3"":""7"",""answer4"":""Pixie"",""answer5"":""Her tiny, fairy-like appearance"",""answer6"":""Pix"",""answer7"":""Before 2020"",""answer8"":""no"",""answer9"":""12"",""answer10"":""A bit anxious, she was so small"",""answer11"":""I enjoy everyday moments more"",""answer12"":""5"",""answer13"":""Family Member"",""answer14"":""She\'s been with me through thick and thin"",""answer15"":""Spin, just took two weeks"",""answer16"":""13, her cushioned crate"",""answer17"":""yes"",""answer18"":""$700"",""answer19"":""15%"",""answer20"":""45%"",""answer21"":""$60"",""answer22"":""Spent about the same in March"",""answer23"":""Bi-weekly"",""answer24"":""Dry food"",""answer25"":""I know just the basics about the brand"",""answer26"":""4"",""answer27"":""3"",""answer28"":""4"",""answer29"":""5"",""answer30"":""5"",""answer31"":""1"",""answer32"":""4"",""answer33"":""Iams"",""answer34"":""My Pixie\'s health, cost-effective"",""answer35"":""4"",""answer36"":""5"",""answer37"":""4"",""answer38"":""4"",""answer39"":""5"",""answer40"":""1"",""answer41"":""4"",""answer42"":""5"",""answer43"":""I interact more"",""answer44"":""The pandemic has us spending more time indoors"",""answer45"":""Not Sure"",""answer46"":""No"",""answer47"":""N/A-I\'m not planning to travel with my dog this Spring"",""answer48"":""Female"",""answer49"":""72"",""answer50"":""2"",""answer51"":""High school diploma or equivalent"",""answer52"":""Retired"",""answer53"":""Less than $25,000"",""answer54"":""Macon"",""answer55"":""Georgia""},{""traits"":""Female aged 60+"",""answer1"":""4"",""answer2"":""Border Collie"",""answer3"":""45"",""answer4"":""Shep"",""answer5"":""Traditional name for a sheepdog"",""answer6"":""Sheppy"",""answer7"":""Before 2020"",""answer8"":""yes"",""answer9"":""5"",""answer10"":""I felt protective"",""answer11"":""Daily physical activity is a must"",""answer12"":""5"",""answer13"":""Loyal companion"",""answer14"":""Always ready to work and play"",""answer15"":""We\'ve mastered herding techniques, took months"",""answer16"":""10, in the utility room on his mat"",""answer17"":""yes"",""answer18"":""$1300"",""answer19"":""10%"",""answer20"":""55%"",""answer21"":""$110"",""answer22"":""Spent about the same in March"",""answer23"":""Weekly"",""answer24"":""Dry food"",""answer25"":""I know a lot about the brand"",""answer26"":""5"",""answer27"":""4"",""answer28"":""5"",""answer29"":""3"",""answer30"":""5"",""answer31"":""3"",""answer32"":""2"",""answer33"":""Acana"",""answer34"":""High-quality, breed-specific formula"",""answer35"":""5"",""answer36"":""4"",""answer37"":""5"",""answer38"":""4"",""answer39"":""5"",""answer40"":""3"",""answer41"":""2"",""answer42"":""4"",""answer43"":""No change"",""answer44"":""Seasonal allergies, we adjust our time outside"",""answer45"":""No"",""answer46"":""No"",""answer47"":""N/A-I\'m not planning to travel with my dog this Spring"",""answer48"":""Female"",""answer49"":""67"",""answer50"":""1"",""answer51"":""Bachelor\'s degree"",""answer52"":""Employed part-time"",""answer53"":""$25,000 to $49,999"",""answer54"":""Topeka"",""answer55"":""Kansas""},{""traits"":""Female aged 60+"",""answer1"":""10"",""answer2"":""Chihuahua"",""answer3"":""5"",""answer4"":""Tiny"",""answer5"":""Her petite size"",""answer6"":""T"",""answer7"":""After 2020"",""answer8"":""yes"",""answer9"":""24"",""answer10"":""Amused by her sassiness"",""answer11"":""It\'s important to love fiercely"",""answer12"":""5"",""answer13"":""Best Friend"",""answer14"":""Tiny is always by my side, my constant tiny shadow"",""answer15"":""Sit pretty, she picked it up in days"",""answer16"":""14, she curls up in the bed under the window"",""answer17"":""yes"",""answer18"":""$550"",""answer19"":""40%"",""answer20"":""30%"",""answer21"":""$50"",""answer22"":""Spent less in March"",""answer23"":""Bi-weekly"",""answer24"":""Mix"",""answer25"":""I know just the basics about the brand"",""answer26"":""5"",""answer27"":""5"",""answer28"":""5"",""answer29"":""2"",""answer30"":""5"",""answer31"":""2"",""answer32"":""1"",""answer33"":""Cesar"",""answer34"":""Tiny loves it, it\'s affordable, easy to store"",""answer35"":""5"",""answer36"":""5"",""answer37"":""4"",""answer38"":""2"",""answer39"":""5"",""answer40"":""2"",""answer41"":""1"",""answer42"":""5"",""answer43"":""No change"",""answer44"":""The seasons changing is the biggest influence"",""answer45"":""Yes"",""answer46"":""Yes"",""answer47"":""Car"",""answer48"":""Female"",""answer49"":""69"",""answer50"":""1"",""answer51"":""Some college, no degree"",""answer52"":""Retired"",""answer53"":""$50,000 to $74,999"",""answer54"":""El Paso"",""answer55"":""Texas""},{""traits"":""Female aged 60+"",""answer1"":""6"",""answer2"":""Bulldog"",""answer3"":""50"",""answer4"":""Winston"",""answer5"":""His stately, British-like demeanor"",""answer6"":""Win"",""answer7"":""Before 2020"",""answer8"":""no"",""answer9"":""3"",""answer10"":""Awe, he\'s got so much character"",""answer11"":""I\'ve become more patient"",""answer12"":""5"",""answer13"":""Family Member"",""answer14"":""He\'s more like a child to me than a pet"",""answer15"":""Speak on command, a stubborn month or so"",""answer16"":""12, sprawled across the hallway rug"",""answer17"":""yes"",""answer18"":""$1100"",""answer19"":""15%"",""answer20"":""45%"",""answer21"":""$90"",""answer22"":""Spent about the same in March"",""answer23"":""Monthly"",""answer24"":""Dry food"",""answer25"":""I know a lot about the brand"",""answer26"":""4"",""answer27"":""2"",""answer28"":""4"",""answer29"":""5"",""answer30"":""5"",""answer31"":""3"",""answer32"":""3"",""answer33"":""Nutro"",""answer34"":""Non-GMO ingredients, Winston\'s preference"",""answer35"":""4"",""answer36"":""3"",""answer37"":""4"",""answer38"":""5"",""answer39"":""5"",""answer40"":""3"",""answer41"":""3"",""answer42"":""3"",""answer43"":""I interact less"",""answer44"":""Winston\'s aging, he is more independent"",""answer45"":""Not Sure"",""answer46"":""No"",""answer47"":""N/A-I\'m not planning to travel with my dog this Spring"",""answer48"":""Female"",""answer49"":""65"",""answer50"":""2"",""answer51"":""Graduate degree"",""answer52"":""Retired"",""answer53"":""Prefer not to say"",""answer54"":""Charleston"",""answer55"":""South Carolina""},{""traits"":""Female aged 60+"",""answer1"":""8"",""answer2"":""Shih Tzu"",""answer3"":""12"",""answer4"":""Gizmo"",""answer5"":""His playful and curious nature"",""answer6"":""Gizzy"",""answer7"":""In 2020"",""answer8"":""yes"",""answer9"":""60"",""answer10"":""Instant love, he\'s such a fluffball"",""answer11"":""I\'m more outgoing, he needs lots of socializing"",""answer12"":""5"",""answer13"":""Best Friend"",""answer14"":""We have an unbreakable bond"",""answer15"":""Roll over, a week\'s full of treats and praise"",""answer16"":""15, on his favorite armchair"",""answer17"":""yes"",""answer18"":""$950"",""answer19"":""10%"",""answer20"":""55%"",""answer21"":""$80"",""answer22"":""Spent about the same in March"",""answer23"":""Monthly"",""answer24"":""Dry food"",""answer25"":""I know just the basics about the brand"",""answer26"":""5"",""answer27"":""4"",""answer28"":""5"",""answer29"":""3"",""answer30"":""5"",""answer31"":""1"",""answer32"":""4"",""answer33"":""Science Diet"",""answer34"":""Gizzy likes it, vet approved, easy to find"",""answer35"":""4"",""answer36"":""4"",""answer37"":""5"",""answer38"":""3"",""answer39"":""5"",""answer40"":""1"",""answer41"":""4"",""answer42"":""4"",""answer43"":""No change"",""answer44"":""Seasonal weather, we keep our routine"",""answer45"":""Yes"",""answer46"":""Not Sure"",""answer47"":""N/A-I\'m not planning to travel with my dog this Spring"",""answer48"":""Female"",""answer49"":""64"",""answer50"":""1"",""answer51"":""Bachelor\'s degree"",""answer52"":""Employed full-time"",""answer53"":""$50,000 to $74,999"",""answer54"":""Reno"",""answer55"":""Nevada""},{""traits"":""Female aged 60+"",""answer1"":""1"",""answer2"":""Australian Shepherd"",""answer3"":""30"",""answer4"":""Blue"",""answer5"":""His striking blue eyes"",""answer6"":""Boo"",""answer7"":""After 2020"",""answer8"":""no"",""answer9"":""2"",""answer10"":""Thrilled, he was full of energy"",""answer11"":""I\'ve got a new sense of purpose"",""answer12"":""5"",""answer13"":""Loyal companion"",""answer14"":""He\'s loyal and always there for support"",""answer15"":""Fetch with a frisbee, about two weeks"",""answer16"":""14, on a runner in the hall"",""answer17"":""yes"",""answer18"":""$1000"",""answer19"":""5%"",""answer20"":""65%"",""answer21"":""$85"",""answer22"":""Spent more in March"",""answer23"":""Weekly"",""answer24"":""Dry food"",""answer25"":""I know a lot about the brand"",""answer26"":""5"",""answer27"":""3"",""answer28"":""5"",""answer29"":""4"",""answer30"":""5"",""answer31"":""4"",""answer32"":""1"",""answer33"":""Taste of the Wild"",""answer34"":""Grain-free, Blue\'s coat looks amazing"",""answer35"":""5"",""answer36"":""4"",""answer37"":""5"",""answer38"":""4"",""answer39"":""5"",""answer40', 'name': 'Answers'}})

final_json = json_repair.loads(response.additional_kwargs['function_call']['arguments'])['answer']

JSON return by json_repair:
[{'traits': '', 60: '', 'answer1': '', 5: ',', 'answer2': '', 'Retriever': '', 'answer3': '', 75: ',', 'answer4': '', 'Buddy': '', 'answer5': '', 'nickname': '', 'answer6': '', 'Bud': '', 'answer7': '', 2020: ',', 'answer8': '', 'yes': '', 'answer9': '', 6: ',', 'answer10': '', 'connection': '', 'answer11': '', 'love': '', 'answer12': '', 'answer13': '', 'Member': '', 'answer14': '', 'family': '', 'answer15': '', 'week': '', 'answer16': '', 14: 'in a dog bed by my bedside', ',': 'answer18', ':': 1200, 'answer19': '', 20: '', 'answer20': '', 'answer21': '', 100: ',', 'answer22': '', 'March': '', 'answer23': '', 'Monthly': '', 'answer24': '', 'food': '', 'answer25': '', 'brand': '', 'answer26': '', 'answer27': '', 3: ',', 'answer28': '', 'answer29': '', 4: ',', 'answer30': '', 'answer31': '', 'answer32': '', 2: ',', 'answer33': '', 'Buffalo': '', 'answer34': '', 'value': '', 'answer35': '', 'answer36': '', 'answer37': '', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'more': '', 'answer44': '', 'pandemic': '', 'answer45': '', 'No': '', 'answer46': '', 'Yes': '', 'answer47': '', 'Car': '', 'answer48': '', 'Female': '', 'answer49': '', 63: ',', 'answer50': '', 1: ',', 'answer51': '', 'degree': '', 'answer52': '', 'Retired': '', 'answer53': '', 25: 0, 'answer54': '', 'Sarasota': '', 'answer55': '', 'Florida': ''}, {'traits': '', 60: '', 'answer1': '', 3: ',', 'answer2': '', 'Beagle': '', 'answer3': '', 20: ',', 'answer4': '', 'Scout': '', 'answer5': '', 'book': '', 'answer6': '', 'Scooty': '', 'answer7': '', 2020: ',', 'answer8': '', 'no': '', 'answer9': '', 8: ',', 'answer10': '', 'joy': '', 'answer11': '', 'active': '', 'answer12': '', 5: ',', 'answer13': '', 'Friend': '', 'answer14': '', 'together': '', 'answer15': '', 'days': '', 'answer16': '', 16: 'on the living room couch', ',': 'answer18', ':': 800, 'answer19': '', 30: '', 'answer20': '', 50: 0, 'answer21': '', 70: ',', 'answer22': '', 'March': '', 'answer23': '', 'Bi-weekly': '', 'answer24': '', 'Mix': '', 'answer25': '', 'brand': '', 'answer26': '', 'answer27': '', 4: ',', 'answer28': '', 'answer29': '', 'answer30': '', 'answer31': '', 2: ',', 'answer32': '', 'answer33': '', 'Purina': '', 'answer34': '', 'it': '', 'answer35': '', 'answer36': '', 'answer37': '', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'change': '', 'answer44': '', 'adapted': '', 'answer45': '', 'Yes': '', 'answer46': '', 'No': '', 'answer47': '', 'Spring': '', 'answer48': '', 'Female': '', 'answer49': '', 68: ',', 'answer50': '', 'answer51': '', 'degree': '', 'answer52': '', 'Retired': '', 'answer53': '', 74: 999, 'answer54': '', 'Boise': '', 'answer55': '', 'Idaho': ''}, {'traits': '', 60: '', 'answer1': '', 7: ',', 'answer2': '', 'Retriever': '', 'answer3': '', 65: ',', 'answer4': '', 'Sunny': '', 'answer5': '', 'personality': '', 'answer6': '', 'Sun': '', 'answer7': '', 2020: ',', 'answer8': '', 'yes': '', 'answer9': '', 10: ',', 'answer10': '', 'happiness': '', 'answer11': '', 'more': '', 'answer12': '', 5: ',', 'answer13': '', 'companion': '', 'answer14': '', 'side': '', 'answer15': '', 'month': '', 'answer16': '', 12: 'on her plush bed in the sunroom', ',': 'answer18', ':': 1500, 'answer19': '', 25: 0, 'answer20': '', 40: '', 'answer21': '', 130: ',', 'answer22': '', 'March': '', 'answer23': '', 'Weekly': '', 'answer24': '', 'food': '', 'answer25': '', 'brand': '', 'answer26': '', 'answer27': '', 2: ',', 'answer28': '', 'answer29': '', 4: ',', 'answer30': '', 'answer31': '', 'answer32': '', 1: ',', 'answer33': '', 'Canin': '', 'answer34': '', 'recommended': '', 'answer35': '', 'answer36': '', 3: ',', 'answer37': '', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'answer44': '', 'answer45': '', 'Sure': '', 'answer46': '', 'Yes': '', 'answer47': '', 'Car': '', 'answer48': '', 'Female': '', 'answer49': '', 'answer50': '', 'answer51': '', 'degree': '', 'answer52': '', 'part-time': '', 'answer53': '', 49: 999, 'answer54': '', 'Tucson': '', 'answer55': '', 'Arizona': ''}, {'traits': '', 60: '', 'answer1': '', 9: ',', 'answer2': '', 'Dachshund': '', 'answer3': '', 14: ',', 'answer4': '', 'Frankie': '', 'answer5': '', 'hotdog': '', 'answer6': '', 'Frank': '', 'answer7': '', 2020: ',', 'answer8': '', 'no': '', 'answer9': '', 48: ',', 'answer10': '', 'attitude': '', 'answer11': '', 'now': '', 'answer12': '', 5: ',', 'answer13': '', 'Protector': '', 'answer14': '', 'size': '', 'answer15': '', 'weekend': '', 'answer16': '', 10: 'in my bed', ',': 'answer18', ':': 500, 'answer19': '', 20: '', 'answer20': '', 40: ',', 'answer21': '', 'answer22': '', 'March': '', 'answer23': '', 'Monthly': '', 'answer24': '', 'food': '', 'answer25': '', 'brand': '', 'answer26': '', 'answer27': '', 3: ',', 'answer28': '', 4: ',', 'answer29': '', 'answer30': '', 'answer31': '', 'answer32': '', 'answer33': '', 'Diet': '', 'answer34': '', 'health': '', 'answer35': '', 'answer36': '', 'answer37': '', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'more': '', 'answer44': '', 'time': '', 'answer45': '', 'Yes': '', 'answer46': '', 'No': '', 'answer47': '', 'Spring': '', 'answer48': '', 'Female': '', 'answer49': '', 70: ',', 'answer50': '', 1: ',', 'answer51': '', 'degree': '', 'answer52': '', 'Retired': '', 'answer53': '', 25: 0, 'answer54': '', 'Springfield': '', 'answer55': '', 'Missouri': ''}, {'traits': '', 60: '', 'answer1': '', 2: ',', 'answer2': '', 'Poodle': '', 'answer3': '', 10: '', 'answer4': '', 'Coco': '', 'answer5': '', 'color': '', 'answer6': '', 'Cokes': '', 'answer7': '', 2020: ',', 'answer8': '', 'yes': '', 'answer9': '', 3: ',', 'answer10': '', 'Adoration': '', 'answer11': '', 'lonely': '', 'answer12': '', 5: ',', 'answer13': '', 'Friend': '', 'answer14': '', 'everywhere': '', 'answer15': '', 'sessions': '', 'answer16': '', 18: 'on a designer doggy bed', ',': 'answer18', ':': 2000, 'answer19': '', 'answer20': '', 70: '', 'answer21': '', 160: ',', 'answer22': '', 'March': '', 'answer23': '', 'Weekly': '', 'answer24': '', 'Mix': '', 'answer25': '', 'brand': '', 'answer26': '', 'answer27': '', 'answer28': '', 'answer29': '', 'answer30': '', 'answer31': '', 'answer32': '', 'answer33': '', 'Orijen': '', 'answer34': '', 'ingredients': '', 'answer35': '', 'answer36': '', 'answer37': '', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'more': '', 'answer44': '', 'community': '', 'answer45': '', 'Yes': '', 'answer46': '', 'answer47': '', 'Car': '', 'answer48': '', 'Female': '', 'answer49': '', 61: ',', 'answer50': '', 1: ',', 'answer51': '', 'degree': '', 'answer52': '', 'Self-employed': '', 'answer53': '', 100: 0, 149: 0, 'answer54': '', 'Diego': '', 'answer55': '', 'California': ''}, {'traits': '', 60: ',', 'answer1': '', 11: ',', 'answer2': '', 'Terrier': '', 'answer3': '', 7: ',', 'answer4': '', 'Pixie': '', 'answer5': '', 'appearance': '', 'answer6': '', 'Pix': '', 'answer7': '', 2020: ',', 'answer8': '', 'no': '', 'answer9': '', 12: ',', 'answer10': '', 'small': '', 'answer11': '', 'more': '', 'answer12': '', 5: ',', 'answer13': '', 'Member': '', 'answer14': '', 'thin': '', 'answer15': '', 'weeks': '', 'answer16': '', 13: 'her cushioned crate', ',': 'answer18', ':': 700, 'answer19': '', 15: '', 'answer20': '', 45: '', 'answer21': '', 'answer22': '', 'March': '', 'answer23': '', 'Bi-weekly': '', 'answer24': '', 'food': '', 'answer25': '', 'brand': '', 'answer26': '', 4: ',', 'answer27': '', 3: ',', 'answer28': '', 'answer29': '', 'answer30': '', 'answer31': '', 1: ',', 'answer32': '', 'answer33': '', 'Iams': '', 'answer34': '', 'cost-effective': '', 'answer35': '', 'answer36': '', 'answer37': '', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'answer44': '', 'indoors': '', 'answer45': '', 'Sure': '', 'answer46': '', 'No': '', 'answer47': '', 'Spring': '', 'answer48': '', 'Female': '', 'answer49': '', 72: ',', 'answer50': '', 2: ',', 'answer51': '', 'equivalent': '', 'answer52': '', 'Retired': '', 'answer53': '', 25: 0, 'answer54': '', 'Macon': '', 'answer55': '', 'Georgia': ''}, {'traits': '', 60: '', 'answer1': '', 4: ',', 'answer2': '', 'Collie': '', 'answer3': '', 45: ',', 'answer4': '', 'Shep': '', 'answer5': '', 'sheepdog': '', 'answer6': '', 'Sheppy': '', 'answer7': '', 2020: ',', 'answer8': '', 'yes': '', 'answer9': '', 5: ',', 'answer10': '', 'protective': '', 'answer11': '', 'must': '', 'answer12': '', 'answer13': '', 'companion': '', 'answer14': '', 'play': '', 'answer15': '', 'months': '', 'answer16': '', 10: '', ',': 'answer18', ':': 1300, 'answer19': '', 'answer20': '', 55: '', 'answer21': '', 110: ',', 'answer22': '', 'March': '', 'answer23': '', 'Weekly': '', 'answer24': '', 'food': '', 'answer25': '', 'brand': '', 'answer26': '', 'answer27': '', 'answer28': '', 'answer29': '', 3: ',', 'answer30': '', 'answer31': '', 'answer32': '', 2: ',', 'answer33': '', 'Acana': '', 'answer34': '', 'formula': '', 'answer35': '', 'answer36': '', 'answer37': '', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'change': '', 'answer44': '', 'outside': '', 'answer45': '', 'No': '', 'answer46': '', 'answer47': '', 'Spring': '', 'answer48': '', 'Female': '', 'answer49': '', 67: ',', 'answer50': '', 1: ',', 'answer51': '', 'degree': '', 'answer52': '', 'part-time': '', 'answer53': '', 25: 0, 49: 999, 'answer54': '', 'Topeka': '', 'answer55': '', 'Kansas': ''}, {'traits': '', 60: '', 'answer1': '', 10: ',', 'answer2': '', 'Chihuahua': '', 'answer3': '', 5: ',', 'answer4': '', 'Tiny': '', 'answer5': '', 'size': '', 'answer6': '', 'T': '', 'answer7': '', 2020: ',', 'answer8': '', 'yes': '', 'answer9': '', 24: ',', 'answer10': '', 'sassiness': '', 'answer11': '', 'fiercely': '', 'answer12': '', 'answer13': '', 'Friend': '', 'answer14': '', 'shadow': '', 'answer15': '', 'days': '', 'answer16': '', 14: 'she curls up in the bed under the window', ',': 'answer18', ':': 550, 'answer19': '', 40: '', 'answer20': '', 30: '', 'answer21': '', 50: 0, 'answer22': '', 'March': '', 'answer23': '', 'Bi-weekly': '', 'answer24': '', 'Mix': '', 'answer25': '', 'brand': '', 'answer26': '', 'answer27': '', 'answer28': '', 'answer29': '', 2: ',', 'answer30': '', 'answer31': '', 'answer32': '', 1: ',', 'answer33': '', 'Cesar': '', 'answer34': '', 'store': '', 'answer35': '', 'answer36': '', 'answer37': '', 4: ',', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'change': '', 'answer44': '', 'influence': '', 'answer45': '', 'Yes': '', 'answer46': '', 'answer47': '', 'Car': '', 'answer48': '', 'Female': '', 'answer49': '', 69: ',', 'answer50': '', 'answer51': '', 'degree': '', 'answer52': '', 'Retired': '', 'answer53': '', 74: 999, 'answer54': '', 'Paso': '', 'answer55': '', 'Texas': ''}, {'traits': '', 60: '', 'answer1': '', 6: ',', 'answer2': '', 'Bulldog': '', 'answer3': '', 50: ',', 'answer4': '', 'Winston': '', 'answer5': '', 'demeanor': '', 'answer6': '', 'Win': '', 'answer7': '', 2020: ',', 'answer8': '', 'no': '', 'answer9': '', 3: ',', 'answer10': '', 'character': '', 'answer11': '', 'patient': '', 'answer12': '', 5: ',', 'answer13': '', 'Member': '', 'answer14': '', 'pet': '', 'answer15': '', 'so': '', 'answer16': '', 12: 'sprawled across the hallway rug', ',': 'answer18', ':': 1100, 'answer19': '', 15: '', 'answer20': '', 45: '', 'answer21': '', 90: ',', 'answer22': '', 'March': '', 'answer23': '', 'Monthly': '', 'answer24': '', 'food': '', 'answer25': '', 'brand': '', 'answer26': '', 4: ',', 'answer27': '', 2: ',', 'answer28': '', 'answer29': '', 'answer30': '', 'answer31': '', 'answer32': '', 'answer33': '', 'Nutro': '', 'answer34': '', 'preference': '', 'answer35': '', 'answer36': '', 'answer37': '', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'less': '', 'answer44': '', 'independent': '', 'answer45': '', 'Sure': '', 'answer46': '', 'No': '', 'answer47': '', 'Spring': '', 'answer48': '', 'Female': '', 'answer49': '', 65: ',', 'answer50': '', 'answer51': '', 'degree': '', 'answer52': '', 'Retired': '', 'answer53': '', 'say': '', 'answer54': '', 'Charleston': '', 'answer55': '', 'Carolina': ''}, {'traits': '', 60: ',', 'answer1': '', 8: ',', 'answer2': '', 'Tzu': '', 'answer3': '', 12: ',', 'answer4': '', 'Gizmo': '', 'answer5': '', 'nature': '', 'answer6': '', 'Gizzy': '', 'answer7': '', 2020: ',', 'answer8': '', 'yes': '', 'answer9': '', 'answer10': '', 'fluffball': '', 'answer11': '', 'socializing': '', 'answer12': '', 5: ',', 'answer13': '', 'Friend': '', 'answer14': '', 'bond': '', 'answer15': '', 'praise': '', 'answer16': '', 15: 'on his favorite armchair', ',': 'answer18', ':': 950, 'answer19': '', 10: '', 'answer20': '', 55: '', 'answer21': '', 80: ',', 'answer22': '', 'March': '', 'answer23': '', 'Monthly': '', 'answer24': '', 'food': '', 'answer25': '', 'brand': '', 'answer26': '', 'answer27': '', 4: ',', 'answer28': '', 'answer29': '', 3: ',', 'answer30': '', 'answer31': '', 1: ',', 'answer32': '', 'answer33': '', 'Diet': '', 'answer34': '', 'find': '', 'answer35': '', 'answer36': '', 'answer37': '', 'answer38': '', 'answer39': '', 'answer40': '', 'answer41': '', 'answer42': '', 'answer43': '', 'change': '', 'answer44': '', 'routine': '', 'answer45': '', 'Yes': '', 'answer46': '', 'Sure': '', 'answer47': '', 'Spring': '', 'answer48': '', 'Female': '', 'answer49': '', 64: ',', 'answer50': '', 'answer51': '', 'degree': '', 'answer52': '', 'full-time': '', 'answer53': '', 50: 0, 74: 999, 'answer54': '', 'Reno': '', 'answer55': '', 'Nevada': ''}, {'traits': '', 60: '', 'answer1': '', 1: ',', 'answer2': '', 'Shepherd': '', 'answer3': '', 30: ',', 'answer4': '', 'Blue': '', 'answer5': '', 'eyes': '', 'answer6': '', 'Boo': '', 'answer7': '', 2020: ',', 'answer8': '', 'no': '', 'answer9': '', 2: ',', 'answer10': '', 'energy': '', 'answer11': '', 'purpose': '', 'answer12': '', 5: ',', 'answer13': '', 'companion': '', 'answer14': '', 'support': '', 'answer15': '', 'weeks': '', 'answer16': '', 14: 'on a runner in the hall', ',': 'answer18', ':': 1000, 'answer19': '', 'answer20': '', 65: '', 'answer21': '', 85: ',', 'answer22': '', 'March': '', 'answer23': '', 'Weekly': '', 'answer24': '', 'food': '', 'answer25': '', 'brand': '', 'answer26': '', 'answer27': '', 3: ',', 'answer28': '', 'answer29': '', 4: ',', 'answer30': '', 'answer31': '', 'answer32': '', 'answer33': '', 'Wild': '', 'answer34': '', 'amazing': '', 'answer35': '', 'answer36': '', 'answer37': '', 'answer38': '', 'answer39': ''}]

that's a super weird return value with those double double quotes, I will look into it. Do you know by any chance why the output is formatted like that?

that's a super weird return value with those double double quotes, I will look into it. Do you know by any chance why the output is formatted like that?

This is extracted from AIMessage returned from Langchain. I tried to use my custom parser instead of parsers provided by Langchain because they were not able to handle broken JSONs.

I have released 0.12.0 to support this format, let me know if it works for you as it passed all tests for me

I have released 0.12.0 to support this format, let me know if it works for you as it passed all tests for me

Thank you for this quick fix. I will check it and let you know in any case of failure with new similar data.

Hi @mangiucugna,
Thank you for your efforts on this. I've encountered a similar issue with the output from the LLM. It seems that the repair_json function isn't handling certain cases correctly.
For instance, when trying to repair the following JSON string:
json_str = '{\n"html": "<h3 id="title">Waarom meer dan 200 Technical Experts - "Passie voor techniek"?</h3>"}'
data = repair_json(json_str, return_objects=True)

The current output is:
{
    u'html': u'<h3 id=',
    u'techniek': u'h3>',
    u'title': u'Waarom meer dan 200 Technical Experts - '
}

However, the expected output should be:
{
    'html': '<h3 id="title">Waarom meer dan 200 Technical Experts - "Passie voor techniek"?</h3>'
}

It seems like the function is having trouble handling certain characters or nested structures properly. Would you mind looking into this further?
Thank you again for your attention to this matter.

Hi @nikolaysm can you open a new issue for that? The issue is with the fact that the right format is  so I am not 100% sure I can support this use case but is definitely a distinct use case from this issue


racy tests TestRunContainerWithRmFlagExitCodeNotEqualToZero TestRunContainerWithRmFlagCannotStartContainer

--- FAIL: TestRunContainerWithRmFlagExitCodeNotEqualToZero (0.65s)
	docker_cli_run_test.go:3414: Expected not to have containers b236c1619dcc

--- FAIL: TestRunContainerWithRmFlagCannotStartContainer (0.51s)
	docker_cli_run_test.go:3435: Expected not to have containers b236c1619dcc

on overlay specifically
see https://jenkins.dockerproject.com/job/Docker Master (overlay on overlay)/132/console

bonus points:
--- FAIL: TestPsListContainers (2.06s)
	docker_cli_ps_test.go:59: Container list is not in the correct order
	docker_cli_ps_test.go:128: Container list is not in the correct order
	docker_cli_ps_test.go:138: Container list is not in the correct order
[PASSED]: ps - test ps size
[PASSED]: ps - test ps filter status
[PASSED]: ps - test ps filter id
[PASSED]: ps - test ps filter name
[PASSED]: ps - test ps filter label
--- FAIL: TestPsListContainersFilterExited (2.33s)
	docker_cli_ps_test.go:535: Should be 2 zero exited containerst got 3

also see #11959

#dibs this one is mine

@jfrazelle looks like @runcom was working on this in https://github.com/docker/docker/issues/11973. Can you check with him and close that PR?

ya no worries im taking on the others and ill see if his works for the one he fixed :)


Missing modules & installation issues

Required Info

Camera Model
{ D435 }

Firmware Version

Operating System & Version
Ubuntu 20.04.4 LTS

Kernel Version (Linux Only)
5.17

Platform
PC

SDK Version
2.50 }

Language
{}

Segment
{ }

Issue Description
I currently am trying to install the SDK in a docker container that is running Ubuntu 20.04.4 with the kernel version of 5.17. This docker container contains another SDK that I also need for my application. I am running into a couple of issues when following the main installation guidelines (using the package managers).

I understand that this issue is due to 5.17 not being supported, but how can I go about resolving it and ensuring that the modules are loaded into the kernel.
Thanks!

Hi @agangavaram  If you are unable to change your kernel version due to elements of your project that depend on 5.17 then you could consider the possibility of building the librealsense SDK from source code with CMake using the RSUSB backend installation method.
An RSUSB build bypasses the kernel and so is not dependent on Linux versions or kernel versions and does not require patching.
If you do not need to install additional wrappers for librealsense such as pyrealsense2 then the simple source code build method in the link below would be recommendable to try first.
https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

Thank you so much for responding so quickly! I'm trying to integrate the RealSense camera with NVIDIAs Deepstream SDK i.e. have the RealSense camera be a source for a GStreamer pipeline.
My existing application runs in a Docker container which is based on the NVIDIA Deepstream image. I have a couple of questions regarding the integration between RealSense and other docker containers.

Is the SDK absolutely necessary to be able to use the RealSense camera in the way that I have described?
If I want my end Docker container to be as lightweight and flexible as possible, should I use the RSUSB build/the source code build method in the link that you sent?

The reason I am asking is because the libuvc installation and build has been taking quite some time, and I want to make my end docker build as fast as possible. Thanks again!

Additionally, on completion of installation I am receiving the following error when I try rs-enumerate-devices.

Typically, if you plan to stream depth then the RealSense SDK is going to need to be involved.

If you are only streaming RGB then RealSense cameras can be accessed like ordinary webcams.
The link below has a RealSense plugin for GStreamer that can stream depth and color, align them and stream depth only or color only if you wish.
https://github.com/WKDSMRT/realsense-gstreamer

When building from source code with CMake, you can significantly reduce the build size by stripping out debug symbols using the information at https://github.com/IntelRealSense/librealsense/issues/7982

Also, when building from source you can use a -jx command to accelerate the build time by allowing the process to make use of the CPU's number of cores.
The 'x' of -jx to use will depend on how many threads the CPU of the computer that you are building on has.  The thread number is 2x the number of cores.  So an appropriate j-number to use on a 4-core (quad core) CPU would be -j8 whilst on a higher-end CPU with 8 or more cores you could use -j16
More information about 'make -jx' values is at the source-code installation documentation link below.  -j8 is a good value to use though.
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md#building-librealsense2-sdk

The Failed to set power state error can indicate that there was a problem with accessing the camera, either because it could not be detected (perhaps because of insufficient power supplied to it) or another application has already accessed the camera and is actively using it, putting the camera in a 'busy' state.

@MartyG-RealSense Thank you once again! I have looked into the RealSense plugin, and plan to use it. The build optimizations are also extremely helpful!
As for the Failed to set power state, I've verified that the camera is not being accessed by any other applications. Additionally, I have tried every USB port and am still receiving the error. The camera is being detected by the v4l2 utility, so I am not sure how to resolve this problem. I appreciate all your help in this matter!

Thanks again for your patience as I researched this case!
The project requirement for kernel 5.17 creates challenges for installing librealsense, as we cannot install from Debian packages (as the most recent kernel supported by the packages is 5.4) and the most recent kernel supported for a source code build is 5.15 (via the unofficial test patch).
The librealsense SDK can work with unsupported kernels, though there may be unpredictable consequences in regard to stability.
Would it be possible to test whether the other SDK that you have installed can work with kernel 5.15?  That may simplify things by allowing the RealSense SDK's new 5.15-supporting kernel patch to be applied.  Given that your camera can be detected by the V4L2 utility, building the SDK from source code with RSUSB = false (also known as the V4L2 backend) may increase the chances of the camera being detected.
Another option would be to try a source code build with the RSUSB backend that is not dependent on the kernel.  The libuvc backend installation script that you tried earlier is actually the direct predecessor of the RSUSB method.  Although they work similarly in principle, it may be a good idea to try the actual modern RSUSB procedure to confirm whether or not RSUSB can work with your Docker container.  Instructions for an RSUSB build can be found at https://github.com/IntelRealSense/librealsense/issues/9931#issuecomment-964289692
Thanks again!

@MartyG-RealSense. I switched to the 5.15 kernel and built the SDK from source code with RSUSB = false, and rs-enumerate-devices is able to detect the camera! However, when I try to open realsense-viewer from the command line, I get no response from the terminal. I want to ensure the firmware is updated in the camera and view the camera in realsense-viewer.

What could be causing this?

If the flags -dbuild_examples=true -dbuild_graphical_examples=true were included in the CMake build instruction then graphics support and built executable versions of graphical examples and tools such as realsense-viewer should be included in the build.in the usr/local/bin location referenced in the image above after youni out the whereis query.

Ok makes sense, everything works on the RealSense side - I just want to understand a few things.
Does the RealSense SDK use the uvc API or the v4l2 API? How does the SDK work on the lowest level? Additonally, does the viewer communicate with uvc or v4l2? My feed looks good through the viewer, but when using a GStreamer pipeline, the colors are distorted. Additionally, I'm running into errors when trying to update firmware through the viewer. I suspect that this has to do with running the viewer in the docker container, and the lack of direct interface between the container and the RealSense camera.
Again, thank you for all your help! I'd love to learn more about how the RealSense SDK works.

RealSense 400 Series cameras are compliant with UVC 1.5, as advised at https://github.com/IntelRealSense/librealsense/issues/3416#issuecomment-471720605

On Linux, V4L2 is the default backend of the librealsense SDK.  More information about V4L2 vs RSUSB can be found at https://github.com/IntelRealSense/librealsense/issues/7904

On Windows, Microsoft Media Foundation is the default backend and building the Windows version of the SDK from source code with the RSUSB backend set to true will configure librealsense to use a Windows backend based on a WinUSB rewrite of the UVC protocol instead of Media Foundation.
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_windows.md

As mentioned above, standard Linux tools can access the camera when the SDK is built for the V4L2 backend, though https://github.com/IntelRealSense/librealsense/issues/6841#issuecomment-660859774 advises that the results may not be nicely colorized.

The SDK has a Low-Level Device API that can provide direct access to the camera sensor hardware.  RealSense SDK programs typically run in the High-Level Pipeline API.

https://dev.intelrealsense.com/docs/api-architecture

Another RealSense user at https://github.com/IntelRealSense/librealsense/issues/4652 also had problems with updating firmware from within a Docker container.  They were advised that it may be possible to do so on an RSUSB = true build.  In your particular situation, it may be easier to update outside of Docker.

The firmware driver is stored inside the camera hardware and not on the computer, so you can update on another computer (even a Windows one) and the firmware driver will be carried within the camera to whatever computer you attach it to.

My host machine is running Fedora 35, and I installed the realsense SDK through rpm. I am able to get the viewer up and running, but when I try to install the firmware, I run into the same error, null pointer passed for argument, "device."
Thank you for the different resources you sent me. From what I understand, there are 2 ways of building the SDK - using a package manager and the manual build. Through the package manager, the SDK will have a V4L2 backend and requires patching of the kernels. This is impossible in a Docker container because of the lack of access to kernel space. However, the manual build allows for the SDK to be built with the RSUSB backend which lives entirely in user space.
My goal application requires everything to be in a Docker container - so I'm trying to understand the best build for this method. Why does setting RSUSB=false, and using a V4L2 backend work in the container?
Thank you

A package build of librealsense is usually based on V4L2, yes.
However, at https://github.com/IntelRealSense/realsense-ros/issues/1515#issuecomment-744223832 the developer of the RealSense ROS1 wrapper advised that from December 2020 onwards, building librealsense and the RealSense ROS wrapper together at the same time from packages with the 'Method 1' installation process using the apt-get command installs a package version of librealsense2 that uses RSUSB instead of V4L.  So if you needed an RSUSB-based librealsense package build then that could be a route to consider if you do not mind having the ROS wrapper sitting unused on your computer.
Intel's official Docker guide for librealsense 2.50.0 and Ubuntu 20.04 does not make mention of V4L2 or RSUSB.  Instead, it takes the approach of pulling a pre-built librealsense Docker saved in Docker Hub.
https://github.com/IntelRealSense/librealsense/tree/master/scripts/Docker
I am not familiar enough with Docker or Fedora to offer in-depth advice about those subjects though unfortunately.

Hi @agangavaram  Do you require further assistance with this case, please? Thanks!

I was able to resolve the issues! Thanks!

That's excellent news, @agangavaram - thanks very much for the update. :)


ESP32C6 Wifi API with cmake project

Hello, I am using esp32c6 with IDF 5.2.2. I followed the following cmake build tutorial :
https://github.com/esp-rs/esp-idf-template/blob/master/README-cmake.md
However, I cannot access wifi libraries. I get the following compile error:
103 | pub mod wifi;
    |         ^^^^
note: the item is gated here    |
97  | / #[cfg(all(
98  | |     not(esp32h2),
99  | |     feature = "alloc",
100 | |     esp_idf_comp_esp_wifi_enabled,
101 | |     esp_idf_comp_esp_event_enabled,
102 | | ))]

I saw soluiton in https://github.com/esp-rs/esp-idf-svc/issues/307 but it does not seem to apply to cmake based projects. Any help would be kindly appreciated.

Did you read and do this?

Did you read and do this?

Yes, my list of components is the following:
set(RUST_DEPS "pthread" "driver" "vfs" "esp_http_client" "esp_http_server" "espcoredump" "nvs_flash" "spi_flash" "mqtt")

with app_update did not even compile, but thats a story for another issue.

Did you read and do this?

Yes, my list of components is the following:
set(RUST_DEPS "pthread" "driver" "vfs" "esp_http_client" "esp_http_server" "espcoredump" "nvs_flash" "spi_flash" "mqtt")

with app_update did not even compile, but thats a story for another issue.

Have you tried putting esp_wifi in that list?

Thank you for your help. The following list of dependencies was needed to get basic wifi example working:
"esp_wifi" "esp_event" "wpa_supplicant" "esp_netif" "lwip"
As for app_update, bootloader_support  was needed as well.

Yes. These components weren't necessary in the 4.4. days, probably because they were enabled by the others. With esp idf 5 the situation might had changed, but the approach remains the same.


Consolidate all URL conversion code in one packge.

Remove from domain packages, it will continue to be useful temporarilly but long term will be replaced by console logic


SUS-1126 Change log formatting / add timestamp

SUS-1126 @macbre @bognix

it turns out that it's enough to set one flag to true to get the timestamp and the whole formatter function is redundant :D


Multiple search fields cause the same constant name to be used

When providing multiple search fields via isSearchField = true the constants file is coming up with a search static string called
BY_CODE for each one and it is not unique this should be the name of the field BY_SEARCHFIELD_NAME

already implemented.


Scala Aspect tests find the wrong filename for source jars.

In com.google.idea.blaze.aspect.scala.scalalibrary.ScalaLibraryTest.testScalaLibrary(), there is a test that loads a test fixture based on the code in the aspect.scala.scalalibrary aspect test.
Right now, the code looks like this:
    assertThat(target.getJavaIdeInfo().getJarsList().get(0).getJar().getRelativePath())
        .isEqualTo(testRelative("simple.jar"));
    // Also contains ijars for scala-library.
    // Also contains jars + srcjars for liblibrary.

If we change the code to match the Java implementation (and actually match the ijar and -src.jar, it will fail:
    assertThat(
            target.getJavaIdeInfo().getJarsList().stream()
                .map(IntellijAspectTest::libraryArtifactToString)
                .collect(toList()))
          .containsExactly(
            jarString(
                    testRelative("simple.jar"),
                    testRelative("simple-ijar.jar"),
                    testRelative("simple-src.jar")));

difflib/DiffUtils
java.lang.NoClassDefFoundError:
	at com.google.common.truth.Platform.makeDiff(Platform.java:82)
	at com.google.common.truth.ComparisonFailureWithFacts.formatExpectedAndActual(ComparisonFailureWithFacts.java:102)
	at com.google.common.truth.ComparisonFailureWithFacts.makeFacts(ComparisonFailureWithFacts.java:81)
	at com.google.common.truth.ComparisonFailureWithFacts.create(ComparisonFailureWithFacts.java:49)
	at com.google.common.truth.FailureMetadata.failEqualityCheck(FailureMetadata.java:179)
	at com.google.common.truth.Subject.failEqualityCheck(Subject.java:913)
	at com.google.common.truth.Subject.failEqualityCheckForEqualsWithoutDescription(Subject.java:867)
	at com.google.common.truth.IterableSubject.containsExactlyElementsIn(IterableSubject.java:437)
	at com.google.common.truth.IterableSubject.containsExactly(IterableSubject.java:360)
	at com.google.idea.blaze.aspect.scala.scalalibrary.ScalaLibraryTest.testScalaLibrary(ScalaLibraryTest.java:52)
        ...

Debugging reveals that the actual name it finds for a source jar is "simple.-src.jar", with an extra period in the wrong place.  And, indeed, if I change the last line to this, it passes:
                    testRelative("simple.-src.jar")));

This makes me think that there's a deeper bug in the way that the aspect is looking for scala source files.

Hello @BillyAutrey, Can you provide the example used in testing the above issue.

Yeah, I described exactly what I did above.
Here's the line as it exists today:
https://github.com/bazelbuild/intellij/blob/68bc3a7e12181ecc36d557db9379111841aa5192/aspect/testing/tests/src/com/google/idea/blaze/aspect/scala/scalalibrary/ScalaLibraryTest.java#L43
And here's the Java version of the same assertion:
https://github.com/bazelbuild/intellij/blob/68bc3a7e12181ecc36d557db9379111841aa5192/aspect/testing/tests/src/com/google/idea/blaze/aspect/java/javalibrary/JavaLibraryTest.java#L91
If you change the Scala code (in the first link) to match, like so:
    assertThat(
            target.getJavaIdeInfo().getJarsList().stream()
                .map(IntellijAspectTest::libraryArtifactToString)
                .collect(toList()))
          .containsExactly(
            jarString(
                    testRelative("simple.jar"),
                    testRelative("simple-ijar.jar"),
                    testRelative("simple-src.jar")));

This will fail, as described in my initial comment.

@BillyAutrey how did you get to this issue? Are you looking for source attachment to external jars? If yes, there are number of fixes that need to be made to get it working. I have a fork with a working implementation, but it will take some time to turn those changes into contributions to official plugin codebase. https://github.com/wix-playground/intellij/tree/scala-attach-sources

@liucijus yeah that's where we were headed.  We actually got Scala sources to attach with some very minor changes, I couldn't get your changes to work in the default bazel code base.

@liucijus yeah that's where we were headed. We actually got Scala sources to attach with some very minor changes, I couldn't get your changes to work in the default bazel code base.

@BillyAutrey I have opened #4108 as an overview of all issues. If there are more case you're aware I would love to hear about them (repro would be more than appreciated).


don't use eventName as parameter and variable

Using $eventName for both as function parameter and in the use statement will fail on PHP 7.1 with a message like "Cannot use lexical variable $eventName as a parameter name" (see symfony/symfony-installer#237).
There also is a test in the test suite for PHP 7.1 ensuring that such a fatal error is triggered: https://github.com/php/php-src/blob/master/Zend/tests/closure_use_parameter_name.phpt

It seems like having the $eventName parameters in the original code was probably a mistake anyway.

This fix seems to be present in the 5.3.1 release only:
$ git tag --contains fcae91ff31de41e312fe113ec3acbcda31b2622e
5.3.1

Shouldn't it be also merged to 6.x?

Guzzle 6 is middleware based, there are no events anymore.

I see, thanks!


how to load mapviz in rqt

rivz can be loaded into rqt framework, but I haven't yet load mapviz into rqt.
Is it possible to use the mapviz in rqt like using rviz in rqt?

Yes; if you've got mapviz installed, it should appear under Plugins / Visualization / Mapviz:

If you're sure you've got it installed but don't see it, try running rqt --force-discover, which will force rqt to re-scan its plugin paths.


Create developer guidance documentation for resolving prebuilts

Overview
In .NET 8.0, repo level prebuilt detection will be enabled.  A prerequisite for this is to have documentation that provides the following guidance for repo developers:

Explanation of what prebuilts are.
Overview of how prebuilt detection works.
Action guide on how to eliminate prebuilts - e.g. use a source-build version if it exists, utilize SBRP, a prebuilt to source-build graph, etc.
FAQ

A natural home for this documentation would be in the source-build repo documentation.
The Action Guide should be tested by enabling prebuilt detection on a couple repos by devs with various source-build knowledge to ensure its completeness.
Additional pointers

Small/simple repositories to start with: sourcelink, xdt, xliff-tasks
Example documentation for similar purposes: Migration to Main

utilize SBRP

Instructions on SBRP should be referencing the currently developed tooling, correct? (the one by @andriipatsula )

Yes - but are the instructions going to change with the new tooling?  I was expecting it to be abstracted away by the generate tooling.

Yes - but are the instructions going to change with the new tooling? I was expecting it to be abstracted away by the generate tooling.

In terms of instructions to create a ref pack - they should not. However, I would expect there to be a link to documentation on known issues of the new tooling since repo owners might run into problems with new packages. And that would be created based on the new tooling.

Also, is there any existing documentation outside the linked source-build repo documentation and other SB repo's docs, such as for SBRP and SB externals?

Also, is there any existing documentation outside the linked source-build repo documentation and other SB repo's docs, such as for SBRP and SB externals?

No

Potential content:

Pre-builds - introduction to what pre-builds are, how we detect them and why do we need them removed from the build
Step-by-step guide for enabling detection - guidance on setting up pre-build detection in a given repository (editing Version.Details.xml, SourceBuildPrebuildDetectionBaseline.xml, etc)
Eliminating pre-builds - a flow of questions / answers after which the reader should be able to eliminate a pre-build

understanding the type of dependency that is being used as a pre-build (direct, indirect, dangling)
verifying if the dependency is already being source-build (a simple pointer to the result of https://github.com/dotnet/source-build/issues/1319 should suffice)
resolving any potential issue if it is source-build but cannot be used directly (ex.: bumping version to latest, creating SBRP package for the pinned version, etc)
checking if SBRP or text-only could be used (just a general introduction, for any issues during generation of the packs a pointer to a different doc should be used)
adding a dependency to source-build (pointer to https://github.com/dotnet/source-build/blob/main/Documentation/sourcebuild-in-repos/new-dependencies.md can be used)

FAQ
Contacts

Draft PR for the doc -> https://github.com/dotnet/source-build/pull/3083

Suggestion for the documentation visibility - links to the docs should be added to places where the user will most likely interact with pre-build detection. This should include:

header of SourceBuildPreBuildBaseline.xml and generated-baseline.xml files
error message for pre-build detection -> most likely the main way repository owners / contributors will interact with pre-build detection, so an easy actionable step like reading the docs would be of great help in that case

Update on progress: will have the PR docs merged + implement the documentation visibility points mentioned above by 25th November EoD


Fix issue: 17138

An imprecision of 1e-7 is to be expected when working in float32 precision. We should not add extraneous ops such as clip to enforce artificial value ranges like this, because that adds computation overhead for everyone.
Here are some thing you can do:

If you critically need to enforce a specific value range, move the clip op to your own application.
Use float64 precision to reduce numerical imprecision.


Decide on versioning strategy

We could follow semver, but maybe a minor bump is justified when we bump the flink version.
Or we could be releasing artifacts including a flink version since it's quite fundamental. Like maybe we should be releasing an x.y.z-1.20 tag. So the project maven version could follow the semver of the flink-sql job API and we use the flink version tag to show what flink version we're building against.

I think a minor version bump on the semver for a flink change is ok.
I think we should probably just leave it as semver and have a compatibility matrix in the README. It is likely that in future more compatibility variables turn up (Kafka, Kubernetes, etc) so keeping them in a table rather than the main version makes sense.


Expose cost estimation values

Summary
Adding a new property, job.cost_estimation which returns
{'estimated_running_time_seconds': 3.9895985801416742,
 'estimated_max_running_time_seconds': 59.84397870212511}

Details and comments
fixes #681

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 7 (42.86%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 51.483%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_provider/job/ibm_circuit_job.py
3
7
42.86%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
3177

Relevant Lines:
6171

💛  - Coveralls


CB-1926: Update blueprint for SDX-HA lite using cardinality.

Used cardinality to create lite SDX HA cluster following the lines of blueprint for medium SDX HA.
Verified the changed by creating an SDX cluster in Manowar-int using it.
This is a continuation of https://github.com/hortonworks/cloudbreak/pull/5354. It took a while to get back to it. This pull request address the comment you had there.

Thanks @kkalvagadda

Thanks @adoroszlai


Resolves #5896 - Add new Data Engineering Sub

Finally I made a new Data Engineering Sub, because the are Data Science and Machine Learning. I think Data Engineering could be one new Sub
Resolves #5896
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

add these in Data Science. If you can tell the difference, write a book about it and we'll add it!


Add HTML polyglot support, resolves #17

@basicdays can you please rebase this on master and push? I've merged it but it won't show until you push I think.

Never mind :)


Regular meeting?

Should we organize a regular meeting for those of us interested in this?

@dgrisham is interested in doing work around Bitswap, measurements, deploying new agents, etc.
@whyrusleeping @diasdavid and @jbenet have been meaning to do this for ages.
@nicola is probably very interested too
new work on the test-lab will make this much more possible
js-ipfs working could help us deploy tests through the browser to 10,000s of people
new work on Filecoin will make it much more relevant (TBA in coming months)
Unfort. this is low priority for me until May/June, so i dont think i can swing more than 20min weekly, or 40min bi-weekly.

cc @dgrisham @whyrusleeping @nicola

//cc @pgte who might be interested in partaking in this research too :)

Hey everyone --
I'm specifically interested in this resource for my master's thesis, so I'm definitely going to be working on it. I think a call could be a great way for me to get some of your thoughts and bounce my own off of you. I know many of you may be busy, so it could be as simple as a 20 min call a week if that's all you want to commit.
In the case that you're interested in doing a bit more with this (or just want more details), my current game plan is to get a good simulation test bed together for investigating Bitswap strategies. I don't have hard details on this right now, but a good place to start would be the first issue Juan posted. At a higher level, the loose goals involve determining how certain strategies perform and whether they're resistant to certain types of attacks, as well as the general feasibility of sybil attacks/freeriders/etc.

Happy to join, unfortunately will be busy until May :(

For everyone still interested in this, I'd love to get your feedback on this: https://github.com/ipfs/go-ipfs/pull/3982 (be sure to read my comment at the end of the page titled 'Update: Alternative Implementation Idea', which is a bit different from what's presented in the OP). @jbenet @nicola @diasdavid

Hey all -- is there interest in a regular meeting at this point? Know @jbenet will be too busy until at least mid-July, but I'd be happy to catch anyone up on what's happened/the current plan. The current state of this is something like:
Theory: Model reciprocative Bitswap strategies using evolutionary game theory (EGT). See the 'P2P Soft Security' paper here for the inspiration for this idea. There's still reading to do (of other papers using EGT for similar purposes) along with work to come up with our own EGT model that best matches what we have in Bitswap (balanced against computational feasibility).
Implementation: Test various strategies using the IPTL and find best way(s) to connect to the EGT model. This involves implementing strategies into Bitswap as well as adding features to https://github.com/ipfs/kubernetes-ipfs/ that will act as a simulation test bed.
cc @whyrusleeping @nicola @diasdavid @pgte

cc @lgierth, who loves bitswap

cc @mafintosh who has showed interested multiple times in Bitswap :)

@jbenet: @miyazano and I are going to meet on a call tomorrow to discuss the applicability of the mathematical methods in the Game Theory and Topological Phase Transition paper (second link here https://github.com/ipfs/research-bitswap/issues/2#issuecomment-324150508), will you be available to join? We're planning on doing it at 21:00 UTC (same time you and I had our schedule meeting in the past).
Everyone else is welcome as well :) Don't feel like you have to read/understand that entire paper, I'm only around section 4 myself. We just want to start a discussion as to whether the methods make sense for a Bitswap model. Feel free to just come and listen in!

hey @dgrisham add it to ipfs/pm maybe? other people might be interested to join! :)

@nicola Good thinking, will do :)

@dgrisham @miyazono managed to update the community calendar and added the research-bitswap call
See it here<EMAIL_ADDRESS>Also created a recurring zoom url -- https://protocol.zoom.us/j/959863667 -- that you can find on the calendar invite


Integrate CurateND search functionality

Work Completed

Implement CurateND search functionality.
Note: Tests will need to be made and updated once we point to Curate's prod servers.

Steps Required

N/A

Combine curate get_user_resources with search if feeling spunky. Update items docstring. Nice job!!

Done!


Timeout response added

Added response for run.py when submission is timeout.

@recluze Kindly review the updated grader.py