Error oci runtime error: exec: "/opt/dockerslim/bin/sensor": permission denied

Hi!
I downloaded latest dist for mac v1.17, cloned samples from docker-slim/docker-slim/tree/master/sample/apps/node and built image from Dockerfile docker build -t my/sample-node-app .
When i tried run ./docker-slim build --http-probe my/sample-node-app and got error:
MacBook-Pro:dist_mac alex$ ./docker-slim build --http-probe my/sample-node-app
docker-slim: [build] image=my/sample-node-app http-probe=true remove-file-artifacts=false image-overrides=map[] entrypoint=[] (false) cmd=[] (false) workdir='' env=[] expose=map[]
INFO[0000] docker-slim: inspecting 'fat' image metadata...
INFO[0000] docker-slim: [sha256:4c29409bc9585b228986bf1fa544153254b4e4ad76c36fdd46f2a8557cd8aed8] 'fat' image size => 419509897 (420 MB)

INFO[0000] docker-slim: processing 'fat' image info...
INFO[0000] docker-slim: starting instrumented 'fat' container...
INFO[0000] docker-slim: created container => 0880f964950ba839968bc42940eda55d40070a6719e6b8540b350ae642adf53a
FATA[0000] docker-slim: failure                          error=API error (500): {"message":"oci runtime error: exec: \"/opt/dockerslim/bin/sensor\": permission denied"}
 stack=goroutine 1 [running]:
runtime/debug.Stack(0xa2f57, 0xc4200188a8, 0x0)
	/usr/local/go/src/runtime/debug/stack.go:24 +0x79
github.com/docker-slim/docker-slim/utils.FailOn(0x582f00, 0xc42023ee60)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/docker-slim/docker-slim/utils/errors.go:11 +0x51
github.com/docker-slim/docker-slim/master/commands.OnBuild(0x0, 0x0, 0x0, 0xc420017c20, 0x7fff5fbff721, 0x12, 0x0, 0x0, 0xc420017b01, 0x5c27d8, ...)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/docker-slim/docker-slim/master/commands/build.go:76 +0x969
main.init.1.func4(0xc42009a8c0, 0x0, 0x0)
	/GITHUB/docker-slim-org/docker-slim/apps/docker-slim/cli.go:321 +0x713
reflect.Value.call(0x36e4a0, 0x41b388, 0x13, 0x3e96a9, 0x4, 0xc420125920, 0x1, 0x1, 0xaa218, 0x3dd0a0, ...)
	/usr/local/go/src/reflect/value.go:434 +0x5c8
reflect.Value.Call(0x36e4a0, 0x41b388, 0x13, 0xc420125920, 0x1, 0x1, 0x0, 0xc4200e3910, 0xb3526)
	/usr/local/go/src/reflect/value.go:302 +0xa4
github.com/codegangsta/cli.HandleAction(0x36e4a0, 0x41b388, 0xc42009a8c0, 0x0, 0x0)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/codegangsta/cli/app.go:487 +0x1e0
github.com/codegangsta/cli.Command.Run(0x3e9bc7, 0x5, 0x0, 0x0, 0xc420015ca0, 0x1, 0x1, 0x3fbdb7, 0x3e, 0x0, ...)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/codegangsta/cli/command.go:191 +0xc3b
github.com/codegangsta/cli.(*App).Run(0xc4200f2000, 0xc42000c280, 0x4, 0x4, 0x0, 0x0)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/codegangsta/cli/app.go:240 +0x611
main.runCli()
	/GITHUB/docker-slim-org/docker-slim/apps/docker-slim/cli.go:526 +0x55
main.main()
	/GITHUB/docker-slim-org/docker-slim/apps/docker-slim/main.go:5 +0x19

A don't know how, but after reinstall docker and docker-machine error gone away. But i have new error when build:
MacBook-Pro:dist_mac alex$ ./docker-slim b 02c41a90c4ae
docker-slim: [build] image=02c41a90c4ae http-probe=false remove-file-artifacts=false image-overrides=map[] entrypoint=[] (false) cmd=[] (false) workdir='' env=[] expose=map[]
INFO[0000] docker-slim: inspecting 'fat' image metadata...
INFO[0000] docker-slim: [sha256:02c41a90c4aeaf54d4438bc73b6bd71e2cf2568f13e421f05b2954b5a1918647] 'fat' image size => 584267897 (584 MB)

INFO[0000] docker-slim: processing 'fat' image info...
INFO[0000] docker-slim: starting instrumented 'fat' container...
INFO[0000] docker-slim: created container => 70582fd314ce5d6ab62c58e45460dc7999c7ee6d8e8bbe4270ff2fe3f4da0232
INFO[0000] docker-slim: watching container monitor...
docker-slim: press <enter> when you are done using the container...

INFO[0003] docker-slim: waiting for the container finish its work...
INFO[0005] docker-slim: shutting down 'fat' container...
INFO[0005] docker-slim: processing instrumented 'fat' container info...
INFO[0005] docker-slim: generating AppArmor profile...
INFO[0005] docker-slim: building 'slim' image...
FATA[0005] docker-slim: failure                          error=no permission to read from '/Users/alex/Downloads/dist_mac/.images/02c41a90c4aeaf54d4438bc73b6bd71e2cf2568f13e421f05b2954b5a1918647/artifacts/files/run/crond.reboot' stack=goroutine 1 [running]:
runtime/debug.Stack(0xc420030010, 0x0, 0x0)
	/usr/local/go/src/runtime/debug/stack.go:24 +0x79
github.com/docker-slim/docker-slim/utils.FailOn(0x582d80, 0xc420476080)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/docker-slim/docker-slim/utils/errors.go:11 +0x51
github.com/docker-slim/docker-slim/master/commands.OnBuild(0x0, 0x0, 0x0, 0xc42000dc50, 0x7fff5fbff728, 0xc, 0x0, 0x0, 0xc42000dc00, 0x5c27d8, ...)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/docker-slim/docker-slim/master/commands/build.go:135 +0xf2c
main.init.1.func4(0xc42009a8c0, 0x0, 0x0)
	/GITHUB/docker-slim-org/docker-slim/apps/docker-slim/cli.go:321 +0x713
reflect.Value.call(0x36e4a0, 0x41b388, 0x13, 0x3e96a9, 0x4, 0xc420127920, 0x1, 0x1, 0xaa218, 0x3dd0a0, ...)
	/usr/local/go/src/reflect/value.go:434 +0x5c8
reflect.Value.Call(0x36e4a0, 0x41b388, 0x13, 0xc420127920, 0x1, 0x1, 0x0, 0xc4200e3910, 0xb3526)
	/usr/local/go/src/reflect/value.go:302 +0xa4
github.com/codegangsta/cli.HandleAction(0x36e4a0, 0x41b388, 0xc42009a8c0, 0x0, 0x0)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/codegangsta/cli/app.go:487 +0x1e0
github.com/codegangsta/cli.Command.Run(0x3e9bc7, 0x5, 0x0, 0x0, 0xc420015ca0, 0x1, 0x1, 0x3fbdb7, 0x3e, 0x0, ...)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/codegangsta/cli/command.go:191 +0xc3b
github.com/codegangsta/cli.(*App).Run(0xc4200f2000, 0xc42000c270, 0x3, 0x3, 0x0, 0x0)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/codegangsta/cli/app.go:240 +0x611
main.runCli()
	/GITHUB/docker-slim-org/docker-slim/apps/docker-slim/cli.go:526 +0x55
main.main()
	/GITHUB/docker-slim-org/docker-slim/apps/docker-slim/main.go:5 +0x19

docker-slim: [build] image=my-image http-probe=true remove-file-artifacts=false image-overrides=map[] entrypoint=[] (false) cmd=[] (false) workdir='' env=[] expose=map[]
INFO[0000] docker-slim: inspecting 'fat' image metadata...
INFO[0000] docker-slim: [sha256:c66def89ac18c8dc5a39d1f850ba0f77ade75855dd49b46867d372981a4ca882] 'fat' image size => 922202376 (922 MB)

INFO[0000] docker-slim: processing 'fat' image info...
INFO[0000] docker-slim: starting instrumented 'fat' container...
INFO[0000] docker-slim: created container => b5195f408d25dc5f25d115997324166f761f4f23daea473bfd6e78133dc81912
FATA[0000] docker-slim: failure                          error=API error (500): {"message":"oci runtime error: container_linux.go:262: starting container process caused \"exec: \\\"/opt/dockerslim/bin/sensor\\\": permission denied\"\n"}
 stack=goroutine 1 [running]:
runtime/debug.Stack(0xa2f57, 0xc420010808, 0x0)
	/usr/local/go/src/runtime/debug/stack.go:24 +0x79
github.com/docker-slim/docker-slim/utils.FailOn(0x582f00, 0xc4201e5f00)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/docker-slim/docker-slim/utils/errors.go:11 +0x51
github.com/docker-slim/docker-slim/master/commands.OnBuild(0x0, 0x0, 0x0, 0xc420019bc0, 0x7fff5fbff9c7, 0x28, 0x0, 0x0, 0xc420019b01, 0x5c27d8, ...)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/docker-slim/docker-slim/master/commands/build.go:76 +0x969
main.init.1.func4(0xc4200988c0, 0x0, 0x0)
	/GITHUB/docker-slim-org/docker-slim/apps/docker-slim/cli.go:321 +0x713
reflect.Value.call(0x36e4a0, 0x41b388, 0x13, 0x3e96a9, 0x4, 0xc420125920, 0x1, 0x1, 0xaa218, 0x3dd0a0, ...)
	/usr/local/go/src/reflect/value.go:434 +0x5c8
reflect.Value.Call(0x36e4a0, 0x41b388, 0x13, 0xc420125920, 0x1, 0x1, 0x0, 0xc4200e3910, 0xb3526)
	/usr/local/go/src/reflect/value.go:302 +0xa4
github.com/codegangsta/cli.HandleAction(0x36e4a0, 0x41b388, 0xc4200988c0, 0x0, 0x0)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/codegangsta/cli/app.go:487 +0x1e0
github.com/codegangsta/cli.Command.Run(0x3e9bc7, 0x5, 0x0, 0x0, 0xc420013cb0, 0x1, 0x1, 0x3fbdb7, 0x3e, 0x0, ...)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/codegangsta/cli/command.go:191 +0xc3b
github.com/codegangsta/cli.(*App).Run(0xc4200f2000, 0xc42000c340, 0x4, 0x4, 0x0, 0x0)
	/GITHUB/docker-slim-org/docker-slim/_vendor/src/github.com/codegangsta/cli/app.go:240 +0x611
main.runCli()
	/GITHUB/docker-slim-org/docker-slim/apps/docker-slim/cli.go:526 +0x55
