modify swagger.yaml

Coverage increased (+0.04%) to 57.182% when pulling<PHONE_NUMBER>fadb30d05dc0f59db5bacb2690b741 on wemeya:master into 565110d9f172859a17e888220fbdf0c40010d158 on vmware:master.

Coverage remained the same at 57.138% when pulling 1b995e17366ba58417ca20749caefd6cccda0b2d on wemeya:master into 565110d9f172859a17e888220fbdf0c40010d158 on vmware:master.


issue running codecombat in docker on debian

svetlana@thinkpenguin:~$ cd dev
svetlana@thinkpenguin:~/dev$ cd codecombat/
svetlana@thinkpenguin:~/dev/codecombat$ docker-co
docker-compose          docker-containerd-ctr
docker-containerd       docker-containerd-shim
svetlana@thinkpenguin:~/dev/codecombat$ docker-compose up
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?

If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
svetlana@thinkpenguin:~/dev/codecombat$ nano docker-compose.yml
svetlana@thinkpenguin:~/dev/codecombat$ dockerd
-bash: dockerd: команда не найдена
svetlana@thinkpenguin:~/dev/codecombat$ file /usr/sbin/dockerd
/usr/sbin/dockerd: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, Go BuildID=l7l_2-AJiaVMlxe4ebrD/wg3WWnG19oMIzVYORZoP/siPVMHrZeAk2Hwitcu6t/ODibfeb7zn9PvIFSCqDV, BuildID[sha1]=16b2bc5541fce90c342efc2df352756f2b04ed7a, stripped
svetlana@thinkpenguin:~/dev/codecombat$ sudo dockerd
[sudo] пароль для svetlana:
Error starting daemon: pid file found, ensure docker is not running or delete /var/run/docker.pid
svetlana@thinkpenguin:~/dev/codecombat$ ps aux | grep docker
root      1882  0.2  0.5 1296024 81896 ?       Ssl  08:03   0:29 /usr/sbin/dockerd -H fd://
root      1903  0.4  0.2 1321248 33560 ?
Reading package lists...
Building dependency tree...
Reading state information...
autoconf is already the newest version.
libgdbm-dev is already the newest version.
libffi-dev is already the newest version.
libyaml-dev is already the newest version.
libncurses5-dev is already the newest version.
libreadline-dev is already the newest version.
The following extra packages will be installed:
  libbison-dev libcurl3 libcurl4-openssl-dev libssl1.0.0 zlib1g
Suggested packages:
  bison-doc gettext-base git-daemon-run git-daemon-sysvinit git-doc git-el
  git-email git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn
  libcurl4-doc libcurl3-dbg libidn11-dev libldap2-dev librtmp-dev
  libssh2-1-dev
Recommended packages:
  less rsync libssl-doc
The following NEW packages will be installed:
  bison build-essential libbison-dev
The following packages will be upgraded:
  curl git libcurl3 libcurl4-openssl-dev libssl-dev libssl1.0.0 zlib1g
  zlib1g-dev
8 upgraded, 3 newly installed, 0 to remove and 92 not upgraded.
Need to get 7852 kB of archives.
After this operation, 2766 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian/ jessie/main libbison-dev amd64 2:3.0.2.dfsg-2 [426 kB]
Get:2 http://security.debian.org/debian-security/ jessie/updates/main zlib1g-dev amd64 1:1.2.8.dfsg-2+deb8u1 [206 kB]
Get:3 http://deb.debian.org/debian/ jessie/main bison amd64 2:3.0.2.dfsg-2 [765 kB]
Get:4 http://deb.debian.org/debian/ jessie/main build-essential amd64 11.7 [7114 B]
Get:5 http://security.debian.org/debian-security/ jessie/updates/main zlib1g amd64 1:1.2.8.dfsg-2+deb8u1 [88.3 kB]
Get:6 http://security.debian.org/debian-security/ jessie/updates/main libssl-dev amd64 1.0.1t-1+deb8u12 [1284 kB]
Get:7 http://security.debian.org/debian-security/ jessie/updates/main libssl1.0.0 amd64 1.0.1t-1+deb8u12 [1049 kB]
Get:8 http://security.debian.org/debian-security/ jessie/updates/main libcurl4-openssl-dev amd64 7.38.0-4+deb8u16 [338 kB]
Get:9 http://security.debian.org/debian-security/ jessie/updates/main curl amd64 7.38.0-4+deb8u16 [202 kB]
Get:10 http://security.debian.org/debian-security/ jessie/updates/main libcurl3 amd64 7.38.0-4+deb8u16 [261 kB]
Get:11 http://security.debian.org/debian-security/ jessie/updates/main git amd64 1:2.1.4-2.1+deb8u10 [3227 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 7852 kB in 3s (2462 kB/s)
(Reading database ... 21694 files and directories currently installed.)
Preparing to unpack .../zlib1g-dev_1%3a1.2.8.dfsg-2+deb8u1_amd64.deb ...
Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+deb8u1) over (1:1.2.8.dfsg-2+b1) ...
Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2+deb8u1_amd64.deb ...
Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2+deb8u1) over (1:1.2.8.dfsg-2+b1) ...
Setting up zlib1g:amd64 (1:1.2.8.dfsg-2+deb8u1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 21692 files and directories currently installed.)
Preparing to unpack .../libssl-dev_1.0.1t-1+deb8u12_amd64.deb ...
Unpacking libssl-dev:amd64 (1.0.1t-1+deb8u12) over (1.0.1t-1+deb8u11) ...
Preparing to unpack .../libssl1.0.0_1.0.1t-1+deb8u12_amd64.deb ...
Unpacking libssl1.0.0:amd64 (1.0.1t-1+deb8u12) over (1.0.1t-1+deb8u11) ...
Preparing to unpack .../libcurl4-openssl-dev_7.38.0-4+deb8u16_amd64.deb ...
Unpacking libcurl4-openssl-dev:amd64 (7.38.0-4+deb8u16) over (7.38.0-4+deb8u14) ...
Preparing to unpack .../curl_7.38.0-4+deb8u16_amd64.deb ...
Unpacking curl (7.38.0-4+deb8u16) over (7.38.0-4+deb8u14) ...
Preparing to unpack .../libcurl3_7.38.0-4+deb8u16_amd64.deb ...
Unpacking libcurl3:amd64 (7.38.0-4+deb8u16) over (7.38.0-4+deb8u14) ...
Selecting previously unselected package libbison-dev:amd64.
Preparing to unpack .../libbison-dev_2%3a3.0.2.dfsg-2_amd64.deb ...
Unpacking libbison-dev:amd64 (2:3.0.2.dfsg-2) ...
Selecting previously unselected package bison.
Preparing to unpack .../bison_2%3a3.0.2.dfsg-2_amd64.deb ...
Unpacking bison (2:3.0.2.dfsg-2) ...
Selecting previously unselected package build-essential.
Preparing to unpack .../build-essential_11.7_amd64.deb ...
Unpacking build-essential (11.7) ...
Preparing to unpack .../git_1%3a2.1.4-2.1+deb8u10_amd64.deb ...
Unpacking git (1:2.1.4-2.1+deb8u10) over (1:2.1.4-2.1+deb8u7) ...
Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+deb8u1) ...
Setting up libssl1.0.0:amd64 (1.0.1t-1+deb8u12) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Setting up libssl-dev:amd64 (1.0.1t-1+deb8u12) ...
Setting up libcurl3:amd64 (7.38.0-4+deb8u16) ...
Setting up libcurl4-openssl-dev:amd64 (7.38.0-4+deb8u16) ...
Setting up curl (7.38.0-4+deb8u16) ...
Setting up libbison-dev:amd64 (2:3.0.2.dfsg-2) ...
Setting up bison (2:3.0.2.dfsg-2) ...
update-alternatives: using /usr/bin/bison.yacc to provide /usr/bin/yacc (yacc) in auto mode
Setting up build-essential (11.7) ...
Setting up git (1:2.1.4-2.1+deb8u10) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Installing rbenv with git...
Initialized empty Git repository in /root/.rbenv/.git/
Updating origin
From https://github.com/rbenv/rbenv
 * [new branch]      master     -> origin/master
 * [new tag]         v0.1.0     -> v0.1.0
 * [new tag]         v0.1.1     -> v0.1.1
 * [new tag]         v0.1.2     -> v0.1.2
 * [new tag]         v0.2.0     -> v0.2.0
 * [new tag]         v0.2.1     -> v0.2.1
 * [new tag]         v0.3.0     -> v0.3.0
 * [new tag]         v0.4.0     -> v0.4.0
 * [new tag]         v1.0.0     -> v1.0.0
 * [new tag]         v1.1.0     -> v1.1.0
 * [new tag]         v1.1.1     -> v1.1.1
 * [new tag]         v1.1.2     -> v1.1.2
Already on 'master'
Branch master set up to track remote branch master from origin.
make: Entering directory '/root/.rbenv/src'
gcc -fPIC     -c -o realpath.o realpath.c
gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib  -o ../libexec/rbenv-realpath.dylib realpath.o
make: Leaving directory '/root/.rbenv/src'

Installing ruby-build with git...
Cloning into '/root/.rbenv/plugins/ruby-build'...

