Dependabot security updates: "Dependabot couldn't find a pom.xml"

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
maven
Package manager version
No response
Language version
Java 17
Manifest location and content before the Dependabot update
repository root, i.e., "/pom.xml"
dependabot.yml content
https://github.com/derivo-company/neo2rdf/blob/fc6c77386d11f49a1042adadba9e5c72915a3a0f/.github/dependabot.yml
Updated dependency
No response
What you expected to see, versus what you actually saw
First, I need to say that the "Dependabot version updates" work without any issues on my repository - really helpful.  I now activated the "Dependabot security updates" for the repository and encounter errors. I hope this is the right place to post this because it is probably rather an issue of the default configuration on the platform GitHub and not an issue of the underlying dependabot code. Apparently, it searches in /home/runner/work/neo2rdf/neo2rdf for the pom.xml file. I suppose, this is the path of the action runner. The link in the text next to the green "open" button of the provided screenshot should probably point to the actual repository file, which it does not. I did not found a way to configure the "Dependabot security updates" separately from "Dependabot version updates".

Probably it is connected to the fact that the pom.xml is in the repository root directory because I tried it in another project where it is in a subedirectory and there it works perfectly fine (repository link).

Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Repository: https://github.com/derivo-company/neo2rdf
Action run: https://github.com/derivo-company/neo2rdf/actions/runs/11056534431/job/30718297282
2024-09-26T16:38:54.4292975Z Current runner version: '2.319.1'
2024-09-26T16:38:54.4317194Z ##[group]Operating System
2024-09-26T16:38:54.4317970Z Ubuntu
2024-09-26T16:38:54.4318323Z 22.04.5
2024-09-26T16:38:54.4318658Z LTS
2024-09-26T16:38:54.4319052Z ##[endgroup]
2024-09-26T16:38:54.4319450Z ##[group]Runner Image
2024-09-26T16:38:54.4319892Z Image: ubuntu-22.04
2024-09-26T16:38:54.4320374Z Version: 20240922.1.0
2024-09-26T16:38:54.4321386Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240922.1/images/ubuntu/Ubuntu2204-Readme.md
2024-09-26T16:38:54.4323071Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240922.1
2024-09-26T16:38:54.4323912Z ##[endgroup]
2024-09-26T16:38:54.4324316Z ##[group]Runner Image Provisioner
2024-09-26T16:38:54.4324885Z 2.0.384.1
2024-09-26T16:38:54.4325230Z ##[endgroup]
2024-09-26T16:38:54.4341952Z ##[group]GITHUB_TOKEN Permissions
2024-09-26T16:38:54.4343968Z Actions: read
2024-09-26T16:38:54.4344643Z Attestations: read
2024-09-26T16:38:54.4345127Z Checks: read
2024-09-26T16:38:54.4345582Z Contents: read
2024-09-26T16:38:54.4345951Z Deployments: read
2024-09-26T16:38:54.4346350Z Discussions: read
2024-09-26T16:38:54.4346790Z Issues: read
2024-09-26T16:38:54.4347173Z Metadata: read
2024-09-26T16:38:54.4347620Z Packages: read
2024-09-26T16:38:54.4348015Z Pages: read
2024-09-26T16:38:54.4348349Z PullRequests: read
2024-09-26T16:38:54.4348827Z RepositoryProjects: read
2024-09-26T16:38:54.4349299Z SecurityEvents: read
2024-09-26T16:38:54.4349711Z Statuses: read
2024-09-26T16:38:54.4350161Z ##[endgroup]
2024-09-26T16:38:54.4353429Z Secret source: None
2024-09-26T16:38:54.4354021Z Prepare workflow directory
2024-09-26T16:38:54.4990539Z Prepare all required actions
2024-09-26T16:38:54.5160796Z Getting action download info
2024-09-26T16:38:54.7293100Z Download action repository 'github/dependabot-action@main' (SHA:bf1e6fc1b2536ed5c395a864fea92c8f64a409cd)
2024-09-26T16:38:55.5072985Z Complete job name: Dependabot
2024-09-26T16:38:55.6050158Z ##[group]Run mkdir -p  ./dependabot-job-891552662-1727368724
2024-09-26T16:38:55.6051113Z mkdir -p  ./dependabot-job-891552662-1727368724
2024-09-26T16:38:55.6079247Z shell: /usr/bin/bash -e {0}
2024-09-26T16:38:55.6079809Z ##[endgroup]
2024-09-26T16:38:55.6630107Z ##[group]Run github/dependabot-action@main
2024-09-26T16:38:55.6630783Z env:
2024-09-26T16:38:55.6631190Z   DEPENDABOT_DISABLE_CLEANUP: 1
2024-09-26T16:38:55.6631884Z   DEPENDABOT_ENABLE_CONNECTIVITY_CHECK: 0
2024-09-26T16:38:55.6633006Z   GITHUB_TOKEN: ***
2024-09-26T16:38:55.6633891Z   GITHUB_DEPENDABOT_JOB_TOKEN: ***
2024-09-26T16:38:55.6634967Z   GITHUB_DEPENDABOT_CRED_TOKEN: ***
2024-09-26T16:38:55.6635513Z ##[endgroup]
2024-09-26T16:38:55.9614663Z 🤖 ~ starting update ~
2024-09-26T16:38:55.9648270Z Fetching job details
2024-09-26T16:38:56.5652550Z ##[group]Pulling updater images
2024-09-26T16:38:56.5702101Z Pulling image ghcr.io/dependabot/dependabot-updater-maven:88ed71055d13287e5485b22a89378616a95f5ef6...
2024-09-26T16:39:08.1148195Z Pulled image ghcr.io/dependabot/dependabot-updater-maven:88ed71055d13287e5485b22a89378616a95f5ef6
2024-09-26T16:39:08.1161041Z Pulling image ghcr.io/github/dependabot-update-job-proxy/dependabot-update-job-proxy:v2.0.20240919194919@sha256:a8861ab9eba169d6c8071b3e2d8d67e7a23b87a6566af87255b746e2e081bca3...
2024-09-26T16:39:09.2016465Z Pulled image ghcr.io/github/dependabot-update-job-proxy/dependabot-update-job-proxy:v2.0.20240919194919@sha256:a8861ab9eba169d6c8071b3e2d8d67e7a23b87a6566af87255b746e2e081bca3
2024-09-26T16:39:09.2018982Z ##[endgroup]
2024-09-26T16:39:09.2019645Z Starting update process
2024-09-26T16:39:09.4903791Z Created proxy container: d8623bc67a6243314a73d5e5bab09350bedb720afa80203db41c7f2367f5a2a1
2024-09-26T16:39:09.7681815Z Created container: 48e14a3d9fa03eb19235dd84c7616e7beb626bc2d9ee3f001923836999cafef8
2024-09-26T16:39:09.7917544Z   proxy | 2024/09/26 16:39:09 proxy starting, commit: cf3f47452d431f45a8cdd6282ca0c7682bafa86d
2024-09-26T16:39:09.7919241Z   proxy | 2024/09/26 16:39:09 Listening (:1080)
2024-09-26T16:39:09.9288116Z updater | Updating certificates in /etc/ssl/certs...
2024-09-26T16:39:10.6679000Z updater | rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
2024-09-26T16:39:10.6914944Z updater | 1 added, 0 removed; done.
2024-09-26T16:39:10.6916244Z Running hooks in /etc/ca-certificates/update.d...
2024-09-26T16:39:10.6930182Z updater | done.
2024-09-26T16:39:13.1717299Z updater | 2024/09/26 16:39:13 INFO <job_891552662> Starting job processing
2024-09-26T16:39:13.1777522Z 2024/09/26 16:39:13 INFO <job_891552662> Job definition: {"job":{"allowed-updates":[{"dependency-type":"direct","update-type":"all"}],"commit-message-options":{"prefix":null,"prefix-development":null,"include-scope":null},"credentials-metadata":[{"type":"git_source","host":"github.com"}],"debug":null,"dependencies":["ch.qos.logback:logback-classic","ch.qos.logback:logback-core","io.netty:netty-codec-http","org.apache.commons:commons-compress","org.apache.commons:commons-compress","org.apache.commons:commons-configuration2","org.apache.commons:commons-configuration2","org.apache.solr:solr-solrj","org.apache.zookeeper:zookeeper","org.apache.zookeeper:zookeeper","org.eclipse.jetty.http2:http2-common","org.eclipse.jetty.http2:http2-common","org.eclipse.jetty.http2:http2-hpack","org.neo4j:neo4j-cypher","org.xerial.snappy:snappy-java","org.xerial.snappy:snappy-java","org.xerial.snappy:snappy-java","org.xerial.snappy:snappy-java"],"dependency-groups":[{"name":"maven","rules":{"patterns":["*"]},"applies-to":"security-updates"}],"dependency-group-to-refresh":null,"existing-pull-requests":[],"existing-group-pull-requests":[],"experiments":{"record-ecosystem-versions":true,"record-update-job-unknown-error":true,"proxy-cached":true,"move-job-token":true,"dependency-change-validation":true,"add-deprecation-warn-to-pr-message":true,"enable-pnpm-yarn-dynamic-engine":true},"ignore-conditions":[],"lockfile-only":false,"max-updater-run-time":2700,"package-manager":"maven","proxy-log-response-body-on-auth-failure":true,"requirements-update-strategy":null,"reject-external-code":false,"security-advisories":[{"dependency-name":"ch.qos.logback:logback-classic","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,1.2.0)"]},{"dependency-name":"ch.qos.logback:logback-classic","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,1.2.13)","[1.3.0,1.3.12)","[1.4.0,1.4.12)"]},{"dependency-name":"ch.qos.logback:logback-core","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,1.2.0)"]},{"dependency-name":"ch.qos.logback:logback-core","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,1.2.9)"]},{"dependency-name":"ch.qos.logback:logback-core","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,1.2.13)","[1.3.0,1.3.12)","[1.4.0,1.4.12)"]},{"dependency-name":"ch.qos.logback:logback-core","patched-versions":[],"unaffected-versions":[],"affected-versions":["1.2.12","1.3.13","1.4.13"]},{"dependency-name":"io.netty:netty-codec-http","patched-versions":[],"unaffected-versions":[],"affected-versions":["[4.0.0,4.1.59.Final)"]},{"dependency-name":"io.netty:netty-codec-http","patched-versions":[],"unaffected-versions":[],"affected-versions":["[4.0.0,4.1.71.Final)"]},{"dependency-name":"io.netty:netty-codec-http","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,4.1.76.Final]"]},{"dependency-name":"io.netty:netty-codec-http","patched-versions":[],"unaffected-versions":[],"affected-versions":["[4.1.83.Final,4.1.86.Final)"]},{"dependency-name":"io.netty:netty-codec-http","patched-versions":[],"unaffected-versions":[],"affected-versions":["[4.0.0,4.1.44)"]},{"dependency-name":"io.netty:netty-codec-http","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,4.1.108.Final)"]},{"dependency-name":"org.apache.commons:commons-compress","patched-versions":[],"unaffected-versions":[],"affected-versions":["[1.7,1.18)"]},{"dependency-name":"org.apache.commons:commons-compress","patched-versions":[],"unaffected-versions":[],"affected-versions":["[1.11,1.16)"]},{"dependency-name":"org.apache.commons:commons-compress","patched-versions":[],"unaffected-versions":[],"affected-versions":["[1.15,1.19)"]},{"dependency-name":"org.apache.commons:commons-compress","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,1.21)"]},{"dependency-name":"org.apache.commons:commons-compress","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,1.4.1)"]},{"dependency-name":"org.apache.commons:commons-compress","patched-versions":[],"unaffected-versions":[],"affected-versions":["[1.22,1.24.0)"]},{"dependency-name":"org.apache.commons:commons-compress","patched-versions":[],"unaffected-versions":[],"affected-versions":["[1.21,1.26.0)"]},{"dependency-name":"org.apache.commons:commons-compress","patched-versions":[],"unaffected-versions":[],"affected-versions":["[1.3,1.26.0)"]},{"dependency-name":"org.apache.commons:commons-configuration2","patched-versions":[],"unaffected-versions":[],"affected-versions":["[2.2,2.7)"]},{"dependency-name":"org.apache.commons:commons-configuration2","patched-versions":[],"unaffected-versions":[],"affected-versions":["[2.4,2.8.0)"]},{"dependency-name":"org.apache.commons:commons-configuration2","patched-versions":[],"unaffected-versions":[],"affected-versions":["[2.0,2.10.1)"]},{"dependency-name":"org.apache.solr:solr-solrj","patched-versions":[],"unaffected-versions":[],"affected-versions":["[6.0.0,8.11.3)","[9.0.0,9.4.1)"]},{"dependency-name":"org.apache.zookeeper:zookeeper","patched-versions":[],"unaffected-versions":[],"affected-versions":["[3.5.0,3.5.5)","[1.0.0,3.4.14)"]},{"dependency-name":"org.apache.zookeeper:zookeeper","patched-versions":[],"unaffected-versions":[],"affected-versions":["[3.5.0-alpha,3.5.3-beta]","(,3.4.9]"]},{"dependency-name":"org.apache.zookeeper:zookeeper","patched-versions":[],"unaffected-versions":[],"affected-versions":["[3.5.0,3.5.2]","[3.4.0,3.4.9]"]},{"dependency-name":"org.apache.zookeeper:zookeeper","patched-versions":[],"unaffected-versions":[],"affected-versions":["[3.9.0,3.9.1)","[3.8.0,3.8.3)","(,3.7.2)"]},{"dependency-name":"org.apache.zookeeper:zookeeper","patched-versions":[],"unaffected-versions":[],"affected-versions":["[3.6.0,3.7.2]","[3.9.0,3.9.1]","[3.8.0,3.8.3]"]},{"dependency-name":"org.eclipse.jetty.http2:http2-common","patched-versions":[],"unaffected-versions":[],"affected-versions":["[11.0.0,11.0.19]","[10.0.0,10.0.19]","[9.3.0,9.4.53]"]},{"dependency-name":"org.eclipse.jetty.http2:http2-common","patched-versions":[],"unaffected-versions":[],"affected-versions":["[11.0.0,11.0.17)","[10.0.0,10.0.17)","[9.3.0,9.4.53)"]},{"dependency-name":"org.eclipse.jetty.http2:http2-hpack","patched-versions":[],"unaffected-versions":[],"affected-versions":["[9.3.0,9.4.52]","[11.0.0,11.0.15]","[10.0.0,10.0.15]"]},{"dependency-name":"org.neo4j:neo4j-cypher","patched-versions":[],"unaffected-versions":[],"affected-versions":["[5.0.0,5.19.0)"]},{"dependency-name":"org.xerial.snappy:snappy-java","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,<IP_ADDRESS>]"]},{"dependency-name":"org.xerial.snappy:snappy-java","patched-versions":[],"unaffected-versions":[],"affected-versions":["(,<IP_ADDRESS>]"]}],"security-updates-only":true,"source":{"provider":"github","repo":"derivo-company/neo2rdf","branch":null,"api-endpoint":"https://api.github.com/","hostname":"github.com","directories":["/home/runner/work/neo2rdf/neo2rdf"]},"updating-a-pull-request":false,"update-subdependencies":false,"vendor-dependencies":false,"repo-private":false}}
2024-09-26T16:39:13.5343559Z   proxy | 2024/09/26 16:39:13 [002] GET https://github.com:443/derivo-company/neo2rdf/info/refs?service=git-upload-pack
2024-09-26T16:39:13.5345721Z 2024/09/26 16:39:13 [002] * authenticating git server request (host: github.com)
2024-09-26T16:39:13.7219192Z   proxy | 2024/09/26 16:39:13 [002] 200 https://github.com:443/derivo-company/neo2rdf/info/refs?service=git-upload-pack
2024-09-26T16:39:13.7542399Z   proxy | 2024/09/26 16:39:13 [004] POST https://github.com:443/derivo-company/neo2rdf/git-upload-pack
2024-09-26T16:39:13.7544255Z 2024/09/26 16:39:13 [004] * authenticating git server request (host: github.com)
2024-09-26T16:39:13.8837141Z   proxy | 2024/09/26 16:39:13 [004] 200 https://github.com:443/derivo-company/neo2rdf/git-upload-pack
2024-09-26T16:39:13.9177360Z   proxy | 2024/09/26 16:39:13 [006] POST https://github.com:443/derivo-company/neo2rdf/git-upload-pack
2024-09-26T16:39:13.9178636Z 2024/09/26 16:39:13 [006] * authenticating git server request (host: github.com)
2024-09-26T16:39:14.0748320Z   proxy | 2024/09/26 16:39:14 [006] 200 https://github.com:443/derivo-company/neo2rdf/git-upload-pack
2024-09-26T16:39:14.3243347Z updater | 2024/09/26 16:39:14 ERROR <job_891552662> Error during file fetching; aborting: /home/runner/work/neo2rdf/neo2rdf/pom.xml not found
2024-09-26T16:39:14.6279547Z   proxy | 2024/09/26 16:39:14 [008] POST /update_jobs/891552662/record_update_job_error
2024-09-26T16:39:14.8757949Z   proxy | 2024/09/26 16:39:14 [008] 204 /update_jobs/891552662/record_update_job_error
2024-09-26T16:39:14.9239812Z   proxy | 2024/09/26 16:39:14 [010] PATCH /update_jobs/891552662/mark_as_processed
2024-09-26T16:39:15.0661685Z   proxy | 2024/09/26 16:39:15 [010] 204 /update_jobs/891552662/mark_as_processed
2024-09-26T16:39:15.0684416Z updater | 2024/09/26 16:39:15 INFO <job_891552662> Finished job processing
2024-09-26T16:39:15.0705083Z updater | 2024/09/26 16:39:15 INFO Results:
2024-09-26T16:39:15.0709832Z Dependabot encountered '1' error(s) during execution, please check the logs for more details.
2024-09-26T16:39:15.0711076Z +---------------------------+
2024-09-26T16:39:15.0711837Z |          Errors           |
2024-09-26T16:39:15.0712968Z +---------------------------+
2024-09-26T16:39:15.0715364Z | dependency_file_not_found |
2024-09-26T16:39:15.0716909Z +---------------------------+
2024-09-26T16:39:15.1857431Z Failure running container 48e14a3d9fa03eb19235dd84c7616e7beb626bc2d9ee3f001923836999cafef8
2024-09-26T16:39:15.2039973Z Cleaned up container 48e14a3d9fa03eb19235dd84c7616e7beb626bc2d9ee3f001923836999cafef8
2024-09-26T16:39:15.2136328Z   proxy | 2024/09/26 16:39:15 Posting metrics to remote API endpoint
2024-09-26T16:39:15.2138860Z   proxy | 2024/09/26 16:39:15 0/5 calls cached (0%)
2024-09-26T16:39:15.9441589Z ##[error]Dependabot encountered an error performing the update