main.main()
	/GITHUB/docker-slim-org/docker-slim/apps/docker-slim/main.go:5 +0x19

I seem to have gotten this same or same kind of error. Running on macOS 10.12.5 and Docker 17.06.0-ce-mac19 (18663)
Tried to run this as sudo, too, which gave a different error.

Do you still have the same problem with the latest version of Docker for Mac?

And can you also check the file permissions on the 'docker-slim-sensor' binary (ls -lh)?

I have a different error now:
docker-slim build --http-probe ed060af17b55
docker-slim: [build] image=ed060af17b55 http-probe=true remove-file-artifacts=false image-overrides=map[] entrypoint=[] (false) cmd=[] (false) workdir='' env=[] expose=map[]
INFO[0000] docker-slim: inspecting 'fat' image metadata...
INFO[0000] docker-slim: [sha256:ed060af17b559ce4d28416a9378889b9dcdc432ec2e70a104044216f481b2271] 'fat' image size => 932183856 (932 MB)
INFO[0000] docker-slim: processing 'fat' image info...
INFO[0000] docker-slim: starting instrumented 'fat' container...
INFO[0000] docker-slim: created container => 5a2c9b746e7faa16739ae78441ca3d958720c2b69c18590953dc2238c4b73ff6
FATA[0000] docker-slim: failure                          error="API error (500): {"message":"oci runtime error: container_linux.go:262: starting container process caused \"process_linux.go:339: container init caused \\\"rootfs_linux.go:57: mounting \\\\\\\"/usr/local/bin/docker-slim-sensor\\\\\\\" to rootfs \\\\\\\"/var/lib/docker/overlay2/a1ae024b792912ba2c6d3a1621434d76f256a02c206ba28412f68e367271ba33/merged\\\\\\\" at \\\\\\\"/opt/dockerslim/bin/sensor\\\\\\\" caused \\\\\\\"stat /usr/local/bin/docker-slim-sensor: input/output error\\\\\\\"\\\"\"\n"}
" stack="goroutine 1 [running]:
runtime/debug.Stack(0x0, 0xc4200ed0b8, 0x12dfe77)
	/usr/local/Cellar/go/1.8.3/libexec/src/runtime/debug/stack.go:24 +0x79
github.com/docker-slim/docker-slim/pkg/utils/errutils.FailOn(0x15f0ea0, 0xc4201f42e0)
	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/pkg/utils/errutils/errutils.go:14 +0x51
github.com/docker-slim/docker-slim/master/commands.OnBuild(0x0, 0x0, 0x0, 0xc4200178f0, 0x7fff5fbffad7, 0xc, 0x0, 0x0, 0xc4200c1a01, 0x1640980, ...)
	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/master/commands/build.go:85 +0x8eb
main.init.1.func4(0xc4200d0640, 0x0, 0xc4200d0640)
	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/cmd/docker-slim/cli.go:321 +0x9a8
github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli.HandleAction(0x13aa200, 0x1447ab0, 0xc4200d0640, 0xc42006c700, 0x0)
	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli/app.go:485 +0xd4
github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli.Command.Run(0x1431faa, 0x5, 0x0, 0x0, 0xc420015b00, 0x1, 0x1, 0x1444ed6, 0x3e, 0x0, ...)
	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli/command.go:207 +0xb6e
github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli.(*App).Run(0xc4200f4000, 0xc42000e340, 0x4, 0x4, 0x0, 0x0)
	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli/app.go:250 +0x7d0
main.runCli()
	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/cmd/docker-slim/cli.go:526 +0x55
main.main()
	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/cmd/docker-slim/main.go:5 +0x25
" version="darwin|Tetra|latest|latest|latest (go1.8.3)"

the permissions:
ls -lh /usr/local/bin/docker-slim-sensor
-rwxr-xr-x@ 1 uninen  staff   4.0M Aug  9 20:51 /usr/local/bin/docker-slim-sensor

Same error as @Uninen, also the same permissions.
❯ docker -v
Docker version 17.07.0-ce, build 87847530f7
❯ m info
ProductName:	Mac OS X
ProductVersion:	10.13
BuildVersion:	17A360a

go version
go version go1.9.1 linux/amd64
docker -v
Docker version 1.13.1, build b5e3294/1.13.1
ls -lh /opt/dockerslim/bin/
total 15M
-rwxr-xr-x. 1 vrx_jmartins vrx_jmartins  11M Nov 28 12:27 docker-slim
-rwxr-xr-x. 1 vrx_jmartins vrx_jmartins 4.2M Nov 28 12:27 docker-slim-sensor
/opt/dockerslim/bin/docker-slim build --http-probe my/sample-node-app2017/11/28 13:05:14 Couldn't set key CPE_NAME, no corresponding struct field found
2017/11/28 13:05:14 Couldn't set key REDHAT_BUGZILLA_PRODUCT, no corresponding struct field found
2017/11/28 13:05:14 Couldn't set key REDHAT_BUGZILLA_PRODUCT_VERSION, no corresponding struct field found
2017/11/28 13:05:14 Couldn't set key REDHAT_SUPPORT_PRODUCT, no corresponding struct field found
2017/11/28 13:05:14 Couldn't set key REDHAT_SUPPORT_PRODUCT_VERSION, no corresponding struct field found
2017/11/28 13:05:14 Couldn't set key PRIVACY_POLICY_URL, no corresponding struct field found
docker-slim: [build] image=my/sample-node-app http-probe=true remove-file-artifacts=false image-overrides=map[] entrypoint=[] (false) cmd=[] (false) workdir='' env=[] expose=map[]
INFO[0000] docker-slim: inspecting 'fat' image metadata...
INFO[0000] docker-slim: [sha256:fcd9befbef3023aa5d5fe14feca760515d35874fe3ac8e9c44a178e8117651ad] 'fat' image size => 451618821 (452 MB)
INFO[0000] docker-slim: processing 'fat' image info...
INFO[0000] docker-slim: starting instrumented 'fat' container...
INFO[0000] docker-slim: created container => 24cb438500abaa022ee4c7623ac5b508a79eb954d2dd3e5fd6446173167ca312
FATA[0000] docker-slim: failure                          error="API error (400): {"message":"OCI runtime create failed: container_linux.go:295: starting container process caused "exec: \"/opt/dockerslim/bin/sensor\": permission denied": unknown"}
" stack="goroutine 1 [running]:
runtime/debug.Stack(0x705ad7, 0xc42007c448, 0x0)
/usr/local/go/src/runtime/debug/stack.go:24 +0xa7
github.com/docker-slim/docker-slim/pkg/utils/errutils.FailOn(0xa6ef80, 0xc42018f7e0)
/go/src/github.com/docker-slim/docker-slim/pkg/utils/errutils/errutils.go:14 +0x51
github.com/docker-slim/docker-slim/internal/app/master/commands.OnBuild(0x0, 0x0, 0x0, 0xc4200797d0, 0x7fff0b2bcfb8, 0x12, 0x0, 0x0, 0x1, 0xacaf48, ...)
/go/src/github.com/docker-slim/docker-slim/internal/app/master/commands/build.go:85 +0x7fb
github.com/docker-slim/docker-slim/internal/app/master.init.0.func5(0xc4200aea00, 0x0, 0xc4200aea00)
/go/src/github.com/docker-slim/docker-slim/internal/app/master/cli.go:322 +0x9f5
github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli.HandleAction(0x7d3d20, 0x87f340, 0xc4200aea00, 0xc42005a500, 0x0)
/go/src/github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli/app.go:485 +0xd2
github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli.Command.Run(0x865d6f, 0x5, 0x0, 0x0, 0xc42004f340, 0x1, 0x1, 0x8793b3, 0x3e, 0x0, ...)
/go/src/github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli/command.go:207 +0xa95
github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli.(*App).Run(0xc42007ab60, 0xc42000e080, 0x4, 0x4, 0x0, 0x0)
/go/src/github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli/app.go:250 +0x758
github.com/docker-slim/docker-slim/internal/app/master.runCli()
/go/src/github.com/docker-slim/docker-slim/internal/app/master/cli.go:536 +0x55
github.com/docker-slim/docker-slim/internal/app/master.Run()
/go/src/github.com/docker-slim/docker-slim/internal/app/master/app.go:6 +0x25
main.main()
/go/src/github.com/docker-slim/docker-slim/cmd/docker-slim/main.go:8 +0x20
" version="linux|Tetra|latest|latest|latest (go1.9.2)"

@Uninen / @hiddeco sorry it took a while to respond with this issue! The permission failure is related to the location where docker-slim is installed and how Docker for Mac works. Docker doesn't mount the /usr directory, so putting anything there or its sub-directories will result in a failure. The latest release ( https://github.com/docker-slim/docker-slim/releases/tag/1.24.2 ) addresses this Docker for Mac limitation.

Hello
I'm facing this issue with CircleCi also
docker-slim[build]: state=started docker-slim[build]: info=params target=geo-ip-api continue.mode=timeout docker-slim[build]: state=inspecting.image docker-slim[build]: info=image id=sha256:4ef948de53f0a92d268cfee147272d22b2b9012bb8989a6e833dbe4960dddbfe size.bytes=798481056 size.human=798 MB docker-slim[build]: info=image.layers index=0 name='golang' tags='1.11.1' docker-slim[build]: info=image.layers index=1 name='geo-ip-api' tags='latest' docker-slim[build]: info=image.exposed_ports list='8000/tcp' docker-slim[build]: state=inspecting.container docker-slim[build]: info=container status=created id=bef71bb2e9526978fc4ce053648a28f1164acd5c6f7a58da87df9f467478494c time="2019-04-24T08:59:06Z" level=fatal msg="docker-slim: failure" error="API error (400): {"message":"oci runtime error: container_linux.go:265: starting container process caused \"exec: \\\"/opt/dockerslim/bin/sensor\\\": permission denied\"\n"} " stack="goroutine 1 [running]: runtime/debug.Stack(0x3, 0xc00029e000, 0xc00018b280) 	/usr/local/Cellar/go/1.11.1/libexec/src/runtime/debug/stack.go:24 +0xa7 github.com/docker-slim/docker-slim/pkg/utils/errutils.FailOn(0x904b40, 0xc00023af20) 	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/pkg/utils/errutils/errutils.go:14 +0x51 github.com/docker-slim/docker-slim/internal/app/master/commands.OnBuild(0x0, 0x0, 0x890800, 0xc0001c4a20, 0x19, 0xc00018e0f0, 0x7ffd16c957a9, 0xa, 0x0, 0x0, ...) 	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/internal/app/master/commands/build.go:149 +0xf48 github.com/docker-slim/docker-slim/internal/app/master.init.0.func5(0xc0001aa140, 0x0, 0xc0001aa140) 	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/internal/app/master/cli.go:543 +0x1045 github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli.HandleAction(0x7f7b80, 0x8a7670, 0xc0001aa140, 0xc000192000, 0x0) 	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli/app.go:485 +0xc8 github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli.Command.Run(0x88b0f8, 0x5, 0x0, 0x0, 0xc00008f470, 0x1, 0x1, 0x8a0a85, 0x3e, 0x0, ...) 	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli/command.go:207 +0x991 github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli.(*App).Run(0xc0000bcb60, 0xc00000e050, 0x5, 0x5, 0x0, 0x0) 	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/vendor/github.com/codegangsta/cli/app.go:250 +0x6ea github.com/docker-slim/docker-slim/internal/app/master.runCli() 	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/internal/app/master/cli.go:826 +0x55 github.com/docker-slim/docker-slim/internal/app/master.Run() 	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/internal/app/master/app.go:6 +0x25 main.main() 	/Users/q/docker-slim/docker-slim/_gopath/src/github.com/docker-slim/docker-slim/cmd/docker-slim/main.go:8 +0x20 " version="linux|Transformer|1.24.2|08f6b1729b5c6c7bfd78f07ac40dd26a24aed81d|2019-03-23_03:41:54PM (go1.11.1)"  Exited with code 1

