Add kwargs to compile functions by source and file

What I did
Added kwargs to compile_source and compile_files functions
Related issue: https://github.com/ApeWorX/py-solc-x/issues/133
How I did it
How to verify it
Checklist

[ ] I have confirmed that my PR passes all linting checks
[x] I have included test cases
[ ] I have updated the documentation (README.md)
[ ] I have added an entry to the changelog

@iamdefinitelyahuman hope this PR finds you well. I'm making it available for your review and, please, let me know in case you think it makes sense moving forward and I'll do the remaining items from checklist


Add before param

Adds before param to all paginated functions and updates the tests and docs. A lot of requests needed to be re-recorded because they have the before param in the query

coverage: 100.0%. remained the same when pulling 3efb32a6594a2b0b20b8e40ba68bedea38aeefd7 on add_before_param into 9bac8d054eda14d15156fbf815b54a209eab8cbf on main.


Script Only Collects Data for a Single Process

We can have multiple unique Java processes with the same main class name. The script needs to loop through all of the list in jps and collect data for each of those processes in parallel.

Included in #6


made github actions

When you set up the makefile, uncomment the steps to do with make. This way everything will be made sure to work.

Just making sure, will gh actions work with a self-built cross-compiler?

github actions just runs some commands on an event, so yes, as long as you set it up as if you just cloned the repo.


Execution of java-tools.sh consistently fails during Ubuntu 20.04 build

Description
During the packer build process, the execution of the java-tool.sh installation fails.  I've tried this weeks and last weeks release builds but both are exhibiting this failure.  Below are the packer output logs for this issue.  We're using the packer templates to generate self-hosted images to use within VMSS backend.
2022-02-15T15:03:08.2149511Z ==> azure-arm: Provisioning with shell script: C:\a\1\s\virtual-environments\images\linux/scripts/installers/java-tools.sh
2022-02-15T15:03:08.8272321Z     azure-arm: OK
2022-02-15T15:03:08.8330709Z ==> azure-arm: Warning: apt-key output should not be parsed (stdout is not a terminal)
2022-02-15T15:03:09.3713290Z     azure-arm: Hit:1 http://azure.archive.ubuntu.com/ubuntu focal InRelease
2022-02-15T15:03:09.3719242Z     azure-arm: Hit:2 http://azure.archive.ubuntu.com/ubuntu focal-updates InRelease
2022-02-15T15:03:09.3730983Z     azure-arm: Hit:3 http://azure.archive.ubuntu.com/ubuntu focal-backports InRelease
2022-02-15T15:03:09.4636306Z     azure-arm: Hit:4 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease
2022-02-15T15:03:09.5342076Z     azure-arm: Hit:5 https://dl.hhvm.com/ubuntu focal InRelease
2022-02-15T15:03:09.6457067Z     azure-arm: Hit:6 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu focal InRelease
2022-02-15T15:03:09.6467979Z     azure-arm: Get:7 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
2022-02-15T15:03:09.7499643Z     azure-arm: Get:8 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb focal InRelease [6153 B]
2022-02-15T15:03:09.9834270Z     azure-arm: Get:9 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb focal/main amd64 Packages [11.6 kB]
2022-02-15T15:03:13.7810471Z     azure-arm: Fetched 132 kB in 1s (120 kB/s)
2022-02-15T15:03:14.6564818Z     azure-arm: Reading package lists...
2022-02-15T15:03:15.0276011Z ==> azure-arm: Warning: apt-key output should not be parsed (stdout is not a terminal)
2022-02-15T15:03:15.0280634Z ==> azure-arm: gpg: no valid OpenPGP data found.
2022-02-15T15:03:15.5752455Z     azure-arm: Hit:1 http://azure.archive.ubuntu.com/ubuntu focal InRelease
2022-02-15T15:03:15.5757382Z     azure-arm: Hit:2 http://azure.archive.ubuntu.com/ubuntu focal-updates InRelease
2022-02-15T15:03:15.5769163Z     azure-arm: Hit:3 http://azure.archive.ubuntu.com/ubuntu focal-backports InRelease
2022-02-15T15:03:15.6268374Z     azure-arm: Hit:4 https://dl.hhvm.com/ubuntu focal InRelease
2022-02-15T15:03:15.6797658Z     azure-arm: Hit:5 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease
2022-02-15T15:03:15.7692951Z     azure-arm: Get:6 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
2022-02-15T15:03:15.8035739Z     azure-arm: Ign:7 https://packages.adoptium.net/artifactory/deb focal InRelease
2022-02-15T15:03:15.8508789Z     azure-arm: Hit:8 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu focal InRelease
2022-02-15T15:03:15.9557781Z     azure-arm: Err:9 https://packages.adoptium.net/artifactory/deb focal Release
2022-02-15T15:03:15.9563661Z     azure-arm:   Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443]
2022-02-15T15:03:15.9640472Z     azure-arm: Hit:10 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb focal InRelease
2022-02-15T15:03:20.5813258Z     azure-arm: Reading package lists...
2022-02-15T15:03:20.6010351Z ==> azure-arm: E: The repository 'https://packages.adoptium.net/artifactory/deb focal Release' does not have a Release file.
2022-02-15T15:03:20.7752543Z     azure-arm: Hit:1 https://dl.hhvm.com/ubuntu focal InRelease
2022-02-15T15:03:20.8027059Z     azure-arm: Hit:2 http://azure.archive.ubuntu.com/ubuntu focal InRelease
2022-02-15T15:03:20.8031350Z     azure-arm: Hit:3 http://azure.archive.ubuntu.com/ubuntu focal-updates InRelease
2022-02-15T15:03:20.8043757Z     azure-arm: Hit:4 http://azure.archive.ubuntu.com/ubuntu focal-backports InRelease
2022-02-15T15:03:20.8194587Z     azure-arm: Hit:5 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease
2022-02-15T15:03:20.8753098Z     azure-arm: Get:6 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
2022-02-15T15:03:20.9100526Z     azure-arm: Ign:7 https://packages.adoptium.net/artifactory/deb focal InRelease
2022-02-15T15:03:21.0002066Z     azure-arm: Hit:8 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu focal InRelease
2022-02-15T15:03:21.0707159Z     azure-arm: Hit:9 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb focal InRelease
2022-02-15T15:03:21.0745474Z     azure-arm: Err:10 https://packages.adoptium.net/artifactory/deb focal Release
2022-02-15T15:03:21.0761732Z     azure-arm:   Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443]
2022-02-15T15:03:22.3432006Z     azure-arm: Reading package lists...
2022-02-15T15:03:22.3639246Z ==> azure-arm: E: The repository 'https://packages.adoptium.net/artifactory/deb focal Release' does not have a Release file.
2022-02-15T15:03:22.5410793Z     azure-arm: Reading package lists...
2022-02-15T15:03:22.7165106Z     azure-arm: Building dependency tree...
2022-02-15T15:03:22.7173165Z     azure-arm: Reading state information...
2022-02-15T15:03:22.8276126Z ==> azure-arm: E: Unable to locate package temurin-8-jdk
2022-02-15T15:03:22.8323714Z ==> azure-arm: cat: /usr/lib/jvm/temurin-8-jdk-amd64/release: No such file or directory
2022-02-15T15:03:22.8378087Z ==> azure-arm: chmod: cannot access '/usr/lib/jvm': No such file or directory
2022-02-15T15:03:22.8416327Z ==> azure-arm: Provisioning step had errors: Running the cleanup provisioner, if present...
2022-02-15T15:03:22.8424883Z ==> azure-arm:
2022-02-15T15:03:22.8433701Z ==> azure-arm: Deleting individual resources ...
Virtual environments affected

