pulumi install attempts to download a provider plugin for pulumi-esc-sdk

What happened?
I added Pulumi ESC SDK to configure Pulumi Cloud ESC, but we have an error on the Python package side, as we can see below:
requirements.txt
pulumi>=3.133.0
pulumi-aws>=6.52.0
pulumi-cloudflare>=5.39.0
pulumi-command>=1.0.1
pulumi-esc-sdk>=0.10.0
pulumi-gcp>=8.3.0
pulumi-kubernetes>=4.18.1
pulumi-tls>=5.0.6
pylint>=3.3.1
pyyaml>=6.0.2

CLI output:
pulumi install
Installing dependencies...

Creating virtual environment...
Finished creating virtual environment
Updating pip, setuptools, and wheel in virtual environment...
Requirement already satisfied: pip in ./venv/lib/python3.12/site-packages (24.0)
Collecting pip
  Downloading pip-24.2-py3-none-any.whl.metadata (3.6 kB)
Collecting setuptools
...
resource plugin esc-sdk-0.10.0 version 0.10.0 installing
error: resource plugin esc-sdk-0.10.0 downloading from : failed to download plugin: esc-sdk-0.10.0: 403 HTTP error fetching plugin from https://get.pulumi.com/releases/plugins/pulumi-resource-esc-sdk-v0.10.0-darwin-arm64.tar.gz

Example
Added in the description
Output of pulumi about
Added in the description
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Moving back to https://github.com/pulumi/esc-sdk as this is where it needs to be fixed (https://github.com/pulumi/esc-sdk/pull/32).

@seanyeh @justinvp I'm reopening this issue as it's not fixed - at least, not entirely.
When running pulumi install (like within Pulumi Deployment), I have the error message below (error on the last line).
🔥 It's also worth noting that esc-sdk appears under the Plugins section as a resource provider when running pulumi about 👇.
So, I guess the Pulumi CLI doesn't fully leverage the pulumi-plugin.json somehow.
pulumi install
Installing dependencies...

Creating virtual environment...
Finished creating virtual environment
Updating pip, setuptools, and wheel in virtual environment...
Requirement already satisfied: pip in ./venv/lib/python3.11/site-packages (24.0)
Collecting pip
  Using cached pip-24.2-py3-none-any.whl.metadata (3.6 kB)
Requirement already satisfied: setuptools in ./venv/lib/python3.11/site-packages (65.5.0)
Collecting setuptools
  Using cached setuptools-75.1.0-py3-none-any.whl.metadata (6.9 kB)
Collecting wheel
  Using cached wheel-0.44.0-py3-none-any.whl.metadata (2.3 kB)
Using cached pip-24.2-py3-none-any.whl (1.8 MB)
Using cached setuptools-75.1.0-py3-none-any.whl (1.2 MB)
Using cached wheel-0.44.0-py3-none-any.whl (67 kB)
Installing collected packages: wheel, setuptools, pip
  Attempting uninstall: setuptools
    Found existing installation: setuptools 65.5.0
    Uninstalling setuptools-65.5.0:
      Successfully uninstalled setuptools-65.5.0
  Attempting uninstall: pip
    Found existing installation: pip 24.0
    Uninstalling pip-24.0:
      Successfully uninstalled pip-24.0
Successfully installed pip-24.2 setuptools-75.1.0 wheel-0.44.0
Finished updating
Installing dependencies in virtual environment...
Collecting pulumi<4.0.0,>=3.0.0 (from -r requirements.txt (line 1))
  Using cached pulumi-3.136.1-py3-none-any.whl.metadata (11 kB)
Collecting pulumi-esc-sdk==0.10.1 (from -r requirements.txt (line 2))
  Using cached pulumi_esc_sdk-0.10.1-py3-none-any.whl.metadata (609 bytes)
Collecting urllib3<2.1.0,>=1.25.3 (from pulumi-esc-sdk==0.10.1->-r requirements.txt (line 2))
  Using cached urllib3-2.0.7-py3-none-any.whl.metadata (6.6 kB)
Collecting python-dateutil (from pulumi-esc-sdk==0.10.1->-r requirements.txt (line 2))
  Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl.metadata (8.4 kB)
Collecting pydantic>=2 (from pulumi-esc-sdk==0.10.1->-r requirements.txt (line 2))
  Using cached pydantic-2.9.2-py3-none-any.whl.metadata (149 kB)
Collecting typing-extensions>=4.7.1 (from pulumi-esc-sdk==0.10.1->-r requirements.txt (line 2))
  Using cached typing_extensions-4.12.2-py3-none-any.whl.metadata (3.0 kB)
Collecting protobuf~=4.21 (from pulumi<4.0.0,>=3.0.0->-r requirements.txt (line 1))
  Using cached protobuf-4.25.5-cp37-abi3-manylinux2014_x86_64.whl.metadata (541 bytes)
Collecting grpcio~=1.66.2 (from pulumi<4.0.0,>=3.0.0->-r requirements.txt (line 1))
  Using cached grpcio-1.66.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.9 kB)
Collecting dill~=0.3 (from pulumi<4.0.0,>=3.0.0->-r requirements.txt (line 1))
  Using cached dill-0.3.9-py3-none-any.whl.metadata (10 kB)
Collecting six~=1.12 (from pulumi<4.0.0,>=3.0.0->-r requirements.txt (line 1))
  Using cached six-1.16.0-py2.py3-none-any.whl.metadata (1.8 kB)
Collecting semver~=2.13 (from pulumi<4.0.0,>=3.0.0->-r requirements.txt (line 1))
  Using cached semver-2.13.0-py2.py3-none-any.whl.metadata (5.0 kB)
Collecting pyyaml~=6.0 (from pulumi<4.0.0,>=3.0.0->-r requirements.txt (line 1))
  Using cached PyYAML-6.0.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.1 kB)
Collecting debugpy~=1.8.5 (from pulumi<4.0.0,>=3.0.0->-r requirements.txt (line 1))
  Using cached debugpy-1.8.7-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (1.1 kB)
Collecting annotated-types>=0.6.0 (from pydantic>=2->pulumi-esc-sdk==0.10.1->-r requirements.txt (line 2))
  Using cached annotated_types-0.7.0-py3-none-any.whl.metadata (15 kB)
Collecting pydantic-core==2.23.4 (from pydantic>=2->pulumi-esc-sdk==0.10.1->-r requirements.txt (line 2))
  Using cached pydantic_core-2.23.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (6.6 kB)
Using cached pulumi_esc_sdk-0.10.1-py3-none-any.whl (87 kB)
Using cached pulumi-3.136.1-py3-none-any.whl (274 kB)
Using cached debugpy-1.8.7-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.1 MB)
Using cached dill-0.3.9-py3-none-any.whl (119 kB)
Using cached grpcio-1.66.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.8 MB)
Using cached protobuf-4.25.5-cp37-abi3-manylinux2014_x86_64.whl (294 kB)
Using cached pydantic-2.9.2-py3-none-any.whl (434 kB)
Using cached pydantic_core-2.23.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (2.1 MB)
Using cached PyYAML-6.0.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (762 kB)
Using cached semver-2.13.0-py2.py3-none-any.whl (12 kB)
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Using cached typing_extensions-4.12.2-py3-none-any.whl (37 kB)
Using cached urllib3-2.0.7-py3-none-any.whl (124 kB)
Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl (229 kB)
Using cached annotated_types-0.7.0-py3-none-any.whl (13 kB)
Installing collected packages: urllib3, typing-extensions, six, semver, pyyaml, protobuf, grpcio, dill, debugpy, annotated-types, python-dateutil, pydantic-core, pulumi, pydantic, pulumi-esc-sdk
Successfully installed annotated-types-0.7.0 debugpy-1.8.7 dill-0.3.9 grpcio-1.66.2 protobuf-4.25.5 pulumi-3.136.1 pulumi-esc-sdk-0.10.1 pydantic-2.9.2 pydantic-core-2.23.4 python-dateutil-2.9.0.post0 pyyaml-6.0.2 semver-2.13.0 six-1.16.0 typing-extensions-4.12.2 urllib3-2.0.7
Finished installing dependencies
Finished installing dependencies

error: failed to download plugin: esc-sdk-0.10.1: failed to download plugin: esc-sdk-0.10.1: 403 HTTP error fetching plugin from https://get.pulumi.com/releases/plugins/pulumi-resource-esc-sdk-v0.10.1-linux-amd64.tar.gz

pulumi about
CLI
Version      3.136.1
Go Version   go1.23.2
Go Compiler  gc

Plugins
KIND      NAME     VERSION
resource  esc-sdk  0.10.1
language  python   unknown

Host
OS       debian
Version  12.7
Arch     x86_64

This project is written in python: executable='/home/aureq/work/customers/zendesk/esc-sdk-33/venv/bin/python' version='3.11.10'

Current Stack: menfin/zendesk/0003

Found no resources associated with 0003

Found no pending operations associated with 0003

Backend
Name           pulumi.com
URL            https://app.pulumi.com/aureq
User           aureq
Organizations  aureq, team-ce, menfin, menfin-team, demo
Token type     personal

Dependencies:
NAME            VERSION
pip             24.2
pulumi          3.136.1
pulumi-esc-sdk  0.10.1
setuptools      75.1.0
wheel           0.44.0

Pulumi locates its logs in /tmp by default

@aureq version 0.10.2 should fix this completely 👍 I just tested it with a blank project

Thanks a lot @seanyeh I've confirmed it's working for me as well. I've asked our customer to also test on their end via their ci/cd pipeline. Once it's confirmed, I'll close this issue. Great work, thank you 🎈

Just confirmed, closing this issue. Thanks again @seanyeh


Can we refactor to avoid creating objects/cameras during import of pygfx?

I've noticed that the environment class is creating instances of various lights during import:
https://github.com/pygfx/pygfx/blob/1b9172599da05eafbe3a7a160c4ca7353f382e51/pygfx/renderers/wgpu/_environment.py#L38-L41
We do this to get the shapes of their uniform buffers, which differ between the instance and the class (supposedly due to inheritance?).
As a side-effect, we go through the entire process of creating lights including creating cameras and world objects. I don't know if they will also get allocated on the GPU, but it does for sure slow down import pygfx.
Would it be difficult to refactor this so that we can obtain the uniform buffers from the Ligtht's classes directly without having to instantiate?

Good idea to try to avoid this.

supposedly due to inheritance?

Yes, the uniform buffer is the combination of the fields set on the class, and its super classes.

Would it be difficult to refactor this so that we can obtain the uniform buffers from the Ligtht's classes directly without having to instantiate?

I think that should be possible .... I'll give it a try right now.


