modift operate.py

修改operate.py以解决image变量未定义导致的语义分割测试失败问题
PaddleX/paddlex_restful/restful/project/operate.py中318、320行的image变量未定义，应修改为img

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


Fix broken link caf_foundations landing zone

Fix broken link caf_foundations landing zone

thanks @catay for the fix :)


[DOCFIX] Update code blocks for consistency & added descriptions for storage integrations

What changes are proposed in this pull request?
Updated code blocks from console to shell for all doc pages for consistency & coloring.
Added syntax highlighting for missing code blocks.
Added descriptions for storage integrations.
Added table formatting on some pages for better UI.
Why are the changes needed?
Some code blocks were missing syntax highlighting and not consistent throughout all of docs.
Tables looked odd as plain text, so used table formatting & structure (ie. Documentation Conventions)
Does this PR introduce any user facing changes?
Yes, docs UI

so no use of ```console anywhere?

No, I changed all of them to ```shell, it actually helped fix some code blocks that had random black and gray lines :)

alluxio-bot, merge this please


Prevent kue from accept jobs

We have several 'worker' scripts that run kue jobs, each script is run on a different server.  When we need to do maintenance on a particular server, we'd like to be able to tell that server to stop processing any new jobs.  Is there anyway to do this?

Just to clarify, we don't want to shut down with a timeout, because some jobs may need to continue running for 30min or whatever the case may be, they vary.  We'd want to finish all active jobs, but stop accepting new ones.

we don't want to shut down with a timeout, because some jobs may need to continue running for 30min or whatever the case may be, they vary. We'd want to finish all active jobs, but stop accepting new ones

why aren't you using shutdown( 30min ) ?

have you also looked at the worker pause API?

Yeah, will use shutdown( 5hrs ), kind of an oversight, was thinking it would wait for timeout, even if there's no active.  Thank you


fabric curved text resolution issue

sorry about issue here i don't have any contact of you I tried your solution for curved text and improved it for rendering from json but it add text on 2d context and text will be resterize and when i export canvas it is blurry not like normal fabric text that is crisp can you please help to fix this issue

https://jsfiddle.net/kingjutt1/fu72dozr/5/
check this fiddle and you can export it to see the difference

I know of this issue and I don't know of a solution. Sorry!


Constraint documentation

Description
Individual documentation pages for each baseline constraint included in AaC
Linked Items:
Closes/Fixes/Resolves #XYZ
Added

Describe any new features.

Changed

Describe any changes in existing functionality.

Deprecated

Describe any deprecated features.

Removed

Describe any removed features.

Fixed

Describe any bug fixes.

Security

Describe any security-related changes.

Checklist:

[ ] I updated project documentation to reflect my changes.
[ ] My changes generate no new warnings.
[ ] I updated new and existing unit tests to account for my changes.
[ ] I linked the associated item(s) to be closed.
[ ] I bumped the version.
[ ] I added the labels corresponding to my changes.

Your documentation PR can link to all of the constraint conversion tasks that it is helping to meet to be closed out when that PR gets merged in, remember.
And you need to add an entry to the Added section and confirm your checklist.
And looks like there is a conflict for the parent page, some tweaks have been made there via the main 0.4.0 PR.

A handful of the files you leveraged for your examples have gotten tweaks in the main PR, so you need to make sure to do a pull and confirm the ranges and highlights are still correct. I went through and put a comment on all of the include configurations to help make sure they all get checked.


cancel button text does not trigger click

Click on Cancel (Not X) nothing happens (X does cancel)

Fixed.


[WIP] support same kind annotation

Why we need this PR
This PR will enable the user to select several CUR Templates (of the same kind) when using NHC escalating remediation.
In a nutshell CUR can be used several times as a remediator each time with a different user defined script.
This feature is dependent on the changes in NHC as well (which will be available from NHC 0.8.0).
Changes made

Added a "Defaulting" (Mutating) Webhook to CUR's Template which automatically adds to the template the "Support Same Kind" annotation which NHC detects
Fetching node name from "Node Name" annotation in case it exist instead of always assuming that the Node's name is the CR's name

Which issue(s) this PR fixes
Not tracked in Jira
Test plan

/test openshift-e2e


syscall: Go can leak a forked process if main thread exits before spawn finished

Please answer these questions before submitting your issue. Thanks!
What did you do?
If I spawn a process in a goroutine, and exit the main thread before the spawn is finished, I am sometimes left with a fork of my original process that does not go away. The fork does not respond to SIGTERM, and sometimes consumes 100% CPU.
https://play.golang.org/p/1HPscvoAiwj
What did you expect to see?
If the main thread exits Go should not leave behind a forked process.
What did you see instead?
A forked process, sometimes using 100% CPU
Does this issue reproduce with the latest release (go1.12.7)?
Yes.
System details
go version go1.12.6 darwin/amd64
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/jacobvosmaer/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/jacobvosmaer/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
GOROOT/bin/go version: go version go1.12.6 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.12.6
uname -v: Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.14.6
BuildVersion:	18G87
lldb --version: lldb-1<IP_ADDRESS>
Apple Swift version 5.1 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)

My guess is that when doing a fork+exec, after the fork, the child wants to "communicate" with the parent; perhaps by reading or writing to a pipe. If the parent is gone the child should exit and do nothing. But it appears that with the "right" timing, the child can get stuck in a loop instead.

There are some lldb stack traces that might help here: https://gitlab.com/gitlab-org/gitaly/issues/1850#note_205304016

Can't reproduce on linux.

If the parent is gone the child should exit and do nothing.

I don't believe that is necessarily correct. If a parent exits, the child becomes a zombie and attaches to PID 1. I understand this issue is about cleaning up the child before the spawn has happened completely.
@randall77 for macOS.

I also cannot reproduce on linux.

I understand this issue is about cleaning up the child before the spawn has happened completely.

Yes. In my toy example, I'm trying to spawn /bin/sh which will exit harmlessly on its own accord, even if its parent is gone. The problem is that when this bug strikes, we never get to the exec which creates the /bin/sh process.
I've learned some more about the real life bug that prompted this issue. It seems that there, even if the main goroutine does not exit, we get a stuck forked process. I was able to attach to some of these with lldb, which is what I linked to above. https://gitlab.com/gitlab-org/gitaly/issues/1850#note_205304016
I'm not sure if this is the exact same state as my reproducing example, but it might be related. To save some clicking I'm including stack traces below.

 mystery fork A, 0% CPU
* thread #1, stop reason = signal SIGSTOP
  * frame #0: 0x00007fff7eaee86a libsystem_kernel.dylib`__psynch_cvwait + 10
    frame #1: 0x00007fff7ebad56e libsystem_pthread.dylib`_pthread_cond_wait + 722
    frame #2: 0x00007fff7d1e6467 libobjc.A.dylib`monitor_tt<false>::wait() + 19
    frame #3: 0x00007fff7d1eb462 libobjc.A.dylib`WAITING_FOR_ANOTHER_THREAD_TO_FINISH_CALLING_+initialize + 132
    frame #4: 0x00007fff7d1eb79b libobjc.A.dylib`initializeNonMetaClass + 79
    frame #5: 0x00007fff7d1eb79b libobjc.A.dylib`initializeNonMetaClass + 79
    frame #6: 0x00007fff7d1ec62f libobjc.A.dylib`initializeAndMaybeRelock(objc_class*, objc_object*, mutex_tt<false>&, bool) + 187
    frame #7: 0x00007fff7d1db690 libobjc.A.dylib`lookUpImpOrForward + 228
    frame #8: 0x00007fff7d1db114 libobjc.A.dylib`_objc_msgSend_uncached + 68
    frame #9: 0x00007fff7ebfafa1 libxpc.dylib`xpc_atfork_child + 125
    frame #10: 0x00007fff7b99eb18 libSystem.B.dylib`libSystem_atfork_child + 54
    frame #11: 0x00007fff7ea0fd97 libsystem_c.dylib`fork + 40
    frame #12: 0x00000000010603ff gitaly`runtime.syscall + 31
    frame #13: 0x000000000105dde0 gitaly`runtime.asmcgocall + 112
    frame #14: 0x0000000001033930 gitaly`runtime.startTheWorldWithSema + 624
    frame #15: 0x000000000104d40e gitaly`syscall.rawSyscall + 78
    frame #16: 0x00000000010a21a2 gitaly`syscall.forkAndExecInChild + 226
    frame #17: 0x00000000010a31a0 gitaly`syscall.forkExec + 864
    frame #18: 0x00000000010c4a12 gitaly`os.startProcess + 610
    frame #19: 0x00000000010c449c gitaly`os.StartProcess + 124
    frame #20: 0x0000000001179f9c gitaly`os/exec.(*Cmd).Start + 1180
    frame #21: 0x00000000016805a3 gitaly`gitlab.com/gitlab-org/gitaly/internal/supervisor.(*Process).start + 435

mystery fork B, 100% CPU
* thread #1: tid = 0x43f1b, 0x00007fff7eba3317 libsystem_platform.dylib`_os_once_gate_corruption_abort + 23, stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
(lldb) bt
* thread #1, stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
  * frame #0: 0x00007fff7eba3317 libsystem_platform.dylib`_os_once_gate_corruption_abort + 23
    frame #1: 0x00007fff7eba114c libsystem_platform.dylib`_os_once_gate_wait + 196
    frame #2: 0x00007fff7eb9ea6f libsystem_platform.dylib`_os_alloc_once + 42
    frame #3: 0x00007fff7eb99d2a libsystem_notify.dylib`_notify_fork_child + 211
    frame #4: 0x00007fff7b99eb13 libSystem.B.dylib`libSystem_atfork_child + 49
    frame #5: 0x00007fff7ea0fd97 libsystem_c.dylib`fork + 40
    frame #6: 0x00000000010603ff gitaly`runtime.syscall + 31
    frame #7: 0x000000000105dde0 gitaly`runtime.asmcgocall + 112
    frame #8: 0x0000000001033930 gitaly`runtime.startTheWorldWithSema + 624
    frame #9: 0x000000000104d40e gitaly`syscall.rawSyscall + 78
    frame #10: 0x00000000010a21a2 gitaly`syscall.forkAndExecInChild + 226
    frame #11: 0x00000000010a31a0 gitaly`syscall.forkExec + 864
    frame #12: 0x00000000010c4a12 gitaly`os.startProcess + 610
    frame #13: 0x00000000010c449c gitaly`os.StartProcess + 124
    frame #14: 0x0000000001179f9c gitaly`os/exec.(*Cmd).Start + 1180
    frame #15: 0x0000000001680563 gitaly`gitlab.com/gitlab-org/gitaly/internal/supervisor.(*Process).start + 435

When I lldb the crashing example I don't get nice symbols. Is it possible I messed up a go build command?

I would also give 1.13rc1 a shot, just to be sure that it is not something already fixed. Keith can probably comment more on what exactly is happening.

it should be possible to write a similar test case in C. Anybody want to try that?