@kareem-elsayed is this only with your CircleCi setup? What's the configuration you are using?

@kcq yes it's just in CircleCi and here is the part from config
- run:
      name: Build Image
      command: |
        docker build -t geo-ip-api .
        wget https://github.com/docker-slim/docker-slim/releases/download/1.24.2/dist_linux.tar.gz && tar xvf dist_linux.tar.gz  && chmod 755 dist_linux/*
        ./dist_linux/docker-slim build  --continue-after 1 geo-ip-api

That's super helpful! Thank you! I'll try to repro the condition to see how it can be addressed.

Thanks @kcq

Trying to repro it with the latest version (1.25.0), but i'm not getting the same behavior with a local Ubuntu setup. Setting up a CircleCi account for a full repro...

@kareem-elsayed can you share more info about your CircleCi configuration? What kind of executor are you using? docker or machine?

A quick summary of what we have in this issue... We have a couple of problems here.
First, the sensor binary doesn't always get mounted. This happens for a number of reasons depending on the host environment. For example, on Mac OS X it happens (used to happen) when you install docker-slim in a directory that Docker for Mac doesn't share. The latest version of docker-slim addresses this use case and now it mounts the sensor from a location that is shared. With CircleCI there's another reason (still figuring out the exact conditions for it).
Second, the collected files have permissions that prevent the master app from accessing them. There's a separate ticket (#73) to address that. The permissions on crond.reboot look strange though. It appears that nobody has access to the file.

Had this problem too running docker-slim in gitlab (maybe similar to CircleCi, travis, ...). Installing and running docker-slim build within the build job in a subdir of the repo worked without problems.
But I have several repo's using docker-slim so I decided to make an own docker-image containing docker-slim. Running this image in gitlab docker-slim build always fails with Error oci runtime error: exec: "/opt/dockerslim/bin/sensor": permission denied. This seems to be a mounting problem. The "solution" is to have the docker-slim files located in the repo-dir (or any sub-dir), which is mounted by default.

@khassel the initial setup worked because Gitlab uses a special /builds directory, which it mounts to all containers, so everything that ends up in it or its subdirectories will be mountable. For your own image with docker-slim you'll need to make sure it's installed to /builds/docker-slim or something like this. This Gitlab ticket is a nice reference about the 'problem': https://gitlab.com/gitlab-org/gitlab-ce/issues/41227
There's a couple of enhancements planned for 1.25.1 where one of them will use a different way to transfer artifacts to and from the target container without using mounted volumes, so it's no longer a problem for these types of environments.
By the way, I recently created a gitter channel ( https://gitter.im/docker-slim/community ), which might be easier to use for more interactive discussions :-) Speaking of the more interactive discussions... would you be open to chatting on Skype, Google Hangout, WhatsApp, Telegram or some other private communication forum? I'd love to get your feedback about the planned CI/CD enhancements and the capabilities you wish were there.

For your own image with docker-slim you'll need to make sure it's installed to /builds/docker-slim or something like this.

no, this didn't work, because the mount overrides the existing /builds dir. But you can copy the files after mounting ...

There's a couple of enhancements planned for 1.25.1 where one of them will use a different way to transfer artifacts to and from the target container without using mounted volumes, so it's no longer a problem for these types of environments.

so I'm waiting for this release ...

By the way, I recently created a gitter channel ( https://gitter.im/docker-slim/community ), which might be easier to use for more interactive discussions :-) Speaking of the more interactive discussions... would you be open to chatting on Skype, Google Hangout, WhatsApp, Telegram or some other private communication forum? I'd love to get your feedback about the planned CI/CD enhancements and the capabilities you wish were there.

Thanks :-) I'm happy so far and I'm not a native english speaker, so it's always a language struggle for me, so chatting would be difficult and time consuming ...

Yes, that's what I meant to say about the /build directory, but I didn't do a good job there :-) You should be able to use the global --state-path flag to point to a /build sub-directory, so docker-slim will copy its sensor there along with using it for the build artifacts when it's minifying the images.
No worries, just wanted to make sure I could answer your question and provide extra background information.

@kcq Hi! I'm still having "permission denied" issues when running docker-slim in gitlab-ci. I joined gitter, maybe we can talk over there so I can give you faster info about the issue?
Let me know when you're around.
Thanks.

Do you have more information about your setup?

Hey Kyle, I'm having another issue now: we install aws-cli on our base image and then run docker-slim on it. Thing is, when the .slim image comes up, aws cli is gone. For example:
FROM docker:latest

#Install Python
RUN apk add --update python python-dev py-pip curl jq make git && \
    pip install awscli --upgrade \
    && mv $(find / -name aws) /usr/bin

If I go the base image, the aws-cli appears in /usr/bin.
After that, when we apply docker-slim to it, apps such as git and aws-cli are gone. They don't show up in any directory.
Can you help with this?
Thanks.

@chuleh , yes, there are a number of --include flags you can leverage potentially. --include-path is a generic flag to include a file or a directory (--include-path-file is a more convenient version where you have a bunch of include paths from a file). There are a few other --include flags to make it easier to include apps/binaries.
What is the base image function? Is it just a set of tools or is it one main tool with a number of optional tools or is it actually an application container image with a server running in it?
docker-slim can minify container images with cli tools. it's easier when it's a single tool though, so you don't have to use any extra flags. when you minify a cli container image you specify the command line parameters for the tool, so docker-slim knows about the tool and what it needs. one of the future features will allow you to specify multiple commands to run with the container image, so you it'll be possible to have different commands for different tools.

@chuleh The new 1.26.0 release has a better containerized environment support... (there's also a docker container distribution for docker-slim: dslim/docker-slim; more info in the repo readme). Give it a try if you have cycles... Let me know how it goes. Really appreciate your feedback!

add --check-version=false parameter fix this error

@chuleh curious if you had much luck with your aws cli container image :) one other possible way to make sure everything gets included is to mount a test script that runs a number of important aws cli commands and temporarily setting the cmd (with --cmd) or entrypoint (with --entrypoint) to that script when executing the docker-slim build command.


[Help]: more duration predictor details & '50' meaning of target len in text2semantic of MaskGCT

