Pre-compiled portaudio dll (inc. ASIO) causes Python to crash in Windows 10

I've installed sounddevice on one Windows 10 machine and can get ASIO to work, which is great. However, when trying to replicate this on another Windows 10 machine the dll causes Python to crash. The only difference in Python is using versions 3.7.3 vs 3.7.6.
I've verified through sd._libname that the portaudio dll being used is C:\ProgramData\Anaconda3\Lib\site-packages\_sounddevice_data\portaudio-binaries\libportaudio64bit.dll. I can replace the dll with other non-ASIO supporting pre-compiled dlls and get sounddevice to run. However, attempting to run with either the dll from the repository, or from wheel versions 0.4.0 or 0.3.14 from https://www.lfd.uci.edu/~gohlke/pythonlibs/#sounddevice causes Python to crash.
So it would seem to be a compatibility issue with the dll and my OS? Could there be another reason? My alternative seems to be going down the route of compiling portaudio with ASIO myself, but I'm hesitant to go there!

I have no idea what's going wrong there ...
The DLL which is distributed together with the sounddevice module is cross-compiled on Linux, while I assume the Gohlke DLL is compiled on Windows. If both show the same error, I kinda have to assume that the problem is somewhere in the PortAudio library code.
You could of course try to compile the DLL on your own, it can't be that complicated, right?
You could also try an older version of the DLL (e.g. from https://github.com/spatialaudio/portaudio-binaries/tree/9f3d08e87b9b4c9a00893dbd7522f5213b3f1b2a).
If the problem persists, you should ask on the PortAudio mailing list: http://portaudio.com/contacts.html (sadly, the instructions seem to be missing currently).

Thanks for the reply and your help.
I tried the older DLL without success. It looks like I'll have to investigate the compiling myself option.

Thanks for the reply and your help.
I tried the older DLL without success. It looks like I'll have to investigate the compiling myself option.

It looks like I'll have to investigate the compiling myself option.

Please keep us updated here!

The mystery continues!
I have tried compiling a DLL on the machine in question (Visual Studio 2017) using the latest portaudio and ASIO downloads. I can succesfully compile using any combination of audio APIs, but the version including ASIO still fails to run (it compiles, it just doesn't work).
I have contacted the portaudio list to see if I can get anywhere.

Thanks for the update!
For reference: https://listserv.cuit.columbia.edu/scripts/wa.exe?A2=PORTAUDIO;f0b9ca30.2009C&FT=M&P=T&H=&S=b

Quick update...
Compling PortAudio with the debug printout option allowed me to see where the crash was happening. It was when it found a Jack Audio install, likely broken (it's Windows). Uninstalling Jack fixed the issue.
I don't know if it was the DLL, or a sounddevice call to it causing the crash, but either way it's working now!

It looks from a response on the PortAudio list (and in the link you posted above) that it is the JackRouter ASIO driver that was the issue.
A similar issue looks to have been reported here: https://github.com/jackaudio/jack2/issues/623. Installing the Jack build posted a few days ago further down this thread doesn't cause issues. I believe a new Jack Windows and Mac install is pending, so hopefully issues will be resolved with any new release.

Thanks for the information!


Fix rare usb enumeration issue

Sometimes USB enumeration fails like 1/15 times (with serial, ccid, and hid classes used).  I narrowed it down to this fix :)

What does it do? :rofl:

The more correct logic I believe is to inform usb-device there's control data to handle if either devcmdstat.read().setup() or intstat_r.ep0out() is set.
Before devcmdstat.read().setup() would get set while intstat_r.ep0out() does not, and usb-device wouldn't know to check for control data.


have handler for force ex.printstacktrace

would it not make sense to make the printstacktrace at https://github.com/remkop/picocli/blob/master/src/main/java/picocli/CommandLine.java#L1924 something that users can control ?
especially I would like to be able to do something that have access to the commands
void handleException(@Mixin mycmd, Exception e) {
    mycmd.info(e.getMessage());
    if (mycmd.verbose) {
		e.printStackTrace();
	} else if (e.getCause() != null) {
		mycmd.info("Run with --verbose for more details");
	}
}

for now if I just wrap a try/catch around the execute() call I always get the full stacktrace printed which just aren't nice and its tedious having to add try/catch in all command call points.

This facility exists: you can set a custom IExecutionExceptionHandler.
See section 9.8.2. “Business Logic Exceptions”:
https://picocli.info/#_handling_errors

The line you highlighted is what gets executed if the custom error handler itself throws an exception.

I could have sworn I saw it print ..well, that’s why I shouldn’t open bugs after midnight :)
...but how does one best figure out if the "verbose" option is set...would I need to look that up dynamically somehow in CommandSpec/Commandline ?

Sorry, I was unclear. The default handler actually simply rethrows the error, then the fallback handler (that you linked to) catches it and prints the stacktrace.
To figure out if verbosity, you can either get a reference to your application via CommandLine.getCommand(), or get the specified option value from the parse result via parseResult.matchedOptionValue(). For example:
// assume we have this option
// @Option(names = {"-v", "--verbose"}) boolean[] verbosity = new boolean[0];

public int handleExecutionException(Exception ex,
                                    CommandLine commandLine,
                                    ParseResult parseResult) {
    commandLine.getErr().println(ex.getMessage());

    MyApp app = commandLine.getCommand();
    System.out.printf("app.verbosity.length=%d%n", app.verbosity.length);
    if (app.verbosity.length >= 2) {
        ex.printStackTrace();
    }

    // alternatively, we can get the verbosity from the parse result:
    boolean[] verbosity = parseResult.matchedOptionValue("verbose", new boolean[0]);
    System.out.printf("parseResult.matchedOption(verbose).length=%d%n", verbosity.length);
    if (verbosity.length >= 1) {
        commandLine.usage(commandLine.getErr());
    }
    return commandLine.getCommandSpec().exitCodeOnExecutionException();
}

@maxandersen Did this answer your question?

yes, excellent @remkop ! thanks.


panic: page 87 already freed

I've been doing a bit of corruption testing under unexpected power off scenarios (using an external USB drive and disconnecting it midstream) and, unfortunately, I'm fairly consistently hitting unrecoverable database corruption issues due to things such as unreachable unfreed or already freed.  I understand write corruption in this scenario is expected, but the database shouldn't be left in an unrecoverable state.
EDIT: I should also note this is on Windows 7 using all default bolt options.
I have a 4KiB database that is corrupted from this scenario that I'll keep around to help debug.  To get started, I'm providing the following pertinent details:

A trace of the panic.  NOTE: The trace is from a vendored version of bolt, but there are no code modifications and it is synced through commit ee954308d64186f0fc9b7022b6178977848c17a3.
Output of the bolt pages command
Output of the bolt check command.  NOTE: This command hangs and never completes

goroutine 12 [running]:
github.com/btcsuite/bolt.(*freelist).free(0xc08202b680, 0xca2, 0x2af7000)
       .../bolt/freelist.go:118 +0x35c
github.com/btcsuite/bolt.(*node).spill(0xc0820e2380, 0x0, 0x0)
        .../bolt/node.go:349 +0x280
github.com/btcsuite/bolt.(*node).spill(0xc0820e2310, 0x0, 0x0)
        .../bolt/node.go:336 +0x134
github.com/btcsuite/bolt.(*node).spill(0xc0820e22a0, 0x0, 0x0)
        .../bolt/node.go:336 +0x134
github.com/btcsuite/bolt.(*Bucket).spill(0xc0820dc7c0, 0x0, 0x0)
        .../bolt/bucket.go:536 +0x1cb
github.com/btcsuite/bolt.(*Bucket).spill(0xc0820dc780, 0x0, 0x0)
        .../bolt/bucket.go:503 +0xac9
github.com/btcsuite/bolt.(*Bucket).spill(0xc0820e65c8, 0x0, 0x0)
        .../bolt/bucket.go:503 +0xac9
github.com/btcsuite/bolt.(*Tx).Commit(0xc0820e65b0, 0x0, 0x0)
        .../bolt/tx.go:150 +0x1f5
...

$ bolt pages test.db

ID       TYPE       ITEMS  OVRFLW
======== ========== ====== ======
0        meta       0
1        meta       0
2        leaf       14
3        leaf       19
4        leaf       19
5        leaf       17
6        leaf       17
7        leaf       27
8        leaf       22
9        leaf       17
10       leaf       17
11       leaf       15
12       leaf       19
13       leaf       26
14       leaf       14
15       leaf       17
16       leaf       25
17       leaf       17
18       leaf       16
19       leaf       22
20       leaf       17
21       leaf       15
22       leaf       27
23       leaf       22
24       leaf       16
25       leaf       16
26       leaf       24
27       leaf       24
28       leaf       27
29       leaf       23
30       leaf       23
31       leaf       18
32       leaf       26
33       leaf       16
34       leaf       22
35       leaf       16
36       leaf       25
37       leaf       19
38       leaf       23
39       leaf       14
40       leaf       25
41       leaf       28
42       leaf       16
43       leaf       16
44       leaf       16
45       leaf       20
46       leaf       18
47       leaf       26
48       leaf       18
49       leaf       24
50       leaf       28
51       leaf       23
52       leaf       21
53       leaf       18
54       leaf       24
55       leaf       20
56       leaf       27
57       leaf       18
58       leaf       18
59       leaf       23
60       leaf       28
61       leaf       26
62       leaf       17
63       leaf       16
64       leaf       26
65       leaf       19
66       leaf       15
67       leaf       14
68       leaf       17
69       leaf       18
70       leaf       27
71       leaf       21
72       leaf       23
73       leaf       16
74       leaf       19
75       leaf       23
76       leaf       19
77       leaf       21
78       leaf       17
79       leaf       24
80       leaf       25
81       leaf       16
82       leaf       27
83       leaf       15
84       leaf       21
85       leaf       22
86       leaf       23
87       freelist   6
88       leaf       16
89       leaf       15
90       leaf       22
91       leaf       19
92       leaf       14
93       leaf       18
94       leaf       19
95       leaf       18
96       leaf       21
97       leaf       23
98       leaf       19
99       leaf       25
100      leaf       19
101      leaf       17
102      leaf       22
103      leaf       16
104      leaf       25
105      leaf       20
106      leaf       17
107      leaf       22
108      leaf       15
109      leaf       16
110      leaf       21
111      leaf       15
112      leaf       14
113      leaf       27
114      leaf       17
115      leaf       15
116      leaf       21
117      leaf       26
118      leaf       26
119      leaf       22
120      leaf       20
121      leaf       16
122      leaf       25
123      leaf       15
124      leaf       18
125      leaf       18
126      leaf       16
127      leaf       28
128      leaf       18
129      leaf       17
130      leaf       19
131      leaf       25
132      leaf       26
133      leaf       24
134      leaf       18
135      leaf       26
136      leaf       20
137      leaf       18
138      leaf       23
139      leaf       26
140      leaf       15
141      leaf       17
142      leaf       24
143      leaf       16
144      leaf       16
145      leaf       22
146      leaf       15
147      leaf       18
148      leaf       26
149      leaf       14
150      leaf       14
151      leaf       14
152      leaf       15
153      leaf       15
154      leaf       17
155      leaf       27
156      leaf       22
157      branch     80
158      leaf       15
159      leaf       15
160      leaf       15
161      leaf       15
162      leaf       15
163      leaf       15
164      branch     42
165      branch     45
166      free
167      branch     4
168      free
169      leaf       2
170      leaf       1
171      free
172      free
173      free
174      free

$ bolt check test.db
page 87: reachable freed
page 105: multiple references
page 83: multiple references
page 87: multiple references
page 87: reachable freed
page 97: multiple references
page 97: multiple references
page 97: multiple references
page 157: multiple references
page 21: multiple references
page 20: multiple references
page 87: multiple references
page 87: reachable freed
page 27: multiple references
page 35: multiple references
page 129: multiple references
page 132: multiple references
page 156: multiple references
page 82: multiple references
page 80: multiple references
page 139: multiple references
page 60: multiple references
page 121: multiple references
page 153: multiple references
page 30: multiple references
page 7: multiple references
page 112: multiple references
page 9: multiple references
page 127: multiple references
page 118: multiple references
page 74: multiple references
page 106: multiple references
page 15: multiple references
page 78: multiple references
page 65: multiple references
page 39: multiple references
page 159: multiple references
page 63: multiple references
page 124: multiple references
page 107: multiple references
page 3: multiple references
page 16: multiple references
page 67: multiple references
page 163: multiple references
page 29: multiple references
page 92: multiple references
page 105: multiple references
page 105: multiple references
page 13: multiple references
page 85: multiple references
page 109: multiple references
page 137: multiple references
page 48: multiple references
page 138: multiple references
page 75: multiple references
page 28: multiple references
page 83: multiple references
page 55: multiple references
page 32: multiple references
page 34: multiple references
page 84: multiple references
page 51: multiple references
page 53: multiple references
page 126: multiple references
page 19: multiple references
page 23: multiple references
page 95: multiple references
page 96: multiple references
page 5: multiple references
page 37: multiple references
page 130: multiple references
page 149: multiple references
page 161: multiple references
page 72: multiple references
page 73: multiple references
page 116: multiple references
page 113: multiple references
page 18: multiple references
page 125: multiple references
page 146: multiple references
page 102: multiple references
page 134: multiple references
page 76: multiple references
page 114: multiple references
page 62: multiple references
page 66: multiple references
page 103: multiple references
page 97: multiple references
page 83: multiple references
page 87: multiple references
page 87: reachable freed
**Hangs here and never completes**

Thanks for doing corruption testing. Bolt definitely should not be corrupting due to power loss.
The huge number of corrupt pages suggests to me that the pages were written out of order in the transaction. Normally bolt writes all the data pages, fsyncs, writes the meta page, then fsyncs again. That way if a failure occurs during writes to the data pages then a meta page is never written which means that those data pages are effectively uncommitted.
I'll do some testing with a USB stick. Can you tell me what USB drive you're using? I don't think it should matter but it's good to narrow down the issue if possible. Also, I'll take a look at how Windows does file syncing to make sure it's correct in Bolt.
I'm about to go to sleep but I'll look at this first thing in the morning.

Also, can you send me the script you used during testing and any steps you performed during the test? e.g. how long did the test run before you pulled the USB?

Thanks for a quick response.
I'm using a (quite old) Kingston DataTraveler 1GB USB stick.  I don't have a script at the moment as it was discovered as a part of a larger project I'm working on (storing bitcoin blocks on the file system while using bolt to store the metadata for their locations, headers, transactions indexing, etc).
I will put something smaller together to help track this down as I know how important it is to have a targeted and reproducible test program for situations like this.

@davecgh I've been running bolt bench with the following parameters this morning against an Amazon Basics 16GB USB drive:
$ bolt bench --batch-size 1 --count 10000 --work --path /Volumes/USB16/bolt.db

It didn't take me long to hit corruption although the corruption is strange. My meta pages show the following:
// meta0
root:     24
freelist: 25
hwm:      26
txnid:    630

// meta1
root:     7
freelist: 10
hwm:      26
txnid:    629

But in the data file itself it shows nothing written to page 14 or higher. It's all just zeros filled in by truncate(). Since the previous transaction (meta1, txnid 629) had written it's high water mark up to page 26, there should be data in pages 15 through 26.
 I can't for the life of me get it disabled on my Mac because the mounting goes through  diskutil mount instead of the standard Unix mount.
It looks like there's a bunch of articles on Google about disabling it on Windows though. Can you try disabling write caching and see if you still have the issue?

@davecgh @benbjohnson
I am not sure if it is just a USB issue. I did some similar testing with read disk, I found no issues.
Can you reproduce the issue on aws disk? @benbjohnson

@benbjohnson I have been running with write caching disabled already.  The issue still periodically happens.  I was able to reproduce it with the bench tool as well (although I had to add the --path option for the bench sub-command as I don't see that on master).
$ git diff bench.go main.go
diff --git a/cmd/bolt/bench.go b/cmd/bolt/bench.go
index 91af960..1e51e76 100644
--- a/cmd/bolt/bench.go
+++ b/cmd/bolt/bench.go
@@ -32,7 +32,12 @@ func Bench(options *BenchOptions) {
        }

        // Find temporary location.
-       path := tempfile()
+       var path string
+       if options.Path == "" {
+               path = tempfile()
+       } else {
+               path = options.Path
+       }

        if options.Clean {
                defer os.Remove(path)
@@ -368,6 +373,7 @@ type BenchOptions struct {
        FillPercent   float64
        NoSync        bool
        Clean         bool
+       Path          string
 }

 // BenchResults represents the performance results of the benchmark.
diff --git a/cmd/bolt/main.go b/cmd/bolt/main.go
index 183d1f2..7e8e908 100644
--- a/cmd/bolt/main.go
+++ b/cmd/bolt/main.go
@@ -99,6 +99,7 @@ func NewApp() *cli.App {
                                &cli.Float64Flag{Name: "fill-percent", Value: bolt.DefaultFillPercent, Usage: "Fill percentage"},
                                &cli.BoolFlag{Name: "no-sync", Usage: "Skip fsync on every commit"},
                                &cli.BoolFlag{Name: "work", Usage: "Print the temp db and do not delete on exit"},
+                               &cli.StringFlag{Name: "path", Usage: "Specify the db path"},
                        },
                        Action: func(c *cli.Context) {
                                statsInterval, err := time.ParseDuration(c.String("stats-interval"))
@@ -121,6 +122,7 @@ func NewApp() *cli.App {
                                        FillPercent:   c.Float64("fill-percent"),
                                        NoSync:        c.Bool("no-sync"),
                                        Clean:         !c.Bool("work"),
+                                       Path:          c.String("path"),
                                })
                        },
                }}

