ERROR: Container command not found or does not exist.

Summary:
On Windows: when something goes wrong like a missing file or similar, the output of docker's error can be more explanatory.
Output of docker version:
$ docker version
Client:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 22:37:33 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 22:37:33 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 12
 Running: 6
 Paused: 0
 Stopped: 6
Images: 42
Server Version: 1.10.2
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 170
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: host bridge null
Kernel Version: 4.1.18-boot2docker
Operating System: Boot2Docker 1.10.2 (TCL 6.4.1); master : 611be10 - Mon Feb 22 22:47:06 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 996.1 MiB
Name: default
ID: AMDN:EJZ3:24NZ:6PET:A3ZB:SRAR:MKLG:IYP2:CWAC:PIXJ:YFKL:ZJYW
Debug mode (server): true
 File Descriptors: 52
 Goroutines: 70
 System Time: 2016-02-29T16:46:15.919696262Z
 EventsListeners: 0
 Init SHA1:
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
 provider=virtualbox

Provide additional environment details (AWS, VirtualBox, physical, etc.):
Virtualbox
List the steps to reproduce the issue:

Docker run image

Describe the results you received:
Getting the error: ERROR: Container command not found or does not exist.
Describe the results you expected:
Expected the image to run
Provide additional info you think is important:
Related to this link - https://github.com/docker/compose/issues/2950

Similar issue: https://github.com/docker/docker/issues/20376

@seanauriti thanks for opening this issue; what do you think would be a better error message? This error is already an attempt to make the error that's returned by the system a bit more friendly, so interested to hear what you think would make a good error :+1:
For reference, see: https://github.com/docker/docker/blob/df2b74188ec51422e84ec1dbdc58abf08c215019/container/monitor.go#L186-L194

Oh, and https://github.com/docker/docker/blob/df2b74188ec51422e84ec1dbdc58abf08c215019/api/client/run.go#L24 :smile:

Is there a way to return the command name?
Maybe if there is a way to run in a more verbose mode to say which commands were running and / or which section of the docker-compose file was being run, that would be a huge help in tracing down where the error is coming from.  Thanks for the quick reply @thaJeztah

One way to help debug the issue is to run
docker-machine ssh [machine-name]
and tail -f /var/log/docker.log  while you are starting the container.  Here is the output I saw for this error:
time="2016-02-29T17:51:30.464189301Z" level=debug msg="ReleaseAddress(LocalDefault/<IP_ADDRESS>/16, <IP_ADDRESS>)" time="2016-02-29T17:51:30.470394694Z" level=error msg="error locating sandbox id 232155e69307b7dd9a5c2e5408d3fcd9d6ed4b3d6eaedd884891262ab83eb39c: sandbox 232155e69307b7dd9a5c2e5408d3fcd9d6ed4b3d6eaedd884891262ab83eb39c not found" time="2016-02-29T17:51:30.470439375Z" level=warning msg="failed to cleanup ipc mounts:\nfailed to umount /mnt/sda1/var/lib/docker/containers/847abf893e4e5c1cad35f5104784e258fecd4d4d6d10cc462ed6403c6b096b32/shm: invalid argument" time="2016-02-29T17:51:30.470453358Z" level=error msg="Error unmounting container 847abf893e4e5c1cad35f5104784e258fecd4d4d6d10cc462ed6403c6b096b32: not mounted" time="2016-02-29T17:51:30.470516269Z" level=error msg="Handler for POST /v1.21/containers/847abf893e4e5c1cad35f5104784e258fecd4d4d6d10cc462ed6403c6b096b32/start returned error: Container command not found or does not exist."

which commands were running and / or which section of the docker-compose file was being run

The original error is basically the error that occurred inside a container (e.g. the container had a CMD run-me, and run-me was not found inside the container)

I have the same problem.

I think it would be descriptive enough if we would print the cmd that could not be run with proper error message, so that its easier to trace down the exact issue.
e.g. cannot start container: command cmd was not found or does not exist
Container command not found seems to be ambiguous one.
For that matter, I think it would be good if this could also be modified to show proper error, like cannot start container, command 'cmd' could not be invoked: permission denied
https://github.com/docker/docker/blob/v1.10.2/errors/daemon.go#L952-L959

问题：
root@do:~# docker run -td --privileged --name "n1" -h "n1" -p 10022:22 ubuntu /usr/sbin/sshd -D
720537133a6ece469fc1aeeb49f2561de2f874fdb491e671756ed17d096b3363
docker: Error response from daemon: Container command not found or does not exist..
root@do:~# echo $?
127
root@do:~# ls /usr/sbin/sshd
/usr/sbin/sshd
环境：
	root@do:~# uname -a
	Linux do 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
	root@do:~# docker --version

Docker version 1.10.2, build c3959b1
解决：
start3
root@ubuntu:~# docker run -td --privileged --name "start3" -h "start3" -P ubuntu/full_package /usr/sbin/sshd -D
1215c900d8f44b1370669101f9b9596938475c04df00bc67e01477388490f250
root@ubuntu:~# docker stop start3
start3
说明：
	这个与环境无关，docker run cmd，执行的命令必须是镜像里面支持的命令，如果镜像里面没有该命令，则会出现这个错误

	root@do:~# docker run -td --privileged --name "n1" -h "n1" -p 10022:22 ubuntu /bin/bash
	be8440d87af0c6372a54cf4e817d0d06f8e40d106c416479c23eeae49773924c
	root@do:~# docker exec -it n1 bash
	root@n1:/# ll /usr/sbin/sshd
	ls: cannot access /usr/sbin/sshd: No such file or directory

所以在 使用 docker run cmd执行命令的时候，需要考虑命令是否被镜像支持

@doungni could you try and explain your question in English? Willing to help, but I'm not sure what your question/comment is

@thaJeztah Thx u point, Has changed

I have command: /app/compose.sh in my YML which works fine on a Mac. In Windows I get an error nearly identical to the above: "Handler for POST /v1.21/containers/7c889d3e71bf9b7059b5cd3faaf8f43490df22aaaa15aa3efb62f5597363242d/start returned error: Container command could not be invoked.
Note that even if my compose.sh is nuked to be an empty file with just #!/bin/bash at the top, I get the same error.

Turns out my issue was the volumes section was not mounting properly because on the windows version only the C:\Users directory gets mounted.  Moving the project into that directory solved the issue.  There were also a few executable +x issues on two files and some files had Windows style carriage returns at the end of the line that needed to be converted.  Still would be nice to know which command cannot be found.

On AWS EC2/ubuntu, I tried to transform a Dockerfile setup from phusion/baseimage to gliderslabs/alpine. Turns out that those shell scripts use bash -- of course! Simply change to sh, as bash is not present, resulting in the above error..

+1 The same issue

See #21345

Thanks for the fix @duglin

Could we re-open this issue?
I'm also hitting this same error message when a volume doesn't exist but is referenced by a service. The message is very misleading which translates into hours of frustration.
I can reproduce the error in a small docker swarm of two nodes using docker-compose.
My compose file specifies a volume beanstalkd_volume. Typically this means that it gets created on both nodes but it sometimes doesn't (which is another issue by itself). So when the volume exists on node02 but not node01 and I constraint the service to start only on node01, I get the same error ERROR: 500 Internal Server Error: Container command not found or does not exist..
services:
  beanstalkd:
    image: schickling/beanstalkd
    environment:
      "constraint:node": "=node01"
    volumes:
      - "beanstalkd_volume:/var/lib/beanstalkd/data"
    networks:
      - backbone
    expose:
      - "11300"
    command: ["beanstalkd", "-V", "-p", "11300"]

volumes:
    beanstalkd_volume:

If I change the constraint to  "constraint:node": "=node02" the container is created. No error is displayed.

Running in verbose mode (docker-compose -f test.yml -p testproj --verbose up) and looking into the (tail -f /var/log/docker.log) helps. For me the problem was entrypoint was missing.

More on the same issue, I just spend a nice amount of time debugging the "Container command not found or does not exist."  error message. It turned my entrypoint file contained windows line-endings.
The problem is that the error message supplied by docker isn't informative enough in this case. The original error inside the container looked like this and is just a crucial bit more helpful:
bash: /docker-entrypoint.sh: /bin/bash^M: bad interpreter: No such file or directory
Before seeing this it took me lots of debugging to verify that the file was
a: present
b: executable
c: not containing any errors (except for those freaking line endings)
d: and even more time to figure out that I has to test the file inside the container as an executable and not using a "sh" prefix.
Solution 1
In my case raising the original error is an option or would that lead to confusing output in other usecases? How often does this error occur? Maybe it is an option to run a few helpful checks for common causes:

Does the entrypoint exist?
Is it executable?
Does it contain Windows line-endings

I had this, turned out to be something messed up with -s overlay.
removed the overlay option, and the existing docker directory, restarted with aufs, all good.
did the same thing restoring overlay, and still all good.
so for me it was something with the overlay driver messing things up for just one image on just one box (it ran fine elsewhere, as did other images on the same box), and no amount of deleting/pulling fresh images would help, only starting fresh.
hope this helps someone.

Not sure if this helps anyone, but I recently ran into this issue after upgrading Docker to 1.11.2, build b9f10c9. I had failed to restart the daemon after the update. Fortunately, restarting Docker was all that was required.

In case anyone else hits this error message, like I did, after upgrading ubuntu to 16.04, the cause of the error for me was apparmor.  The appropriate solution would be to update the apparmor profile for docker so things work properly.  For me, on my personal server, I just disabled and deleted apparmor.

I have this problem trying to run an interpreter from PyCharm. This is the error:
Can't run remote python interpreter: Container command 'python' not found or does not exist.
I'm using El Capitan

@Nathre2501 are you using Docker for Mac, or Docker Machine / Toolbox (VirtualBox)?

@thaJeztah i installed both, just now uninstalled both and now im trying to set it up using toolbox but i still have the same problem

@Nathre2501 what image is it running? Is python actually installed in the container? Or is PyCharm installing it?

@thaJeztah
It's installed in my system and pycharm is able to list the modules inside de container. Do i necessarily need to install python in the container?

@thaJeztah The problem was that pycharm needs the project to be located in the main unit. I had the project in some other volume so it couldn't run python. Moving the project fixed the problem.

We merged a change for docker 1.12 that returns a better error message, instead of masking it as "command not found"; https://github.com/docker/docker/pull/22983/files#diff-3cb140026df40998ea29c5bcb6bb292eR150
I'm closing this issue, because this should be resolved in 1.12, but if anyone is able to give the 1.12 release candidate a spin to verify, that would be great http://github.com/docker/docker/releases