All done!
Note that this installer does NOT edit your shell configuration files:
1. You'll want to ensure that `~/.rbenv/bin' is added to PATH.
2. Run `rbenv init' to view instructions on how to configure rbenv for your shell.
3. Launch a new terminal window after editing shell configuration files.
4. (Optional) Run the doctor command to verify the installation:
   wget -q "https://github.com/rbenv/rbenv-installer/raw/HEAD/bin/rbenv-doctor" -O- | bash

Removing intermediate container 223247842d6c
 ---> ffc3fe543f36
Step 7/9 : RUN rbenv install ${RUBY_VERSION} &&     rbenv global ${RUBY_VERSION}
 ---> Running in 0cc58cff5cc9
Downloading ruby-2.6.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.6/ruby-2.6.1.tar.bz2
Installing ruby-2.6.1...
Installed ruby-2.6.1 to /root/.rbenv/versions/2.6.1

Removing intermediate container 0cc58cff5cc9
 ---> 1eac68a2c5c9
Step 8/9 : RUN mkdir $NPM_GLOBAL_PREFIX &&     npm config set prefix $NPM_GLOBAL_PREFIX --global
 ---> Running in 126498e10976
Removing intermediate container 126498e10976
 ---> 3b482efdec3b
Step 9/9 : COPY . .
 ---> ff3a5fbd4ef3
Successfully built ff3a5fbd4ef3
Successfully tagged codecombat_proxy:latest
WARNING: Image for service proxy was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating codecombat_proxy_1 ... done
Attaching to codecombat_proxy_1
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>install /coco/node_modules/uws
proxy_1  | > node-gyp rebuild > build_log.txt 2>&1 || exit 0
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>install /coco/node_modules/node-sass
proxy_1  | > node scripts/install.js
proxy_1  |
proxy_1  | Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.1/linux-x64-57_binding.node
proxy_1  | Download complete
proxy_1  | Binary saved to /coco/node_modules/node-sass/vendor/linux-x64-57/binding.node
proxy_1  | Caching binary to /root/.npm/node-sass/4.13.1/linux-x64-57_binding.node
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/@babel/polyfill/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/babel-polyfill/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/babel-runtime/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/karma/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/node-sass
proxy_1  | > node scripts/build.js
proxy_1  |
proxy_1  | Binary found at /coco/node_modules/node-sass/vendor/linux-x64-57/binding.node
proxy_1  | Testing binary
proxy_1  | Binary is fine
proxy_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@babel/cli/node_modules/fsevents):
proxy_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
proxy_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack/node_modules/fsevents):
proxy_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
proxy_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
proxy_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
proxy_1  |
proxy_1  | added 1955 packages from 1431 contributors and audited 2025 packages in 56.106s
proxy_1  | found 1279 vulnerabilities (633 low, 46 moderate, 584 high, 16 critical)
proxy_1  |   run `npm audit fix` to fix them, or `npm audit` for details
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>proxy /coco
proxy_1  | > COCO_PROXY='true' nodemon
proxy_1  |
proxy_1  | 10 Jul 01:11:39 - [nodemon] v1.6.1
proxy_1  | 10 Jul 01:11:39 - [nodemon] reading config /coco/nodemon.json
proxy_1  | 10 Jul 01:11:39 - [nodemon] to restart at any time, enter `rs`
proxy_1  | 10 Jul 01:11:39 - [nodemon] ignoring: /coco/.git/**/* /coco/node_modules/**/* bower_components .sass-cache
proxy_1  | 10 Jul 01:11:39 - [nodemon] watching: server_config.js server_setup.coffee /coco/app/schemas/**/* ./server app/assets/main.html
proxy_1  | 10 Jul 01:11:39 - [nodemon] watching extensions: js,coffee
proxy_1  | 10 Jul 01:11:39 - [nodemon] starting `node index.js`
proxy_1  | 10 Jul 01:11:39 - [nodemon] child pid: 610
proxy_1  | 10 Jul 01:11:39 - [nodemon] watching 177 files
proxy_1  | Using dev proxy server
proxy_1  | fs.js:948
proxy_1  |   binding.stat(pathModule._makeLong(path));
proxy_1  |           ^
proxy_1  |
proxy_1  | Error: ENOENT: no such file or directory, stat '/coco/public/images/favicon/favicon.ico'
proxy_1  |     at Object.fs.statSync (fs.js:948:11)
proxy_1  |     at resolveSync (/coco/node_modules/serve-favicon/index.js:187:17)
proxy_1  |     at favicon (/coco/node_modules/serve-favicon/index.js:61:12)
proxy_1  |     at setupExpressMiddleware (/coco/server_setup.coffee:86:11)
proxy_1  |     at Object.exports.setupMiddleware (/coco/server_setup.coffee:201:3)
proxy_1  |     at module.exports.createAndConfigureApp (/coco/server.coffee:26:15)
proxy_1  |     at Object.module.exports.startServer (/coco/server.coffee:14:9)
proxy_1  |     at Object.<anonymous> (/coco/index.js:12:8)
proxy_1  |     at Module._compile (module.js:653:30)
proxy_1  |     at Object.Module._extensions..js (module.js:664:10)
proxy_1  |     at Module.load (module.js:566:32)
proxy_1  |     at tryModuleLoad (module.js:506:12)
proxy_1  |     at Function.Module._load (module.js:498:3)
proxy_1  |     at Function.Module.runMain (module.js:694:10)
proxy_1  |     at startup (bootstrap_node.js:204:16)
proxy_1  |     at bootstrap_node.js:625:3
proxy_1  |
proxy_1  | 10 Jul 01:11:40 - [nodemon] app crashed - waiting for file changes before starting...

Hi, devs, first of all, thanks for the possibility to run CodeCombat locally.
But why don't you fix the Docker image for such a long time?
As far as I understand images and containers are supposed to run on any kind of environment and return exactly the same result. That's the whole idea behind it.
You got lot's of questions and issues regarding failing containers for quite a long time, but nothing is fixed.
Could you please take a look?
Thank you in advance!

Hi, have you tried to use the docker image on debian, @ashliakhov ? It is everyone's, if you reproduce the problem, maybe it would 1) help others see it is not an issue on my pc and 2) we would have two our heads trying to fix it rather than one mine. Thanks

I confirm the issue on Manjaro. Definitely a lot of things fail while building so it looks like assets are not generated properly and http://localhost:7777 shows precisely nothing. If, as suggested in the discussion of another issue on this tracker, I copy the favicon.ico by hand, the failure is still there.
I attached below the log of docker-compose up --build command. My hunch is, some (most?) dependencies are not installed, leading to the whole thing's spectacular failure.
coco-build_up.log

svetlana@thinkpenguin:~$ cd dev
svetlana@thinkpenguin:~/dev$ cd codecombat/
svetlana@thinkpenguin:~/dev/codecombat$ docker-co
docker-compose          docker-containerd-ctr
docker-containerd       docker-containerd-shim
svetlana@thinkpenguin:~/dev/codecombat$ docker-compose up
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?

If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
svetlana@thinkpenguin:~/dev/codecombat$ nano docker-compose.yml
svetlana@thinkpenguin:~/dev/codecombat$ dockerd
-bash: dockerd: команда не найдена
svetlana@thinkpenguin:~/dev/codecombat$ file /usr/sbin/dockerd
/usr/sbin/dockerd: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, Go BuildID=l7l_2-AJiaVMlxe4ebrD/wg3WWnG19oMIzVYORZoP/siPVMHrZeAk2Hwitcu6t/ODibfeb7zn9PvIFSCqDV, BuildID[sha1]=16b2bc5541fce90c342efc2df352756f2b04ed7a, stripped
svetlana@thinkpenguin:~/dev/codecombat$ sudo dockerd
[sudo] пароль для svetlana:
Error starting daemon: pid file found, ensure docker is not running or delete /var/run/docker.pid
svetlana@thinkpenguin:~/dev/codecombat$ ps aux | grep docker
root      1882  0.2  0.5 1296024 81896 ?       Ssl  08:03   0:29 /usr/sbin/dockerd -H fd://
root      1903  0.4  0.2 1321248 33560 ?
Reading package lists...
Building dependency tree...
Reading state information...
autoconf is already the newest version.
libgdbm-dev is already the newest version.
libffi-dev is already the newest version.
libyaml-dev is already the newest version.
libncurses5-dev is already the newest version.
libreadline-dev is already the newest version.
The following extra packages will be installed:
  libbison-dev libcurl3 libcurl4-openssl-dev libssl1.0.0 zlib1g
Suggested packages:
  bison-doc gettext-base git-daemon-run git-daemon-sysvinit git-doc git-el
  git-email git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn
  libcurl4-doc libcurl3-dbg libidn11-dev libldap2-dev librtmp-dev
  libssh2-1-dev
Recommended packages:
  less rsync libssl-doc
The following NEW packages will be installed:
  bison build-essential libbison-dev
The following packages will be upgraded:
  curl git libcurl3 libcurl4-openssl-dev libssl-dev libssl1.0.0 zlib1g
  zlib1g-dev
8 upgraded, 3 newly installed, 0 to remove and 92 not upgraded.
Need to get 7852 kB of archives.
After this operation, 2766 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian/ jessie/main libbison-dev amd64 2:3.0.2.dfsg-2 [426 kB]
Get:2 http://security.debian.org/debian-security/ jessie/updates/main zlib1g-dev amd64 1:1.2.8.dfsg-2+deb8u1 [206 kB]
Get:3 http://deb.debian.org/debian/ jessie/main bison amd64 2:3.0.2.dfsg-2 [765 kB]
Get:4 http://deb.debian.org/debian/ jessie/main build-essential amd64 11.7 [7114 B]
Get:5 http://security.debian.org/debian-security/ jessie/updates/main zlib1g amd64 1:1.2.8.dfsg-2+deb8u1 [88.3 kB]
Get:6 http://security.debian.org/debian-security/ jessie/updates/main libssl-dev amd64 1.0.1t-1+deb8u12 [1284 kB]
Get:7 http://security.debian.org/debian-security/ jessie/updates/main libssl1.0.0 amd64 1.0.1t-1+deb8u12 [1049 kB]
Get:8 http://security.debian.org/debian-security/ jessie/updates/main libcurl4-openssl-dev amd64 7.38.0-4+deb8u16 [338 kB]
Get:9 http://security.debian.org/debian-security/ jessie/updates/main curl amd64 7.38.0-4+deb8u16 [202 kB]
Get:10 http://security.debian.org/debian-security/ jessie/updates/main libcurl3 amd64 7.38.0-4+deb8u16 [261 kB]
Get:11 http://security.debian.org/debian-security/ jessie/updates/main git amd64 1:2.1.4-2.1+deb8u10 [3227 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 7852 kB in 3s (2462 kB/s)
(Reading database ... 21694 files and directories currently installed.)
Preparing to unpack .../zlib1g-dev_1%3a1.2.8.dfsg-2+deb8u1_amd64.deb ...
Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+deb8u1) over (1:1.2.8.dfsg-2+b1) ...
Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2+deb8u1_amd64.deb ...
Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2+deb8u1) over (1:1.2.8.dfsg-2+b1) ...
Setting up zlib1g:amd64 (1:1.2.8.dfsg-2+deb8u1) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
(Reading database ... 21692 files and directories currently installed.)
Preparing to unpack .../libssl-dev_1.0.1t-1+deb8u12_amd64.deb ...
Unpacking libssl-dev:amd64 (1.0.1t-1+deb8u12) over (1.0.1t-1+deb8u11) ...
Preparing to unpack .../libssl1.0.0_1.0.1t-1+deb8u12_amd64.deb ...
Unpacking libssl1.0.0:amd64 (1.0.1t-1+deb8u12) over (1.0.1t-1+deb8u11) ...
Preparing to unpack .../libcurl4-openssl-dev_7.38.0-4+deb8u16_amd64.deb ...
Unpacking libcurl4-openssl-dev:amd64 (7.38.0-4+deb8u16) over (7.38.0-4+deb8u14) ...
Preparing to unpack .../curl_7.38.0-4+deb8u16_amd64.deb ...
Unpacking curl (7.38.0-4+deb8u16) over (7.38.0-4+deb8u14) ...
Preparing to unpack .../libcurl3_7.38.0-4+deb8u16_amd64.deb ...
Unpacking libcurl3:amd64 (7.38.0-4+deb8u16) over (7.38.0-4+deb8u14) ...
Selecting previously unselected package libbison-dev:amd64.
Preparing to unpack .../libbison-dev_2%3a3.0.2.dfsg-2_amd64.deb ...
Unpacking libbison-dev:amd64 (2:3.0.2.dfsg-2) ...
Selecting previously unselected package bison.
Preparing to unpack .../bison_2%3a3.0.2.dfsg-2_amd64.deb ...
Unpacking bison (2:3.0.2.dfsg-2) ...
Selecting previously unselected package build-essential.
Preparing to unpack .../build-essential_11.7_amd64.deb ...
Unpacking build-essential (11.7) ...
Preparing to unpack .../git_1%3a2.1.4-2.1+deb8u10_amd64.deb ...
Unpacking git (1:2.1.4-2.1+deb8u10) over (1:2.1.4-2.1+deb8u7) ...
Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+deb8u1) ...
Setting up libssl1.0.0:amd64 (1.0.1t-1+deb8u12) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Setting up libssl-dev:amd64 (1.0.1t-1+deb8u12) ...
Setting up libcurl3:amd64 (7.38.0-4+deb8u16) ...
Setting up libcurl4-openssl-dev:amd64 (7.38.0-4+deb8u16) ...
Setting up curl (7.38.0-4+deb8u16) ...
Setting up libbison-dev:amd64 (2:3.0.2.dfsg-2) ...
Setting up bison (2:3.0.2.dfsg-2) ...
update-alternatives: using /usr/bin/bison.yacc to provide /usr/bin/yacc (yacc) in auto mode
Setting up build-essential (11.7) ...
Setting up git (1:2.1.4-2.1+deb8u10) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Installing rbenv with git...
Initialized empty Git repository in /root/.rbenv/.git/
Updating origin
From https://github.com/rbenv/rbenv
 * [new branch]      master     -> origin/master
 * [new tag]         v0.1.0     -> v0.1.0
 * [new tag]         v0.1.1     -> v0.1.1
 * [new tag]         v0.1.2     -> v0.1.2
 * [new tag]         v0.2.0     -> v0.2.0
 * [new tag]         v0.2.1     -> v0.2.1
 * [new tag]         v0.3.0     -> v0.3.0
 * [new tag]         v0.4.0     -> v0.4.0
 * [new tag]         v1.0.0     -> v1.0.0
 * [new tag]         v1.1.0     -> v1.1.0
 * [new tag]         v1.1.1     -> v1.1.1
 * [new tag]         v1.1.2     -> v1.1.2
Already on 'master'
Branch master set up to track remote branch master from origin.
make: Entering directory '/root/.rbenv/src'
gcc -fPIC     -c -o realpath.o realpath.c
gcc -shared -Wl,-soname,../libexec/rbenv-realpath.dylib  -o ../libexec/rbenv-realpath.dylib realpath.o
make: Leaving directory '/root/.rbenv/src'

Installing ruby-build with git...
Cloning into '/root/.rbenv/plugins/ruby-build'...

All done!
Note that this installer does NOT edit your shell configuration files:
1. You'll want to ensure that `~/.rbenv/bin' is added to PATH.
2. Run `rbenv init' to view instructions on how to configure rbenv for your shell.
3. Launch a new terminal window after editing shell configuration files.
4. (Optional) Run the doctor command to verify the installation:
   wget -q "https://github.com/rbenv/rbenv-installer/raw/HEAD/bin/rbenv-doctor" -O- | bash

Removing intermediate container 223247842d6c
 ---> ffc3fe543f36
Step 7/9 : RUN rbenv install ${RUBY_VERSION} &&     rbenv global ${RUBY_VERSION}
 ---> Running in 0cc58cff5cc9
Downloading ruby-2.6.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.6/ruby-2.6.1.tar.bz2
Installing ruby-2.6.1...
Installed ruby-2.6.1 to /root/.rbenv/versions/2.6.1

Removing intermediate container 0cc58cff5cc9
 ---> 1eac68a2c5c9
Step 8/9 : RUN mkdir $NPM_GLOBAL_PREFIX &&     npm config set prefix $NPM_GLOBAL_PREFIX --global
 ---> Running in 126498e10976
Removing intermediate container 126498e10976
 ---> 3b482efdec3b
Step 9/9 : COPY . .
 ---> ff3a5fbd4ef3
Successfully built ff3a5fbd4ef3
Successfully tagged codecombat_proxy:latest
WARNING: Image for service proxy was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating codecombat_proxy_1 ... done
Attaching to codecombat_proxy_1
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>install /coco/node_modules/uws
proxy_1  | > node-gyp rebuild > build_log.txt 2>&1 || exit 0
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>install /coco/node_modules/node-sass
proxy_1  | > node scripts/install.js
proxy_1  |
proxy_1  | Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.1/linux-x64-57_binding.node
proxy_1  | Download complete
proxy_1  | Binary saved to /coco/node_modules/node-sass/vendor/linux-x64-57/binding.node
proxy_1  | Caching binary to /root/.npm/node-sass/4.13.1/linux-x64-57_binding.node
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/@babel/polyfill/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/babel-polyfill/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/babel-runtime/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/karma/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/core-js
proxy_1  | > node -e "try{require('./postinstall')}catch(e){}"
proxy_1  |
proxy_1  | Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
proxy_1  |
proxy_1  | The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
proxy_1  | > https://opencollective.com/core-js
proxy_1  | > https://www.patreon.com/zloirock
proxy_1  |
proxy_1  | Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
proxy_1  |
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>postinstall /coco/node_modules/node-sass
proxy_1  | > node scripts/build.js
proxy_1  |
proxy_1  | Binary found at /coco/node_modules/node-sass/vendor/linux-x64-57/binding.node
proxy_1  | Testing binary
proxy_1  | Binary is fine
proxy_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@babel/cli/node_modules/fsevents):
proxy_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
proxy_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack/node_modules/fsevents):
proxy_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
proxy_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
proxy_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
proxy_1  |
proxy_1  | added 1955 packages from 1431 contributors and audited 2025 packages in 56.106s
proxy_1  | found 1279 vulnerabilities (633 low, 46 moderate, 584 high, 16 critical)
proxy_1  |   run `npm audit fix` to fix them, or `npm audit` for details
proxy_1  |
proxy_1  | ><EMAIL_ADDRESS>proxy /coco
proxy_1  | > COCO_PROXY='true' nodemon
proxy_1  |
proxy_1  | 10 Jul 01:11:39 - [nodemon] v1.6.1
proxy_1  | 10 Jul 01:11:39 - [nodemon] reading config /coco/nodemon.json
proxy_1  | 10 Jul 01:11:39 - [nodemon] to restart at any time, enter `rs`
proxy_1  | 10 Jul 01:11:39 - [nodemon] ignoring: /coco/.git/**/* /coco/node_modules/**/* bower_components .sass-cache
proxy_1  | 10 Jul 01:11:39 - [nodemon] watching: server_config.js server_setup.coffee /coco/app/schemas/**/* ./server app/assets/main.html
proxy_1  | 10 Jul 01:11:39 - [nodemon] watching extensions: js,coffee
proxy_1  | 10 Jul 01:11:39 - [nodemon] starting `node index.js`
proxy_1  | 10 Jul 01:11:39 - [nodemon] child pid: 610
proxy_1  | 10 Jul 01:11:39 - [nodemon] watching 177 files
proxy_1  | Using dev proxy server
proxy_1  | fs.js:948
proxy_1  |   binding.stat(pathModule._makeLong(path));
proxy_1  |           ^
proxy_1  |
proxy_1  | Error: ENOENT: no such file or directory, stat '/coco/public/images/favicon/favicon.ico'
proxy_1  |     at Object.fs.statSync (fs.js:948:11)
proxy_1  |     at resolveSync (/coco/node_modules/serve-favicon/index.js:187:17)
proxy_1  |     at favicon (/coco/node_modules/serve-favicon/index.js:61:12)
proxy_1  |     at setupExpressMiddleware (/coco/server_setup.coffee:86:11)
proxy_1  |     at Object.exports.setupMiddleware (/coco/server_setup.coffee:201:3)
proxy_1  |     at module.exports.createAndConfigureApp (/coco/server.coffee:26:15)
proxy_1  |     at Object.module.exports.startServer (/coco/server.coffee:14:9)
proxy_1  |     at Object.<anonymous> (/coco/index.js:12:8)
proxy_1  |     at Module._compile (module.js:653:30)
proxy_1  |     at Object.Module._extensions..js (module.js:664:10)
proxy_1  |     at Module.load (module.js:566:32)
proxy_1  |     at tryModuleLoad (module.js:506:12)
proxy_1  |     at Function.Module._load (module.js:498:3)
proxy_1  |     at Function.Module.runMain (module.js:694:10)
proxy_1  |     at startup (bootstrap_node.js:204:16)
proxy_1  |     at bootstrap_node.js:625:3
proxy_1  |
proxy_1  | 10 Jul 01:11:40 - [nodemon] app crashed - waiting for file changes before starting...

Same issue on Ubuntu 20.04.

Had this problem, tried to fix it, but I can't login to sign the CLA. Edit the start command in docker-compose.yml like this:
command: bash -c "npm install && npm install bower && npm run proxy" OR command: bash -c "npm install && npm run build && npm run proxy"

Hey !
Same problem here on a Debian 11 after few modifications :

add "--force-yes" in the Dockerfile apt-get install to have it execute
Update version of node and ruby since they were too old and the install crashes
Now, got to the same error with the following logs (same with both "npm install bower" or "npm run build" in the docker-compose.yml) :
in the docker-compose logs :

proxy_1  | [nodemon] 2.0.19
proxy_1  | [nodemon] reading config ./nodemon.json
proxy_1  | [nodemon] to restart at any time, enter `rs`
proxy_1  | [nodemon] or send SIGHUP to 95 to restart
proxy_1  | [nodemon] watching path(s): server_config.js server_setup.coffee app/schemas/**/* server app/assets/main.html
proxy_1  | [nodemon] watching extensions: js,coffee
proxy_1  | [nodemon] starting `node index.js`
proxy_1  | [nodemon] forking
proxy_1  | [nodemon] child pid: 108
proxy_1  | [nodemon] watching 180 files
proxy_1  | Using dev proxy server
proxy_1  | Error. Couldn't find /coco/public_coco/images/favicon/favicon-coco. It is likely that the public_coco folder is not built. Try:
proxy_1  |
proxy_1  |   npm run build
proxy_1  |
proxy_1  | for an initial build, or
proxy_1  |
proxy_1  |   npm run dev
proxy_1  |
proxy_1  | for live rebuilding of your front-end changes. If those don't work, make sure you are running the correct version of node and have installed all dependencies with:
proxy_1  |
proxy_1  |   npm install --also=dev
proxy_1  |
proxy_1  | [nodemon] app crashed - waiting for file changes before starting...

a "npm run build" finish without any problem

a "npm run start" gives de following error

verbose stack Error<EMAIL_ADDRESS>start: `node ./index.js`
verbose stack Exit status 1
verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
verbose stack     at EventEmitter.emit (events.js:400:28)
verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycleb/spawn.js:55:14)
verbose stack     at ChildProcess.emit (events.js:400:28)
verbose stack     at maybeClose (internal/child_process.js:1088:16)
verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:296:5)
verbose pkgid<EMAIL_ADDRESS>verbose cwd /coco
verbose Linux 5.10.0-19-cloud-amd64
verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start"
verbose node v14.21.2
verbose npm  v6.14.17
error code ELIFECYCLE
error errno 1
error<EMAIL_ADDRESS>start: `node ./index.js`
error Exit status 1
error Failed at the<EMAIL_ADDRESS>start script.
error This is probably not a problem with npm. There is likely additional logging output above.
verbose exit [ 1, true ]


zigbee driver crashes: notifying bugsnag: startup failed : [Error connecting to gateway dial tcp <IP_ADDRESS>:2541: connection refused]

Here's the log entries:
[2015-05-14 21:03:18.382] [INFO] sphere-director driver-go-zigbee - 2015/05/14 21:03:18 notifying bugsnag: [Gateway EOF]: Error reading socket %!s(MISSING)
[2015-05-14 21:03:18.609] [INFO] sphere-director Director - Module driver-go-zigbee was terminated unexpectedly. pid: 11107
[2015-05-14 21:03:18.628] [INFO] sphere-director Director - Module driver-go-zigbee has died 3 times. Delaying restart by  0 ms
[2015-05-14 21:03:18.693] [INFO] sphere-director Director - Starting driver-go-zigbee Attempt 4 since it was first started 6 days, 20 hours, 58 seconds, 934 milliseconds ago
[2015-05-14 21:03:18.752] [INFO] sphere-director Director - Starting driver-go-zigbee version 0.1.6 from path /opt/ninjablocks/drivers/driver-go-zigbee
[2015-05-14 21:03:18.756] [INFO] sphere-director Director - Maximum memory for driver-go-zigbee is 20mb

4 times in nearly a week is actually less than I'd expect! The failed socket read from the gateway means that the gateway service has likely crashed (and not our code). Apart from seeing if there is a new version from TI there isn't much to be done from this side.

How much of the Zigbee stuff is under NDA?
I'm happy to go look and check for a new version but not sure if I'll be able to.

Everything outside this go library is under NDA unfortunately :/


[MO-ADK] Adding support for MO-ADK

[x] MO-ADK

Finished development of MOADK feature in commit [4ada460b], merged into dev & pkg.


Revert of method changes leaves the change in the next changes browser

If you open the Changes Browser, and revert all the method changes, and close and reopen the Changes Browser... all the changed methods are still present in the list.
If I were using this feature to prune out changes I didn't want to commit and I had a boatload of methods (this is exactly my use case when I do work on the bug system), I would really be annoyed at not being able to get the reverted methods off of the list of changes.
See below.  I made two changes, then reverted them.  This is the reopened changes browser.

I believe this was related to #742 and should be fixed in 3.1.0.


fix broken cli

To fix issue https://github.com/heartexlabs/label-studio/issues/173
required is not a valid argument for add_subparsers

Thanks for the PR @zehengl, merging in.


Added OpenID bindings for iOS and Android

Hello! I'm the build bot for the Mono project. I need approval from a Mono team member to build this pull request. A team member should reply with "approve" to approve a build of this pull request, "whitelist" to whitelist this and all future pull requests from this contributor, or "build" to explicitly request a build, even if one has already been done. Contributors can ignore this message.

whitelist

build


Add Example Images

it looks like image does not work

it looks like image does not work

It won't until its merged into main


[BUG]: react-markdown's remark plugins throws type error

Describe the bug
When import ReactMarkdown from "react-markdown" used with remark-gfm plugin, it throws the following error
assignable to type 'Pluggable<any[], Settings>'.
  Type 'Gfm' is not assignable to type 'Plugin<any[], Settings>'.
    The 'this' types of each signature are incompatible.
      Property 'attachers' is missing in type 'Processor<Settings>' but required in type 'Processor<void, Node<Data>, void, void>'.

To fix this we can use @ts-expect-error
Other related issues: https://github.com/orgs/rehypejs/discussions/63
Steps To Reproduce
build packages using react-markdown
Build packages
npm run bootstrap -- --scope @refinedev/chakra-ui --scope @refinedev/antd  --scope @refinedev/mui --scope @refinedev/mantine

Expected behavior
Should not give type error
Screenshot
No response
Desktop
No response
Mobile
No response
Additional Context
No response

Related https://github.com/remarkjs/react-markdown/issues/627


Camera2D limits don't clamp camera position

Godot version
3.5rc4
System information
windows
Issue description
Camera2D limits don't clamp camera position
Steps to reproduce
Add a 2D scene with a Camera2D, set limits.
move camera to reach the limits.
you can go further but position still increases.
This leads to the effect that camera is kinda sticked to the corner: you scroll back but it doesn't scroll.
It seems clamping camera position fixes it, but this should be default behavior imo.
Minimal reproduction project
camera_limits.zip
in the project camera limits work as I expect, but if you comment lines with clamp
pos.x = clamp(pos.x, limit_left, limit_right)
pos.y = clamp(pos.y, limit_top, limit_bottom)

, you will see the issue

var pos = position-event.relative*zoom
var x = zoom.x*viewport_size.x/2
var y = zoom.y*viewport_size.y/2
pos.x = clamp(pos.x, limit_left+x, limit_right-x)
pos.y = clamp(pos.y, limit_top+y, limit_bottom-y)

this is better

Related to https://github.com/godotengine/godot/issues/56336.

https://github.com/godotengine/godot-proposals/issues/1640 is for offset tho

Camera2D limits don't clamp camera position

This is correct. Camera2D's limits don't clamp the camera's position. Camera2D's limits set the limits of camera's boundaries i.e. the edges of the camera (not the camera's position). The Camera2D's boundaries won't go beyond the limits.
Note: If, as in your example, the difference between the limit_left and limit_right is less than the camera display's width or the difference between the limit_top and limit_bottom is less that the camera display's height (See Project Settings display/window/size/width and display/window/size/height), then the camera's boundaries must exceed these limits effectively leading to undefined behaviour, which is why it appears to stick to one corner. It cannot squeeze between the limits; so it does the best it can: it puts the camera's top-right corner in the top-right corner of the limits.

The question is why not clamp

This is how it's designed. You define the boundary area of your game using the camera limits. The camera is free to show anything within those limits, but won't show anything beyond those limits.

Why can't the camera just stop when it reaches the boundary and don't change the position anymore.
Really interesting why this is designed this way and when this would be useful instead of just clamping the position

As an end user I just want the camera to work right.
But I'm facing it and I need to create the code to manually clamp the position.
Everyone will do this, because this "sticking" feels wrong.
If this is really needed to be designed this way, could there be an option like "also clamp the position!"

Why can't the camera just stop when it reaches the boundary and don't change the position anymore.

That's exactly what is does.

As an end user I just want the camera to work right.
But I'm facing it and I need to create the code to manually clamp the position.
Everyone will do this, because this "sticking" feels wrong.
If this is really needed to be designed this way, could there be an option like "also clamp the position!"

The limits are designed to constrain the camera display area. The problem with the example you've provided is that the camera limits are smaller than the camera display area.
This is not a bug. It's how it's how camera limits have been designed, and they work for most users. If you have a question about how camera limits work, please use one of the other forums where you question can be better answered: https://godotengine.org/community

This is done so that you can, for example, position the camera anywhere in the game e.g. the start of your next level, and then change the camera limits from surrounding the current level to surrounding your new level. With smoothing_enabled and limit_smoothed both set to true, the camera will then gently scroll from the end of the current level to the start of the next level.

If I may add a possible solution for @me2beats
if(dragging):
    nextCameraPositon.x = clamp(self.position.x + (mouseInitPos.x - get_global_mouse_position().x) * delta * dragSpeed * self.zoom.x, left_limit, right_limit)
    nextCameraPositon.y = clamp(self.position.y + (mouseInitPos.y - get_global_mouse_position().y) * delta * dragSpeed * self.zoom.y, top_limit, bottom_limit)
    self.position = nextCameraPositon

This piece inside the _process function clamps the position of the camera inside 4 numbers set as top, bottom, left and right limits. As it works every frame it does not affect the visuals

I agree with me2beats that there should be an option to clamp the position by default. I just spent several hours trying to figure out why there was a delay when panning my camera from one edge of the screen to the other, only to find out that the camera's real position was completely outside the limits...
Or at least it be clearer in the docs... there's the line "Camera2D node's position doesn't represent the actual position of the screen, which may differ due to applied smoothing or limits", and maybe this is a me problem but I didn't realize this was my problem even after reading it because I had no idea what "position of the screen" was supposed to mean, let alone that what it's trying to say is "what the camera is actually showing you"?


bump Istio 1.11.1 -> 1.11.2

to be consistent with other changes in kyma

https://github.com/kyma-project/kyma/pull/12112
https://github.com/kyma-project/test-infra/pull/4151
https://github.com/kyma-project/kyma/pull/12120

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


Updated version number to reflect release

Updated ENVIRO_VERSION to reflect the current release version (to avoid not-inconsiderable confusion when people upgrade and then tell me they're on 0.0.10... :laughing: )

Oh dear- do I need to issue a patch release for this? 👀

Hmm, not sure, but if you release it as v0.2.1, don't forget to re-bump the version number or we'll be stuck in a loop!

A good rule of thumb is to never re-use released version numbers (no silently replacing published binaries), so when accidents like this happens, it is best to bump the version number again :slightly_smiling_face:


[FEATURE] Disable grave in spawn protected / claimed area (OPAC)

Is your feature request related to a problem? Please describe.
In my server, i do alot of cleanup of graves in areas i dont want them to spawn, mainly land claimed with Open Parties And Claims.
Describe the feature you would like to see.
I'd like a feature to disable the grave feature (just drop items) if the grave would have spawned in a claimed area.
Describe any alternatives you've considered.
I've considered alternatives such as just not spawning graves there, but i don't want players to lose their items.
Additional context
N/A

Thanks for taking the time to make this suggestion. I'll have to think about this some and see if I can't come up with a solution (code-wise, I like the idea of simply dropping the items in claimed areas). I'm afraid I don't have an ETA for when it'll get done but it's definitely something I'd like to add.

I've looked into this more and have found something that kinda works. Inside of openpartiesandclaims-server.toml (found within your server's config folder) there is an option called forcedBlockProtectionExceptionList. If you set the option to the following it allows players to break/use graves inside claimed chunks:
forcedBlockProtectionExceptionList = ["minecraft:crafting_table", "anything$forgottengraves:grave*", "break$forgottengraves:grave*"]

Another thing you can do, if the server is a PvP one, is enable disableInPvP within this grave mod's config so that items drop when a player is killed by another player (instead of creating a grave).
I know this isn't ideal, graves will still spawn, but I've taken a couple looks at the OPAC codebase briefly and haven't been able to wrap my head around how I'd integrate it yet.


irssi: oldversion -> newversion

This enables SASL authentication1.

Please change the commit subject to irssi: oldversion -> newversion, per the contribution guidelines.

Sorry, I was being unclear: I mean to substitute oldversion and newversion for the actual versions.

The idea is to have a fixed pattern to make it easier to quickly see what the commit is doing/make it easier to mine the commit log.

Ha, of course -- that makes sense.  Can you point me to the corresponding part of the contribution guidelines?  Are there guidelines re: the PR comment?

See https://nixos.org/nixpkgs/manual/#chap-submitting-changes. I recommend reading over that entire chapter, really, lots of good stuff in there. If you still have questions, do not hesitate to ask.

Would you please update the commit subject as well? Updating the PR subject doesn't affect the commit object. Apart from that this looks good to me, will merge once the formalities are in order.

:+1:

Thank you


Auto - Purchaser

This updates #48 by @russeli to apply on the latest master

The buyUpgrade function should be edited to following to support purchasing elements in future:
var buyUpgrade = function(id) {
	if(id >= 3 && 6 >= id) { //If upgrade is element damage
		g_Minigame.CurrentScene().TryUpgrade(document.getElementById('upgr_' + id).childElements()[3]);
	} else {
		g_Minigame.CurrentScene().TryUpgrade(document.getElementById('upgr_' + id).childElements()[0].childElements()[1]);
	}
}

I won't bother forking this just to make the update. :)

I'm not familiar with Greasemonkey or Tampermonkey, but if it does update the script automatically without notifying or asking the user for confirmation, the initial value of avgClicksPerSecond
should be set to 1(?) before merging, so that the impact on the users is minimized.
For example the script might start upgrading click damage, even though the user doesn't click at all.

GM / TM checks in various intervals to see if it can update the script. If it does, the user has to refresh the minigame for the changes to take effect.
— Jesse Bryan
On Sat, Jun 13, 2015 at 5:12 PM, russeli<EMAIL_ADDRESS>wrote:

I'm not familiar with Greasemonkey or Tampermonkey, but if it does update the script automatically without notifying or asking the user for confirmation, the initial value of avgClicksPerSecond
should be set to 1(?) before merging, so that the impact on the users is minimized.
For example the script might start upgrading click damage, even though the user doesn't click at all.
Reply to this email directly or view it on GitHub:
https://github.com/mouseas/steamSummerMinigame/pull/74#issuecomment-111755689

I've been running this all day. It works fine. Have you implemented the tier four upgrades though?

No implementing was required, it works based on the upgrade type.

:+1: I was surprised and delighted to find that I already had a few levels of AFK Equipment purchased.
--
It's a small matter, but when respawning it looked like the script purchased shields a few times due to health being 0, until the respawn kicked in.  My thought is setting a flag so that only one shield purchase happens per respawn.

The same probably happens at any point when health is lower than 30%. So let's say flag is raised when hp hits below 30%. When do you reset the flag? You could reset it when you press respawn, but how about in cases where hp is lower than 30% but greater than 0.
Other solution could be checking a flag wether we have died and only buying armor in that case. Though then the armor would get upgraded less frequently adding more load to medics etc.
PS. I pushed one fix

The reddit guide mentions that buying armor automatically fills HP, so that shouldn't be an issue.

I now added Lucky Shot to calculations, according to some sources autoattacks don't crit so I left their calculations untouched.


Initial Backup Utility

@immuta/devops
Creates ruby gem and binary wrapper for backing up Github repositories
for an organization. It takes in a github_api_token, org, location
from either the CLI or a configuration file and backs up the repos
on disk. If the repos already exist subsequent runs will just fetch
the changes/updates. Creates mirror repositories so they could be
restored quite easily with all commit history and branches intact.
Still needs quite a bit of documentation, probably some additional
logging, a readme, and a no-op functionality so testing can be
written against it. Also needs RPM build support directory with spec
file so Jenkins can be used to build RPMs for it, but wanted to commit
the code first.

:+1:


Callbacks not firing

I'm logging in the console some text when these methods get fired, but they are not going off. I am signed in and subscribed correctly. I have also set the callback correctly. None of the callbacks are firing correctly. Could this be an issue with the singleton pattern?
public MeteorHelper(Context context) {
    mMeteor = new Meteor(context, context.getString(R.string.url_server));
    mMeteor.setCallback(this);
    mContext = context;
}

public static synchronized MeteorHelper getInstance(Context context) {
    if (mInstance == null) {
        mInstance = new MeteorHelper(context);
    }
    return mInstance;
}

@Override
public void onDataAdded(String collectionName, String documentID, String newValuesJson) {
    Log.v(TAG, "(onDataAdded) collection: " + collectionName + " documentId: " + documentID + " payload: " + newValuesJson);
}

@Override
public void onDataChanged(String collectionName, String documentID, String updatedValuesJson, String removedValuesJson) {
    Log.v(TAG, "(onDataChanged) collection: " + collectionName + " documentId: " + documentID + " payload: " + updatedValuesJson);
}

@Override
public void onDataRemoved(String collectionName, String documentID) {
    Log.v(TAG, "(onDataRemoved) collection: " + collectionName + " documentId: " + documentID);
}

Instead they are just going to my log like so:
06-12 16:19:39.146    6960-6960/com.walintukai.watchdog.debug I/System.out﹕ RECEIVE: {"msg":"added","collection":"assets","id":"cZCMZabRbPmEt3gk5","fields":{"name":"House 1","desc":{"country":"USA","city":"Emeryville","postal":"942828","street":"Christie Ave","year":2004}}}
06-12 16:19:39.146    6960-6960/com.walintukai.watchdog.debug I/System.out﹕ RECEIVE: {"msg":"ready","subs":["fff1d350-5270-490e-87dc-1f6b783e6ab1"]}

Sorry for the late reply!
We've checked your use case and code and it should work without any problems, actually.
The log statements that you saw was because this library had internal logging enabled by default. This has been fixed in https://github.com/delight-im/Android-DDP/commit/db19049f26e2440decab0e93ea83acf0569725f2 so that you won't see these statements anymore -- unless you explicitly enable this library's internal logging.
Could it be that you didn't see your Log.v(...) results due to a wrong filter set in your debugger/console?
Regarding the singleton pattern in general, you should change the constructor's visibility from public MeteorHelper(...) to private MeteorHelper(...) -- but this is not really that important, of course.
To save you from having to implement the singleton yourself, we've added a recommended singleton implementation in the MeteorSingleton class in https://github.com/delight-im/Android-DDP/commit/65a0b034e8de9aa9fbe3089eaac7742a1c818a36.
Please get one of the latest JARs and check the "Singleton access" section in the documentation.
Does that help?


Fix video currentTime after scrolling away from video

On web, when you scroll away from a video an IntersectionObserver is used to play() and pause() the video. As described in  #6035 the currentTime of the video is lost after scrolling away. It appears conditional rendering in the following code is causing this:
https://github.com/bluesky-social/social-app/blob/6bc5a05f4bdfd3bf9dea400b3a6b5d9ac356457a/src/view/com/util/post-embeds/VideoEmbed.web.tsx#L145-L159
I've traced these changes back to two prior PRs for context:

https://github.com/bluesky-social/social-app/pull/5246
https://github.com/bluesky-social/social-app/pull/5251

I didn't experience any issues playing a fullscreen video and the currentTime of the video was retained as expected.

This was very much intentional, to ensure that the number of video players doesn't grow indefinitely as you scroll. I'd be open to a solution that caches/restores the play position but still unmounts the player when scrolling away

Thanks for the feedback. Can you share a little more about the resources you are concerned about consuming? I imagine a paused video should also pause the hls stream and once a user leaves a feed the video element should also be destroyed.
Since a video is unmounted each time you scroll past it, the current experience leads to multiple http requests being fired each time the video is remounted. I feel like this is an a more common performance concern as opposed to what may happen if a user loads thousands of videos and they are all paused.
For example, just now on my following feed, which has already been loaded, I scrolled past like 80 posts. On the way down I re-downloaded 8MB, I then scrolled back up and re-downloaded another 8MB.


Value of field sftpPrivateKeyPath must be a readable file

I've followed the instructions but I can't get the sftp.key file to be read. Is there a step that I'm missing?

I solved it!


add test for ContractClassAbiEntryWithType from ontractClassAbiEntry

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

Current dependencies on/for this PR:

main

PR #766

PR #767   👈

PR #763
PR #762

This comment was auto-generated by Graphite.


Improve support for word representations

It would be great to be able to load pretrained word representations, at least the ones from Glove[1] and word2vec [2].
In the same fashion it would be useful to have a most_similar method able to efficiently retrieve the top n similar words.
[1] http://nlp.stanford.edu/projects/glove/
[2] https://code.google.com/p/word2vec/

spacy.tokens.Token.repvec loads pretrained word representation.
I agree that it would be very useful to be able to efficiently retrieve similar words...

On Wednesday, May 6, 2015, mfilipov<EMAIL_ADDRESS>wrote:

spacy.tokens.Token.repvec loads pretrained word representation.

This should have a better API -- currently you need to precompile the word
vectors.

I agree that it would be very useful to be able to efficiently retrieve
similar words...

This is an open research problem. Consider that there are (n^2-n)/2
combinations, with n of order 10^6 for our vocab.
The folks over at gensim are thinking about this too. I'm on my phone rigt
now, but when I get a chance I'll link their discussion.

—
Reply to this email directly or view it on GitHub
https://github.com/honnibal/spaCy/issues/58#issuecomment-99421133.

I don't know how Matthew generated the built-in embedding vectors, but to me the quality is okay.
But if you're not happy with it and want to use your own embeddings, there's spacy.vocab.write_binary_vectors you can use, it takes bzip2 format file as input and set the output to .../spacy/en/data/vocab/vec.bin. I've never done it and just read from the code, so I might be wrong.
Also remember, spaCy expecting 300 as the size of each vector as it's hardcoded here and here.
For most_similar function, that's easy to implement, but I'd rather do it somewhere outside spaCy.  You can also use gensim to load spaCy vectors!
import spacy.en
from gensim.models.word2vec import Word2Vec, Vocab

nlu = spacy.en.English()
vectors = np.asarray(map(lambda x: x.repvec, nlu.vocab))
model = Word2Vec(size=vectors.shape[1])

for i, lex in enumerate(nlu.vocab):
    model.vocab[lex.orth_] = Vocab(index=i, count=None)
    model.index2word.append(lex.orth_)

model.syn0norm = vectors

loaded to model.syn0norm because spaCy vectors are already normalised and to avoid gensim L2-normalisation for all-zeros vectors.
In [249]: model.most_similar(u'space')
Out[249]:
[(u'Space', 1.0),
 (u'SPACE', 1.0),
 (u'SPACES', 0.7741692662239075),
 (u'spaces', 0.7741692662239075),
 (u'Spaces', 0.7741692662239075),
 (u'workspace', 0.6425580978393555),
 (u'hyperspace', 0.578804612159729),
 (u'CYBERSPACE', 0.5667369961738586),
 (u'cyberspace', 0.5667369961738586),
 (u'Cyberspace', 0.5667369961738586)]

But if you just want most_similar function, read doc on how compute vector similarity or  you can do something like this...
import numpy as np
import spacy.en

nlu = spacy.en.English()
vectors = np.asarray(map(lambda x: x.repvec, nlu.vocab))
vocab = map(lambda x: x.orth_, nlu.vocab)

def most_similar(word, topn=5):
    if isinstance(word, str):
        word = unicode(word)
    dists = np.dot(vectors, nlu.vocab[word].repvec)
    return map(lambda x: (vocab[x], dists[x]), np.argsort(dists)[::-1][:topn])

Example:
In [189]: most_similar(u'query')
Out[189]:
[(u'query', 0.99999994),
 (u'Query', 0.99999994),
 (u'queries', 0.74670404),
 (u'keystroke', 0.65798581),
 (u'signup', 0.62638754)]

Extra
Maybe you want to know the similar words from the same sentence. That's also easy, you can have a function like this..
def most_similar_in_sentence(tokens, word, pos_tags=[], topn=5):
    if isinstance(word, str):
        word = unicode(word)
    if pos_tags:
        vocab = filter(lambda x: x.pos_ in pos_tags, tokens)
    else:
        vocab = tokens
    dists = np.dot(np.asarray(map(lambda x: x.repvec, vocab)), nlu.vocab[word].repvec)
    return map(lambda x: (vocab[x].orth_, dists[x]), np.argsort(dists)[::-1][:topn])

Example
In [199]: text = u"""One solution is to stick a cache in front of the query system. We could probably serve a majority of similarity queries from a small cache."""

In [200]: tokens = nlu(text)

In [201]: most_similar_in_sentence(tokens, u'query')
Out[201]:
[(u'query', 0.99999994),
 (u'queries', 0.74670404),
 (u'cache', 0.49115649),
 (u'cache', 0.49115646),
 (u'solution', 0.36885005)]

Maybe you want to filter based on POS tag.
In [202]: most_similar_in_sentence(tokens, u'query', pos_tags=['VERB'])
Out[202]:
[(u'stick', 0.29887787),
 (u'could', 0.23798984),
 (u'is', 0.2375059),
 (u'serve', 0.23126227)]

In [203]: most_similar_in_sentence(tokens, u'query', pos_tags=['NOUN', 'VERB', 'ADJ', 'NUM'], topn=10)
Out[203]:
[(u'query', 0.99999994),
 (u'queries', 0.74670416),
 (u'cache', 0.49115649),
 (u'cache', 0.49115646),
 (u'solution', 0.36885005),
 (u'system', 0.32158077),
 (u'stick', 0.29887787),
 (u'similarity', 0.29796919),
 (u'One', 0.24750805),
 (u'could', 0.23798984)]

Hope that helps!

The vectors are taken from here: https://levyomer.wordpress.com/2014/04/25/dependency-based-word-embeddings/
These embeddings were computed from dependencies, using a parser that's very similar to SpaCy's (the Goldberg and Nivre (2012) model. SpaCy uses some updates on this model, most importantly Brown cluster features.)
The dependency-based embeddings seem substantially better to me. At least, they agree more closely with my expectations for what sort of regularities these vectors should be capturing.
Once I get around to generating embeddings myself, I'd like to have a set of vectors keyed by (lemma, POS tag) tuples, instead of the current string-keyed vectors, which rely on somewhat arbitrary text pre-processing. I'd also like to do named entity linking, and have vectors in the same space for entities.
This stuff is in the roadmap, but somewhere behind constituency parsing, and the named entity plans.

See additional documentaton here: http://spacy.io/tutorials/load-new-word-vectors/

@honnibal : Can you share the code snippet to load Omer Levy's dep embedding


vectormath.transpose is wrong

vectormath.transpose(v) should give a 1xN whose column entries are the components of the vector. Instead, it's creating a Nx1 matrix, but reporting its size as 1xN.

Fixed by 1ad842d97c1061fab4b7c9fab6b4a5bc4681d701


Add additional CRIU create image tests

related: runtimes/backlog/issues/1037
https://github.com/adoptium/aqa-tests/pull/4406

@AdamBrousseau could you review this PR? Thanks


error about 'android:keyboardNavigationCluster' after upgrade to v3.4.2

I'm just going to put this here, in case someone else runs into the same problem. After upgrading to v3.4.2, all of a sudden I started getting this error during run/build:
C:\workspace\epicuro-mobile\platforms\android\app\build\intermediates\res\merged\F0F1F2F3F4F5F6F7\debug\values-v26\values-v26.xml    :15:21-54: AAPT: No resource found that matches the given name: attr 'android:keyboardNavigationCluster'..
To fix this, add the following to your app.grade:
android {
  compileSdkVersion 26
  buildToolsVersion '26.0.2'
}

(there probably already is an android section that you can add the middle two lines to)

@Burgov thanks for reporting this. Just for the sake of completeness, do you know which plugins have the requirement for android:keyboardNavigationCluster?

@Pip3r4o here's the result of a grep action in my work folder:
$ grep -r "keyboardNavigationCluster"
Binary file platforms/android/app/build/intermediates/assets/F0F1F2F3F4F5F6F7/debug/metadata/treeStringsStream.dat matches
platforms/android/app/build/intermediates/incremental/mergeF0F1F2F3F4F5F6F7DebugResources/merged.dir/values-v26/values-v26.xml:        <item name="android:keyboardNavigationCluster">true</item>
platforms/android/app/build/intermediates/incremental/mergeF0F1F2F3F4F5F6F7DebugResources/merger.xml:        <item name="android:keyboardNavigationCluster">true</item>
platforms/android/app/build/intermediates/res/merged/F0F1F2F3F4F5F6F7/debug/layout-v26/abc_screen_toolbar.xml:        android:keyboardNavigationCluster="true"
platforms/android/app/build/intermediates/res/merged/F0F1F2F3F4F5F6F7/debug/values-v26/values-v26.xml:        <item name="android:keyboardNavigationCluster">true</item>
Binary file platforms/android/app/build/intermediates/transforms/dex/F0F1F2F3F4F5F6F7/debug/folders/1000/1f/main/classes.dex matches
Binary file platforms/android/app/metadata/output/assets/metadata/treeStringsStream.dat matches
Binary file platforms/android/app/src/main/assets/metadata/treeStringsStream.dat matches

it doesn't give me a conclusive answer, but maybe it means sth to you. If you need any other information, let me know.


New command: spo listitem roleassignment add

Usage
m365 spo listitem roleassignment add [options]
Description
adds a role assignment to a listitem.
Options

Option
Description

-u, --webUrl <webUrl>
URL of the site where the list is located

-i, --listId [listId]
ID of the list. Specify either listId, listTitle or listUrl.

-t, --listTitle [listTitle]
Title of the list. Specify either listId, listTitle or listUrl.

--listUrl [listUrl]
Relative URL of the list. Specify either listId, listTitle or listUrl.

--listItemId <listItemId>
Id of the listitem to assign the role to.

--principalId [principalId]
The SharePoint Id of the principal. It may be either a user id or group id to add a role assignment for. Specify either upn, groupName or principalId.

--upn [upn]
upn/email of user to assign role to. Specify either upn, groupName or principalId.

--groupName [groupName]
The group name of Azure AD or SharePoint group. Specify either upn, groupName or principalId.

--roleDefinitionId [roleDefinitionId]
ID of role definition. Specify either roleDefinitionId or roleDefinitionName but not both

--roleDefinitionName [roleDefinitionName]
The name of a role definition, like 'Contribute', 'Read', etc. Specify either roleDefinitionId or roleDefinitionName but not both

What about this one @Adam-it 😇

I may take this one 😋
there is still a lot of those we need to have and I guess I should spend some time and create issue for each one. We still are missing managing permissions on web level, we have for listitem reseting and breaking roleinheritance which will work for file and folder as well but we could create commands which will alias the listitem one.
We need commands which will allow to add and remove roles to roledefenitions and we need a add roledefenition command... etc etc. There Is still a lot of work here and I have it all somewhere in the back of my head next to a big pile of other OpenSource stuff I want to do 🙄😅.
but ok.. I will reprioritize and create all of those 👍.
@martinlingstuyl do you think you could take over some of my PRs 🙏 that would be really helpful to me as I could even start this weekend 😉

Haha, all in due time... though I think it would be helpful to create issues to get it out of your head. That way we can get the work done quicker. Would you mind taking some time to do that?
But of course: prioritize what you can do vs what needs to be done first.
I would take PR's off of your shoulders, but I can not really review them the coming two weeks. I'm fully back half august. I'll see what I can do in the meantime. No promises.

putting this on hold before we agree on some on the approach here
https://github.com/pnp/cli-microsoft365/issues/3540

@pnp/cli-for-microsoft-365-maintainers any additional comments here 🤔?
I suppose very similar to the one on the list level which I already implemented and is merges so this one should be quite solid (https://github.com/pnp/cli-microsoft365/issues/3300).
maybe we could open it up?

Not sure about the -i and -t shorts, as -i could be pointing to either the ID of the list or the list item. Other than that, it's good to go 💪

Updated the specs 👍

Updated the specs 👍

thanks @martinlingstuyl for updating the spec. I thought it's on me 😉. Lets open it up for others. I will try to catch up with what I currently have and if this still will be free I will take this one

ok I got my current work done. I may take this one


Add language-puppet to stackage

Everything seems to be in place for this to succeed with the latest snapshot (825da72)

https://github.com/fpco/stackage/pull/1578


Different FastDDS XML configuration files for the two sides of the domain bridge

Hello all
I have a specific case I need to solve, for which I need the two sides of the domain bridge to connect to different machines.
I'm using FastDDS whitelisting setup with an XML file following the documentation here.
My issue is that the two ROS2 nodes, for example gateway_0 and gateway_1 use the same XML file. I want to specify one file for gateway_0 and another for gateway_1, but am not sure how to proceed.
What I'm looking for to start on this issue is the code location where the nodes are created to understand more, and maybe at this location I can do something to switch from the two XML files.
Any help on the subject is appreciated!
Victor

I'm not familiar with how to specify a particular FastDDS XML file for one ROS node in a process. Specifically, I guess you'll want to somehow associate the XML file per ROS context (which has a one-to-one mapping with DDS participants).
Here is where ROS nodes are created:
https://github.com/ros2/domain_bridge/blob/main/src/domain_bridge/domain_bridge.cpp#L165
and the ROS context for that node is created just above that:
https://github.com/ros2/domain_bridge/blob/b5b296a6291a05384eeed10ca1779fc8220b2292/src/domain_bridge/domain_bridge.cpp#L161


[Feat]Touchable Text has accessible

Is your feature request related to a problem? Please describe.
Text with onPress prop should be accessible.
Describe the solution you'd like
Describe alternatives you've considered
Additional context

:tada: This issue has been resolved in version 1.8.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Why not use Expression.NotEqual in TagWith?

I noticed when using an IQueryable's .ToString() that the SQL generated by this method is
WHERE ... AND (N'!__tag!' = N'My Comment') ...

which defaults to being FALSE. Thus if I want to run that query I get from a ToString() I have to change = to <> before running the query.
I wonder if you'd consider using Expression.NotEqual instead? Seems like it'd be just as easy, and would make the where clause be more transparent for .ToString() and any other similar situations that might come up.

Hello,
First of all, thanks for your feedback :)
I'm going to study it. Definitely, we can not switch to "not equals" for everybody because it could be a breaking change for people that may be relying on the current generated SQL (for example, for unit testing). However, it could be a configuration setting in TaggingOptions or something like that.
I'm a bit busy now, but I'll take a look at it in the next few weeks.
Thanks!
PS: Of course, you are welcome to send a PR with this feature! 😉

Hi @d-a-s ,
I've just published the 1.3.0-preview1 NuGet package. With this version you can change the predicate used by default from the component initialization code:
TagWith.Initialize<SqlServerTagger>(
    new TaggingOptions() {
        PredicateExpression = PredicateExpression.NotEquals
    }
);

Please, take a look at this new version and check if everything works fine :)
Thanks!


[Enhancement] Delta Lake supports reading map and struct type

Fixes #issue

What type of PR is this:

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

Checklist:

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

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

Bugfix cherry-pick branch check:

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

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:disappointed: fail : 0 / 26 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/ColumnTypeConverter.java
0
26
00.00%
[474, 475, 477, 479, 481, 668, 669, 670, 672, 676, 678, 679, 681, 682, 683, 685, 689, 690, 691, 692, 693, 694, 695, 696, 698, 700]

[FE PR Coverage Check]
:heart_eyes: pass : 23 / 26 (88.46%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/ColumnTypeConverter.java
23
26
88.46%
[670, 683, 696]

@mergify backport branch-3.1


unable to load the json file and getting error for files size above 172 KB

I have a file with 172 KB(this is the smallest file as of now i tested with 123Kb its working fine).
While uploading i m getting below error in console.
😿 Something went wrong.
Check the JS console for more details.
Failed to load format Error: Samples must be provided in increasing order of cumulative value. Last sample was 87005, this sample was 87004
at h._enterFrame (speedscope.80eb88d2.js:165:7141)
at h.enterFrame (speedscope.80eb88d2.js:165:7512)
at speedscope.80eb88d2.js:171:1675
at a (speedscope.80eb88d2.js:171:1800)
at speedscope.80eb88d2.js:171:2361
at Array.map ()
at s (speedscope.80eb88d2.js:171:2354)
at import.7f8cb9f9.js:121:3665
at Generator.next ()
at s (import.7f8cb9f9.js:121:780)

Hi @vickymore2003! Can you provide more information about where these profiles are coming from? e.g. what language are you profiling, what profiler are you using, etc?
Speedscope certainly supports files larger than this (folks have successfully imported profiles larger than 1GB), and the error described in the stack trace you provided is about the content of the file, not the size of the file.


Filter environment variables passed to ProcessCapture to increase security

This is an idea how to reduce a security risk when running ORT, for which I would like to get some feedback:
Especially when running the Analyzer, external logic in build scripts is executed which could do potentially harmful thing. One attack vector could be reading sensitive information from environment variables, such as database credentials or credentials to other services provided to the ORT process.
At least when external processes are created via the ProcessCapture class, this risk could be mitigated by filtering the map with environment variables passed to the new process. Since the variables are specific to a concrete runtime environment, probably a configurable filter mechanism is required. For instance, users could define inclusion and/or exclusion filters in the ORT configuration file that are applied when constructing the environment. This would support use cases such as including only variables starting with a specific prefix (which are explicitly intended to be used by external tools) or removing variables with "postgres" in their name which are specific for the database.
This is of course not bullet-proof, but would be an improvement in this area.

The topic has been discussed in the ORT Community Meeting on 2022-10-20 with the following outcome:

There is general agreement that a solution addressing this issue would be useful.
The most secure solution - that should be followed here - is a whitelist approach. This means:

In the ORT configuration, users have to explicitly list the environment variables which should be passed through to external processes. All others are removed from the environment when starting an external process.
ORT provides a default for this setting that includes a minimum set of variables that are known to be required by the tools used, such as GRADLE_HOME, MAVEN_HOME, M2_REPO, etc.

For the beginning, a global whitelist is sufficient. Later on, tool-specific whitelists may be supported.

The approach of listing all allowed variables used by the various tools is hardly practicable. In a first (and incomplete) attempt to compile such a list, I came up with more than 300 variables. This list would also have to be maintained and adapted to changes in the supported tools. So, while this may be the most secure approach, I doubt that it is feasible.
Therefore, I would suggest an alternative approach: ORT could define some patterns for variables it excludes by default, e.g. ".PASS.", ".USER.", ".*_KEY". The user could then configure a list of variables that match a pattern, but should be nevertheless included.

This is a good idea. .*TOKEN.* too.


decreased dendritic spine number

If this is a request for a new term, please provide us with the following information.

Preferred term label (e.g., asplenia)

decreased dendrite branch number

Synonyms (e.g., absent spleen)

Textual definition (the definition should be understandable even for non-specialists. Include a PubMed ID or URL(s) to refer to any relevant article(s) that provides information about the suggested term).

reduction in the amount of spines on a given dendrite

Any additional notes to clarify the meaning or use of the term. Please provide a PubMed ID or URL(s) for the source of this information.

PMID: 8046469

Suggested parent term (Please look in the hierarchy of the MP using the MP Browser or other browsers such as OLS and find the place in the MP where the new term best fits)

abnormal dendritic spine morphology

If you would like a nanoattribution, please indicate your ORCID id or provide a label such as MGI:sbello (organization, first initial-last name)

https://orcid.org/0000-0003-2307-1226

Per GO:0140059,  dendrite arborization is defined as: "the process in which the anatomical structures of a dendritic tree are generated and organized into dendritic branches". In GO, dendrite arborization is a child of dendrite morphogenesis GO:0048813 (which is a Biological Process).
The MP generally places branching morphogenesis terms under a relevant development parent term in the morphology branch of the hierarchy. Hence, the majority of dendritic branching defects are currently annotated to abnormal dendrite morphology MP:0008143 (or child terms thereof) typically as a decreased number of dendrite branches.
We should create abnormal, increased as well as decreased dendritic branching terms under abnormal dendrite morphology MP:0008143 and review our annotations to see if we need more specific, child branching terms for Purkinje cell dendrites, motor neuron dendrites, retinal ganglion cell dendrites etc.

Should this be branch number rather than branching? That is are we looking at the arborization process or just the number of branches? A decrease in branch number could potentially be due to loss or abnormal pruning rather than impaired branching process.

How does this relate to the existing term "decreased dendritic spine density" (MP:0020508) definition is "decrease in the number of dendritic spines in a given cross-sectional area of a dendrite"

This may not be an applicable difference, but the spine density refers to the number of spines per certain amount of dendrite whereas the spine number refers to amount of spines as a whole on the dendrite.

I'll get this in on Monday and will make the density term a child.

Added
abnormal - MP:0021017
decreased - MP:0021018
increased - MP:0021019
Left density as a sibling to number terms. I think the logic for this on other terms was that you could have the same number of X but spread over a different area so that density was changed but number was not.
Note, we do not have logical definitions for the density terms. There does not appear to be a PATO term for this meaning of density. I suspect that if PATO added a term for density = count/amount per unit area that this would fall under the term amount.
There is a PATO ticket (https://github.com/pato-ontology/pato/issues/173) for cell density which is related but more specific but we never did resolve this. Probably worth revisiting on a uPheno call.


Format & fix typos

Should change no functionality.

Check and approved! Thanks for the efforts @innerlee


migrate to Android V2 embedding

The plugins android_path_provider use a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if these plugins support the Android V2 embedding. Otherwise, consider removing them since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.

I migrated the package
so if anyone wants to use it u can by putting this in pubspec.yaml
android_path_provider:     git:       url: git://github.com/zezo357/android_path_provider_v2
hope it helped and incase there is a problem I can fix just make an issue there I will try to fix it

@zezo357 can you create a PR for that migration?

@steven-spiel done

Thank you all. Pull requests have been merged and published to pub.dev.


HAP Warning Issue, Anyone Seen This, Know How To Fix ?

Seeing this issue recently after updating. Anyone have any ideas on what its referencing and how to fix:
'HAP Warning: Characteristic not in required or optional characteristics for service . Adding anyway.'
Thanks

I seem to have the same error. I had no issues configuring Homebridge and setting up the Home App. But this warning came up after I had grouped my accessories from within Home App and restarted Homebridge. After the restart, my Home App lost the grouping and I had to do that again. Maybe this is a related issue. Is anyone able to reproduce this issue?


fix a typoe

In UNIT4 : Pretrained models for audio classification
We’ll load an official Audio Spectrogram Transformer checkpoint fine-tuned on the Speech Commands dataset, under the namespace "MIT/ast-finetuned-speech-commands-v2":
Copied
classifier = pipeline(
"audio-classification", model="MIT/ast-finetuned-speech-commands-v2"
)
classifier(sample["audio"])
Fix it to be classifier(sample["audio"]["array"])
I don't know how to make a pull request yet! :)

@abdelkareemkobo Hmm, I think we may need to be careful here.  I just submitted a PR for a related fix.  I initially thought that the following two statements were equivalent but they are not

The above is for the minds-14 dataset, not Speech Commands but in this case classifier(sample["audio"]) produces the correct intent classification whereas adding the "array" index does not.  I'm currently not able to load the speech command dataset (it hangs when trying to stream the dataset in).  What is the difference in output when trying to classify these two different ways on the Speech Commands dataset?


change escape character

Hello,
Is there any way change the default escape character '\ 'into ''' ?
After my testing with oracle + database/sql + github.com/sijms/go-ora,
it seems that escape single quote with ' didn't work.
I used ReplaceAll instead to solve the current single quote issue I met.
Regards,
Steven

Thank you for the information,  I'll  add this feature.

Hi @dbaid   you can use sqlstring.SetSingleQuoteEscaper  to change the default escape character '
sqlstring.SetSingleQuoteEscaper("'")

sql := sqlstring.Format('.......',x,x)

Thank you. It works.
Best Regards,
dbaid

@dbaid  You should update  the version v0.3.0 and replace ' with ''
sqlstring.SetSingleQuoteEscaper("''")
sql := sqlstring.Format(".......",x,x)

@feiin
Thank you for your update.
Here is an example of my code.
sqlstring.SetSingleQuoteEscaper("''")
sqlstring.Escape(contact.Address.String)
It works. No worry!!
Regards,
dbaid


Files for all 4 team members

Closes #10: Wallet Connect: Web3Modal Theming Challenge
Closes #113: Go+: Super SAFU - GoPlus API Use

Resubmitting pull request for all 4 team members: Greg Schwartz, David Fung, Brittney Wong, Luis Miguel.
Closes https://github.com/SporkDAOOfficial/ETHDenver-2023/issues/10: Wallet Connect: Web3Modal Theming Challenge
Closes https://github.com/SporkDAOOfficial/ETHDenver-2023/issues/113: Go+: Super SAFU - GoPlus API Use


Route validation is overly aggressive

Hi,
Since updating to 1.9.5, our previously valid template now errors. I tracked it down to this commit: https://github.com/cloudtools/troposphere/commit/25c40f6c5b40dd5ecbef756475c63c949deb4c31
Our code looks a bit like this:
Route(
                    pri_route,
                    DestinationCidrBlock=EVERYWHERE,
                    RouteTableId=Ref(pri_route_table),
                    InstanceId=If(
                        USE_NAT_GATEWAY,
                        Ref('AWS::NoValue'),
                        Ref(NAT)
                    ),
                    NatGatewayId=If(
                        USE_NAT_GATEWAY,
                        Ref(NAT_GATEWAY),
                        Ref('AWS::NoValue')
                    )
                )

Because InstanceId and NatGatewayId are specified, validation fails despite the resulting template being otherwise valid (because of the ifs). I'm wondering if the correct thing to do is to roll back the validation?
/cc @tigertoes

This is a duplicate of #778, which was fixed in #780 (and is now in HEAD).

Aha, must have missed those. Thanks.