It's the sort of challenge I enjoy so I'll take a look. But a person familiar with Go internals would be much faster at it than me. I won't be offended if such a person swoops in and beats me to it.

OK that was not hard. Just translated my Go example to C.
https://gist.github.com/jacobvosmaer/69fae756e88d2f5f4ef5091ceeba1d88
As before, leave it running for a while in a restart loop, and you get a weird forked process left behind.

The C reproducer highlights how odd this is even more: all it tries to do is fork followed by exit, yet the leaking forked processes are not exiting.

Thanks!
Does anybody want to try to report this to Apple?
To fix this in Go I think it would suffice to have exit in runtime/sys_darwin.go acquire a write lock on syscall.ForkLock.  Unfortunately that will be a bit of a hassle since the runtime package doesn't depend on the syscall package, and since syscall.ForkLock is exported it can't move.

It really does feel like a macOS bug. With my C reproducer, if I leave it running it leaks way more processes than the Go one. Most of the leaked processes are at 0% CPU instead of 100% CPU.
* thread #1, stop reason = signal SIGSTOP
  * frame #0: 0x00007fff6d67ef06 libsystem_kernel.dylib`__psynch_mutexwait + 10
    frame #1: 0x00007fff6d73bd52 libsystem_pthread.dylib`_pthread_mutex_firstfit_lock_wait + 96
    frame #2: 0x00007fff6d7394cd libsystem_pthread.dylib`_pthread_mutex_firstfit_lock_slow + 222
    frame #3: 0x00007fff6d5ed2b4 libsystem_c.dylib`__cxa_finalize_ranges + 36
    frame #4: 0x00007fff6d5ed6b3 libsystem_c.dylib`exit + 55
    frame #5: 0x0000000106b09e21 fork-leak`do_fork + 33
    frame #6: 0x00007fff6d73b2eb libsystem_pthread.dylib`_pthread_body + 126
    frame #7: 0x00007fff6d73e249 libsystem_pthread.dylib`_pthread_start + 66
    frame #8: 0x00007fff6d73a40d libsystem_pthread.dylib`thread_start + 13

What is particularly worrying here is that after I remove the leaked processes with kill -9, some part of the system (kernel? userspace kernel helper?) keeps spinning the CPU. It shows in the activity monitor as constant "system" load. I can only get rid of that by rebooting.

I don't feel confident reporting this to Apple for a number of reasons:

I don't have enough experience with C and Unix programming to stand behind my C reproducer
I don't know to what extent the C reproducer matches the behavior of the Go runtime: even if the C reproducer is proof of a macOS bug, do we know if it's the same bug I see in Go?

If they respond to my C reproducer by saying "your code is wrong" or "you should use posix_spawn" then I have nothing to say to that.

I don't feel confident reporting this to Apple for a number of reasons:

I don't have enough experience with C and Unix programming to stand behind my C reproducer
I don't know to what extent the C reproducer matches the behavior of the Go runtime: even if the C reproducer is proof of a macOS bug, do we know if it's the same bug I see in Go?

If they respond to my C reproducer by saying "your code is wrong" or "you should use posix_spawn" then I have nothing to say to that.

That's certainly true. But we are still making progress even if Apple proved we were doing wrong, isn't it?

I tried various methods. Can we reslove?
Process 38893 stopped
* thread #1, stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
    frame #0: 0x00007fff731566b9 libsystem_platform.dylib`_os_once_gate_corruption_abort + 23
libsystem_platform.dylib`_os_once_gate_corruption_abort:
->  0x7fff731566b9 <+23>: ud2

libsystem_platform.dylib`_os_lock_recursive_abort:
    0x7fff731566bb <+0>:  movl   %edi, %eax
    0x7fff731566bd <+2>:  leaq   0x7d1(%rip), %rcx         ; "BUG IN CLIENT OF LIBPLATFORM: Trying to recursively lock an os_lock"
    0x7fff731566c4 <+9>:  movq   %rcx, 0x2651c3ad(%rip)    ; gCRAnnotations + 8
Target 0: (bit) stopped.

* thread #1, stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
  * frame #0: 0x00007fff731566b9 libsystem_platform.dylib`_os_once_gate_corruption_abort + 23
    frame #1: 0x00007fff73152feb libsystem_platform.dylib`_os_once_gate_wait + 196
    frame #2: 0x00007fff73150f89 libsystem_platform.dylib`_os_alloc_once + 42
    frame #3: 0x00007fff73038c75 libsystem_coreservices.dylib`_libcoreservices_fork_child + 78
    frame #4: 0x00007fff6ff40aa9 libSystem.B.dylib`libSystem_atfork_child + 44
    frame #5: 0x00007fff72fba8ad libsystem_c.dylib`fork + 40
    frame #6: 0x000000000106f73f bit`runtime.syscall + 31
    frame #7: 0x000000000106d5b0 bit`runtime.asmcgocall + 112
    frame #8: 0x000000000103c8c0 bit`runtime.startTheWorldWithSema + 576
    frame #9: 0x000000000106a86c bit`syscall.rawSyscall + 76
    frame #10: 0x00000000010afca6 bit`syscall.forkAndExecInChild + 230
    frame #11: 0x00000000010b0eb8 bit`syscall.forkExec + 1080
    frame #12: 0x00000000010da23b bit`os.startProcess + 667
    frame #13: 0x00000000010d9c3c bit`os.StartProcess + 124
    frame #14: 0x0000000001342505 bit`os/exec.(*Cmd).Start + 1317
    frame #15: 0x0000000001341f6b bit`os/exec.(*Cmd).Run + 43
    frame #16: 0x0000000001343171 bit`os/exec.(*Cmd).CombinedOutput + 145

For the C reproducer in https://github.com/golang/go/issues/33565#issuecomment-525877539 , I can reproduce on macOS. I can also reproduce it on Linux, with even a much higher rate of leaking children. It seems the child stuck at exit call:
#0  __lll_lock_wait_private (futex=futex@entry=0x7f0507afaae8 <__exit_funcs_lock>) at ./lowlevellock.c:35
#1  0x00007f05079785f8 in __run_exit_handlers (status=0, listp=0x7f0507af8718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:56
#2  0x00007f050797867a in __GI_exit (status=<optimized out>) at exit.c:139
#3  0x0000561c884091d5 in do_fork ()
#4  0x00007f0507b07ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#5  0x00007f0507a37def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

If we exec instead of exit in child, it doesn't seem to stuck. So it may be a different issue. The original bug seems that it stuck at the fork call instead of exit.

This may be similar to #53863 ? (which is a macOS system bug and may be fixed in a future macOS version.)

I am getting these unkillable processes in the os/exec test during all.bash pretty reliably. Here is a stack trace from one:
* thread #1, stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
  * frame #0: 0x00007ff801638f85 libsystem_platform.dylib`_os_once_gate_corruption_abort + 23
    frame #1: 0x00007ff8016347c1 libsystem_platform.dylib`_os_once_gate_wait + 212
    frame #2: 0x00007ff8016327e9 libsystem_platform.dylib`_os_alloc_once + 42
    frame #3: 0x00007ff804089144 libsystem_notify.dylib`_notify_fork_child + 349
    frame #4: 0x00007ff80c41ac89 libSystem.B.dylib`libSystem_atfork_child + 58
    frame #5: 0x00007ff80151382d libsystem_c.dylib`fork + 84
    frame #6: 0x000000000106d55f exec.test`runtime.syscall.abi0 + 31
    frame #7: 0x000000000106b3e4 exec.test`runtime.asmcgocall.abi0 + 100
    frame #8: 0x000000000106824b exec.test`syscall.rawSyscall + 139
    frame #9: 0x00000000010771b0 exec.test`syscall.forkAndExecInChild + 240
    frame #10: 0x0000000001077f5f exec.test`syscall.forkExec + 863
    frame #11: 0x000000000109b992 exec.test`os.startProcess + 818
    frame #12: 0x000000000109b59a exec.test`os.StartProcess + 90
    frame #13: 0x00000000010ffb0e exec.test`os/exec.(*Cmd).Start + 1518
    frame #14: 0x00000000012d5045 exec.test`os/exec_test.TestEchoFileRace + 165
    frame #15: 0x00000000010ecaab exec.test`testing.tRunner + 267
    frame #16: 0x00000000010edaca exec.test`testing.(*T).Run.func1 + 42
    frame #17: 0x000000000106b5c1 exec.test`runtime.goexit.abi0 + 1

Is there anything we can do?

I am getting these unkillable processes in the os/exec test during all.bash pretty reliably. Here is a stack trace from one:
* thread #1, stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
  * frame #0: 0x00007ff801638f85 libsystem_platform.dylib`_os_once_gate_corruption_abort + 23
    frame #1: 0x00007ff8016347c1 libsystem_platform.dylib`_os_once_gate_wait + 212
    frame #2: 0x00007ff8016327e9 libsystem_platform.dylib`_os_alloc_once + 42
    frame #3: 0x00007ff804089144 libsystem_notify.dylib`_notify_fork_child + 349
    frame #4: 0x00007ff80c41ac89 libSystem.B.dylib`libSystem_atfork_child + 58
    frame #5: 0x00007ff80151382d libsystem_c.dylib`fork + 84
    frame #6: 0x000000000106d55f exec.test`runtime.syscall.abi0 + 31
    frame #7: 0x000000000106b3e4 exec.test`runtime.asmcgocall.abi0 + 100
    frame #8: 0x000000000106824b exec.test`syscall.rawSyscall + 139
    frame #9: 0x00000000010771b0 exec.test`syscall.forkAndExecInChild + 240
    frame #10: 0x0000000001077f5f exec.test`syscall.forkExec + 863
    frame #11: 0x000000000109b992 exec.test`os.startProcess + 818
    frame #12: 0x000000000109b59a exec.test`os.StartProcess + 90
    frame #13: 0x00000000010ffb0e exec.test`os/exec.(*Cmd).Start + 1518
    frame #14: 0x00000000012d5045 exec.test`os/exec_test.TestEchoFileRace + 165
    frame #15: 0x00000000010ecaab exec.test`testing.tRunner + 267
    frame #16: 0x00000000010edaca exec.test`testing.(*T).Run.func1 + 42
    frame #17: 0x000000000106b5c1 exec.test`runtime.goexit.abi0 + 1

Is there anything we can do?

try refactor code async logic to sync or before syscall wait async code finish.  I guess maybe when after syscall forked. they will inherit parent process and parent process is  in async state. the child process memory is dirty

I have a fix for the Go stacks that were reported in this issue. I am not as sure about the C reproducer - it may be that it tickles a different fork+exec bug in Apple libc.


Generate performance report even if previous builds are still running

Fixes JENKINS-26515

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


Make (most of) flow flags pass pipeline options.

For the differen CPU/GPU architectures, different options are used for
creating dispatch region formation. While we want to reduce the number
of such configurations, these options represent things that are
WIP. Having LLVM options make these non-reproducible. So making them
pass pipeline options.
Changing the benchmark configuration to use this flags instead.