drop_duplicates() doesn`t work correctly at MODIN_STORAGE_FORMAT=omnisci

When I run:
import modin.pandas as pd
from modin.pandas.test.utils import test_data_with_duplicates_values
import modin.config as cfg
cfg.StorageFormat.put('omnisci')

data = test_data_with_duplicates_values[0]
modin_df = pd.DataFrame(data)
modin_df.drop_duplicates()

I have error:
AssertionError: Only column drop is supported

@modin-project/modin-omnisci  could someone please check if this still happens?

Closing as not reproducible. If you could reproduce the issue, please reopen.


Use openjdk:8-jdk-alpine as the base image

This is consistent with master, which uses openjdk:8-jdk. By fixing
the version to openjdk:8u121-jdk-alpine, we weren't getting built with
the latest patch version of openjdk (8u121 vs 8u131 at time of
writing), nor the latest version of Alpine (3.5.2 vs 3.6.2).

it was changed due to #508

Aha, OK. Thanks for letting me know. I'll keep an eye on the upstream bug: https://bugs.alpinelinux.org/issues/7372


Update Query.js

there is an error without this line in some cases:
SyntaxError: Unexpected token o
at parse (native)
at dedynamofy (/opt/icid/registration/node_modules/dynamoose/lib/Attribute.js:404:14)
at Attribute.parseDynamo (/opt/icid/registration/node_modules/dynamoose/lib/Attribute.js:467:13)
at Schema.parseDynamo (/opt/icid/registration/node_modules/dynamoose/lib/Schema.js:80:45)
at toModel (/opt/icid/registration/node_modules/dynamoose/lib/Query.js:206:16)
at Array.map (native)
at Response. (/opt/icid/registration/node_modules/dynamoose/lib/Query.js:214:31)
at Request. (/opt/icid/registration/node_modules/aws-sdk/lib/request.js:353:18)
at Request.callListeners (/opt/icid/registration/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
at Request.emit (/opt/icid/registration/node_modules/aws-sdk/lib/sequential_executor.js:77:10)

Could you provide the code that caused the failure?

db.customers.query({orgCode: {eq: orgCode}} ,function(err, result) {
the error in the line above. I checked this code many times and it works perfect after adding a line in your code.
orgCode in ddb is a number, I tried to set number and string in query function, so it didn't work for me.
I also checked my model "customers" and it's right. The error appeared when I added a Boolean values to my ddb table and model:
showAllEmployees: Boolean

There was an issue with the CI testing. Looking the the test output logs the debug line shows the model returned is an empty object. https://github.com/automategreen/dynamoose/pull/26/files#diff-c7f251522c2a751e0d457dee5ffb83f0L207
Can your run your code that generates the error with the debug enabled?
DEBUG=dynamoose* node your-app.js

dynamoose:model getItem response +97ms { Item:
   { externalPhoneNumbers: { SS: [Object] },
     apiHost: { S: 'api.intellicid.ru' },
     yellowPeriod: { N: '1465862400' },
     isLicensed: { BOOL: true },
     customerName: { S: 'ООО Урал-Интеграция' },
     IVRNumber: { S: '73432861080' },
     callbackNumber: { S: '73432281511' },
     customerID: { S: 'ui-vg-1.ural.croc.ru' },
     appID: { S: 'iCID' },
     orgCode: { N: '306513' },
     showAllEmployees: { BOOL: true },
     greenPeriod: { N: '1464739200' },
     phoneRules: { S: '2000-2100; 5000-5100    ' },
     emailFrom: { S<EMAIL_ADDRESS>},
     postSuffix: { S<EMAIL_ADDRESS>} } }
  dynamoose:model applying virtuals +1ms
  dynamoose:attribute parseDynamo: apiHost : "string" : "api.intellicid.ru" +0ms
  dynamoose:attribute parseDynamo: callbackNumber : "string" : "73432281511" +2ms
  dynamoose:attribute parseDynamo: customerID : "string" : "ui-vg-1.ural.croc.ru" +0ms
  dynamoose:attribute parseDynamo: appID : "string" : "iCID" +0ms
  dynamoose:attribute parseDynamo: customerName : "string" : "ООО Урал-Интеграция" +0ms
  dynamoose:attribute parseDynamo: emailFrom : "string"<EMAIL_ADDRESS>+0ms
  dynamoose:attribute parseDynamo: externalPhoneNumbers : "string" : ["73432281511","73432861080"] +0ms
  dynamoose:attribute parseDynamo: greenPeriod : "number" :<PHONE_NUMBER> +0ms
  dynamoose:attribute parseDynamo: yellowPeriod : "number" :<PHONE_NUMBER> +1ms
May 06 2016 10:41:20 GMT+0000 - error: uncaughtException: Unexpected token o date=Fri May 06 2016 10:41:20 GMT+0000 (UTC), pid=13526, uid=500, gid=500, cwd=/opt/icid/registration, execPath=/usr/local/bin/node, version=v4.4.3, argv=[/usr/local/bin/node, /opt/icid/registration/app.js], rss=46280704, heapTotal=34202976, heapUsed=19918936, loadavg=[0.0029296875, 0.0146484375, 0.04541015625], uptime=11046031
SyntaxError: Unexpected token o
    at parse (native)
    at dedynamofy (/opt/icid/registration/node_modules/dynamoose/lib/Attribute.js:404:14)
    at Attribute.parseDynamo (/opt/icid/registration/node_modules/dynamoose/lib/Attribute.js:467:13)
    at Schema.parseDynamo (/opt/icid/registration/node_modules/dynamoose/lib/Schema.js:80:45)
    at Response.<anonymous> (/opt/icid/registration/node_modules/dynamoose/lib/Model.js:312:14)
    at Request.<anonymous> (/opt/icid/registration/node_modules/aws-sdk/lib/request.js:353:18)
    at Request.callListeners (/opt/icid/registration/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
    at Request.emit (/opt/icid/registration/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/opt/icid/registration/node_modules/aws-sdk/lib/request.js:595:14)
    at Request.transition (/opt/icid/registration/node_modules/aws-sdk/lib/request.js:21:10)

I think that is what you want to see. all objects are parsed fine except for a "BOOL" type.
This quickfix helps with the problem, but thats really not the best option to fix module every time.

OK -- Understand the issue.  Your using the DynamoDB native type BOOL.  BOOL was added to DynamoDB after Dynamoose was created.  Dynamoose expect booleans to be the type S and used JSON.parse to convert 'true' to true.  This will require some thinking on my side to decide how best to handled this without breaking a bunch of existing stuff.

Closing - Tracking adding boolean support in #55


replace beta workloads/RBAC APIs with GA'd APIs

What this PR does / why we need it:
RBAC was GA'd in 1.8 and the core workloads API was GA'd in 1.9
As per the k8s version support matrix, all Kubernetes releases supported by the community charts now support both apps/v1 and rbac.authorization.k8s.io/v1.
Special notes for your reviewer:
I have not individually tested each and every chart if they work with this change; just did a search-and-replace. From initial findings upgrading production charts should not be affected since helm upgrade will continue to use the old API version, so this only kicks in on a fresh helm install.
TODO:

[x] bump chart versions

I fixed up the one linting error related to this change, but it looks like the rest of them are unrelated to this PR. Please let me know if I should make any extra changes (reverting work against deprecated charts, for example)

@bacongobbler as great as this is, we prefer to prefer have changes in each chart submitted as separate PRs (this way we avoid issues where some charts failing CI prevent other chart updates from going through). Do you think you could separate this out?

@bacongobbler I agree with @prydonius. You'll have a hard time getting a huge PR past CI and will have to merge in upstream changes all the time while trying to fix CI issues. I question if we should really make such a global change anyways. You'd also have to update readme files which usually specify the minimum K8s version. Also, while we officially support the current and previous minor versions, a chart maintainer may decide to support older versions. We do have such charts. In any case, we should be nice and get LGTMs by the chart maintainers and not just force this upon all charts across the board.

sounds good. I'm off on vacation until next week but when I'm back, I'll start shipping individual PRs for the charts.

I question if we should really make such a global change anyways.

I would argue that if someone's willing to put in the work then yes. k8s isn't going to support extensions/v1beta1 forever. ;)

In any case, we should be nice and get LGTMs by the chart maintainers and not just force this upon all charts across the board.

that sounds more than fair to me.


Blank white screen on startup

Hey,
First of all thank you for your effort,
I am using Macbook Pro 2018 with latest os version. When i open the app it just shows white screen.

Hi @acukan, thank you for the bug report.
I have fixed it in 1.0.2.
https://github.com/pixel-point/kube-forwarder/releases/tag/v1.0.2

That problem gone, I am testing it now 👍


Hiring Rust Devs for established NFT project on Solana

Hi,
I am the co-founder of Doge Capital - A NFT project on Solana .
https://thedogecapital.com
https://twitter.com/thedogecapital
We are hiring developers proficient in Rust for our ongoing project. Let me know if you are interested. Looking forward to your response.

Good luck,
but this is not the appropriate place to tell it.


target/common: Fix dasm traces truncation when using SnitchSim

When using the verification.py library and SnitchSim to run a simulation then read results from the kernel execution, the IPC thread will crash the whole program once SnitchSim has finished issuing the read commands. This is because the current check for EOF in ipc.cc erroneously checks for EOF before the fread attempt, instead of after the fread attempt. See the following StackOverflow for how this is usually corrected:
https://stackoverflow.com/questions/5431941/why-is-while-feoffile-always-wrong
Because of this erroneous check, the last operation (which is usually a read memory operation) will be doubly executed, causing the attempt to write to and flush rx to fail, since SnitchSim.py will have already closed the pipe and directory. As such, the program crashes and the .dasm traces are never fully written out.
This PR fixes the EOF check in ipc.cc to correctly check for EOF or errors after a read attempt instead of before.

Thanks a lot for your contribution @Raragyay!


Bug Report: deathCounter is never incremented, always at 0

Which target are you using?
[x] Windows
[ ] Linux
[ ] Mac
Explain your issue
The title explains it all. The code straight up never calls deathCounter other than to reset it to 0 and to create it on PlayState.
This makes it so deathCounter does literally nothing but appear on the pause screen

WHATTTT, ITS LITERALLY THE 3RD TIME I ADD THE SUM LINE FOR THE COUNTER WHY DOES IT ALWAYS DISAPPEAR😭😭

code's haunted ig

Code's haunted, call in the Ghostbusters.

I mentioned this already and it was fixed a while ago in a dev repo.
simple fix, idk why it wasn't forked and pr'd here but whatever.
Fix comming whenever new dev builds get sent to main repo


adding new resources from chef-client 14.3.37 with short examples

Added

chocolatey_config
chocolatey_source
powershell_package_source
kernel_module
ssh_known_hosts_entry

Based upon https://discourse.chef.io/t/chef-14-3-37-released/13285

Nice stuff. Thanks

@nmat You're right. Made a hotfix in version 3.3.1.


GH-2189 code cleanup

GitHub issue resolved: #2189
Briefly describe the changes proposed in this PR:

Remove unused imports
Use diamond operator
Add missing Override annotations

PR Author Checklist:

[x] my pull request is self-contained
[ ] I've added tests for the changes I made
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change
[x] every commit has been signed off

Note: we merge all feature pull requests using squash and merge. See RDF4J git merge strategy for more details.

No code changes, just a bit of cleanup

Looks great :) Github CI is happy.

If you are cleaning up develop, can you do the same to master? So we don’t get lots of conflicts next time master is merged into develop.

Sure, I'll wait until after the 3.2 release though ;-)
Just a series of Inspect'n'Transform checks in Netbeans, so it's not much work.

Sure, I'll wait until after the 3.2 release though ;-)
Just a series of Inspect'n'Transform checks in Netbeans, so it's not much work.

I presume we will be merging develop into master for that. So then no need.


update comment for Mash truthiness methods

Resolves #501

I didn't think this change warranted an entry in the changelog, but Travis wants one. Should I add an entry or would you like to overrule Travis?

🚀


version patch not work for alpha/beta

When patch below version:
1.1.1-alpha
It not work

Support for prerelease version has been added.
Please update to version 2.1.0.


Add choco and scoop install commands to README

I'd much rather use a command line tool than directly use the GUI, so list Chocolatey and Scoop as choices.

Closing - no links provided.


Adds windoors for security and the brig.

About the PR
This PR adds windoors (based off the SecureWindoor prototype) that require security access to open. This is necessary for a planned re-mapping of Security to accommodate windoors. Please note that the mapping changes seen below are NOT part of this PR - this is simply the YAML for the windoor itself.
Screenshots

Changelog

:cl:

add: Security windoors for planned mapping rework.

shouldn't there be reinforced windows into the outside of the prison rooms so people outside can see the prisoners?

shouldn't there be reinforced windows into the outside of the prison rooms so people outside can see the prisoners?
and fire locks on both the reinforced tables

The map is not part of this PR, but the answer to why there's no firelocks is because you cannot see the windoors underneath them in mapping mode. The firelocks will be there in the final version of the mapping PR. The lack of exterior windows on the cells was an intentional decision to make it harder to break into them, though that would of course be negotiable as the mapping PR is not final yet.


How to set the ip or hostname to not go through the proxy.

Hi @666asd, I'm afraid that's not supported. PRs welcome if you're interested - this is definitely possible, but it might be quite a lot of work and it's not something I need personally so I'm unlikely to implement this myself.
It depends on your use case, but if you're using an intercepting mitm proxy like HTTP Toolkit, you may be able to use TLS passthrough options and similar as an alternative (to define hostnames within the proxy whose traffic is forwarded untouched, as if it was sent directly).


Fix commented out nsub in EntityArray

The original copy/paste left this entity in a comment. This patch fixes this.

jira issue for this fix: https://issues.apache.org/jira/browse/LANG-1242

Thanks! :+1:


Arithmetic Operators

As the Solution is updated to the repo already : https://github.com/jarvismayur/Hackerrank-Problem-Solutions/tree/main/Python/Arithmetic Operators


⚠ Spryr has degraded performance

In 193a017, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 6941 ms

Resolved: Spryr performance has improved in 81f1772 after 17 minutes.


feat: port MeasureTheory.Lattice

[x] depends on: #3819

This PR/issue depends on:

leanprover-community/mathlib4#3819
By Dependent Issues (🤖). Happy coding!

Merging master to get a clean diff.

bors merge


Journal info

This PR implements a new module, wikidata, that contains a new processor, JournalPublisherProcessor, gathering relationships between journals (using NLM IDs) and publishers (using ISNI IDs) with the new published_by relationship type.
The PubmedProcessor is also updated to yield Journal nodes as well as relationships between publications and journals, with the   new published_in relationship type.
Other changes:

Fixed array delimiter in the cellmarker module

Accompanying PR
See https://github.com/sorgerlab/indra/pull/1416
Outstanding issues

[x] Un-group ~ISSN~ ISNI values, they are currently of the format XXXX XXXX XXXX XXXX. we could ungroup them to 16 characters from the 19 (with the spaces) internally.
[x] Wikidata identifiers are in some nodes as additional data - should they be keyed with a prefix, WD or without? Example: {'wd_id': 'WD:Q123465'} or {'wd_id': 'Q123465'}. See in the code for the _get_journal_nodes() and in comment below.
[x] Include impact factor

The tests failing now do so because they import stuff from indra that is added in https://github.com/sorgerlab/indra/pull/1416

The tests failing now do so because they import stuff from indra that is added in sorgerlab/indra#1416

Once sorgerlab/indra#1416 is merged we can re-run the tests.


Trivial: Make logged time intervals in bootstrap controller positive

Checklist:

[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

@Mergifyio refresh


Setting up Google Analytics

@tobifroe could you please add the following script to the unikube base template?
`

