cmd/link: invalid TLS access model used with -buildmode c-shared

What version of Go are you using (go version)?

$ link -V
link version go1.18

Does this issue reproduce with the latest release?
Yes, 1.18 is the latest release.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/olo/.cache/go-build"
GOENV="/home/olo/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/olo/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/olo/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/golang"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3022165828=/tmp/go-build -gno-record-gcc-switches"

What did you do?
We have a CGo-based library that we build in c-shared mode to use as a dynamic shared object on Linux (x86_64).
The library is, unfortunately, an internal project and I cannot disclose the source code.
For the C compiler, we are using Clang.
The final linking of the shared object file is performed with the following invocation of the go link tool (some irrelevant flags removed):

go link -s -X internalmodule/go/buildinfo.Compiler=clang -o shared_library.so -buildmode c-shared -buildid= -linkmode external -L importdir -extld /path/to/external_clang++_ld  '-extldflags=A BUNCH OF EXT LD FLAGS' package.a

What did you expect to see?
All this setup has been working fine with Clang's previous version, 9.0.20190721 and the exact same (binary for binary) Golang toolchain version.
We would expect it to work the same after upgrading to a newer Clang version.
What did you see instead?
With a newer Clang version 12.0.20210610, we are observing cmd/link fail with the following error:

ld.lld: error: relocation R_X86_64_TPOFF32 against runtime.tlsg cannot be used with -shared
>>> defined in /tmp/go-link-4046235013/go.o
>>> referenced by cpu_x86.go:65 (/usr/local/go/src/internal/cpu/cpu_x86.go:65)
>>>               /tmp/go-link-4046235013/go.o:(internal/cpu.doinit)

The first suspicion would obviously be on Clang. However, we tracked it down to this change: https://reviews.llvm.org/D33100
As can be seen, Clang has introduced a stricter check on where this relocation is allowed due to correctness reasons.
Further reading of https://akkadia.org/drepper/tls.pdf indicates that this relocation type is intended for the TLS Local Exec model, and exec models are not suitable for usage in dynamic shared objects (only in final built executables).
We've analyzed all the intermediate/dependency .a archive files and the .o object files they contain with readelf -r, and none of them contain the R_X86_64_TPOFF32 relocation anywhere.
The temporary go.o file generated by the go link command is the first that appears during the build process that contains it, indicating that it is this command inserting the relocation.
We've tracked down the code in cmd/link that generates this relocation to this place:
https://github.com/golang/go/blob/go1.18/src/cmd/link/internal/amd64/asm.go#L403
which further confirms that cmd/link is using an invalid TLS access model for the situation (-buildmode c-shared was used).
I do not yet have a good enough understanding of the Go linker and why is it choosing this access model, but its behavior seems to be clearly incorrect.
It's possible that, as the latest Clang releases get more prevalent, this issue will pop up in other places with other users who rely on -buildmode c-shared.
This issue might also have some relation to issue #48596 and bears some similarity to the old (and fixed) issue #9652.

cc @cherrymui @rsc @ianlancetaylor

Hi! Yes to both of those things (we use the Buck build system which breaks down the process into individual invocations of Go tools like compile, link, asm or pack directly). We supply -buildmode c-shared to link.
I'm currently working on a minimalized repro case that only relies on pure Golang toolchain, but other things will keep me busy till about mid-July, so cannot provide more info at the moment.

What flags do you pass to compile and asm? Could you show a full list of commands you run? Thanks.
Note that not all compiler/assembler flags are compatible with the build mode.

The original build is quite extensive and complicated, but here's the gist of what's being run to produce some of the key .o's that feed into the problematic link:
compile -p main -pack -trimpath <ROOT_OF_SCM_REPO> -nolocalimports -dynlink '-buildid=' -o <OUTPUT_ARCHIVE>.a -I <INCLUDE_DIR> -complete <ADDITIONAL_BUILD_INFO_SYMBOLS>.go /PATH/TO/main.go

The asm invocation is only used on some of the Golang core crypto lib internals way earlier in the build dependency tree, not on any of our own sources:
asm -trimpath <ROOT_OF_SCM_REPO> -D GOOS_linux -D GOARCH_amd64 -o <OUTPUT_OBJECT>.o -I <INCLUDE_DIR> -I <golang.org/x/crypto/curve25519/internal/field/field_HEADERS_DIR> -I <golang.org/x/crypto/curve25519/internal/field/field_HEADERS_DIR> <GOLANG_SOURCE_TREE>/go/golang.org/x/crypto/curve25519/internal/field/fe_amd64.s

I believe this part is a recreation of Golang's own distribution build within Buck.
Is there perhaps some key arg to go compile that we aren't supplying that causes its produced .o to trigger go link switch to logic that chooses the LocalExec Thread Local Storage access model?

I think you need to pass the -shared flag to the compiler and the assembler. I don't think you want to pass the -dynlink flag.
Note that this also applies to the Go standard library packages. If you use pre-built packages, make sure they are built with those flags as well.

@cherrymui I created a minimal repro script.

 go env, go, clang, ld.lld versions
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/maxshegai/.cache/go-build"
GOENV="/home/maxshegai/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/maxshegai/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/maxshegai/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3023500340=/tmp/go-build -gno-record-gcc-switches"

$ go version
go version go1.19 linux/amd64

$ clang++ -v
clang version 14.0.0 (Fedora 14.0.0-1.fc36)
Target: x86_64-redhat-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-redhat-linux/12
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-redhat-linux/12
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64

$ ld.lld -v
LLD 14.0.0 (compatible with GNU linkers)

Script:
#!/bin/bash

AFILE="${PWD}"/repro.a
SOFILE="${PWD}"/repro.so

go tool compile -o "${AFILE}" "${PWD}"/main.go

go tool link -buildmode c-shared -linkmode external -extld /usr/bin/clang++ \
   "-extldflags=-Wl,--no-mmap-output-file -fuse-ld=lld -o ${SOFILE}" \
   "${AFILE}"
EOF

$ cat main.go
package main

func main() {}

Output
$ ./repro.sh
/usr/local/go/pkg/tool/linux_amd64/link: running /usr/bin/clang++ failed: exit status 1
ld.lld: error: relocation R_X86_64_TPOFF32 against runtime.tlsg cannot be used with -shared
>>> defined in /tmp/go-link-202360648/go.o
>>> referenced by cpu_x86.go:57 (/usr/local/go/src/internal/cpu/cpu_x86.go:57)
>>>               /tmp/go-link-202360648/go.o:(internal/cpu.doinit)

ld.lld: error: relocation R_X86_64_TPOFF32 against runtime.tlsg cannot be used with -shared
>>> defined in /tmp/go-link-202360648/go.o
>>> referenced by cpu_x86.go:79 (/usr/local/go/src/internal/cpu/cpu_x86.go:79)
>>>               /tmp/go-link-202360648/go.o:(internal/cpu.doinit)

ld.lld: error: relocation R_X86_64_TPOFF32 against runtime.tlsg cannot be used with -shared
>>> defined in /tmp/go-link-202360648/go.o
>>> referenced by cpu_x86.go:85 (/usr/local/go/src/internal/cpu/cpu_x86.go:85)
>>>               /tmp/go-link-202360648/go.o:(internal/cpu.doinit)

...

# Similar errors referencing different go files

Hey, @cherrymui, thanks for looking into this. We're using the lower level go tool compile/link as we've got to stay integrated with the cross-language build system deployed internally here at Meta, especially for cgo projects.
We have our reservations about rebuilding the world with -shared. Can you briefly explain the possible implications of doing so, please?

In short -shared tells the compiler and assembler to build PIC code, so it can be used for c-shared, PIE,  or plugin build mode.
I'd still suggest to use the go  command if possible. Directly using the compiler and linker is not a supported mode and may change any time, especially with non-trivial flags such as c-shared build mode. If you really want to do that, maybe you could take a look at the compiler/assembler/linker invocations from the go command by doing go build -x or go build -n, and pass the same flags.

My last 2 cents after closure of this task in the interest of future follow-up discussions that may happen.
First of all, thanks @cherrymui for pointing out the necessity to rebuild all the dependencies with -shared! This allowed us to pinpoint the issue and work around it.
I can see that the world needs rebuilding with -shared, as the resultant final binary is compiled into machine code which needs to work somehow and meet the requirements of a DSO. There can't be any reservations about that.
However, I believe that this discussion brought to light another interesting fact, which to the best of my knowledge (and Googling) is not very well documented.
In our testing and repro work, we have noticed that the go build subcommand, when used in c-shared buildmode, has an implicit special case behavior relating to the standard library.
Namely, it spawns an implicit build job to perform temporary compilation of Golang standard library modules with the -shared flag, making use of an implied, universal availability of their sources.
Here's an easy way to observe this behavior:
$ cat go_build.sh
#!/bin/bash
go build -a -n -buildmode=c-shared -ldflags "-extld=/usr/bin/clang++ -extldflags=-fuse-ld=lld -o main.so" main.go 2>&1 | grep 'compile.*internal'

$ cat main.go
package main

func main() {}