Error: The updater encountered one or more errors.

For more information see: https://github.com/derivo-company/neo2rdf/network/updates/891552662 (write access to the repository is required to view the log)
2024-09-26T16:39:15.9450996Z 🤖 ~ finished: error reported to Dependabot ~
2024-09-26T16:39:15.9534324Z Post job cleanup.
2024-09-26T16:39:16.0902815Z Cleaning up orphan processes

Smallest manifest that reproduces the issue
No response

I created a separate repository with a pom.xml file in the root directory in order to try to reproduce the error, but the dependabot security updates apparently work (link):

I compared the job configuration of

a successful "Dependabot version update" job in the neo2rdf repository
the errorneous "Dependabot security update" job neo2rdf
the minimum working Java Maven project repository with pom.xml file in root directory

This is probably the relevant difference:
Excerpt of security update job config (job not successful, autoconfigured by GitHub)
"source": {
    "provider": "github",
    "repo": "derivo-company/neo2rdf",
    "branch": null,
    "api-endpoint": "https://api.github.com/",
    "hostname": "github.com",
    "directories": [
        "/home/runner/work/neo2rdf/neo2rdf"
    ]
}

Excerpt of version update job (job successful, manually configured in .github/dependabot.yml)
"source": {
    "provider": "github",
    "repo": "derivo-company/neo2rdf",
    "branch": null,
    "directory": "/.",
    "api-endpoint": "https://api.github.com/",
    "hostname": "github.com"
}

Security update of minimum working Java Maven project repository (job successful, autoconfigured by GitHub)
"source": {
    "provider": "github",
    "repo": "MaximilianWenzel/java-security-update-root",
    "branch": null,
    "api-endpoint": "https://api.github.com/",
    "hostname": "github.com",
    "directories": [
        "/"
    ]
}

Apparently, somehow the auto configuration in the "neo2rdf" repository went wrong.

I'm encountering the same issue in one of my repositories. It seems like the root directory isn't being properly set up, but I haven't been able to find a way to fix it.

Thanks! It already helps to know that others encounter this issue as well sometimes.


TypeError: Incorrect value for stdio stream: inherit

