Beta Stage Account: Experimental and Centralized

ronin — 09/17/2022
@Istora it looks like the @ETC_Network account got approved for the advanced api we needed/requested. (this was a centralized process that required an identity with twitter). I'll be AFK this week, heading to the mountains. But when I get back lets plug that api in.
Also @@moderators let's organize this account to populate in the discord feed- we could test this out in a test server if desired. I think we can add a feature in here to add "like" and "retweet" buttons to the tweets as well. Simple bots like that.
Transparency for the community (centralization concern topic): This account is still in the development stage (centralized requirements) as we figure out how to properly configure it; items like: repo processes, account settings, account integration, account api applications and twitter company requirements. Once everything is ironed out in the initialization process, we will work on properly converting it to a shared social asset between good stewards.
How? On first thought, this will likely involve the account moving to a shared password manager and email. If there is a better approach to decentralizing the account once configured, it will be pursued. I want to be very clear that I have no intent to hold this asset like Charles (centralized email with access granted via tweetdeck), it was specifically parked to become a "community managed twitter account" if the need ever presented itself. So that is the end goal here. We will get it there, you're just watching it be built/organized in the open for transparency. 👀
Once the account is out of my control in this way, I believe then it is appropriate to list the account on CoinGecko/CMC and other outlets as a project twitter. But for now, that seems premature as we iron our those details above. Please let us continue to iron out the bugs/configuration issues. 👍 I hope that is transparent on the approach, so no one is caught off guard as we collectively organize this social asset

ronin — 09/17/2022
Also i think it would be a good idea to have multiple twitter accounts integrated into this repo. So hopefully we can get accounts like @w1g0 's plugged in as well (this one has the V2 twitter api). The @ETC_Network account was chosen by @Istora because of a technical limitation where the account needed to have access to twitter's old v1 api to be compatible with the current version of twitter-together.
@ETC_Network origin: I had parked this account back in 2020 when IOHK was acting suspect (@stev specifically) on the @eth_classic account. He was posting articles that intentionally FUD the network to push his desired ECIP's. Cited 1049 was already approved (false) and promoting Checkpointing (centralized) and the IOHK Treasury (centralized) from the official account. This is why the need/plan to organize a community ran twitter account appeared. I wasn't alone in noticing this behavior. 2022's public messages from Charles regarding the @eth_classic account capture confirmed the suspicion that IOHK/Charles would become bad actors with the account due to their centralized ECIPs being rejected by the community. This is where Charles called ETC a dead project on the week of the merge to capture some news headlines for himself and Cardano. The journalist outlets took the bait on his sensational statement that is proven wrong by the clear unprecedented adoption of ETC during that time and gave him free publicly.
Ethereum Classic adapts and keeps it moving forward. :phoenix1:  Cheers all 🍻
One last thing on this twitter-together project: If you don't like the approach, please by all means pursue a different approach. This was the best solution I could find when trying to solve the problem. By no means should it be the only solution. So if you have a better approach, please pursue it (actually put the work in) and pitch it to the community in the open so they can adopt it. ETC is stronger with more participation from the community. Looking forward to seeing new faces involved as this network continues to grow.

So hopefully we can get accounts like @w1g0 's plugged in as well (this one has the V2 Twitter api).

After a long time I tried Twitter again but it is such a dopamine inducing platform for the woke so I will no longer participate in that closed source, censored platform. When you guys are considering Mastodon or any other uncensored, truly decentralized, open source platforms and the protocol has been written out, added more reviewers and increased the number of reviewers, I'm willing to connect.

So hopefully we can get accounts like @w1g0 's plugged in as well (this one has the V2 Twitter api).

After a long time I tried Twitter again but it is such a dopamine inducing platform for the woke so I will no longer participate in that closed source, censored platform. When you guys are considering Mastodon or any other uncensored, truly decentralized, open source platforms and the protocol has been written out, added more reviewers and increased the number of reviewers, I'm willing to connect.

So the issue with Mastodon is the lack of users. Also it is federated, so even that platform is not decentralized. But the real problem is the lack of users. The goal of this is to have an account where people will read the content. Twitter seems to be the place where the general public aggregates. So it seems a necessity to have a presence there.

So the issue with Mastodon is the lack of users. Also it is federated, so even that platform is not decentralized. But the real problem is the lack of users. The goal of this is to have an account where people will read the content. Twitter seems to be the place where the general public aggregates. So it seems a necessity to have a presence there.

The goal here is to educate to use these platforms and what better to start with your own community. By discarding the idea because of the lack of users you FOMO right into the Status Quo of things.
Ethereum Classic already has a user base, let's activate this existing user base before driving more adoption. Otherwise you'll attract more 'general' users to a platform that has no use case. These people will be very critical because they don't understand the values of ETC (even many inside the community don't understand them), they will compare it to Cardano, Polkadot etcetera. It's already noticeable in the influx in the community Discord.
Yes, it's federated meaning that you can set up your own server space with your own rules, so can any member in the community willing to spend the resources.
Ultimately if people inside the community will start using these platforms, other will see the success of an activated community together with a more and more centralized and censored media landscape, they will join creating a suction effect.


Fix potential issue of misinterpreting format string

Fixes potential issue with calling non-formatting functions with strings that maybe interpreted as a format string.
As an example log.Trace("%v")n would end up logging "%!v(MISSING)" instead.

Done.


cannot process multiple videos at once

When using Darknet V3 (v3.0.152) requests to process a single video works:
darknet_05_process_videos_multithreaded LegoGears DSCN1580A.MOV

But if attempting to process multiple video files like this:
darknet_05_process_videos_multithreaded LegoGears DSCN*.MOV

The first video works, and every video after that fails to run.  The output shows zero frames processed, and -nan FPS.

This error does not appear in darknet_04_process_videos, only in darknet_05_process_videos_multithreaded.


Too many labels?

Hi Joseph,
First and foremost: Thank you for this package! It certainly saved me a lot of time.
I've added it as a package to an asp.net core application and it's successfully sending logs to a loki instance that we run. The downside is that there are a lot of labels being sent with each log line. This is due to the call to .Enrich.FromLogContext() that we add to the Serilog configuration. This context information is great to have but not always necessary as a stream in loki.
Would you accept PRs that add a configuration option to allow the user to specify a list of log event properties (if they are present) that should be used as labels and all other properties from the context be appended to the log message. Or better yet, two lists of properties, one to be used as labels, one to be appended to the log message and all other properties from the log context be discarded?
Thanks ,
Bo

@bradacina Yes, that sounds like something this library should have. I'd be interested to see what the PR looks like.

@JosephWoodward here's what I have in mind: https://github.com/JosephWoodward/Serilog-Sinks-Loki/pull/15
I haven't looked at your unit tests or benchmarks yet.

@JosephWoodward I'm also very interested in this feature. Is there any way I can help in order to this feature to be available ASAP?
I've also seen that the library is using a deprecated endpoint of the loki api, are there any plans to start using the new recommended endpoint?

@JosephWoodward here's what I have in mind: https://github.com/JosephWoodward/Serilog-Sinks-Loki/pull/15
I haven't looked at the unit tests or benchmarks yet.

Thanks for your pull request, I’ll take a look at it this evening. It’d be good to get this one deployed as soon as possible.

@JosephWoodward I'm also very interested in this feature. Is there any way I can help in order to this feature to be available ASAP?
I've also seen that the library is using a deprecated endpoint of the loki api, are there any plans to start using the new recommended endpoint?

Yeah, I’d like to migrate to the new endpoint but I’m also conscious of breaking changes so may introduce some flag around which endpoint to use (so those on an older version of Loki won’t experience breaking changes).

Hi @JosephWoodward . Is there anything that needs doing (or anything you need help with) to get this issue moving forward?

@bradacina No, I don't think so. I've pulled it down locally and have been going through it. It seems some of the tests are failing so I'm trying to understand why.

Since I have not looked at the unit tests at all, I'll do the same on my end and see if something jumps out at me.

I also ran into this issue. I ended up extending the LogLabelProvider with a list of property names to ignore.
I also noticed that the LokiBatchFormatter was added a new loki content stream per log event, rather than aggregating all the log events by labels and adding entries for each aggregate.
After making those two changes, my loki chunks went from over a million from a week of runtime down to about ~4k.
My Format method in LokiBatchFormatter ended up like this:

        public void Format(IEnumerable<LogEvent> logEvents, ITextFormatter formatter, TextWriter output)
        {
            if (logEvents == null)
                throw new ArgumentNullException(nameof(logEvents));
            if (output == null)
                throw new ArgumentNullException(nameof(output));

            List<LogEvent> logs = logEvents.ToList();
            if (!logs.Any())
                return;

            var streamsDictionary = new Dictionary<string, LokiContentStream>();
            foreach (LogEvent logEvent in logs)
            {
                var labels = new List<LokiLabel>();

                labels.Add(new LokiLabel("level", GetLevel(logEvent.Level)));
                foreach (LokiLabel globalLabel in _globalLabels)
                {
                    labels.Add(new LokiLabel(globalLabel.Key, globalLabel.Value));
                }

                foreach (KeyValuePair<string, LogEventPropertyValue> property in logEvent.Properties)
                {
                    // Some enrichers pass strings with quotes surrounding the values inside the string,
                    // which results in redundant quotes after serialization and a "bad request" response.
                    // To avoid this, remove all quotes from the value.
                    // We also remove any \r\n newlines and replace with \n new lines to prevent "bad request" responses
                    // We also remove backslashes and replace with forward slashes, Loki doesn't like those either
                    if (IgnoreLogEventProperty(property.Key))
                    {
                        continue;
                    }
                    labels.Add(new LokiLabel(property.Key, property.Value.ToString().Replace("\"", "").Replace("\r\n", "\n").Replace("\\", "/")));
                }

                var localTime = logEvent.Timestamp.LocalDateTime;
                var localTimeAndOffset = new DateTimeOffset(localTime, TimeZoneInfo.Local.GetUtcOffset(localTime));
                var time = localTimeAndOffset.ToString("o");

                var sb = new StringBuilder();
                sb.AppendLine(logEvent.RenderMessage());
                if (logEvent.Exception != null)
                {
                    var e = logEvent.Exception;
                    while (e != null)
                    {
                        sb.AppendLine(e.Message);
                        sb.AppendLine(e.StackTrace);
                        e = e.InnerException;
                    }
                }

                // Order the labels so they always get the same chunk in loki
                labels = labels.OrderBy(l => l.Key).ToList();
                string key = string.Join(",", labels.Select(l => $"{l.Key}={l.Value}"));
                if (!streamsDictionary.TryGetValue(key, out var stream))
                {
                    streamsDictionary.Add(key, stream = new LokiContentStream
                    {
                        Labels = labels
                    });
                }

                // Loki doesn't like \r\n for new line, and we can't guarantee the message doesn't have any
                // in it, so we replace \r\n with \n on the final message
                stream.Entries.Add(new LokiEntry(time, sb.ToString().Replace("\\", "/").Replace("\r\n", "\n")));
            }

            var content = new LokiContent
            {
                Streams = streamsDictionary.Values.ToList()
            };

            if (content.Streams.Count > 0)
                output.Write(content.Serialize());
        }

