Error when using VS 2015 as remote debugger

Using WebsiteManagementClient.GetSiteWithCache() on a WebApp with remote debugging with VS 2015 causes an error. I had this problem with azure-powershell but since the azure-powershell team chose to ignore the bug (or didn't want to update it) I tracked it down to this lib myself. This is coming from https://github.com/Azure/azure-powershell/issues/462.
This can probably be fixed be regenerating the code for using Websites.

@FuUuUuUoO Can you please provide more detail?  What is the error that you are getting?  Without more information, we cannot track this down.

The issue is probably that this line fails:
https://github.com/Azure/azure-sdk-for-net/blob/master/src/ServiceManagement/WebSite/WebSiteManagement/Generated/WebSiteOperations.cs#L3673
It does so due to the enum not containing a value for VS2015 I believe (see https://github.com/Azure/azure-sdk-for-net/blob/21db6e5490e66af39a9c6dbf0ad10650d9ca037b/src/ResourceManagement/WebSite/WebSiteManagement/Generated/Models/RemoteDebuggingVersion.cs for the enum).
This issue is probably currently the reason why a lot of people think that Visual Studio Online sucks. By default the web app deployment agent task doesn't work if you are working from VS 2105. That's why I have made an effort trying to pin this down.
I suggest adding VS2016 while you are at it... it will be released eventually too.

This is a huge annoying issue to us,
We need to remeber to disable remote debugging when using VS2015 (enabling first a known value like VS2013 and then disabling it all together) so we can publish our sites from powershell.
When using VSTS build, if a developer does a remote debugging session with VS2015, most of the time breaks the continuous integration build we have setup.
It's December now, VS is on Update 1, and this is open since 14 Jul... at least, include the enum value an release and update...

Also came across this for a site where I had dabbled with remote profiling from VS2015
https://azure.microsoft.com/en-gb/blog/remote-profiling-support-in-azure-app-service/

As remote profiling is now being promoted more this increases the likelihood of this occurring. Really needs to be fixed.

Had this yesterday during a critical moment with our production app lagging behind, because in Dev environment we enabled Remote Debugging and didn't dare to promote it to production, while CI was failing.
Solution described here helped, but it is even more outrageous.
I guess Azure developers nowadays have to have been participating in Hogwarts School of Witchcraft and Wizardry with this kind of magic solutions needed.
Please fix it ASAP :clap:

@DovydasNavickas @lkempf @storafrid @ielcoro @andybatescc  Hi all, this is a very simple issue that should have been fixed long ago.  Unfortunately, since this impacts the RDFE (and not the ARM) client, it looks like it has been deprioritized by the feature team.  We'll work to get a fix out ASAP.

Good to hear. We're the ones who already found out the issue and know the cure, so it's not that painful anymore. But for people who are still to find this out... It should be prioritized at the top, if it's a small and simplr issue :+1:
I guess there should be more involvement from RDFE team in this GitHub repository issues list.
Also, is there a separate place to report issues for RDFE specifically? Can't seem to find it...

Fix was just checked in to master, released on nugget version 4.5.0 (https://www.nuget.org/packages/Microsoft.WindowsAzure.Management.WebSites/4.5.0-prerelease ) and checked into powershell (finally)


6rc.10 installation flow

Versions
local and global cli 6 rc 9

Repro steps
Inside my cli project I want update from rc9 to rc10 so:

npm uninstall @angular/cli -g
npm i @angular/cli@next -g

Observed behavior
=================================================================
The Angular CLI configuration format has been changed, and your existing configuration can
be updated automatically by running the following command:

ng update @angular/cli
==================================================================

I can read my config's changed so I run : ng update @angular/cli  then I get:
Your global Angular CLI version (6.0.0-rc.10) is greater than your local
version (6.0.0-rc.9). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
            Found a modern configuration file. Nothing to be done.

Desired behavior
Is this expected behavior ? Seems a little bit weird to me.

ng update acts different than npm i, because ng update runs migration rules that will update your project to match the version that you are installing.
ng update @angular/cli itself though shouldn't not install pre-released versions, unless specified to do so with the --next flag, which seems to have been addressed.


As a user, I would like to use the error notification framework for my own errors

From: https://powerofus.force.com/_ui/core/chatter/groups/GroupProfilePage?g=0F980000000CjRe&fId=0D58000001MFVTL

As a developer, if I write custom code on top of the NPSP, is it possible to log my own errors to NPSP's log? I perused Github and these classes don't look global, so my guess is no. But I'd be happy to be wrong.
If not, is that something you guys might consider opening up to us hackers? Would really save time coding our own error handling, and would provide a seamless experience for the admins.

Very good question. Even if the classes aren't global, we could use Apex to write directly to the Error__c object. Would the email/chatter-group alerts still work if our custom apex code wrote directly to the Error__c object?

Included in beta release version 3.32 (Beta 8) and higher

Included in production release version 3.32


AEM 6.5.6 with ACS Commons 4.7.0 Breaks when I install my code package. AbstractTransformer class is missing in the 4.7.0 ported version.

Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: _______
AEM Version - 6.5.6

[ ] ACS AEM Commons Version: _____
ACS COMMONS : 4.7.0

[ ] Reproducible on Latest? yes/no YES

Expected Behavior
I have noticed that the com.adobe.acs.commons.rewriter.AbstractTransformer is missing in version 4.7.0 which we are using to rewrite our links. What is the equivalent to use here.
FYI: Currently we are on AEM 6.4 with ACS Commons 3.17.4 and can you please let me know what are the differences here.
Please describe briefly the expected behavior, i.e. when I do X, Y should happen.
Actual Behavior
The current behaviour is when I install my Code package on AEM 6.5 with ACS Commons 3.17.4 the entire application comes up as blank and when I see the error log it points to the Rewriter Function.
Please describe briefly the actual behavior, i.e. when I do X, Z happens.
Steps to Reproduce
Starting from a vanilla instance of AEM at the above version, describe in explicit steps how to reproduce. Link to
any supporting assets, e.g. content packages, below
Links
Links to related assets, e.g. content packages containing test components

com.adobe.acs.commons.rewriter.AbstractTransformer has been renamed to com.adobe.acs.commons.rewriter.ContentHandlerBasedTransformer
see: https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/1890/commits/41bb2685aedeebd04d12bea6b1c5816ecf57f8c0

com.adobe.acs.commons.rewriter.AbstractTransformer has been renamed to com.adobe.acs.commons.rewriter.ContentHandlerBasedTransformer
see: https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/1890/commits/41bb2685aedeebd04d12bea6b1c5816ecf57f8c0


How to stack deferred values?

Is there any possibility to stack few FutureValues for DeferredCount in the code like this:
users.ForEach(x =>
            {
                x.Prospects = db.Prospects.Where(p => p.UserId == x.Id).DeferredCount().FutureValue();
            });

I mean now it will produce a lot of queries, but how can I stack them and execute them at once?

Hello @Immelstorn ,
We could add a ExecuteBatch method (or a similar name) to send all query pending.
So a code similar to this could work:
users.ForEach(x =>
            {
                x.Prospects = db.Prospects.Where(p => p.UserId == x.Id).DeferredCount().FutureValue();
            });

QueryFutureManager.ExecuteBatch();

If you don't have a lot of prospects, I recommend you, however, to get all them at once (including some that you don't need).
ctx.Prospects.GroupBy(x => x.Id).Select(x => new {Id = x.Key, Count = x.Count()}).ToDictionary(x => x.Id);

We are supposed to release a new version tomorrow. We will try to include this feature in it.
Best Regards,
Jonathan

@JonathanMagnan unfortunately I have a lot of prospects, so I can't get them at once.
If you will release this feature tomorrow - it would be great, thanks, I'll wait for this release. Thanks

The ExecuteBatch(DbContext) method has been added.
It should be released within a few hours.
You will have however to modify a little bit your code. Since you implicitly cast the FutureValue as int, it will get resolved every time.
Dictionary<int, QueryFutureValue<int>> dict;

users.ForEach(x =>
{
	dict.Add(int, db.Prospects.Where(p => p.UserId == x.Id).DeferredCount().FutureValue());
});

QueryFutureManager.ExecuteBatch(db); // Not necessary anymore... since the first implicit conversion will resolve all pending queries

users.ForEach(x =>
{
	x.Prospects = dict[x.Id];
})

Hello @Immelstorn
The v1.6.7 has been released.
Let me know if you still have the issue.
Best Regards,
Jonathan

Hello @Immelstorn ,
We will close this issue since we got no confirmation.
Please reopen it if you still have the issue,
Best Regards,
Jonathan


refactor CLI (1/2): Cosmetic changes

While working on the many-to-many mapping I wanted to introduce a new subcommand ... only to end up refactoring the whole ruff_cli::cli::Cli struct.
This CLI refactor has gotten so large that I'll split it up in two PRs (this PR contains the purely cosmetic changes, the next PR will contain the larger refactors).

(A major CLI refactor PR is incoming as a followup PR ... while working on the many-to-many mapping, I wanted to introduce a new subcommand ... only to end up refactoring the whole Cli (or now Args) struct in ruff_cli ... this is a precursor PR so that the followup CLI refactor PR has a cleaner diff).

LGTM, but now has a conflict (sorry!)

Rebased :)


Add request mask to the example People API url

Without this parameter the server responds with a 400 error informing
about the malformed request and displaying the error on the page.
The error message in the json response is:
"Request mask can not be empty. Valid paths are: [person.adresses,
person.age_ranges....

LGTM. Thanks for the contribution.


not longer working

Seems it is not longer working, i cant get any values form my sensors (running HA 2022.9.4)
main sensor shows only "off" but not anymore "start" and "end" vor next vacation as its was

Should be fixed: https://github.com/HazardDede/home-assistant-ferienapidotde/releases/tag/v0.2.4


file handling part

PR Description
file handling part is added earlier it was not there
with open(value, 'rb') as f:
                file_content = f.read()

Related Issues

Related Issue #259
Closes #259

Checklist

[x] I have gone through the contributing guide
[x] I have run the tests (flutter test) and all tests are passing

Added/updated tests?
We encourage you to add relevant test cases.

[ ] Yes
[x] No, and this is why: please replace this line with details on why tests have not been included

Hey @nikkivirtuoso, nit: could you please reformat PR title, and future commits with respect to standard practices? See more here

@opxdelwin sir, i have renamed the PR as per the standard practices, please have a look

Closing the PR as the issue has been resolved.
Check issue thread for more details.


Decription of the icons in input field while hovering

For a first time user of the site there should be a description of what the icon does when we click on it .
The description should appear while hovering on the icon.
I myself got confused about what will happen if i click on this icon .
so, I think the description will be of great help :-)

@abhijeet007rocks8 How can I run this project on my local environment using node and express to make sure the changes are correct.
Please guide.

I'll need to go through the complete project once
I'll get back to you after 5th after finalising the GSSOC'21 merges and points distribution

@abhijeet007rocks8 Are you free now ?

@Divyanshj I'm free now how may I help you

@abhijeet007rocks8 Can you help me in running this project on my local machina.
I am new to open source, please guide !

