Cache never finishes building

Workflow version
2021.11
Alfred version
4.6.1 build 1274
macOS version
12.1
Debugger output
[15:19:56.258] Logging Started...
[15:20:04.735] Google Drive[Script Filter] Queuing argument 'j'
[15:20:04.886] Google Drive[Script Filter] Queuing argument 'ju'
[15:20:04.897] Google Drive[Script Filter] Script with argv 'j' finished
[15:20:04.900] Google Drive[Script Filter] {"items":[{"title":"Cache is being built…","subtitle":"Please be patient. Depending on how many files you have, it can take a while.","valid":false}]}
[15:20:04.963] Google Drive[Script Filter] Queuing argument 'jua'
[15:20:05.072] Google Drive[Script Filter] Queuing argument 'juan'
[15:20:05.100] Google Drive[Script Filter] Script with argv 'jua' finished
[15:20:05.102] Google Drive[Script Filter] {"items":[{"title":"Cache is being built…","subtitle":"Please be patient. Depending on how many files you have, it can take a while.","valid":false}]}
[15:20:05.234] Google Drive[Script Filter] Script with argv 'juan' finished
[15:20:05.238] Google Drive[Script Filter] {"items":[{"title":"Cache is being built…","subtitle":"Please be patient. Depending on how many files you have, it can take a while.","valid":false}]}

More details
Trying to use this workflow for the first time. Initiated cache build 3 days ago. When I enter a query, I get the message, "please be patient..". 3 days later I am still getting the same message.
The google drive I am trying to index is approx. 980 GB.
Any suggestions would be welcome.

approx. 980 GB

The size does not matter, only the number of paths. Ten 1MB files take ten times as long than one 10MB file. But three days sounds like something interrupted the process.
Restart your Mac, then run the following in a terminal:
osascript -e 'tell application id "com.runningwithcrayons.Alfred" to run trigger "googledrivelaunchd" in workflow "com.alfredapp.googledrive" with argument "uninstall"'
osascript -e 'tell application id "com.runningwithcrayons.Alfred" to run trigger "googledrivelaunchd" in workflow "com.alfredapp.googledrive" with argument "install"'

It will force a restart of the cache building. Be sure to have the debugger open when you do it.