I will see if I can put a PR up with that sometime this week.

@steveadoo32 I'd love to see a PR around this, especially this part:

After making those two changes, my loki chunks went from over a million from a week of runtime down to about ~4k.

The latest 3.0.0 release now a PropertiesAsLabels field that allows you to configure which properties should be treated as labels.
I'll close this issue off, if there are any further issues then please feel free to re-open it.


revert to sqlalchemy1.4

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1854

Relevant Lines:
3003

💛  - Coveralls


refactor: Schema refactor & clean code

Description

Schema refactor to make definitions more pythonic in some ways.
Perf enhancements using GitHub APIs for user verification, 1second -> 10-15 milliseconds (as long as the request isn't throttled).
Module level declaration of schema ie schema isn't initialized on every request.
API level schema error handling.

Expected test failing
ref:  #187


amneziawg-amd64-1.0.0.msi

Hi, can't do handshake on windows 11 (((
What i'm doing wrong?

Same problem. Two Win10 devices on the network, same hardware. One started without problems, and the other one can't establish a connection at all. Same problem as in the screenshot above.

Same problem. Two Win10 devices on the network, same hardware. One started without problems, and the other one can't establish a connection at all. Same problem as in the screenshot above.

With the same key/config at the same time?
If so:

Don't connect to one key from multiple devices at the same time. The connection will be unstable and result in packet loss. Generate a key for every device that you will use.

Completely different configurations on these two devices. The second device cannot connect, even if the working one is physically disconnected from the network. And there is no packet loss - the connection is not established at all.


Repetition of Named Entity in coref resolution

I am trying to find corefs for the following text:
'Alan and Bruder are great friends with Chris and Donald. Alan and Bruder want to head to Lebanon while Chris and Donald wish to stay in United States. Chris and Donald have not made up their mind yet, but will get there soon. Alan and Bruder do not want to separate but there seems to be no choice.'

As seen in the screenshot, I get correct clusters for 'Chris and Donald' (cell 336), but when I try to resolve these corefs, 'Donald' gets repeated twice in the result (cell 337 - second line).
Can someone help me in understanding what might be going wrong here?

Hm, that looks like a bug to me. Thanks for the report!

It's really weird that the wrong substitution only happens one time though, the other occurrences seem fine...

@svlandeg After inspecting some cases, I believe it happens when 'Chris', 'Donald' and 'Chris and Donald' are three individual entities as recognised by neuralcoref.
I also wrote a short custom code to resolve coref which tries to eliminate this error:
tok_list = list(token.text_with_ws for token in case_doc) #fetches tokens with whitespaces from spacy document     for cluster in clusters:       cluster_main_words = set(cluster.main.text.split(' ')) #get tokens from representative cluster name       for coref in cluster:         if coref!=cluster.main: #if coreference element is not the representative element of that cluster             if coref.text!=cluster.main.text and bool(set(coref.text.split(' ')).intersection(cluster_main_words))==False:                #if coreference element text and representative element text are not equal and none of the coreference element words are in representative element               # This was done to handle nested coreference scenarios                 tok_list[coref.start] = cluster.main.text + case_doc[coref.end-1].whitespace_                 for i in range(coref.start+1, coref.end):                     tok_list[i] = ""
Basically, I avoided the representative element text to substitute the utterance of text if both are the same. Eg. If 'Chris' is the representative entity and the code encounters 'Chris' as an utterance, if it will not substitute it, since they are the same. By doing this, the duplication could be avoided.
I hope this makes sense.


Doesn't work for Actors or Items

It doesn't show links on either actors or items

Hasn't been maintained in two years, maybe thats why? @Sigafoos is this module abandonned?

It was updated recently on a pull request, was attempting to make this issue for that PR


Bug Start-ThreadJob not pooling and hidden global constant

Steps to reproduce
$a = {Start-Sleep -Seconds 100;Write-Host "sleep 100 - 1st"}
$b = 1..10 | ForEach-Object { Start-ThreadJob -ScriptBlock $a -ThrottleLimit 2 }
$c = 1..10 | ForEach-Object { Start-ThreadJob -ScriptBlock $a -ThrottleLimit 10 }
$b

Expected behavior
ThrottleLimit should either only apply for the one line it was specified with e.g. the one that fills $b and the other one for those that fill $c.
But that may be hard to impossible, as it would require the command within the scriptblock of the foreach knowing about the piping and even than it would break in countless of other cases.
The better fix may be adding a "ThreadPool" parameter that allows "ThrottleLimit" to just apply to that pool of threads, as well as documenting within the Get-Help pages that ThrottleLimit changes a global constant and that it influences already scheduled tasks.
A third possible fix would be to store the ThreadLimit with the ThreadJob id and compare the amount of currently running threads against the limit of the next one in the list (basically if 4 tasks already run and task 5 should be started,  it simply could be checked what the ThreadLimit of task 5 is and if lesser Threads are currently running). This would introduce an implicit synchronization, as all tasks of b would complete before any of the ones within $c will start, but as the tasks are currently also processed using FIFO this may be the best fix. Using this approach all tasks within $b will be started using a ThreadLimit of 2, except the last one, that will be started using the ThreadLimit of $c. E.g. it will run together with the first 9 tasks of $c. This however is not an issue, as 9 is below the expected limit of 10. And also for the tasks in $b 1 is also below the there defined limit of 2. If the limit of a later task is smaller, it simply will not start until enough of the previous tasks have completed.
And the implementation of ThreadPools for Start-ThreadJob could be put into the backlog for being implemented with the next version.
When dealing with different APIs, the current behaviour could lead to unexpectedly running into rate limitations.
E.g. if $b contains threads to the API of e.g. https://example.com/ with a strict rate limit of 2 and $c contains threads querying the api of https://contoso.com/ with a less strict rate limit of 10
Actual behavior
The ThrottleLimit apparently changes a global constant which influences how many threads within $b are started, even though it was specified for $c.
Environment data

Name                           Value
----                           -----
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Microsoft Windows 10.0.20190
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

It looks like overhead to have many pools because resources are related to a computer.

I just provided multiple possibilities for an implementation. My personal favourite is the 3rd one (the one starting with "A third possible fix would be ").

No Auto close, Feature Request is still not implemented. Wtf?!? Do I need to write a bot that auto replies to keep my Tickets open now?


Departments?

I'm noticing that User#department is excluded from being saved, despite being an editable field in the profile edit view. There's also a deptid column in the users table but doesn't appear to be used anywhere.
What's the story on this? Looks like a foot in, foot out kind of situation.

Two half baked features. I'd guess it was simply mistakenly excluded. It is not shown anywhere at the moment, think it was mostly for "cross sectional" reporting.

Removed from user edit for now


I have the latest version 1.56.2 .. will disable all extensions and give it a try

Please test using the insiders version: 1.57

I've just tried insiders version 1.57, with no extensions installed,
I'm experiencing the same issue, specially when I have both TS & JS files opened, even if only one of each kind is opened.
fyi, may be I started experiencing this heavily this week only .. don't remember exactly when though!

Please try collecting the TS Server log from the crashed instance:

Set "typescript.tsserver.log": "verbose"

Restart VS Code and reproduce the problem

Open the TypeScript section of the output panel

At the very top, find the first line that prints to path to the semantic error log file. It should look something like:
[Info  - 19:54:59.247] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20200213T104930/exthost55/vscode.typescript-language-features/tsserver-log-ZT2zau/tsserver.log

That file contains the typescript logs.

Look through that log file for the first error or stack trace you see. If you can share the log, I can also take a look to see if anything stands out

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

Well, TSServer keeps exiting periodically with rolling over to a new log file each time as follows:

Typescript Output
[Info  - 16:02:16.118] Starting TS Server
[Info  - 16:02:16.119] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:02:16.121] <syntax> Forking...
[Info  - 16:02:16.132] <syntax> Starting...
[Info  - 16:02:16.138] <semantic> Forking...
[Info  - 16:02:16.196] <semantic> Starting...
[Info  - 16:04:30.124] Killing TS Server
[Info  - 16:04:30.124] Starting TS Server
[Info  - 16:04:30.124] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:04:30.134] <syntax> Forking...
[Info  - 16:04:30.143] <syntax> Starting...
[Info  - 16:04:30.144] <semantic> Forking...
[Info  - 16:04:30.175] <semantic> Starting...
[Info  - 16:04:30.193] Killing TS Server
[Info  - 16:04:30.193] Starting TS Server
[Info  - 16:04:30.193] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:04:30.195] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-hD2Xke/tsserver.log
[Info  - 16:04:30.195] <syntax> Forking...
[Info  - 16:04:30.201] <syntax> Starting...
[Info  - 16:04:30.202] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-zadtNG/tsserver.log
[Info  - 16:04:30.202] <semantic> Forking...
[Info  - 16:04:30.209] <semantic> Starting...
[Info  - 16:10:35.983] TSServer exited
[Info  - 16:10:35.983] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-zadtNG/tsserver.log
[Info  - 16:10:38.47] Starting TS Server
[Info  - 16:10:38.47] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:10:38.57] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-LM6H99/tsserver.log
[Info  - 16:10:38.57] <syntax> Forking...
[Info  - 16:10:38.65] <syntax> Starting...
[Info  - 16:10:38.67] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-3aujZw/tsserver.log
[Info  - 16:10:38.68] <semantic> Forking...
[Info  - 16:10:38.86] <semantic> Starting...
[Info  - 16:44:47.603] TSServer exited
[Info  - 16:44:47.603] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-3aujZw/tsserver.log
[Info  - 16:44:47.603] Starting TS Server
[Info  - 16:44:47.603] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:44:47.610] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-9uKvUA/tsserver.log
[Info  - 16:44:47.610] <syntax> Forking...
[Info  - 16:44:47.616] <syntax> Starting...
[Info  - 16:44:47.618] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-ZpGVAl/tsserver.log
[Info  - 16:44:47.619] <semantic> Forking...
[Info  - 16:44:47.645] <semantic> Starting...
[Info  - 16:47:08.582] TSServer exited
[Info  - 16:47:08.582] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-ZpGVAl/tsserver.log
[Info  - 16:47:08.582] Starting TS Server
[Info  - 16:47:08.582] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:47:08.584] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-q47TeG/tsserver.log
[Info  - 16:47:08.584] <syntax> Forking...
[Info  - 16:47:08.592] <syntax> Starting...
[Info  - 16:47:08.593] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-xQMKrh/tsserver.log
[Info  - 16:47:08.593] <semantic> Forking...
[Info  - 16:47:08.607] <semantic> Starting...
[Info  - 16:49:51.89] TSServer exited
[Info  - 16:49:51.89] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-xQMKrh/tsserver.log
[Info  - 16:49:51.89] Starting TS Server
[Info  - 16:49:51.89] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:49:51.91] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-reiduR/tsserver.log
[Info  - 16:49:51.91] <syntax> Forking...
[Info  - 16:49:51.98] <syntax> Starting...
[Info  - 16:49:51.99] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-ttZwsl/tsserver.log
[Info  - 16:49:51.99] <semantic> Forking...
[Info  - 16:49:51.110] <semantic> Starting...
[Info  - 16:53:18.146] TSServer exited
[Info  - 16:53:18.146] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-ttZwsl/tsserver.log
[Info  - 16:53:18.147] Starting TS Server
[Info  - 16:53:18.147] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:53:18.151] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-kB2UL6/tsserver.log
[Info  - 16:53:18.151] <syntax> Forking...
[Info  - 16:53:18.162] <syntax> Starting...
[Info  - 16:53:18.167] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-lAMB9t/tsserver.log
[Info  - 16:53:18.167] <semantic> Forking...
[Info  - 16:53:18.202] <semantic> Starting...
[Info  - 16:55:59.495] TSServer exited
[Info  - 16:55:59.495] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-lAMB9t/tsserver.log
[Info  - 16:55:59.495] Starting TS Server
[Info  - 16:55:59.495] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:55:59.500] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-whPqdJ/tsserver.log
[Info  - 16:55:59.500] <syntax> Forking...
[Info  - 16:55:59.506] <syntax> Starting...
[Info  - 16:55:59.510] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-NG2Lg5/tsserver.log
[Info  - 16:55:59.510] <semantic> Forking...
[Info  - 16:55:59.527] <semantic> Starting...
[Info  - 16:59:11.117] TSServer exited
[Info  - 16:59:11.117] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-NG2Lg5/tsserver.log
[Info  - 16:59:11.121] Starting TS Server
[Info  - 16:59:11.121] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:59:11.124] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-SIG1Bj/tsserver.log
[Info  - 16:59:11.124] <syntax> Forking...
[Info  - 16:59:11.131] <syntax> Starting...
[Info  - 16:59:11.132] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-e6nCHU/tsserver.log
[Info  - 16:59:11.132] <semantic> Forking...
[Info  - 16:59:11.148] <semantic> Starting...
[Info  - 17:02:35.234] TSServer exited
[Info  - 17:02:35.234] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-e6nCHU/tsserver.log
[Info  - 17:02:35.235] Starting TS Server
[Info  - 17:02:35.235] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 17:02:35.248] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-P4STrc/tsserver.log
[Info  - 17:02:35.248] <syntax> Forking...
[Info  - 17:02:35.264] <syntax> Starting...
[Info  - 17:02:35.266] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-8uiAlR/tsserver.log
[Info  - 17:02:35.266] <semantic> Forking...
[Info  - 17:02:35.305] <semantic> Starting...
[Info  - 17:06:44.548] TSServer exited
[Info  - 17:06:44.548] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-8uiAlR/tsserver.log
[Info  - 17:06:44.548] Starting TS Server
[Info  - 17:06:44.548] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 17:06:44.563] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-qlhzEl/tsserver.log
[Info  - 17:06:44.563] <syntax> Forking...
[Info  - 17:06:44.575] <syntax> Starting...
[Info  - 17:06:44.577] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-D2UHQs/tsserver.log
[Info  - 17:06:44.577] <semantic> Forking...
[Info  - 17:06:44.581] <semantic> Starting...
[Info  - 17:09:56.60] TSServer exited
[Info  - 17:09:56.60] TSServer log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-D2UHQs/tsserver.log
[Info  - 17:09:56.60] Starting TS Server
[Info  - 17:09:56.60] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 17:09:56.66] <syntax> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-OGVXZw/tsserver.log
[Info  - 17:09:56.66] <syntax> Forking...
[Info  - 17:09:56.75] <syntax> Starting...
[Info  - 17:09:56.76] <semantic> Log file: /Users/my_user_name/Library/Application Support/Code - Insiders/logs/20210610T180209/exthost1/vscode.typescript-language-features/tsserver-log-I9cyZn/tsserver.log
[Info  - 17:09:56.76] <semantic> Forking...
[Info  - 17:09:56.95] <semantic> Starting...