@Divyanshj firstly install node and npm
2nd clone the repo to you local
3rd from terminal navigate to repo folder
4th use command npm install
5th use command npm start


Cannot block a site at different times on different days

I want to block Facebook on Sunday from 08:00 to 14:00 and on Monday from 14:00 to 20:00. It's impossible to do it. Please, fix it.

I'd also like to request this feature.


The call_immediate parameter of jsPsych.timelineVariable() fails to work when callede explicitly

In the documentation about jsPsych.timelineVariable(), it stated that:

It is possible to explicitly set this option to true to force the function to immediately return the current value of the timeline variable.

Here, "this option" referred to the call_immediate parameter, which should mean that if I explicitly set it to true, the call to this method should return the value of the timeline variable instead of a function that will return it later.
However, when I tried it out using the code piece below:
<!DOCTYPE html>
<html>

<head>
    <title>demo</title>
    <script<EMAIL_ADDRESS>    <script src="https://unpkg.com/<EMAIL_ADDRESS>    <link<EMAIL_ADDRESS>rel="stylesheet" type="text/css" />
</head>

<body></body>
<script>
    const jsPsych = initJsPsych();

    var procedure = {
        timeline: [
            {
                type: jsPsychHtmlKeyboardResponse,
                stimulus: `${jsPsych.timelineVariable('value', true)}`,
                trial_duration: 1000,
                choices: "NO_KEYS"
            }
        ],
        timeline_variables: [
            { value: 'value-1' }
        ]
    };

    jsPsych.run([procedure]);
</script>

</html>

An error was thrown: Uncaught TypeError: Cannot read properties of undefined (reading 'timelineVariable').
I traced it back to the source code (the jspsych.js file in the release), and found that the method jsPsych.timelineVariable() is implemented thus:
timelineVariable(varname, immediate = false) {
    if (this.internal.call_immediate || immediate === true) {
        return this.timeline.timelineVariable(varname);
    }
    else {
        return {
            timelineVariablePlaceholder: true,
            timelineVariableFunction: () => this.timeline.timelineVariable(varname),
        };
    }
}

However, if immediate is true, the call to this.timeline returns undefined, thus causing the error thrown in my provided example.