Hi,
I followed the README, and cloned the demo app.
However, when I run 'lab install', I run into the following error - everytime.
#> Starting service devlab_mongodb_puretech_1446502746915
!> Failed to start devlab_mongodb_puretech_1446502746915
!> TypeError: Incorrect value for stdio stream: inherit
!> Error running  npm run test;, exited with code 1
#> Stoping service: devlab_mongodb_puretech_1446502746915
Can you please help with this issue. I am running this on Koding.com

What version of Node are you running?

I ran node version 5 (latest) from docker

I'm not really sure, the only issue I can find (and replicate) is spawn on older versions of Node. I'm assuming you checked with node -v to ensure you're running 0.12?

@Subby4Git I believe @Fluidbyte meant your local node version (responsible for running DevLab), not the container version in the devlab.yml file.

Oh, thanks for the clarification @TomFrost! I had misunderstood it for the devlab container version.
I will look into it and let you know of the result.

Closing. Docs in the README on preventing this error.


Weather icons

Hi James, please accept my apologies for creating an issue when I guess that's not really what this is, I just don't have Twitter so couldn't contact you any other way.
I've created my own custom icon set, numbered as per the Yahoo condition codes, and wondered if you were interested in linking to them via your site. I know you already point people at icon sets but so far as I can tell mine would be the only one that's complete, insofar as Yahoo's codes are concerned at least. I have a white versions and the same set coloured.
If you're interested let me know and I'll provide a URL. In any case, thank you very much for an awesome plugin.

Thanks for checking out simpleWeather! I would love to check out the icons and possibly link to them. Let me know the url.

Hi James,
Here's a tinyURL to a zip file containing coloured and white icons, plus a preview image of the coloured set: http://tinyurl.com/p4shbyr
Fraser.

Thanks for this. However, I'm not comfortable just linking to a third party zip file. Ideally if you could put a post up about them, showing the preview image (even a github repo of them), I could link to it vs directly to a download. Once you get them up somewhere let me know the new url.
Also, a quick suggestion would be to also make these into an icon font as well as the png files. This way people could use either (I prefer icon fonts personally). IcoMoon has a great app to generate fonts from uploading icons if needed.

Hi James, apologies for sending a link directly to a zip, that was a bit of a school boy error. I have now created a repository and committed them all to that: https://github.com/theberengersniper/weather-icons
I plan to update the sets over the next few weeks by adding additional sizes and, as you suggested, an icon font version.

Awesome, I'll get a link added to it soon. We are currently working on a redesign of the site to better organize extra data like this so it might be a little bit. I'll reopen this ticket as a reminder. Thanks again.


can anticheats detect this as something bannable?

Was thinking on using it to add DLAA to tarkov instead of just dlss, but I don't know if will be detected as a cheat by anticheat software from multiplayer games
any idea?

There's a chance it might be detected, this doesn't modify the game code itself but does hook into DLSS using same methods as some game cheats, can't really get around that unfortunately.
If tarkov lets you use DLSS 3.1.11+ you could force DLAA through global NV profile instead, wouldn't need any kind of code hooks for that, the DLSSTweaksConfig.exe tool can let you change that at the bottom of the list.


Add typings for timezonecomplete 1.13.0

@rogierschouten thank you your contributions.
please remove timezonecomplete/timezonecomplete-1.12.0.d.ts and tests.
this repository maintain newest versions only.

Thanks for the comment, I thought it was policy to support older versions. I was confused by this section in the contribution guide, perhaps it can be clarified:
Version

In case there are multiple versions supported, the latest one will be without a version number in the file name. Older versions will be in the form of library-1.2.0.d.ts where the postfix should resemble a valid semantic version number (semver).

@rogierschouten woo! sorry. timezonecomplete.d.ts has some older version already.
but it is not duty.
e.g. node.d.ts is for stable version(v0.10, v0.12) and node-0.11.d.ts is for experimental version.
this PR's change is not include breaking changes. I think timezonecomplete do not need keep older versions. thanks!


LLM-provider agnostic client

Is your feature request related to a problem? Please describe.
In my development work, I've found it tedious when working with multiple providers having to initiate a client for each provider and patch them separately, while keep track of one object for each provider throughout my app.
This felt very redundant to me because those clients are all stateless apart from an api key. This is of course not an issue with the instructor lib itself, but imo it is a good place for instructor to come in play as it is already somewhat working towards (whether intentionally or not) having a provider-agnostic interface.
Describe the solution you'd like
A generic LLM client patched with instructor that invokes different client depending on the model name supplied during a call. This also allows extensions into other things like token usage tracking. I have a working solution for this that I'd be happy to contribute but wanted to check if this is of interest/considered by the team, or deemed unnecessary/out of scope.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

i recommend https://docs.litellm.ai/docs/


⚠ SceneTime has degraded performance

In c824fc8, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 21941 ms

Resolved: SceneTime performance has improved in 40ee4a9 after 5 minutes.


ecsspert.com: use final url

Updating the URL for eCSSpert.com so it matches the final URL. This should give it a more accurate page index score.
Also, I'm updating the previous weeks, so that you can show how the site's ranking changed over time. Let me know if this is not needed and I'll revert it.

Thank you!


bazel: Add custom rule to produce android debug info

When building the jni dylib for android, we previously stripped all
debug info to decrease the artifact size. With this change we now
produce the same stripped binary as before, but before stripping it we
create a dump of the debug info suitable for crash reporting.
This is made overly difficult for a few reasons:

Bazel doesn't support fission for Android https://github.com/bazelbuild/bazel/pull/14765
Extra outputs from rules are not propagated up the dependency tree,
so just building android_dist at the top level, isn't enough to get
the extra outputs built as well
Building the library manually alongside the android artifact on the
command line results in 2 separate builds, one for android as a
transitive dependency of android_dist and one for the host
platform

This change avoids #1 fission for now, but the same approach could be used
once that change makes its way to a bazel release.
This change ignores #2 but fixes #3 so it requires you to explicitly
build the library as part of the command line invocation if you want
debug info, like:
./bazelw build --fat_apk_cpu=... android_dist //library/common/jni:libenvoy_jni.so.debug_info

Theoretically we could probably shove this artifact into the aar to make
sure it was correctly produced, but that risks us accidentally shipping
that in the aar.
Signed-off-by: Keith Smiley<EMAIL_ADDRESS>

I'm thinking I can do something to avoid having to pass the extra target, looking at that now


Register globally to use within script tags

Hi,
I noticed issue #28 - I was wondering if this is possible to register anything globally though.
So instead of having to import trans each time (with import { trans } from "laravel-vue-i18n"), just use trans or $t or whatever immediately within the script tags like the following:
<script setup>
const someTranslation = $t('global.something'); // like in <template>
// or
const someTranslation = trans('global.something');
</script>

Hey @robinvoor you can make it available globally by using:
import { trans } from "laravel-vue-i18n"

window.trans = trans;

No plans to add that to the plugin.
Thanks,
Francisco


QP create issues on asymetrically reported QP sizes

Hi,
Some of the sample applications seem to assume that the reported RQ size is always greater or equal than SQ size. This is not required. The call to create QP uses the same value for RQ and SQ.
Coming from min(maxCQ, maxRQ), which may fail if SQ turned out to be reported in adapter info as smaller than maxCQ and maxRQ.
Please find below a potential fix for ndping.
Thanks.
Fix to asymetrically reported QP sizes

  This patch incorporates the Initiator queue depth reported through
  AdapterInfo.

  When reported sizes for SQ are smaller than RQ, createQP uses
  min(CQDepth,RQDepth) for both SQ and RQ causing QP creation errors.

diff --git a/src/examples/ndping/ndping.cpp b/src/examples/ndping/ndping.cpp
index 8a08a12..deac1fb 100644
--- a/src/examples/ndping/ndping.cpp
+++ b/src/examples/ndping/ndping.cpp
@@ -62,7 +62,8 @@ public:

       ND2_ADAPTER_INFO adapterInfo = { 0 };
       NdTestBase::GetAdapterInfo(&adapterInfo);
-        m_queueDepth = min(adapterInfo.MaxCompletionQueueDepth, adapterInfo.MaxReceiveQueueDepth);
+        m_queueDepth = min(adapterInfo.MaxReceiveQueueDepth, adapterInfo.MaxInitiatorQueueDepth);
+        m_queueDepth = min(m_queueDepth, adapterInfo.MaxCompletionQueueDepth);
       m_queueDepth = (queueDepth != 0) ? min(queueDepth, m_queueDepth) : m_queueDepth;
       m_inlineSizeThreshold = adapterInfo.InlineRequestThreshold;

@@ -195,7 +196,8 @@ public:

       ND2_ADAPTER_INFO adapterInfo;
       NdTestBase::GetAdapterInfo(&adapterInfo);
-        m_queueDepth = min(adapterInfo.MaxCompletionQueueDepth, adapterInfo.MaxInitiatorQueueDepth);
+        m_queueDepth = min(adapterInfo.MaxReceiveQueueDepth, adapterInfo.MaxInitiatorQueueDepth);
+        m_queueDepth = min(m_queueDepth, adapterInfo.MaxCompletionQueueDepth);
       m_queueDepth = (queueDepth != 0) ? min(queueDepth, m_queueDepth) : m_queueDepth;
       m_inlineSizeThreshold = adapterInfo.InlineRequestThreshold;

Thanks for reporting this, @idbar . Do you mind submitting a PR with this?

Sure, @jithinjosepkl. Let me prepare a more complete patch and I'll submit it as soon as I have it. Thanks.

This issue is fixed in my fork:
https://github.com/MrDavid949/NetworkDirect


Multisheet render

Hi All,
Could someone help me how to render excel file with multiple sheets? Cant find any information regarding this.
Thanks

@romapavliuk  why is this closed ? did you find the anwser ?


Fix sizeof channel negotiation task

Noticed while running a client program that invoked aws_channel_setup_client_tls and subsequently had heap corruption errors. When running with ENABLE_SANITIZERS=ON, it produced a report that the negotiation_task was only being allocated with 64 bytes where as aws_channel_task_init called AWS_ZERO_STRUCT where it was trying to set 104 bytes to 0, thus over-running the original memory region.

Released in https://github.com/awslabs/aws-c-io/releases/tag/v0.14.6.


sparse float vector index to support mmap when loading from index file

issue: https://github.com/milvus-io/milvus/issues/29419
/kind: improvement

/lgtm


caption text at training

Hi
I am using music_audioset_epoch_15_esc_90.14.pt as a music classifier. I would like to classify the mood and genre of our music files. I am trying to find the cosine similarity using the text "The mood of this song is (romantic, energetic, etc)" but I only get about 0.4. I think that if I use a text similar to the one you used in your training, the value will be better, so could you please tell me what type of text you used?