I've also run into this stress testing.. but in my case I'm going against an SSD on OSX. What can I provide to help debug? I still have the db, but it is 2 gigs..

I've also run into this issue using SSD on Google Compute Engine instances. Bolt build from: https://github.com/boltdb/bolt/commit/033d4ec028192f38aef67ae47bd7b89f343145b5

Any progress on this?

I work with @mdmarek, we've hit this panic more often now.   Same stack trace as posted by the original poster.   In our case, we call tx.Commit() on a timed interval and we've only seen the panic for databases under heavy loads (large commits).

Also seeing this error frequently, but bolt check doesn't show any db corruption.

@jezell @epsniff @benbjohnson @nicpottier @gyuho I really think we should get this fixed. Can anyone provide a way to reproduce this? I would like to look into it.

@xiang90 I don't have a way to reproduce right now. I'm doing some refactoring and clean up on the test suite in order to get better, long running simulation testing. I think that'll help to reproduce these types of issues.

We're having major troubles with one of our production bolt databases continually dying with an error similar to @jezell

@newhook @jezell can you give me any details about your usage of bolt? DB size, key & value sizes, sequential writes or random writes, delete frequency, nested buckets, etc. Anything really. I'm trying to reproduce the issue but I'm not sure what's triggering it right now. It seems to happen to a few people frequently but other people it doesn't happen at all.

We had been using bolt for a git LFS implementation that was running on top of GlusterFS. We were able to mitigate the issue by migrating everything away from GlusterFS and moving bolt to run directly on top of mounted SSD storage. The git repos were not experiencing any corruption, but the bolt db databases used to track the LFS chunks were being corrupted regularly. I suspect it was related to some kind of concurrency or fsync type problem with Gluster and how Bolt writes to disk, since corruption hasn't occurred since we eliminated Gluster from the equation.

We're running on a RAID 5 3xSSD (INTEL SSDSC2BB800H4) cluster on Ubuntu 14 using LSI MegaRAID SAS 9271-4i. The application was running for a long time (like 4 months or so) until the corruption occurred.

@newhook Can you post your stack trace too?  I wonder if master would work better.

@benbjohnson Did we fix anything related recently?

panic: page 4 already freed

goroutine 818021 [running]:
github.com/boltdb/bolt.(*freelist).free(0xc2fd236c90, 0x5b0, 0x7ecaaacc4000)
        /source/.gopack/vendor/src/github.com/boltdb/bolt/freelist.go:117 +0x355
github.com/boltdb/bolt.(*node).spill(0xc48b570e70, 0x0, 0x0)
        /source/.gopack/vendor/src/github.com/boltdb/bolt/node.go:358 +0x279
github.com/boltdb/bolt.(*Bucket).spill(0xc55bcffdc0, 0x0, 0x0)
        /source/.gopack/vendor/src/github.com/boltdb/bolt/bucket.go:536 +0x1c4
github.com/boltdb/bolt.(*Bucket).spill(0xc55bcffd80, 0x0, 0x0)
        /source/.gopack/vendor/src/github.com/boltdb/bolt/bucket.go:503 +0xac2
github.com/boltdb/bolt.(*Bucket).spill(0xc6581b6b78, 0x0, 0x0)
        /source/.gopack/vendor/src/github.com/boltdb/bolt/bucket.go:503 +0xac2
