utils/repology: update API URL

The Repology API has changed since our original implementation, but since it's been redirecting it hasn't been an issue for us until #15804 noted that packages like bonnie++ weren't being checked by brew bump. With the original API scheme the fix would be to URL-encode the plus sign characters, but simply updating the URL fixed it as well.
(The current API unfortunately doesn't have the option of returning just the results for a single package in a single repository, so we've been wading through the results of every repository a given package is in, which has been slowing down the command considerably.)
$ brew bump --no-pull-requests --formula -d bonnie++
/usr/local/Homebrew/Library/Homebrew/brew.rb (Formulary::FormulaLoader): loading /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/bonnie++.rb
/usr/bin/env /usr/local/opt/curl/bin/curl --disable --cookie /dev/null --globoff --show-error --user-agent Homebrew/4.1.3-23-gd2863d0-dirty\ \(Macintosh\;\ Intel\ Mac\ OS\ X\ 10.13.6\)\ curl/7.54.0 --header Accept-Language:\ en --retry 3 --location --silent https://repology.org/api/v1/project/bonnie\+\+
==> bonnie++ is up to date!
Current formula version:  2.00a
Latest livecheck version: 2.00a
Latest Repology version:  2.00a
Open pull requests:       none
Closed pull requests:     none

Fixes #15804 (both mentioned issues).

Thanks again @EricFromCanada!


Rootful CNI port forwarder does not work for (deprecated) CentOS 7

Rootful CNI port forwarder does not work for CentOS 7, although it works for other templates such as AlmaLinux 8
YAML:
images:
- location: "https://cloud.centos.org/altarch/7/images/CentOS-7-x86_64-GenericCloud-2009.qcow2"
  arch: "x86_64"
  digest: "sha256:e38bab0475cc6d004d2e17015969c659e5a308111851b0e2715e84646035bdd3"
containerd:
  system: true
  user: false
firmware:
  legacyBIOS: true
cpuType:
  x86_64: "Haswell-v4"

lima sudo /usr/local/bin/nerdctl run -it --rm -p 8080:80 nginx:alpine does not seem to expose the port 8080.
Tested v0.10.0, v0.11.3, and master 1af48114f55b0c80eaf0981f6ffcf7a7550f3f7c

Hit this error on ubuntu as well.
limactl shell default  sudo nerdctl run -it -p 50500:80 ubuntu

Is there a workaround for this?


added content for missing error message cs4033

Summary
added content for missing error message cs4033

One additional change we should make:  Remove the F1 keyword for this error in the "sorry we don't have information..." page:
https://github.com/dotnet/docs/blob/main/docs/csharp/misc/sorry-we-don-t-have-specifics-on-this-csharp-error.md?plain=1#L143


Allow option to generate .classpath paths  relative to user.home, rather than absolute

Currently, sbteclipse generates absolute pathnames into the ivy repository. This is the main reason why my .classpath files are not portable across machines. I would like a way to generate paths relative to my user.home location, since the default ivy2 repo is relative to that.
sbt-idea currently does this, eg:
root url="jar://$USER_HOME$/.ivy2/cache/junit/junit/jars/junit-4.7.jar!/"
Some evidence that this is an issue for other people also:
http://stackoverflow.com/questions/12983203/use-userprofile-in-eclipse-classpath-windows
http://stackoverflow.com/questions/14663211/change-name-and-or-path-of-classpath-file-in-eclipse?rq=1

Any updates on this issue? It would be nice to have portable .classpath files.

I just faced this issue too.
It would be nice to have portable .classpath.
Currently, to deal with it, I need to re-run sbteclipse on the project on each machine, and also ignore .classpath and project settings files in the version control system -- so that they don't constantly conflict.


Deprecated info on the docs

Nuxt 3 docs says nuxt modules are now build-time only and  buildModules property is deprecated in favor of modules

nuxt/google-fonts docs says  Nuxt < v2.9 users should use modules property in nuxt.config.js instead of buildModules. Causing a misunderstanding that buildModules property and dev flag should be used on nuxt versions later than v2.9 , which is wrong.

Why is this closed? The documentation isn't updated yet.
Maybe it's common knowledge experienced Nuxt users but I could have saved me quite some time if I knew this earlier.

Why is this closed? The documentation isn't updated yet. Maybe it's common knowledge for experienced Nuxt users but I could have saved me quite some time if I knew this earlier.

because it is https://google-fonts.nuxtjs.org/getting-started/setup


Vulnerabilities in fluent/fluentd-kubernetes-daemonset:v1.13-debian-forward-1

I scanned fluent/fluentd-kubernetes-daemonset:v1.13-debian-forward-1  image with trivy, it returns 250+ CVEs.
Total: 257 (UNKNOWN: 6, LOW: 159, MEDIUM: 42, HIGH: 42, CRITICAL: 8)
All vulnerabilities listed :  vuln.txt
There are lot of vulnerabilities there it seems. I guess this is due to underlying debian image.
Could you please fix these vulnerabilities in the image ?

Thanks,
But the attached file contains your host OS's vulnerabilities, so this list is not accurate apparently.
This image is derived from buster-slim image, could you help to clarify which CVE affects it actually?
It seems that it should be forwarded to https://github.com/docker-library/ruby/tree/master/2.6/slim-buster instead.
If it contains vulnerabilities that are not contained in buster-slim, it should be fixed, though.

@kenhys Thanks for pointing it out. Yes all vulnerabilities are host OS's. I think its because of the base image buster-slim.
I would forward it to  https://github.com/docker-library/ruby/tree/master/2.6/slim-buster.
However, are you going to use alpine image as base image which has very few vulnerabilities compared to buster ?
BTW, these are the vulnerabilities found for fluentd :

Target : usr/local/bundle/gems/http_parser.rb-0.6.0/Gemfile.lock

ID
SEVERITY
PACKAGE
VERSION
FIXED IN

CVE-2018-1000201
HIGH
ffi
1.0.11
1.9.24

CVE-2018-1000201
HIGH
ffi
1.0.11-java
1.9.24

CVE-2020-10663
HIGH
json
1.8.0
2.3.0

CVE-2020-10663
HIGH
json
1.8.0-java
2.3.0

CVE-2017-16516
HIGH
yajl-ruby
1.1.0
1.3.1

CVE-2020-8130
HIGH
rake
0.9.2
12.3.3

Target : fluent/Gemfile.lock

CVE-2021-32740
HIGH
addressable
2.7.0
2.8.0

Target : usr/local/bundle/gems/async-http-0.50.7/examples/fetch/Gemfile.lock

CVE-2020-8184
HIGH
rack
2.2.2
2.2.3, 2.1.4

Target : usr/local/bundle/gems/async-http-0.50.7/examples/fetch/Gemfile.lock

This case is false positive because it is not used.

fluent/fluentd-kubernetes-daemonset:v1.13-debian-forward-1 image is updated from time to time,
current image doesn't have such vulnerabilities. The current image point to v1.13.3-debian-forward-amd64-1.1.

ffi 1.15.3
yajl-ruby 1.4.1
json 2.4.1
rake 13.0.6
addressable 2.8.0

I guess you checked the old image.

Thanks @kenhys !


Can i capture ajax request or createSpy  api

Are you requesting a feature or reporting a bug?
i want to test a case that when i scroll to the bottom and send a ajax request.
what should i do?
What is the current behavior?
What is the expected behavior?
How would you reproduce the current behavior (if this is a bug)?
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code

Specify your

operating system:
testcafe version:
node.js version:

Hi @chenby,
To scroll a page to the bottom you can use the hover action:
await t.hover('body', { offsetY: -1 });

You can send an xhr-request via ClientFunction:
const sendXhr = ClientFunction(() => {
    // here is xhr sending code
});

await sendXhr();

Thanks。
I mean that my website send an xhr-request,and How do i know it can work.

It there some results of this xhr-request? I suppose it should be some new markup? If so, you can check that the markup is added.
await t
    .hover('body', { offsetY: -1 })
    .expect(Selector('some-new-element').exists).ok();

It just report some event, and return {code：200}

We have no such built-in functionality but we've planned to implement it: #1341.
As a workaround you can use some third-party library to handle requests, for exapmle nock

Thanks a lot


[webhook] Add support for serviceAccount imagePullSecrets

Description
As the title says, add support to use imagePullSecrets attached to the ServiceAccount of a Pod to access private docker registries.
Also add some logging to see which secret was actually used.

@bonifaido I just tested this and I think this is unnecessary. A pod that uses a ServiceAccount that has  an imagePullSecret attached, will have the imagePullSecret injected automatically. So from the point of view of the vault-secrets-webhook, the imagePullSecret is always attached to the pod, no need to handle this specific situation in the vault-secrets-webhook code.
I just checked the official documentation for this: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account

Now, any new pods created in the current namespace will have this added to their spec:
spec:
 imagePullSecrets:
 - name: myregistrykey

Did I misinterpret your intentions in regard to this feature?

In that case, we are fine, which is great! TBH I didn't know that this happens automatically. Sorry for that!

@bonifaido Neither I nor my colleagues did know that it works like this :smile: I have removed the logic dealing with the service accounts and just left the small additions to the logging in. I also clarified the situation with regard to the ServiceAccount in the comments.
I just want to test the changes in our setup and if everything works, I will mark this ready for review.


Can you set the background color to be transparent?

If so, how can we achieve this goal?
Related to article, https://docs.microsoft.com/en-us/microsoftteams/manage-praise-app

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


feat(stylesheets/_header): update banner logo

Goal is to keep our engineering stuff "on brand" with the rest of the stuff. Image was provided by branding team.

I don't see the removal of the existing header background image? How was that existing image present in this code?

There wasn't one. The existing header was just a background color overlayed with the Widen Logo + "Widen Engineering" text. The mockup that I saw had the new image underneath that.
I actually made the same mistake and spent too much time trying to make a new asset version for the existing logo/header in order to keep analytics working. Then I checked the mockup :P
The header is defined here https://github.com/Widen/widen.github.io/blob/develop/_includes/header.html#L5


[BugFix] Fix irecv for lazy tensordicts

Description
Describe your changes in detail.
Motivation and Context
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
You can use the syntax close #15213 if this solves the issue #15213

[ ] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Remove all that do not apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[ ] Example (update in the folder of examples)

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[ ] I have read the CONTRIBUTION guide (required)
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly (required for a bug fix or a new feature).
[ ] I have updated the documentation accordingly.

Codecov Report
Patch and project coverage have no change.

Comparison is base (14e9aec) 88.28% compared to head (1c4c016) 88.29%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #274   +/-   ##
=======================================
  Coverage   88.28%   88.29%
=======================================
  Files          28       28
  Lines        9678     9677    -1
=======================================
  Hits         8544     8544
+ Misses       1134     1133    -1

Flag
Coverage Δ

linux-cpu
86.30% <ø> (+<0.01%)
:arrow_up:

linux-gpu
88.22% <ø> (+<0.01%)
:arrow_up:

