VirtualBox: mouse grabbing incorrectly (locking)

After launch an app via plank the mouse completely locks up to anything else except additional clicks to plank. After killing plank the mouse is then freed up again.  Same thing seems to happend with thunar and maybe other apps.

Tried switching to evdev driver over libinput but the same behavior occured with either driver.  Its possible its a virtual box issue.  I was seeing problems like this before with vbox.

Turns out this is a VirtualBox issue.  VMware Player works fine.  Looking into using KVM/QEMU instead.

KVM/QEMU does the same thing maybe VirtualBox is based of this tech, dunno

virtualbox 5.2.18 seems to have resolved the issue


Starts to implement updating availability.

In an effort to have smaller PRs, here is the javascript and jsp file changes that execute the preparation of data to send in a fetch request.

This is ready for re-review.

This is ready for re-review.


Update Alphabet.hx

Fix for errors where it would having troubles finding the frames from the images. I'm on a Mac (And thats most likely why there is an error)  but shouldn't cause troubles on other platforms

This can cause more issues, no.


docker daemon is not working on '1.13.0-rc1'

Description
Failed to start the docker daemon by docker daemon command.
Steps to reproduce the issue:

Create a 1.13-rc1 docker host on Digital Ocean via docker-machine command:

$ docker-machine create -d digitalocean \
    --engine-install-url "https://test.docker.com/" \
    --engine-storage-driver overlay2 \
    d1

ssh into the machine, and you will find you cannot run docker command

$ docker-machine ssh d1
Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-47-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

0 packages can be updated.
0 updates are security updates.

root@d1:~# docker info

^C
root@d1:~# docker --version
^C
root@d1:~#

Checking the running process
root@d1:~# ps -ef | grep docker
root       985     1  0 01:51 ?        00:00:00 /usr/bin/docker daemon -H tcp://<IP_ADDRESS>:2376 -H unix:///var/run/docker.sock --storage-driver overlay2 --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --tlskey /etc/docker/server-key.pem --label provider=digitalocean

You will find the /usr/bin/docker daemon is used (which is came from docker-machine template).
Then, check the systemd status
root@d1:~# systemctl status docker
● docker.service
   Loaded: loaded (/etc/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2016-11-14 01:51:14 UTC; 2min 49s ago
 Main PID: 985 (docker)
    Tasks: 4
   Memory: 14.1M
      CPU: 25ms
   CGroup: /system.slice/docker.service
           └─985 /usr/bin/docker daemon -H tcp://<IP_ADDRESS>:2376 -H unix:///var/run/docker.sock --storage-driver overlay2 --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pe

Nov 14 01:51:14 d1 systemd[1]: Started docker.service.
Nov 14 01:51:14 d1 docker[985]: Command "daemon" is deprecated, and will be removed in Docker 1.16. Please run `dockerd` directly.

There is no further information, which should have more docker daemon boot up info. It seems the docker daemon stuck there.
Edit the /etc/systemd/system/docker.service, replace the docker daemon with dockerd, then reboot the docker service
root@d1:~# systemctl daemon-reload
root@d1:~# systemctl restart docker
root@d1:~# systemctl status docker
● docker.service
   Loaded: loaded (/etc/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2016-11-14 01:58:23 UTC; 3s ago
 Main PID: 1731 (dockerd)
    Tasks: 16
   Memory: 51.4M
      CPU: 363ms
   CGroup: /system.slice/docker.service
           ├─1731 /usr/bin/dockerd -H tcp://<IP_ADDRESS>:2376 -H unix:///var/run/docker.sock --storage-driver overlay2 --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --t
           └─1737 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd -

Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.094362027Z" level=warning msg="Your kernel does not support cgroup rt runtime"
Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.095659953Z" level=info msg="Loading containers: start."
Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.135899718Z" level=info msg="Firewalld running: false"
Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.313196823Z" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to
Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.356318661Z" level=info msg="Loading containers: done."
Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.376632354Z" level=warning msg="failed to retrieve docker-init version: unknown output format"
Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.377394788Z" level=info msg="Daemon has completed initialization"
Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.377644240Z" level=info msg="Docker daemon" commit=75fd88b graphdriver=overlay2 version=1.13.0-rc1
Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.389155910Z" level=info msg="API listen on /var/run/docker.sock"
Nov 14 01:58:25 d1 dockerd[1731]: time="2016-11-14T01:58:25.389750526Z" level=info msg="API listen on [::]:2376"

This time, we can see the real boot log. And docker command can be used as well.
root@d1:~# docker --version
Docker version 1.13.0-rc1, build 75fd88b

I understand docker daemon is deprecated, but should work until 1.16.
Output of docker version:
Client:
 Version:      1.13.0-rc1
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   75fd88b
 Built:        Fri Nov 11 19:47:07 2016
 OS/Arch:      linux/amd64

Server:
 Version:             1.13.0-rc1
 API version:         1.25
 Minimum API version: 1.12
 Go version:          go1.7.3
 Git commit:          75fd88b
 Built:               Fri Nov 11 19:47:07 2016
 OS/Arch:             linux/amd64
 Experimental:        false

Output of docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.13.0-rc1
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8517738ba4b82aff5662c97ca4627e7e4d03b531
runc version: ac031b5bf1cc92239461125f4c1ffb760522bbf2
init version: N/A (expected: v0.13.0)
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-47-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 488.5 MiB
Name: d1
ID: M7VK:YNAL:VPTV:T5CX:CAS3:W7WX:WT6E:3PVE:GOBD:TQKT:MJLT:5K7C
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Labels:
 provider=digitalocean
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

@twang2218 I cannot reproduce :sweat: It works fine with docker daemon (it's deprecated — but still there until 1.16). /usr/bin/docker daemon actuallly runs dockerd (if you do a ps afx | grep docker you should see it).
I think docker daemon didn't start for another reason but not sure why… Do you still have access to your machine and the systemd logs ?

@vdemeester As I said in the debug section, ps -ef did show the /usr/bin/docker daemon process, however, the log of daemon doesn't seem right, it's not full booted, and the docker command was not working, either.
Yes, I still have the access of the machine, and the problem is repeatable. If I change it to dockerd, everything will be fine, and if I change it to docker daemon, then the problem appears. So, if you want anything, just let me know.
Here is the systemctl status
root@d1:~# systemctl status docker
● docker.service
   Loaded: loaded (/etc/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2016-11-14 16:08:53 UTC; 6min ago
 Main PID: 10431 (docker)
    Tasks: 3
   Memory: 189.9M
      CPU: 15ms
   CGroup: /system.slice/docker.service
           └─10431 /usr/bin/docker daemon -D -H tcp://<IP_ADDRESS>:2376 -H unix:///var/run/docker.sock --storage-driver overlay2 --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pe

Nov 14 16:08:53 d1 systemd[1]: Started docker.service.
Nov 14 16:08:53 d1 docker[10431]: Command "daemon" is deprecated, and will be removed in Docker 1.16. Please run `dockerd` directly.

Here is journalctl output:
root@d1:~# journalctl -u docker
-- Logs begin at Mon 2016-11-14 01:44:24 UTC, end at Mon 2016-11-14 16:15:59 UTC. --
...
-- Reboot --
Nov 14 16:08:53 d1 systemd[1]: Started docker.service.
Nov 14 16:08:53 d1 docker[10431]: Command "daemon" is deprecated, and will be removed in Docker 1.16. Please run `dockerd` directly.

This is the full log when using docker daemon, nothing else, even I enabled the debug option -D.
The Docker Machine version is 0.8.2, which is the part of Docker for Mac, 1.12.3 (13776):
$ docker-machine -v
docker-machine version 0.8.2, build e18a919

As you saw in the docker info section, the OS I choose on Digital Ocean is Ubuntu 16.04.1 LTS, and fully updated and 'dist-upgraded', the kernel version is 4.4.0-47-generic.
Here is the settings I used for docker-machine on creating host on Digital Ocean:
#!/bin/bash
export DOCKER_API_VERSION=1.24
export DIGITALOCEAN_IMAGE=ubuntu-16-04-x64
export DIGITALOCEAN_REGION=sfo2
export MACHINE_DRIVER=digitalocean

After source the variables, I just simply create the host by
docker-machine create --engine-install-url "https://test.docker.com/" --engine-storage-driver overlay2 d1

I can confirm that using docker daemon in a systemd unit file results in the service not starting. Possibly systemd thinks the command failed because the warning was printed. Manually running the command works

Just checked with @vdemeester and he confirmed it worked for him on DigitalOcean (Ubuntu), so we're a bit confused now :smile:

I double checked it on Vultr.com, I created a Ubuntu 16.04 host on Vultr via docker-machine with Vultr driver. It's repeatable, and not Digital Ocean only problem.
One thing I noticed this time, if I just created the host via docker-machine and SSH into the host, the docker daemon is booted up, everything is right, however, after I ps -ef | grep docker, I found it's dockerd rather than docker daemon, I double checked all the docker.service, they are all docker daemon. So, somehow, docker-machine use the dockerd for the first time.
So, I just reboot the system, to make sure it's using what stated in the docker.service, and this time, bug appears.

I tried without using docker-machine, on both Digital Ocean and Vultr, same result.
I created a clean Ubuntu 16.04.1 host, and after update and reboot, then I run the following command to install the docker
curl -fsSL https://test.docker.com/ | sh

After the installation, the docker is running, I can run docker info, and ps -ef | grep docker show me the dockerd process.
Then, I edit /etc/systemd/system/multi-user.target.wants/docker.service, change the dockerd to docker daemon.
Reload and restart the docker service:
systemctl daemon-reload
systemctl restart docker

The systemctl restart docker never returned, I waited for several minutes.
After Ctrl-C, or just logged in from another console, the bug appears.
# systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (start) since Mon 2016-11-14 17:27:05 UTC; 1min 48s ago
     Docs: https://docs.docker.com
 Main PID: 11507 (docker)
    Tasks: 3
   Memory: 6.2M
      CPU: 20ms
   CGroup: /system.slice/docker.service
           └─11507 /usr/bin/docker daemon -H fd://

Nov 14 17:27:05 d2 systemd[1]: Starting Docker Application Container Engine...
Nov 14 17:27:05 d2 docker[11507]: Command "daemon" is deprecated, and will be removed in Docker 1.

And all docker commands, even docker --version, are not responding.

I ran into this issue as well.  I'm going to fix machine to use dockerd for starters.

@nathanleclaire Can you check out #28501?

in my admittedly limited and probably flawed testing, seems to work 👍
a unit file with /usr/bin/docker daemon seems to result fine in a running dockerd instance without the hang issue ! thanks all.


Trait default method segfault

Hi!
Pony is an amazing project, it was love at first sight for me. Having tried so many other languages, I can tell you I am having a great deal of fun and satisfaction coding in Pony. Congratulations, please keep it up!
I have bumped into this problem trying to define a default trait method that returns a literal object. The example is overly-simplified and looks useless and dumb, but the intent is to provide a capability-adding method to the object adopting the trait. New capabilities are additive, so it makes sense that the new augmented object, in turn, implement the trait.
As an alternative solution, I have implemented a separate class that returns the object literal in its apply method.
I am wondering whether I am hitting some consistent limitation I am not aware of, or this might be a bug.
Thanks!

Code in question:
actor Main
  new create(env: Env) =>
    Foo[String box](env, "message")
    Foo[String box].double()(env, "message")

trait Printer[T: Stringable box]
  fun apply(env: Env, msg: T)

  fun double(): Printer[T] =>
    object ref is Printer[T]
      fun apply(env: Env, msg: T) =>
        env.out.print("First " + msg.string())
        env.out.print("Second " + msg.string())
    end

class Foo[T: Stringable box] is Printer[T]
  fun apply(env: Env, msg: T) =>
    env.out.print("Just one " + msg.string())

Here's the backtrace from a debug version of the compiler:
/home/sean/code/ponylang/ponyc/src/libponyc/pass/expr.c:661: pass_expr: Assertion `errors_get_count(options->check.errors) > 0` failed.

Backtrace:
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ponyint_assert_fail+0x96) [0x555555d2afb6]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(pass_expr+0x534) [0x555555c868e4]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x2a4) [0x555555c87224]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(+0x733ce6) [0x555555c87ce6]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(+0x7336aa) [0x555555c876aa]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_passes_type+0x114) [0x555555c879f4]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(+0x7bc485) [0x555555d10485]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(expr_object+0x1a15) [0x555555d0f905]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(pass_expr+0x422) [0x555555c867d2]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x2a4) [0x555555c87224]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_visit+0x1e4) [0x555555c87164]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(+0x733ce6) [0x555555c87ce6]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(+0x7336aa) [0x555555c876aa]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(ast_passes_program+0x22) [0x555555c872f2]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(program_load+0xb8) [0x555555ca9e58]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(+0x6d232c) [0x555555c2632c]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(main+0x261) [0x555555c261d1]
  /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7ffff7ca6d90]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7ffff7ca6e40]
  /home/sean/code/ponylang/ponyc/build/debug/ponyc(_start+0x25) [0x555555c25ea5]
