How to add context_extensions for ext-auth grpc

I use the ext-auth grpc to auth + authz for my service. But it need to some custom data. How can I push that data into ext-auth via header or context_extensions
Example.
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: SecurityPolicy
metadata:
  name: ext-auth-example
spec:
  targetRef:
    group: gateway.networking.k8s.io
    kind: HTTPRoute
    name: myapp
  extAuth:
    grpc:
      backendRef:
        name: grpc-ext-auth
        port: 9002
     headersForAuth:
       - x-user: abc
       - x-product-id: 123
       - x-provider: um

or
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: SecurityPolicy
metadata:
  name: ext-auth-example
spec:
  targetRef:
    group: gateway.networking.k8s.io
    kind: HTTPRoute
    name: myapp
  extAuth:
    grpc:
      backendRef:
        name: grpc-ext-auth
        port: 9002
     contextExtensions:
       - x-user: abc
       - x-product-id: 123
       - x-provider: um

in the above example is x-user part of the request header ?

in the above example is x-user part of the request header ?
@arkodg
It is not part of the title. It's just a custom field that I want the envoy to send to the ext-auth as additional information.

@quyenhoang96 this should be possible with earlyRequestHeaders https://gateway.envoyproxy.io/latest/tasks/traffic/http-request-headers/#early-header-modification
dup of https://github.com/envoyproxy/gateway/issues/4267


Discussion: Breaking Change: SPWebApp... parameters are not consistent: WebAppUrl vs. Url vs. WebApplication

Details of the scenario you try and problem that is occurring:
In a recent customer engagement I stumbled about some inconsistency about the naming of the WebAppUrl, URL and WebApplication parameter in the SPWebApp... Resources.
The WebAppUrl, Url or WebApplication are parameter (keys) for these resources:

Resource
WebAppUrl
Url
WebApplication

MSFT_SPWebAppAuthentication
x
-
-

MSFT_SPWebAppBlockedFileTypes
-
x
-

MSFT_SPWebAppGeneralSettings
-
x
-

MSFT_SPWebAppPeoplePickerSettings
x
-
-

MSFT_SPWebAppPermissions
x
-
-

MSFT_SPWebAppPolicy
x
-
-

MSFT_SPWebAppProxyGroup
x
-
-

MSFT_SPWebAppSiteUseAndDeletion
-
x
-

MSFT_SPWebAppSuiteBar
x
-
-

MSFT_SPWebAppThrottlingSettings
-
x
-

MSFT_SPWebAppWorkflowSettings
-
x
-

MSFT_SPWebApplication
-
x
-

MSFT_SPWebApplicationAppDomain
-
-
x

MSFT_SPWebApplicationExtension
x
-
-

Changing these parameters would be a breaking change. I just wanted to point this out and hope we will find a way on how to match these keys.
The SqlServerDsc Resource did something similar: Issue 308

@andikrueger As you pointed out, this would definitively be a breaking change. The best we can really do, is duplicate some of the params, deprecate the original ones, and when 3.0 comes out, then introduce the breaking changes. I am just not convinced that this would be worth the effort though.
I understand that the SQLServer team went through the exercise, but we've been a little more on the conservative front with SPDSC, where we only released one set of breaking changes over the past 2 years. The floor is open for discussions :)

I'm uncertain about the effort too - There are way to many parameters that need to be changed and the change would be more cosmetics, than really necessary.
Maybe we could stick with  the current mix, but should find a commitment which of the three current parameters is the one for new SPWebApp... resources.

These aren't the only resources that require the web application url:

Resource
WebAppUrl
Url
WebApplication

SPAppStoreSettings
x
-
-

SPBlobCacheSettings
x
-
-

SPCacheAccounts
x
-
-

SPContentDatabase
x
-
-

SPDesignerSettings
-
x
-

SPFarmSolution
-
-
x (WebApplications)

SPManagedPath
x
-
-

SPOutgoingEmailSettings
x
-
-

SPTimerJobState
x
-
-

I like the idea of standardizing the parameter names, but agree with Nik that we should not do this before v3.0.
If we agree on a parameter name, we can make sure that from now on any new resources would use the same name. Personally I like the name WebAppUrl. What do you think?

Implementing this change into the newly created v3.0-development branch. Changing all parameters to WebAppUrl.

Just submitted PR #824

Merged via PR 824, closing issue


Can't install

Dear community,
I am trying to use map in my react native app, but I can't install the react-native-maps package, I got an error
app.json
{
  "name": "myapp",
  "version": "1.0.7",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    ....
    "react": "^17.0.1",
    "react-native": "^0.64.2",
    "react-native-webview": "^11.6.4",
   ...
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/runtime": "^7.12.5",
    "@react-native-community/eslint-config": "^2.0.0",
    "babel-jest": "^26.6.3",
    "eslint": "7.14.0",
    "jest": "^26.6.3",
    "jetifier": "^1.6.8",
    "metro-react-native-babel-preset": "^0.64.0",
    "react-test-renderer": "17.0.1"
  },
  "jest": {
    "preset": "react-native"
  }
}

The error
$ npm i react-native-maps
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer react@">= 16.0 || < 17.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/react-native-maps
npm ERR!     react-native-maps@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
npm ERR! node_modules/react-native
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer react-native@">= 0.51" from<EMAIL_ADDRESS>npm ERR!   node_modules/react-native-maps
npm ERR!     react-native-maps@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\x\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR!      C:\Users\x\AppData\Local\npm-cache\_logs\2021-06-24T15_47_18_114Z-debug.log

what should I do ?

This issue is not related strictly to react-native-maps but because you have a new version of npm with different default values for resolving dependency versions.
To workaround this issue run: npm install react-native-mapse --legacy-peer-deps
It is mentioned in the error btw

@LadislavBohm
Thank you so much for your answer.
I installed the package successfully, but it still doesn't appear in the screen even when I did the steps as documentation.

Duplicate https://github.com/react-native-maps/react-native-maps/issues/3812

This issue is not related strictly to react-native-maps but because you have a new version of npm with different default values for resolving dependency versions. To workaround this issue run: npm install react-native-mapse --legacy-peer-deps
It is mentioned in the error btw

npm i react-native-maps --legacy-peer-deps


fix missing connectivity image on homepage tile

not sure when this crept in but due to the recent release now it's in both stable and dev sites, so I'm marking as backport candidate.

rendered docs are good, merging


Remove limits carry-over for loki

How to categorize this PR?
/area auto-scaling
/kind bug
What this PR does / why we need it:
Removes loki limit value carry-over during reconcile. After recent transition to a fixed limit for loki/loki carry-over is unnecessary and prevents the new limit from coming into effect on existing clusters, effectively establishing the cluster's current accidental limit as a permanent, fixed one.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

A bug was fixed which caused current, accidental resource limit values for the loki container of the loki component, to be established as fixed limits, in place of the correct absolute limit value.

/invite @voelzmo

/uncc

/cherry-pick release-v1.48

/approve

/lgtm
/assign @rfranzke


Javascript task does not work when using browserSync proxy

You also cannot tell blendid not to use webpack-dev-middleware to get around this so we can at least build the JS file locally.