github.com/boltdb/bolt.(*Tx).Commit(0xc6581b6b60, 0x0, 0x0)
        /source/.gopack/vendor/src/github.com/boltdb/bolt/tx.go:151 +0x1ee
github.com/boltdb/bolt.(*DB).Update(0xc27dc99380, 0xca1e051d68, 0x0, 0x0)
        /source/.gopack/vendor/src/github.com/boltdb/bolt/db.go:554 +0x169
customerio/index/index.(*DBMBolt).UpdateShard(0xc20800d5f0, 0x90da, 0xc5a9d20a50, 0x0, 0x0)
        /source/src/customerio/index/index/db_mbolt.go:448 +0xc9
customerio/index/index.func·057(0xc5000090da)
        /source/src/customerio/index/index/db_memory.go:359 +0x503
created by customerio/index/index.(*DBMemory).Flush
        /source/src/customerio/index/index/db_memory.go:367 +0x34a

@xiang90 There haven't been many code changes except the CoreOS ones recently. v1 is from Nov 2014. There have been a decent number of changes between v1 and v1.1 which released in Oct 2015.

@xiang90 Are you seeing this issue?

@benbjohnson No. But i would love to fix it if anyone can reliably reproduce it.

@benbjohnson I'm not sure exactly what version, but chances are it was whatever was current on Jul 8 11:18:40 2015.

@benbjohnson the version @newhook is using is commit 04a3e85793043e76d41164037d0d7f9d53eecae3 (work with him and just checked the vendored source)

@benbjohnson I wrote some code to reproduce this.   So far I've gotten to trigger twice after running for about 10mins.    Ill post a link in few mins.

It's not consistent how long it needs to run before it panics...  But usually within 10 mins, but a couple of times it ran longer..
https://gist.github.com/epsniff/f919369dccb4d5c13504

@epsniff Can you try to reproduce (confirm it can be reproduced) on a Cloud env? Or I can try to do it next week. Then it would be easier for us to look into the issue.

@xiang90 I was able to reproduce it on a Google Compute Engine(GCE) instance of type n1-standard-4 (4 vCPUs, 15 GB memory).   With a 200GB (standard persistent disk).   Go 1.5.2.   The version of BoltDB has commit 033d4ec028192f38aef67ae47bd7b89f343145b5 as the last commit.

@epsniff Awesome! That helps a ton. Also, what Go version are you running? And do you know what file system your /tmp directory is running on?

Go 1.5.2   And /tmp was a standard persistent disk, which is equivalent to AWS's EBS General Purpose (SSD)  disks I believe.

@epsniff Great! I will try and get back to you guys next week.

The disks were formatted with ext4...

@epsniff I'm able to get the panic on my MBP after about 20m. That gives me something to work with! :boom:

@benbjohnson, @xiang90 did either of you ever get a chance to work on this one?

@epsniff Sorry. I should have. I will try this week.

@epsniff I've spent time on it and made progress to reproduce it consistently but I haven't had time to resolve the issue yet.

I found the issue. Fixed with https://github.com/boltdb/bolt/pull/539.
@epsniff Thanks again for the program to reproduce. I refactored it a bit to continuously run in smaller chunks until it panics and then it saves the transaction log so it can be replayed:
https://gist.github.com/benbjohnson/9d2ebbc90b8b52f3fe25
I ran the script to reproduce for 24h without any issue. Previously it failed in 10-20m. If anyone else wants to test the changes, let me know.

That is awesome, thanks so much Ben!

@benbjohnson thank you for fixing it.

We are using boltdb vendored at commit 583e8937c61f1af6513608ccc75c97b6abdf4ff9 (v1.3.0).
Unfortunately, I just got this panic, running using gomobile on iPhone 6s, iOS 10.

In the test speed also encountered
I will try to be able to reproduce
"C:\Program Files (x86)\JetBrains\Gogland 163.10615.6\bin\runnerw.exe" C:/Go\bin\go.exe run G:/编程/golang/src/github.com/gamexg/go-test/数据库/boltdb/1.go
panic: page 178 already freed

goroutine 8846 [running]:
panic(0x4c8980, 0xc04235b890)
	C:/Go/src/runtime/panic.go:500 +0x1af
github.com/boltdb/bolt.(*freelist).free(0xc04203ff50, 0x2254, 0x2522000)
	G:/编程/golang/src/github.com/boltdb/bolt/freelist.go:117 +0x2c7
github.com/boltdb/bolt.(*node).spill(0xc04230a620, 0xc042462280, 0xc042462280)
	G:/编程/golang/src/github.com/boltdb/bolt/node.go:358 +0x1e3
github.com/boltdb/bolt.(*node).spill(0xc04230a5b0, 0xc0424d6630, 0xc0421119e0)
	G:/编程/golang/src/github.com/boltdb/bolt/node.go:345 +0xbe
github.com/boltdb/bolt.(*Bucket).spill(0xc0423bae80, 0xc0424d6500, 0xc042111c50)
	G:/编程/golang/src/github.com/boltdb/bolt/bucket.go:541 +0x442
github.com/boltdb/bolt.(*Bucket).spill(0xc04206d898, 0x219cf650, 0x566800)
	G:/编程/golang/src/github.com/boltdb/bolt/bucket.go:508 +0x942
github.com/boltdb/bolt.(*Tx).Commit(0xc04206d880, 0x0, 0x0)
	G:/编程/golang/src/github.com/boltdb/bolt/tx.go:163 +0x12c
github.com/boltdb/bolt.(*DB).Update(0xc042078000, 0xc04225bed0, 0x0, 0x0)
	G:/编程/golang/src/github.com/boltdb/bolt/db.go:602 +0x114
github.com/boltdb/bolt.(*batch).run(0xc042249300)
	G:/编程/golang/src/github.com/boltdb/bolt/db.go:722 +0x106
github.com/boltdb/bolt.(*batch).(github.com/boltdb/bolt.run)-fm()
	G:/编程/golang/src/github.com/boltdb/bolt/db.go:696 +0x31
sync.(*Once).Do(0xc042249310, 0xc04225bf58)
	C:/Go/src/sync/once.go:44 +0xe2
github.com/boltdb/bolt.(*batch).trigger(0xc042249300)
	G:/编程/golang/src/github.com/boltdb/bolt/db.go:696 +0x53
github.com/boltdb/bolt.(*batch).(github.com/boltdb/bolt.trigger)-fm()
	G:/编程/golang/src/github.com/boltdb/bolt/db.go:666 +0x31
created by time.goFunc
	C:/Go/src/time/sleep.go:154 +0x4b
exit status 2

windows 7 in esxi@nfs
package main

import (
	"log"

	"fmt"
	"time"

	"os"

	"github.com/boltdb/bolt"
)

func test1() {
	// Open the my.db data file in your current directory.
	// It will be created if it doesn't exist.
	os.Remove("test1.db")
	db, err := bolt.Open("test1.db", 0600, nil)
	if err != nil {
		log.Fatal(err)
	}
	defer db.Close()

	err = db.Update(func(tx *bolt.Tx) error {
		_, err := tx.CreateBucketIfNotExists([]byte("MyBucket"))
		return err
	})
	if err != nil {

	}

	sTime := time.Now()
	for i := 0; i < 10000; i++ {
		err = db.Update(func(tx *bolt.Tx) error {
			b := tx.Bucket([]byte("MyBucket"))
			err := b.Put([]byte(fmt.Sprint("key", i)), []byte("00000000000000000000"))
			return err
		})
	}
	//每次创建 Bucket 耗时： 33.2749032s
	fmt.Println("每次创建 Bucket 耗时：", time.Now().Sub(sTime))
}

func test2() {
	// Open the my.db data file in your current directory.
	// It will be created if it doesn't exist.
	os.Remove("test2.db")
	db, err := bolt.Open("test2.db", 0600, nil)
	if err != nil {
		log.Fatal(err)
	}
	defer db.Close()

	err = db.Update(func(tx *bolt.Tx) error {
		_, err := tx.CreateBucketIfNotExists([]byte("MyBucket"))
		return err
	})
	if err != nil {

	}

	sTime := time.Now()
	for i := 0; i < 10000; i++ {
		err = db.Batch(func(tx *bolt.Tx) error {
			b := tx.Bucket([]byte("MyBucket"))
			err := b.Put([]byte(fmt.Sprint("key", i)), []byte("00000000000000000000"))
			return err
		})
	}

	fmt.Println("批量操作：", time.Now().Sub(sTime))
}
func test3() {
	// Open the my.db data file in your current directory.
	// It will be created if it doesn't exist.
	os.Remove("test3.db")
	db, err := bolt.Open("test3.db", 0600, nil)
	if err != nil {
		log.Fatal(err)
	}
	defer db.Close()

	err = db.Update(func(tx *bolt.Tx) error {
		_, err := tx.CreateBucketIfNotExists([]byte("MyBucket"))
		return err
	})
	if err != nil {

	}

	sTime := time.Now()
	err = db.Update(func(tx *bolt.Tx) error {
		b := tx.Bucket([]byte("MyBucket"))
		for i := 0; i < 10000; i++ {
			err := b.Put([]byte(fmt.Sprint("key", i)), []byte("00000000000000000000"))
			if err != nil {
				return err
			}
		}
		return nil
	})
	//单次事务执行： 100.0057ms
	fmt.Println("单次事务执行：", time.Now().Sub(sTime))
}

func main() {
	//test1()
	test2()
}

The g-drive is a mapped NFS @ FreeNAS network drive. In the g-disk test will be panic. Panic does not appear on the local disk test.