`

@Truthans Something like this would be the clean solution. Would that work for us?

@tobifroe yes, as it looks I'd say this would work.


Can't toggle line comments with default key combo

Pressing Ctrl+/ results in the File Open action instead of the expected Toggle Line Comment. Using the key binding resolver I can see that pressing Ctrl-/ results in the combination keys being detected as ctrl-o for whatever reason. The bindings in the /usr/share/atom/resources/app/keymaps/linux.json file are correct. I don't have a user defined action for that shortcut.
This may be a problem with my specific keyboard, since it's a Mac aluminium keyboard model A1243. However, in every other application ctrl-/ doesn't get detected as ctrl-o and even in Atom I can use the / key to type an actual /, so I have no idea how that is being turned into an o when combined with ctrl.
Overriding the shortcut to ctrl-shift-/ results in the correct behavior of toggling line comments.
System: Ubuntu 14.04 x64, Atom 0.152.0, Portuguese keyboard layout.

I was having a similar issue in Atom with ctrl-/ not responding until I changed script from "auto detect" to html

problem with latinamerican keyboard, we need to change ctrl+shif+7, it don work with /


shim v2: should support containerd/rust-extensions.

If we set up [plugins." io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
field, rust shim will get an error but goshim will not. This is because if we use
goshim, containerd will send the Options struct in oci.pb.go, but if we use rust shim,
containerd will send the Options struct in api.pb.go. The Options struct in oci.pb.go
will use the proto method to send all the fields, but api.pb.go will use toml to send
all the fields. Rust shim deal with the input from containerd using proto method, so
containerd should use oci.pb.go's Options struct when we use rust shim.

@mxpv

This doesn't seem like it would be the only way to solve the problem and isn't defining a new class of containerd plugin

This is because if we use goshim, containerd will send the Options struct in oci.pb.go, but if we use rust shim, containerd will send the Options struct in api.pb.go.

Can you explain this one a little more?

Configure [plugins." io.containerd.grpc.v1.cri".containerd.runtimes.runc.options] in the containerd configuration file and configure runtime_type = "io.containerd.runc.v2-rs" in the configuration file.
For example:
        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
          runtime_type = "io.containerd.runc.v2-rs"

          [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
            BinaryName = ""

Starting a container with the crictl command will fail because runtime_type = "io.containerd.runc.v2-rs" will use the code of the default branch in the function getRuntimeOptionsType(t string) which return &runtimeoptions.Options{}. &runtimeoptions.Options{} is what I mean api.pb.go's struct Options. And the correct one should be return runcoptions.Options{} which is what I mean oci.pb.go's struct Options, so that rust shim can parse Options correctly.
@dmcgowan

@zzzzzzzzzy9 rust-extensions (and runc rust shim in particular) aim to be a drop in replacement. Do you think we can fix this on rust shim side instead?

It's hard to fix this on rust shim side.
    let mut data: Vec<u8> = Vec::new();
    std::io::stdin()
        .read_to_end(&mut data)
        .map_err(io_error!(e, "read stdin"))?;

    if !data.is_empty() {
        let opts =
            Any::parse_from_bytes(&data).and_then(|any| Options::parse_from_bytes(&any.value))?;

        if !opts.shim_cgroup.is_empty() {
            add_task_to_cgroup(opts.shim_cgroup.as_str(), pid)?;
        }
    }

This is where the error return in rust shim. parse_from_bytes is the method of protobuf, I don't think change this is a good way to fix this. It's much easier in containerd side.

@zzzzzzzzzy9 I was wondering more why runtime_type = "io.containerd.runc.v2-rs" rather than runtime_type = "io.containerd.runc.v2".  I would have expected the path to differ but the type to be the same.

runtime_type = "io.containerd.runc.v2-rs" means use containerd/rust-extensions shim, this shim binary name is containerd-shim-runc-v2-rs, so, runtime_type should be io.containerd.runc.v2-rs. The more infomations can see in https://github.com/containerd/rust-extensions

@zzzzzzzzzy9 In this case, the shim implementation is different but the type should be the same.


Change license to Apache 2

I'm not sure if this is the right change to make, let's discuss it.  The edX policy is that code making up edx.org is AGPL, but that tooling and other non-edX-specific code (especially code that might be useful outside of the Open edX world) should be licensed with Apache 2.

Sounds good, @nedbat. The only concerns I have are (this is more for others/posterity, since we have already talked a little about this):

A script in this repo is already licensed (https://github.com/edx/jenkins-configuration/blob/master/src/main/groovy/3shutdownCLI.groovy)
The tooling makes direct use of Jenkins APIs and code snippets. Jenkins itself has the MIT licensen (https://github.com/jenkinsci/jenkins/blob/master/LICENSE.txt)
I just wanted to make sure that this won't indirectly conflict with anything in the apache license.

@estute These are good questions.  I've added a sentence to the top of NOTICE, "Except where otherwise noted, this work is:".
It's find to combine MIT and Apache, they are both liberal open source licenses.


Linter

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.462%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
347

Relevant Lines:
384

💛  - Coveralls


[ALLUXIO-1766] @ReturnType moved after @Path in FileSystemMasterRestS…

https://alluxio.atlassian.net/browse/ALLUXIO-1766

ok to test

Can one of the admins verify this patch?

LGTM


 After using F5 the error is gone and the piechart is shown.
Stacktrace:
Maximum call stack size exceeded RangeError: Maximum call stack size exceeded
at Object.toString ()
at http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171196
at Object.r [as isMergeableObject] (http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171292)
at http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171752
at s (http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171932)
at o (http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171434)
at http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171918
at Array.forEach ()
at http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171841
at s (http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171932)

Hi Jaap
Could you please add some more details? A minimalistic test project is
preferred. If that is not possible, and you would like some support, that
please you create a ticket via support.mendix.com
Cheers Andries
On Tue, May 14, 2019, 11:06 Jaap01<EMAIL_ADDRESS>wrote:

Maximum call stack size exceeded RangeError: Maximum call stack size
exceeded when using the piechart. After using F5 the error is gone and the
piechart is shown.
Stacktrace:
Maximum call stack size exceeded RangeError: Maximum call stack size
exceeded
at Object.toString ()
at
http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171196
at Object.r [as isMergeableObject] (
http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171292
)
at
http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171752
at s (
http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171932
)
at o (
http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171434
)
at
http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171918
at Array.forEach ()
at
http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171841
at s (
http://localhost:8080/widgets/com/mendix/widget/custom/PieChart/PieChart.js?636934243162194841:1:171932
)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mendixlabs/charts/issues/79?email_source=notifications&email_token=ABTJZDLVXOHTJTMDLDJI2F3PVJ6KDA5CNFSM4HMX2FAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GTTZYOA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABTJZDKATP7S6UHOX7JWJADPVJ6KDANCNFSM4HMX2FAA
.

Closed, due to missing details. If this issue is still relevant, please open a ticket at support.mendix.com with good sample project. Cheers, Andries


PullRequestReleaseNotes -init Requires a token

Hello,
I tried to initialize my config file using the -init to generate the sample yml file but it seems that the provider token is mandatory here to generate the file.
Is it expected ?

@darknoon29 thanks for your report. I will look into it, it doesn't sound like you should be forced to provide a token to init the config.

@darknoon29 the issue is resolved in v1.2.3 which will be available shorty.


Guard GCC pragmas

This PR adds preprocessor checks to only use GCC pragmas with compatible compilers.
Fixes #2924

Coverage remained the same at 100.0% when pulling e20f3f95eb1b5485c37e079bbf18d58b1d49f607 on issue2924 into 57d31d1b83c5a84b7760f862d30239015fc690f7 on develop.

Just curious—there are other #pragma GCC s which are guarded on the __clang__ variable instead of __GNUC__. I think clang defines the latter, but gcc might not define the former. Would it make sense to change those to __GNUC__ as well?

Just curious—there are other #pragma GCC s which are guarded on the __clang__ variable instead of __GNUC__. I think clang defines the latter, but gcc might not define the former. Would it make sense to change those to __GNUC__ as well?

The only other place is this:
// disable documentation warnings on clang
#if defined(__clang__)
    #pragma GCC diagnostic push
    #pragma GCC diagnostic ignored "-Wdocumentation"
#endif

This pragma is meant for Clang, because only Clang has a -Wdocumentation warning. If we would change it to __GNUC__, then GCC would be confused about this unknown flag.

@nlohmann What is missing to avoid things like this with the CI? warning-free tests on all platforms?

@nlohmann What is missing to avoid things like this with the CI? warning-free tests on all platforms?

I currently set no specific warning flag for MSVC. Is there something comparable to -Werror which is still pragmatic for MSVC?

/WX for warnings as errors and /W4 for maximum warnings. Maybe you can scavenge something from https://github.com/nlohmann/json/pull/2245/commits/0b8644c452d864dc88d801ce55b47207051857d7.

I'll give it a try, see https://github.com/nlohmann/json/pull/2930 - feedback more than welcome!


[WIP] fix 105 - sequence points when "let rec" is used, plus other debug stepping issues

Addressing http://github.com/Microsoft/visualfsharp/issues/105 - an old issue with debug stepping when inner functions are present.
A bunch of other issues associated with stepping through closures are also addressed.
For those reviewing: Emitting sequence points correctly from the TAST is a PITA.  It is particularly complicated by

inlined code (which results in additional "sticky" let bindings)
other constructs that implicitly introduce additional compiler-generated "let" bindings

The code to do this is a mess, but the behavior is pinned down by a load of code generation tests.  Some of these are updated in this PR (and some unused baselines are removed).
This PR also adds a manual "walkthrough" for debug stepping in tests\walkthroughs\DebugStepping\TheBigFileOfDebugStepping.fsx.  This is a manual test case, see instructions at the top of the file, we can use this to assess debug stepping quality from time-to-time.

I got this failure, it looks like a flaky test
+++ Conformance\Expressions\SyntacticSugarAndAmbiguities (SyntacticSugar01) +++

OK, now this is green and is ready for review.  See the updated notes in the PR description.

This is ready to merge

One test failed, looks unrelated to PR (it has passed prior to integration)

+++ Conformance\InferenceProcedures\NameResolution\AutoOpen (Module01.fs) +++
Failed to Find Any Target:
FAIL


UnpicklingError: invalid load key, 'v'.

When running act_scales = torch.load('../act_scales/opt-13b.pt') it reported error：
Traceback (most recent call last):
File "/opt/TrySmooth/main.py", line 62, in
act_scales = torch.load('/opt/TrySmooth/act_scales/opt-13b.pt')
File "/opt/conda/lib/python3.8/site-packages/torch/serialization.py", line 713, in load
return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
File "/opt/conda/lib/python3.8/site-packages/torch/serialization.py", line 920, in _legacy_load
magic_number = pickle_module.load(f, **pickle_load_args)
_pickle.UnpicklingError: invalid load key, 'v'.
I wonder if there‘s anybody else encountered this error and wills to help.

I encountered the same error but don't have a solution yet.

To use '../act_scales/opt-13b.pt', one should do 'git lfs pull' first, but it is not possible :sweat_smile: (see issue https://github.com/mit-han-lab/smoothquant/issues/33)

I encountered the same error, how to solve this problem

Brother Alvant pointed out that this is already not solvable, it seems git lfs donnot allow such amount of data without the maintainer paying enough(out of quota). The act_scales might be generated by ourselves, and we can also refer to smoothquant-main\examples\smoothquant_opt_real_int8_demo.ipynb, which directly loads the quantized model and does evaluation both on accuarcy and latency. Isn't that more appealing?

Alvant 兄弟指出，这已经无法解决，似乎 git lfs 不允许在维护者支付足够费用（超出配额）的情况下提供如此大量的数据。act_scales可能是我们自己生成的，我们也可以参考 smoothquant-main\examples\smoothquant_opt_real_int8_demo.ipynb，它直接加载量化模型，并对精度和延迟进行评估。这不是更吸引人吗？

Hi, furry
I have met the same problem.
When process the code act_scales = torch.load('/lizhiwei/smoothquant/act_scales/opt-1.3b.pt')
it comes out
UnpicklingError: invalid load key, 'v'.
So, does it mean that the smoothquant-main\examples\smoothquant_opt_demo.ipynb is not usable now? This demo is broken?

Here I created a colab script based on the code of this project, using opt-1.3b for example.
https://colab.research.google.com/drive/1PP42K9OekoXfXpoXYDhrMUa_xdZY3XR9?usp=sharing

Hi,
Thank you for raising this issue! We have uploaded our activation scales on Huggingface.
Best,
Guangxuan


propagatedUserEnv could be extended to better specify how to integrate the package into the environment

Issue description
Currently, propagatedUserEnv is used in many desktop-related packages, to ensure that the system or user environment has packages that are needed at runtime. In most cases the application locates such dependencies by searching in profile directories (often assisted by environment variables such as XDG_DATA_DIRS and PATH).
However, whether the correct files are linked into the environment depends on how the environment is generated, especially on the pathsToLink used in buildEnv. This is currently not addressed well. For example, system-path.nix (which builds /run/current-system/sw) hardcodes a bunch of default entries for pathsToLink, and the Plasma NixOS module just adds /share to pathsToLink (which affects the entire system environment, not just Plasma things). One can grep the NixOS modules to see all cases where modules set environment.pathsToLink to ensure that some part of some packages is linked in.
nix-env and other user environment managers also lack precise information about which paths need to be linked in. It seems to me that nix-env uses pathsToLink=["/"] but I am not 100% sure. Which ironically sometimes results in an app running fine when installed with nix-env but not in the system environment (because some needed paths were not linked).
Proposal
First, I don't like how propagatedUserEnv is implemented through shell scripts and nix-support/propagated-user-env-packages. Using passthru would be more elegant and would make it simpler to support including more detailed information about environment dependencies. So if we make improvements in this area, it should be a new system that uses passthru.
It should be possible for a package to specify, via passthru, that it requires specific paths from specific packages to be linked in the environment. The buildEnv implementation would look at these specifications and ensure that the requested paths are linked. Paths not requested would not be linked if not required, e.g. a package requested in this way could end up with only /share linked and not /bin even if it has something in /bin.
It could look like this in a package definition:
passthru = {
    environmentDependencies = [
        { package = some_package; pathsToLink = [ "/share" ]; }
        { package = another_package; pathsToLink = [ "/bin" ]; }
    ];
};

From the perspective of buildEnv, these specifications are not recursive. In particular, buildEnv only considers the environmentDependencies of packages that are requested to be in the environment at the top level. Automatic propagation of environmentDependencies of a library to applications depending on it could be implemented via mkDerivation and additional passthru attributes (without buildEnv having to deal with this).
The general idea of a package specifying how to integrate it into the environment could be extended to other kinds of specifications, like which environment variables need to be set (if perhaps the environment would someday be responsible for generating executable wrappers).

It would be nice if we considered abstract dependencies (for example icon theme) as well.

It would be nice if we considered abstract dependencies (for example icon theme) as well.

I suppose that it would be up to helpers and conventions. buildEnv probably shouldn't know about such specific things, but should receive sufficient information to know what to link where.
By the way, I have recently learned that there are actually two buildEnv implementations, the Perl one in nixpkgs (pkgs/build-support/buildenv) and the C++ one that is built into Nix. The latter one is used by nix-env for managing channels, managing profiles in /nix/var/nix/profiles (tracking the current and previous generations), and managing the content of user profiles (nix-env -i/-e). The former two uses are pretty basic (they just manage symlinks in a directory), so they would not be affected by any extensions of the buildEnv concept. However management of the user profile (content of ~/.nix-profile) is a problem here, as any feature implemented in the nixpkgs buildEnv would not be available for nix-env user profiles. It is also a technical problem because passthru and meta attributes are unavailable in the context of that builtin buildEnv code (that's why nix-support/propagated-build-inputs exists - only so that the builtin buildEnv can find those propagated packages).
So I am hoping that nix-env -i/-e gets deprecated soon, to enable us to make improvements in buildEnv without being held back by nix-env.


Execute Query: Network error: GraphQL Error for HTTP 200

When I execute any query like the one below in VSCode, the query is correctly executed, it always prepends "Error: Network error: GraphQL Error:"

We use this GraphQL-Dotnet API since 2 years without any problem. From JS with lokka and graphql-request.
So I have no idea where that Network error comes from.
Expected Behavior
When Executing a query I would expect to so only
{
  "data": {
    "version": "0.1"
  },
  "status": 200
}

Actual Behavior
But what I get is
Error: Network error: GraphQL Error: {
  "data": {
    "version": "0.1"
  },
  "status": 200
}

Steps to Reproduce the Problem Or Description
Sadly I have no idea how I can provide such in my case.
Specifications

VSCode Version: 1.28.2

Logs Of TS Server || GraphQL Language Service
It only prints "NetworkHelper: operation: query"

Just out of curiosity, could you try to have your server return
{
  "data": {
    "version": "0.1"
  }
}

instead? (no extra status property).
Is the network error still printed in this case?

Well the interesting point is that this property does not come from our api. Ive checked that, but our graphql server only returns the data prop.

it could be that your server is configured to respond to invalid graphql queries with a 200 rather than a 403. there was a bug with rendering non-200 requests, now all request responses are rendered in the execution results pane!


commit_version_bump broken when a project's Settings.bundle is in a group

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I recently had to fix a problem in the settings_bundle plugin that breaks commit_version_bump because the same poor assumptions are reflected in code I'm responsible for there: https://github.com/fastlane/fastlane/blob/master/fastlane/lib/fastlane/actions/commit_version_bump.rb#L215. I'll submit a PR to fix, but I'd like to do something better than just repeat the plugin logic and avoid having to modify Fastlane proper in the future for a plugin error. Also, it's possible for settings bundles to have nonstandard names, like MySettings.bundle, which I also recently implemented in the plugin. While fixing this issue it might be best to think more generally.
I have two proposals:

Add an option to commit_version_bump like :include or :extra_files to allow anything else to be included explicitly as part of the version bump.
Pass the modified files in the lane_context from any action that modifies files under SCM, e.g. SharedValues::MODIFIED_FILES. This could be done across the board for actions including increment_version_number and increment_build_number, which would simplify the implementation of commit_version_bump. Or this state could simply be used by plugins without changes to any other actions.

Personally I think I prefer option 2 and in the absence of any feedback will soon submit a PR along those lines. I'm delaying the next release of the plugin for this purpose.
Complete output when running fastlane, including the stack trace and command used
The lane used to test:
lane :test do
  xcodeproj = "examples/SettingsBundleExample/SettingsBundleExample.xcodeproj"

  increment_build_number xcodeproj: xcodeproj
  update_settings_bundle xcodeproj: xcodeproj,
                         key: "CurrentAppVersion",
                         value: ":version (:build)"
  update_settings_bundle xcodeproj: xcodeproj,
                         key: "BuildDate",
                         value: Time.now.strftime("%B %-d, %Y")
  commit_version_bump xcodeproj: xcodeproj, settings: true
end

[jdee@Jimmy-Dees-MacBookPro settings-bundle (tmp)]$ bundle exec fastlane test
+---------------------------------+---------+------------------------+
|                            Used plugins                            |
+---------------------------------+---------+------------------------+
| Plugin                          | Version | Action                 |
+---------------------------------+---------+------------------------+
| fastlane-plugin-settings_bundle | 1.2.0   | update_settings_bundle |
+---------------------------------+---------+------------------------+

[17:16:05]: -------------------------------------------------
[17:16:05]: --- Step: Verifying required fastlane version ---
[17:16:05]: -------------------------------------------------
[17:16:05]: Your fastlane version 2.36.0 matches the minimum requirement of 2.28.2  ✅
[17:16:05]: ------------------------------
[17:16:05]: --- Step: default_platform ---
[17:16:05]: ------------------------------
[17:16:05]: Driving the lane 'test' 🚀
[17:16:05]: ------------------------------------
[17:16:05]: --- Step: increment_build_number ---
[17:16:05]: ------------------------------------
[17:16:05]: $ cd /Users/jdee/github/jdee/settings-bundle/examples/SettingsBundleExample && agvtool next-version -all && cd -
[17:16:06]: ▸ Setting version of project SettingsBundleExample to:
[17:16:06]: ▸ 2.
[17:16:06]: ▸ Also setting CFBundleVersion key (assuming it exists)
[17:16:06]: ▸ Updating CFBundleVersion in Info.plist(s)...
[17:16:06]: ▸ Updated CFBundleVersion in "SettingsBundleExample.xcodeproj/../SettingsBundleExample/Info.plist" to 2
[17:16:06]: ▸ /Users/jdee/github/jdee/settings-bundle
[17:16:07]: ------------------------------------
[17:16:07]: --- Step: update_settings_bundle ---
[17:16:07]: ------------------------------------
[17:16:07]: ------------------------------------
[17:16:07]: --- Step: update_settings_bundle ---
[17:16:07]: ------------------------------------
[17:16:07]: ---------------------------------
[17:16:07]: --- Step: commit_version_bump ---
[17:16:07]: ---------------------------------
[17:16:07]: $ git rev-parse --show-toplevel
[17:16:07]: ▸ /Users/jdee/github/jdee/settings-bundle
[17:16:07]: $ git diff --name-only HEAD
[17:16:07]: ▸ examples/SettingsBundleExample/Settings.bundle/Root.plist
[17:16:07]: ▸ examples/SettingsBundleExample/SettingsBundleExample.xcodeproj/project.pbxproj
[17:16:07]: ▸ examples/SettingsBundleExample/SettingsBundleExample/Info.plist
[17:16:07]: $ git ls-files --other --exclude-standard
+------------------+------+
|      Lane Context       |
+------------------+------+
| DEFAULT_PLATFORM | ios  |
| PLATFORM_NAME    |      |
| LANE_NAME        | test |
| BUILD_NUMBER     | 2    |
+------------------+------+
[17:16:11]: Found unexpected uncommitted changes in the working directory. Expected these files to have
changed:
examples/SettingsBundleExample/SettingsBundleExample.xcodeproj/project.pbxproj
examples/SettingsBundleExample/SettingsBundleExample/Info.plist
examples/Settings.bundle/Root.plist.
But found these actual changes:
examples/SettingsBundleExample/Settings.bundle/Root.plist
examples/SettingsBundleExample/SettingsBundleExample.xcodeproj/project.pbxproj
examples/SettingsBundleExample/SettingsBundleExample/Info.plist.
Make sure you have cleaned up the build artifacts and
are only left with the changed version files at this stage in your lane, and don't touch the
working directory while your lane is running. You can also use the :force option to bypass this
check, and always commit a version bump regardless of the state of the working directory.

+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 3    | increment_build_number              | 2           |
| 4    | update_settings_bundle              | 0           |
| 5    | update_settings_bundle              | 0           |
| 💥   | commit_version_bump                 | 0           |
+------+-------------------------------------+-------------+

[17:16:11]: fastlane finished with errors

[!] Found unexpected uncommitted changes in the working directory. Expected these files to have
changed:
examples/SettingsBundleExample/SettingsBundleExample.xcodeproj/project.pbxproj
examples/SettingsBundleExample/SettingsBundleExample/Info.plist
examples/Settings.bundle/Root.plist.
But found these actual changes:
examples/SettingsBundleExample/Settings.bundle/Root.plist
examples/SettingsBundleExample/SettingsBundleExample.xcodeproj/project.pbxproj
examples/SettingsBundleExample/SettingsBundleExample/Info.plist.
Make sure you have cleaned up the build artifacts and
are only left with the changed version files at this stage in your lane, and don't touch the
working directory while your lane is running. You can also use the :force option to bypass this
check, and always commit a version bump regardless of the state of the working directory.

[INSERT OUTPUT HERE]
Environment
🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.12.5

Ruby
2.4.0

Bundler?
true

Git
git version 2.11.0 (Apple Git-81)

Installation Source
~/.rvm/gems/ruby-2.4.0/bin/fastlane

Host
Mac OS X 10.12.5 (16F73)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.4.0/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.3.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
fastlane_version "2.28.2"

default_platform :ios

desc "Test lane to update SettingsBundleExample"
lane :test do
  xcodeproj = "examples/SettingsBundleExample/SettingsBundleExample.xcodeproj"

  increment_build_number xcodeproj: xcodeproj
  update_settings_bundle xcodeproj: xcodeproj,
                         key: "CurrentAppVersion",
                         value: ":version (:build)"
  update_settings_bundle xcodeproj: xcodeproj,
                         key: "BuildDate",
                         value: Time.now.strftime("%B %-d, %Y")
  commit_version_bump xcodeproj: xcodeproj, settings: true
end

desc "Test lane to update SettingsBundleLibraryExample"
lane :library_test do
  xcodeproj = "examples/SettingsBundleLibraryExample/SettingsBundleLibraryExample.xcodeproj"
  # Rather than passing the xcodeproj argument to all invocations of update_settings_bundle
  ENV["SETTINGS_BUNDLE_XCODEPROJ"] = xcodeproj

  increment_build_number xcodeproj: xcodeproj
  update_settings_bundle target: "SettingsBundleLibraryExample",
                         key: "CurrentAppVersion",
                         value: ":version (:build)"
  update_settings_bundle target: "SettingsBundleExampleFramework",
                         key: "CurrentFrameworkVersion",
                         value: ":version (:build)",
                         file: "Framework.plist"
  update_settings_bundle key: "BuildDate",
                         value: Time.now.strftime("%B %-d, %Y")
end

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.36.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-settings_bundle
1.2.0
🚫 Update available

Loaded gems

Gem
Version

did_you_mean
1.1.0

io-console
0.4.6

rake
12.0.0

plist
3.3.0

CFPropertyList
2.3.5

claide
1.0.1

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.4.4

fastlane-plugin-settings_bundle
1.2.0

coderay
1.1.1

method_source
0.8.2

slop
3.6.0

pry
0.10.4

rspec-support
3.6.0

rspec-core
3.6.0

diff-lcs
1.3

rspec-expectations
3.6.0

rspec-mocks
3.6.0

rspec
3.6.0

parallel
1.11.2

ast
2.3.0

parser
<IP_ADDRESS>

powerpack
0.1.1

rainbow
2.2.2

ruby-progressbar
1.8.1

unicode-display_width
1.2.1

rubocop
0.49.1

public_suffix
2.0.5

addressable
2.5.1

babosa
1.0.2

bundler
1.15.0

colored
1.2

highline
1.7.8

commander-fastlane
4.4.4

dotenv
2.2.1

excon
0.56.0

multipart-post
2.0.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
<IP_ADDRESS>

fastimage
2.1.0

gh_inspector
1.0.3

jwt
1.5.6

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

hurley
0.2

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.0.15

representable
2.3.0

retriable
2.1.0

google-api-client
0.9.28

json
2.1.0

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

slack-notifier
1.5.1

terminal-notifier
1.8.0

terminal-table
1.8.0

tty-screen
0.5.0

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.2.8

xcpretty-travis-formatter
0.0.4

rspec-simplecov
0.2.2

docile
1.1.5

simplecov-html
0.10.1

simplecov
0.14.1

generated on: 2017-06-01

The bug is fixed by the PR that was merged. Another PR will follow with possible enhancements. Closing.


[Issue] JSON validation for OS specific hooks

[X] Make sure you've installed the latest version using instructions in the wiki

Output from azd version
azd version 0.6.0-beta.2 (commit https://github.com/Azure/azure-dev/commit/c4a201e55a13eba77f9037b296a90e0f81b00dbe)
Output from az version
n/a - not relevant for my scenario
Describe the bug
When adding OS dependent configurations to the azure.yaml file, VSCode depicts an error due to a missing run

This is due to the structure of the JSON schema that requires a run on top-level of the hook. According to the documentation the syntax like:
name: todo-nodejs-mongo
metadata:
  template<EMAIL_ADDRESS>hooks:
  preinit:
    posix: # Only runs on Posix environments
      shell: sh
      run: echo 'Hello'
   windows: # Only runs on Windows environments
     shell: pwsh
     run: Write-Host "Hello

is valid.
To Reproduce
Add a OS dependent configuration to your azure.yaml file.
Expected behavior
The validation should not show any error when adding OS specific configurations even if a run on top-level is missing
Environment
VSCode 1.75.1
Additional context
n/a

@wbreza can you take a look and triage it?


    docs: fixed typo of preserved

New updates on head repo.
https://github.com/vuejs/docs/commit/b9a640611d5c5f65b5babe265f023a986d6de874

resolved 6f3f322bebcc627f3001196774f92decd8950fa2


Resolved fields do not get filtered by the permission system

There is still a problem with how resolvers and the permission system interact, which I think I brought up a while ago.
Here for example is a schema field of mine:
{
    fieldName: 'IPs',
    fieldSchema: {
      type: Array,
      optional: true,
      group: formGroups.banUser,
      canRead: ['sunshineRegiment', 'admins'],
      resolveAs: {
        type: '[String]',
        resolver: (user, args, context) => {
          const IPs = context.LWEvents.find({userId: user._id, name: 'login'}, {fields: context.Users.getViewableFields(context.currentUser, context.LWEvents), limit: 10, sort: {createdAt: -1}}).fetch().map(event => event.properties && event.properties.ip);
          const uniqueIPs = _.uniq(IPs);
          return uniqueIPs
        },
        addOriginalField: false,
      },
    }
  },

  {
    fieldName: 'IPs.$',
    fieldSchema: {
      type: String,
      optional: true,
    }
  }

Based on how things usually work, one would expect that you can't resolve the IPs field if you are not either in the group admins or sunshineRegiment. However, any user can actually resolve this field, which has caused some security issues in my app. Changing this behavior to make it so that resolved fields by default get filtered out if the permissions are specified.

You'd want to modify the code here to respect the checks: https://github.com/VulcanJS/Vulcan/blob/c4cec6a0122c2386a5f4a22e0f9942f2d5a8fb83/packages/vulcan-lib/lib/modules/graphql.js#L175

OK so this helped me clarify my understanding of how resolved fields work. It makes sense when you think about it, but I just hadn't really paid enough attention before!
So resolver will always run, and like someone said elsewhere they get added after the Vulcan code runs. So it's not something we can control.
However we can control the code of the resolver function. So for example if your IPs resolver should only return a value if the user has access to the IPs field then just wrap your resolver in a if (document.IPs) {...} block (where document is the current user, movie, post, etc. i.e. the first argument of the resolver function).
So this isn't really a bug, more of a consequence of how GraphQL works.
The reason you ran into the bug in this specific case is because your IPs resolver doesn't actually make use of the value of the IPs field, and thus keeps on returning a value even when said field was restricted.
I'll close this for now but feel free to reopen it if I missed something.

I agree that this makes sense given the architecture, but I think it is really surprising for someone who hasn't thought about the architecture for a long time, and the consequences are really bad if you mess up your permission system.
I think wrapping the resolver in an access check in the file that justin posted below is a much better behavior here.

It sounds right to me and more intuitive. You may need stricter permissions for nested fields of the resolved objects but never lighter permissions.
It still allows fully custom behaviour as you can always make your permissions less strict and enforce them by yourself or handle failure case in a specific way (like trigger an alert to an admin for very sensitive data etc.).


Update & Publish renderer extension and use it in Python extension for Native Notebooks

https://github.com/microsoft/vscode-notebook-renderers

[ ] Review Extension information

name, id, description, license
readme
contribution doc

[ ] We need to update the renderer API in renderer extension as we did here:
https://github.com/microsoft/vscode-python/pull/13665/files
Changes related to the following need to be applied to renderer extension:

index.tsxhttps://github.com/microsoft/vscode-python/pull/13665/files#diff-e9d196ad86eab236c4a11ac079541dc7
package.jsonhttps://github.com/microsoft/vscode-python/pull/13665/files#diff-b9cfc7f2cdf78a7f4b91a753d10865a2

[ ] After publishing extension, remove related renderer code from DS code (from Python extension)

Closed in favor of #1423 (epic)


Add Vim logo (1023 bytes)

Used a hack to make the strokes appear to align to the outside of the polygons thanks to a blog post by Alex Chan.
Link: https://alexwlchan.net/2021/03/inner-outer-strokes-svg/

Ironically, I edited the SVG with vim after running svgcleaner (to add the ARIA attributes) and vim added a newline making it one byte too big!

Updated this SVG to match standard formatting.


Documentation Generation

I'm currently writing the documentation generation tool for Odin. So if you pass it a file with valid syntax, it will generate the documentation for the file from just its associated comments.
So a a procedure declaration with a group of comments above it will be associated with that group of comments.
// foo_bar does amazing things beyond your wildest dreams
// It does this by doing magic behind your very eyes
proc foo_bar(name: string, loc = #caller_location) -> int {
    return 42;
}

What format would be preferable for documentation?

Markdown
HTML
Custom format
Other?

Is there a way to differentiate doc comments from comments that shouldn't be in docs?

Some languages goes with three slashes for documentation comments and two for regular comments.
Doing it directly in HTML allow for easy online docs. Though Markdown is better for GitHub project, and will easily convert to HTML if that's needed. So Markdown +1 from here!

@ratchetfreak There will not be. I don't personally like this as one of the points of comments is for documentation. Why should there be a completely different way to handle this specific case?
They way it will work is that it will grab the leading comment before the declaration and the line comment after the semicolon (for specific declarations).
Subsequent lines of text will be considered part of the same paragraph (like markdown) so if you want a line break, leave an empty comment to separate paragraphs.
I want comments in code to be just as documenting as the generated documentation.

I say +1 for markdown too though will markdown in the comment be stripped our can you embed markdown in your comments?

Markdown is more sane than HTML or XML or any *ML ....

Markdown +1
You have browser extensions to support markdown in the browser.
The one I tested for chrome works (you have to enable for files in options):
https://github.com/simov/markdown-viewer#advanced-options
It might be good to make people aware of that. Prior to this day I always looked at md files in simple text editors that don't support the format.

Also please generate links to other files of the documentation.
For example, here you can click on String as well to go to the documentation of String:
http://processing.github.io/processing-javadocs/core/processing/core/PApplet.html

Like @bdoner said with 3 slashes, java has /** instead of /* for example. I don't really care what it looks like but I think it would be good to have it more specific then just taking the comments above a proc.
-some IDE's highlight comments for documentation in a different color
-it makes it easier to search threw documentation
-what if you're comment is not meant to go in the doc?

Rust's doc gen is pretty good, I think they use markdown as well

A bit late to the party, but you might really want to look at how Rust does it.
Just click the [src] button in any part of the doc to see the actual source, including their documentation comments.
It's Markdown, and examples in documentation are automatically tested by the compiler when running cargo test. Also you can insert lints enabling (or disabling) warnings about undocumented items.
Also documentation comments (i.e with /// for the next item or //! for the root item) are actually just syntactic sugar for regular metadata attributes (just like #[inline] and friends).
There's room for improvement, for instance referencing items such as parameters, types and modules is a bit hackish and not convenient to do. As a result most people (including me) just write them between ticks ('`') to show that it's code, but obviously it's not satisfying.
Anyway, one should pick a solution which makes it super easy and super fun to write good-looking documentation for anything. XML is certainly not one. Markdown might be, but has its annoyances. Putting everything between ticks gets old fast, and most of the syntax is useless for documentation of code.
Perhaps a small markup language designed for this purpose could do the trick.