The very first log file didn't have any err in it,  but generally each file of them has slightly over 160k+ lines
The 2nd log file, kept showing this err throughout the whole file, until it exited and rolled over to another log file

Error
Err 15    [18:10:39.550] Could not find file "full_file_path_for_currently_opened_file".
All files are: []
Err 16    [18:10:39.583] Could not find file "full_file_path_for_currently_opened_file".
All files are: []
Err 17    [18:10:39.583] Exception on executing command {"seq":2,"type":"request","command":"projectInfo","arguments":{"file":"full_file_path_for_currently_opened_file","needFileNameList":false}}:

    No Project.

    Error: No Project.
        at Object.ThrowNoProject (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:156260:23)
        at ProjectService.doEnsureDefaultProjectForFile (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:160037:131)
        at ProjectService.ensureDefaultProjectForFile (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:160032:75)
        at IOSession.Session.getFileAndProjectWorker (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:164393:87)
        at IOSession.Session.getProjectInfoWorker (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:164238:36)
        at IOSession.Session.getProjectInfo (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:164235:29)
        at Session.handlers.ts.Map.ts.getEntries._a.<computed> (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:163534:61)
        at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:165205:88
        at IOSession.Session.executeWithRequestId (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:165196:28)
        at IOSession.Session.executeCommand (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:165205:33)
        at IOSession.Session.onMessage (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:165231:35)
        at Interface.<anonymous> (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:167833:31)
        at Interface.emit (events.js:315:20)
        at Interface._onLine (readline.js:337:10)
        at Interface._normalWrite (readline.js:482:12)
        at Socket.ondata (readline.js:194:10)
        at Socket.emit (events.js:315:20)
        at addChunk (internal/streams/readable.js:309:12)
        at readableAddChunk (internal/streams/readable.js:284:9)
        at Socket.Readable.push (internal/streams/readable.js:223:10)
        at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)

and of course the full_file_path_for_currently_opened_file file was there in my file system the whole time

I checked 2 random remaining files, but they didn't have any err in them
Let's also notice that this whole case happens when my RAM is full or near full
I really hope this would help .. and thanks a lot for following up on this
anything else I can help with, just please tell me

Hm, do you see this for every project you open or just one of them in particular?
I'm going to add some extra logging to also see if some kind of out of memory issue is causing this

The next insiders build will also log the exit signal for the server process. Hopefully that helps us track down what is going on

About your question .. I'm working only on one Typescript project (backend one) for quite a while now .. so, I can't tell if other Typescript projects would work well or not .. but other javascript projects are working fine with me though.

Did you have a chance to test using the most recent insiders build? It should print more info when the server exits

Sorry for being late,
well, in a single log file, I can see about 15 occurrences for loading the global typescript-vscode-sh-plugin plugin .. I'm not sure if this is normal or not

Plugin part
Info 3742 [18:27:45.185] Loading global plugin typescript-vscode-sh-plugin
Info 3743 [18:27:45.185] Enabling plugin typescript-vscode-sh-plugin from candidate paths: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features,/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js/../../..
Info 3744 [18:27:45.186] Loading typescript-vscode-sh-plugin from /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features (resolved to /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/node_modules)
Info 3745 [18:27:45.195] typescript-vscode-sh-plugin active for version < 4.2 and JS/JSX files. Current version : 4.3.2
Info 3746 [18:27:45.195] Intercepting getEncodedSemanticClassifications and getEncodedSyntacticClassifications.
Info 3747 [18:27:45.195] Plugin validation succeeded