Hi, for music we used This audio is a <genre> song. I think the task you are dealing with is also a bit of out of distribution of the training data. I don't think we included a lot of music with mood labels in music version of the CLAP.
Best,

Thanks for the reply. I will try it with your text.


[NEW ALGORITHM] Push-Relabel

Name:
Push-Relabel Algorithm
About:
The Push-Relabel Algorithm is an efficient method for computing the maximum flow in flow networks. It operates by maintaining a preflow and repeatedly pushing excess flow from vertices to their neighbors while adjusting vertex heights to facilitate further pushes. This algorithm excels in handling dense graphs and provides improved performance over traditional methods, making it suitable for a wide range of network optimization problems.

Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[x] Contributor in GSSoC-ext
[x] Contributor in hacktoberfest
[x] Want to work on it

@pankaj-bind please assign to me, i'll do it asap!

@sandeepmaddheshiya you are assigned


VRAM usage and mesh generation

Hi, thanks for developing a fascinating algorithm!
I have just attempted running it on an Nvidia RTX 4070 with 12 GB VRAM, and get a CUDA out of memory error when running bash script/fit_people_30s.sh (it attempts to allocate ~13GB). I now wonder if there are any simple ways of reducing the VRAM usage during the fitting of the model — for example, which parameters in profiles/people/people_30s.yaml have the largest effect on memory?
Additionally, what would be the preferred way of generating a textured mesh from the learned avatar?
Thanks,
Filip

Similar question about generating meshes

Same question about generating the 3DGS?


Extension causes high cpu load

Issue Type: Performance
Extension Name: vscode-pylance
Extension Version: 2024.8.1
OS Version: Windows_NT x64 10.0.19045
VS Code version: 1.91.1

:warning: Make sure to attach this file from your home-directory:
:warning:file:///c%3A/Users/Barou/AppData/Local/Temp/ms-python.vscode-pylance-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

@Yahya78h  thanks for the issue. Can you attach the mentioned file? Otherwise this is unactionable for us.

please see https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue
if you have a public repo or code sample that would really help.
closing for now.


Feat/upsert (WIP)

New upsert feature.
Will clean exported code.

Codecov Report

Merging #3 (ecefcdb) into master (50c8d98) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #3   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         8    +1
  Lines          183       263   +80
=========================================
+ Hits           183       263   +80

Impacted Files
Coverage Δ

bob.go
100.00% <100.00%> (ø)

upsert.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


provide pca9685 sensor driver and document

Signed-off-by: wusheng.tws<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Security Check : f93ef105286e3d3989b9df4d3fb74edb44025dfe

auto build success,number:45

autotest success,number:1082


update token expiration configs

change advertising token expiration from 1 day to 7 days

Decision to change token expiration has been put off
https://atlassian.thetradedesk.com/jira/browse/UID2-1313


[FEATURE] - Make settings lockable / password protected

Hello,
Is your feature request related to a problem? Please describe.
I'm looking for a simple solution for my kids' smartphones to force them to a wireguard VPN. I have setup a own WiFi, VLAN and VPN for my kids, so all the traffic is routed through my proxy server / ad-blocker at home. Unfortunately no app allows to effectively block changes in their configuration or simply turn it off at any time.
Describe the solution you'd like
Allow to set a password for switching the VPN on or off AND for changing the configuration. Important note here, we cannot rely on the Android password/biometrics feature as this is bound to the kids for unlocking their phones. So it needs to be independent.
Describe alternatives you've considered
I've already looked into other alternatives, e.g. AppLocker and similar tools, but these can either be circumvented somehow or include a lot of trackers / ads.
Best regards.

Hello! I think this is a really good idea and it would be pretty easy to implement. I look into it.!

Yes, we would really love this feature as well.
Thanks!


Experimental module docs [wip]

docs for experimental module/descriptor

ready (enough) for review @manzt  ... lemme know if you think this is a reasonable direction

Oh wow, awesome <3 Can't wait to have a read. Also I've found the _repr_mimbundle_ documentation is very poor elsewhere, so it's really nice to have some concrete explanation of what that is in this as well :)


Broken link from traceback to code line

Example submission: 9255483

Here's another submission where the link no longer works: https://dodona.ugent.be/nl/submissions/13723111/

@niknetniko This issue now seems resolved.

@niknetniko This issue now seems resolved.

Yep, in the end this was a Dodona issue, so no action was needed in TESTed.


Random Quote is not working

Describe the bug
Random quote failed to render.
Expected behavior
A random quote at every refresh.

fixed now


Refactoring

Refactor, fixing listview, removing old resources that are unused, removing metroframework.design/font references, moving files to Shotr.Core, cleanup, etc.

fixes #8

fixes #8


How to resolve Could not lock exclusive.lock

When writing test, test suite is used to simplify testing code. Here's the architecture of test.
func New() *App {
...
	homePath := cast.ToString(appOpts.Get(flags.FlagHome))
	wasmDir := filepath.Join(homePath, "wasm")
	wasmer, err := wasmvm.NewVM(
		filepath.Join(wasmDir, "wasm"),
		availableCapabilities,
		32, // wasmkeeper.contractMemoryLimit,
		wasmConfig.ContractDebugMode,
		wasmConfig.MemoryCacheSize,
	)
	if err != nil {
		panic(err)
	}
...
}

func Setup()  *App {
...
	app := New(
		log.NewNopLogger(),
		db,
		nil,
		true,
		appOptions,
		wasmOpts,
	)
...
}

type KeeperTestSuite struct {
	suite.Suite

	ctx sdk.Context

	app *app.App
}

func (suite *KeeperTestSuite) SetupTest() {
	suite.app = app.Setup(suite.T(), false)
	suite.ctx = suite.app.BaseApp.NewContext(false)
}

func (suite *KeeperTestSuite) Test1() {
...
}

func (suite *KeeperTestSuite) Test2() {
...
}

When Test1 and Test2 are run individually, it works fine, but when they are run both, it is returning following issue.
test panicked: Could not lock exclusive.lock. Is a different VM running in the same directory already?
            goroutine 315 [running]:

Would be nice to get recommendation for the best way to fix the issue in test suite.

This is a newly added safety check implemented in wasmvm 2. The idea is that no two wasmvm.VM instances should run on the same directory at the same time. When you write tests that run in parallel, you need to use a different directory for each test. So more or less create a temp dir here for each test:
wasmDir := filepath.Join(homePath, "wasm")

Thanks for your input, closing the issue.


Restructure multithreading

Redefine the Worker trait, which allows the chosen worker to create a
new scope. This is relevant for a newly created (and installed) rayon
worker.
The rayon thread pool is now local to the decoding step. This fixes an
issue where improper task scheduling would deadlock decoding. It's not
clear how the intended task scheduling can be reliably achieved without
the guarantee of having at least a second, free, worker thread.
Closes: #227

Added more tests, no based off the global pool, to demonstrate/test that this does not make a quantifiable difference. As suggested to add them here. @awused Did I miss any, do you have more suggestions? You can easily verify that all of the tests hang with the previous implementation.

Okay, scratch that. This is why it was a draft. How about this: In this rayon case, we always in_place_scope the main decoder loop. (The architecture should already be there after the rework). Then, instead of creating workers, in append_row we run the Immediate worker as a new scoped task—this is still single threaded, non-blocking, but I'll get to it. Both start and get_result will run directly on the immediate worker without any of dubious communication structure of the multithreaded module.
Now the critical part: We modify Worker::append_row such that multiple rows can be spawned at the same time. The rayon implementation can then create multiple tasks in its scope, which lets other threads worksteal from us. Not sure about the runtime implications of this scheme. However, this way making the rayon worker  entirely non-blocking might be easier than imagined.

I've given rayon usage a complete overhaul. No more blocking at all but Mutex to modify the shared result sets.


Movie length songs

Describe your bug here.
when I tried to import the Shrek movie audio file into this engine, the game does  something very bizarre that is hard to explain.
Basically I get put into a soft locked state with the chart refusing to read.
I've tried to do the same in other engines but I keep getting the same error.
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No, I am using a build from game banana

and that it's named Inst and the voices being simply Voices

nope song length has be to 22 min and 30 secs on each part

pretty sure this isn't a psych engine limitation but rather a haxe one

i mean... why would you try to run the Shrek movie in Psych Engine...

i mean... why would you try to run the Shrek movie in Psych Engine...

Because why not! I want the world record for the longest single fnf song in the game. I know a shrek mod already exists but I want it in one song, not split into 5 different songs

bro answered 3 months later


doc: change install methods, remove install from repository

indicate git clone intended for developers

It now has conflict with the master version from another PR. Would you like to rebase/merge first?
done. Looks good now and content is correct. thanks for working on the clone repository option.


Remove MGMT_IFNAME since it is autodetermined by node anotations in OVN-K

/cc @bn222

Requires  https://github.com/openshift/ovn-kubernetes/pull/1697  to be merged.
/hold

/unhold

https://github.com/openshift/ovn-kubernetes/pull/1697#issuecomment-1591526835 is now merged.
@bn222 PTAL

/lgtm


Remove references to nightly images

Still using nightly in quite a few places: https://github.com/Azure/azure-functions-docker/search?l=Dockerfile&q=nightly

Still using nightly in quite a few places: https://github.com/Azure/azure-functions-docker/search?l=Dockerfile&q=nightly

@CooperLink FYI. Are all of these the old/obsolete files?

Powershell 7 v4 is the only blessed production image that references 'nightly'.  For now I will introduce a PR to remove all references to nightly and test the images.  Should be fine to just move them all over to GA dotnet6.
To be clear, non-appservice images are not necessarily old/obsolete.  They do have purposes.  They are just not used in production Linux Dedicated Applications for Azure Functions.

Merged resolution to this issue. Thank you for filing @anthonychu


postgresql: some improvements to the derivation

Description of changes
This fell out of my work on "building with meson / in pkgsStatic", which I have recently been progressing well with. Still nothing to show, yet, though.
@Ma27 let me know what you think!
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Sure, will do so tomorrow.

Oh but there is a merge conflict.

Could you please verify that on the rebased branch everything works at least on your platform? ofborg's logs are not green and it is not clear to me why.

Imho, ofborg had been failing before, too. I did verify the changes on master only, so far. I don't expect any change after the kind of conflicts I fixed.
I will kick off another build on staging though. Might take a while ;)

Oh I see, I haven't noticed we are targeting staging, so there is no need for that. In fact, I think this PR is mature enough to be further cooked in staging :).

Aish I would have merged this right now if you hadn't forced pushed. Let's merge this after evaluation is green.


Add document for all auto conversion in generator

We have a lot of InputXXXTransformer under \src\AutoRest.CSharp\Common\Input\InputTypes\Transformation to do some modification for the input. We need some document to illustrate them.