I am closing this issue as it's very very old and a newer one with newer details a better idea.


conda:// paths do not work (conda executable not found) when conda is not installed for All Users

What it says in the title

More likely, if conda was not added to the windows path during installation.


remove "removeCanvaskit" function

When https://github.com/flutter/engine/pull/26059 lands we can remove the "removeCanvaskit" function that was added in https://github.com/dart-lang/dart-pad/pull/1895.

This is making me wish GitHub had a snooze button for issues. 😄


Fixed #25654: Added support for GEOSUnaryUnion to `GEOSGeometry'.

I copied description of unary_union from GEOS.
Docs test fails because of spelling:

Unioning
noding
linework
I would be grateful if someone could help replace these words or confirm that they are right.

Those terms are okay to add to the word list.

merged in 034dfbfc057b6090f9f2589731b8f58a70e4f885, thanks!


fix(kit): icon in date-related components occupies space when hidden

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows Conventional Commits
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[x] Feature
[ ] Refactoring
[ ] Code style update
[ ] Build or CI related changes
[ ] Documentation content changes

What is the current behavior?
Closes #2960
What is the new behavior?
Icon is completely hidden when removed via DI
Does this PR introduce a breaking change?

[ ] Yes
[x] No

I forgot to add docs for tuiIsPresent pipe, will do it now