About the TSServer exited message itself .. Let's take an example of this part of the output:
[Info  - 16:36:20.593] <syntax> Forking...
[Info  - 16:36:20.604] <syntax> Starting...
[Info  - 16:36:20.606] <semantic> Log file: /Users/my_user/Library/Application Support/Code - Insiders/logs/20210621T190045/exthost1/vscode.typescript-language-features/tsserver-log-SpwGYc/tsserver.log
[Info  - 16:36:20.606] <semantic> Forking...
[Info  - 16:36:20.613] <semantic> Starting...
[Info  - 16:38:46.472] TSServer exited. Signal: SIGABRT
[Info  - 16:38:46.472] TSServer log file: /Users/my_user/Library/Application Support/Code - Insiders/logs/20210621T190045/exthost1/vscode.typescript-language-features/tsserver-log-SpwGYc/tsserver.log
[Info  - 16:38:46.474] Starting TS Server
[Info  - 16:38:46.474] Using tsserver from: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 16:38:46.477] <syntax> Log file: /Users/my_user/Library/Application Support/Code - Insiders/logs/20210621T190045/exthost1/vscode.typescript-language-features/tsserver-log-dhtyot/tsserver.log

The first file named /tsserver-log-SpwGYc/tsserver.log just ended with the following:
(I replaced actual file paths for privacy purposes)
Info 3737 [18:38:04.278] -----------------------------------------------
Info 3738 [18:38:04.292] event:
    {"seq":0,"type":"event","event":"projectLoadingFinish","body":{"projectName":"/Users/path_to_file/tsconfig.json"}}
Info 3739 [18:38:04.294] event:
    {"seq":0,"type":"event","event":"telemetry","body":{"telemetryEventName":"projectInfo","payload":{"projectId":"0fcd9ae24a9a8d62221db465921f834fc91864bc98d0c506518c72367d56aca9","fileStats":{"js":0,"jsSize":0,"jsx":0,"jsxSize":0,"ts":777,"tsSize":2003306,"tsx":0,"tsxSize":0,"dts":1203,"dtsSize":28813933,"deferred":0,"deferredSize":0},"compilerOptions":{"composite":true,"target":"es2019","module":"commonjs","moduleResolution":"node","esModuleInterop":true,"downlevelIteration":true,"allowJs":false,"strict":true,"noEmit":false,"noEmitOnError":true,"noErrorTruncation":true,"noImplicitAny":true,"noImplicitThis":true,"noImplicitUseStrict":false,"noResolve":false,"noStrictGenericChecks":false,"noUnusedLocals":true,"noUnusedParameters":true,"noImplicitReturns":true,"noFallthroughCasesInSwitch":true,"isolatedModules":false,"inlineSourceMap":true,"inlineSources":true,"sourceMap":false,"experimentalDecorators":true,"emitDecoratorMetadata":true,"forceConsistentCasingInFileNames":true,"rootDir":"","baseUrl":"","outDir":"","paths":""},"typeAcquisition":{"enable":false,"include":false,"exclude":false},"extends":true,"files":false,"include":false,"exclude":true,"compileOnSave":false,"configFileName":"tsconfig.json","projectType":"configured","languageServiceEnabled":true,"version":"4.3.2"}}}
Info 3740 [18:38:04.294] Creating configuration project /Users/path_to_file/tsconfig.json
Info 3741 [18:38:04.294] event:
    {"seq":0,"type":"event","event":"projectLoadingStart","body":{"projectName":"/Users/path_to_file/tsconfig.json","reason":"Creating project referenced in solution /Users/path_to_file/tsconfig.json to find possible configured project for /Users/path_to_file/js_file.js to open"}}
Info 3742 [18:38:04.294] Loading global plugin typescript-vscode-sh-plugin
Info 3743 [18:38:04.294] Enabling plugin typescript-vscode-sh-plugin from candidate paths: /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features,/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js/../../..
Info 3744 [18:38:04.294] Loading typescript-vscode-sh-plugin from /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features (resolved to /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/node_modules)
Info 3745 [18:38:04.295] typescript-vscode-sh-plugin active for version < 4.2 and JS/JSX files. Current version : 4.3.2
Info 3746 [18:38:04.296] Intercepting getEncodedSemanticClassifications and getEncodedSyntacticClassifications.
Info 3747 [18:38:04.296] Plugin validation succeeded
Info 3748 [18:38:04.296] FileWatcher:: Added:: WatchInfo: /Users/path_to_file/index.ts 500 undefined WatchType: Closed Script info
Info 3749 [18:38:04.318] Starting updateGraphWorker: Project: /Users/path_to_file/tsconfig.json
Info 3750 [18:38:04.369] DirectoryWatcher:: Added:: WatchInfo: /Users/path_to_file/node_modules 1 undefined Project: /Users/path_to_file/tsconfig.json WatchType: Failed Lookup Locations
Info 3751 [18:38:04.371] Elapsed:: 1.6069939732551575ms DirectoryWatcher:: Added:: WatchInfo: /Users/path_to_file/node_modules 1 undefined Project: /Users/path_to_file/tsconfig.json WatchType: Failed Lookup Locations

and the one after it called /tsserver-log-dhtyot/tsserver.log, just started with:
Info 0    [18:38:47.114] Starting TS Server
Info 1    [18:38:47.115] Version: 4.3.2
Info 2    [18:38:47.115] Arguments: .......

Is this a very large project? SIGABRT suggests that the server process may be running out of memory. You can also try configuring typescript.tsserver.maxTsServerMemory

Yes it is a very large project indeed, and we are separating it into different packages with utilizing project references as recommended,
I tried to increase the maxTsServerMemory from its default 3072 to 5120, but issue still there most of the time!
I could have increased it more than that, but I have only 16 GB, and I still need Docker and browser and other stuff, where it might not be practical to increase it more than that I guess.

Can you also try some of the recommendation listed in https://code.visualstudio.com/docs/typescript/typescript-compiling#_working-with-large-projects
Transferring to TS for further investigation about why it may be using so much memory


Naive-sql-engine not support spark-3.0.1 when running TPC-DS.

When we using OAP-1.1 with spark-3.0.1 to run TPC-DS all queries, 19 queries failed. The error message is showed below:
Error: Error running query: java.lang.NoSuchMethodError: org.apache.spark.sql.execution.adaptive.ShuffleQueryStageExec.shuffle()Lorg/apache/spark/sql/execution/exchange/ShuffleExchangeLike; (state=,code=0)

@zhixingheyi-tian @zhouyuan Please help to track the issue. Thanks!

currently native sql does not have a API layer to connect with different spark version, there are two branches:

https://github.com/oap-project/native-sql-engine/tree/branch-1.1-spark-3.x -> 1.1 release supports spark 3.0.0 only
https://github.com/oap-project/native-sql-engine/tree/branch-1.1-spark-3.1.1 -> 1.1.1 release supports spark 3.1.1 only
may need to create another branch to support Spark 3.0.1 if there's strong requirement

for future release we are considering to adding a compatible API layer
https://github.com/oap-project/native-sql-engine/issues/273


Unable to adjust the zones in the .jar or the .deb versions.

I can't change the zones in the editor for some reason.

The zone text fields stay diabled and without value regardless of the zone selected and the "gang wars" setting.

Unfortunately, I didn't write that (or most of) the code, I just added some macOS-specific features, started work on support for garages and fixed the project structure, build process and documentation.
I tried multiple times to understand what that code is supposed to do but I always get lost on the way and end up with no time left. Since you mentioned that using the debugger works, I'd suspect some sort of race condition or as you've mentioned an issue with reading inputs.
I don't really understand that part of the code and haven't properly coded Java in almost three years now, so I'm sorry but I can't give you any more info on the specifics of the Zone tab, than:
From what I understand, users are supposed to select an area of the map, which will then result in the zones on the map being highlighted, so they can set the gangs that are active in that zone.
The handleEvent method you mentioned probably sets the disabled state of the text fields, they should be disabled when nothing is selected, but I'm not sure if that event even is fired correctly when an area is selected.

The website linked at the repository start page is the original website, @paul35621 is the original developer.
I just took over maintainership hoping I could fix what kept it from working for the macOS version, add some quality-of-life improvements, and maybe even get some outside contributions that fix other issues by hosting it in a more accessible manner on GitHub.
You can try reaching out to him using email if that's still available on his website, but I can't guarantee that he'll respond.
In any case, even if you just clean up the code a bit to make it more readable, any contribution back is more than welcome, maybe it will help someone else who tries to tackle this issue.

No, the code was previously only available on pauls website (linked at the top of this repo) as a zip without any way to contribute changes, so I wrote an email asking if he would be okay with putting the project on GitHub so I could fix the issues I have and maybe develop further features, to which he replied that I should then also take over maintainership (ie. being one of the people able to merge commits, reply to issues, etc.) because he doesn't have the time for all that.
As far as I know Paul created his GitHub account only because I wanted to add him to the group.
As I said, if you manage to get further even a little bit, please consider creating a PR with your changes so other people (maybe me should I suddenly get motivated again) can continue your work.


retrofitting sensu defs

I am making this page as a central list of which sensu terms have
been retrofitted with the new standard definitions.
I have done Gnetophyta, diptera, metazoa and Dictyosteliida so far.
Jen
Reported by: jenclark
Original Ticket: "geneontology/ontology-requests/1550":https://sourceforge.net/p/geneontology/ontology-requests/1550

thanks www.movied.org


[e2e] Add ecs_service tag to ECS e2e tests expectations