[Branch-3.1] fix refresh mv error when iceberg table is empty

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[FE Incremental Coverage Report]
:disappointed: fail : 4 / 9 (44.44%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/MaterializedView.java
0
3
00.00%
[724, 725, 728]

:large_blue_circle:
com/starrocks/sql/common/SyncPartitionUtils.java
1
2
50.00%
[581]

:large_blue_circle:
com/starrocks/scheduler/PartitionBasedMvRefreshProcessor.java
3
4
75.00%
[1532]


Run with security after creating user?

Is there a way I can restart services using the auth flag?  Right now I'm able to start and create a user in mongo, but then I'd like to restart using the --auth flag so I can limit interaction with the db.
roles:
  - Stouts.mongodb
  - Stouts.nodejs

vars:
  mongodb_conf_bind_ip: <IP_ADDRESS>
  mongodb_conf_auth: no

tasks:
  - name: Ensure Mongodb is started
    service: name=mongod state=started

post_tasks:
  - name: Generate MongoDB Super User
    mongodb_user: database=admin user=superuser password=daroots state=present

I re-thought how to do it and got what I needed with something like this:
vars:
  mongodb_conf_bind_ip: <IP_ADDRESS>
  mongodb_conf_auth: yes

post_tasks:
  - name: Generate MongoDB Test User
    mongodb_user: "database=test user=testuser password=roles='readWrite' state=present"

  - name: Generate MongoDB Super User
    mongodb_user: "database=admin user=superuser password=roles='readWriteAnyDatabase,dbAdminAnyDatabase,userAdminAnyDatabase' state=present"

Seems like assigning all users I needed, then follow with the super user will allow me to create users while also using --auth flag.

@ShawnStrickland i'm trying the same thing, but your snippet above does not work, as from what i understand here's what happening:

The mongodb role installs mongodb and sets the auth flag to yes in mongo.conf
In the post task, you're creating the admin user

However, at that time, the mongodb server has already been restarted, which means you get database error: not authorized for query on test.system.users in the playbook.
@Stouts what's the proposed solution for adding administrative users with this role?


Detail window still in dark theme even light is selected

Describe the bug
The light theme is selected, however the detail window (right side) is still in dark mode.
Reload, re-install does not help.
Especially for the flow diagrams for pipelines is the dark theme not helpful
Steps to reproduce the behavior

Select "light" theme
click on item to see the details on the right side

Expected behavior
All areas, windows considering the theme selection
Screenshots
See screenshot. I even changed the macOS theme to light only to be sure ;-)

Code snippets
n/a
System

Kui version: 8.10.4
Operating system: macOS 10.14

thanks for the bug report! and apologies for the delay in responding. the two-tone presentation is intentional, but the low contrasts in the flow view certainly are not. thanks!


[BUG]: Including # in PLAYWRIGHT_SERVICE_RUN_ID causes SyntaxError

Describe the bug
When attempting to run tests via Microsoft Playwright Testing, if the PLAYWRIGHT_SERVICE_RUN_ID value contains a #, the tests will fail with a SyntaxError.
 SyntaxError: browserType.connect: The URL contains a fragment identifier
    Call log:
      - <ws connecting> wss:{Playwright Service URL here}

To Reproduce
Steps to reproduce the behavior:

Run playwright tests via MPT with a PLAYWRIGHT_SERVICE_RUN_ID value with a # in it
PLAYWRIGHT_SERVICE_RUN_ID="my-service#id" npx playwright test {testFiles/Patterns} -c {path-to-service-config} --workers={workerAmt}
Conversely, run the same command WITHOUT a PLAYWRIGHT_SERVICE_RUN_ID value containing a #, and you'll see the tests run.
PLAYWRIGHT_SERVICE_RUN_ID="my-service-id" npx playwright test {testFiles/Patterns} -c {path-to-service-config} --workers={workerAmt}

Expected behavior
Tests run in MPT without any issues
Screenshots
N/A
Setup information (please complete the following information):

Azure Subscription Id: 936a42f7-c37d-405e-83e1-feb0bdb095e2
Workspace Name: vaconnects
Service trace Id (if available): n/a
Log snippet (if available): see above
Browser on which tests are executed (if applicable): chromium
Time range (in PST) when the issue was experienced: 0700
Playwright Version: 1.47.2
Client machine OS: Mac
OS requested on Service: Linux

Additional context
I haven't done extensive testing to see if other reserved characters cause this issue. I encountered it because I was taking the branch name for the PR and using that to form the PLAYWRIGHT_SERVICE_RUN_ID. Some team members include a # in their branch name (annoying but 🤷🏻 ). The team members with branch names like feature/#1234-my-feature would experience this issue. Team members with branch names like feature/4321-my-feature did not experience the issue.
All in all, I'm not totally against restricting things like this if it's a major lift, but it should at least be documented.

Thanks for reporting this @aaron-goff
We are evaluating this issue and will update with the resolution plan soon.

This specific issue is fixed in the version 1.0.0-beta.4


To run APDetection on a custom dataset

@chandlerbing65nm Hello Sir! I have a few queries on how to train and test this model on a custom dataset. So, I am trying to use the VALID dataset, and as I'm relatively new to this area, I don't have any idea how to run it on this dataset (it has 30 classes and I dont know where I need to edit to specify those class names as well). Can you let me know how exactly do I have to modify the config or dataset files in order to run the train.py on VALID dataset?

@Pranav110500 this repo follows the same framework for training, adding custom dataset, etc from MMDetection. I suggest study first how to do it in MMDetection since all of the information you will need are already available there.


Fixed 34042 -- made the admin navigation sidebar more accessible to screen readers

Improve the experience for screen readers in the django admin with accessibility changes to the sidebar according to https://code.djangoproject.com/ticket/34042
Clarify that the sidebar is closed or open with aria-expanded 'closed' or 'open', aria-label 'Sidebar', and setting the display style to none or block.

@Gloib Do you have time to keep working on this?

buildbot, test on selenium.

@Gloib Thanks for updates :+1: Please update also tests:

admin_views.test_nav_sidebar.SeleniumTests.test_sidebar_can_be_closed and
admin_views.test_nav_sidebar.SeleniumTests.test_sidebar_state_persists

they should now check the visibility instead of tabIndex.

buildbot, test on selenium.

Test failure is not related with this patch.


The inlayHints_lifetimeElisionHints_useParameterNames config doesn't get passed to the server config struct

The inlayHints_lifetimeElisionHints_useParameterNames config doesn't get passed to the server config struct, presumably because we also use inlayHints_lifetimeElisionHints which takes priority over the namespace?

Right so this was just a mistake on my part, we obviously can't use fields on inlayHints_lifetimeElisionHints since that is already set to a string, so we should rename inlayHints_lifetimeElisionHints to inlayHints_lifetimeElisionHints_mode or something similar


Invalid render for CSS @supports

scssphp did not rendering CSS @supports feature.
Render by scssphp (Wrong)
@supports (transform-style: preserve-3d) {
  transform: translate3d(0, 0, 0);
}

Render by official scss compiler (Correct)
@supports (transform-style: preserve-3d) {
  .carousel-item-next.carousel-item-left,
.carousel-item-prev.carousel-item-right {
    transform: translate3d(0, 0, 0);
  }
}

I am using scssphp to compile bootstrap 4 and it is working awesome. except above issue. Please test bootstrap 4.1.3 scss
I am really thankful to @leafo for this php sass compiler

I can confirm this issue:
.sticky-top {
  @supports (position: sticky) {
    position: sticky;
  }
}

compiles as
@supports (position: sticky) {
  position: sticky; }

so this is a duplicate of #493

(duplicate anf fixed, can be closed @robocoder)


Implement paragraph-wise motion and selection.

Ah, apologies, this PR also includes the other one for open_line.js. Merge that one first and then this diff will look sensible ;-)
Let me know what you think about the keybinds. I wanted Ctrl+Up/Down for the motion and Alt-h (emacs style) for the selection, but those were all taken, so I kinda just grabbed whatever was available.

Very nice

I will have to change the keys, though. Alt-up and Alt-down are already taken...

I changed them to Ctrl-PageUp and Ctrl-PageDown. Not great, but we're running out of keys.

Heh, i didn't even notice that alt up and down were taken.
Your choice works fine for me, it's ctrl+fn+up/down on my keyboard anyway.
Thanks for merging!
On Mar 1, 2015 11:34 PM, "Zef Hemel"<EMAIL_ADDRESS>wrote:

I changed them to Ctrl-PageUp and Ctrl-PageDown. Not great, but we're
running out of keys.
—
Reply to this email directly or view it on GitHub
https://github.com/zedapp/zed/pull/517#issuecomment-76669112.

There's a script to check this stuff:
node script/verify_keys_overload.js
If it doesn't print anything all is OK.
On Mon, Mar 2, 2015 at 9:52 AM Robert Bruce Park<EMAIL_ADDRESS>wrote:

Heh, i didn't even notice that alt up and down were taken.
Your choice works fine for me, it's ctrl+fn+up/down on my keyboard anyway.
Thanks for merging!
On Mar 1, 2015 11:34 PM, "Zef Hemel"<EMAIL_ADDRESS>wrote:

I changed them to Ctrl-PageUp and Ctrl-PageDown. Not great, but we're
running out of keys.
—
Reply to this email directly or view it on GitHub
https://github.com/zedapp/zed/pull/517#issuecomment-76669112.

—
Reply to this email directly or view it on GitHub
https://github.com/zedapp/zed/pull/517#issuecomment-76676592.


Stop publishing images with tagged by commit ID

What this PR does / why we need it:
From the beginning, we started publishing both images tagged by semantic version and commit ID.
But, currently, we are only using the ones tagged by the semantic version.
So this PR stops tagging by Git commit ID.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

For sure. It is essentially unneeded anymore.

/approve


Scala Common Enrich: add adapter to process AppNexus events

First event to support: AppNexus id retrieval. Something like:
http://ib.adnxs.com/getuid?http://your-collector.acme.com/com.appnexus/v1/id/%24UID

Migrated to https://github.com/snowplow/enrich/issues/71


"Failed to setup" every time HA restarts

Version: 2024.2.1
HA Version: 2024.2.1
When I go to integrations I see that the integration setup failed, and this is in the logs:
Logger: homeassistant.config_entries
Source: config_entries.py:468
First occurred: February 11, 2024 at 5:47:28 PM (1 occurrences)
Last logged: February 11, 2024 at 5:47:28 PM

Config entry 'Bedroom AC' for midea_ac integration could not authenticate: Failed to authenticate with device.

This error originated from a custom integration.

Logger: msmart.base_device
Source: custom_components/midea_ac/__init__.py:39
Integration: Midea Smart AC (documentation, issues)
First occurred: February 11, 2024 at 5:47:28 PM (1 occurrences)
Last logged: February 11, 2024 at 5:47:28 PM

Authentication failed. Error: Connect timeout.

Reloading the integration fixes it until I restart HA again. Then it comes back.

Can you enable debug logging and post the full logs after a restart?
What's your HA setup? Home Assistant OS? Docker?

Hi - same problem here, reloading config from the Integrations page manually work fine
WIith debug loggin enabled:
2024-02-16 07:21:12.838 ERROR (MainThread) [msmart.base_device] Authentication failed. Error: Connect timeout.
2024-02-16 07:21:12.840 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Guest Bedroom' for midea_ac integration could not authenticate: Failed to authenticate with device.
2024-02-16 07:21:12.841 ERROR (MainThread) [msmart.base_device] Authentication failed. Error: Connect timeout.
2024-02-16 07:21:12.841 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Office' for midea_ac integration could not authenticate: Failed to authenticate with device.