Ran two scripts as you directed.
here is the output from the terminal:
juan@Juans-MacBook-Pro ~ % osascript -e 'tell application id "com.runningwithcrayons.Alfred" to run trigger "googledrivelaunchd" in workflow "com.alfredapp.googledrive" with argument "uninstall"'
juan@Juans-MacBook-Pro ~ % osascript -e 'tell application id "com.runningwithcrayons.Alfred" to run trigger "googledrivelaunchd" in workflow "com.alfredapp.googledrive" with argument "install"'
juan@Juans-MacBook-Pro ~ %
Here is the output from the debugger:
[14:10:06.340] Logging Started...
[14:10:42.646] Google Drive[External] Processing complete
[14:10:42.650] Google Drive[External] Passing output 'uninstall' to Run Script
[14:10:42.727] Google Drive[Run Script] Processing complete
[14:10:42.732] Google Drive[Run Script] Passing output '' to Conditional
[14:11:18.864] Google Drive[External] Processing complete
[14:11:18.869] Google Drive[External] Passing output 'install' to Run Script
[14:11:18.942] Google Drive[Run Script] Processing complete
[14:11:18.946] Google Drive[Run Script] Passing output 'BUILD_CACHE' to Conditional
[14:11:18.948] Google Drive[Conditional] Processing complete
[14:11:18.949] Google Drive[Conditional] Passing output 'BUILD_CACHE' to Run Script
[14:11:19.030] Google Drive[External] Processing complete
[14:11:19.033] Google Drive[External] Passing output '' to Arg and Vars
[14:11:19.034] Google Drive[Arg and Vars] Processing complete
[14:11:19.035] Google Drive[Arg and Vars] Passing output '' to Run Script
[14:11:19.158] Google Drive[Run Script] Processing complete
[14:11:19.166] Google Drive[Run Script] Passing output '' to Run Script
[14:11:19.168] Google Drive[Run Script] Passing output '' to Conditional
[14:11:19.169] Google Drive[Conditional] Processing complete
[14:11:19.169] Google Drive[Conditional] Passing output '' to Conditional
[14:11:19.402] ERROR: Google Drive[Run Script] 'remote_info_plist' (https://raw.githubusercontent.com/alfredapp/google-drive-workflow/master/source/info.plist) appears to not be reachable.
The computer crashes about 1 minute after running the second script.

Perhaps it is relevant that this is running on a 2021 Macbook Pro M1 with 16GB RAM.
Here's the overview:
Model Name:	MacBook Pro
Model Identifier: MacBookPro18,1
Chip: Apple M1 Pro
Total Number of Cores: 10 (8 performance and 2 efficiency)
Memory: 16 GB
System Firmware Version: 7429.61.2
OS Loader Version: 7429.61.2
Activation Lock Status:	Disabled

First message I get in the Finder is :CommCenter wants to use the "login" keychain. If I enter it here, I get a long series of popup messages from different services asking the same question, then the computer crashes.

here is the output

Please take care to always use fenced code blocks when posting code.
Update to the latest version before continuing.

First message I get in the Finder is :CommCenter wants to use the "login" keychain. If I enter it here, I get a long series of popup messages from different services asking the same question, then the computer crashes.

That has nothing to do with the Workflow. Search for CommCenter online (example) and fix the crash before trying again with the instructions from the previous post.

Updated to version 2021.12 of the workflow.
Ran first script. Debugger output:
[08:13:13.193] Logging Started... [08:13:56.510] Google Drive[External] Processing complete [08:13:56.515] Google Drive[External] Passing output 'uninstall' to Run Script [08:13:56.593] Google Drive[Run Script] Processing complete [08:13:56.600] Google Drive[Run Script] Passing output '' to Conditional
posting this output now in case 2nd script causes my computer to crash again before I can post the output from the 2nd script.

output from 2nd script:
no crash, new error "no such file or directory".
[08:18:21.226] Google Drive[External] Processing complete [08:18:21.232] Google Drive[External] Passing output 'uninstall' to Run Script [08:18:21.238] STDERR: Google Drive[Run Script] Boot-out failed: 5: Input/output error Try re-running the command as root for richer errors. rm: /Users/juan/Library/LaunchAgents/com.alfredapp.launchd.googledrivecache.plist: No such file or directory [08:18:21.239] Google Drive[Run Script] Processing complete [08:18:21.240] Google Drive[Run Script] Passing output '' to Conditional

Please don’t reply serially. This is not a chat, and having multiple posts in a row makes it really hard to follow. Plus, your last output was not from the second command, it was from the first.
You can’t do it one step at a time, you have to restart your Mac then run both commands and wait. Those commands are resetting the cache rebuild. As I said before you need to fix your crash issue before doing it. The cache takes a while to build, so when your machine crashes, everything was wasted. Until you fix the other problem with your macOS installation, there’s no point in continuing to try this.

Hi Vítor,
Ok, I'm not familiar with the use of GitHub for posting issues. I will consolidate my response in one comment.
The commCenter messages (and following crash) only happen after I run the scripts.  So there is no issue to fix separate from these scripts.
I believe I have followed the instructions correctly. On the 24th, I restarted the Mac, started the Alfred  debugger, and ran both commands from the terminal. That is when the keychain messages began popping up, followed by a crash a minute or two later.
I repeated the process, with the same result.
Today, I updated the workflow per your instructions, rebooted, and ran both scripts, one after the other. There were no error messages in the log this time, but after about a minute I got a pop-up, this time starting with CallHistoryPluginHelper. "Callhistorypluginhelper wants to use..."
I did nothing, did not even click cancel. After another minute or so the computer shut down.
I did not put the debit log results in GitHub yet because the computer crashed. I did copy the output to a note. Hopefully after restarting I can log in and retrieve the log and post it.
Sincerely,
Juan
Sent from Yahoo Mail on Android
On Mon, Dec 27, 2021 at 9:57 AM, Vítor @.***> wrote:
Please don’t reply serially. This is not a chat, and having multiple posts in a row makes it really hard to follow. Plus, your last output was not from the second command, it was from the first.
You can’t do it one step at a time, you have to restart your Mac then run both commands and wait. Those commands are resetting the cache rebuild. As I said before you need to fix your crash issue before doing it. The cache takes a while to build, so when your machine crashes, everything was wasted. Until you fix the other problem with your macOS installation, there’s no point in continuing to try this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

Ok, restarted the computer, started Alfred workflow debugging, and ran both commands from terminal, one after the other.  I did not take any action on the computer. After about a minute, got a pop-up that "CallHistoryPluginHelper wants access to your keychain". I did nothing, not even to click 'cancel' on the pop-up. After about another minute, the computer shut down.
Because the pop-ups and the following shutdown only appear after running these scripts, I do not see any way to troubleshoot this separately.  I can contact Apple Support, but I expect they will say the problem lies with the script.  I am not a developer, but what stands out to me in the report is this line:
CORE 0 is the one that panicked
I can provide the crash report if that would be helpful. How do you suggest proceeding?

got a pop-up that "CallHistoryPluginHelper wants access to your keychain"

That is yet again something different. All those commands are doing is setting up a launchd agent and running it. It has nothing to do with the KeyChain. Furthermore, it doesn’t make sense the crash would happen a minute after running the commands. Only thing that comes to mind is that something in your launchd is broken.

I can provide the crash report if that would be helpful.

It might.

How do you suggest proceeding?

What is the output of launchctl list | grep googledrivecache?

Hi Vítor,
I will run that grep in the next hour and will let you know the results.
Two things occured to me: first, roughly how much disk space do I need to have free in order to build a cache for a Google Drive of about 1 TB and tens of thousands of files? I have 200 GB free now. Should that be sufficient? Not sure what is being cached.
Second, my Google drive app is in ' streaming ' mode,  rather than ' offline ' mode, so that all the files are in the cloud only, and only the files I am using are downloaded on demand. Will your workflow handle that configuration?
Sincerely,
Juan
Sent from Yahoo Mail on Android
On Mon, Dec 27, 2021 at 11:51 AM, Vítor @.***> wrote:
got a pop-up that "CallHistoryPluginHelper wants access to your keychain"
That is yet again something different. All those commands are doing is setting up a launchd agent and running it. It has nothing to do with the KeyChain. Furthermore, it doesn’t make sense the crash would happen a minute after running the commands. Only thing that comes to mind is that something in your launchd is broken.
I can provide the crash report if that would be helpful.
It might.
How do you suggest proceeding?
What is the output of launchctl list | grep googledrivecache?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

I have 200 GB free now

More than enough.

Not sure what is being cached.

The paths themselves, as text, plus little associated information (e.g. if it’s a file or directory).

my Google drive app is in ' streaming ' mode,  rather than ' offline ' mode, so that all the files are in the cloud only

The Workflow specifically addresses that configuration.

FWIW, the only non-standard thing I can think of that I have installed on my Mac OS configuration is Homebrew, with which I installed 'coreutils'. I mention that in case it might affect the operation of your script.
here's the output from the command:
launchctl list | grep googledrivecache
output:
-	0	com.alfredapp.launchd.googledrivecache
below is the crash report generated when the computer crashes:
Crash Report
Debugger message: panic
Memory ID: 0x1
OS release type: User
OS version: 21C52
Kernel version: Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:41 PST 2021; root:xnu-8019.61.5~1/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: 88208EF24C07AA8B02CDA1369E036EBD
Kernel UUID: 2F4E22DC-64BE-3369-B574-0909F0571FA6
iBoot version: iBoot-7429.61.2
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x000000000fe10000
KernelCache base:  0xfffffe0016e14000
Kernel slide:      0x000000001063c000
Kernel text base:  0xfffffe0017640000
Kernel text exec slide: 0x0000000010724000
Kernel text exec base:  0xfffffe0017728000
mach_absolute_time: 0x3717b44fd
Epoch Time:        sec       usec
  Boot    : 0x61c9e158 0x0009d408
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x61c9e3ba 0x000d14ce

Zone info:
Foreign   : 0xfffffe00202fc000 - 0xfffffe0020310000
Native    : 0xfffffe100060c000 - 0xfffffe300060c000
Readonly  : 0xfffffe14cd2d8000 - 0xfffffe1666c6c000
Metadata  : 0xfffffe74811b0000 - 0xfffffe748d134000
Bitmaps   : 0xfffffe748d134000 - 0xfffffe7492b6c000
Largest zones:
Zone Name                      Cur Size  Free Size
kext.   kalloc.32768              5256M         0K
        vnodes                      60M        11K
        APFS_INODES                 44M     11546K
        namecache                   24M        38K
kext.   kalloc.16384                 4M         0K
CORE 0 PVH locks held: None
CORE 1 PVH locks held: None
CORE 2 PVH locks held: None
CORE 3 PVH locks held: None
CORE 4 PVH locks held: None
CORE 5 PVH locks held: None
CORE 6 PVH locks held: None
CORE 7 PVH locks held: None
CORE 8 PVH locks held: None
CORE 9 PVH locks held: None
CORE 0 is the one that panicked. Check the full backtrace for details.
 About one or two hours in, do gd in Alfred and see if it works.

Ok, the command executed without any errors. Rebooting and I will let it run overnight and test it in the morning.
On Monday, December 27, 2021, 08:26:18 PM EST, Vítor Galvão @.***> wrote:
I don’t see anything in the crash that looks relevant.
here's the output from the command
In that case, run:
rm "${HOME}/Library/Caches/com.runningwithcrayons.Alfred/Workflow Data/com.alfredapp.googledrive/tmp.db"
If it succeeds, reboot and go about your day. About one or two hours in, do gd in Alfred and see if it works.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

Opened Alfred, typed:
gd Juan (because I know there are files and directories that include that name)
Alfred returned the message:
No cache found!
Last night, after executing the command and rebooting the computer per your instructions, I checked the folder, com.alfredapp.googledrive. It was empty.

Indeed, this only reinforces the issue is somewhere in your macOS setup/installation and not the Workflow. Though we already knew that because from the Workflow’s many users you’re the only experiencing the problem. I’m still not sure where exactly your setup is bad but it seems to be somewhere around launchd. The rest you’ll have to figure out yourself, since the issue isn’t related to either Alfred or the Workflow and I cannot reproduce.
You can still try to use the Workflow by manually generating the cache via :gdrebuildcache.

Hmmm. I see what you mean, and yet I only have this issue when I run these scripts. It seems to be an interaction between your scripts my OS.
The options I can think of are:1. Do a clean reinstall of the MacOS (time-consuming to reinstall everything)2. Contact Apple Support (I am doubtful that they will be able or willing to troubleshoot this issue)3. Choose another cloud provider that spotlight does integrate with in the 'optimized' mode, rather than with all files stored locally.  It sounds like Dropbox is one such provider. Limited research indicates that even iCloud does not support indexing if the files are not mirrored on the local drive.
Any thoughts?
Juan
On Tuesday, December 28, 2021, 08:45:13 AM EST, Vítor Galvão @.***> wrote:
Indeed, this only reinforces the issue is somewhere in your macOS setup/installation and not the Workflow. Though we already knew that because from the Workflow’s many users you’re the only experiencing the problem. I’m still not sure where exactly your setup is bad but it seems to be somewhere around launchd. The rest you’ll have to figure out yourself, since the issue isn’t related to either Alfred or the Workflow and I cannot reproduce.
You can still try to use the Workflow by manually generating the cache via :gdrebuildcache.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

It seems to be an interaction between your scripts my OS.

Not necessarily. The script calls regular macOS tools, so presumably if you did that on your own in another capacity, the issue would still happen. It’s unlikely the script is causing the issue, but that launchd (which the script interacts with) is the source of the problem.
Think of it like having a car (the scripts) which you drive over a specific road (launchd) and always get a flat tire. Your reply assumes a combination of the car and road is causing the flat tire, when the likeliest answer is only the road is to blame; you just never tried going over that particular road with a different car.

Any thoughts?

I agree with your assessment in the three points, including the caveat in 2.

Limited research indicates that even iCloud does not support indexing if the files are not mirrored on the local drive.

I can’t say one way or another, as I never tried it. I would find it odd for that to be the case, though, since they’re both controlled by Apple.
Worth noting that on the Alfred Forums, the only regular complaint of missing indexing is about Google Drive.

Thanks for the feedback. Perhaps it is worth opening a ticket with Apple, and perhaps also doing a search for the terms launchd, osascript and system crashes. I would hate to reinstall the OS, only to find that the problem still occurs because it is a code issue with launchd.
Are there other standard (ideally Apple) scripts that I could run to see if I have this issue with other scripts? That would be very helpful.
Juan
On Tuesday, December 28, 2021, 10:59:29 AM EST, Vítor Galvão @.***> wrote:
It seems to be an interaction between your scripts my OS.
Not necessarily. The script calls regular macOS tools, so presumably if you did that on your own in another capacity, the issue would still happen. It’s unlikely the script is causing the issue, but that launchd (which the script interacts with) is the source of the problem.
Think of it like having a car (the scripts) which you drive over a specific road (launchd) and always get a flat tire. Your reply assumes a combination of the car and road is causing the flat tire, when the likeliest answer is only the road is to blame; you just never tried going over that particular road with a different car.
Any thoughts?
I agree with your assessment in the three points, including the caveat in 2.
Limited research indicates that even iCloud does not support indexing if the files are not mirrored on the local drive.
I can’t say one way or another, as I never tried it. I would find it odd for that to be the case, though, since they’re both controlled by Apple.
Worth noting that on the Alfred Forums, the only regular complaint of missing indexing is about Google Drive.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

I've been having the same problem as @jfthompson1, including the weird "CommCenter" keychain errors. I'm also running a M1 MacBook and have a largish number of paths (find "/Volumes/GoogleDrive/My Drive" | wc -l gives me ~250K).
I believe the problem is due to Ruby glob trying to load all of its paths inefficiently into memory. I replaced glob by calling the builtin system find command instead.
I also had to add a default access time (Jan 1, 1970) instead of skipping a file completely, since path.atime.to_i seemed to fail for every path in my Google Drive.
I will add a PR for these changes shortly.

I believe the problem is due to Ruby glob trying to load all of its paths inefficiently into memory.

I wouldn’t expect it to manifest how it has, though.

I replaced glob by calling the builtin system find command instead.

Try the Find module first. Let’s keep it Ruby where we can rather than shelling out and having to interpret that.

I also had to add a default access time (Jan 1, 1970) instead of skipping a file completely, since path.atime.to_i seemed to fail for every path in my Google Drive.

That seems like another issue caused by the interaction between macOS and Google Drive. But this Workflow is meant to address that, so sure.

@jfthompson1 @MWYang Could you both please try the attached version and see if it works for you?
Google Drive.alfredworkflow.zip

@jfthompson1 @MWYang Could you both please try the attached version and see if it works for you?
Google Drive.alfredworkflow.zip

Wait, I need a further fix.

@jfthompson1 @MWYang The attached version changes few things but should work by using the Find module instead of glob. Could you both try it out and see if it works for you?
Google Drive.alfredworkflow.zip

Thanks for fast response. Unfortunately, this new version still seems to create the same or similar issue as before — just as with the current release, my computer hangs and crashes shortly after running the script.

I wouldn’t expect it to manifest how it has, though.

I share your skepticism – 250K paths shouldn't be too much for modern computers. But IMO the evidence still points to a problem when trying to do all of the path scanning purely in Ruby.
This post suggests using IO.popen in combination with find. That would avoid the creation of a temporary text file with the find results.

But IMO the evidence still points to a problem when trying to do all of the path scanning purely in Ruby (plus interaction with large number of paths and/or M1).

I’m not convinced yet. I’m also on an M1 and I can run the Workflow on the whole drive (/) which is over 4 million files and there is no crash. That’s with both the previous and current solutions. Plus, we can easily test that using find does indeed return things as it finds them rather than building the list first. Just compare:
require 'pathname'
Pathname.new(ENV['HOME']).glob('**/*').each { |a| puts a }

to
require 'pathname'
Pathname.new(ENV['HOME']).find { |a| puts a }

There is a noticeable delay before the first one begins to show files, while the second one is instant.

I'd want to look into this further, but I'm not sure of the best way forward.

Because I cannot reproduce, it’s near impossible to work on next steps. I’d need a reproducible case or know what is particular about both of your setups.
I recommended to @jfthompson1 using :gdrebuildcache but got no reply if it causes the same issue or not. Does doing that crash it for you?

Yes, I did try only using :gdrebuildcache and got the same behavior. And then I narrowed the cause down to the glob and database loop by running a modified version of the :gdrebuildcache on its own outside of Alfred. I'm very positive the issue is with running that specific block of code, but I'm also still not sure what exactly the mechanism is.
What led me to further think this is some kind of memory issue is that I saw ruby posting multiple GB (I think close to 10 GB one time before my computer froze) on the Disk section of Activity Monitor. That struck me as very weird, since the finished cache DB is only <50 MB.
But RAM usage also looked reasonable up until crash. So I'm not too sure either.
I'm happy to help you debug further, since I get that you can't do much without being able to reproduce the issue. But I also don't know what to try next.

What about  this one?

Ah, unfortunately still doesn't work with the same error. I should've mentioned earlier than I only have 8 GB of RAM, so even though I have many fewer files, my ceiling is lower.
When I wrote PR #11, I double-checked that Ruby read the written-to-disk list of files one line at a time (ofc there were other flaws with this PR). Maybe the way Ruby handles file reads immediately discards previous lines in a way that the .find solution doesn't?

I have high hopes for this one.
But if that doesn’t work, here’s a followup which should be considerably slower.
And here’s a question for both of you: how many free disk space do you have?

My hard drive has ~125 GB free out of 256 GB.
The first one using just .lazy still led to the same problem. The second one manually starting the garbage collection did finish building the cache successfully (i.e. no forced restart) but still caused my computer to be frozen and inoperable (i.e. multiple keychain login windows popped up, Mac menu bar gone, trackpad inoperable). It also ran much slower, as you thought it would.
I tried the second one again but changed the script to only call garbage collection every 1000 loops. Doing that still resulted in a bunch of keychain login windows, but the script did finish successfully, and after manually completing each of the login windows, my computer seemed to be fully operational again. Still, it's not something I would like to do regularly.

This still seems to be something related to your particular setups. I’m planning on making another release soon, though it won’t fix this. I don’t want to follow the solution in the PR because the true problem isn’t clear and I don’t want to make the code possibly worse for everyone else to fix an uncertain issue faced by a single person.
So much the better if we can find the definitive cause and solution in a way that is idiomatic and doesn’t affect anyone else. Until then, I did offer a working solution that works for you despite being slower and you also have the code from your PR. There’s no problem in changing those for your particular setup.
Thank you for the investigation so far.


[Feature] Allow tests to be run in sequence, not in parallel

When using neotest to test an entire file, these tests are run in parallel however in some cases, e.g. in a Golang test suite with multiple test cases each depending on creating and cleaning up a database, this can lead to race conditions causing bugs in the test behaviour.
This is partially a problem in userland that tests can't be run in parallel, but if this is not within your control, as is the case in my work (i.e. I can't refactor these tests) I'd prefer to just have each test run in sequence.
Is there an easy way to achieve this behaviour? i.e. a flag that can be passed to the run command to say run tests in this file sequentially.