What does this PR do?
Add ecs_service tag to ECS e2e tests expectations
Motivation
This tag was introduced by #28660 and we missed the update of the e2e tests because it was already flagged as flaky.
Describe how to test/QA your changes
TestECS e2e tests should pass.
Possible Drawbacks / Trade-offs
Additional Notes

TestECSSuite passed.

/merge


Issue in Scrolling

i am facing issue with RTl layout if i change orientaion scroll is not working , i cannot easily swipe it

When layout is rtl i cannot swipe it


Fix python 3 issues

This PR resolves minor errors in the parser to make it work with python 3.

👍, but I accept the PR please update https://github.com/clippercard/clippercard-python/blob/master/clippercard/init.py#L25 to version 0.4.1 - I will then publish the update to pypi

👍 Please update https://github.com/clippercard/clippercard-python/blob/master/clippercard/init.py#L25 vesion to 4.0.1 and this PR will be accepted to be published to pypi after.

Updated


feat: enable ethereum manually

Update demo to work with EmbarkJS.enableEthereum
DO NOT MERGE until a new version of EmbarkJS has been published

@iurimatias @jrainville PR updated

@iurimatias any updates on this one?


UINotificationService doesn't not return ID for the show() method

Before Creating an issue

Are you running the latest version? YES
Are you reporting to the correct repository? YES
Did you search existing issues? YES

Bug Report
Describe the Bug
let service = UINotificationService.create({});
let id = service.show(...);
console.log(id) => it's undefined

@SachidanandAlle I don't know what you're exactly trying to do with the notification.
But, you can see the https://github.com/OHIF/Viewers/blob/master/platform/core/src/services/UINotificationService/index.js to check what the show method does.
It doesn't return any id. What the method function does is to add a queue when it's called. The enqueued requests are consumed asynchronously.
Additionally, I believe you don't need to call the UINotificationService.create({}) in most cases.
You can simply use the useSnackbarContext in a hook function or withSnackbar in class component.

https://github.com/OHIF/Viewers/blob/master/platform/core/src/services/UINotificationService/index.js#L35-L36

Create and show a new UI notification; returns the
ID of the created notification.


Update to Node v20.11.0 LTS and address all related issues.

Continued testing has verified that the codebase is stable under Node v20.11.0 LTS.


chore(FDS-447) RFC Button

This PR adds an RFC button and description to the home page of the docs. I initially added it to the header, but I think having some more context about what we are looking for makes more sense so I added it into a drawer on the landing page instead. Feel free to move it elsewhere if the team discovers a different location that suits it better.
PR Author Checklist

[x] PR title adheres to Conventional Commits
[x] I have finished reviewing the contents of this PR for accuracy
[x] If needed, I have included a Changeset and it follows Semantic Versioning principles
[x] I have completed all of the above and have enabled auto-merge for this PR

Fails

:no_entry_sign:
Please add a '### Snapshots' section to explain the reason we are changing snapshots.

  Generated by :no_entry_sign: dangerJS against bf061bfdee9e7b25ea610ce7a00605f01dd3094f


[Usage]: Adaptive Batching and number of concurrent requests

Your current environment
I am using the async engine or docker with openai completions endpoint.
How would you like to use vllm
Lets say I am setting max num batched tokens to 50k. It tells me I can run 15 concurrent requests. Now as far as I understood adaptive batching, if one request finished computing, the batch is refilled with the next request ensuring a consistent throughput.
So can I send 1000 requests at once and it would continuously process around 15 requests at a time by refilling the batch?
Or should I only send 15 requests at a time and wait until they are processed to send the next 15?
Is there some limit which would overwhelm the system?
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

In most cases, you should simply provide all of your requests at once and the scheduler in vLLM will do it's best job to batch the largest number of requests together based on the kv cache available. The Maximum concurrency for 32k tokens per request: 15.1x message is for the worst case where each request is using the full context length of the model. In practical use you can often get much higher batching.
The one exception to this is sending tens of thousands of requests at once may overload the server if it can only finish them slowly. This shouldn't cause a crash though

Thanks. If it does not crash, what would be the result of overloading, and is there a way to calculate the point of overloading?

Closing since the initial question was answered, would still be nice if anyone has an idea regarding the overloading.

Overloading without crashing would just be like potentially generation poor performance from many requests in-flight. This is less of an issue now that we separated the server from the scheduler and the scheduler from the engine with multi-processing in >=0.6


no trusted certificate error

 com.tibco.bw.palette.restjson.runtime.exceptions.HttpCommunicationException: An IOException was thrown while trying to execute the HTTP Method at resource path https://login.microsoftonline.com:443/xxxxxxxxxxxxxxxxxxxxx/oauth2/token-{ActivityName=InvokeRESTAPI, ProcessName=test.Process, ModuleName=test}
 javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
 javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
 sun.security.validator.ValidatorException: No trusted certificate found

https://login.microsoftonline.com:443/xxxxxxxxxxxxxxxxxxxxx/oauth2/token trying to do post ..getting error trusted certificate is not found .
please help in creating javakeystore for login.microsoftonline.com:443 connecting through ssl

@Chenjigaram Can you please provide us with the URL of the Azure Doc you are having issues with? We look forward to your reply.

@Chenjigaram I'd recommend posting your question in https://azure.microsoft.com/en-in/support/community/  since it's not directly related to the documentation. We'll follow up there.

@Chenjigaram Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


[Gratitude] cargo bench is amazing, thank you

Just a quick note to thank you for the work on the bench command. It saves me a lot of trouble developing and maintaining my own harness. It also functions as a common reference for everyone to use, which means i don't need to explain some custom method for running benchmarks and gathering results.
In my view it functions as a base reference for everyone to quickly communicate either ad hoc measurement setups or build results. And it works brilliantly on first use, with simple setup and straightforward results.
Thank you.

Thanks for the words! There are still rooms to improve for https://github.com/rust-lang/cargo/labels/Command-bench. Always open to contributions, and feel free to have a chat with the maintainers on Zulip!


We should add hash wrappers as well for all Sui/Narwhal used functions

This will help to avoid surprises in Sui or Narwhal re using different sha2/sha3/keccak deps in different places. Ideally we should control every crypto algorithm in fastcrypto. After having these wrappers, we should update both Narwhal and Sui repos by invoking fastcrypto's api.
I was thinking that the same applies for base64, but let's wait for this, as Rust's popular base64 crate is working on the malleability fix.

@kchalkias Do we also need BLAKE2? It's used a few places in fastcrypto, but only in tests where it could be replaced with any other hash function.

The hash functions are added and there's an issue on the SUI repo to add them there (https://github.com/MystenLabs/sui/issues/4760), so could we close this issue now?


Harbor UI fails to load ID or email when there are several users on VCSA

@reasonerjt
Build: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.3.0-rc2-2628-9e2a95b6.ova
I have about 1000 users on VCSA and one such user is lgayatri1

For a given project in Harbor , I cannot add this user as UI fails to load all matched user names. There are double entries for the users shown.

Harbor logs attached.
Harbor.zip

@lgayatri in VIC this part belongs to Admiral, I opened: https://github.com/vmware/admiral/issues/225


consensus::State deserialization fixes

Fixes #679.
This should make the consensus::State struct backwards compatible for JSON deserialization. Note that serialization will always use the new format which is not backwards compatible because of a rename from parts to part_set_header in one field.

[X] Referenced an issue explaining the need for the change
[X] Updated all relevant documentation in docs
[X] Updated all code comments where relevant
[X] Wrote tests
[X] Updated CHANGELOG.md

That's interesting. These failures didn't show up in local testing. Checking...

All right, the test problem is my fault, I didn't run the full test suite after changing the total to a string.

Codecov Report

Merging #680 (7a1f0c1) into master (fa415e3) will increase coverage by 0.2%.
The diff coverage is 87.1%.

@@           Coverage Diff            @@
##           master    #680     +/-   ##
========================================
+ Coverage    39.2%   39.4%   +0.2%
========================================
  Files         190     191      +1
  Lines       12552   12595     +43
  Branches     3237    3241      +4
========================================
+ Hits         4927    4974     +47
+ Misses       7381    7373      -8
- Partials      244     248      +4

Impacted Files
Coverage Δ

proto-compiler/src/constants.rs
0.0% <ø> (ø)

proto/src/serializers/from_str.rs
85.7% <ø> (ø)

proto/src/serializers/optional.rs
83.3% <0.0%> (ø)

proto/src/serializers/part_set_header_total.rs
75.0% <75.0%> (ø)

tendermint/src/block/parts.rs
68.5% <100.0%> (ø)

tendermint/src/consensus/state.rs
85.2% <100.0%> (+13.5%)
:arrow_up:

tendermint/src/block/height.rs
67.2% <0.0%> (ø)