Sorry you're having issues. Can you answer the above questions about your HA setup?
Those looks don't look like debugging was enabled (or I don't log nearly enough helpful information!).

Sorry, my bad with the debug logs - will redo, but not able to replicate it at present - last 3 reboots have loaded the devices fine
Running HA OS on a Pi4b
I'll upload the correct logs if it happens again

home-assistant_midea_ac_2024-02-16T08-02-45.973Z.log

I rolled back my HA Core version to 2024.1.6 and the problem has gone away - it appears possibly related to https://github.com/home-assistant/core/issues/109903 which also went away when rolling back to 2024.1.6

Thanks for the logs. For whatever reason the network doesn't appear to be up when your HA restarts, but it also looks like I should be implementing a "reauth" flow to allow the integration a chance to connect again.
https://developers.home-assistant.io/docs/integration_setup_failures/

Just released a new version that I'm hoping will help you with your problem. Let me know either way.

I have the same problem. Whenever home assistant restarts, I get authentication erros a few times, then it just works.

Hi,
I have the same problem too but I've temporary resolved defining a simple automation that reload the entities after homeassistant restart.
Something like:
alias: Midea
description: ""
trigger:
  - platform: homeassistant
    event: start
condition: []
action:
  - service: homeassistant.reload_config_entry
    target:
      device_id:
        - ************************
    data: {}
mode: single

I hope can be helpful.

Have you all updated to 2024.2.3?

I didn't notice there was a new version after 2024.2.2. I updated now and it seems to work fine for me.
Thanks

Yeah I don't blame you. I released them within a few hours of each other since I realized I left a bug in 2024.2.2

Seems to be working for me now, updated and restarted and it looks to be working.

👍 Glad to hear it. Let me know if anything else comes up.

hello, the issue started again, with the Not loaded error

@snichita you have not provided sufficient information for me to debug. I am not even certain what your problem is.
Please,

Create a new issue, describing your specific problem.
Provide complete debug logs showing the issue.


Rename prime.js and alias command to t2. Fixes #29

Merge when it's convenient. Really no hurry for this.

Closing in favor of #37.


License

We need a license for this project.
What do people think about GPL?
https://en.wikipedia.org/wiki/GNU_General_Public_License
or we could go with Apache 2 like TensorFlow does
https://github.com/tensorflow/tensorflow/blob/master/LICENSE

I also tend to use Apache 2. I love this website: https://choosealicense.com/, in case you want a different way to think about it.

I would also recommend BSD3: https://choosealicense.com/licenses/bsd-3-clause/

Any license that allows free reuse at least for academic purposes is fine by me.
If we have questions on the finer points, Seth (@kltm)is a fount of license-y wisdom

I would say our goals are

Any body can use the software
Nobody sues us
I thought that was what GNU does -- and it also encourages other people to play the same game?

What advantage do the other licenses have actually?

I tend to prefer and recommend BSD-3 clause for software (over MIT). If somebody realistically thinks patents are an issue, there is Apache.
GPL is...complicated and can prevent reuse is others do not use the same license. If one is joining a body of software that already uses it, it's fine. For new works, something more permissive generally plays better with the community.

@kltm Thankls!
So is everybody ok with BSD3 ?

So is everybody ok with BSD3 ?

+1 BSD3

https://github.com/monarch-initiative/N2V/pull/152
Please acccept if OK. You need to say (c) by -- I put Monarch Initiative if that is OK?


Reconsider how we deploy the prometheus and grafana operators

Currently the monitoring stack operator deploys the grafana and prometheus operators through reconciliation loops.
This seems to be discouraged according to the following document: https://sdk.operatorframework.io/docs/best-practices/best-practices/
An Operator shouldn’t deploy or manage other operators (such patterns are known
as meta or super operators). It’s the Operator Lifecycle Manager’s job to
manage the deployment and lifecycle of operators. For further information check
Dependency Resolution.

If multiple operators are packaged and shipped as a single entity by the same
CSV for example, then it is recommended to add all owned and required CRDs, as
well as all deployments for operators that manage the owned CRDs, to the same
CSV.

We should reconsider whether to adopt the suggested practice as well in order to reduce the responsibility and privileges of the monitoring stack operator.

Closed by https://github.com/rhobs/monitoring-stack-operator/pull/50


feat(chart): add imagePullSecrets support

Hi,
This PR introduces support for imagePullSecrets for both the manager deployment and the daemon ds. One can either declare those values globally or locally for each component. Motivations behind this change are:

Authenticate to the registry in case of a custom, private image
Getting rid of rate limitations for services like Dockerhub when pulling images onto a large cluster

Please let me know if anything looks wrong to you.
Thanks in advance for reviewing the code.
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist:

[x] I have bumped the chart version according to versioning
[x] I have updated the chart changelog with all the changes that come with this pull request according to changelog.
[x] Any new values are backwards compatible and/or have sensible default.
[x] I have signed off all my commits as required by DCO.

Changes are automatically published when merged to master. They are not published on branches.

@emaincourt Thanks. But question is, the imagePullSecrets of kruise-manager or kruise-daemon can only be secrets in kruise-system. How could you apply the secrets during helm install?

@FillZpp Sorry for the delay and thank you very much for reviewing the changes.
Actually yes those secrets must live in the kruise-system namespace, but that’s the responsibility of the owner of the cluster to make them available at deployment time.
In case you want to make it possible to optionally create the secret at install time, a secret could be added to the chart but I quite believe it would be outside of the scope.
What do you think ?

Actually yes those secrets must live in the kruise-system namespace, but that’s the responsibility of the owner of the cluster to make them available at deployment time.

Alright, that's fine. Maybe .Values.manager.imagePullSecrets is unnecessary since the images of kruise-manager and kruise-daemon are the same so .Values.imagePullSecrets is enough.

In case you want to make it possible to optionally create the secret at install time, a secret could be added to the chart but I quite believe it would be outside of the scope.

Actually, we can create the image in helm chart by https://helm.sh/docs/howto/charts_tips_and_tricks/#creating-image-pull-secrets , but this needs user to set registry/username/password parameters when helm install.
Do you think this is better than manually create secrets into kruise-system after helm install?

@FillZpp Thanks for the review !

Alright, that's fine. Maybe .Values.manager.imagePullSecrets is unnecessary since the images of kruise-manager and kruise-daemon are the same so .Values.imagePullSecrets is enough.

That's actually a pretty fair point. I did not realize it sorry. I updated the manifest to match it.

Actually, we can create the image in helm chart by https://helm.sh/docs/howto/charts_tips_and_tricks/#creating-image-pull-secrets , but this needs user to set registry/username/password parameters when helm install.
Do you think this is better than manually create secrets into kruise-system after helm install?

Well honestly I've never seen a chart allowing for imagePullSecret creation. I would expect secrets creation/update to be handled by a centralized/secured application, which would stand as a vault. Basically, in case I need to update this secret, I would not expect to have to update all the value files of all the charts I deploy, nor to share docker credentials with the whole team.
What do you think ?


Snowpark setup third-party terms

Mention Snowpark / Anaconda third-party terms within "Additional Setup."
If we always require pandas to be installed (https://github.com/dbt-labs/dbt-snowflake/pull/229), then using dbt Python models at all requires accepting third-party terms as a prerequisite.

This is a small change to beta docs that clarifies a point of confusion for a beta tester. I'm going to go ahead and merge as is, given the size of the current backlog


Train fixes

suddenly the docs build CI jobs is failing with
Exception occurred:
  File "/home/runner/work/sfaira/sfaira/docs/conf.py", line 124, in setup
    app.add_stylesheet('css/custom.css')
AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
The full traceback has been saved in /tmp/sphinx-err-3xhte9a0.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
make: *** [Makefile:16: html] Error 2
Error: Process completed with exit code 2.

any idea where this is coming form @davidsebfischer @Zethson ?


Specify MSRV instead of fixing the toolchain

Description
Specifying a rust-toolchain file fixes the Rust version being used, while we should rather specify an MSRV instead, as is the rust-version field of Cargo.toml intended to be.
PR Checklist:

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added or updated tests that comprehensively prove my change is effective or that my feature works

I'm not sure why the CI for code-coverage is failing, it shouldn't. The error is the following:
Run cargo tarpaulin --verbose --engine llvm --release --out Xml
error: invalid value 'Xml' for '--out [<FMT>...]'

I've noticed it failing on other repos as well (for instance https://github.com/toposware/cheetah), though not really blocking.

Swapping my review with Simon's as I think he can be of much greater value here

@sebastiendan Sure thing! Although the CI check being red is a bit ugly. As we'll publish this on crates.io at some point, we'll probably want to address it soon. But non-blocking for this particular PR.

Run cargo tarpaulin --verbose --engine llvm --release --out Xml

Speculation: perhaps it should be --out xml? And it works for macos users because the FS is case insensitive?

Speculation: perhaps it should be --out xml? And it works for macos users because the FS is case insensitive?

Perhaps, though I'm confused why it was working in the first place then.
Regarding the MSRV comment, I don't really have an objection to not setting a MSRV and just relying on the latest stable, it just felt more proper to have it declared (and I think as a general rule if every crate was specifying their MSRV this would definitely help the ecosystem) but I'll leave the experts decide here 🙂
@Freyskeyd Do you have any opinion?

Closing in favor of https://github.com/topos-protocol/ice-frost/pull/9.


Azure Linux Web App, "it" culture not working

Describe the bug
Create a new aspnetcore 2.2 web app, enable it and en cultures as the documentation instructs, and make a page that prints the current date in short date format "d".
Run it locally with an italian browser, it correctly use the dd/MM/yyyy pattern, then deploy it to azure linux web app (code and framework dependent, not container) navigate to that page with the same browser with italian language : the displayed date has the english M/d/yyyy pattern.
Printing the output of this code in a page confirms that the database of culture information has problems :
new System.Globalization.CultureInfo("it").DateTimeFormat.ShortDatePattern)
new System.Globalization.CultureInfo("en").DateTimeFormat.ShortDatePattern)

@Eilon can you move this to CoreFx?

This issue was moved to dotnet/corefx#36631


Return an error if someone calls get_header_xxx for a header which is considered rejected

As the go celestia node doesn't yet have shwap protocol on mainnet, we should put this on hold as we will always be rejecting das'ed headers. This means we would always return an error to the users on get_header