Process 1091 stopped
* thread #1, name = 'ponyc', stop reason = signal SIGABRT

The AST item in question when we go boom appears to be a TK_DOT.
tk_dot ends up in entity_access which definitely returns false from some locations without setting an error.
Next step is additional debugging to figure out what is the unexpected bit and probably one of:

how we getting this far without having already displayed an error earlier
what was supposed to have been done earlier that wasn't
what's the unhandled case

in all likelihood, its the first in that list.

Changing to:
actor Main
  new create(env: Env) =>
    Foo[String box](env, "message")
    Foo[String box].double()(env, "message")

trait Printer[T: Stringable box]
  fun apply(env: Env, msg: T)

  fun double(): Printer[T] =>
   Foo[T]

class Foo[T: Stringable box] is Printer[T]
  fun apply(env: Env, msg: T) =>
    env.out.print("Just one " + msg.string())

fixes the issue, so, focus on the object literal when debugging.


Run on android

I want to run this program on Android in my phone is there any way?

This is unlikely. AI is very computationally intensive.
You can use online services, for example, the Premium version of the X-Minus or Google Colab notebook: https://colab.research.google.com/github/lucassantilli/UVR-Colab-GUI/blob/main/UVR_v5.ipynb


feat(AlgebraicTopology): homotopy in quasicategories

Defined a homotopy between two 1-simplicies in a quasicategories, and proved the property of being homotopic forms an equivalence relation.

[ ] depends on: #9935

Here are some general remarks:

Try to follow the mathlib coding style (which is not as strict as it used to be, but there are some guidelines https://leanprover-community.github.io/contribute/style.html and we try to have a certain uniformity in the code presentation).
As the notion of homotopy that we shall soon define for simplicial objects (or at least simplicial sets) shall be slightly different from this one, I believe that this file should be renamed AlgebraicTopology.QuasiCategory.Homotopy. As Quasicategory is defined as SSet.Quasicategory, I would think that whole file should be under the namespace SSet.Quasicategory instead of Quasicategory.
As simplicial sets are particular cases of simplicial objects, we can take advantage of the dot notation, so that (C.map (δ 2).op) τ can be rephrased as C.δ 2 τ, etc.
In the introduction of the file, try to include a reference paper/book where the mathematical notions appear, so that users of mathlib can get easier access to the mathematical background.
In general, we should not mark as awaiting-review PRs which depend on other PRs.


feat: site with mdbook

Overview
TODO

[x] set up mdbook with same file structure (i.e. /cips and /wgs move to /cips/wgs)
[x] custom handling for frontmatter in CIPs, use option 3 from here https://github.com/celestiaorg/CIPs/pull/170#issuecomment-2239814656
[x]  set up dns
[x]  test out on personal github pages https://cips.jcstein.dev
[x]  prep for plausible

[x]  add plausible script

[x]  favicon
[x]  prep site for dns

The previous PR got too messy and I'd like to try without moving the structure around. https://github.com/celestiaorg/CIPs/pull/168

https://jcstein.github.io/CIPs/index.html

Options for frontmatter:
1. change the styling to have backticks around it and display the code block

this also works on github

2. change the style of the frontmatter itself to be .md-friendly instead of github-flavored-markdown friendly. IMHO this looks worse

edge case for option 3 is that you can't see the whole table

but if it is a code block, you can

i'm actually not sure what's best here 😅
it's pretty janky to scroll through the code block

going with option 3

demo: https://cips.jcstein.dev/
diff for final touches: https://github.com/celestiaorg/CIPs/compare/jcs/add-site-v0...jcstein:CIPs:main
once this is approved, 2 things will need to happen before going live:

@sysrex to add DNS for cips.celestia.org for github pages deployment. this should just be adding a CNAME entry for "cips" since gh pages is already setup for the A records of celestia.org
@musalbas to begin collecting plausible analytics. it's already set up on the site's end https://github.com/celestiaorg/CIPs/blob/2bedecfa0fd9d0f11145859c0d633eeb429c9000/theme/head.hbs#L1

GFM style look very annoying to edit for CIP authors and look worse rendered to me. Why do you think it looks worse than option 2?

I think options 2 and 3 are equally as annoying to edit/author and neither is perfect. GFM just fits into the current style that is displayed on github

I don't follow how, as option 2 just requires the author to write bulletpoints whereas option 2 requires them to add a bunch of ------ ascii art and scroll right to see the whole text

I see, the table for option 2 is easier to edit. i will demo on this PR
| cip | 1 |
| - | - |
| title | Celestia Improvement Proposal Process and Guidelines |
| author | Yaz Khoury<EMAIL_ADDRESS>|
| status | Living |
| type | Meta |
| created | 2023-04-13 |

renders:

cip
1

title
Celestia Improvement Proposal Process and Guidelines

author
Yaz Khoury<EMAIL_ADDRESS>

status
Living

type
Meta

created
2023-04-13


Feature(ArrayDeclarationMutator), add new mutator.

This new mutator changes array declaration into empty arrays.

This proposal is an implementation of #227

Looks good!
array-mutator

Thanks!


Add client info to ENR

What was wrong?
Knowing which client and version of that client your node is failing to connect to is helpful for debugging issues on the portal network.
Getting a node's info via RPC is either cumbersome or impossible, depending on the node's settings.
How was it fixed?

A client string (e.g. trin v0.1.0) is added  to trin's ENR as a value under the key client.
If a portal node has a client key in its ENR, it is displayed in the output of the portal_*RoutingTableInfo RPC endpoint, like so:

{
  "client": "trin v0.1.0",
  "enr": "enr:-Je4QFui-99WVnY8Q4C3rR6iZokv_rK1d7Q4fUaWHEd6PEqPcPbVmSoaXOnHG-dFZd0L0v5GWIJXhz7XP3unaqBJv0YBhmNsaWVudIt0cmluIHYwLjEuMIJpZIJ2NIJpcIR_AAABiXNlY3AyNTZrMaEC64Hx6X6On6OQSGP-X5PaXZsCkEzUrimYclGbmwhFAXyDdWRwgiMq",
  "node_id": "0x0241dc8d483d628cbad18704e3a9b094642a07882d329c92e25fa5da4eb4155c",
  "radius": "18446744073709551615",
  "status": "Connected"
}

To-Do

[x] Add entry to the release notes (may forgo for trivial changes)
[x] Clean up commit history

It seems like we don't have consensus among the client teams yet to add this, so I'm going to hold off on review for now.

@jacobkaufmann Fair, I'll re-request review if/when we do.

Updated this to use shorthand notation within the ENR's key and value (as per @carver's suggestion): "c" for "client" and "t" for trin".

Eh, I'm okay moving forward with it before we have other clients fully convinced. I haven't really heard strenuous objection, and maybe we'll convince them otherwise after we can demonstrate the value by having trin share the info.

I don't think you needed to wait for another 👍🏻 but just in case you are... you have another from me.!


[python/gym] Add termination conditions and reward components toolboxes.

Currently, there is no toolbox with various pre-implemented toolboxes for termination conditions and reward components. It would be nice to provide some highly optimized yet modular implementations of the most common cases. Here is a template of what would be done for the reward:
from typing import Sequence, Tuple, Dict, Union, Callable
from abc import ABCMeta, abstractmethod

import numpy as np

class AbstractRewardCatalog(ABCMeta):
   def __init__(self, env: BaseJiminyEnv, reward_mixture: Dict[str, float]) -> None:
       self.env = env
       self.reward_mixture = {getattr(self, reward_component): weight}

   @abstractmethod
   def _initialize_buffers(self) -> None:
       pass

   @abstractmethod
   def _refresh_buffers(self) -> None:
       pass

   def compute_reward(self,
                      terminated: bool,
                      truncated: bool,
                      info: InfoType) -> float:
       reward_total = 0.0
       self._refresh_buffers()
       for reward_fun, weight in self.reward_mixture.items():
           reward_total += reward_fun(terminated, truncated, info)
       return reward_total

class WalkerRewardCatalog(AbstractRewardCatalog):
   def _initialize_buffers(self) -> None:
       self.foot_placements: Sequence[Tuple[np.ndarray, np.ndarray]] = ()

   def _refresh_buffers(self) -> None:
       pass

   def foot_placement(self,
                      terminated: bool,
                      truncated: bool,
                      info: InfoType) -> float:
       (left_foot_pos, _), (right_foot_pos, _) = self.foot_placements
       return np.linalg.norm(left_foot_pos - right_foot_pos)