tendermint/src/hash.rs
56.9% <0.0%> (+3.2%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #680 (7a1f0c1) into master (fa415e3) will increase coverage by 0.2%.
The diff coverage is 87.1%.

@@           Coverage Diff            @@
##           master    #680     +/-   ##
========================================
+ Coverage    39.2%   39.4%   +0.2%
========================================
  Files         190     191      +1
  Lines       12552   12595     +43
  Branches     3237    3241      +4
========================================
+ Hits         4927    4974     +47
+ Misses       7381    7373      -8
- Partials      244     248      +4

Impacted Files
Coverage Δ

proto-compiler/src/constants.rs
0.0% <ø> (ø)

proto/src/serializers/from_str.rs
85.7% <ø> (ø)

proto/src/serializers/optional.rs
83.3% <0.0%> (ø)

proto/src/serializers/part_set_header_total.rs
75.0% <75.0%> (ø)

tendermint/src/block/parts.rs
68.5% <100.0%> (ø)

tendermint/src/consensus/state.rs
85.2% <100.0%> (+13.5%)
:arrow_up:

tendermint/src/block/height.rs
67.2% <0.0%> (ø)

tendermint/src/hash.rs
56.9% <0.0%> (+3.2%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Package does not load the correct source file in a Worker

I've created a repro repo here: https://github.com/spmonahan/decode-named-character-reference-worker-webpack-bug
The issue is that when I try to use Remark in a Worker the DOM version of decode-named-character-reference is being loaded despite the worker export being configured in this package.
According to Webpack's docs the worker export is supported and while this might be a Webpack bug I wanted to raise it here in case it's a package configuration issue.

Actually, looks like this is a Webpack issue: https://github.com/webpack/webpack/issues/17512


Solution for CSAT-QA tasks evaluation

Hello! Thank you for your great repo..!
Here, I suggested a solution for CSAT-QA tasks.
CSAT-QA has 6 tasks:  csatqa_gr, csatqa_li, csatqa_rch, csatqa_rcs, csatqa_rcss, and csata_wr.
But, the tasks have an error: dataset 'EleutherAI/csatqa' doesn't exist on the hub or cannot be accessed..
So, I changed the dataset_path in the yaml file and this works fine.
Thank you!

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


Waifu2x'd images have 16 bit per channel

This is probably intentional, but the images output by waifu2x have 16 bits per channel, which adds considerable size. Is there an an option to lower the output bit-depth?

The output bit-depth depends on the GraphicsMagick settings.
Probably your GraphicsMagick was compiled with --with-quantum-depth 16.
The bit-depth option is currently not supported. I will add it sometime.

I added -depth option to waifu2x.lua.
And web.lua generates 8 bit-depth PNG by default.


Resolved overlapping issue between chatbot and scroll to top button

Hi @Anishkagupta04 ,
closes #537
considering the current positioning where the chatbot is in the rightmost bottom of the page and the scroll-to-top button is just above it, I adjusted the scroll-to-top button to be moved to the left side of the page to avoid overlap.
Video/Screenshots (mandatory)
Here as you can see :

Please take a look and also add required labels.

Thankyou for your contribution


First meeting - Kick-off and "Get to know each other!"

Schedule and plan first meetup.
Place: Hackerspace Silesia
When: July (?)
Topics:

Get to know each other
https://github.com/inaka/gold_fever
https://www.youtube.com/watch?v=gpSn9yUf2wM

Planned and will be hosted this friday - www.meetup.com/Silesian-BEAMers/events/225583648/


Fixed bug in reading STL data on windows

The causes are the following two.

The first cause was that fread() did not work correctly unless fopen() was called with the read mode as binary mode like "r" -> "rb".
The second cause was that the zAxis type of the split data type in the zVec3DTree was a byte type, and the code expected to get -1 in the initialization process, but the byte type is defined as the standard unsigned char type in Windows, and the value turned into something unexpected (255). In Linux and Unix-like RTOS environment, byte type is defined as signed char type in zeda_def.h, so -1 was taken and it worked correctly.

The fix is as follows.

fopen() is modified to be executed as "r" -> "rb".
( It is confirmed that both binary type STL and ascii type STL can be read normally in "rb" mode on both Windows and Linux )
Redefine zAxis type directly as  byte -> signed char type.

In addition, there was another bug in the macro include process in terra_test.c, which has been fixed.

Thank you for investigating this issue.
It is not preferable to open text files with "rb" option. I think the file should be reopened with "rt" once it is detected to be written in ASCII format.
The problem around byte is more serious. Basically, we shouldn't employ a type that has the same name but different definition with any other compilers. It means that we have to redefine "byte" as "unsigned char" (I saw it is also compatible with std::byte). Obviously, it leads many inconsistencies with the libraries. An idea is to replace byte in the current codes to int8_t. I will do it on my own responsibility.
Regarding a careless but in terra_test.c, thank you for fixing it.
Let me approve your request and merge it into the main branch. Then, I'll correct the concerned parts.


[Enhancement] eventmesh server go rocketmq connector

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request
Complete the rocketmq connector in golang
Describe the solution you'd like
You can refers to https://github.com/apache/rocketmq-client-go.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Hi, @walleliu1016 , I wonder if any assignees are working on this task?  If not currently, I want to try this.


container component doesn't keep style prop on replace

      <ReactCSSTransitionReplace
        component='div'
        style={{ overflowY: 'auto' }}
        transitionName={{
          enter: PreviewEnter,
          leave: PreviewLeave
        }}
        transitionEnterTimeout={300}
        transitionLeaveTimeout={300}
      >
        { this.renderPreview() }
      </ReactCSSTransitionReplace>

on first render the inline style css overflow-y: auto is there, but on change of { this.renderPreview() } the outer container's inline style is gone

I've finally looked into this and found something quite strange. Any other style property is maintained as you would expect. It is only overflowY and overflowX that is not restored after overflow: hidden was added and removed.
You can disable this behaviour by setting the prop overflowHidden={false}. In that case overflow: hidden is never applied and the values on the style prop are maintained throughout.


How to use the frigate card?

A have always used the cusom gallery-card as slideshow for my images and videos. This card doesn't work anymore. Hacs pointed to frigate card, but how to set it up? It's not clear how to configure it to present the images and videos in the media folder.

A have always used the cusom gallery-card as slideshow for my images and videos. This card doesn't work anymore. Hacs pointed to frigate card, but how to set it up? It's not clear how to configure it to present the images and videos in the media folder.

What is your goal? Frigate card cannot show arbitrary media in a gallery, but can show media of supported camera engines (e.g. Frigate, motionEye or [experimental] reolink), then it can help. If you're only interested in media from those types of cameras, this card can help. Otherwise, it cannot.

A have always used the cusom gallery-card as slideshow for my images and videos. This card doesn't work anymore. Hacs pointed to frigate card, but how to set it up? It's not clear how to configure it to present the images and videos in the media folder.

What is your goal? Frigate card cannot show arbitrary media in a gallery, but can show media of supported camera engines (e.g. Frigate, motionEye or [experimental] reolink). If you're only interested in media from those types of cameras, this card can help. Otherwise, it cannot.
Full documentation is at: https://card.camera/

Thanks for your answer. In that case I can not use this card. Goal is to have a slideshow of photos and videos. The custom gallery card in hacs pointed to the frigate card but that looks like its only for cameras.

Goal is to have a slideshow of photos and videos.

If your camera is a Frigate camera, that would work. If it's any arbitrary photos/videos, I'm afraid this is not the card for you.


Update links on Data Downloads page

@LucaFumis could you please update the links on the Platform Data Downloads page to include a link to the non-clinical experimental toxicity TSV file created by Prudence?
Also, we will want to ensure that we have the updated baseline expression file link generated by Asier.
And can we please nest the links? So for example:

Target safety

Known side effects and safety risk information JSON
Non-clinical experimental toxicity TSV

Ticket closed as PR merged and pushed to production

Ticket closed as PR merged and pushed to production


shell_plus --print-sql output length problem

I found sql length problem. it doesn't confirm full sql text.
example: select query and 3 table join
SELECT rs.aid,
rs.bid,
rs.cid,
rs.did,
rs.fid,
rs.gid,
rs.date,
req.id,
req.cid,
req.cid2,
req.fid,
req.gid,
req.date,
req.closedate,
req.opendate,
req.opendate2,
req.opendate3,
req.opendate4,
su.id,
su.bid,
su.cid,
su.did,
su.eid,
tt.id,
tt.rid,
tt.pid,
tt.tag1,
tt.tag2,
p.id,
p.mid,
p.jid,
p.addr3,
p.addr2,
p.addr1,
p.tag1,
p.tag2,
p.tag3,
p.tag4, `p
[Execution time: 0.431622s] [Database: default]

There is a configuration setting controller how long a printed SQL statement is allowed to be called: SHELL_PLUS_PRINT_SQL_TRUNCATE = 1000
Try settings this higher in settings.py and see if that helps.
(In git master version it's now also possible to disable truncation by using SHELL_PLUS_PRINT_SQL_TRUNCATE = None)

@trbs Thanks : )

I set two configuration in settings.py
SHELL_PLUS_PRINT_SQL_TRUNCATE = None
RUNSERVER_PLUS_PRINT_SQL_TRUNCATE = None


List supported DBs in output of aptible help db:create

Currently users must check https://support.aptible.com/topics/paas/what-databases-does-aptible-support/ separately.

If we end up exposing  this in the API (not saying we should, but if we did), we should remember to refactor this: https://github.com/aptible/ember-cli-aptible-shared/pull/84

We  now support aptible db:versions which addresses this: https://www.aptible.com/documentation/enclave/cli/db-versions.html


Set RBAC roles into resource we need to have access to

Description
Right now we use wildcards, see: https://github.com/kyma-project/btp-manager/pull/123/files
We must have access only to the resources that we need.
AC

[x] 1) set btp-manager RBAC ac roles to specific resources we need
[x] 2) automate RBAC check when getting new chart from upstream, see
[x] 3) find a way how to managed RBACs when some k8s types are gone from previous BTP Operator release and new BTP Operator release has some new k8s types to be created.
[ ] 4) enhance documentation about auto-update, here

I missed the docs part


Port "Validation occurs against declared type rather than real type" to 2.1.x

Issue: https://github.com/aspnet/Mvc/issues/7952

Stealing this one since we're going with an expansion of #8019

Reassigning because we're taking @pranavkm's fix (#8049)

Fixed in https://github.com/aspnet/Mvc/commit/174c5eaa6c8370a4d3c4ba898aee9e7a5904720c


Usage of jsonRecursiveSort in prettierrc seems to have no effect

Hi @Gudahtt ,
I'm attempting to set recursive sorting of JSON files by default, but I can't seem to get this to work with my prettierrc configuration correctly.
For reference, running prettier --json-recursive-sort file.json does work as expected.
I've tried both of these configs, to no effect:
{
  "jsonRecursiveSort": true
}

{
  "overrides": [
    {
      "files": "*.json",
      "options": {
        "jsonRecursiveSort": true,
        "parser": "json",
        "plugins": ["prettier-plugin-sort-json"]
      }
    }
  ]
}

Best,
Mike

Thanks for the report!
I've tried reproducing this but haven't succeeded so far. I tried with a file called .prettierrc.yml in the root of my project, with the contents:
singleQuote: true
trailingComma: all
jsonRecursiveSort: true

What was your file called? If it was prettierrc (without the leading period), Prettier may not be reading it. See the configuration file documentation for more information: https://prettier.io/docs/en/configuration.html

Thanks @Gudahtt I'll try with YAML and see if that works tomorrow

Just updated to prettier 3.0.0, will reopen if this issue persists

For me on v3.0.0 nothing happens either with the flag or the .prettierrc.json. But this could be due to no Prettier v3 support


Provide 'support' for same entities with different namespaces

We have to decide on how to tackle this problem and what EMMOpython should support  and not.
As of now the ontology.get_by_label_all(xxx), will return all different xxx, also with different namespaces, but ontology.xxx will only return the first it finds.
If both are present in different namespaces it should at least give a warning, and some way to decide which one to use.
Alternatively it should be impossible to import different domain ontologies if they have overlapping terms.

Good point. For compatibility with Owlready2 and for convenience I think that it is preferable that onto.xxx only returns a single object. But I agree that we then should give a warning. The same is the case with onto[xxx].
The names of the methods get_by_label() and get_by_label_all() are quite long. Would it make sense to rename them to get_one() and get(), respectively?

I am not sure which is the smartest way to go about this. I think get_by_label and get_by_label_all are fine. However, if we want to always check if there are more than one of a specific class we would have to always run get_by_label_all. If so, we should change get_by_label to run get_by_labe_all and return depending on the result from this.
However, I am not sure that is very smart. Would it not slow down the code very much if all entities should be checked every time? Especially when the ontology is big...

Ok, so we will not check and warn. How can we make it easy to be explicit? Full IRI using the world already works:
onto.world['http://emmo.info/emmo/middle/materials#EMMO_eb77076b_a104_42ac_a065_798b2d2809ad']

This is the only fully unique way to refer to an entity, but is not very convenient.
Prefixing the label with the last component in the namespace would be more convenient
onto.materials.Atom
onto.mydomain.Atom

and work in most cases. Should we implement it?
This would require two changes:

Update get_by_label() to recognise a namespace
Patch owlready2.namespace.Namespace with a __getattr__() method that returns the entity with the given label in this namespace.

For efficiency we could cache the namespaces in a dict
onto.namespaces = {e.namespace.name: e.namespace for e in onto.get_entities()}

Unrelated to this, it seems that EMMO-python does not provide attribute access by name any more, like
onto.EMMO_eb77076b_a104_42ac_a065_798b2d2809ad

That should probably also be fixed?

This is a good suggestion. The exception in which it will not work needs to be well described in the documentation

Has been solved a bit differently with prefixes in #439 .
onto.get_by_label('label', prefix='prefix') does return the correct entity.


Fix htcondor tests

Codecov Report

Merging #634 (cffca11) into main (102542f) will increase coverage by 1.99%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #634      +/-   ##
==========================================
+ Coverage   62.95%   64.94%   +1.99%
==========================================
  Files          46        1      -45
  Lines        5825      388    -5437
  Branches       74       74
==========================================
- Hits         3667      252    -3415
+ Misses       2158      136    -2022

Components
Coverage Δ

apel_plugin
64.94% <ø> (ø)

auditor
∅ <ø> (∅)

slurm_collector
∅ <ø> (∅)

slurm_epilog_collector
∅ <ø> (∅)

htcondor_collector
∅ <ø> (∅)

priority_plugin
∅ <ø> (∅)

cargo-deny check will be fixed in #633


Api does not support random_shuffle?

Api does not support random_shuffle?

No pseudo-random results with arbitrary seeds are allowed within contracts.  Contract execution must be deterministic, so it is repeatable by all verifying nodes.  Pseudo-randomness with pre-determined seeds is allowed.  See the dice contract for an example.

Random_shuffle can set seed


Underloaded Neuron Cores with Llama3

System Info
TGI Image: ghcr.io/huggingface/neuronx-tgi:0.0.23

Platform:

- Platform: Linux-5.15.0-1031-aws-x86_64-with-glibc2.35
- Python version: 3.10.12

Python packages:

- `optimum-neuron` version: 0.0.23
- `neuron-sdk` version: 2.18.0
- `optimum` version: 1.20.0
- `transformers` version: 4.41.1
- `huggingface_hub` version: 0.23.2
- `torch` version: 2.1.2+cu121
- `aws-neuronx-runtime-discovery` version: 2.9
- `libneuronxla` version: 2.0.965
- `neuronx-cc` version: <IP_ADDRESS>+6dfecc895
- `neuronx-distributed` version: NA
- `neuronx-hwm` version: NA
- `torch-neuronx` version: <IP_ADDRESS>.1.0
- `torch-xla` version: 2.1.2
- `transformers-neuronx` version: <IP_ADDRESS>

Neuron Driver:

aws-neuronx-collectives/now <IP_ADDRESS>-c101c322e amd64 [installed,local]
aws-neuronx-dkms/now <IP_ADDRESS> amd64 [installed,local]
aws-neuronx-runtime-lib/now <IP_ADDRESS>-1b3ca6425 amd64 [installed,local]
aws-neuronx-tools/now <IP_ADDRESS> amd64 [installed,local]

Who can help?
@dacorvo
Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[X] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction (minimal, reproducible, runnable)
I use optimum-cli to export Llama3 model from the official repository with this command:
optimum-cli export neuron --model meta-llama/Meta-Llama-3-8B
--batch_size 1
--sequence_length 8192
--auto_cast_type fp16 `
--num_cores 24
/data/llama3_neuron/
I use the same image for that as I use to run TGI: ghcr.io/huggingface/neuronx-tgi:0.0.23
Then I run the TGI container with this command:
docker run -p 8080:80
--rm
-it
-v $(pwd)/data:/data
--device=/dev/neuron0
--device=/dev/neuron1
--device=/dev/neuron2
--device=/dev/neuron3
--device=/dev/neuron4
--device=/dev/neuron5
--device=/dev/neuron6
--device=/dev/neuron7
--device=/dev/neuron8
--device=/dev/neuron9
--device=/dev/neuron10
--device=/dev/neuron11
--privileged
-e HF_TOKEN=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
-e HF_AUTO_CAST_TYPE="fp16"
-e HF_NUM_CORES=24
ghcr.io/huggingface/neuronx-tgi:latest
--model-id /data/llama3_neuron
--max-batch-size 1
--max-input-length 3164
--max-total-tokens 8192
I run simple load tests with locust, emulating 10 users sending concurrent requests of variable length, and see that all neuron cores are loaded around 60% only and the performance is far from ideal (0.1-0.2 rps):

Expected behavior
Neuron cores are loaded closely to 100%.

@dlptv, thank you for your feedback. I see that you added a token in the code snippet you submitted: this is not safe to publicly share hugginface tokens, even with low rights, so please invalidate it as soon as possible.
The reason why your cores are not used at full capacity is because you are using a batch size of 1, meaning that requests are processed in sequence instead of being parallelized. Try with a batch_size of 10 and you will see a difference.


doc: add comment for timezone string

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

Thanks @xxchan  and @tustvold


docs/openapi spec sorted yaml

This PR = #7413 - the last commit, "force entries order in generated file" + a lyaml low-level dumper that generates sorted yamls instead + some other minor things.
The reason why the dumper is so much code is because lyaml doesn't expose its internal dumper, so the only way to do sorted yaml is copy-pasting the whole thing in order to edit one tiny part of the dump_mapping function (to do the key sort before iterating over the table). Related: https://github.com/gvvaughan/lyaml/issues/46

We decided to not use this change.


community[patch]: cap SQLAlchemy and update deps

SQLAlchemy 2.0.36 introduces a regression when creating a table in DuckDB.
Relevant issues:

In SQLAlchemy repo (resolution is to update DuckDB): https://github.com/sqlalchemy/sqlalchemy/discussions/12011
In DuckDB repo (PR is open): https://github.com/Mause/duckdb_engine/issues/1128

Plan is to track these issues and remove cap when resolved.

The duckdb code is fixed from the looks of it: https://github.com/Mause/duckdb_engine/issues/1128
The dependency lock is causing issues for other dependencies:
> The user requested sqlalchemy==2.0.36
> flask-sqlalchemy 3.1.1 depends on sqlalchemy>=2.0.16
> langchain 0.3.8 depends on SQLAlchemy<3 and >=1.4
> langchain-community 0.3.8 depends on SQLAlchemy<2.0.36 and >=1.4


The baseurl for CentOS is invalid

The baseurl for CentOS has been invalid, update it.

NOTE: Please check the “Allow edits from maintainers” box below to allow
reviewers fix problems on your patch and speed up the review process.
Please delete this note before submitting the pull request.

This change is

@nightmeng Please sign the CLA. I can then merge this PR. Thx

@nightmeng Are you having any trouble signing the CLA?

So that this doesn't get stale, I'm implementing this change in PR #3579.


used separate mutex for addrbook locaAddresses

Motivation
#2007
Closes #2007
Changes
Used separate RWMutex for addrBook localAddresses
Test Plan
Used existing package unit tests.

@y0sher truth to be told, I got no idea where the bug is, that 'bors' failed. May it be an error in integration tests or somewhat?

@justplesh not your fault. we're having some issues with the testing infra we'll merge as soon as it will resolve.

@y0sher is there any way I can help to resolve an issue with infra?

it's an elasticsearch logs delay, we're moving to a new and improved testing infra that won't have these issues. thanks for the good will!
I refreshed the indices, lets try again :)
bors merge

bors merge

bors merge

bors merge

bors merge

bors merge

@noamnelke , looks like you have an automated script for that lol..
maybe will be better to add more timeout in the tests ?

haha, I'm lazy, but you're probably right...

see, no need 😝

@noamnelke wait, there will be more PR's soon ))


Feature/re-introducing ranks on the Node class (formlerly known as k_approximations)

The BAA, when using LRSP, need to give an indication of what rank needs to be used. Formerly we had:
for i, vec in enumerate(node.vectors):
    qc_vec = schmidt.initialize(vec, isometry_scheme=isometry_scheme, unitary_scheme=unitary_scheme)

which takes any vector and uses the Plesch-Algorithm to encode it. But the idea of using LRSP with BAA is to tell if any of those vectors are approximated by LRSP. Therefore, we need to add that information:
for i, (vec, low_rank) in enumerate(zip(node.vectors, node.ranks)):
    qc_vec = schmidt.initialize(
        vec, isometry_scheme=isometry_scheme, unitary_scheme=unitary_scheme,
        low_rank=low_rank
    )

and as a consequence, the Schmidt decomposition will now know what to do with this. From there, we need to (re-) add ranks (formerly it was called k_approximations) to the Node object. As we use @dataclass annotation (maybe we can use pydantic sometime in the future instead?) we need to add another default value when instantiating Node, which I chose to have [0] as being the vector with low_rank=0 default of schmidt.initialize function.
The logic is encoded in _create_node. All other changes are readability changes (like is_leaf property and its use of the class Node).
Finally, I added the test of BAA which includes two tests, one "no-op" that checks to see that the algorithm spits out exactly the same input state if no approximation is done. And a second, more complicated one, that does a series of tests and asserts if all except of 1% (rounded up) of the subtests pass. The test can be run in parallel mode by enabling it by the environment variable QLIB_TEST_PARALLEL=True which is False by default of course.
Please let me know if I can add more detail to any of these topics @israelferrazaraujo!
Also, as you always highlight yourself, I could be wrong about the ranks property and its use in the Schmidt decomposition.

Ah, I realize that I use pandas for organizing the test data. Uh, how shall we do this further on? Should I rewrite the code to avoid pandas?

I think I will re-write it without pandas!

Failing test! I see that in my tests, too, the test_initialize_loss_greedy_low_rank in test_baa_schmidt sometimes does not pass through. There is a mistake still there in the expected fidelity loss.

OK, this is indeed a consequence of my changes. I think we need to talk about the ramifications. I think that my changes need to be done in order for BAA & LRSP to be effectively active. Then, the greedy algorithm fails to find a valid solution sometimes!

I have merged your changes and will rework on my code now. I will create a new PR then!


[Question] Use a type-checker or different linter than those provided inside Spyder?

Issue Report Checklist
(Since this is a question, I removed the irrelevant checkboxes)

[x] Searched the issues page for similar reports

Question
Is there a way to use pieces of software such as Pyright or Ruff in Spyder? I went through the settings but could not find anything. I also searched for the corresponding plugins with no avail.
Versions

Spyder version: 6.0.0

I'm leaving the version here in case someone searches through the issue tracker in the future.

Hi @qexat and thank your for the feedback! I think this could be related with https://github.com/spyder-ide/spyder/issues/21040 For the moment, from the Spyder side, we don't have support for those projects. However, the package we use as LSP server to do the linting and completions for Python (https://github.com/python-lsp/python-lsp-server) seems like has a third party ruff extension available
Let us know if the info above helps!

Closing as a duplicate of #21040


Refactor TomcatService into ManagedTomcatService & UnmanagedTomcatSer…

…vice, for compatibility with SpringBoot.
Issues resolved:

2 Tomcat servers starting. (Spring & Tomcat9)
NPE due to Spring removing connector from tomcat instance. (Spring & Tomcat8.5)
Avoid unnecessary management of Tomcat server which is already being managed. (SpringBoot)

ArmeriaAutoConfiguration added error logging for server startup failure.
ArmeriaSettings fixed documented yaml.
boot-tomcat-sample/ SprignBoot app which reproduces the issue for tomcat8.5.
ManagedTomcatService added.
UnmanagedTomcatService added.
TomcatService functionality moved to subclasses.
TomcatVersion made public and VisibleForTesting added.
TomcatServiceTest renamed to ManagedTomcatServiceTest

Summary
Spring creates the Tomcat starter and uses it to start the tomcat server. Afterward, removes the connectors are removed from the service during startup.
After Spring is fully initialized it then re-associates the connectors, to the service.
Tomcat9
A new connector is created during the call to Tomcat.getConnector().
Resulting in  2 tomcat connectors. If both are using the default 8080 port, then a port collision occurs.
refer Tomcat9
Tomcat 8.5
A null is return from Tomcat.getConnector(). This will throw an error on startup, in the current code.
refer Tomcat85
As a follow up PR I will add the ArmeriaServerConfigurator to boot-autoconfigure.
Also I will fix async (Servlet 3.0) requests.

Thanks, @jmostella !


Lambda function executing code from prior layer version on "test" in aws  lambda console

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
A clear and concise description of what the bug is.
I have a function that executes code from a layer. I have made changes to the layer that remove the lodash dependency from everywhere in the code, then I run "amplify push" and push the layer and update the version, next I configure my function to use the update layer version, and then run "amplify push" to update the function in the cloud in the dev env. Finally, I press the "test" button on the aws lambda console, and it  fails saying it cannot find lodash dependency. I have examined the zip file for the layer version and there is no reference to lodash. I have confirmed in the lambda console which layer version is configured for the function, and confirmed that the source code in the zip file from the console that it does not contain any reference to lodash. I don't know what to do now, it seems that there is some issue where and old version is pinned somewhere and it cannot access the new version's code.

Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.25.0
To Reproduce
Steps to reproduce the behavior or terminal output if applicable
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Mac/Windows/Ubuntu]
Node Version. You can use node -v to check the node version on your system