Highlight arrow points to off-screen items in Inventory

When a level requires an item and does the big highlight arrow, sometimes the item will initially be offscreen, so the arrow points at nothing (below the Play button).

We probably need to automatically scroll the inventory list to the item being pointed at before showing the arrow.

Fixed as duplicate of #3458


Invalid HandlerSetter type for useGlobalEvent hook

Describe the bug
The following PR introduced some breaking change in typings: https://github.com/beautifulinteractions/beautiful-react-hooks/pull/156/files#diff-b52768974e6bc0faccb7d4b75b162c99R19
Argument of type '() => void' is not assignable to parameter of type 'any[]'.
  Type '() => void' is missing the following properties from type 'any[]': pop, push, concat, join, and 27 more.  TS2345

     7 | 	const onWindowResize = useGlobalEvent('resize');
     8 |
  >  9 | 	onWindowResize(() => {
       | 	               ^
    10 | 		setWindowWidth(window.innerWidth);
    11 | 	});
    12 |

I've tried the following, but of course, it is not working properly. But satisfies the TS compiler :smile_cat:
onWindowResize([
	() => {
		setWindowWidth(window.innerWidth);
	},
]);

Possible workaround
Use the third param of useGlovalEvent hook:
useGlobalEvent('resize', undefined, () => {
	setWindowWidth(window.innerWidth);
});

To Reproduce
I've prepared CRA repo to show this bug.
One with latest version --> compare: failling-issue-v0.30.5
And one with version that introduced the problematic change: compare: failling-issue-v0.30.1
Expected behavior
Well, I should have no TS compiler errors following hook examples. I know, these are JS examples, but we should either provide working TS versions of examples, or fix the typings. I vote for the latter one.
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
$ node --version && npm --version && yarn --version
v12.11.1
6.11.3
1.22.5

Hi @jacekk
thank you for pointing this out and yes this is definitely a bug urgently needs to be fixed
I merged that PR as I didn't notice the bug, I'm not great with TS
would you mind to open a PR?

@antonioru I will try to find some time. Kinda busy days lately :confused:

@antonioru I will try to find some time. Kinda busy days lately 😕

hehe I totally understand :)
don't worry, no pressure meant, your work will be welcome as soon as you feel like doing it
thank you very much, I really appreciate it


How to access index in rv-each?

The documentation says under "Differences from rivets.js":

Change how scope of iteration binder works. Instead of copying properties down to children, uses a prototype like approach
Related: 486 512 417
Change how to customize index name in each binder (using an attribute)
Related: 551 552

Issue 551 and pull-request 552 from rivets.js, which are referred to here, talk about this feature, but it's not clear how (and if) it is implemented in tinybind. The rivets.js generic { index } does not work, nor the other syntax { %item% } that was later added in rivets.
Is it possible to access the iteration index inside rv-each in tinybind?

Oh, I found it. The syntax is {$index}.
Found it in the example.
But what about nested indexes? Rivets.js has this syntax now:

{ %items% }: whatever

The index of the iterated array items here can be accessed with { %items% }. In this way, it is possible to distinguish indexes of nested rv-each iterations.
Is something like that also possible in tinybind?

Oh, I see. That's how it works:

{ something }: whatever

Would be worth documenting,  I think.


[Feature] Pre-push hooks

Search before asking

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

Description
It would be great to have a pre-push hook for the KubeRay repo.
Every lightweight check in the CI should be included as part of the hook.
Things to include:

Linters (including, if possible, the new Helm check)
Code and config generation

If the hook modifies code, it should fail.
Guidance on install the hook should be included in the Development README.
Use case
It is convenient for development to have your push blocked by a pre-push failure.
Otherwise, you have to go to the GitHub UI and wait for checks to run. This slows development iteration speed.
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Scripts to be run at the discretion of the developer are an alternative.


Bring analytics back online

still need to test, but this is looking decent
requesting review but not quite merge yet

Biggest question is - can all the electron specific code on the renderer be separated out to other files to make it easier to re-use this repo for a web build too?

Biggest question is - can all the electron specific code on the renderer be separated out to other files to make it easier to re-use this repo for a web build too?

It definitely should, but let's defer that to another day while we get v0.3.0 out
A big Q about that is how we have non-deterministic actions in the useEffect hooks.
probably something like this? (with effect being a prop)

One thing to note on config in particular is that we can't really do that with localStorage imo. User's settings will need to be persisted for upgrades (I assume localstorage will reset in the Electron app each time at least). Also, FWIW on the web due to adblocks I consider it fair game to get set analytics enabled to true by default and skip the prompt.

yeah, i'm not trying to say "use localstorage only", i'm wanting a logical code partition so that local storage is used as a client buffer, and then we sync from there to whatever makes sense for that deployment.

yeah, i'm not trying to say "use localstorage only", i'm wanting a logical code partition so that local storage is used as a client buffer, and then we sync from there to whatever makes sense for that deployment.
oh, right -- fair enough!


Fix http parser

ZHF: #309482
Description of changes
Upstream was using depreacted module imp. Replaced with importlib.
Appiled a patch from this pr: https://github.com/benoitc/http-parser/pull/101

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 311123 run on x86_64-linux 1

4 packages built:

python311Packages.http-parser
python311Packages.http-parser.dist
python312Packages.http-parser
python312Packages.http-parser.dist


replace note about restore

A customer complained about this note in this topic. It seems out of place.

The note was certainly inappropriate because I included the wrong include file. Rather than removing it as you'd originally done, @mairaw, I've modified your PR to replace it with the correct include. I've also changed the PR title to reflect the new intent of the PR. If this builds and displays a note that we don't list the values of preview keys, we can merge.

Perfect!


Unable to list functions using provider v0.70.1