After thinking twice, I think it makes more sense provide a QuantityManager that would be expose _initialize_buffers  and _refresh_buffers.  Then, its quantity manager can be passed to independent objects satisfying some callable protocole (which means it would be a lambda, a function or a class defining __class__ aka functor). It would more modular and easier to extend this way. To be computationally efficient, this quantity manager should heavily rely on caching. This cache must be clear manually before computing any reward component, then quantities would be computed only the first time it is requested, or never if not used. Here is a snipped:
class QuantityManager:
    def __init__(self, robot: BaseJiminyRobot, quantities: Dict[str, Callable[[], Any]]) -> None:
        self.robot = env.robot
        self.quantities = quantities
        self._cache : Dict[str, Any]

    def __getattr__(self, name: str) -> Any:
        return self.__cache.setdefault(name, self.quantities.get(name))

    def reset() -> None:
        self.__cache.clear()

class RelativePose:
    def __init__(self, robot: BaseJiminyRobot, first_name: str, second_name: str) -> None:
        first_index = robot.pinocchio_model.getFrameId(first_name)
        second_index = robot.pinocchio_model.getFrameId(second_name)
        self.first_pose = self.robot.oMf[first_index]
        self.second_pose = self.robot.oMf[second_index]

    def __call__(self) -> pin.SE3:
        return self.first_pose.actInv(self.second_pose)

[...]

foot_pose_rel_qty = RelativePose(env.robot, "LeftSole", "RightSole")
quantity_manager = QuantityManager(env.robot, {"foot_placement": foot_pose_rel_qty}))

This issue has been addressed. Closing.


Limit dropdown options based on activities available

Only show sledding & snowmobiling options if they exist at that location:

Currently this list of options is generated based on the user level. Its going to need to be reworked to handle being built from the activities available.


feat: password reset functionality

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


Feature/optimization

Took a quick look at the code and found some things we can optimize

Awesome, thanks @grzegorz-jakubiak


Remove BuildNetCoreApp condition and build .NET Core 2.0 libraries

When building locally, CodeDom seems fine.
I will give it a try and remove the preview.

Hmm, the AppVeyor may be related to the nuget version? Not sure for the Travis failure...

Yes, I think I need to edit the AppVeyor file to download a newer Nuget.exe
Also, one of the DLLs is x86, so it gives BadImageFormatException.
Not sure if/how I can invoke an x86 dotnet in the CI.
There is one more problem with TestReflectionServices which I am not sure about.
I will probably check this again during the weekend.

x86: I see, there are actually two PlatformTarget entries in Metadata.csproj, we should remove the x86 one and keep anycpu.

For TestReflectionServices: .NET Core has different assembly layouts than the full framework so that could be the issue. Another thing to try is adding FEATURE_METADATA_READER to netcoreapp2.0.props (since you fixed it to work with .NET Core anyway).

PlatformTarget x86 was the original one though. AnyCPU was added by mistake in https://github.com/IronLanguages/dlr/pull/36/files#diff-0101e7dd4da19af70160bb466410a2abR5
Perhaps x86 was used on purpose before.

I would still drop x86 and change it to anycpu (unless it's causing failures in net40 or net45).

Trying to use http://www.alteridem.net/2017/05/04/test-net-core-nunit-vs2017/
to run the other tests from command line gives an error about Microsoft.NET.Test.Sdk and net40.
I suspect either NuGet does not like this or there is an actual incompatibility.

Seems like the Travis build is not picking up on the .NET Core reference assembly?
Possible solutions:

Remove the reference to the assembly and see what sort of error it gives with the Mono csc. Maybe it'll give a clue as to how to resolve the issue.
Use the full path to the assembly.
Make a separate project file to generate the methodargs DLL.

I added some relative path references for the ClrAssembly build. Not sure if this is the best approach.


[Manual Merge Required] Backport 0febef8448f174b6c4ed7c012f28395d593f2ee2

Microsoft Reviewers: Open in CodeFlow

cc @palenshus

Installation failure did not repro locally


Bug

Here: https://books-dev.web.cern.ch/backoffice/documents?q=&p=1&s=10 I search 'exploring' to retrieve a document I've created, the search result is here: https://books-dev.web.cern.ch/backoffice/documents?q=exploring&sort=mostrecent&order=asc&p=1&s=10 and when I click on the record https://books-dev.web.cern.ch/backoffice/documents/0png2-mbk12 the page is fully blank
Browser used: firefox

https://books-dev.web.cern.ch/search?q=exploring&p=1&s=10
-> when I click on the document, I get this message:
UI Error
Something went wrong when rendering the component

Thank you for reporting this. The error is this.metadata.keywords is undefined, it looks like that the UI is not happy when there are no keyword. It is a bug.
We are going to fix this soon.

Fixed by: https://github.com/inveniosoftware/invenio-app-ils/pull/831

@agentilb the fix has been deployed and you should now be able to progress with your tests.
Be aware that we have some cache issues for the moment, you will have to hard refresh the browser the first time (if you see the new book covers from Syndetics is a good sign).


run executable should be able to invoke function with args

wasm3 allows you to supply a wasm file and invoke a specific function, supplying it with parameteres like so:
wasm3 [options] <file> [args...]
The run exe should do the same, and utilities should be provided to autoconvert string parameters into the proper Val types the wasm function expects, if possible.

closed by #13


I am wondering if "og:title" is SEO title

I am wondering if "og:title" is SEO title

[x] This is a question about using the theme.

[x] This is a feature request.

[ ] I believe this to be a bug with the theme.

[ ] I have updated all gems with bundle update.
[ ] I have tested locally with bundle exec jekyll build.

Minimal Mistakes version: 4.8.0

Jekyll version:

GitHub Pages hosted: yes

Operating system:

I am wondering if "og:title" is SEO title
I will propose at _includes/seo.html
<meta property="og:title" content="{{ page.title | default: site.title | markdownify | strip_html | strip_newlines | escape_once }}">

to
<meta property="og:title" content="{{ seo_title }}">

please check your site this :
https://developers.facebook.com/tools/debug/sharing/

seo_title adds in extraneous stuff that isn't needed for sharing. Page title (or the site title in the case of the homepage) looks much nicer when sharing.
Homepage:

Other pages:

Using seo_title gives you the full title that appends the separator (eg. -) and then the site title. If used for og:title would give things like Quick-Start Guide - Minimal Mistakes, which is good for the <title> element and SEO purposes, but for social sharing is unnecessary.

ok, thank you.
I like use "-" style, format, so I will set it for myself.


Expand tree by default when filtering

When you search for an item in the tree using the filter box the tree collapses by default. I think it would be a better experience if all folders expanded by default when using the filter/search box.
Edit: for clarity & typo

I agree - this is actually a bug introduced in 2.7.1. Working on a fix.

Bug fixed in 2.7.3


Consider def functions instead of lambda

Pylint suggests to not use lambda functions, but instead use def functions, where possible.

This is no longer relevant.


[Bug Report] Your descriptivMy server is not listed on the community server liste title here!

Have you read the Important information text above

[X] Yes i did

Current behavior
COMMUNITY_SERVER has been set to true, but the list of community servers can not be searched, the server can enter the play normally, does this need to change any Settings? Or is there a port that needs to be cleared?
Desired behavior
My server appears in the community list
Links to screenshots
No response
To Reproduce
readme setup
Software setup

OS:ubuntu22.04
Docker:

Hardware setup

vCPU: 1700x
RAM: 32G
Disk:250G

Additional context
No response

It's an issue with Palworld itself.  The game only loads a list of 200 community servers and only searches among that list of 200.  You can try refreshing the list to pull in different servers, but chances are low that you'll see yours.

@Compupaq
I can't search it on https://www.battlemetrics.com/servers/palworld, this article also can search 200 number?

Hey @dakezuo if you can enter from an external open ip and play, then your server should be listed in EOS when you enabled Community-Mode. What @Compupaq writes is true, Palworld has a really weird server-browser that needs some work. Also sometimes the EOS servers a quite stressed and you could try to search for your server on https://www.battlemetrics.com/servers/palworld - yes thats true, but give i like 30-60m.
Aside from that there isnt, anything i can do, aside from explaining it to you 😢

Nice! Happy gaming! 😎


feat- a cheatsheet for reference and made a folder as requested

Sir, as per your requirement I have made a folder and added my cheatsheet file there.
Hope it was a healthy contribution :)

Well written @royalpinto007  . Looking forward to see more cheats from your side

Thank you Sir, it means a lot to me.
I will surely contribute more, thanks again!


Unable to Get it working on Windows 10

Installed the latest version and downloaded the latest ini file
When I do Check this is what I get:

Please help

This happens when you already have modified termsrv.dll file, or some registry settings are incorrect.
RDP Wrapper requires original termsrv.dll file. And also build 10586 is already obsolete - try updating to the latest Windows version.

Hi Expert,
I am also having issue to get the RDP wrapper to work correctly. It was working fine until last week. I have no idea what happened. RDPConf shows everything is running but when I tried RDPCheck, I got a black screen. I tried to connect from outside world and I was getting error message of "couldn't connect to the remote PC. Make sure the PC is turned on and connected to the network..."

Is there anything I can do to resolve this issue?
Thanks & regards,
Eric

@ericmar81 Hello, Eric!
This can happen when the system is low on resources (CPU, RAM or Disk). Also on some PCs the first connection can hang about 5 minutes — I don't know the reason of this. Anything you can do is to wait until the connection finally establishes or disconnects (then try connecting again).
Also you may try to upgrade your system with Windows Update.