See related issue with more context here: https://github.com/Azure/autorest.csharp/issues/5190


Pictures zoom on the Value panel doesn't work on macOS and Linux

Description
I tried to zoom in / zoom out pictures on the Value panel using mouse (and shortcuts CMD + + и CMD + - as well). The same situation is on Linux.
Seems like we have a bug, and for now this feature works only on Windows.
DBeaver Version
Ultimate Edition 22.3.0
Operating System
No response
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

This seems to be the same case as #19204


Improve errors

Right now, we're building the errors manually in many places, which is error-prone and leads to a lot of duplicated code.
It would be great to add methods to deal with error creation, such as:
const { organizationInvitationsOrgNotFound } = require('../error');
throw organizationInvitationsOrgNotFound(invitation.organizationId);

which internally, it would be something like:
class HubError extends Error {
  static organizationInvitationsOrgNotFound(orgId) {
    return new HubError({
      ...
    });
  }
}

Due to the fact that we are implementing Studio from "scratch", I am closing this issue.


Update language-packs.md

Updated to make the 21H1 or 21H2 inbox apps link

@eltimmck : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off


Documentation for bus route booking site

Title and Issue number
Re-structured readme file

Close #3033

Checklist:

[✅] I have mentioned the issue number in my Pull Request.
[✅] I have commented my code, particularly in hard-to-understand areas
[✅] I have created a helpful and easy to understand README.md

@MohitGupta121 Kindly,review this.


Use last WorkflowTaskFailed event for strongly typed error

Description & motivation 💭
If there are multiple WorkflowTaskFailed events in eventHistory.end then the first one was being set as the workflowTaskFailedEvent in getWorkflowStartedCompletedAndTaskFailedEvents since end has events in descending order. This change ensures that the last WorkflowTaskFailed is set as the workflowTaskFailedEvent and passed to the WorkflowTypedError component.
Screenshots (if applicable) 📸
Design Considerations 🎨
Testing 🧪
How was this tested 👻

[x] Manual testing
[ ] E2E tests added
[ ] Unit tests added

Steps for others to test: 🚶🏽♂🚶🏽♀
Checklists
Draft Checklist
Merge Checklist
Issue(s) closed
Docs
Any docs updates needed?

Let's add a unit test to get-started-completed-and-task-failed-events.test.ts to cover this case.


Return a non-zero exit code on failure

Right now if a command fails, it returns an exit code 0, which should mean the program ran successfully.
This PR causes failures to return 1.

Thank you! <3


Version Conflict with Xamarin.Android.Support.Compat

In the last version (v2.4.1) I keep facing the error below. It doesn't happen in the previous version (v2.3.2). Because of this, I'm unable to update it to the last one.
Version conflict detected for Xamarin.Android.Support.Compat. Reference the package directly from the project to resolve this issue.
 {Project NameSpace} -> Xamarin.Android.Support.Design 27.0.2 -> Xamarin.Android.Support.Compat (= 27.0.2)
 {Project NameSpace} -> ZXing.Net.Mobile 2.4.1 -> Xamarin.Android.Support.v4 <IP_ADDRESS> -> Xamarin.Android.Support.Compat (= <IP_ADDRESS>).

In the dependencies it's noted that it needs Xamarin.Android.Support.v4 (>= <IP_ADDRESS>) but I don't know why it only works with the exact version and not newer.

I solved it by below method but I am afraid it is correct method.
But anyway I am running it by below method.

NUGET Package Manager --> installed Tab --> Xamarin.Android.Support.Design
--> change Version
v27.0.2 --> v<IP_ADDRESS>
then you can normally install ZXing.Net.Mobile 2.4.1
Finally you have to Set Target Compile Version upper than Android 7.0

I'm having the same issue updating to android 9, any chance in supporting Xamarin.Android.Support.* <IP_ADDRESS>?

Version conflict detected for Xamarin.Android.Support.Compat. Install/reference Xamarin.Android.Support.Compat <IP_ADDRESS> directly to project.

{NameSpace} -> Xamarin.Android.Support.CustomTabs <IP_ADDRESS> ->
Xamarin.Android.Support.Compat (= <IP_ADDRESS>)
{NameSpace}-> ZXing.Net.Mobile 2.4.1 -> Xamarin.Android.Support.v4 <IP_ADDRESS>   > -> Xamarin.Android.Support.Compat (= <IP_ADDRESS>)

Any updates on this issue yet? I'm also experiencing issues and need to upgrade to <IP_ADDRESS>

Same issue here....

Thanks for reporting this issue!  Unforunately it took me way too long to respond 😭.  Sorry, I apologize!  Recently the source code for this project was completely refactored to modernize it.  Many PR's were included in this effort, and many bugs were hopefully fixed.  Please try out the latest 3.x series of NuGet packages (currently in prerelease).  To try and make the project more maintainable in my spare time going forward, I've decided to close all existing issues to start with a clean slate.  If you're still experiencing this issue on the newest version, please open a new issue with as much detail as possible.  Thank you for your patience and understanding!  Happy scanning!

@Redth Those 3.x settings look like they are still beta versions. Is that ever going to change?


LNER Azuma

Thank you for adding this, this is my favourite system so far. Do you think you're planning on making a start of route for the system? I think it would be more realistic.

Find me some videos, and sure!

A video here. LNER Azuma on departure.
https://youtu.be/EgDFN4eAIaY?feature=shared

I found some vids


ARROW-2520: [Rust] CI should also build against nightly Rust

Since these builds are both pretty fast can you run them in the same CI entry?

Sure, I was considering that alternative too. Hopefully both toolchains are going to be cached properly.

Codecov Report

Merging #2477 into master will increase coverage by 1.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2477      +/-   ##
==========================================
+ Coverage    86.2%   87.46%   +1.26%
==========================================
  Files         308      259      -49
  Lines       46980    44746    -2234
==========================================
- Hits        40500    39139    -1361
+ Misses       6406     5607     -799
+ Partials       74        0      -74

Impacted Files
Coverage Δ

cpp/src/plasma/protocol.cc
95.36% <0%> (-3.31%)
:arrow_down:

cpp/src/plasma/store.cc
89.14% <0%> (-0.5%)
:arrow_down:

cpp/src/arrow/compute/compute-test.cc
99.34% <0%> (-0.02%)
:arrow_down:

cpp/src/plasma/plasma.h
100% <0%> (ø)
:arrow_up:

cpp/src/plasma/common.h
100% <0%> (ø)
:arrow_up:

go/arrow/datatype_nested.go

go/arrow/math/uint64_amd64.go

go/arrow/internal/testing/tools/bool.go

go/arrow/internal/bitutil/bitutil.go

go/arrow/memory/memory_avx2_amd64.go

... and 48 more

Continue to review full report at Codecov.

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

@xhochy could You take a look at this one too?

Thanks!


[Wallet] Use Charles proxy to see eth JSON rpc calls when using forno

Description
Update wallet network security config so we can use Charles as a proxy. This allows us to see eth JSON rpc calls while using forno, which can be helpful for debugging. Also added instructions to set up Charles
Tested
On a pixel 2
Does not yet support iOS
Related issues
Set this up to debug slow transaction receipts (#1741 ) and profile app data usage using forno (see #451)
Backwards compatibility
Yes

Example of what we can see using the proxy


error: /auth/renew 403 Forbidden

version
filemanager: 1.3.11
ubuntu: 16.04.3
chrome: 62
filemanager configure

address: <IP_ADDRESS>
baseURL:
noAuth: false
database: "/home/filemanager/filemanager.db"
log: "/home/filemanager/error.log"
port: 5000
reCaptchaKey: ''
reCaptchaSecret: ''
plugin: ''
scope: "/home/downloads"
allowCommands: true
allowEdit: true
allowNew: true
commands:
        - git
        - ls

What are you trying to do?
visit my filemanager webpage

What did you expect to see?
no error

What did you see instead (give full error messages and/or log)?
In f12, there is a error: Failed to load resource: the server responded with a status of 403 ()       api/auth/renew
In my server terminal stdout, there is a error: 2017/12/06 20:43:56 /auth/renew: 403 Forbidden

This error always happen when I visit login webpage.
It seems that there is a error about auth in configure ?

Did you log in?

@hacdias No, I didn't. show you a screenshot

But after I logged in, the error disappeared.
Although this error does not affect the function, but I think it is necessary to report this

Oh, but this is expected. I did try to remove those erros but I don't think it's possible since it is XmlHTTPRequest who does that,

Oh, I got it.
Thanks for your reply !


[WIP] Fix backend/mlx/core and  backend/common/dtypes for MLX + Improve integration_tests/numerical_test.py

MLX Backend Specific Failures:
Missing Operations: The MLX backend lack implementations for specific operations, including:

mod
rand
rmatmul
ror
rpow
rxor
xor

 KERAS_BACKEND=mlx pytest keras/src/backend/
=================================================================================================================== short test summary info ====================================================================================================================
FAILED keras/src/backend/common/variables_test.py::VariableOperationsTest::test__mod__ - AssertionError:
FAILED keras/src/backend/common/variables_test.py::VariableOperationsTest::test__rand__ - AttributeError: 'mlx.core.array' object has no attribute '__rand__'. Did you mean: '__and__'?
FAILED keras/src/backend/common/variables_test.py::VariableOperationsTest::test__rmatmul__ - AttributeError: 'mlx.core.array' object has no attribute '__rmatmul__'. Did you mean: '__imatmul__'?
FAILED keras/src/backend/common/variables_test.py::VariableOperationsTest::test__ror__ - AttributeError: 'mlx.core.array' object has no attribute '__ror__'. Did you mean: '__ior__'?
FAILED keras/src/backend/common/variables_test.py::VariableOperationsTest::test__rpow__ - AttributeError: 'mlx.core.array' object has no attribute '__rpow__'. Did you mean: '__ipow__'?
FAILED keras/src/backend/common/variables_test.py::VariableOperationsTest::test__rxor__ - AttributeError: 'mlx.core.array' object has no attribute '__rxor__'. Did you mean: '__ior__'?
FAILED keras/src/backend/common/variables_test.py::VariableOperationsTest::test__xor__ - AttributeError: 'mlx.core.array' object has no attribute '__xor__'. Did you mean: '__ior__'?
========================================================================================================== 7 failed, 413 passed, 91 skipped in 7.92s ===========================================================================================================

Codecov Report
Attention: Patch coverage is 0% with 76 lines in your changes are missing coverage. Please review.

:exclamation: No coverage uploaded for pull request base (mlx@722883a). Click here to learn what that means.

Files
Patch %
Lines

keras/src/backend/mlx/nn.py
0.00%
76 Missing :warning:

Additional details and impacted files
@@          Coverage Diff           @@
##             mlx   #19619   +/-   ##
======================================
  Coverage       ?   53.10%
======================================
  Files          ?      506
  Lines          ?    46011
  Branches       ?     8517
======================================
  Hits           ?    24435
  Misses         ?    19985
  Partials       ?     1591

Flag
Coverage Δ

keras
53.10% <0.00%> (?)

keras-numpy
53.10% <0.00%> (?)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Hi @fchollet and @lkarthee :)
I apologize for not being active here recently. I have been busy preparing for a very important job interview.
My work with Keras has significantly improved my resume and contributed to my being selected for these interviews. so thank you!
I promise I will return and be more active.