linux-macos-cpu
?

linux-stable-cpu
86.33% <ø> (+<0.01%)
:arrow_up:

linux-stable-gpu
88.22% <ø> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

tensordict/tensordict.py
82.32% <ø> (+0.03%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Add version tags

I want to use in my rails app through rails-assets.org

@rjgarciadelpino , there are version tags. If you do git tag, it will show you. Unless I don't see something :) Let me know please

Perhaps you meant this page: https://github.com/psergus/ngWYSIWYG/tags
However, this will appear when we have the first release. I guess it will happen soon when I add tests.

Ok! I thought it was production ready!
El 20/10/2015 22:34, "Sergey Petrenko"<EMAIL_ADDRESS>escribió:

Perhaps you meant this page: https://github.com/psergus/ngWYSIWYG/tags
However, this will appear when we have the first release. I guess it will
happen soon when I add tests.
—
Reply to this email directly or view it on GitHub
https://github.com/psergus/ngWYSIWYG/issues/15#issuecomment-149693987.

I use it on my production site. However, I would like to add testing suite before the public can accept it as a production ready. You know what I mean :)

@psergus perhaps you can start with beta versions v0.1 so that we don't keep changing our code to make it compatible with the directive upgrades

ashuorg, good idea. I will wrap it up and do asap
Sent from my iPhone

On Dec 17, 2015, at 3:22 AM, ashuorg<EMAIL_ADDRESS>wrote:
@psergus perhaps you can start with beta versions v0.1 so that we don't keep changing our code to make it compatible with the directive upgrades
—
Reply to this email directly or view it on GitHub.

I did a release. Thx for the suggestion :)
On Thu, Dec 17, 2015 at 7:33 AM, Sergey Petrenko<EMAIL_ADDRESS>wrote:

ashuorg, good idea. I will wrap it up and do asap
Sent from my iPhone
On Dec 17, 2015, at 3:22 AM, ashuorg<EMAIL_ADDRESS>wrote:
@psergus https://github.com/psergus perhaps you can start with beta
versions v0.1 so that we don't keep changing our code to make it compatible
with the directive upgrades
—
Reply to this email directly or view it on GitHub
https://github.com/psergus/ngWYSIWYG/issues/15#issuecomment-165428220.

--
Best regards,
Sergey Petrenko

I have created a pull-request to help on dealing with tags, patchs, features and releases. Hopefully @psergus will accept it :+1:
Besides that, since there is at least one tag already (v0.3.3), I think we can close this issue.


Certora's formal verification code

Thanks so much for this @RedLikeRosesss! Could you add a README to this folder as to how to run those code


React native expection java.lang.UnsatisfiedLinkError: dlopen failed: “/data/data/{package}/lib-main/libgnustl_shared.so” is 32-bit instead of 64-bit

I am trying to integrate React Native with my existing Android App. I am getting the following exception when initializing React Native Screen:
java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/com.snapdeal.main/lib-main/libgnustl_shared.so" is 32-bit instead of 64-bit
The App is only crashing on 64-bit devices.
As per my learning so far, I've found this issue reported on React Native Repo, but the solution suggested in this thread is not helpful as I am not using any external SO library in existing App.
Apart from above, I've realized another difference in library structure on the device where my App is installed. I am comparing structure of my App vs react native demo app.
React demo App

root@generic_x86_64:/data/data/com.react.demo/lib # ls
libfb.so
libfolly_json.so
libglog.so
libglog_init.so
libgnustl_shared.so
libicu_common.so
libimagepipeline.so
libjsc.so
libreactnativejni.so
libreactnativejnifb.so
root@generic_x86_64:/data/data/com.react.demo/lib-main # ls
dso_deps
dso_lock
dso_manifest
dso_state

My App

root@generic_x86_64:/data/data/com.my.app/lib-main # ls
dso_deps
dso_lock
dso_manifest
dso_state
libfb.so
libfolly_json.so
libglog.so
libglog_init.so
libgnustl_shared.so
libicu_common.so
libimagepipeline.so
libjsc.so
libreactnativejni.so
libreactnativejnifb.so

Sharing few more details about my project:
package.json

{
"name": "projectname",
"version": "1.0.0",
"description": "Native NPM",
"main": "index.js",
"scripts": {
"test": "echo "Error: no test specified" && exit 1",
"start": "node node_modules/react-native/local-cli/cli.js start"
},
"repository": {
"type": "git",
"url": ""
},
"author": "Ishan D",
"license": "ISC",
"dependencies": {
"react": "^15.3.2",
"react-native": "^0.37.0",
"react-native-linear-gradient": "^1.5.15",
"rn-viewpager": "^1.1.3"
},
"devDependencies": {}
}

dependencies used in android native project

ext {
compileSdkVersion = 24
buildToolsVersion = '24.0.2'
minSdkVersion = 16
targetSdkVersion = 24
supportLibrariesVersion = '23.0.1'
playServiceVersion = '9.0.2'
dep = [
        fabricPlugin          : 'io.fabric',
        fabricMavenUrl        : 'https://maven.fabric.io/public',
        fabricClasspath       : 'io.fabric.tools:gradle:1.+',

        playServiceClasspath  : 'com.google.gms:google-services:1.3.0-beta1',
        playServicePlugin     : 'com.google.gms.google-services',

        playServiceAppindexing: "com.google.android.gms:play-services-appindexing:$playServiceVersion",
        playServiceLocation   : "com.google.android.gms:play-services-location:$playServiceVersion",
        playServiceVision     : "com.google.android.gms:play-services-vision:$playServiceVersion",
        playServiceAuth       : "com.google.android.gms:play-services-auth:$playServiceVersion",
        playServiceBase       : "com.google.android.gms:play-services-base:$playServiceVersion",
        playServiceIdentity   : "com.google.android.gms:play-services-identity:$playServiceVersion",
        playServiceAnalytics  : "com.google.android.gms:play-services-analytics:$playServiceVersion",
        playServiceGcm        : "com.google.android.gms:play-services-gcm:$playServiceVersion",

        underCouchClasspath   : 'de.undercouch:gradle-download-task:2.0.0',
        underCouchPluigin     : 'de.undercouch.download',

        crashlytics           : 'com.crashlytics.sdk.android:crashlytics:2.4.0@aar',

        moengage              : 'com.moengage:moe-android-sdk:6.0.29',

        supportV4             : "com.android.support:support-v4:$supportLibrariesVersion",
        supportAppCompatV7    : "com.android.support:appcompat-v7:$supportLibrariesVersion",
        supportCardviewV7     : "com.android.support:cardview-v7:$supportLibrariesVersion",
        supportDesignV7       : "com.android.support:design:$supportLibrariesVersion",

        okhttp                : 'com.squareup.okhttp:okhttp:2.5.0',
        junit                 : 'junit:junit:4.12',
        mockito               : 'org.mockito:mockito-core:1.10.19'
]

}

Any clue is appreciated.

React Native version: 0.37.
Platform: Android
Operating System: Android M +

ReactNative doesn't provide 64-bit libraries, checkout discussions here:

https://github.com/facebook/react-native/issues/2814
https://github.com/facebook/react-native/issues/9454

If you just run something trivial like the demo app can you get that working on the 64-bit device you are testing with?

@lacker Yes, demo app was working and I got my App working as well. The problem was because of react-native android dependencies. I've used the same maven url as in docs here without looking at my projects dir structure.

I'm having this same issue... My maven url is correct though...
React Native 0.41.2, integrating into an existing app. Error occurs only when trying to render a react view. Overlay permissions are set correctly, and the React packager is running.

When I run app (using 'react-native run-android' command) at 64-bit smartphone it worked fine, but release version apk crashed instantly, while same apk also working fine at 32-bit smartphone
RcaHandler: Build: Sony/E5603/E5603:6.0/30.2.A.0.100/167960284:user/release-keys
RcaHandler: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/com.garagemobileapp/lib-main/libgnustl_shared.so" is 32-bit instead of 64-bit
RcaHandler: 	at java.lang.Runtime.load(Runtime.java:332)
RcaHandler: 	at java.lang.System.load(System.java:1069)

do you solve you problem ? so did i have this problem

+1
Running RN 0.43.3. Worked fine on my Nexus 6, doesn't work on my Pixel. Both are on Android 7.1.2.
I can run the app if I add this to my build.gradle file, but then other things seem to break in my React views.
ndk {
    abiFilters "armeabi-v7a", "x86"
}

packagingOptions {
    exclude "lib/arm64-v8a/librealm-jni.so"
}

+1, same error on API 23 device when using 0.44.2 with existing app integration.
After adding following seems works ok:

locating the gradle.properties file in the root project, and add Android.useDeprecatedNdk=true.

in the build.gradle of the app:

android {
    ...
    defaultConfig {
        ...
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }

        packagingOptions {
            exclude "lib/arm64-v8a/librealm-jni.so"
        }
    }
}

In this way, using 32bit so instead of 64 bit, still, hope there's an official solution.