Hi @Shaobin-Jiang,
When you call the timelineVariable() function immediately in your code, there is no active timeline or timeline variables because the experiment is not running yet (jsPsych.run() hasn't been called yet). The declaration of the procedure variable happens prior to the experiment running, and so calling timelineVariable() when creating the variable results in the error that you've encountered.
The call_immediate parameter should no longer be necessary to use in version 7+. If you call jsPsych.timelineVariable() in a context where there is no active timeline then it should return a placeholder function that will be invoked when the trial actually runs. If you call it in a context where there is an active timeline (e.g., inside a function parameter) then it should evaluate immediately.

Understood!


Change Analysis does not display object_category

This field is not displayed on validation

@themrkeys good catch..fixed


disable PSP on a running k8s cluster < 1.25

In prepare to update to 12.5,... we need to remvoe all PodSecurityPolicy
Which change config to:
operator.psp_auto_creation_enabled: false
There still the generated PSP.
The ty to remove it via kubectl dleete psp ... hangs forever. As you have an finalizer and there is blocking it.
Best would be that in case disable PSP you make sure that any eventualy before generated PSP get removed.
We use vmagent, vmalert and vmcluster and all 3 have same issue.
The code look like only take care of create node delete

@f41gh7 @Amper Could you please take a look?

@frankconrad Hi, what operator version do you use?

There still the generated PSP.

You mean those psp already generated are still there, right?
Turn off psp_auto_creation_enabled won't let operator clean psp created before, but stop creating new psp when new vmalert/vmagent/vmcluster applied.
So can you try delete the old vmalert/vmagent/vmcluster resources to let the operator do the cleanup thing and recreate them.

@frankconrad Hi, what operator version do you use?

There still the generated PSP.

You mean those psp already generated are still there, right?
Turn off psp_auto_creation_enabled won't let operator clean psp created before, but stop creating new psp when new vmalert/vmagent/vmcluster applied.
So can you try delete the old vmalert/vmagent/vmcluster resources to let the operator do the cleanup thing and recreate them.

I use victoria-metrics-operator chart 0.23.1
which use operator v0.34.1
yes there are still there
But I can't delete them, kubectl hangs

On a prodcution system you can't delete them...
I think there should be an better handling on operator side.
Remove finalizer is a hack.

In prepare to update to 12.5,... we need to remvoe all PodSecurityPolicy
Which change config to: operator.psp_auto_creation_enabled: false There still the generated PSP. The ty to remove it via kubectl dleete psp ... hangs forever. As you have an finalizer and there is blocking it.
Best would be that in case disable PSP you make sure that any eventualy before generated PSP get removed.
We use vmagent, vmalert and vmcluster and all 3 have same issue.
The code look like only take care of create node delete

Hello, it should be no problem with exist PSP objects and you shouldn't delete it. Kubernetes will remove it automatically.
It's a nice feature to clean-up no longer used resources. Such as PSP,HPA, additionalServices, auto-created serviceScrape. Probably operator has to store features state at annotations and correctly delete it.

Done at v0.36.0 release


New mkvtomp4.py Update Gives Errors!

Hi, mkvtomp4.py that was updated 4 hours ago gave me this error;
2020-02-05 13:26:12 - mkvtomp4 - INFO - Starting conversion.
2020-02-05 13:26:12 - SABPostProcess - ERROR - Error converting file /mnt/downloads/nzb/Farscape.S03E22.1080p.BluRay.x264-TENEIGHTY/teneighty-farscape.s03e22.mkv.
Traceback (most recent call last):
  File "/mp4automator/SABPostProcess.py", line 72, in <module>
    output = converter.process(inputfile)
  File "/mp4automator/mkvtomp4.py", line 217, in process
    outputfile, inputfile = self.convert(inputfile, options, preopts, postopts, reportProgress)
  File "/mp4automator/mkvtomp4.py", line 819, in convert
    if not self.forceConvert and self.output_extension == input_extension and len([x for x in [options['video']] + [x for x in options['audio'].values()] + [x for x in options['subtitle'].values()] if x['codec'] != 'copy']) == 0:
NameError: global name 'input_extension' is not defined

I had a backup of that file so I replaced the new one with the one you updated for my issue: https://github.com/mdhiggins/sickbeard_mp4_automator/issues/1111
And that worked! Thought you should know.

This should be resolved now, please give it a try

That worked! I just want to say thank you so much for keeping this automator alive and functional. Salute!

Thanks for catching that; its what I get for staying up til 5 am and trying to code


Add Schema tests(NOT NULL & UNIQUE) when generating YAML Files

This is a request to add Schema Tests to YAML files based on my conversation with @shahga.

Added Schema Tests to YAML files in the latest release: v0.7.0


executor failed running [/bin/bash -c bash ./install_tensorrt.sh && rm install_tensorrt.sh]: exit code: 2

make -C docker release_build
make: Entering directory '/data/yankai/TensorRT-LLM/docker'
Building docker image: tensorrt_llm/release:latest
DOCKER_BUILDKIT=1 docker build --pull
--progress auto
--build-arg BASE_IMAGE=nvcr.io/nvidia/pytorch
--build-arg BASE_TAG=23.08-py3
--build-arg BUILD_WHEEL_ARGS="--clean --trt_root /usr/local/tensorrt"
--build-arg TORCH_INSTALL_TYPE="skip"
--target release
--file Dockerfile.multi
--tag tensorrt_llm/release:latest
..
[+] Building 1026.3s (11/30)
=> [internal] load build definition from Dockerfile.multi                                                                                0.2s
=> => transferring dockerfile: 44B                                                                                0.0s
=> [internal] load .dockerignore                                                                                0.3s
=> => transferring context: 35B                                                                                0.0s
=> [internal] load metadata for nvcr.io/nvidia/pytorch:23.08-py3                                                                                3.0s
=> [internal] load build context                                                                                0.7s
=> => transferring context: 647.23kB                                                                                0.3s
=> [base 1/1] FROM nvcr.io/nvidia/pytorch:23.08-py3@sha256:12a39f22d6e3a3cfcb285a238b6219475181672ff41a557a75bdeeef6d630740                                                                                13.9s
=> => resolve nvcr.io/nvidia/pytorch:23.08-py3@sha256:12a39f22d6e3a3cfcb285a238b6219475181672ff41a557a75bdeeef6d630740                                                                                0.1s
=> [devel  1/10] COPY docker/common/install_base.sh install_base.sh                                                                                0.3s
=> [devel  2/10] RUN bash ./install_base.sh && rm install_base.sh                                                                                88.4s
=> [devel  3/10] COPY docker/common/install_cmake.sh install_cmake.sh                                                                                0.5s
=> [devel  4/10] RUN bash ./install_cmake.sh && rm install_cmake.sh                                                                                577.6s
=> [devel  5/10] COPY docker/common/install_tensorrt.sh install_tensorrt.sh                                                                                0.6s
=> ERROR [devel  6/10] RUN bash ./install_tensorrt.sh && rm install_tensorrt.sh                                                                                341.0s

[devel  6/10] RUN bash ./install_tensorrt.sh && rm install_tensorrt.sh:
#11 0.710 ++ grep -oP '(?<=^ID=).+' /etc/os-release
#11 0.711 ++ tr -d '"'
#11 0.714 + ID=ubuntu
#11 0.714 + case "$ID" in
#11 0.714 + install_ubuntu_requirements
#11 0.714 + CUDNN_VERSION=8
#11 0.714 + apt-get update
#11 1.336 Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
#11 1.401 Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
#11 3.027 Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
#11 3.058 Get:4 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [1010 kB]
#11 3.404 Get:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
#11 3.774 Get:6 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [17.5 MB]
#11 4.534 Get:7 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1203 kB]
#11 4.875 Get:8 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [1404 kB]
#11 5.158 Get:9 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [44.0 kB]
#11 7.525 Get:10 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1792 kB]
#11 7.778 Get:11 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [164 kB]
#11 7.783 Get:12 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [266 kB]
#11 7.792 Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1473 kB]
#11 8.758 Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1278 kB]
#11 8.775 Get:15 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [49.8 kB]
#11 8.776 Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1430 kB]
#11 9.105 Get:17 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [78.3 kB]
#11 9.111 Get:18 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [32.6 kB]
#11 9.205 Fetched 28.3 MB in 8s (3352 kB/s)
#11 9.205 Reading package lists...
#11 9.819 + apt-get install -y --no-install-recommends libcudnn8 libcudnn8-dev libnccl-dev
#11 9.874 Reading package lists...
#11 10.45 Building dependency tree...
#11 10.58 Reading state information...
#11 10.71 libcudnn8 is already the newest version (<IP_ADDRESS>-1+cuda12.2).
#11 10.71 libcudnn8-dev is already the newest version (<IP_ADDRESS>-1+cuda12.2).
#11 10.71 libnccl-dev is already the newest version (2.18.3-1+cuda12.2).
#11 10.71 0 upgraded, 0 newly installed, 0 to remove and 47 not upgraded.
#11 10.71 + apt-get clean
#11 10.72 + rm -rf /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy-backports_InRelease /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy-backports_main_binary-amd64_Packages.lz4 /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy-backports_universe_binary-amd64_Packages.lz4 /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy-updates_InRelease /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy-updates_main_binary-amd64_Packages.lz4 /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy-updates_multiverse_binary-amd64_Packages.lz4 /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy-updates_restricted_binary-amd64_Packages.lz4 /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy-updates_universe_binary-amd64_Packages.lz4 /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy_InRelease /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy_main_binary-amd64_Packages.lz4 /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy_multiverse_binary-amd64_Packages.lz4 /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy_restricted_binary-amd64_Packages.lz4 /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_jammy_universe_binary-amd64_Packages.lz4 /var/lib/apt/lists/auxfiles /var/lib/apt/lists/lock /var/lib/apt/lists/partial /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_jammy-security_InRelease /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_jammy-security_main_binary-amd64_Packages.lz4 /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_jammy-security_multiverse_binary-amd64_Packages.lz4 /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_jammy-security_restricted_binary-amd64_Packages.lz4 /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_jammy-security_universe_binary-amd64_Packages.lz4
#11 10.74 + install_tensorrt
#11 10.74 + TENSOR_RT_VERSION=<IP_ADDRESS>
#11 10.74 + CUDA_VERSION=12.2
#11 10.74 ++ python -c 'import sys; print(".".join(map(str, sys.version_info[0:2])))'
#11 10.78 + PY_VERSION=3.10
#11 10.78 ++ echo 310
#11 10.78 + PARSED_PY_VERSION=310
#11 10.78 + '[' -z '' ']'
#11 10.78 + ARCH=amd64
#11 10.78 + '[' -z amd64 ']'
#11 10.78 + '[' amd64 = arm64 ']'
#11 10.78 + '[' amd64 = amd64 ']'
#11 10.78 + ARCH=x86_64
#11 10.78 + '[' x86_64 = x86_64 ']'
#11 10.78 + DIR_NAME=x64-agnostic
#11 10.78 + '[' x86_64 = aarch64 ']'
#11 10.78 + OS=linux
#11 10.78 + RELEASE_URL_TRT=https://developer.nvidia.com/downloads/compute/machine-learning/tensorrt/secure/9.1.0/tars/tensorrt-<IP_ADDRESS>.linux.x86_64-gnu.cuda-12.2.tar.gz
#11 10.78 + wget --no-verbose https://developer.nvidia.com/downloads/compute/machine-learning/tensorrt/secure/9.1.0/tars/tensorrt-<IP_ADDRESS>.linux.x86_64-gnu.cuda-12.2.tar.gz -O /tmp/TensorRT.tar
#11 320.5 2023-11-20 03:34:10 URL:https://developer.download.nvidia.cn/403.html [252/252] -> "/tmp/TensorRT.tar" [1]
#11 320.5 + tar -xf /tmp/TensorRT.tar -C /usr/local/
#11 337.8
#11 337.8 gzip: stdin: unexpected end of file
#11 337.8 tar: Unexpected EOF in archive
#11 337.8 tar: Unexpected EOF in archive
#11 337.8 tar: Error is not recoverable: exiting now

executor failed running [/bin/bash -c bash ./install_tensorrt.sh && rm install_tensorrt.sh]: exit code: 2
Makefile:46: recipe for target 'release_build' failed
make: *** [release_build] Error 1
This error occurs when building docker, how to solve it?

Can you try running last few lines locally?

https://github.com/NVIDIA/TensorRT-LLM/pull/11 10.78 + wget --no-verbose https://developer.nvidia.com/downloads/compute/machine-learning/tensorrt/secure/9.1.0/tars/tensorrt-<IP_ADDRESS>.linux.x86_64-gnu.cuda-12.2.tar.gz -O /tmp/TensorRT.tar
https://github.com/NVIDIA/TensorRT-LLM/pull/11 320.5 2023-11-20 03:34:10 URL:https://developer.download.nvidia.cn/403.html [252/252] -> "/tmp/TensorRT.tar" [1]
https://github.com/NVIDIA/TensorRT-LLM/pull/11 320.5 + tar -xf /tmp/TensorRT.tar -C /usr/local/

Can you try running last few lines locally?

#11 10.78 + wget --no-verbose https://developer.nvidia.com/downloads/compute/machine-learning/tensorrt/secure/9.1.0/tars/tensorrt-<IP_ADDRESS>.linux.x86_64-gnu.cuda-12.2.tar.gz -O /tmp/TensorRT.tar
#11 320.5 2023-11-20 03:34:10 URL:https://developer.download.nvidia.cn/403.html [252/252] -> "/tmp/TensorRT.tar" [1]
#11 320.5 + tar -xf /tmp/TensorRT.tar -C /usr/local/

After I re-run it several times, this problem no longer occurs, but the following problem appears again...

=> ERROR [wheel 9/9] RUN python3 scripts/build_wheel.py --clean --trt_root /usr/local/tensorrt                                                                                475.1s

[wheel 9/9] RUN python3 scripts/build_wheel.py --clean --trt_root /usr/local/tensorrt:
#25 1.232 Looking in indexes: https://pypi.org/simple, https://pypi.ngc.nvidia.com, https://pypi.ngc.nvidia.com
#25 2.703 Collecting build (from -r requirements.txt (line 1))
#25 2.704   Obtaining dependency information for build from https://files.pythonhosted.org/packages/93/dd/b464b728b866aaa62785a609e0dd8c72201d62c5f7c53e7c20f4dceb085f/build-1.0.3-py3-none-any.whl.metadata
#25 3.391   Downloading build-1.0.3-py3-none-any.whl.metadata (4.2 kB)
#25 3.394 Requirement already satisfied: torch in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 2)) (2.1.0a0+29c30b1)
#25 4.499 Collecting transformers==4.31.0 (from -r requirements.txt (line 3))
#25 4.499   Obtaining dependency information for transformers==4.31.0 from https://files.pythonhosted.org/packages/21/02/ae8e595f45b6c8edee07913892b3b41f5f5f273962ad98851dc6a564bbb9/transformers-4.31.0-py3-none-any.whl.metadata
#25 4.713   Downloading transformers-4.31.0-py3-none-any.whl.metadata (116 kB)
#25 5.162      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 116.9/116.9 kB 268.3 kB/s eta 0:00:00
#25 5.718 Collecting diffusers==0.15.0 (from -r requirements.txt (line 4))
#25 5.943   Downloading diffusers-0.15.0-py3-none-any.whl (851 kB)
#25 6.627      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 851.8/851.8 kB 1.3 MB/s eta 0:00:00
#25 7.224 Collecting accelerate==0.20.3 (from -r requirements.txt (line 5))
#25 7.225   Obtaining dependency information for accelerate==0.20.3 from https://files.pythonhosted.org/packages/10/d3/5382aa337d3e67214003a17b06bfc07cf0334356b4e8aaf3b12b0d38c83f/accelerate-0.20.3-py3-none-any.whl.metadata
#25 7.443   Downloading accelerate-0.20.3-py3-none-any.whl.metadata (17 kB)
#25 8.068 Collecting colored (from -r requirements.txt (line 6))
#25 8.068   Obtaining dependency information for colored from https://files.pythonhosted.org/packages/6f/0d/a10351ef1a98e0b03d66887ec2d87c261f9a0fbff8f2bdb75614cc0a2850/colored-2.2.3-py3-none-any.whl.metadata
#25 8.291   Downloading colored-2.2.3-py3-none-any.whl.metadata (3.6 kB)
#25 8.293 Requirement already satisfied: polygraphy in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 7)) (0.48.1)
#25 8.295 Requirement already satisfied: onnx>=1.12.0 in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 8)) (1.14.0)
#25 8.296 Requirement already satisfied: mpi4py in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 9)) (3.1.5)
#25 8.298 Requirement already satisfied: tensorrt>=8.6.0 in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 10)) (9.1.0.post12.dev4)
#25 8.299 Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 11)) (1.22.2)
#25 9.106 Collecting cuda-python==12.2.0 (from -r requirements.txt (line 12))
#25 9.106   Obtaining dependency information for cuda-python==12.2.0 from https://files.pythonhosted.org/packages/2b/5c/ad3b6bee78f95134834dc2ce8805fc12ac70d7a9ba065e2d7c05263549dc/cuda_python-12.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
#25 9.303   Downloading cuda_python-12.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (749 bytes)
#25 9.904 Collecting sentencepiece>=0.1.99 (from -r requirements.txt (line 13))
#25 10.14   Downloading sentencepiece-0.1.99-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.3 MB)
#25 10.94      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.3/1.3 MB 1.6 MB/s eta 0:00:00
#25 10.95 Requirement already satisfied: wheel in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 14)) (0.41.1)
#25 11.81 Collecting lark (from -r requirements.txt (line 15))
#25 11.81   Obtaining dependency information for lark from https://files.pythonhosted.org/packages/99/ca/f3532a61dce7dd52fbd38737a12e16cdc7699697e23287eb7addfdd93e3f/lark-1.1.8-py3-none-any.whl.metadata
#25 12.01   Downloading lark-1.1.8-py3-none-any.whl.metadata (1.9 kB)
#25 12.38 Requirement already satisfied: filelock in /usr/local/lib/python3.10/dist-packages (from transformers==4.31.0->-r requirements.txt (line 3)) (3.12.2)
#25 13.04 Collecting huggingface-hub<1.0,>=0.14.1 (from transformers==4.31.0->-r requirements.txt (line 3))
#25 13.04   Obtaining dependency information for huggingface-hub<1.0,>=0.14.1 from https://files.pythonhosted.org/packages/05/09/1945ca6ba3ad8ad6e2872ba682ce8d68c5e63c8e55458ed8ab4885709f1d/huggingface_hub-0.19.4-py3-none-any.whl.metadata
#25 13.24   Downloading huggingface_hub-0.19.4-py3-none-any.whl.metadata (14 kB)
#25 13.24 Requirement already satisfied: packaging>=20.0 in /usr/local/lib/python3.10/dist-packages (from transformers==4.31.0->-r requirements.txt (line 3)) (23.1)
#25 13.25 Requirement already satisfied: pyyaml>=5.1 in /usr/local/lib/python3.10/dist-packages (from transformers==4.31.0->-r requirements.txt (line 3)) (6.0.1)
#25 13.25 Requirement already satisfied: regex!=2019.12.17 in /usr/local/lib/python3.10/dist-packages (from transformers==4.31.0->-r requirements.txt (line 3)) (2023.6.3)
#25 13.25 Requirement already satisfied: requests in /usr/local/lib/python3.10/dist-packages (from transformers==4.31.0->-r requirements.txt (line 3)) (2.31.0)
#25 14.20 Collecting tokenizers!=0.11.3,<0.14,>=0.11.1 (from transformers==4.31.0->-r requirements.txt (line 3))
#25 14.40   Downloading tokenizers-0.13.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (7.8 MB)
#25 18.31      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.8/7.8 MB 2.0 MB/s eta 0:00:00
#25 19.37 Collecting safetensors>=0.3.1 (from transformers==4.31.0->-r requirements.txt (line 3))
#25 19.37   Obtaining dependency information for safetensors>=0.3.1 from https://files.pythonhosted.org/packages/20/4e/878b080dbda92666233ec6f316a53969edcb58eab1aa399a64d0521cf953/safetensors-0.4.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
#25 19.57   Downloading safetensors-0.4.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.8 kB)
#25 19.58 Requirement already satisfied: tqdm>=4.27 in /usr/local/lib/python3.10/dist-packages (from transformers==4.31.0->-r requirements.txt (line 3)) (4.65.0)
#25 19.66 Requirement already satisfied: Pillow in /usr/local/lib/python3.10/dist-packages (from diffusers==0.15.0->-r requirements.txt (line 4)) (9.2.0)
#25 19.67 Requirement already satisfied: importlib-metadata in /usr/local/lib/python3.10/dist-packages (from diffusers==0.15.0->-r requirements.txt (line 4)) (6.8.0)
#25 19.70 Requirement already satisfied: psutil in /usr/local/lib/python3.10/dist-packages (from accelerate==0.20.3->-r requirements.txt (line 5)) (5.9.4)
#25 19.70 Requirement already satisfied: cython in /usr/local/lib/python3.10/dist-packages (from cuda-python==12.2.0->-r requirements.txt (line 12)) (3.0.0)
#25 20.18 Collecting pyproject_hooks (from build->-r requirements.txt (line 1))
#25 20.41   Downloading pyproject_hooks-1.0.0-py3-none-any.whl (9.3 kB)
#25 20.41 Requirement already satisfied: tomli>=1.1.0 in /usr/local/lib/python3.10/dist-packages (from build->-r requirements.txt (line 1)) (2.0.1)
#25 20.43 Requirement already satisfied: typing-extensions in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 2)) (4.7.1)
#25 20.43 Requirement already satisfied: sympy in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 2)) (1.12)
#25 20.43 Requirement already satisfied: networkx in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 2)) (2.6.3)
#25 20.43 Requirement already satisfied: jinja2 in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 2)) (3.1.2)
#25 20.43 Requirement already satisfied: fsspec in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 2)) (2023.6.0)
#25 20.44 Requirement already satisfied: protobuf>=3.20.2 in /usr/local/lib/python3.10/dist-packages (from onnx>=1.12.0->-r requirements.txt (line 8)) (4.21.12)
#25 20.65 Requirement already satisfied: zipp>=0.5 in /usr/local/lib/python3.10/dist-packages (from importlib-metadata->diffusers==0.15.0->-r requirements.txt (line 4)) (3.16.2)
#25 20.66 Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.10/dist-packages (from jinja2->torch->-r requirements.txt (line 2)) (2.1.3)
#25 20.70 Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.10/dist-packages (from requests->transformers==4.31.0->-r requirements.txt (line 3)) (3.2.0)
#25 20.70 Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.10/dist-packages (from requests->transformers==4.31.0->-r requirements.txt (line 3)) (3.4)
#25 20.70 Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/local/lib/python3.10/dist-packages (from requests->transformers==4.31.0->-r requirements.txt (line 3)) (1.26.16)
#25 20.70 Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.10/dist-packages (from requests->transformers==4.31.0->-r requirements.txt (line 3)) (2023.7.22)
#25 20.71 Requirement already satisfied: mpmath>=0.19 in /usr/local/lib/python3.10/dist-packages (from sympy->torch->-r requirements.txt (line 2)) (1.3.0)
#25 20.95 Downloading transformers-4.31.0-py3-none-any.whl (7.4 MB)
#25 27.01    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.4/7.4 MB 1.2 MB/s eta 0:00:00
#25 27.21 Downloading accelerate-0.20.3-py3-none-any.whl (227 kB)
#25 27.37    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 227.6/227.6 kB 1.5 MB/s eta 0:00:00
#25 27.58 Downloading cuda_python-12.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (20.1 MB)
#25 57.51    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 20.1/20.1 MB 469.8 kB/s eta 0:00:00
#25 57.71 Downloading build-1.0.3-py3-none-any.whl (18 kB)
#25 57.94 Downloading colored-2.2.3-py3-none-any.whl (16 kB)
#25 58.16 Downloading lark-1.1.8-py3-none-any.whl (111 kB)
#25 58.42    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 111.6/111.6 kB 456.8 kB/s eta 0:00:00
#25 58.62 Downloading huggingface_hub-0.19.4-py3-none-any.whl (311 kB)
#25 59.35    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 311.7/311.7 kB 425.5 kB/s eta 0:00:00
#25 59.55 Downloading safetensors-0.4.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.3 MB)
#25 63.16    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.3/1.3 MB 372.8 kB/s eta 0:00:00
#25 64.94 Installing collected packages: tokenizers, sentencepiece, safetensors, pyproject_hooks, lark, cuda-python, colored, huggingface-hub, build, transformers, diffusers, accelerate
#25 65.29   Attempting uninstall: cuda-python
#25 65.29     Found existing installation: cuda-python 12.1.0rc5+1.g994d8d0
#25 65.30     Uninstalling cuda-python-12.1.0rc5+1.g994d8d0:
#25 65.35       Successfully uninstalled cuda-python-12.1.0rc5+1.g994d8d0
#25 69.24 Successfully installed accelerate-0.20.3 build-1.0.3 colored-2.2.3 cuda-python-12.2.0 diffusers-0.15.0 huggingface-hub-0.19.4 lark-1.1.8 pyproject_hooks-1.0.0 safetensors-0.4.0 sentencepiece-0.1.99 tokenizers-0.13.3 transformers-4.31.0
#25 69.24 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
#25 70.60
#25 70.60 [notice] A new release of pip is available: 23.2.1 -> 23.3.1
#25 70.60 [notice] To update, run: python3 -m pip install --upgrade pip
#25 71.35 -- The CXX compiler identification is GNU 11.4.0
#25 71.36 -- Detecting CXX compiler ABI info
#25 71.48 -- Detecting CXX compiler ABI info - done
#25 71.49 -- Check for working CXX compiler: /usr/bin/c++ - skipped
#25 71.49 -- Detecting CXX compile features
#25 71.49 -- Detecting CXX compile features - done
#25 71.49 -- NVTX is disabled
#25 71.49 -- Importing batch manager
#25 71.49 -- Building PyTorch
#25 71.49 -- Building Google tests
#25 71.49 -- Building benchmarks
#25 71.49 -- Looking for a CUDA compiler
#25 73.38 -- Looking for a CUDA compiler - /usr/local/cuda/bin/nvcc
#25 73.38 -- CUDA compiler: /usr/local/cuda/bin/nvcc
#25 73.41 -- GPU architectures: 70-real;80-real;86-real;89-real;90-real
#25 74.39 -- The CUDA compiler identification is NVIDIA 12.2.128
#25 74.40 -- Detecting CUDA compiler ABI info
#25 76.54 -- Detecting CUDA compiler ABI info - done
#25 76.58 -- Check for working CUDA compiler: /usr/local/cuda/bin/nvcc - skipped
#25 76.58 -- Detecting CUDA compile features
#25 76.58 -- Detecting CUDA compile features - done
#25 76.59 -- Found CUDAToolkit: /usr/local/cuda/include (found version "12.2.128")
#25 76.61 -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
#25 76.73 -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
#25 76.73 -- Found Threads: TRUE
#25 76.77 -- ========================= Importing and creating target nvinfer ==========================
#25 76.77 -- Looking for library nvinfer
#25 76.77 -- Library that was found /usr/local/tensorrt/targets/x86_64-linux-gnu/lib/libnvinfer.so
#25 76.77 -- ==========================================================================================
#25 76.77 -- ========================= Importing and creating target nvuffparser ==========================
#25 76.77 -- Looking for library nvparsers
#25 76.77 -- Library that was found nvparsers_LIB_PATH-NOTFOUND
#25 76.77 -- ==========================================================================================
#25 76.77 -- CUDAToolkit_VERSION 12.2 is greater or equal than 11.0, enable -DENABLE_BF16 flag
#25 76.77 -- CUDAToolkit_VERSION 12.2 is greater or equal than 11.8, enable -DENABLE_FP8 flag
#25 77.20 -- Found MPI_CXX: /opt/hpcx/ompi/lib/libmpi.so (found version "3.1")
#25 77.20 -- Found MPI: TRUE (found version "3.1")
#25 77.20 -- COMMON_HEADER_DIRS: /src/tensorrt_llm/cpp;/usr/local/cuda/include
#25 77.20 -- TORCH_CUDA_ARCH_LIST: 7.0;8.0;8.6;8.9;9.0
#25 77.20 CMake Warning at CMakeLists.txt:248 (message):
#25 77.20   Ignoring environment variable TORCH_CUDA_ARCH_LIST=5.2 6.0 6.1 7.0 7.5 8.0
#25 77.20   8.6 9.0+PTX
#25 77.20
#25 77.20
#25 77.60 -- Found Python3: /usr/bin/python3.10 (found version "3.10.12") found components: Interpreter Development Development.Module Development.Embed
#25 77.61 -- Found Python executable at /usr/bin/python3.10
#25 77.61 -- Found Python libraries at /usr/lib/x86_64-linux-gnu
#25 80.61 -- Found CUDA: /usr/local/cuda (found version "12.2")
#25 80.61 -- Found CUDAToolkit: /usr/local/cuda/include (found version "12.2.128")
#25 80.69 -- Caffe2: CUDA detected: 12.2
#25 80.69 -- Caffe2: CUDA nvcc is: /usr/local/cuda/bin/nvcc
#25 80.69 -- Caffe2: CUDA toolkit directory: /usr/local/cuda
#25 80.89 -- Caffe2: Header version is: 12.2
#25 81.05 -- /usr/local/cuda/lib64/libnvrtc.so shorthash is eaa826f0
#25 81.05 -- USE_CUDNN is set to 0. Compiling without cuDNN support
#25 81.06 -- Added CUDA NVCC flags for: -gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_89,code=sm_89;-gencode;arch=compute_90,code=sm_90
#25 81.09 CMake Warning at /usr/local/lib/python3.10/dist-packages/torch/share/cmake/Torch/TorchConfig.cmake:22 (message):
#25 81.09   static library kineto_LIBRARY-NOTFOUND not found.
#25 81.09 Call Stack (most recent call first):
#25 81.09   /usr/local/lib/python3.10/dist-packages/torch/share/cmake/Torch/TorchConfig.cmake:127 (append_torchlib_if_found)
#25 81.09   CMakeLists.txt:281 (find_package)
#25 81.09
#25 81.09
#25 81.09 -- Found Torch: /usr/local/lib/python3.10/dist-packages/torch/lib/libtorch.so
#25 81.09 -- TORCH_CXX_FLAGS: -D_GLIBCXX_USE_CXX11_ABI=1
#25 81.09 -- Building for TensorRT version: 9.1.0, library version: 9
#25 81.11 -- Using MPI_CXX_INCLUDE_DIRS: /opt/hpcx/ompi/include;/opt/hpcx/ompi/include/openmpi;/opt/hpcx/ompi/include/openmpi/opal/mca/hwloc/hwloc201/hwloc/include;/opt/hpcx/ompi/include/openmpi/opal/mca/event/libevent2022/libevent;/opt/hpcx/ompi/include/openmpi/opal/mca/event/libevent2022/libevent/include
#25 81.11 -- Using MPI_CXX_LIBRARIES: /opt/hpcx/ompi/lib/libmpi.so
#25 81.13 -- CMAKE_SYSTEM_PROCESSOR: x86_64
#25 82.62 -- USE_CXX11_ABI: True
#25 474.9 [ 11%] Creating directories for 'googletest-populate'
#25 474.9 [ 22%] Performing download step (git clone) for 'googletest-populate'
#25 474.9 Cloning into 'googletest-src'...
#25 474.9 fatal: unable to access 'https://github.com/google/googletest.git/': Failed to connect to github.com port 443 after 130010 ms: Connection timed out
#25 474.9 Cloning into 'googletest-src'...
#25 474.9 fatal: unable to access 'https://github.com/google/googletest.git/': Failed to connect to github.com port 443 after 131050 ms: Connection timed out
#25 474.9 Cloning into 'googletest-src'...
#25 474.9 fatal: unable to access 'https://github.com/google/googletest.git/': Failed to connect to github.com port 443 after 131050 ms: Connection timed out
#25 474.9 -- Had to git clone more than once: 3 times.
#25 474.9 CMake Error at googletest-subbuild/googletest-populate-prefix/tmp/googletest-populate-gitclone.cmake:39 (message):
#25 474.9   Failed to clone repository: 'https://github.com/google/googletest.git'
#25 474.9
#25 474.9
#25 474.9 gmake[2]: *** [CMakeFiles/googletest-populate.dir/build.make:102: googletest-populate-prefix/src/googletest-populate-stamp/googletest-populate-download] Error 1
#25 474.9 gmake[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/googletest-populate.dir/all] Error 2
#25 474.9 gmake: *** [Makefile:91: all] Error 2
#25 474.9
#25 474.9 CMake Error at /usr/local/cmake-3.24.4-linux-x86_64/share/cmake-3.24/Modules/FetchContent.cmake:1604 (message):
#25 474.9   Build step for googletest failed: 2
#25 474.9 Call Stack (most recent call first):
#25 474.9   /usr/local/cmake-3.24.4-linux-x86_64/share/cmake-3.24/Modules/FetchContent.cmake:1744:EVAL:2 (__FetchContent_directPopulate)
#25 474.9   /usr/local/cmake-3.24.4-linux-x86_64/share/cmake-3.24/Modules/FetchContent.cmake:1744 (cmake_language)
#25 474.9   /usr/local/cmake-3.24.4-linux-x86_64/share/cmake-3.24/Modules/FetchContent.cmake:1958 (FetchContent_Populate)
#25 474.9   tests/CMakeLists.txt:21 (FetchContent_MakeAvailable)
#25 474.9
#25 474.9
#25 474.9 -- Configuring incomplete, errors occurred!
#25 474.9 See also "/src/tensorrt_llm/cpp/build/CMakeFiles/CMakeOutput.log".
#25 474.9 See also "/src/tensorrt_llm/cpp/build/CMakeFiles/CMakeError.log".
#25 475.0 Traceback (most recent call last):
#25 475.0   File "/src/tensorrt_llm/scripts/build_wheel.py", line 248, in
#25 475.0     main(**vars(args))
#25 475.0   File "/src/tensorrt_llm/scripts/build_wheel.py", line 149, in main
#25 475.0     build_run(
#25 475.0   File "/usr/lib/python3.10/subprocess.py", line 526, in run
#25 475.0     raise CalledProcessError(retcode, process.args,
#25 475.0 subprocess.CalledProcessError: Command 'cmake -DCMAKE_BUILD_TYPE="Release" -DBUILD_PYT="ON"  -DTRT_LIB_DIR=/usr/local/tensorrt/targets/x86_64-linux-gnu/lib -DTRT_INCLUDE_DIR=/usr/local/tensorrt/include -S "/src/tensorrt_llm/cpp"' returned non-zero exit status 1.

executor failed running [/bin/bash -c python3 scripts/build_wheel.py ${BUILD_WHEEL_ARGS}]: exit code: 1
Makefile:46: recipe for target 'release_build' failed
make: *** [release_build] Error 1
make: Leaving directory '/data/yankai/TensorRT-LLM/docker'

Please confirm that you can access github.com and other related websites normally. Thanks!


Source Request: NSFW Rule 34

Source name
NSFW Rule 34
Source link
https://nsfwr34.com
Source language
English
Other details
+18/NSFW=Yes
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist on the website extensions list or the app.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

Isn't this the same as the existing rule 34 extension?

Isn't this the same as the existing rule 34 extension?

If you open the website you will see that they are different websites


Sankey tooltip is not visible on the right of the chart

On Sankey visualizations, the tooltips always appear to the right of the cursor, which can sometimes be cut-off if it runs off the chart. This means that users are unable to read the tooltip for the "targets".
This might technically be a cosmetic issue, but since this bug results in users being unable to read tooltips, I filed it as a bug.
Expected results
Tooltip should adjust its position to always be visible, instead of always appearing to the right of the cursor. Ideally, I think the tooltip would follow the cursor (similar to line charts).
Actual results
Tooltip always appears to the right of the cursor, so it sometimes gets cut off.
Screenshots
https://user-images.githubusercontent.com/14146019/116744917-a787d500-a9af-11eb-8049-fbc84d645ba3.mov
How to reproduce the bug

Create a Sankey viz
Hover mouse over the chart near the right side

Environment
(please complete the following information):

superset version: superset version: up-to-date with master as of April 2021
python version: python --version: 3.8
node.js version: node -v: v14.16.1

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[X] I have checked the superset logs for python stacktraces and included it here as text if there are any. (frontend, so n/a)
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

fixed


Dialyzer warnings

👋🏼 Hi there. Thanks for sharing this library 🙌🏼 .
I'm playing around with it to implement some basic union types. However, Elixir's LD Dialyzer is complaining about overloaded contracts and invalid specifications:
defmodule MyApp.Result do
  import ExUnion

  defunion(ok(value) | error(value))
end

Overloaded contract for 'Elixir.MyApp.Result.Error':new/1 has overlapping domains; such contracts are currently unsupported and are simply ignored (ElixirLS Dialyzer)
──────────────────────────────────────────────────────────────────────────────
Overloaded contract for 'Elixir.MyApp.Result.Ok':new/1 has overlapping domains; such contracts are currently unsupported and are simply ignored (ElixirLS Dialyzer)
──────────────────────────────────────────────────────────────────────────────
Invalid type specification for function 'Elixir.MyApp.Result':'__union__'/0. The success typing is
          () ->
             #{'__struct__' := 'Elixir.ExUnion.Definition',
               'module' := 'Elixir.MyApp.Result',
               'name' := <<_:48>>,
               'types' :=
                   [#{'__struct__' := 'Elixir.ExUnion.Definition.Type',
                      'fields' := [any(), ...],
                      'module' :=
                          'Elixir.MyApp.Result.Error' |
                          'Elixir.MyApp.Result.Ok',
                      'name' := 'error' | 'ok'},
                    ...]} (ElixirLS Dialyzer)