Hi @Faisal-Alsrheed Any update on this PR? Please. Thank you!


Automated release when merged to master

Create job/workflow which builds release for MacOS and Linux when build and tests are successful

Fixed in version 0.1.2. It now builds binaries for macos and linux when tagging


Note, specs are being changed a bit in next version

Just leaving this up. I'm busy with updating our engine on a few things.
Things to note

Mining has changed. It's now symmetric and does it by processing "mining requests"
Wood Growth, City Upkeep and adjacency bonus have changed
Carts probably will be building roads at a rate of 0.75 now.

Thanks for the heads up!


Lab 13 creation of access policy

Contact Details
<EMAIL_ADDRESS>What happened?
Exercise : 01
Task: 02
Step: 04
Description of issue:
Hello team, the key vault access policy creation process looks outdated. Currently, the creation steps are different.
Thank you
Lab
Lab 13 Integrate Azure Key Vault with Azure DevOps
Relevant screenshots
paste here 😉
Do you want to help us? 👏

[ ] Create a Pull Request by following this project's Contribution Guide

I am closing the issue. We are in the process of refreshing this lab. Thank you.


dnstwist-20211204.tar.gz missed in the pypi index

👋  it looks like dnstwist-20211204.tar.gz file did not get uploaded into the pypi index. Thanks!

Thanks for pointing that out. I just uploaded.

created Homebrew/homebrew-core#90532, but somehow there are some dependency setup issues (gonna check out per that PR)

@elceef the requirements.txt missed in the artifact.
I think simply upload https://github.com/elceef/dnstwist/archive/refs/tags/20211204.tar.gz into pypi index is good enough.

The behavior has changed. Previously, when a required library was missing, only a notification was displayed. Now it's an error message with error code. In this particular case it looks like ssdeep is the issue.


Failed to destroy after upgrading to 0.8

I have a setup like this :
class Program < ApplicationRecord

  has_many :collaborations, foreign_key: "program_id", dependent: :destroy

  before_destroy :destroy_collaborations

  def destroy_collaborations
    reload.collaborations.each do |collaboration|
      collaboration.skip_before_destroy = true
      collaboration.destroy
    end
  end
end

class Collaboration < ApplicationRecord
  attr_accessor :skip_before_destroy

  before_destroy :program_still_have_collaborator?

  def program_still_have_collaborator?
    if program.reload.collaborations == [self]
      errors.add(:program, :program_without_collaborator)
      throw(:abort) unless skip_before_destroy
    end
  end
end

I upgraded to rails 7 and thus acts_as_paranoid 0.8. However, when i try to destroy a program, i constantly get the error "Failed to destroy" error because of my Collaboration before_destroy callback. I did not have this issue before upgrading

Hi @tomcoquery, I have a few questions that will help me debug this:

Which of these classes has acts_as_paranoid?
What is the backtrace for the "Failed to destroy" error?
Does it still work if you don't upgrade to Rails 7 but still use acts_as_paranoid 0.8?

Hi, thanks for your reply.

Both classes have acts_as_paranoid

Here's the full backtrace :

# /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/acts_as_paranoid-0.10.2/lib/acts_as_paranoid/core.rb:165:in `destroy!'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/has_many_association.rb:124:in `each'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/has_many_association.rb:124:in `delete_records'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/collection_association.rb:390:in `remove_records'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/collection_association.rb:381:in `block in delete_or_destroy'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/database_statements.rb:314:in `transaction'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/transactions.rb:209:in `transaction'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/collection_association.rb:308:in `transaction'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/collection_association.rb:381:in `delete_or_destroy'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/collection_association.rb:188:in `destroy'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/collection_association.rb:165:in `destroy_all'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/has_many_association.rb:28:in `handle_dependency'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/associations/builder/association.rb:141:in `block in add_destroy_callbacks'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:467:in `instance_exec'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:467:in `block in make_lambda'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:199:in `block (2 levels) in halting'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:687:in `block (2 levels) in default_terminator'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:686:in `catch'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:686:in `block in default_terminator'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:200:in `block in halting'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:595:in `block in invoke_before'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:595:in `each'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:595:in `invoke_before'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:106:in `run_callbacks'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/acts_as_paranoid-0.10.2/lib/acts_as_paranoid/core.rb:173:in `block in destroy'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/transactions.rb:354:in `block in with_transaction_returning_status'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/transaction.rb:319:in `block in within_new_transaction'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/transaction.rb:317:in `within_new_transaction'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/database_statements.rb:316:in `transaction'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/transactions.rb:350:in `with_transaction_returning_status'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/acts_as_paranoid-0.10.2/lib/acts_as_paranoid/core.rb:172:in `destroy'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:71:in `each'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:71:in `block in find_each'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:138:in `block in find_in_batches'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:245:in `block in in_batches'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:229:in `loop'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:229:in `in_batches'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:137:in `find_in_batches'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/relation/batches.rb:70:in `find_each'
     # /Users/tomcoquery/.asdf/installs/ruby/3.0.1/lib/ruby/gems/3.0.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/querying.rb:22:in `find_each'

The error disappears if I remove the gem and do a regular rails destroy (on rails 7). The error is also present if i stay on rails 6.1 and update acts_as_paranoid to 0.8.

Thanks @tomcoquery. One final question: Which version of acts_as_paranoid were you running before the update?

I can reproduce this. I did have to add belongs_to to the Collaboration class, but I'm sure that's present in the full code. When I remove the acts_as_paranoid calls, the error goes away. However, even in that case the records are not destroyed!
The reason is that dependent: :destroy adds its own callback to the Program class that destroys the Collaboration records. This callback is called before the custom destroy_collaborations callback, so before skip_before_destroy is set.
To make this work again, you need to swap the before_destroy and has_many lines, so the code will look like this:
before_destroy :destroy_collaborations
has_many :collaborations, foreign_key: "program_id", dependent: :destroy

Brilliant, this indeed fixes the problem. Thank you for taking the time to investigate.


why http3 roundTripper.Close() don't wait received the Handshake_DOWN

Hello, I found a problem when I test the http3
the next 0-rtt will fail，if  do not wait for the handshake to complete,
roundTripper.Close() code is:
func (c *client) Close() error {
	if c.session == nil {
		return nil
	}
	return c.session.CloseWithError(quic.ApplicationErrorCode(errorNoError), "")
}

If I close the connection immediately after I receive the first reply,  the next transfer 0-rtt will fail 。
if I sleep a second  before roundTripper.Close() will also 0-rtt success.
	for i < 3 {
			i++
			roundTripper := &http3.RoundTripper{
				TLSClientConfig: &tc,
				QuicConfig: &qconf,
			}
			hclient := &http.Client{
				Transport: roundTripper,
			}
			req, err := http.NewRequest(http3.MethodGet0RTT, url, nil)
			_, err = hclient.Do(req)
			if err != nil {
				log.Fatal(err)
			}
			// print body
			fmt.Println("need to wait for the handshake_done before closing")
			time.Sleep(1*time.Second) // need wait one rtt for handshake
			roundTripper.Close()
	}

I found some solutions to wait handshake confirmed：
https://github.com/kaiyuhou/quic-go-v201/blob/c5310f35c799cdbe226c2901effca5f260d36610/http3/roundtrip.go#L186

@kaiyuhou Can you tell me why?
why http3.RoundTripper.close() not support wait handshake confirmed?

( May I ask which tool you use to generate the graph? )

https://qvis.quictools.info/#/sequence @NitroCao

I don't understand this issue. What's the problem?

I don't understand this issue. What's the problem?
@marten-seemann  hi, When I test the http3 0-rtt，
I found I need to wait for the handshake to complete before closing, otherwise the next can not usr 0-rtt

	for i < 3 {
			i++
			roundTripper := &http3.RoundTripper{
				TLSClientConfig: &tc,
				QuicConfig: &qconf,
			}
			hclient := &http.Client{
				Transport: roundTripper,
			}
			req, err := http.NewRequest(http3.MethodGet0RTT, url, nil)
			_, err = hclient.Do(req)
			if err != nil {
				log.Fatal(err)
			}
			// print body
			fmt.Println("need to wait for the handshake_done before closing")
			time.Sleep(1*time.Second) // need wait one rtt for handshake
			roundTripper.Close()
	}

Hi @ldmid666 , I am so surprised that you find my solution to this issue! You can use this diff to solve your problem if you just want to find a hack solution to mitigate this problem. The solution is simple and straightforward: https://github.com/kaiyuhou/quic-go-v201/commit/c16996205e73c9591fd5ce7033ab528d055b3f1b
Hi, @marten-seemann let me explain this issue to you:

When the client sends out the 0-RTT request, it will use pre-cached QUIC 0-RTT Token and TLS Session Ticket to resume the connection and encrypt the request packet.

(Then the pre-cached QUIC 0-RTT Token and TLS Session Ticket will auto expired.)

The server will immediately send back the response data packet.
Ideally, the client will send Handshake_Finished to the server, and the server will send back Handshake_Done.

The Handshake_Done will carry a new QUIC 0-RTT Token and TLS Session Ticket, which can be used for the next 0-RTT connection.

But, in current quic-go implementation, after the application (i.e., HTTP/3 client) received the response data, it will call the defer roundTripper.Close().

The QUIC client will directly send a Connection_Clone (Application) to the server and close the QUIC session.
So, it has no chance to receive the new QUIC 0-RTT Token and TLS Session Ticket.

Therefore, the next connection will fall back to 1-RTT.

So, in this case, a success 0-RTT connection will always be followed by a failed 0-RTT, and then a success 0-RTT.

Will the application has the ability to solve this issue? I think No. Because the application doesn't have detailed information about the underline QUIC handshake status. So, it has to be solved at the QUIC level.