moved tuiIsPresent pipe to a separate PR #3002

@splincode @waterplea so, everything got a lot simpler. I hope no one will come with an idea of hiding the icon using an empty string, and if they do, I wouldn't consider the result a bug on the Taiga side. so we're free to write as you suggested:
[tuiTextfieldIcon]="calendarIcon && iconContent"

as for this one
[tuiTextfieldIcon]="calendarIcon ? calendarIcon : null"

it can easily be reverted to the original
[tuiTextfieldIcon]="calendarIcon"

@splincode since Alex is unavailable now, can we get someone else involved to get two approvals?

[tuiTextfieldIcon]="calendarIcon"

[tuiTextfieldIcon]="calendarIcon"

@splincode what do you mean?

@theorlovsky sorry, I mean use [tuiTextfieldIcon]="calendarIcon && iconContent"

@theorlovsky sorry, I mean use [tuiTextfieldIcon]="calendarIcon && iconContent"

@splincode I already use it

@theorlovsky sorry, it's good now

@splincode how can we get a second approval here?

@vladimirpotekhin @nsbarsukov fyi


Update README.md

I added a configuration tutorial to the README to provide users with a clear and permanent written reference. While this information is available in the "Settings" tab of the interface, having written documentation in the README allows for quick reference and aids understanding for those who prefer a textual approach.