Problem Overview
(Briefly and clearly describe the issue you're facing and seeking help with.)
I want to understand whether the duration predictor is prepared for getting duration as training data or not. Additionally, I'm also curious about number '50' of rule-based calculating duration in text2semantic.
Steps Taken
1. duration predictor
In this paper, we also train a flow matching [45]
based duration prediction model to predict the total duration conditioned on the text and prompt
speech duration, leveraging in-context learning. More details can be found in Appendix A.5.
Is the duration predictor used for generating duration as training input for text to semantic model? Or just given approximated duration is used for evaluating?
2. '50' meaning of target len in text2semantic of MaskGCT
Below code is snippet of text2semantic in maskgct.
@torch.no_grad()
def text2semantic(
    self,
    prompt_speech,
    prompt_text,
    prompt_language,
    target_text,
    target_language,
    target_len=None,
    n_timesteps=50,
    cfg=2.5,
    rescale_cfg=0.75,
):
    prompt_phone_id = g2p_(prompt_text, prompt_language)[1]
    target_phone_id = g2p_(target_text, target_language)[1]

    if target_len is None:
        target_len = int(
            (len(prompt_speech) * len(target_phone_id) / len(prompt_phone_id))
            / 16000
            * 50
        )
    else:
        target_len = int(target_len * 50)

I was trying to find out this value in paper, but i wasn't.
I'm curious about what constant number '50' is. I guess this number is minimum frame numbers for uttering a one phoneme. Please let me know this number 🥲

I'm also curious about what constant number '50' is. Looking forward to the author's reply!


Reports that remote media can cease downloading

I haven't seen this personally, however there are some reports that remote media just stops being downloaded without warning.
The running theory was that this was #92 however that's been relatively proven to not be the case.
We're probably leaking something somewhere though, given the issue is resolved by restarting the service.
More investigation required (and reproduction steps, if possible).

This doesn't seem to be happening anymore


New package: ActiveSetPursuit v1.0.0

Registering package: ActiveSetPursuit
Repository: https://github.com/MPF-Optimization-Laboratory/ActiveSetPursuit.jl
Created by: @mpf
Version: v1.0.0
Commit: 2eec6bacf1182e0e59bf26955113696f529993f5
Git reference: HEAD
Description: Sparse least-squares solver
Release notes:

Derived from the original Matlab version, found at https://github.com/MPF-Optimization-Laboratory/asp

Please close this PR. We will register it as 0.x.y initially.


Add unwrap_or_raise()

Fix: #93

the basics here look good 👍🏼  but the API feels not so nice. i think we can do better, but let's keep that discussion in #93

💡 just brainstorming…
i don't quite like how this proposed api makes it almost inevitable to use a lambda construct for something that's supposed to do something simple. (fwiw, i don't like lambdas in general, in python at least.)
maybe this could handle Type[BaseException] in a special way? so that it can be either a callable (such as a lambda) or an exception class directly?
res.unwrap_or_raise(ValueError)  # raise ValueError()

however, nice errors, which this is about in the first place, typically require more than just an exception class, e.g. a message:
res.unwrap_or_raise(ValueError, "foo")  # raise ValueError("foo")

but sometimes it's not just a string, so maybe also this?
res.unwrap_or_raise(MyException, *args, **kwargs)  # raise MyException(*args, **kwargs)

… but these may be hard to type correctly.
passing an exception instance could work but would always construct it, even when it's not needed:
res.unwrap_or_raise(ValueError("foo"))  # hmmm :/

this also needs docs in the readme

this also needs docs in the readme

Brief explanation for the new API added. I'm not sure it's enough to explain the API as it's a bit strange compared to others, so let me know if more detail needs.

Thanks @ileixe , let's see if it passes the tests and if so I'll test the changes locally and merge it if it all looks good.

Codecov Report

Merging #95 (297c0a7) into master (eb9350f) will increase coverage by 0.03%.
The diff coverage is 100.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #95      +/-   ##
==========================================
+ Coverage   99.12%   99.15%   +0.03%
==========================================
  Files           3        3
  Lines         341      352      +11
==========================================
+ Hits          338      349      +11
  Misses          3        3

Impacted Files
Coverage Δ

src/result/result.py
99.30% <100.00%> (+0.02%)
:arrow_up:

tests/test_result.py
99.03% <100.00%> (+0.03%)
:arrow_up:

@francium Added. Thanks!

Does it make sense to add an overload for usage where an Exception is already the .err value?
    def unwrap_or_raise(self) -> NoReturn:
        """
        The contained result is ``Err``, so raise the exception with the value.
        """
        raise self._value

Our code typically already uses a BaseException object for the err part of the tuple, so this would make more sense for us to adopt. This allows the inner functions to provide more detail about their exception in a pythonic way. For example, a FastAPI app might want to pass along HTTPException(status_code=401, detail="User does not exist."), which would not be possible to use with unwrap_or_raise in its current state.
Happy to make a PR if there's interest. Though passing Exception in the err does go against the style that's currently in the readme.

@WesleyYue can you please open a new issue for what you're describing. We can discuss it there rather than this old PR.


validate scheme inputs

Still needs quite a bit of work, the problem I was running into was having the voting machine configs use the same form validation object because of the switch in type from Params to VotingMachineParams.
@sogasg do you think having separate  formError objects with different event handlers make sense? Also some of the valueTypes set inside of voting machines don't map to an explicit type...
Solves #86

My thinking was that it might be better to add a validate function to the Param type so that we could use the param’s validate function for validating the param. Instead of validating against the valueType. This validation function could take the value and return an array or object of errors or empty if no errors. Then we could use that function when validating.
Do you think that makes sense?

So before setting the ‘’’SchemeConfig’’’ in the state we’d call this validate function, correct? What would the predicate be other than to check the ‘’’valueType’’’


Redesign UntypedCache, Cache hierarchy

If possible remove UntypedCache from the design or hide it from the public API at least

[ ] change to interface
[ ] evaluate to change scope to internal

obsolete


[PostGIS] Support of curves geometries (SQL/MM Part 3) in map viewer

Is your feature request related to a problem? Please describe.
I really like the possibility to have an overview of PostGIS data in the map viewer, this is an amazing feature that I couldn't live without. However, curves geometries are currently not supported.
Describe the solution you'd like
Support of curves geometries (SQL/MM Part 3) in map viewer.
Additional context

SQL/MM Part 3

Hello @rbovard,
Thanks for the feature request.
We need to investigate possible solutions as the library we're using for rendering doesn't support curves out of the box.

Thanks a lot for the dev @ShadelessFox, but it seems to not work here (tested with version 23.1.3)
In some case, I have only a line on the map (but not at the right place):

SRID=2056;LINESTRING (2554021.510361592 1146045.9171061674, 2554011.061413642 1146056.4932663445)
Or no geom at all with Z value:

SRID=2056;LINESTRING (2553886.8849250823 1145802.2807940794 375.55, 2553881.9850559025 1145812.2269134985 375.38)

Hello @rbovard,
The provided geometries work fine for me. Maybe the viewer has different SRID?

No it's correct, I've checked that:

But it I run the same query as you, it's working:
SELECT st_geomfromewkt('SRID=2056;LINESTRING (2554021.510361592 1146045.9171061674, 2554011.061413642 1146056.4932663445)')

So the issue is on the "stored" data?

Also works for me. It might depend on the database's data type (I'm testing against PostgreSQL 11.6).
I'm also unsure why we are discussing this issue here, as it's seemingly unrelated to curved geometries.
Can you please create a separate issue, specify the database and attach log files?

Oops, I'm sorry. I was sure my table was with based with curved geometries.
I'll do that.

Mmm, after another check my column is in fact definded as geometry(compoundcurvez, 2056) but the geometry inside is stored as linestring.
Should I open another issue or it's better to continue here?

I found the problem.

We linearize geometries even for display purposes on the grid, not only in the viewer.
Explicit SRID=2056; prefix is not stripped for some reason when passed to the viewer.

Please create a separate issue.

Thanks for the research, I'v created 2 separate new issues.


Allow packages to match regardless of punctuation

 As a user I need packages to match regardless of punctuation, so that I don't need to know how spack named it.


Improve the UI  Apply page card .

The cards of apply page is not good I would like to improve that card under GSSOC'24 and Hacktofest'24
thank you

@Shubham-Zone plz assign me on this issue under GSSOC'24 and Hacktofest'24 and levels 2/3 labels

@Himanshu-kumar025 this interface is not in my app


Save State Performance

Hey,  I'm have come across a minor performance issue when saving state in the subscriber.  In this instance there is a simple fix available too, but I thought I would reach out to see what people think about it first.
So, you're wanting to persist the data, without getting in the way of your code performance.  Then why are we blocking the saveState waiting for the write of data to the data storage in question.
The problem
The current implementation causes waits for localStorage or any other storage method to block the current thread waiting until its performed its operation.
This can cause the application to become non-responsive for a moment while we're writing this state to disk.
/* helper to simulate the delay in localStorage writing */
function wait(ms){
   var start = new Date().getTime();
   var end = start;
   while(end < start + ms) {
     end = new Date().getTime();
  }
}

/* ORIGINAL blocking version */
const myPlugin = store => {
  store.subscribe((mutation, state) => {
    console.time('VuexSubscription')
    wait(7000)
    console.timeEnd('VuexSubscription')
  })
}

The proposal
Make the write method asynchronous.  In this example we go one more and use requestIdleCallback in order to find some guaranteed free time and avoid jank.
/* PROPOSED non blocking version */
// Shim `requestIdleCallback`
const requestIdleCallback = window.requestIdleCallback || (cb => {
  let start = Date.now();
  return setTimeout(() => {
    cb({
      didTimeout: false,
      timeRemaining() {
        return Math.max(0, 50 - (Date.now() - start))
      }
    })
  }, 1);
})

const myPlugin = store => {
  store.subscribe((mutation, state) => {
    console.time('VuexSubscription')
    requestIdleCallback(() => {
      wait(7000)
    }, {timeout: 60})
    console.timeEnd('VuexSubscription')
  })
}

So, what do you think?
Is it absolutely important to block the main thread waiting for the data to write to the storage?

For those coming from Google and looking for a quick patch solution.
Put this into your store/index.js
const requestIdleCallback = window.requestIdleCallback || (cb => {
  let start = Date.now()
  return setTimeout(() => {
    let data = {
      didTimeout: false,
      timeRemaining () {
        return Math.max(0, 50 - (Date.now() - start))
      }
    }
    cb(data)
  }, 1)
})

const vuePersist = {
  // ... your other config
  saveState: (key, state, storage) => {
    requestIdleCallback(() => {
      let data = JSON.stringify(state)
      if (storage && storage._config && storage._config.name === 'localforage') {
        data = merge({}, state)
      }
      storage.setItem(key, data)
    })
  }
}

:+1: have a great day

@kylewelsby thanks for your thorough writings here! I see your point and you are correct in stating that the writing doesn't have to be blocking the thread. However your solution with the requestIdleCallback() call, is not supported in that many browsers. Maybe you have some ideas for that?

An alternative with a throttled setState, when you don't need to persist the state that often :

import Vue from 'vue';
import Vuex from 'vuex';
import createPersistedState from 'vuex-persistedstate';
import _throttle from 'lodash/throttle';

Vue.use(Vuex);

export default new Vuex.Store({
  state: {},
  mutations: {},
  actions: {},
  plugins: [
    createPersistedState({
      setState: _throttle((key, state, storage) => {
        storage.setItem(key, JSON.stringify(state));
      }, 100),
    }),
  ],
});

Another alternative to throttling (lightly tested) is to overwrite the state that we are going to set when we become idle.  That avoids making repeated calls to hit local storage later on.
let settingState = null
let setInProgress = false

export default ({ store }) => {
  window.onNuxtReady(() => {
    createPersistedState({
...
      setState: (key, state, storage) => {
        console.log('Consider set state', settingState)

        if (settingState) {
          console.log('Already setting')
          if (!setInProgress) {
            // We're not currently setting the state, we're waiting - so we can overwrite the state we're
            // intending to set with the latest one.  This saves multiple slow calls to set in local storage.
            console.log('Can overwrite')
            settingState = state
          }
        } else {
          // We're not already setting it.  Queue it up for when we're idle.
          console.log('Queue for idle')
          settingState = state
        }

        requestIdleCallback(() => {
          if (settingState) {
            console.log('set state now')
            setInProgress = true
            storage.setItem(key, JSON.stringify(state))
            setInProgress = false
            settingState = null
            console.log('completed set state')
          } else {
            // We have already set the latest state in an earlier callback.
            console.log('Nothing to set')
          }
        })
      }
    })(store)
  })
}


Refactor yelp example

Adopts new helper functions in yelp example and refactors source to be more readable / reusable.
https://replay.io/view?id=d853e5fa-400c-40ae-9584-15a1329bad72
Blocked by #29

feel free to land when the conflicts are resolved

Resolved!

Merge away


I/flutter ( 6107): Error: google_fonts was unable to load font Wallpoet-Regular because the following exception occured: I/flutter ( 6107): Exception: Failed to load font with url: https://fonts.gstatic.com/s/a/9989a07c4d82441ed4366747a76f537b925a6d9f691e7b0cd97713bcac160b20.ttf

I am trying to add fonts through Google Fonts Package , I am getting error every time. On my previous app, it use to work fine , Even tried changing old version, didn't work for me.
                   Text(movieModel.title, style: GoogleFonts.wallpoet()),
pubsec.yaml
dependencies: google_fonts: ^0.6.2

Few more information:

I am trying to run it on mobile device, not on emulator. Even at emulator it use to work fine.
I upgraded it to latest version first, then changed it to 0.6.2  just to check if it was working on older version.

It's Working now.


Transmission hangs when using gzip compression

I am quite new to this project and haven't seen the history of this project. I just found the project few days ago and found it useful in my current project... Thank you very much! I am also not yet very confident in Java.  Did I understand correclty, that support of gzip was introduced only a month ago?
I use a standard web server, as shown in the samples "HelloServer.java". Also that server without modifications shows the problem: A current Firefox or the IE11 Internet Explorer wait for each page they receive several seconds, obviously until some timeout occurs, before they display the result. My guess is that the reason is that NanoHTTPD does not send the "Content-Length:" header field in combination with "gzip" encoding. (At least Firefox sends "gzip, deflate" in the "Accept-Encoding" header, and NanoHTTPD decides to use "gzip"; and does not send any content length anymore.)
When I add an ugly hack to my server class to suppress gzip encoding, everything works as expected:
        String encoding = session.getHeaders().get("accept-encoding");
        encoding = encoding.replaceAll("gzip", "NO_GZIP");
        session.getHeaders().put("accept-encoding", encoding);

This tricks NanoHTTPD to not see anymore that the client accepts gzip, and sends the response unzipped, and with a correct content length. The browser knows when the response is finished, and shows it immediately without timeout.
Yes, I saw that todays latest version of NanoHTTPD provides a new method useGzipWhenAccepted() that could be overwritten, instead of modifying the header fields, but this doesn't solve the issue that gzip is not yet working in a good way.
Best regards, and thanks for looking at this issue,
kustco.
P.S.: When you agree that this is a bug and that even for gzip a correct "Content-Length" should be sent in the response, I could try to fix the issue myself and perform a pull request. But I suppose, stability and code quality would be better, when you fix it. I do not even know the HTTP specifications: Is the zipped or the uncompressed content length to be reported in that header? Or possibly even the header field is forbidden for "gzip", NanoHTTPD is right, and Firefox is wrong. Or anything other in my personal environment.

I just found that there is a pull request #193 that is supposed to fix this issue. I only searched for issues, and not for fixes, before submitting my issue...
https://github.com/NanoHttpd/nanohttpd/pull/193

no problem! better an issue to much than missing one, thanks for reporting


Meteor 1.3-rc.2 +<EMAIL_ADDRESS>There is no route for the path: /

I'm trying to test my app with Meteor 1.3-rc.2.
The first issue I'm encountering is the following error:
There is no route for the path: /
Any hints on where to look first on this?

I have the same error after upgrading to 1.3, would you please share how you fixed it?

Same issue here, after upgrading 1.3, everything became messy.

Any solution on this? I'm having the same problem.

I found that some errors are not reported in the server or client consoles. and that any missing object or import could lead to the error  "There is no route for the path: /"
to fix that error, I have upgraded to the lated 1.3 and fixed all the missing imports.

@thewolf would you mind elaborating how you fixed the missing imports?

Why this is closed? Many people having the same problem, any idea?

Had same issue here, but fyi I just added the / route to the FlowRouter which simply does nothing
#weird, yes...

Having the same issue - just update to 1.3 and suddenly I get this error. How do I know which imports are not working?


support mermaid, drawio render

include-files: debug: URLs are not relative path
include-code-files: Support include URL files
diagram-generator: Support mermaid, drawio and diagram(drawio in wiki.js)

The diagram generator is now maintained at https://github.com/pandoc-ext/diagram. If you are still interested in contributing, then please consider to port and re-open the PR in the new repo.


issues after updating pipenv

Note: I will list two issues that I'm currently facing with pipenv down below.
So recently I was trying to generate a pipfile.lock fr Heroku and I was having a problem when trying to use pipenv install firebase-admin. The issue is in the version of requests, at least that's according to the messageERROR: ERROR: Could not find a version that matches requests<3.0.0,<3.0.0dev,==2.11.1,>=2.0.1,>=2.18.0 that appears in the console.
This appears even though I have version 2.24.0 which it lists down as one of the versions that it tried to install.
after doing the obvious like clearing the cache and installing using --pre I decided on updating pipenv before writing this down as an issue. to my surprise however, now I'm getting an issue with the resolver.
Traceback (most recent call last):
  File "c:/users/abdul/anaconda3/envs/semsar-flask-env/lib/site-packages/pipenv/resolver.py", line 807, in <module>
    main()
  File "c:/users/abdul/anaconda3/envs/semsar-flask-env/lib/site-packages/pipenv/resolver.py", line 794, in main
    from pipenv.vendor.vistir.misc import replace_with_text_stream
ImportError: cannot import name 'replace_with_text_stream'

I'm very frustrated as I couldn't find any solutions on the internet.

You are likely to have two different versions of Pipenv installed.
Please uninstall them all and install the latest version of Pipenv

Thanks for the suggestion, but no that wasn't the problem as I tried uninstalling/installing beforehand.
Anyways I solved my problem by bypassing pipenv altogether and forced Heroku to use the requirements.txt as described in this particular issue.
#!/main_project_directory/bin/env bash

# Make non-zero exit codes & other errors fatal:
# http://redsymbol.net/articles/unofficial-bash-strict-mode/
set -euo pipefail

# Prevent heroku-buildpack-python from using pipenv instead of pip and requirements.txt.
rm Pipfile Pipfile.lock

I had a similar problem when trying to update an existing virtual environment. I solved it by deleting it and reinstalling it from scratch:
pipenv --rm
pipenv isntall

I had this same issue. It seemed to be because the virtualenv Python was being used to execute Pipenv which is outside the virtualenv. The virtualenv presumably itself has an older version of Pipenv in it.
I ended up solving it by running pipenv --rm install to delete and recreate the environment with the latest version of Pipenv which solved the issue.


Add history tab in the sidebar

A history tab would be useful to track changes in a file, open an old revision, or rollback some edits.

Hi @benweet -- I saw you committed some code for the File History tab but I don't see it in the UI. Is it released yet? I'm happy to act as a beta tester at some point if that's useful ;)
https://github.com/classeur/classeur/commit/b9321c6515ad5327d84ba7c516debcfd859427c0
Love Classeur so far and can't wait till this feature is out.

@johnaxel In a document, navigate to the Menu tab, enable Side bar slider (should turn blue). In the side bar that pops out, click the icon resembling Time Machine. (see image)
[![History pane][pic]][pic]
[pic]: http://i.imgur.com/Ane7C0j.png

:+1: thanks!

Looks like still not working!

Dear @winteum,
Can you confirm that you have an empty history sidebar?
~Robert

Yes, empty!
On Wed, Jul 6, 2016 at 3:56 PM, Robert Orzanna<EMAIL_ADDRESS>wrote:

Dear @winteum https://github.com/winteum,
Can you confirm that you have an empty history sidebar?
~Robert
[image: image]
https://cloud.githubusercontent.com/assets/170947/16630759/12837742-43bc-11e6-9964-4ccb72e67174.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/classeur/classeur/issues/17#issuecomment-230870175,
or mute the thread
https://github.com/notifications/unsubscribe/AEQANasYDZ2wsmBdbL4rWLAtGxk8GjXWks5qS_pQgaJpZM4GV5GR
.

Hi @winteum
Can you confirm you're signed in?

Yes, through my Google account.
On Wed, Jul 6, 2016 at 4:19 PM, Benoit Schweblin<EMAIL_ADDRESS>wrote:

Hi @winteum https://github.com/winteum
Can you confirm you're signed in?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/classeur/classeur/issues/17#issuecomment-230876098,
or mute the thread
https://github.com/notifications/unsubscribe/AEQANSmCgwVvddzxkbY73P5miXk8_Nsjks5qS_-zgaJpZM4GV5GR
.

Usually history appears after you modify the files multiple times with a couple of minutes of interval. Can you try with an old file you've been working on?

Yes, I was trying this. I'll continue to try modifying to see if it's shows there.

Alright. A snapshot of the file should take place after 2-3 minutes of
inactivity.
On 6 Jul 2016 8:28 p.m., "winteum"<EMAIL_ADDRESS>wrote:

Yes, I was trying this. I'll continue to try modifying to see if it's
shows there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/classeur/classeur/issues/17#issuecomment-230880664,
or mute the thread
https://github.com/notifications/unsubscribe/AA9WyTZ1iVORfQE-6d0o3EkJbCAixNjnks5qTAHMgaJpZM4GV5GR
.

I even created another file but still no snapshots neither.

We can reproduce the issue. Investigating...

@winteum should be fixed now. Can you confirm?

Yes, it's working!
On Wed, Jul 6, 2016 at 7:01 PM, Benoit Schweblin<EMAIL_ADDRESS>wrote:

@winteum https://github.com/winteum should be fixed now. Can you
confirm?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/classeur/classeur/issues/17#issuecomment-230920699,
or mute the thread
https://github.com/notifications/unsubscribe/AEQANarLuBHbnIA3vHe2SR9B2nddDmFMks5qTCXSgaJpZM4GV5GR
.


New Twitch Chat Panel Accessed Via Menu OP

This adds a several menu options to the clan chat button which allows you to switch back and forth between twitch and clan chat as well as filter twitch chat on or off. I will be adding more detail to this description in the future this is just so people can take a look.

I appreciate your feedback I will make sure to to commit these changes soon

I finally updated the scripts in this pr to the new opcodes so twitch chat is up and working again. @TheStonedTurtle  already reviewed my code but if someone could pull this down, test it out, and give me feedback I would highly appreciate it. :)