Are you also experiencing this?

Thank you for the report. I knew I forgot something  - that is checking the generated type-specs. 😄
I'll check it out over the week. 👍

Awesome! 🙌🏼

Resolved in v0.1.1

Awesome @sascha-wolf, thank you 🙌🏼 !


Small gramatical fixes proposal

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


Zah review changes

There's one design issue that bothers me, and with this pr it becomes apparent. The issue is that eth procs are implied to be implemented in a single (rigidly included) file. This is because the rpc macro is so tempting, but it is not available to the rest of the world. TBH I don't consider the rpc macro useful at all (it's really simplistic and does straightforward but not obvious transformations), instead I would prefer smth like the following:
# rpc_debug_interface.nim
import rpc_server
# ... more imports

let s = sharedRpcServer()

s.on("debug.verbosity") do(a: JsonNode) -> JsonNode:
  # change verbosity

s.on("debug.dropDb") do(a: JsonNode):
  # drop db

# rpc_eth_interface.nim
import rpc_server

let s = sharedRpcServer()
s.on("eth.getBallance") do(a: JsonNode) -> JsonNode:
  # get balance

Basically your impl already allows something similar, it's just about the decoupling approach. Further improvements could be auto marshalling of Jsons:
s.on("debug.dropDb") do() -> bool:
  # drop db. Note how I'm not taking any args, and returning bool.
  return true

s.on("debug.verbosity") do(level: int):
  # change verbosity. Note how I'm taking int arg, and returning nothing.

Hope that makes sense.

@yglukhov
Before this PR, the ethprocs were a separate semi-independent module, but it became apparent that in order to get the 'built in' ethproc rpcs into the compile time list (that automatically sets up new servers with procs registered using the {.rpc.} macro), and also allow 3rd party rpc procs too, the ethprocs would have to be visible at compile time to the initServer call.
This is because, as far as I can tell, once a module is imported it's macros are expanded and thus the code is 'fixed' to only have the calls that have already been processed by {.rpc.} at the module import time.
Honestly, I'm not happy about this set up. Working in included files is not a great experience; you lose all your type checking for that file as, at least in this case, the server types aren't visible to ethprocs.
I had hoped to have ethprocs as a (theoretically) optional import that just added the default Ethereum rpc calls, but as it stands it's not this flexible.
In the current scheme, if the registration is taken out of newRpcServer, ethprocs wouldn't need to be included, but this forces the user to have to manually call registerRpcs(server) even to get the 'built in' ethprocs calls, which I had wanted to avoid.
Your macro ideas are interesting and something to consider. I agree that the {.rpc.} macro isn't necessarily giving you gains when writing rpc calls, especially as with this PR it constrains ethprocs to require being included in the main server types module.
I like the idea of namespaces and being able to separate out calls from VM to debug and other situations. I also like the do: variant of writing calls and marshalling to JSON automatically.
However I do feel that decoupling is sorely needed at this stage.
@zah do you have any thoughts on this?

@coffeepots

in order to get the 'built in' ethproc rpcs into the compile time list

Is there such a necessity? I can't see any other usages of rpcCallRefs except adding into it, and passing it to register in runtime.

In the current scheme, if the registration is taken out of newRpcServer, ethprocs wouldn't need to be included, but this forces the user to have to manually call registerRpcs(server) even to get the 'built in' ethprocs calls, which I had wanted to avoid.

So with my approach there would be no need to additionally register anything. The on function would just add the handler to the server.

However I do feel that decoupling is sorely needed at this stage.

I'm pretty sure the limitations will be visible very soon. servertypes includes ethprocs. Now correct me if I misunderstood your intention. servertypes itself sounds like a pretty common name that is going to end up being imported in a lot of other nimbus modules (directly or indirectly). It is likely you're going to import nimbus files in ethprocs (which is bad on its own, because that would introduce cyclic package dependency), and it is extremely likely to introduce import cycles. Breaking the cycles after they live for a while in a project is a big pita from my experience :).