I am not sure whether QUIC RFC mentioned this or the current design choice in quic-go is an RFC undefined behavior. But I would think the current design choice is reasonable.
If the client doesn't care about the potential next 0-RTT session assumption performance, the client has no reason to keep the current connection, waiting for the Handshake_Done message from the server, if the client has already received the response data.
But I am now thinking, if it does not violate the RFC, it may be worth adding the functionality of my roundTripper.closeAfterHandshakeConfirmed() function as a option to the roundTripper.Close() function. I do need it to solve my scenarios when using quic-go since half a year ago. And now we find another person who wants it.

Thank you for the detailed explanation.

Will the application has the ability to solve this issue? I think No. Because the application doesn't have detailed information about the underline QUIC handshake status. So, it has to be solved at the QUIC level.

What about EarlySession.HandshakeComplete?
But really, there's no requirement on the server to immediately send a new token and a new session ticket (this has nothing to do with HANDSHAKE_DONE, btw). quic-go (currently) does so, but that's an implementation decision and might change at some point in the future.
If you want to guarantee that the next connection attempt will be able to use 0-RTT, you'll probably want to monitor your TLS session ticket cache.

For immediately, I mean the server will immediately send back the application response. So, it will come faster than the Handshake_Down message, which raises this issue.
I like your idea of monitoring the TLS session ticket cache at the application level.

BTW, the current http3 client example is a little simple. It doesn't show users how to create QUIC TokenStore and TLS ClientSessionCache, and the correct way to enable 0-RTT.

For EarlySession.HandshakeComplete, is there a way for the application to access it?

For immediately, I mean the server will immediately send back the application response. So, it will come faster than the Handshake_Down message, which raises this issue.

That is the correct behavior. You want the server to send the response as quickly as possible. Otherwise, 0-RTT would be kind of pointless.

For EarlySession.HandshakeComplete, is there a way for the application to access it?

Not sure if there's a way to get it from http3. I don't see a strong use case, tbh. It's used internally, for all requests that don't use 0-RTT.

BTW, the current http3 client example is a little simple. It doesn't show users how to create QUIC TokenStore and TLS ClientSessionCache, and the correct way to enable 0-RTT.

@kaiyuhou Thank you for the detailed explanation.  @marten-seemann  I also found another problem about 0-rtt example. I refer to your code zero_rtt_test.go.
https://github.com/lucas-clemente/quic-go/blob/8ecbb05d446ae3aef199f8ad50678d637ec95eb3/integrationtests/self/zero_rtt_test.go#L91
    gets := make(chan string, 100)
    puts := make(chan string, 100)
    clientConf.ClientSessionCache = newClientSessionCache(gets, puts)

I found  the SessionCache must be a LRU cache. Otherwise, it will be blocked  (to write new?).

ClientSessionCache is an interface, you're free to use any implementation of that interface you like.

I think we've resolved the issue here. Closing this.


Severe slowdown of Markdown preview

VSCode Version: Code - Insiders 1.16.0-insider (f1a3bc4f714123eaff5e15ad976d7f403cc1bfa2, 2017-08-11T05:16:53.568Z)
OS Version: Windows_NT x64 10.0.16251
Extensions:

Extension
Author (truncated)
Version

markdown-preview-github-styles
bie
0.0.2

vscode-eslint
dba
1.2.11

coldfusion
ili
0.0.10

wordcount
ms-
0.1.0

htmlescape-vscode-extension
ray
0.0.4

spellchecker
swy
1.2.13

I noticed that Markdown preview is incredibly slow for me now - sometimes taking near a minute to render. It seems to be a "one time per doc" issue as if I close the preview and open it up again, it works well, but previewing a new Markdown file is slow again.
I'm using files from my blog - here is one example: https://github.com/cfjedimaster/raymondcamdendotcom/blob/master/content/post/2017/08/09/career-advice-for-a-new-web-dev.md

I'm having trouble reproducing this on a windows machine. A few questions:

Does the latest insiders build still show this problem?
If you disable all extensions, does this still occur?
If you get rid of the script block in the document, does the problem still occur?

Thanks

Updated and it went away. Thank you. :) Found a new bug though. ;)

Actually - I'm going to stay here as I think it may be related. Please tell me if not and I'll refile.
So the initial issue I saw is definitely fixed. One thing I do a lot (and it bugs the heck out of me but honestly it is my fault, not VSC) is this:
Open a MD file.
Click preview.
Open a second MD file.
And I forgot the preview had focus. So the second MD file opens in the second ... block? Whatever it is.
So I just did that. I closed the second MD file in the second block and I noticed the preview was gone. Instead, there was a loading style widget on top. It's like the preview "lost" the view and had to rerender, and that took like 5-10 seconds. I can try recording a video if that would help.

Yes, please try recording a short video or providing more detailed repo steps. I could not reproduce this issue

So - the problem has gotten worse. I'm now getting extension host crashes. But here is a video.
https://www.screencast.com/t/cRMHoSlj94E
Going to try w/ extensions disabled too.

Ok, so testing w/ all extensions disabled and it is working correctly. I'm using "Markdown Preview Github Styling" - I bet that is the issue. Going to re-enable it and see if it comes back.

@cfjedimaster Yes, please try disabling extensions and seeing if the issue still reproduces. Also, can you please post the video somewhere that does not require Flash to view

Sorry - Jing was the quickest solution I could find.
So woah... get this. I believe it may be a spell checker extension!

Yep. This is the extension causing issues (I believe) - https://marketplace.visualstudio.com/items?itemName=swyphcosmo.spellchecker. Going to file a bug report them. Thanks for hearing me out.

Ok, thanks for the quick followup. Closing as caused by extension


Add Block Library

To help with authoring and to know what variations exist

https://www.aem.live/docs/sidekick-library


Source code questions

https://github.com/mdevils/cst/blob/master/src/elementTree.js#L10-L91 could be replaced with https://github.com/jscs-dev/babel-jscs/blob/aeccaae43660db17549e95c8b3ec8a7b00df1389/index.js#L6 which are these: https://github.com/babel/babel/blob/bb5f1120b79c086256b270182f2bd232b89d4276/src/babel/types/visitor-keys.json.
Any reason why we needed to duplicate them here?

Hello Joel, I also found visitor-keys useful, right now duplication only exists for tracking what's done/tested, so it is a temporal duplication.

Hope you don't mind the issues asking questions. There's no PR to leave comments on. I'll keep my questions to this thread to avoid creating multiple issues.

I appreciate questions! Every non obvious thing is a reason for docs improval :)


Fix RayCast2DEditor uninitialized value

node was previously read before being set. Found by Valgrind.

Thanks!

Cherry-picked for 3.5.1.


SignedSDJWT properties and functions access

While the SignedSDJWT struct itself is public, it doesn't expose most of it's methods and variables as such, hence rendering them inaccessible for consumers of the library. I'm not exactly sure what should be public and what actually makes sense to keep internal, but I'd be happy to make a PR once someone can point it out to me.
Currently I am looking to re create the claims, but recreateClaims() functions is not public.
The same applies for many of the other properties and functions across the library - internal access does not make them callable by the library integrator.

Hi @kuldar-daniel thank you for your comments. Please make a PR that suits your use case.


work around chrome startup issue with --load-and-launch-app

Came across the --silent-launch switch in this issue's comment thread:
https://code.google.com/p/chromium/issues/detail?id=175381
It seems to fix the issue I've been seeing in which Chrome sometimes fails to successfully launch:
https://github.com/uProxy/uproxy/issues/2174
This will make our release script a lot less painful to run.

nice!

:+1:


Are multi-agent environments supported?

This comment in code indicates that they are supported:
https://github.com/NervanaSystems/coach/blob/master/rl_coach/level_manager.py#L50
But don't see any documentation or examples.

Hi @bbalaji-ucsd,
You are correct, there is infrastructure in place to enable future support in multi-agent RL, but currently it is not officially supported. This is why there are no examples nor documentation.  Adding support will probably require a new multi-agent based GraphManager, and potential changes to LevelManager.


password rest

can i intercept passwords when the victim enter the link and change the password using forget password?

Check this tool on Telegram, can be fully customized to do whatever you want for phishing. and can also grab cookies.
https://t.me/dayztar

**Hi 👽 ! If you are interested in ⚙Advanced Phishing⚙ and the ✨Evilginx3✨ tool then I offer you Google Gmail and Custom Phishlets with a ✅Free Tutorial✅ which arrives if the 📈Telegram reaches 50 Subscribers📈
⏳ GOOGLE GMAIL PHISHLET 2024 WITH PROOF ⏳
->
⛔https://www.youtube.com/watch?v=nA47UknIE6A⛔
🔓 Ask your questions and a free tutorial from 50 subs on telegram !!!
->
📩https://t.me/Noremorse1011📩**


Rewrite of the general guidelines

Intent is to incorporate all the guidelines thus far written, but place them in a reusable package that is easy to read for the client library developer.  Requirements for the Azure SDK team (for example, requirements around Azure Core or the HTTP pipeline) are defered to an appendix.
To read the entire guidelines (since this is a complete rewrite):
git clone https://github.com/adrianhall/azure-sdk
cd azure-sdk
git checkout rewrite
npm install
npm run build

Then open out/DesignGuidelines.html in a browser.
All the new files are located within the general folder.  The idea to this is that if you are creating new guidelines, you copy the general folder to a new folder as a starting point.
Once this is merged and all the per-language guidelines are updated and edited, I will submit another PR to get rid of the old copies.

One minor nitpick - I'm never a fan of using the term 'customer', because it feels like we expect payment. The terminology section defines 'consumer', and I think we should use that in all places.

One minor nitpick - I'm never a fan of using the term 'customer', because it feels like we expect payment. The terminology section defines 'consumer', and I think we should use that in all places.

Totally agree - I've updated all but one reference (which made sense in context)


Where is srrg_test?

Hi, not an issue. But where do I find the test suite srrg_test? I would like to see the srrg_test/test_helper.hpp file just out of curiosity.

Hey,
This is just a wrapper to the gtest suite. It is located in the repo here.
Cheers!


Remove deprecated tracker

Remove deprecated tracker job and related reference.
Signed by: Tomcli<EMAIL_ADDRESS>

will wait for CI to pass

Travis failure unrelated


Playwright framework with sample live chat widget test for chat button #1

Playwright framework with sample live chat widget test for chat button
For custom live chat widget, currently using sampleWidget from sample folder. as on required for test case will create configured script in automation_tests folder .
Adding all tests files under automation_tests
Run below command to execute automation tests,

npm run test:build : to build sampleWidget and run tests on latest sampleWidget script.
npm run test: to run tests on existing sampleWidget script.

Please refer test [as screenshot image]

Done

raised new PR. did not require this one now.


[FEAT: Improvements] Complete Reaction Observer

Reaction Observer