Additional context
Add any other context about the problem here.

Dealing with the same exact thing. I figured out amplify doesn't follow AWS's layer versioning convention and instead uses its own one based on layer's description.
If you go here https://console.aws.amazon.com/lambda/home?region=us-east-1#/layers
and open up your layer you'll see that

As you can see aws has 69 versions of this layer while amplify only has 11, at the same time I'm only able to see 9 from the CLI.

I noticed that amplify doesn't always recognizes code update inside package (not sure what it depends on) but a new aws version seems to be created every time. In other words: I might have version 1, then change the code in it, amplify doesn't show any new versions in the CLI, then I do a push with other function updates and see a new version pop up on aws (:2 with description that says "Lambda layer version 1"). Something like this:
2 | arn:aws:lambda:us-east-1:99999999999:layer:CommonLayer:2 | Lambda layer version 1
1 | arn:aws:lambda:us-east-1:99999999999:layer:CommonLayer:1 | Lambda layer version 1

Then a few code changes & pushes later amplify CLI finally recognizes layer update and offers an update to V2, but the issue is that by then you have already deprecated V2 in favour of something like V5

Dealing with the same exact thing. I figured out amplify doesn't follow AWS's layer versioning convention and instead uses its own one based on layer's description.
If you go here https://console.aws.amazon.com/lambda/home?region=us-east-1#/layers (choose your appropriate region)
and open up your layer you'll see that