@binarymaster Hi,
Thanks for your reply. The thing is I never encounter such issue in the past until recently. It has been running fine.
:(

Well, RDP Wrapper can't modify itself and system files, so this issue isn't related to it, but to the system.


Make config file adaptable for other fish TS-length model

This and similar line of code under transect_results._get_strata_sig_b is where the empirical hake TS-length model is specified:
https://github.com/uw-echospace/EchoPro/blob/2c832292cb9cbae0b5bfd07c0b1ef328043d94c2/EchoPro/computation/transect_results.py#L99
To allow using the TS-length model for other species, replace these lines with a function that obtains the model from the species name from the config file.

Model metadata are currently incorporated into initialization_config.yml:
https://github.com/OSOceanAcoustics/echopop/blob/f244105852a86a7ea0fa887401321b39106e5c90/config_files/initialization_config.yml#L29-L39
However, a more efficient format would likely be necessary for cases where there are many species represented (e.g. an input spreadsheet). Right now, the calculation for sigma_bs is hard-coded for pacific_hake:
https://github.com/OSOceanAcoustics/echopop/blob/f244105852a86a7ea0fa887401321b39106e5c90/echopop/survey.py#L440-L442
Otherwise, strata_mean_sigma_bs includes the argument species_id for designating the species-of-interest:
https://github.com/OSOceanAcoustics/echopop/blob/f244105852a86a7ea0fa887401321b39106e5c90/echopop/survey.py#L400-L401
The remaining calculations then use species_id as a grouping variable for calculating sigma_bs_mean:
https://github.com/OSOceanAcoustics/echopop/blob/f244105852a86a7ea0fa887401321b39106e5c90/echopop/survey.py#L456-L477
Consequently, the function strata_mean_sigma_bs only requires minor tweaking to be compatible with multi-species analyses.

The updated implementation in PR #241 enables any defined species (using their number code) to be included when calculating the mean $\sigma_{bs}$ for each stratum.
This can be closed once PR #241 is closed.

This has been encapsulated within #289 and can therefore be closed.


Establish better naming convention for aggregate models

As we've been adding new models our organization, our model names have become a bit of a mess, without much consistency to them. This is not really a bad thing, we've been learning more about the needs of the data models, and deciding upon useful naming conventions is something that really comes out of having a strong idea of these needs.
I've noticed a few pain points/inconsistencies with our aggregate models in particular:

It's usually not possible to tell from the name whether the aggregate is at the station or detector (or controller!) level. Sometimes the name says station, but it's actually at the detector level. Sometimes it says neither.
We don't have much consistency about how to name different levels of temporal aggregation
We don't have a convention for how to name different levels of spatial aggregation

I'm opening this issue to discuss possible naming conventions going forward. Here is one proposal (but I'm interested in hearing other ideas!)
Proposal
Overall name structure is:
{model stage}_{category}__{device type}_agg_{temporal aggregation}_{spatial_aggregation}
This is pretty verbose, but would capture most of the relevant information about the intent of an aggregate model from the name. Some description of the components:
model stage: This is the stage of a model, such as stg, int, or as we move towards "mart" models, could be something like dim, or fct, or nothing.
category: This is either the data source system (e.g., clearinghouse or db96) or the broad category of intention of the data model (like diagnostics or imputation). This usually would correspond the the name of the directory in which the model file sits.
device type: For VDS data this would usually be "controller", "station", or "detector", and indicates the "grain" of the model. For instance, most of our VDS tables are at the "detector" level because they include a lane column. But when the lanes are aggregated up to the station level, it would be "station". Note that this could also be considered a spatial aggregation, but in most cases I felt it was important enough information to have a dedicated part in the name.
temporal aggregation: One of five_minute, hourly, daily, weekly, monthly, or yearly.
spatial aggregation: Things like district or freeway or county or city.
If one part of the naming convention didn't make sense for a given model, we could drop it from the name. In particular, I'm thinking that with "mart" models, which are intended to be shared with downstream data consumers who might not know our conventions and project structure, we might drop model stage and category.
A couple of examples:

int_clearinghouse__five_minute_station_agg --> int_clearinghouse__detector_agg_five_minute
int_imputation__five_minute_station_agg --> int_imputation__detector_agg_five_minute.
int_clearinghouse__station_temporal_hourly_agg --> int_clearinghouse__station_agg_hourly
When we create a freeway-district five-minute agg model: int_clearinghouse__detector_agg_five_minute_freeway_district

Thoughts @kengodleskidot and @mmmiah?

I am good with your proposal. Some additional clarification can be added. Literally all temporal aggregation is also spatial aggregation as we have city, county, lane and vice versa. It would be better to include whether the agg is only station level of station-lane level. May be something like this-
int_clearinghouse__station_lane_agg_hourly ( by lane by station)
int_clearinghouse__station_agg_hourly (by Station only)
We can avoid to add too many spatial features as it will produce a big name like int_clearinghouse__station_lane_agg_hourly_city_county_district_freeway_type which may be not required at all. Otherwise I see the value of consistent meaningful name that you proposed. My aggregation need to be also renamed. Let me renamed those based on this proposal

I am good with your proposal. Some additional clarification can be added. Literally all temporal aggregation is also spatial aggregation as we have city, county, lane and vice versa.

I'm not sure what you mean here: if we are only aggregating by a timestamp, then we are doing any spatial aggregation. I don't think we have any spatial aggregations yet in this project (until we do a group by city, county, what have you). I'm treating lane aggregations a bit differently from other spatial aggregations in this proposal.

It would be better to include whether the agg is only station level of station-lane level. May be something like this- int_clearinghouse__station_lane_agg_hourly ( by lane by station) int_clearinghouse__station_agg_hourly (by Station only)

In the above proposal, a model with the grain of station_lane is synonymous with "detector".

I believe that we group by id, timestamp (year, month, week , day) and also district, county, city, type in spatial and temporal aggregation! Yeah 'detector' term makes sense in replace of 'station_lane'. I will change my spatial temporal agg name soon and have a review on it

In order to do a spatial aggregation, we would need to group by district, county, city, etc without grouping by ID. Otherwise each unique combination of those keys would still be set by the id and timestamp.
Put another way: a spatial group by should have multiple stations per group in order to actually be aggregating anything (similar to how a temporal group by should have multiple timestamps per time bucket)

A thought about the above proposal: it can miss some important context about the purpose of a model: it only has the device level and the aggregation level. What if we also included an optional "purpose" component that could be, e.g., "metrics"? This starts to get quite verbose, but seems like it could be useful to me...
{model stage}_{category}__{device type}_{purpose}_agg_{temporal aggregation}_{spatial_aggregation}
So int_performance__five_min_perform_metrics would then become int_performance__detector_metrics_agg_five_minutes.
Thoughts @mmmiah?

In order to do a spatial aggregation, we would need to group by district, county, city, etc without grouping by ID. Otherwise each unique combination of those keys would still be set by the id and timestamp.

Based on your definition, it seems good to me and agree that we have not done yet the spatial aggregation in that sense

A thought about the above proposal: it can miss some important context about the purpose of a model: it only has the device level and the aggregation level. What if we also included an optional "purpose" component that could be, e.g., "metrics"? This starts to get quite verbose, but seems like it could be useful to me...
{model stage}_{category}__{device type}_{purpose}_agg_{temporal aggregation}_{spatial_aggregation}
So int_performance__five_min_perform_metrics would then become int_performance__detector_metrics_agg_five_minutes.
Makes more sense!

Is there a need to include _agg_ since it appears to be something that is common to most (if not all) of our models?
For the mart models dropping the model stage makes sense but the category could prove useful for the report/visualization designers to make it easier for them to identify which data sets are associated with a report/visualization type (diagnostic reports vs. performance metrics reports vs. bottleneck reports, etc.).
I like making {purpose} as optional since it may not always be required and helps keep the length of the model name as short as possible.
On a related note, we probably need to have someone go through the .yml files for QA/QC as well as understanding. I'm thinking this may be a good task for the new staff to help them understand what the models are and what they contain. Any thoughts @mmmiah @ian-r-rose @britt-allen

I don't think I agree that most of our models are aggregates (at least, not in the sense that the VDS models are). Our metadata models aren't aggregates, the coefficients models use aggregation in computing coefficients, but I don't think they are aggregates in the same way as our VDS ones.

On a related note, we probably need to have someone go through the .yml files for QA/QC as well as understanding. I'm thinking this may be a good task for the new staff to help them understand what the models are and what they contain.

I think this is a good idea!


feat(build): update dev dependencies and greenkeeper exclusions

Coverage decreased (-0.9%) to 91.479% when pulling 532fb5bcaf683a995223180c45db352fe2229c9f on feat-dev-deps into 78d51136aeacfdb503fa7ce4af26d9a8d72bfab3 on master.

Coverage decreased (-0.9%) to 91.479% when pulling 532fb5bcaf683a995223180c45db352fe2229c9f on feat-dev-deps into 78d51136aeacfdb503fa7ce4af26d9a8d72bfab3 on master.


  I got "I" and then died.

Maybe you can change your speculative model or set the spec_decoding_acceptance_method to typical_acceptance_sampler. When using '[ngram]', a bug exists in the RejectionSampler source code. It can not handle draft_probs with the shape (0, k).

Is anyone fixing this bug?
cc @cadedaniel

I'm happy to try other options. It was working well for someone else, but not for me on the phi-3-mini-128k model.  Failed instantly.  I'll probably wait until this bug is fixed before trying again.
The hope is that for structured output, others are getting quite good speed-up.  i.e. for guided_json and JSON output, about 5x improvement for a 7b model.  Sounds great, but just crashes for me.

I'm happy to try other options. It was working well for someone else, but not for me on the phi-3-mini-128k model. Failed instantly. I'll probably wait until this bug is fixed before trying again.
The hope is that for structured output, others are getting quite good speed-up. i.e. for guided_json and JSON output, about 5x improvement for a 7b model. Sounds great, but just crashes for me.

Did you try adding --spec-decoding-acceptance-method='typical_acceptance_sampler' \? It works for me to avoid the crash.

I'm happy to try other options. It was working well for someone else, but not for me on the phi-3-mini-128k model. Failed instantly. I'll probably wait until this bug is fixed before trying again.
The hope is that for structured output, others are getting quite good speed-up. i.e. for guided_json and JSON output, about 5x improvement for a 7b model. Sounds great, but just crashes for me.