It is likely you're going to import nimbus files in ethprocs (which is bad on its own, because that would introduce cyclic package dependency), and it is extremely likely to introduce import cycles.

I think this is reason for a refactor on its own. I'm going to look at this today.

I believe so, as otherwise you need to re-define your rpc calls for each server you set up. However there's probably a better way to do this.

Adding the same set of handlers to different servers (if that's what you mean) is pretty easy with my suggestion:
proc addDebugFunctions(s: RpcServer) =
  s.on("debug.dropDB") do():
    # drop db
  s.on("debug.verbosity") do(level: int):
    # set verbosity

addDebugFunctions(sharedRpcServer())
addDebugFunctions(anotherRpcServer())

@yglukhov, one detail that you might be missing is that I requested that these handlers should be async procs (because replying to some RPC call may require executing other async operations).
This can be done with your proposed interface, but it will have a transformation.
Regarding the use of an included file, we should kill this indeed. We don't need to use compile-time mechanisms for everything. It's perfectly fine for the macro to call a run-time registerRpcHandler proc, which just adds a function pointer to some run-time table. It woudn't even be a problem to spread the implementations across multiple files then.

one detail that you might be missing is that I requested that these handlers should be async procs

@zah, yes, I skipped those intentionally to simplify reading of my snippets. The do closures should return Future[JsonNode] at the most generic level. But with automarshalling it could be done automagically for sync procs.


[SPARK-44519][CONNECT] SparkConnectServerUtils generated incorrect parameters for jars

What changes were proposed in this pull request?
https://github.com/apache/spark/pull/41932 try to add test case for connect, then we found the maven build failure based on the bug discussed at https://github.com/apache/spark/pull/41932#discussion_r1266118099
After some communication, @cloud-fan and @zhengruifeng suggested to ignore the test case for connect.
So I commit this PR to fix the bug.
Why are the changes needed?
Fix the bug that SparkConnectServerUtils generated incorrect parameters for jars.
Does this PR introduce any user-facing change?
'No'.
Just update the inner implementation.
How was this patch tested?
N/A

ping @LuciferYang cc @HyukjinKwon @zhengruifeng

Merged into master and branch-3.5. Thanks @HyukjinKwon @beliefer

@LuciferYang @HyukjinKwon Thank you !


airpods4

Airpods 4 (active noise reduction version) cannot take effect on ios16.2. Please update it for him.

Is there anyone knows how to update for Airpod 4?

Anyone able to provide the product ID for AirPods 4?

Anyone able to provide the product ID for AirPods 4?

Model Name: ACCESSORY_MODEL_NAME_27
Model Number: A3057
Is this help?

airpods4:A3057（8219）
This is the active noise reduction version, hope to help you

有人能提供AirPods 4的产品ID吗？

8219

waiting

Please update Airpods 4

Sorry guys been busy recently, commit 18ed868 probably solves this, closing this one for now

Thanks for your fruitful working, may I get a release *.deb file then? I don't know how to compile or update🥰

Thanks for your fruitful working, may I get a release *.deb file then? I don't know how to compile or update🥰

Check Releases tab for 0.4 prerelease 2

Got it!

Hi, does it work for Airpods 4 ANC + iOS 16.4?


Add features to make creating devices easier

In the list of available devices and scenes, add a column with checkboxes, and and editable column for the names.  Have a "bulk add checked devices" button at the bottom.  Have some indication of what devices have already been created.

Do you still need this feature? Trying to get a sense if there is a huge need for this.

This was added in v0.3.0


Compile of Stateless widget reports problem with a non-final field but runs correctly

I started with the default project. I added a String field called "app".
Then I wrote a simple constructor that referenced the app field in the constructor's argument.
eg.  myClass(({Key? key, this.app = ''}) : super(key: key);
When I compile it the field definition is flagged as a non final field which it is.
eg  String app == '';        This is the statement that has the error.
when I write it as  "final String app = '';"  the constructor statement above is flagged with an error.
If I leave the field non final everything works correctly. I invoke the class from the main routine
passing in the "app" value. The value is set in the instance of the class and the field is
reference in the "appBar" element and displays the correct text passed to the constructor.
Is there a better way to code this without an error? Can the error checker be changed to detect
that the only place the violation is due to the "constructor", or a possible "init" section.  I know, but
then what about a function that is called by the constructor or init section?   Too complicated.
Well then how about a non immutable widget which overrides a build function  "Widget build(...)".
But it should allow for a inherited data section that only allows a one time set value for each
field it contains.
How do you pass initial values to a class that is immutable. It seems the immutable definition
is not a function of the language but an error that flutter is trying to enforce, with some contradictions.

Hi @leemke
Try the code sample below

minimal code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      theme: ThemeData.dark(),
      home: const Home(
        app: 'My AppBar',
      ),
    );
  }
}