Thank you for your contribution!


Refactor Model Interface to not use a tuple for its forward function

TF SavedModel interface fails when we use a tuple as the parameter to the forward() function.
Currently we do:
@tf.function(jit_compile=True)
def forward(self, inputs: Tuple[Any, ...]) -> Tuple[Any, ...]:
  input_ids, attention_mask = inputs
  output = self.model(input_ids, attention_mask,
                      training=False).last_hidden_state
  return (output,)

But in order for it to work with SavedModel, we need to change it to:
@tf.function(jit_compile=True)
def forward_sm(self, input_ids, attention_mask):
  return self.model(input_ids, attention_mask,
                    training=False).last_hidden_state

Fixed by #https://github.com/openxla/openxla-benchmark/pull/113)


Website code translation not in workflow

Things like 404 pages, side bar, footer content are not currently in our translation workflow.
To translate them, the following steps needs to be done:

cd website
npm run docusaurus -- write-translations

It will generate json files under /website/i18n/en/.... Those json files need to be translated and placed under each /website/i18n/<locale>/

These commands will also cover strings wrapped in <translate></translate> blocks.
Ideally, a PR-triggered workflow should be set up that runs these commands and commit to the PR directly, so that the docs contributor won't have to do it themselves.
What's nice about these commands is that they do a smart update and retain (partially) translated contents.

We can add the checks in "build website" workflow


Appstore rejected because of Required Permissions

Hello,
Very awesome stuff you guys have done here.
I ran into an issue recently while trying to deploy my flutter app to the app store.
The app got rejected cause certain permissions that were required were not included in the Info.plist file.
Here are the permissions in question:
NSAppleMusicUsageDescription
NSSpeechRecognitionUsageDescription
NSCalendarsUsageDescription
NSMotionUsageDescription
NSLocationAlwaysUsageDescription
NSLocationWhenInUseUsageDescription

They recommend adding descriptions to the Info.plist for each of these permissions, but I don't require any of these permissions in my app, so its sort of weird (and unsafe) having to grant access to these guys.
I did some digging and it turns out its being caused by a dependency in your package: permission_handler
Please, Any ideas on how to resolve this?

Hi @scrombie,
Thanks for bringing this to our attention. This is related to #645, and  we are working to fix it


大佬大佬,求助求助,帮看看报错

I:\fsd\fsd\venv\Scripts\python.exe script\main.py
[01/23/2023-20:24:19] [TRT] [E] 6: The engine plan file is not compatible with this version of TensorRT, expecting library version <IP_ADDRESS> got <IP_ADDRESS>, please rebuild.
[01/23/2023-20:24:19] [TRT] [E] 4: [runtime.cpp::nvinfer1::Runtime::deserializeCudaEngine::50] Error Code 4: Internal Error (Engine deserialization failed.)
Traceback (most recent call last):
File "script\main.py", line 63, in
clrnet = CLRNet(llamas_engine_path)
File "I:\fsd\fsd\Perception\LaneDetection\clrnet_trt.py", line 75, in init
self.context = self.engine.create_execution_context()
AttributeError: 'NoneType' object has no attribute 'create_execution_context'
进程已结束,退出代码1

@nizhihao7 engine文件需要自己生成

@nizhihao7 是的，onnx文件下载仓库里的就行，按照readme的方法转换为engine文件

@Yutong-gannis 大佬转化完了,您再帮我看看~
I:\fsd\fsd\venv\Scripts\python.exe script\main.py
Traceback (most recent call last):
File "script\main.py", line 63, in
clrnet = CLRNet(llamas_engine_path)
File "I:\fsd\fsd\Perception\LaneDetection\clrnet_trt.py", line 73, in init
with open(engine_path, "rb") as f, trt.Runtime(self.logger) as runtime:
FileNotFoundError: [Errno 2] No such file or directory: 'I:\fsd\fsd\Engines\llamas_dla34.engine'
进程已结束,退出代码1

@nizhihao7 没有找到文件，是不是文件位置犯错了，或者直接在clrnet = CLRNet()里填绝对路径

@Yutong-gannis 我去路径里看了看,我好像只转出了llamas_dla34_tmp.onnx.这个llamas_dla34.engine它提示失败.

@nizhihao7 看一下所有报错