$ ./go_build.sh
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b004/_pkg_.a -trimpath "$WORK/b004=>" -p internal/goarch -std -+ -complete -installsuffix shared -buildid ZHkSq2swJTRI2k6gm2D5/ZHkSq2swJTRI2k6gm2D5 -goversion go1.18.4 -shared -c=4 -nolocalimports -importcfg $WORK/b004/importcfg -pack /usr/lib/golang/src/internal/goarch/goarch.go /usr/lib/golang/src/internal/goarch/goarch_amd64.go /usr/lib/golang/src/internal/goarch/zgoarch_amd64.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b003/_pkg_.a -trimpath "$WORK/b003=>" -p internal/abi -std -+ -installsuffix shared -buildid w_fa4cF9I81-PRD0VKU4/w_fa4cF9I81-PRD0VKU4 -goversion go1.18.4 -symabis $WORK/b003/symabis -shared -c=4 -nolocalimports -importcfg $WORK/b003/importcfg -pack -asmhdr $WORK/b003/go_asm.h /usr/lib/golang/src/internal/abi/abi.go /usr/lib/golang/src/internal/abi/abi_amd64.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b007/_pkg_.a -trimpath "$WORK/b007=>" -p internal/cpu -std -+ -installsuffix shared -buildid mBY4T5UiI7pryaN5qOLs/mBY4T5UiI7pryaN5qOLs -goversion go1.18.4 -symabis $WORK/b007/symabis -shared -c=4 -nolocalimports -importcfg $WORK/b007/importcfg -pack -asmhdr $WORK/b007/go_asm.h /usr/lib/golang/src/internal/cpu/cpu.go /usr/lib/golang/src/internal/cpu/cpu_x86.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b006/_pkg_.a -trimpath "$WORK/b006=>" -p internal/bytealg -std -+ -installsuffix shared -buildid iBmsnO3jk4HE__XY62V5/iBmsnO3jk4HE__XY62V5 -goversion go1.18.4 -symabis $WORK/b006/symabis -shared -c=4 -nolocalimports -importcfg $WORK/b006/importcfg -pack -asmhdr $WORK/b006/go_asm.h /usr/lib/golang/src/internal/bytealg/bytealg.go /usr/lib/golang/src/internal/bytealg/compare_native.go /usr/lib/golang/src/internal/bytealg/count_native.go /usr/lib/golang/src/internal/bytealg/equal_generic.go /usr/lib/golang/src/internal/bytealg/equal_native.go /usr/lib/golang/src/internal/bytealg/index_amd64.go /usr/lib/golang/src/internal/bytealg/index_native.go /usr/lib/golang/src/internal/bytealg/indexbyte_native.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b008/_pkg_.a -trimpath "$WORK/b008=>" -p internal/goexperiment -std -complete -installsuffix shared -buildid -JUqi24MGyMHg9nBuQLq/-JUqi24MGyMHg9nBuQLq -goversion go1.18.4 -shared -c=4 -nolocalimports -importcfg $WORK/b008/importcfg -pack /usr/lib/golang/src/internal/goexperiment/exp_fieldtrack_off.go /usr/lib/golang/src/internal/goexperiment/exp_heapminimum512kib_off.go /usr/lib/golang/src/internal/goexperiment/exp_pacerredesign_on.go /usr/lib/golang/src/internal/goexperiment/exp_preemptibleloops_off.go /usr/lib/golang/src/internal/goexperiment/exp_regabiargs_on.go /usr/lib/golang/src/internal/goexperiment/exp_regabireflect_on.go /usr/lib/golang/src/internal/goexperiment/exp_regabiwrappers_on.go /usr/lib/golang/src/internal/goexperiment/exp_staticlockranking_off.go /usr/lib/golang/src/internal/goexperiment/exp_unified_off.go /usr/lib/golang/src/internal/goexperiment/flags.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b009/_pkg_.a -trimpath "$WORK/b009=>" -p internal/goos -std -+ -complete -installsuffix shared -buildid nAczB-jLkeyDmoPbSPMJ/nAczB-jLkeyDmoPbSPMJ -goversion go1.18.4 -shared -c=4 -nolocalimports -importcfg $WORK/b009/importcfg -pack /usr/lib/golang/src/internal/goos/goos.go /usr/lib/golang/src/internal/goos/zgoos_linux.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b010/_pkg_.a -trimpath "$WORK/b010=>" -p runtime/internal/atomic -std -+ -installsuffix shared -buildid cqPR-KtXpcMsgrvGIPEQ/cqPR-KtXpcMsgrvGIPEQ -goversion go1.18.4 -symabis $WORK/b010/symabis -shared -c=4 -nolocalimports -importcfg $WORK/b010/importcfg -pack -asmhdr $WORK/b010/go_asm.h /usr/lib/golang/src/runtime/internal/atomic/atomic_amd64.go /usr/lib/golang/src/runtime/internal/atomic/doc.go /usr/lib/golang/src/runtime/internal/atomic/stubs.go /usr/lib/golang/src/runtime/internal/atomic/types.go /usr/lib/golang/src/runtime/internal/atomic/types_64bit.go /usr/lib/golang/src/runtime/internal/atomic/unaligned.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b011/_pkg_.a -trimpath "$WORK/b011=>" -p runtime/internal/math -std -+ -complete -installsuffix shared -buildid zM2rfYoL8pHhlQ9JCx1h/zM2rfYoL8pHhlQ9JCx1h -goversion go1.18.4 -shared -c=4 -nolocalimports -importcfg $WORK/b011/importcfg -pack /usr/lib/golang/src/runtime/internal/math/math.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b012/_pkg_.a -trimpath "$WORK/b012=>" -p runtime/internal/sys -std -+ -complete -installsuffix shared -buildid DP45ebbCVyK97YOvB_62/DP45ebbCVyK97YOvB_62 -goversion go1.18.4 -shared -c=4 -nolocalimports -importcfg $WORK/b012/importcfg -pack /usr/lib/golang/src/runtime/internal/sys/consts.go /usr/lib/golang/src/runtime/internal/sys/intrinsics.go /usr/lib/golang/src/runtime/internal/sys/intrinsics_common.go /usr/lib/golang/src/runtime/internal/sys/sys.go /usr/lib/golang/src/runtime/internal/sys/zversion.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b013/_pkg_.a -trimpath "$WORK/b013=>" -p runtime/internal/syscall -std -installsuffix shared -buildid Zk3yU1uXw4CdQuVMDyE1/Zk3yU1uXw4CdQuVMDyE1 -goversion go1.18.4 -symabis $WORK/b013/symabis -shared -c=4 -nolocalimports -importcfg $WORK/b013/importcfg -pack -asmhdr $WORK/b013/go_asm.h /usr/lib/golang/src/runtime/internal/syscall/syscall_linux.go
/usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/b016/_pkg_.a -trimpath "$WORK/b016=>" -p internal/race -std -complete -installsuffix shared -buildid TkqfhZvzcqMe2AZz5SMH/TkqfhZvzcqMe2AZz5SMH -goversion go1.18.4 -shared -c=4 -nolocalimports -importcfg $WORK/b016/importcfg -pack /usr/lib/golang/src/internal/race/doc.go /usr/lib/golang/src/internal/race/norace.go
$

As one can see, without any explicit declarations, module sources like golang/src/runtime/internal/sys/sys.go get implicitly passed through go compile -shared with output sent to a temporary binary archive like $WORK/b012/_pkg_.a.
I'd like to argue that this is a huge and surprising departure from established practice with compiler and build toolchains in other compiled languages.
Typically, when the language's standard library needs special mode of compilation for a flavor of its binaries (be it target CPU architecture or shared vs static), it's done in advance and the compiled binaries get shipped along with "normal" ones. E.g. regular C libraries which usually ship both static archives and .so shared objects in separate precompiled files.
This makes many beneficial things easier, e.g. having the trusted compiled libraries authenticated and cryptographically signed; saving time on compilation etc. At the very least, this has the benefit of adhering to the principle of least astonishment for the user.
And Golang even has a facility for shipping different flavors of compiled standard libs, after all we have architecture-oriented dirs like go/pkg/darwin_amd64/, go/pkg/darwin_arm64/, go/pkg/linux_amd64/.
It is obviously up to the Golang project to decide how the build toolchain works, but I'd like to suggest changing the behavior from on-demand recompilation of standard library modules to shipping them pre-compiled in shared mode (e.g. in directories named like go/pkg/linux_amd64_shared/).

@aadamowski the build of the packages are cached, so it shouldn't be rebuilt the next time you build it with the same flag.
However, you used the -a flag at go build, which is specifically to force rebuilding everything. You can see that even without the special build mode a plain go build -a will rebuild all dependent packages.

I understand. However, performance is only a minor of all the concerns that I have around this design. It also applies only to local builds (on a specific machine/OS instance/filesystem), not any distributed build infrastructures (out of the box).
My largest concern is the departure from the established practices around how build toolchains generally work and what features their individual tools provide (e.g. a compiler does not suddenly decide on its own to compile a piece of source it wasn't explicitly asked to compile).

Sorry, I'm not sure I understand. You used the -a flag, which is explicitly asking to compile everything.

Oh, I see what you mean. Yes, I'd like to be able to drop the usage of -a from go build and still be able to produce a c-shared library with pre-compiled shared stdlib packages, and without a need to recompile and overwrite the deps when switching between c-shared and regular buildmodes (they'd need to be cached separately from each other).
In essence, I'd argue for go build to maintain separate caches for built artifacts, keyed on build architecture and shared vs regular (non-PIC) build modes.