class Home extends StatelessWidget {
  const Home({Key? key, this.app = ''}) : super(key: key);

  final String app;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(app),
      ),
      body: const FlutterLogo(size: 300),
    );
  }
}

Analyzing master_flutter...
No issues found! (ran in 1.5s)

You need to mark it as final and you still pass text from the parent widget
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this, you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Improve cleanup of log files

Consider ways to automatically clean up log (and plan) files, without compromising supportability. (And bearing in mind that sometimes support is required for jobs in which AzCopy itself thinks it succeeded, and so would automatically delete the logs in a simple delete-on-success approach.  The prime example is performance-related support issues).
This issue is branched from #221

Since this is a new thread I'm going to summarize the situation.

AzCopy writes two types of files in order to do its work: log files and plan files
The parameter --log-level NONE may be used to prevent logs from being written but plan files must always be written
The location of the plan files may be moved by using AZCOPY_JOB_PLAN_LOCATION
The location of the log files may be moved by using AZCOPY_LOG_LOCATION
All log and plan files may be cleaned up by running azcopy a second time with the jobs clean parameter
There is no azcopy feature that will clean up individual job files in the same process that writes them
If the caller to azcopy wants to run jobs concurrently and needs the files to be cleaned up individually, she must parse output from each job and clean the files up with a separate process

(And bearing in mind that sometimes support is required for jobs in which AzCopy itself thinks it succeeded, and so would automatically delete the logs in a simple delete-on-success approach. The prime example is performance-related support issues).

In performance related support issues the user would be running multiple times and could turn on the switch to keep files.  The rest of us can use the switch to clean up.  I don't care if azcopy defaults to keeping everything under the sun.   It should be a good citizen and clean up after itself--even if that has to be activated by the caller using a switch or environment variable or magic incantation.
There is no situation where the performance is bad just one time that would result in needing the logs.  If the performance is bad on one run but all subsequent runs are fine it is an outlier.  If the user has sporadic performance problems then they need to keep all logs until they figure it out by using appropriate switches (or the default).  The rest of us would really appreciate a clean up parameter so that we don't have to do extra work to pick up after azcopy.

If the caller to azcopy wants to run jobs concurrently and needs the files to be cleaned up individually, she must parse output from each job and clean the files up with a separate process

For completeness, if she wanted to get a bit fancy, should you set up separate environments for each instance, with different AZCOPY_JOB_PLAN_LOCATION and AZCOPY_LOG_LOCATION, which would in theory allow the use of azcopy jobs clean.  I'm not sure I'd necessarily advise that, because if you mess it up you'll end up deleting (or at least trying to delete) files belonging to another instance.  But it is theoretically possible.
Thanks for your summary here @jtmoree-kahalamgmt-com .  This issue is on our list to consider in prioritization of future work.  I can't guarantee any particular decision regarding timing.

Is there a reason azcopy creates a new file for each invocation instead of appending to an existing log-file? I wouldn't be complaining about clean-up if azcopy simply appended to a small number of files.
On a related subject, can you enable date-time prefixes in the generated files? That way I can use a glob to clean-up older files without having to inspect each log file's last-write-time value.

Good question re one file or many. I worked on a previous tool that used a one-file approach, and it did have some downsides. (E.g. if customer wanted to send log to us for support, it was hard for us and them to find the right part).
We'll have to think about the prefix question. Thanks for asking it.
BTW, if really want date-based naming or similar, and you don't mind writing a little script, you can have a script that sets the environment variables AZCOPY_LOG_LOCATION and AZCOPY_JOB_PLAN_LOCATION to something date based (or unique in some other way) before each run of AzCopy.

I just had a server where AzCopy already create 30GB of logs in three months time... Seems to not be a very reasonable default. Keeping n Files per Default would be a lot more user friendly.

Thanks for your summary here @jtmoree-kahalamgmt-com

Seconded! Thank you.

I don't care if azcopy defaults to keeping everything under the sun. It should be a good citizen and clean up after itself

This.
A lot of other software has temporary files too. BUT they are left behind only when something goes wrong; as soon as everything is completed fine then temporary files are automatically cleaned. Why doesn't azcopy let us have very simple, nice things that every other software provides?
This is especially true for binary "plans" that only azcopy itself can understand and re-use. Logs are more complicated because most users want to keep them for some about of time or some amount of disk space using logrotate or a similar approach, see earlier discussions in #221.
On the other hand, if the transfer went well  then why would any user want to preserve a "plan" and the ability to resume a transfer that was completed fine? That does not make any sense to me, what am I missing? Listing previous, successful jobs with azcopy jobs list should not require as much disk as if they all failed.

The rest of us would really appreciate a clean up parameter so that we don't have to do extra work to pick up after azcopy. [...]
even if that has to be activated by the caller using a switch or environment variable or magic incantation.

Exactly: changing default behavior is disruptive, we get it. But at the very least azcopy should have some --behave-like-every-other-tools options.

Is there a reason azcopy creates a new file for each invocation instead of appending to an existing log-file?

Separate files is convenient for interactive use where multiple copies can be running at the same time. On the other hand it's mostly useless and painful for regular "cron" jobs, see earlier discussions in #221

For completeness, if she wanted to get a bit fancy, she could set up separate environments [...] and you don't mind writing a little script, [...]

“Simple things should be simple, complex things should be possible.” Why require every user to duplicate the same efforts to "setup environments" or "write little scripts" which is time-consuming and error prone for basic features that are usually built-in in other, similar software? Logging must be either logrotate-friendly or provide logrotate features built-in. It's really that simple. How come azcopy developers never experience this lack of log rotation themselves, are they never automating azcopy for anything? Do they use some other, Windows-specific log rotation tool that azcopy is more compatible with?

This issue is on our list to consider in prioritization of future work. I can't guarantee any particular decision regarding timing.

This was in October 2019. So this issue is not officially but practically in the "closed as wontfix" state?

So the main purpose of "plan" files seems to support resuming partially failed transfer with azcopy jobs resume https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-configure "Find errors and resume jobs by using log and plan files in AzCopy"
This looks like a great feature but if transfer "plans" are leveraging disk space one wonders why azcopy sync memory usage seems to grow really fast and linearly with the number of files. In fact azcopy sync is simply running out of memory for large file sets (and hogging the entire system memory for smaller ones):