@Yutong-gannis 您看看~
(venv) PS I:\fsd\fsd> polygraphy surgeon sanitize ./engines/llamas_dla34.onnx --fold-constants --output ./engines/llamas_dla34_tmp.onnx [W] 'colored' module is not installed, will not use colors when logging. To enable colors, please install the 'colored' module: python3 -m pip install colored [I] RUNNING | Command: I:\fsd\fsd\venv\Scripts\polygraphy surgeon sanitize ./engines/llamas_dla34.onnx --fold-constants --output ./engines/llamas_dla34_tmp.onnx [I] Inferring shapes in the model with onnxruntime.tools.symbolic_shape_infer.     Note: To force Polygraphy to use onnx.shape_inferenceinstead, setallow_onnxruntime=Falseor use the--no-onnxruntime-shape-inference` command-line option.
[I] Loading model: I:\fsd\fsd\engines\llamas_dla34.onnx
[I] Original Model:
Name: torch-jit-export | ONNX Opset: 11
---- 1 Graph Input(s) ----
{input [dtype=float32, shape=(1, 3, 320, 800)]}

---- 1 Graph Output(s) ----
{3076 [dtype=float32, shape=(1, 192, 78)]}

---- 222 Initializer(s) ----

---- 2603 Node(s) ----

[I] Folding Constants | Pass 1
[E] Module: 'onnx_graphsurgeon' version '0.3.12' is installed, but version '>=0.3.21' is required.
Please install the required version or set POLYGRAPHY_AUTOINSTALL_DEPS=1 in your environment variables to allow Polygraphy to do so automatically.
Attempting to continue with the currently installed version of this module, but note that this may cause errors!
[W] Constant folding pass failed. Skipping subsequent passes.
Note: Error was:
fold_constants() got an unexpected keyword argument 'size_threshold'
[I] Saving ONNX model to: ./engines/llamas_dla34_tmp.onnx
[I] New Model:
Name: torch-jit-export | ONNX Opset: 11
---- 1 Graph Input(s) ----
{input [dtype=float32, shape=(1, 3, 320, 800)]}

---- 1 Graph Output(s) ----
{3076 [dtype=float32, shape=(1, 192, 78)]}

---- 222 Initializer(s) ----

---- 2603 Node(s) ----

[I] PASSED | Runtime: 5.488s | Command: I:\fsd\fsd\venv\Scripts\polygraphy surgeon sanitize ./engines/llamas_dla34.onnx --fold-constants --output ./engines/llamas_dla34_tmp.onnx
(venv) PS I:\fsd\fsd> trtexec --onnx=./engines/llamas_dla34_tmp.onnx --saveEngine=./engines/llamas_dla34.engine
&&&& RUNNING TensorRT.trtexec [TensorRT v8402] # C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.2\bin\trtexec.exe --onnx=./engines/llamas_dla34_tmp.onnx --saveEngine=./engines/llamas_dla34.engine
[01/23/2023-21:28:30] [I] === Model Options ===
[01/23/2023-21:28:30] [I] Format: ONNX
[01/23/2023-21:28:30] [I] Model: ./engines/llamas_dla34_tmp.onnx
[01/23/2023-21:28:30] [I] Output:
[01/23/2023-21:28:30] [I] === Build Options ===
[01/23/2023-21:28:30] [I] Max batch: explicit batch
[01/23/2023-21:28:30] [I] Memory Pools: workspace: default, dlaSRAM: default, dlaLocalDRAM: default, dlaGlobalDRAM: default
[01/23/2023-21:28:30] [I] minTiming: 1
[01/23/2023-21:28:30] [I] avgTiming: 8
[01/23/2023-21:28:30] [I] Precision: FP32
[01/23/2023-21:28:30] [I] LayerPrecisions:
[01/23/2023-21:28:30] [I] Calibration:
[01/23/2023-21:28:30] [I] Refit: Disabled
[01/23/2023-21:28:30] [I] Sparsity: Disabled
[01/23/2023-21:28:30] [I] Safe mode: Disabled
[01/23/2023-21:28:30] [I] DirectIO mode: Disabled
[01/23/2023-21:28:30] [I] Restricted mode: Disabled
[01/23/2023-21:28:30] [I] Build only: Disabled
[01/23/2023-21:28:30] [I] Save engine: ./engines/llamas_dla34.engine
[01/23/2023-21:28:30] [I] Load engine:
[01/23/2023-21:28:30] [I] Profiling verbosity: 0
[01/23/2023-21:28:30] [I] Tactic sources: Using default tactic sources
[01/23/2023-21:28:30] [I] timingCacheMode: local
[01/23/2023-21:28:30] [I] timingCacheFile:
[01/23/2023-21:28:30] [I] Input(s)s format: fp32:CHW
[01/23/2023-21:28:30] [I] Output(s)s format: fp32:CHW
[01/23/2023-21:28:30] [I] Input build shapes: model
[01/23/2023-21:28:30] [I] Input calibration shapes: model
[01/23/2023-21:28:30] [I] === System Options ===
[01/23/2023-21:28:30] [I] Device: 0
[01/23/2023-21:28:30] [I] DLACore:
[01/23/2023-21:28:30] [I] Plugins:
[01/23/2023-21:28:30] [I] === Inference Options ===
[01/23/2023-21:28:30] [I] Batch: Explicit
[01/23/2023-21:28:30] [I] Input inference shapes: model
[01/23/2023-21:28:30] [I] Iterations: 10
[01/23/2023-21:28:30] [I] Duration: 3s (+ 200ms warm up)
[01/23/2023-21:28:30] [I] Sleep time: 0ms
[01/23/2023-21:28:30] [I] Idle time: 0ms
[01/23/2023-21:28:30] [I] Streams: 1
[01/23/2023-21:28:30] [I] ExposeDMA: Disabled
[01/23/2023-21:28:30] [I] Data transfers: Enabled
[01/23/2023-21:28:30] [I] Spin-wait: Disabled
[01/23/2023-21:28:30] [I] Multithreading: Disabled
[01/23/2023-21:28:30] [I] CUDA Graph: Disabled
[01/23/2023-21:28:30] [I] Separate profiling: Disabled
[01/23/2023-21:28:30] [I] Time Deserialize: Disabled
[01/23/2023-21:28:30] [I] Time Refit: Disabled
[01/23/2023-21:28:30] [I] Inputs:
[01/23/2023-21:28:30] [I] === Reporting Options ===
[01/23/2023-21:28:30] [I] Verbose: Disabled
[01/23/2023-21:28:30] [I] Averages: 10 inferences
[01/23/2023-21:28:30] [I] Percentile: 99
[01/23/2023-21:28:30] [I] Dump refittable layers:Disabled
[01/23/2023-21:28:30] [I] Dump output: Disabled
[01/23/2023-21:28:30] [I] Profile: Disabled
[01/23/2023-21:28:30] [I] Export timing to JSON file:
[01/23/2023-21:28:30] [I] Export output to JSON file:
[01/23/2023-21:28:30] [I] Export profile to JSON file:
[01/23/2023-21:28:30] [I]
[01/23/2023-21:28:30] [I] === Device Information ===
[01/23/2023-21:28:30] [I] Selected Device: NVIDIA GeForce GTX 1070 Ti
[01/23/2023-21:28:30] [I] Compute Capability: 6.1
[01/23/2023-21:28:30] [I] SMs: 19
[01/23/2023-21:28:30] [I] Compute Clock Rate: 1.683 GHz
[01/23/2023-21:28:30] [I] Device Global Memory: 8191 MiB
[01/23/2023-21:28:30] [I] Shared Memory per SM: 96 KiB
[01/23/2023-21:28:30] [I] Memory Bus Width: 256 bits (ECC disabled)
[01/23/2023-21:28:30] [I] Memory Clock Rate: 4.004 GHz
[01/23/2023-21:28:30] [I]
[01/23/2023-21:28:30] [I] TensorRT version: 8.4.2
[01/23/2023-21:28:31] [I] [TRT] [MemUsageChange] Init CUDA: CPU +234, GPU +0, now: CPU 11874, GPU 1058 (MiB)
[01/23/2023-21:28:31] [I] [TRT] [MemUsageChange] Init builder kernel library: CPU +2, GPU +0, now: CPU 11934, GPU 1058 (MiB)
[01/23/2023-21:28:31] [I] Start parsing network model
[01/23/2023-21:28:31] [I] [TRT] ----------------------------------------------------------------
[01/23/2023-21:28:31] [I] [TRT] Input filename:   ./engines/llamas_dla34_tmp.onnx
[01/23/2023-21:28:31] [I] [TRT] ONNX IR version:  0.0.6
[01/23/2023-21:28:31] [I] [TRT] Opset version:    11
[01/23/2023-21:28:31] [I] [TRT] Producer name:    pytorch
[01/23/2023-21:28:31] [I] [TRT] Producer version: 1.9
[01/23/2023-21:28:31] [I] [TRT] Domain:
[01/23/2023-21:28:31] [I] [TRT] Model version:    0
[01/23/2023-21:28:31] [I] [TRT] Doc string:
[01/23/2023-21:28:31] [I] [TRT] ----------------------------------------------------------------
[01/23/2023-21:28:31] [W] [TRT] onnx2trt_utils.cpp:369: Your ONNX model has been generated with INT64 weights, while TensorRT does not natively support INT64. Attempting to cast down to INT32.
[01/23/2023-21:28:31] [W] [TRT] onnx2trt_utils.cpp:395: One or more weights outside the range of INT32 was clamped
[01/23/2023-21:28:31] [W] [TRT] onnx2trt_utils.cpp:395: One or more weights outside the range of INT32 was clamped
[01/23/2023-21:28:31] [E] Error[4]: [shuffleNode.cpp::nvinfer1::builder::ShuffleNode::symbolicExecute::392] Error Code 4: Internal Error (Reshape_226: IShuffleLayer applied to shape tensor must have 0 or 1 reshape dimensions: dimensions were [-1,2]
)
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:773: While parsing node number 237 [Pad -> "496"]:
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:774: --- Begin node ---
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:775: input: "313"
input: "494"
input: "495"
output: "496"
name: "Pad_237"
op_type: "Pad"
attribute {
name: "mode"
s: "constant"
type: STRING
}
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:776: --- End node ---
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:779: ERROR: ModelImporter.cpp:180 In function parseGraph:
[6] Invalid Node - Pad_237
[shuffleNode.cpp::nvinfer1::builder::ShuffleNode::symbolicExecute::392] Error Code 4: Internal Error (Reshape_226: IShuffleLayer applied to shape tensor must have 0 or 1 reshape dimensions: dimensions were [-1,2])
[01/23/2023-21:28:31] [E] Failed to parse onnx file
[01/23/2023-21:28:31] [I] Finish parsing network model
[01/23/2023-21:28:31] [E] Parsing model failed
[01/23/2023-21:28:31] [E] Failed to create engine from model or file.
[01/23/2023-21:28:31] [E] Engine set up failed
&&&& FAILED TensorRT.trtexec [TensorRT v8402] # C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.2\bin\trtexec.exe --onnx=./engines/llamas_dla34_tmp.onnx --saveEngine=./engines/llamas_dla34.engine
(venv) PS I:\fsd\fsd>
`

@Yutong-gannis 您看看~!
(venv) PS I:\fsd\fsd> polygraphy surgeon sanitize ./engines/llamas_dla34.onnx --fold-constants --output ./engines/llamas_dla34_tmp.onnx
[W] 'colored' module is not installed, will not use colors when logging. To enable colors, please install the 'colored' module: python3 -m pip install colored
[I] RUNNING | Command: I:\fsd\fsd\venv\Scripts\polygraphy surgeon sanitize ./engines/llamas_dla34.onnx --fold-constants --output ./engines/llamas_dla34_tmp.onnx
[I] Inferring shapes in the model with onnxruntime.tools.symbolic_shape_infer.
Note: To force Polygraphy to use onnx.shape_inference instead, set allow_onnxruntime=False or use the --no-onnxruntime-shape-inference command-line option.
[I] Loading model: I:\fsd\fsd\engines\llamas_dla34.onnx
[I] Original Model:
Name: torch-jit-export | ONNX Opset: 11
---- 1 Graph Input(s) ----
{input [dtype=float32, shape=(1, 3, 320, 800)]}

---- 1 Graph Output(s) ----
{3076 [dtype=float32, shape=(1, 192, 78)]}

---- 222 Initializer(s) ----

---- 2603 Node(s) ----

[I] Folding Constants | Pass 1
[E] Module: 'onnx_graphsurgeon' version '0.3.12' is installed, but version '>=0.3.21' is required.
Please install the required version or set POLYGRAPHY_AUTOINSTALL_DEPS=1 in your environment variables to allow Polygraphy to do so automatically.
Attempting to continue with the currently installed version of this module, but note that this may cause errors!
[W] Constant folding pass failed. Skipping subsequent passes.
Note: Error was:
fold_constants() got an unexpected keyword argument 'size_threshold'
[I] Saving ONNX model to: ./engines/llamas_dla34_tmp.onnx
[I] New Model:
Name: torch-jit-export | ONNX Opset: 11
---- 1 Graph Input(s) ----
{input [dtype=float32, shape=(1, 3, 320, 800)]}

---- 1 Graph Output(s) ----
{3076 [dtype=float32, shape=(1, 192, 78)]}

---- 222 Initializer(s) ----

---- 2603 Node(s) ----