IOW, the idea is to add another sublevel to module cache directory structure (https://go.dev/ref/mod#module-cache) to guarantee separation between compiled artifacts that cannot possibly work together (due to being cross-compiled for a different architecture, or mixing of -shared and non-shared build modes).

I see. Thanks, I think we now have a better understanding of it now and how to adapt Buck's Golang support to handle c-shared gracefully and in a way that aligns with go build's philosophy.
Would you have some time to answer the last few questions?
AFAIU the behavior you mentioned for keying on compile/linker flags only applies to the build cache, correct? E.g. in my case, after dropping -a I've observed go build to use a stable, deterministic path of .cache/go-build/4c/4c90960653622732a99fe2bbbc13bb81c3f3f3c66a1c5c5f44a36f493f0130be-d. I assume the last part is a hash of the relevant compilation/build flags derived from the Action ID? For deeper study, do I understand correctly that the code responsible for this is go/src/cmd/go/internal/work/buildid.go? I was trying to locate some documentation around the Action ID design but only found source code so far.
Is there any similar mechanism that would apply to pre-compiled modules originating externally (installed on the system, not produced by the local build environment) and where the go tools search for them?
Such mechanism, AFAIU, would need to be more coarse than Action ID which seems to be very fine-grained (one of the inputs is the hash of all the combined build dependencies) and doesn't seem reusable between different builds.
Is there any classification mechanism that doesn't depend on all the possible inputs and build args and only the ones that could affect compiled binary compatibility (such as the target CPU architecture, or -shared)?
I am looking for the best way to preserve compiled modules dependencies and distribute/ship them in several supported flavors (basically what I described above - CPU arch, -shared and any other flag that may affect compatibility between compiled object files; the compiled artifacts that have a matching combination of all those would be picked up automatically by the build without recompilation).
The goal is to save the build fleet time that would be spent on repeatedly recompiling popular modules from sources (most importantly the stdlib, but not limited to it).


It means that the certificate authority that imgix.net is using is not in your set of trusted roots.  Are you able to successfully load other https URLs or are they all giving this error?  Where are you running imageproxy?  For example, inside a docker container, a regular linux box, etc?

@willnorris after you created newer docker image on dockerhub it refreshed trusted roots and problem is not a problem now. Probably you will want to refresh trusted roots each time docker command starts


In Apple 6S, open the drawer condition, click on the right side can not be closed

In Apple 6S, open the drawer condition, click on the right side can not be closed。 lightly click can close,
but Click on a little harder can't close. i think it's due to 3DTouch

please solve， thanks


feature(layouts): responsive nav-list

Description
Added responsive list for layouts>nav-list and updated layouts overview w/ images.
What's included?

Images to more accurately describe 4 layout options
Responsive collapse/reveal for nav list sidenav

Test Steps

[x] View Layouts
[x] View Layouts > Nav List & collapse down to mobile size

Screenshots or link to CodePen/Plunker/JSfiddle

LGTM, tests are running fine after merging with develop and added the webdriver-update as npm postinstall

That is a very cool navigation layout. I tried to add it to my app, but I couldn't (by following the example in   the docs ). But that nav-list responsiveness is not working. The nav-list just occupy the whole screen. Do you know what could be happening? The layout is inside of a component navigated through router-outlet. Any case that this layout could not work?
thnx in advance and congrats for the nice work


Bugs Which needs to Get fixed

Bugs List :

[x] Need to fix Split error in telegram upload working fine for UpTo 2GB and raising above the amount around 3-4gb++ the bot doesn't split the files and says files are corrupted. This bug is only noticed with Alpine Docker image and not in the default Ubuntu image

Bugs List :

[x]  Need to fix Split error in telegram upload working fine for UpTo 2GB and raising above the amount around 3-4gb++ the bot doesn't split the files and says files are corrupted. This bug is only noticed with Alpine Docker image and not in the default Ubuntu image

All checks passed no bug or errors found ... Maybe server error or downtime


Increase Typing Coverage & Enable MyPy

Add Type Hints and Enable mypy with strict checking.
Preparatory work in https://github.com/astronomer/astronomer-providers/tree/mypy-strict
Running make run-mypy will show the errors that need fixing.
Acceptance Criteria:

MyPy enabled in strict mode and runs in CI.

@rajaths010494 to check the latest on the mypy-strict branch and post the update here

astronomer/providers/core/triggers/filesystem.py: note: In member "__init__" of class "FileTrigger":
astronomer/providers/core/triggers/filesystem.py:31: error: Call to untyped function "__init__" in typed context  [no-untyped-call]
            super().__init__()
            ^
astronomer/providers/core/triggers/filesystem.py: note: In member "run" of class "FileTrigger":
astronomer/providers/core/triggers/filesystem.py:49: error: The return type of an async generator function should be "AsyncGenerator" or one of its supertypes  [misc]
        async def run(self) -> None:
        ^
astronomer/providers/core/triggers/filesystem.py:49: error: Return type "None" of "run" incompatible with return type "Coroutine[Any, Any, AsyncIterator[TriggerEvent]]" in supertype "BaseTrigger"  [override]
        async def run(self) -> None:
        ^
astronomer/providers/core/triggers/external_task.py:5: error: Module "airflow.models" does not explicitly export attribute "DagRun"; implicit reexport disabled  [attr-defined]
    from airflow.models import DagRun, TaskInstance
    ^
astronomer/providers/core/triggers/external_task.py:5: error: Module "airflow.models" does not explicitly export attribute "TaskInstance"; implicit reexport disabled  [attr-defined]
    from airflow.models import DagRun, TaskInstance
    ^
astronomer/providers/core/triggers/external_task.py: note: In member "__init__" of class "TaskStateTrigger":
astronomer/providers/core/triggers/external_task.py:21: error: Call to untyped function "__init__" in typed context  [no-untyped-call]
            super().__init__()
            ^
astronomer/providers/core/triggers/external_task.py: note: In member "run" of class "TaskStateTrigger":
astronomer/providers/core/triggers/external_task.py:43: error: Function is missing a return type annotation  [no-untyped-def]
        async def run(self):
        ^
astronomer/providers/core/triggers/external_task.py: note: In member "count_tasks" of class "TaskStateTrigger":
astronomer/providers/core/triggers/external_task.py:57: error: Function is missing a type annotation for one or more arguments  [no-untyped-def]
        def count_tasks(self, session) -> int:
        ^
astronomer/providers/core/triggers/external_task.py:71: error: Returning Any from function declared to return "int"  [no-any-return]
            return count
            ^
astronomer/providers/core/triggers/external_task.py: note: In member "__init__" of class "DagStateTrigger":
astronomer/providers/core/triggers/external_task.py:82: error: Call to untyped function "__init__" in typed context  [no-untyped-call]
            super().__init__()
            ^
astronomer/providers/core/triggers/external_task.py: note: In member "run" of class "DagStateTrigger":
astronomer/providers/core/triggers/external_task.py:102: error: Function is missing a return type annotation  [no-untyped-def]
        async def run(self):
        ^
astronomer/providers/core/triggers/external_task.py: note: In member "count_dags" of class "DagStateTrigger":
astronomer/providers/core/triggers/external_task.py:117: error: Function is missing a type annotation for one or more arguments  [no-untyped-def]
        def count_dags(self, session) -> int:
        ^
astronomer/providers/core/triggers/external_task.py:130: error: Returning Any from function declared to return "int"  [no-any-return]
            return count
            ^
astronomer/providers/core/sensors/external_task.py: note: In member "execute" of class "ExternalTaskSensorAsync":
astronomer/providers/core/sensors/external_task.py:12: error: Function is missing a type annotation  [no-untyped-def]
        def execute(self, context):
        ^
astronomer/providers/core/sensors/external_task.py:17: error: Call to untyped function "get_execution_dates" in typed context  [no-untyped-call]
            execution_dates = self.get_execution_dates(context)
                              ^
astronomer/providers/core/sensors/external_task.py: note: In member "execute_complete" of class "ExternalTaskSensorAsync":
astronomer/providers/core/sensors/external_task.py:47: error: Function is missing a type annotation  [no-untyped-def]
        def execute_complete(self, context, session, event=None):  # pylint: disable=unused-argument
        ^
astronomer/providers/core/sensors/external_task.py:52: error: Call to untyped function "get_execution_dates" in typed context  [no-untyped-call]
            execution_dates = self.get_execution_dates(context)
                              ^
astronomer/providers/core/sensors/external_task.py: note: In member "get_execution_dates" of class "ExternalTaskSensorAsync":
astronomer/providers/core/sensors/external_task.py:63: error: Function is missing a type annotation  [no-untyped-def]
        def get_execution_dates(self, context):
        ^
astronomer/providers/cncf/kubernetes/hooks/kubernetes_async.py:1: error: Unused "type: ignore" comment
    import aiofiles  # type: ignore[import]
    ^
astronomer/providers/cncf/kubernetes/hooks/kubernetes_async.py: note: In member "_load_config" of class "KubernetesHookAsync":
astronomer/providers/cncf/kubernetes/hooks/kubernetes_async.py:53: error: Module has no attribute "tempfile"  [attr-defined]
                async with aiofiles.tempfile.NamedTemporaryFile() as temp_config:
                           ^
astronomer/providers/amazon/aws/hooks/redshift_data.py: note: In member "get_conn_params" of class "RedshiftDataHook":
astronomer/providers/amazon/aws/hooks/redshift_data.py:20: error: Argument 1 to "get_connection" of "BaseHook" has incompatible type "Optional[str]"; expected "str"  [arg-type]
            connection_object = self.get_connection(self.aws_conn_id)
                                                    ^
astronomer/providers/amazon/aws/hooks/redshift_data.py: note: In member "execute_query" of class "RedshiftDataHook":
astronomer/providers/amazon/aws/hooks/redshift_data.py:67: error: Function is missing a return type annotation  [no-untyped-def]
        def execute_query(self, sql: Union[str, Iterable[str]], params: Optional[Dict]):
        ^
astronomer/providers/amazon/aws/hooks/redshift_data.py:67: error: Missing type parameters for generic type "Dict"  [type-arg]
        def execute_query(self, sql: Union[str, Iterable[str]], params: Optional[Dict]):
                                                                                ^
astronomer/providers/snowflake/hooks/snowflake.py: note: In member "run" of class "SnowflakeHookAsync":
astronomer/providers/snowflake/hooks/snowflake.py:14: error: Function is missing a return type annotation  [no-untyped-def]
        def run(self, sql: Union[str, list], autocommit: bool = False, parameters: Optional[dict] = None):
        ^
astronomer/providers/snowflake/hooks/snowflake.py:14: error: Signature of "run" incompatible with supertype "SnowflakeHook"  [override]
        def run(self, sql: Union[str, list], autocommit: bool = False, parameters: Optional[dict] = None):
        ^
astronomer/providers/snowflake/hooks/snowflake.py:14: note:      Superclass:
astronomer/providers/snowflake/hooks/snowflake.py:14: note:          def run(self, sql: Union[str, List[Any]], autocommit: bool = ..., parameters: Union[Dict[Any, Any], Iterable[Any], None] = ..., handler: Optional[Callable[..., Any]] = ...) -> Any
astronomer/providers/snowflake/hooks/snowflake.py:14: note:      Subclass:
astronomer/providers/snowflake/hooks/snowflake.py:14: note:          def run(self, sql: Union[str, List[Any]], autocommit: bool = ..., parameters: Optional[Dict[Any, Any]] = ...) -> Any
astronomer/providers/snowflake/hooks/snowflake.py:14: note:          def run(self, sql: Union[str, List[Any]], autocommit: bool = ..., parameters: Union[Dict[Any, Any], Iterable[Any], None] = ..., handler: Optional[Callable[..., Any]] = ...) -> Any
astronomer/providers/snowflake/hooks/snowflake.py:14: note:          def run(self, sql: Union[str, List[Any]], autocommit: bool = ..., parameters: Optional[Dict[Any, Any]] = ...) -> Any
astronomer/providers/snowflake/hooks/snowflake.py:14: error: Signature of "run" incompatible with supertype "DbApiHook"  [override]
        def run(self, sql: Union[str, list], autocommit: bool = False, parameters: Optional[dict] = None):
        ^
astronomer/providers/snowflake/hooks/snowflake.py:14: note:          def run(self, sql: Any, autocommit: Any = ..., parameters: Any = ..., handler: Any = ...) -> Any
astronomer/providers/snowflake/hooks/snowflake.py:14: note:          def run(self, sql: Union[str, List[Any]], autocommit: bool = ..., parameters: Optional[Dict[Any, Any]] = ...) -> Any
astronomer/providers/snowflake/hooks/snowflake.py:14: error: Missing type parameters for generic type "list"  [type-arg]
        def run(self, sql: Union[str, list], autocommit: bool = False, parameters: Optional[dict] = None):
                                      ^
astronomer/providers/snowflake/hooks/snowflake.py:14: error: Missing type parameters for generic type "dict"  [type-arg]
        def run(self, sql: Union[str, list], autocommit: bool = False, parameters: Optional[dict] = None):
                                                                                ^
astronomer/providers/snowflake/hooks/snowflake.py:56: error: Call to untyped function "get_autocommit" in typed context  [no-untyped-call]
                if not self.get_autocommit(conn):
                       ^
astronomer/providers/snowflake/hooks/snowflake.py: note: In member "check_query_output" of class "SnowflakeHookAsync":
astronomer/providers/snowflake/hooks/snowflake.py:60: error: Function is missing a return type annotation  [no-untyped-def]
        def check_query_output(self, query_ids: List[str]):
        ^
astronomer/providers/snowflake/hooks/snowflake.py: note: In member "get_query_status" of class "SnowflakeHookAsync":
astronomer/providers/snowflake/hooks/snowflake.py:72: error: Function is missing a return type annotation  [no-untyped-def]
        async def get_query_status(self, query_ids: List[str]):
        ^
astronomer/providers/core/sensors/filesystem.py: note: In member "execute" of class "FileSensorAsync":
astronomer/providers/core/sensors/filesystem.py:29: error: Function is missing a type annotation  [no-untyped-def]
        def execute(self, context):
        ^
astronomer/providers/core/sensors/filesystem.py:30: error: Call to untyped function "poke" in typed context  [no-untyped-call]
            if not self.poke(context=context):
                   ^
astronomer/providers/core/sensors/filesystem.py:31: error: Call to untyped function "FSHook" in typed context  [no-untyped-call]
                hook = FSHook(self.fs_conn_id)
                       ^
astronomer/providers/core/sensors/filesystem.py: note: In member "execute_complete" of class "FileSensorAsync":
astronomer/providers/core/sensors/filesystem.py:46: error: Function is missing a type annotation  [no-untyped-def]
        def execute_complete(self, context, event=None):  # pylint: disable=unused-argument
        ^
astronomer/providers/core/example_dags/example_external_task_wait_for_me.py:11: error: Call to untyped function "datetime" in typed context  [no-untyped-call]
        start_date=datetime(2022, 1, 1),
                   ^
astronomer/providers/core/example_dags/example_external_task_wait_for_me.py:13: error: Call to untyped function "TimeSensorAsync" in typed context  [no-untyped-call]
        wait_for_me = TimeSensorAsync(
                      ^
astronomer/providers/core/example_dags/example_external_task.py:18: error: Call to untyped function "datetime" in typed context  [no-untyped-call]
    with DAG("test_external_task_async", schedule_interval="@daily", start_date=datetime(2022, 1, 1)) as dag:
                                                                                ^
astronomer/providers/cncf/kubernetes/triggers/wait_container.py: note: In member "__init__" of class "WaitContainerTrigger":
astronomer/providers/cncf/kubernetes/triggers/wait_container.py:50: error: Incompatible default for argument "container_name" (default has type "None", argument has type "str")  [assignment]
            container_name: str = None,
                                  ^
astronomer/providers/snowflake/triggers/snowflake_trigger.py: note: In function "get_db_hook":
astronomer/providers/snowflake/triggers/snowflake_trigger.py:10: error: Function is missing a type annotation for one or more arguments  [no-untyped-def]
    def get_db_hook(self) -> SnowflakeHookAsync:
    ^
astronomer/providers/snowflake/triggers/snowflake_trigger.py: note: In member "__init__" of class "SnowflakeTrigger":
astronomer/providers/snowflake/triggers/snowflake_trigger.py:29: error: Call to untyped function "__init__" in typed context  [no-untyped-call]
            super().__init__()
            ^
astronomer/providers/snowflake/triggers/snowflake_trigger.py: note: In member "run" of class "SnowflakeTrigger":
astronomer/providers/snowflake/triggers/snowflake_trigger.py:49: error: Function is missing a return type annotation  [no-untyped-def]
        async def run(self):
        ^
astronomer/providers/http/example_dags/example_http.py:6: error: Call to untyped function "datetime" in typed context  [no-untyped-call]
    with DAG("example_async_http_sensor", tags=["example", "async"], start_date=datetime(2022, 1, 1)) as dag:
                                                                                ^
astronomer/providers/core/example_dags/example_file_sensor.py:8: error: Call to untyped function "datetime" in typed context  [no-untyped-call]
        start_date=datetime(2022, 1, 1),
                   ^
astronomer/providers/core/example_dags/example_file_sensor.py:12: error: Call to untyped function "FileSensorAsync" in typed context  [no-untyped-call]
        sensor_task = FileSensorAsync(
                      ^
astronomer/providers/snowflake/operators/snowflake.py: note: In member "__init__" of class "SnowflakeOperatorAsync":
astronomer/providers/snowflake/operators/snowflake.py:12: error: Function is missing a type annotation for one or more arguments  [no-untyped-def]
        def __init__(self, *, poll_interval: int = 5, **kwargs):
        ^
astronomer/providers/snowflake/operators/snowflake.py: note: In member "execute" of class "SnowflakeOperatorAsync":
astronomer/providers/snowflake/operators/snowflake.py:20: error: Function is missing a type annotation  [no-untyped-def]
        def execute(self, context):
        ^
astronomer/providers/snowflake/operators/snowflake.py: note: In member "execute_complete" of class "SnowflakeOperatorAsync":
astronomer/providers/snowflake/operators/snowflake.py:44: error: Function is missing a type annotation  [no-untyped-def]
        def execute_complete(self, context, event=None):  # pylint: disable=unused-argument
        ^
astronomer/providers/databricks/example_dags/example_databricks.py:24: error: Call to untyped function "datetime" in typed context  [no-untyped-call]
        start_date=datetime(2022, 1, 1),
                   ^
astronomer/providers/databricks/example_dags/example_databricks.py:41: error: Argument "job_id" to "DatabricksRunNowOperatorAsync" has incompatible type "int"; expected "Optional[str]"  [arg-type]
            job_id=1003,
                   ^
astronomer/providers/amazon/aws/operators/redshift_sql.py: note: In member "execute" of class "RedshiftSQLOperatorAsync":
astronomer/providers/amazon/aws/operators/redshift_sql.py:29: error: Argument "sql" to "execute_query" of "RedshiftDataHook" has incompatible type "Union[Dict[Any, Any], Iterable[Any], None]"; expected "Union[str, Iterable[str]]"  [arg-type]
            query_ids = redshift_data_hook.execute_query(sql=self.sql, params=self.params)
                                                             ^
astronomer/providers/snowflake/example_dags/example_snowflake.py:28: error: Call to untyped function "datetime" in typed context  [no-untyped-call]
        start_date=datetime(2022, 1, 1),
                   ^
astronomer/providers/google/cloud/hooks/gcs.py: note: In member "get_storage_client" of class "GCSHookAsync":
astronomer/providers/google/cloud/hooks/gcs.py:20: error: Argument "session" to "Storage" has incompatible type "ClientSession"; expected "Optional[Session]"  [arg-type]
                return Storage(service_file=file, session=session)
                                                          ^
astronomer/providers/amazon/aws/example_dags/example_s3.py:16: error: Call to untyped function "datetime" in typed context  [no-untyped-call]
        start_date=datetime(2021, 1, 1),
                   ^
astronomer/providers/amazon/aws/example_dags/example_redshift_sql.py:10: error: Call to untyped function "datetime" in typed context  [no-untyped-call]
        start_date=datetime(2021, 1, 1),
                   ^
astronomer/providers/amazon/aws/example_dags/example_redshift_cluster_management.py:19: error: Call to untyped function "datetime" in typed context  [no-untyped-call]
        start_date=datetime(2021, 1, 1),
                   ^
astronomer/providers/google/cloud/hooks/bigquery.py: note: In member "get_job_instance" of class "BigQueryHookAsync":
astronomer/providers/google/cloud/hooks/bigquery.py:88: error: Argument "session" to "Job" has incompatible type "ClientSession"; expected "Optional[Session]"  [arg-type]
                return Job(job_id=job_id, project=project_id, service_file=f, session=session)
                                                                                ^
astronomer/providers/google/cloud/hooks/bigquery.py: note: In member "get_job_status" of class "BigQueryHookAsync":
astronomer/providers/google/cloud/hooks/bigquery.py:102: error: Argument 1 to "result" of "Job" has incompatible type "ClientSession"; expected "Optional[Session]"  [arg-type]
                    job_status_response = await job_client.result(s)
                                                                  ^
astronomer/providers/google/cloud/hooks/bigquery.py: note: In member "get_job_output" of class "BigQueryHookAsync":
astronomer/providers/google/cloud/hooks/bigquery.py:124: error: Argument 1 to "get_query_results" of "Job" has incompatible type "ClientSession"; expected "Optional[Session]"  [arg-type]
                job_query_response = await job_client.get_query_results(session)
                                                                        ^
astronomer/providers/google/cloud/example_dags/example_gcs.py:27: error: Module has no attribute "DAG"  [attr-defined]
    with models.DAG(
         ^
astronomer/providers/google/cloud/example_dags/example_bigquery_queries.py:47: error: Module has no attribute "DAG"  [attr-defined]
    with models.DAG(
         ^
Found 61 errors in 24 files (checked 88 source files)

Fixed mypy errors for amazon providers and merged the changes to  amazon-s3-operators branch


Documentation for adding missing features to sqlpp11

I have a quick question, we are in the process of transforming our database state handler class from python to c++ (Postgres), and we decided to go with sqlpp11. one feature that we use very commonly is RETURNING unique_id on insert. however, this is not supported by sqlpp11.
at the moment what we do is using a custom query with the returning type of select(unique_id), however, we would much rather change the header file to make the library natively supporting commands like
DO NOTHING ON CONFLICT, or RETURNING ""
than using custom queries with verbatim.
what is the best way to go about this? I read the library and I was able to successfully add support for do_nothing_on_conflict to the insert statement, but the case for RETURNING an id seems to be a much more complicated problem.
is there an internal developer guide or something that we can use ?!!

Hi,
there is no developer guide, but there are basically two steps:

Implement new clause(s), e.g. RETURNING. Using existing steps as templates, this is mainly a matter of replacing strings. It is a lot of boilerplate, sorry about that, but it is not that bad in the end.
Implement a new insert statement that contains this new clause. This is quite simple, you basically just combine a couple of clauses, see for instance insert.h

Your new clause is a bit special in that it turns the insert into something that can have one or more values. This looks more like the return value of a select. Your new clause needs to inform the statement that it changes the behavior of insert.
This is done by specifying tag::is_return_value and the _result_methods_t template.
I would assume that select_column_list.h is closest to what you need. It looks a bit daunting, I know, but again, you mainly need to change a few names/strings in here, I think.
An (albeit much simpler) example of a connector-specific statement can be found in the sqlite connector, see https://github.com/rbock/sqlpp11-connector-sqlite3/blob/master/include/sqlpp11/sqlite3/insert_or.h
It is not going to be trivial, but it is not going to be horribly complex either, I guess.
Let me know if you get stuck, I can try to help.
Cheers,
Roland

'returning' is already defined in the postresql connector and that's great but not 'on conflict', that would be a nice to have.

'returning' is already defined in the postresql connector

Cool, and it is added to a postgresql-specific version of insert already...
on conflict should be a walk in the park in comparison :-)

Thanks, I would let you know if we got stuck

Documentation is on the wish list I am currently compiling out of "old" issues.
I'll add a specific wish for "Adding missing features" and close this ticket.


feature/EAS-2049 FSRT - doesn't lower method definitions on object lits

This lowers functions within object literals.

Nice job! The test case passes now. However, we're hitting a bug, where the method calls are incorrectly being resolved to another object under the following conditions:
  let foo = {
    someFunction() {},
  };
  let testObject = {
    someFunction() {
      const res = api.asApp().requestConfluence(route`/rest/api/3/test`);
      test_function('hi');
      return res;
    },
  };
  // this shouldn't trigger a vulnerability, but it currently is.
  foo.someFunction();

To be honest, I'm pretty sure this bug already existed before your PR, however, we didn't end up hitting it, because object methods weren't lowered in the first place. The bug is most likely because of how the interpreter/checkers resolve object method properties, but I could be wrong.
Regardless, we should probably also make the method calling more accurate in this PR as well due to the risk of reporting false positives. You could either:

Have the method invocation resolve to ambiguity if there are multiple possible methods and skip the function invocation. This would be the easiest way if you would like to defer more accurate method resolving to  another task/PR.
Figure out why the methods are being aliased and try to correctly assign them to their parent object.

Also, you can use fsrt --dump-ir App ./test-apps/basic to view the IR for a function. It doesn't help much in this case, since it doesn't show the DefId of the function on foo.someFunction, however, you might find some use for it. You could also tweak it to dump more relevant information if that helps you debug.

I am glad you caught this. This took me some time to debug, but I needed to reset the parent to none after the function after it was called. It was an error in this pull request and actually would have been an issue for all functions following regardless of name. Thank you again. Hope you have a good evening


fix: typo in about us page

Change Kaagaz_link to Kaagaz

I'm interested in working on this issue. Please assign it to me!

I need an issure to resolve


Add fields filter

Hello,
I needed to filter all the non-interesting spans from a federation, does this way of doing suits you?
Then you don't have to filter in the exporters or in the storage or in the displays.
Thank you.

@rangzen thanks for the PR. I'll try to have a look soon

@ravilushqa Thank you :pray:

@rangzen good job! thanks for contributing 💪


⚠ Bofrost.be has degraded performance

In 8ab591d, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1581 ms

Resolved: Bofrost.be performance has improved in 70d598a.


Feature request- sort by start time

For sports with a 'Flex' or 'Utility' position, I'd like to automatically sort lineups so that the player with the latest start time is used in the most flexible position.  If a football lineup has 3 RBs (one as flex), I'd like the RB who starts at 4PM to be in 'Flex' rather than one who starts at 1PM.
Thanks again as always!

I added sorting in new version


Unify test execution setups and verifications

Where possible, use the GitHubJson builder. Where possible, don't disable commit and title checks. Create a default JSON that will have correct title and commit and use builder for failure tests.

I've considered this as a part of #37

If you do the additional tasks I mentioned, you can close this issue.

Resolved in #118.


Issues on Setup (Windows)

Description:
Two Issues
Minor
Known hosts mismatch when using GIT
https://i.imgur.com/4hZFdLQ.png
Easily resolved but worth documenting
Major
Getting a error with a command, which is preventing competition.
https://i.imgur.com/LULTHXe.png
Expected Behavior:
No error and completion of installation of app
Context information:
Output of git rev-parse HEAD
{paste here}

Output of docker version
{paste here}

Output of docker-compose version
{paste here}

System info: Mac, Windows or Linux. Include which disto/version
Windows 11, up to date

Steps to reproduce the issue:

Follow install instructions
New App, with DB (Postgres)
Laravel 10

Stacktrace & Additional info:
{paste here}

Thanks for your submission! I'll take a look at this later today.

@matthiscock The Postgres issue has been resolved in version 1.6.1. Docker Desktop doesn't update versions right away when they're published, so it could take a couple of hours.
I'll be reviewing some good ways to resolve the SSH issue and will update the thread once done.

I can confirm this is sorted - and now proceeds throught.
The known hosts is still there (but on your radar)

@matthiscock In the screenshot you provided, that was due to a permissions issue. I pushed a fixed in the next release that will automatically adjust the permissions of the SSH file to be more secure, so that should no longer be an issue.
I see a few others have experienced the known hosts issue as well, though. I'm adding a troubleshooting section to the documentation, though.

Documentation has been added for Unix systems, and an installation setup screen has been added to the Docker extension to aid with it: https://app-ignition.com/docs/1.0/installation#git


dump RSSI?

Step 1: Describe your environment

OS version: macOS 10.13.1
Arduino IDE version: 1.8.5
MFRC522 Library version: mast-branch?
Arduino device: uno r3
MFRC522 device: funduino

Step 2: Describe the problem
is it possible to get RSSI information from RC522? Must I use a cottonwood like this: http://www.instructables.com/id/Arduino-to-Cottonwood-UHF-RFID-Reader-RSSI-Command/?

Just look into the data sheet, I did not found anything about a rssi-information.
So no, it is not possible.

There are some information about rssi, i just do not know how to get it. Page 59, section <IP_ADDRESS>.
Theoretically, the chip has to identify the signal strength and then read the data. Section <IP_ADDRESS> talks about signal strength threshold, and it is possible to do some setting in arduino library to change the threshold.
I just want to find a way to obtain the detected signal strength. Maybe change the RC522 circuit?

Page 59, section <IP_ADDRESS>: means how much power is used to send the signal.
The section <IP_ADDRESS> RxThresholdReg register offers some information about the signal strength. But it is just the minimum strength and it seems that the measured strength is not written to any register.

Is it possible to start the minimum strength with a small value and increase it with a interval? Once we could read the data inside ID card, once stop the increasing. This may give us the minimum strength required to read the data and this will also be very helpful for my research.
PS: I am a physics+chemistry guy. I'm not familiar with the chip or coding.

Problem solved with this: https://github.com/miguelbalboa/rfid/issues/43
Use PCD_WriteRegister function and loops could done my idea to get RSSI, approximately.


fsSize from Docker container

Is your feature request related to a problem? Please describe.
Hello, I am migrating from Telegraf to own nodejs solution. I run systeminformation in a docker container (all my applications are in Docker).
For Telegraph, with help of its documentation, I had the docker-compose :
    volumes:
      - ./telegraf.conf:/etc/telegraf/telegraf.conf:ro
      - ./telegraf.d:/etc/telegraf/telegraf.d:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /:/hostfs:ro
    environment:
      HOST_ETC: /hostfs/etc
      HOST_PROC: /hostfs/proc
      HOST_SYS: /hostfs/sys
      HOST_VAR: /hostfs/var
      HOST_RUN: /hostfs/run
      HOST_MOUNT_PREFIX: /hostfs

I tried to do the same with systeminformation, but fsSize returns [] (empty array).
Describe the solution you'd like
I'd like to do like Telegraf, mount my root host fs into a docker container folder and systeminformation would be able to give me informations about it (free size, total size, used size at minimum, read/write stats if possible)
Describe alternatives you've considered
If not possible, I will make my own exec() but am I alone ? Should be good to support systeminformation in docker container.
Additional context
No
Regards

systeminformation seems not to support to be inside a Docker container. I close the ticket for my side, I called df and parse, and same for listProcesses listing /proc/[0-9]+/stat
Regards


Update editor.md

For some reason the substitution tag syntax was <% %> when it should be [%field_name%] for custom fields and [sender_info] for sender information, unsubscribe and weblink tags.

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @ppruitt-sg,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Can not build on macOS

Running flutter run -d macos gives:
error: No signing certificate "Developer ID Application" found: No "Developer ID Application" signing certificate matching team ID "S3TL5AY6Y3" with a private key was found. (in target 'Runner' from project 'Runner')
** BUILD FAILED **

I changed the Team in Xcode to None and the Signing Certificate to Sign to run locally. After that a flutter run -d macos gives the following:
Running pod install...                                             14.0s
ld: warning: dylib (/Users/christian/workspace/self/flutter/examples/flutter-folio/build/macos/Build/Products/Debug/FMDB/FMDB.framework/FMDB) was built for newer macOS version (10.12) than being linked (10.11)
ld: warning: dylib (/Users/christian/workspace/self/flutter/examples/flutter-folio/build/macos/Build/Products/Debug/BoringSSL-GRPC/openssl_grpc.framework/openssl_grpc) was built for newer macOS version (10.12) than being linked (10.9)
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/win32-1.7.4+1/lib/src/structs.dart:1111:7: Error: Struct 'ENUMLOGFONTEX' is empty. Empty structs are undefined behavior.
class ENUMLOGFONTEX extends Struct {
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/win32-1.7.4+1/lib/src/structs.dart:2835:7: Error: Struct 'BLUETOOTH_PIN_INFO' is empty. Empty structs are undefined behavior.
class BLUETOOTH_PIN_INFO extends Struct {
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/win32-1.7.4+1/lib/src/structs.dart:2960:7: Error: Struct 'EXCEPINFO' is empty. Empty structs are undefined behavior.
class EXCEPINFO extends Struct {}
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/win32-1.7.4+1/lib/src/structs.dart:2966:7: Error: Struct 'PROPERTYKEY' is empty. Empty structs are undefined behavior.
class PROPERTYKEY extends Struct {}
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/win32-1.7.4+1/lib/src/structs.dart:2973:7: Error: Struct 'PROPVARIANT' is empty. Empty structs are undefined behavior.
class PROPVARIANT extends Struct {}
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/win32-1.7.4+1/lib/src/structs.dart:2978:7: Error: Struct 'SAFEARRAY' is empty. Empty structs are undefined behavior.
class SAFEARRAY extends Struct {}
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/win32-1.7.4+1/lib/src/structs.dart:2985:7: Error: Struct 'CLSID' is empty. Empty structs are undefined behavior.
class CLSID extends Struct {}
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/win32-1.7.4+1/lib/src/structs.dart:2992:7: Error: Struct 'STATSTG' is empty. Empty structs are undefined behavior.
class STATSTG extends Struct {}
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/win32-1.7.4+1/lib/src/structs.dart:2999:7: Error: Struct 'NLM_SIMULATED_PROFILE_INFO' is empty. Empty structs are undefined behavior.
class NLM_SIMULATED_PROFILE_INFO extends Struct {}
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/ffi-0.1.3/lib/src/utf8.dart:23:7: Error: Struct 'Utf8' is empty. Empty structs are undefined behavior.
class Utf8 extends Struct {
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/ffi-0.1.3/lib/src/utf16.dart:16:7: Error: Struct 'Utf16' is empty. Empty structs are undefined behavior.
class Utf16 extends Struct {
      ^
../../sdks/flutter_macos_2.0.0-stable/.pub-cache/hosted/pub.dartlang.org/ffi-0.1.3/lib/src/allocation.dart:47:33: Error: Expected type 'T' to be a valid and instantiated subtype of 'NativeType'.
  final int totalSize = count * sizeOf<T>();
                                ^

Command PhaseScriptExecution failed with a nonzero exit code
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
** BUILD FAILED **

Building macOS application...
Exception: Build process failed

Here's my flutter doctor output
❯ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, 2.1.0-10.0.pre, on macOS 11.2.1 20D74 darwin-x64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Android Studio (version 4.1)
[✓] VS Code (version 1.54.0)
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

Any ideas?

I have also encountered:
error: No signing certificate "Developer ID Application" found: No "Developer ID Application" signing certificate matching team ID "S3TL5AY6Y3" with a private key was found. (in target 'Runner' from project 'Runner')
** BUILD FAILED **

So I edited this file project.pbxproj,
diff --git a/macos/Runner.xcodeproj/project.pbxproj b/macos/Runner.xcodeproj/project.pbxproj
index 7ddf124..1b61191 100644
--- a/macos/Runner.xcodeproj/project.pbxproj
+++ b/macos/Runner.xcodeproj/project.pbxproj
@@ -211,6 +211,7 @@
 					33CC10EC2044A3C60003C045 = {
 						CreatedOnToolsVersion = 9.2;
 						LastSwiftMigration = 1100;
+						ProvisioningStyle = Automatic;
 						SystemCapabilities = {
 							com.apple.Sandbox = {
 								enabled = 1;
@@ -437,8 +438,7 @@
 				CLANG_WARN_OBJC_ROOT_CLASS = YES_ERROR;
 				CLANG_WARN_RANGE_LOOP_ANALYSIS = YES;
 				CLANG_WARN_SUSPICIOUS_MOVE = YES;
-				CODE_SIGN_IDENTITY = "Apple Development";
-				CODE_SIGN_INJECT_BASE_ENTITLEMENTS = NO;
+				CODE_SIGN_IDENTITY = "-";
 				COPY_PHASE_STRIP = NO;
 				DEBUG_INFORMATION_FORMAT = "dwarf-with-dsym";
 				ENABLE_NS_ASSERTIONS = NO;
@@ -452,7 +452,6 @@
 				GCC_WARN_UNUSED_VARIABLE = YES;
 				MACOSX_DEPLOYMENT_TARGET = 10.11;
 				MTL_ENABLE_DEBUG_INFO = NO;
-				OTHER_CODE_SIGN_FLAGS = "--timestamp";
 				SDKROOT = macosx;
 				SWIFT_COMPILATION_MODE = wholemodule;
 				SWIFT_OPTIMIZATION_LEVEL = "-O";
@@ -466,22 +465,13 @@
 				ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
 				CLANG_ENABLE_MODULES = YES;
 				CODE_SIGN_ENTITLEMENTS = Runner/DebugProfile.entitlements;
-				CODE_SIGN_IDENTITY = "Developer ID Application";
-				CODE_SIGN_INJECT_BASE_ENTITLEMENTS = NO;
-				CODE_SIGN_STYLE = Manual;
+				CODE_SIGN_STYLE = Automatic;
 				COMBINE_HIDPI_IMAGES = YES;
-				DEVELOPMENT_TEAM = S3TL5AY6Y3;
-				ENABLE_HARDENED_RUNTIME = YES;
-				FRAMEWORK_SEARCH_PATHS = (
-					"$(inherited)",
-					"$(PROJECT_DIR)/Flutter/ephemeral",
-				);
 				INFOPLIST_FILE = Runner/Info.plist;
 				LD_RUNPATH_SEARCH_PATHS = (
 					"$(inherited)",
<EMAIL_ADDRESS> 				);
-				OTHER_CODE_SIGN_FLAGS = "--timestamp";
 				PROVISIONING_PROFILE_SPECIFIER = "";
 				SWIFT_VERSION = 5.0;
 			};
@@ -521,8 +511,7 @@
 				CLANG_WARN_OBJC_ROOT_CLASS = YES_ERROR;
 				CLANG_WARN_RANGE_LOOP_ANALYSIS = YES;
 				CLANG_WARN_SUSPICIOUS_MOVE = YES;
-				CODE_SIGN_IDENTITY = "Apple Development";
-				CODE_SIGN_INJECT_BASE_ENTITLEMENTS = NO;
+				CODE_SIGN_IDENTITY = "-";
 				COPY_PHASE_STRIP = NO;
 				DEBUG_INFORMATION_FORMAT = dwarf;
 				ENABLE_STRICT_OBJC_MSGSEND = YES;
@@ -543,7 +532,6 @@
 				MACOSX_DEPLOYMENT_TARGET = 10.11;
 				MTL_ENABLE_DEBUG_INFO = YES;
 				ONLY_ACTIVE_ARCH = YES;
-				OTHER_CODE_SIGN_FLAGS = "--timestamp";
 				SDKROOT = macosx;
 				SWIFT_ACTIVE_COMPILATION_CONDITIONS = DEBUG;
 				SWIFT_OPTIMIZATION_LEVEL = "-Onone";
@@ -576,8 +564,7 @@
 				CLANG_WARN_OBJC_ROOT_CLASS = YES_ERROR;
 				CLANG_WARN_RANGE_LOOP_ANALYSIS = YES;
 				CLANG_WARN_SUSPICIOUS_MOVE = YES;
-				CODE_SIGN_IDENTITY = "Apple Development";
-				CODE_SIGN_INJECT_BASE_ENTITLEMENTS = NO;
+				CODE_SIGN_IDENTITY = "-";
 				COPY_PHASE_STRIP = NO;
 				DEBUG_INFORMATION_FORMAT = "dwarf-with-dsym";
 				ENABLE_NS_ASSERTIONS = NO;
@@ -591,7 +578,6 @@
 				GCC_WARN_UNUSED_VARIABLE = YES;
 				MACOSX_DEPLOYMENT_TARGET = 10.11;
 				MTL_ENABLE_DEBUG_INFO = NO;
-				OTHER_CODE_SIGN_FLAGS = "--timestamp";
 				SDKROOT = macosx;
 				SWIFT_COMPILATION_MODE = wholemodule;
 				SWIFT_OPTIMIZATION_LEVEL = "-O";
@@ -605,22 +591,13 @@
 				ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
 				CLANG_ENABLE_MODULES = YES;
 				CODE_SIGN_ENTITLEMENTS = Runner/DebugProfile.entitlements;
-				CODE_SIGN_IDENTITY = "Developer ID Application";
-				CODE_SIGN_INJECT_BASE_ENTITLEMENTS = NO;
-				CODE_SIGN_STYLE = Manual;
+				CODE_SIGN_STYLE = Automatic;
 				COMBINE_HIDPI_IMAGES = YES;
-				DEVELOPMENT_TEAM = S3TL5AY6Y3;
-				ENABLE_HARDENED_RUNTIME = YES;
-				FRAMEWORK_SEARCH_PATHS = (
-					"$(inherited)",
-					"$(PROJECT_DIR)/Flutter/ephemeral",
-				);
 				INFOPLIST_FILE = Runner/Info.plist;
 				LD_RUNPATH_SEARCH_PATHS = (
 					"$(inherited)",
<EMAIL_ADDRESS> 				);
-				OTHER_CODE_SIGN_FLAGS = "--timestamp";
 				PROVISIONING_PROFILE_SPECIFIER = "";
 				SWIFT_OPTIMIZATION_LEVEL = "-Onone";
 				SWIFT_VERSION = 5.0;
@@ -634,22 +611,13 @@
 				ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
 				CLANG_ENABLE_MODULES = YES;
 				CODE_SIGN_ENTITLEMENTS = Runner/Release.entitlements;
-				CODE_SIGN_IDENTITY = "Developer ID Application";
-				CODE_SIGN_INJECT_BASE_ENTITLEMENTS = NO;
-				CODE_SIGN_STYLE = Manual;
+				CODE_SIGN_STYLE = Automatic;
 				COMBINE_HIDPI_IMAGES = YES;
-				DEVELOPMENT_TEAM = S3TL5AY6Y3;
-				ENABLE_HARDENED_RUNTIME = YES;
-				FRAMEWORK_SEARCH_PATHS = (
-					"$(inherited)",
-					"$(PROJECT_DIR)/Flutter/ephemeral",
-				);
 				INFOPLIST_FILE = Runner/Info.plist;
 				LD_RUNPATH_SEARCH_PATHS = (
 					"$(inherited)",
<EMAIL_ADDRESS> 				);
-				OTHER_CODE_SIGN_FLAGS = "--timestamp";
 				PROVISIONING_PROFILE_SPECIFIER = "";
 				SWIFT_VERSION = 5.0;
 			};

Here is the error I am getting after that
/Users/a/Desktop/PL/flutter-folio/macos/Pods/BoringSSL-GRPC/src/ssl/t1_lib.cc:3319:9: error: use of undeclared identifier 'SSL_get_secure_renegotiation_support'; did you mean 'GRPC_SHADOW_SSL_get_secure_renegotiation_support'?
      !(SSL_get_secure_renegotiation_support(ssl) &&
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        GRPC_SHADOW_SSL_get_secure_renegotiation_support
In file included from /Users/aivan/Desktop/PL/flutter-folio/macos/Pods/BoringSSL-GRPC/src/ssl/t1_lib.cc:109:
/Users/a/Desktop/PL/flutter-folio/macos/Pods/BoringSSL-GRPC/src/include/openssl/ssl.h:4662:5: note: expanded from macro 'SSL_get_secure_renegotiation_support'
    SSL_get_secure_renegotiation_support
    ^
/Users/a/Desktop/PL/flutter-folio/macos/Pods/BoringSSL-GRPC/src/include/openssl/ssl.h:1590:20: note: 'GRPC_SHADOW_SSL_get_secure_renegotiation_support' declared here
OPENSSL_EXPORT int SSL_get_secure_renegotiation_support(const SSL *ssl);
                   ^
In file included from <built-in>:1:
/Users/a/Desktop/PL/flutter-folio/macos/Pods/Target Support Files/BoringSSL-GRPC/BoringSSL-GRPC-prefix.pch:2489:46: note: expanded from macro 'SSL_get_secure_renegotiation_support'
#define SSL_get_secure_renegotiation_support GRPC_SHADOW_SSL_get_secure_renegotiation_support
                                             ^
1 error generated.
note: Using new build system
note: Planning build
note: Constructing build description
** BUILD FAILED **

Here is my dev environment
[✓] Flutter (Channel stable, 2.0.1, on Mac OS X 10.14.6 18G8022 darwin-x64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[!] Xcode - develop for iOS and macOS
    ! Xcode 11.3.1 out of date (12.0.1 is recommended).
      Download the latest version or update via the Mac App Store.
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] VS Code (version 1.54.1)
[✓] Connected device (2 available)

! Doctor found issues in 1 category.

If you open the project in Xcode, switch to automatic signing, choose your own development team, should work?

If you open the project in Xcode, switch to automatic signing, choose your own development team, should work?

I tried but this is what I get 👇👇👇👇


Opentest Server on Non-Localhost IP

Hello, I would like to start OpenTest Server on system IP (not localhost). I dont see any configuration for doing so.
Am I missing out any thing here. Please let me know.
regards
Pranay

The OpenTest server is listening on all IP addresses available on the host - no configuration is needed.

Thanks Adrian, It worked.There was minor network configuration issue between my Windows and VMBox (Ubuntu).


DOM Element Refs

Currently it doesn't look like there is any way to get a reference to the DOM node. Setting a ref prop on the component always sets the ref to null (I think this is because it uses a functional component; React doesn't support refs on these). Styled-components allows a innerRef property for this. I looked at implementing this in emotion, but it looks like it might be a bit more complicated than I thought at first since you can wrap other styled components, not just DOM nodes.
My use-case for this is to allow focusing a DOM node based on keyboard events. For this I need a reference to the actual DOM node to call .focus(), either using findDOMNode or a ref on the actual DOM node. Any help or pointers are greatly appreciated.

I did find that you can wrap it in a Component class that works around this:
const Input = styled('input')`font-size: 16px`
class InputWrapper extends React.Component {
  render () { return <Input {...this.props} />; }
  focus () { ReactDOM.findDOMNode(this).focus(); }
}

Yes this is a needed feature.
We need to extend the api for styled to accept an innerRef option.

I tried my hand at it: https://github.com/tkh44/emotion/pull/43

Closed in #43


refactor(autowhatever_module): move to dependencies instead of devDep…

Please check if the PR fulfills these requirements

[ ] The commit(s) message(s) follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
react-autowhatever is in devDdependency and in peerDependency. We will need to add it manually to our projects package.json files.
What is the new behavior?
react-autowhatever is a dependency.
Does this PR introduce a breaking change?

[x] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Get rid of react-autowhatever module in projects depending on react-talend-components.

When this is released, don't forget to update BREAKING_CHANGES.md to include a log on the next version


4 viruses

before it was just 1 trojan sure that was fine no big deal but now there is 2 trojans and 2 hacktools???

false positives, since the dll in the file uses functions that can be triggered as a virus or malware in general.
software is safe, been using it since forever and can confirm nothing happened to my pc so yours is also good.

False positives, and 3 of these are not related to R3nzSkin but to Extreme Injector.


error in python example: detect_scenes_file() takes exaclty 2 arguments (3 given)

Hello! This is an excellent project and thanks for your contribution!
I just try your demo in python:
import scenedetect

scene_list = []        # Scenes will be added to this list in detect_scenes().
path = 'my_video.mp4'  # Path to video file.

# Usually use one detector, but multiple can be used.
detector_list = [
    scenedetect.detectors.ThresholdDetector(threshold = 16, min_percent = 0.9)
]

video_framerate, frames_read = scenedetect.detect_scenes_file(
    path, scene_list, detector_list)

# scene_list now contains the frame numbers of scene boundaries.
print scene_list

# create new list with scene boundaries in milliseconds instead of frame #.
scene_list_msec = [(1000.0 * x) / float(video_fps) for x in scene_list]

# create new list with scene boundaries in timecode strings ("HH:MM:SS.nnn").
scene_list_tc = [scenedetect.timecodes.get_string(x) for x in scene_list_msec]

When I run the simple python example, I encountered following problems:
TypeError: detect_scenes_file() takes exactly 2 arguments (3 given)

And I find no other people have the same problem with me, can anybody help me with this issue? Thanks a lot!

Looks like it was changed about four months ago but the docs weren't updated:
https://github.com/Breakthrough/PySceneDetect/commit/a18ea066abf867c27459b258faf300a0a625bfff
Looks like it needs a scene manager object...
I'm going to try from main() in https://github.com/Breakthrough/PySceneDetect/blob/fc8d251b7f36ef1c2381e1276dc2966ad181ea3d/scenedetect/init.py

Thanks for responding so quickly. It looks like that is compatible with the cli approach. When called within a script though I've been having problems.
File "//anaconda/lib/python3.5/site-packages/PySceneDetect-0.3.6-py3.5.egg/scenedetect/manager.py", line 55, in init
AttributeError: 'dict' object has no attribute 'detection_method

@robin-garnham Whoops, my apologies, I glanced right over the args argument.  Yes, I'll have to add a page to the documentation about how that dict should be formatted.

Wow this projects is great. I also used version 0.3 so I will wait on updated docs. Thank you!

Ok what i have right now is working solution:
`
  class PySceneDetectArgs(object):
    def __init__(self, input, type='content'):
    self.input = input
    self.detection_method = type
    self.threshold = None
    self.min_percent = 95
    self.min_scene_len = 15
    self.block_size = 8
    self.fade_bias = 0
    self.downscale_factor = 1
    self.frame_skip = 2
    self.save_images = False
    self.start_time = None
    self.end_time = None
    self.duration = None
    self.quiet_mode = True
    self.stats_file = None

  scene_detectors = scenedetect.detectors.get_available()

  smgr_content   = scenedetect.manager.SceneManager(PySceneDetectArgs(input=video_path, type='content'),   scene_detectors)
  #smgr_threshold = scenedetect.manager.SceneManager(PySceneDetectArgs(input=video_path, type='threshold'), scene_detectors)

  scenedetect.detect_scenes_file(path=video_path, scene_manager=smgr_content)
  #scenedetect.detect_scenes_file(path=video_path, scene_manager=smgr_threshold)

  detected_scenes = smgr_content.scene_list

`

Hi There,
where can we find a working example of a python program matching the newly intriduced API changed ( v0,4)?
thanks!

Hello everyone;
Unfortunately, the v0.4 API isn't completed yet, due to major structural changes to PySceneDetect as a whole, and thus the documentation is not written yet.  However, I do plan on moving to v1.0 once a stable API has been implemented.
In the meantime, you may want to consider using PySceneDetect v0.3.5 if that meets your requirements.  My apologies for having to use a workaround for the time being - I hope to have a stable API implemented by the end of next month, now that the command-line functionality is stable.


Remove duplicate (case sensitive) recent workspace/folder names on the welcome screen

On the welcome window (on start up of VSCode or opening a new window), there is the Recent workspaces/folder section. If I edit the name of a folder in the recents list outside of VSCode and open the same folder again in VSCode, both the old and new folder names will appear again on the welcome window. This behavior repeats on every subsequent folder rename. Since  they both refer to the same folder, it seems redundant to include the old names, unless there was a deliberate decision to keep this behavior. If this request is approved I would like to work on it.
Steps to recreate:

Open VSCode or open a new window in VScode if already open
Under "Start" section, do "open folder"
Close that folder's window on VSCode
Rename the folder (outside of VSCode) only with different casing (e.g. "folder1" to "Folder1")
Open a new window on VSCode, repeat step 2 by selecting the same folder but with the "new" name
Open a new window, and both folder names appear under "Recent"

Example shown in screenshot below -

Encountered on the following version of VSCode:
Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-11T01:11:34.018Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.1.0
macOS: 11.01

Hm, interestingly we don't seem to be very clever to find duplicates around here:
https://github.com/microsoft/vscode/blob/5e6a2779f63c3a1a5d770498c4ead5fd8f34859a/src/vs/platform/workspaces/electron-main/workspacesHistoryMainService.ts#L429-L439


test_conf failing

The test fail with:
04-test_conf.t ..................... 1/4
1..4
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:systray:initialize_systray Could not create tray window
wine /home/travis/build/openssl/openssl/test/confdump.exe /home/travis/build/openssl/openssl/test/recipes/04-test_conf_data/dollarid_off.conf > test_conf-dollarid_off.conf-stdout => 0
ok 1 - dumping dollarid_off.conf
not ok 2 - comparing the dump of dollarid_off.conf with dollarid_off.txt
#   Failed test 'comparing the dump of dollarid_off.conf with dollarid_off.txt'
#   at ../test/recipes/04-test_conf.t line 34.
#          got: '1'
#     expected: '0'
wine /home/travis/build/openssl/openssl/test/confdump.exe /home/travis/build/openssl/openssl/test/recipes/04-test_conf_data/dollarid_on.conf > test_conf-dollarid_on.conf-stdout => 0
ok 3 - dumping dollarid_on.conf
not ok 4 - comparing the dump of dollarid_on.conf with dollarid_on.txt
#   Failed test 'comparing the dump of dollarid_on.conf with dollarid_on.txt'
#   at ../test/recipes/04-test_conf.t line 34.
#          got: '1'
#     expected: '0'
# Looks like you failed 2 tests of 4.
04-test_conf.t ..................... Dubious, test returned 2 (wstat 512, 0x200)

@kroeckx If this a platform specific issue, then you may need to address it?


No access

Please fix it!!!!!!!
After latest update I can’t open token with Touch ID.... app does not work!!!!
Please fix it!!!!!!!!
Please fix it!!!!!!!!!!!!!!!!!!
It is very annoying!!!!!!!
Fix it !!!!!!!!!!!

Could you test and confirm that the following TestFlight build fixes this issue?
https://testflight.apple.com/join/kSkazqq7

Please fix it!!!!!!!
After latest update I can’t open token with Touch ID.... app does not work!!!!
Please fix it!!!!!!!!
Please fix it!!!!!!!!!!!!!!!!!!
It is very annoying!!!!!!!
Fix it !!!!!!!!!!!

I reverted the authentication settings that were causing issues and pushed a 2.2.1 release to the app store, please check it.

Ok, app opens but token does not require Touch ID any more to perform codes , is that normal
??
Thank you for your answer
Στάλθηκε από το iPhone μου
2 Δεκ 2020, 19:03, ο χρήστης «Justin Stephenson <notifications<EMAIL_ADDRESS>έγραψε:
Please fix it!!!!!!!
After latest update I can’t open token with Touch ID.... app does not work!!!!
Please fix it!!!!!!!!
Please fix it!!!!!!!!!!!!!!!!!!
It is very annoying!!!!!!!
Fix it !!!!!!!!!!!
I reverted the authentication settings that were causing issues and pushed a 2.2.1 release to the app store, please check it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/freeotp/freeotp-ios/issues/217#issuecomment-737364429, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AR4P7E5U7QI47QBCEASEIZLSSZXNRANCNFSM4UCWW75A.

Ok, app opens but token does not require Touch ID any more to perform codes , is that normal ?? Thank you for your answer Στάλθηκε από το iPhone μου 2 Δεκ 2020, 19:03, ο χρήστης «Justin Stephenson <notifications<EMAIL_ADDRESS>έγραψε: Please fix it!!!!!!! After latest update I can’t open token with Touch ID.... app does not work!!!! Please fix it!!!!!!!! Please fix it!!!!!!!!!!!!!!!!!! It is very annoying!!!!!!! Fix it !!!!!!!!!!! I reverted the authentication settings that were causing issues and pushed a 2.2.1 release to the app store, please check it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#217 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AR4P7E5U7QI47QBCEASEIZLSSZXNRANCNFSM4UCWW75A.

The token may need to be removed and re-added to reenable the touch ID.


[BUG] Investigate another way to map functions and objects from the pipeline.

Describe the bug
Apparently, there is a high probability of collision by using a hash function from python.
To Reproduce
This is hard to reproduce, but it happens.
Expected behavior
If you are passing to the pipeline two objects that came from the same class but they are different instances, they should be threatened as separated stanzas.
Additional context
One possible solution is to use uuid module and functions instead.

I merged the last changes and it generated a new task for each hierarchy. This needs to be rebased if we are planning to support operators with uuids.


AttributeError: 'MolTreeNode' object has no attribute 'cid'

Hi!
This error occurs when I ran sample.py in fast_molvae without any changes.
Traceback (most recent call last):
File "/fast_molvae/sample.py", line 39, in
print model.sample_prior()
File "/jtnn_vae.py", line 119, in sample_prior
return self.decode(z_tree, z_mol, prob_decode)
File "/fast_jtnn/jtnn_vae.py", line 200, in decode
jtenc_holder, mess_dict = JTNNEncoder.tensorize_nodes(pred_nodes, scope)
File "/fast_jtnn/jtnn_enc.py", line 73, in tensorize_nodes
cid = y.cid[1] if y.cid[0] == x.idx else 0
AttributeError: 'MolTreeNode' object has no attribute 'cid'
Process finished with exit code 1
Maybe something wrong with your codes?
Thank you!

Hi,
The issue is fixed. I accidentally committed some codes that are still developing :)
My apologies

Thanks！


add DatesDisabled to allow user block some dates

Sets the days that should be disabled.
Type: Array or String Default: "" or []
Usage:
{{bootstrap-datepicker-inline multidate=true datesDisabled="07/21/2015"}}
or
{{bootstrap-datepicker-inline multidate=true datesDisabled=disabledDates}}
//controller.js
export default Ember.Controller.extend({
disabledDates: ['07/21/2015', '07/22/2015', '07/23/2015']
});

Cooooool! Thank you @filipecrosk :+1:

Thank you @soulim =D
Today I saw a problem:
if you set some disabled dates you can't click on these dates, but if you navigate through keyboard it's possible to select a date. I checked on the main project(@eternicode) and this problem remains there. I think the best idea is make this improvement there, but what do you think?


feat(api): adds support for Mixed Libraries

Description
Adds support for mixed libraries with movies and show types which enables syncing from mixed libraries. This also fixes the bug (for some user) where if you have manually (and/or using automatic collections option within library) created Collections library, jellyfin not syncing. Now it syncs whether you have manual/automatic/tmdb box set plugin created Collections.
Screenshot (if UI-related)
Jellyfin > Dashboard > Libraries

Jellyseerr > Settings > Jellyfin

Both Movies & Series from the mixed library synced and available

To-Dos

[x] Successful build yarn build
~- [ ] Translation keys yarn i18n:extract~
~- [ ] Database migration (if required)~

Issues Fixed or Closed

Fixes #95

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

v1.3.0
GitHub release

Your semantic-release bot :package::rocket:


Problems with HTTPS

We seem to have issues with UniProt Curated Features and SuperFamily, as they are not supporting HTTPS.
The EBI forces from today every request to run over HTTPS:
https://www.ebi.ac.uk/about/news/service-news/embl-ebi-be-https-default-1-october
I've contacted both resources, but it may take a bit until they answer.

Yup, that was my question on Friday. I expected that. I hope you find a solution.

The solution is that UniProt und SuperFamily follow the protocol or the viewer needs to pull the data somehow else.

I've talked to SuperFamily and they said that HTTPS is working. It seems like there is a little certificate issue though:

Might be worth looking into that. Haven't heard back from UniProt.

I think we need to amend this bit as well:
https://github.com/MICommunity/ComplexViewer/blob/master/src/controller/xiNET_Storage.js#L121

Hi Max,
I assume that you retrieve our page via an JS http request client side?
Then you might be blocked because secure to insecure is not allowed in some
browsers. In which case there is nothing we can do at this time.
You could introduce a proxy or use the db_fetch thing from EBI External
Services.
Our HTTPS site is not ready yet (getting the right certificates is a bit of an
hassle)
If you are doing it from the server then I have no idea why your code stopped
working.
Regards,
Jerven

Duplicate of #99 ? I think we won't be able to contact web services on other servers directly after changing to https

I guess once UniProt has got the certificate it should be fine. And we update the URLs. I created a pull request with the updated SuperFamily URL.

Thank @colin-combe for merging it! It did the trick for SuperFamily! ...but, the data coming from the SuperFamily WS seems to vary a bit in speed. But it works. I would expect the same for UniProt, once they have their certificate.

I'll deploy the version soon to PROD.

SuperFamily is now working again in production! ;-)

Cool; I guess I was wrong in what I said before... as long as they have https sorted out its fine.

Alright! I was talking to UniProt! The txt version of their results won't be available for some time. They are waiting for a certificate. But this service is supposed to deliver the same information: https://www.ebi.ac.uk/proteins/api/proteins/P69905

OK, changed to use that https json service for uniprot data.
That version deployed at complexviewer.org for you to test.
There's an open pull request to merge those changes and also the changes to show the spinner for 2 seconds then show moving proteins (see #120, think that's the best we can do at moment).

UniProt works!
I'm not sure the spinner-then-bouncing option is much better. Let's see what users are saying!

I think this can be closed as now working with https

Actually, it's broken again. It didn't work during the webinar on Wednesday and I forgot that it got fixed in the meantime. New ticket?

No new ticket, reopening is better for continuation of same issue i think.
The change that fixed this is not deployed in ComplexPortal (you can see it is still contacting an http rather than https address).
The change is also not merged into the MICommunity repo but is languishing in pull request #123
I can merge these into MICommunity repo now if you like?

Thanks, Colin. Yes, please merge into MICommunity.
@noedelta can you update the version on the CP, please? Probably got forgotten with Max leaving and I tested the new version only on the demo site.

OK, merged.
(perhaps still some problems with the initial layout to be considered)
Will leave issue open until this is sorted out...

@colin-combe yes leave open til it's updated in the CP.


Mujoco Python to Unity

The feature, motivation and pitch
hello. I would like to demonstrate the process of reproducing mujoco training data in Python and reproducing that data into a Unity Mujoco model using Unity's Mujoco plugin. Is there anything that can be helpful when creating a feature like this? Even if you try to find the information, it's not easy.
Alternatives
No response
Additional context
No response

Hello,
Can you explain a bit more what exactly are you trying to do? Transfer a control policy learned in python to Unity? Record motion trajectories as data in python, and use them/replay them in Unity?

Thank you for your reply.
To be exact, the Mujoco model is learned with Pytorch and a PT file is created. After that, I plan to use the learned PT file to play motion in Unity's Mujoco model.


Show refbot1 and refbot2 instructions in a Sandbox-only block

Context
Dan Williams pointed out that during the demo he'd felt he needed to remember the refbot1 and refbot2 email addresses. We should present this information close to where it's needed by users of the sandbox.
Changes proposed in this pull request
Add another sandbox-only block, this time on the "Details of referee" page

Guidance to review
Check the copy. Should the field be inside the box?
Things to check

[X] This code doesn't rely on migrations in the same Pull Request
[X] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[X] API release notes have been updated if necessary
[X] New environment variables have been added to the Azure config

Could be just me, but the way the styling is applied makes it look like "Email address" is a sandbox feature...

Could be just me, but the way the styling is applied makes it look like "Email address" is a sandbox feature...

I agree, maybe the email field should stay outside the purple box.

I agree about separating email from the box. Otherwise looks good.

Thanks all. Updated


Journey mapping the exit this page original and current journeys

What
Journey mapping the exit this page original and current journeys
Why
To see the changes we've made and demonstrate why the rationale behind them
Who needs to work on this
Designer
Who needs to review this
Designer
Done when

[x] Original journey is mapped for keyboard and mouse user
[x] Keyboard only journey points are documented for original journey
[ ] Current journey is mapped for keyboard and mouse user
[ ] Keyboard only journey points are documented for current journey

Need to update this with the changes made since the last time I looked at this. Will set aside some time to do so on 24/2


Timing Side-Channel When Comparing Context Handles

Knowledge of a context handle might enable an attacker to impersonate other entities within
the same locality to the DPE command handler. While an attacker could also retrieve context
handles from other localities, it was found these could not be used to execute DPE
commands.

Thanks for writing these up! We also have parallel issues for each of these in caliptra-dpe (e.g. https://github.com/chipsalliance/caliptra-dpe/issues/188).
We'll update the labels and copy your descriptions to the issues in caliptra-dpe and then close these ones. Some of the fixes will be in caliptra-sw though, so I need to go through each of these and look at where they should be tracked.

Fixed by https://github.com/chipsalliance/caliptra-dpe/pull/199


Breadcrumb

http://v4-alpha.getbootstrap.com/components/breadcrumb/

[ ] Breadcrumb
[ ] BreadcrumbItem (w/ active)

An interesting thing is the "without list markup" which bootstrap v4 documents. The way it is achieved with the PR i put up is with the use of overriding the tag via the tag prop. This seems cumbersome, but since most of the time dev user would override the the a tag with something like{Link}, it doesn't seems to bad.
Perhaps in the future, a prop on the Breadcrumb component would help it's child BreadcrumbItems.
IDK, something like
<Breadcrumb item={Link}>
  <BreadcrumbItem to={...}>Home</BreadcrumbItem>
  <BreadcrumbItem to={...}>Library</BreadcrumbItem>
  <BreadcrumbItem tag="span" active>Data</BreadcrumbItem>
</Breadcrumb>

where it would use item (or it could be called itemTag) to tell the BreadcrumbItems what tag to use by default (and if item is present, default it's own tag to nav) and thus produce this:

  Home
  Library
  Data

Let me know what you think, this can easily be a non breaking enhancement after the PR which is currently there.

@TheSharpieOne that would be a good thing to introduce to root level components that have item or inner components that depend on the root class or tag. I think that would be a great use of context.

closed via #85. Let's move discussion of this sort of change to a new issue


Closes: #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

This is an update to the validations.py script and adds a check for the first letter of the name string to not include a period or underscore.


Add concat env for shader file reading, make it more convenient for …

Xcode Capture GPU Frame as #2479 discussed
Fixes #issue
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[x] tested examples with the following backends:

[x] Metal

[ ] rustfmt run on changed code

I mean, surely the examples aren't meant to be "movable" but then new applications tend to copy code from them, so it's good to show best practices in general, not something unique to examples.

Adding absolute path for shader file results in no requirement for setting the working directory of Xcode Run action, which is easily to make mistakes to beginners. Or replace fs::read_to_string() with include_bytes!() then debugging shaders directly with Reload Shader of Xcode?

Setting up a working dir is a one time operation that you'd do for any other non-trivial project anyway, so why try to avoid it?

On Nov 30, 2018, at 10:15, Michael(LAI<EMAIL_ADDRESS>wrote:
Adding absolute path for shader file results in no requirement for setting the working directory of Xcode Run action, which is easily to make mistakes to beginners. Or replace fs::read_to_string() with include_bytes!() then debugging shaders directly with Reload Shader of Xcode?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Everyone will not have to repeat that operation. And I think it's better to provide a Xcode project within examples.

if we do provide an XCode project for the examples, can't we set the working dir in it to be relative to something (e.g. project dir)?

Sure.


fix: using StoredEvent model from config in Projectionist

In addition to what was updated in 1.0.4, this PR proposes to also use the StoredEvent model from the config in the Projectionist class.
Currently, when injecting a custom StoredEvent model in a projector, e.g. App\Events\StoredEventWithMeta $storedEvent and running the rebuild command, the following error shows up: Argument 2 passed to (..) must be an instance of App\Events\StoredEventWithMeta, instance of Spatie\EventProjector\Models\StoredEvent given. With this PR, the correct instance is passed.

This PR doesn't seem right: you can call functions on a string.

Right, that does make sense. Yet, how is this different from what happened here?

This PR doesn't seem right: you can call functions on a string.
I'm wrong, you can call static methods on a string. PR is fine! 👍

Thanks!


joint variant calling

Hi @pjedge , thank you for developing this tool.   Do you have solution to run multiple samples in same run?  Thanks.

I have nothing specific to recommend. Longshot was designed for single sample use only.


[17.11] Increase gRPC request timeout to 20 seconds when sending snapshots

Cherry pick #2391.
git cherry-pick -s -x e3e2821fe3eae707915b78215526da078d2d75a7
Cherry-pick was clean.

Ping @anshulpundir @thaJeztah

Closing PR because 17.11 branch is now cut off at 312be5983e2d2f01f0cbcc99d027b28433256705, which includes this commit.


Bug: loop or previous error module "core" when using lazy.nvim

return {
    "niuiic/code-shot.nvim",
    lazy = false,
    dependencies = {
        "niuiic/core.nvim",
    },
    opts = {}
}

On startup:
Failed to run `config` for code-shot.nvim

...al/share/nvim/lazy/code-shot.nvim/lua/code-shot/init.lua:2: loop or previous error loading module 'core'

# stacktrace:
  - /code-shot.nvim/lua/code-shot/init.lua:2
  - ~/.config/nvim/lua/core/lazy.lua:15
  - ~/.config/nvim/lua/core/init.lua:4
  - ~/.config/nvim/init.lua:1

You have another module named “code”. .config/nvim/lua/core/init.lua
Get Outlook for iOShttps://aka.ms/o0ukef

From: Vu Nhat Chuong @.>
Sent: Tuesday, August 27, 2024 4:26:44 PM
To: niuiic/code-shot.nvim @.>
Cc: Subscribed @.***>
Subject: [niuiic/code-shot.nvim] Bug: loop or previous error module "core" when using lazy.nvim (Issue #3)
return {
"niuiic/code-shot.nvim",
lazy = false,
dependencies = {
"niuiic/core.nvim",
},
opts = {}
}
On startup:
Failed to run config for code-shot.nvim
...al/share/nvim/lazy/code-shot.nvim/lua/code-shot/init.lua:2: loop or previous error loading module 'core'
stacktrace:

/code-shot.nvim/lua/code-shot/init.lua:2
~/.config/nvim/lua/core/lazy.lua:15
~/.config/nvim/lua/core/init.lua:4
~/.config/nvim/init.lua:1

—
Reply to this email directly, view it on GitHubhttps://github.com/niuiic/code-shot.nvim/issues/3, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APGYCDLFBXOUWQE5425FIQLZTQZ4JAVCNFSM6AAAAABNFS7CIWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4DQNRTHE2TIMI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Oh so since I name my main config dir as core I can't use core.nvim dep. Oops