Faced a similar issue while trying to setup additional proxy middleware in browsersync.
Apparently https://github.com/vigetlabs/blendid/pull/503 has added an option extraMiddlewares that allow us to add additional proxy middleware.
https://github.com/vigetlabs/blendid/blob/6a29c48c89372d6a0bd1a9b60342ce6d38621763/gulpfile.js/tasks/browserSync.js#L36-L44
Usage
  browserSync: {
    server: {
      extraMiddlewares: [
        proxy({
          ...url.parse('http://api-server/api'),
          route: '/api',
        }),
      ],
    },
    port: 8888,


Update for pmdarima 2.0.1 and update black

Signed-off-by: Ben Wilson<EMAIL_ADDRESS>What changes are proposed in this pull request?
Fix issue with pmdarima >=2.0.0 with Diviner.
How is this patch tested?
Existing unit tests and one additional test for pipeline validation
Does this PR change the documentation?

[X] No. You can skip the rest of this section.
[ ] Yes. Make sure the changed pages / sections render correctly by following the steps below.

Navigate to diviner/docs via the command line.
Execute make clean from the docs directory.
Execute make html from the docs directory.
Navigate to the diviner/docs/_build/html/ directory.
Open index.html in your browser and validate that your changes render correctly.

Release Notes
Is this a user-facing change?

[X] No. You can skip the rest of this section.
[ ] Yes. Give a description of this change to be included in the release notes for Diviner users.

(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s) does this PR affect?
Components

[X] area/models: Forecasting framework interfaces and associated training and prediction code for Diviner
[X] area/analysis: Ad-hoc analytic EDA functionality (i.e., trend decomposition)
[ ] area/data: Data structure transformation code
[ ] area/examples: Example code
[ ] area/serialization: Model serialization and deserialization
[X] area/utilities: Common or per-framework utility code
[ ] area/scoring: Cross validation, back-testing, and associated scoring functionality
[ ] area/docs: Diviner documentation pages

How should the PR be classified in the release notes? Choose one:

[ ] rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
[ ] rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
[ ] rn/feature - A new user-facing feature worth mentioning in the release notes
[X] rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
[ ] rn/documentation - A user-facing documentation change worth mentioning in the release notes

Fix for https://github.com/databricks/diviner/issues/14


Mechanism for letting requesters test and debug their own tasks

At present preview functionality on the drag-drop shows the task interface mockup. Enhance it to handle Preview and Debug

@neilthemathguy What should the Debug feature do?  and any modifications required to the preview feature?

pasting the reply from @mbernst  "in AMT, people have a “requester sandbox” they can push their tasks to. it’s a version of AMT with no workers on it so that you can try out your own task and make sure it works. Especially helpful if you have logic on the back end that’s trying to combine multiple workers’ actions and you need to test it. This can be simulated without a separate sandbox by letting me set a task as one that only I can do. Not high priority, just wanted to mention so that we don’t paint ourselves into a corner later."

Sandbox like functionality is very useful. Here is the MTurk  sandbox.  I think there are multiple ways to achieve this in our platform, I will add the details here. We can brainstorm around this further. For now I will flag it as a Need to be Prioritize; and we can revisit this during the refactoring.


update misleading tests for R.invert and R.invertObj

As discovered in #780, R.invert(1) and friends all evaluate to {}. Inexplicably assert.throws({}) is not a type error, so these tests test nothing. Were these tests correctly written they would fail as these expressions do not throw when evaluated. A comedy of errors. :)

I'm against this PR, because I think that test isn't just for checking if code works as expected, but it's also a live documentation. Test should be removed only if the functionality that it tests is out. Once the edge case is discovered, then it should be properly tested - someone can rely on its current behaviour.
Therefore I would change the assertions or change the current implementation - for those values it would throw an error as was intended.

I agree with @honzabrecka about the test suite being live documentation.  I'm not sure I would make the argument a general principle, but I believe it applies here.
So yes, @davidchambers, there is a comedy of errors here.  But assuming we wrapped lambdas around these expressions and started failing the tests, we have learned something.  Don't those tests properly establish the API we would want from invert[Obj]?  Shouldn't we throw an error there?  Or do you think returning an empty object is the right behavior?

Shouldn't we throw an error there? Or do you think returning an empty object is the right behavior?

The result of inverting a value not comprised of key–value pairs is unspecified. We could throw a TypeError for null/undefined, and include tests to assert this, but I don't want to decide whether new Number(42) is an invertible object. I'd like to specify the behaviour for objects, arrays, and arguments objects, include tests for these, and let the implementation determine the behaviour of the unspecified cases.

I can certainly live with leaving it the way it is.  But I think then that we should actually capture that with test.  Perhaps
it('returns an empty object when passed a primitive', function() {
     assert.equal(R.invert(42), {});
     assert.equal(R.invert('abc'), {});
});;

it('returns an empty object when passed nothing', function() {
     assert.equal(R.invert(null), {});
     assert.equal(R.invert(undefined), {});
});;

I don't feel we have to exhaustively cover all types of primitives, but a smattering for demonstration purposes would be useful.

I've updated this pull request to include the suggested tests.

Sorry, I didn't say it, but we should probably do the equivalent thing on invertObj.

[W]e should probably do the equivalent thing on invertObj.

Yes, of course. There seem to be so many things to fix today; I'm not quite my usual methodical self. Updated.

LGTM


Socket Hangup Error when Pushing over 50,000 document chunks using Langchain for NodeJS

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.

Example Code
const model = new GoogleVertexAIEmbeddings({
            onFailedAttempt: (err) => {
                logger.error(err);
            },
            location: process.env.MODEL_LOCATION,
            authOptions: {
                projectId: gcp_credentials.projectId, //for some reason I have to set projectId separately from the credentials object
                credentials: gcp_credentials,
            }
        });

const config = get_config();

const pgvectorStore = await PGVectorStore.initialize(
            model,
            config
        );

const documents = loadDocuments(); //the array of chunked documents
await pgvectorStore.addDocuments(docs);

Error Message and Stack Trace (if applicable)
message: 'request to https://[redacted]-aiplatform.googleapis.com/v1/projects/[redacted]/locations/[redacted]/publishers/google/models/textembedding-gecko:predict failed, reason: socket hang up',

Description
Hi all - I am using the PGVectorStore class with the GoogleVertexAIEmbeddings class to create embeddings from just under a gig of clinical documents. I use the DirectoryLoader class along with CSVLoader to load the documents and split them using the RecursiveCharacterTextSplitter class to chunk the documents down to 3000 tokens per chunk. When I pass the full list of ~56,000 document chunks to addDocuments() (I split the big CSV file of clinical documents into chunks as well limiting each file to ~50k), the entire process fails reliably and repeatedly with the error message: 'request to https://[redacted]-aiplatform.googleapis.com/v1/projects/[redacted]/locations/[redacted]/publishers/google/models/textembedding-gecko:predict failed, reason: socket hang up',
I went through the VertexAI code and can see it is calling a chunk_array function that looks like it's splitting the array into chunks of 5, but that doesn't appear to be working as intended.
The reason I say this is because I went ahead and split my array into chunks of 5 and am calling addDocuments() with the array of 5 document chunks at a time and so far everything has been working reliably and consistently. If there's something I'm missing please let me know, otherwise I'm not sure how to further debug.
System Info

MacOS Ventura
MacBook Pro M2
NodeJS v20.*
@langchain/community v0.0.26

Is it possible this was fixed in #4279 if you update to latest @langchain/google-genai?

Going to assume it's fixed, please reopen if upgrading to latest doesn't fix


Model outputs NaN

I have this following model:
model = Sequential()
model.add(Embedding(7551, 300, input_length = 200, mask_zero = True, weights = [embmat_300], trainable=False))
model.add(Bidirectional(LSTM(32, dropout = 0.2, recurrent_dropout = 0.2)))
model.add(Dense(2, activation = 'sigmoid'))
model.compile(loss = 'binary_crossentropy', optimizer = 'adam', metrics = ['accuracy'])

And the output of this model is something like this:
Float32Array(2) [NaN, NaN]
Any idea of what's wrong? Any help would be appreciated.

Problem solved by setting gpu: true


Webhook --dynamic-serving-dns-names doesn't set SANs

Describe the bug:
I'm trying to use --dynamic-serving-dns-names on the webhook daemon to add subject alternative names to the certificate used by the webhook pod.
e.g. I've tried --dynamic-serving-dns-names=cert-manager-webhook,cert-manager-webhook.cert-manager,cert-manager-webhook.cert-manager.svc,cert-webhook.example.com
However the certficate generated doesn't seem to have any of these dns names.
Checked via e.g. kubectl -n cert-manager get secret cert-manager-webhook-ca -o yaml | yq -r '.data["tls.crt"] | @base64d' | openssl x509 -text -noout which gives e.g.:
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            23:92:50:f2:cd:27:34:01:d1:76:79:ee:7e:3e:81:8e
        Signature Algorithm: ecdsa-with-SHA384
        Issuer: CN = cert-manager-webhook-ca
        Validity
            Not Before: May 30 05:26:30 2022 GMT
            Not After : May 30 05:26:30 2023 GMT
        Subject: CN = cert-manager-webhook-ca
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (384 bit)
                pub:
                    04:50:7b:6f:8a:13:e6:5c:fd:04:bd:65:cb:4b:0f:
                    f3:10:69:fd:71:90:29:d2:c7:90:b3:d5:fd:f7:91:
                    8a:85:ed:aa:e5:5d:61:57:27:41:6d:f7:85:8d:86:
                    c8:9d:17:93:21:75:7a:f7:45:86:b4:10:0d:74:22:
                    69:e9:e7:6f:4d:1d:ef:da:04:93:72:9e:31:b3:b7:
                    69:db:14:e8:43:1b:d6:75:18:94:0a:8a:2d:03:64:
                    87:ff:ec:af:93:0a:89
                ASN1 OID: secp384r1
                NIST CURVE: P-384
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment, Certificate Sign
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Key Identifier:
                D4:7A:94:A2:E6:8F:EE:1E:6F:FF:82:FA:33:5F:7A:D9:F4:EB:6A:0D
    Signature Algorithm: ecdsa-with-SHA384
         30:65:02:30:6a:6b:25:3b:00:af:4b:71:94:f6:da:63:3f:5f:
         db:ae:9c:41:1a:4d:72:16:52:0e:51:e0:e9:4e:b8:f7:c9:93:
         22:14:36:21:f9:0a:f0:a9:04:2b:45:96:74:1a:dd:03:02:31:
         00:87:2f:91:51:7d:ae:ba:38:4e:33:b7:02:c7:d8:09:6d:20:
         af:9c:1f:ea:89:73:65:ee:71:65:cc:41:7e:b5:60:e3:d4:2c:
         18:30:80:e9:e8:c1:ce:64:3f:ac:8a:df:c5

Expected behaviour:
The generated certificate should have subject-alternative-names (SANs) with the dynamic-serving-dns-names provided.
Steps to reproduce the bug:
See description above.
Anything else we need to know?:

I came up with https://github.com/cert-manager/cert-manager/pull/5163 trying to debug this.
This is likely the cause of several historical tls: bad certficate errors in the issue tracker

Environment details::

Kubernetes version: Server Version: version.Info{Major:"1", Minor:"21+", GitVersion:"v1.21.9-eks-0d102a7", GitCommit:"eb09fc479c1b2bfcc35c47416efb36f1b9052d58", GitTreeState:"clean", BuildDate:"2022-02-17T16:36:28Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Cloud-provider/provisioner: EKS
cert-manager version: 1.6.1; replicated with 1.8.0
Install method: e.g. helm which is then kustomize-d

/kind bug

Hi @james-callahan thanks for opening the issue!
The cert that is stored in the cert-manager-webhook-ca Secret is a self-signed CA cert that will be used to sign the actual webhook's serving cert (which is only stored in memory) and should have the DNS names from --dynamic-serving-dns-names.
(You should be able to verify that the serving cert is as expected with something like:
kubectl port-forward -ncert-manager svc/cert-manager-webhook 8081:443
openssl s_client -showcerts -connect localhost:8081 2>/dev/null | openssl x509 -text -noout

)

(If you are struggling with webhook configuration on EKS there are some known issues with the networking setup there https://cert-manager.io/docs/concepts/webhook/#webhook-connection-problems-on-aws-eks)


Investigate an approach for dealing with updating indexer's mapping during the data migration process

@karenhanson will test out a couple of options using pass-docker set up to decide which course of action we should take in updating indexer mapping. This will inform and solidify data migration plan for the releaes of Proxy Submitter feature
Outcome should include a detailed proposal of how we should carry out this update in demo and production envs.

Have documented how to do the migration


Switch CI configuration to boostorg/boost-ci

Codecov Report

Merging #3 (852dc5c) into develop (4531c3d) will increase coverage by 17.23%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop       #3       +/-   ##
============================================
+ Coverage    78.71%   95.95%   +17.23%
============================================
  Files          118      165       +47
  Lines         5032     9072     +4040
============================================
+ Hits          3961     8705     +4744
+ Misses        1071      367      -704

Impacted Files
Coverage Δ

include/boost/gil/pixel_iterator_adaptor.hpp
88.88% <0.00%> (-11.12%)
:arrow_down:

include/boost/gil/histogram.hpp
97.44% <0.00%> (-0.44%)
:arrow_down:

include/boost/gil/extension/numeric/affine.hpp
90.38% <0.00%> (-0.19%)
:arrow_down:

include/boost/gil/pixel.hpp
100.00% <0.00%> (ø)

include/boost/gil/channel.hpp
100.00% <0.00%> (ø)

include/boost/gil/utilities.hpp
100.00% <0.00%> (ø)

include/boost/gil/image_view.hpp
100.00% <0.00%> (ø)

include/boost/gil/packed_pixel.hpp
100.00% <0.00%> (ø)

include/boost/gil/color_convert.hpp
100.00% <0.00%> (ø)

include/boost/gil/step_iterator.hpp
100.00% <0.00%> (ø)

... and 188 more

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 4531c3d...852dc5c. Read the comment docs.


Reading PDF files

Hi, your blog (in the section titled Long Multimodal Input - Paper Reading) shows an example of Aria answering a question based on a PDF file. https://www.rhymes.ai/blog-details/aria-first-open-multimodal-native-moe-model   However, when I feed the same PDF file into Aria running locally it outputs "PIL.UnidentifiedImageError: cannot identify image file 'test.pdf'"  Does Aria natively support PDF files as input? Am I just not using the right Python library (PIL)? Thanks.

No, the raw inputs for Aria model support image and text only. For the PDF files, you have to preprocess it with PyMUPDF library. Here are some more details that how to process PDF files. @andy8025


Must use valid, tested version for indy-* deps

Signed-off-by: Corin Kochenower<EMAIL_ADDRESS>

@jovfer - DCO sign-off is now in my commit message and I have set the indy-* dep versions to the versions you say have been tested.


feat: 북마크 아이콘 피드백 컴포넌트에 추가

closed #367
🎉 변경 사항

피드백 컴포넌트에 북마크를 추가했어요.

isView props: 본인의 결과 페이지에서만 북마크가 보이기 때문에 isView props를 추가했어요.
isBookmarked props: 북마크 여부를 내려주는 props 예요.

🌄 스크린샷

Codecov Report
Patch and project coverage have no change.

Comparison is base (8e54cfe) 90.96% compared to head (4b7f031) 90.96%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #369   +/-   ##
=======================================
  Coverage   90.96%   90.96%
=======================================
  Files          43       43
  Lines         299      299
  Branches       52       52
=======================================
  Hits          272      272
  Misses         27       27

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


rename makefile -> Makefile. make files non-executable

I only wanted the 1st commit 020a67b2f4f7eece53bc6f9a1d3dad076d38934d to be merged. ;-)


add arrays.intersection

Ref: #92

FYI, updating your local master copy then rebasing the feature branch on top of it works better than merging master into the feature branch.

The master branch is protected (ie blocks push -f) but you can force push onto feature branches if you need to clean up the history.

I think there is a more efficient approach. Take a look at the arrays.frequency spec.
Instead of creating sets for each array and doing a ton of lookups.
You can determine the intersections in 2 steps:

determine the frequency (ie how many arrays it appears in) for each item
filter the array of frequencies to extract only the values where frequency = 3 of input arrays

Does that make sense?

I don't know if it applies perfectly, as one would still need to search through each array for each unique element. I could optimize with a method more like 'some' that breaks off array search on find.
The function with the fastest real run time flips based on browser or device.
https://jsperf.com/reduce-intersection-benchmark/1
Let me know if I am missing something about the implementation.
function intersection (array, ...arrays) {
  const unique = [...new Set(array)]
  if (arguments.length === 1) return unique;
  return unique.reduce((acc, element) => {

    // if array includes element, then create or increment object frequency record
    const frequency = arrays.reduce((res, cur) => {
      if (cur.reduce((bool, elem) => {
        if (bool) return bool;
        if (elem === element) { return true; }
      }, false)) {
        res[element] = !res[element] ? 2 : ++res[element];
      }
      return res;
    }, {});

    // filter object for records with counts equal to number of inputs
    if (Object.values(frequency)[0] === arguments.length) {
      acc.push(Object.keys(frequency)[0])
    }
    return acc;
  }, []);
}

Nevermind. I thought it would be something more like.
function intersection (...arrays) {
  const numArrays = arrays.length;
  return [...arrays
    .reduce((prev, curr) => prev.concat(curr))
    .reduce((acc, curr) => {
      if (acc.has(curr)) {
        acc.set(curr, acc.get(curr) + 1);
      } else {
        acc.set(curr, 1)
      }
      return acc;
    }, new Map())]
    .reduce((acc, curr) => {
      if (curr[1] === numArrays) { acc.push(curr[0]); }
      return acc;
    }, []);
}

But failed to consider arrays that contain more the same value more than once.
I'm going to go ahead and land this as is.

OK, this works. I have no idea if it's faster than your solutions
function intersection (...arrays) {
  const numArrays = arrays.length;
  return [...arrays
    .reduce((acc, curr) => {
      acc.push([...new Set(curr)]);
      return acc;
    }, [])
    .reduce((acc, curr) => acc.concat(curr))
    .reduce((acc, curr) => {
      if (acc.has(curr)) {
        acc.set(curr, acc.get(curr) + 1);
      } else {
        acc.set(curr, 1)
      }
      return acc;
    }, new Map())]
    .reduce((acc, curr) => {
      if (curr[1] === numArrays) { acc.push(curr[0]); }
      return acc;
    }, []);
}

Pretty comparable in an initial test. They are both the fastest apparently.


⚠ Bofrost.lu has degraded performance

In be99454, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1254 ms

Resolved: Bofrost.lu performance has improved in 033cf7d after 6 minutes.


Not Working with react-native 0.27.2

I am using react native 0.27.2 and its working can you tell me a specific error you are getting

I am using react native 0.27.2 and its working can you tell me a specific error you are getting

@codesinghanoop no errors is displaying screen just remain white or blank. nothing running. logcat shows much information that i am unable to figure out.
debugging in chrome does not show any error :(
what can i do, and did you test it recently? may be latest commit have any issue with 0.27.2

I have create project in 0.33.1 and after configuration i got this
JS server already running.
Running adb -s LGH812a6734905 reverse tcp:8081 tcp:8081
Building and installing the app on the device (cd android && ./gradlew installDebug...
FAILURE: Build failed with an exception.

Where:
Build file '/Users/waleed/Documents/projects/VideoDemo/android/app/build.gradle' line: 129

What went wrong:
A problem occurred evaluating project ':app'.

Project with path ':react-native-video' could not be found in project ':app'.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

https://github.com/waleedarshad-vf/VideoDemo

OK i missed these lines but after adding these i got just blank screen
include ':react-native-video'
project(':react-native-video').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-video/android')
https://github.com/waleedarshad-vf/VideoDemo please rectify it if you can

Another project https://github.com/waleedarshad-vf/zigTest but got just black screen same is the case with 0.27.2 :(

I think problem is in app/build.gradle (compile "com.facebook.react:react-native:+" change this to compile 'com.facebook.react:react-native:0.27.2')

@codesinghanoop 0.27.2 is another thing. it is not working even with 0.33.1. did you try running the above project

Closing since this is very old.


Update _site.yml

Will this open the containers link in a new tab?

@carriewright11 how do I verify if this worked?

I am not sure. But we can try merging it and see if it works, and we can undo it if needed.


No comments by Travis Buddy on failure

I recently attempted to use travis-buddy in my repo. I created a branch namely tb and made a PR to it from another branch namely tbt1. I modified the files so as to fail the tests. The tests fail as expected but there is no comment by the travis-buddy.
Kindly point me out if I am missing something somewhere.

Same here. It used to work, but it does not anymore.

@bluzi can it be that Buddy works for travis-ci.org and doesn't for travis-ci.com?
@YashJipkate's https://github.com/YashJipkate/oppia uses .com

Perhaps this would need to know whether this is travis-ci.org or .com build:
https://github.com/bluzi/travis-buddy/blob/7edaef2cd643ff706874c74c848ef160bee3c08e/pipes/fetch-build-logs.pipe.js#L7

Same here, I use webhooks but travis buddy don't make a comment on the pull request


Support OAuth/refresh token from config

Absolute minimum code to support usage of a refresh token within the config file if it exists. User can now set the refresh token using rsc setup. The main advantage is that no extra cli options are needed for users that use OAuth2 when consuming ~/.rsc or via --config.
Addresses issue #77.

Test fails don't look code related. @raphael any chance you could help get this merged?

Looks like the build failed because PRs from forked repositories can't access the credentials tied to the repository.

Thanks. Tests pass now.


Connection::builder_pure_rust() item not found

I can't get rsfbclient to run under Linux or MacOS
Version rsfbclient 0.25.1
Cargo.toml
[dependencies] rsfbclient = { version = "0.25.1", features = ["pure_rust"] }
main.rs
use rsfbclient::{Connection}; let mut conn = Connection::builder_pure_rust()...  function or associated item not found in Connection<_>

Older versions work fine?

I once created the project with 0.16 and I think it worked back then. Today it works neither with 0.16 nor with the current 0.25.1

I use Arch Linux and had installed rust with pacman. For whatever reason, no builder was usable. After a reinstallation with the script from rust-lang.org rsfbclient works again. I can't say exactly what the problem was, because other rust sources compiled fine with the pacman version. Sorry for the inconvenience.

On the Mac, default-features = false is absolutely necessary for pure-rust. Strange that default_features (underscore) also works :-)


Prometheus crash when remote_storage_adapter comes up after failure (panic: runtime error: makeslice: len out of range)

What did you do?
We are using remote_storage_adapter implementation (https://github.com/prometheus/prometheus/tree/master/documentation/examples/remote_storage/remote_storage_adapter) to push metrics to InfluxDB.
Sometimes when remote_storage_adapter is back after failure (docker service scale remote_storage_adapter=0 && sleep 300 && docker service scale remote_storage_adapter=1) prometheus server crash.
Logs
time="2017-07-18T15:14:20Z" level=warning msg="Error sending 100 samples to remote storage: Post http://remote_storage_adapter:9201/write: dial tcp: lookup remote_storage_adapter on <IP_ADDRESS>:53: no such host" source="queue_manager.go:500"
time="2017-07-18T15:14:26Z" level=info msg="Remote storage resharding from 118 to 47 shards." source="queue_manager.go:351"
time="2017-07-18T15:14:36Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:14:46Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:14:56Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:15:06Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:15:16Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:15:26Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:15:36Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:15:46Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:15:46Z" level=info msg="Checkpointing in-memory metrics and chunks..." source="persistence.go:633"
time="2017-07-18T15:15:48Z" level=info msg="Done checkpointing in-memory metrics and chunks in 1.235390018s." source="persistence.go:665"
time="2017-07-18T15:15:56Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:16:06Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:16:16Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:16:26Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:16:36Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:16:46Z" level=info msg="Remote storage resharding from 47 to 2 shards." source="queue_manager.go:351"
time="2017-07-18T15:16:56Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:17:06Z" level=info msg="Currently resharding, skipping." source="queue_manager.go:354"
time="2017-07-18T15:17:16Z" level=info msg="Remote storage resharding from 2 to -1 shards." source="queue_manager.go:351"
panic: runtime error: makeslice: len out of range
goroutine 193 [running]:
github.com/prometheus/prometheus/storage/remote.(*QueueManager).newShards(0xc42028a700, 0xffffffffffffffff, 0x1)
/go/src/github.com/prometheus/prometheus/storage/remote/queue_manager.go:396 +0x40
github.com/prometheus/prometheus/storage/remote.(*QueueManager).reshard(0xc42028a700, 0xffffffffffffffff)
/go/src/github.com/prometheus/prometheus/storage/remote/queue_manager.go:375 +0xcf
github.com/prometheus/prometheus/storage/remote.(*QueueManager).reshardLoop(0xc42028a700)
/go/src/github.com/prometheus/prometheus/storage/remote/queue_manager.go:364 +0x105
created by github.com/prometheus/prometheus/storage/remote.(*QueueManager).Start
/go/src/github.com/prometheus/prometheus/storage/remote/queue_manager.go:265 +0x85
Environment
System: Ubuntu 16.04
Prometheus is running on top of docker-swarm.
Prometheus cmd line:
/opt/prometheus/prometheus -config.file /srv/prometheus/prometheus.yml -web.listen-address <IP_ADDRESS>:9090 -storage.local.engine persisted -storage.local.retention 360h -storage.local.target-heap-size<PHONE_NUMBER> -storage.local.num-fingerprint-mutexes 4096 -storage.local.path /data/data/1/
Prometheus version:
prometheus, version 1.6.3 (branch: master, revision: c580b60c67f2c5f6b638c3322161bcdf6d68d7fc)
build user:       root@a6410e65f5c7
build date:       20170522-09:15:06
go version:       go1.8.1
Prometheus config
global:
  evaluation_interval: 1m
  external_labels:
    region: region1
  scrape_interval: 15s
  scrape_timeout: 15s
alerting:
  alertmanagers:
    # docker_swarm_alertmanager
    - dns_sd_configs:
      - names: [tasks.alertmanager]
        type: A
        port: 9093
remote_write:
  # docker_remote_write
  - url: http://remote_storage_adapter:9201/write

rule_files:
- alerts.yml

scrape_configs:
  - job_name: telegraf

    static_configs:
    - targets: ['<IP_ADDRESS>:9126','<IP_ADDRESS>:9126','<IP_ADDRESS>:9126','<IP_ADDRESS>:9126','<IP_ADDRESS>:9126','<IP_ADDRESS>:9126','<IP_ADDRESS>:9126','<IP_ADDRESS>:9126','<IP_ADDRESS>:9126','<IP_ADDRESS>:9126','<IP_ADDRESS>:9126']
  - job_name: pushgateway
    dns_sd_configs:
    - names:
      - tasks.pushgateway
      type: A
      port: 9091
  - job_name: prometheus
    dns_sd_configs:
    - names:
      - tasks.server
      type: A
      port: 9090
  - job_name: alertmanager
    dns_sd_configs:
    - names:
      - tasks.alertmanager
      type: A
      port: 9093

Thanks for reporting!  I'll take a look.


Interactive Playground snippets lack coloring when reopened on reload

Issue Type: Bug

Open Interactive Playground
Reload window

VS Code version: Code - Insiders 1.21.0-insider (3fec61014742dec894b3a31cdf8556bf533cb0e1, 2018-02-28T06:08:46.169Z)
OS version: Darwin x64 16.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

Load (avg)
3, 3, 3

Memory (System)
16.00GB (0.02GB free)

Process Argv
/Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron --user-data-dir tmp/user --extensions-dir tmp/ext

Screen Reader
no

VM
0%

Extensions: none
Reproduces without extensions

Just noticed this is still happening in the latest release.
$ code --version
1.31.1
1b8e8302e405050205e69b59abb3559592bb9e60
x64


Lag is progressive/cumulative

Hi, I'm using a VR device (Oculus GO) and I made a small app that mirrors the device to a very low bugdet PC.
I have noticed that lag keeps gradually growing as time goes by, as in if 1sec of lag is perceived during the first minute of playback, it will be twice as much a minute later. Another example of this is that if I unplug the cable, the playback keeps going until all the piled up "remaining" time is reproduced.
At first I was experiencing significant lag so I decreased the bitrate to 1M and it felt smooth, but the problem is that the lag keeps piling up, so after 10min it becomes troublesome.  Is there a way to "Refresh" the view every once in a while?
this is the command I'm using atm:
scrcpy -f  -b 1M -m 800 -c 1224:1440:0:0
(I've also tried without "-m 800")
PC Specs:
OS: Windows 10
Processor: N4200
RAM: 4GB
Playback is always using cable

if I unplug the cable, the playback keeps going until all the piled up "remaining" time is reproduced.

Is the CPU at 100% on the computer?

At first I was experiencing significant lag so I decreased the bitrate to 1M and it felt smooth

Which have more effect on the lag: bitrate (-b 1M) or definition (-m 640)?


RFC: Canonical Wide Log utility for emitting a single log entry per lambda execution or processed transaction (batch)

Is this related to an existing feature request or issue?
No response
Which Powertools for AWS Lambda (Python) utility does this relate to?
Logger
Summary
The logger is great and offers a heap of functionality. It is very useful for developer logging, debug, info, error logging but I don't think its great for observability logging.  Some ideas have been circulating in the observability community around canonical logging and, more recently, about wide events.  The idea of a single log entry per Lambda function invocation holding ALL the meta-data for what occurred during that execution is a very useful concept and something I have used for tracking, tracing and observing transactions across a distributed system.
Use case
I want to be able to gather meta-data during transaction processing and store it somewhere so I can write it all out in a single place, representing everything that happened to the transaction as it was being processed by my code.  I want to be able to add to this meta-data from shared-libraries and want to enable developers to easily throw meta-data into the bucket for collection when transaction processing is done.
Log attributes does this sto a degree already - but is focused on applying the meta-data to every log output, not just a single oneat the end of processing.
Proposal
Existing capability:
from aws_lambda_powertools import Logger
from aws_lambda_powertools.utilities.typing import LambdaContext

logger = Logger()

@logger.inject_lambda_context
def lambda_handler(event: dict, context: LambdaContext) -> str:
    logger.append_keys(customer=event.customer_id)

    try:
        logger.info({"operation": "collect_payment", "charge_id": event["charge_id"]})

        # do more processing

    finally:
        logger.info("WIDE") # log WIDE log entry along with collected attributes from 'append_keys'

    return "hello world"

Using a Wide Logging utility:
from aws_lambda_powertools import Logger
from aws_lambda_powertools.utilities.typing import LambdaContext

logger = Logger()

@logger.inject_lambda_context
@logger.wide_logger()
def lambda_handler(event: dict, context: LambdaContext) -> str:
    logger.wide.add(customer=event.customer_id)

    logger.debug({"operation": "collect_payment", "charge_id": event["charge_id"]})
    logger.wide.add(charge_id=event.get("charge_id"))
    logger.wide.add(operation=collect_payment)

    # do more processing

    return "hello world"

Using middleware to emit the wide log means it is a set and forget operation, which adds value for developers who are already overloaded.
Being able to add in meta-data as transaction processing happens, encourages thoughtful use of meta-data attributes.
Collating them in a central object for emitting at the end means the meta-data you are collecting for observability purposes is separate from attributes you collate for debug logging - 2 very distinct purposes and separating the concerns will encourage clearer thinking on Observability vs debug.
Out of scope
Nothing.
Potential challenges
Wide logging needs to be considered at a transaction level - so not always as a per-function execution statement which is not true in the case of functions which process data through a batch mechanism - SQS, SNS, stream (DynamoDB, Kafka, Kinesis, etc).  The middleware would need to apply to both batch functions and lambda handlers.
Dependencies and Integrations
This should be a natural extension of the logger utility - a slightly different function to just logging.  I liken the idea of this more like the Metrics implementation where meta-data is collated during code execution and output at a singular level.This
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Powertools for AWS Lambda (Python) Tenets
[X] Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[!question]
1 - If I got it correctly, the idea of this RFC is to create a middleware to add the ability to create WIDE logs per transaction/lambda execution. Could you confirm if the idea here is to add support for WIDE logs, canonical format logs, or both?

Conceptually Canonical and Wide logs are similar in the way they are written once to your log output, I would say they are actually the same thing.  names are important which is why I personally like “Wide Logs”, it says what it is.  Nobody understands what a Canonical log should be IMO 🙃. Let’s Agree - they are the same thing, and have the same logical functionality.  From a Powertools perspective we should choose the name that we stay with and most customers understand.

[!question]
2 - You mention creating a middleware to not only provide WIDE logging per handler execution but also propagate this logger instance across batch/idempotence/event handler executions. I have some difficulty seeing how we can share this instance between all the utilities, perhaps using a decorator on all the functions you want to use this WIDE logger instance?

When I think about using this kind of logging - I am generally looking to write a single log entry per transaction that gets processed.  This is the complexity I was raising - to provide the utility such that it is useable in all of the following contexts:

Whole Lambda Execution where a single API transaction is processed.  e.g Event Handler
In a batch setting (BatchProcessor)
Any others I have forgotten?
Not really thinking of implementation - but highlighting the context of where I feel it should be used.

[!question]
3 - What is the log level of this WIDE log? INFO by default? Customers can change this at runtime? This should inherit the same log level of the Logger() instance? In your example, you are using DEBUG and WIDE (INFO?) with the same Logger instance and I can imagine the middleware is respecting the log level configured at the constructor level.

I have  a typescript implementation and I output it as “INFO” with a “WIDE” tag for filtering.  I have been thinking more about whether it should be a different log level altogether in case INFO is not turned on - I feel WIDE or Canonical logs are ones you always want to write out so may need to think more about this from a level perspective - are they logs at all?, and what does that mean from an AWS Lambda perspective.

[!question]
4 - We have some parameters at the Logger constructor level and we also have some standalone functions, such as append_keys for example. In this WIDE logs middleware, should we consider and respect everything that was defined in the Logger() instance? For example: if the customer adds keys via append_keys or set correlationid via set_correlation_id, should we propagate this to this Middleware? We should not? This can result in duplicate or unwanted keys in the WIDE logs because a customer can call append_keys anywhere, for example.

My thought here is that the Wide (or Canonical) log functionality should operate from a seperate attribute “bucket” to gather wide log data during processing.  This is how my typescript implementation works, I liken it to the Metrics functionality which enables gathering of data and writes it out once.

[!question]
5 - When will we flush the WIDE log to output? Right after the Lambda execution has completely finished? And if the customer is processing Idempotency and Batch Processing in the same Lambda execution, wouldn't this cause some confusion between the data the customer wants in the WIDE logs?

Let’s tackle this one in pieces - there are more than one question, I will focus on the why’s and what I would like - not the HOW - this needs to come later after we  agree on the contexts and function.
When will we flush the WIDE log output?
Wide log output should be flushed logically at the end of the lambda execution.  This makes the most sense and is how my Typescript implementation works via Middy Middleware.
If the customer is processing in batch?
Refer back to the context for the functionality - I agree this is a complexity.  For me I would want a WIDE log entry per transaction.  I would also want a mix of attributes which are common to each item in a batch as well as attributes that are ONLY for a single item.
If the customer is using Idempotency Utility?
This is another complexity - if the request being processed is a duplicate identified by Idempotency - you would not want a WIDE log entry output - since it has already been processed.  If it is not a duplicate transaction - then you would want Wide logging to occur as normal.
At the end of the day we should provide a utility to enable customers to use it as they need to and desire regardless of the context of operation.  The functionality should be consistent and simple in each use-case so customer’s can choose how to use it.


Added storybook

WIP adding storybook.
Closes #36.

I have storybook working, however, something is broken with the display of source code for the components. It's a handy feature to have, but we can live without it for now.
I put in a support message on SB Discord and they pointed me to this issue: https://github.com/storybookjs/storybook/issues/20356
It seems pretty similar, so I am going to assume this is just a bug with latest SB release and NextJS. Let's track that issue and fix the source code display later.
Ready for review!


suggestion: show a list of available tags to add

Though I can add a tag at creation time, I don't know what the valid ones are perhaps a tag-cloud or even a multi-select dropdown would be good.
by encouraging tagging you could pass them though to the twitter entry as a hashtag
Could we also have a link on the frontpage to page listing them to encourage exploring?
For example if anytone would like an explore, the current list of tags are as follows (I have made them into links)
18th Century
19th Century
beach
cat
colleague
dog
emoji
famous
funny
graveyard
illegible
indoors
metal
multiple plaques
park
picture
poem
quote
statue
stone
train station
twinned
wood

On https://openbenches.org/add/ click in the text field next to "Choose some tags:" and a list appears which can be scrolled through. That is all the valid tags. So that's how you know what the valid tags are. Or maybe I don't understand the problem you're describing.
I like the idea of a list of tags somewhere easily viewable for people to click on and explore but based on the number mentioned in this comment   roughly 6% of benches have tags which means the feature wouldn't be all that useful. Perhaps there could be a big tagathon. No idea how that would work. :smile:

Yes a virtual tagathon  by perhaps downloading the database using that to work out some commonalities and doing bulk  inserts based on them.
The could then have another use that if a bench is shared, the tags are included in the text with hash's in front of them, in effect making route back to openbenches for some interested in "cricket" for example

Add page now makes tagging more obvious. Editing a bench allows you to add or remove tags.


b3Printf: URDF file '/home/user/handover-sim/handover/data/assets/table/table.urdf' not found

Hi, thank you for your great work for human-to-robot handovers.
When I run a handover environment (Ubuntu20.04 python 3.8):
python examples/demo_handover_env.py
SIM.RENDER True
I meet the following error:
pybullet build time: May 20 2022 19:44:17
argv[0]=
startThreads creating 1 threads.
starting thread 0
started thread 0
argc=3
argv[0] = --unused
argv[1] =
argv[2] = --start_demo_name=Physics Server
ExampleBrowserThreadFunc started
X11 functions dynamically loaded using dlopen/dlsym OK!
X11 functions dynamically loaded using dlopen/dlsym OK!
Creating context
Created GL 3.3 context
Direct GLX rendering context obtained
Making context current
GL_VENDOR=NVIDIA Corporation
GL_RENDERER=NVIDIA GeForce RTX 4080/PCIe/SSE2
GL_VERSION=3.3.0 NVIDIA 525.105.17
GL_SHADING_LANGUAGE_VERSION=3.30 NVIDIA via Cg compiler
pthread_getconcurrency()=0
Version = 3.3.0 NVIDIA 525.105.17
Vendor = NVIDIA Corporation
Renderer = NVIDIA GeForce RTX 4080/PCIe/SSE2
b3Printf: Selected demo: Physics Server
startThreads creating 1 threads.
starting thread 0
started thread 0
MotionThreadFunc thread started
b3Printf: b3Warning[examples/Importers/ImportURDFDemo/BulletUrdfImporter.cpp,152]:
b3Printf: URDF file '/home/hwpeng/handover-sim/handover/data/assets/table/table.urdf' not found
Traceback (most recent call last):
File "examples/demo_handover_env.py", line 27, in
main()
File "examples/demo_handover_env.py", line 19, in main
env.reset(scene_id=scene_id)
File "/home/user/.conda/envs/handover_sim/lib/python3.8/site-packages/gym/wrappers/order_enforcing.py", line 18, in reset
return self.env.reset(**kwargs)
File "/home/user/.conda/envs/handover_sim/lib/python3.8/site-packages/easysim/simulator_env.py", line 48, in reset
self._simulator.reset(env_ids)
File "/home/user/.conda/envs/handover_sim/lib/python3.8/site-packages/easysim/simulators/bullet.py", line 98, in reset
self._load_body(body)
File "/home/user/.conda/envs/handover_sim/lib/python3.8/site-packages/easysim/simulators/bullet.py", line 178, in _load_body
self._body_ids[body.name] = self._p.loadURDF(body.urdf_file, **kwargs)
pybullet.error: Cannot load URDF file.
ven = NVIDIA Corporation
numActiveThreads = 0
stopping threads
Thread with taskId 0 exiting
Thread TERMINATED
destroy semaphore
semaphore destroyed
destroy main semaphore
main semaphore destroyed
finished
numActiveThreads = 0
btShutDownExampleBrowser stopping threads
Thread with taskId 0 exiting
Thread TERMINATED
destroy semaphore
semaphore destroyed
destroy main semaphore
main semaphore destroyed

Hi @HWPengSYSU1993
Can you please share? how did you resolve this issue, if it has been resolved?

Hi @RAFAYAAMIR. Actually, I didn't follow the step-4 of "Download the DexYCB dataset". So I close this issue, as it work by following the instruction of installing the dataset.

handover-sim/handover/data/assets/table/table.urdf should be generated in Installation step 5. ii. (see here and here). Make sure pybullet has been installed from step 2., and you have run step 5. i. to download and extract the assets.


Update swagger-ui to 4.15.5

Was upgraded in
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/8f363f7359cb1cb8fa5de5195ec6d97aefaa16b3


Download entirely from disk

Change the WorkZip service to access the data from Isilon not from fedora.

We may want to reevaluate the HEAD request method for getting the location.  Can we get the data from the Solr document instead?

Fixed in #1557


[camera] Fix IllegalArgumentException on takePicture() on Android

Description
Adds pictureImageReader.getSurface() to surfaceList, fixing an IllegalArgumentException when taking pictures on Android.
Related Issues
Fixes flutter/flutter#41339
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Closing this PR since the problem as already been solved. Has been retested on Android 6 and 9.


feat: UILD-269: Jest/RTL Unit Tests for src/components/ItemSearch

https://folio-org.atlassian.net/browse/UILD-269

HI @s3fs, @SKarolFolio,
I guess this ticket is not needed for alpha. So, It is ok to merge this to master.
Moving forward, let us merge all the alpha bugfixes to release/alpha branch.


[Ubuntu] pin powershell-core version

Description
Pin pwsh-core version to avoid upgrades to 7.3
Related issue:
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[X] Changes are tested and related VM images are successfully generated

/azp run ubuntu2004,ubuntu2204


Develop - show bit of feedback

Checklist before merging

[x] Documentation updated
[x] Config.json changes reflected in source/get_data.validate_config
[x] Version number updated in pyproject.toml
[x] Completion script updated
[x] Completion script updated in commands/info.completion()
[x] Changelog updated in commands/info.changelog() (only empty changelog after merge into master)

This will be a stable-dev version, I want people to try this and report issues, if they have any. Not a lot has changed, so should be without issues :crossed_fingers:


Automator: update<EMAIL_ADDRESS>in<EMAIL_ADDRESS>

Generated by Automator - 2021-08-24T23:14:25+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-security-k8s-tests_istio_release-1.10

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-security-k8s-tests_istio_release-1.10

integ-pilot-k8s-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-k8s-tests_istio_release-1.10

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-security-k8s-tests_istio_release-1.10

integ-pilot-k8s-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-k8s-tests_istio_release-1.10

integ-pilot-multicluster-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-multicluster-tests_istio_release-1.10

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

/retry

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-multicluster-tests_istio_release-1.10

integ-pilot-k8s-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-k8s-tests_istio_release-1.10

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

/test integ-pilot-k8s-tests_istio_release-1.10

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-k8s-tests_istio_release-1.10

integ-pilot-multicluster-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-multicluster-tests_istio_release-1.10

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-multicluster-tests_istio_release-1.10

integ-pilot-k8s-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-k8s-tests_istio_release-1.10

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-multicluster-tests_istio_release-1.10

integ-pilot-k8s-tests_istio_release-1.10
07e5127c8ec9e9800becb680c8dee4dcf3e78d9d
link
/test integ-pilot-k8s-tests_istio_release-1.10

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

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio_release-1.10
cce818d0a7513e86cdb2e89c5cffad7ae66d7d09
link
/test integ-security-multicluster-tests_istio_release-1.10

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

Should be fine to close since https://github.com/istio/istio/pull/34862 made it in.


feat(data): Implement events subscribing from message bus

Close: #2936
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?

Issue Number: #2936
What is the new behavior?

Add subscribing logic to bootstrapping MessageBus client
Implement Event received via MessageBus

Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Open PR to add the config SubscribeEnabled https://github.com/edgexfoundry/go-mod-bootstrap/issues/239

Codecov Report

Merging #3474 (26c9dd0) into master (f8639be) will decrease coverage by 0.08%.
The diff coverage is 10.00%.

@@            Coverage Diff             @@
##           master    #3474      +/-   ##
==========================================
- Coverage   40.59%   40.50%   -0.09%
==========================================
  Files         202      203       +1
  Lines       16557    16606      +49
==========================================
+ Hits         6722     6727       +5
- Misses       9357     9401      +44
  Partials      478      478

Impacted Files
Coverage Δ

internal/core/data/init.go
0.00% <0.00%> (ø)

internal/core/data/main.go
0.00% <0.00%> (ø)

internal/core/data/v2/application/subscriber.go
0.00% <0.00%> (ø)

internal/core/data/messaging/messaging.go
83.92% <100.00%> (+1.57%)
: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 f8639be...26c9dd0. Read the comment docs.

Resolved the conflict.


Auto Config Non-Blocking Retries with asyncAcks

Back port issue of https://github.com/spring-projects/spring-kafka/issues/2702

Fixed via: https://github.com/spring-projects/spring-kafka/commit/4401f968904b7e549c285c8d6c804146249983a7


chore(deps): update dependency @types/node to v22.5.4

This PR contains the following updates:

Package
Type
Update
Change

@types/node (source)
devDependencies
minor
22.3.0 -> 22.5.4

[!WARNING]
Some dependencies could not be looked up. Check the warning logs for more information.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (22.5.4). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Add this project, though it is academic and not obviously open source...

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7200321/
https://link.springer.com/article/10.1007%2Fs41207-020-00163-1
https://www.thepatent.news/2020/06/10/easy-to-build-portable-ventilator-for-covid-19-patients-concept-and-challenges/
Contact person<EMAIL_ADDRESS>

They made the design file public:
https://www.tinkercad.com/things/eFTlRufTFzH-preliminary-design-of-an-innovative-simple-and-easy-to-build
though I suspect it does not have a license.


OSError: [Errno -70] NetCDF: DAP server error when parallel=True on a cluster

What is your issue?
Hi,
I am trying to access MERRA-2 dataset using opendap links on xarray.
The code below is based on a tutorial that @betolink sent me as an example.
The code runs well if parallel=False, but returns OSError: [Errno -70] NetCDF: DAP server error if I set parallel=True, no matter if I create the cluster or not.
@betolink suspected that the workers doesn’t know the authentication and suggested me to do something like mentioned in @rsignell issue.
Which would involve adding client.register_worker_plugin(UploadFile('~/.netrc')) after creating the client. I also tested that but returned the same error. In the code below I had to replace ~/.netrc for the full path because it was returning file not found error.
It is important to say that parallel=True works fine on my local computer using Ubuntu by WSL.
Has anyone faced this problem before or has any guesses on how to solve this issue?
# ----------------------------------
# Import Python modules
# ----------------------------------

import warnings

warnings.filterwarnings("ignore")

import xarray as xr
import matplotlib.pyplot as plt
from calendar import monthrange

create_cluster = True
parallel = True
upload_file = True

if create_cluster:
    # --------------------------------------
    # Creating 50 workers with 1core and 2Gb each
    # --------------------------------------
    import os
    from dask_jobqueue import SLURMCluster
    from dask.distributed import Client
    from dask.distributed import WorkerPlugin

    class UploadFile(WorkerPlugin):
        """A WorkerPlugin to upload a local file to workers.
        Parameters
        ----------
        filepath: str
            A path to the file to upload
        Examples
        --------
        >>> client.register_worker_plugin(UploadFile(".env"))
        """
        def __init__(self, filepath):
            """
            Initialize the plugin by reading in the data from the given file.
            """

            self.filename = os.path.basename(filepath)
            self.dirname = os.path.dirname(filepath)
            with open(filepath, "rb") as f:
                self.data = f.read()

        async def setup(self, worker):
            if not os.path.exists(self.dirname):
                os.mkdir(self.dirname)
            os.chdir(self.dirname)
            with open(self.filename, "wb+") as f:
                f.write(self.data)
            return os.listdir()

    cluster = SLURMCluster(cores=1, memory="40GB")
    cluster.scale(jobs=10)

    client = Client(cluster)  # Connect this local process to remote workers
    if upload_file:
        client.register_worker_plugin(UploadFile('/home/isimoesdesousa/.netrc'))

# ---------------------------------
# Read data
# ---------------------------------
# MERRA-2 collection (hourly)
collection_shortname = 'M2T1NXAER'
collection_longname  = 'tavg1_2d_aer_Nx'
collection_number = 'MERRA2_400'
MERRA2_version = '5.12.4'
year = 2020

# Open dataset
# Read selected days in the same month and year
month = 1  # January
day_beg = 1
day_end = 31

# Note that collection_number is MERRA2_401 in a few cases, refer to "Records of MERRA-2 Data Reprocessing and Service Changes"
if year == 2020 and month == 9:
    collection_number = 'MERRA2_401'

# OPeNDAP URL

url = 'https://goldsmr4.gesdisc.eosdis.nasa.gov/opendap/MERRA2/{}.{}/{}/{:0>2d}'.format(collection_shortname, MERRA2_version, year, month)
files_month = ['{}/{}.{}.{}{:0>2d}{:0>2d}.nc4'.format(url,collection_number, collection_longname, year, month, days) for days in range(day_beg,day_end+1,1)]
# Get the number of files
len_files_month=len(files_month)

# Print
print("{} files to be opened:".format(len_files_month))
print("files_month", files_month)

# Read dataset URLs
ds = xr.open_mfdataset(files_month, parallel=parallel)

# View metadata (function like ncdump -c)
ds

As this deals with HPCs, I also posted on pangeo forum
https://discourse.pangeo.io/t/access-ges-disc-nasa-dataset-using-xarray-and-dask-on-a-cluster/3195/1

It might be related to the issue, but the code below is for a different GES DISC dataset from a different server goldsmr5 and the code also break for parallel=True. The same code works well for parallel=False.
import xarray as xr
import pandas as pd

# list daily timestamps from a starting date to an end date
dts = pd.date_range(start = "2013-01-01", end = "2022-12-01", freq = "D")

# base url for the files
base = "https://goldsmr5.gesdisc.eosdis.nasa.gov/opendap/MERRA2/M2I3NPASM.5.12.4/"
# prefix of the files
prefix = "MERRA2_400.inst3_3d_asm_Np"

# function to construct the url of the files
url = lambda d: f"{base}{d.year}/{d.month:02d}/{prefix}.{d.year}{d.month:02d}{d.day:02d}.nc4"

# list of urls for the files
fnames = [url(dti) for dti in dts]

# lets try to load the first 5 files
ds = xr.open_mfdataset(fnames[:5], parallel=True)

The error:
OSError: [Errno -51] NetCDF: Unknown file format: b'https://goldsmr5.gesdisc.eosdis.nasa.gov/opendap/MERRA2/M2I3NPASM.5.12.4/2013/01/MERRA2_400.inst3_3d_asm_Np.20130105.nc4'


Trigger button action of the selected nodes with new Hotkey

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes
Forum request.
Triggers button action for selected nodes via a Hotkey (ctrl-shift-t).
Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run npm run test to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Not sure I like ctrl-shift-t as the default.  That is by default "reopen the most recently closed tab in a browser" and since the editor is browser based, you will get mixed feedback.
A more natural default for me is CTRL-space.  Since space is synonymous with "pressing a button" (try tabbing on to any button on any browser then press space), this makes CTRL-space feels like a more natural fit.

As I said on Slack I wasn't sure about this choice 😅
ctrl-space is used globally to toggle sidebar. These two scopes (global and workspace) are not very compatible for this use. There will be nonsense behavior with the sidebar.

ctrl-space is used globally to toggle sidebar

Ah yeah DOH.
Then perhaps just space?

Howabout CTRL-Enter? Enter has more of an indication of "do something" than a space ...

Maybe but already used for core:go-to-selection.
space is available and makes sense.

Maybe but already used for core:go-to-selection.

Weird, I tried it out and it didn't do anything, hence my suggestion. But yes, it's also bound to go-to-selection in my node red.
I did realise that CTRL-Enter is used close and save the edit panel (if open), as CTRL-Escape closes it without saving.

howabout alt-enter - that seems to be free ;)

Putting aside the debate for the right keyboard shortcut (which could be left unset initially...) I'd suggest the action should be called trigger-selected-node-action or -button.

Perfect for me, now which shortcut to choose?

Perfect for me, now which shortcut to choose?

CTRL+Enter seems reasonable

One problem, already used 😅

Ctrl-Enter already used and I'm not sure about having it do different things in different contexts. I don't have a good suggestion yet, but I just know whatever is picked will not satsify everyone.

One problem, already used 😅

Yeah, but if the node editor is not visible, it has no use.
If overloading the operation is not preferable, the what about F5 - F5 is most IDEs means "Go" (start debugging)?
Or maybe CTRL-B (as in Button)

Shift + espace or Shift + enter ?


chore: set @mongodb/enterprise-advanced as dependabot pr reviewers

Proposed changes
set @mongodb/enterprise-advanced as dependabot pr reviewers, add a mongocli label on prs

Jira ticket: CLOUDP-#

Closes #[issue number]
Checklist

[ ] I have signed the MongoDB CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[ ] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[ ] I have updated test/README.md (if an e2e test has been added)
[ ] I have run make fmt and formatted my code

Further comments

linked to https://github.com/mongodb/mongodb-atlas-cli/pull/3315


port to protocol-9p >= 0.11.0

several packages renamed into jbuilder-style module namespaces
use upstream send_pings support for 9P heartbeats

w/ assist from @djs55

oops this might supersede #547 @samoht -- also includes 0.11 improvements

The Docker files don't build. Do they work for you? Maybe they need a newer base image...
The following dependencies couldn't be met:
  - protocol-9p -> lwt = 3.0.0
    no matching version

I've pushed a working refreshed base image and also fixed the tests.

I dont understand why CircleCI failed...

'cause you need the other https://github.com/moby/datakit/pull/547/commits/0bf8e879a44c8b5e44fc720e943829eb1e0ea984
(and the other patches might be useful too)

thx @samoht, cherry picked your patches

I've pushed a fix for appveyor


Error: [node-persist][readFile] ... does not look like a valid storage file!

POST /resources/subscribe 200 - - 3.177 ms
Error: [node-persist][readFile] .node-persist/storage/b48b13e73a6ac2a86dc54425dd24d9ff does not look like a valid storage file!
    at ./libre-billboardoo-frontend/node_modules/node-persist/src/local-storage.js:314:89
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)

Could you please elaborate on the issue? When does this error occur? While using the Push API? At random intervals?
Please provide more information

At random intervals.

That's weird. Are you using the Push API in the project?

At random intervals.

That's weird. Are you using the Push API in the project?

No, I just used npx remix-pwa@latest
Maybe this is a problem?
https://github.com/wakboardoo/libre-billboardoo-frontend/blob/19aa2a99e7efb9cde187e64b087d67730f3e6612/app/entry.client.tsx#L46-L73

Yes. You can disable it, that part is for Push API. Remove that section, restart the app.
You might want to delete caches and unregister the SW then re-register it.

Closing issue as resolved


Fix for Dependencies with classifier and SNAPSHOT

Fixes issue #3786
Dependencies with a classifier and SNAPSHOT version cannot be resolved bug
Fixes Issue #3786
Description of Change
Since recent changes to workaround MSHARED-998 the use of the class ArtifactResult appeared in the code. While this class looks like ArtifactCoordinate, we have to take care of the getVersion() method because for SNAPSHOT versions it provides the timestamped result, not the 'real' version.
So I only changed the getVersion() by getBaseVersion() call for class ArtifactResult.
I have tested the change manually with a fake project and it solves the  DependencyNotFoundException as expected.
Have test cases been added to cover the new functionality?
no, not yet, sorry...

ping @aikebah as you may want to review my (minor) change on the method sameArtifact(...) you recently added to work around MSHARED-998

For an explanation of getVersion() VS getBaseVersion() here is a comment by Robert Scholte of Maven: https://stackoverflow.com/questions/19196836/use-case-of-artifact-getbaseversion#comment28405796_19196934

LGTM

Thanks for the PR @fmarot overlooked this scenario, which has bitten me in other cases in the past. When I read your ping and the summary it was immediately obvious to me what the change was about


Good catch, thanks. @ArturMoczulski can you take a look? We will also want to make sure there's a test for this case.

This looks good to me, this was part of the original set of changes moving from 0.18.2 to 1.0.0, c.f. https://github.com/rollbar/rollbar-php/commit/709fae9ee7f389b48e762ae8b5ac41b3cbbef635#diff-b156308dfc58bccc36efd0ce1cb4d496L68
The behaviour in 0.18.2 is the same as this PR, so for compatibility alone this is a good change.

Let's merge this PR so I can start working on a test

👍


[JENKINS-47808] Fix OutOfMemoryException when parsing huge JMeter XML result file

My try to fix [JENKINS-47808].
The first commit is here to reproduce the bug (with an infinite inputstream to simulate huge XML file).
The second commit fix the bug by using a StAX implementation to detect the XML file type.

Codecov Report

Merging #148 into master will decrease coverage by 0.04%.
The diff coverage is 70.58%.

@@            Coverage Diff            @@
##           master    #148      +/-   ##
=========================================
- Coverage   68.34%   68.3%   -0.05%
=========================================
  Files          44      44
  Lines        3895    3896       +1
  Branches      678     678
=========================================
- Hits         2662    2661       -1
  Misses        989     989
- Partials      244     246       +2

Impacted Files
Coverage Δ

...on/plugins/performance/parsers/ParserDetector.java
73.01% <70.58%> (-2.8%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks!


Valgrind - FreeBSD 11.0-CURRENT amd64

Memcheck, a memory error detector
 Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
 Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
 Command: ./ekr_loop
 Parent PID: 86141

Syscall param ioctl(generic) points to uninitialised byte(s)
    at 0x518F7BA: ioctl (in /lib/libc.so.7)
    by 0x5137DB2: if_nametoindex (in /lib/libc.so.7)
    by 0x4061B8: sctp_init_ifns_for_vrf (sctp_bsd_addr.c:479)
    by 0x4061B8: sctp_init_vrf_list (sctp_bsd_addr.c:676)
    by 0x42CC62: sctp_pcb_init (sctp_pcb.c:6834)
    by 0x4320DF: sctp_init (sctp_usrreq.c:170)
    by 0x4017F2: main (ekr_loop.c:278)
  Address 0x7fef00974 is on thread 1's stack
  in frame #1, created by if_nametoindex (???)

 Syscall param ioctl(generic) points to uninitialised byte(s)
    at 0x518F7BA: ioctl (in /lib/libc.so.7)
    by 0x42F263: sctp_userspace_get_mtu_from_ifn (sctp_userspace.c:49)
    by 0x425279: sctp_add_addr_to_vrf (sctp_pcb.c:612)
    by 0x4061E6: sctp_init_ifns_for_vrf (sctp_bsd_addr.c:477)
    by 0x4061E6: sctp_init_vrf_list (sctp_bsd_addr.c:676)
    by 0x42CC62: sctp_pcb_init (sctp_pcb.c:6834)
    by 0x4320DF: sctp_init (sctp_usrreq.c:170)
    by 0x4017F2: main (ekr_loop.c:278)
  Address 0x7fef00928 is on thread 1's stack
  in frame #1, created by sctp_userspace_get_mtu_from_ifn (sctp_userspace.c:41)

 HEAP SUMMARY:
     in use at exit: 12,992 bytes in 21 blocks
   total heap usage: 21,548 allocs, 21,527 frees, 15,851,333 bytes allocated

 LEAK SUMMARY:
    definitely lost: 0 bytes in 0 blocks
    indirectly lost: 0 bytes in 0 blocks
      possibly lost: 0 bytes in 0 blocks
    still reachable: 12,992 bytes in 21 blocks
         suppressed: 0 bytes in 0 blocks
 Rerun with --leak-check=full to see details of leaked memory

 For counts of detected and suppressed errors, rerun with: -v
 Use --track-origins=yes to see where uninitialised values come from
 ERROR SUMMARY: 25 errors from 2 contexts (suppressed: 0 from 0)

Fixed. The if_nametoindex issue requires the following change to  libc.


nixos/nscd: use nsncd by default

As announced in the NixOS 22.11 release notes, 23.05 will switch NixOS to using nsncd (a non-caching reimplementation in Rust) as NSS lookup dispatcher, instead of the buggy and deprecated glibc-provided nscd.
If you need to switch back, set services.nscd.enableNsncd = false, but please open an issue in nixpkgs so your issue can be fixed.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Congrats!


Client for upcoming rancher_public_dns service

This PR contains the POC for a client for the rancher_public_dns api

go-rancher/client/rancher_public_dns  -  contains the generated classes from the rancher_public_dns schema

go-rancher/client/common.go  - Changes needed in common.go code to facilitate the http request flow using custom auth token instead of Basic auth.

@ibuildthecloud  please can you review this poc. If things look ok, I will continue using this client for all the rancher-public_dns api's.

@ibuildthecloud @prachidamle shouldn't we put a project specific - dns in this case - client code under go-rancher project? To me it would make sense to put it to the dns repo

i agree that the DNS client should go in a different repo.  The same generator can be used and import go-rancher, but the generated code should go to a different tepi

@alena @ibuildthecloud  Moved the client code to rancher_public_dns private repo


Refactor the workflow system to combine in UFS-WM NoahMP App

Clean up and phase out land-driver/CCPP and vec2tile/tile2vecor codebase
Apply increment to UFS restarts

The current code to add DA increment generated by JEDI to UFS sfc data restart uses the tile2vector and the fractional grid cells.

Close it for now. Will revisit this issue after testing the reproducibility.


ValueError: unknown url type

Periodically observe the glitch after upgrade 10 days ago, nothing has changed. See screenshots.

My version youtube-dl: 2017.01.29. I use the app qPython. This same problem occurs with this playlist: https://www.youtube.com/watch?v=fkzGLro1PXI&list=PLTCvoQuRThNp41WNnl02lHiY-5zMtIwOM. I can give you even more than a hundred links to are experiencing this problem, but many video he shakes without any problems.

You are using an outdated version of youtube-dl. Read this FAQ entry if you have troubles updating.


Can't use with JavaScriptServices app

I'm sure the 'issue' here is the end user, but unsure where I'm going wrong
Using the https://github.com/aspnet/JavaScriptServices starter
Running Angular 4.1.2 with 2.0.0 version of angular-application-insights
This is my app.module.client.ts
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { FormsModule } from '@angular/forms';
import { HttpModule } from '@angular/http';
import { sharedConfig } from './app.module.shared';
import { SharedService } from './services/shared.service';
import { ApplicationInsightsModule, AppInsightsService } from '@markpieszak/ng-application-insights';

@NgModule({
    bootstrap: sharedConfig.bootstrap,
    declarations: sharedConfig.declarations,
    imports: [
        BrowserModule,
        FormsModule,
        HttpModule,
        ApplicationInsightsModule.forRoot({
            instrumentationKey: 'key-removed-for-github'
        }),
        ...sharedConfig.imports
    ],
    providers: [
        { provide: 'ORIGIN_URL', useValue: location.origin }, SharedService, AppInsightsService
    ]
})
export class AppModule {
}

And this is the console error I get in Chrome
Angular application insights Error [downloadAndSetup]:  TypeError: applicationinsights_js_1.AppInsights.downloadAndSetup is not a function
    at AppInsightsService.init (main-client.js:1481)
    at new ApplicationInsightsModule (main-client.js:1281)
    at AppModuleInjector.createInternal (ng:///AppModule/module.ngfactory.js:262)
    at AppModuleInjector.NgModuleInjector.create (vendor.js:14073)
    at NgModuleFactory.create (vendor.js:14046)
    at vendor.js:15287
    at ZoneDelegate.invoke (vendor.js:83283)
    at Object.onInvoke (vendor.js:14664)
    at ZoneDelegate.invoke (vendor.js:83282)
    at Zone.run (vendor.js:83043)

Any ideas?

Haven't tried it with that first basic angular4 integration, does this happen right on page load?

https://github.com/MarkPieszak/aspnetcore-angular2-universal/issues/329#issuecomment-313381570
Thanks to @marchel2 for posting it

Make sure you are calling the injector to get AppInsightsService during ngOnInit:

export class HomeComponent implements OnInit {

    private AIService: AppInsightsService;
    private isBrowser: boolean;

    constructor( @Inject(PLATFORM_ID) private platformId, private injector: Injector) {
        this.isBrowser = isPlatformBrowser(this.platformId);
    }

    ngOnInit() {
        if (this.isBrowser) {
            this.AIService = <AppInsightsService>this.injector.get(AppInsightsService);
            this.AIService.trackEvent('Testing', { 'user': 'me' });
        }
    }
}

This should be fixed now, the readme also showcases how to use it with JavascriptServices or my companion repo. Hope that helps!

I am trying to use the library with the dotnet angular template provided by the aspnet templating team.
I did everything exactly as stated in the documentation.
I have a shared AppModule and one for the server and another one for the browser. During ssr only the server one and the shared one used. I load the appinsights module in the browser AppModule.
I am injecting the AppInsightsService through the injector only if it is running in the browser.
Still, I get an error during prerendering: Microsoft.AspNetCore.NodeServices.HostingModels.NodeInvocationException: Prerendering failed because of error: ReferenceError: define is not defined
The problem occurs at applicationinsights-js\bundle\ai.module.js:187:1, so this line:
define("JavaScriptSDK.Module/AppInsightsModule", ["require", "exports"], function (require, exports).
I have tried the https://github.com/MarkPieszak/aspnetcore-angular2-universal starter project and it works fine with this module, but I have to use the other template.
Do you have any idea how to resolve this?


Appstudio update test-component-pac-hdon

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-hdon-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
16 seconds
deprecated-base-image-check

✅ Succeeded
17 seconds
sanity-inspect-image

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
16 seconds
sbom-json-check

✅ Succeeded
47 seconds
clamav-scan

✅ Succeeded
9 seconds
sanity-optional-label-check

✅ Succeeded
9 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-hdon-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
16 seconds
clone-repository

✅ Succeeded
29 seconds
build-container

✅ Succeeded
11 seconds
sanity-inspect-image

✅ Succeeded
12 seconds
clair-scan

✅ Succeeded
11 seconds
deprecated-base-image-check

✅ Succeeded
36 seconds
clamav-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
9 seconds
sanity-optional-label-check

✅ Succeeded
8 seconds
sanity-label-check

✅ Succeeded
5 seconds
show-summary

Pipelines as Code CI/test-component-pac-hdon-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
16 seconds
clone-repository

✅ Succeeded
29 seconds
build-container

✅ Succeeded
11 seconds
sanity-inspect-image

✅ Succeeded
11 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
clair-scan

✅ Succeeded
36 seconds
clamav-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
9 seconds
sanity-optional-label-check

✅ Succeeded
8 seconds
sanity-label-check

✅ Succeeded
5 seconds
show-summary


Use terraform-oci-vcn module, terraform-oci-bastion, terraform-oci-operator

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Use terraform-oci-vcn module: https://github.com/oracle-terraform-modules/terraform-oci-vcn
instead of managing base as a monolithic module.
New or Affected Resource(s)

Potential Terraform Configuration

# Copy-paste any Terraform configurations for how the requested feature may be used.

References

The admin module will be renamed to operator
vcn: https://registry.terraform.io/modules/oracle-terraform-modules/vcn/oci/1.0.1
bastion: https://registry.terraform.io/modules/oracle-terraform-modules/bastion/oci/1.0.1
operator: https://registry.terraform.io/modules/oracle-terraform-modules/operator/oci/1.0.4

Done in #51


Unifying the code style with "PHP CS Fixer"

Having a unified code style will allow every contributor to write code with the same style everywhere.
This is a great tool for it: https://github.com/FriendsOfPHP/PHP-CS-Fixer
A template example extracted from PHPUnit: https://github.com/sebastianbergmann/phpunit/blob/master/.php_cs.dist

Sounds good. I look at it, but there are so many changes that I have to figure out a ruleset that isn't doing so many changes and than move this in the direction of PSR-12.

This issue is now fixed:

I set up a .php_cs.dist file
Fixed the code according to the rules
Integrated it into the CI


feat(AvatarUpload): implement AvatarUpload

FX-2889
Description

implemented new component AvatarDropzone
I decided to skip the title and file description parts for now. They can be introduced in another new component if needed.
I solved the focused state differently than the designs to simplify the implementation.

How to test

you can use temploy to test the component. Default story is mimicking the uploading UX

Screenshots

Development checks

[x] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Make sure that additions and changes on design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests

Breaking change

codemod is created and showcased in the changeset
test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-bot run all

@toptal-anvil ping reviewers

@toptal-anvil ping reviewers

@toptal-anvil ping reviewers

Closing this due to not confuse with new designs and implementations here https://github.com/toptal/picasso/pull/3068


Where is the latest version used in the example page?

The example page (https://mozilla.github.io/pdf.js/web/viewer.html) appears to be using version 4.1.243, while the releases page shows version 4.0.379.
It appears that 4.1.243 resolves a Chrome Print Preview crasher bug for some printer drivers, but I don't know where I can download it.
Can you point me in the right direction please?

The example page (https://mozilla.github.io/pdf.js/web/viewer.html)

Please note that that's a development version, and consequently it's not a good idea (nor officially supported) to use that one in production environments since doing so may cause problems (either now or later).
Hence we don't distribute that, and you'd need to build it yourself; see https://github.com/mozilla/pdf.js?tab=readme-ov-file#getting-the-code and https://github.com/mozilla/pdf.js?tab=readme-ov-file#building-pdfjs


how about dbclick action ,and then twice copy result

hi,how about dbclick action ,and then twice copy result.sometimes it is useful.i dont need copy two times.

Hey @tryfashion, it sounds interesting. Well, there are some bugs that I will be contributing first to solve, but definitely, after them, I'll be considering all related proposals to triage and potentially work on them, okay? Thank you so much for proposing it.