[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Ubuntu 20.04 (20220213 update)
Ubuntu 20.04 (20220207 update)
Is it regression?
N/A
Expected behavior
Successful build of Ubuntu 20.04 image via packer.
Actual behavior
Packer build is failing repeatedly on step for java-tools.sh .
Repro steps
Execute packer build for Ubuntu 20.04 image template.  I didn't try 18.04 as we're not using for our self-hosted agent pools.

Hello @egg-r ,
We are working  to fix this issue.

I've reported the issue upstream, there was a problem regarding ssl certificates, but then the repo started emitting the 403 error

Can confirm the issue.
Because of the reason Ubuntu 18.04 is affected as well.

Is working again:
azure-arm: Hit:1 http://azure.archive.ubuntu.com/ubuntu focal InRelease
azure-arm: Hit:2 http://azure.archive.ubuntu.com/ubuntu focal-updates InRelease
azure-arm: Hit:3 http://azure.archive.ubuntu.com/ubuntu focal-backports InRelease
azure-arm: Hit:4 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu focal InRelease
azure-arm: Hit:5 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease
azure-arm: Hit:6 https://dl.hhvm.com/ubuntu focal InRelease
azure-arm: Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease
azure-arm: Hit:8 https://adoptopenjdk.jfrog.io/adoptopenjdk/deb focal InRelease
azure-arm: Get:9 https://packages.adoptium.net/artifactory/deb focal InRelease [7457 B]
azure-arm: Get:10 https://packages.adoptium.net/artifactory/deb focal/main amd64 Packages [1941 B]
azure-arm: Fetched 9398 B in 1s (8762 B/s)
azure-arm: Reading package lists...

Looks like it got resolved upstream. Closing now.

hello folks...
i'm seeing this again. artifactory returning 403.
any idea who to contact upstream?

same here. Can't install JDK any longer. Failing on the same 403 error.

they are still working on this - https://github.com/adoptium/adoptium-support/issues/923#issuecomment-1903460979


Prepare for adding to official documentation

Few changes to align with best practices.

Actions/probes shoulmd always follow pep8
Export the files for the documentation to get generated
Add changelog default entry

Feel free to merge if you want, then cut a new release and I will add to the docs the package. Make sure you update the changelog please.
Signed-off-by: Sylvain Hellegouarch<EMAIL_ADDRESS>

Awesome, thanks! PR Merged, Changelog Updated, and a new release cut.


Update to more complete variant of Source Sans Pro font

Use version 2.020 and make sure greek and cyrillic characters are
included.

Coverage remained the same at 99.053% when pulling 64751d76f8bc11b5d4635c31726611afca3410df on tf:source-sans-pro-with-greek into 0024e057d72d774fbd5aebecf365ee09fb1c0816 on codevise:master.


New package: GovernmentOfThePRC.ShangHai.PuDong.ZhiHuiPuDong version 3.8.0

Pull request has been created with komac v2.8.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Verify:

The application appears to require login before displaying the version number.

Sorry for not updating the version number before you approved this pull request...

Apologies - I was optimizing for availiability.


[Android] build issue

After I install and tried to build, terminal screen gave me this error
Project with path ':@terrylinla/react-native-sketch-canvas' could not be found in project ':app'.
Here is my app/build.gradle's dependencies
dependencies {
   implementation project(':@terrylinla/react-native-sketch-canvas')
}

How should I fix this? Seems like ios is doign fine

Solved by this
https://github.com/terrylinla/react-native-sketch-canvas/issues/52


Current usage suddenly reporting 10x higher

I've been using the add-on for about 6 months with no issues apart from a lost connection earlier this month.
On 6 Mar 24 Current usage jumped from 5.3l to 51l and has remained in this range ever since.
Consumption has not changed and current usage in the Kingspan app supports this.
It seems that all of a sudden the value is being multiplied by 10 appearing to be since the lost connection.
See screenshots.

I had a similar outage and I can only think it's a glitch on the Kingspan side


doc: Fix copy/paste mistake in data sources user and group.

What does this fix or implement?
Fixes this issue: https://github.com/ionos-cloud/terraform-provider-ionoscloud/issues/492
Checklist

[X] PR name added as appropriate (e.g. feat:/fix:/doc:/test:/refactor:)
[ ] Tests added or updated
[X] Documentation updated
[ ] Changelog updated and version incremented (label: upcoming release)
[X] Github Issue linked if any
[ ] Jira task updated

LGTM


OrientDB ver 2.2.14

OrientDB Version: <2.2.14>
Java Version: 7
OS: window server 2012
the orientdb data I deleted a lot but the capacity is not decreasing, hope everyone can help

Expected behavior

Actual behavior

Steps to reproduce

Hi @phihong89
OrientDB does not recollect space from the clusters when records are deleted.
The easy solution to defragment a DB is to export and re-import it
In general, v 2.2.14 is really very outdated, I'd strongly suggest to upgrade to latest 3.1.11 or, if you have constraints on v 2.2.x, to use 2.2.37
Thanks
Luigi


⚠ ClamAV has degraded performance

In 41f4722, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 445 ms

Resolved: ClamAV performance has improved in 6fe5409.


Mockito builds are slow

Mockito builds can be extremely slow, compared to the other projects -- in particular if gradle needs to be downloaded. Additionally, the defined dependencies lead to running the entire test suite whenever a compilation is performed -- the tests should be skipped unless explicitly executed.

Defects4J now only downloads gradle in the init script. This speeds up the Mockito builds quite a bit.

Is this still an issue?

PR #183 addressed this issue as well, so we can close it.


package manager fails to build

Using Sling 8. I can provide a full list of all my OSGI bundles installed, if you'd like.

I created a package and gave it a filter of /content. Underneath /content, I have several websites worth of node data, but nothing overwhelming.
When I clicked "(Re)build this package" it would only include content at a particular path (/content/edliohs/home/jcr:content/spotlight/message1/Principal Message 8.23.16.pdf) and wouldn't include any of the other hundreds of nodes throughout the content tree. It behaved as if I had an exclude rule excluding everything under /content except that node.
I deleted that node.

Note: it can and will build anything else, for example the /apps directory. Just nothing under content.

The package manger is a user interface for the Jackrabbit Vault framework. The rules to build a package are implemented in this framework. But for single files a package the simplest way to specify the filter is a list of filters with the complete path to the file as the filters root path. I've attached an example for one file.
issue-60-content-1.0.zip

Yes, all of this I know. I'm not new to JCR or package manager concept (I used CRX for several years). In my issue description, you can see that my filter root path is /content. It's behaving as if there is an exclude rule or include rule that I didn't include, such that nothing will be included in my content package except this one single path (/content/edliohs/home/jcr:content/spotlight/message1/Principal Message 8.23.16.pdf).
In other words, I build a /content package, and it's empty when I download it.
I'm wondering if there is some sort of cache of filter rules that composum keeps in the JCR somewhere? The list of reasons this could be happening is long, but composum is definitely on that list in my assessment.

The "output" that i provided above is the output from Composum Package Manager when it builds a package that I've just created with only one filter (/content) and there are hundreds of nodes underneath /content.

Thank you for the report! This does not look like it is a Composum package manager issue at all, since it just delegates this operation to the Jackrabbit implementation. So there would not be much we could do.
Since this is pretty old, anyway, and likely not reproducible, I'll close this issue.


[zh]resync feature-gates in CLI

This PR resync page content/zh-cn/docs/reference/command-line-tools-reference/feature-gates.md.

/approve

/lgtm


Simple Javadoc correction to JdbcEventStore

Simple correction to javadoc for class, it said the class was using JPA to store events - actually should be JDBC. No JPA libraries are needed.

I know it's a very minor commit, but I made the change because until I checked I thought I might need the JPA libraries because of the javadoc comment. So I thought I would fix it.

Why did you close it?


Bug: EXC_BREAKPOINT --> valueForHTTPHeaderField

What did you do?
We noticed random crashes within our App related to Network issues. Looking into the stack trace provided by our crash report tool we noticed that we always end up in the Alamofire -> HTTPHeaders.swift -> Validation.swift (Line:110).
What did you expect to happen?
App should not crash for an Api Call which has been successful.
What happened instead?
For a random Api Call the App crashes.
Alamofire Environment
Alamofire Version:

Alamofire (5.4.3)
AlamofireImage (4.2.0):
Alamofire (~> 5.4)

Dependency Manager:

CocoaPods

Xcode Version: 13.1
Swift Version: 5
Platform(s) Running Alamofire: iOS
macOS Version Running Xcode: BigSur 11.5.2
Stack Trace
OS Version: iOS 14.7.1 (18G82)
Report Version: 104

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Crashed Thread: 11

Application Specific Information:
_inner > valueForHTTPHeaderField:

Thread 11 Crashed:
0   CoreFoundation                  0x3269d405c         CFRelease
1   CFNetwork                       0x3278fac94         [inlined] cfnTranslateCFError
2   CFNetwork                       0x3278fac94         cfnTranslateCFError
3   Alamofire                       0x10dab1350         Request.validate<T> (Validation.swift:110)
4   Alamofire                       0x10dab11b0         Request.validate<T> (Validation.swift:102)
5   Alamofire                       0x10dab28cc         DataRequest.validate<T> (Validation.swift:175)
6   Alamofire                       0x10da43bb8         DataRequest.validate (Request.swift:1154)
7   Alamofire                       0x10da6c628         [inlined] <redacted>
8   Alamofire                       0x10da6c628         thunk for closure
9   Alamofire                       0x10da407f8         [inlined] <redacted>
10  Alamofire                       0x10da407f8         [inlined] <redacted> (Request.swift:469)
11  Alamofire                       0x10da407f8         [inlined] <redacted>
12  Alamofire                       0x10da407f8         [inlined] forEach
13  Alamofire                       0x10da407f8         Request.didCompleteTask (Request.swift:469)
14  Alamofire                       0x10daa69e8         SessionDelegate.urlSession (SessionDelegate.swift:214)
15  Alamofire                       0x10da9c098         Session.didCompleteTask (Session.swift:1240)
16  Alamofire                       0x10daa68cc         SessionDelegate.urlSession (SessionDelegate.swift:213)
17  Alamofire                       0x10daa6adc         SessionDelegate.urlSession
18  CFNetwork                       0x327a0a5bc         _CFNetworkHTTPConnectionCacheSetLimit
19  Foundation                      0x32920af84         __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__
20  Foundation                      0x3290f8624         -[NSBlockOperation main]
21  Foundation                      0x32920d3ac         __NSOPERATION_IS_INVOKING_MAIN__
22  Foundation                      0x3290f82ac         -[NSOperation start]
23  Foundation                      0x32920de50         __NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__
24  Foundation                      0x32920d8dc         __NSOQSchedule_f
25  libdispatch.dylib               0x326409480         _dispatch_block_async_invoke2
26  libdispatch.dylib               0x3263fa818         _dispatch_client_callout
27  libdispatch.dylib               0x326402000         _dispatch_lane_serial_drain
28  libdispatch.dylib               0x326402bfc         _dispatch_lane_invoke
29  libdispatch.dylib               0x32640d4b8         _dispatch_workloop_worker_thread
30  libsystem_pthread.dylib         0x3be5017a0         _pthread_wqthread

We need more detail in order to investigate this crash. How are you creating your Session? How are you making the requests that crash? Do you have any analytics or performance framework integrated that might be swizzling their way into the networking stack? Have you run with the thread sanitizer to see if you have any other threading issues? Do you have a project that reproduces the issue we can use to investigate?

Closing this for now due to lack of response. This looks very similar to crashes caused by the Firebase Performance framework's integration into URLSession or some other network performance framework, so you might try removing it and seeing if the new version has the crash.

Hello @jshier,
I apologise for my late answer, but answering your question the creation of the session is as follow :
`
let conf = URLSessionConfiguration.default
conf.httpAdditionalHeaders = ["Accept": "application/json",
"Referer": baseUrl,
"Content-Type": "application/json"]
conf.allowsCellularAccess = true
conf.requestCachePolicy = .reloadIgnoringLocalCacheData
    // Setup standard manager without ssl pinning
    alamoSession = Alamofire.Session(configuration: conf)

`
the issue is that this crash happens randomly and recreating a project wich could reproduce the issue was unfortunately not possible. And yes we use Sentry as performance and monitoring tool.


How to import AcceptSDK into project-Swift2.3

Hi,man
What can I do that importing "AcceptSDK" into my project with Swift2.3 ？ Do you have any other
version of SDK?
Look forward to your reply，thanks very much !

Are you still facing the issue? Could you please update Xcode and try?

It can work in my application after update Xcode & swift ，thanks @ptaneja


updates(osp and conformity): new content

Description
osp page content updates.
conformity page content updates
Why
change request
Issue
NA
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[ ] I have performed IP checks for added or updated 3rd party libraries
[ ] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[ ] I have added tests that prove my changes work
[ ] I have checked that new and existing tests pass locally with my changes
[ ] I have commented my code, particularly in hard-to-understand areas

@jjeroch FYI issue got resolved.
Thanks @evegufy

@manojava-gk 'updates' isn't a conventional commits type:

Please have a look at the examples:


Replace log4j logger with slf4j in java files

Do we need to go anything in the build to reduce the chance of including the circular log4j/slf adapter relationship?
Would something like the rules for maven enforcer at https://tenmilesquare.com/utilizing-maven-enforcer-plugin-to-ensure-dependency-and-version-usage/ help add this validation in one place, and avoid errors downstream in our poms?
Additionally #22 is a change in how we express our own dependencies, which can affect transitive dependency resolution?

One proposal - make the slf change, and then add this enforcement if we see it appear again and find it helps prevent the error. If not leave as is?


False Ctivity type

Here we can see Ride, Ride, Ride, but the first activity is a Run activity

I read RUN....ride ride :)