@hanhanW  please take a look at the changes to the benchmark configuration if they make sense to you

There are some other benchmark configuration here: https://github.com/google/iree/blob/main/iree/benchmark/TensorFlow/CMakeLists.txt
You probably need -DIREE_BUILD_BENCHMARKS=ON with cmake configuration if you want to build it locally.

Update on this PR based on some offline discussions. We might not need options on the flow pipeline at all. Closing this PR for now. Will revisit at a later point after some new infra that Ben is putting in place.


Evaluate physicist's Hermite polynomial

Resolves #128 .

Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines, including the relevant style guides.
[x] Read and understand the Code of Conduct.
[x] Read and understood the licensing terms.
[x] Searched for existing issues and pull requests before submitting this pull request.
[x] Filed an issue (or an issue already existed) prior to submitting this pull request.
[x] Rebased onto latest develop.
[x] Submitted against develop branch.

Description

What is the purpose of this pull request?

This pull request:

Adds physicist's Hermite polynomial functionality to math/base/tools/hermitepoly

Related Issues

Does this pull request have any related issues?

This pull request:

resolves #128

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

@stdlib-js/reviewers

Oh man, I wish I had saved those build instructions for the SVG.  I'm going to look through some of the Makefiles later and refresh my memory.  Last time, I went through the process there was an issue with the URL - after I generate the SVG will you run the command to generate the URL?

@jrreed83 Yes, all you need to do is generate the SVG. I will update the src URL after merge so that it points to the project repository. Here is the file containing the Makefile command: https://github.com/stdlib-js/stdlib/blob/develop/tools/make/lib/markdown/equations.mk#L122. The command you want to run is
$ make markdown-svg-equations MARKDOWN_FILTER=.*/hermitepoly/.*

Ok.  I added the equation svg.  Thanks for pointing to that line in the make file.

@jrreed83 Thanks! And no worries. Admittedly, development tooling documentation is a bit lacking, but, hopefully, I'll be able to allocate some time to remedying this deficiency.

Thanks!  That documentation sounds like a lot of fun.  In all seriousness though, if there's anyway to help with that too, I'm game.


Airswap Update

Add Airswap to the DEX subsection
Add bounty emails

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

Is this list still actively

Hi @ejwessel, thank you for your contribution!


[Feature-Request] Depth image compression by colorization

Start with the why:
VideoEncoder only supports NV12 or GRAY8 format. It cannot be used to encode depth images, only disparity images with subpixel disabled. This creates a big headache for us with PoE models. We hope to be able to transmit depth images with high resolution, high precision and high frame rate. The approach presented in this RealSense white paper seems promising. Hope it works for OAK cameras.
Move to the what:
Add depth image compression by colorization feature.
Move to the how:
The basic idea is to colorize the 16-bit depth image or disparity image according to the method mentioned in the white paper. Then use VideoEncoder for compressed transport. The recovery part on the Host side should be relatively easy to implement. The main feature that needs to be added is colorization on the camera. Currently ImageManip does not support color conversion of 16-bit images. Perhaps this particular color conversion method should be added to ImageManip, or implemented elsewhere.

Any plan for this? It should be possible to create a custom blob and use the new Cast node. But if you can add this to ImageManip node, I'll now waste time on this.

CC: @moratom on whats the applicability on RVC2

If we use disparityWidth of 96 and subpixelFractionalBits of 4, the max disparity should be 1520. This colorization method provides 1529 discrete levels. So there should be no quantization error, and normalization step might be skipped.

Another solution is to use the RVL depth image compression algorithm. RVL codec has been added to ROS since Noetic/Jazzy. We are also considering adding it to RTAB-Map.


Domain activation is Failed - Unable to add Subdomains with a domain name hosted in another AWS account.

App Id: d2uz048gh5b550
Region: eu-west-1
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
Hey Amplify Team
Hope you are doing great!
I am trying to configure a multi-account AWS setup for an app hosted in Amplify.
Currently, we've got 3 accounts test/dev/prod with separate Amplify apps for each env.
We are trying to create subdomains for Apps hosted in each account, i.e testing.domain.io --> testing acc, dev.domain.io --> dev, domain.io --> prod
The domain name is added to the Route53 in our main acc.
As described here: https://github.com/aws-amplify/amplify-console/issues/22 I was able to configure the domain name for the testing app by exclluding root and removing the www cname. However, when I try to add the "testing.domain.io" subdomain I get an error "Update domain association failed".
I have also tried to add a random name as a cname just for tests with no luck.
Error message
"Update domain association failed"
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.


Use memory pool for receiving QUICStreamFrame

Currently we allocate QUICStreamFrame instances with simple new statement on receiving side, but we should probably avoid this and use some memory pool.
We need to think about how much amount of memory we need / allow to use for this.

Flow Control

It is necessary to limit the amount of data that a receiver could
buffer, to prevent a fast sender from overwhelming a slow receiver,
or to prevent a malicious sender from consuming a large amount of
memory at a receiver.  To enable a receiver to limit memory
commitment to a connection and to apply back pressure on the sender,
streams are flow controlled both individually and as an aggregate.  A
QUIC receiver controls the maximum amount of data the sender can send
on a stream at any time, as described in Section 4.1 and Section 4.2

21.4.  Slowloris Attacks
The attacks commonly known as Slowloris [SLOWLORIS] try to keep many
connections to the target endpoint open and hold them open as long as
possible.  These attacks can be executed against a QUIC endpoint by
generating the minimum amount of activity necessary to avoid being
closed for inactivity.  This might involve sending small amounts of
data, gradually opening flow control windows in order to control the
sender rate, or manufacturing ACK frames that simulate a high loss
rate.

Would you be interested in using something like MemArena? See here. This is quite a bit updated from what's in the TS code base.

Yes. MemArena is a candidate for this. Though I haven't read the documentation, I'm not sure which allocator I should use. I read the code and I found that MemArena uses malloc internally, which we usually avoid, right?
It would be great if there was a comparison table like:

64KB
1KB - 1MB
1MB

Allocator A
Best
OK
Don't

Allocator B
OK
OK
Best

Allocation frequency and lifetime would be other perspectives.

Closing as we are dropping our own QUIC implementation.


Is there any way to change the box border thickness?

Hello,
I want to achieve OTP Input like this:

Is there any way to change the Border Thickness?
Regards,
Gunpal Jain

@gunpal5 : Thanks for suggesting. Unfortunately you can not customize Border Thickness in this control. But, I will surely add it to a roadmap for .NET Maui control.
https://github.com/MGohil/PINView.Maui

@gunpal5 : In .NET Maui PINView control, you can now set the BoxBorderThickness, if you are planning to migrate from Xamarin.Forms to .NET Maui.


Add a 10 minute delay to surveys

For #5261
Also update the threshold and disable times for native and webviews

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #5596 (cdb8faf) into main (3c7e93c) will increase coverage by 2%.
The diff coverage is 76%.

@@          Coverage Diff           @@
##            main   #5596    +/-   ##
======================================
+ Coverage     70%     73%    +2%
======================================
  Files        402     402
  Lines      26721   26734    +13
  Branches    3897    3904     +7
======================================
+ Hits       18832   19527   +695
+ Misses      6300    5564   -736
- Partials    1589    1643    +54

Impacted Files
Coverage Δ

src/client/datascience/dataScienceSurveyBanner.ts
79% <76%> (+10%)
:arrow_up:

...ent/datascience/jupyter/jupyterExecutionFactory.ts
66% <0%> (-6%)
:arrow_down:

src/client/datascience/jupyter/jupyterExecution.ts
64% <0%> (-5%)
:arrow_down:

src/client/datascience/jupyter/serverPreload.ts
78% <0%> (-3%)
:arrow_down:

...er/jupyterInterpreterSubCommandExecutionService.ts
85% <0%> (-2%)
:arrow_down:

...science/jupyter/kernels/kernelDependencyService.ts
86% <0%> (-2%)
:arrow_down:

src/client/common/process/pythonDaemonFactory.ts
82% <0%> (-2%)
:arrow_down:

...tascience/jupyter/liveshare/hostJupyterNotebook.ts
44% <0%> (-2%)
:arrow_down:

...ience/interactive-common/notebookServerProvider.ts
74% <0%> (-1%)
:arrow_down:

src/client/common/utils/decorators.ts
77% <0%> (-1%)
:arrow_down:

... and 72 more


Feature request: Fleet server

Hi
I believe my request is far beyond the original scope of your project, but I consider this GitHub repo as a great start for elastic developers.
Adding a fleet server to the docker compose would be awesome

Hey, @l4t3b0!  I'm actively working on "Part Two" of that blog post which will build on top of this one.  It will include things like Fleet Server and Agent setup, along with other Integrations, APM, and additional features.

Sounds great 🥳
When can we expect that?

Eagerly waiting for the Fleet Server and Agent setup. Generating service token and incorporating it into docker-compose.yml without restarting the containers is a bit challenging at the moment.

@l4t3b0 , @captain-hindsightt  - I just found that another team at Elastic has done a similar project last year and has a container approach that includes Fleet/Agent already.  Check out https://www.elastic.co/security-labs/the-elastic-container-project and see if that will help you in the meantime!

@elkninja Thanks for the update, I will definitely check it out. ✌


Minimal PyTorch test

Signed-off-by: Luca Giorgi<EMAIL_ADDRESS>

This cannot currently be tested since the spawning of the image is blocked

PR test:
https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/98/

Fixed the import error in the PR test.
New PR test:
https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/100/

PR test job: https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/204/

Unexpected failures, rerunning: https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/206/

PR test here: https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/208/
Last run was aborted due to issues with the user's PVC

Rerunning, still issues with the PVC: https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/211/

Pr test: https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhods-ci-pr-test/150/
Same deal as #69, I'd like to get some reviews here before merging.
@vasukulkarni @jgarciao @bdattoma @pablofelix @aloganat @LaVLaS

Previous run hit some Jenkins config issue, latest run here: https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhods-ci-pr-test/151

closing in favor of #69


[Open Legend] Character sheet doesn't allow for invisible GM rolls

There is currently no option to use the roll macros on character sheets and make them invisible to players.

1st) Which Open Legend sheet do you mean, though I don't think either one does this (nor a lot of charactersheets)

there isn't a lot of need for it in most cases, though for the sheet I have considered it, but it isn't a priority right now

This isn't really an issue, but a feature request, see: https://community.openlegendrpg.com/t/roll20-character-sheet/162

The charactersheet on Roll20 simply named "Open Legend", we're not using the minimalist one.
While it's perfectly possible to GM the game without it, it would make fudging the numbers as the GM a lot easier.
My apologies, it's my first time using these channels.

For #3, no worries, just harder for a person that works on sheets to see issues posted here unless the author is mentioned/pinged, hence why it took me 25 days to notice it.
For #2, not a personal fan of fudging numbers, BUT, I understand some people want to. I was planning to implement a way to send various rolls to the GM, though not for fudging, for players that want to do something without the party knowing about it. It of course can be used by the GM in a similar fashion.
I'll actually be working on the sheet some over the next 2 weeks, though I will probably be working on other things first, so not sure If I'll get something implemented for GM rolls this stretch, but possibly after I get back from my next trip.
Again, feel free to post in the forum topic I linked above, I take lots of requests there, and it will help remind me.