Thanks @sduqlsc that worked for me too. Though I only needed to add:
android {
    ...
    defaultConfig {
        ...
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
}

Btw, the above code is also part of the boilerplate Android project that is created when you would run react-native init. Though I'm not sure what the impact would be of disabling arm64 / x86_64 output.

@mattijsf glad to hear that. 👍

@sduqlsc @mattijsf 👍🏻 thanks man

No official words from the react team?

It's also in effect when using Litho lib

Thanks @sduqlsc @mattijsf
Iam using fresco and unity.
and placing
 ndk {
            abiFilters "armeabi-v7a", "x86"
        }

inside defaultConfig solved my problem
But i want to know impact of this configuration , Thanks

@BALUSANGEM the reason why should config certain ndk abiFilters is that this is configured in the jni file—— check out  your react native project directory\node_modules\react-native\ReactAndroid\src\main\jni\Application.mk：

As for the impact, some 3rd party libraries may only provide armeabi instead of "armeabi-v7a", "x86". So in my opinion, there is a risk of app crash.

I have the same problem，I must add   'armeabi', 'arm64-v8a'   to  ndk，
ndk {
abiFilters "armeabi-v7a", "x86", 'armeabi', 'arm64-v8a'
}
How to solve it?

I used
exclude '/lib/mips64/**'
exclude '/lib/arm64-v8a/**'
exclude '/lib/x86_64/**'

and it doesn't work but If I use those:
        exclude 'lib/armeabi-v7a/libgnustl_shared.so'
        exclude 'lib/x86/libgnustl_shared.so'

I'm able to build application and run. But I get explicitly error:
 java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[........] couldn't find "libgnustl_shared.so"
 at java.lang.Runtime.loadLibrary0(Runtime.java:984)
 at java.lang.System.loadLibrary(System.java:1530)


Key derivation seems needlessly convoluted

The way the encryption key is currently derived seems to be:

rand gets 128 or more bits entropy from the OS and seeds a ChaCha PRNG with that
No more than 83 bits of entropy out of it get turned into an alphanumeric string
That string is fed to Argon2 to pad it back to 128 bits of length (still 83 bits of entropy)

The straightforward way to derive an encryption key would be just getting 128 bits from the OS entropy source with getrandom crate, and that seems superior in every way: it is more secure (128 bits of entropy rather than 83), faster (no intermediate time-consuming cryptography), and results in a smaller download size for both the native binary and web client. When the key needs to be represented in text, it can simply be base64-encoded.
Why is key derivation implemented this way, instead of the seemingly superior straightforward solution?
References
The key is derived here:
https://github.com/ekzhang/sshx/blob/91c82d46cde4d1ffa0ae34e2a9a49911e2e53baa/crates/sshx/src/controller.rs#L47
where rand_alphanumeric uses rand::ThreadRng internally:
https://github.com/ekzhang/sshx/blob/91c82d46cde4d1ffa0ae34e2a9a49911e2e53baa/crates/sshx-core/src/lib.rs#L21-L29
The ThreadRng is backed by some sort of ChaCha variant, according to cargo tree.
After the key is derived it is then fed to Argon2 with a public salt:
https://github.com/ekzhang/sshx/blob/91c82d46cde4d1ffa0ae34e2a9a49911e2e53baa/crates/sshx/src/encrypt.rs#L7-L10

The key needs to be short to make the URL shorter. This was a conscious choice, since long URLs are hard to share.
I recognize that rand gets a lot of entropy from the OS, but that's kind of free — it doesn't really make sense for it to request only 83 bits of randomness!

Then at the very least you can skip the entirety of rand and the ChaCha PRNG, and call getrandom directly.

Makes sense! That sounds like a good way to remove a small dependency.

I think the main benefit is making the system more cryptographically sound.
I am convinced that data from getrandom still has the same entropy if you run it through base64 to turn it to ASCII; it is not obvious to me that it still holds when you run it through ChaCha PRNG and then rand's alphanumeric adapter.

For comparison, here's a typical encrypted pastebin URL:
https://www.pastevault.com/paste/HqAOOMMTrBgShmIiGZmNXiDT7RA#krik45QzN6gpp14Qni8fhPcviFV3ZuTtO7O33PIOcE3
That's a 256-bit key, to make the encryption quantum-resistant. This should counter the "collect now, decrypt later" programs that three-letter agencies are known to use.
But as long as you don't care about providing confidentiality that's better than the HTTPS outside this encrypted stream, 83 bits of entropy are probably fine.

Base64 and URLs don't mix that well. That's why there's https://github.com/magiclen/base64-url, if that helps here.


Share SP certificates.

Introduction of a dynamic way of creating and distributing certificates.

[X] Certificate sharing by variables.
[X] Generate a SP certificate in runtime and share it with the ssp cluster.

There are the following two flows that are controlled by their variables.

Certificate sharing by variables :

sp_ssl_cert
sp_ssl_cert_key

Generate a SP certificate in runtime and share it with the ssp machines (cluster).

self_signed_sp_cert_generate: ( true | false )

:link: https://github.com/grnet/rciam-deploy-inv/pull/35

So we have two different certificates ( SP & IdP ) :

Generate self-signed SP certificates
Generate self-signed IdP certificates

and we want for both, a way of automatic generation at the runtime of the Ansible role or simply transferring them to the machines.

To avoid confusion in the generation of certificates - we can simply pass them through variables: https://github.com/rciam/rciam-deploy/pull/31
( We can even transfer them through files. )


[BUG] Netbeans freezes and stop working when i'm trying to write a class static inside a directive

Try to write letter by letter on blade file
@test([ Test1::class, Test2::class, Test3::class ])

I know about it ... it seems to be a bit tricky and the fix might take a while.

Hi I've pushed a patch on the release https://github.com/haidubogdan/netbeans-php-blade-plugin/releases/tag/nb-14102022
The php lexer embedding seems to crash on operations when a embedded text contains "label:text".
The "patchy" solution is to detect in the embeded php text this kind of syntax and see it as plain HTML

Thanks, it don`t freezes  anymore

@haidubogdan hi, it freezes again on current version, is a regression??

Try to write letter by letter on blade file
@test([ Test1::class, Test2::class, Test3::class ])

I think the issue was more or less present in the new version.
Currently the lexer has a workaround to avoid sending the embedding text to php if it contains syntax like (: identifier:identifier which seem to trigger the Php Emebedding freeze.
By splitting the text to be sent for embedding the corner case with (: should be avoided. But it could have the side effect of strange php highlight coloring. So it needs to be monitored.

Thanks, seems to be working again


crypto.subtle is undefined

Hi,
Let me start by saying that this looks like a really interesting and polished project, and this is not so much a bug report as a request for feedback, or perhaps a feature request.
I'm experimenting with self-hosting sshx-server, which doesn't seem to be documented from what I can find, but I've pieced together what might be necessary from the Dockerfile and the development instructions. I've got the server running just fine, I can connect to it with sshx and I get a Link that opens successfully in the browser, but I then get crypto.subtle is undefined in the Firefox dev console.
From this question I gather that the reason might be that crypto.subtle refuses to run over HTTP, which I guess makes sense.
The problem is that my instance of sshx-server needs to run over unencrypted HTTP over a VPN, and there is no CA infrastructure set up that allows me to establish "green" TLS connections in this environment. I appreciate that in normal use-cases, it would be insane to run an sshx server over HTTP, but in this case it's not a problem because only connections over the VPN are allowed anyway, and they are already encrypted and authorized.
Questions:

Would it be possible to make this work without making changes to sshx-server? My initial thought was that maybe using something like nginx to reverse proxy the traffic could at least allow me to use self-signed TLS, but this would require sshx to take some kind of --insecure flag similar to curl to allow the certificate verification to fail, and the browser can then separately choose to connect "insecurely".

Any other ideas on how this could be made to work without having to set up an entire CA infrastructure for the VPN?

I got it to work decently, I think.
I set up caddy on the node running sshx-server and simply told it to:
[vpn-dns]:443 {
    tls internal
    reverse_proxy [vpn-ip]:8080
}

This works with the caveat that the sshx binary itself will refuse to connect to https://foo.bar since the certificate is self signed. Therefore, when connecting you need to make sure you're using regular http:
sshx --server http://[vpn-dns]:8080

Since this isn't the URL you want back in your response link, you also need to run the server component with --override-origin like this:
sshx-server --listen [vpn-ip] --port 8080 --override-origin "https://[vpn-dns]"

The response given when running sshx then correctly has [vpn-dns] in the link.
In summary, I guess a very minor feature request could be to add an --insecure flag to sshx as it would make setup a bit easier.

I'm experimenting with self-hosting sshx-server, which doesn't seem to be documented from what I can find

It is actually mentioned in the README that this is unsupported!

Glad you were able to get it to work for your use case though. Trusting self-signed certificates seems like a reasonable option to have for now. Would #31 fit your use case?

Well that explains why I didn't find anything!
It wouldn't really help in this case unfortunately since this environment has no independent CA and no current plans to implement one.
While supporting additional CAs is also a good idea, I'd argue that it also makes sense to allow the user to bypass certificate authentication for sshx completely if they know what they're doing, much like curl does.
VPN isn't the only use case for this, the connection could also be happening over an SSH tunnel for example, or it could be running on localhost, serving https externally but with no plans to accept external sshx clients. Simply put, it would add a lot of useful flexibility.

Makes sense!


Model type openelm not supported

When attempting to run the example code below for OpenELM, found on Hugging Face, there is an error "ValueError: Model type openelm not supported". It says "ModuleNotFoundError: No module named 'mlx_lm.models.openelm'"
from mlx_lm import load, generate
model, tokenizer = load("mlx-community/OpenELM-1_1B-instruct-4bit")

There is an outstanding PR for this https://github.com/ml-explore/mlx-examples/pull/719

For Posterity - Make sure to get the last release of mlx-lm when trying openELM
 pip install --upgrade mlx_lm


142 Add multi-gpu evaluation to spleen bundle

Signed-off-by: Nic Ma<EMAIL_ADDRESS>Fixes #142 .
Description
This PR added the multi-gpu evaluation config in the spleen bundle.
Status
Ready/Work in progress/Hold
Please ensure all the checkboxes:

[x] Codeformat tests passed locally by running ./runtests.sh --codeformat.
[ ] In-line docstrings updated.
[ ] Update version and changelog in metadata.json if changing an existing bundle.
[ ] Please ensure the naming rules in config files meet our requirements (please refer to: CONTRIBUTING.md).
[ ] Ensure versions of packages such as monai, pytorch and numpy are correct in metadata.json.
[ ] Descriptions should be consistent with the content, such as eval_metrics of the provided weights and TorchScript modules.
[ ] Files larger than 25MB are excluded and replaced by providing download links in large_file.yml.
[ ] Avoid using path that contains personal information within config files (such as use /home/your_name/ for "bundle_root").

/black

/build

/build

/black

/build


Upgrade to typeorm 0.3.7

This PR upgrades to typeorm 0.3.7 (and NestJS v9 in the query-typeorm package).
There are 2 things which I haven't committed and wanted to ask your opinion:

This repo uses Prettier to format the code. Because I didn't have the VSCode extension installed, I always had conflicts when saving file because the default TS formatter / ESLint didn't agree with Prettier. Adding this file will make sure that the Prettier extension is used.

.vscode/settings.json
{
  "editor.defaultFormatter": "esbenp.prettier-vscode"
}

For some reason, by default, I wasn't to debug the tests in packages/query-typeorm/__tests__/services/typeorm-query.service.spec.ts with breakpoints which made it pretty difficult to troubleshoot failing tests. I created an issue here but a workaround I found was to add this file.

.vscode/launch.json
{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Debug Jest Tests",
      "type": "node",
      "request": "launch",
      "runtimeArgs": [
        "--inspect-brk",
        "${workspaceRoot}/node_modules/.bin/jest",
        "--runInBand",
        "-t",
        "set the relation to null", // replace with name of your test
      ],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen"
    }
  ]
}

Finally, typeorm 0.3.x marked a lot of methods as deprecated but they still work (getConnection() etc.). I've only changed the minimum for the code to run and the tests to pass. When this gets merged, I can work on updating the deprecated code.

Thanks for the PR! In #26 I updated a lot of other deps but not Typeorm yet, so this is a nice one!

Thanks for the PR! In #26 I updated a lot of other deps but not Typeorm yet, so this is a nice one!

Yes I saw but my browser crashes when I try to open the PR to see your changes because there are too many modifications I think 🥲

FYI: I have the following plan:

Fix last things in my pr
Merge your PR into my PR
Test everything in my application to be even more sure that everything still works
Profit 🎉

Not sure how I committed into your branch but this is now part of #26, will release it as a alpha release soon so you can start using it and it can be fully tested.

Not sure how I committed into your branch [...]

Uh yes. Probably because I ticked the box "Allow edits and access to secrets by maintainers" and I see from the git history that you merged the branch "improvements" into my branch.
So I'll close this and we will track changes on #26 then.

This is now released in v2.0.0-alpha.1

I don't think I can upgrade yet:

Maybe I'll just wait for your PR to be merged.

I tried upgrading that one but all the tests kept failing, will investigate soon to try to resolve that.
Currently also trying out the v2 alpha in a project of mine to see if everything runs ok.

@GP4cK did you still have issues with @nestjs/common? As it's a peer dep it should not block the usage.
The project I'm testing the v2 alpha in had no issues at all atm so we can update that peer to be v9 of nestjs without it being a issue.

@TriPSs yes npm i still outputs this error message. Are you using npm i --force? Do you mind sharing the content of your package.json dependencies?

@GP4cK im using yarn, will update the peer deps and release it.


Add v1 serialized model fixtures to tests

As I go through a major rewrite of the Axon compiler in #260, I've realized it will be very easy to make breaking changes if we do not include versions of old serialized models as a part of the test suite. The current API does serialization/deserialization with tmp files, but we should have some static tests as well to ensure we don't break backwards compatibility when we have a stable release

Given model serialization is going to be completely deprecated in the next release, I'm okay not looking too far into support for this.


feat(index)!: remove ability to index IndexVec with usize

#5733  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Build translated docs to fix #797

To test this PR
run python ./scripts/docs.py build-all  This will build the docs site
run python ./scripts/docs.py serve  This will serve the doc site

In release.sh file release.sh file line 102
I think there will be a need to update how the command is run. pointing to the right mkdocs.yaml file. Probably point to docs/en/mkdocs.yml file.
I think they will be a change to this command too https://github.com/dynaconf/dynaconf/blob/master/release.sh#L133
and this too https://github.com/dynaconf/dynaconf/blob/master/release.sh#L134
This too https://github.com/dynaconf/dynaconf/blob/master/netlify.toml#L5 will need to run the python ./scripts/docs.py build-all command
@rochacbruno Please check through these files and let me know the changes I'm proposing is correct

Hi @winmorre the preview site is not loading, and I guess it is because it is missing the customizations on https://github.com/dynaconf/dynaconf/blob/master/netlify.toml

Hi @winmorre the preview site is not loading, and I guess it is because it is missing the customizations on https://github.com/dynaconf/dynaconf/blob/master/netlify.toml

@rochacbruno Please how do I go about this?
looking the link sent but don't know what to do to fix this

Hi @winmorre the preview site is not loading, and I guess it is because it is missing the customizations on https://github.com/dynaconf/dynaconf/blob/master/netlify.toml

@rochacbruno Please how do I go about this? looking the link sent but don't know what to do to fix this

Replace mkdocs build --clean with the call to the script you added python ./scripts/docs.py build-all

@rochacbruno  I have updated the PR

@rochacbruno please I have fix the merge conflicts and I have updated the PR

thanks @winmorre to figure out the build error.

Looks like this needs a rebase from master?

Looks like this needs a rebase from master?

ok

@rochacbruno I have updated the PR


"MochiSampler No available kernel. Aborting execution." had gone after last git pull

I can confirm that after last update kernels error has gone.
H100 80GB VRAM
nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2024 NVIDIA Corporation
Built on Wed_Aug_14_10:10:22_PDT_2024
Cuda compilation tools, release 12.6, V12.6.68
Build cuda_12.6.r12.6/compiler.34714021_0

Alright thanks, what I learned was that when given list of backends, torch tries to use them in the order they are in the list.


Add storage and yarn related entries for rails 5.2

Reasons for making this change:
ActiveStorage has become part of Rails 5.2. File uploads are uploaded to /storage and you shouldn't add them to git.
Added precompiled packs and yarn logs to git ignore.
Links to documentation supporting these rule changes:
https://github.com/rails/webpacker/issues/534
https://github.com/rails/webpacker/issues/1193
https://stackoverflow.com/questions/50538316/should-active-storage-binary-variant-files-get-pushed-to-version-control

@gurvircheema thanks!


Updated outdated content from bug bash in samples for Service Bus

Update the outdated content found in https://github.com/azure/azure-sdk-for-net/issues/16746

Closing this issue as there is a separate effort to update samples by another team. We will be using what we found in https://github.com/Azure/azure-sdk-for-net/issues/16746 to cross reference samples that need an update


Avoid sending Z packet in the middle of extended protocol packet sequence if we fail to get connection form pool

Sending a query in the extended protocol is done by transmitting a sequence of discrete protocol messages (in contrast with simple mode where the entire query is sent in a Q packet).
This poses a problem to Pgcat if the pool is busy because if we are unable to checkout a connection from the pool we send back to the client a SystemError and a ReadyForQuery packets. This is unexpected by client (Getting ReadyForQuery before sending S). This resulted in error messages like
FATAL:  could not get connection from the pool
message type 0x5a arrived from server while idle
FATAL:  could not get connection from the pool
message type 0x5a arrived from server while idle
FATAL:  could not get connection from the pool
message type 0x5a arrived from server while idle
FATAL:  could not get connection from the pool
message type 0x5a arrived from server while idle
FATAL:  could not get connection from the pool
message type 0x5a arrived from server while idle
FATAL:  could not get connection from the pool
message type 0x5a arrived from server while idle
FATAL:  could not get connection from the pool
message type 0x5a arrived from server while idle
ERROR:  portal "" does not exist
message type 0x5a arrived from server while idle
message type 0x31 arrived from server while idle
message type 0x32 arrived from server while idle
message type 0x54 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x43 arrived from server while idle
message type 0x5a arrived from server while idle
message type 0x31 arrived from server while idle
message type 0x32 arrived from server while idle
message type 0x54 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x43 arrived from server while idle
message type 0x5a arrived from server while idle
message type 0x31 arrived from server while idle
message type 0x32 arrived from server while idle
message type 0x54 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x43 arrived from server while idle
message type 0x5a arrived from server while idle
message type 0x31 arrived from server while idle
message type 0x32 arrived from server while idle
message type 0x54 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x43 arrived from server while idle
message type 0x5a arrived from server while idle
message type 0x31 arrived from server while idle
message type 0x32 arrived from server while idle
message type 0x54 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x43 arrived from server while idle
message type 0x5a arrived from server while idle

In this fix, we will hold off on sending back the error and the ReadyForQuery packets if we fail to get a connection from the pool while we are processing extended protocol messages other than S. This will expose us to an edge case if all extended protocol messages end up being discarded because we have no available connections and only S goes through in which case the query will fail (which is appropriate) with the error message unnamed prepared statement does not exist, because Pgcat has discarded the packets that were supposed to build the prepared statement which S wants to run.
Pgbouncer doesn't handle this case simply because failure to obtain a connection from the pool is a fatal error in Pgbouncer that terminates the client connection.

Okay, I have a test failing without my fix.

Great debugging @drdrsh


Specify a RubyGems version?

I apologize if this has been discussed before, but I didn't see it when I searched. Is there any desire to specify a RubyGems version (like you can specify a ruby version) in the Gemfile? This was in the context of bundler-audit and whether it should audit the ruby version, and how it can't do that for the rubygem version (even though CVEs are posted in ruby-advisory-db)

Bundler can't currently do that.
(well, it can, but it's 100% unsupported: gem "rubygems\0", rubygems_version would cause the resolver to raise an exception if you're on a different version, but really please don't use that)

That's very interesting. I had been thinking something like how you specify a ruby version
rubygems '~> 2.7.3'

Then you could audit the Gemfile with bundler-audit, knowing that bundler would prevent it from loading if the rubygems version at runtime didn't match (and was possibly insecure).
The 100% unsupported method of treating it like a gem is very interesting. I tried it but I got "pathname contains null byte" on 1.16.0, so I'll listen to your advice :)
Is this a worthwhile feature?

It's an interesting feature, but I'm not sold on it being worthwhile. If you just want to enforce a version, having abort "bad version" unless Gem::VERSION == "2.7.3" in the Gemfile is sufficient. The ruby DSL has been a bit of a pain to maintain, and has had a bunch of corner cases, so I'd rather not introduce another DSL method unless there's a large upside to it

I felt the same way, interesting enough to ask, but likely not useful enough to add and maintain. Thank you for considering it, I'll go with the abort approach.

If you want something that's a little more flexible with the version specifier, you can do it like this:
fail "rubygems too old" unless Gem.rubygems_version >= Gem::Version.new('2.7.6')

It'd be nice to have a more elegant way to achieve this.  I agree with the original suggestion.


Undefined is not an object deviceCountry() in emulator. And elsewhere?

Summary

Version
15.3

Affected OS
Android

OS Version
8

Current behavior
I received this undefined object error when using deviceCountry() in an emulator. I do not have a physical Android device to test with, so I can't verify if it's emulator specific, but I'm assuming the emulator is not returning a device country and so it's crashing.
I would imagine however, that this is theoretically possible on a physical device too and should be fixed.
One last thing to note is that because of a conflict with Google Play Services versions I edited RNDeviceInfo to remove that dependency and installed it project-wide instead. I don't think it's related, but it could be, so I thought I'd mention it.

Expected behavior
We should return a device country or null if none found.

Hi @paintedbicycle, I think that in this case, it's RNDeviceInfo which is undefined.
Can you make sure that you linked the library properly?

Oh how weird. OK, yep you're right, it became unlinked.

@paintedbicycle how you solve this ?

@lmichailian - My react-native-device-info package had become unlinked in Android. Check to make sure:
This is in settings.gradle:
include ':react-native-device-info' project(':react-native-device-info').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-device-info/android')
This is in /app/build.grade:
dependencies {     compile project(':react-native-device-info') }
and these are in MainApplication.java:
import com.learnium.RNDeviceInfo.RNDeviceInfo;     @Override     protected List<ReactPackage> getPackages() {       return Arrays.<ReactPackage>asList(         new MainReactPackage(),         new RNDeviceInfo(),       );     }


NIFI-5066: Fixing enable/disable verification

NIFI-5066:

Ensuring we verify we can enable/disable when appropriate.

@mcgilman I tried testing this. Created a Process Group with 2 processors. One was STOPPED, the other DISABLED. Clicked on canvas to clear the selection. Then clicked "Disable" in the Operate palette. Got back an error: "92e58351-0163-1000-ab38-7947aeead66e is not stopped".

Thanks @markap14. I've pushed another commit that should address what you're seeing.

@mcgilman all looks good now, thanks! Have merged to master.


Updates for iOS SDK tutorial

Small fixes/updates to the iOS SDK tutorial to go along with authenticator update.

can this be merged?


added custom icons to Checkbox

Made it possible to use custom icons with Checkbox, like this example in the docs https://mantine.dev/core/checkbox/#change-icons

Here's a test app  https://py.cafe/amward/dash-mantine-checkbox-icons


fix(github-actions): group all workflow updates

This will group all GitHub Actions workflow file updates; as it sees the new "uses" field released, it will update a single PR.
Reference: https://docs.renovatebot.com/configuration-options/#matchmanagers

It doesn't prevent anything.
 This just groups them (hopefully) into a single PR per repo.
Also, this only works if the updates to multiple packages like actions-node, actions-checkout, etc. are sent to us simultaneously.
All repos wait the whole week to get updates so it is more likely this config will save us some noise.


codesign verification rejected "the code is valid but does not seem to be an app"

Great app, love to use Go with Electron. I have an issue signing the .app with codesign though, more of an issue verifying with spctl. I have a valid certificate and I've done code signing before, I've only ran into an issue with this golang/electron app.
Using the go-astilectron-demo project, these are the commands I run.

Build .app astilectron-bundler -v

Sign .app codesign --deep --strict --force --verbose=4 --sign <my cert here> "Astilectron demo.app"

Verify .app spctl -vvvv -a "Astilectron demo.app"
This is where the issue happens. The response from spctl is:

Astilectron demo.app: rejected (the code is valid but does not seem to be an app)
origin=<my cert here>

Anyone else having this issue? I've tried multiple methods with no luck.

@hunterlong this must be because the bundler creates the MaxOSX app manually. Something must be missing unfortunately. Is there any way you could share a minimalist app that you actually succeed to sign? Since a MacOSX app is a folder containing few files in a specific folder tree, I'm interested in checking whether I've not omitted anything that would make the signing fail.
Let me know.

Thanks for getting back to me so quickly. I've been able to sign electron apps for Mac and Windows using p12 certificates. electron-builder makes the code signing process mostly automatic. electron-builder does seem to be using codesign though.
The project i've been working with is CoinApp, it's open source and is just a basic electron app. (not as complexed as this project) Building and signing is done on travis-ci so you can see how it's done. I'm thinking there's an issue with the generated Info.plist file? Maybe?

That's my guess too. Or another needed file may be missing in the App created by the bundler.
In any case, is there any way you could zip the CoinApp built with electron-builder and share it on this issue? I don't have the full electron toolchain installed, and I'd rather check evertyhing on a valid app.


Refactor AnyWidget command registration

separates the collection and registration of anywidget commands.  _collect_anywidget_commands happens on __init_subclass__ ... and doesn't require getting any attributes on widget instances.  while _register_anywidget_commands still happens on widget init.
just an option. not necessarily much better :)

Ooo excited to have a look, thanks :) You can ignore the JS tests, i need to update some snapshots (they are broken on main).


Error on Profile Screen in DriverApp on development builds

Encountered the following error on the Profile screen when running the DriverApp on EAS builds:
Invariant Violation: requireNativeComponent: "RNCAndroidDialogPicker" was not found in the UIManager.

Error doesn't occur when I comment out the Selector component in profile.tsx


get_all_lexers() fails in mod_wsgi environment when IPython is installed

(Original issue 1317 created by cjwelborn on 2017-01-20T04:11:40.111501+00:00)
I just discovered a weird bug, that only seems to happen when IPython is installed. This actually looks like their problem, and I plan on filing a bug there, I just wanted to make you aware of it. Here's my traceback (just gathering a list of lexer names/aliases):
File "/home/cj/scripts/welbornprod/wp_site/wp_main/utilities/highlighter.py" in <listcomp>
  35. LEXERNAMES = [lexer_[1] for lexer_ in lexers.get_all_lexers()]

File "/usr/lib/python3/dist-packages/pygments/lexers/__init__.py" in get_all_lexers
  53.     for lexer in find_plugin_lexers():

File "/usr/lib/python3/dist-packages/pygments/plugin.py" in find_plugin_lexers
  53.         yield entrypoint.load()

File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py" in load
  2249.         return self.resolve()

File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py" in resolve
  2255.         module = __import__(self.module_name, fromlist=['__name__'], level=0)

File "/usr/local/lib/python3.5/dist-packages/IPython/__init__.py" in <module>
  49. from .terminal.embed import embed

File "/usr/local/lib/python3.5/dist-packages/IPython/terminal/embed.py" in <module>
  16. from IPython.core.interactiveshell import DummyMod, InteractiveShell

File "/usr/local/lib/python3.5/dist-packages/IPython/core/interactiveshell.py" in <module>
  62. from IPython.utils import io

File "/usr/local/lib/python3.5/dist-packages/IPython/utils/io.py" in <module>
  93.     stdout = IOStream(sys.stdout, fallback=devnull)

File "/usr/local/lib/python3.5/dist-packages/IPython/utils/io.py" in __init__
  42.             setattr(self, meth, getattr(stream, meth))

Exception Type: AttributeError at /misc/xtools
Exception Value: 'mod_wsgi.Log' object has no attribute 'name'

Its actually there in IPython.utils.io, where they are trying to clone a file-like object without a name (a mod_wsgi.Log). So I don't know if there is anything you can do, or if it warrants some kind of workaround. Like I said, I just wanted to make you aware of it and I'm heading over to file a bug report at ipython now. I'll probably hack around it to get my little project going.
P.S.: This was pygments version 2.1.3 (latest on PyPi).
Thanks,
-Chris

(Original issue 1317 last updated on 2017-01-20T05:39:25.438178+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by cjwelborn on 2017-01-20T05:17:48.321432+00:00)
I hacked around it for now by creating my own get_all_lexers(), and filed a report with IPython.
#!python
from pygments import lexers

def bugfix_get_all_lexers():
    """ BUGFIX for pygments and IPython plugin.
        Bug report: https://github.com/ipython/ipython/issues/6386

        Return a generator of tuples in the form ``(name, aliases,
        filenames, mimetypes)`` of all know lexers.
    """
    # I'm on Python 3.5, so just values().
    for item in lexers.LEXERS.values():
        yield item[1:]
    try:
        for lexer in lexers.find_plugin_lexers():
            yield lexer.name, lexer.aliases, lexer.filenames, lexer.mimetypes
    except AttributeError:
        pass

(Original comment by birkenfeld on 2017-01-20T05:39:20.083562+00:00)
Hi Chris,
unfortunately it's not really well-defined what methods/attributes a file-like object has to support, but you could also ask mod_wsgi to give their Log a name attribute, akin to sys.stdin which is called <stdin>.
I'm going to close this, since as you said it's a problem in (mainly) IPython.
cheers, Georg


[5.4] Make with

This allows functionality similar to old $container->make(class, params) functionality.

This still needs some work but is a proof of concept.

I still find this whole feature quite odd... curious what the behavior should even be when resolving things that are singletons or instances that have already been resolved.

All my tests pass now. If anyone sees any broken behavior it with it feel free to let me know so I can add a test.

I should note this makes a change to the old behavior of the make(abstract, params) method. In this version, it will never use a previously resolved singleton instance when calling makeWith. In my opinion it should make a new instance each time this method is called because the given parameter array is dynamic.

Hey Taylor, thanks for this. I know you mentioned that back and forth on this is not helping and I do agree.
I have a small problem with this PR. The make method should have the same signature as makeWith (as it was), PSR-11 declares a get method, not a make method. Wouldn't it be more prudent to create a get method that takes a single parameter and just mark make as deprecated for removal in L6. At that point maybe alias make to get and finally implement a makeWith method at that point?
This would solve a lot of community issues up front without code changes (unless already running on 5.4), and implement the methods you need for PSR-11 compatibility in the future?

Make can not have same signature as makeWith on 5.4 because we don't make breaking changes on point releases. Adding that parameter would break the interface.
I personally am totally apathetic towards PSR-11 as I think it's fairly useless overall but since it is so simple to add I don't have a huge problem with adding compatibility for it in Laravel 5.5.

Haha, and here I was, wrongly assuming that this was all gearing the container up for PSR-11. Thanks for clearing that up.
I'm sure it'd be BC if the signature became make($abstract, $parameters = null)?
Either way, nit picking and I'm grateful you've put this PR together.

No, it wouldn't be backwards compatible. Look at the container interface.

It wouldn't break the interface if $parameters is optionnal. @Daveawb  is right.

Changing an existing public signature to add an optional param is a break. Might not affect many, but still a break.

How would it affect them ? Even in the hypothesis some users were extending the base container without the optional parameter, it would still pass :

interface ContainerInterface {

	public function make($abstract);
}

class Container implements ContainerInterface {

	public function make($abstract, $parameters = null)
	{
		// works
	}
}

class ExtendedContainer extends Container {

	public function make($abstract)
	{
		// works as well
	}
}

@RemiCollin Actually looking at it, Taylor is absolutely correct when he says look at the interface for the container. Adding the extra parameter to the interface would not play well with any extended container instances that do not currently add an optional parameter. Alas, this is what it is. Looking forward to this PR being merged.

Yes, if you change the Container interface. But that would not be mandatory in that case, if you look at my example.
Mostly wanted to showcase how it would be possible to maintain pre-5.4 compatibility, while not introducing BC in current release. Not saying it would be a good pratice or not, it's totally debatable, but I think that any tool/language feature we have to provide users with smoother upgrades should be considered.

People, I'm not going to argue if it is a breaking change or not. It obviously is if you understand how PHP works. Please no more discussion on that topic.

Do people even want this feature or not. People were freaking out about wanting in the issue thread and now its just a couple of people arguing about BC. I'm not going to bother with it (because I think the feature is kinda silly) if this isn't actually a needed feature.

Not arguing, just discussing implementation.
But you're right, I won't bother if you feel it's an inappropriate discussion to have on a PR.

@taylorotwell Gosh the communitys wants and needs have really ground you down man. No arguments to be had here, just, I hope, constructive conversation. The community does absolutely want this, I'm not sure why no one else has chimed in and given a thumbs up but I speak for many people on my team who would very much like this functionality back.

@taylorotwell With this it is impossible to pass a scalar in params :(

@taylorotwell Thanks for the feature. I think you should mention this method makeWith() method on laravel's website under the changelog section.

Do people even want this feature or not?

I didn't know I wanted this feature until about 1 hour ago. Has make it so much easier to pass different configs into generating Guzzle clients now depending on if I'm testing/debugging/in production.
So thank you!

Do people even want this feature or not?

It saved my time too. Thanks!

Thank you, thank you for this re-addition!

Hi all,
I'm having an issue with testing/mocking/replacing the bind in the container.
Let me try to explain.
$this->source->type is, for this test, LocalFolder
$this->source is the source of data
This is the implementation:
$handler = app()->makeWith(
    $this->source->type,
    ['source' => $this->source]
);

$fileContents = $handler->get($item);

Everything working nicely in other tests but when I try to replace that class, it doesn't hit the replacement:
$this->app->bind(LocalFolder::class, new class($source) extends LocalFolder {
    public function get($item)
    {
        dd("IT HIT");
        return 'MOCKED_CONTENT';
    }
});

It never hits "IT HIT" :(
Do you know if there is any problem/issue with binding and resolving with makeWith?
Thank you so much.
Best regards

this is not the appropriate place to ask for debugging help.  Please ask in the Slack or on a forum (stackoverflow or others).  Thanks

Got this behavior lost in Laravel 5.5 again?


helm install not working - mac arm64

helm install superset1 superset-0.12.3.tgz --debug
install.go:214: [debug] Original chart version: ""
install.go:231: [debug] CHART PATH: /Users/mymac/helm/superset-0.12.3.tgz
client.go:142: [debug] creating 16 resource(s)
client.go:486: [debug] Starting delete for "superset1-init-db" Job
client.go:490: [debug] Ignoring delete failure for "superset1-init-db" batch/v1, Kind=Job: jobs.batch "superset1-init-db" not found
wait.go:66: [debug] beginning wait for 1 resources to be deleted with timeout of 5m0s
client.go:142: [debug] creating 1 resource(s)
client.go:712: [debug] Watching for changes to Job superset1-init-db with timeout of 5m0s
client.go:740: [debug] Add/Modify event for superset1-init-db: ADDED
client.go:779: [debug] superset1-init-db: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:740: [debug] Add/Modify event for superset1-init-db: MODIFIED
client.go:779: [debug] superset1-init-db: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
Error: INSTALLATION FAILED: failed post-install: 1 error occurred:
* timed out waiting for the condition
helm.go:84: [debug] failed post-install: 1 error occurred:
* timed out waiting for the condition
INSTALLATION FAILED
main.newInstallCmd.func2
helm.sh/helm/v3/cmd/helm/install.go:154
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.8.0/command.go:983
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.8.0/command.go:1115
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.8.0/command.go:1039
main.main
helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
runtime/proc.go:267
runtime.goexit
runtime/asm_arm64.s:1197
Output of helm version:
version.BuildInfo{Version:"v3.14.0", GitCommit:"3fc9f4b2638e76f26739cd77c7017139be81d0ea", GitTreeState:"clean", GoVersion:"go1.21.6"}
Output of kubectl version:
Client Version: v1.26.1
Kustomize Version: v4.5.7
Server Version: v1.25.2
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Docker-desktop

You'll need to talk to the Helm chart author about the issue you're seeing.

Do u have arm64 version of apache/superset
Thanks and Regards,
Abhishek Sen
Contact:<PHONE_NUMBER>
On Thu, Feb 8, 2024 at 9:59 AM Ian Zink @.***> wrote:

You'll need to talk to the Helm chart author about the issue you're seeing.
—
Reply to this email directly, view it on GitHub
https://github.com/helm/helm/issues/12778#issuecomment-1934665073, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APAGTYCU6B5GVX4YSOVPVPTYSUHBLAVCNFSM6AAAAABC3RSMWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZUGY3DKMBXGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Error 500 on default.aspx

Got form some log:
500 (1036 ms) POST http://www.geocaching.com/default.aspx
Got it just after login.

switchToEnglish(viewstates);
500 - Server Error
We're sorry, your request has resulted in an error.
If you feel that the page you are looking for should be available, please let us know. Otherwise, you may continue to use the site through its navigation, or browse the links below:
Visit the Geocaching Home Page
Create a New Membership
Log In with Your Groundspeak Account


 Allow unicorn to either upgrade or rev…

…ert it
The oldsig QUIT instruction no longer seems to be necessary. Sending USR2 to unicorn is enough to spin up the new master and either drop the old master process once the new master starts successfully or roll back to the old master if the new master fails.
The upgrade step also sometimes incorrectly returns a success message when unicorn has not started, or failed to upgrade. Currently it waits two seconds then attempts to send a 0 signal to the PID. This has been updated to wait 20 seconds to give unicorn plenty of time to start, and will also check to see if the PID changed or if it was reset back to the old master, returning a failure message to indicate this.
This may be a breaking change if there are older versions of unicorn/other gems that DO require the oldsig QUIT to be sent, so if you'd prefer this could be implemented as a 'safe_upgrade' command rather than changing the upgrade path.
#114

Hi @dsturrock,
I'm no longer maintaining this gem. We have moved on from using capistrano, and switched to kubernetes. Since it is not possible for me to test these changes anymore, and I don't want to take the risk of potentially causing issues for other users of this gem, I'd encourage you to use the fork that you've created in your projects.
Thanks for your contribution. This issue will remain open so others will be directed to your fork if they experience the same problems.


models/builder.py creates empty output directory

I have downloaded the microsoft/phi-3-mini-128k-instruct model from huggingface using the huggingface-cli script.
When I try to convert the model to ONNX format, the directory specified with the -o flag stays empty.
I use the following command:
python -m onnxruntime_genai.models.builder -m phi-3-mini-128k-instruct-onnx-cpu -i phi-3-mini-128k-instruct -o phi-3-mini-128k-instruct-onnx-cpu -p int4 -e cpu -c cache --extra_options int4_accuracy_level=1 filename=phi3-mini-128k-instruct-onnx-cpu.onnx

python: 3.10.8
onnxruntime: 1.18.1
onnxruntime-genai: 0.3.0

https://github.com/microsoft/onnxruntime-genai/blob/4b0dd43064287dfbd6f13f16593d36b5525c0cdc/src/python/py/models/builder.py#L2412-L2430
Since you already downloaded the model onto disk and you are providing an input path to a directory, you don't need the -m phi-3-mini-128k-instruct-onnx-cpu part in your command. Can you omit that part and try again?

Omitting the -m phi-3-mini-128k-instruct-onnx-cpu did not work. The directory is still empty.
I have some warnings about missing flash_attn. But I don't think this could be the problem.

Hi @mlinke-ai, can you share the full output of the command here. And what are the specs of the machine you are running on?

The complete output of the command is as following (slightly shortened to remove some clutter):
Valid precision + execution provider combinations are: FP32 CPU, FP32 CUDA, FP16 CUDA, FP16 DML, INT4 CPU, INT4 CUDA, INT4 DML
Extra options: {'int4_accuracy_level': '1', 'filename': 'phi3-mini-128k-instruct-onnx-cpu.onnx'}
C:\Users\mlinke\AppData\Roaming\Python\Python310\site-packages\transformers\models\auto\configuration_auto.py:950: FutureWarning: The `use_auth_token` argument is deprecated and will be removed in v5 of Transformers. Please use `token` instead.
  warnings.warn(
GroupQueryAttention (GQA) is used in this model.
C:\Users\mlinke\AppData\Roaming\Python\Python310\site-packages\transformers\models\auto\auto_factory.py:469: FutureWarning: The `use_auth_token` argument is deprecated and will be removed in v5 of Transformers. Please use `token` instead.
  warnings.warn(
2024-07-08 13:36:31,595 transformers_modules.phi-3-mini-128k-instruct.modeling_phi3 [WARNING] - `flash-attention` package not found, consider installing for better performance: No module named 'flash_attn'.
2024-07-08 13:36:31,595 transformers_modules.phi-3-mini-128k-instruct.modeling_phi3 [WARNING] - Current `flash-attenton` does not support `window_size`. Either upgrade or use `attn_implementation='eager'`.

 Do you have a larger machine you can use?
I am working on an improved method to load these large models using mmap instead to avoid out-of-memory errors such as this one and the above ones you've faced. With mmap, the model builder can then adapt to the machine's memory constraints.

Sorry for the long delay, company processes are slow sometimes.
Sadly, I don't have access to a machine with more RAM. Looking forward for your implementation using mmap.

I'll close this issue for now. We will announce when we have the memory improvements.


Troubleshoot database connection

Cannot seem to update/connect to database remotely.
ToDo: Find way to setup database connection so that you can update stuff in the database.

Seems that using UPDATE in the php file works fine and does update the database. You can use CURRENT_TIME and actually see it be displayed for proof.


python310Packages.pyrainbird: 0.4.3 -> 0.6.2

Description of changes
https://github.com/jbarrancos/pyrainbird/releases/tag/0.6.2

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)
[ ] 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/)
22.11 Release Notes (or backporting 22.05 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

2 packages built:

python310Packages.pyrainbird
python39Packages.pyrainbird


finishNavigation not closing the navigation view on Android

Calling finish navigation from the on_arrival or progress_change events is not closing the navigation view, the only way to exit navigation seems to be the user explicitly closing the window.

Yeah and even the user cancelling navigation causes a blank screen to show, although from what I saw in my emulator it didn't exactly crash

Below line is working in Android when i place in case MapBoxEvent.on_arrival:
MapBoxNavigation _directions;
await _directions.finishNavigation();

After arrival, it is removing that navigation screen and going back to my app screen.
I am using google map and only using mapbox for navigation, so below line with _controller is not working.
await _controller.finishNavigation();

Should be working now


Default image digest value incorrect

When following the instructions to install ingress-nginx with Helm, I continued to run into an issue when aks was creating the container for kube-webhook-certgen. After troubleshooting, I noticed the default digest value associated with the Helm install was not present in my repo. i added the  --set controller.admissionWebhooks.patch.image.digest option with an available digest hash and it worked.

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

ID: 12009c1f-282d-2632-fac0-64b09c432833
Version Independent ID: 6052d3d4-d295-9340-b16d-4c200e34cd73
Content: Use ingress controller with static IP - Azure Kubernetes Service
Content Source: articles/aks/ingress-static-ip.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

It looks like the current documentation and its commands only works with the ingress-nginx helm version 3.39.0

@chiblackhawks Thank you for bringing this to our attention!  We will investigate this and get back to you shortly.

Thanks for the feedback!
The digests are now empty, to solve this issue.
#please-close


#bug; Uniswap v3 liquidity pools missing input tokens

Describe the bug
The following liquidity pools only have one input token symbol:
Uniswap V3 /Wrapped Ether 0.3%
0xe8c6c9227491c0a8156a0106a0204d881bb7e531
Uniswap V3  (Wormhole)/USD Coin 0.01%
0x537a0a5654045c52ec45c4c86ed0c1ffe893809d
Uniswap V3 /Wrapped Ether 0.3%
0xcdff6ddfc9e4807c9927fd58708c2ef3484cc305
Uniswap V3 /Wrapped Ether 1%
0x3afdc5e6dfc0b0a507a8e023c9dce2cafc310316
Uniswap V3 /Wrapped Ether 0.05%
0x886072a44bdd944495eff38ace8ce75c1eacdaf6
Uniswap V3  (Wormhole)/Tether USD 0.01%
0xe1d74c16203f87644584a1ad3ac34c4f1e8f7e1e
Uniswap V3 /Tribe 0.05%
0xe83bad50c0b3f58ded74ecd67f001337e319075f
Uniswap V3 /USD Coin 1%
0xc486ad2764d55c7dc033487d634195d6e4a6917e
Uniswap V3  (Wormhole)/Dai Stablecoin 0.01%
0x76138d5acbb1edd2c39989775107b0ec9866fa3c
Uniswap V3 /Wrapped Ether 0.3%
0x75a63a58bcd7ddf799462fb50264974c5c6239cb
Uniswap V3 /Tether USD 0.3%
0x628e2d0a150779b649810056e931d2eadcd4db5b
Uniswap V3 /Wrapped Ether 0.3%
0xc75ba9831e713666e2ba1d11952c95011c961573
Uniswap V3 /Wrapped Ether 1%
0x64f701f93cfbe2cc5d4886f1a514eb1ac02543eb
Uniswap V3 /USD Coin 0.3%
0x0f9d9d1cce530c91f075455efef2d9386375df3d
Uniswap V3  (Wormhole)/USD Coin 0.3%
0xd73b43c9271d0c02a6bbda814017685448ff36e5
Uniswap V3 /Tether USD 1%
0xb5f8d230523c4bdcd00603ee354921441fde39b4
Uniswap V3 /Tether USD 0.3%
0x5cccad2332292cd5882365bb3584424241ab2210
Uniswap V3 /Tether USD 1%
0xf74a97cc57f1691b4df364264df742e81b4c7754
Uniswap V3 /Wrapped Ether 0.05%
0xeb2423fbeb5d94cd83136a74341a39a2487fb3cb
Uniswap V3 /Wrapped Ether 1%
0x3d3a645a4edd9cce81ff15941042d6f08f9b053f
Uniswap V3 /Tether USD 0.3%
0x2afeeadc34dc95b194f3d8d22b912a983640e082
Uniswap V3  (Wormhole)/Tether USD 0.3%
0x1f6423a6ed9e9cbaa34e924d34d9fbd952f9de16
Uniswap V3 /Wrapped Ether 0.3%
0x11c633c532cedd178ba09708b8e377cd6e58d767
Uniswap V3 /Tether USD 0.05%
0x0cbe2f86e2fd90040ebb557b99f83400bf8f3717
Uniswap V3  (Wormhole)/Tether USD 1%
0x9963536672d5037b986a4cbe00780b1937f79e91
Uniswap V3 /Wrapped Ether 1%
0x98f8b8968612463e011beb3127a0980aa3e2b0a7
Uniswap V3 /USD Coin 0.05%
0x936198fcac6d8cdec3815f24ba250041f593f6c3
Uniswap V3 /Wrapped Ether 0.05%
0x919d9fb4f00089bda65dff6c90cb78552ee4c19d
Uniswap V3 /Wrapped Ether 0.3%
0x8f9a0935b26097a1fc15d4919e0b9e466edc1c57
Uniswap V3 /Wrapped Ether 0.3%
0x8ca580042454ddea4f09fe99dcd189cc3464fa63
Uniswap V3 NFT/NFT 0.05%
0xacabefc959a714b6d2061112a4e3f4fcad00d52f
Uniswap V3 /Universe Finance Token 1%
0xaaba8a92687bfdba363a3ccb29991599d84fed8f

Here is the raw json from my query:
            {
                "__typename": "LiquidityPool",
                "id": "0xcdff6ddfc9e4807c9927fd58708c2ef3484cc305",
                "name": "Uniswap V3 /Wrapped Ether 0.3%",
                "cumulativeVolumeUSD": "39012620.92336277826566512764821941",
                "cumulativeProtocolSideRevenueUSD": "0",
                "cumulativeSupplySideRevenueUSD": "117037.8627700883347969953829446602",
                "cumulativeTotalRevenueUSD": "117037.8627700883347969953829446602",
                "inputTokens": [
                    {
                        "__typename": "Token",
                        "symbol": ""
                    },
                    {
                        "__typename": "Token",
                        "symbol": "WETH"
                    }
                ]
            },

Some of these indeed seem to be pools with two different tokens, such as:
Uniswap V3 /Wrapped Ether 0.3%
0xcdff6ddfc9e4807c9927fd58708c2ef3484cc305

which appears to be AVT/ETH, or this one:
Uniswap V3 /Wrapped Ether 0.3%
0xe8c6c9227491c0a8156a0106a0204d881bb7e531

which appears to be MKR/ETH.
Others appear to be a (Wormhole) swapping the same tokens, such as:
Uniswap V3  (Wormhole)/USD Coin 0.01%
0x537a0a5654045c52ec45c4c86ed0c1ffe893809d

which corresponds to USDC/USDC.
Reproduction
Using the following query:
    {
        liquidityPools(
          first: 1000
          orderBy: cumulativeVolumeUSD
          orderDirection: desc
          skip: 10000
        ) {
          id
          name
          cumulativeVolumeUSD
          cumulativeProtocolSideRevenueUSD
          cumulativeSupplySideRevenueUSD
          cumulativeTotalRevenueUSD
          inputTokens {
            symbol
          }
        }
      }

Link to subgraph
Expected behavior
Maybe I'm missing something, but I would have expected each liquidity pool to have two input tokens, especially as they do indeed display this via the Uniswap app. Plus, the (Wormhole) pools don't make sense to me. What are they, am I missing something about my understanding of Uniswap? Why are some of these pools missing input token symbols?
Additional context
I'm trying to query total cumulative volumes of all tokens on Uniswap so these liquidity pools appear rather mysterious! Any help appreciated, many thanks.

@daniel-finnan Thanks for the thorough issue. Will let @steegecs speak on this more, since he built the Uniswap subgraphs, but in the mean time you can query  the id of the inputTokens which looks like it is returning for some of the examples you listed above and maps to the token on etherscan. Seems like some of the tokens in the subgraph are just not returning the symbol field.

On the (Wormhole) part of my issue, cleared up my understanding of what was going on here, e.g.
Token (origin) USDC
Token (target) USDCso(Wormhole)
But the lack of two input tokens on the query result is a little confusing I think.


Just a typo

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2481634

bot merge


Change Microsoft.Xaml.Interactions.Core to Microsoft.Xaml.Interactivity

Fixes #209
The major revision is the perfect time to fix this long-standing issue with the complexity of usings behaviors involving having to remember and include multiple namespaces in XAML. This removes the warnings from CA1020 as well.
Talked to Sergio, we think just aligning on Microsoft.Xaml.Interactivity as the main namespace would make sense (it's shorter, the more familiar name, and means the core attachment point doesn't move), this would look like this:
Before:
<Button xmlns:Core="using:Microsoft.Xaml.Interactions.Core" xmlns:Interactivity="using:Microsoft.Xaml.Interactivity">
    <Interactivity:Interaction.Behaviors>
        <Core:EventTriggerBehavior EventName="Click">
            <Core:ChangePropertyAction PropertyName="Background">
                <Core:ChangePropertyAction.Value>
                    <SolidColorBrush Color="Red"/>
                </Core:ChangePropertyAction.Value>
            </Core:ChangePropertyAction>
        </Core:EventTriggerBehavior>
    </Interactivity:Interaction.Behaviors>
</Button>

After:
<Button xmlns:Interactivity="using:Microsoft.Xaml.Interactivity">
    <Interactivity:Interaction.Behaviors>
        <Interactivity:EventTriggerBehavior EventName="Click">
            <Interactivity:ChangePropertyAction PropertyName="Background">
                <Interactivity:ChangePropertyAction.Value>
                    <SolidColorBrush Color="Red"/>
                </Interactivity:ChangePropertyAction.Value>
            </Interactivity:ChangePropertyAction>
        </Interactivity:EventTriggerBehavior>
    </Interactivity:Interaction.Behaviors>
</Button>

For migration, folks should just be able to change the xmlns for Core:
<Button xmlns:Core="using:Microsoft.Xaml.Interactivity" xmlns:Interactivity="using:Microsoft.Xaml.Interactivity">
    <Interactivity:Interaction.Behaviors>
        <Core:EventTriggerBehavior EventName="Click">
            <Core:ChangePropertyAction PropertyName="Background">
                <Core:ChangePropertyAction.Value>
                    <SolidColorBrush Color="Red"/>
                </Core:ChangePropertyAction.Value>
            </Core:ChangePropertyAction>
        </Core:EventTriggerBehavior>
    </Interactivity:Interaction.Behaviors>
</Button>

Not sure why GlobalSuppression.cs is marked as a binary... opened #283

I tested and was able to build nuget packages locally and test in a File->New WinUI 3 app:
        <Button
            xmlns:i="using:Microsoft.Xaml.Interactivity"
            x:Name="myButton"
            Content="Click Me">
            <i:Interaction.Behaviors>
                <i:EventTriggerBehavior EventName="Click">
                    <i:ChangePropertyAction
                        PropertyName="Background"
                        TargetObject="{x:Bind myButton}"
                        Value="Red" />
                </i:EventTriggerBehavior>
            </i:Interaction.Behaviors>
        </Button>

Made it so much easier to just stumble around into without having to go look up the docs for a change. ☺


[AddToApp] NullPointerException thrown while FlutterActivityAndFragmentDelegate try attaching the engine to FlutterView

Flutter version: 1.12.13+hotfix.5
Target platform: Android
In FlutterActivityAndFragmentDelegate onStart() the flutterView will attachToFlutterEngine() in next loop via Handler callback.
But at some strange times, release() may have been called before it, see following logs.
Logs
java.lang.NullPointerException
Attempt to invoke virtual method 'void io.flutter.embedding.android.FlutterView.attachToFlutterEngine(io.flutter.embedding.engine.FlutterEngine)' on a null object reference

1 io.flutter.embedding.android.FlutterActivityAndFragmentDelegate$2.run(FlutterActivityAndFragmentDelegate.java:2)
2 android.os.Handler.handleCallback(Handler.java:836)
3 android.os.Handler.dispatchMessage(Handler.java:103)
4 android.os.Looper.loop(Looper.java:203)
5 android.app.ActivityThread.main(ActivityThread.java:6406)
6 java.lang.reflect.Method.invoke(Native Method)
7 com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1113)
8 com.android.internal.os.ZygoteInit.main(ZygoteInit.java:974)

Solution
Surrounding with if (flutterView != null):
new Handler().post(new Runnable() {
    @Override
    public void run() {
       if (flutterView != null) {
          Log.v(TAG, "Attaching FlutterEngine to FlutterView.");
          flutterView.attachToFlutterEngine(flutterEngine);

          doInitialFlutterViewRun();
       }
    }
  });
}

Hi @yrom
can you please provide your flutter doctor -v
and your full flutter run --verbose?
Also, to better address the issue, would be helpful
if you could post  a minimal code sample
or the steps to reproduce the problem.
Thank you

Duplicate of https://github.com/flutter/flutter/issues/45347.


make data-turbo-submits-with attribute work with links that have data-turbo-method (feature-request)

The data-turbo-submits-with attribute is useful for showing simple text when doing long-running posts. It would be helpful if this worked for Anchor tags with the data-turbo-method attribute set

I don't speak for the maintainers when I say this, but I'm personally opposed to expanding support for -to-<form> element.
In the short-term, while you wait for any potential development, have you tried to explore an alternative solution that replaces your unsafe  elements with <form> element counterparts?
If you're using Rails, an  element like:
...

could be replaced by a <form> element like:
<form method="post" action="/articles/1">
  <input type="hidden" name="_method" value="put">
  <button>...</button>
</form>

I agree that a link such as this could be implemented as a form.
I also agree that anchors to forms is a weird feature. I do think that as long as it's supported it should be close to feature parity with the forms implementation though

Agree with @seanpdoyle, closing this


Drop (useless?) is_expected.to compile examples

Those is_expected.to compile looks useless from my perspective because there are other examples checking for other things in the catalog. So we can see the catalog compilation is failed anyway.

Below are some unit test benchmarks on my m1-based macbook
Before the change:
9442 examples, 0 failures, 14 pending

rake spec_standalone: Finished in 11 minutes 10 seconds (files took 4.44 seconds to load)
rake parallel_spec_standalone: Took 187 seconds (3:07)

After the change:
8182 examples, 0 failures, 14 pending

rake spec_standalone: Finished in 8 minutes 56 seconds (files took 4.53 seconds to load)
rake parallel_spec_standalone: Took 168 seconds (2:48)

Afair compile does validate relationships, I don't think other tests do that.

At least in the past compile catched issues that were not visible in other tests.

Yeah this is essentially what we are interested in and what compile gives us: https://rspec-puppet.com/documentation/classes/#test-that-the-catalogue-compiles

It will test that the manifest can be compiled into a catalogue, and that the catalogue has no dependency cycles between resources.

The second part is what the other tests don't give you afair.

Ah! Right, I didn't thought about relationship.. let's close the PR then


update ccls root pattern

CCLS searches for a .ccls file to identify the root folder for a project. This patch adds .ccls to the root pattern in ccls.lua.

You have a couple of lint errors.

Updated the patch to fix the lua lint errors.
There were also a few git commit lint errors, but not sure what they were about.

There were also a few git commit lint errors, but not sure what they were about.

The commit message needs to follow the 'conventional commit' format. So something like this:
fix(ccls): Add .ccls as root pattern

CCLS searches for a .ccls file to identify the root folder for a project. This
patch adds .ccls to the root pattern in ccls.lua.

https://github.com/conventional-changelog/commitlint/#what-is-commitlint

Not entirely sure why the commit linter is still complaining. Possibly that it has to be all lowercase...?
-fix(ccls): Add .ccls as root pattern
+fix(ccls): add .ccls as root pattern

CC @mjlbach

I think it's the capitalization as well (sentence-case?)

yes, has to be lower case

Sorry for my delayed reaction. I updated the commit message.


Added model documentation

Any pull request you open is subject to the TensorFlow Hub Terms of Service at www.tfhub.dev/terms and Google's Privacy Policy at https://www.google.com/policies/privacy.
We check modified Markdown files for validity using this GitHub Workflow. You can execute the same checks locally by passing the file paths of modified Markdown files (relative to the assets/docs directory) to validator.py e.g. python3 ./tools/validator.py google/google.md google/models/albert_base/1.md ....

Hi
The GitHub action fails with the following error:
Error: Version 3.6 with arch x64 not found
Can you let us know if the pull request can be merged or if something else is needed from our side?

Thanks @maringeo
I have resolved the issue with the language, license and tar.gz files. However now I am getting the following error:
{'universaldot/udot_scann/1.md': 'File cannot be used by SavedModel: udot_scann/saved_model.pb'}
Any idea why the file can't be used?
The original file is here: https://github.com/UniversalDot/tensorflow/raw/develop/SaveModel format/udot-scann-001.tar.gz
Many thanks.

Hi @JosephKnecht-lab , could you please remove __MACOSX/._saved_model.pb from the archive? Thank you!

Hey @TutubanaS Can you remove the __MACOSX/._saved_model.pb file and make sure that the build passes as we spoke yesterday?
@WGierke Thanks for the reminder.

Hi @WGierke @maringeo
The build seems to be passing now. Let us know if anything else is needed from our side before merging.
Thanks.


Creating new files using dynamic names

Hello, I'm trying to create new files using string templates, but unsuccessfully. I need to generate new file names per file, when I pass filename to fs.root.getFile always get a undefined value. Here is my code:
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, (fs) => {
          const filename = `${filename} - ${date}.xlsx`
          fs.root.getFile(filename, { create: true, exclusive: true }, function (fileEntry) {
          console.log("fileEntry is file?" + fileEntry.isFile.toString());
          writeFile(fileEntry, new Blob([response.data], { type: 'application/xlsx' }));
            }, reject());
     }, reject());

cordova and cordova-plugin-file are dependencies of a vue.js application

Thanks a lot for your issue, however the issue template exists for a reason 😉
It helps us to debug the issue further and to provide a solution much faster. With important information missing, we unfortunately can't help you.
Therefore, please edit this issue accordingly or close and create a new one and make sure to provide all the required information.

stale


Handle quote escape in bindy

Description

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

Nice magic with the scanner.
We have StringQuoteHelper for safe splitting when using quotes as double or single quote chars. But I guess the scanner and bindy can in theory use other quote chars - but who would not use " ?

If we need to backport this, then its good to have a JIRA ticket for this to track this


[WIP] Add KFP 2.0 compatibility on SDK and API levels

Placeholder PR intended as a follow-up to https://github.com/mlrun/mlrun/pull/4668
The work here isn't final, but it's shared to gather feedback and flag risks.
This codebase can compile a local pipeline with KFP SDK 2.0 (in the new IR YAML format), dispatch it to the MLRun API, which enriches it, and pass it along to the KFP API.
MLRun's frontend gets information about pipelines and runs in the expected data schema, but graph-related information still poses some challenges.
Many of the current implementation gaps are tracked as TODOs in code. Beyond those, the following non-exhaustive list is worth considering:

KFP pipelines aren't yet ready to include Nuclio serving functions
KFP execution nodes only support S3/Minio as artifact targets
Code distribution among the internal pipeline modules (common, kfp.v1_8 and kfp.v2_0) was ill-informed and needs reviewing in light of new code reuse opportunities
Tests are still very broken

Following feedback gathered on https://github.com/mlrun/mlrun/pull/4668, we greatly changed the dynamic import strategy used to abstract KFP versions from most of the MLRun codebase. Such changes cascaded back to this PR, so I consolidated both.


NOp field name [run_process_replay]

Always be in the habit of "[run_process_replay]" in the PR title on refactors like this

run process replay is running per default https://github.com/tinygrad/tinygrad/actions/runs/10118219467/job/27984684885?pr=5742

it runs by default but does not assert if all are the same, and refactoring like this should keep kernels the same

ahh thanks


(maint) Guard against Windows::SID constant redefinitions

This adds guards to prevent the Windows::SID constants from being
redefined. This comes up when running Bolt on a target that has the
agent installed. For more context, see https://github.com/puppetlabs/bolt/issues/2694

@lucywyman They're failing on https://github.com/puppetlabs/puppet/pull/8544 . That PR has more context on what's causing the failure.

Hi @beechtom, it seems like this could be an issue for any constant in puppet. Could you check to see why sid.rb is getting loaded twice? Are $LOADED_FEATURES getting cleared? Or is one code path calling require while another is calling load?

@beechtom It seems like the rspec issues may have been solved? I think a rebased might do the trick.

A rebase with main should fix the tests: see https://github.com/puppetlabs/puppet/commit/bc416192bfa24f24c636c2026fe3b3835bcad8ca
I agree that we should identify what is causing the constant redefinition.

Hm, we're having a hard time reproducing this and some of the data the user provided is inconsistent (for example they said their platform is CentOS 7, but this should only get loaded if it's on a Windows system...). We asked for more information, putting this on hold until we understand what's happening better.

Woohoo! I've at least reproduced the issue and tracked down what's happening, though I'm not clear on what a good solution is. The warning is getting raised when we generate types in Bolt, which autoloads all the available providers for the types. It looks like some providers require 'puppet/util/windows/sid' regardless of whether the underlying operating system is Windows or not for example: https://github.com/voxpupuli/puppet-windows_env/blob/master/lib/puppet/provider/windows_env/windows_env.rb#L253 (I'm not sure if there are others as well!). I'm still not quite sure how the constant is defined but require still loads the file, but using pry to step through that's definitely what's triggering the warnings in Bolt.
I can spend more time digging into why Ruby is complaining when that file gets required, since forcing users to rewrite their providers seems pretty unreasonable. But if y'all have any other context or ideas I'm all ears. I haven't verified this is an issue on Windows yet, only on CentOS (the platform the original user was on).

Thanks @lucywyman! That looks to be a bug in the provider, as line https://github.com/voxpupuli/puppet-windows_env/blob/cea2fd3c3eddada2235c466b653ee598ae14cd6a/lib/puppet/provider/windows_env/windows_env.rb#L253 should be guarded along with the other windows specific requires.

Ah, ok, sweet. I'll let Vox and the user know, and we'll get it sorted out.


Modify testing queries when comparing with Boost for kNN

When working on trying to optimize kNN with k=1, I produced a buggy
code. However, the current version of the test never caught it. I played
around with the test, trying to find out why that was the case. While I
have not determined the root cause, I found the following:

Using a structured grid for the tree always made the test pass
Using a random cloud for the tree with query points being subset of
that cloud made it pass

Thus, I decided to switch to using a random cloud for source, and make
query points distinct.

I updated the test, building on @Rombur's work in #494. It should now be easy to plug in different data sets to run spatial and nearest comparisons with Boost.

OK, it's been 3 weeks and there is no explicit feedback on this PR. I am going to assume that it means that nobody cares if this gets merged or not, so I plan to merge this at the end of the day.
If you do want to provide the feedback, only critical fixes will be accepted.

What's going on here? You open a PR that slips through review, don't ping us on the PR for 3 weeks, and then decide on a busy week that you will merge your own PR which fails CI btw.

What's going on here? You open a PR that slips through review, don't ping us on the PR for 3 weeks, and then decide on a busy week that you will merge your own PR which fails CI btw.

@Rombur Look at it from my perspective. I open PR, nothing for four days. I update the PR and explicitly ping you, nothing for 3 weeks.  I mention it several times during ArborX meetings, asking for a review, nothing. When I consider PR done, and when I pinged someone to review it, I remove it from my worklist, and don't return to it until I get the feedback. What else do you want me to do?
And, if you looked closer, you would notice that the CI failure has nothing to do with the PR.

I gave your oral feedback several times. Don't have the time to elaborate now.

@dalg24 You can think of me as having short memory, I don't always recall what feedback you gave without something to reference, like a github comment.
Thanks for the review.

While they are some good changes (using a seed, reusing point cloud generations for boxes), your patch is very noisy in the sense you change a lot of things for little improvement overall.

That's subjective.

The main blocker is you may use functions for the boiler plate bit but you must have the assertion macros own the main unit test

Will fix.

The main blocker is you may use functions for the boiler plate bit but you must have the assertion macros own the main unit test

Actually, I'm not sure a) why you would want to do that, and b) how you propose to do that. Regarding b), we construct both boost and arborx trees and then compare the results. It's unclear to me what the function would have to return to be able to run that assert inside the test body.