#1215

Is there already an issue filed about this memory (ab)use and lack of scalability? #693 seems more focused on one particular detail.

@marc-hb Sync does some in-memory processing which copy does not do, and that uses RAM. So in some cases, it's better to simply configure "copy" to have behaviour that is similar (but not identical) to "sync".  See https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-optimize#optimize-file-synchronization
BTW, I moved to a different team a couple of years ago, so I'm not actively involved in AzCopy now, but am responding here because I see that this is a thread which I started :-)

For anyone unfamiliar with the tool, but looking for a way to clean leftovers:
azcopy jobs list
azcopy jobs clean

I've just wasted an hour of my life chasing this through issue ticked after issue ticket, and my general impression that "version 10" of azcopy is not suitable for production usage. Several of its developers made comments that the requirements of the users is much less important than the convenience of azcopy developers being able to track down bugs via collecting always-on log files.
Filling up customer system disks with files nobody asked for is not how production-ready software is written.
On Windows the standard is to write to the Event Log, which is a fixed-sized circular buffer and won't fill the disk.
On Linux the standard is for CLI utilities to output nothing on success, and have no side effects other than what is explicitly configured.
For PowerShell and similar advanced CLIs, the standard is to enable background/resumable jobs ONLY if explicitly prompted by users. E.g.: how can "azcopy" securely store the configuration parameters for resumable jobs!? Either it throws the SAS token away which makes the job not really resumable, or it is leaving secrets on disks where the end-user is not expecting this!
It has been 4+ years of many users patiently explaining to the azcopy team that they're not writing a toy utility for their own personal use.
Please just do what has been asked: Logging should be off by default, leave an option to enable it, and don't waste time with silly half-measures like "--log-level NONE" not actually disablings logs!

There are commands to cleanup and wipe out older job files. These files are kept by default (untill cleared by user manually) so that at any moment user can go back and check the status of a given job to identify if any of the job failed and what all files were not copied successfully. User can resume the job as well to continue with whatever failed last time. If you think job is done and there is no need to keep the status now then using job cleanup command you can delete these files.

@vibhansa-msft this issue should not have been closed as "completed" (if so, where's the PR?) - whereas a more honest action would be "closed as wontfix".
...but a better response would be to re-open this issue with an admission that unchecked logfile build-up without even the option for automatic cleanup is not a hallmark of good-quality software that meets its users' needs.
...at the very least, shouldn't a first-party Microsoft title be a good citizen on its own platform by integrating with Windows' Disk Cleanup utility?


wltest: add support for Android 4.4 on Hikey 620

Tested using Jankbench with the bootloader provided with the following AOSP factory image: https://developers.google.com/android/images-preview#hikey
More recent bootloaders require a UEFI-specific boot.img and won't be compatible with this implementation.
Instructions to set-up the board:
https://github.com/96boards/documentation/blob/master/ConsumerEdition/HiKey/Installation/LinuxFactoryImage.md
Userspace image (and ramdisk) from the latest linaro AOSP build supporting the 4GB EMMC Hikey620:
http://builds.96boards.org/snapshots/hikey/linaro/aosp-master/509/
I wonder where these details should be documented. A README in each platform folder maybe ?

I'll run more extensive tests using this next week so I suggest we wait until then to be sure it's all stable ;).

OK - this all LGTM so once you have tested feel free to hit the merge button.

I have been running Jankbench, Exoplayer and homescreen overnight, on 5 different kernels. Looks good, I merge


Feedback errors on devices when preview

Hey,
I am fresh to Nativescript, I run into a problem which I cant get fixed.
When i'm testing it within the emulator everything works fine, but when I preview it on my android and iPhone device its giving the next error:
IOS:
ERROR Error: Uncaught (in promise): ReferenceError: Can't find variable: ISMessages
Android:
ERROR Error: Uncaught (in promise): TypeError: Cannot read property 'alerter' of undefined
I already tried to remove the platforms and rebuild it again, but unfortunately no luck.
Is there maybe another solution?
PS: Thanks for everything :)

This repo needs updating, I don't think it's too compatible with the latest NativeScript release. If you want to learn NativeScript please look elsewhere for now.


Get rid of slotattestation.DefaultAttestationCommitmentOffset and replace with a protocol parameter

          Shouldn't `slotattestation.DefaultAttestationCommitmentOffset` be a protocol parameter or removed completely? What if different implementations use different values?

Originally posted by @piotrm50 in https://github.com/iotaledger/iota-core/pull/171#discussion_r1254208733

This has been done with #221


error with file_get_contents

The following code results in a warning:
use org\bovigo\vfs\vfsStream as Vsf;

$root = Vsf::setup('dir');
Vsf::newFile('foo')->at($root)->withContent('~');
file_get_contents(Vsf::url('dir/foo'));

Warning: file_get_contents(vfs://dir/foo): failed to open stream:
"org\bovigo\vfs\vfsStreamWrapper::stream_open" call failed

Am I missing something?

Sorry for not getting back to this earlier. I just tested with your snippet code, and it works:
➜  vfsStream git:(master) ✗ cat foo.php
<?php
require 'vendor/autoload.php';

use org\bovigo\vfs\vfsStream as Vsf;

$root = Vsf::setup('dir');
Vsf::newFile('foo')->at($root)->withContent('~');
var_dump(file_get_contents(Vsf::url('dir/foo')));

➜  vfsStream git:(master) ✗ php foo.php
string(1) "~"

Can you post more details (e.g. PHP version, probably related php.ini settings)?

Hi, this happened long time ago. I don't remember the context anymore. You can close it if you wish. If I ever get to know how to reproduce it again, the issue will be reopened :)

Ok :)


added terraform controller module

Terraform controller is a class that is a layer on top of terraform. It
will create the configuration file, create and destroy infrastructure,
get resources information...
On this commit, the first draft of the controller was created.

A few thing to improve:

Instead of passing the aws credentials by parameter, use ~/.aws/credentials file. With the option to specify a profile if it's different that the default.
Add more comments of the functions
Create a utils function to execute shell commands and exit if encounters and error

Just a question from an outsider: Why are you dynamically assembling terraform configuration? It's usually much simpler to have a static one in a repo and then inject variables: https://learn.hashicorp.com/tutorials/terraform/variables

I don't much about terraform, but we need instances on different regions (we don't know beforehand how many or which regions we will need). Do you think this is possible with a static configuration?

One of the examples in the tutorial is actually showing customizing the region: https://learn.hashicorp.com/tutorials/terraform/variables?in=terraform/configuration-language#parameterize-your-configuration

One of the examples in the tutorial is actually showing customizing the region: https://learn.hashicorp.com/tutorials/terraform/variables?in=terraform/configuration-language#parameterize-your-configuration

But we need the configuration to have one or multiple providers, and one or multiple instances. Depending on the number of regions that the EXD team provides

I think you have two options:

Pass an array as a variable.
You can just call terraform multiple times with different variables and state files.


Please add guts.plus

It measures 73.9KB uncompressed according to https://gtmetrix.com/reports/guts.plus/yiwGfdgV/

Oops, it's already on there lol


Introduce Button extension for calling asynchronous operations

extension Button {

    public init(action: @escaping () async -> Void, @ViewBuilder label: () -> Label) {
        self.init {
            Task {
                await action()
            }
        } label: {
            label()
        }
    }

}

Added to Interact in https://github.com/inseven/interact/pull/67.


Add installation/setup instructions for Ubuntu

Kusma,
I have switched from Win7 to Lubuntu and finally got Rocket set up the other day on the new OS \o/ .  It took me a bit of trial and error to get everything right.  I wrote up my notes and offer them in this PR for the benefit of others.  Let me know what you think!
cxw

Updated!  I also had to add a .gitignore entry for a file created by the Qt5 make process.  Thanks for the quick response and feedback!

I see the build passed Travis (here), but the Travis status in GH shows as "Expected".  Please let me know if there's anything I need to do!

Sorry, I'm just low on time right now!


NavigationViewItem Icon disappear in NavigationView PaneFooter (2.6 prerelease)

Describe the bug
The icon of NavigationViewItems in the PaneFooter disappear.
Steps to reproduce the bug
Add some NavigationViewItems with an icon  in a PaneFooter
Expected behavior
Icon appear like in MenuItems
Screenshots

Version Info

NuGet package version:
[Microsoft.UI.Xaml.2.6.0-prerelease.210227001]
[Microsoft.UI.Xaml.2.6.0-prerelease.210217002]

Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2020 Update (19042)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context
Was working until:
[Microsoft.UI.Xaml.2.6.0-prerelease.210129001]

@karenbtlai FYI @Psykobal I assume that the "Menu Item1" item is supposed to have an icon?

Can you provide the xaml you used to get this UI? or better yet a repro project.

I made a repro project: NavigationViewTest
It has 4 variations. Do you need more details?


Issue 44 resolved

Description
Please provide a meaningful description of what this change will do, or is for. Bonus points for including links to
related issues, other PRs, or technical references.
Note that by not including a description, you are asking reviewers to do extra work to understand the context of this
change, which may lead to your PR taking much longer to review, or result in it not being reviewed at all.
Type of Change

[x] Bug Fix
[x] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[ ] Other (please describe)

Checklist

[x] I have read the contributing guidelines
[x] Existing issues have been referenced (where applicable)
[x] I have verified this change is not present in other open pull requests
[x] Functionality is documented
[x] All code style checks pass
[x] New code contribution is covered by automated tests
[x] All new and existing tests pass

Hey! @vatsalshah041
Thank you for the PR. I have reviewed the commits and left a few comments.
In general, I think there are 2 main issues:

debugging code is present in many places, which should be cleaned.
change in ports is breaking the application when it is run locally.

Can you please have a look at those?


Having Export/Import problem with the AutoComplete Cache

As soon as I attempt to Import the saved msg file, the application crashes with "MFCMAPI x64 has stopped working"
Do you have any suggestions?
New computer from Dell.  Never has been used.
Winver: 1709 (16299.214)
MFCMapi: x<IP_ADDRESS>99.01

likely no longer repros


error

File "D:\Masendor-master\gamescript\gameunitstat.py", line 169, in init
for row in rd:
UnicodeDecodeError: 'gbk' codec can't decode byte 0x94 in position 47: illegal multibyte sequence

This issue is likely fixed by now.


fix: add get-kubeclipper.sh

What type of PR is this?

/kind flake
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for reviewers:

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

Codecov Report

Merging #554 (0409686) into release-1.3 (5553ed7) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@             Coverage Diff              @@
##           release-1.3     #554   +/-   ##
============================================
  Coverage        12.16%   12.16%
============================================
  Files              111      111
  Lines            16993    16993
============================================
  Hits              2067     2067
  Misses           14679    14679
  Partials           247      247

/assign @x893675
and need check pick to master

/lgtm
/approve

/cherrypick master


Pinch to zoom?