libswift: fixes and improvements for the bootstrapping build

fix some missing dependencies in the bootstrapping build mode
improve the bootstrapping-with-hostlibs build mode: this reduces the build time overhead from 3min -> 30seconds.

For details see the commit messages

@swift-ci smoke test


Distinguish between a Wallet's Locked and Unlocked states

This PR was motivated by work @kayagokalp and I are doing on the
following:
https://github.com/FuelLabs/sway/issues/2413
We noticed that in order to perform any operations using a Wallet, the
private key must be known, even if those operations were simply
retrieving asset balances or a list of transactions.
This PR aims to draw a clearer distinction between Wallet methods that
require access to a private key and those that do not. The idea is to
encourage users of the API to be conscious of when their wallet is in an
unlocked state (i.e. their private key resides in memory) and when it
does not.
To achieve this, we turn Wallet into a session type, parameterised
over its state which can be either Locked or Unlocked.
The default state is Locked in the case that the parameter is not
specified for Wallet or LocalWallet, meaning that if users require
holding the wallet in an unlocked state they must specify the type
explicitly, e.g. Wallet<Unlocked>. I think this explicitness can
assist us in maintaining awareness of the state of the wallet that we
require in our downstream APIs.
Users should generally prefer using the Wallet in a locked state (the
default) and should ideally only unlock the wallet for the duration
that they need to perform operations requiring the private key. Users
can now construct a Wallet in a Locked state, e.g.
Wallet::from_address(public_addr, provider) and access the various
useful read-only operations without knowing the private key or having it
stored in memory.
As a follow-up to this work, we should take a closer look at the usage
of LocalWallet in downstream crates (including fuels-contract) to
see if we can refactor these to use the wallet in a Locked state more
often, only moving into the Unlocked state when absolutely necessary.

I really like this idea, and the API seems very friendly and nice, from a quick glance. I'm still reviewing the details though. One thing is that we should definitely document the new terms introduced here (Locked and Unlocked) and what they mean, etc., in the SDK book, somewhere in here.

OK, this should be good to go!
@digorithm thanks for the feedback, and good point about updating the docs! I've added a new "Wallet Access" chapter that should cover the new behaviour and terminology.

Love the type safety.
Beautifully done. I see only one potential downside to way this is implemented:
If I have a function:
fn something(a_wallet: &LocalWallet<Locked>) {
}

But only have an unlocked wallet at my disposal I'd have to call lock on it -- destroying it in the process:
something(&unlocked_wallet.lock());
// unlocked_wallet cannot be used anymore

so that would mean users would have to either keep locked&unlocked versions or clone on demand:
let locked_wallet = unlocked_wallet.clone().lock();
something(&locked_wallet);
// can still use unlocked_wallet

This can be solved by implementing AsRef:
impl AsRef<Wallet<Locked>> for Wallet<Unlocked> {
    fn as_ref(&self) -> &Wallet<Locked> {
    }
}

Which would enable users to do:
something(unlocked_wallet.as_ref());

or would enable us to do:
fn something<T: impl AsRef<LocalWallet<Locked>>>(locked_wallet: &T){
}

which could then be called as
something(&unlocked_wallet);

But implementing AsRef isn't straightforward since a Wallet<Unlocked> doesn't really contain a Wallet<Locked> which you can just return by reference. So that would mean that you would have to have Wallet<Unlocked> delegate everything that doesn't need the private key to an enclosed Wallet...
But this isn't such a big problem since you can still say:
fn something<T>(a_wallet: &T){
}

and would get only the functionality that is common between locked and unlocked wallets -- i.e. effectively only what a locked wallet can do. It's a bit more roundabout way of saying Wallet<Locked>. Also, the generic T will corrupt everything we might pass the wallet to, requiring that the function be generic over T as well -- since you don't actually get to call lock on Wallet<T>. This also might cause problems down the line if we should get a third specialization but we'll worry about that when we come to it.
That rubs me a bit wrong but I can live with it seeing as this is a very elegant solution.

That's a good point, but I personally don't see why we would have more functions specifically defined only for Locked wallets other than the current proposed ones (created Locked and lock()). Shouldn't any behavior that should be acceptable by the Locked wallets should also be acceptable by Unlocked ones, therefore defined inside the generic T impl?
I spent a whopping whole 3 minutes (😂 ) trying to think of a use case that goes against this but couldn't find it. I say we move on as-is, and if such a use case comes up, we could introduce more special-casing to handle it, as you mentioned.

Keep in mind that functions like fn something can take a wallet in any state too in the case that we don't mind what state it's in e.g.:
fn something<T>(wallet: &Wallet<T>) {
}

The only method that Wallet<Locked> implements that Wallet<T> does not is the lock method, so it's almost always worth taking a &Wallet<T> in the case that you don't require signing anything.

Thinking on this a little further, perhaps a nicer abstraction might be:
pub struct Wallet {
    address: Bech32Address,
    provider: Option<Provider>,
}

pub struct WalletUnlocked {
    wallet: Wallet,
    private_key: SecretKey,
}

This way, we could have WalletUnlocked deref to its inner Wallet type, meaning Wallet methods can always be called on WalletUnlocked (though not vice versa).
It would also allow us to call functions like fn something(wallet: &Wallet) { ... } with both unlocked  and locked wallets, e.g. something(&unlocked_wallet), something(&wallet) would both be valid. This way we also wouldn't have to worry about the generic state input type when we want our functions to generalise over wallet states.
I might have a go at this now as I imagine it'll be quite a bit less fancy, more ergonomic and simpler to create APIs for!

I've pushed two more commits with a simpler solution as described in the second half of this comment.
The new solution still uses session types to clearly distinguish wallet access, but we do so in a manner that does not require a generic state type parameter over a single Wallet type. This should make it easier to create ergonomic, safe-by-default APIs, e.g.
fn list_assets(wallet: &Wallet) { ... }

The list_assets function can be called with instances of either Wallet or WalletUnlocked, as WalletUnlocked derefs to its inner Wallet.
This should help to avoid the potential API design footgun highlighted by @segfault-magnet above, where a user may have "accidentally" designed their APIs only accepting a locked wallet (due to Locked being the default state type), which would halve caused issues for users that need to retain access to their wallet in an unlocked state.

OK, just rebased onto master and addressed the associated clippy errors!


Appstudio update test-component-pac-zbwo

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-zbwo-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
23 seconds
clone-repository

✅ Succeeded
39 seconds
sast-snyk-check

✅ Succeeded
24 seconds
appstudio-configure-build

✅ Succeeded
1 minute
build-container

✅ Succeeded
11 seconds
sanity-inspect-image

✅ Succeeded
15 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
14 seconds
clair-scan

✅ Succeeded
17 seconds
sbom-json-check

✅ Succeeded
11 seconds
sanity-label-check

✅ Succeeded
12 seconds
sanity-optional-label-check

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-zbwo-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
appstudio-init

✅ Succeeded
9 seconds
clone-repository

✅ Succeeded
16 seconds
appstudio-configure-build

✅ Succeeded
18 seconds
sast-snyk-check

✅ Succeeded
28 seconds
build-container

✅ Succeeded
19 seconds
deprecated-base-image-check

✅ Succeeded
18 seconds
sanity-inspect-image

✅ Succeeded
44 seconds
clamav-scan

✅ Succeeded
12 seconds
clair-scan

✅ Succeeded
22 seconds
sbom-json-check

✅ Succeeded
11 seconds
sanity-label-check

✅ Succeeded
11 seconds
sanity-optional-label-check

✅ Succeeded
7 seconds
show-summary


[1671] Course fee improvements

Context
Users are currently unable to save the empty string value on the course fee fields.
Changes proposed in this pull request
Mark fee attributes on course as strings
This prevents json_api_client from typecasting a valid value of '' (empty string) to 0, which are two separate values in our system. It also removes some weird behaviour, like how 9,000.00 is cast to 9.
We should revisit our own (or rather, now lack of any) casting and validations to make sure we're doing as much work as we can so that users don't constantly bump into "X is not a number" type errors when they type reasonable values like £9,000.00.
Use text_fields instead of number_fields
The Design System encourages using input type='text' for currency values. While it is not specifically stated, it is because type='number' introduces potential accessibility issues.
Guidance to review
No tests as it feels like those would be testing the web platform and json_api_client respectively.

 Saving an empty fee gets converted to 0


Updates

In the Vagrant VMs, prefer IPv4 DNS results over IPv6.
Remove EPEL repo checks since we install them and therefore
know they are present.
Use CentOS extras repo only in the manager install.
Move pre-test installation of repos from all integration tests
to just EFS test since SSI wil gain those repos from storage
server deployment now.
Signed-off-by: Brian J. Murrell<EMAIL_ADDRESS>

Thought about this, how do we want to work with offline installs in this scenario?

Thought about this, how do we want to work with offline installs in this scenario?

Didn't we discuss that the complications that offline installs cause are not limited to IML and that however the user solves the problem for other "addon" repos (internal mirroring, etc.) will apply to IML's repos equally?
We also discussed creating a new job/process for building the traditional "contains everything" tarball again.  That of course would resolve this issue, for initial installation at least.  This would be a solution parallel to the O/S distribution ISO that users can install from without Internet access.
But even once a user does such an offline ISO installation, they still need access to online update repos.  So once again, however they resolve that issue, they can apply the same solution to the IML repos.

Can one of the admins verify this patch?

Can one of the admins verify this patch?


rbenv fails to install 2.6.1 on macOS Mojave 10.14.5 (error: something wrong with CFLAGS)

I've tried several workarounds for this, but can't make any headway. I keep running into the following error when I attempt to install ruby 2.6.1 (and various other versions) with rbenv: configure: error: something wrong with CFLAGS="-I/usr/local/include -L/usr/local/lib -O3 -Wno-error=shorten-64-to-32  "
I've tried to uninstall/reinstall rbenv and various other packages. I've attempted various workarounds proposed online, but none have helped so far.
Terminal output:
~/Dev/donorsee-v1/donorsee-api $ xcode-select -p
/Library/Developer/CommandLineTools
~/Dev/donorsee-v1/donorsee-api $ rbenv install 2.6.1
ruby-build: use openssl from homebrew
Downloading ruby-2.6.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.6/ruby-2.6.1.tar.bz2
Installing ruby-2.6.1...
ruby-build: use readline from homebrew

BUILD FAILED (OS X 10.14.5 using ruby-build 20190423)

Inspect or clean up the working tree at /var/folders/mj/bl1z76wj4_qdn_49qmn73bv00000gn/T/ruby-build.20190624211944.83911
Results logged to /var/folders/mj/bl1z76wj4_qdn_49qmn73bv00000gn/T/ruby-build.20190624211944.83911.log