Very valid use case that should be covered! I've added a concurrent config option for global defaults and also a concurrent argument to individual runs

@rcarriga that's awesome, thanks ❤, I'll give it a shot and report back

@rcarriga I've been trying this out and have found the behaviour of using concurrent = false to be much slower than I'd have expected. I think this might be due to a peculiarity of how the go tests are structured. So go has the concept of table tests similar to what you get with jest in js
e.g.
package add
import "testing"
func TestAdd(t *testing.T) {
	// DB setup happens hear
    cases := []struct {
        desc     string
        a, b     int
        expected int
    }{
        {"TestBothZero", 0, 0, 0},
        {"TestBothPositive", 2, 5, 7},
        {"TestBothNegative", -2, -5, -7},
    }
    for _, tc := range cases {
        actual := add(tc.a, tc.b)
        if actual != tc.expected {
            t.Fatalf("%s: expected: %d got: %d for a: %d and b %d",
                tc.desc, actual, tc.expected, tc.a, tc.b)
        }
    }
}

We've current got things setup so that each one of the Test* items is detected as a test. This is how a lot of tests in go are written.
In my case the parent function does the DB setup and clean up runs inside each test case (the above is too simple, but hopefully the idea is clear), running that in parallel is what causes the issues since cleanup is happening whilst other tests are running.
With concurrent = false things are very, very slow/can block seemingly indefinitely, I think this is maybe because the test setup is being run as though the TestAdd was called but with only one of those items at a time. I'm not sure since I can't really inspect what is being run (without adding logs throughout neotest). In the first instance I was wondering if you had any ideas?

The concurrency that neotest core controls is the running of the commands that an adapter returns, so it's up to the adapter to return whatever command is suitable.
So in this case I'm guessing that neotest-go is returning a separate command for each TestBothZero, TestBothPositive and TestBothNegative which will mean that 3 commands will be run that'll each do the setup and tear down completely isolated. Without disabling concurrency these 3 still ran all setup/tear down, it was just concurrent so you didn't notice however now since they're run serially it's noticeable. The solution to this problem would be for neotest-go to return a command to run the TestAdd test.

Yeah, this will be a quirk of our desire to support running individual table based test cases, but I guess when the request is for a parent test then we'd ideally want it to just test the file and run that command. I think it isn't in this case that we are explicitly constructing a command to run all tests, but each test case is being identified as a separate (parallel) test rather than because the parent is being run there is no reason to attempt to run the child tests since that is already being covered.
I don't know if neotest has the concept of parent and child relationships, as AFAIK all we are doing is sending the command to run a test file or nearest test for example, but if that test has subtests these are also being run separately. I mean, the there is no difference based on the fact that some positions are children of another.
Does that make sense? I think my explanation here was probably not ideal bit too tired to formulate this clearly

Yes I think I follow. The way neotest breaks apart the tree is very simple, as you said it doesn't account for parent/child relationships in the tree, it just breaks up positions based on type. You can see the logic here https://github.com/nvim-neotest/neotest/blob/master/lua/neotest/client/runner.lua#L125-L132. I'd be open to allowing for more complex splitting of positions but not sure how.
Off the top of my head, neotest could allow adapters to return multiple specs and so they can split the tree however they like.
So currently if we have a tree like
{
  type = "file",
  id = "test_file",
  {
    { type = "file",
      id = "lone_test"
    },
    {
      type = "test",
      id = "parent_test",
      {
        {
          type = "test",
          id = "child_test_1",
        },
        {
          type = "test",
          id = "child_test_2",
        },
        {
          type = "test",
          id = "child_test_3",
        },
      },
    },
  },
}

and the adapter only returns a run spec for tests, we'll end up with 5 separate run specs for each test.
However instead the adapter could return multiple specs for the "file" position, and return specs for lone_test and
parent_test. That way neotest doesn't need to worry about more complex relationships between positons but the adapter
maintains control of exactly which positions are run.

@rcarriga that makes sense if we knew all the positions in the adapter that were going to be returned for the file then we could filter then based on the parent and the strategy e.g. file etc to decide what to run inside the adapter. Haven't looked at neotest code or the adapter in a while but does the adapter have access to a tree similar to the example in your code snippets I know we have functions to help get the positions but can't remember if in run command function we can access the positions for a particular type of run command 🤔

Yep the build_spec function receives the tree to run so the adapter has full context of what is being run, which is where it would return multiple specs

OK the build_spec function can now return a list instead of just one RunSpec. Going to close this as the rest of the required changes are in neotest-go


merge develop

Pull Request Checklist

[x] Pull request is based on the develop branch
[ ] Pull request includes a changelog file. The entry should:

Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from EventStore to EventWorkerStore.".
Use markdown where necessary, mostly for code blocks.
End with either a period (.) or an exclamation mark (!).
Start with a capital letter.
Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry.

[x] Pull request includes a sign off
[x] Code style is correct
(run the linters)

merge matrix-org:develop


Fix documentation typos

Thank you for your contribution!  It's a good way to contribute to Hacktoberfest 😎


No compatible version found<EMAIL_ADDRESS><6.0.0'

npm ERR! notarget No compatible version found<EMAIL_ADDRESS><6.0.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.0.1","5.6.23","5.7.1","5.7.2"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'babel-core'
npm ERR! notarget

npm ERR! notarget It was specified as a dependency of 'babel-core'

Just a head-sup the npm log indicates this is likely related to babel-core

a quick check against npm reveals, that there does exist a valid version.
npm info babylon --json | jq '.versions'
[
  "0.0.1",
  "5.6.23",
  "5.7.1",
  "5.7.2",
  "5.8.2"
]

maybe try (with npm 2.x >):
npm cache clear
npm install

this seems to now have been resolved, sounds like some kinda npm publish hickup.


ClassNotFoundException in AnnotationProcessor's process method  when  use Class.forName()

Hi,
I use  a  AnnotationProcessor    generate some javacript model class within Intellij IDEA .
When i execute compileGroovy task in my gradle build,my annotationProcessor can be execute,and can find the annotaioned class,but when get the Class object , there throw ClassNotFoundException.see pickure below:

It seems like the classloader can't find  my Model class ,how shoud i handle this problem?
Enviroment:
Java8
Gradle4.1
gradle-apt-plugin:0.12
IDEA: 2017.2.5
Thanks!