I had the same problem, but solved it by reinstalling docker-engine (if it's any help to someone)

Please reopen this issue i am getting container command '/bin/sh' not found even with FROM ubuntu:latest

@zotherstupidguy could you please provide some more information? Output of docker version, docker info, and steps to reproduce?

Docker version 1.11.2, build b9f10c9
Containers: 63  Running: 0  Paused: 0  Stopped: 63 Images: 144 Server Version: 1.11.2 Storage Driver: devicemapper  Pool Name: docker-254:0-1712742-pool  Pool Blocksize: 65.54 kB  Base Device Size: 10.74 GB  Backing Filesystem: xfs  Data file: /dev/loop0  Metadata file: /dev/loop1  Data Space Used: 3.718 GB  Data Space Total: 107.4 GB  Data Space Available: 16.7 GB  Metadata Space Used: 7.483 MB  Metadata Space Total: 2.147 GB  Metadata Space Available: 2.14 GB  Udev Sync Supported: true  Deferred Removal Enabled: false  Deferred Deletion Enabled: false  Deferred Deleted Device Count: 0  Data loop file: /var/lib/docker/devicemapper/devicemapper/data  WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldevor use--storage-opt dm.no_warn_on_loop_devices=trueto suppress this warning.  Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata  Library Version: 1.02.133 (2016-08-15) Logging Driver: json-file Cgroup Driver: cgroupfs Plugins:   Volume: local  Network: null host bridge Kernel Version: 4.7.0-1-ARCH Operating System: Antergos Linux OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 7.633 GiB Name: zzz ID: 3YXK:JET5:6GP7:BB4W:RQB2:G3TD:5AX7:OIXW:OXM6:XTDJ:XCDL:XHJI Docker Root Dir: /var/lib/docker Debug mode (client): false Debug mode (server): false Registry: https://index.docker.io/v1/
Steps to reproduce:

git clone https://github.com/zotherstupidguy/airtime.git
cd docker-airtime
docker build -f Dockerfile -t airtime .

I think you meant: https://github.com/zotherstupidguy/docker-airtime.git.
Can you show the output of docker history ubuntu:latest ?

does docker run -ti ubuntu:latest /bin/sh work for you?

@zotherstupidguy how did you install docker? from our apt repository, or from packages provided by Antergos Linux? I noticed the kernel version says -arch; is Antergos based on Arch linux? I recently saw a discussion that 1.11.2 doesn't work on recent versions or Arch, and upgrading to 1.12 fixed that

@thaJeztah Yes Antergos is Arch-based distro; sorry but i really don't remember much about the setup as this was some time ago, and it was working perfectly before!  shall look into reinstalling or upgrading and report!

I did the following to reinstall docker on Arch-linux and remove that error, got another error from the image but I think it is image specific not related to this issue.

sudo pacman -Rns docker
sudo pacman -S docker

Had same failure IF:
CMD ["/main -runmode server"]

Else for success:
CMD ["/main"]

all works just fine.  Suspect some parsing "magic".

CMD ["/main -runmode server"] isn't valid unless your exe is called main -runmode server - which I doubt.

By bad. Copy paste.

+1

docker version

docker version
Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:23:11 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:23:11 2016
 OS/Arch:      linux/amd64

docker info

Containers: 38
 Running: 6
 Paused: 0
 Stopped: 32
Images: 53
Server Version: 1.11.2
Storage Driver: devicemapper
 Pool Name: docker-8:1-234881221-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 32.89 GB
 Data Space Total: 107.4 GB
 Data Space Available: 68.8 GB
 Metadata Space Used: 43.63 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.104 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm$no_warn_on_loop_devices=true` to suppress this warning.
Metadata Space Available: 2.104 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2016-06-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.10.0-327.18.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 14.69 GiB
Name: e5876c17-8860-48d8-9742-cfea5e952642.bigdata.sysadmin
ID: I7DX:J6UJ:5N3J:S5MV:XB2H:HPW7:Q3R3:RZTY:LR63:CK6A:H4UK:6SAX
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Labels:
 slave=true
 LINKER_MESOS_ATTRIBUTE=lb:enable
 provider=generic
Cluster store: zk://<IP_ADDRESS>:2181
Cluster advertise: <IP_ADDRESS>:2376

error info when start cadvisor

sudo docker run \
>   --volume=/:/rootfs:ro \
>   --volume=/var/run:/var/run:rw \
>   --volume=/sys:/sys:ro \
>   --volume=/var/lib/docker/:/var/lib/docker:ro \
>   --publish=8080:8080 \
>   --detach=true \
>   --name=cadvisor \
>   google/cadvisor:latest
c698691a1995a208d238875a9e3b8a751634ba4a6633581b5a6fd25e02d4266e
docker: Error response from daemon: Container command '/usr/bin/cadvisor' not found or does not exist..

I have the same problem, and could not find any solution yet. The run.sh script included in Dockefile is not getting executed when the container started all three of the following has the issue:

CMD ["./run.sh"]
CMD ["run.sh"]
CMD ["/opt/myapp/run.sh"]

docker run -it --name test1 test:1.0
time="2017-03-28T14:20:07-04:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
C:\Program Files\Docker Toolbox\docker.exe: Error response from daemon: Container command '/opt/myapp/run.sh' not found
or does not exist..
** docker info**
time="2017-03-28T14:15:48-04:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Containers: 21
Running: 10
Paused: 0
Stopped: 11
Images: 20
Server Version: 1.11.1
Storage Driver: overlay
Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge null host
Swarm:
NodeID:
Is Manager: false
Node Address:
Init Binary:
containerd version:
runc version:
init version:
Kernel Version: 4.7.2
Operating System: Buildroot 2016.08
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.954 GiB
Name: minikube
ID: CLUS:65CW:5GME:SKDK:KM4Y:2QIB:CUDE:NVRW:ZOZU:5ECA:G4PI:SLN2
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Http Proxy: http://one.proxy.att.com:8080
Https Proxy: http://one.proxy.att.com:8080
Registry: https://index.docker.io/v1/
Labels:
provider=virtualbox
Experimental: false
Insecure Registries:
<IP_ADDRESS>:5000
<IP_ADDRESS>/8
Live Restore Enabled: false
docker version
time="2017-03-28T14:17:46-04:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Client:
Version:      17.03.0-ce
API version:  1.23
Go version:   go1.7.5
Git commit:   60ccb22
Built:        Thu Mar  2 01:11:00 2017
OS/Arch:      windows/amd64
Server:
Version:      1.11.1
API version:  1.23 (minimum version )
Go version:   go1.5.4
Git commit:   5604cbe
Built:        Wed Apr 27 00:34:20 2016
OS/Arch:      linux/amd64
Experimental: false
Dockerfile
FROM java:8
RUN mkdir /opt/myapp
COPY ./run.sh /opt/myapp/
COPY ./e911test.jar /opt/myapp/
WORKDIR /opt/myapp/
RUN chmod +x ./run.sh
CMD ["/opt/myapp/run.sh"]
run.sh
#!/bin/sh
java -version

@vnalla given that you're on Windows, make sure that the script has the right (Linux) line endings; if it's using Windows line endings, Linux will give a cryptic error message (like the one you got)

I have edited that file in CentOS VM. Here is od -c run.sh output:
[vn2158@njcdtl01vn2158 docker-images]$ od -c run.sh
0000000   #   !   /   b   i   n   /   s   h  \r  \n  \r  \n   j   a   v
0000020   a       -   v   e   r   s   i   o   n  \r  \n  \r  \n  \r  \n
0000040

Yup, the one that doesn't work has \r\n (Windows line endings). If you run that on any Linux machine, it will say "command not found" (also if it's not in a docker container)


No support for require.js

Love your code, but I have an issue with the menu plugin.  In skrollr you check for the existence of require and load it as a modal if its there or else add it to the window instance.  In the menu control, you just assume that require.js does not exist and just try to pull it from the window object:
var MENU_DURATION_ATTR = 'data-menu-duration';
var MENU_IGNORE_ATTR = 'data-menu-ignore';
var skrollr = window.skrollr; <-------- is this right?
var history = window.history;
var supportsHistory = !!history.pushState;

Is this by design?

All this module stuff wasn't written by me and nobody updated the plugins. https://github.com/Prinzhorn/skrollr#amd

Please note that only skrollr core has AMD support so far.


calling addContext() multiple times hides the context entirely

wdio.conf.js snippet
  framework: 'mocha',
  reporters: ['dot', 'mochawesome'],
  reporterOptions: {
    mochawesome: {
      outputDir: 'mochawesome-report'
    }
  },
  mochaOpts: {
    ui: 'bdd',
    require: ['ts-node/register', 'tsconfig-paths/register'],
    timeout: 60000
  }

test case
import addContext from 'mochawesome/addContext'

describe('wdio test', function() {
  it('should pass', function() {
    addContext(this, `Hello`)
    addContext(this, `World`)
  })
})

Report generated with wdio

Expected behavior (Generated with mocha + mochawesome)

versions:
    "mochawesome": "^3.0.3",
    "mocha": "^5.1.1"
    "wdio-mocha-framework": "^0.6.3",
    "wdio-mochawesome-reporter": "^2.0.0",
    "webdriverio": "^4.13.2",
    "mochawesome-report-generator": "^3.1.3",

Could also be an issue with mochawesome-report-generator, in which case I can open an issue there :)

Also the generated JSON object
{
  "stats": {
    "suites": 1,
    "tests": 1,
    "passes": 1,
    "pending": 0,
    "failures": 0,
    "start": "2018-09-10T17:48:44.787Z",
    "end": "2018-09-10T17:48:49.098Z",
    "duration": 4311,
    "testsRegistered": 1,
    "passPercent": 100,
    "pendingPercent": 0,
    "other": 0,
    "hasOther": false,
    "skipped": 0,
    "hasSkipped": false,
    "passPercentClass": "success",
    "pendingPercentClass": "danger"
  },
  "suites": {
    "title": "",
    "suites": [
      {
        "title": "wdio test (firefox)",
        "suites": [],
        "tests": [
          {
            "title": "should pass",
            "fullTitle": "should pass",
            "timedOut": false,
            "duration": 4,
            "speed": "fast",
            "pass": true,
            "fail": false,
            "pending": false,
            "code": "",
            "isRoot": false,
            "uuid": "de1734be-af79-4c60-9889-6f1f175f73d6",
            "parentUUID": "b1ff8fc3-fdcb-426f-87c6-878a99a4dc40",
            "skipped": false,
            "isHook": false,
            "context": "[{\"title\":\"Session Id\",\"value\":\"f640e363-8e71-4948-9427-abe4fb8e799d\"},[\"Hello\",\"World\"]]",
            "state": "passed",
            "err": {}
          }
        ],
        "pending": [],
        "root": false,
        "fullFile": "",
        "file": "",
        "passes": ["de1734be-af79-4c60-9889-6f1f175f73d6"],
        "failures": [],
        "skipped": [],
        "duration": 6,
        "_timeout": 0,
        "uuid": "b1ff8fc3-fdcb-426f-87c6-878a99a4dc40",
        "beforeHooks": [],
        "afterHooks": []
      }
    ],
    "tests": [],
    "pending": [],
    "root": true,
    "fullFile": "",
    "file": "",
    "passes": [],
    "failures": [],
    "skipped": [],
    "duration": 0,
    "_timeout": 0,
    "uuid": "cf5f3992-096b-4e53-a1ca-96efc57f9ce4",
    "beforeHooks": [],
    "afterHooks": []
  },
  "copyrightYear": 2018
}

After a little bit of investigation, it seems like the context object needs to be flattened
Changing
context: [
  {
    "title": "Session Id",
    "value": "f640e363-8e71-4948-9427-abe4fb8e799d"
  },
  [
    "Hello",
    "World"
  ]
]

to
context: [
  {
    "title": "Session Id",
    "value": "f640e363-8e71-4948-9427-abe4fb8e799d"
  },
  "Hello",
  "World"
]

resulted in the following generated report, which is perfect

v2.0.1 published to address this issue


Update template for React 18 and React-Redux v8

We need to update this template to support React 18 and React-Redux v8.
This should include:

Changing the template rendering setup to match React 18's createRoot(), per https://reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html and https://github.com/facebook/create-react-app/pull/12220
Updating all dependencies to the latest
Specifically updating react-redux to the latest 8.0-rc (and eventually 8.0 final, but I'd like to have the PR for the template ready before I release 8.0): https://github.com/reduxjs/react-redux/releases

Related JS template issue: https://github.com/reduxjs/cra-template-redux/issues/52

Resolved with https://github.com/reduxjs/cra-template-redux-typescript/releases/tag/v2.0.0 .


Make better stacking of food storage (cityscreen)

As the city grows from 10 to 11, the food shields (bottom left) should become more compact as shown below (basically one pixel that separates them should disappear):

Currently in Civone:

If you need help I can check what happens with this as the city grows even further.

Related to this issue: https://github.com/SWY1985/CivOne/issues/167
Need to implement better stacking. Screenshots of the original game will help greatly.

I'll do it just give me some time.

Thanks, great job. I will try to get this correctly implemented in the next build.


WebSocketCall IllegalStateException

Despite the "experimental" note on okhttp-ws page, I'm currently using it for an App with ~4.5k daily active users and I'm seeing some crash reports of:
Fatal Exception: java.lang.IllegalStateException
Unable to take ownership of connection.

at
com.squareup.okhttp.ws.WebSocketCall.createWebSocket (WebSocketCall.java:157)

I can see that there is a TODO in the source for this case (https://github.com/square/okhttp/blob/master/okhttp-ws/src/main/java/com/squareup/okhttp/ws/WebSocketCall.java#L155). Is the ws library still in development (as in: should I expect to see a fix soon)?

That TODO is unrelated and deals with the fact that the code is in a
different package than the main library.
On Mon, Aug 17, 2015, 5:25 AM Angelo Suzuki<EMAIL_ADDRESS>wrote:

Despite the "experimental" note on okhttp-ws page, I'm currently using it
for an App with ~4.5k daily active users and I'm seeing some crash reports
of:
Fatal Exception: java.lang.IllegalStateException
Unable to take ownership of connection.
at
com.squareup.okhttp.ws.WebSocketCall.createWebSocket (WebSocketCall.java:157)
I can see that there is a TODO in the source for this case (
https://github.com/square/okhttp/blob/master/okhttp-ws/src/main/java/com/squareup/okhttp/ws/WebSocketCall.java#L155).
Is the ws library still in development (as is: should I expect to see a fix
soon)?
—
Reply to this email directly or view it on GitHub
https://github.com/square/okhttp/issues/1807.

Are you using version 2.4.0? The connection ownership stuff is mostly unknown to me so I'll have to talk/defer to @swankjesse about it. It may have also already been fixed as part of other work towards 2.5.0 which should be releasing soon.

Yes, I'm using the 2.4.0 version, but if there would be a potential fix for this on 2.5.0 I wouldn't mind waiting.
It is actually a rare crash, having happened 19 times on our current App version, which has already 243.157 sessions (~0,007% of the sessions crashed because of this issue).
If it is of any help, it only occurred so far on Samsung devices and on Lollipop ranging from version 5.0 to 5.1.1.

This issue is happening to us with much higher frequency. And not only Samsung but also HTC and LG devices also faced this. What is the status of this issue? Has it been fixed at 2.4.0?

2.5.0 is latest, although the code is largely unchanged from what I
remember.
On Mon, Aug 17, 2015 at 6:25 AM Angelo Suzuki<EMAIL_ADDRESS>wrote:

Despite the "experimental" note on okhttp-ws page, I'm currently using it
for an App with ~4.5k daily active users and I'm seeing some crash reports
of:
Fatal Exception: java.lang.IllegalStateException
Unable to take ownership of connection.
at
com.squareup.okhttp.ws.WebSocketCall.createWebSocket (WebSocketCall.java:157)
I can see that there is a TODO in the source for this case (
https://github.com/square/okhttp/blob/master/okhttp-ws/src/main/java/com/squareup/okhttp/ws/WebSocketCall.java#L155).
Is the ws library still in development (as is: should I expect to see a fix
soon)?
—
Reply to this email directly or view it on GitHub
https://github.com/square/okhttp/issues/1807.

I believe this was also fixed with the new allocations model.
https://github.com/square/okhttp/pull/2045

It still happen on version 3.2.0. My app have 2k DAU and 300+ crashes last 30 day! How can I fix it?

@iceteahh please open a new issue with a stacktrace. If you have steps to reproduce, please include that also.


In TUI allow a scape hatch so that the json path result is one value only

Did you search for existing issues already?
Yes
Is your feature request related to a problem? Please describe.
Given I'm using the TUI
And I'm using  hypothetical list all endpoint
And I want to just copy the id of the index 1 element
[
  {
    "id": "681e0103-f78e-4763-aa30-6bbed06e3615",
    "name": "john",
    "phone": "123",
    "email"<EMAIL_ADDRESS>  },
  {
    "id": "47d27fd8-6679-4fcb-ac63-ceb06edcb7bf",
    "name": "mary",
    "phone": "505-81293728",
    "email"<EMAIL_ADDRESS>  }
]

When I enter the JSONPath in the TUI
Then I should get only one value so that then I can just do the action "Copy Body"

But instead I get an array, so I have to go into view body, so that vim is openend and from there select what I want. This should be easier to do.
And in a sense is even worse because I have my EDITOR environment variable to nvim, making this last step described even more anoying because of all the plugins that I have

Describe the solution you'd like
What I can think of is an action "Copy Body First Element"  in the response panel when there is a JSONPath expression already in. I'm open to other suggestions, but it should be easy to use
Describe alternatives you've considered
idk
Additional context
idk

I see why this is annoying but I'd rather not add a special case for this in Slumber. Also FWIW even if this was added, it would still copy including the wrapping quotes so it wouldn't get what you want. Some potential alternatives:

Your terminal probably supports disabling mouse reporting temporarily so you can just copy the text directly in Slumber. In iterm this is done by holding Option. For other terminals try searching "disable mouse reporting temporarily" or similar
Copy the entire body with the Copy Body action, then pipe it through jq with paste | jq -r .0 | copy (copy and paste are aliases you'll have to define, based on what OS you use)
Open the body in your configured viewer/pager (less by default) with the "View Body" action and copy the ID there


Memory leak when publishing via realtime

See screencast: https://www.screencast.com/t/IE5uVcUj
The user bisected this as a regression from 1.0.3 to 1.0.4, when Sentry was introduced.

I can't reproduce this. I've used this code:
func publish() {
    let channel = client.channels.get("test")
    channel.publish("event", data: "ASDFASDLPFG,ASDKLPFGMPASDKMFPKOASKMDFPIOADSPIFJ OIMADSOIFCMOIASJDFPIOAMSÒIFPCOIAWJERPMOICJAWEPOCMPEOIRJCMPAOIWECFRPOAIWEJFCPMOIAWEJFMCPOAWIJEFPOCMIOPJAMWIOEFJCMPOAIWEJFPCMO ASDOFKAI,ACSIOEJRSAPOF")
    delay(0.2) {
        publish()
    }
}

But the memory kept constant the whole time...

@tcard Please ask the user to try this branch and see if it helps: pod 'Ably', :git => 'https://github.com/ably/ably-ios.git', :branch => 'fix-625'. I turned off the additional log data for Sentry.

Enabling address sanitizer could also help us getting more information: https://developer.apple.com/documentation/code_diagnostics/address_sanitizer/enabling_the_address_sanitizer
The client should enable it and look something like ⬇ in the log:
==7829==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 7 byte(s) in 1 object(s) allocated from:
    #0 0x42c0c5 in __interceptor_malloc /usr/home/hacker/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:74
    #1 0x43ef81 in main /usr/home/hacker/memory-leak.c:6
    #2 0x7fef044b876c in __libc_start_main /build/buildd/eglibc-2.15/csu/libc-start.c:226

SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).

Nevermind. I reproduce it successfully 🙌

Code to reproduce the problem:
// Using Ably version 1.0.7

import UIKit
import Ably

class ViewController: UIViewController {

    @IBOutlet weak var button: UIButton!

    let options = ARTClientOptions(key: "<redacted>")
    var realtime: ARTRealtime!

    override func viewDidLoad() {
        super.viewDidLoad()
        button.addTarget(self, action: #selector(self.didTouchButton), for: .touchUpInside)

        options.logLevel = .debug
        realtime = ARTRealtime(options: options)
        let channel = realtime.channels.get("memory-leak")
	channel.attach()
    }

    func didTouchButton() {
        let channel = realtime.channels.get("memory-leak")
        var i = 0
        while i != 10000000 {
            channel.publish(nil, data: "asdlçfjaslçdkjf aslkjd alskdjf")
            i += 1
        }
    }

}

@ricardopereira Hmm, I think that will put 10000000 messages in the "waiting for ACK" queue right away, but that's not a leak, that's expected. That's why I put a delay in my code between iterations,  to give some room for ACKs to arrive. The user said he was publishing at a 2 messages/sec rate. Are you sure that's not it?

I’ll check that but it makes sense what you said. Thanks.
On 5 August 2017 at 13:57:55, Toni Cárdenas<EMAIL_ADDRESS>wrote:

@ricardopereira https://github.com/ricardopereira Hmm, I think that
will put 10000000 messages in the "waiting for ACK" queue right away, but
that's not a leak, that's expected. That's why I put a delay in my code
between iterations, to give some room for ACKs to arrive. The user said he
was publishing at a 2 messages/sec rate. Are you sure that's not it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ably/ably-ios/issues/625#issuecomment-320442317, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADYIwYagFY1mDagpZl-_6y7_O7EjHX5nks5sVGbTgaJpZM4OsMlr
.

FYI, customer stated in regards to the env:

We are sending messages through Ably very rapidly, about once every 100ms. I was running on device, not simulator, but I was using a Debug configuration. This is a React Native project, and are also using Twilio Video.

[in regards to a question on what he meant by Debug config]: My own project's Debug configuration, not yours. Just the IOS environment. And we are not using the react native lib, just the cocoapod. The code I show in the video is from our native bindings, and only IOS uses Ably atm.

Could be an IOS 11 issue... we are running ARKit in this app.

@tcard You're right. It's not a leak.
I even tested it using the Leaks instruments and it's clean.
@mattheworiordan I have iOS 11 on my phone and it's working fine ¯_(ツ)_/¯

Closing this as we cannot reproduce.


Make delay between client completion and server results poll configurable

The delay between RPC cast clients/Notifiers reporting test complete and the controller's first poll of the servers should be configurable.
Since RPC cast and Notifiers do not block for an ack from the servers it is possible that all clients will consider the test complete before the messages actually arrive at the servers.  If the controller issues a poll for results from the servers before any messages have arrived then all servers will report zero and the controller will consider the test complete.
When a test is run with a small number of casts/notifications and the message bus has a high propagation delay it is possible that the test will fail in the above scenario.

For the case where we run ombt in a very controlled way (e.g fixed number of clients/servers and messages sent), the user can know in advance how many messages are expected to be received on the servers side.
The test [1] could be modified to something like :
In the case we expect a certain number of messages to arrive :
done = (polling_server_time >= max_polling_server_time or messages_count >= expected_messages_count)

or (if the total number of messages isn't set)
done = (seen == 0)

You've got a good point there!  I'll be traveling the next week but I can work on that change when I get back Or feel free to submit a pull request if you've got the time & desire to try it yourself.

Pull request #10 includes that message count check now.  Let me know what you think.

That looks good. We'll start using the feature.
Thanks !


Demo not working with video

The demo does not yet support video.
As written in the code, this can be done by decoding the video
input_list = []
    if os.path.exists(args.input_files):
        if os.path.isfile(args.input_files):
            # inference on a single file, extract extension
            ext = os.path.splitext(os.path.basename(args.input_files))[1]
            if ext in ['.png', '.jpg', '.jpeg']:
                # image file
                input_list.append(args.input_files)
            elif ext in ['.mpeg', '.mpg']:
                # video file
                print(args.input_files)
                # TODO: decode video and convert to image list
                # initialize the video stream and pointer to output video file
                vs = cv2.VideoCapture(args.input_files)
                writer = None

                # try to determine the total number of frames in the video file
                try:
                    prop =  cv2.cv.CV_CAP_PROP_FRAME_COUNT if imutils.is_cv2() \
                        else cv2.CAP_PROP_FRAME_COUNT
                    total = int(vs.get(prop))
                    print("[INFO] {} total frames in video".format(total))

                    # loop over frames from the video file stream
                    while True:
                        # read the next frame from the file
                        (grabbed, frame) = vs.read()
                        input_list.append(frame)

                        # if the frame was not grabbed, then we have reached the end
                        # of the stream
                        if not grabbed:
                            break

                    vs.release()
                    print("[INFO] Finished processing of video into frames")

                # an error occurred while trying to determine the total
                # number of frames in the video file
                except:
                    print("[INFO] could not determine # of frames in video")
                    total = -1

                #raise NotImplementedError("Inference on video is not supported yet.")
            else:
                raise ValueError("Unsupported extension: {}.".format(ext))

afterwards, go over every frame:
 try:
        with torch.no_grad():
            for i, fname in enumerate(input_list):
                if isinstance(fname, str):
                    # load image
                    raw_image = read_image(fname, 'RGB')
                else:
                    raw_image = fname
                    #NotImplementedError("Inference on video is not supported yet.")

writing to the disk can be done via cv2.VideoWriter
                	# check if the video writer is None
                if writer is None:
                    # initialize our video writer
                    fourcc = cv2.VideoWriter_fourcc(*"MJPG")
                    writer = cv2.VideoWriter(panoptic_out_dir, fourcc, 30,
                        (panoptic_pred), True)

                    # some information on processing single frame
                    if total > 0:
                        elap = (end - start)
                        print("[INFO] single frame took {:.4f} seconds".format(elap))
                        print("[INFO] estimated total time: {:.4f}".format(
                            elap * total))

                # write the output frame to disk
                writer.write(output)

Here, I am not sure which to write to the video, I guess the video with the overlay of the predictions would be appropriate.
Thanks for considering including this!

Thanks for the examples!
One question, since video is decoded by opencv, is it in RGB format or BGR format? My code takes RGB format by default so I might need to transpose it if it is in BGR format.
I will create a PR soon, still need your help to encode video and save to disk.

@M-Colley
Please check PR #31, outputs are saved in three lists:
    semantic_image_list: List[np.ndarray] = []
    instance_image_list: List[np.ndarray] = []
    panoptic_image_list: List[np.ndarray] = []

Is it possible to write results to video without saving them to disk first?

The demo code from Detectron2 now supports video: https://github.com/bowenc0221/panoptic-deeplab/blob/master/tools_d2/demo.py


hot fix for quotes

sorry just found this bug

No problem, could you please let me knows if the 0.4.5 version works as expected ?


[CT-1901] [Bug] Revoke granted IAM roles fails

Is this a new bug in dbt-redshift?

[X] I believe this is a new bug in dbt-redshift
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
I am using the new grants setting to grant select permissions on all DBT-generated tables to the AWS Administrator Access IAM role, so that anyone who can access our AWS account can also query the Redshift database, e.g. using Redshift Query Editor.
In Redshift SQL, the grant works like this:
grant select on "mydb"."myschema"."mytable to "IAMR:AWSReservedSSO_AWSAdministratorAccess_XXXXXXXXXXX"

To achieve this, I have added the following in my dbt_project.yml:
models:
  myschema:
    +grants:
        +select:
          # variables are not supported in dbt_project.yml (https://github.com/dbt-labs/dbt-core/discussions/6170)
          - "{{ '\"IAMR:AWSReservedSSO_AWSAdministratorAccess_XXXXXXXXXXXXXX\"' if target.name == 'prod' else '\"IAMR:AWSReservedSSO_AWSAdministratorAccess_YYYYYYYYYYYYYYY\"' }}"

Note the additional quotation marks in the grant statement and the role name. Those are required by Redshift for IAM users/roles.
This works for any table model which is built as table, but not for incremental models. For incremental models, DBT generates a revoke statement first. This however does not contain the quotation marks:
revoke select on "mydb"."myschema"."mytable" from IAMR:AWSReservedSSO_AWSAdministratorAccess_XXXXXXXXXXX;

grant select on "mydb"."myschema"."mytable" to "IAMR:AWSReservedSSO_AWSAdministratorAccess_XXXXXXXXXXX";

The revoke fails with Redshift error message user "IAMR:awsreservedsso_awsadministratoraccess_xxxxxxxxxxx" does not exist.
Expected Behavior
The revoke statement should be valid for IAM users/roles and contain the required quotation marks.
Steps To Reproduce

Create an incremental table model
Set a grant to use an IAM role using the "IAMR:xxxx" syntax
Run the model
Run the model again (incrementally) and see the revoke fail

Relevant log output
No response
Environment
- OS: Windows 10
- Python: 3.9.1
- dbt-core: 1.3.1
- dbt-redshift: 1.3.0

Additional Context
No response

As a workaround, I run the following macro in the on-run-end hook:
{% macro create_schema_grants() %}
{% for schema in schemas %}
grant usage on schema {{ schema }} to {{ var("iam_grant_role_admin") }};
grant select on all tables in schema {{ schema }} to {{ var("iam_grant_role_admin") }};
{% endfor %}
{% endmacro %}

where the variable is defined in dbt_project.yml:
vars:
  iam_grant_role_admin: "{{ '\"IAMR:AWSReservedSSO_AWSAdministratorAccess_XXXXXXXXXXXXXX\"' if target.name == 'prod' else '\"IAMR:AWSReservedSSO_AWSAdministratorAccess_YYYYYYYYYYYYYYY\"' }}"

Thanks for opening @mp24-git! I think this is a duplicate of: https://github.com/dbt-labs/dbt-core/issues/6444
We might want to quote grant recipients by default, except on databases where quoting leads to gnarly case sensitivity (Snowflake).


Necessity of Sarah SIS and SID Interpolation

The original sarah datasets, SID and SIS, have both a band of nans along the earth where dawn and nightfall takes place. On one side you find mostly values > 0, on the other only values of 0.

Atm we are extensively interpolating those areas with a 1d interpolation, which for large cutouts takes a lot of time. The question raises, is the interpolation necessary.

Could you determine whether the interpolation is necessary?

Yes, it's not the case, the interplolation function is fast.

Are you sure about this?
I dug out the profiling I did last week (small UK cutout):

Based on that

I would agree that a single interpolation is fast (time percall < 1s)
The number of calls is extremly high due to the way the data is decomposited such that we get ncalls = 6221 in the example and the majority of the cumulated time somewhere in the interpolation step (~ 4800 s).

Interpolation is necessary for older years in sarah, i think there was an analysis in Pfenninger 2016

Thanks for the clarification!
They mention as a reason for interpolating (pg. 1253):

For the analysis performed here, missing periods of 6 h or shorter are interpolated from neighboring values. Longer periods are filled by taking data for the same dates from the preceding year (or the subsequent year in the first year ofdata), and adjusting by the between-year difference in mean of the 7 days before and after the missing period. The amount of missing data and the difference between raw and filled SARAH data is shown later in Fig. 11.

The relevant area is the gray one.
What do you think @FabianHofmann ?

And some more fuzzy tidbit from me, either from 2000 or from 2010, there wasn't any periods longer than 6h, that's why i implemented only the first half of what stefan did.

closing this, the interpolation can now be turned off in #20


Parallel random number generation

Generation of random primes can be sped up by parallelizing. On the implementation side, there are two possibilities:

Generate several random seeds and run searches based on them in parallel. This will mean that we will have to build the small residues table for each of them, but it is not a big overhead for "production-size" primes (>=1024 bit).
Start with the same random seed and a single residue table, and start parallel searches from different points within the range covered by the generated table.

A more complicated part is the API. How do we expose that in the most async-runtime-agnostic way? The parallel tasks will need to take some kind of a signal object as an argument, so that they could be terminated when one task finds a prime. The stop points could even be checked on every internal Miller-Rabin iteration (that is, in-between every modular exponentiation there).

I think this can be considered fixed with #60 merged. It doesn't seem to be possible to abstract away the thread pool implementation, but it remains private, so at least it won't bother the user.
More cancellation points probably won't help all that much with the performance since we have to go through hundreds of checks before we find a prime, so most of the checks will still be executed completely.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26147

TagBot fix

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44612

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/57057

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/93387

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/96001

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113555

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120069


Fix tenantnamespace UTs

This change has fixed the problem that tenantnamespaces cannot be cleaned up in UTs.
The following have been done:

Since tenantnamespace UT has tenant controller installed recently, we should remove creating tenant admin namespace step in old tests.
The request chan used in TestReconcile is a blocking channel, we have to make sure the request is read from the channel otherwise the following reconcile logic is blocked. Hence, in all tests, we make sure a reconcile request is received after deleting tenantnamespace CR and wait until the CR is removed before calling deleting tenant. This ensures that the finalizer of the tenantnamespace CR is removed.
Fix a bug in tenantnamespace reconciler to handle a case that the clusterrole does not exist when the tenant does not have the tenant users specified in the spec.

/assign @rjbez17

/lgtm
/approve


Validate database prefix against DBNAME_REGEX for system dbs

Overview
Previously we only checked that the suffix of the database is
matching one of the predefined system databases. We really should
check the prefix against DBNAME_REGEXP to prevent creation of
illegally named databases.
Testing recommendations
make eunit apps=couch tests=validate_dbname_fail_test_,validate_dbname_success_test_,is_systemdb_test_

Related Issues or Pull Requests
This fixes #1644
Checklist

[x] Code is written and works correctly;
[x] Changes are covered by tests;
[ ] Documentation reflects the changes;

hello,
i just want to make sure that this doesn't break our current usage.
we create DBs with names like this account%2F85%2Fea%2F6075c6c1e266f8512e2233541bdb-201807

@lazedo
It would still work:
(node1@<IP_ADDRESS>)3> couch_db:validate_dbname("account/85/ea/6075c6c1e266f8512e2233541bdb-201807").
ok

=======================================================
  All 144 tests passed.


Investigate design/architecture surrounding NSURL____ classes

It seems moderately likely that our current object model surrounding NSURLConnection, Protocol, Session, Request and Response, are incorrect. Connection callbacks are currently built on top of Protocol callbacks, which do not appear to support uploading, making it unclear how Connection should support uploading. Additionally, the mapping of Projections objects to NS objects seems intuitively incorrect, as Protocol wraps nearly all of them, and the rest wrap basically none.
Spend some time figuring out what the correct approach here is.

Please be sure to add support for
NSURLProtocol	propertyForKey:inRequest:
NSURLProtocol	setProperty:forKey:inRequest:
NSURLSessionTask	suspend


Add an option for custom CSS

It would be great to have an option to allow custom CSS to be applied on the webpage by phantomJS before rendering the screenshot. Do you plan to add this feature in the future ?
Thx

We might as well expose the whole page object itself and let the user do whatever. Thoughts @sindresorhus?

@kevva :-1: Then the user is free to change and break anything and will complain to us when it breaks what we do. I'd rather have defined and controlled ways to do this.

That's the downside of the flexibility that'd give, yeah. I'll add an option for this then.

How should the API look like for this feature? Would it accept raw css, or a file?
const pageres = new Pageres({delay: 2})
    .src('yeoman.io', ['480x320', '1024x768', 'iphone 5s'], {crop: true})
    .css('custom.css')
    .dest(__dirname)
    .run()
    .then(() => console.log('done'));

FWIW, the raw css options would be suficient for my personal intended use.

Actually, it would be pretty easy to check if the argument provided is a file or not so we can support both. I can imagine that if you really want to add a lot of custom css stuff, you would rather prefer a separate file instead of embedding the css.

I really appreciate the effort guys. Thanks a lot !


Red and Blue color values swapped on iOS app (RoboVM issue?)

To begin, I am not sure if this is a LibGDX issue, a RoboVM issue, or an issue with my application configuration.
I have a major roadblock in releasing my iOS app, which concerns the swapping of the red and blue color  bits on my app. I have tested my app on an Android device, on both an OS X and Windows machines, and on the iOS simulator. On all these devices, the color values appear like the screenshot below:

However, on an actual iOS device, the colors appear like the following image:

I tested the app on multiple iOS devices running different versions of iOS (8 and 9), and it still appeared like the second, incorrect image.
I tried to edit the color and depth formats in the IOSApplicationConfiguration to no avail, and tried all combination of the two. I also looked at the documentation for any pList attributes that may be causing the bug, but I found nothing of relevance. What could be a possible explanation to this error?
The project was first generated using the LibGDX Eclipse project generation utility back when LibGDX was still in version 1.5, and RoboVM was still in Beta. The projects have been converted to Gradle projects using the Eclipse Gradle plugin, and I am compiling the project using the Eclipse RoboVM plugin. Hopefully this information helps. I will provide code snippets of any part of my code if asked.

For anybody in the future wondering what was (probably) the problem: iOS (the OS) likes "crunched" png images, so RoboVM provides function to crunch the images automatically. This crunching however violates the PNG standard, so when libGDX's png-compliant loader tries to load the images, they are "corrupted".
TLDR: Disable PNG crunch in RoboVM
<skipPngCrush>true</skipPngCrush>


Deploying Customized store Applications

@chiarnglin Hope you are doing good.We had a question related to customized store applications.
The present existing code contains version that works for a new application but when we customize any application from the store, in servicenow we have two version numbers.(customized version and base version : mentioned in below link)
https://docs.servicenow.com/bundle/quebec-application-development/page/build/applications/task/manage-customizations-store-apps.html
So, for these applications, how can we deploy in pipeline using this code.
Which attribute has to be used for customized version and base version?

Hello!
First of all, I'd suggest checking docs -
https://developer.servicenow.com/dev.do#!/reference/api/quebec/rest/cicd-api#cicd-POST-app_repo-install?navFilter=cicd
Don't forget to switch to Quebec.
As you can see, baseAppVersion and autoUpgradeBaseApp has default values
and not mandatory fields.
If you want to use them, please set up Github secrets(
SNOW_BASE_APP_VERSION, SNOW_AUTO_UPGRADE_BASE_APP), then add
baseAppVersion: ${{ secrets.SNOW_BASE_APP_VERSION }}
autoUpgradeBaseApp: ${{ secrets.SNOW_AUTO_UPGRADE_BASE_APP }}
to your workflow file.
Also, you can verify this step in a manual way by using Postman(or another
REST client) and POST query with following format:
https://{{APP_CLIENT_INST}}
/api/sn_cicd/app_repo/install?version={{VERSION}}&scope={{APP_SCOPE}}&auto_upgrade_base_app={{TRUE/FALSE}}&base_app_version={{BASE_VERSION}}
Thanks, Stan
вт, 13 квіт. 2021 о 10:25 Vinay @.***> пише:

The present existing code contains version that works for a new
application but when we customize any application from the store, in
servicenow we have two version numbers.(customized version and base version)
https://docs.servicenow.com/bundle/quebec-application-development/page/build/applications/task/manage-customizations-store-apps.html
So, for these applications, how can we deploy in pipeline using this code.
Which attribute has to be used for customized version and base version?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ServiceNow/servicenow-cicd-azure-extension/issues/19,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4SNFFMPWXNWXAQGG7ULYTTIPWYHANCNFSM422YJ43Q
.

Hello Stan,
Thanks for your response and any idea if this is already incorporated in this azure extension?
Kind regards,
Vinay

As far as I know it's in schedule (up to 2-3 month).
On Tue, Apr 13, 2021, 12:57 Vinay @.***> wrote:

Hello Stan,
Thanks for your response and any idea if this is already incorporated in
this azure extension?
Kind regards,
Vinay
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ServiceNow/servicenow-cicd-azure-extension/issues/19#issuecomment-818611413,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4SNFEN66AFDTXH3OTOHFTTIQIRVANCNFSM422YJ43Q
.

Hi @vinay2099,
We're currently in the process of updating our external integrations (including Azure Pipelines extension) for our Quebec features, including application customizations for Store apps. @zostrum (Stan) is our developer working on the updates. I don't have an exact date for the release yet, but we'll work on getting these updates out as soon as we can for our early Quebec adopters.
On a separate note, I'd like to jump on a call with your team since it's been a few months, sync up with you on roadmap and your top pain points or feature requests! Can you reach out to me at<EMAIL_ADDRESS>Thanks,
Chiarng


[Feature Request] Support multiValueQueryStringParameters

API Gateway gives multiValueQueryStringParameters to lambda when QueryParameters are multiple parameters.
However, mangum always passes queryStringParameters to query_string in ASGI's scope.
I can create a PR if you want it to support multiple query parameters.
Related Links
https://aws.amazon.com/blogs/compute/support-for-multi-value-parameters-in-amazon-api-gateway/

@koxudaxi yep, I think we ought to support this here. Please go ahead and open a PR, thanks!

Resolved by https://github.com/erm/mangum/pull/81

Reopening this because I'm noticing that https://github.com/erm/mangum/pull/81 actually replaces queryStringParameters, but we should be handling (and testing) both. I'll put forward a PR myself when I have a chance, but happy to accept any additional PRs in the meantime.

@erm

we should be handling (and testing) both.

I think we don't need to handle queryStringParameters
I tested a lambda app with a single query parameter and multi-value query parameters.
API Gateway always gives Event with queryStringParameters and multiValueQueryStringParameters.
If I'm misunderstood then I'm sorry.
But, we may need to add a test for a single query parameter.

@erm
I put the event results.

I show you some patterns as text.

?test=param1&test=param2
'queryStringParameters': {'test': 'param2'}, 'multiValueQueryStringParameters': {'test': ['param1', 'param2']},

?test=param1
 'queryStringParameters': {'test': 'param1'}, 'multiValueQueryStringParameters': {'test': ['param1']},

?test=
'queryStringParameters': {'test': ''}, 'multiValueQueryStringParameters': {'test': ['']},

Query parameter is nothing
 'queryStringParameters': None, 'multiValueQueryStringParameters': None,

@koxudaxi thanks for explaining! I wasn’t aware of how normal query strings would work with the new changes. If you could PR a test to the effect of your examples I would appreciate it.


fix AgentTokenBufferMemory to properly honour token limits

Description:
AgentBufferTokenMemory was not properly reding existing messages from history and going over set token limit. This PR changes its implementation slightly by keeping separate, in-memory, buffer that holds recent messages whose total size does not exceed specified max_token_limit. Chat history object holds and retains all messages.

Issue: the issue #
Oveflowing chat memory and therefore token limit budget for llm calls

Dependencies:
None

Tag maintainer: for a quicker response, tag the relevant maintainer (see below),

Twitter handle:
NA

Note to self:
If no one reviews your PR within a few days, please @-mention one of @baskaryan, @hwchase17.

@baskaryan , @hwchase17 and chance someone could give it look?

fixes #15593

memory objects are now legacy, for memory chains/agents we recommend using langgraph


back mem action

min is save / load
nut we also can have MemStat and traits for unload / load and save
so if a thread is unused awhile (about 1h) and it use enough memory (by posted text (limit on each post ~16KB))  let's say about 300KB (it's +- enough idk) then we can unload it(posted text) and load when some one will read it

16kb (max post RAM size) * 500 (posts) * 100 (thrs) * 20 (boards) = ~16gb
so... low prior


Add OPTIONS method to the Lambda Function

Use this to test:
curl -X OPTIONS -H "Access-Control-Request-Method: POST" -H "Access-Control-Request-Headers: content-type" -H "Origin: localhost" -v https://9u4xt4nqr1.execute-api.us-west-2.amazonaws.com/default/test

Fix API issue: Add OPTIONS method to pass pre-flight cors error.

add options method to lambda function
add options route to api with the lambda function integration.
Test the API ping using Curl
curl -X OPTIONS -H "Access-Control-Request-Method: POST" -H "Access-Control-Request-Headers: content-type" -H "Origin: localhost" -v https://9u4xt4nqr1.execute-api.us-west-2.amazonaws.com/default/test
Test API ping using the front end component

time estimate: 10 minutes


start transforming test into a matrix

Codecov Report

Merging #37 (0b3a05e) into main (2f07ad9) will increase coverage by 1.72%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #37      +/-   ##
==========================================
+ Coverage   40.28%   42.00%   +1.72%
==========================================
  Files          36       36
  Lines        3197     3197
==========================================
+ Hits         1288     1343      +55
+ Misses       1845     1789      -56
- Partials       64       65       +1

Flag
Coverage Δ

go_tests
42.00% <ø> (+1.72%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

xopjson/models.go
47.27% <ø> (ø)

xopjson/jsonlogger.go
56.69% <0.00%> (+0.19%)
:arrow_up:

basegroup.go
38.70% <0.00%> (+1.84%)
:arrow_up:

xoputil/jbuilder.go
77.77% <0.00%> (+3.70%)
:arrow_up:

xoptest/testlogger.go
55.15% <0.00%> (+4.12%)
:arrow_up:

xopjson/attributes.go
22.80% <0.00%> (+4.67%)
:arrow_up:

span.go
23.72% <0.00%> (+5.08%)
:arrow_up:

xopconst/attributes.go
40.81% <0.00%> (+12.24%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add persistent undo

I realize this is on your todo already, but I figured an open issue might both increase pressure for this particular feature, and serve as a handy little notification for me whenever it gets added.

Reasonable enough. Whenever I manage to free up some time to do it I'll make sure to update the issue.


ios: Local images are not rendering in 0.62.2

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
I am rendering local images, using the 'Image' component, on android, with path like  file:///data/user/0/com.xxxx/files/productdata_da13681addffaed7622ece9b2bb56e22bc65f6b9.jpg.
On iOS, however, these images are not rendering.
I tried the suggestion in https://stackoverflow.com/a/54627588/5532513, didn't help.
React Native version:
System:
OS: macOS 10.15.5
CPU: (8) x64 Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
Memory: 1.49 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.16.2 - /usr/local/bin/node
Yarn: 1.21.1 - /usr/local/bin/yarn
npm: 6.14.4 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK: Not Found
IDEs:
Android Studio: 4.0 AI-193.69<IP_ADDRESS>14223
Xcode: 11.5/11E608c - /usr/bin/xcodebuild
Languages:
Java: Not Found
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.11.0 => 16.11.0
react-native: 0.62.2 => 0.62.2
Steps To Reproduce
Just using:
<Image
        style={{ width: 50, height: 50 }}
        source={{ uri: mobileImageFilePath }}
      />

Expected Results
Images should be displayed.

Yup I'm getting the same problem. I made a new project with react-native init, added a local file, and then used a <Image /> component. It works as expected on Android, but not on iOS. Doesn't work with URIs either.

OS: macOS 11
Platforms: iOS 14.0
Xcode: 12.0
react-native: 0.62.2 => 0.62.2
 iOS14.0 cannot display pictures, iOS13.5 displays normally

Same issue here!

Are you also having a problem only with local files that your application is storing?
(I would like to emphasize that I don't have any problems with assets)
I am using RNFetchBlob to store these files. Do you? The problem may be different behavior of RNFetchBlob on iOS compared to android.

I have this problem with local assets in my RN app project, as well as rendering remote assets with a url.

As I wrote above, in my case local assets work fine, and I am not using url to display images.

I am closing this issue. I need to do some more tests.
I suggest that you open new issue(s) for your problems. It seems that the at least some of these problems are different than mine.

I have this problem with local assets in my RN app project, as well as rendering remote assets with a url.

Hello, you solved the problem with local image paths? I don’t understand why the author closed the ticket

I didn't solve the problem yet, but I realized that I need to do more tests before posting an issue.
At least some of the comments reported other issues - like displaying assets and rendering from a URL, so they should open other issues. You can also open an issue, explaining your problem.

I have the same issue

I have same issue with iOS 14. It doesn't show local images in my react native app.

so, how to solve it in iOS 14?

This has been fixed in 0.63.2 See https://github.com/react-native-community/releases/blob/master/CHANGELOG.md#v0632

I am reopening this, until we tests it in 0.63.2 and see that the problem has been solved.

Could we get a hotfix for 0.62?

Looking for a 0.62 emergency fix for this as well.  Way to go Apple, way to go...

i can't update the react-native to 63 yet... need a fix on 62

For anyone that cant't upgrade to 62 like me and need to fix this, get yourself set up with https://github.com/ds300/patch-package and then put this in your patches folder:
react-native+0.62.2.patch:
diff --git a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
index 21f1a06..0ff66f3 100644
--- a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
+++ b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
@@ -275,6 +275,8 @@ - (void)displayLayer:(CALayer *)layer
   if (_currentFrame) {
     layer.contentsScale = self.animatedImageScale;
     layer.contents = (__bridge id)_currentFrame.CGImage;
+  } else {
+    [super displayLayer:layer];
   }
 }

Hotfix for RN 0.61.2 please. I cannot make it work, even my bottom navigator doesn't have images

For anyone that cant't upgrade to 62 like me and need to fix this, get yourself set up with https://github.com/ds300/patch-package and then put this in your patches folder:
react-native+0.62.2.patch:
diff --git a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
index 21f1a06..0ff66f3 100644
--- a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
+++ b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
@@ -275,6 +275,8 @@ - (void)displayLayer:(CALayer *)layer
   if (_currentFrame) {
     layer.contentsScale = self.animatedImageScale;
     layer.contents = (__bridge id)_currentFrame.CGImage;
+  } else {
+    [super displayLayer:layer];
   }
 }

This worked for me for Debug on RN 0.61.5, but it won't work for Release! Any idea? I've even downgraded from Xcode 12 to 11.1 to no avail.

For anyone that cant't upgrade to 62 like me and need to fix this, get yourself set up with https://github.com/ds300/patch-package and then put this in your patches folder:
react-native+0.62.2.patch:
diff --git a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
index 21f1a06..0ff66f3 100644
--- a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
+++ b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
@@ -275,6 +275,8 @@ - (void)displayLayer:(CALayer *)layer
   if (_currentFrame) {
     layer.contentsScale = self.animatedImageScale;
     layer.contents = (__bridge id)_currentFrame.CGImage;
+  } else {
+    [super displayLayer:layer];
   }
 }

This worked for me for Debug on RN 0.61.5, but it won't work for Release! Any idea? I've even downgraded from Xcode 12 to 11.1 to no avail.

This worked for me for Debug on RN 0.61.5, but it won't work for Release! Any idea why? I've even downgraded from Xcode 12 to 11.1, hoping that would solve the issue, but it didn't. This is the output of xcodebuild -showsdks

If you've used my patch verbatim then it's probably not working because you're on a different version and patch package won't like that.
Regardless, as far as I am aware the issue is only on iOS 14, so it works in Debug mode because you're running on an iOS simulator that is running version 13. If you can't upgrade to a fixed version of RN< then go to node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m and add that extra else statement, then run patch-package. Read the docs for patch-package to better understand what I mean.

This worked for me for Debug on RN 0.61.5, but it won't work for Release! Any idea why? I've even downgraded from Xcode 12 to 11.1, hoping that would solve the issue, but it didn't. This is the output of xcodebuild -showsdks

If you've used my patch verbatim then it's probably not working because you're on a different version and patch package won't like that.
Regardless, as far as I am aware the issue is only on iOS 14, so it works in Debug mode because you're running on an iOS simulator that is running version 13. If you can't upgrade to a fixed version of RN< then go to node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m and add that extra else statement, then run patch-package. Read the docs for patch-package to better understand what I mean.

This worked for me for Debug on RN 0.61.5, but it won't work for Release! Any idea why? I've even downgraded from Xcode 12 to 11.1, hoping that would solve the issue, but it didn't. This is the output of xcodebuild -showsdks

If you've used my patch verbatim then it's probably not working because you're on a different version and patch package won't like that.
Regardless, as far as I am aware the issue is only on iOS 14, so it works in Debug mode because you're running on an iOS simulator that is running version 13. If you can't upgrade to a fixed version of RN then go to node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m and add that extra else statement, then run patch-package react-native. Read the docs for patch-package to better understand what I mean.

Yes, I've done the changes manually and applied patch-package react-native to keep them, to no avail.

This worked for me for Debug on RN 0.61.5, but it won't work for Release! Any idea why? I've even downgraded from Xcode 12 to 11.1, hoping that would solve the issue, but it didn't. This is the output of xcodebuild -showsdks

If you've used my patch verbatim then it's probably not working because you're on a different version and patch package won't like that.
Regardless, as far as I am aware the issue is only on iOS 14, so it works in Debug mode because you're running on an iOS simulator that is running version 13. If you can't upgrade to a fixed version of RN then go to node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m and add that extra else statement, then run patch-package react-native. Read the docs for patch-package to better understand what I mean.

Yes, I've done the changes manually and applied patch-package react-native to keep them, to no avail.

It's likely to be a caching issue somewhere in the build process I would wager. Not much else I can do to help, my patch was just the following commit: https://github.com/facebook/react-native/commit/b6ded7261544c703e82e8dbfa442dad4b201d428 I don't have any real deeper understanding of this issue.

It's likely to be a caching issue somewhere in the build process I would wager. Not much else I can do to help, my patch was just the following commit: https://github.com/facebook/react-native/commit/b6ded7261544c703e82e8dbfa442dad4b201d428 I don't have any real deeper understanding of this issue.

It is a bit obscure, as we've tried doing it in another computer with Xcode 11.1, and the issue still persists. On Android it does build correctly, I'll try with a blank slate project and see if it could be any of the Cocoapods libraries I use that's causing the issue.

It is a bit obscure, as we've tried doing it in another computer with Xcode 11.1, and the issue still persists. On Android it does build correctly, I'll try with a blank slate project and see if it could be any of the Cocoapods libraries I use that's causing the issue.


Cleanup PlatformDependent* code

Motivation:
PlatformDependent* contains some methods that are not used and some other things that can be cleaned-up.
Modifications:

Remove unused methods
cleanup

Result:
Code cleanup.

just some cleanup

Cherry-picked into 4.1 (0c48265) and 4.0 (01d747a)

@normanmaurer - The hyperlink for 4.1 isn't correct ... did it get merged correctly?

@Scottmitch yep... fixed the comment.


DockerService interface

Could you take a look to this commit https://github.com/CloudOpting/cloudopting-manager/commit/3cf1696bac4d40d987a5c186e648bf9877af57f3?
I think that it is a better way to provide a pure java interface and abstract BPMN logic from tokens and this stuff.

The DockerService is a singleton by definitio of injection of spring.
This means that each sequent calls will be done on the same instance if we do not have the token the user2 could get the answer of the user1 also we as a java application decided we want that the single process will be serial but we could have more than 1 process running at time so the python component will be called to do more than one build at time on different folders so you need to be sure to give the correct answer to the correct user.
For sure the python API will have to use a token.
this has to be passed down to all the invoking chain.


Closure conversion: this access is not rewritten correctly

From @karlklose on October 12, 2016 8:15
FAILED: none-vm debug_x64 language/implicit_closure2_test
Expected: Pass
Actual: RuntimeError
CommandOutput[vm]:

stderr:
...
Unhandled exception:
Closure call with mismatched arguments: function 'b'

NoSuchMethodError: method not found: 'b'
Receiver: Instance of 'Closure#0'
Arguments: []
#0      Object._noSuchMethod ()
#1      Object.noSuchMethod ()
#2      Closure#0.call ()
#3      A.foo ()
#4      main ()
#5      _startIsolate.<anonymous closure> ()
#6      _RawReceivePortImpl._handleMessage ()

Command[vm]: DART_CONFIGURATION=DebugX64 reify/bin/reified_dart --ignore-unrecognized-flags --package-root=out/DebugX64/packages/ kernel-sdk/sdk/tests/language/implicit_closure2_test.dart
Took 0:00:11.736345

Short reproduction command (experimental):
    python tools/test.py -t120 language/implicit_closure2_test

===
=== 1 test failed
===

Copied from original issue: dart-lang/kernel#41

This test is obsolete: the referenced test passes with closure conversion enabled.


merge stat functions from jmh530

see https://github.com/libmir/numir/pull/22#issuecomment-366453609

@jmh530 I changed the default variance behaviour to isPopulation=true because numpy's default is it. And also add my previous UTs for alongDim cases.

I have no issue with the population default changing.
For documentation UTs, you might double-check that everything that is byDim is converted to an alongDim. I wouldn't consider this an issue for the non-documentation UTs.

BTW do you have any ideas to solve this linker error on appveyor (windows LDC) ?
https://ci.appveyor.com/project/ShigekiKarita/numir-f7jog/build/1.0.43/job/2vrdd05pv7hih959

Codecov Report

Merging #24 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master    #24    +/-   ##
======================================
  Coverage     100%   100%
======================================
  Files           9      9
  Lines        1062   1221   +159
======================================
+ Hits         1062   1221   +159

Impacted Files
Coverage Δ

source/numir/stats.d
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0779596...ad59ee1. Read the comment docs.

There is a lot of places where map can be replaces with simple ops or vmap. Some of them allocates a closure if a lazy slice is returned. So operators and/or vmap should solve the problem and simplify readability.

@9il I think when I had originally written this up vmap was not yet in mir.
Thanks for the review. I plan to do some work on cholesky in Lubeck
tomorrow.
On Mon, Feb 19, 2018 at 12:48 AM, Ilya<EMAIL_ADDRESS>wrote:

There is a lot of places where map can be replaces with simple ops or
vmap. Some of them allocates a closure if a lazy slice is returned. So
operators and/or vmap should solve the problem and simplify readability.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/libmir/numir/pull/24#issuecomment-366594577, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMJWyo1FxY0fQWcx35r2ioo-VuBes17iks5tWQsegaJpZM4SJwX8
.

@9il I think when I had originally written this up vmap was not yet in mir.

Yes, this is quite fresh addition.

I plan to do some work on cholesky in Lubeck
tomorrow.

Oh, please take a look into the PR first, https://github.com/kaleidicassociates/lubeck/pull/5.
It contains cholesky and few others. The PR will be ready at the end of the month. (it is going slowly, the contributor is student and it is his first D program). I will ask him to move cholesky in a separate PR and merge it faster.

Great. I noticed it earlier today (for some reason I had not been following
Lubeck). I hadn't looked too closely because the discussion was in Russian,
but the code is easy to follow.
On Mon, Feb 19, 2018 at 1:00 AM, Ilya<EMAIL_ADDRESS>wrote:

@9il https://github.com/9il I think when I had originally written this
up vmap was not yet in mir.
Yes, this is quite fresh addition.
I plan to do some work on cholesky in Lubeck
tomorrow.
Oh, please take a look into the PR first, kaleidicassociates/lubeck#5
https://github.com/kaleidicassociates/lubeck/pull/5.
It contains cholesky and few others. The PR will be ready at the end of
the month. (it is going slowly, the contributor is student and it is his
first D program). I will ask him to move cholesky in a separate PR and
merge it faster.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/libmir/numir/pull/24#issuecomment-366595901, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMJWynK4h-4AQhNCOBLeU7k_wdZ0honrks5tWQ4CgaJpZM4SJwX8
.

Now appveyor recovers because I replaced numir.stats.power with ^^ in mir-algorithm.


Android support

[Enter feedback here]

The article stated 2 contradictory facts :

We have full Android and iOS mobile support for an attendee to join.
the view-only attendee won't be able to experience the following options in meetings: Join the Overflow Room via the Teams Android mobile app.

The article stated that "The view-only experience is enabled by default for any organizer who has E3/E5/A3/A5 SKU" but in the message center Office 365 MC240169 Microsoft communicated that it's OFF by default
Is the Q&A feature available in the overflow room ?

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

ID: 2bf705c2-1f24-bdb5-e712-e8408b941aca
Version Independent ID: ddedd7e0-7d85-06e0-7f20-8b83b3dccec7
Content: View-only meeting experience - Microsoft Teams
Content Source: Teams/view-only-meeting-experience.md
Service: msteams
GitHub Login: @cichur
Microsoft Alias: v-cichur

Hi @mamrouni,
Thank you for your comments.
We'll fix the information about Android support. Both Android and iOS are supported.
View-only is OFF by default. We'll correct the article.
Q & A isn't available for View-only participants.
Thank you,
Cindy


Add ncpi-catalog-dug explorer based on ncpi-catalog

Need
We will use this framework to deliver a modification of the NCPI  catalog augmented with data from the "Dug" project.
DOD

A new explorer based on the  ncpi-catalog config called ncpi-catalog-dug
Config is exactly the tame except for the name of the explorer.
New dev script in package.json
New build script in package.json

@BruceRodrigues an updated logo for the ncpi catalog "Dug" version can be found here:
https://www.figma.com/file/i4uZsYkKAML9ivi2TIo6ug/explore-dashboard?node-id=1378%3A25429


Fixing compilation on latest Boost

fixing compilation on Boost 1.69
also assumes that Boost include libraries are at "/usr/local/Cellar/boost/1.69.0_2/include"

Thank you for your pull request and helping to revitalize this example for a more recent version of Boost.
I see you've hard-coded the location of the Boost library under /usr/local/Cellar/, making an assumption that the user has installed Boost using Homebrew. I see a few issues with this approach:

Homebrew does not usually preserve older versions of software, so once a version of Boost newer than 1.69 becomes available on Homebrew, the 1.69 version may not be available anymore via Homebrew's servers. While older versions of Homebrew recipes can sometimes be "recovered" by digging through the git history (https://danepowell.com/blog/homebrew-formula-versions), this method does not always work because older recipes may not be compatible with the latest versions of Homebrew and/or MacOS. Thus I see hard-coding the specific version of the Boost library and assuming it's installed via Homebrew causing the building of this example to break easily in the future.
I believe that assuming Homebrew has been used to install Boost means this example could no longer be built on other operating systems like Linux and Windows.
The README for this example describes manually downloading specific versions of Boost and Asio into the root of the repo as a prerequisite for building the example, and I don't see that you've updated that part of the README for installing those libraries via Homebrew instead.

To avoid these issues, what do you think about modifying your pull request to remove the Homebrew assumption and instead maintain the current method of downloading the specific versions of the Boost and Asio libraries into the root of the repo? I.e. your pull request could update the README and Makefile to specify using the newer version of Boost and/or Asio but still assuming the user will manually download these libraries into the root of the repo.
To throw out another idea, what about integrating the specific versions of Boost/Asio as git submodules of this repo? E.g. here's the release/tag for Boost 1.69 we could use to add Boost as a submodule to this repo: https://github.com/boostorg/boost/releases/tag/boost-1.69.0 I believe that would remove the step of manually downloading the specific versions of these libraries, although we may need to document how to clone the repo in the correct way that also fetches the code from the submodules.

I used to use CMakeLists.txt instead. Although I need to change the directory structure, is that fine?

Can you clarify why you want to switch to cmake?
I think you may be thinking of using the built-in FindBoost module to make it easier to discover where Boost is located on the system. I think that is a good idea, but I would ask that you make use of the version argument to require a specific version of Boost, as this example may not always be compatible with newer versions of Boost as they are released.
Can you also update the parts of the README that would become stale after the switch to using cmake?

@kevincon sure thing!

Just pushed a new commit, I added find Boost from CMake to make it flexible between systems

I wasn't able to push commits to your PR branch, but I could if you checked this box: https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork
Alternatively, can you cherry-pick these two commits to your branch?
541eec526eef73e3e42b71c250b8121ffb0d165d
0d3b9ed16c29976d4190e3b600f86faeb9be4d93

@kevincon I thought you automatically have push rights to my repo once I fork from you

@dendisuhubdy I pushed some commits to update the README and gitignore the new build directory. Can you push some new commits to address those comments I left before?

Looks good! Thanks again!

@kevincon anytime amigo


from Terser Unexpected token punc «:», expected punc «,»

Discussed in https://github.com/open-telemetry/opentelemetry-js/discussions/4018

Originally posted by devgalintown July 24, 2023
Using  "terser-webpack-plugin": "^4.2.3", in a Vue,js project.
 "webpack": "4.41.0",
"webpack-bundle-analyzer": "^3.0.4",
"webpack-cli": "3.3.12",
"webpack-hot-middleware": "^2.25.3",
"webpack-merge": "^4.2.2",
"webpack-merge-and-include-globally": "^2.3.4",
"webpack-node-externals": "^1.7.2",

Prod Config file structure:
new TerserPlugin({
parallel: true,
extractComments: false,
sourceMap: isDev,
terserOptions:{
compress: isProd,
ecma: 2020
},
}),
It was all building okay before I added Opentelemetry instrumentation.
codebase is similar to this:
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http'
import { WebTracerProvider, BatchSpanProcessor, SimpleSpanProcessor, ConsoleSpanExporter } from '@opentelemetry/sdk-trace-web'
import { registerInstrumentations } from '@opentelemetry/instrumentation'
import { getWebAutoInstrumentations } from '@opentelemetry/auto-instrumentations-web'
export default function initializeOtel() {
const headers = {
"Content-Type": "application/json"
}
const collectorOptions = new OTLPTraceExporter(headers)
const provider = new WebTracerProvider()
provider.addSpanProcessor(new BatchSpanProcessor(collectorOptions))
provider.register()
const instrumentations = [
getWebAutoInstrumentations()
]
registerInstrumentations(instrumentations)
}
Initialized in base vue file :
beforeMount() {
initializeOtel()
}
I tried removing terser package but still got the error. Tried ecma script version change, comma remove/add among other. Please help me figure this out.
Thanks.

The tooling you mention above seems to be quiet old. Could you try with up to date tooling?
There is also info missing which OTel version, which typescript version,... you use.

Tooling means webpack version you mean?
Otel versions
"@opentelemetry/api": "^1.4.1",
"@opentelemetry/auto-instrumentations-web": "^0.32.2",
"@opentelemetry/context-zone": "^1.13.0",
"@opentelemetry/exporter-trace-otlp-http": "^0.39.1",
"@opentelemetry/instrumentation": "^0.39.1",
"@opentelemetry/instrumentation-document-load": "^0.32.2",
"@opentelemetry/instrumentation-user-interaction": "^0.32.3",
"@opentelemetry/instrumentation-xml-http-request": "^0.39.1",
"@opentelemetry/propagator-b3": "^1.13.0",
"@opentelemetry/sdk-trace-web": "^1.13.0",
"@opentelemetry/semantic-conventions": "^1.13.0",
I am using Vue.js
"vue": "^2.7.14",
"vue-analytics": "^5.22.1",
"vue-carousel": "^0.7.3",
"vue-clipboard2": "^0.3.1",
"vue-date-dropdown": "^1.0.5",
"vue-i18n": "^8.27.0",
"vue-loader": "^15.10.1",
"vue-multiselect": "^2.1.6",
"vue-recaptcha": "^1.2.0",
"vue-router": "^3.6.5",
"vue-select": "^2.6.4",
"vue-server-renderer": "^2.7.14",
"vue-slick": "^1.2.0",
"vue-slider-component": "2.7.7",
"vue-social-sharing": "^2.4.7",
"vue-style-loader": "^4.1.3",
"vue-template-compiler": "^2.7.14",
"vue-the-mask": "^0.11.1",
"vue2-circle-progress": "^1.2.3",
"vuejs-datepicker": "^1.6.2",
"vuex": "^3.6.2",
"vuex-router-sync": "^5.0.0",

Yes, I was talking about updating webpack, vue, typescript. Typescript version is not mentioned above so don't know which you you use. e.g. vue 2.x goes EOL soon anyway.
I'm not familiar with all these tools but there was at least one issue recently where someone used a too old typescript version causes it's setup to fail.

@Flarna
oh okay.
typescript version: 2.5.3

well, that version is 6 year old. OTel uses 4.4.4 as of new (already 2 years old).
I'm quite sure that such an old typescript version doesn't understand the type definitions emitted by 4.4.4.
I think a tooling update is needed to get compatibility.


Reorganized GUIDs in is_xinput_device and added several missing GUIDs, second attempt

Re-submission of #89564 to fix issues present upon submission (still new to this)
Fixes #76724
Fills in some gaps that were left in the issue, especially with the Xbox One S controllers that received new GUIDs after a firmware update. Also reorganizes the GUIDs to reflect chronological release of hardware. Basically just a follow-up on pull #78043

Never mind, I see the problem wasn't that I didn't link an issue, it's that I was trying to fix a CLOSED issue despite the problem in the issue still manifesting. Will create new, updated issue with new PR.

Hei sorry to bring up some older PR. This was not merged into Godot as far as I can see. Did you resubmit these changes in another PR? Double Input issues with Xbox 1708 controllers are solved for me with these additional changes and it would be nice to have it in the engine at some point.

Do you plan on bringing these changes into the engine at some point? Else I would pick it up and try to get it merged in.

Unfortunately I am not in a position to do so, especially since I do not have access to any of the affected controllers to test.


Bug report

What happened?
If using frontmatter and inline keys with the same value
LIST WHERE  Vault = "Privat"
does not work.
If only using one method the query works.
See also https://forum.obsidian.md/t/dataview-with-keys-from-frontmatter-not-working/38234
DQL
LIST
WHERE  Vault = "Privat"
JS
No response
Dataview Version
0.4.26
Obsidian Version
0.14.6
OS
MacOS

You already have the answer in forum.
This is not a bug: you have two values for the same field (a value in yaml frontmatter and other in the inline field).
The result metadata is:
Vault:
  - Privat
  - Privat

(And please close the answered helps in forum)


I want to specify UIRectCorner on RoundCornerImageProcessor

Issue Description
What
Hi😃 Thank you for developing a very useful library❗
I want to specify UIRectCorner on RoundCornerImageProcessor and Image.kf.image.
For example
let processor = RoundCornerImageProcessor(cornerRadius: 20, targetSize: CGSize(width: 40, height: 40), byRoundingCorners: [.topRight, .bottomRight])

Would you please add this?
Other Comment
I have read the 3.7.1 source code for Image.kf.imgae.
If iOS, just specify a parameter of UIBezierPath.
But if macOS, I dont know how to specify...

Good suggestion. I will look at it now to see what we can do.

Implemented in #669

Thank you very much @onevcat 😍❗


odo forgets environment variable while second push

[kind/bug]

What versions of software are you using?

Operating System: :penguin:
Output of odo version: odo v1.0.0-beta3 (HEAD)

How did you run odo exactly?
odo create nodejs
odo config set --env FOO=BAR
odo push
oc describe dc <dc_name> // you will see env variables
odo push
oc describe dc <dc_name> // boom, there's no FOO=BAR

Actual behavior
After second odo push, env variable is not there in DC
Expected behavior
After second odo push, env variable should be there in DC
Any logs, error output, etc?

Let's start with writing tests that will replicate this, and then implement the fix.

/assign @amitkrout

/unassign @amitkrout

Let's start with writing tests that will replicate this, and then implement the fix.

@kadel the issue is reproducible and I agree with your idea of starting with writing a test. Or rather a failing test in this case. However, odo config view reports the environment variable correctly. We need to execute oc commands and parse its output. Do we have any tests that do this right now? Which category of tests would this fall under?

@kadel the issue is reproducible and I agree with your idea of starting with writing a test. Or rather a failing test in this case. However, odo config view reports the environment variable correctly. We need to execute oc commands and parse its output. Do we have any tests that do this right now? Which category of tests would this fall under?

Yes, we already have tests that execute oc commands and parses outputs to verify if everything was set properly.  There is even a small library in tests helpers that wraps oc commands in a nice way. Just check existing tests.
I think that you can put this test where we have other odo push related tests. cc: @amitkrout

I think that doing odo push right after doing the first odo push should have not created a new DeploymentConfig in the first place because nothing was changed. It looks to me like the env vars of existing DeploymentConfig were not being used properly and this resulting in odo thinking that something changed which resulted in it creating a new pod. https://github.com/openshift/odo/blob/54b9a583f3823ba2b684a327c403f00a46814566/pkg/component/component.go#L1070-L1084
As can be seen above, evl contains the env vars but it's not being used when creating updateComponentParams.


Compile Error when adding a constant to DenseVector/DenseMatrix

The Following yields an error: (Scala 2.13, Breeze 1.2)
import breeze.linalg._

// Works Fine
1.0 - DenseVector(1.0, 2.0)
1.0 - DenseMatrix((1.0, 2.0), (3.0, 4.0))

// Error:
// overloaded method + with alternatives: ... cannot be applied to (breeze.linalg.DenseVector[Double])
1.0 + DenseVector(1.0, 2.0)
1.0 + DenseMatrix((1.0, 2.0), (3.0, 4.0))

Sorry I thought I replied to this. Scala's weird treatment of + to match Java's for string concatenation somehow makes it so that I can't make this overload work. You can use +:+ instead if you want, or obviously you can just flip the LHS and RHS.


Issue creating an apk package to install company certs

Hi,
I'm looking at using apko and melange as an alternative to docker. Normally in our dockerfiles we have to copy in any relevant company certs so that communicating with on-prem services is possible over https.
Usually done like:
cp certs-location /usr/local/share/ca-certificates
Update-ca-certificates
I've been stuck trying to do this using a custom apk.
I've been able to move the certs into the apko build, but update-ca-certificates command is not running so the company certs are not trusted.
I can shell into the container and then run update-ca-certificates manually (as root), which works. This is obviously not desired as I want it to be ran on build.
custom apk packagec config:
package:
  name: certs
  version: v0.1.0
  epoch: 0
  description: "certs"
  dependencies:
    runtime:

environment:
  contents:
    repositories:
      - https://dl-cdn.alpinelinux.org/alpine/edge/main
    packages:
      - busybox
      - ca-certificates

pipeline:
  - runs: |
      mkdir -p ${{targets.destdir}}/usr/local/share/ca-certificates
      cp ./certs/* ${{targets.destdir}}/usr/local/share/ca-certificates
      update-ca-certificates

apko yaml config:
contents:
  keyring:
    - https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
  repositories:
    - https://packages.wolfi.dev/os
    - "@local packages"
  packages:
    - cosign=2.2.4
    - vault=1.13.0
    - wolfi-base
    - certs@local
    - curl
    - busybox
    - ca-certificates

accounts:
  users:
    - username: base
      uid: 65532
      gid: 65532
  run-as: 65532

entrypoint:
  command: /bin/sh -l

archs:
  - x86_64

I've been able to move the certs into the apko build, but update-ca-certificates command is not running so the trusted certs are not trusted.
custom apk packagec config:
package:
  name: certs
  version: v0.1.0
  epoch: 0
  description: "certs"
  dependencies:
    runtime:

environment:
  contents:
    repositories:
      - https://dl-cdn.alpinelinux.org/alpine/edge/main
    packages:
      - busybox
      - ca-certificates

pipeline:
  - runs: |
      mkdir -p ${{targets.destdir}}/usr/local/share/ca-certificates
      cp ./certs/* ${{targets.destdir}}/usr/local/share/ca-certificates
      update-ca-certificates

apko yaml config:
contents:
  keyring:
    - https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
  repositories:
    - https://packages.wolfi.dev/os
    - "@local packages"
  packages:
    - cosign=2.2.4
    - vault=1.13.0
    - wolfi-base
    - certs@local
    - curl
    - busybox
    - ca-certificates

accounts:
  users:
    - username: base
      uid: 65532
      gid: 65532
  run-as: 65532

entrypoint:
  command: /bin/sh -l

archs:
  - x86_64

Though adding a scriptlet would work but still does not work.
scriptlets:
    post-install: |
      #!/bin/busybox sh
      update-ca-certificates