Last 10 log lines:
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for cd using physical directory... cd -P
checking whether CFLAGS is valid... no
configure: error: something wrong with CFLAGS="-I/usr/local/include -L/usr/local/lib -O3 -Wno-error=shorten-64-to-32  "
make: *** No targets specified and no makefile found.  Stop.
~/Dev/donorsee-v1/donorsee-api $ brew uninstall apple-gcc42
Error: No such keg: /usr/local/Cellar/apple-gcc42

Full log:
/var/folders/mj/bl1z76wj4_qdn_49qmn73bv00000gn/T/ruby-build.20190624211944.83911/ruby-2.6.1 /var/folders/mj/bl1z76wj4_qdn_49qmn73bv00000gn/T/ruby-build.20190624211944.83911 ~/Dev/donorsee-v1/donorsee-api
checking for ruby...   Stop.

As was true for others, the issue I was running into had something to do with how C had been installed and/or which C library/include files were being referenced. I had CFLAGS defined in the following way to support a different, Python-based project:
# location of C include files and lib files
#   This is sometimes needed when pip uses C compiler.
export CFLAGS="-I/usr/local/include -L/usr/local/lib"

Once I removed the CFLAGS definition from my .bashrc file and reset my terminal, I was able to use rbenv to install Ruby 2.6.1. I'll still need to figure out how to make that Python-based project co-exist with my Ruby projects, but at least I can move forward with installing Ruby.

@bcarradini Thank you for the update! 🙇

This was the issue for me! Thanks for following up with the it - saved me a ton of time.

I do NOT have CFLAGS set but rbenv init still complains
CFLAGS=" -O3 -Wno-error=shorten-64-to-32  "
On my mac(11.6) clang has -Wa -Wl and -Wp.  I see nothing about no-error


"Modules"-"Tools"-"Writing a new tool"-"Implementing the Tool class"-"Advanced" has issue

Describe the bug
Executing the example tool in "Modules"-"Tools"-"Writing a new tool"-"Implementing the Tool class"-"Advanced" errors with the following the error message.
node:internal/modules/run_main:129
    triggerUncaughtException(
    ^

[ToolError: Tool "OpenLibrary" has occurred an error!] {
  isFatal: false,
  isRetryable: true,
  context: { input: { title: 'Hrry Potter' }, options: undefined },
  [errors]: [
    TypeError: Request with GET/HEAD method cannot have body.
        at node:internal/deps/undici/undici:13178:13
        at async OpenLibraryTool._run (/Users/akihikokuroda/development/repositories/i-am-bee/bee-agent-framework/examples/tools/custom/openLibrary.ts:59:22)
        at async Object.executor (/Users/akihikokuroda/development/repositories/i-am-bee/bee-agent-framework/src/tools/base.ts:222:19)
        at async pRetry.retries (/Users/akihikokuroda/development/repositories/i-am-bee/bee-agent-framework/src/internals/helpers/retryable.ts:168:16)
        at async handler (/Users/akihikokuroda/development/repositories/i-am-bee/bee-agent-framework/src/internals/helpers/retry.ts:48:14)
        at async pRetry (/Users/akihikokuroda/development/repositories/i-am-bee/bee-agent-framework/src/internals/helpers/retry.ts:71:10)
  ]
}

To Reproduce
Copy past the example in a xxx.ts file.
Add the following lines at the end.
const tool = new OpenLibraryTool();
const result = await tool.run({
  title: "Harry Potter",
});
console.log(result.getTextContent());

Expected behavior
It shows some response without error.
Screenshots / Code snippets
Set-up:
Additional context
The OpenLibrary site is always down for me so it doesn't matter to fix this issue or replace with different example.
The openLibraryTool example in the bee-community-tools` repository is doesn't have this issue.

Fixed. Thank you for the the report.


btrbk: 0.32.0 -> 0.32.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for btrbk is: "A backup tool for btrfs subvolumes"
meta.homepage for btrbk is: "https://digint.ch/btrbk"
meta.changelog for btrbk is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/5iqjz7jxk3ysislwjwqvr5r4lbc6yqjd-btrbk-0.32.1/bin/.btrbk-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/5iqjz7jxk3ysislwjwqvr5r4lbc6yqjd-btrbk-0.32.1/bin/btrbk had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/5iqjz7jxk3ysislwjwqvr5r4lbc6yqjd-btrbk-0.32.1/bin/lsbtr had a zero exit code or showed the expected version
0 of 3 passed binary check by having a zero exit code.
0 of 3 passed binary check by having the new version present in output.
found 0.32.1 with grep in /nix/store/5iqjz7jxk3ysislwjwqvr5r4lbc6yqjd-btrbk-0.32.1
found 0.32.1 in filename of file in /nix/store/5iqjz7jxk3ysislwjwqvr5r4lbc6yqjd-btrbk-0.32.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
btrbk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5iqjz7jxk3ysislwjwqvr5r4lbc6yqjd-btrbk-0.32.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A btrbk https://github.com/r-ryantm/nixpkgs/archive/3b25e846f2fac1134a553b76328c1656250f967e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5iqjz7jxk3ysislwjwqvr5r4lbc6yqjd-btrbk-0.32.1
ls -la /nix/store/5iqjz7jxk3ysislwjwqvr5r4lbc6yqjd-btrbk-0.32.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

btrbk

Maintainer pings
cc @asymmetric for testing.

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

1 package built:

btrbk


Please add "onDragEnd"

Hi. Please add onDragEnd so I could update my database after drag items is ends.

onDragStopped already exist. How would onDragEnd be different?


Dynamically add info to welcome.json on boot

Hi Martin,
For venus-grafana-deployer I would also like to add a link to the admin interface.
As you stated Grafana doesn't support dynamic info in text fields, so I worked around it.
(of course this doesn't work with the current examples/docker-compose.yaml, as the version needs to be updated first)
Fixes #20

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Please support GPUs above sm_89

Is your feature request related to a problem? Please describe.
sdfstudio dosen't support RTX 40XX, since it's using torch-1.12.1
and changing to torch-2.X is difficult on my own (tried to merge this project with [nerfstudio] but failed)
Describe the solution you'd like
Update the project to the latest nerfstudio upstream
Describe alternatives you've considered
Integrate bakedangelo and other models directly into nerfstudio
Additional context
The packages I think should be updated: torch, nerfacc
Howerver from my experience, those updates might take a huge amount of code modifications, so the alternatives plan is more convenient.

Hi, thanks for the suggestions. We will try to make an update.


Add new models

The list of models we export is actually larger than in mentioned in the current version. We need to update the docs and "re-push" the package.

Classification
Regression

Linear
scikit-learnLogisticRegressionLogisticRegressionCVPassiveAggressiveClassifierPerceptronRidgeClassifierRidgeClassifierCVSGDClassifierlightningAdaGradClassifierCDClassifierFistaClassifierSAGAClassifierSAGClassifierSDCAClassifierSGDClassifier
scikit-learnARDRegressionBayesianRidgeElasticNetElasticNetCVHuberRegressorLarsLarsCVLassoLassoCVLassoLarsLassoLarsCVLassoLarsICLinearRegressionOrthogonalMatchingPursuitOrthogonalMatchingPursuitCVPassiveAggressiveRegressorRANSACRegressor(only supported regression estimators can be used as a base estimator)RidgeRidgeCVSGDRegressorTheilSenRegressorStatsModelsGeneralized Least Squares (GLS)Generalized Least Squares with AR Errors (GLSAR)Ordinary Least Squares (OLS)[Gaussian] Process Regression Using Maximum Likelihood-based Estimation (ProcessMLE)Quantile Regression (QuantReg)Weighted Least Squares (WLS)lightningAdaGradRegressorCDRegressorFistaRegressorSAGARegressorSAGRegressorSDCARegressor

SVM
scikit-learnLinearSVCNuSVCSVClightningKernelSVCLinearSVC
scikit-learnLinearSVRNuSVRSVRlightningLinearSVR

Tree
DecisionTreeClassifierExtraTreeClassifier
DecisionTreeRegressorExtraTreeRegressor

Random Forest
ExtraTreesClassifierLGBMClassifier(rf booster only)RandomForestClassifierXGBRFClassifier(binary only, multiclass is not supported yet)
ExtraTreesRegressorLGBMRegressor(rf booster only)RandomForestRegressorXGBRFRegressor

Boosting
LGBMClassifier(gbdt/dart/goss booster only)XGBClassifier(gbtree/gblinear booster only)
LGBMRegressor(gbdt/dart/goss booster only)XGBRegressor(gbtree/gblinear booster only)

In the midst of adding this, but needs an update of the toolchain to support lightgbm (which is also the package name in the bundle).

Ran tests for:

package
model
New
Tested (01052020)
Note

lightgbm
LGBMClassifier(rf booster only)
yes
ok

lightgbm
LGBMRegressor(rf booster only)
yes
ok

lightning
AdaGradClassifier
yes
no
Skip for now

lightning
AdaGradRegressor
yes
no
Skip for now

lightning
CDClassifier
yes
no
Skip for now

lightning
CDRegressor
yes
no
Skip for now

lightning
FistaClassifier
yes
no
Skip for now

lightning
FistaRegressor
yes
no
Skip for now

lightning
KernelSVC
yes
no
Skip for now

lightning
SAGAClassifier
yes
no
Skip for now

lightning
SAGARegressor
yes
no
Skip for now

lightning
SAGClassifier
yes
no
Skip for now

lightning
SAGRegressor
yes
no
Skip for now

lightning
SDCAClassifier
yes
no
Skip for now

lightning
SDCARegressor
yes
no
Skip for now

sklearn
ARDRegression
no
ok

sklearn
BayesianRidge
yes
ok

sklearn
DecisionTreeClassifier
no
ok

sklearn
DecisionTreeRegressor
no
ok

sklearn
ElasticNet
no
ok

sklearn
ElasticNetCV
no
ok

sklearn
ExtraTreeClassifier
no
ok

sklearn
ExtraTreeRegresso
no
ok

sklearn
ExtraTreesClassifier
no
ok

sklearn
ExtraTreesRegressor
no
ok

sklearn
HuberRegressor
no
ok

sklearn
Lars
no
ok

sklearn
LarsCV
no
ok

sklearn
Lasso
no
ok

sklearn
LassoCV
no
ok

sklearn
LassoLars
no
ok

sklearn
LassoLarsCV
no
ok

sklearn
LassoLarsIC
no
ok

sklearn
LinearRegression
no
ok

sklearn
LinearSVC
no
ok

sklearn
LinearSVR
no
ok

sklearn
LogisticRegression
yes
ok

sklearn
LogisticRegressionCV
yes
ok

sklearn
NuSVC
no
ok

sklearn
NuSVR
no
ok

sklearn
OrthogonalMatchingPursuit
no
ok

sklearn
OrthogonalMatchingPursuitCV
no
ok

sklearn
PassiveAggressiveClassifier
no
ok

sklearn
PassiveAggressiveRegressor
no
ok

sklearn
Perceptron
yes
ok

sklearn
RandomForestClassifier
no
ok

sklearn
RandomForestRegressor
no
ok

sklearn
RANSACRegressor
no
ok

sklearn
Ridge
no
ok

sklearn
RidgeClassifier
yes
ok

sklearn
RidgeClassifierCV
yes
ok

sklearn
RidgeCV
no
ok

sklearn
SGDClassifier
no
ok

sklearn
SGDRegressor
no
ok

sklearn
SVC
no
ok

sklearn
SVR
no
ok

sklearn
TheilSenRegressor
no
ok

statsmodels
[Gaussian] Process Regression Using Maximum Likelihood-based Estimation (ProcessMLE)
yes
not ok
Skip for now

statsmodels
Generalized Least Squares (GLS)

ok

statsmodels
Generalized Least Squares with AR Errors (GLSAR)
yes
ok

statsmodels
Ordinary Least Squares (OLS)

ok

statsmodels
Quantile Regression (QuantReg)
yes
ok

statsmodels
Weighted Least Squares (WLS)

ok

xgboost
XGBClassifier(gbtree/gblinear booster only)
no
ok

xgboost
XGBRegressor(gbtree/gblinear booster only)
no
ok

xgboost
XGBRFClassifier(binary only, multiclass is not supported yet)
no
ok

xgboost
XGBRFRegressor
no
ok

So, added a few models (including lightgbm) and xgboost. Not added the lightning ones (although in test_all_models.py these are specified already and they should be simple to add by:

Checking if _model_fitted() and _precit() work for lightning models
Mapping the lightning package to the sklearn toolchain (in main.py)
Running the tests.

I am closing this for now.

package
model
Tested (05052020)
Note

lightgbm
LGBMClassifier
ok

lightgbm
LGBMRegressor
ok

sklearn
ARDRegression
ok

sklearn
BayesianRidge
ok

sklearn
DecisionTreeClassifier
ok

sklearn
DecisionTreeRegressor
ok

sklearn
ElasticNet
ok

sklearn
ElasticNetCV
ok

sklearn
ExtraTreeClassifier
ok

sklearn
ExtraTreeRegresso
ok

sklearn
ExtraTreesClassifier
ok

sklearn
ExtraTreesRegressor
ok

sklearn
HuberRegressor
ok

sklearn
Lars
ok

sklearn
LarsCV
ok

sklearn
Lasso
ok

sklearn
LassoCV
ok

sklearn
LassoLars
ok

sklearn
LassoLarsCV
ok

sklearn
LassoLarsIC
ok

sklearn
LinearRegression
ok

sklearn
LinearSVC
ok

sklearn
LinearSVR
ok

sklearn
LogisticRegression
ok

sklearn
LogisticRegressionCV
ok

sklearn
NuSVC
ok

sklearn
NuSVR
ok

sklearn
OrthogonalMatchingPursuit
ok

sklearn
OrthogonalMatchingPursuitCV
ok

sklearn
PassiveAggressiveClassifier
ok

sklearn
PassiveAggressiveRegressor
ok

sklearn
Perceptron
ok

sklearn
RandomForestClassifier
ok

sklearn
RandomForestRegressor
ok

sklearn
RANSACRegressor
ok

sklearn
Ridge
ok

sklearn
RidgeClassifier
ok

sklearn
RidgeClassifierCV
ok

sklearn
RidgeCV
ok

sklearn
SGDClassifier
ok

sklearn
SGDRegressor
ok

sklearn
SVC
ok

sklearn
SVR
ok

sklearn
TheilSenRegressor
ok

statsmodels
Generalized Least Squares (GLS)
ok

statsmodels
Generalized Least Squares with AR Errors (GLSAR)
ok

statsmodels
Ordinary Least Squares (OLS)
ok

statsmodels
Quantile Regression (QuantReg)
ok

statsmodels
Weighted Least Squares (WLS)
ok

xgboost
XGBClassifier
ok

xgboost
XGBRegressor
ok

xgboost
XGBRFClassifier
ok
Binary only

xgboost
XGBRFRegressor
ok


[SPARK-39234][SQL][3.3] Code clean up in SparkThrowableHelper.getMessage

What changes were proposed in this pull request?

Remove the starting "\n" in Origin.context. The "\n" will be append in the method SparkThrowableHelper.getMessage instead.
Code clean up the method SparkThrowableHelper.getMessage to eliminate redundant code.

Why are the changes needed?
Code clean up to eliminate redundant code.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing UT

This is to port https://github.com/apache/spark/pull/36612 to 3.3. I would like to port https://github.com/apache/spark/pull/36651 later too.

Merging to 3.3


Fix jsdoc for splice

Array.prototype.splice returns an Array, not a Number. You could also change the code to do what the docs say instead.

Thanks!  Yes, the intention is to match the native semantics.


Comment line in script.

Lines starting with hash are not fully commented. Only if there is space after the hash.
Is this expected behaviour?
I assume script like this will not execute stat, but it will.
#stat; stat
# stat; stat

Thanks for bringing this to my attention. Fixed in commit 00761de.


Not bug, just curiosity

Doing some research into the method of finding an optimal learning rate.
I made the models both from scratch as the videos and also in a torch friendly way, or well using torch modules, dataloaders, optmizer, etc ..
However something weird when running the following, which 'should' be same as code from video. The lr - loss graph is showed in im1 below.
im2 is using code very similar to videos, i.e manually updating weights. Why are the results not the same ? Is the optimizer doing somethign different in the backend ? Over all the training is about the same, both will converge roughly at the same rate.
def findlr(model, data, test_dataloader):
    lrs = torch.linspace(0.01, 1, 1000)
    lrs = 10**torch.linspace(-3, 0, 1000)
    lri = []
    lss = []

    optim = torch.optim.SGD(model.parameters(), lr=lrs[0])
    for i in range(len(lrs)):
        for g in optim.param_groups:
            g['lr'] = lrs[i]

        x, y = next(iter(data))
        l = calcLoss(model(x), y)
        model.zero_grad()
        l.backward()
        optim.step()

        lri.append(lrs[i].item())
        lss.append(l.item())

        print(lrs[i], l.item())
    plt.plot(lri, lss)
    plt.show()
    ```

 im1:

im2:

I am not really sure. But according to the video, I say this is related to weight. Maybe the weight was too large in the im2.

It could also be the gain that the weights were multiplied to, that also affects the results ( the graphs).


Support sarif as a report type - #3045

New optional report format which can be plugged via --plugins detekt-report-sarif.jar:
Output preview via the VSCode extension:

CI will fail due to not a published version of sarif4j. We need to wait until #3045 gets an answer from the sarif authors.

I just skimmed through the code change list. Hence, I only have some general questions.
Is there a roadmap for the Java support? I'm not sure whether reinventing the wheel by implementing the SARIF support in Kotlin is the right approach here?

I just skimmed through the code change list. Hence, I only have some general questions.
Is there a roadmap for the Java support? I'm not sure whether reinventing the wheel by implementing the SARIF support in Kotlin is the right approach here?

When the official MS java support will be out, we can easily migrate to it.
We do not reinvent any wheels here, just generating POJOs :).
Please also see my comment in https://github.com/detekt/detekt/issues/3045#issuecomment-711062052.