Apparently, this annotation processor expects your annotated class to be in the same "classpath" as the annotation processor (see https://github.com/ralscha/extclassgenerator/blob/cf186f52e97d9599e25381a8ad79e26bd52fd936/src/main/java/ch/rasc/extclassgenerator/ModelAnnotationProcessor.java#L137-L138), which is not the case when you (purposefully) segregate them into -classpath and -processorpath.
Please file a bug on https://github.com/ralscha/extclassgenerator/ that the annotation processor does not work in your context.

Hi,
Thanks very much!
I will try it.


IRGen: Fix regression when pattern matching against an existential with associated types

Now, we need to just ban this case when we're in Swift 4 mode, but
to keep existing code working, add a hack.
Fixes rdar://problem/29605388.

@swift-ci Please smoke test


Update to newer Node 4.4.4 API

Thank you for your contribution!
This is something interesting, but this would loose backward compatibility for old users of this project which didn't upgrade their Node.js version.
An acceptable solution would be to base the syntax on nan, which allow c++ compilation from node 0.8 to 6.3. Feel free to submit any PR on this!


Support import aliases

I sometimes have identically named models in an api and domain package. Therefore I need to alias the import of the api package. This unfortunately generates the model names without the import alias resulting in invalid mapping code.
import 'package:api/api.dart' as api;
import 'package:auto_mappr_annotation/auto_mappr_annotation.dart';
import 'package:domain/domain.dart';

part 'test_mapper.g.dart';

@AutoMappr([
  MapType<Test, api.Test>(),
  MapType<api.Test, Test>(),
])
class Mappr extends $Mappr {}

I'll take a look at this :)

@DevNico hey, I already have WIP implementation for this. :)

Oh alright guess I'll just wait for you then :D


Alignment of Newsletter Input box and Subscribe button is not good  [GsSOC'23]

Issue Description
There's an issue with the alignment of input text field and the Submit button in the Newsletter section (Footer). I'll solve that issue by making some simple changes into Footer CSS.
Expected Behavior
After applying this changes in the footer section, the input text and the submit button will become more user friendly.
Current Behavior
Currently the alignment of input text field and the submit button is not looking good because of the bad alignment of submit button.
Possible Solution (optional)

I'll Change some CSS Positioning Properties.
I'll also make some changes into padding of the button.

Before :

After :

On which page and what screen size are you seeing this?

On which page and what screen size are you seeing this?

On all the pages it seems the same.
It's on full screen (1490 x 705). I can make it responsive.

@Monilprajapati assigned

Hey @varun-singhh Is this Repo still active? So i can resolve this Issue and raise the PR.


NSD DNSSec broken after BIND 9.18.0

Describe the bug
BIND 9.18.0 removed the python-based dnssec-keymgr, leading to failures in the nsd-dnssec unit.
Apr 20 12:41:12 koryaksky nsd-dnssec-start[4182876]: /nix/store/0rm8aws5rfxj4crab61yzffqldvc6xg2-unit-script-nsd-dnssec-start/bin/nsd-dnssec-start: line 7: /nix/store/57knpqw2siwi6saz3vws91hq33pvsg51-bind-9.18.1/bin/dnssec-keymgr: No such
file or directory

Steps To Reproduce
Enable dnssec handling via services.nsd.zones.<name>.dnssec
Expected behavior
dnssec is properly handled
Additional context
The deprecation of the dnssec-keymgr tool is documented here: https://downloads.isc.org/isc/bind9/9.18.2/doc/arm/html/notes.html#removed-features
Potential fix: package up https://gitlab.isc.org/isc-projects/dnssec-keymgr and use it instead of the no-longer included tools.
Notify maintainers
@hrdinka
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.34, NixOS, 22.05 (Quokka), 22.05pre-git`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.7.0`
 - nixpkgs: `/etc/src/nixpkgs`

current nixpkgs hash: 1ffba9f2f683063c2b14c9f4d12c55ad5f4ed887

systemd[1]: Started DNSSEC key rollover. nsd-dnssec-start[492709]: /nix/store/57fladh8c6dnzcva1fy7qq9wik5vw0bq-unit-script-nsd-dnssec-start/bin/nsd-dnssec-start: line 7: /nix/store/3h8ayi2ksj6kmfxb1qj8f2wj06a1jiay-bind-9.18.7/bin/dnssec-keymgr: No such file or directory systemd[1]: nsd-dnssec.service: Main process exited, code=exited, status=127/n/a
I would be happy to test.

Hi. Sorry, I completely forgot about this. I am currently looking into it. LDNS is just a C library for DNS programming. It offers example programs that include everything to setup DNSSEC. It does however lack the automatic key management and rollover functionalities of binds keymgr.
NSD is suggesting(?) to use OpenDNSSEC for policy based key management, like dnssec-keymgr is doing it. The project however, seems kinda dead. The Wiki with all the documentation does not work. The source repo however has seen some kind of activity.
I still can’t use DNSSEC so my knowledge about it is minimal. Does one of you know any best practices regarding DNSSEC and NSD? Should we use OpenDNSSEC or the simple LDNS tools and dismiss key-rollover/mimic it somehow. Is there another better tool that is broadly used?
Do you have examples for using/setting it up?

Thanks for the pointer to OpenDNSSEC! Can't believe I've missed that. The wiki at https://wiki.opendnssec.org/ indeed gives a 503 atm but that might have no relation with the state of the project itself.
It seems that in NixOS only the LDNS library (and the binary 'drill') is built, not the example tools that are included in the source: https://www.nlnetlabs.nl/projects/ldns/documentation/  These example tools might actually be of use: I had to install 'bind' now for tools like 'dnssec-keygen'.
I'll give it a try next week, and get back if I have something to show.

The examples are packaged in the ldns.examples output.

Hey all. Any pointers / any progress on how to solve this?

I have an ugly fix ... In the file nixos/modules/services/networking/nsd.nix replace the single line
  dnssecTools = pkgs.bind.override { enablePython = true; };

with this big hack
  dnssecTools =
    (pkgs.bind.overrideAttrs (_: rec {
      pname = "bind";
      version = "9.16.50";
      patches = [];
      outputs = ["out"]; # These two lines are needed because without them, I get this error:
      postInstall = ""; # error: cycle detected in build of ... in the references of output 'dev' from output 'out'
      postFixup = ''
        sitepackages=$(find $out/lib -name site-packages -print)
        substituteInPlace $out/bin/dnssec-keymgr \
          --replace-fail \
            'import isc.keymgr' \
            "$(printf '%s\n%s\n' \
              'sys.path.insert(1, "'$sitepackages'")' \
              'import isc.keymgr')"
      '';
      src = pkgs.fetchurl {
        url = "https://downloads.isc.org/isc/bind9/${version}/${pname}-${version}.tar.xz";
        hash = "sha256-gW26o8EVAZ8w/OvZ6O+Pdjf0rd6Rx52qCZsDUlWhV5U=";
      };
    }))
    .override {enablePython = true;};

I have no idea how it worked without the fixup step before.
If anyone knows a better way to fixup the reference to the python library built by the package, let me know.
It would probably be best to switch to using ldns.examples ... it might be difficult to recreate the exact same options the module has now.

Great stuff, thanks for the reply. I have since moved on to using Knot DNS (the other non BIND nameserver used on root servers), and it worked wonderfully for me, no workarounds needed.


Cannot install on Windows + Python 2.7, but can on 3.3, 3.4, and 3.5

I've created a minimal example of installing murmurhash using pip on AppVeyor here: https://github.com/suchow/test-murmurhash. It runs successfully on Windows and Python 3.3, 3.4, and 3.5, but not on 2.7.
The error it gives is:
murmurhash/mrmr.cpp(248) : fatal error C1083: Cannot open include file: 'stdint.h': No such file or directory
error: command 'C:\\Users\\appveyor\\AppData\\Local\\Programs\\Common\\Microsoft\\Visual C++ for Python\\9.0\\VC\\Bin\\cl.exe' failed with exit status 2

Here are the full build logs: https://ci.appveyor.com/project/suchow/test-murmurhash/build/1.0.1/job/r9t9duixfppuaefx#L13.

Microsoft forgot to include that header in VS Studio 2008, it's a common error that's not specific to murmurhash. Please obtain the header, e.g., from https://msinttypes.googlecode.com/svn/trunk/stdint.h and place it in an include directory (e.g., under /include).

Thank you, I can confirm that this fixed the issue.

Btw: we are now packaging stdint.h with murmurhash, so you don't need to download/install it yourself anymore.


New Term Request: DNA double-strand break immobilization

Hello,
In the following paper (PubMed=31548606) the authors show a biological process for IFFO1 (UniProt: Q0D2I5) of "DNA double-strand break immobilization leading to a decrease in DNA translocation".
I would like to know if a term equivalent to “DNA double-strand break immobilization” already exists, otherwise if it could be created?
Thank you,
Lucille

Is this the term you need?
GO:1990683   DNA double-strand break attachment to nuclear envelope
(immobilization is the 'outcome' of the process)

I will use that GO:1990683 term, it is close enough to the function i need.
Thank you,
Lucille


Redirect home on unauthorized

Description
Normally the application handles 403s before this and redirects home. This is a failsafe for edge cases that would leave the user on a grey 403 page that is just builtin to Play. To be consistent with the rest of the app we redirect home.
This only known way to hit this is to have an active session, change the application secret, and try using your existing session.
Checklist
General
Read the full guidelines for PRs here

[x] Added the correct label: < feature | enhancement | bug | under-development | dependencies | infrastructure | ignore-for-release | database >
[x] Assigned to a specific person, civiform/developers, or a more specific round-robin list
[x] Performed manual testing (Chrome and Firefox if it includes front-end changes)

Instructions for manual testing
In Dev Mode

bin/run-dev
start app as guest, fill out a page or two of data
change secret
reload
wait for app to be fully loaded
click save and next on open page
get the 403 error, along with the warn/error in the console log

In Prod Mode

runProd
start app as guest, fill out a page or two of data
stop app
change secret
runProd
wait for app to be fully loaded
click save and next on open page
get the 403 error, along with the warn/error in the console log

Issue(s) this completes
Fixes #7279

For my edification, can you elaborate on "to be consistent with the rest of the app"? Given that this 403 case is generally unexpected, it seems like we're losing something by redirecting to home with no indication of what went wrong. In real life I get really annoyed when a website does that. :) Would it make sense / be possible to add a toast or something on the homepage even just to say "something unexpected went wrong, sorry!"?

Agreed it's annoying.
There are other parts of the application that already just redirect home. I don't like it, but I also want to be consistent with the way it's done throughout the app. There's a long thread on slack you can peruse.
Retrofitting the behavior to an error message is outside the scope of what I need this for and have time for right now. The change in behavior probably make more sense to get connected with the Northstar upgrades anyway.
Also, based on the data I have from Seattle prod unhandled 403s never get logged because we typically have them handled. It's an edge case with changing the application secret value which is how I'm triggering it.

Thanks for the context! Of course I saw the beginning of that thread in Slack but not the rest of it.


AudioObject property needs switch on develop due to API changes

Main is only available on macOS 12+:

I see this, which is super gross:
static bool deviceHasOutputStreams(AudioObjectID deviceID)
{
    AudioObjectPropertyAddress address = {
        kAudioDevicePropertyStreamConfiguration,
        kAudioDevicePropertyScopeOutput,
#if HAVE(AUDIO_OBJECT_PROPERTY_ELEMENT_MAIN)
        kAudioObjectPropertyElementMain
#else
        ALLOW_DEPRECATED_DECLARATIONS_BEGIN
        kAudioObjectPropertyElementMaster
        ALLOW_DEPRECATED_DECLARATIONS_END
#endif
    };
    return deviceHasStreams(deviceID, address);
}

Big Sur:

@ryanfrancesconi Can you check https://github.com/rnine/SimplyCoreAudio/commit/719f01e5fb675bfda866f961672bf2aacd21f923 on your end?

Sorry for the delay. Didn't see your update. I think this change is working - looks clever, but I can't test overall as the framework still doesn't compile: (macOS 11.4)

I think the same concept needs to be applied to all macOS 12 deprecations. At least for me as a macOS (not iOS) developer it's going to be along time before I would ever enforce compatibility with 12. I'd guess 5 years at least.

Good warning to not update to XCode 13 I guess....

@ryanfrancesconi Yeah. Good point!
Actually, would you be interested in becoming a project collaborator? I am afraid I don't have much time to commit to this project right now, so your help would be truly appreciated!

sure, I'd be happy to help. I didn't want to step on your toes with PRs but this project is quite important to what I'm doing!

Excellent! Invite sent!


strange error when using cuda: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN

I'm encountering an issue when trying to use the CUDA provider with sherpa-rs on Windows.
I use the latest versions of CUDA, ONNX, and other dependencies. On my machine, CUDA works fine with my other Rust ONNX Runtime projects  So I am sure it is installed and working correctly.
When I try to utilize the models with cuda, I get the following error, with CPU, no problem at all. Even when I type coreml, it just says "CoreML is for Apple only. Fallback to cpu!" and it keeps working.

let mut recognizer: WhisperRecognizer = WhisperRecognizer::new(
            "tiny-decoder.onnx".into(),
            "tiny-encoder.onnx".into(),
            "tiny-tokens.txt".into(),
            "sv".into(),
            Some(false),
            Some("cuda".to_string()),
            None,
            None,
        );

sherpa-rs = { version = "0.1.7", features = ["cuda"] }
Using CUDA provider fatal runtime error: Rust cannot catch foreign exceptions error: process didn't exit successfully:target\debug\test_vad.exe(exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)
I also did cargo clean, and cargo run again but its the same.  I found this discussion but its not clear to detect the source error:
https://users.rust-lang.org/t/status-stack-buffer-overrun/34873/4

Thanks for report.
I suspect that it's related to linking issue / missing DLLs. I released new version.
Can you try again?
Set the version to
sherpa-rs = "=0.1.8-beta.0"

unfortunately its the same.
sherpa-rs = { version = "=0.1.8-beta.0", features = ["cuda"] }
Note that the CPU version with this feature flag does not work either:
    let extractor_config = speaker_id::ExtractorConfig::new(
        "3dspeaker_speech_eres2net_sv_en_voxceleb_16k.onnx".into(),
        None,
        None,
        true,
    );

but if I use
 Some("coreml".to_string()),
at least it works on cpu. "sion.cc:GetSessionOptionsImpl:198 CoreML is for Apple only. Fallback to cpu!"
To able to run in CPU properly I should simply use sherpa-rs = { version = "=0.1.8-beta.0"] } (without cuda flag)
I don't know, maybe it's my machine. Window Updates might have broken something. But I would like to say that my other onnx projects are working correctly with Cuda (rust & python).
Debug:
est_vad\target\debug\build\sherpa-rs-sys-398016b229ca6795\out\sherpa-onnx\sherpa-onnx\csrc\speaker-embedding-extractor-impl.cc:GetModelType:38 language=English
framework=3d-speaker
feature_normalize_type=global-mean
comment=This model is from iic/speech_eres2net_sv_en_voxceleb_16k
url=https://www.modelscope.cn/models/iic/speech_eres2net_sv_en_voxceleb_16k/summary
sample_rate=16000
output_dim=192
normalize_samples=1