As you can see aws has 68 versions of this layer while amplify only has 11, at the same time I'm only able to see 9 from the CLI.

This results in different aws versions mapping to the same amplify version.
I noticed that amplify doesn't always recognizes code update inside package (not sure what it depends on) but a new aws version seems to be created every time. In other words: I might have version 1, then change the code in it, amplify doesn't show any new versions in the CLI, then I do a push with other function updates and see a new version pop up on aws (:2 with description that says "Lambda layer version 1"). Something like this:
2 | arn:aws:lambda:us-east-1:99999999999:layer:CommonLayer:2 | Lambda layer version 1
1 | arn:aws:lambda:us-east-1:99999999999:layer:CommonLayer:1 | Lambda layer version 1

Then a few code changes & pushes later amplify CLI finally recognizes layer update and offers an update to V2, but the issue is that by then you have already deprecated V2 in favour of something like V5
P.S. I'm pushing 2 separate amplify environments (staging & dev) with the same layers so that only makes those versions multiply faster, but it's not the problem itself. It happens on a single env as well.
Still my use case is rather unconventional as we keep the layer in a separate repo (it has DB connectivity that is shared across multiple amplify apps) so the layer's code in my amplify app is ignored on the main project's gitignore (root of the project).
So it's not part of the amplify's app repo, while at the same time we need that code in the build phase so we pull it from git as a separate step in the build script, that pulled code is probably recognized by amplify as a "change" so later on during build when it pushes backend, it also creates a new layer version each time we deploy anything.

Did you manage to solve this? I'm facing the exact same issue as you did:

@pashka4281 @cc-bojan
Did any of you found a solution ?
I'm facing the same issue too and it's kind of frustrating because I can never use the last version of my layer as I intend to.
Thanks in advance !

@pashka4281 @cc-bojan
Did any of you found a solution ?
I'm facing the same issue too and it's kind of frustrating because I can never use the last version of my layer as I intend to.
Thanks in advance !

This is something we are tracking in an overall rework for Lambda Layer Improvement There is a similar issue targeting this problem tracking #5072

@pashka4281 @cc-bojan
Did any of you found a solution ?
I'm facing the same issue too and it's kind of frustrating because I can never use the last version of my layer as I intend to.
Thanks in advance !

Yeah, we just started to modify templates manually inserting the proper version's ARN instead of using the cli