Update to 0.8.0

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

The build is failing with this error message unfortunately 😅
ninja: error: '../../../../../../src/cpp/skia-builder/skia/third_party/externals/wuffs/release/c/wuffs-v0.3.c', needed by 'obj/third_party/externals/wuffs/release/c/libwuffs.wuffs-v0.3.o', missing and no known rule to make it


[nrktv] add additional URL scheme for episodes

Series' episodes seem to have gained an additional URL scheme. This
expands the valid URL for NRKTVEpisodeIE.
A test was also added, but it fails due to a proper update of the
EPISODE_RE. (The existing test also fails, so d'uh.)
NRKTVSeriesIE may also need to be adapted.
Fixes https://github.com/rg3/youtube-dl/issues/18304
Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Add another URL scheme for episodes. Description above and in commit message.

@dstftw This was not merged? can we know the reasoning behind closing without being merging?

@dstftw This was not merged? can we know the reasoning behind closing without being merging?

This was fixed with a commit similar to mine, not with a merge:
https://github.com/rg3/youtube-dl/commit/33cc1ea586480ccc60fd25f2d42cfb44eec605c6
Fine by me if it works. Will test later (but I assume the author already did).


running storybook warns of not declaring core-js version

Storybook upgrade has some soft warnings during the build for upcoming version requirements:
WARNING: We noticed you're using the `useBuiltIns` option without declaring a core-js version. Currently, we assume version 2.x when no version is passed. Since this default version will likely change in future versions of Babel, we recommend explicitly setting the core-js version you are using via the `corejs` option.

You should also be sure that the version you pass to the `corejs` option matches the version specified in your `package.json`'s `dependencies` section. If it doesn't, you need to run one of the following commands:

  npm install --save core-js@2    npm install --save core-js@3
  yarn add core-js@2              yarn add core-js@3

Stories are housed in the fscomponents package.

Fixed with #850


[bug] hasattr on missing nested attributes should return False

Minimal example to reproduce the bug:
import omegaconf
a= omegaconf.OmegaConf.create({"a": {"b": [1, 2], "c": "abc"}})
print(hasattr(a, "d"))

prints True. OmegaConf version: 2.0.0rc15

This is impossible to fix as far as I can tell:
hasattr relies on AttributeError, but by design a.d returns None when not in struct mode so it cannot throw an AttributeError.
Closing this, but feel free to discuss further here on in a message.


Records intro in what's new page can cause confusion/misunderstanding

C# 9.0 introduces record types, which are a reference type that provides synthesized methods to provide value semantics for equality. Records are immutable by default.
Record types make it easy to create immutable reference types in .NET.

Records in general doesn't seem to ensure immutability in any way. This is very specific to positional records only.

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

ID: c36588d0-6bdf-1740-220c-10b20bb88730
Version Independent ID: 587ed47f-f532-e018-9b0d-6ee76afd20e4
Content: What's new in C# 9.0 - C# Guide
Content Source: docs/csharp/whats-new/csharp-9.md
Product: dotnet-csharp
Technology: csharp-whats-new
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Good point @Youssef1313
I'd like to keep this article brief, so some nuances are not covered. But, it shouldn't be misleading The reality is even more subtle: a developer can add additional members, even when using primary constructors. Therefore, even positional records aren't guaranteed to be immutable.
How about this for alternative wording:

C# 9.0 introduces record types, which are a reference type that provides synthesized methods to provide value semantics for equality. Record types make it easy to create immutable reference types in .NET. Record types are immutable, unless hand written members allow mutation.

@BillWagner This is more clear and less misleading, but I'm not sure whether immutability should be ever mentioned or not.

I think immutability should be mentioned. It's one of the reasons why a developer would choose a record instead of a class. (Value semantics being the other reason).

The difference I can see between a class and a record is value equality being added by default, and other synthesized methods such as PrintMembers and Clone which are irrelevant to immutability.
Besides those, I see that a record is nearly identical than a class.
Not sure if I'm missing something. I haven't played enough with records.

Value semantics being the other reason

@BillWagner what do you mean by "value semantics"? Whenever I see "value semantics", I think about distinction between variables and their copying of value types and reference types. From the value types article:

A variable of a value type contains an instance of the type. This differs from a variable of a reference type, which contains a reference to an instance of the type. By default, on assignment, passing an argument to a method, and returning a method result, variable values are copied. In the case of value-type variables, the corresponding type instances are copied.

As records are classes, I assume record variables still follow reference-type semantics. Is that correct?
If you mean by "value semantics" something different, would it be possible to find another term for that? In general, would be ideal to avoid using the word "value", as it's overloaded with various meanings and may be more confusing than helping.
Uh... now I see you mean "value semantics for equality". Now, in the docs that's just called "value equality":
https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/statements-expressions-operators/equality-comparisons#value-equality
Should we keep using that term ("value equality")?

Thanks @pkulikov Yes, "value equality" is the correct term.

@BillWagner @Youssef1313 what about this take:

C# 9.0 introduces record types. A record type is a reference type that provides compiler-generated methods to support value equality. By default, record types are immutable, but you can define members that support mutation.

(Main motivation is to avoid "synthesized" and "hand written" terms; in the docs, "user-provided" or "user-defined" is usually used instead of "hand-written". Also, with source generators, those can be not hand-written, but still user-provided, I guess).

Immutability would be a great trait to associate with records but I'm afraid that it can't really be mentioned more than in passing, and very specifically with positional records, without leaving a very misleading impression as to what the feature provides.  The difference between an otherwise identical record and class is little more than value equality.

I also think immutability should be mentioned. The primary constructor is a key difference between a record and a class, and when using only a primary constructor, records are immutable. Personally I find myself using records mainly for immutability features (init accessors and withers), and rarely for their value equality.
Yes I realize classes can use init accessors too, but given this is a whats new page, I think writing it from the point of view of existing code where classes don't have init accessors makes sense.

I understand, and in the context of positional records then immutability makes sense.  But we're already seeing confusion on the C# repository, Gitter, Discord and Twitter regarding records and immutability.  With immutability being the headlining feature of records here and in the documentation and repeated across the infinite blogs that take those docs as gospel, having to respond that records aren't immutable except in a narrow case is a very unsatisfying answer.
If you want these docs to claim that records are immutable, I think it would be better to open with simple positional records only, then expand into nominal records and how init-properties are what actually enable the immutability and how the remaining features of records (value equality and withers) make their consumption easier.  The current first example is quite literally no different than the class version of an immutable reference type despite claiming that record reduces the boilerplate.

It would be good to word it so that no one can come away thinking "if I see a record, I know it's immutable."

I also think immutability should be mentioned. The primary constructor is a key difference between a record and a class, and when using only a primary constructor, records are immutable. Even without out, personally I find myself using records mainly for immutability features (init accessors and withers), and rarely for their value equality.
Yes I realize classes can use init accessors too, but given this is a whats new page, I think writing it from the point of view of existing code where classes don't have init accessors makes sense.

If immutability should be mentioned, the doc should be very clear that records doesn't mean or guarantee it, and only simple positional records (i.e. record MyRec(whatever, ....); and not record MyRec(whatever, ...) { // extra fields/properties }.
It should also mention that even simple positional records doesn't provide deep immutability. (which may come in future C# versions)


Remove old-style func.yaml generation from fn init

This is mainly an exercise in cleaning up the codebase, but I would like to have fn init without any --trigger behave like fn init --trigger none.  This would let us remove a lot of duplicated code in init.go.
run, deploy etc are not affected, only init.

Yep, this is exactly what should happen - --trigger none was just a bridge to keep both worlds working during the V2 development.


Closing the position infowindow should not stop geolocation

...because the new track display options allow position tracking without infowindow...
Hence, removing some code from the closebutton makes the UI more intuitive.

Search for closeclick in psgeolocation.js and comment out the stuff that unsets variables, stop workers, increments counter.
Need to give a second thought to this, though.
Awaiting user feedback.

Should not stop, unless the trace line is also off.


Implementation of DialogFragment support for Elements

This adds support for DialogFragments in the Elements tab. This code is actually pretty straightforward now that tree diffing is checked in ( #204 ), without which I had code with all sorts of clowney timers and stuff.
I refactored ChainedDescriptor to be an interface, with AbstractChainedDescriptor sitting on top of it as the canonical implementation. I did this because DialogFragmentDescriptor has the unique problem of needing to not pass-through to its super-descriptor's implementation of getChildren(). If it did, then it would emit both the View and the Window which contains the View. Not only would this be silly, but it causes an infinite loop and would break all sorts of stuff that assume each element can only appear once in the DOM tree. I chose this approach because the code was much simpler, and free of future bug and clown hazards, versus allowing classes that derive from AbstractChainedDescriptor to override the non-"on" methods (e.g. to implement a non-chained version of getChildren).
Note that this does not add support for Dialogs that aren't attached to a DialogFragment. If anyone needs that then we can go ahead and add support for it, but for now it's just so much simpler to just support DialogFragment.
Closes #193

lgtm less a few minor notes.  Would prefer a screenshot for the PR so I can see in context where the dialog fragments actually sit in the hierarchy.  Thanks so much for working on this!


Further cleanup of Gradle build files

Consolidate some version numbers in the top-level build file to make upgrading easier

I think for this kind of cleanup we can land without two reviews, so I'll go ahead


chore(deps): update dependency eslint to v8.49.0

This PR contains the following updates:

Package
Type
Update
Change

eslint (source)
devDependencies
minor
8.48.0 -> 8.49.0

Release Notes

eslint/eslint (eslint)
v8.49.0
Compare Source
Features

da09f4e feat: Implement onUnreachableCodePathStart/End (#17511) (Nicholas C. Zakas)
32b2327 feat: Emit deprecation warnings in RuleTester (#17527) (Nicholas C. Zakas)
acb7df3 feat: add new enforce option to lines-between-class-members (#17462) (Nitin Kumar)

Documentation

ecfb54f docs: Update README (GitHub Actions Bot)
de86b3b docs: update no-promise-executor-return examples (#17529) (Nitin Kumar)
032c4b1 docs: add typescript template (#17500) (James)
cd7da5c docs: Update README (GitHub Actions Bot)

Chores

b7621c3 chore: remove browser test from npm test (#17550) (Milos Djermanovic)
cac45d0 chore: upgrade<EMAIL_ADDRESS>(#17549) (Milos Djermanovic)
cd39508 chore: package.json update for @eslint/js release (ESLint Jenkins)
203a971 ci: bump actions/checkout from 3 to 4 (#17530) (dependabot[bot])
a40fa50 chore: use eslint-plugin-jsdoc's flat config (#17516) (Milos Djermanovic)
926a286 test: replace Karma with Webdriver.IO (#17126) (Christian Bromann)
f591d2c chore: Upgrade config-array (#17512) (Nicholas C. Zakas)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Codecov Report
Patch and project coverage have no change.

Comparison is base (6cd1c19) 100.00% compared to head (d0a1ef4) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main      #152   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           20        20
  Lines          163       163
  Branches        35        35
=========================================
  Hits           163       163

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Auto migrate now migrates every time

Fixes #280

Looks good to me, as long as we'll be able to bypass this script and run "/app/swiftarr migrate --revert" if we ever need to revert.

Looks good, but do we really need different log messages for initial vs subsequent? Could simplify it and just echo "Running automatic database migration".
Feel free to keep as-is, though!

I thought about removing it but a part of me wanted to keep the logic built around detecting initial migration in there in case we wanted to use it later on. Git history also exists though.

Looks good to me, as long as we'll be able to bypass this script and run "/app/swiftarr migrate --revert" if we ever need to revert.

Yes at any time the container can be re-created with AUTO_MIGRATE=false which will avoid automatically performing any migrations. It is then left up to the operator to re-apply when the time is right.


lora-phy: refactor sx127x to have chip trait instead of enum

Example of how to factor out the enum in favor of a trait. Sx126x would need to be done next.

Really nice. It reads way better now and makes more sense!

@lthiery  Could you pick up this commit (rebased + fixed to apply on top of main) and force push this branch?
https://github.com/lora-rs/lora-rs/commit/4fd55216e6438197a15a3d3e4685b3ef287fc45e

closed in favor of #248


App opens like a link with url bar at the top, rather than like an android app

Describe the bug
After installing the generated apk, the app opens like a normal link in the Google app rather than an android app. It has a url bar at the top
To Reproduce
Steps to reproduce the behavior:
use bubblewrap cli to generate apk using the following manifest:
Note: The links are fake
// twa-manifest.json

{
  "packageId": "app.web.facpro.twa",
  "host": "facpro.web.app",
  "name": "FACPRO - Faculty Research Progress",
  "launcherName": "FACPRO",
  "display": "fullscreen",
  "themeColor": "#FFFFFF",
  "navigationColor": "#000000",
  "navigationColorDark": "#000000",
  "navigationDividerColor": "#000000",
  "navigationDividerColorDark": "#000000",
  "backgroundColor": "#FFFFFF",
  "enableNotifications": true,
  "startUrl": "/",
  "iconUrl": "https://facpro.web.app/logo512.png",
  "maskableIconUrl": "https://facpro.web.app/maskable_icon_x512.png",
  "splashScreenFadeOutDuration": 300,
  "signingKey": {
    "path": "/path/to/android.keystore",
    "alias": "android"
  },
  "appVersionName": "1",
  "appVersionCode": 1,
  "shortcuts": [],
  "generatorApp": "bubblewrap-cli",
  "webManifestUrl": "https://facpro.web.app/manifest.json",
  "fallbackType": "customtabs",
  "features": {},
  "alphaDependencies": {
    "enabled": false
  },
  "enableSiteSettingsShortcut": true,
  "isChromeOSOnly": false,
  "orientation": "default",
  "fingerprints": [],
  "additionalTrustedOrigins": [],
  "retainedBundles": [],
  "appVersion": "1"
}

//manifest.json of website

{
  "short_name": "FACPRO",
  "name": "FACPRO - Faculty Research Progress",
  "icons": [
    {
      "src": "favicon.ico",
      "sizes": "64x64 32x32 24x24 16x16",
      "type": "image/x-icon"
    },
    {
      "src": "logo192.png",
      "type": "image/png",
      "sizes": "192x192"
    },
    {
      "src": "logo512.png",
      "type": "image/png",
      "sizes": "512x512"
    },
    {
      "src": "maskable_icon_x512.png",
      "type": "image/png",
      "sizes": "512x512",
      "purpose": "any maskable"
    }
  ],
  "start_url": ".",
  "display": "standalone",
  "theme_color": "#ffffff",
  "background_color": "#ffffff"
}

Expected behavior
The app should open like an normal android app, without the url bar
Screenshots
Screenshot of app with url bar (in android emulator)

Screenshot of app with url bar (in physical device OnePlus 7)

Desktop

OS: Fedora 35 workstation
Browser: Chrome
Version: 100

Smartphone (please complete the following information):

Device: OnePlus 7
OS: Android 11
Browser: chrome
Version: Android Chrome 100.0.4896.79

Additional context
Additionally, the PWA works great when installing from the browser using the install app option from the website. It opens like a usual android app, without the url bar

Yes, the screenshot is on an emulator, but the same thing happens on my OnePlus 7 too. I'll add a screenshot for that too

@Pika-Pool , A Trusted Web Activity needs the origins being opened to be validated using Digital Asset Links, in order to show the content in full-screen (without URL bar). Did you provide the /.well-known/assetlinks.json endpoint for your root domain and subdomain with correct assetlinks?

@SJShip, I just checked it, and I had names the assetlinks.json file as assetslinks.json. I've wasted so much time on this because of a small spelling mistake. Unbelievable.🤦🤦
Thanks a lot for pointing it out.


Docker: Sync origin-js source between local filesystem and container

I'm thinking we'll want to use Docker volumes to achieve this. I [did something similar a while back, in the demo dapp. It doesn't work any more, here is an example using docker-compose.
See https://github.com/OriginProtocol/origin-js/pull/227#issuecomment-395558722 for why we need this.
Or, we may not want docker to be running the origin-js dev environment at all: https://github.com/OriginProtocol/origin-js/issues/230 .

I can help out with this one if possible?

@ahaidery Thanks for offering to help ! :) @tomlinton has actually a setup of docker-compose that uses volume - check out this branch as well as this discussion. We are in the process of testing out this setup - would you want to give it a try and give any feedback ?

Yeah, this issue should have been closed already. We solved this problem in origin-box. Thanks @ahaidery .


When hour drag has ended, timepicker mode is changed to select time

Fix for https://github.com/flutter/flutter/issues/17276

Wait... You created a pull request to a master branch of your own fork. Please create the same request to flutter original repository. Thanks!

@tjunxiang92 Could you please change the master of the pull request to the one of flutter?
We also need this fix.


Adds ability to set search view hint as requested (Hint #6)

Adds setSearchViewHint(String searchViewHint) method. Adds use of this method in example.

What about the collapsed hint?
As there are two states of the widget, the APIs should be setCollapsedHint and setExpandedHint.

I thought it may look strange to put a hint on the collapsed view as hints generally appear when the keyboard pops and when you tap on it, it expands. It may not even show unless it is in focus. I'll experiment tonight and let you know.

Have added hints API for all modes. Check Readme.


Fix paths in tsconfig.json

VS Code is reporting errors in this file (at least when used in a vanilla JS project - I didn't test with a TS project)

I left renaming the file to jsonconfig.json for a follow-up

hmm. closing this for now because I can't reproduce locally. the screenshot was from another user, but they've reported they still have issues even after this change


amazon linux python 3.10 aarch64: Unsupported compiler -- at least C++11 support is needed!

bash-4.2# pip install hnswlib
Collecting hnswlib
  Downloading hnswlib-0.7.0.tar.gz (33 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting numpy (from hnswlib)
  Obtaining dependency information for numpy from https://files.pythonhosted.org/packages/b1/39/3f88e2bfac1fb510c112dc0c78a1e7cad8f3a2d75e714d1484a044c56682/numpy-1.25.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata
  Using cached numpy-1.25.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (5.6 kB)
Using cached numpy-1.25.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (14.2 MB)
Building wheels for collected packages: hnswlib
  Building wheel for hnswlib (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for hnswlib (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [55 lines of output]
      running bdist_wheel
      running build
      running build_ext
      creating tmp
      /usr/bin/aarch64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/tools/deps/include -I/tools/deps/include/ncursesw -I/tools/deps/libedit/include -fPIC -I/usr/local/include/python3.10 -c /tmp/tmp01l956bu.cpp -o tmp/tmp01l956bu.o -std=c++14
      /usr/bin/aarch64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/tools/deps/include -I/tools/deps/include/ncursesw -I/tools/deps/libedit/include -fPIC -I/usr/local/include/python3.10 -c /tmp/tmphmbrrdan.cpp -o tmp/tmphmbrrdan.o -std=c++11
      Traceback (most recent call last):
        File "/usr/local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/usr/local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/usr/local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 251, in build_wheel
          return _build_backend().build_wheel(wheel_directory, config_settings,
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 434, in build_wheel
          return self._build_with_temp_dir(
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 419, in _build_with_temp_dir
          self.run_setup()
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 341, in run_setup
          exec(code, locals())
        File "<string>", line 116, in <module>
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/__init__.py", line 103, in setup
          return distutils.core.setup(**attrs)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/dist.py", line 1001, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/wheel/bdist_wheel.py", line 364, in run
          self.run_command("build")
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/dist.py", line 1001, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/command/build.py", line 131, in run
          self.run_command(cmd_name)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/dist.py", line 1001, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 88, in run
          _build_ext.run(self)
        File "/tmp/pip-build-env-9i51uibi/overlay/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 345, in run
          self.build_extensions()
        File "<string>", line 103, in build_extensions
        File "<string>", line 70, in cpp_flag
      RuntimeError: Unsupported compiler -- at least C++11 support is needed!
      [end of output]

When building extension wheels setuptools will try to use the compiler (ie: CC) used to build python itself ...
In my case, my python binary was built on ubuntu where CC was set to /usr/bin/aarch64-linux-gnu-gcc:
$ python3 -m sysconfig | grep -E '\bCC ='
        CC = "/usr/bin/aarch64-linux-gnu-gcc"

But amazon/redhat linux has:
$ ls /usr/bin/ | grep gcc
aarch64-redhat-linux-gcc
aarch64-redhat-linux-gcc-7

So when I use my binary python on amazon linux it can't find gcc. To resolve this, override CC with an env var, eg:
export CC = gcc

or link /usr/bin/aarch64-linux-gnu-gcc -> gcc


WIP – v0.2.0

The next release! :trumpet: :tada: :dancers:

Do you have any punch list for v0.2.0 so I can help out where possible? This library is da' :bomb:

Yo @begizi. My plan for 0.2.0 was sort of just to get it out the door ASAP for ya', since it contains a feature you're waiting on. If there's no rush, we could try to get more in it.
One very important feature is partially described here (also, lul @ the forceRender option! That sounds pretty similar to that other PR you made :P ). This library – and that feature – are inspired by SlickGrid. The feature is basically a way to check if a change is 'small' enough to be rendered instantly. You can see it in slickgrid here. They only do the 50ms delay when the change is big.

Gonna close and cherry-pick 581969cedad09a3204aabdb4b96010cd2d6bcb99 onto a new PR. I've just been merging shtuff to master.


NSLS-II test with PandA

Based on #141 plus #138 plus main minus a merge commit from #147 plus some missing pieces.
Works in tandem with https://github.com/NSLS-II-TST/profile_collection/pull/4/files.

We don't need this PR/branch as we succeeded using #141 directly.


Add ARG query for Azure VM disk encryption

Overview/Summary

Add ARG query for Azure VM disk encryption recommendation (f0a97179-133a-6e4f-8a49-8a44da73ffce) :

Related Issues/Work Items

Breaking Changes
None
As part of this pull request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ ] Ensured PR tests are passing
[x] Performed testing and provided evidence (e.g. screenshot of output) for any changes associated to ARG queries
[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

Thank you @jdmsoss for contributing to APRL.
I think it is better that VM centric results because this recommendation is for virtual machines. Like as the following:

name
id
tags
param1
param2
param3

vm1
vm1-id
vm1-tags
diskName:vm1-osdisk
EncryptionAtHost: Disabled
DiskEncryption: Disabled

vm1
vm1-id
vm1-tags
diskName:vm1-datadisk1
EncryptionAtHost: Disabled
DiskEncryption: Disabled

vm1
vm1-id
vm1-tags
diskName:vm1-datadisk2
EncryptionAtHost: Disabled
DiskEncryption: Disabled

vm2
vm2-id
vm2-tags
diskName:vm2-osdisk
EncryptionAtHost: Disabled
DiskEncryption: Disabled

Similar cases:

Enable Accelerated Networking (AccelNet)

The actual settings on network interfaces, but the result is VM centric.

VMs should not have a Public IP directly associated

Public IP address settings are on network interfaces, but the result is VM centric.

What do you think?

Indeed, it makes sense @tksh164 !
I will update the code this week to produce a result per VM and not per disk. Thank you!

@jdmsoss please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Microsoft"

It's seems this PR was automatically updated with two commits from my fork. I didn't find a clean way to remove one of these commit (05bcc65) from this PR for now. What simple method would you suggest for removing this commit from here?
In the meantime, we can keep commit bd2afe1 which takes into account @tksh164 suggestion 😉
Thank you!

@jdmsoss I think that the most effortless way is to close this PR then re-create a new one.


How to obtain the dense correspondence predication?

Can you tell me which code produces the dense correspondence prediction shown in your paper?

@MercurialJD I used the visualization notebook from the original NC-Net Repo and changed it a little to work with ANCNet. You can find my notebook here.


lsp-embedded-request-forwarding: don't encode uri used in map (fix #682)

This PR fixes #682

Doc at https://code.visualstudio.com/api/language-extensions/embedded-languages#request-forwarding also contains this error.

Thanks @gjsjohnmurray !

I also updated the documentation


OpenSSL 1.0.2 for CentOS 7

The README.md file has instructions about making the app for CentOS 7.
However, the precompiled binary as well as the instructions for compiling from source produce a build that calls libcrypto.so.1.0.0.
However, CentOS 7 has never shipped such an old version of OpenSSL. It's puzzling that there are instructions which purport to work on CentOS 7.
Please update the Linux build so that it references libcrypto.so.1.0.2k instead, which is what CentOS 7.7 ships.

Oops, turns out I hadn't removed the first precompiled binary designed for Ubuntu 12.04 that I had installed in /usr/bin. Removing that mhl, then compiling from source, and then moving it into /usr/local/bin on CentOS 7.7 works great! It seems to be calling the correct, actually existing OpenSSL library. Thanks for this tool!


Better Dependency management

Background
While it's possible to define additional import's in the generated paths or entities code, it is not yet possible to declare dependencies to those modules in the generated Package.swift.
When investigating how to give the user more control over importing Get (and I guess other default dependencies), it became a bit clearer that we needed a more powerful way to define which dependencies we want to use and what they bring to the generated code.
Se notes here: https://github.com/CreateAPI/CreateAPI/issues/84#issuecomment-1205026288
Fundamentally, I believe that we need a way to declare custom dependencies, and with that:

Where the dependency comes from and it's version requirements (if it needs to go into Package.swift)
What the dependency provides (i.e the Request type)
Where the custom dependency is required (i.e maybe it only needs improving into entities)

With this information, we'd able to do the following:

Merge the custom dependencies with required dependencies (i.e Get) where appropriate
Figure out which files need to import which module
Embed each dependency in Package.swift, including the custom ones

Examples
Previous Behaviour
For matching the previous behaviour, the following config:
entities:
  imports:
  - CoreLocation

Would become this:
dependencies:
- module: CoreLocation
  importIn:
  - entities

We can deprecate the old options and automatically backfill them during a transition period.
Package Dependencies
In the event that we also need to bring in a package to help with some additional customisations:
entities:
  protocols:
  - DataTransferObject
dependencies:
- module: DataTransferKit
  url: https://github.com/myorg/DataTransferKit.git
  from: "0.0.2" # need other options too, such as branch, revision, upToNextMinor etc
  importIn:
  - entities

This will both import DataTransferKit in generated entity files for the protocol conformance, and will also include the dependency in the generated Package.swift file.
Overrides
Finally, being able to override the existing imports. For example, Get:
dependencies:
- module: MyAPIKit
  url: https://github.com/myorg/MyAPIKit.git
  branch: main
  provides:
  - Request

Instead of using importIn, this tells CreateAPI that this dependency provides the given type which would allow it to replace built-in dependencies that provide that type (Get).
Right now, the generator would just import MyAPIKit instead of Get in all Paths, but in the future we would have the potential to expand this to any type. For example:
paths:
  overriddenResponses:
    MyEntity: GenericType
dependencies:
- module: MyUtilsKit
  path: ../MyUtilsKit
  provides:
  - GenericType

And the result would be that MyUtilsKit is then imported only in specific source files that reference GenericType.
While this would be neat, I don't think this is a requested feature right now so I imagine that it would be out of scope to begin with. It just demonstrates how provides has the potential to be very flexible.

With my work from #135 and omitting the importIn functionality, I think we should keep entites.import and paths.import as they exist now. This comes from a config organization and construction perspective, where the entities and paths sections hold options that configure their respective sections (for the most part). This also would also break some convention we have right now, where each section may describe a property with a list (entites.import now) instead of a property that may describe a flag of where to go importIn: entities/paths.

Per the provides option, for the Request type specifically I think creating paths.requestProvider would be optimal to make the, well, provider of Request more explicit instead of hiding under a dependency import. I say this because it's probably the most important type that we need.
Per the other usage of provides, that could be a bit easy and wonder how it would work with https://github.com/CreateAPI/CreateAPI/issues/114 at a fine level.

Ok I think that's cool. You are right, It's not too much burden to manage the imports manually and I had also been thinking about how this ties in with my note at the bottom of #134.
If we keep dependencies strictly relating to Swift Package dependencies, then we can group them all under the same namespace in the config options:
paths:
  enabled: false
package:
  enabled: true
  name: my-package
  dependencies:
    # ...

WDYT of this approach? I haven't looked at your PR yet but I can get #134 adjusted and merged asap so you can base the new dependencies option on top of it if so?
The one thing that I wonder about is using the term enabled to describe inclusion of a given type of generated content? Is included a better alternative? Alternatively we could have a separate option called generate that would have been more like the original --generate flag:
module: MyAPIKit
generate: [entities, package]
entities:
  defaultType: class
package:
  name: my-api-kit
  dependencies:
    # ...

We can take this conversation over to #134 if you'd like?

I'll close this for now since initial support is there! Thanks again @LePips 🚀


Feat: AI-based template

Describe the feature
Generating the AI based template for user in workspace.
Add ScreenShots
No screenshots needed!
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@subhadeeproy3902 Please assign me this issue!


Additional dependency "Microsoft Build Tools 2013"

The program currently references to Microsoft.Build assemblies which need to be preinstalled in order to run it. All assemblies and resources are contained within the "Microsoft Build Tools 2013" resource offered by Microsoft.
URL: http://microsoft.com/download/details.aspx?id=40760

Will solve this issue by integrating the binaries by downloading them from Microsoft's server during the tool's runtime. Don't want to have yet another dependency if possible.

Delaying to Milestone 1.2.0, investigated how complicated it would be to extract the files directly from the installer... I actually need something that parses the internal MSI structure reliably. Easier said than done.


Update dependency prettier to v3.4.1

This PR contains the following updates:

Package
Type
Update
Change

prettier (source)
devDependencies
minor
3.3.3 -> 3.4.1

Release Notes

prettier/prettier (prettier)
v3.4.1
Compare Source
diff
Remove unnecessary parentheses around assignment in v-on (#16887 by @fisker)

<!-- Input -->
<template>
  <button @click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @click="foo += 2">Click</button>
</template>

v3.4.0
Compare Source
diff
🔗 Release Notes

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json


[BUG] Using Indexed with an Enum raises TypeError("Cannot extend enumerations")

To Reproduce
from enum import Enum
from beanie import Document, Indexed

class SomeEnum(Enum):
    BAR = "bar"

class Thing(Document):
    param: Indexed(SomeEnum)

    class Settings:
        name = "things"

Expected behavior
That the indexing works correctly just like it does with any other type.

Workaround
For those who face this same issue, simply utilize the indexes attribute in the Settings sub-class, as per documentation.

Thanks for the suggestion, but the link is broken.
I guess the configuration would be like this:
class Settings:
    name = 'things'
    indexes: ClassVar[list] = [
        pymongo.IndexModel(
            [('param', pymongo.DESCENDING)],
            name='param_index',
        ),
    ]


⏩ Pull Request code checks

User Story
As a Cloud Ops engineer
I expect code format is checked when a pull request is submitted
So that linting errors are flagged before getting merged.
Value / Purpose
Testing of code
Reduction of errors when Actions run
Useful Contacts
Rich
Definition of Done
GitHub Action is checking PR's

Possible Linters - Gov UK


Release tags requested

Release tags would help the community using this repo future proof their projects.
https://github.com/Va1/browser-sync-webpack-plugin/releases

Duplicate #19 , I suggest.


Bump version of istanbul?

The old version of istanbul that gets pulled in seems to use an old version of handlebars that has a vulnerability:
handlebars 1.3.0 has known vulnerabilities:  severity: low; summary: Quoteless Attributes in Templates can lead to Content Injection; https://nodesecurity.io/advisories/61
[...]
qunit 0.9.0
 ↳ istanbul 0.2.5
  ↳ handlebars 1.3.0

currently its using https://github.com/gotwarlost/istanbul/tarball/harmony
Whats the latest version with harmony support?

"the harmony branch should be treated as obsolete with the latest Istanbul release. The mainline release now has all the features that the harmony branch has."
https://github.com/gotwarlost/istanbul/issues/284#issuecomment-117874944

Could you bump the version of Istanbul to v1.0.0-alpha.2 as it offers accurate coverage reporting of ES6 code.

Per https://github.com/gotwarlost/istanbul/blob/v0.4.5/CHANGELOG.md:

v0.3.9

Merge harmony branch and start adding ES6 features to istanbul

513c75f updates istanbul to v0.4.5 which comes with handlebars v4.0.5. The vulnerability was fixed in 4.0.0 per https://snyk.io/vuln/npm:handlebars.
qunit
+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>``


Missing v0.0.12 and v0.0.13 release binaries

Should 0.0.12 and 0.0.13 does not have any release binaries?

Thanks - fixed.


Please consider loading inline svg instead of fa icons in wp admin

@kevinruscoe  Please consider loading inline svg instead of fa icons in wp admin. I do not use fontawesome for this frontend or at all. So I prefer to not load it in wp admin either. Could we disable it somehow?

Hello, I've pushed an update which allows this. Please check out the wiki (https://github.com/kevinruscoe/acf-star-rating-field/wiki/Cheat-Guide)

@kevinruscoe Great and fast response thanks! Works great thanks!