@arturbosch, just checking in on this, as there's strong interest internally at Microsoft for consuming this new report format. Any idea when it might be merged/available?

@arturbosch, just checking in on this, as there's strong interest internally at Microsoft for consuming this new report format. Any idea when it might be merged/available?

Hey @michaelcfanning , thanks for interest and the ping.
I've worked on this further locally. I have one last question regarding default -1 values in the scheme which should not appear in the report. I will keep you updated in #3132 later this week.
There are so many good rule improvements in the main branch so I really should get up to speed to finish this and release 1.15.0 xD.

@arturbosch, glad to help w/any SARIF advice. The large # of optional properties/defaults is definitely a concern depending on your JSON mechanism. The C# SARIF SDK uses a library (Newtonsoft JSON.NET) that automatically elides/hydrates these on save/open. We autogenerated the C# OM that has appropriate attributes for this by writing a custom tool, 'JsonSchema.ToDotNet' that parses the SARIF JSON schema. We could consider a similar trick in your scenario, if your JSON serializer supports similar features.
I took Larry's suggestion and have opened an issue to write a validator that flags all unnecessarily rendered default values. There's a lot of surface here to examine...
Something to keep in mind, though: SARIF which contains this data is valid. You might consider hard-coding eliminating obvious things for now, while considering a more systematic/comprehensive solution.

@arturbosch, glad to help w/any SARIF advice. The large # of optional properties/defaults is definitely a concern depending on your JSON mechanism. The C# SARIF SDK uses a library (Newtonsoft JSON.NET) that automatically elides/hydrates these on save/open. We autogenerated the C# OM that has appropriate attributes for this by writing a custom tool, 'JsonSchema.ToDotNet' that parses the SARIF JSON schema. We could consider a similar trick in your scenario, if your JSON serializer supports similar features.
I took Larry's suggestion and have opened an issue to write a validator that flags all unnecessarily rendered default values. There's a lot of surface here to examine...
Something to keep in mind, though: SARIF which contains this data is valid. You might consider hard-coding eliminating obvious things for now, while considering a more systematic/comprehensive solution.

@michaelcfanning thanks for the advise.
I've switcher to Jackson which allowed to preserve the order of properties and eliminate default values from the report.


feat: Add in ETH comparison within market.realms.world

Describe the feature you'd like to request
Clicking into an asset the is no comparison against ETH which is mostly what NFT trading is denominated in.

Describe the solution you'd like to see
Would it be possible to adjust something similar to:

It may be better to have a switch to change USD<>ETH
Additional information
No response

Hi @Calcutatator, I can work on this issue. Could you please assign it to me?


fix: the same component into the same container #5571

The same components are mounted in the same container. No update is found due to diff comparison, so the content remains unchanged However, in the DOM renderer, 'innerHTML' will be emptied, resulting in blank pages
Close #5571

I'm not too sure yet wether we want apps to be implicitly unmounted when someone mounts a new app into an already use container, or we want to block, thow a warning and make developers properly and explicitly unmount themselves (see #5571).

Your consideration is right. I'm also thinking about this matter. However, I think if this operation leads to page blank in the development process, some developers will be confused. Maybe we should uninstall the component and give a prompt to let the developer know that he is in the wrong operation, and the page will initialize due to re mounting. At this time, he will know what happened

Closing in favor of #5573
I don't think we should automatically unmount for the user since this could be unintended and it's better to force the user to
be explicit about their intentions.


NuGet occasionally fails on DevOps Ubuntu agents

NuGet restore occasionally fails on DevOps Ubuntu agents with the following error:
dotnet pack --output /home/vsts/work/1/a

[command]/bin/bash --noprofile --norc
/home/vsts/work/_temp/045fd6ff-93e9-4d15-8355-70158fa521aa.sh

Microsoft (R) Build Engine version 15.9.20+g88f5fadfbe for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