I am very sorry, don't know how it may happen. )))
It is closed, of course!


Initial commit of 2020 Google Season of Docs

This file is for the 2020 Google Season of Docs. Contributions from prospective
mentors are welcome!
Signed-off-by: Brian Warner<EMAIL_ADDRESS>

LGTM


shellscriptloader-0.1.1.sh

Hi,
So bootstrap.sh contains:
source shellscriptloader-0.1.1.sh
which doesn't appear in the shellscripts repo. But there is a set of similar scripts in contrib:
contrib/shellscriptloader-0.1.1/loader.sh
I tried using loader.sh as a replacement in bootstrap.sh, but received an error when loading:
loader: loader_include_loop(): found file not readable: $shellscripts_home/utils/log.sh
Is loader.sh a good replacement or could my placing of the shellscripts on my PATH be broken? Any hints appreciated!
Cheers,
Rowland

I had the same problem when trying to use contrib/shellscriptloader-0.1.1/loader.sh, but when I used contrib/shellscriptloader-0.1.1/loader.bash, it worked fine.

@tim-clifford Nice tip, thanks!


x509: certificate signed by unknown authority

I'm using prometheusIngester module to query my prometheus instance. It is behind a web proxy that does the SSL termination. I'm getting the following issue when using the default Docker image from dockerhub.
slo-exporter_1  | time="2021-02-08T15:45:32.03454Z" level=error msg="failed querying Prometheus: 'Post "https://my-prometheus.com": x509: certificate signed by unknown authority'" component=prometheusIngester query="http_server_requests_seconds_count"

To fix that I need to manually install ca-certificates, ending up with the following Dockerfile
FROM seznam/slo-exporter:v6.7.0

RUN apt update && apt install ca-certificates -y

I can send a PR adding this line if you agree.

Hi, thanks for rising the issue!
Your request sounds reasonable to me, so please feel free to send the PR :+1:
Just please add also the apt clean after the installation to keep the image small as possible.
Thanks!

Merged, released as v6.7.1.
Thank you for contributing.
Btw feel free to join us at slack, in case you come across other issues, or just want to discuss use-cases you want to address with slo-exporter. :)


extract jest config from package.json

Summary
Make package.json slimmer.
Changelog:
[General] [Changed] - Move Jest config outside of package.json
Test Plan
pass current ci

I can take care of this.


chrome on MacOS

hi, cool system.
I tried to run the demo on Chrome (latest) in MacOS and was not successful (even though the same works on Safari and Firefox).
The problem was that the sender issues a peer connect command, server receives the command (and thought it is connected). but the sender never saw that the connection was established and get stuck there.

found the issue. it's my own issue. It turns out one of my chrome extensions interfered. after its removal, everything works.

What extension was this? I've been seeing a similar situation in Chrome on Windows. Opening everything in Incognito or even just one half of the connection in Incognito works, but the same "stall" that you saw occurs if both are open in normal Chrome.
I had yet to diagnose if it's being caused by an extension or something with mDNS.

I removed a whole bunch of them, only left LastPass after clean up.
Here are the ones I remember:

All google plugin - Google Drive, Google Sheets, etc...
PureVPN
A plugin that I wrote myself.
...
I wasn't sure the problem was due to the extensions at first, so I wasn't
keeping track. I should have tracked it.

If you want to diagnose, you can just start chrome in Incognito mode, and
that makes it no extension for sure. If even that doesn't work, I would go
down other paths.
On Tue, Sep 15, 2020 at 10:50 AM Jack McKernan<EMAIL_ADDRESS>wrote:

What extension was this? I've been seeing a similar situation in Chrome on
Windows. Opening everything in Incognito or even just one half of the
connection in Incognito works, but the same "stall" that you saw occurs if
both are open in normal Chrome.
I had yet to diagnose if it's being caused by an extension or something
with mDNS.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/jmcker/Peer-to-Peer-Cue-System/issues/14#issuecomment-692875103,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFSGF64RZNJNHOIADXNANLSF6SO3ANCNFSM4RMCEDIA
.


Support for did:peer?

Any plans to support did:peer in OKAPI? This is becoming very important in the DIDComm world for out-of-band invitations.
Languages:

[ x] .NET
[ ] Go
[ ] Java
[ ] Dart
[ ] Python
[ ] Swift
[ ] Wasm

There are no plans on the road map at present, but I will confer with my teammates and see what plans could be made. Will let you know what I find out.
@tmarkovski @chiarapaskulin @janpieterz

Is there a future roadmap for OKAPI?


TAJO-1890: Clean up debug and test modes and unhandled exceptions.

+1
LGTM! Ship it. :-)

committed.


As devops, I want to provide settings via the environment and disable the admin UI

The original library uses environment variables. In case environment variables for OIDC are set, this whole admin page should be disabled, a message showing "These settings are managed by your organization." and ofcourse the OIDC environment variables should be used INSTEAD of the database values.
The values passed in the environment should be shown on the page.

See https://github.com/maykinmedia/django-setup-configuration/issues/1


Howto set token manually?