Provider Version
0.70.1 (we have also noticed this issue with 0.54.0).
Terraform Version
0.14.11
Describe the bug
We are unable to list the functions (snowflake_functions.current.functions) using snowflake_functions as a data source. Upon including "functions" as a Terraform output, the output shows as "[tolist(null) /* of object */]" and the following error is received in the debug logs:
[DEBUG] error listing functions: unable to scan row for SHOW USER FUNCTIONS IN SCHEMA "<db_name>"."<schema_name>" err = %!w(): timestamp=2023-09-28T11:46:56.575Z
Expected behavior
We expect the list of functions to be returned in the Terraform output as it is when we use provider v0.37.1, for example:
functions_data = [
tolist([
{
"argument_types" = tolist([
"FLOAT",
])
"comment" = "user-defined function"
"database" = ""
"name" = ""
"return_type" = "FLOAT"
"schema" = "<schema_name>"
},
etc.
Code samples and commands
Data source declaration:
data "snowflake_functions" "current"{
depends_on  = [snowflake_function.exampleone,snowflake_function.exampletwo]
database = ""
schema   = "T"
}
Usage:
locals {
functions  =  [ data.snowflake_functions.current.functions ]
}
Additional context
We have noted that the queries used for the output (found in Snowflake query history) for both versions of the provider are the same:
SHOW USER FUNCTIONS IN SCHEMA "<db_name>"."<schema_name>
However, with version 0.70.1 (and 0.54.0) the output "functions" is showing as a list of null, so we suspect there was some issue in between running the query and returning its results to Terraform.

Hey @aggielam26. Thanks for reaching out to us.
The version you are using uses the old, already-removed implementation. Because we are still in 0.x.x version, we are not providing bugfixes to the older releases - fixes are always in the newest versions.
Please try bumping to the newer versions of the provider (remember to follow the https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/MIGRATION_GUIDE.md#migration-guide). Also, please bump your terraform to at least 1.1.5 version (this is required with newer provider versions).
Let me know if the error persists in the newer versions.

Hey @aggielam26. Did you have a chance to migrate to the newer provider version?

Closing due to inactivity. @aggielam26 please bump to the newest version and create a new issue if the problem persists.


⚠ Bofrost.de has degraded performance

In c7e50f9, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1478 ms

Resolved: Bofrost.de performance has improved in 1f0641c after 46 minutes.


Hr create applicant

@rathorevaibhav I'll need access to the UAT site where I can go through the functionality as well.

@rathorevaibhav great job at decoupling 👍
I'm creating a separate tracking for Vue Components. Let's merge this one now and start testing.

Oh you've already created it :) #19

@nishanth-kd I realized I didn't put the validation logic. I've created a tracking #20 and we can take it forward there. Merging this now.


exposed the setLoadFactor method for KSFailure

I am not sure if this is the correct place to merge these changes. I wanted to expose this function for some mphys optimizations. We can maybe push our changes to a different branch, and have mdolab/master be up to date with graeme's version.

Yes I think we should keep the master branch up to date with the upstream.
For smaller PRs, its probably best to make the PRs directly to upstream, if the maintainers are willing to accept/merge, and then we can pull to master.
However, for larger development efforts we may need to make a separate branch for the changes which we then make PRs to upstream.

I agree that it's best to keep master up to date with upstream. Ideally, this change is submitted to Graeme as a PR, but the other alternative would be to just push it to a branch for now. I am going to close this PR in favour of one of those two options.


Execution failed for task ':tasks'.

Execution failed for task ':tasks'.

Could not create task ':react-native-headphone-detection:compileDebugJavaWithJavac'

build gradle:
buildToolsVersion = "33.0.0"
//kotlinVersion= "1.7.0"
minSdkVersion = 21
compileSdkVersion = 33
targetSdkVersion = 33

In order to compile Java 9+ source, please set compileSdkVersion to 30 or above


double-gamma incorrectly displayed

In http://www.brill.com/sites/default/files/ftp/downloads/34732_Preview.pdf on the 16th page (in the document itself the page is labelled 10) the double-gamma in ἄγγελος (and many other words in the first column of text) is misrendered.
What I expected to see: two gammas -- γγ
What I saw instead: it's difficult to describe but I'd say that it looks kind of like kettle (see screenshot)

Versions tested: pdf.js as shipped with ff 33.1 and master (20bf84ac5).
Other notes:

Single gammas render fine, for instance ἆγε in the second column. The double-gammas are rendered fine in Preview and in the renderer that Chrome uses.

In Greek gamma is equivalent to g in English and is this character: γ. In Greek double gammas are pronounced differently. I notice that in Preview and in Chrome when I select text, I can't select individual gammas when they're paired up -- either both or neither.

@CodingFabian Is this still broken using the latest versions of Firefox and PDF.js?

yes still broken in latest nightly (41.0a1 (2015-06-09)) and latest pdf.js (fda6c186447c6eeea5850613888ce67c4dc4f502)

Reduced test-case: https://www.dropbox.com/s/yxcacixy2gfyblp/issue5540_reduced.pdf?dl=0.
Note: I don't have access to a Mac, so I'm hoping that it accurately captures the issue.

it does:

fixed by #6171 confirmed on my mac using preview version for that PR.
@Snuffleupagus please close, thanks.


Remove all notions of morphology equality

This is now handled in morph-tool

I think the version number should change, because this is a big change in functionality (in the right direction, IMO)

Ok, I'll tag this commit with an increment in the minor version number


feat(MultiSelect): pass through <ListBox.Selection> translations (cherry-pick)

Porting over this change from v7.X over to 6.X 3395 which closed 3393
This PR passes translateWithId through to the nested <ListBox.Selection> in MultiSelect components
Testing / Reviewing
Ensure that translations are working correctly for the <ListBox.Selection> title

Wrong root branch. Closing and recreating...


Can't remove an item that has never been added

Using store.createRecord and then modifying the defaults. Upon save of the model I get this error:

Can't remove an item that has never been added

The server response looks normal, but I get this error and the fragments disappear from my template view.
Fragment
export default DS.ModelFragment.extend({
  key: attr('string'),
  name: attr('string'),
  description: attr('string'),
  kind: attr('string'),
  abilities: hasOneFragment('ability', {
    defaultValue: {
      view: true
    }
  }),

  componentName: computed('kind', function () {
    const kind = this.get('kind');
    return `permission-${kind}`;
  })
});

It seems like it thinks that abilities is an array that was changed..

Found it, I have a computed property and it's trying to parse it on the fragment..

I'm not sure I understand what's going on here, is this a model fragments issue, or were you overriding the fragment property by mistake? As usual, a jsbin is the best way for me to diagnose.

If you are ever able to reproduce this behavior in a failing test, jsbin, etc. please reopen.

I think the issue is caused by having a computed property on a fragment. Is this a known bug?

That's a good point.. I did have a CP.

I think this was happening because fragments that were accessed prior to the save didn't get updated with the new data until after they are accessed again. This also only happens when the adapter returns a response with data in it, instead of a 204. It should be fixed by #109, here's the relevant test.

Is this still an issue in the 0.3.x series?

Shouldn't be, just forgot to close

So this is still an issue in 0.3.3, 204 solves it kind, but introduces an issue where you have fragments that aren't updated after save, since the new data isn't send back, so the model isn't updated.

And passing data with the 204 doesn't help.

Is there a way to set the data back on those items? Because the only workaround is a refresh of the page, and if you forget and save the model, you overwrite the data with blank fragments.

@slindberg would love your thoughts on this.

So this is still an issue in 0.3.3, 204 solves it kinda, but introduces an issue where you have fragments that aren't updated after save, since the new data isn't send back, so the model isn't updated.

This issue is fixed in v0.4.0, which is tied to ED >= v1.13.0. Unfortunately I don't have the spare cycles to try to backport this fix to a v0.3.x series release, since the fix was a byproduct of refactoring adapter updates for v1.13 compatibility. I think your only option right now is to update ED :confused:

For clarity's sake and for future readers of this issue, there are two ways an API can respond to a POST/PUT/PATCH1:

200 OK - Contains a data payload. ED treats this new data payload as canonical, and MF should respect that (if it doesn't, it's a bug).
204 No Content - Does not contain data payload. ED assumes that the current state of the model is now canonical, and simply transitions to a clean state. MF should also respect this.

So if your server needs to update properties on the model (e.g. update a modified timestamp), you must use the first approach. If the server also modifies fragments, the objects will be updated to reflect the new state.
The issue was that when the adapter responds with a payload, existing fragments/arrays were not notified of the update, so they ended up returning stale data. As I said, this should be fixed in v0.4.0.
[1] Note that the actual HTTP response code does not matter (as long as it's a 2XX), it's simply convention.


Making CI work

@GuillaumeGomez also please set the "rolling builds" flag in appveyor settings.

On it. Thanks @gkoz!


Throw on error in server.start().

Servers fails silently if the port is already in use. This second throw makes the error more explicit.

Thanks for creating a PR.
I'm not sure this is solving anything. Could you provide steps to reproduce?

Launching the server twice (by error) the 2nd instance stalls because the port is already in use. The throw makes that error explicit.

I'll give that a try, but it doesn't seem like server start would even be called. If there was an err, we would have already thrown it and the process wouldn't continue.

Ah! No wonder the PR didn't make sense to me. It wasn't an error with Composer but with server.start and you're not defining the first argument of that function.

The first throw is about configuration and plugins, initial state. The second throw happens after that, when why try to open an already used port.
That's exactly what happened to me after I generated my first project. I launched the generated server twice, no error was shown, but when I edited a few files and restarted that second instance (forgetting about the first), my changes didn't seem to take effect. Adding the 2nd throw showed me I had another instance already running.

Please also update:

api/templates/server.js
web/templates/server.js

Thanks! After we fix the shadowing, let's squash your commits into one and then we can merge.

Sorry about that. I don't know about squashing, I do the absolute minimum with git. I can type what you tell me to but please, no more git docs ;-)

I can open another issue, but while we're on the topic, would it make sense to reuse one template instead of have 3 copies to update? Not sure how yeoman can deal with that.

would it make sense to reuse one template instead of have 3 copies to update? Not sure how yeoman can deal with that.

Not a big deal IMO.

Also thanks for getting involved and seeing this PR through 🎉 :shipit:

v8.0.3 has been published with these changes.

Thanks for seeing me thru it :-)


Acrylic  not working

i try all method check my code re write code. use settings. enable gpu increase opacity but transprancy not  working

What are you expecting about “transparency”? Acrylic is not transparency. A screenshot would be nice.

then how i achive transrarency with blur effect. its full black

What have you tried so far. Can you share a screenshot of what you have now?

here is image

Please any one reading this email please I beg you with the name of any
thing you worship please help me out with $200 am dieing but you can save a
life by helping me out I will really appreciate if my request are granted
am the one innocent, you can send me the money through Bitcoin, this my
Bitcoin wallet address 3HUj5eE3DApm6tW68aDVJMfrAUij2oTXD2 God bless you
On Mon, Jun 7, 2021, 4:34 AM kideas11 @.***> wrote:

[image: image]
https://user-images.githubusercontent.com/84661890/120955504-f7a24600-c76a-11eb-9cb9-eecce5454322.png
here is image
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/10333#issuecomment-855550510,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARVXUW6SY2FZL6OGULKSXQTTRQ43NANCNFSM46DBIOMA
.

Please check the FAQ. If acrylic works in Calculator but not the terminal, I'd definitely be surprised.

i try all methods but nothing work if you want more you surely assit me using windows quick assist

Okay sorry, could you confirm that acrylic is working in the Calculator app?


streamlining GHA testing

Address this comment.
Also, we are generating a cov report, but not actually checking/comparing/reporting anything from it. If we would like to set up codecov, I can do that easily, I will just need admin access to spopt.

Going ahead to merge this and focus on the coverage stuff in #24


Earlgrey: csrng_core doesn't work in Verilator after Opentitan update

After updating Opentitan to newest version, csrng_core test is failing with:
%Error: Could not get lowconn handle for port, aborting
%Error: Internal Error: ../V3Ast.cpp:346: Null item passed to setOp1p

Looks like we're missing some dependencies.

#520 adds missing dependencies.
After it, there is the warning thrown:
lc_ctrl_pkg.sv:177:60: Operator VAR 'TransTokenIdxMatrix' expects 1323 bits on the Initial value, but Initial value's REPLICATE generates 2987 bits.
There is the issue about that package: https://github.com/chipsalliance/UHDM-integration-tests/issues/495, so I mark it as blocked and come back after fixing the problems with that package.

It works after https://github.com/antmicro/verilator/pull/508


Add wezterm support as a new backend beside tmux

Hey there. I had been a long neovim + tmux Ctrl[j,jk,h,l] user for long time. And recently found another alternative setup which satisfies all my needs. It's wezterm + its built-in multiplexer, which gives me:

a multiplexer ability to split panes and create a new tab instance
use copy mode with vim like keybinding
built-in ssh support
and finally, as a bonus, to preview images and having terminal multiplexing at the same time! Which is awesome!

The only missing part is make it works with the Ctrl[j,jk,h,l] nav workflow: to switch back and forth between panes and neovim windows seamlessly (resize panes as well, which I do not use). The solution for emacs + evil (vim binds)  is already implemented. And perhaps, it is time to make it work for neovim as well.
The trick is to ask wezterm about the available panes at the interested side and use these ids to direct navigation like:
wezterm cli get-pane-direction right # capture id number as stdout output
wezterm cli activate-pane --pane-id 46 # use the id

What about to create a new backend (lets say wezterm) and make the plugin work for wezterm also? Thank you for any input.

Heho,
nice you discovered wezterm! Awesome terminal! I guess it would be worth another plugin to not drive more complexity into this one. The current implementation would deviate quite a bit.
Maybe willothys plugin already fits your needs.
A good starting point would be:

https://github.com/wez/wezterm/discussions/995
https://github.com/willothy/wezterm.nvim/


Packager + WebpackPlugin

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

I understand that the WebpackPlugin is in flux, so I just may be ahead of the curve trying this out right now, but figured I had to ask. (I did pulldown an update of EF v6beta prior to all this testing)
Currently if I run npm run package it builds a package for me. That said, it does not appear to be using the plugin. I have none of my images displaying, and the .json file I used to setup my keyboard shortcuts never appeared to load (these were all working in development). My JS and SASS seem to work, just without images or json. When I look under out/MyApp-darwin-x64/MyApp.app/Contents/Resources/app I see a complete copy of everything in my root folder, except the out folder itself.
Did I miss a critical step? I did take a pass at setting dir: path.resolve(__dirname, '.webpack') but still didn't get my images or json (???). Feel like I must be missing some critical step?
forge.config.js
const path = require('path');
const WebpackPlugin = require('@electron-forge/plugin-webpack').default;
const pkg = require('./package.json');

const forgeConfig = {
  "packagerConfig": {
    arch: 'x64',
    electronVersion: '2.0.9',
    icon: path.resolve(__dirname, 'src/assets/mac/myapp.icns'),
    name: 'Karaoke Edge Lite',
    overwrite: true,
    platform: 'darwin',
    prune: true
  },
  "makers": [
    {
      "name": "@electron-forge/maker-squirrel",
      "config": {
        "name": “myapp”
      }
    },
    {
      "name": "@electron-forge/maker-zip",
      "platforms": [
        "darwin"
      ]
    },
    {
      "name": "@electron-forge/maker-deb",
      "config": {}
    },
    {
      "name": "@electron-forge/maker-rpm",
      "config": {}
    }
  ],
  plugins: [
    new WebpackPlugin({
      mainConfig: path.resolve(__dirname, 'webpack.main.config.js'),
      renderer: {
        config: path.resolve(__dirname, 'webpack.renderer.config.js'),
        prefixedEntries: [],
        entryPoints: [{
          html: path.resolve(__dirname, 'src/windows/main/index.html'),
          js: path.resolve(__dirname, 'src/windows/main/index.js'),
          name: 'main_window',
        }, {
          html: path.resolve(__dirname, 'src/windows/background/index.html'),
          js: path.resolve(__dirname, 'src/windows/background/index.js'),
          name: 'background_window',
        }, {
          html: path.resolve(__dirname, 'src/windows/help/index.html'),
          js: path.resolve(__dirname, 'src/windows/help/index.js'),
          name: 'help_window',
        }, {
          html: path.resolve(__dirname, 'src/windows/about/index.html'),
          js: path.resolve(__dirname, 'src/windows/about/index.js'),
          name: 'about_window',
        }],
      },
    }),
  ],
};

module.exports = forgeConfig;

Please ignore me. My fault. I was using the file-loader instead of the url-loader, and the json is loading, it's just taking longer to setup the keyboard shortcuts in the prod app than it was in development (?).


configuring uuid flag for generating a version 4 uuid value and writi…

…ng it to the path and key passed as arguments

code content looks good. the indentation is messed up from when you removed the loop, though. Just run the file through go fmt and its job done.


Track if a player with banned gear or no specs gets the kill

In the case where a player doesn't spec twice or uses banned gear and gets the kill, it would be beneficial for them to be flagged in some way

This has been added for players that dont 2x spec


The Spatialbox was choosing wrong regions, rows and columns

Please, review the Spatial toolbox from my repository for the bug fixes

I am getting the same issue. The region i get the data for  is different from the region i select.
Is it fixed in the python version?

Hello. I am getting the same issue. The region I get the data for is different from the region i select. Is it fixed in the Python version? best regards Anurag

Please show a sequence of operations that lead to the bug. We hardly support this software, the Python version is not yet ready at this level of GUI, it's only a Jupyter notebook with commands https://github.com/alexlib/pivpy

As it can be observed from the attached image, I have chosen a region to plot the data along its rows. The y range should be from 0.068 to 0.1 (approximately), according to the selection.
However, as can be seen from the legend, the data is plotted with y ranging from 0.04-0.068, which is incorrect.
Thanks for the prompt reply.
best regards
Anurag

choose columns at the bottom instead of rows

From: akkupant @.>
Sent: Tuesday, April 16, 2024 4:56:45 PM
To: OpenPIV/openpiv-spatial-analysis-toolbox @.>
Cc: Alex Liberzon @.>; State change @.>
Subject: Re: [OpenPIV/openpiv-spatial-analysis-toolbox] The Spatialbox was choosing wrong regions, rows and columns (#4)
As it can be observed from the attached image, I have chosen a region to plot the data along its rows. The y range should be from 0.068 to 0.1 (approximately), according to the selection.
However, as can be seen from the legend, the data is plotted with y ranging from 0.04-0.068, which is incorrect.
Thanks for the prompt reply.
best regards
Anurag
OpenPIVSpatial.png (view on web)https://github.com/OpenPIV/openpiv-spatial-analysis-toolbox/assets/166389050/8e61de4c-c63c-4b43-82c3-0b78c43e34c9
—
Reply to this email directly, view it on GitHubhttps://github.com/OpenPIV/openpiv-spatial-analysis-toolbox/issues/4#issuecomment-2059160862, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFWMZVXH3G7Y37YT36XO5DY5UUZ3AVCNFSM4AMI43T2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBVHEYTMMBYGYZA.
You are receiving this because you modified the open/close state.Message ID: @.***>

As can be seen again, the  y range in the plot does not lie inside the selected region. I'm sorry if I'm mistaken anywhere but I wanted to be able to plot the variation of u along x or y direction.

Thanks again!


About Setting up your computer Page

I am a newbie but I think I found that there is something wrong on this page.
http://newcoder.io/begin/setup-your-machine/#linux
I am a Ubuntu user. The description about virtualenv & virtualenvwrapper for Ubuntu user should be the upper part of code.

Let me know if I am wrong.

I don’t understand your request. Could you rephrase, or post a screenshot with arrows?

I second him too. The upper part is for Ubuntu and the lower part is for RHEL/Fedora/centos

I suspect that the paths changed on Ubuntu, or that the code was written before the deb packaging was changed, or it can be an issue of “installed with pip” vs. “installed with apt”.
The debian package installs things in /usr/share: http://anonscm.debian.org/cgit/collab-maint/virtualenvwrapper.git/tree/debian/virtualenvwrapper.bash-completion

I can confirm I needed to use "echo 'source /etc/bash_completion.d/virtualenvwrapper' >> ~/.bash_profile" on Linux Mint 17.1 (would have followed the Ubuntu/Debian instructions)


mini_portile2 will not run on Ruby 3.1.0.dev (master) where net-ftp is a bundled gem

When using mini_portile2 on Ruby 3.1.0.dev, we see this error:
/home/runner/work/nokogiri/nokogiri/vendor/bundle/ruby/3.1.0/gems/mini_portile2-2.5.1/lib/mini_portile2/mini_portile.rb:4:in `require': cannot load such file -- net/ftp (LoadError)
	from /home/runner/work/nokogiri/nokogiri/vendor/bundle/ruby/3.1.0/gems/mini_portile2-2.5.1/lib/mini_portile2/mini_portile.rb:4:in `<top (required)>'
	from /home/runner/work/nokogiri/nokogiri/vendor/bundle/ruby/3.1.0/gems/mini_portile2-2.5.1/lib/mini_portile2.rb:2:in `require'
	from /home/runner/work/nokogiri/nokogiri/vendor/bundle/ruby/3.1.0/gems/mini_portile2-2.5.1/lib/mini_portile2.rb:2:in `<top (required)>'
	from ../../../../ext/nokogiri/extconf.rb:402:in `require'
	from ../../../../ext/nokogiri/extconf.rb:402:in `process_recipe'
	from ../../../../ext/nokogiri/extconf.rb:871:in `<main>'

Recent commits on Ruby master (e.g., https://github.com/ruby/ruby/commit/e49c998d1e41737016c8afb7e1b22797018caebb) moved the net-* set of libraries from the standard library to be bundled gems.
I'm creating this issue to:

[x] add ruby-head to the set of rubies being tested in CI
[x] address the above error (and any other related errors)

Fixed in v2.5.2.

Hi, apologies if v2.4.0 is not supported but I couldn't find any info on supported versions.
While working on another package (asciidoctor), I noticed installing<EMAIL_ADDRESS>breaks on ruby 3.1 since it depends on<EMAIL_ADDRESS>which has this issue.
I'm not too familiar with ruby, but it seems this can be fixed:

by nokogiri:

release<EMAIL_ADDRESS>with net-ftp as a dependency
release<EMAIL_ADDRESS>using mini_portile2~>2.5.0

by mini_portile:

release<EMAIL_ADDRESS>with net-ftp as a dependency

I'm not sure which fix would be best, but I'll be happy to open a PR in whichever repo it should go to.
Unless both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>are no longer supported, in which case I'll open an issue in asciidoctor.
Thanks.

Hi! Nokogiri v1.10 is not a supported version, since v1.11 was released in January 2021 (the current supported branch is v1.13.x). Please ask the asciidoctor maintainers to update the gemspec!

I actually did this while I had context swapped in: https://github.com/asciidoctor/asciidoctor/pull/4339

Hi @flavorjones

Nokogiri v1.10 is not a supported version, since v1.11 was released in January 2021

Got it.

I actually did this while I had context swapped in: https://github.com/asciidoctor/asciidoctor/pull/4339
Thanks!


Make the navbar sticky

Make the navbar sticky

Honestly it doesn't matter if the navbar is sticky or not. Tech With Tim doesn't use it. It's annoying, but we can work on it later.


Use split(" ") instead of split_whitespace()

Fixes #6
1- We know that arguments are seperated by ASCII spaces, not weird ass utf8 whitespace
2- Multiple spaces means theres an argument that is an empty string (for the sake of example, spaces are replaced with |) run arg1||arg3 means that arg1 = arg1, arg2 = "" and arg3 = arg3

i really doubt the code works like you think it does for point 2, given how cmd_tokens.as_slice() goes.
We can't have any spaces in the arguments otherwise it'll think it's the environment variable section.

resolved via discord convo, b64 encoded so no spaces


rf-239 Refactor Buttons Bar

Which Issue was this PR made for?

Thanks for the work!

Sorry the linter hook's just been added to the build process so you'd need to fix that: https://github.com/Amijakan/mochatto/blob/main/client/src/components/AvatarCanvas.tsx This is what I've been doing so far, but I personally I think the readability here sucks.
I think it'd be much cleaner to actually import prop-types like so: https://reactjs.org/docs/typechecking-with-proptypes.html and use that
Other than that, LGTM

Fixed the issues, along with a merge conflict. Prop-Types and react types do different things so this needs both (I won't deny it looks weird though).


Update to Gradle 3.5

Depends on
https://github.com/TWCable/gradle-plugin-scr/pull/7
https://github.com/TWCable/gradle-plugin-cq-package/pull/24
https://github.com/TWCable/gradle-plugin-cq-bundle/pull/8

The three PRs referenced above are now resolved.


Bugfix labelrefresh

fixed logic in UserDefaults+Addition to default to 8 ==LTC.  But user can now pick photons/lites/Litecoin in the settings

Would ACK if you could reset (certs) changes to breadwallet.xcodeproj/project.pbxproj.

ACK


Problem with label Caddy Proxy

When deploying Docker Compose, Caddy does not set up config file correctly
 labels:
      caddy: grafana.yuandrk.net
      caddy.reverse_proxy: "{{upstreams 3000}}"
      caddy.header: /*

result:
grafana.yuandrk.net {
	header /*
	reverse_proxy
}

As a result of investigating the problem, it was found that using the stable version of Caddy and creating a Caddyfile with reverse_proxy is a better approach. Next, the plan is to create a bash script to interact with the user/program.