[I] PASSED | Runtime: 5.488s | Command: I:\fsd\fsd\venv\Scripts\polygraphy surgeon sanitize ./engines/llamas_dla34.onnx --fold-constants --output ./engines/llamas_dla34_tmp.onnx
(venv) PS I:\fsd\fsd> trtexec --onnx=./engines/llamas_dla34_tmp.onnx --saveEngine=./engines/llamas_dla34.engine
&&&& RUNNING TensorRT.trtexec [TensorRT v8402] # C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.2\bin\trtexec.exe --onnx=./engines/llamas_dla34_tmp.onnx --saveEngine=./engines/llamas_dla34.engine
[01/23/2023-21:28:30] [I] === Model Options ===
[01/23/2023-21:28:30] [I] Format: ONNX
[01/23/2023-21:28:30] [I] Model: ./engines/llamas_dla34_tmp.onnx
[01/23/2023-21:28:30] [I] Output:
[01/23/2023-21:28:30] [I] === Build Options ===
[01/23/2023-21:28:30] [I] Max batch: explicit batch
[01/23/2023-21:28:30] [I] Memory Pools: workspace: default, dlaSRAM: default, dlaLocalDRAM: default, dlaGlobalDRAM: default
[01/23/2023-21:28:30] [I] minTiming: 1
[01/23/2023-21:28:30] [I] avgTiming: 8
[01/23/2023-21:28:30] [I] Precision: FP32
[01/23/2023-21:28:30] [I] LayerPrecisions:
[01/23/2023-21:28:30] [I] Calibration:
[01/23/2023-21:28:30] [I] Refit: Disabled
[01/23/2023-21:28:30] [I] Sparsity: Disabled
[01/23/2023-21:28:30] [I] Safe mode: Disabled
[01/23/2023-21:28:30] [I] DirectIO mode: Disabled
[01/23/2023-21:28:30] [I] Restricted mode: Disabled
[01/23/2023-21:28:30] [I] Build only: Disabled
[01/23/2023-21:28:30] [I] Save engine: ./engines/llamas_dla34.engine
[01/23/2023-21:28:30] [I] Load engine:
[01/23/2023-21:28:30] [I] Profiling verbosity: 0
[01/23/2023-21:28:30] [I] Tactic sources: Using default tactic sources
[01/23/2023-21:28:30] [I] timingCacheMode: local
[01/23/2023-21:28:30] [I] timingCacheFile:
[01/23/2023-21:28:30] [I] Input(s)s format: fp32:CHW
[01/23/2023-21:28:30] [I] Output(s)s format: fp32:CHW
[01/23/2023-21:28:30] [I] Input build shapes: model
[01/23/2023-21:28:30] [I] Input calibration shapes: model
[01/23/2023-21:28:30] [I] === System Options ===
[01/23/2023-21:28:30] [I] Device: 0
[01/23/2023-21:28:30] [I] DLACore:
[01/23/2023-21:28:30] [I] Plugins:
[01/23/2023-21:28:30] [I] === Inference Options ===
[01/23/2023-21:28:30] [I] Batch: Explicit
[01/23/2023-21:28:30] [I] Input inference shapes: model
[01/23/2023-21:28:30] [I] Iterations: 10
[01/23/2023-21:28:30] [I] Duration: 3s (+ 200ms warm up)
[01/23/2023-21:28:30] [I] Sleep time: 0ms
[01/23/2023-21:28:30] [I] Idle time: 0ms
[01/23/2023-21:28:30] [I] Streams: 1
[01/23/2023-21:28:30] [I] ExposeDMA: Disabled
[01/23/2023-21:28:30] [I] Data transfers: Enabled
[01/23/2023-21:28:30] [I] Spin-wait: Disabled
[01/23/2023-21:28:30] [I] Multithreading: Disabled
[01/23/2023-21:28:30] [I] CUDA Graph: Disabled
[01/23/2023-21:28:30] [I] Separate profiling: Disabled
[01/23/2023-21:28:30] [I] Time Deserialize: Disabled
[01/23/2023-21:28:30] [I] Time Refit: Disabled
[01/23/2023-21:28:30] [I] Inputs:
[01/23/2023-21:28:30] [I] === Reporting Options ===
[01/23/2023-21:28:30] [I] Verbose: Disabled
[01/23/2023-21:28:30] [I] Averages: 10 inferences
[01/23/2023-21:28:30] [I] Percentile: 99
[01/23/2023-21:28:30] [I] Dump refittable layers:Disabled
[01/23/2023-21:28:30] [I] Dump output: Disabled
[01/23/2023-21:28:30] [I] Profile: Disabled
[01/23/2023-21:28:30] [I] Export timing to JSON file:
[01/23/2023-21:28:30] [I] Export output to JSON file:
[01/23/2023-21:28:30] [I] Export profile to JSON file:
[01/23/2023-21:28:30] [I]
[01/23/2023-21:28:30] [I] === Device Information ===
[01/23/2023-21:28:30] [I] Selected Device: NVIDIA GeForce GTX 1070 Ti
[01/23/2023-21:28:30] [I] Compute Capability: 6.1
[01/23/2023-21:28:30] [I] SMs: 19
[01/23/2023-21:28:30] [I] Compute Clock Rate: 1.683 GHz
[01/23/2023-21:28:30] [I] Device Global Memory: 8191 MiB
[01/23/2023-21:28:30] [I] Shared Memory per SM: 96 KiB
[01/23/2023-21:28:30] [I] Memory Bus Width: 256 bits (ECC disabled)
[01/23/2023-21:28:30] [I] Memory Clock Rate: 4.004 GHz
[01/23/2023-21:28:30] [I]
[01/23/2023-21:28:30] [I] TensorRT version: 8.4.2
[01/23/2023-21:28:31] [I] [TRT] [MemUsageChange] Init CUDA: CPU +234, GPU +0, now: CPU 11874, GPU 1058 (MiB)
[01/23/2023-21:28:31] [I] [TRT] [MemUsageChange] Init builder kernel library: CPU +2, GPU +0, now: CPU 11934, GPU 1058 (MiB)
[01/23/2023-21:28:31] [I] Start parsing network model
[01/23/2023-21:28:31] [I] [TRT] ----------------------------------------------------------------
[01/23/2023-21:28:31] [I] [TRT] Input filename:   ./engines/llamas_dla34_tmp.onnx
[01/23/2023-21:28:31] [I] [TRT] ONNX IR version:  0.0.6
[01/23/2023-21:28:31] [I] [TRT] Opset version:    11
[01/23/2023-21:28:31] [I] [TRT] Producer name:    pytorch
[01/23/2023-21:28:31] [I] [TRT] Producer version: 1.9
[01/23/2023-21:28:31] [I] [TRT] Domain:
[01/23/2023-21:28:31] [I] [TRT] Model version:    0
[01/23/2023-21:28:31] [I] [TRT] Doc string:
[01/23/2023-21:28:31] [I] [TRT] ----------------------------------------------------------------
[01/23/2023-21:28:31] [W] [TRT] onnx2trt_utils.cpp:369: Your ONNX model has been generated with INT64 weights, while TensorRT does not natively support INT64. Attempting to cast down to INT32.
[01/23/2023-21:28:31] [W] [TRT] onnx2trt_utils.cpp:395: One or more weights outside the range of INT32 was clamped
[01/23/2023-21:28:31] [W] [TRT] onnx2trt_utils.cpp:395: One or more weights outside the range of INT32 was clamped
[01/23/2023-21:28:31] [E] Error[4]: [shuffleNode.cpp::nvinfer1::builder::ShuffleNode::symbolicExecute::392] Error Code 4: Internal Error (Reshape_226: IShuffleLayer applied to shape tensor must have 0 or 1 reshape dimensions: dimensions were [-1,2]
)
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:773: While parsing node number 237 [Pad -> "496"]:
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:774: --- Begin node ---
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:775: input: "313"
input: "494"
input: "495"
output: "496"
name: "Pad_237"
op_type: "Pad"
attribute {
name: "mode"
s: "constant"
type: STRING
}
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:776: --- End node ---
[01/23/2023-21:28:31] [E] [TRT] ModelImporter.cpp:779: ERROR: ModelImporter.cpp:180 In function parseGraph:
[6] Invalid Node - Pad_237
[shuffleNode.cpp::nvinfer1::builder::ShuffleNode::symbolicExecute::392] Error Code 4: Internal Error (Reshape_226: IShuffleLayer applied to shape tensor must have 0 or 1 reshape dimensions: dimensions were [-1,2])
[01/23/2023-21:28:31] [E] Failed to parse onnx file
[01/23/2023-21:28:31] [I] Finish parsing network model
[01/23/2023-21:28:31] [E] Parsing model failed
[01/23/2023-21:28:31] [E] Failed to create engine from model or file.
[01/23/2023-21:28:31] [E] Engine set up failed
&&&& FAILED TensorRT.trtexec [TensorRT v8402] # C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.2\bin\trtexec.exe --onnx=./engines/llamas_dla34_tmp.onnx --saveEngine=./engines/llamas_dla34.engine
(venv) PS I:\fsd\fsd>

@Yutong-gannis 喔嚯~搞不定了 = =233 .我看了一下[CLRNet-onnxruntime-and-tensorrt-demo]也是只能转出tmp.onnx~转第二个的时候也是一样失败~ Onz

@nizhihao7 试试直接转engine，不用polygraphy surgeon，还不行的话，考虑换成tensorrt<IP_ADDRESS>

@Yutong-gannis 直接转换也失败,我现在用的好像就是8424

@ywjno 这个问题能解决吗

使用<IP_ADDRESS>可以成功转换

@Dameng23333 好的好的,我试试看.只升级TensorRT到8522其他还有改变不?~

@我和你版本一样的，不太像是版本问题。polygraphy surgeon sanitize model.onnx --fold-constants  -o folded.onnx加这个fold constants试试

@Yutong-gannis
polygraphy surgeon sanitize ./engines/llamas_dla34.onnx --fold-constants -o ./engines/llamas_dla34.engine
这样可以直接转出来engine,是这样转不?

@nizhihao7 先优化onnx再用trtexec转

@Yutong-gannis 那好像还是不行,只能这样转,多转一次第二次都是失败的.我升级8522看看~

@Yutong-gannis 8522可以转~~~
这是转完之后的
I:\fsd\fsd\venv\Scripts\python.exe script\main.py
[01/23/2023-23:10:43] [TRT] [E] 1: [stdArchiveReader.cpp::nvinfer1::rt::StdArchiveReader::StdArchiveReader::40] Error Code 1: Serialization (Serialization assertion stdVersionRead == serializationVersion failed.Version tag does not match. Note: Current Version: 213, Serialized Engine Version: 232)
[01/23/2023-23:10:43] [TRT] [E] 4: [runtime.cpp::nvinfer1::Runtime::deserializeCudaEngine::50] Error Code 4: Internal Error (Engine deserialization failed.)
Traceback (most recent call last):
File "script\main.py", line 63, in
clrnet = CLRNet(llamas_engine_path)
File "I:\fsd\fsd\Perception\LaneDetection\clrnet_trt.py", line 75, in init
self.context = self.engine.create_execution_context()
AttributeError: 'NoneType' object has no attribute 'create_execution_context'
进程已结束,退出代码1

@nizhihao7 看报错好像是没有修改环境中的tensorrt，你只是转换用的8.5吗

tensorrt 8.5.x 的版本转换出来的engine文件是不支持的
tensorrt 不仅whl的版本要一样，环境变量里面的Path也要相同

我可是费了3天时间有两天弄到凌晨3点才弄好的环境，请仔细看一遍 Readme

trtexec.exe 这个文件正常的应该是在 $TENSORRT_PATH/bin 下，这是把它这个文件放到 $CUDA_PATH/bin 文件夹下了么？
$TENSORRT_PATH/lib添加到环境变量 Path 里面了么？
修改完环境变量 Path 之后重启 Powershell 了么？

好的好的,我先升级一下onnx_graphsurgeon.我找半天怎么升级= =

把 安装权重转换所依赖的包 的那行命令运行一下就能安装转换engine文件所依赖的包

@ywjno @Yutong-gannis @Dameng23333 好像成了~多谢大佬们.但是分辨率设置多少比较好~?

各位大佬,现在有点游戏设置的小问题.整个车子偏右几乎压着右边的白线.而且车道经常识别不到- -.游戏设置能给个截图参考一下不?

偏右好了. 游戏窗口没摆好= =.但是白线识别还是不怎么好~经常看不见= =是车辆灯光问题还是游戏设置的问题? 白天有些时候也是识别不到,尴尬~

@ywjno 如果比我的视频效果差，可能是精度问题，或者你可以在clrnet_trt.py里调一下conf_threshold

识别窗口的上面能认出东西，下面判断行驶方向的不行，即使修改了 clrnet_trt.py 的 L106行也不行，话说self.conf_threshold = 0.6这句话在L80的循环里面重复赋相同的值是就是那么写的么？

@ywjno @nizhihao7 导航线的话需要装mod,写在readme里了

那两个 mod 已经装了的

mod已经安装了，上高架的那个环线有点识别不到，导航线会识别到高架上那条然后突然转弯撞墙，这个是没识别到车道线的问题么？

@nizhihao7 这个可能要后面单独做一个场景

@ywjno 可能确实只能这样，技术路线没选好，可能分割可以更稳定一点

@Yutong-gannis   安装numpy==1.23.5 lap 显示这个python setup.py bdist_wheel did not run successfully.无法解决帮我看看~~~

@panyuab 更新setuptools版本试试

@Yutong-gannis setuptools是最新版本

看看 这个 能不能解决问题
有新问题单独开issue吧，这个感觉可以关掉了。。。