[x] can parse array modifiers
[ ] can parse map or sets or any collections modifiers
[x] can parse property settings

  this.prop++
  this.prop--
  this.prop = ...
  this.prop = '...'.trim()...()
  this.prop += ...
  // etc

[ ] can parse property assignements to any vars

const arr = this.array;

closing, using proxies when the component is typed


Window Border colour keeps reverting to orange.

OS: Windows 10 x64
Issue Descriptions:
As the title really, After the update I started the client and the window border was orange do went into the setting and turned dark mode off and on, that fixed it but then after a while the border went back to orange.

Can you pinpoint a particular action that switches back? I haven't been able to reproduce this yet.

This is a small bug
If you don't like it, just use windows borders

Having the same issue, except I can't get the border to ever be anything but orange.

@jostrander I eventually managed to replicate this, but only on my friends rubbish laptop :+1:   It looks like in the latest version of electron something changed in chromium in regards to DOM rendering so some of our inject code was running before the DOM was ready.  It has been fixed in master in 5c24c63d78761dde80c69de7e4bb5f500b4ae496


not working

In both versions (python and windows) it stays at 'title' and the songs are never downloaded

Hi It still works,
try using a vpn
see image

now i have this error

Installed pysocks but now stays in 'title' again

Hi It still works, try using a vpn
see image

thanks


Schema-Parse: Create Different "Ref" Type For Definition References

When we're referencing another definition in the TypeInfo AST (ex: Object properties of Object type), we should have a seperate "...Ref" type defined which only includes the fields we care to support for that type of reference.
For example:
EnumDefinitionRef
ObjectDefinitionRef
QueryDefinitionRef
etc

This is necessary because currently the AST typings are ambiguous, and don't accurately portray that nested definition references are "partial" and not fully complete.

Doing this should allow us to remove the "Blackboard".
We should create a "validator" for "resolveReferences" to ensure that all named type references are valid pointers.


mx.ui.action does not work as expected in popups

Sharing some information:
https://github.com/mendix/generator-mendix/blob/master/generators/app/templates/WidgetBoilerplate/src/WidgetName/widget/WidgetName.js.ejs#L76
Found a limitation on the https://apidocs.mendix.com/6/client/mx.ui.html#.action
Though documentation states that origin: this.mxform is not needed, it is not completely true. It is not working for full pages but does not work for popups. So this call action will close the page but not a popup. : (
So I think we need to reintroduce the origin again.
Cheers.

I'll think we need to bring this up @ R&D, because adding origin: this.mxform results in a MX7 deprecation warning. That beings said, we can safely reintroduce it, will be deprecated in MX8 if I'm correct.

The deprecated variant of Mendix 5 was named caller not aware about the origin...

Yeah my comment was removed because I spotted my own error ;-). We'll reintroduce origin I guess, and revert back to mx.data.action


Avoid m2m selects when diffing

Problem Statement
I'm about to create a timeline using diff_against quite often. Internally it uses django's model_to_dict which fires SQL queries for every ManyToMany field (twice - for every model related to the diff).
Describe the solution you'd like
I'd like to get rid of those SQL queries, as many to many relations are not supported so far.
Therefore I'd like to introspect the model and use the exclude argument to model_to_dict to avoid firing those queries.
Describe alternatives you've considered
Alternatively pass along the excluded fields to model_to_dict to at least give the caller of diff_against the opportunity to exclude many to many relations.

Duplicate of #776


A missing "." has been added

Pre-Requisites

[X ] Yes, I updated AUTHORS.md OR this is not my first contribution
[ X] Yes, I included and/or modified tests to cover relevent code OR my change is non-technical
[ X] Yes, I wrote this code entirely myself OR I properly attributed these changes in Third Party Notices

Description of Changes
A missing "." has been added, to demo the way to contribute to my mentees at https://www.meetup.com/togetherweopensource/
My meetup is purposed to help deprivileged and underrepresented people to get into IT via OpenSource contributions

Hi Lee. I totally agree. I was in the very beginning of my OpenSource
journey.
Nowadays I would rather suggest investigating the project and writing a
post about it as a first contribution, not fixing a dot.
On Tue, 9 Aug 2022 at 01:45, Lee Meador @.***> wrote:

@.**** requested changes on this pull request.
I will need you to add something more than your name and a period before
its worth making an actual version change. People would laugh at the
version notes.
—
Reply to this email directly, view it on GitHub
https://github.com/AmericanAirlines/preload-local-actions/pull/154#pullrequestreview-1065950627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQWQ6QGNICVI64J7DU77QDVYGS3ZANCNFSM5YYSRELA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

--
Kind regards,
Nikita Koselev


Motion thread should use motion HAL in motion thread

Currently motion is done in planner thread. This wasn't an issue when there was no jogging in GUI, but now is an issue
I've implemented a few workarounds to be removed. Notably:
    def poll_update_pos(self):
        last_pos = self.motion_thread.pos_cache
        if last_pos:
            self.update_pos(last_pos)
        # FIXME: hack to avoid concurrency issues with planner and motion thread fighting
        # merge them together?
        if not self.pt:
            self.motion_thread.update_pos_cache()
        self.position_poll_timer.start(400)

this should all be good now. the last big outstanding issue was that the planner thread contended with the motion thread, but now the planner thread offloads the actual movement to the motion thread


Support 32 bit compilation

As noted in #19 ulong is used for size type, which should be fixed.
Surely there's other stuff to be discovered that's brake 32bit compilation...

We need Travis test first

Adding travis will not be trivial, since x86 libs have to be build. Here I wanted to tend only to ulong vs size_t problem. I'd like to solve testing in separate PR.

I'd like to solve testing in separate PR.

That is why it's in separate issue #19


global cwise transform fails if regl is a dependency

A weird interaction, but figured I'd ask since it lives in the same ecosystem. A global cwise transform is useful since most cwise-based modules are not cwise-transformed. However, browserify -g cwise fails if regl is a dependency.
To reproduce:
$ echo "require('regl')" > index.js
$ npm i cwise
$ browserify -g cwise index.js

The resulting output is:
SyntaxError: Unexpected token (2:22) while parsing file: /Users/rreusser/test8/node_modules/regl/lib/constants/arraytypes.json
    at Parser.pp.raise (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/node_modules/acorn/dist/acorn.js:1745:13)
    at Parser.pp.unexpected (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/node_modules/acorn/dist/acorn.js:2264:8)
    at Parser.pp.semicolon (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/node_modules/acorn/dist/acorn.js:2243:59)
    at Parser.pp.parseExpressionStatement (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/node_modules/acorn/dist/acorn.js:2677:8)
    at Parser.pp.parseStatement (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/node_modules/acorn/dist/acorn.js:2462:160)
    at Parser.pp.parseBlock (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/node_modules/acorn/dist/acorn.js:2692:21)
    at Parser.pp.parseStatement (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/node_modules/acorn/dist/acorn.js:2443:19)
    at Parser.pp.parseTopLevel (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/node_modules/acorn/dist/acorn.js:2379:21)
    at parse (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/node_modules/acorn/dist/acorn.js:101:12)
    at module.exports (/Users/rreusser/test8/node_modules/cwise/node_modules/static-module/node_modules/falafel/index.js:22:15)

It's just a small json file, so it's not immediately apparent what there is to dislike about it. I'm wondering if perhaps it's just uglify-js that needs a 2.6 -> 2.7 update or something of the sort (acorn maybe?).

It could be due to ES6 syntax.  Switching the cwise transform to babel might fix it.

Can you clarify what you mean? Do you mean to babelify first, then apply the cwise transform?
$ browserify -g [ babelify --presets [ es2015 ] ] -g cwise index.js > bundle.js

That might work, but a better solution would be to fix the cwise transform falafel dependency to use es6 instead.

I updated cwise's static-module dep to see if I'd get lucky, but didn't fix it. I verified that the newer version indeed sends {ecmaVersion: 6} to falafel.
The cause seems to be that acorn is parsing the json requires as javascript. See: https://github.com/ternjs/acorn/issues/415 So in that sense, it's 'correct' to fail, but the question then is which step in the chain is failing such that it's trying to parse json as javascript.
The one simple fix that did work was to change regl's constants to .js files that export their data, but it's unpleasant to have to propagate silly workarounds upstream.

For reference, a repo that uses cwise with an updated static-module dependency : https://github.com/rreusser/cwise-regl-interaction
To reproduce:
git clone https://github.com/rreusser/cwise-regl-interaction.git
cd cwise-regl-interaction
npm install
npm run bundle

Didn't otherwise manage to make headway though. 😞

Possibly related to/solved by #13. 🍻 @etpinard!


question about “crop_img_patch_with_box” function

Hello， Do you add “crop_img_patch_with_box” in /AutoAlignV2/tools/data_converter/create_gt_database.py?
Or is this function from mmdet3d?
Thank you.

i have the same question.it will show TypeError: list indices must be integers or slices, not tuple,right? there are actually a wrong, but do not know the solution. may i get your ways?  thanks

File "tools/create_data.py", line 237, in
max_sweeps=args.max_sweeps)
File "tools/create_data.py", line 84, in nuscenes_data_prep
with_bbox=True)
File "/opt/lcx/project/AutoAlignV2/tools/data_converter/create_gt_database.py", line 324, in create_groundtruth_database
object_img_patches = crop_img_patch_with_box_v2(gt_boxes, example['img'])
File "/opt/lcx/project/AutoAlignV2/tools/data_converter/create_gt_database.py", line 129, in crop_img_patch_with_box_v2
img_patch = org_img_list[num_img][y1:y1 + h, x1:x1 + w]
IndexError: list index out of range
i meet the question like this. it shows that the org_img_list input only contains one image while we choose 6 images of different  views to crop it. so my question is, why only crop one image patches?

Hi, we only choose one view to crop, the first view that has the object, following the order (FRONT, LEFT_FRONT, RIGHT_FRONT, LEFT_BACK, RIGHT_BACK, BACK, maybe). The reason that I crop one image patch is we simply want to reduce the size of GT database.

thanks a lot for your prompt answer~ so in [crop_img_patch_with_box”] function, i may just filter other views like this?
if(num_img ==0)   img_patch = org_img_list[0][y1:y1 + h, x1:x1 + w]  img_patches.append(img_patch) where num_img varies from 0 to 5, which means 6 different views gt bboxes.
buaazeus opened this issue on Oct 26, 2022 · 3 co

Hi, we only choose one view to crop, the first view that has the object, following the order (FRONT, LEFT_FRONT, RIGHT_FRONT, LEFT_BACK, RIGHT_BACK, BACK, maybe). The reason that I crop one image patch is we simply want to reduce the size of GT database.

You may have a try. The code should not have this problem since I have used it to generate the database before... it's quite strange... Perhaps I change it for waymo later.