/usr/share/dotnet/sdk/2.2.103/NuGet.targets(499,5):
error : Could not find a part of the path
'/tmp/NuGetScratch/33261173-cbea-49db-b2c3-730de7efa5b9'.
[/home/vsts/work/1/s/Template/Microsoft.Azure.Template.Test/Microsoft.Azure.Template.Test.csproj]

Primary Issue
https://github.com/NuGet/Home/issues/7341
Failing Builds
2/11/19: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4330

I spent several hours but was unable to repro on demand or figure out what might be causing this.


importing NgxAsideComponent

on Angular 7, after installing via npm, ngx-aside folder is created as expected but no 'src' folder containing NgxAsideComponent definition so is no possible to use it on any component. 'projects' folder and 'ngx-aside' folder inside... is supposed to download manually and locate where desired?... or is it a bug while installing?

Hello @Nuajan. I don't know if you were experiencing the same issue I was. I tried importing NgxAsideComponent but it couldnt be found.
In the ngx-aside.d.ts NgxAsideComponent is exported as ea, ...
export { NgxOverlayComponent as ɵc } from './lib/overlay.component';
https://github.com/passenger6/ngx-aside/blob/f2e10784dbc0fc48e29a9a727cfbc5659ed93c0a/dist/ngx-aside/ngx-aside.d.ts#L6
Install the NgxAside as you would normally in your project and do import { ɵa as NgxAsideComponent } from 'ngx-aside';.
@passenger6: The NgxAside demo on Stackblitz is not working.
Solution: I created a demo as I want to implement in my project.


Implement Tabs v2 Component

Spec reference: https://www.google.com/design/spec/components/tabs.html

jfyi: angular material seems already implemented it
https://material.angularjs.org/latest/demo/tabs

I've been experimenting with Polymer and Vuejs / MDL, and to be honest I much prefer the ecosystem of Vuejs and MDL. It just seems simpler to achieve what I'm after, with one notable exception - Tabs. In the past, it's been suggested that MDL is aiming for static sites rather than dynamic - is that still the case for Tabs v2? I would love better support for dynamic tabs, changing the active tab in code, etc. It would be good to know the direction before I go too far down this line...

In the past, it's been suggested that MDL is aiming for static sites rather than dynamic - is that still the case for Tabs v2?

Nope! As we mentioned in our developer docs, MDL V2 strives to seamlessly incorporate into [a wide] range of usage contexts, from simple static websites to complex, Javascript-heavy applications to hybrid client/server rendering systems. To that end, our tabs component will be fully-customizable and easy to both drive programmatically and listen to programmatically.
To that end, we probably won't be writing any explicit logic to associate a given tab with a content panel, because our goal is to focus mainly on the UX around the tabs and provide an interface for developers to do that themselves. However, I can see this as something a framework library wrapping our UI components might do.

That is indeed great news. And, are those docs publicly available yet? I couldn't find much at all about V2 via the main site, and that text it looks like you quoted only returned this from a google search.
If it's at the stage of needing testers yet, I'd be keen to be involved. We're building simple apps, but they are all experiments so tolerant of beta libraries. I'd also be integrating with Vue / vue-mdl, which might or might not be useful at this stage.
Tx.

Superceded by https://github.com/material-components/material-components-web/issues/37


failed to run

I got a Fortran runtime error, when I execute "./main.exe namelist.basic".
Here is the log:
At line 311 of file bin_microphysics_module.f90 (unit = 8, file = 'namelist.run')
Fortran runtime error: Cannot match namelist object name .false.

Error termination. Backtrace:
#0  0x7fd71b823960 in ???
#1  0x7fd71b8244d9 in ???
#2  0x7fd71b82510f in ???
#3  0x7fd71ba729b4 in ???
#4  0x7fd71ba7bd6d in ???
#5  0x7fd71ba7c0e3 in ???
#6  0x5561a6f9b625 in __bmm_MOD_read_in_bmm_namelist
        at /home/liurw/Documents/bin-microphysics-model/bin_microphysics_module.f90:311
#7  0x5561a6f703dd in MAIN__
        at /home/liurw/Documents/bin-microphysics-model/main.f90:57
#8  0x5561a6f703dd in main
        at /home/liurw/Documents/bin-microphysics-model/main.f90:25

Thanks, I've just seen the issue and will resolve it. It is just an old namelist with different variables in it.

Done


Moving window for graph page

While graphing data, we often don't need to see the entire history of the data coming through. We can of course refresh and reset the window, but that is inconvenient and doesn't work exactly the way we'd like. It would be preferable to have the option to view data in a moving window rather than seeing all historical data.

You can zoom in to the line graph by scrolling vertically, then pan left and right by scrolling horizontally or by clicking and dragging. The view will auto-scroll by default when connected to a live source, but that can be toggled by clicking the red arrow in the title bar or scrolling to the left. There are more details in the line graph and live sources docs.

Closing this issue since I believe the issue was resolved.


code for USL-T

Dear author,
I wonder when the code for USL-T will be released ?

USL-T implementation is a little different to USL, as it requires training while this codebase currently doesn't support training. I'm planning to integrate it into this codebase. Does giving you the selected samples before the integration help your research?

Thanks a lot for your reply.
The indices of selected samples generated by USL-T would be much helpful !
Meanwhile I'll wait for the code to be released.

I added the indices in README.

Added USL-T implementation, checkpoints, and sample selection. Feel free to contact me if you have any questions.


Fix warpscript jar build

Fix warpscript jar build by including fdb and leveldb warpscript functions paths

Fixed by #1252


nixos/samba: add mount.cifs +s wrapper

Description of changes
After discussion at:
https://discourse.nixos.org/t/cant-mount-samba-share-as-a-user/49171/ it was apparent that this wrapper is missing. This fixes the bad experience the OP had.
Things done

Built on platform(s)

[ ] 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

[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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.

cc @kekneus373

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/cant-mount-samba-share-as-a-user/49171/11

Friendly ping to @kekneus373 .


Check and Honor Retry-After headers when communicating with the server

Server may advise minimum retry intervals in seconds after a server side issue. Check and respect this header if it is present.

This fix is present and merged in 4.5.4dev


[WIP] Correct tests running on Python 2.7 under Windows

Ongoing fixes to Python 2.7 running under windows. No issue for this (yet).

[x] ~Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)~
[x] Title summarizes what is changing
[x] Has a news entry file (remember to thank yourself!)
[x] Has unit tests & system/integration tests
[x] ~Any new/changed dependencies in package.json are pinned (e.g. "1.2.3", not "^1.2.3" for the specified version)~
[x] ~package-lock.json has been regenerated by running npm install (if dependencies have changed)~

Restart to see if timeouts are transient or reproduceable (I cannot reproduce locally).

Closing for now @d3r3kk


Remove std dependencies and mark the crate #![no_std]

This change removes all std dependencies, except for rppal and marks the crate #![no_std]. no_std is a must for small embedded microcontrollers.
The only real feature loss due to this is the sophisticated thiserror based error handling.
But quite honestly, I don't really think this is a loss. We could try to tweak the new implementation a bit to get more information from low level upstream, but I really doubt there's any use of that information. If there's an error during bus access, then there's something physically wrong with the bus. No low level error code will really help here.

I rebased this PR on current main branch.
no_std is not useful as long as we depend on rppal directly. Removal of rppal is currently blocked by an upstream PR. It's unclear when this is going to succeed.
Therefore, I'd suggest we pull in no_std now to avoid bitrot and constant rebase work.

What do you think. Should we merge this now, or should we wait for rppal?


Python: Fix netron.main() and netron command without arguments

This PR solves the problem that netron.main() returns TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType. This error has been occurs since the commit ed1846e1372cc5911b6ab4a9ebe620a52911150e.
Also, you added an assert statement in this line, but I deleted it. It won’t become False because type(file) returns NoneType not None if file is None, and in that case, Netron shows the file picker screen. Therefore, I suppose that it is not needed.
If I missed something, please tell me that. Thanks.
I tested on Python 2.7 and 3.6.

Thank you!


Failed to load class "org.slf4j.impl.StaticLoggerBinder".

I get these error messages:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
All that I do with this library
val detector = OsThemeDetector.getDetector()
val isDarkThemeUsed = detector.isDark
JOptionPane.showMessageDialog(null, if (isDarkThemeUsed) "You are using dark theme" else "You are using light theme")

Look at #11.


[Feature] Code Copy Feature inside Questions and Answers

Description
Implement a code copy feature within the Questions and Answers section of our project. This feature will allow users to easily copy code snippets posted in questions or answers with a single clic**k, enhancing usability and convenience for developers and learners on the platform.**
Screenshots
We can add a copy button on top of code block.

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)

@Nishitbaria Pls assign this task to me under GSSOC'24 ✨


Escape Wikipedia featured and random page URLs

Description

This PR fixes an issue where Wikipedia articles with spaces in the title were not opening correctly.
Basically we escaped the URLs for Wikipedia's Search Page command but we forgot to do it for the other commands (Open Random Page, Open Featured Page). The original fix for Search Page was done here #787.
Screencast

The following video shows it working for current featured page, which failed according to #828
https://user-images.githubusercontent.com/36263538/156019566-b1cc2ca8-bb9e-4660-8f80-39ce5ace90b7.mp4
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast

I also removed HTML tags from some titles (like today's featured page)


CI seems broken

Describe the bug
 Checking datafusion-substrait v42.2.0 (/__w/datafusion/datafusion/datafusion/substrait)

error[E0277]: the ? operator can only be applied to values that implement Try
--> datafusion/substrait/src/logical_plan/consumer.rs:1131:12
|
1131 |         if expr.is_volatile()? {
|            ^^^^^^^^^^^^^^^^^^^ the ? operator cannot be applied to type bool
|
= help: the trait Try is not implemented for bool
Checking wasm-bindgen-test v0.3.45
Checking datafusion-sqllogictest v42.2.0 (/__w/datafusion/datafusion/datafusion/sqllogictest)

For more information about this error, try rustc --explain E0277.
error: could not compile datafusion-substrait (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
To Reproduce
No response
Expected behavior
No response
Additional context
No response

Sorry -- fix is here: https://github.com/apache/datafusion/pull/13219


math/big: Float.Float64() may not round correctly for values near math.SmallestNonzeroFloat64

The compiler constant expression
math.SmallestNonzeroFloat64 / 2

gets printed as 5e-324 (program), but the exact computation of math.SmallestNonzeroFloat64 / 2 using math/big arithmetic followed by rounding results in 0 (program).
There's either an error with the rounding or constant arithmetic somewhere, or a mistake in my assumptions.
This affects a test case in types2/testdata/const1.src.

i think it's a mistake, in golang compile, the math.SmallestNonzeroFloat64 / 2 will use big.Float to calculate multi-precision floating， and when transform to float64 the precision will loss, so the print will undefined.
and your example use big.Rat,  it's different

i think types2/testdata/const1.src maybe wrong, you are right ,i want to pull a request to this to do some contribution for golang

i read the comment for Float64(),  the result not 0 may be right
// Float64 returns the float64 value nearest to x. If x is too small to be
// represented by a float64 (|x| < math.SmallestNonzeroFloat64), the result
// is (0, Below) or (-0, Above), respectively, depending on the sign of x.
// If x is too large to be represented by a float64 (|x| > math.MaxFloat64),
// the result is (+Inf, Above) or (-Inf, Below), depending on the sign of x.
func (x *Float) Float64() (float64, Accuracy) {

math.SmallestNonzeroFloat64 / 2 is a  special example  will rounding to math.SmallestNonzeroFloat64,   the logic is here。change the  types2/testdata/const1.src
func (x *Float) Float64() (float64, Accuracy) {
		if e < emin {
			// recompute precision
			p = mbits + 1 - emin + int(e)
			if p < 0 /* m <= 0.25 */ || p == 0 && x.mant.sticky(uint(len(x.mant))*_W-1) == 0 /* m == 0.5 */ {
				// underflow to ±0
				if x.neg {
					var z float64
					return -z, Above
				}
				return 0.0, Below
			}
			// otherwise, round up
			// We handle p == 0 explicitly because it's easy and because
			// Float.round doesn't support rounding to 0 bits of precision.
			if p == 0 {
				if x.neg {
					return -math.SmallestNonzeroFloat64, Below
				}
				return math.SmallestNonzeroFloat64, Above
			}
		}
}

Program to compute accurate values to 512 bits.


Search Functionality and the Ampersand

I have a JQL which has an ampersand in the string. i.e. component = "Research & Architecture".
If I use this in my restful API the library or underlying component uri encodes it, so when it gets to the Jira server the string looks like this 'Research %26 Architecture'. This fails the query on the server side stating that it does not exist for the field component.
I have tried the following to see if I can get it to work:
component = "Research & Architecture" - Error. SyntaxError: Unexpected token & in JSON, which makes sense.
component = "Research \& Architecture" -  "Error in the JQL Query: '\&' is an illegal JQL escape sequence. The valid escape sequences are \', \", \t, \n, \r, \\, '\ ' and \uXXXX. (line 1, character 57)"
component = "Research \u0026 Architecture" -  "The value 'Research %26 Architecture' does not exist for the field 'component'."
component = "Research \u0026 Architecture" - error. The value 'Research %26 Architecture' does not exist for the field 'component'
component = "Research \\u0026 Architecture" - fails on the server with, Error in the JQL Query: '\&' is an illegal JQL escape sequence. The valid escape sequences are \', \", \t, \n, \r, \\, '\ ' and \uXXXX. (line 1, character 57)
I am unable to change the component value, since I do not own it. Is there anything else I can do so it is not encoded, to make this query work?

After some research and checking stack overflow, this appears to be a limitation with the POST operation a search. Since the JIRA api supports GET on a search. This appears to be a case where a GET operation on a search, would serve as a good alternative.
https://stackoverflow.com/questions/61190145/jira-rest-api-and-ampersand/61210126#61210126


Implement 3D MET data storage

3D MET data storage would be nice, opening this but currently lower priority.

We should look at the ECMWF docs to see how to best retrieve the data. Some blocks of data are retrieved from tape making the process very slow.

Nice to have rather than need to have at the moment. Keep as low priority

See #897


Rename Office 365 CLI GitHub actions

Following the rename of Office 365 CLI to CLI for Microsoft 365, we should rename the GitHub actions for CLI.

[ ] login
[ ] deploy
[ ] runscript

I'll pick this up.

Rather than rename the Actions, I think that we should create new actions under the new name, utilising the new package, @pnp/cli-microsoft365 and leave the Office 365 CLI actions in place.
The reason for this is that it doesn't appear that we can rename actions once they have been published to the marketplace, so the only option would be to remove the action and re-create it, as we don't know what the usage is of the actions are (GH doesn't provide metrics) we could break things for people.
I propose we leave Office 365 CLI actions in place, but update the docs to state that it is deprecated and point them to the new CLI for Microsoft 365 Actions as an upgrade path.
Whilst we do this, we should also promote this change for awareness and maybe put in a timeline to remove the Office 365 CLI actions completely.
@pnp/cli-for-microsoft-365-maintainers thoughts?

Good idea! Let's do that!

Before we proceed, just to double check: is it not possible to change the display name of the action or the actual name referenced in the workflow (ie. @pnp/action-cli-login)? If it's the latter, then we could simply release a v2 because there is no mention of O365 anywhere in it. If it's the display name that can't be changed in the marketplace then it would be indeed clearer to have a new set

Actions are published to GitHub Marketplace immediately and aren't reviewed by GitHub as long as they meet these requirements:

The action must be in a public repository.
Each repository must contain a single action.
The action's metadata file (action.yml or action.yaml) must be in the root directory of the repository.
The name in the action's metadata file must be unique.
The name cannot match an existing action name published on GitHub Marketplace.
The name cannot match a user or organization on GitHub, unless the user or organization owner is publishing the action. For example, only the GitHub organization can publish an action named github.
The name cannot match an existing GitHub Marketplace category.
GitHub reserves the names of GitHub features.

Source: https://docs.github.com/en/actions/creating-actions/publishing-actions-in-github-marketplace#about-publishing-actions
Unfortunately, the name property in the action.yml files contains Office 365 CLI
name: 'Office 365 CLI Login'
description: 'Login to tenant using Office 365 CLI'

This is what is used in the marketplace

Whilst we could change the internals to use @pnp/cli-microsoft365 and push out an updated version like you have suggested, we would not be able to update the name in the marketplace without publishing a new action from a new repo.

Good find! I guess that settles it then. Let's release a new set of actions tied to v3 using the new name.

Should we create the new repos with a more consistent name?
pnp/cli-microsoft365-action-login
I will update the existing action readme with a deprecation message and point to the new actions when we have the new actions on the marketplace.

cc/ @andrewconnell for awareness that the new version will mean a change in the action name.

Just to clarify, below is an approach for updating the login action.

Create new repo pnp/cli-microsoft-365-action-login
Push current master branch from pnp/cli-action-login to pnp/cli-microsoft-365-action-login, so this keeps the commit history
Raise PR to update master branch on pnp/cli-microsoft-365-action-login updating all references of Office 365 CLI to CLI for Microsoft 365 and update the package name from @pnp/office365-cli to @pnp/cli-microsoft365
Configure action publishing settings in pnp/cli-microsoft-365-action-login
Add tag for 3.0.0 to master branch in pnp/cli-microsoft-365-action-login to publish action to marketplace
Raise PR to add deprecation message to pnp/cli-action-login readme

@waldekmastykarz happy with the above? This would mean that when published folks using the new actions in a GH workflow, they would use<EMAIL_ADDRESS>

Why use v3 for the action? In the actions we have published currently we used v1 for actions using CLI v2. Haven't we agreed to version actions independently of the CLI?

I was thinking along the lines of matching the current major version of the CLI, but you are correct in that it was agreed to version the actions independently.
Happy to move to 2.0.0, although now I think about it more there is nothing stopping us from using 1.0.0 as I can remove the existing tag and recreate it before publishing to the marketplace.
Do we want to start a new action from v2.0.0? Might be confusing for people who don't know the history.

Let's start with v1. That way, in case there are breaking changes in the action, we can communicate them accordingly. Even though we might update to a newer version of the CLI in the future, as long as the changes aren't affecting actions, actions' users would not need to be concerned.

Looking into this further, we can change the name and description of the action in the metadata, which is pushed to the marketplace on publish, found this in the repo settings.
The docs refer to name in the metadata only and not the name of the workflow action which comes from a combination of the repo name and the tag versions.
I've raised a PR with changes required for the Login action, once merged we can then perform a v2.0.0 release which should push the updated name and description to the marketplace and publish<EMAIL_ADDRESS>

Nice! 👏

All three actions have now been renamed. all use the new package, @pnp/cli-microsoft365 and have been published to the marketplace.
https://github.com/marketplace/actions/cli-for-microsoft-365-login
https://github.com/marketplace/actions/cli-for-microsoft-365-deploy
https://github.com/marketplace/actions/cli-for-microsoft-365-run-script

So... that means with the rename, there should be no impact on existing uses, correct? Because it's not an action rename, it's just a packaging or marketing rename in reality... right?

Yep, exactly that, all existing workflows will still function as they do now.


Fixed random weight issues

There are currently two issues with the new random weight:

Separation between dialogues and goto types didn't work properly:
~ start

% Random 1
% =>< something
% Random 2
% Random 3

=> END

~ something

=> END

1 was on its own, the goto didn't match with the 1, however 2 and 3 matched with the goto because of the lazy and evaluation.

Siblings next_id was not set properly for middle-of-the-pack siblings:
~ start

% Random 1
% Random 2
% Random 3
% Random 4

=> END

1 being the original, its next_id was properly set, as well as 4 because of it being the last.
However 2's next_id was still 3, and 3's was 4. So you could have several dialogues being displayed one after the other.

Both have been fixed with this PR.

Good catch 👍


fatal error: io_github_kasukusakura_silkcodec_NativeBridge.h: No such file or directory

Thanks for providing such wonderful tool first of all.
But when I tried to build it myself, I'm getting:
/work/native/src/bind/NativeBridge.cpp:4:10: fatal error: io_github_kasukusakura_silkcodec_NativeBridge.h: No such file or directory
    4 | #include "io_github_kasukusakura_silkcodec_NativeBridge.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

https://github.com/KasukuSakura/silk-codec/blob/e9321202ece18be04e32207b524a25ca846f3ff0/native/src/bind/NativeBridge.cpp#L4
What steps I'm missing?
PS. This is how I'm building it myself:
export CROSS=linux-x64
docker run -v `pwd`:/work --env "CROSS" "dockcross/$CROSS" bash -c 'chmod +x .scripts/build.sh; /work/.scripts/build.sh'

Thanks

You need to run ./gradlew compileJava first to auto gen jni headers

Wow, thanks a lot for the fast response!!
Hmm..

Here are the highlights of this release:
 - Faster incremental Java compilation
 - Easier source set configuration in the Kotlin DSL

For more details see https://docs.gradle.org/7.1/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)

BUILD SUCCESSFUL in 51s
2 actionable tasks: 2 up-to-date

bash-4.2# find . | sort > /tmp/fl.2

bash-4.2# diff -wU 1 /tmp/fl.1 /tmp/fl.2 | wc
      0       0       0

I.e., nothing get generated under pwd, after running ./gradlew compileJava
I saw the following prompt flashing by during it runs though:
:ci-helper:compileJava > Resolve files of :ci-helper:compileClasspath > Generating

the generated headers in ./build/generated/sources/headers/java/main/
you can see the same path in CMakeList.txt and see full building steps in github ci workflow.yml

Ah, i finally am able to make it:
[100%] Linking CXX executable silk_codec
[100%] Built target silk_codec

Thanks!

BTW, I'm just curious, when and how you were able to figure it all out, the transcoding between silk and PCM?