FYI, you can build from the source code of the main branch. I guess the container you are using is built with vllm version v0.5.3 or v0.5.3.post1. (#6698) has fixed this bug. Alternatively, you can wait for the release of v0.5.4, which should not cause the crash again.

0.5.4 seems to fix the issue.


DPUL Home Page Redesign

If we're talking about redesigning the whole home page, perhaps LUX could be used for more than just the headers/footers? For example, replacement of the flippy cards could be a yet-to-be-designed LUX component.

Footer for DPUL came up in a meeting today. Any timeline on when footer will changed to that of PUL main site?


typo

Beast: The returned Mutation

AFAIK it was a query :upside_down_face:

BTW I am thinking to generate a more specific codegen lib for Qt and (more precisely Qt-QML) if you are interested on joining forces I would be happy (: https://github.com/nrbnlulu/qtgql/pull/12

Oh yes this should be fixed in the documentation generation, generally that features is still quite underdeveloped, will have a look there again, any further suggestions on how turms should handle that?
When it comes to performance, I am inclined to agree, and I initially was planning on just using pure dataclasses, however there is this little problem with interfaces and their (de)serialization especially if you want to use fragments. Given this json return
Given this query

fragment Apple on Apple{
   worm
}

fragment Banana on Banana {
  eaten
}

query Get_Fruits {
   fruits {
        name
        ...Apple
        ...Banana
   }
}

And this return
{"fruits": [{"__typename": "Apple", "worm": true }, {"__typename": "Banana", "eaten": true}]}

You would have to generate your own deserialization logic that is able to map to the correct Fragment, which lead me to just ditch that approach and use pydantic (which supposedly will see a performance bump soon moving to rust based deserialization). Hope that clarifies the decision a bit better!
And yes I would love to work on that, was hoping to maybe find something more like useQuery, useMutation in the QT ecosystem. Just tell me where to start ;)
Btw, this is a turms related issue so i will move the discussion there!


in Linux why  the client loop must same as server loop

i used per thread per loop.
i used tcp listen in a thread with a loop ,and i want to run the client in another thread (another loop) for net io service.
but when i call function uv_accept . that is a assert with in the file  src\unix\stream.c .
int uv_accept(uv_stream_t* server, uv_stream_t* client) {
int err;
/* TODO document this */
assert(server->loop == client->loop);
if (server->accepted_fd == -1)
return -EAGAIN;

is that mean the client loop must same as server loop. in old version that is not have the assert.

This is by design. The libuv loop is not thread safe, so you can't initialize a handle that belongs to a loop from another. This was never possible. If you where relying on it because there was no assert at some point, that was a mistake, I'm afraid.
The behavior is now properly documented here and has been since v1.0.
Note to self: remove that TODO note.

OK。 thanks. i am now used it in the same loop .   but i am worry Inefficiency in the loop with so much client connections in the same loop to call read and write .
2016-06-15
love19862003
发件人：Saúl Ibarra Corretgé<EMAIL_ADDRESS>发送时间：2016-06-15 15:44
主题：Re: [libuv/libuv] in Linux why the client loop must same as server loop (#915)
<EMAIL_ADDRESS>抄送："fanny.wu"love19862003<EMAIL_ADDRESS>This is by design. The libuv loop is not thread safe, so you can't initialize a handle that belongs to a loop from another. This was never possible. If you where relying on it because there was no assert at some point, that was a mistake, I'm afraid.
The behavior is now properly documented here and has been since v1.0.
Note to self: remove that TODO note.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Don't worry about that. The polling mechanisms we sue have been designed for high load. More threads won't necessarily help.

OK . thanks very much  for you help.
2016-06-15
love19862003
发件人：Saúl Ibarra Corretgé<EMAIL_ADDRESS>发送时间：2016-06-15 15:44
主题：Re: [libuv/libuv] in Linux why the client loop must same as server loop (#915)
<EMAIL_ADDRESS>抄送："fanny.wu"love19862003<EMAIL_ADDRESS>This is by design. The libuv loop is not thread safe, so you can't initialize a handle that belongs to a loop from another. This was never possible. If you where relying on it because there was no assert at some point, that was a mistake, I'm afraid.
The behavior is now properly documented here and has been since v1.0.
Note to self: remove that TODO note.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Maybe it is a flaw of libuv. I wrote a epoll test code in c using a single listening thread and multiple working threads, it is more effective than libuv dose. When forcing to a single working thread, it shows same results.

The behavior is that way by design and is documented: https://github.com/libuv/libuv/issues/915#issuecomment-226112652


Outline panel display incorrectly

VSCode Version: 1.36
OS Version: Ubuntu 18.04.2 LTS (Linux kernel: 4.18.0-25-generic)

Steps to Reproduce:

Open an empty workspace
Right click on the side-panel, then choose New File
Name it TEST.cpp
Loot ak Outline panel, there are many line with content "{}__7"

The problem disappears when I disable ms-vscode.cpptools extension.

Please report the issue against the owners of the CPP extensions you are using. Very likely: https://github.com/Microsoft/vscode-cpptools


Have some jquery script in html,how to make them work after mount

Dear,
I have a static html page which has some jquery script like:
$('#Button').on('click', function(e) {});
How to make the script work after mount the single-spa-html app,
I can pass a bind event callback in h5 enviroment,but since it is a webview also used in native app,
so better can make it work without external binding.
Thanks,

One option is to add a custom mount lifecycle function:
const htmlLifecycles = singleSpaHtml({...})

export function bootstrap = [htmlLifecycles.bootstrap];

export function mount = [
  htmlLifecycles.mount,
  async function() {
    $('#Button').on('click', function(e) {});
  }
];

export function unmount = [
  htmlLifecycles.unmount
];

Closing because I think i've answered this, but feel free to reopen or comment further


Additional body kwarg given on GET requests

Description
When sending a GET request, an additional body keyword argument is sent to the handling function, causing it to fail with TypeError: some_function() got an unexpected keyword argument 'body'.
Expected behaviour
Only the described parameters should be forwarded to the function. Also, according to the spec, it seems that there should be no body provided on GET and DELETE.
Actual behaviour
A body keyword argument is added as a function parameter.
Steps to reproduce
requirements.txt
flask==1.0.2
requests==2.20.0
connexion==2.0.1

api.yaml
openapi: 3.0.0
info:
  version: '1'
  title: Sample HTTP GET endpoint

paths:
  '/{some_param}':
    get:
      description: Testing
      operationId: app.sample_get
      parameters:
        - name: some_param
          in: path
          required: true
          schema:
            type: string
      responses:
        default:
          description: OK

app.py
def sample_get(**kwargs):
    return kwargs

Run application and send request
connexion run api.yaml
python -c 'import requests; print(requests.get("http://localhost:5000/testing").text)'

Returns
{
  "body": {},
  "some_param": "testing"
}

Expected return:
{
  "some_param": "testing"
}

Additional info:

Python 2.7.10
connexion 2.0.1

Unfortunately in OpenAPI 3 specs the request body does not have a name.
We support assigning it a name with the 'x-body-name' key, but by default
it is called body.
x-body-name works like this:
requestBody:
  content:
    application/json:
      schema:
        x-body-name: pet
        $ref: '#/components/schemas/Pet'

On Wed, Nov 7, 2018, 6:16 AM Pål Nes<EMAIL_ADDRESS>wrote:

Description
When sending a GET request, an additional empty body keyword argument is
sent to the handling function.
Expected behaviour
Only the described parameters should be forwarded to the function. Also,
according to the spec, it seems that there should be no body provided on
GET and DELETE.
Actual behaviour
An empty body keyword argument is added as a function parameter.
Steps to reproduce
requirements.txt
flask==1.0.2
requests==2.20.0
connexion==2.0.1
api.yaml
openapi: 3.0.0info:
version: '1'
title: Sample HTTP GET endpoint
paths:
'/{some_param}':
get:
description: Testing
operationId: app.sample_get
parameters:
- name: some_param
in: path
required: true
schema:
type: string
responses:
'200':
description: OK
'400':
description: Bad request.
default:
description: Error
app.py
def sample_get(**kwargs):
return kwargs
Run application and send request
connexion run api.yaml
python -c 'import requests; print requests.get("http://localhost:5000/testing").text'
Returns
{
"body": {},
"some_param": "testing"
}
Additional info:

Python 2.7.10
connexion 2.0.1

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zalando/connexion/issues/757, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlPSbuxJssbT0cEj8yyLVk5RasVu0Exks5ususugaJpZM4YSglU
.

oops I misread your ticket. body should definitely not be passed in on GET
requests!
On Wed, Nov 7, 2018, 7:13 AM Daniel Grossmann-Kavanagh<EMAIL_ADDRESS>wrote:

Unfortunately in OpenAPI 3 specs the request body does not have a name.
We support assigning it a name with the 'x-body-name' key, but by default
it is called body.
x-body-name works like this:
requestBody:
  content:
    application/json:
      schema:
        x-body-name: pet
        $ref: '#/components/schemas/Pet'

On Wed, Nov 7, 2018, 6:16 AM Pål Nes<EMAIL_ADDRESS>wrote:

Description
When sending a GET request, an additional empty body keyword argument is
sent to the handling function.
Expected behaviour
Only the described parameters should be forwarded to the function. Also,
according to the spec, it seems that there should be no body provided on
GET and DELETE.
Actual behaviour
An empty body keyword argument is added as a function parameter.
Steps to reproduce
requirements.txt
flask==1.0.2
requests==2.20.0
connexion==2.0.1
api.yaml
openapi: 3.0.0info:
version: '1'
title: Sample HTTP GET endpoint
paths:
'/{some_param}':
get:
description: Testing
operationId: app.sample_get
parameters:
- name: some_param
in: path
required: true
schema:
type: string
responses:
'200':
description: OK
'400':
description: Bad request.
default:
description: Error
app.py
def sample_get(**kwargs):
return kwargs
Run application and send request
connexion run api.yaml
python -c 'import requests; print requests.get("http://localhost:5000/testing").text'
Returns
{
"body": {},
"some_param": "testing"
}
Additional info:

Python 2.7.10
connexion 2.0.1

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zalando/connexion/issues/757, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlPSbuxJssbT0cEj8yyLVk5RasVu0Exks5ususugaJpZM4YSglU
.

@palnes can you take a look at #761 please?

Cool beans! That works for me. :)

Unfortunately in OpenAPI 3 specs the request body does not have a name. We support assigning it a name with the 'x-body-name' key, but by default it is called body. x-body-name works like this:

requestBody:
  content:
    application/json:
      schema:
        x-body-name: pet
        $ref: '#/components/schemas/Pet'

This doesn't seem valid OAS to me though. @dtkav

@ioggstream which part is invalid?

iirc siblings values alongside $refs are ignored, and other processors could strip that field.

https://swagger.io/docs/specification/using-ref/

I know this issue is closed but others reading this might find it useful to know that while the OpenAPI & Swagger code generators don't include the x-body-name property as shown above   nor do those tools preserve the x-body-name property in the resulting run-time specification YAML, if added manually prior to running a server utilizing the spec, the OpenAPI 5.0.1 OpenAPIOperation._get_body_arguments function will make use of the property.
If the x-body-name is placed in the actual schema type definition (so the usage follows the restriction as mentioned above by @ioggstream and in the docs at  :
   schemas:
      ParseModelRequest:
        type: object
        x-body-name: parse_model_request
        properties:
          modelRequest:
            $ref: '#/components/schemas/ProjectDataRequest'
          elements:
            $ref: '#/components/schemas/Elements'

The OpenAPI python-flask code generator will keep the x-body-name there & the run-time usage works.
I need to evaluate any effect on the generated python client code.

@dtkav
You say that it works as below but this is not valid OAS and other tools will not support this construct.
For example the code gen tools won't work with this.
A media type ma be a $ref OR a schema you can't has an extension AND a ref.
Is there any attempt to fix this by moving the extension to somewhere that is legal.
So rather than ....
requestBody:
  content:
    application/json:
      schema:
        x-body-name: pet
        $ref: '#/components/schemas/Pet'

It's really tedious that tools can't work together or follow the spec as it forces hacks in other libraries and user code.
requestBody:
  content:
    application/json:
       x-body-name: pet
      schema:
        $ref: '#/components/schemas/Pet'


feat: randomize mandatory fee config values

Currently, max_cj_fee_abs and max_cj_fee_rel are set to hardcoded values in the default config.
These should be randomized in order to not interfere with the fee market limits too much.
See @openoms approach for RaspiBlitz: https://github.com/rootzoll/raspiblitz/pull/3321/files#diff-77862cc87b7e1a30dd99c39f53e73f3d249e0c101e4fac4b0d3930b1fc5798faR218-R220
Also: It might be possible to get rid of shipping the default.cfg altogether.

Also: It might be possible to get rid of shipping the default.cfg altogether.

Ultimately decided against removing the default config during this task. Tracked in a distinct issue #67


Audit the dependency,@floating-ui/dom

I was working on the PR #722 for upgrading @floating-ui/dom, but I was not able to figure out where or whether this dependency is currently used. Making an issue here to track the audit process. If this is not currently used, we can remove it.

The PR #391 mentions that @floating-ui/dom is used in the marketing page tooltips, but I was unable to find it in the current version.

Originally posted by @nsunami in https://github.com/libscie/ResearchEquals.com/issues/722#issuecomment-1252899544

As @chartgerink mentioned in https://github.com/libscie/ResearchEquals.com/pull/722#issuecomment-1255046786, this dependency is being used like this:

I added a description about this dependency to our Wiki.

Thanks @nsunami! I think we can close this then?
Note: This could be deprecated potentially when we have the new marketing page that is being developed. We'll have to doublecheck of course.

@chartgerink  Welcome!  And thanks for the note about the upcoming marketing page!
Just to double-check—is @floating-ui/dom somehow interact with react-tooltip? Looking at the index.tsx file, react-tooltip is used around the tooltip content. I realized this while working on the dependabot upgrade for react-tooltip https://github.com/libscie/ResearchEquals.com/pull/825, and I just wanted to make sure before closing this issue.

Oh haha - it seems like it's not being used indeed. You could try removing it and see whether things work as expected?
I might've forgotten to remove it after exploring it as an option and never double checking the dependency list.

Got it! Will do! 👍


Unable to install.

I'm unable to install this plugin. Has anyone tried lately? Is this plugin still supported? If not, are there any alternatives?

@gifthlong, hmm, ok, so, you couldn't install it either. hmm.

@thecoleorton @gifthlong you guys were able to isntall? I downloaded it to my laptop and then installed, it got installed but not showing in config.xml.
Any idea?

We had the same issue and i debugged it a bit deeper. It looks like there is an naming conflict 🙈
The plugin repo is called phonegap-mobile-accessibility and the package name is phonegap-plugin-mobile-accessibility. In the latests version of cordova the plugins are install via npm.
cordova-fetch installes the plugin into phonegap-plugin-mobile-accessibility and verifies that it is installed under phonegap-mobile-accessibility. (serach for "Failed to get absolute path to installed module").
To fix this: just change the name in the package.json to phonegap-plugin-mobile-accessibility ;-)

@ruettenm any example? There is no entry in package.json yet as it fails on
cordova plugin add https://github.com/phonegap/phonegap-mobile-accessibility.git

If anyone is still having issues with this. Try using a lower node version.
Problem was experienced with v15 and downgrading to v12 using nvm solved the issues.


report whitespace workaround

Added code to add line breaks to the ends of existing provisions and certain variables instead of having them on the template inside showBegin/showEnd blocks.

DEV deployments have completed successfully!
Backend available
Frontend available

Your Pull Request code is being promoted!  Please follow the link below.
Main Merge Workflow


Docker build fails for the 1.5.0 release

Following the good advice of @pathmapper in #487, and as long as #489 is open, I'm trying to build the Docker image for version 1.5.0 locally.
However npm install step seems to fail with the following error:
<EMAIL_ADDRESS>/maputnik
+--<EMAIL_ADDRESS>+-- UNMET DEPENDENCY<EMAIL_ADDRESS>+-- UNMET DEPENDENCY<EMAIL_ADDRESS>`-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>
How can overcome this issue?
How to reproduce

Clone the repository, if needed
Change to the 1.5.0 tag using git checkout tags/v1.5.0
Run docker build --tag=maputnik_editor .

Notes

Running npm install from the command line fails similarly.
This is the output of the docker build:

Sending build context to Docker daemon  341.7MB
Step 1/9 : FROM nodesource/xenial:6.1.0
 ---> 8f9070d29e4b
Step 2/9 : EXPOSE 8888
 ---> Using cache
 ---> 5aabdfd4ce84
Step 3/9 : ENV HOME /maputnik
 ---> Using cache
 ---> d3c88a45ca80
Step 4/9 : RUN mkdir ${HOME}
 ---> Using cache
 ---> 6a31c85f1c85
Step 5/9 : COPY . ${HOME}/
 ---> Using cache
 ---> f942c2b7122a
Step 6/9 : WORKDIR ${HOME}
 ---> Using cache
 ---> 1ac762e6ac26
Step 7/9 : RUN npm install -d --dev
 ---> Running in ff2e6d71165d
npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm WARN install Usage of the `--dev` option is deprecated. Use `--only=dev` instead.
npm info attempt registry request try #1 at 2:36:01 PM
npm http request GET https://registry.npmjs.org/fsevents
npm http 200 https://registry.npmjs.org/fsevents
npm info attempt registry request try #1 at 2:36:22 PM
npm http request GET https://registry.npmjs.org/scheduler
npm info attempt registry request try #1 at 2:36:22 PM
npm http request GET https://registry.npmjs.org/file-saver
npm info attempt registry request try #1 at 2:36:22 PM
npm http request GET https://registry.npmjs.org/react
npm info attempt registry request try #1 at 2:36:22 PM
npm http request GET https://registry.npmjs.org/react-dom
npm http 200 https://registry.npmjs.org/scheduler
npm info retry fetch attempt 1 at 2:36:23 PM
npm info attempt registry request try #1 at 2:36:23 PM
npm http fetch GET https://registry.npmjs.org/scheduler/-/scheduler-0.12.0.tgz
npm http fetch 200 https://registry.npmjs.org/scheduler/-/scheduler-0.12.0.tgz
npm http 200 https://registry.npmjs.org/file-saver
npm info retry fetch attempt 1 at 2:36:23 PM
npm info attempt registry request try #1 at 2:36:23 PM
npm http fetch GET https://registry.npmjs.org/file-saver/-/file-saver-1.3.8.tgz
npm http 200 https://registry.npmjs.org/react-dom
npm info retry fetch attempt 1 at 2:36:23 PM
npm info attempt registry request try #1 at 2:36:23 PM
npm http fetch GET https://registry.npmjs.org/react-dom/-/react-dom-16.7.0.tgz
npm http 200 https://registry.npmjs.org/react
npm info retry fetch attempt 1 at 2:36:23 PM
npm info attempt registry request try #1 at 2:36:23 PM
npm http fetch GET https://registry.npmjs.org/react/-/react-16.7.0.tgz
npm http fetch 200 https://registry.npmjs.org/file-saver/-/file-saver-1.3.8.tgz
npm http fetch 200 https://registry.npmjs.org/react-dom/-/react-dom-16.7.0.tgz
npm http fetch 200 https://registry.npmjs.org/react/-/react-16.7.0.tgz
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>/maputnik
+--<EMAIL_ADDRESS>+-- UNMET DEPENDENCY<EMAIL_ADDRESS>+-- UNMET DEPENDENCY<EMAIL_ADDRESS>`-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>
npm WARN optional Skipping failed optional dependency /karma/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm ERR! Linux 4.15.0-43-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-d" "--dev"
npm ERR! node v6.1.0
npm ERR! npm  v3.8.6
npm ERR! path /maputnik/node_modules/scheduler
npm ERR! code EXDEV
npm ERR! errno -18
npm ERR! syscall rename

npm ERR! EXDEV: cross-device link not permitted, rename '/maputnik/node_modules/scheduler' -> '/maputnik/node_modules/.scheduler.DELETE'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /maputnik/npm-debug.log
The command '/bin/sh -c npm install -d --dev' returned a non-zero code: 238

Hi @zstadler,
as mentioned in https://github.com/maputnik/editor/issues/487#issuecomment-458527102, you may use the following command to build a local docker image of v1.5.0:
docker build https://github.com/maputnik/editor.git#v1.5.0
There is no need to clone the repo before.
You could append --tag maputnik/editor:1.5.0 to the command to name and tag the image:
 docker build https://github.com/maputnik/editor.git#v1.5.0 --tag maputnik/editor:1.5.0

Thank you @pathmapper !


Improve #[cfg] diagnostics

Unfortunately I ran into https://github.com/rust-analyzer/rust-analyzer/issues/4058 while testing this on https://github.com/nrf-rs/nrf-hal/, so I didn't see much of it in action yet, but it does seem to work.

bors r+


Public code blocked where it shouldn't

VS Code Version: latest
OS Version:
Logs:

Steps to Reproduce:

select a code that is obviously from a public repo
translate it to english or whatever language it is not in
tell github copilot to translate it to the language the public file already has.

My Settings:

I'm getting the public code blocked response on every single question at the moment. I do have it set to allow, but I don't think the problem is it is only ignoring my settings there. I think something has changed that it thinks every single response has public code, and it ignores the users setting as well.

Same goes for me, every response is filtered for some reason

Same here. Wanted to give me new code for my login.blade.php with the same design of register.blade.php then the answer "Sorry, the response matched public code". I tried already to block matching public code at the github settings but still facing this issue.
The code isnt anywhere on a repo on github or somewhere else. The reset password could be in some cases with the same layout cause its needed for nearly every application....
The answer here (https://github.com/microsoft/vscode-copilot-release/issues/295#issuecomment-1760046462) doesnt make any changes...

Can you please provide the logs from GitHub Copilot Chat output channel. This will help us investigate what is going on in the backend with these requests

Looks like off-topic detection incorrectly marks responses as filtered, which leads to the wrong error.
We are working on a fix. Meanwhile, public-code error responses mean that the off-topic detection kicked in and you can solve this by rephrasing your question.

Fix ix happening here: https://github.com/github/copilot-api/issues/1817

How to get the output logs of it?
rephrasing doesn’t make any difference. I tried several times with different prompts and everytime it starts creating the answer and then stopping with the error message.
And if set the setting to „block“ then it don’t gonna generate codes anymore or it only doesn’t check public code ?

How to get the output logs of it?
rephrasing doesn’t make any difference. I tried several times with different prompts and everytime it starts creating the answer and then stopping with the error message.
And if set the setting to „block“ then it don’t gonna generate codes anymore or it only doesn’t check public code ?

CTRL/CMD + SHIFT + U then go to the dropdown and select "GitHub Copilot Chat" and copy the info

How to get the output logs of it?
rephrasing doesn’t make any difference. I tried several times with different prompts and everytime it starts creating the answer and then stopping with the error message.
And if set the setting to „block“ then it don’t gonna generate codes anymore or it only doesn’t check public code ?

CTRL/CMD + SHIFT + U then go to the dropdown and select "GitHub Copilot Chat" and copy the info

My console output:
2023-11-03T19:49:01.667Z [INFO] [streamMessages] message 0 returned. finish reason: [stop] 2023-11-03T19:49:01.668Z [INFO] [streamChoices] request done: headerRequestId: [0066d12e-e5ab-4152-a2b9-b3401b1043b4] model deployment ID: [x2191bfb807ec] 2023-11-03T19:49:44.464Z [INFO] [chat fetch] engine https://api.githubcopilot.com/chat 2023-11-03T19:49:44.464Z [INFO] [chat fetch] modelMaxTokenWindow 4096 2023-11-03T19:49:44.464Z [INFO] [chat fetch] chat model gpt-4 2023-11-03T19:49:46.518Z [INFO] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 2053 ms 2023-11-03T19:49:46.519Z [INFO] [streamMessages] message 0 returned. finish reason: [content_filter] 2023-11-03T19:49:46.520Z [INFO] [streamChoices] request done: headerRequestId: [ddc1a7c7-da96-49a1-ac45-9a5dedf6f80d] model deployment ID: [x3b0892d9e5fc]
Prompt (originaly in german): I want to create an interactive table for leads where the user can move columns, add new columns, sort the table by columns, perform a live search, and have lazy loading for large amounts of data. Please create the necessary steps for me step by step and wait after each file for my prompt "continue" to create the next file. When you are done, say "Finished".

@ismir2020 You have the public code match setting disabled in your GH settings or via the organization that granted you copilot access?

Ive Set it to allow and to block. Tested with both settings value and both getting this error. Don’t have Organisation profile. Followed the documentation for allowing or blocking this setting under Settings -> Copilot -> allow/block

Ive Set it to allow and to block. Tested with both settings value and both getting this error. Don’t have Organisation profile. Followed the documentation for allowing or blocking this setting under Settings -> Copilot -> allow/block

Do you have some logs when you have it set to Allow that I can check?

Ive Set it to allow and to block. Tested with both settings value and both getting this error. Don’t have Organisation profile. Followed the documentation for allowing or blocking this setting under Settings -> Copilot -> allow/block

Do you have some logs when you have it set to Allow that I can check?

No cause I cleared the chat cause I thought it didn’t get the settings update from allow to block. But I can try to run the commands again with Allow tomorrow and send you the console output

Facing same issue since yesterday evening.
2023-11-05T11:36:56.957Z [INFO] [chat] copilot token chat_enabled: true
2023-11-05T11:36:56.957Z [INFO] [auth] Got Copilot token for akhilesh84
2023-11-05T11:37:13.229Z [INFO] [chat fetch] engine https://api.githubcopilot.com/chat
2023-11-05T11:37:13.229Z [INFO] [chat fetch] modelMaxTokenWindow 4096
2023-11-05T11:37:13.229Z [INFO] [chat fetch] chat model gpt-4
2023-11-05T11:37:14.163Z [INFO] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 933 ms
2023-11-05T11:37:14.165Z [INFO] [chat fetch] Request ID for failed request: ,8712b723-631d-4d6b-b77b-dcc0f87642d4
2023-11-05T11:37:14.169Z [ERROR] [chat fetch] Unhandled status from server:,400,Bad Request

Same here, and it has been this way for a long time. I assumed I had turned public code > off for some reason without remembering why, and assumed the reason was valid, whatever it was.
However this was not the case and the setting had been to "allow public code" all along, so it is a long running issue.
I also set it to allow to use my snippets to improve the product, if that matters. I initially suspected the issue was because it had just decided to use my code in said product improvement, but then ironically immediately disallowed me from viewing my, now public, code. However since both settings were to allow, this can't have been the case. Perhaps there is a twilight zone where the snippet gets submitted but the user setting to allow use isn't verified yet?

As of 10:30 AM on Sunday (Nov 5), I'm receiving 404s for matching public code found in code completion.

@akhilesh84 I think you're getting off topic filtered (the model doesnt think your question is about code) and we're just reporting it incorrectly. Can you update to the latest pre-release and vs code insiders and give it a shot. I've fixed this bug.
@ryanjsalva That's for completions and not chat, which is not something this repo tracks. Those are tracked in GitHub's own discussion https://github.com/orgs/community/discussions/categories/copilot

@svenbledt: snippy blocking was (correctly) not enabled for your request. It was instead blocked by RAI's "violence" filter, since (as you can see at the end of your screenshot), the completion was talking about guns/"waffe"="weapon".
@dbdean: I couldn't find any blocked chat responses for your account in the past week. Were you signed in as this GH user? If you can still repro the blocking, could you please include logs per above?
@ismir2020: Indeed sometimes you get blocked by the text copyright filter; it seems like this happened when the model was generating boilerplate html with included scripts (ex APIM ID 095ff90f-8815-45cb-a3f6-93d124c202d1). At other times, your chat responses seem to have been over-blocked by the RAI "sexual" filter (ex APIM ID 2d80df99-5f58-426a-adaf-cba4c9ada41c). Will try to follow up with RAI folks to report the false positives.
@NidusUmbra: Your code was over-blocked by the RAI "self-harm" filter (ex APIM ID 0bf83e34-3549-4370-bc73-ea5041dde7c9). Ditto re: reporting the false positives.

@ismir2020: Indeed sometimes you get blocked by the text copyright filter; it seems like this happened when the model was generating boilerplate html with included scripts (ex APIM ID 095ff90f-8815-45cb-a3f6-93d124c202d1). At other times, your chat responses seem to have been over-blocked by the RAI "sexual" filter (ex APIM ID 2d80df99-5f58-426a-adaf-cba4c9ada41c). Will try to follow up with RAI folks to report the false positives.

Okay. Wondering how this filter can apply at a registration and a login form. Maybe cause of the CDN links for js,css and so on?
How I can workaround with this ? Any suggestions?

Maybe cause of the CDN links for js,css and so on?
yes, that's exactly where it triggered

How I can workaround with this ? Any suggestions?
you can try asking it to skip generating the CDN links and to only generate code instead

But this cdn shouldnt be filtered through any filter cause its normal coding style to use cdn links for the files. isnt it?

Same thing in latest insiders version.
with  allowed on my github profile

@akhilesh84 I think you're getting off topic filtered (the model doesnt think your question is about code) and we're just reporting it incorrectly. Can you update to the latest pre-release and vs code insiders and give it a shot. I've fixed this bug.

its working on insiders . Thanks.
Any timelines for fix to be made available on regular build. i updated to 1.84.1 but the issue persist

Any timelines for fix to be made available on regular build. i updated to 1.84.1 but the issue persist

They're released monthly. So start of December

Running current insiders just getting this, cant see how this matches public code

Getting error 400 for the past hour, tried both VSCode and VSCode insider:
2023-11-21T20:33:36.392Z [INFO] [chat fetch] engine https://api.githubcopilot.com/chat
2023-11-21T20:33:36.392Z [INFO] [chat fetch] modelMaxTokenWindow 4096
2023-11-21T20:33:36.392Z [INFO] [chat fetch] chat model gpt-4
2023-11-21T20:33:36.558Z [INFO] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 166 ms
2023-11-21T20:33:36.559Z [INFO] [chat fetch] Request ID for failed request: ,262e9f1f-c2cd-4f38-af44-bfe48074f1cc
2023-11-21T20:33:36.559Z [ERROR] [chat fetch] Unhandled status from server:,400,Bad Request
The diagnostics:
Copilot

Version: 1.138.0
Build: prod
Editor: vscode/1.85.0-insider

Environment

http_proxy: n/a
https_proxy: n/a
no_proxy: n/a
SSL_CERT_FILE: n/a
SSL_CERT_DIR: n/a
OPENSSL_CONF: n/a

Feature Flags

Custom Certificates: disabled
Send Restricted Telemetry: enabled
Chat: enabled

Node setup

Number of root certificates: 140
Operating system: Darwin
Operating system version: 22.6.0
Operating system architecture: arm64
NODE_OPTIONS: n/a
NODE_EXTRA_CA_CERTS: n/a
NODE_TLS_REJECT_UNAUTHORIZED: n/a
tls default min version: TLSv1.2
tls default max version: TLSv1.3

Network Configuration

Proxy host: n/a
Proxy port: n/a
Proxy auth: n/a
Kerberos SPN: n/a
Reject unauthorized: disabled

Reachability

github.com: HTTP 200 -
copilot-proxy.githubusercontent.com: HTTP 200 -
default.exp-tas.com: HTTP 200 -

VS Code Configuration

HTTP proxy:
HTTP proxy autentication: n/a
Proxy Strict SSL: true
Extension HTTP proxy support: override

Extensions

Is win-ca installed?: false
Is mac-ca installed?: false

Same thing, the issue is present for all questions and all codes no matter if private, public, or even my own.

This might be duplicate of #583 or related.

I am still seeing a similar issue. My settings allow response to match public code and still I am seeing this as a response on many requests.

Consolidating as duplicate of https://github.com/microsoft/vscode-copilot-release/issues/583

2023-12-27 11:46:55.188 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2023-12-27 11:46:55.191 [info] [chat fetch] modelMaxTokenWindow 4096
2023-12-27 11:46:55.191 [info] [chat fetch] chat model gpt-4
2023-12-27 11:46:59.159 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 3968 ms
2023-12-27 11:46:59.160 [info] [streamMessages] message 0 returned. finish reason: [content_filter]
2023-12-27 11:46:59.161 [info] [streamChoices] request done: requestId: [927fdfc4-4fae-49f7-ae10-f64ee7ad437a] responseId: [35722e39-4d67-498a-a86d-ce4ed0a2641d] model deployment ID: [x8d3c95500d67]

More annoying is the fact that this affect the "autocomplete" and you don't know why (its because of this bug).
I use copilot mostly for the repetitive tasks like filling languages or create human readable text from error codes etc,
I had this list of error codes:
...
// _structureParser.missingRequiredKey
// accountSet.invalidAccountName
// accountSet.invalidApiKey
// accountSetIfArgs.missingArgs
// accountIsSet.notSet'
...

And i was using copilot autofill to create an array based on that commented list with human readable error messages but it refused to fill 'accountSet.invalidApiKey' no matter what, and worse, the autocomplete doesn't even give us a public code warning like the chat.
...
        '_structureParser.invalidTypeNumber' => [
          'en' => 'The value provided is not a number.',
          'pt' => 'O valor fornecido não é um número.'
        ],
        'accountSet.invalidAccountName' => [
          'en' => 'The account name provided is not valid.',
          'pt' => 'O nome de conta fornecido não é válido.'
        ],
        'accountSet.invalidApiKey' => [

        ],
        'accountSetIfArgs.missingArgs' => [
          'en' => 'The function requires arguments.',
          'pt' => 'A função requer argumentos.'
        ],
        'accountIsSet.notSet' => [
          'en' => 'The account name and API Key are not set.',
          'pt' => 'O nome de conta e a API Key não estão definidos.'
        ],
...

Even if you do not enable public code (i have it and it still won't work), a lot of code will always look similar and be a coincidence that looks like public code, but shouldn't... "invalidApiKey" shouldn't be considered public code, it way too generic.


Array update REPL tests

Just for reference, these examples will fail if all array updates are mutable.
! @amosr @jystic

I stole these

https://github.com/ambiata/icicle/pull/445


ConnString Database Function Updates

Ticket: TT-66
Changes
1. Database

Added DB *sql.DB, meaning that now you need to pass in the database connection to run any function.

2. database.go

I spoke with @noahjrc today, and he mentioned using some outdated functions, which was my mistake.
In order to avoid confusion, I removed them. Among them were UpdateRow, AddRow, and others.

3. Events and Itineraries

When you add an Event, it should also add that Event to all Itineraries associated with that Event.
Same thing, but replace Event with Itineraries, and vice versa.

Did not test, but logic wise it LGTM

Oh I tested it out, everything works fine (main-service + auth-service)


Sending Email

Hi,
I have some issue to send mail through HelpDesk.
I added my email host and user identifications in settings.py and when I run ./manage.py shell, I can send mail.
In my followup list, I enabled the mail sending, but when a ticket is create, the creator doesn't receive an email... did I miss something? Is there something else to modify?
(sorry for my bad english)
Reykoh

What method are you using to send email? Is your queue configured with a valid e-mail address for your chosen email delivery service? (The queue email is used when sending email from the queue). Do any other emails get sent, ie on assignment, update, or close?

Hi Ross
Do you know if it is possible to compose normal emails from Django Help Desk for front end users?
Keegan

No, it's a helpdesk system not a full CRM or email client.


Plugin not working correctly with existing elements

Bug report
Describe the bug
The alias is not always saved with existing elements (I use strapi 4.6.0)
Steps to reproduce the behavior
Configure plugin for an existing collection, for exemple with: /[Title]
Edit content on an existing element of the collection.
Let the url generation on autogenerated
An url is generated (visible in the alises list) but using API the element is not found.
Return on the element, the input where the alias should be visible is empty.
Make change (but not in the title) and save.
A new alias is generated (title-0) but still not accessible via API (not found error)
When I fetch all elements of the collection the property url_path_id is null
When creating a new element the alias is saved correctly and accessible via url
Expected behavior
The element should always be accessible using its url

I'm having the same issue; I was able to fix it by manually going into the database and setting url_path_id for each existing item, but I'm not sure why the admin panel was not able to set that up.
Related, it would be very helpful to have the ability to delete (or modify) url paths from the admin page! :)

Hi,
I had the same behavior, but I think it's only happening on content type entries you had before installing the plugin. ie :

create content type article
Add one article, "Hello World"
Realise you didn't install the usual plugins, install url-alias
Go back to Article "Hello World" -> can't get any alias to be saved, generate url but assiciation isn't made
Create a new article -> This one works as intended.

I hope this will help reproducing the issue :)

I have tried reproducing in the latest version and it no longer looks like it is an issue (probably fixed by #45).
@Tiffoun, @kzurawel or @Norbz could one of you check if you are still experiencing the issue in version 1.0.0-alpha.10?

Yeah the fix works, though as it's not released just yet the issue is technically still present.
I'll close as soon as I've released.

This issue has been fixed, and released with version 1.0.0-beta.6.


small questions

Hi @JasonShin  how're you??? I'm interested on reasonML (sicerally I just found this) but right now I'm working with nuxtjs developing universal apps (server rendering apps) checking your code seems than would be possible embedded reason code in vue files, which is pretty interesting for me...
my questions are...what is the status about this??? are you using right now???
would be possible integrate this with nuxt???
thank you

@cocodrino
Hey, I'm doing good. At the moment I don't any plans on integrating nuxt.js into reason-vue. I believe once the initial reason-vue MVP is complete, you can drop in nuxt.js reason binding and it should just work.

thank you Jason, this looks really promising, I'll be alert...


OCPBUGS-379: scan: Add conditions to scans

Some users were confused about our re-running feature. They expected the
suites to be re-created every time and the fact that they were not and
the createTimestamp remained constant was causing questions.
Let's add conditions to the scans as well so that it's obvious that the
scan was re-ran.
Jira: OCPBUGS-379

/jira refresh

LGTM

I think this is a nice usability improvement.

To test, create a scan (regardless of the method, can be with a ssb) and then there's two tests to do:

check that .status.conditions exists and that it contains useful information, most importantly when the scan finishes
it should be now possible to do e.g. oc wait --for=condition=ready scan $scan_name

cc @xiaojiey

I tested these FWIW:
$ oc wait --for=condition=processing scan upstream-ocp4-cis
compliancescan.compliance.openshift.io/upstream-ocp4-cis condition met
$ oc wait --for=condition=ready scan upstream-ocp4-cis

I tested these FWIW:
$ oc wait --for=condition=processing scan upstream-ocp4-cis
compliancescan.compliance.openshift.io/upstream-ocp4-cis condition met
$ oc wait --for=condition=ready scan upstream-ocp4-cis

cc @Wiharris @sheriff-rh let me know if the info in this PR is enough for docs-approved. I can also provide the list of available conditions (it's not long) if you think it's needed, but honestly the main driver is to show that the scan had some activity and when for debugging purposes. The oc wait --for commands is a nice syntax sugar, but not strictly needed to document IMO.

/label qe-approved
Details seen from https://privatebin.corp.redhat.com/?a8014970a27a5708#8ty9NfcyQ4LrZARsqVRT617VvF3gGwBc5zcmJmLdbSdb

/retest
AWS timeout issues.


Windows support

On pub.dev the package is advertised that it works on windows but running the example app in this repo on windows it does not appear to be working. In my opinion the windows support from pub.dev should be removed if it is not supported.

@iulian0512
Corrected. Will be updated in an upcoming release.
https://github.com/surfstudio/flutter-swipe-refresh/pull/32


Improve cookie banner research explanation

Reworked research section of the Cookie banner component page based on user feedback:
https://github.com/alphagov/govuk-design-system/issues/1502
User feedback 1 (example text)

"I shared it with the designers...earlier today and it’s resulted in some interesting discussions, one in particular around the content in the banner. We wonder if “…understand how you use the service…” is potentially misleading, as analytics shouldn’t be able to track one user. Maybe something like “We’d also like to store cookies to track visits and find out how people use the website, so we can make improvements.” would be a better option?"

@36degrees Hi Ollie, would you mind taking a look over this for us to make sure the wording is technically correct?

You can preview this change here:
Built with commit f6bb2766cd9b91bf914da09fc9e947fff772746d
https://deploy-preview-1519--govuk-design-system-preview.netlify.app


Add sequence id to acknowledgement results key

Created with this https://p2pvalidator.atlassian.net/browse/NTRN-221 in mind, although it's more an improvement than fix.
Because audit issue was really non existent - relayer cannot submit same message with same sequence id to the chain.
What's there:

added sequence id to ack storage - so we can query acks for exact sequence id we issued
add deposit for .sh scripts (fix)
sudo call returns error if we try to write ack into same (port_id, seq_id) pair - (NOT SURE ABOUT THAT)

Also: See https://github.com/neutron-org/neutron-integration-tests/pull/21 for related integration tests suite updates

test w feat/introduce-sequence-id works flawless


Deadlock in metadata-store callback thread

Describe the bug
This is a deep digging of previous flaky test #12672.
The previous fix are all work around by changing the namespace, reducing messages, setting retentions.
As I can reproduce it locally repeatedly by running the whole test class, I found it's actually a dead lock issue.
As the screenshot showed below, the backlogQuota checking procedure is running on the metadata-store thread ( the thread is in a single thread executor, owned by org.apache.pulsar.metadata.impl.AbstractMetadataStore#executor), and org.apache.pulsar.broker.resources.NamespaceResources#getPolicies is called to get the policy data. NamespaceResources#getPolicies is a blocking method and depends on metadata-store thread to executed to be finished.
So the deadlock happens.
To Reproduce

checkout git-id ffccd46168f473514308903a6719fe01059ce92d
Run test in class PersistentTopicsTest

Expected behavior
In metadata-store thread, we should avoid to get metadata in a blocking way.
Screenshots

Desktop (please complete the following information):

OS: macOS

Additional context
nop.

@linlinnn @codelipenghui PTAL

@Jason918 Looks we are calling a sync method in an async callback https://github.com/apache/pulsar/blob/a2b7cae3cfe8d3776483b1ecaf69af47949b70e1/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/PersistentTopicsBase.java#L2728
Do you want to push a fix?


Incorrect editor colourisation of application in value name

Problem
The text "application" is being coloured blue when your code refers to a let bound value name.

Steps to reproduce

Open an F# file, define and use a value with "application" in it's name.
Machine infos

Operating system: Darwin
Arch: x64
VSCode: 1.23.1
Runtime: .Net
Mono version:

Mono JIT compiler version <IP_ADDRESS> (2018-02/9824e260f56 Mon Apr 30 18:45:52 EDT 2018)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           normal
	SIGSEGV:       altstack
	Notification:  kqueue
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug
	Interpreter:   yes
	LLVM:          yes(3.6.0svn-mono-master/8b1520c8aae)
	GC:            sgen (concurrent by default)

MSBuild version:

Microsoft (R) Build Engine version <IP_ADDRESS> (xplat-master/402b4b23 Wed Mar 28 23:51:55 EDT 2018) for Mono
Copyright (C) Microsoft Corporation. All rights reserved.

CC: @MangelMaxime

Hum this is strange the only rules using application directly in the regex is the one for cexprs
@Krzysztof-Cieslak As a side note, I will probably slow down contribution on the grammar because NDC Oslo is coming and I need to finish slides :)

Slides.... damn, I know i forgot about something

See ionide/ionide-fsgrammar#71.


crash on latest iOS 11.3

All apps I have used is crashing in latest iOS 11.3 & onwards.
Note: I have uploaded apps on iOS 8 before.

Please provide a stack trace for troubleshooting the issue.


Improve completion script option-parameter separator handling

Follow-up issue resulting from discussion on #461:
improve option-parameter separator handling. The current behaviour is that an attached separator prevents the option from being recognized.

Is it possible instead to modify the case statement to append = to options that take an argument: for example:
  case ${PREV_WORD} in
    --directory|-d|--directory=|-d=)

Hmm, had a quick try but it did not seem to work. No time to look deeper now... :-(

Just to note: a Map is a special case that takes a = separator and the arguments on either side may require special handling based on type.


podspec for 0.4.0 no longer available?

Hi,
I just noticed that the spec for 0.4.0 is no longer available on CocoaPods/Specs. Can we add that?

Would appreciate having this fixed.

Should be fixed now?

Yep, it is. Thanks!


File Not Found

Hello Team,
We are suddenly facing slack notification issue on concourse pipelines.
Error: File Not Found
Please guide us how to resolve this issue, all jobs are failing due to this.
Thanks,

did you try deleting the pipeline and set-pipeline?