fatal runtime error: Rust cannot catch foreign exceptions
error: process didn't exit successfully: `target\debug\test_vad.exe` (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)

Looks like there's upstream issue with sherpa-onnx. I crash for me too with the following:
Build it with:
Note: Add -DSHERPA_ONNX_ENABLE_GPU=ON to enable cuda.
git clone https://github.com/k2-fsa/sherpa-onnx
cd sherpa-onnx
cmake -B build . -DCMAKE_BUILD_TYPE=Release -DSHERPA_ONNX_ENABLE_BINARY=ON
cmake --build build -j8

Prepare Whisper
winget install -e --id JernejSimoncic.Wget
winget install -e --id GnuWin32.Tar
wget.exe https://github.com/k2-fsa/sherpa-onnx/releases/download/asr-models/sherpa-onnx-whisper-tiny.tar.bz2
tar.exe xvf sherpa-onnx-whisper-tiny.tar.bz2

Run with
.\build\bin\Debug\whisper-c-api.exe

If it works, try to change the provider from cpu to cuda in the file whisper-c-api.c:
cmake --build build -j8

Then run again.

By the way, I think you should add CI tests to this project.
The current CI only ensures the project can be built without issues. It would be great if you also test that it runs without any problems.

@altunenes
I missed build flag in the previous comments and that cause the issue.
Please try to build it with the following commands (Don't forget to include the flag to enable cuda)
Build it with:
Note: Add -DSHERPA_ONNX_ENABLE_GPU=ON to enable cuda.
git clone https://github.com/k2-fsa/sherpa-onnx
cd sherpa-onnx
cmake -B build . -DCMAKE_BUILD_TYPE=Release -DSHERPA_ONNX_ENABLE_BINARY=ON
cmake --build build --config Release -j8

Prepare Whisper
winget install -e --id JernejSimoncic.Wget
winget install -e --id GnuWin32.Tar
wget.exe https://github.com/k2-fsa/sherpa-onnx/releases/download/asr-models/sherpa-onnx-whisper-tiny.tar.bz2
tar.exe xvf sherpa-onnx-whisper-tiny.tar.bz2

Run with
.\build\bin\Debug\whisper-c-api.exe

If it works, try to change the provider from cpu to cuda in the file whisper-c-api.c:
cmake --build build --config Release -j8

Then run again.

By the way, I think you should add CI tests to this project.
The current CI only ensures the project can be built without issues. It would be great if you also test that it runs without any problems.

I added CI tests.
Now we can see clearly the issue reported here.
https://github.com/thewh1teagle/sherpa-rs/actions/runs/10242004087/job/28331095556
DirectML works (shared lib)
By the way there's another issue with cuda on ubuntu
https://github.com/thewh1teagle/sherpa-rs/actions/runs/10242004087/job/28331095754

》 Now we can see clearly the issue reported here.
There are NO GPUs on the CI machines.
Are you able to reproduce locally on your Windows NVIDIA GPU machine?
Please also try cuda 11.8.
(It was cuda 11.8 in the onnxruntime doc. It is somehow changed to 12.x someday for some unknown reason.)

》 Now we can see clearly the issue reported here.
There are NO GPUs on the CI machines.
Are you able to reproduce locally on your Windows NVIDIA GPU machine?
Please also try cuda 11.8.
(It was cuda 11.8 in the onnxruntime doc. It is somehow changed to 12.x someday for some unknown reason.)

just to make sure, sherpa-onnx supports Cuda 12.x, with the latest Onnx right? My windows machine really slow nowadays and my tests with different envs settings takes really time, sorry for the delays :(

We only support onnxruntime 1.17.1

Oh, I missed that important detail! I'm so sorry! :-(
so this is the source of the error then. Thank you so much. I reproduced this error on the latest CUDA and ort.
I close the issue for now (feel free to open it again if you have a comment on any other detail).

does it work for onnxruntime 1.17.1?

As I said, for now it is not possible to test this on my current work machine. My current work machine is really slow on these days and it is quite difficult for me to switch to a different environment. But hopefully, I will test this soon.


Add target: ES2021

Fixes #41238
We may never have year 2021 but TypeScript will.

you committed so much code...hard work!

General feedback: Could we stop putting esnext to file paths so that we can stop renaming it whenever new standard happens? It causes unnecessary and boring changes 😬

@uniqueiniquity the internal TypeScript / TypeScript-VS repos will need to be updated to match.

@saschanaz My bad. Got it!😂

@minestarks @uniqueiniquity This is merged now, so the internal repos need to update.

I would note that ES2021 is still not official, per the ECMA. that won't happen for at least another 30 days.


[Website] Add "unique challenges of cloud native telco" section to landing page

Describe the update:

update landing page - https://lfnetworking.org/cloud-native-networking/

Describe why update is needed

the 1st version of the landing page was released in Nov 2023
Additional request from the LFN TAC on Feb 21, 2024 to incorporate additional text on the landing page that will:

Provides a short explanation for the unique challenges of telco networking and the benefits that taking a cloud native approach can bring.   The goal is to add brief text to the landing page that further motivates/explains why the CNTI is of value.

Tasks

[x] Create draft doc > https://docs.google.com/document/d/1RcEfH4WGvFhUdpfU68RKV7icoVDTvLvKsltkxqbCz8Y/edit
[ ] Draft new landing page content
[ ] Share draft with LFN staff and request updates
[ ] QA published changes
[ ] Close issue

@Smitholi67 here is the existing landing page draft if you want to use it https://docs.google.com/document/d/1lF3rR3z39B0troqducYxd0vMT8WE9hvFWC3OCphc760/edit#heading=h.1i5sxjm9swy1


[Bug]: Last word in line has off-by-one with operators

Bug Description
// no trailing whitespace in the line below
nvim-spider is great
               ^

Doing e.g. ce will leave you with
nvim-spider is t
               ^

It works fine when there is a trailing whitespace
neovim version
v0.9.0-dev-1312+g908494889

Make sure you have done the following

[X] I have updated to the latest version of the plugin.

oh boy, vim indeed has some weird quirks when it comes to indeces. Fixed

Indeed. Interesting how one never notices these things until they change :grin: thanks a lot for the quick fix!


unused: init at 0.1.0

Motivation for this change
Add the unused tool.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Cool. I generally rebase and force-push, because I don't think nixos squashes PR commits in its repos. Hopefully someone with merge rights can merge it in after that.

@joshuaclayton you might be interested in this.

@lrworth ah, neat! I just pushed a new commit in as of yesterday to better support non-UTF-8 tags files (this was an issue in the Haskell version as well: https://github.com/joshuaclayton/unused/issues/72).
I'm going to cut a 0.2 release in the next few minutes (in case it's not too much trouble to include that rather than 0.1) since I'm guessing it may be a sticking point for folks.

Great! Let's wait until 0.2 then.

@lrworth on second thought, I'm still seeing issues with mimalloc compiling on ubuntu correctly in GH actions: https://github.com/unused-code/unused/runs/1574360688?check_suite_focus=true
Until I work that out, I think we'll be on pause for a 0.2 release (mimalloc cuts execution time by 30%+ here, so I don't want to out-right remove it without investigating further).

Updated to 0.2.0, which also seems to have resolved the yaml problem and let us use rustPackages.
I'll bump promptly when and if https://github.com/unused-code/unused/issues/25 is resolved.

Still builds and runs on NixOS with the new version

It is recommended by many that the changes made to maintainer-list.nix be put in a seperated commit, with the commit message "maintainer-list: add lrworth"

Result of nixpkgs-review pr 107077 run on x86_64-darwin 1

1 package built:

unused

Closed as there is no maintainer for this package.

@SuperSandro2000 those fields are optional on purpose, and we don't need to force contributors to fill them in if they don't want to. @lrworth can contribute this package as a maintainer, without filling them all in if they would like to.

Thanks @grahamc. Let's try this again then?

@SuperSandro2000 those fields are optional on purpose, and we don't need to force contributors to fill them in if they don't want to. @lrworth can contribute this package as a maintainer, without filling them all in if they would like to.

Sorry about this. I just wanted to convince the author to add this informations. The information is tied to his commit anyway.

@lrworth @grahamc @endgame @SuperSandro2000 thanks for helping get this merged!

@lrworth I haven't used Nix yet (still on MacOS Homebrew) – if you have a few minutes, I'd very much appreciate a PR to unused highlighting how to install so others can take advantage of this as well.

https://github.com/unused-code/unused/pull/26


no data in serial monitor using an Arduino on Apple M3 / Sonoma

System

apple M3 / Sonoma

Using the serial port monitor and an arduino no data is visible to the serial monitor. No problems with uploading code to Arduino and receiving data from Arduino using the serial port (Matlab, python, C, all works). However the serial monitor does not work
Using another MacBook, Intel, with Ventura and the same Visual Code configuration works well.
Also serial monitors from other extensions works. Why does this standard not work ?
Kind regards - jan

@JanMenssen, I'm curious if this is an external issue on our serialport dependency, could you use the command-line package to see if this is an issue with it? https://serialport.io/docs/7.x.x/guide-cli/#serialport-terminal

@gcampbell-msft : Thank you for you comment and your suggestion
I am not happy with installing non-necessary programs on my computer. In my opinion every installed program may be a risk for malfunctioning on other programs (I am a software engineer for more than 30 years). Also the command npm which seems needed to install this serial port monitor is not recognized on my Mac ?
So I you can give me good reasons why you want installing the serial monitor you suggest, I will do install it.
But as I mentioned earlier, serial communication with an Arduino works in a program I wrote in Matlab, it works in a program I wrote In Python and it works in a program I wrote in C. Also with another serial monitor in VS code (serial terminal from awsxxf) no problems.
And strange, on an old MacBook Pro 206 with Ventura no problems arise with VS code and the micosoft serial monitor. ??
Kind regards and again thank you for you suggestion

Sorry, intention was not to close it

I got a permission  error installing the serial port program  see below. Maybe this is related to the serial port program ??
jan@Jans-MacBook-Pro ~ % npm install -g @serialport/terminal
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /usr/local/lib/node_modules/@serialport
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/@serialport'
npm ERR!  [Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/@serialport'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'mkdir',
npm ERR!   path: '/usr/local/lib/node_modules/@serialport'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR! A complete log of this run can be found in: /Users/jan/.npm/_logs/2024-03-21T21_38_08_793Z-debug-0.log
jan@Jans-MacBook-Pro ~ %

If I am using the serial monitor I am able to send bytes to the arduino, so it seems only the receiving part is not working

@JanMenssen Thank you for being willing to try that out. I, like you, find it interesting that older version of Mac don't seem to have these issues. The intent of having you download that was to see if the issue is stemming from the serialport dependency.
I haven't found anything that seems like this specific issue, but I wonder if it has something to do with an FDTI driver? https://github.com/serialport/node-serialport/issues/83
Without your specific version of Mac on hand, it's difficult to test this. Thank you for your patience.


Bump url-parse from 1.5.1 to 1.5.7

Bumps url-parse from 1.5.1 to 1.5.7.

Release notes
Commits

updated-dependencies:

dependency-name: url-parse
dependency-type: indirect
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

Close


Adapt voice hints and exporting to changes in BRouter 1.7.X

Patches contained in this series (see commit messages for details), all relating to adapting to changes in BRouter 1.7.0:

Add BL and TLU to VoiceHints and adapt indexing to BRouter 1.7.0
Emit console warning when using an unsupported BRouter version
Document new export formats added in BRouter 1.7.0 and fix export error
Prevent Gpsies-style export from throwing for undefined symbols

Further changes would be needed (e.g. new Locus format, straight line voice hints, 180° u-turn voice hints at cul-de-sac-style vias, height calculation buffers etc.), but that's all there is for now.
Regarding the new console warning if BRouter is too old, I'm open to better suggestions, of course. I haven't added this new requirement to the CHANGELOG yet, but it should probably be mentioned there and in the release notes once a new release is tagged. Not sure how increasing the required BRouter version was handled in the past.

Thanks for the PR! I'm fine with merging that as is.

Regarding the new console warning if BRouter is too old, I'm open to better suggestions, of course.

Fine by me.

Not sure how increasing the required BRouter version was handled in the past.

Not at all, other than providing a working standalone bundle with each release. On my to-do list is to include brouter as a dev or peer dependency, which initially wasn't possible because of the GPL license.

Thanks!


remove obsolete login. add some logs

@m-terra thank you very much for the update.
It wil be part of the next release.

@bakito thanks! lmk when it's out


WIP: Adds devices existence checks before using

Check devices if they exist before actually using them.
This allows an add-on developer to specify devices that might not be available on all platforms.
For example: We could add the Raspberry camera device to the SSH add-on, without breaking it on other platforms.
Fixes: #656
Ref: #184

That don't work because, the supervisor run without any privileged.
You need go the way with hardware.py and /sys/ or /prog/

🤦♂
Will revisit it. Meanwhile, I'll add the 🚧 WIP tag.

Small input, maybe we can use the machine tag. Like we do on audio to resolve the name of input. I think we need also add a functionality that you can add a config option like machine: [rpi] and this can only be installed on a rpi platform.

I'm closing this PR. It has to be rewritten anyway and I'm short on time as well.


Rename hub-templates.md to hub-helm-charts.md

Whoops! I forgot this in #953

I will merge this without review as it only affects our docs


dio: Implement embedded-hal OutputPin

Someone might want to trigger a CI rerun for this - transient network issues.


Removed the Shuffle.h

Not needed anymore.

Coverage remained the same at 99.846% when pulling 734471c19817133e301f426b98da784ad991b039 on basvodde:master into 983cb38a7764b222bacbcd5168bde775b032c156 on cpputest:master.


Add dmp() function for only dumping arguments, without ending the script

This is my first PR so tell me if I did something wrong.
I almost always recreate this function for every new Laravel project and I thought it may be a part of Laravel core.

Thanks, but this function already exists, provided by symfony.

Do you mean dump($var)? Thanks, I didn't know that


Replace finalizer() usage in Recycler.WeakOrderQueue with ObjectClean…

…er usage.
Motivation:
We recently introduced ObjectCleaner which can be used to ensure some cleanup action is done once an object becomes weakable reachable. We should use this in Recycler.WeakOrderQueue to reduce the overhead of using a finalizer() (which will cause the GC to process it two times).
Modifications:
Replace finalizer() usage with ObjectCleaner
Result:
Fixes [#7343]

also @johnou

General question about ObjectCleaner. IIUC we are trading a finalize method for each object vs each "register" call will introduce:
- WeakReference

Runnable

then in general for ObjectCleaner some static state:

concurrent Set,
ReferenceQueue
background thread(s)
a few atomic operations

It is not clear to me that the ObjectCleaner will provide an overall win here (memory, GC time, throughput, etc...). How can we quantify the differences before and after?

@Scottmitch need to also consider that finalize is being deprecated.

@Scottmitch I think one of the main reasons for this changes are what @johnou said... finalize is deprecated now and we should try to avoid using it if we can.


remove apiVersion from client constructor

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.AI.AnomalyDetector


ReturnURL is unexpectedly called on android

Describe the bug
When testing a failed payment flow in the React Native SDK on Android the returnURL is requested. However the documentation states that this is not the case.
To Reproduce
Steps to reproduce the behavior:

Start an iDeal payment
Choose Test Issuer Cancelled
Complete the cancelled payment
App is called back on the returnURL

Expected behavior
I expect the SDK to handle this (as mentioned in the documentation). Or for the documentation to more clearly indicate how to handle this on Android. ( https://docs.adyen.com/online-payments/build-your-integration/?platform=Cross-platform&integration=React+Native+Drop-in&version=1.0.0#make-a-payment )
I noticed the android documentation shows this: Get this URL from Drop-in in the RedirectComponent.getReturnUrl(context). However this function is not available in React Native as far as I know.
As a workaround I have now implemented this for generating the redirectUrl:
const getRedirectURL = () => {
   if (Platform.OS === "android") {
     return `adyencheckout://${DeviceInfo.getBundleId()}`;
   }
   return Config.APP_DEEPLINK;
 };

Screenshots

Hey @stefkampen

I noticed the android documentation shows this: Get this URL from Drop-in in the RedirectComponent.getReturnUrl(context). However this function is not available in React Native as far as I know.

On Android React Native this is done by SDK - property returnURL is populated by AdyenCheckout (as you can see on a screenshot.)
All you need to do - set returnURL value to Configuration then send it to Adyen API; on iOS it will use your value, on Android - ignore it and assign new value generated by SDK.

I get this for the initialisation of the AdyenCheckout. But how would you handle this for the 3rd step in the documentation (calling the payments api)? Because a returnUrl is needed there too and it can't come from the SDK because you need to provide it yourself to the API call.

Because a returnUrl is needed there too and it can't (magically) come from the SDK because you need to provide it yourself to the API call.

Good news - it is "magically" come from the SDK  :)
In example:
<AdyenCheckout
          paymentMethods={paymentMethods}
          config={{
             ...
             returnUrl: 'my-app://adyen', // This will be used only on iOS
             ...
          }}
          onSubmit={(data, component) => {
             // data.returnUrl here contains passed-throught value for iOS or `adyencheckout://${DeviceInfo.getBundleId()}` for Android
             const result = await ApiClient.payments(data, configuration);
            // do the rest
          }}
          ...
          >
          ...
        </AdyenCheckout>

onSubmit callback will have

Thanks. Due to our backend team having strict rules about the backend API I have to restructure the incoming data from the onSubmit before sending it to our backends payments endpoint. And since it's not in the types of the interface I did not expect it over there.
As a suggestion is it possible to add it to the type of the PaymentMethodData?

And since it's not in the types of the interface I did not expect it over there.

This is a good point!
Thanks for pointing it out @stefkampen 💚

Release on 1.2.0


Do Test Cases need back to top anchor links?

Test Cases on the drupal site have a "back to top" anchor link after each section in the test case.
How important is it that we include that in the first release?

In the new framework the Test Case content will be in a pdf so shouldn't need this


Feature/new uast serialization

Instead of serialize UASTs as a JSON array of marshaled UAST nodes encoded as base64, now the list of nodes are serialized as a sequence of marshaled nodes preceded by their lengths, it is:
BigEndianInt32(len(marhsal(node))+marshal(node)+
BigEndianInt32(len(marhsal(node))+marshal(node)+
BigEndianInt32(len(marhsal(node))+marshal(node)+
...

The node size is being encoded as an int32 in big endian to make it directly readable from the JVM just in case we will need manage it from spark. If you think there are better options just let me know and I'll change it.
Also, there is a new flag in the cli --alt-uast-serialization and an environment variable GITBASE_UAST_SERIALIZATION to choose if use this mode or the old one. This way, we don't brake compatibility for the moment.

I think given this is a v0 we could actually break compatibility and just enable this mode. WDYT @ajnavarro?

@erizocosmico yep, the idea is to use this new format as default, but provide a way to make it work with dependant applications providing the flag (the flag will be removed in next versions).

Pinging @bzz @carlosms to make them aware of that change (anyways, on new release notes we will add a paragraph explaining this breaking change).

Thank you for kind notice @ajnavarro!  @carlosms thank you for taking care of it


s3 complete_multipart_upload errors out

works on 2.1.0, fails on 2.2.0. installed using poetry, but I don't think makes any difference.  A minimum reproducible example would be very helpful, as none of our tests/use cases picked this bug up.

closing this. I was not using moto properly, and was circumventing some logic ✌

Happy to hear that it waai our fault. 🙂
Are you able to share some details on how this error occurred? Even if the logic was wrong, Moto still shouldn't throw any AttributeError

sure. Instead of simulating uploading parts by calling upload_part, I was explicitly creating a FakeMultipart upload manually and adding it to the moto backends. the problem is that with the new version, I would need to add an additional storage property to that object. I changed testing approach so that I actually call upload_part in my tests

Ah, gotcha - that makes sense. Thanks for the explanation!


Bug Report: Animation of notes being played does not play when using a xbox controller.

If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below.
Windows (x86_64)
What version of the game are you using? Look in the bottom left corner of the main menu.
1.7
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.

Have any version later than 1.6.0
Play any song with a xbox controller

Please describe your issue. Provide extensive detail and images if possible.
https://user-images.githubusercontent.com/89805628/131391110-7087a349-8b01-41b7-8d39-3192e9a463ec.mp4

you are now the com player.

You may  bave activated botplay on previous versions of KE. Try going ti Options > Misc and see the botplay


FIX: Renamed all $apiToken variable and ApiToken class with $apiKey a…

…nd ApiKey respectively
FIX for: https://github.com/openai-php/client/issues/23

Thank you. But this issue is already addressed: https://github.com/openai-php/client/pull/25.

Okay, Will contribute in future. :)


Upgrade dependencies

Direct:
golang.org/x/exp v0.0.0-20220722155223-a9213eeb770e
golang.org/x/net v0.0.0-20220728211354-c7608f3a8462
golang.org/x/sync v0.0.0-20220722155255-886fb9371eb4
Indirect:
golang.org/x/crypto v0.0.0-20220722155217-630584e8d5aa
golang.org/x/sys v0.0.0-20220731174439-a90be440212d

Codecov Report

Merging #373 (85b14bd) into master (e59fa91) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #373   +/-   ##
=======================================
  Coverage   70.05%   70.06%
=======================================
  Files          68       68
  Lines        5761     5746   -15
=======================================
- Hits         4036     4026   -10
+ Misses       1317     1316    -1
+ Partials      408      404    -4

Impacted Files
Coverage Δ

udp/client/responsewriter.go
61.29% <0.00%> (-1.68%)
:arrow_down:

net/conn.go
84.37% <0.00%> (-1.57%)
:arrow_down:

tcp/clientobserve.go
65.00% <0.00%> (-1.39%)
:arrow_down:

udp/client/clientobserve.go
68.93% <0.00%> (+1.69%)
:arrow_up:

tcp/options.go
43.65% <0.00%> (+3.82%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us.


Linting errors when bringing in components:  error  '$$Events' is defined but never used  @typescript-eslint/no-unused-vars

Current Behavior
Lots of the current components have out of the box linting errors with eslint.  https://github.com/exceptionless/Exceptionless/actions/runs/7032476394/job/19136290542
Expected Behavior
There should be no linting errors with default eslint configuration.
Steps To Reproduce

Install a component
Run eslint .

Link to Reproduction / Stackblitz (reproduction template)
No response
More Information
Since components are source imported linting is important.

I feel like it would be easy to fix this in a pr, but the core fix would be to add eslint to the project if it's not already.

We're not messing with anyone's ESlint configuration as that's a slippery slope. See #449

Having the same issue. It just doesn't make sense to have the $$Events variable if is not used. This is happening for all the components as I can see. In consequence import type { InputEvents } from "." is unnecessary too.

Having the same issue. It just doesn't make sense to have the $$Events variable if is not used. This is happening for all the components as I can see. In consequence import type { InputEvents } from "." is unnecessary too.

It does make sense. That's how you get intellisense/types when using the events on the component from outside of it.
https://github.com/dummdidumm/rfcs/blob/ts-typedefs-within-svelte-components/text/ts-typing-props-slots-events.md

I got it. So, what's the solution for fix the lint warnings? I'm using lint-staged so I can't commit having those "issues". I don't want to suppress all unused-vars warning by setting it to false in the eslint config, because I want to get alerted if my code have unused vars.
Any workaround?

@diegoulloao https://gist.github.com/huntabyte/b73073a93a7a664f3cbad7c50376c9c9

I added this for now:
ignorePatterns: ['src/lib/components/ui']


String route params not matched for email

Hi,
We seem to have encountered a bug with the route system.
class MyClass < Grape::API
      EMAIL_OR_ID_REGEXP = %r{([A-Z0-9._%a-z\-]+(@|%40)(?:[A-Z0-9a-z\-]+\.)+[A-Za-z]{2,14})|(\d+)}

      desc "Returns a user"
      params do
        requires :user_identifier, type: String, allow_blank: false, desc: "ID or email"
      end
      get '/user/:user_identifier' do
         puts "GET method"
      end

      desc "Creates a user"
      params do
        requires :user_identifier, type: String, allow_blank: false, desc: "ID or email"
      end
      post '/user/:user_identifier', requirements: { user_identifier: EMAIL_OR_ID_REGEXP }  do
         puts "POST method"
      end

end

We try this with Swagger UI, which says that a command line equivalent would be :
curl -X GET --header 'Accept: application/json' 'http://<IP_ADDRESS>:9299/api/user/anything%40something.else
The thing is that we do not match the GET regex of the match? method of router.rb
Because of this, we continue and end up in the greedy_match? method. This one finds the POST endpoint, and /user/:user_identifier matches but not the "post", so it returns a 405 Method not allowed exception.
If we add the requirement (the same as the post endpoint), it succeeds, presumably because you add our regex to yours.
I believe the issue is due to our submitting that converts @ by %40, which is unsupported by grape. But it is a string nonetheless, no?
Thanks,
Simon

There's a lot going on in the regex. I suggest turning it into a minimal spec maybe next and we can try to help?


[MINOR][DOCS] Update CTAS with LOCATION behavior with Spark 3.2+

What changes were proposed in this pull request?
This PR aims to update CTAS with LOCATION behavior according to Spark 3.2+.
Why are the changes needed?
SPARK-28551 changed the behavior at Apache Spark 3.2.0.
https://github.com/apache/spark/blob/24b82dfd6cfb9a658af615446be5423695830dd9/sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala#L2306-L2313
Does this PR introduce any user-facing change?
No. This is a documentation fix.
How was this patch tested?
N/A
Was this patch authored or co-authored using generative AI tooling?
No.

Thank you, @beliefer !


Infinite loop on downloading with pixiv sketch yes v20210822

Prerequisites

[V] Did you read FAQ section in readme.md?
[V] Did you test with the latest releases or commit ?
[V] Did you search for existing issues in Issues?

Description
I'm using the master branch, after implementing this fix #1011 this happened
this one https://github.com/Nandaka/PixivUtil2/commit/cc547c6f29debf6ef27ddf04d9585b028d3403d5
Steps to Reproduce

download from list
pixiv sketch yes
downloading until found any pixiv sketch from certain user
the following output in the actual behavior repeats ad infinitum

Expected behavior: [What you expected to happen]
check if the file has been downloaded or not, download or move on to the next one
Actual behavior: [What actually happened]
Processing Artist Id: gaden
Getting page 1 from<EMAIL_ADDRESS>Processing from post #-10 to #0
Member Url: https://www.pixiv.net/ajax/user/1633/profile/all
Reading D:\Python\PixivUtil2\config.ini ...
Configuration loaded.

Versions
20210822

As far as I've noticed, this fix https://github.com/Nandaka/PixivUtil2/commit/e92b2a49d9618e5a41cfc04f3afc8f5c9e1e0975 fixed the issue, I'll keep you posted if i found an unwanted behavior during the run


Default to sub config file paths/svc connection for public + sovereign live tests

This doesn't cover the many files still using secret sub configs with custom principals, those will be migrated separately. This changes the defaults to use file-based sub configs and service connections everywhere else. It is intended to be merged after/alongside federated auth mode becoming the default.
Relies on https://github.com/Azure/azure-sdk-tools/pull/8680

API change check
API changes are not detected in this pull request.

/azp run js - search-documents - tests


Correct the documentation when using react-native-reanimated

Hey @r0b0t3d can you send send in another PR after updating RNMMKVJSIModulePackage file by adding the above changes but commented out like everything else is so anyone who copies it can find them there?


AWS SNS Topic and Lambda Function

We have a necessity to create an AWS SNS Topic that can be used to
communicate SNS notifications from the govuk-{environment}-artefact
buckets.

We also need a Lambda function to synchronize buckets between
environments.

The two points mentioned above has been covered via this commit.
Solo: @suthagarht

Test


Support using down arrows in IE9-11

Change onBlur to onFocusOut to support IE9-11.  onFocusOut isn't ideal as React onFocusOut doesn't bubble currently, however onBlur is not supported at all on IE9, 10 and 11.
Fixes #193

The downside to doing this is that now the React version fires lots of warnings. There doesn't seem to be a way to fix this currently; this issue has more relevant discussion: https://github.com/facebook/react/issues/3751

Published in v1.4.2!


TXT query on cloudflare.com returns empty answer

Hi,
I have a weird issue:
When I query cloudflare.com for TXT records I get an empty answer instead of the expected records.
The same query using dig and the same dns server returns the expected records.
The TXT query works for all domains I tested except cloudflare.com. I've also tried using different dns servers with no luck.
Am I doing something wrong on my end or is this just a weird bug?
How to reproduce
package main

import (
	"github.com/miekg/dns"
	"log"
)

func main()  {

	c := dns.Client{}
	m := dns.Msg{}
	m.SetQuestion("cloudflare.com.", dns.TypeTXT)
	r, _, err := c.Exchange(&m, "<IP_ADDRESS>:53")
	if err != nil {
		log.Fatal(err)
	}
	log.Print(r)

}

Ghe, I was mystified as well, but cloudflare sets Tc:
;; flags: qr tc rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

not putting anything in the answer is borderline RFC incompliant though...

/close

Ah, thanks for the response. Must have missed the truncate flag.


Default the live subcommand to showing annotations

As it stands the live subcommand in its default behaviour isn't massively useful. I did find the --annotate option, however initially I thought there was something wrong with my setup (camera or marker) when it wasn't finding the marker I was showing it.
I would also encourage having the CLI print out info about the markers it's seeing. Here's what I've got for that locally:
        if markers:
            print(f"Found {len(markers)} makers:")

            for marker in markers:
                print(f" #{marker.id}")
                print(f" {marker.pixel_corners=}")
                print(f" {marker.spherical=}")
                print(f" {marker.cartesian=}")
                print(f" {marker.orientation=}")
                print()

            print()
            print(" --- ")
            print()

I was originally going to impliment a feature to print the results to the terminal but my main concern was the quantity of data.

One option might be to only print the details for the first marker and then emit a "more markers' details not printed" message. Combining that with a --print-details=N flag (default N=1) would allow the user to opt to have more markers details printed if that's what they want. (N=0 would disable printing; negative values or maybe `N='all' prints an unlimited number)
Thoughts?

If your webcam is running at 30fps and there are a few markers that is a few hundred lines per second.

A way to limit the fps might be neat too -- for the case of debugging the orientation stuff, 2 fps is plenty.


Unable to create vhub connection when remote vnet is in different subscription

I have a Virtual WAN and associated Virtual Hub that span 2 subscriptions, e.g. Production and Non-Production subscriptions.  The Virtual Hub is hosted in the Production subscription.  I want to create VNET Connections to VNETs that are hosted in the Non-Production subscription.
I am following the current implementation of az network vhub connection create , documented at https://docs.microsoft.com/en-us/cli/azure/ext/virtual-wan/network/vhub/connection?view=azure-cli-latest.  According to the documentation, there is no way to specify "subscription".
Testing:
Test 1: az account set --subscription "Production"
I get an error message stating Remote Virtual Network 'foo' not found for hub VNET connection 'bar'
Test 1: az account set --subscription "Non-Production"
I get an error message stating The Resource 'Microsoft.Network/virtualHubs/foo-vhub' under resource group 'bar-rg' was not found

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

ID: 19fef5c5-b3a5-31af-ccab-580959df37bd
Version Independent ID: a9a8cb89-574f-9266-af7d-eb1c9cfcf275
Content: az network vhub connection
Content Source: latest/docs-ref-autogen/ext/virtual-wan/network/vhub/connection.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

add to S177

Does --remote-vnet work for your purpose?

@bq1756 any feedback?

close as inactive


SPARKC-383: cache all common CassandraRow data in a single CassandraR…

…owMetaData object
One CassandraRowMetaData per resultSet/Partition.
That reduce object creation time and memory footprint.
At this momement it is:

Java driver codec
Map comlumn names -> index for get by name methods
CqlColumnNames -> index

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success

retest this please

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success

Build against Scala 2.10 finished with success

Build against Scala 2.11 finished with success

I finished the review. Overall looks good. There are minor code style issues.

Build against Scala 2.10 finished with success

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success

Build against Scala 2.11 finished with success

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success

+1


Support COVERALLS_ENDPOINT for Enterprise usage

This is need for posting coverage to a Coveralls Enterprise instance.
More info here: https://enterprise.coveralls.io
Thank you!
Edit: added support for COVERALLS_PARALLEL
(https://coveralls.zendesk.com/hc/en-us/articles/203484329-Parallel-Build-Webhook)

Thanks @jtbandes -- I'm not sure why this Travis job is failing now:
https://travis-ci.org/eddyxu/cpp-coveralls/jobs/156086540#L156

Looks like probably a Python version problem: http://stackoverflow.com/questions/38957513/hi-i-just-installed-requests-with-pip-but-i-cant-import-it

2 months ago 😅
Probably the requests package has changed since then — maybe you can try updating this repo's requirements.txt to point to a specific (older) version and then it'll work.

I suspect this only broke recently: https://github.com/kennethreitz/requests/commit/7700ecae14930fd078e28e35425661d46778bfa9

Requests officially supports Python 2.6–2.7 & 3.3–3.5

😫
@eddyxu, how do you feel about dropping 3.2 from the build matrix?

@jtbandes @eddyxu all green! 🎉

@jtbandes  thanks a lot for working on this. I am totally fine of dropping python 3.2 :)

@nickmerwin @jtbandes  what about let us drop Python 3.2 follow the lead  of request?

@eddyxu ok sounds good -- I'll update the PR.

@nickmerwin awesome!

This LGTM. I look forward to installing it from pypi :)

Merged and release 0.3.12. Enjoy


How to improve html→text conversion

Hi,
in some parts I want to influence how e-mail plaintext version is generated.
I see config is hardcoded, so there are not many ways how to do it.
Possible features what could help:

custom config for html-to-text (global and in Vue template)
add <html-only> and <text-only> for use in Vue templates
custom formatter in Vue template - <table plaintext-format="dataTable" :plaintext-options"{ leadingLineBreaks: 1, trailingLineBreaks: 1 }>"

we just merged a new project rewrite, please do check the docs and the updated logic https://vuemail.net/

@Flowko I does not see how this is solved in new version. Could you link me there, please?


add Dockerfile

i wanted to run it as an aws lambda layer

Do you think it would be possible to have a simple Alpine Linux build and then have an amazonlinux as an optional later stage? I'm reluctant to add such a specific implementation in the generic Dockerfile - the default shouldn't be an AWS Lambda I think.

Yes sure
On Wed, 4 Sep 2019 at 18:04, Viktor Elofsson<EMAIL_ADDRESS>wrote:

Do you think it would be possible to have a simple Alpine Linux build and
then have an amazonlinux as an optional later stage? I'm reluctant to add
such a specific implementation in the generic Dockerfile - the default
shouldn't be an AWS Lambda I think.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/unidentifieddeveloper/blaze/pull/5?email_source=notifications&email_token=AAAUYWBZB3L7F2UQTYFMRDLQH7TB7A5CNFSM4ITSICCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD54IX7Q#issuecomment-527993854,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAUYWBLTCHYYNWA4EL2Z4LQH7TB7ANCNFSM4ITSICCA
.

--
%>>> "".join( [ {'':'@','^':'.'}.get(c,None) or chr(97+(ord(c)-83)%26) for
c in ",adym,)&uzq^zqf" ] )


[Feature] 是否支持InternLM-XComposer2-4KHD-7B的部署

Motivation
想问下有InternLM-XComposer2-4KHD-7B部署的计划吗？
Related resources
No response
Additional context
No response

好像不同的地方只有视觉部分，会和XComposer2 一起支持。

感谢

It is supported in PR #1458 and will be released in v0.4.0
May give it a try.