I need the pinch to zoom and pan features over pages and I would like to contribute to the project in order to achieve it.
Do you have any suggestion on where and how to start ?
I'm thinking of an extension of the CurlView that inherits its features and add the zoom code and the listeners for the touches.

same issue

I implemented pinch zoom here: https://play.google.com/store/apps/details?id=net.codecanyon.trimax.flipbook


Examples Layout Docs

I could imagine many new examples coming up :) . The current layout makes this hard as they will fill the header right?

Is there any Quarto layout to let us have a "gallery view like" https://scikit-learn.org/stable/auto_examples/index.html ?

Yes, I fully agree that it doesn't look amazing and that there are many more example notebooks to be written (e.g. I'd like to have a side by side comparison of r-fixest and py-fixest as @Wenzhi-Ding had suggested at one point).
Adding a side bar should definitely be possible - the quartodoc documentation, which is of course written in quartodoc (😄) has a nice sidebar panel. There also is an example section  with more example pages. Let me know in case you spot one that you particularly like! =)

Btw, with which tool are the scikit-learn docs build? Is it sphinx?

I think so... I will try to see if we can get something similar in Quarto


Update Dockerfile

Refer new structure from #75
Use single branch flow with releases for now

Shouldn't this be merged? @DesignrKnight


[Feature] 0.6.0 release

Is your feature request related to a problem? Please describe.
Hi, I can see that all the PRs associated with release 0.6.0 have been completed, could I get an update on when that will be released?
Describe the resource you would like to have implemented.
I'd like access to the newer resource types that have been implemented in 0.6.0.
Describe the solution you'd like
A tagged version published to https://registry.terraform.io/ that I can use as part of standard terraform modules.
Describe alternatives you've considered
Referencing the main branch of this repository. However, this adds management overhead, and exposes us to potentially incomplete features and bugs.
Additional context
Raised as I noticed that https://github.com/elastic/terraform-provider-elasticstack/issues/46 the last issue for the 0.6.0 milestone has been resolved.

Hi @thomas-parrish-axi
The provider will be released soon. We can't provide exact dates, unfortunately.
the best way to test existing PRs and new functionality so long the provider isn't released, is simply by building it from source.


Number of labels and number of boundaries.

As there are three boundaries and three functions in task 1, So do we have to use one boundary for one function?? or all the boundaries for each function??

I hope the right person will answer this question in our group @poojashresthacode

BTW, did you check the code, which is in the repository? Maybe you can have an idea from there that what he did.

As there are three boundaries and three functions in task 1, So do we have to use one boundary for one function?? or all the boundaries for each function??

I used 1 boundary for each function in order they are given


drivers: watchdog: Add Raspberry Pi Pico watchdog driver

This adds basic support for the watchdog timer on the RP2040 MCU and
Raspberry Pi Pico development board
Tested on a raspberry pi pico board with a modified hello world sample, board reboots after ~8 seconds

@yonsch could you give this a review?

Yes, the basic wdt test passes on the device.

@thedjnK One thing I forgot - please add watchdog to the table of supported features in the board's doc


manifestPlaceholders Initialization is Broken in Android

I have noticed that in the most recent version of the OneSignal react-native SDK, the old method of initializing on Android (placing the OneSignal app ID in build.gradle manifest placeholders) no longer appears to work.
We will be investigating this issue this week.

When building for Android I’m getting these “requires a placeholder substitution” errors:
> Task :react-native-onesignal:processDebugAndroidTestManifest FAILED
…/node_modules/react-native-onesignal/android/build/intermediates/tmp/manifest/androidTest/debug/manifestMerger2995308312281659017.xml Error:
        Attribute meta-data#onesignal_app_id@value at manifestMerger2995308312281659017.xml requires a placeholder substitution but no value for <onesignal_app_id> is provided.
…/node_modules/react-native-onesignal/android/build/intermediates/tmp/manifest/androidTest/debug/manifestMerger2995308312281659017.xml Error:
        Attribute meta-data#onesignal_google_project_number@value at manifestMerger2995308312281659017.xml requires a placeholder substitution but no value for <onesignal_google_project_number> is provided.

Does anyone have a temporary workaround for this?
I tried adding the following to build.gradle as suggested by the OneSignal Android SDK setup documentation, but this doesn’t seem to work either:
android {
   defaultConfig {
      manifestPlaceholders = [
          onesignal_app_id: 'PUT YOUR ONESIGNAL APP ID HERE',
          onesignal_google_project_number: 'REMOTE'
      ]
    }
 }

I just upgraded a few days ago and I'm getting this issue when building. Has there been any progress, and is there a work around? My gradle is set up with many different flavors that substitute their onesignal app id/google project number, but at the very least I'd like to be able to specify a static one so I can build individual apks out.
Is the only thing needed for this disabling the manifest placeholders and then setting the correct values in the library gradle file?

have any updates? seems i use appIdFromManifest this function, and only get the empty string

Closing due to no response. Feel free to reply if you wish to reopen

The problem persist
android {
    compileSdkVersion rootProject.ext.compileSdkVersion

    defaultConfig {
        applicationId ...
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode ...
        versionName ...

        // Enabling multidex support.
        multiDexEnabled true

        manifestPlaceholders = [
            onesignal_app_id: ...,
            onesignal_google_project_number: 'REMOTE'
        ]
    }
    ...

> Task :react-native-onesignal:processDebugAndroidTestManifest FAILED
/react-native-onesignal/android/build/intermediates/tmp/manifest/androidTest/debug/manifestMerger8819906485659168097.xml Error:
	Attribute meta-data#onesignal_app_id@value at manifestMerger8819906485659168097.xml requires a placeholder substitution but no value for <onesignal_app_id> is provided.
/react-native-onesignal/android/build/intermediates/tmp/manifest/androidTest/debug/manifestMerger8819906485659168097.xml Error:
	Attribute meta-data#onesignal_google_project_number@value at manifestMerger8819906485659168097.xml requires a placeholder substitution but no value for <onesignal_google_project_number> is provided.

See http://g.co/androidstudio/manifest-merger for more information about the manifest merger.

@rochapablo , it looks like that solution worked for you. I will close this issue if that's okay with you. If you continue seeing issues, let me know and I will reopen
Summary:

I came across this problem in unrelated project, but I found a solution that works for me: disabling Gradle feature "Only sync the active variant". In Android Studio: File > Settings > Experimental > Gradle -> uncheck "Only sync the active variant" checkbox.


Updated project settings

This request creates separate frameworks for each target and added libxml2.tbd to Linked frameworks to resolve runtime linking issue, resolves issue #43

I don't see why you roll back the project to the old 4-target way since having multiple targets with so many duplicated build settings is definitely not a good way to maintain the project.
For more information about having a single target for 4 platforms, you can refer to a blog post how PromiseKit does this.
http://promisekit.org/news/2016/08/Multiplatform-Single-Scheme-Xcode-Projects/

because when I add it to iOS project and try to run, get this exception:
dyld: Library not loaded: @rpath/Fuzi.framework/Fuzi
  Referenced from: (Project path)
 Reason: no suitable image found.  Did find: (macOS framework)

@amosavian I would recommend you to use Carthage rather than adding the project directly to your, since Carthage builds a universal framework and you can choose to use Release or Debug configuration while dragging the project and the product framework in Xcode might end up using the one in the Debug build product folder.
Having one target definitely can definitely specify different configurations for different platforms if you had taken time to read that blog post I shared, it used this approach to configure the unit test framework.
The problem is not about maintaining 4 targets is difficult, it is about we don't know how many new platforms will be introduced by Apple in the future, and I definitely would prefer a more generic & sustainable way to maintain the project.
And I created a iOS project to try to reproduce your problem today, but it seems all went well so I don't really know what happened with your project.

@cezheng I have problems with Submitting to Appstore
Check the answer on this question: http://stackoverflow.com/questions/26559948/found-an-unexpected-mach-o-header-code-1918975009-in-xcode-6

don't know if you turned to Carthage or not, but since the framework should not contain iOS simulator binaries, you should add this step if you use Carthage: https://github.com/Carthage/Carthage#if-youre-building-for-ios-tvos-or-watchos


New release?

Could a new release be published any chance?
Thank you kindly.

We have released Waffle version 4 now :)


Learn how to instrument NGINX with OpenTelemetry

Updated article for instrumenting alpine-based nginx would be handy; I have attempted it in another project: https://gitlab.com/logius/beveiligd-koppelvlak-extern/base-images/nginx-unprivileged
But still get the error: "Error loading shared library libcrypt.so.1", even when adding gcompat due to musl use in Apline, I have not been able to integrate OTEL; I suspect switching to the suggested ubunutu-based images is recommended but it would be nice if a lightweight Apline image can be instrumented too

@WIP42 this repository is for the documentation and blog posts, please comment on this existing issue that you are interested in alpine support for the nginx webserver module: https://github.com/open-telemetry/opentelemetry-cpp-contrib/issues/302

I will close this issue now, please comment if you think that the website can help with anything here


Failure to install storybook-cli

As mentioned on issue #1937 there's been a bad release of opencollective.
A workaround is mentioned below.
The issue seen is:
$ npm i -g @storybook/cli
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm ERR! path<EMAIL_ADDRESS>npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod<EMAIL_ADDRESS>npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR!      /Users/armenzg/.npm/_logs/2017-10-02T15_23_17_309Z-debug.log

If you install it via yarn you will get the pinned version of opencollective 1.0.3 (as indicated in yarn.lock)
yarn global add @storybook/cli
yarn global v1.1.0
[1/4] 🔍  Resolving packages...
warning<EMAIL_ADDRESS>🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
warning<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
success Installed "<EMAIL_ADDRESS>with binaries:
      - getstorybook
✨  Done in 9.04s.

People that have their own React projects and want to include storybook can work around this issue (and others in the future) by switching to yarn and have all their dependencies pinned.

going to close this since it duplicates https://github.com/storybooks/storybook/issues/1937


Add retry logic to cluster selection

Try a (configurable) number of times to reach a cluster that can handle additional load.

Firstly, we need to disable the regular retries (using with cluster_info.osbs.retries_disabled():, https://github.com/projectatomic/osbs-client/blob/master/osbs/api.py#L1143) for the list-builds and create-build operations. If we don't do that, it will take a long time to move onto the next cluster in the list. We'll have two levels of retrying for the same thing.
Also, we need to apply retry logic to more than just cluster selection. What if creating the build on the selected cluster fails? In that situation we need to try another cluster.
Imagine this situation: clusters A, B, and C are for the same platform, but cluster A is unreachable. What we want to happen then is: try listing builds for cluster A once only -- i.e. discount the cluster for this selection attempt when it fails, then try listing builds for cluster B, then cluster C. After this first pass of attempting to list builds, pick a cluster based on load (e.g. B), then attempt to create the build on it, once only. If creating the build fails, try creating a build on cluster C, once only.
If all those things failed, start again, trying to list builds for cluster A as well as clusters B and C again.

Luiz and Vadim, I hadn't seen Tim's comment when I requested your reviews (had to refresh). Looks like I'll probably close this PR and make Tim's changes.

I have a new branch for this now.