Hey,
my question is very similar to https://github.com/manfredsteyer/angular-oauth2-oidc/issues/1060. I have to two independent frontends (A and B). Both frontends obtains their tokens via authCode.
In one use-case the frontends should work together. A opens B, the user can type something into B and press "save"  and the data will be transmitted to our backend.
It would be nice, when user only needs one time to login (at A).
My idea was that A opens B with a queryparam (like http://frontendB.com?token=123) and I can inject the token into the oauth-service. I tried it with the authGuard and a wrapper for the oauth-service:
@Injectable({
  providedIn: 'root'
})
export class AuthGuard implements CanActivate {
  constructor(private routingService: RoutingService, private oAuthService: OauthServiceWrapper, private router: Router) {
  }

  canActivate(next: ActivatedRouteSnapshot,
              state: RouterStateSnapshot): Observable<boolean | UrlTree> | Promise<boolean | UrlTree> | boolean | UrlTree {

    if (this.oAuthService.hasValidAccessToken()) {
      // authorised so return true
      return true;
    }

    const params = new URLSearchParams(location.search);

    if (params.has('token')) {
      this.oAuthService.setRefreshToken(params.get('token'));

      return this.oAuthService.refreshToken()
        .then(() => this.router.navigate([], {
          queryParams: {
            token: null,
          },
          queryParamsHandling: 'merge'
        }))
        .then(() => true);
    }

    // not logged in so redirect to login page
    this.routingService.navigateToLogin();
    return false;
  }
}

@Injectable({
  providedIn: 'root'
})
export class OauthServiceWrapper extends OAuthService{

  public setRefreshToken(token: string): void {
    this._storage.setItem('refresh_token', token);
  }

}

But it wont work, because I get a this error:
ERROR Error: Uncaught (in promise): Error: 'tokenEndpoint' should not be null
Error: 'tokenEndpoint' should not be null

Is there a way to archive my goal?

I have to two independent frontends (A and B)

But:

My idea was that A opens B with a queryparam (like http://frontendB.com?token=123)

Beware that you're punching a hole in the security of your setup. If front-ends are independent, they should not reuse (quite powerful) bearer tokens from each other. You're currently 'breaking out of' the (intention of) the specs I think.
In theory however your approach could possibly work. You might need to pass more stuff around than just a refresh(?) token, not sure. For that you have to rely on the inner workings (which might change across versions! remember you're stepping outside the OAuth2/oidc specs here), so I recommend reading through the library source to see what all is inside the storage.

While that's all more generic replies to your approach, the specific error message you quote is just that, on its own: a message that configuration was not complete. Either there was a problem loading the discovery document, or you've not fully manually configured things. That problem will likely be caused by code not shown in your message, so you'll have to debug your app some more I think.
Good luck!

Yeah, you're right. To rely on inner working is indeed a bad idea.
We will try a other solution (the best option we see: Using the cookies of our identity-provider).


BUG: Cannot deploy Lambda via Serverless from global npm install location

Describe the bug
Because we use the project's lib/lambda/ path directly, this leads to permission denied when installed by one user and used by another, typically installed by root and used by non-root accounts.
To Reproduce
Steps to reproduce the behavior:

Install SA as root using npm install -g serverless-artillery
As non-root user, run slsart deploy

Expected behavior
SA deploys
Actual behavior
{ Error: EROFS: read-only file system, mkdir '/usr/lib/node_modules/serverless-artillery/lib/lambda/.serverless' when trying to make the  .serverless

because user running doesnt' haver permissions to write to install dir.

Fix will copy the lib\lambda folder to a temporary location, where the user has write privileges before running npm install and deploying on their behalf. The same logic applies to detect if this is the custom project vs. the standard Lambda.


[RELEASE] mc RELEASE.2024-04-29T09-56-05Z

MinIO Client RELEASE.2024-04-29T09-56-05Z has changes that impact the docs:

[ ] Enables broken envvar to disable the pager functionality of mc COMMAND -h PR #4909

Seems this mc command is hidden. Was there a request to document this functionality?
cli.BoolFlag{
 		Name:   "disable-pager, dp",
 		Usage:  "disable mc internal pager and print to raw stdout",
 		EnvVar: envPrefix + globalDisablePagerEnv,
 		Hidden: true,
 	},

@zveinn

I'll make a PR monday to make it visible. Once done I'll comment on this issue again

unhidden in https://github.com/minio/mc/pull/4929


New Storage View

 Create Storage new layouts

I've moved it to https://github.com/baking-bad/bcd/pull/390


Handle greater-than-1 aggregated range proof length properly

Currently panics: https://github.com/MystenLabs/dapol/blob/ebaa2541ebad993a9ad75e17fd8029e301d45c71/src/range/padding.rs#L80

Moved to fork: https://github.com/silversixpence-crypto/dapol/


"Export an Azure Cosmos container to a JSON file" example is wrong

"Export an Azure Cosmos container to a JSON file" example should not have "CollectionThroughput" in the end

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

ID: 9edf1df2-588e-01ff-6d1c-234b8e51d550
Version Independent ID: 27873c08-b6cc-a52f-f277-ff9818a5e4d2
Content: Tutorial: Database migration tool for Azure Cosmos DB
Content Source: articles/cosmos-db/import-data.md
Service: cosmos-db
GitHub Login: @deborahc
Microsoft Alias: dech

@papadi Thank you for the feedback. We are actively investigating and will get back to you soon.

@papadi Thanks for the valuable input to make the document correct.
We have updated the document content accordingly. The changes should be live once the PR is approved. You can review the PR meanwhile and let us know for any issue.

@papadi We will now proceed to close this thread. PR should be live in few days. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Content-Length forwarded with auth request leading to hanging

When a POST request is made with a body, a request is made to oauth2_proxy:
GET /oauth2/auth HTTP/1.1
Host: [redacted]
X-Forwarded-Proto: https
X-Scheme: https
X-Auth-Request-Redirect: /api/auth/login
Content-Length: 77
Accept-Encoding: gzip
accept: application/json, text/plain, */*
cache-control: no-cache
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3192.0 Safari/537.36
content-type: application/json;charset=UTF-8
accept-language: en-US,en;q=0.8
cookie: [redacted]

The GET request has a Content-Length header which causes oauth2_proxy to hang waiting for a body. In order to fix this we've added:
proxy_pass_request_body off;
proxy_set_header Content-Length "";

to the location /oauth2/ block.
Does that make sense? If so, it should be added to the README to prevent others from having this same problem.

Hmm, that's interesting - the nginx documentation suggests the same thing: http://nginx.org/en/docs/http/ngx_http_auth_request_module.html#example
I only started using "auth_request" mode this year, and I did find that I had to go back to the original "proxy" mode for a web app called nsqadmin, in order for some actions to work. This would explain it.
One small problem is that this simple fix would break signing in with a username and password directly (enabled with --htpasswd-file). So maybe we'd need a separate block for /oauth2/auth.


update builder to use go1.21.1 and bump cosign image

Summary

update builder to use go1.21.1 and bump cosign image

humm, i will take a look on that

fixed


google geocoder not working

Empty results:

You need to provide your API KEY like below:
geocoder.google('Mountain View, CA', key='your-api-key')

or set it in your system’s environment variables

@maning Good to know. Thanks.


hertz server connection monitoring

Is your feature request related to a problem? Please describe.
When there is an abnormal request on the line when the framework does not have connection monitoring, this time it is very difficult to troubleshoot the problem .
Describe the solution you'd like
Supports connection monitoring
Additional context
This is a real online requirement.

Waiting for help? Or transfer it to meego task.

Do you have any additional context for the issue? It's not clear to me what we should do.

There are no actual scenarios at the moment, choose to turn it off .


Session Tokens as environment variable

Hello,
First, Thanks for creating and maintaining this project :-)
One of the alternatives that AWS offers to access it services is using SessionTokens. As you know, this type of authentication requires an extra header with the a temporal security token (https://github.com/CargoSense/ex_aws/blob/master/lib/ex_aws/auth.ex#L36-L38). This is already implemented when the information is retrieved from the instance_role https://github.com/CargoSense/ex_aws/blob/master/lib/ex_aws/config.ex#L57-L61, but it does not work when the tokens are present in the env.
In order to make this work, I guess it would be enough to add the security_token as part of the common config fields on https://github.com/CargoSense/ex_aws/blob/master/lib/ex_aws/config.ex#L10, so it can be loaded as any other config option, but I wanted to check with you first before submitting a PR
related: http://docs.aws.amazon.com/STS/latest/APIReference/API_GetSessionToken.html
Thanks

Aren't these tokens only valid for 12 hours? If so, what good are they when used in a way that doesn't have a repeatable update process?

Hi @benwilson512. Thanks for replying so fast. I can think in several situations when you could use tokens that expire in less than 12 hours (for example, tailing a kinesis stream for debugging purposes), but I am actually using them in development. I could, of course, use different ways to do this, but I think that having a config option suits better and can be really usefull

Aight sounds good. Feel free to make a PR :) Your overall approach sounds good, we'll hash out details on the PR itself.

Completed


How to include non packaged system dependencies

In my situation, I have proper system dependencies for Linux and MacOS with apt/brew (working fine!). For Windows, I have a few lines to run before building my executables (nothing available on choco).
I found the "reusable workflow" item in the documentation, but it is not clear to me whether what I would install with such a workflow would persist in the runners of the build artifact matrix later?
More generally, I like listing dependencies and let the scripts write the install commands on my behalf, but I assume there's often some patching to do in addition, so what is the official recommendation here?

In that case, build.rs is the right approach: https://doc.rust-lang.org/cargo/reference/build-scripts.html I haven't used it myself yet, but the cc crate is used to help with this. https://crates.io/crates/cc

I see, thank you!
Here is what I need to run for Windows. Ideally, I would just add this to the generated release.yml.
Isn't it overkill to go with build.rs which looks more designed to compile code?

    runs-on: windows-latest
    steps:
    - uses: actions/checkout@xx
    - ...
    - name: Windows dependencies
      shell: bash
      run: |
        curl -L https://downloads.myriadrf.org/builds/PothosSDR/PothosSDR-2021.07.25-vc16-x64.exe -o pothossdr.exe
        7z x -opothos -y pothossdr.exe
        echo "${{github.workspace}}/pothos/bin" >> $GITHUB_PATH

Chiming in to say that I've seen this in other spots as well. I understand that build.rs would work but I don't disagree that using it might be more than I would personally want to do for my own projects. I wonder if there's a way for us to let folks specify these as config instead of asking them to write rust code (as a "build.rs" solution wouldn't work for a non-rust project anyways)

Thanks for jumping in @ashleygwilliams
Yes indeed, I think it would be reasonable to have something basic in the Cargo.toml starting from
[workspace.metadata.dist.dependencies.script]
target1 = "script_target1.sh"
target2 = "script_target2.sh"

hey @xoolive i think that looks very reasonable and is similar to the config we have for generic builds (https://opensource.axo.dev/cargo-dist/book/generic-builds.html). inparticular- wrapping things in a shell file that is set to a config value is a pattern we've used before. - would you be at all interested in contributing/collaborating on this feature?

Hi @ashleygwilliams I will try to come up with something, although I cannot commit to any ETA. I am quite new to Rust, but will do my best and ask for a review. Do we agree that I can focus on a solution that generates the proper output in cargo dist plan --output-format=json?


receive the onDraw from props and pass the canvas and info to it

This PR resolves #763

I have signed the CLA on https://cla.shopify.com/individual-cla after facing cla-needed error.

Thanks for making this PR. We think that what you want is the Drawing component: https://github.com/software-mansion-labs/drawings-and-animations-workshop/blob/main/src/SkiaLogo/PathGradient.tsx#L94
That will fix your use case. I will close this PR, feel free to reopen it if you believe the Drawing component doesn't solve your use case. We will document the Drawing component #763

Dear @wcandillon, please see my example:

The pencil is under the PNG image and I think my PR is the only way. Furthermore, why is Canvas using full of SkiaView props types? if you hadn't considered this for Canvas, I think you should remove other SkiaView props types from the Canvas type. it makes confusion.

The <Drawing> component provides exactly the functionality you are looking for.


crypto: test fips140=only mode

fips140=only from #70123 breaks any non-FIPS cryptography. Testing a mode designed to break things is tricky.
Running the whole test suite is prohibitive. Instead, we should probably write a dedicated test that goes through things that are expected to work, and things that are not expected to work.

Related Code Changes

crypto: implement fips140=only mode

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)


md_ops: wait for MDServer to be initialized

In the init code, MDOps is set before MDServer, and so there's a race condition where something (e.g., the disk cache initialization code that triggers when the keybase service connection is established) can try to use the MDServer before it exists.
So just add a simple sleep for the very rare case where this could happen. This doesn't seem like it's worth the code complexity of something that would get notified exactly when the MDServer is set.
Issue: KBFS-3587

Sweet, this could be responsible for some of the kbfsdocker flakes.

Not sure about that -- the symptom here is a client-side panic, not a communication failure to the server.

Hmm, fair enough.


presets/styles for address interpolation

[ ] Line tagged with addr:interpolation should show 1-way markers.
[ ] Selecting the line should show two address fields, one for each end.
[ ] Field for addr:interpolation.

wip at #4220

Nice, I'd thought about suggesting this but never got round to it. Is this available to test anywhere? As it's not on http://preview.ideditor.com/master/

@boothym

Is this available to test anywhere

I'll have it running on a test server for a while

As it's not on http://preview.ideditor.com/master/

Only the master branch is there, this pull request hasn't been merged yet, when the PR is merged, it will update master and be available there.

@JamesKingdom thought so, thanks for the test server.
Looks good - only thing I that I can suggest is the ability to search for the address preset on vertexes...


Streaming code cannot see environment variables set when using risedev dev

Describe the bug
SOME_ENV_VAR=foo ./risedev d cannot pass the environment variable to compute node. According to @BugenZhao, this is not expected.
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response

Maybe related: https://github.com/risingwavelabs/risingwave/pull/14228

Could occur if there's already a tmux server running before launching ./risedev d.
https://stackoverflow.com/questions/50506708/how-to-start-two-tmux-sessions-with-different-environments


Don't display artist card if there are no published works

Cab addressed this already and just deployed 👍


Fix mismatched types

Like the code for Windows, we want to avoid build failures by adding to_string() for non-Windows code.

Thanks!


Fix compiler error on Android

I am using React Native 0.50.3 and could not compile my Android app after installing this module.
The solution is removing an "@Override" tag, however I am not sure what would happen when trying to compile using React Native < 0.47.0.

Works for me on RN 0.49.5, thank you.

@ojcarcete Thanks. Seem we have to update other platforms too. Is there any CHANGELOG or migration guide for upgrading to latest version of React Native?

@hnq90 Lately I have been using rn-diff, which gives you the changes made to the react native app template since your current version.
After you either apply the patch or perform the changes manually, you'll need to npm install your target version of React-Native and deal with the rest of your project's dependencies. Also keep in mind the latest versions have switched to using a single index.js entrypoint, you'll have to create this file manually.
This is by far the worst part of React-Native in my opinion... good luck!


Limitation on loading files size in local mode

While trying to upload  files greater than ~10MB in server/Local
get exception:
Uncaught (in promise) RangeError: Source is too large
at Uint8Array.set ()
at ReadBufferStream.concat (webpack:.../node_modules/dcmjs/build/dcmjs.es.js?:855)
Problematic files is XA cine.
Files ~0.5 MB/single frames are loaded successfully.

I just tried this with a 28mb mammogram and everything worked fine. Could you de-identify your dataset and share it? Does it work if it is uploaded to a PACS first?

Just before anonimaization:
-files was multiframe XA and it was applied directly from local disk.

Thanks for the fast response!

It worked while provided by WADO-RS

Good to know. It might be an issue with multiframe images on the local viewer. I notice that the multiframe images I am testing are not working either (the ?frame=N is probably not being added to the imageId). They aren't crashing, though.

Please see uploaded problematic file at https://github.com/vicOnGit75/TmpStorage;
Anyway I guess this behavior you watched- not crashing, but not exiting from uploading state with
error :Uncaught (in promise) RangeError: Source is too large
at Uint8Array.set ()
...
in console.

@vicOnGit75 what browser are you using? I think the max array size may be lower depending on your browser vendor.

on my chrome 76
i get

window.performance.memory.jsHeapSizeLimit
2197815296
Should I check smth else?


chore(updatecli): Uses the native temurin source

Enhanced JDK version bumping configurations for JDK 17 and JDK 21 thanks to the native temurin source
Removed outdated script for JDK verification to streamline processes.

Testing done
updatecli diff --debug --config ./updatecli/updatecli.d/jdk17.yaml --values ./updatecli/values.github-action.yaml 2>&1
updatecli diff --debug --config ./updatecli/updatecli.d/jdk21.yaml --values ./updatecli/values.github-action.yaml 2>&1

Submitter checklist

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

jenkinsci.docker.alpine_jdk17.Default.#7 [alpine_jdk17-plugins-cli] do not upgrade if plugin has been manually updated

fails, but this has nothing to do with the proposed changes. #1958 fails the same way with different file changes. 🤷


Object diet

Part 1 of a multi-part series. This speeds up each node's wrapping process a little bit. There's a lot more to do in the Neo4j gem but it's gotta start somewhere.

Coverage decreased (-0.76%) to 92.69% when pulling f2d48ab0f0ed89193e0d13b0032a6898b8acbc0e on object_diet into df1016517f06a2f9db45b44a1e9d84397ac7cc64 on master.


Longer texts in toasts on mobile cut off

Maybe the toast should then have more height

Need to add
media="screen, projection" {
.toast {
height: 100%;
}
}


Scheduled test cases fix

Fix for the scheduled integration test_chat_model test case failure

Reason for failure: mistralai model does not allow AIMessage followed by SystemMessage
Successful Workflow

@raspawar ok, if this is the issue then the server side implementation must have changed. our options are to 0. change the default model to one that passes all the tests, 1. mark this test as xfail.
go w/ (1) for now and investigate (0).

My guess is ==> It is not server side implementation This test cases were added in recent PR: #63 And Integration test cases run only in Scheduled tests github workflow action, so after it got merged, scheduled test cases started failing.

#63 added test_stop while the failures are in test_messages. the test_stop tests are already marked xfail
change test_messages to also be xfail for now.

ok, I will keep looking, meanwhile I have marked test_messages as xfail, so can we close this as the scheduled test cases will keep failing


Prune resources when IstioControlPlane changes

https://github.com/istio/istio/issues/17825

@irisdingbj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
de5665c4fce6cef6c0a20e61839065f6cd93bff9
link
/test gencheck_operator

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

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
de5665c4fce6cef6c0a20e61839065f6cd93bff9
link
/test gencheck_operator

lint_operator
de5665c4fce6cef6c0a20e61839065f6cd93bff9
link
/test lint_operator

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

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
de5665c4fce6cef6c0a20e61839065f6cd93bff9
link
/test lint_operator

gencheck_operator
9fdb2ecbbaf8bd85bb70a89b98c145647682bac1
link
/test gencheck_operator

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

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
9fdb2ecbbaf8bd85bb70a89b98c145647682bac1
link
/test gencheck_operator

lint_operator
9fdb2ecbbaf8bd85bb70a89b98c145647682bac1
link
/test lint_operator

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

@irisdingbj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
9fdb2ecbbaf8bd85bb70a89b98c145647682bac1
link
/test lint_operator

gencheck_operator
f9f989da81cc853d0691210c90493b15bc8a2a2b
link
/test gencheck_operator

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

@irisdingbj The resources can be pruned when I switch profile with latest master code;
The controller will prune resources with different generation annotation, the current logic is pretty tricky, but it is working in my env.
See my comments for the original issue: https://github.com/istio/istio/issues/17825#issuecomment-541320696

@irisdingbj The resources can be pruned in my env when I switch profile with latest master code;
The controller will prune resources with different generation annotation, the current logic is pretty tricky, but it is working in my env.
See my comments for the original issue: istio/istio#17825 (comment)

Tried using latest master code and this works.


About the Self-RAG retrieval rate

I found that the retrieval rate is really high for Self-RAG.
in active_pipeline.py line 164
judge_retrieve(self, input_prompts):
            all_pred_text = []
            all_pred_log_probs = []
            # For vllm, requesting too many logprobes can seriously affect speed
            # 20 probs is enough for calculate
            preds = self.generator.generate(input_prompts, return_raw_output=True, logprobs=20, max_tokens=1, skip_special_tokens=False)
            for single_pred in preds:
                pred_text = single_pred.outputs[0].text
                pred_log_probs = single_pred.outputs[0].logprobs
                all_pred_text.append(pred_text)
                all_pred_log_probs.append(pred_log_probs)

            retrieval_flags = []
            for idx, single_pred in enumerate(preds):
                if self.threshold is not None:
                    score_dict = {}
                    for tok, tok_id in self.ret_tokens.items():
                        if tok_id not in all_pred_log_probs[idx][0]:
                            score_dict[tok] = -100
                        else:
                            prob = all_pred_log_probs[idx][0][tok_id].logprob
                            score_dict[tok] = np.exp(prob)
                    do_retrieve = (
                        score_dict["[Retrieval]"] / (score_dict["[Retrieval]"] + score_dict["[No Retrieval]"])
                        > self.threshold
                    )
                else:
                    do_retrieve = "[Retrieval]" in all_pred_text[idx]

                retrieval_flags.append(do_retrieve)

if tok_id not in all_pred_log_probs[idx][0]:
score_dict[tok] = -100
else:
prob = all_pred_log_probs[idx][0][tok_id].logprob
score_dict[tok] = np.exp(prob)
Is this right? It should be score_dict[tok] = np.exp(-100).
I tried that but it seems that the retrieval rate would be too high. The retriever will be triggered almost all the time. Then it may be pointless to decide wether to retrieve or not?

Thanks for your question. We noticed this in previous experiments. There are indeed some problems here. If the score is set to -100, the do_retrieve score will become negative when calculated, which is less than self.threshold, we will fix it in next version. However, if this idea is followed, there should be a lot of examples in the dataset that are not retrieved, which is inconsistent with your experimental phenomenon.
So I guess it may be my explanation below. The logic here is actually to access the logprobs of the next token generated. Due to the limitations of vllm and performance reasons, we only get the logprobs of the top 20 tokens. In this case, if the top 20 tokens do not have the "[Retrieval]" and "[No Retrieval]" tags, the overall score will be 0.5, which is greater than the threshold of 0.2, and the query needs to be retrieved. In fact, we set the top 30000 tokens at the beginning, but this will cause the generation to be very slow.
I think this is a problem with this method or the trained model, which leads to inaccurate retrieval scores.

I mean I changed -100 to np.exp(-100) and found that the retriever will be triggered for almost every request.
Also, I looked into the offical github repo for self-RAG, they even didn't use np.exp() for the computation of the probility

So I am confused about how to get correct results, and I don't know why we can decide on wether to retrieve or not based on this method.


update BaseBackend to use a default coord_crs from the tms

update BaseBackend to use a default coord_crs from the tms parameter. There is also the mosaic def's tms which could be used but it is not clear if should be assumed or not...
This was causing issues with custom non earth TMSs. This is a higher priority than #233 to get resolved.

@vincentsarago, forgive me if I don't explain the issue well here as it's fairly complicated (lots of interplay between Proj/WKT2 standards) but here's my current understanding:
I am working in the planetcantile project to define TMSs for other planetary bodies (Moon, Mars, etc) so that these can be used across titiler/morecantile/cogeo-mosaic for mosaic.json. Currently in Titiler the mosaicjson endpoints will default to WGS84 for the CRS here and cause Proj errors when attempting to convert between my non-earth CRSs/TMSs.
o without modifying Titiler directly I think it makes more sense to update cogeo-mosaic as each TMS has a explicit or implicitly discoverable geographic crs from it's CRS parameter. One can work around this by setting PROJ_IGNORE_CELESTIAL_BODY=YES, but that is a hack and may not always do the right thing depending on the ellipsoid (many of the planetary CRSs have ellipsoids with different flattenings/ no fattenings as the ellipsoids are defined with equal semi major/minor axes, but are not explicitly spherical CRS which are possible to define with WKT2...)
Again, If a person defines a mosaic.json file, a TMS is required, and so think it makes sense to always grab the appropriate geographic crs from the TMS object (which will know it implicitly from the CRS/geographic_crs of the tms) rather than assuming WGS84. assets_for_tile seems to do this already but for consistency and to avoid the exceptions I was seeing from titiler this PR attempts to make that consistent
On a side note, I am also debugging an issue in morecantile with the geographic_crs/rasterio_geographic_crs ending up as 4326 vs the intended geographic_crs depending on how the TMS is serialized/initialized. Although I haven't made enough progress on that to post an issue or pr yet.


Avoid memory allocation inside busy-loops?

The autogenerated code for evaluating a transition codewords returns a vector for each element in the FRI domain. I wonder if the code wouldn't be faster if the entire data structure for holding the result (the transition quotient/transition codeword values) was generated outside the busy-loop (the loop that runs over the entire FRI domain) and the function that calculates a list of transition quotients/codewords for a single point then only got a mutable reference to a slice in the data structure that stores the result.
My intuition tells me that allocations of vectors inside these busy loops slows the code down.
Current function signature
 #[inline]
fn evaluate_transition_constraints(
        &self,
        current_row: &[XFieldElement],
        next_row: &[XFieldElement],
        challenges: &AllChallenges,
    ) -> Vec<XFieldElement> {

Suggested function signature, returning void.
#[inline]
    fn evaluate_transition_constraints(
        &self,
        current_row: &[XFieldElement],
        next_row: &[XFieldElement],
        challenges: &AllChallenges,
        res: &mut [XFieldElement; CONSTRAINT_COUNT],
    )

res could be an array pointer or a pointer to a vector, or a mutable slice. Not sure what would type check and work best.

Constraint evaluation is very fast now – closing.


Unable to instantiate Apache Zeppelin on Docker using kitematic

Expected behavior
apache zeppelin instance should get started.
Actual behavior
(HTTP code 404) unexpected - {"message":"manifest for apache/zeppelin:latest not found"}
Information about the Issue
Some manifest is missing
Steps to reproduce the behavior

Goto Kitematic
Type apache/zeppelin
I have selected : "https://hub.docker.com/r/apache/zeppelin/"
Then it throws an error

docker pull apache/zeppelin:0.7.3
docker run --rm -p 8080:8080 apache/zeppelin:0.7.3
You need to specify tagname


adding python 3 compatibility

fixing some of the imports and commands to work with python 3.5

Hello kmader,
First of all, I am sorry for the late reply. I have to say I am new to the open-source community and I failed to pay attention to the few pull requests. I will try to find the time to manage this aspect of the project better from now on, as I definitely see the added benefit, which I simply diregarded previously because of pressure for my own research. Mistake of me.
I totally like your changes and the python 3 compatibility feature. Changes look good.
 And so there are numerous conflicts. As it's totally my fault for not replying to this earlier and the conflict resolution is now quite some work, I hope you are ok if I build on top of your branch myself to resolve the conflicts before I merge them in?
Sorry again and thanks a lot for your initiative.
Kostas

The conflicts were resolved by rebasing to current master. Changes extended and partly validated. On branch python3compat, to be merged to master soon.
Thank you very much for the contribution kmader/4quant and sorry for the late action. I will try to manage pull requests better in the future.
Kostas


attribute-typo: allow dontNpmInstall

joplin:                                                                                <details>                                                                                warning: attribute-typo                                                                                A likely typo in dontNpmInstall argument was found, did you mean dontInstall?                                                                                Near pkgs/development/node-packages/node-env.nix:409:14:                                                                                ────────────────────                                                                                |                                                                                409 |       inherit dontNpmInstall preRebuild unpackPhase buildPhase;
    |              ^
────────────────────

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/attribute-typo.md
warning: attribute-typo
A likely typo in preRebuild argument was found, did you mean postBuild?

Near pkgs/development/node-packages/node-env.nix:409:14:

────────────────────
    |
409 |       inherit dontNpmInstall preRebuild unpackPhase buildPhase;
    |              ^
────────────────────

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/attribute-typo.md
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?

Near pkgs/development/node-packages/node-packages.nix:85205:5:

Thanks.


feat(payload builder): transaction pool filter

Adds a TransactionFilter trait, exposing a is_valid function that can be called in order to verify if the provided transaction passes the filtering implemented.
Implements the above mentioned trait on a NoOpTransactionFilter which lets all transactions pass.

Closes https://github.com/paradigmxyz/reth/issues/10437

@mattsse slight bump on this :)

I've undone the payload builder integration because I have something else in mind now


Version 1.3.2 not able to authenticate due to missing region

I upgraded to 1.3.2 in order to be able to use profile switching.  At first, I could not authenticate after exporting my AWS_PROFILE.  I then tried just PROFILE and that seems to be the way now; unsure if that is related or not to my second issue below.
➜  ~ export AWS_PROFILE=my-profile-name ➜  ~ ssmsh                                                                                <aws:my-profile-name> Error initializing session. Is your authentication correct? SharedCredsLoad: failed to get profile
However:
➜  ~ export PROFILE=my-profile-name ➜  ~ ssmsh Error initializing session. Is your authentication correct? MissingRegion: could not find region configuration
So I assume using PROFILE is fine now, and moved on to why region was undefined and seemingly unable to be defined.  In my ~/.aws/config, I have region set for each profile and verified they are correct using the aws cli.  I have tried to define the region a number of ways using ssmsh commands as well as export, but just wind up with errors like:
 flag provided but not defined: -region Usage of ssmsh:   -file string     	Read commands from file (use - for stdin)   -version     	Display the current version
Therefore, ssmsh won't start up due to a missing region that I cannot seem to set.

Thanks for the report, @TorPeeto! Can you download the 1.3.2 release again? I've updated it with a fix. Let me know if that works for you.

Thanks for the reply @bwhaley !
I re-downloaded and am now unblocked.  I can use AWS_PROFILE to set my profile, and ssmsh initiates using my aws profile along with the region that it is configured with!
However, the new profile feature within ssmsh does not work now.
export AWS_PROFILE=my-profile-1
ssmsh                                                                                <aws:my-profile-1>
/>ls
Warning: Listing a large number of parameters may take a long time.
Press ^C to interrupt.
dir1/
dir2/
dir3/
dir4/
dir5/
/>profile
my-profile-1
/>profile my-profile-2
/>profile
my-profile-1
/>

Oh dear 🤦♂  - working on that.

Okay, this time with feeling! Please find a new binary attached to the 1.3.2 release, @TorPeeto.

That did the trick @bwhaley - Thank you!  Looks like this issue is resolved

Whew. I need to write more & better tests. Thanks for your patience.


build a full featured erlang:alpine image

to keep image size under 30MB is unrealistic, but to build full featured erlang
has more benefits; image size is between 60~70MB now.
comparing with 45 builtin erlang apps (https://github.com/erlang/otp/tree/master/lib)
now the alpine image has 42 of them, missing ones are jinterface, orber, odbc.
the dirty scheduler is enabled by default since 20, hence this configure switch can be removed.
closes #58 #57

docker-library/official-images#3237


Added Rasterband::set_no_data accepting Option<f64>.

[X] I agree to follow the project's code of conduct.
[x] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

Closes #275

@lnicola FYI: Went with breaking change approach.

bors r+


test(transformer/replace-global-defines): remove panicking test

Follow-on after #7811. Remove the panicking test. It does currently cause a panic if replacement contains scopes (e.g. () => 123) but that's a bug. So we shouldn't have a test saying that it should panic.

#7838  👈 (View in Graphite)
main

How to use the Graphite Merge Queue
Add either label to this PR to merge it via the merge queue:

0-merge - adds this PR to the back of the merge queue
hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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

Merge activity

Dec 13, 6:27 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


The phase banner's bottom border doesn't look right when immediately above the masthead

When viewing the design system homepage on mobile the phase banner is immediately above the blue 'Design your service...' masthead and the border-bottom is flush against it and it stands out.
It's only 1px so it's easy to miss, but it doesn't look intentional so I thought it was worth reporting.

Operating system: Andorid, Linux
Browser: Chrome, Firefox
Browser version: Latest.

Thanks for taking the time to write this up, @peteryates 🙌🏻


Removing ThreadLocal then close() called in ReadAheadInputStream

@tbw777
"No description provided."

Closing: No feedback in 3 weeks.

its good to close, because it required more deep research


updated invalid links

The links have moved to a new place.
Signed-off-by: Eric Lee<EMAIL_ADDRESS>

Thanks very much

@adriancole It's my pleasure. Thanks.


Microsoft Download Server download not available

Currently the Visual Studio Runtime 2022 is not downloadable from the Microsoft servers

Downloads are available again, but slower then usual.

Downloads work now as intended.


Support NCCL 2.14

Tasks

[ ] Read Release Notes (cuTENSOR / cuSPARSELt / cuDNN / NCCL).
FlexCI

[ ] Update .pfnci/schema.yaml and .pfnci/matirx.yaml
[ ] Backport.

Library Installer

[ ] Update cupyx/tools/install_library.py.
[ ] Backport.

Documentation

[ ] Update Requirements section in the Installation Guide
[ ] Backport.

[ ] Implement new features using the version, if any.

Done in #6534 and #7069


Errors in 1-Introduction/Stock_NeurIPS2018_3_Backtest.ipynb

Where is 'processed_full' defined?

----> 1 data_risk_indicator = processed_full[(processed_full.date<TRAIN_END_DATE) & (processed_full.date>=TRAIN_START_DATE)]
      2 insample_risk_indicator = data_risk_indicator.drop_duplicates(subset=['date'])
NameError: name 'processed_full' is not defined

Where is the file  'agent_a2c.zip'?

----> 1 trained_a2c = A2C.load("agent_a2c") if if_using_a2c else None
      2 trained_ddpg = DDPG.load("agent_ddpg") if if_using_ddpg else None
FileNotFoundError: [Errno 2] No such file or directory: 'agent_a2c.zip'

I countered above error when I followed the tutorial (https://finrl.readthedocs.io/en/latest/start/first_glance.html). But every Colab notebook example reads files created from the previous example and sometimes non-existing files too.  I am afraid that I cannot continue the tutorial.
Can I let the current Colab notebook read files created from the previous Colab  notebok example?

Hi, thanks for your report.
We are working on the reconstruction of these notebooks. Stock_NeurIPS2018_3_Backtest.ipynb was just updated. Please try it out.

Can I let the current Colab notebook read files created from the previous Colab notebok example?
Yeah the three-part design is aim for letting users try different setting in each part, and use the files created from previous part in the latter part. You could also use the sample files (data and agent files) we provided to quickly go through the whole process.

Thanks for your rapid response. I tried again and I barely went through the Colab  examples up to 3.

Can I let the current Colab notebook read files created from the previous Colab notebok example?

Yeah the three-part design is aim for letting users try different setting in each part, and use the files created from previous part in the latter part. You could also use the sample files (data and agent files) we provided to quickly go through the whole process.

I found that files could not be shared between different Colab scripts. It means that the train_data.csv created in the 1st Colab script is not readable from the 2nd Colab script. It tried to download it from the 1st one to local and upload to the 2nd Colab, but the download failed maybe because the file size is too big.
After many trials and failures, I barely found a way to share the files using Google Drive. This way looks good, but may not be straight forward to beginners because it requires change of the source code.
Are you running and testing using Jupyter notebook in your own server, not in Colab? Files are shared between different Jupyter notebooks and I wonder that this is why you don't have the file sharing problems.
I hope that the Tutorial examples run in Colab rather than in Jupyter Notebook in an indivisual machine because I have to pay money to use a cloud server which costs
money, and the cost is expensive when I use GPU or TPU. I want to run most of time in Colab which is completely free including GPU and TPU.


Next token prediction - head code location / config to pass

Hello! Great work and thanks for the opensource! I'm trying to check the pretraining and see the next token prediction on a dataset we have.
I find the standalone model probably better for loading pretrained weights and changing the dataloading for this purpose. But in the standalone model, there is no head provided for the next token prediction. It is said to be in the main hyenaDNA code but it is a bit hard for me to find where it lies and how I can modify the standalone .py for it. Can you help me with where this part of the code is or maybe how we can modify the config file for this purpose?
Also, I'm not an expert in genome study so I'm not familiar with the data structure if it is assumed to be well known. Since I don't have access to the main data you use but with some other single chromosome genome sequences, can you let me know the data structure so I can generate the correct files needed? (the .fa, I think consists of a line of info and a line of sequence for each record? And for .bed is the starting and ending position information?)
Thanks!

Hello!  Thanks!
Unfortunately, a lot of the things you asked for are not supported (but the data is available and public!), and require some custom manipulation of the code.  Fortunately it's not especially difficult to do, but it does require some time investment to get familiar with the architecture and training code.  We're certainly open to contributions!  (welcome to research!)
Pretraining data info.
For pretraining you'll definitely want to use the main repo code.  There's a lot of little extra things that make pretraining efficient and high quality in the main repo.
The language head is used here, so you'll want to get familiar with this.  This is what allows you to get an actual prediction of the next token, vs. getting just an embedding.
And maybe something like this would help you get started with loading and passing in sequences, but again, it needs modification.
Good luck!


App Crash on open

Description
Fatal Exception: com.facebook.jni.CppException: facebook::react::Recoverable: Could not open file/data/user/0/in.mohalla.video/files/CodePush/4adb53238f96cb818fe4edd33d9ae00c8750c2186a87cadd2a51c0bd6f14669d/data/data/in.mohalla.video/files/CodePush/unzipped/CodePush/index.android.bundle: No such file or directory
at com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromFile(CatalystInstanceImpl.java)
at com.facebook.react.bridge.CatalystInstanceImpl.loadScriptFromFile(CatalystInstanceImpl.java:245)
at com.facebook.react.bridge.JSBundleLoader$2.loadScript(JSBundleLoader.java:48)
at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:268)
at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1371)
at com.facebook.react.ReactInstanceManager.access$1100(ReactInstanceManager.java:136)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1065)
at java.lang.Thread.run(Thread.java:923)
React Native Version
0.71.7
Output of npx react-native info
System:
OS: macOS 13.4
CPU: (10) arm64 Apple M1 Pro
Memory: 2.77 GB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.1.0 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 9.6.4 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 11.0.17 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.3 => 0.66.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
App Crashes as soon as u open it. Not able to reproduce though but it is being reported in Crashlytics and had been happening in 0.66.3 also. I recently upgraded to 0.71.7, but still hapening
Snack, code example, screenshot, or link to a repository

file/data/user/0/in.mohalla.video/files/CodePush/4adb53238f96cb818fe4edd33d9ae00c8750c2186a87cadd2a51c0bd6f14669d/data/data/in.mohalla.video/files/CodePush/unzipped/CodePush/index.android.bundle: No such file or directory

That's an issue with CodePush
Hi @mohitarora777
Thanks for reporting this issue.
It seems like this issue is actually unrelated to React Native core but related to Microsoft's CodePush. Please open this issue against this other repository:
https://github.com/microsoft/code-push/issues
I'll be closing this but feel free to reopen if the other repo points back to us as a issue in the core of React Native.

hi was there any resolution to this issue @mohitarora777  ? Getting the same crash


Remove version: taers232c.GAMADV-XTD3 version 6.72.16

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/taers232c/GAMADV-XTD3/releases/download/v6.72.16/gamadv-xtd3-6.72.16-windows-x86_64.msi
OK
(Automated message - build 910)


Refactor code to update expectations to avoid "string typing" and code repetition

Use case
As the collector code base grows, there are common concerns around handling expectations that leads to copy/pasted code and general repetition. Moreover, handling is very "stringly typed" and is inherently brittle.
Current Workaround
Keep coding as it is.
Proposed Solution
Create common components in pyobas to manage expectations:

determine an expectation type
update an expectation with a default, or given message / succes and failure

Additional Information
Example problematic code: https://github.com/OpenBAS-Platform/collectors/blob/0a2e802bdb03a391ae9831d794a235a29786c866/microsoft-defender/src/openbas_microsoft_defender.py#L388-L410

Do I understand that this feature will be solved in 1.10 ? @antoinemzs @RomuDeuxfois

Hi Ellyn, no this is not part of 1.10.0; it's rather a technical improvement that will be gradually taken on alongside feature work such as #68

Clear, thanks for the update and clarification @antoinemzs 👍


robot compile should work without ROS

Because we import bitbots_bringup in robot_compile a valid ROS environment is required.
The script should work without ros

closed


Add security.md file

Content copied from https://github.com/wagtail/wagtail/blob/main/SECURITY.md

Thank you!


Pop up won't appear if there are quotes inside the title

To Reproduce
from winotify import Notification

toast = Notification(app_id="windows app",
                     title='Winotify "Test" Toast',
                     msg="New Notification!",
                     icon=r"c:\path\to\icon.png")

toast.show()

The notification won't appear.

And a similar issue
toast = Notification(app_id="windows app",
                     title='Winotify $ 99 Toast',
                     msg="New Notification!",
                     icon=r"c:\path\to\icon.png")

works fine
while  title='Winotify $99 Toast' will be shown as "Winotify  Toast"


Feature smartmeter handle shipment file

This pull request contains the changes for handle shipment file use case.

All is well.

All is well.

All is well.

All is well.

All is well.


fix: make c'tor explicit

This prevents a upcoming warning when we enable clang-tidy on headers.

This change is

We decided offline to disable this clang-tidy warning, so this PR is no longer needed.


feat(pinecone): add support for delete by metadata filter

This PR adds pass-through ability to delete records from Pinecone using metadata filtering which was officially supported in the v1 release of Pinecone's JS client.
This gives users the ability to delete vectors using matching metadata filters which can be more flexible than deleting by ID.

This is great, thank you!


grammar improvements in the glossary

Per prior arrangement, if this PR needs approval, or if the commits need to be pulled into the private repo -- and while @eriklindeman is OOF April 10-17 -- only @FarazGIS should be notified. Thanks.
In this PR, the overall Acrolinx score improved from 89 to 97 in glossary.md.

#sign-off


Support GPU broadcast exchange reuse to feed CPU BHJ when AQE is enabled

Signed-off-by: Andy Grove<EMAIL_ADDRESS>This PR makes it possible for a GPU exchange to be re-used by ReuseExchange even when it is feeding a CPU join. A specialized columnar-to-row transition is inserted that converts the data to the serialized format that the CPU expects.
~WIP because I am concerned that this introduces a resource leak and I am still looking into that.~
I also need to figure out what we can do for testing. I manually tested this by running NDS q14a.
Closes https://github.com/NVIDIA/spark-rapids/issues/2042

@revans2 @tgravescs I would appreciate a review to make sure I understood this correctly.

without me having looked at the details is there a reason we use a separate GpuBroadcastColumnarToRow vs just implementing doExecuteBroadcast in GpuColumnarToRow?  Would be good to state that in description.

@tgravescs @revans2 This is ready for re-review. This is what the plan looks like now:

Thanks for the review @revans2. I pushed some commits to fix the simple feedback items and filed https://github.com/NVIDIA/spark-rapids/issues/2219 for a refactor to reduce code duplication.

just to note, I tried out a version of this with Q14a and that query took about 2.2 minutes on my setup vs 1.8 on the CPU. With the Spark fix we have proposed it took 1.2 minute.  I'm assuming the difference in time there was in a CPU broadcasthashjoin vs a GPU broadcasthashjoin.
the explain text output in the UI also seems not show the GPUBroadcastToCpu but the graph at the top does.  That might be a spark issue though.

the explain text output in the UI also seems not show the GPUBroadcastToCpu but the graph at the top does. That might be a spark issue though.

This issue seems specific to Spark 3.1.1 and works fine with 3.0.2 so it does seem to be a regression in Spark somehow, although I have not finished investigating this.

Things look good I didn't see a follow on issue for code cleanup, and I would like to see us dig into the performance issues that Tom saw
https://github.com/NVIDIA/spark-rapids/pull/2188#issuecomment-824115676

Yeah I'm wondering if there is a way we can keep things GPU based on what I saw on the plans  in the runs with spark fix, but we can do as followup.

Here's the issue for code cleanup: https://github.com/NVIDIA/spark-rapids/issues/2219

build

I looked into the explain issue some more and setting spark.sql.ui.explainMode to extended causes Spark to just call toString on the plan which was the original behavior and this does correctly show the new operator. Setting to formatted (the default) does not.
Note that even though this is a UI setting, it actually has to be set before running the query because it affects the data that actually gets recorded in the event log.

Test failed due to Temporary failure in name resolution: Unknown host with an internal host. Will retry.

build


Get github pages working

@seabbs -- I see you have the github action to build and deploy, but I'm hitting a 404 here.
I'm not totally sure where the issue is -- seems like you have the index and whatnot in the build action?

Just debugging the actions now (see the actions tab for the failed builds). Two exciting issues so far: 1. Can't spell README; 2. Forgot pandoc.


Fix SC2069 for shellcheck

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Fix SC2069 for shellcheck
Which issue(s) this PR fixes:
xref https://github.com/kubernetes-sigs/kwok/issues/470
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/ok-to-test


Deploy Prometheus Metrics Server Adapter to Support HPA in Cluster

Here is the repo  for Kubernetes custom metrics server. It is based on the metrics server and extension api-server. So it requires following changes if I want to support it in RKE:

Enable API aggregation layer in RKE cluster, it requires to add related parameters to API server.
Deploy the Prometheus metrics server adapter with those

As reference, GKE enable the API aggregation layer by default. With command kubectl get -n kube-system configmap extension-apiserver-authentication , you can see these configmap data has been set. It means that these authentication data can be used by extension api-server directly. Here is the document for extension api-server.
For the Prometheus metrics server, here is the repo. It will fetch metrics from prometheus and push them to k8s metrics api as custom metrics. And then HPA controller(native k8s) could use those metrics as reference to scale workloads.

Link to https://github.com/rancher/rancher/issues/19084

Blocked by https://github.com/rancher/rancher/issues/14231

@aiyengar2 As part of monitoring v2, do we deploy this adapter?

@aiyengar2 As part of monitoring v2, do we deploy this adapter?

@deniseschannon yes, it’s packaged in

@deniseschannon yes, it’s packaged in


compiler service breaks when migrating to newer python version

inmanta.env.VirtualEnv.init_env() raises an exception if the venv contains a site packages dir for an older Python version. This makes upgrading to a newer orchestrator version more difficult. We should either document clearly that the venv dir should be cleared on a major update, or we should make sure the compiler (service?) can do so.

May or may not affect agent venv as well.


Running Outline Client stopped on my Debian x64.

Describe the bug
When you normally click connect, an error began to appear asking you to exit the application and start it again. However, the problem does not disappear.
To Reproduce
I run it my Debian KDE x64 laptop. And it worked until today.
Expected behavior
I expected usual connection to my VPN
Screenshots
Outline is starting
loading web app from file:///tmp/.mount_OutliniebiJq/resources/app.asar/www/index_electron.html?appName=Outline
Could not load active tunnel:  [Error: ENOENT: no such file or directory, open '/home/ian/.config/Outline/connection_store'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/ian/.config/Outline/connection_store'
}
Checking for update
Update for version 1.9.0 is not available (latest version: 1.9.0, downgrade is disallowed).
connecting to 59f86756-132a-4971-a095-4b74371337e8...
using tun2socks to check connectivity
[EXIT - tun2socks]: Exited with code 4
connectivity check error: Error: Process terminated by non-zero exit code: 4
UDP support: false
starting routing daemon
tun2socks started
could not connect: Error (configure system proxy failure)
Error occurred in handler for 'outline-ipc-start-proxying': Error: unknown NativeError Error
    at t.toErrorCode (/tmp/.mount_OutliniebiJq/resources/app.asar/build/electron/electron/index.js:2:451500)
    at /tmp/.mount_OutliniebiJq/resources/app.asar/build/electron/electron/index.js:2:438137
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async node:electron/js2c/browser_init:189:563
[EXIT - tun2socks]: Exited with code 0
tun2socks exited with no errors
could not stop routing: Write failed
disconnected from 59f86756-132a-4971-a095-4b74371337e8

Client System (please complete the following information):

Outline Client Version [Linux 1.9.0]
Your Operating System: [Debian KDE 5.10.0-20-amd64]

Submit Feedback
Please submit feedback through the app and label it with this issue number.
Additional context
Add any other context about the problem here.

So, after several reboots problem is gone.

Rebooting is not the solution.

I also have this same problem. Have to restart my computer quite often because of it :cry:
Outline Client: Version 1.13.1 (476278)
Operating system: Debian GNU/Linux 12 (bookworm) 6.1.0-20-amd64

Sometimes I have same problem. I'll write the reasons why I have such a problem, the solution and a wish to the developers.
I'm using Ubuntu 24.10 and Outline Client: Version 1.14.0  (480310), but Debian should have same behavior.
In normal way if you already used Outline it will create connection outline-tun0 that will be enabled after boot.
$ nmcli con
NAME                UUID                                  TYPE      DEVICE
Wired connection 1  779af331-b706-3d2f-b510-aed2be49a6a5  ethernet  enp2s0
lo                  d7ec8725-7d8f-42c4-8569-42508855b7b5  loopback  lo
outline-tun0        9940e3af-4432-4168-975e-74a6fd3b1337  tun       outline-tun0

Also there is few outline services:
$ systemctl list-units | grep outline
  sys-devices-virtual-net-outline\x2dtun0.device                                           loaded active plugged   /sys/devices/virtual/net/outline-tun0
  sys-subsystem-net-devices-outline\x2dtun0.device                                         loaded active plugged   /sys/subsystem/net/devices/outline-tun0
  outline_proxy_controller.service                                                         loaded active running   Outline Proxy Routing Controller

When I need to connect other VPN (for work) sometimes I have to disconnect outline-tun0:
$ nmcli con
NAME                UUID                                  TYPE      DEVICE
Wired connection 1  779af331-b706-3d2f-b510-aed2be49a6a5  ethernet  enp2s0
lo                  d7ec8725-7d8f-42c4-8569-42508855b7b5  loopback  lo

But when I starting Outline VPN again it does not check, if I have outline-tun0 connection and I'm getting error.
[tun2socks] - checking connectivity ...
[tun2socks - EXIT]: Exited with code 0
UDP support: true
starting routing daemon
[tun2socks] - starting to route network traffic ...
[tun2socks] - started
could not connect: Error: configure system proxy failure
    at Socket.<anonymous> (/tmp/.mount_OutlinJYXcqa/resources/app.asar/output/client/electron/index.js:2:678072)
    at Object.onceWrapper (node:events:646:26)
    at Socket.emit (node:events:526:28)
    at Socket.emit (node:domain:475:12)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Readable.push (node:internal/streams/readable:228:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)
Error occurred in handler for 'outline-ipc-start-proxying': Error: configure system proxy failure
    at Socket.<anonymous> (/tmp/.mount_OutlinJYXcqa/resources/app.asar/output/client/electron/index.js:2:678072)
    at Object.onceWrapper (node:events:646:26)
    at Socket.emit (node:events:526:28)
    at Socket.emit (node:domain:475:12)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Readable.push (node:internal/streams/readable:228:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)
[tun2socks - EXIT]: Exited with code 0
[tun2socks] - exited with no errors
could not stop routing: Write failed
disconnected from 2d4c40cf-18e8-4b47-accf-bf911fe659d5

So I need to restart outline_proxy_controller (it is running, but still).
$ sudo systemctl restart outline_proxy_controller.service

Then outline-tun0 connection is back and I can connect to Outline VPN.
More useful info written in Readme:
https://github.com/Jigsaw-Code/outline-apps/blob/master/client/electron/linux_proxy_controller/README.md
To developers: please, add check if outline-tun0 connection exist and connected when users start Outline VPN client. Then people can just restart client if something went wrong.


Set up Cypress + initial tests

Add Cypress dependency
Generate automatic Cypress files
Add initial tests for accesskey, autoplay, button, and html
Update README with test information
Update .gitignore to remove Cypress videos

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

This PR adds Cypress as a testing tool (as a devDependency). It also adds a few common functions and tests for 4 of the tests (accesskey, autoplay, button, and html).
Resolves: #66
How to test these changes:

Install the new dependencies: npm i
Build the library: npm run build
Run the tests:

To open the tests in a browser: npm run cypress:open
To run the tests from the command line: npm run cypress:run

Link(s)

Cypress website
Cypress documentation

Screenshot(s)

Result of running npm run cypress:run (headless):

Result of running npm run cypress:open:

Checklist:

[x] I have thoroughly read the CONTRIBUTING guidelines.
[x] I understand my pull request will be thoroughly reviewed at high detail.
[x] I understand the work in my pull request will only be available in the next version release of Checka11y.css and not in the current version release.
[x] I confirm the work in this pull request is valid according to my findings and is not something for anything personal.
[x] I have updated the README and/or features.md where and if applicable (still put an x if you have considered this but thought there was nothing to add or modify).
[x] I have added myself to the contributors section in package.json (still put an x if you have considered this but decided not to add yourself).
[x] I have checked I have not committed any accidental files.
[x] I have tested all the main modern browsers (I.e. Chrome, Firefox, Edge, Safari - please leave this unchecked if there were any browsers listed you could not test and list them in the help section with details why you couldn't test that browser)
[x] All new and existing a11y checks still work correctly (compare your local test/index.html to the test/index.html in the master branch).

Help

No a11y check changes, so didn't test those. It would be good to check how the tests are structured.
It may be better to separate the tests in their own spec instead of all in a file. That way we could avoid merge conflicts too.
Suggestions?

I'm new to GitHub in terms of CI/CD, can we run these on every PR? 🤔

@jackdomleo7 I would need to check if it's possible. I have set up jest tests on builds using Travis in other projects (for npm releases), but what you want is to run the tests on commit, right?

@alvaromontoro Don't worry about TypeScript, it was cheeky of me 😅 Later tonight, I'll have a thorough look through this branch and will pull it locally to see exactly how it works.

Sorry, I didn't get the TypeScript reference.
I was able to add pre-git to the repo. By adding pre-git, we can have the tests as part of the commit and/or push process: if the tests fail, users will not be able to commit or push (or both, depending on the settings). My main concern about that is that it uses an old version of lodash that shows vulnerabilities when installing. I'd need to check how to fix those.

@alvaromontoro Husky might be an alternative. I've used it fairly recently with prettier (not cypress).
Or we could use a github action (this would probably be my preference) https://github.com/cypress-io/github-action
@jackdomleo7 I assume you've removed your comment on typescript as I can't see it but having tests in typescript is kind of pointless. We don't need to test the test code, only the real code 😂

I was thinking more of a pipeline step for every PR, is that something I have to do? 🤔

These are the options so far:

Leave it as it is right now. With no changes, tests will be there but devs will need to be run them manually (and they may skip it altogether).
Add a plugin to automatically run the tests on commit and prevent commits if tests fail (I have pre-git running locally, but husky may be a better option as suggested by @danspratling.)
Integrate with GitHub Actions to run the tests (I must admit I don't have any experience with GitHub Actions, but I can try to set it up.)

So... how should we move forward with this change and the PR?

I think your PR is fine as it is, However, could you add a checklist option in this file asking whether they've ran tests. Then at some future point, I will do something in the pipeline. 😊 Then this can be approved.


Refactor export GPG_TTY command to add line break (#25721)

The command to add GPG_TTY does not update the shell config correctly if the file ends in a comment.
$ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \
  else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi

I previously installed pnpm so running this changed my  .zshrc file to:
#pnpm endexport GPG_TTY=$(tty)

Why:
Closes: #25721

What's being changed (if available, include any code snippets, screenshots, or gifs):
Fixed by updating each instance of the command from:
echo 'export GPG_TTY=$(tty)'

to:
echo -e '\nexport GPG_TTY=\$(tty)'

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@AlmostEfficient Thank you for opening a PR and linking it to your issue! ✨
We appreciate the extra context, too. I'll get this triaged for review! :zap: