fix(admin-api): nested parameters can be parsed correctly when using form-urlencoded requests

Summary
When using curl to send a form-urlencoded request with nested parameters, such as
$ curl -X POST http://localhost:8001/parsed_params \
   --data 'items[1]=foo' \
   --data 'items[2]=bar'

the expected response is {"items":["foo","bar"]}, but instead, it returns {"items":{}}.
This is actually an EE issue, but I see that there is a risk of this in CE even though it doesn't currently occur. So I initiated that fix on CE.
The cause of the problem is due to the fact that nested parameters are lost when the decode_args method is called twice, without this fix.
Checklist

[x] The Pull Request has tests
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

Fix FTI-6165

Have you tried using curl to send requests for verification without using a testing framework?

Have you tried using curl to send requests for verification without using a testing framework?

Yes, I did. The behavior is consistent with what I described above


Generate Kibana 6.x.x links in slack alerts

The documentation mentions rule configuration options for generating Kibana links,
only for Kibana version 3 and 4:
https://github.com/Yelp/elastalert/blob/master/docs/source/ruletypes.rst#generate_kibana_link
Is it possible to generate Kibana links for Kibana v6.x.x on Slack alerts?

I am currently working on something to generate links for the discover app if you're interested.  Early stages, but promising so far:
https://github.com/JeffAshton/elastalert/tree/kibana6_discover_query_keys

Thanks, @JeffAshton .

@syst0m :  Here's the PR in case you are interested:
https://github.com/Yelp/elastalert/pull/2471

@JeffAshton Cool, thanks. :)


Fix check for custom-prom.yml

The -f flag is not supported by the shell used, -e is supported.

Good find with the path. -f is supported in Posix sh and works; just tested that. Closing in favor of just fixing the path.


WARNIG/INFO: ssl VERIFYHOST/VERIFYPEER is disabled

The currently used behavior is unsafe.
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 2);
https://github.com/paysafecard/paysafecard-rest_api-php/blob/21e9695016b5acae21eb3fb385fbe2080aae3aaf/payment/PaymentClass.php#L54
https://github.com/paysafecard/paysafecard-rest_api-php/blob/21e9695016b5acae21eb3fb385fbe2080aae3aaf/payment/PaymentClass.php#L55

Thanks Daniel for your review and contribution. We will check your request internally and come back on this.

Fixed.


New software integration issues

Couldn't integrate Github with Dbeaver.
Couldn't download new software.

I don't understand the use-case.
What are you trying to do?


Show style windows - is this possible?

I'm using this for gfx support. In the run_ui closure, I try to show the style editor:
ui.show_style_editor(ui.imgui().style_mut());

It doesn't work when ui isn't &mut. But even if it were, imgui() doesn't take &mut self it seems.

This doesn't seem to be possible at the moment due to Rust borrowing rules. Maybe I should make ImGuiStyle derive Copy so you could store the "temporary" style separately and copy before the UI rendering on each frame.

Heh, I completely forgot that editing the current style directly is actually supported but with a different function :smile:
Try
ui.show_default_style_editor();


Validate Network Subgraph chainId

Resolves #555
TODO:

[x] validate chainId when the indexer syncs the Network Subgraph
[ ] validate chainId when the indexer does not syncs the Network Subgraph

Since it's a startup check, I can test it locally:

[x] valid setup
[ ] invalid: different networks for JSON RPC provider and Network Subgraph
[ ] no-op: no Network Subgrpah deployment hash provided


Fix handling of enum values in JSON request bodies

In Swagger's body schemas, enum and type are mutually exclusive.
Blocks https://github.com/HumanCellAtlas/data-store/pull/1178

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@660b5e1). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #108   +/-   ##
=========================================
  Coverage          ?   87.93%
=========================================
  Files             ?       29
  Lines             ?      978
  Branches          ?        0
=========================================
  Hits              ?      860
  Misses            ?      118
  Partials          ?        0

Impacted Files
Coverage Δ

hca/util/__init__.py
91.69% <100%> (ø)

Continue to review full report at Codecov.

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

LGTM, and I think we should just consider the DCP CLI tests a type of integration test for the DSS.


podman exec -i import large .SQL file got stuck

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
run sudo podman exec --log-level debug -i   on a container with command which need read a large file (about 1.2GB)  into stdin got stuck after few seconds and no error output the the pipeline seems not work too
Steps to reproduce the issue:

run mariadb container

sudo mkdir /tmp/mysql
sudo podman run --name my-mariadb \
-e MYSQL_ROOT_PASSWORD=rootpwd \
-e MYSQL_ROOT_HOST=<IP_ADDRESS> \
-e MYSQL_DATABASE=demo \
-e MYSQL_USER=demo \
-e MYSQL_PASSWORD=demopwd \
-v /tmp/mysql:/var/lib/mysql:z \
-v /etc/localtime:/etc/localtime:ro \
-p <IP_ADDRESS>:3307:3306 \
--mount type=tmpfs,destination=/tmp \
mariadb:10.4.11 \
--character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci

sudo podman logs -f my-mariadb to show the log, ensure the mariadb has started successfully

any *.sql file,  must large than  1GB in order to show the issue.
the larger the better.

try import the sql file (for example: /home/ttys3/backup.20191217-0017.sql) :

sudo podman exec -i my-mariadb sh -c 'exec mysql -uroot -p"$MYSQL_ROOT_PASSWORD" -h <IP_ADDRESS> --protocol=tcp --port=3306 demo' < /home/ttys3/backup.20191217-0017.sql

Describe the results you received:
run podman with  the debug level logging enabled so we can see details:
sudo podman exec --log-level debug -i my-mariadb sh -c 'exec mysql -uroot -p"$MYSQL_ROOT_PASSWORD" -h <IP_ADDRESS> --protocol=tcp --port=3306 demo' < /home/ttys3/backup.20191217-0017.sql

we'll see the following output:
DEBU[0000] Reading configuration file "/usr/share/containers/libpod.conf"
DEBU[0000] Merged system config "/usr/share/containers/libpod.conf": &{{false false false false false true} 0 {   [] [] []}  docker://  crun map[crun:[/usr/bin/crun /usr/sbin/crun /usr/local/bin/crun /usr/local/sbin/crun /sbin/crun /bin/crun /run/current-system/sw/bin/crun] kata-fc:[/usr/bin/kata-fc] kata-qemu:[/usr/bin/kata-qemu] kata-runtime:[/usr/bin/kata-runtime] runc:[/usr/bin/runc /usr/sbin/runc /usr/local/bin/runc /usr/local/sbin/runc /sbin/runc /bin/runc /usr/lib/cri-o-runc/sbin/runc /run/current-system/sw/bin/runc]] [crun runc] [crun] [] [/usr/libexec/podman/conmon /usr/local/libexec/podman/conmon /usr/local/lib/podman/conmon /usr/bin/conmon /usr/sbin/conmon /usr/local/bin/conmon /usr/local/sbin/conmon /run/current-system/sw/bin/conmon] [PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin] systemd   /var/run/libpod -1 false /etc/cni/net.d/ [/usr/libexec/cni /usr/lib/cni /usr/local/lib/cni /opt/cni/bin] podman []   k8s.gcr.io/pause:3.1 /pause false false  2048 shm    false false}
DEBU[0000] Using conmon: "/usr/bin/conmon"
DEBU[0000] Initializing boltdb state at /var/lib/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /var/lib/containers/storage
DEBU[0000] Using run root /var/run/containers/storage
DEBU[0000] Using static dir /var/lib/containers/storage/libpod
DEBU[0000] Using tmp dir /var/run/libpod
DEBU[0000] Using volume path /var/lib/containers/storage/volumes
DEBU[0000] Set libpod namespace to ""
DEBU[0000] No store required. Not opening container store.
DEBU[0000] Initializing event backend journald
DEBU[0000] using runtime "/usr/bin/crun"
WARN[0000] Error initializing configured OCI runtime kata-runtime: no valid executable found for OCI runtime kata-runtime: invalid argument
WARN[0000] Error initializing configured OCI runtime kata-qemu: no valid executable found for OCI runtime kata-qemu: invalid argument
WARN[0000] Error initializing configured OCI runtime kata-fc: no valid executable found for OCI runtime kata-fc: invalid argument
DEBU[0000] using runtime "/usr/bin/runc"
INFO[0000] Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman-bridge.conflist
WARN[0000] Default CNI network name podman is unchangeable
DEBU[0000] Creating new exec session in container aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127 with session id 0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573
DEBU[0000] /usr/bin/conmon messages will be logged to syslog
DEBU[0000] running conmon: /usr/bin/conmon               args="[--api-version 1 -s -c aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127 -u 0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573 -r /usr/bin/crun -b /var/lib/containers/storage/overlay-containers/aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127/userdata/0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573 -p /var/lib/containers/storage/overlay-containers/aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127/userdata/0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573/exec_pid -l k8s-file:/var/lib/containers/storage/overlay-containers/aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127/userdata/0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573/exec_log --exit-dir /var/lib/containers/storage/overlay-containers/aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127/userdata/0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573/exit --socket-dir-path /var/run/libpod/socket --log-level debug --syslog -i -e --exec-attach --exec-process-spec /var/lib/containers/storage/overlay-containers/aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127/userdata/0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573/exec-process-055699493]"
INFO[0000] Running conmon under slice machine.slice and unitName libpod-conmon-aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127.scope
WARN[0000] Failed to add conmon to systemd sandbox cgroup: Unit libpod-conmon-aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127.scope already exists.
DEBU[0000] Attaching to container aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127 exec session 0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573
DEBU[0000] connecting to socket /var/run/libpod/socket/0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573/attach
DEBU[0000] Received: 0
DEBU[0000] Received: 51652
[conmon:d]: exec with attach is waiting for start message from parent
[conmon:d]: exec with attach got start message from parent
DEBU[0000] Successfully started exec session 0ddacf905be885f3b9f0ce3cf493ac15a49c49b10539cc1f4906194c435f7573 in container aeb3db6100780de3519b9c3dd4130cca3bd75a7dcf283844dc36e6a296fe8127
--------------
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */
--------------

--------------
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */
--------------

--------------
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */

...

and then, no output anymore.  the SQL file content got ouput because we have --verbose param passsed to mysql command so that we can see the importing job is working or not.
but after a few seconds, the output stopped and podman exec got stucked. not error ouput.
and, podman never exit until you send Ctrl + C
Describe the results you expected:
should run mysql command and import the .sql file without error
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:            1.8.0
RemoteAPI Version:  1
Go Version:         go1.13.6
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.13.6
  podman version: 1.8.0
host:
  BuildahVersion: 1.13.1
  CgroupVersion: v2
  Conmon:
    package: conmon-2.0.10-2.fc31.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.10, commit: 6b526d9888abb86b9e7de7dfdeec0da98ad32ee0'
  Distribution:
    distribution: fedora
    version: "31"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  MemFree:<PHONE_NUMBER>
  MemTotal:<PHONE_NUMBER>2
  OCIRuntime:
    name: crun
    package: crun-<IP_ADDRESS>-1.fc31.x86_64
    path: /usr/bin/crun
    version: |-
      crun version <IP_ADDRESS>
      commit: cd7cea7114db5f6aa35fbb69fa307c19c2728a31
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  SwapFree:<PHONE_NUMBER>8
  SwapTotal:<PHONE_NUMBER>8
  arch: amd64
  cpus: 12
  eventlogger: journald
  hostname: 8700k.localhost
  kernel: 5.5.7-200.fc31.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.0-20.1.dev.gitbbd6f25.fc31.x86_64
    Version: |-
      slirp4netns version 0.4.0-beta.3+dev
      commit: bbd6f25c70d5db2a1cd3bfb0416a8db99a75ed7e
  uptime: 23h 39m 53.65s (Approximately 0.96 days)
registries:
  docker.io:
    Blocked: false
    Insecure: false
    Location: dockerhub.azk8s.cn
    MirrorByDigestOnly: false
    Mirrors: null
    Prefix: docker.io
  search:
  - docker.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - quay.io
store:
  ConfigFile: /home/ttys3/.config/containers/storage.conf
  ContainerStore:
    number: 0
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.5-2.fc31.x86_64
      Version: |-
        fusermount3 version: 3.6.2
        fuse-overlayfs: version 0.7.5
        FUSE library version 3.6.2
        using FUSE kernel interface version 7.29
  GraphRoot: /home/ttys3/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 0
  RunRoot: /run/user/1000
  VolumePath: /home/ttys3/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.8.0-2.fc31.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
physical machine with 32GB DDR4 memory
CPU: i7 8700K with 6 core 12 threads run @ 4.7GHz
nvme disk

Likely related to https://github.com/containers/libpod/issues/5046

@mheon  I've updated the issue.  provided info about run sudo podman exec  with --log-level debug

@mheon  Yes, seems the stdin input got truncated, and mysql  command is waiting for data forerver but podman does not git it anymore.

I also encountered this while passing a dump to a db through stdin.
Simple to replicate the issue with:
Small file is passed through nicely
$ sha256sum smallfile
95540861de1b1e09c1cb0c0fa9b8f282997ab8da29da7d6dc49dbc52ad39a05f  smallfile
$ cat smallfile | podman run --rm -i alpine:latest sha256sum
95540861de1b1e09c1cb0c0fa9b8f282997ab8da29da7d6dc49dbc52ad39a05f  -

But a large one does not have the same content
$ sha256sum largefile
850bae09e12d13d6060133f3135d50174cc25901844754f27efedda95ade4b57  largefile
$ cat largefile | podman run --rm -i alpine:latest sha256sum
d71676670c100658a023e7bcdc2b599e21cfb22c1b3e40d375ea5d66f3d2def0  -

Where largefile is about 1,4 GB
Fedora 31 and podman 1.8.0

I hope https://github.com/containers/libpod/issues/5046 solved this one also, but haven't tested

Ok reopen if it has not.


Perf FileSystem Interface

Some code I wrote when benchmarking different client implementations in Tachyon Perf (specifically AbstractTFS and Hadoop's File System client).
The overall idea was to extract the current implementation of PerfFileSystem and make it into an interface, PerfFS. Then implement that interface with various different clients (ie. TachyonPerfFS, THCIPerfFS). This will allow tests to be made using the common interface and be extended to a variety of client implementations.
The filesystem to be used is specified through the config TACHYON_PERF_UFS. Currently it is just a string matching switch in PerfConstants, but it can be refactored to be more versatile if needed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/2961/
Test PASSed.

@RongGu  @swatDong

Leave comment about 'TACHYON_PERF_UFS', overall LGTM.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/2979/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/2978/Failed Tests: 1org.tachyonproject:tachyon-underfs-hdfs: 1tachyon.master.MasterClientTest.openCloseTest
Test FAILed.

+1 LGTM


minor correction to README example

would give "cannot use vl (type api.ValueList) as type *api.ValueList in argument to exec.Putval.Write" before

Thanks @marthjod!


[MongoPlugin] java.lang.String cannot be cast to org.bson.types.ObjectId

Environment
Mac OS X El Capitan
Idea 2016.3 and 2016.2
Mongo Plugin: 0.9.2016
Java 1.8.0_74
How to reproduce
I have a collection with String type "_id". When I Edit a document and hit Save button I get the java.lang.String cannot be cast to org.bson.types.ObjectId.

Hi,
_id is usually for ObjectId.

Hi,
I don't agree with your proposals. I downgraded to version 0.8.1 of this plugin and it is working correctly. According to the MongoDB documentation:

The field name _id is reserved for use as a primary key; its value must be unique in the collection, is immutable, and may be of any type other than an array.

See also
https://docs.mongodb.com/manual/core/document/
http://stackoverflow.com/questions/11090446/can-i-use-string-as-id-type-for-mongodb-document
Cheers and thanks for your support.
Josef

Hi,
Could you please add the stackstrace?
Thanks

Hi David,
Sorry, but there is no StackTrace in the IntelliJ IDEA log files. The error was shown on the screen with red colour only and the given message was logged in the Event Log view as well. Can't you reproduce the error as described above in the issue?

Sure. Will check tomorrow.

Hi,
There is a SNAPSHOT build available on the home page of the project. Please confirm it fixes the issue you encounter, or reject ;).

Hi Dave,
Thank you for a quick fix, I shall confirm that the issue doesn't occur on the 0.10.0-SNAPSHOT build with Idea 2016.3 any more.
Cheers


Trace: CCT

implementation of cct for otf2 reader
verified with external tools like vampir for a couple of different traces

will fail tests until graph change is merged

Rename columns. Location -> Process ID and so on

Lets make the CCT construction optional (dependent on user input)


Remove Image button fails without error message

First of all, great work with this dockerui app! :tada:
I found a bug when clicking on the "Remove Image" button.
web console
Error: [$resource:badcfg] Error in resource configuration for action `remove`. Expected response to contain an array but got an object

Request
Request URL:http://localhost:9000/dockerapi/images/sha256:e713b5e836513871b647b658cd09a78537b47375f5f1402f7085ac773ec629c4
Request Method:DELETE
Status Code:200 OK

Response
conflict: unable to delete e713b5e83651 (must be forced) - image is being used by stopped container e96cb9bcc278

I believe the bug is cause by the string being returned when the client is expecting an array.
However I'm not familiar enough with the code to fix it at this time.

What DockerUI version are you running? If it's not the latest, give  1.10.0-beta a try, f353dc2c419664bc8aa5523bad6d9af7025106ee should've resolved this.

I was running latest tag.
I don't see a 1.10.0-beta but I tried with 0.10.0-beta and got the same problem using Action > Remove since there is no longer a Remove Image button.

Whoops, I meant 0.10.0-beta. There should still be a Remove Image button on the bottom of image pages:

But I'm seeing the same error, the global interceptor didn't catch this because it checks for Conflict. case sensitively :disappointed:

In the fix f353dc2, response.data.startsWith('Conflict.') returns false for response conflict: unable to delete e713b5e83651 (must be forced) - image is being used by stopped container e96cb9bcc278. I met with the same issue on Docker API Version: 1.23 UI Version: v0.10.1-beta.
By the way, thanks for great dockerui app!

Fixed by #211


cilium-agent crash and unable to recover when enable-l7-proxy is toggled

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Cilium-agent crashes and unable to recover, as explained below,

When "enable-l7-proxy: true" and using DNS proxy to add L3/L4 rules for the toFQDNs, the FQDN cache gets populated as lookup entries and the policies were working ok.
When "enable-l7-proxy: false" on the same daemonset and rolling restart the cilium agents, cilium-agent was healthy for a brief moment until the "FQDN garbage collector" kicked in, after which it bails out on "panic: runtime error: invalid memory address or nil pointer dereference".
Noticed that this happened only on some of the nodes, the ones that had entries in the FQDN cache, and those nodes never recovered.
Also noticed that the same behaviour can be reproduced by cilium fqdn cache clean which forces the crash.
FQDN garbage collector was started on the nodes that had been crashing, whereas on the other nodes only the conntrack garbage collector was running from startup.
Reverting to "enable-l7-proxy: true", all the nodes were back healthy.

cc: @supreethrao
Cilium Version
Versions:

1.9.8
1.10.5

Kernel Version
Linux 5.4.0-1054-aws #57~18.04.1-Ubuntu SMP x86_64 GNU/Linux
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.14", GitCommit:"d2a081c8e14e21e28fe5bdfa38a817ef9c0bb8e3", GitTreeState:"clean", BuildDate:"2020-08-13T12:24:51Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
No response
Relevant log output
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x221b242]

goroutine 1953 [running]:
github.com/cilium/cilium/pkg/proxy.(*Proxy).UseCurrentNetworkPolicy(0x0, 0x2f450f0, 0xc000efc000, 0xc000d35bc0, 0xc0027e1300)
        /go/src/github.com/cilium/cilium/pkg/proxy/proxy.go:656 +0x22
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).useCurrentNetworkPolicy(0xc000efc000, 0xc0027e1300)
        /go/src/github.com/cilium/cilium/pkg/endpoint/policy.go:167 +0x8f
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).ApplyPolicyMapChanges(0xc000efc000, 0xc0027e1300, 0x0, 0x0)
        /go/src/github.com/cilium/cilium/pkg/endpoint/bpf.go:1217 +0x138
github.com/cilium/cilium/pkg/endpointmanager.(*EndpointManager).UpdatePolicyMaps.func2(0xc000702570, 0xc0027e1300, 0xc000702580, 0xc000efc000)
        /go/src/github.com/cilium/cilium/pkg/endpointmanager/manager.go:174 +0x65
created by github.com/cilium/cilium/pkg/endpointmanager.(*EndpointManager).UpdatePolicyMaps
        /go/src/github.com/cilium/cilium/pkg/endpointmanager/manager.go:171 +0x1ae
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x221b242]

goroutine 1954 [running]:
github.com/cilium/cilium/pkg/proxy.(*Proxy).UseCurrentNetworkPolicy(0x0, 0x2f450f0, 0xc000efc900, 0xc001798140, 0xc0027e1300)
        /go/src/github.com/cilium/cilium/pkg/proxy/proxy.go:656 +0x22
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).useCurrentNetworkPolicy(0xc000efc900, 0xc0027e1300)
        /go/src/github.com/cilium/cilium/pkg/endpoint/policy.go:167 +0x8f
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).ApplyPolicyMapChanges(0xc000efc900, 0xc0027e1300, 0x0, 0x0)
        /go/src/github.com/cilium/cilium/pkg/endpoint/bpf.go:1217 +0x138
github.com/cilium/cilium/pkg/endpointmanager.(*EndpointManager).UpdatePolicyMaps.func2(0xc000702570, 0xc0027e1300, 0xc000702580, 0xc000efc900)
        /go/src/github.com/cilium/cilium/pkg/endpointmanager/manager.go:174 +0x65
created by github.com/cilium/cilium/pkg/endpointmanager.(*EndpointManager).UpdatePolicyMaps
        /go/src/github.com/cilium/cilium/pkg/endpointmanager/manager.go:171 +0x1ae

Anything else?
Based on the source, it looks like,

envoy control plane XDS server is started only if L7 proxy is enabled. https://github.com/cilium/cilium/blob/fcd00390c30c6eeffbe2fefa81d5b22e59397297/daemon/cmd/daemon.go#L579
this condition should be calling !isProxyDisabled() on the endpoint instead of doing a nil check on the interface because the type exists but value is nil,
https://github.com/cilium/cilium/blob/c78195592e65349c72724784c834cd8cd5b20218/pkg/endpoint/policy.go#L154

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for the report! Do you want to send a pull request with the fix?


Program instaquits when trying to create a new file (empty, glsl, etc)

Just downloaded it last night, and I know it's still relatively new, but I'm not quite sure why the program instaquits while trying to create a new file.

Thanks for reporting.
I am going to publish a really big update tomorrow. Will you be able to test it then? If it still happens in the updated version I will try to fix it... Although I think I have already fixed it

Yeah sure, just let me know. Will it be released in a binary ?

I just released the update but unfortunately no binaries until tomorrow/friday - I still need to fix/implement few small features/bugs.

I have released the binaries - could you test the fixes?

In terms of the new binary you just released, it didnt work.

I'm having the same issue. I use the current release binaries on Win 10 x64.

Thanks for reporting... I apologize for this :(.. AFAIK it worked normally on Windows yesterday (or few days ago) but I have made some modifications to the source code since then and sadly haven't tested on Windows... My fault and I apologize for this so badly... I will try to publish a hotfix tomorrow as fast as I can so please stay tuned :/

Thanks for reporting... I apologize for this :(.. AFAIK it worked normally on Windows yesterday (or few days ago) but I have made some modifications to the source code since then and sadly haven't tested on Windows... My fault and I apologize for this so badly... I will try to publish a hotfix tomorrow as fast as I can so please stay tuned :/

No worries, it's an impressive tool nonetheless. Do note that version 1.0 has the same problem for me so the issue might be something different.

Thank you for the reports @valenotary and @CptPotato ! I have just found the cause of this error!!!
It is located on this line:
https://github.com/dfranx/SHADERed/blob/4e62d5a06592de7c8a4bef7f4eb0bd7cbae1ab2f/GUIManager.cpp#L600
where I convert the message output window to PreviewUI window and call PreviewUI's methods - thus it crashes! I will push a fix later today (in binary version too)!

Could you please test the fix for this @valenotary @CptPotato and confirm that it is working now so that I can close the issue? I updated the release for v1.1 so now you can download the binaries

looks like this fixed the issue, thanks!

np! closing


diagnose give summary at end; if no problems found, say so

Summary:
diagnose command succeeds silently; very confusing to users who expect something.

addressed by https://github.com/stan-dev/cmdstan/pull/684


Better Error Handling

I'm trying to upload my project to Bintray, and getting this error:
Caused by: groovyx.net.http.HttpResponseException: Method Not Allowed
    at groovyx.net.http.HTTPBuilder.defaultFailureHandler(HTTPBuilder.java:652)
    at groovyx.net.http.HTTPBuilder.doRequest(HTTPBuilder.java:508)
    at groovyx.net.http.HTTPBuilder.doRequest(HTTPBuilder.java:441)
    at groovyx.net.http.HTTPBuilder.request(HTTPBuilder.java:373)
    at groovyx.net.http.HTTPBuilder$request.call(Unknown Source)
    at com.jfrog.bintray.gradle.BintrayUploadTask$_bintrayUpload_closure4.doCall(BintrayUploadTask.groovy:151)
    at com.jfrog.bintray.gradle.BintrayUploadTask$_bintrayUpload_closure4.doCall(BintrayUploadTask.groovy)
    at com.jfrog.bintray.gradle.BintrayUploadTask.bintrayUpload(BintrayUploadTask.groovy:192)
    at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:63)
    ... 50 more

Looking at this line of code, it's not clear what the problem is:
https://github.com/bintray/gradle-bintray-plugin/blob/master/src/main/groovy/com/jfrog/bintray/gradle/BintrayUploadTask.groovy#L151
Is there any suggestion how to do identify what the problem is? If so, I'll add some improved error handling and submit an pull request.

我出现了相同的问题，而且我确定我的bintray账号密码并没有错

@scanor, your last comment is not readable.
@RobertFischer, can you please share a sample project that reproduces this error? I'm not sure we can guess the cause of the problem without it.
Thanks.

@eyalbe4  I,m sorray about my poor English, I can read English ,but I can't write. My last comment mean that I am sure about my bintray account and password are right. But In some computer,I can upload success  while some can not.

I have the same problem, This is my project https://github.com/Omico/SetupWizardLib

我也遇到相同的问题

Caused by: groovyx.net.http.HttpResponseException: Method Not Allowed
at groovyx.net.http.HTTPBuilder.defaultFailureHandler(HTTPBuilder.java:651)
at groovyx.net.http.HTTPBuilder$1.handleResponse(HTTPBuilder.java:503)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044)
at groovyx.net.http.HTTPBuilder.doRequest(HTTPBuilder.java:515)
at groovyx.net.http.HTTPBuilder.doRequest(HTTPBuilder.java:434)
at groovyx.net.http.HTTPBuilder.request(HTTPBuilder.java:366)
at groovyx.net.http.HTTPBuilder$request$0.call(Unknown Source)
at com.jfrog.bintray.gradle.BintrayUploadTask$_bintrayUpload_closure5.doCall(BintrayUploadTask.groovy:249)
at com.jfrog.bintray.gradle.BintrayUploadTask$_bintrayUpload_closure5.doCall(BintrayUploadTask.groovy)
at com.jfrog.bintray.gradle.BintrayUploadTask.bintrayUpload(BintrayUploadTask.groovy:459)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
... 77 more

12:45:41.926 [INFO] [org.gradle.api.Task] Gradle Bintray Plugin version: 1.8.0
12:45:41.930 [INFO] [com.jfrog.bintray.gradle.BintrayHttpClientFactory] Using proxy null:@mirrors.zzu.edu.cn:80
12:45:41.932 [DEBUG] [org.gradle.model.collection.internal.BridgedCollections] Ignoring element 'tasks' added to 'bintrayUpload' after it is closed.
12:45:41.935 [DEBUG] [groovyx.net.http.HTTPBuilder] HEAD https://api.bintray.com/packages/GPL_R/app_core/core
12:45:41.943 [DEBUG] [org.apache.http.impl.conn.BasicClientConnectionManager] Get connection for route {tls}->http://mirrors.zzu.edu.cn:80->https://api.bintray.com
12:45:42.514 [DEBUG] [org.apache.http.impl.conn.DefaultClientConnectionOperator] Connecting to mirrors.zzu.edu.cn:80
12:45:42.998 [DEBUG] [org.apache.http.client.protocol.RequestAuthCache] Auth cache not set in the context
12:45:42.998 [DEBUG] [org.apache.http.client.protocol.RequestProxyAuthentication] Proxy auth state: UNCHALLENGED
12:45:42.998 [DEBUG] [org.apache.http.impl.conn.DefaultClientConnection] Sending request: CONNECT api.bintray.com:443 HTTP/1.1
12:45:43.486 [DEBUG] [org.apache.http.impl.conn.DefaultClientConnection] Receiving response: HTTP/1.1 405 Method Not Allowed
12:45:43.486 [DEBUG] [org.apache.http.client.protocol.ResponseProcessCookies] Cookie spec not specified in HTTP context
12:45:43.486 [DEBUG] [org.apache.http.impl.conn.DefaultClientConnection] Connection <IP_ADDRESS>:50575<-><IP_ADDRESS>:80 closed
12:45:43.486 [DEBUG] [org.apache.http.impl.client.DefaultHttpClient] CONNECT refused by proxy: HTTP/1.1 405 Method Not Allowed
12:45:43.486 [DEBUG] [org.apache.http.impl.conn.BasicClientConnectionManager] Releasing connection org.apache.http.impl.conn.ManagedClientConnectionImpl@2846e903
12:45:43.487 [DEBUG] [org.apache.http.impl.conn.BasicClientConnectionManager] Connection can be kept alive for<PHONE_NUMBER>854775807 MILLISECONDS
12:45:43.487 [DEBUG] [groovyx.net.http.HTTPBuilder] Response code: 405; found handler: org.codehaus.groovy.runtime.MethodClosure@71c9890
12:45:43.489 [DEBUG] [org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter] Removed task artifact state for {} from context.
12:45:43.489 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Finished executing task ':core:bintrayUpload'
12:45:43.489 [LIFECYCLE] [class org.gradle.internal.buildevents.TaskExecutionLogger] :core:bintrayUpload FAILED


Resample also does transpose

https://github.com/phenology/springtime/blob/dd6020add46bb95de96c1d7369067e31e7523e1b/src/springtime/main.py#L131-L146
It is not clear that resample does more than just resample.

Resample was moved from a generic step to a dataset-specific step, so this is no longer the case (#192)


Fix broadcast function

This fixes the broadcast function so that a sender can be provided.
It also renames the parameter name room to room_name as it was clashing with the function name.
Fixes #22

May want to reset your branch to not include the commits that are already published onto main.

We still need some function or other to broadcast all current code from Client A to another client when they connect.
You'll see here on the right (Client B) doesn't receive any of the previous data from Client A

We still need some function or other to broadcast all current code from Client A to another client when they connect. You'll see here on the right (Client B) doesn't receive any of the previous data from Client A

I think we should worry about this after we implement the text editor because we will need to send to the new client only specific types of events (for example we don't want to send cursor movement events, but we only want to send the code).


File Provider errors out on middleware listing

Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[X] No

What did you do?
Configured the middlewares like so:
[http.routers]
  [http.routers.synology]
      entryPoints = ["https"]
      # middlewares = ["compress", "redirect", "forward-auth"]
      rule = "Host(`synology.sub.domain.com`)"
      service = "synology"

What did you expect to see?
A working *file.Provider
What did you see instead?
In the logs and in the rawJSON output from Traefik I can see that the file.Provider is not loading properly. Removing this middlewares definition makes the issue go away.
It seems like either EntryPoints should match Middlewares or vice versa?
https://github.com/containous/traefik/blob/v2.0/pkg/config/dyn_config.go#L16-L17
Output of traefik version: (What version of Traefik are you using?)
v2.0.0-alpha4

What is your environment & configuration (arguments, toml, provider, platform, ...)?
[global]
  Debug = true
  SendAnonymousUsage = false

[api]

[providers]
  [providers.file]
    watch=true

  [providers.docker]
    endpoint = "unix:///var/run/docker.sock"
    domain = "sub.domain.com"
    watch = true
    exposedByDefault = false

[entryPoints]
  [entrypoints.http]
    address = ":80"

  [entrypoints.https]
    address = ":443"

[http.routers]

  [http.routers.synology]
      entryPoints = ["https", "http"]
      # middlewares = ["compress", "redirect", "forward-auth"]
      rule = "Host(`synology.sub.domain.com`)"
      service = "synology"

  [http.middlewares]
    [http.middlewares.compress.compress]

    [http.middlewares.redirect.redirectScheme]
      scheme = "https"

    [http.middlewares.forward-auth.forwardAuth]
      address = "https://traefik-forward-auth:4181"
      authResponseHeaders = ["X-Forwarded-User"]

    [http.services.synology]
      [http.services.synology.LoadBalancer]
          [[http.services.synology.LoadBalancer.servers]]
            url = "http://<IP_ADDRESS>:5000"
            scheme = "http"
            weight= 1

[acme]
  acmeLogging = true
  email =<EMAIL_ADDRESS>  storage = "/acme.json"
  onHostRule = true
  entryPoint = "https"
  [acme.dnsChallenge]
    provider = "a_well_known_provider"

  [[acme.domains]]
    main = "sub.domain.com"
  [[acme.domains]]
    main = "*.sub.domain.com"

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
With the middlewares included in config
time="2019-05-31T22:16:48Z" level=error msg="Cannot start the provider *file.Provider: toml: cannot load TOML value of type string into a Go slice"

Also what kind of test framework does traefik use? Typically I see _test.go files in the same directory. Was trying to see where toml file validation is done.

hello,
with the TOML file you provided I do not reproduce the problem.

Forgot to mention I'm starting traefik via docker-compose:
traefik:
    container_name: traefik
    image: traefik:v2.0
    ports:
      - "80:80"
      - "443:443"
      - "8080:8080"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /nfs/docker/traefik/traefik.toml:/traefik.toml
      - /nfs/docker/traefik/acme.json:/acme.json
      - /nfs/docker/traefik/access.log:/access.log
      # - /nfs/docker/traefik/traefik.log:/traefik.log
    restart: always
    env_file: ./traefik.env
    labels:
      - "traefik.enable=false"
    dns:
      - <IP_ADDRESS>
      - <IP_ADDRESS>
      - <IP_ADDRESS>

Hi @dalanmiller , do you have the same error if your traefik.toml is stored on the local host machine (instead of the /nfs directory which looks like a NFS mountpoint)?

@dduportal good 👁 ! Can confirm that trying to spin up Traefik locally with a non-mounted traefik.toml file arrives at the same result. I believe there to be something wrong with the parsing of the middlewares declaration:
      middlewares = ["compress", "redirect", "forward-auth"]

Also tried:
      middlewares = "compress, redirect, forward-auth"

Also tried the following, thinking the hyphen was an issue:
      middlewares = ["compress", "redirect"]

.... I found the problem!
I had added another http.router and had defined entryPoints with solely a string value instead of an array with a single item. All set here.


icacls crashes

icacls is not functioning -- exists in the system directory but crashes at execution

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

ID: 0a990d09-b5b1-3aba-de57-0aec79c12784
Version Independent ID: 36d90c17-ba95-4ed6-de9d-f379dcad6c4d
Content: icacls
Content Source: WindowsServerDocs/administration/windows-commands/icacls.md
Service: windows-server-threshold
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

@sjakob52 : Sorry that it has taken so long to post a reply to your issue ticket. Please note that this repository is intended for improvement of the Microsoft Docs documentation pages, not so much for troubleshooting software or the OS itself. I can only assume that your issue has already been resolved via other resources, so just to let you know what I would have suggested if I had been around to notice this ticket earlier:
You may want to look elsewhere for answers, unless you have suggestions for improving one or more specific pages in the MS Docs repository.
Disclaimer: I am not affiliated with Microsoft or the Microsoft Docs teams here on GitHub.
The intention of this repository is to improve on the existing documentation by providing the users a way to report factual errors, improvement suggestions and request updates for new versions.
The MS Docs team members might not have time to answer your question, both due to the small size of the team and the big workload.
Try the following resources to get in touch with users who may be able to help you:

TechNet forums: https://social.technet.microsoft.com/Forums/en-US/home
MSDN: https://social.msdn.microsoft.com/Forums/en-US/home
Microsoft Community: https://answers.microsoft.com/

I will proceed to close this issue ticket now, but if you find that there are any errors, discrepancies or details in need of correction, please open a new ticket to report the faulty parts of the document page itself. Thank you for using the Microsoft Docs documentation pages (even though it did not resolve your issue back in 2018).

#please-close


system_gateways, default gateway switching based on a set 'priority'

This is interesting but still seems like a half-measure to fix https://redmine.pfsense.org/issues/4507. Having to visit each of the gateways and set a priority seems counterintuitive and difficult for the user.
A better way would be to allow a single gateway group to be marked as default when gateway switching is enabled. Groups already have a familiar GUI interface for tiers and functions for finding current active gateways. That way the current behavior could be preserved if there was no default group.

fyi i'm working on the proposed changes.. Will hopefully have some progress in a week or two..

@PiBa-NL Thanks!

Closing this one, as a different/better implementation is in progress https://github.com/pfsense/pfsense/pull/3781


fix: Added missing inherit_hide_question_number in hide question number sample

Nice! I was wondering what was going on in the hide question number sample activity. I'll go ahead and do the merge. Thanks, @dougmartin!


Fix logging bits

Adding documentation for Logging trait
Removing unnecessary part of the log
Getting rid of newlines in log messages
Updating akka to get rid of an unnecessary log message on stdout
Fix Package error message
Surface proper message when rule update failed due to trigger absence
Adding new exception type, fixing entity conformance logs
Report invoke being too big properly, needs to be short-circuited
Refactoring remote entitlement service

more dense code
adjust log levels related to entitlement
surface errors reported by the remote entitlement service

Fix loglevel of conflicts on delete
Fix loglevel for trigger fire iff action was deleted

Fixes #1045
Fixes #1044
Every commit fixes exactly one thing for easier reviewability.

Memo to self: Implement tests for:

Rule activation after deleting the trigger associated should surface a 404 "Only rules with existing triggers can be activated"
GET on an action/trigger/rule should return a 409 Conflict if the name is tied to an entity of different type
POST to action/trigger with a payload being too big should result in 413

PG1 174 was green


Style variables correctly in functions

Question-mark characters should only be styled as operators within triple patterns. For example the command
SELECT * WHERE { BIND(?A+?B AS ?C) }
should not have the "+?" sequence styled as "operator".  NB the problem does not occur if there is a space between these two characters. With the fix, "?A" and "?B" will both be styled as variable-2 (and "+" as operator).
By processing operators characters one at a time,  the existing code on line 40 to zealously interpret anything beginning with '?' as a variable can run in this case. We also don't need one of my earlier fixes that prevented "^^<" being treated as a three operators rather than two operators then the start of a verbose turtle-encoded IRI.
NB Line 40 actually causes a false positive in the case where the '?' appears in a triple pattern as a property path operator: this fix does not address this existing bug: it is quite complicated as '?' can appear in both variables and property paths while the parser is in the "pattern" state.

This looks like it removes some code that probably had a reason to be there. Does just removing ? from operatorChars not solve the problem?

Thanks for the detailed explanation! Merged.


Plotman (k33) keeps making plots for a -d storage disk that's already full - it even reports it as full!

Per title...
(venv) roet@Lovecraft:~/chia-blockchain$ plotman dsched
  /mnt/farm/HDD02/Plots_OK/pooled/plotman : 5:0
  /mnt/farm/HDD06/Plots_OK/pooled/plotman : 4:1
  /mnt/farm/HDD00/Plots_OK/pooled/plotman : 3:2
  /mnt/farm/HDD01/Plots_OK/pooled/plotman : 3:4
  /mnt/farm/HDD03/Plots_OK/pooled/plotman : 3:3
  /mnt/farm/HDD05/Plots_OK/pooled/plotman : 3:2
  /mnt/farm/HDD07/Plots_OK/pooled/plotman : 2:5
(venv) roet@Lovecraft:~/chia-blockchain$ plotman dirs
         tmp             ready         phases
  /home/roet/tmp/ssd00      OK   1:5 2:5
  /home/roet/tmp/ssd01      OK   1:3 2:2 3:3 4:1 5:0
 /mnt/4x_volume/run-22      OK   1:2 1:6 3:2 3:6
/mnt/nvme_vol/nvme_0-0      --   1:3 1:5 2:6 3:4
/mnt/nvme_vol/nvme_0-1      OK   1:4 2:4 3:2 5:0
           /mnt/ssd03/      OK   1:1 2:4 5:0
                  dst                     plots   GBfree         inbnd phases         pri
/mnt/farm/HDD00/Plots_OK/pooled/plotman   45      5898     1:5 2:4 3:2                95
/mnt/farm/HDD01/Plots_OK/pooled/plotman   66      1200     1:3 2:4 3:4                112
/mnt/farm/HDD02/Plots_OK/pooled/plotman   71      0        1:5 2:6 [+1] 5:0 5:0 5:0   106
/mnt/farm/HDD03/Plots_OK/pooled/plotman   46      5489     1:3 2:2 3:3                96
/mnt/farm/HDD05/Plots_OK/pooled/plotman   65      1424     1:2 1:6 3:2                115
/mnt/farm/HDD06/Plots_OK/pooled/plotman   35      8152     1:1 4:1                    53
/mnt/farm/HDD07/Plots_OK/pooled/plotman   36      7927     1:4 2:5                    86

HDD02 is full as can be, even when I started plotman interactive: the disk already was full! Yet it started plotting lots of new plots to it...
(venv) roet@Lovecraft:~/chia-blockchain$ cat ~/.config/plotman/plotman.yaml
# Default/example plotman.yaml configuration file
# k temp size calculations on https://plot-plan.chia.foxypool.io/

# https://github.com/ericaltendorf/plotman/wiki/Configuration#versions
version: [2]

logging:
        # One directory in which to store all plot job logs (the STDOUT/
        # STDERR of all plot jobs).  In order to monitor progress, plotman
        # reads these logs on a regular basis, so using a fast drive is
        # recommended.
        # sudo mount -t tmpfs -o size=20M tmpfs /mnt/ram/
        #        plots: /home/chia/chia/logs
        plots: /mnt/ram/
        transfers: /home/roet/plotman/log.transfer/
        application: /home/roet/plotman/log.app/plotman.log
        disk_spaces: /home/roet/plotman/log.diskspaces/diskspaces.log

# Options for display and rendering
user_interface:
        # Call out to the `stty` program to determine terminal size, instead of
        # relying on what is reported by the curses library.   In some cases,
        # the curses library fails to update on SIGWINCH signals.  If the
        # `plotman interactive` curses interface does not properly adjust when
        # you resize the terminal window, you can try setting this to True.
        use_stty_size: True

# Optional custom settings for the subcommands (status, interactive etc)
commands:
        interactive:
                # Set it to False if you don't want to auto start plotting when 'interactive' is ran.
                # You can override this value from the command line, type "plotman interactive -h" for details
                autostart_plotting: True
                autostart_archiving: True

# Where to plot and log.
directories:
        # One or more directories to use as tmp dirs for plotting.  The
        # scheduler will use all of them and distribute jobs among them.
        # It assumes that IO is independent for each one (i.e., that each
        # one is on a different physical device).
        #
        # If multiple directories share a common prefix, reports will
        # abbreviate and show just the uniquely identifying suffix.
        tmp:
                - /mnt/nvme_vol/nvme_0-0
                - /home/roet/tmp/ssd00
                - /mnt/ssd03/
                - /mnt/nvme_vol/nvme_0-1
                - /home/roet/tmp/ssd01
                - /mnt/4x_volume/run-22

        # Optional: tmp2 directory.  If specified, will be passed to
        # chia plots create as -2.  Only one tmp2 directory is supported.
        # tmp2: /mnt/tmp/a
        # /home/roet is on nvme01
        # tmp2: /home/roet/plots.tmp-2/plotman
        #tmp2: /mnt/4x_volume/tmp.02 with global stagger 66 it goes well for a long time
        #then it starts forgetting about plots, slowly filling the disks in a few days time

        # Optional: A list of one or more directories; the scheduler will
        # use all of them.  These again are presumed to be on independent
        # physical devices so writes (plot jobs) and reads (archivals) can
        # be scheduled to minimize IO contention.
        #
        # If dst is commented out, the tmp directories will be used as the
        # buffer.
        # disk full        - /mnt/farm/HDD04/Plots_OK/pooled/plotman
        dst:
                - /mnt/farm/HDD00/Plots_OK/pooled/plotman
                - /mnt/farm/HDD01/Plots_OK/pooled/plotman
                - /mnt/farm/HDD02/Plots_OK/pooled/plotman
                - /mnt/farm/HDD03/Plots_OK/pooled/plotman
                - /mnt/farm/HDD05/Plots_OK/pooled/plotman
                - /mnt/farm/HDD06/Plots_OK/pooled/plotman
                - /mnt/farm/HDD07/Plots_OK/pooled/plotman

# Archival configuration.  Optional; if you do not wish to run the
# archiving operation, comment this section out.  Almost everyone
# should be using the archival feature.  It is meant to distribute
# plots among multiple disks filling them all.  This can be done both
# to local and to remote disks.
#
# As of v0.4, archiving commands are highly configurable.  The basic
# configuration consists of a script for checking available disk space
# and another for actually transferring plots.  Each can be specified
# as either a path to an existing script or inline script contents.
# It is expected that most people will use existing recipes and will
# adjust them by specifying environment variables that will set their
# system specific values.  These can be provided to the scripts via
# the `env` key.  plotman will additionally provide `source` and
# `destination` environment variables to the transfer script so it
# knows the specifically selected items to process.  plotman also needs
# to be able to generally detect if a transfer process is already
# running.  To be able to identify externally launched transfers, the
# process name and an argument prefix to match must be provided.  Note
# that variable substitution of environment variables including those
# specified in the env key can be used in both process name and process
# argument prefix elements but that they use the python substitution
# format.
#
# Complete example: https://github.com/ericaltendorf/plotman/wiki/Archiving
#archiving:
#  target: local_rsync
#  env:
#    command: rsync
#    site_root: /mnt/farm

# Plotting scheduling parameters
scheduling:
        # Run a job on a particular temp dir only if the number of existing jobs
        # before [tmpdir_stagger_phase_major : tmpdir_stagger_phase_minor]
        # is less than tmpdir_stagger_phase_limit.
        # Phase major corresponds to the plot phase, phase minor corresponds to
        # the table or table pair in sequence, phase limit corresponds to
        # the number of plots allowed before [phase major : phase minor].
        # e.g, with default settings, a new plot will start only when your plot
        # reaches phase [2 : 1] on your temp drive. This setting takes precidence
        # over global_stagger_m
        # LIMIT WAS 8 TEMPORARILY TO 9 FOR HDD_VOLUME
        tmpdir_stagger_phase_major: 2
        tmpdir_stagger_phase_minor: 1
        # Optional: default is 1
        tmpdir_stagger_phase_limit: 9

        # Don't run more than this many jobs at a time on a single temp dir.
        # WAS 8 BUT TEMPORARY SET TO 16 FOR HDD VOLUME
        tmpdir_max_jobs: 16

        # Don't run more than this many jobs at a time in total.
        # WAS 16 SET TO 32 FOR HDD VOLUME
        global_max_jobs: 32

        # Don't run any jobs (across all temp dirs) more often than this, in minutes.
        # Next runtest try 165 min global stagger ;-(
        # 70 seemed to work well with nvm1 nvm2 ssd0 ssd1, currently using 40 after adding 3x hdd_volume folders
        # for my system in general, with x the amount of temp folders, this is best for m: x*m=280 or m=280/x
        # 35 seemed ok but let's double it to 70, assuming 21hours for a fully stocked queue
        # 93 mins gave equilibrium with plots made and finished with 4:0 set to 3 I had 2 plots building at all times
        # 81 mins same... no catching up as of yet
        # 78 still not really catching up... back to 70? sigh
        # 75 still not enough pressure to get up to 4 plots at all times per temp, so back to 70
        # let's play a game... 65 is catching up with the new 4 max. up to 67 before it gets too tight - or 66, sigh 65 back to 68 after left over temp files bug
        # m68 after a few days remains stable at max 20 parallel plots - there's always a TMP READY and available. Disks may be on max, lots of 100% busy's. Testing 66 next
        # m66 causes bug with ID-less, forgotten plots that get left behind. So m67 next (after a few hours of no new plots) - BULLSHIT; RAM LOG DISK FULL IS WHAT
        # correction concerning m66 it works fine, but a bit more pressure might be ok. Mosst of the disks are at 100% use already but let's see... m64!
        # hmm m64 and I notice a forgotten plot again filling up ssd03 since yesterday 24h to 27h ago. Back to 65
        global_stagger_m: 65

        # How often the daemon wakes to consider starting a new plot job, in seconds.
        polling_time_s: 20

        # Optional: Allows the overriding of some scheduling characteristics of the
        # tmp directories specified here.
        # This contains a map of tmp directory names to attributes. If a tmp directory
        # and attribute is not listed here, the default attribute setting from the main
        # configuration will be used
        #
        # Currently support override parameters:
        #     - tmpdir_stagger_phase_major (requires tmpdir_stagger_phase_minor)
        #     - tmpdir_stagger_phase_minor (requires tmpdir_stagger_phase_major)
        #     - tmpdir_stagger_phase_limit
        #     - tmpdir_max_jobs
        tmp_overrides:
                # In this example, /mnt/tmp/00 is larger and faster than the
                # other tmp dirs and it can hold more plots than the default,
                # allowing more simultaneous plots, so they are being started
                # earlier than the global setting above.
                #"/mnt/tmp/00":
                #        tmpdir_stagger_phase_major: 1
                #        tmpdir_stagger_phase_minor: 5
                #        tmpdir_max_jobs: 5
                # Here, /mnt/tmp/03 is smaller, so a different config might be
                # to space the phase stagger further apart and only allow 2 jobs
                # to run concurrently in it
                # QUESTION HOW TO PLAY WITH THESE PHASES?? :(
                #"/mnt/tmp/03":
                #        tmpdir_stagger_phase_major: 3
                #        tmpdir_stagger_phase_minor: 1
                #        tmpdir_max_jobs: 2
                # - /mnt/nvme_vol/nvme_0-0
                # - /home/roet/tmp/ssd00
                # - /mnt/4x_volume/run-11
                # - /mnt/nvme_vol/nvme_0-0
                # - /home/roet/tmp/ssd01
                # - /mnt/4x_volume/run-22
                "/mnt/nvme_vol/nvme_0-0":
                        tmpdir_stagger_phase_major: 3
                        tmpdir_stagger_phase_minor: 6
                        tmpdir_stagger_phase_limit: 4
                "/home/roet/tmp/ssd00":
                        tmpdir_stagger_phase_major: 3
                        tmpdir_stagger_phase_minor: 6
                        tmpdir_stagger_phase_limit: 4
                "/mnt/nvme_vol/nvme_0-1":
                        tmpdir_stagger_phase_major: 3
                        tmpdir_stagger_phase_minor: 6
                        tmpdir_stagger_phase_limit: 4
                "/home/roet/tmp/ssd01":
                        tmpdir_stagger_phase_major: 3
                        tmpdir_stagger_phase_minor: 6
                        tmpdir_stagger_phase_limit: 4
                "/mnt/ssd03":
                        tmpdir_stagger_phase_major: 3
                        tmpdir_stagger_phase_minor: 6
                        tmpdir_stagger_phase_limit: 4
                "/mnt/4x_volume/run-22":
                        tmpdir_stagger_phase_major: 3
                        tmpdir_stagger_phase_minor: 6
                        tmpdir_stagger_phase_limit: 4
#                "/mnt/4x_volume/run-33":
#                        tmpdir_stagger_phase_major: 3
#                        tmpdir_stagger_phase_minor: 5
#                        tmpdir_stagger_phase_limit: 3
#                "/mnt/4x_volume/run-44":
#                        tmpdir_stagger_phase_major: 3
#                        tmpdir_stagger_phase_minor: 5
#                        tmpdir_stagger_phase_limit: 3

# Plotting parameters.  These are pass-through parameters to chia plots create.
# See documentation at
# https://github.com/Chia-Network/chia-blockchain/wiki/CLI-Commands-Reference#create
plotting:
        # Your public keys.  Be sure to use the pool contract address for
        # portable pool plots.  The pool public key is only for original
        # non-portable plots that can not be used with the official pooling
        # protocol.
        farmer_pk: a06153760fb8dc63
        # pool_pk: ...
        pool_contract_address: xch1fx6n53h2zlwchylzxn0d6dwp90h9u4sqpemwqnhq958pru

        # If you enable Chia, plot in *parallel* with higher tmpdir_max_jobs and global_max_jobs
        type: chia
        chia:
                # The stock plotter: https://github.com/Chia-Network/chia-blockchain
                # https://www.incredigeek.com/home/install-plotman-on-ubuntu-harvester/
                # executable: /home/roet/chia-blockchain/venv/bin
                k: 33                # k-size of plot, leave at 32 most of the time
                e: False             # Use -e plotting option
                n_threads: 4         # Threads per job
                n_buckets: 64       # Number of buckets to split data into default 128 smaller is more ram less wear
                job_buffer: 7400     # 3389 k32 #7400 k33 #14800 k34 #29600 k35     # Per job memory

        # If you enable madMAx, plot in *sequence* with very low tmpdir_max_jobs and global_max_jobs
        madmax:
                # madMAx plotter: https://github.com/madMAx43v3r/chia-plotter
                # executable: /path/to/chia_plot
                n_threads: 4          # Default is 4, crank up if you have many cores
                n_buckets: 256        # Default is 256

dst is not meant to be used as the final resting place for plots unless you are going to manage these situations yourself.  It is meant as a buffer.  Archiving is used to distribute plots to fill disks.
https://github.com/ericaltendorf/plotman/wiki/Archiving


Failed to precompile in julia 1.11.0

Precompiling Mooncake...
Info Given Mooncake was explicitly requested, output will be shown live
ERROR: LoadError: UndefVarError: `arraylen` not defined in `Core.Intrinsics`
Stacktrace:
 [1] getproperty(x::Module, f::Symbol)
   @ Base ./Base.jl:42
 [2] top-level scope
   @ ~/.julia/packages/Mooncake/GMFJI/src/rrules/builtins.jl:76
 [3] include(mod::Module, _path::String)
   @ Base ./Base.jl:557
 [4] include(x::String)
   @ Mooncake ~/.julia/packages/Mooncake/GMFJI/src/Mooncake.jl:1
 [5] top-level scope
   @ ~/.julia/packages/Mooncake/GMFJI/src/Mooncake.jl:80
 [6] include
   @ ./Base.jl:557 [inlined]
 [7] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt128}}, source::Nothing)
   @ Base ./loading.jl:2806
 [8] top-level scope
   @ stdin:4
in expression starting at /home/wuli/.julia/packages/Mooncake/GMFJI/src/rrules/builtins.jl:36
in expression starting at /home/wuli/.julia/packages/Mooncake/GMFJI/src/Mooncake.jl:1
in expression starting at stdin:4
  ✗ Mooncake
  ✗ Mooncake → MooncakeSpecialFunctionsExt
  0 dependencies successfully precompiled in 17 seconds. 85 already precompiled.

Hi @PhyX-Meow and thanks for opening this issue. We're aware of this, and are working to fix it in the next 24 hours. Please see #180 for links to various discussions.

This should be resolved by #288 . Please re-open if version 0.4.11 does not resolve this problem.


Auto members

This adds automatic members, also profile pictures too!

I think this should be ready!


Renamed Mexico City to Runtime Manager

Documentation, comments, code, and build scripts.

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: 769ad300a60dac496a26c1ce585e23759f8178d8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@ShaleXIONG, thanks, I missed those conflicts during a rebase earlier.

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: 900a95d41d3081351342cc1f72186037bc8032fb
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: 2a9d2b13707730f7aa6d4270ba31438a2ad95ea6
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: e11d90c741f94367747b3de0193acc71c2408557
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


[QENG-3063] Fix reboot test timeout issues on jenkins

QENG-3063

Prior to this change, the host_test.rb check for rebooting systems could sometimes fail, only on our Beaker acceptance jenkins, but in such a way that it was clear that something was happening after the attempt to reboot started, but no further output was available.
Exploratory work showed that when a rebooted host changes IP address, it is possible for not only the normal long sequence of Fibonacci-fallback connect retries to happen, but for also various low-level TCP connection failures (with their own long timeouts) to occur.
Since output was being buffered, and not flushed, and neither of these phases was generating a lot of output (enough to trigger a buffer flush on its own), it was possible for more than our 10 minute jenkins output timeout to pass without effectively changing the output buffer.
Flushing our log output overcomes the jenkins timeout problem. We do not here address questions of long IP-address change timeouts.
/cc @puppetlabs/beaker
/related: https://github.com/puppetlabs/beaker/pull/1005/

:+1:, will merge after Jenkins goes green

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1775/
Test FAILed.

Bwahahahahah!
He means NEVER!

lololol

So, as I mentioned in the hipchat channel... the way we're spec testing our logger was to invent a MockIO class which prevents .flush from working (causes an error due to the IO stream not being initialized). That class is a subclass of IO, which is great, but it neuters all the methods so that they can't work.
Why? Who knows.
Instead of being overly mockist (and making it difficult to change our code and have confidence), we could actually test the IO paths more fully.  E.g., http://product.reverb.com/2014/12/19/testing-logging-in-ruby-with-stringio/
So, turns out, StringIO makes the tests pass just as well as our MockIO does, but actually does things like round-tripping through an IO-compatible structure (not just a blank object with stubbed method names).
The downside is that we're not really testing things through StringIO any more than we were with MockIO, since all the tests just do expect() calls on the object.  But we could. I think we should, at our next opportunity.
Will push that spec change in a second.
Also, I probably want to go ahead and neuter the intermittently failing create_remote_file via rsync tests (as discussed in hipchat) for this go-around so that we can actually get things green in the cases where this makes a difference. There will be a separate Jira issue for that related problem.

Pushed changes to use StringIO instead of MockIO (we should consider making those tests non-mockist in the future), also neutered BKR-612 test here, since it will almost certainly fail whenever this failing behavior would be exposed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1776/
Test FAILed.

Added fails_intermittently wrappers to more fully isolate rsync-related specs that can fail on debian7 and centos7 due to stale IP issues. Will build until our green build shows a rebooted host which has a stale IP -- that green means that this patch is working for QENG-3063 without tripping up on rsync issues (which will be resolved via BKR-612).

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1782/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1783/
Test PASSed.

:metal: :guitar:
This build includes a centos7 host which changes IP on reboot, reboot tests do not fail; rsync tests would fail but are caught in the fails_intermittently blocks.
:ship:

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1784/
Test PASSed.


IUPAC name for CHEBI:79500?

Can I ask to annotate 3alpha,21-Dihydroxy-D-homo-5beta-pregn-17a(20)-en-11-one (CHEBI:79500) to the ChEBI standard?
I suppose the IUPAC name should be 3α,21-dihydroxy-16a-homo-5β-pregn-17(20)-en-11-one
Thanks!

And similarly, 3-aza-A-homocholest-4a-en-4-one (CHEBI:79753) can be given a shorter IUPAC name based on cholestane, I guess 3-aza-4a-homocholest-4a-en-4-one

Thanks. The changes have now been made.


diff.go: add the missing '.' in 'kubectl diff -h' output.

diff.go: add the missing '.' in 'kubectl diff -h' output.
Signed-off-by: ZhenLiu94<EMAIL_ADDRESS>Sorry, we do not accept changes directly against this repository. Please see
CONTRIBUTING.md for information on where and how to contribute instead.

Cheers @ZhenLiu94.
We prefer these changes be rolled into larger fixes as there are likely similar changes needed. Reference.
Regardless this repo is unable to accept direct PRs. They instead need to be made against the main Kubernetes repo. Reference
/close


Change class access to support mono

Fixes ppy/osu#1204

Going to go ahead and merge this since it is a critical bug and stopping people from contributing (and being able to run) the project.


Manga District domain error following Cloudfare  issue

Source information
Manga District 1.4.43
Source language
English
Steps to reproduce
I have a Cloudfare issue with Manga District source version 1.4.43. However, when I'm trying to fix it in webview, I get "net::ERR_NAME_NOT_RESOLVED" page

Expected behavior
Webview page opening on source website so that I can solve Cloudfare issue
Actual behavior
net::ERR_NAME_NOT_RESOLVED page
Mihon/Tachiyomi version
TachiyomiSY Preview r564
Android version
Android 11
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

This is actually a domain error issue

Nothing we can do about it, if their site is legitimately dead, let us know (and share any announcements they might've had)


Add get_sender_address() runtime function

Any test for the patch?

It's in private repo https://github.com/tonlabs/toolchain-test-suite/pull/29.


Feat: Refactor Code

[x]  Replace indentation with tabs

[ ]  Flatten indentation stacks

[ ]  Fix variable naming

If we go back to refactor more, we can create a new issue for it


Connection pool for multithreaded apps (e. g. using Nameko+Django+gevent)

Hi,
I've recently discovered Nameko and instantly fell in love with it. Great work!
The only thing I am missing was connection pooling mechanism: spamming server with RPC calls sometimes led to GEvent exceptions about using same socket by multiple greenlets.
So I decided to implement a simple connection pooling mechanism to use Nameko with my Django apps.
Usage is fairly simple:
from nameko.standalone.rpc import ClusterRpcProxyPool

pool = ClusterRpcProxyPool(config, pool_size=8)
pool.start()

# Within django view or model:
with pool.next() as rpc:
    rpc.mailer.send_mail(foo='bar')

# ...
pool.stop()

It uses gevent-powered Queue for pooling connections. Once there are no more free connections to reuse, it will block until a connection becomes available. Later we can implement dynamic pool size to create more connections if the pool is drained for a longer time.
I tested my code with siege, and here are the results:

Creating one ClusterRpcProxy per request:

10~20 RPS
~50% availability (driving RabbitMQ nuts)

Creating global shared ClusterRpcProxy for all requests:

~50 RPS
~70% availability (periodic crashes due to multiple greenlets using same sockets)

Using ClusterRpcProxyPool:

~110 RPS, ~6K RPM
100% availability

I hope this code helps. I'm open to any comments to make it better.

There is some overlap here with https://github.com/clef/flask-nameko. Connection pooling is clearly a use-case we need to support. The performance improvement is very significant!
We intentionally made the standalone package independent of eventlet to avoid clashes with whatever concurrency pattern the client is using.
This is a nice PR but it might be better as a separate library, as flask-nameko is, unless there's a non-eventlet based pool implementation we can use here. I think that would be the best solution, if possible.
@davidszotten thoughts?

Hey @mattbennett, thanks for the response!
Dependency on eventlet is not necessary, it can simply be replaced by built-in Queue implementation which can be monkey-patched by gevent or whatever the client is using. I just used eventlet because it seemed like nameko is using it as well.

for production usage of the standalone proxy, i agree that a connection pool is required to get reasonable performance. perhaps to the extent that we should ship one in nameko. i think the library from clef linked above has a slightly nicer implementation, e.g. only instantiating proxies on demand.
if we do provide one, it would be nice to have enough hooks to e.g. tie in to the django/flask request cycle
there are some further considerations, e.g. around call ids that i think the version of this i wrote for ofs (never got open sourced iirc)

I'm thinking of probably moving this out into some new django-nameko package. Some Django support would be pretty convenient, I think.

This could be enhanced to instantiate proxies only on demand, no? With that change (and using non-eventlet primitives) this would be an enhancement of nameko's out-of-the-box offering. It would be even better if it pooled connections inside the existing API, rather than adding a new one.
A new django-nameko package would be cool too, especially if there are Django specific additions to make. That's probably the path of least resistance would be a nice outcome.

@mattbennett Right. Currently it blocks if the pool is drained. We can make it spawn more proxies in this case.
I'm currently packaging it within django-nameko package in order to do some good testing in real projects, will be in touch.

Great stuff, thanks. Looking forward to the results!

In case you're interested, here's the plugin for Django: https://github.com/and3rson/django-nameko

@and3rson nice work! I wrote the flask-nameko library, which is super similar. @davidszotten and @mattbennett - since there's so much overlap between flask-nameko and django-nameko, it seems like we should definitely try to consolidate the logic / call style into something standard across the two of them (at least at the underlying implementation level).
I'd much prefer to have a connection pooled proxy merged into nameko than maintain an outside project - what are the major blockers / constraints to make that happen? @mattbennett I know you mentioned you'd want it to fall within the existing APIs, can you flesh that idea out a little bit more?
Thanks!

@jessepollak there is some overlap here with our recent mailing list thread.
I think the ideal API here has the following qualities:

Is backwards compatible with the existing proxy (i.e. no change in the API, or having to interact with the pool)
Connections are pooled and re-used rather than creating a new one for each use
The pool supports a minimum number of connections (to be created at startup) and a maximum number (and blocks or raises when exhausted), and others are created on demand.
Stale connections are detected and recovered transparently

@jessepollak @mattbennett Thanks for your feedback, guys!
I'm willing to cooperate on this, so let me know if I can make some help.

@mattbennett just to clarify, do you think this should replace the ClusterRpcProxy or should it be a new class?

@jessepollak if it can be backwards compatible I think we should consider it an enhancement to the existing ClusterRpcProxy.
If you decide to experiment with a different AMQP library as per the mailing list, that would be best as a PoC.

Did this endeavour die off? A pool would be pretty useful!

Great pool request!
Nameko should have pools anyway: it's very costful to create and close new connection for any request
Otherwise, everyone should create similar realization on their own project

To echo what was said earlier, great pool request!
However, many people probably want to change the next() function to this:
    def next(self, timeout=None):
        """ Fetch next connection.
        This method is thread-safe.
        """
        return self.queue.get(timeout=timeout)

This will ensure that it never times out. On the other hand, setting "timeout=False" by default (as it was before) ensures that it times out immediately if the queue is empty. See also the original queue get() function:
https://github.com/python/cpython/blob/3.7/Lib/queue.py#L153


Fixed possible hang in S3ListHandlerTest

This PR contains

In method CallbackUtils.chainCallback(), this could lead to hang of request processing when when an Error occurs. Changed to catch Throwable, and wrap Error in  RestServiceException
Added a pair of new new methods that invokes a preAction and finalCallback with complete error handling, in order to eliminate boilerplate code in S3 handlers
Modified existing S3 handlers to use the new methods

Codecov Report
Attention: 51 lines in your changes are missing coverage. Please review.

Comparison is base (6a64918) 71.83% compared to head (444b010) 18.25%.

Files
Patch %
Lines

...n/java/com/github/ambry/commons/CallbackUtils.java
10.52%
16 Missing and 1 partial :warning:

...va/com/github/ambry/frontend/s3/S3BaseHandler.java
0.00%
14 Missing :warning:

...va/com/github/ambry/frontend/s3/S3ListHandler.java
0.00%
9 Missing :warning:

...ava/com/github/ambry/frontend/s3/S3PutHandler.java
0.00%
9 Missing :warning:

.../com/github/ambry/frontend/s3/S3DeleteHandler.java
0.00%
2 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2712       +/-   ##
=============================================
- Coverage     71.83%   18.25%   -53.58%
+ Complexity    11769     2799     -8970
=============================================
  Files           827      827
  Lines         70343    70337        -6
  Branches       8482     8487        +5
=============================================
- Hits          50528    12842    -37686
- Misses        17167    56299    +39132
+ Partials       2648     1196     -1452

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


Precision reduced between v4 and v5

Is it expected ?
On my machine, the code
import numpy as np
import simsimd as simd
X = np.array([1.0, 2.0, 3.0], dtype=np.float32)
print(simd.cosine(X, X))

prints 5.960464477539063e-08 on v4.4.0 and 0.00036910176277160645 on v5.0.0

For me that was detected by a test in LangChain that uses numpy.allclose()

Is it checked without passing atol/rtol arguments?

Yes, with defaults.

So do we have to accept the precision loss or will there be changes to improve it ?

@cbornet can you please also share the output of this:
python -c "import simsimd; print(simsimd.get_capabilities())"

If it prints haswell, the issue is likely coming from here - the rsqrt. But I am not sure if it's a good idea to replace it with a more accurate solution. If so, we need to change it in every cosine distance kernel in spatial.h.

Sure. Here is the result:
{'serial': True, 'neon': False, 'sve': False, 'neon_f16': False, 'sve_f16': False, 'neon_bf16': False, 'sve_bf16': False, 'neon_i8': False, 'sve_i8': False, 'haswell': True, 'skylake': False, 'ice': False, 'genoa': False, 'sapphire': False}

with the haswell on.

That makes a lot of sense, thank you @cbornet!

matt_dz suggested several reading materials on Twitter:

The CORE-MATH project. link
Precision and Performance Analysis of C Standard Math Library Functions on GPUs. link
Accuracy of Mathematical Functions in Single, Double, Double Extended, and Quadruple Precision link
Correctly-rounded evaluation of a function: why, how, and at what cost? link
RLIBM: Rutgers Architecture and Programming Languages Lab's Correctly Rounded Libm link

I love that some of those materials explicitly target GPUs. I was thinking about putting together a mixed-precision math hackathon; all those links look like excellent preparation materials. Still, I must figure out when to allocate time for them properly. I've previously tried to mix such precision-calibration issues with other intra-day tasks, which was clearly not enough to grok them.
Help and recommendations are more than welcome!


TypeError: string indices must be integers while running example script

Describe the bug
TypeError: string indices must be integers while running example script
To Reproduce
Steps to reproduce the behavior:

install from source code poetry add ../fog_x -E rtx
run example script

import fog_x

# 🦊 Dataset Creation
# from distributed dataset storage
dataset = fog_x.Dataset(
    name="demo_ds",
    path="~/test_dataset", # can be AWS S3, Google Bucket!
)

# 🦊 Data collection:
# create a new trajectory
episode = dataset.new_episode()
# collect step data for the episode
episode.add(feature = "arm_view", value = "image1.jpg")
# Automatically time-aligns and saves the trajectory
episode.close()

# 🦊 Data Loading:
# load from existing RT-X/Open-X datasets
dataset.load_rtx_episodes(
    name="berkeley_autolab_ur5",
    additional_metadata={"collector": "User 2"}
)

# 🦊 Data Management and Analytics:
# Compute and memory efficient filter, map, aggregate, groupby
episode_info = dataset.get_episode_info()
desired_episodes = episode_info.filter(episode_info["collector"] == "User 2")

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
python examples/example_fogx_collector.py
I 2024-04-29 22:36:24,783 dataset.py:104] Dataset path: /home/ubuntu/test_dataset
I 2024-04-29 22:36:24,784 polars_connector.py:144] Prepare to load table demo_ds loaded from /home/ubuntu/test_dataset/demo_ds.parquet.
I 2024-04-29 22:36:24,795 polars_connector.py:152] Table demo_ds loaded from /home/ubuntu/test_dataset/demo_ds.parquet.
I 2024-04-29 22:36:24,813 db_manager.py:293] Closing the episode with metadata {}
2024-04-29 22:36:25.753912: I external/local_tsl/tsl/cuda/cudart_stub.cc:32] Could not find cuda drivers on your machine, GPU will not be used.
2024-04-29 22:36:25.758487: I external/local_tsl/tsl/cuda/cudart_stub.cc:32] Could not find cuda drivers on your machine, GPU will not be used.
2024-04-29 22:36:25.826837: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instruct
ions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-04-29 22:36:27.131030: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
2024-04-29 22:36:27.799667: W external/local_tsl/tsl/platform/cloud/google_auth_provider.cc:184] All attempts to get a Google authentication beare
r token failed, returning an empty token. Retrieving token from files failed with "NOT_FOUND: Could not locate the credentials file.". Retrieving
token from GCE failed with "FAILED_PRECONDITION: Error executing an HTTP request: libcurl code 6 meaning 'Couldn't resolve host name', error detai
ls: Could not resolve host: metadata.google.internal".
I 2024-04-29 22:36:28,023 dataset_info.py:599] Load dataset info from gs://gresearch/robotics/berkeley_autolab_ur5/0.1.0
I 2024-04-29 22:36:28,575 logging_logger.py:49] Constructing tf.data.Dataset berkeley_autolab_ur5 for split None, from gs://gresearch/robotics/ber
keley_autolab_ur5/0.1.0
I 2024-04-29 22:36:28,576 dataset.py:381] train
Traceback (most recent call last):
  File "/home/ubuntu/FogX-Store/examples/example_fogx_collector.py", line 20, in <module>
    dataset.load_rtx_episodes(
  File "/home/ubuntu/.cache/pypoetry/virtualenvs/fogxstore-nGESZMNh-py3.10/lib/python3.10/site-packages/fog_x/dataset.py", line 385, in load_rtx_e
pisodes
    for step in tf_episode["steps"]:
TypeError: string indices must be integers

Desktop (please complete the following information):

OS: Ubuntu 22.04 LTS
Poetry: 1.8.2
Python: 3.10.12

Additional context
Add any other context about the problem here.

commit 1c6e2f8 fix this issue. It's caused by not specifying the split in tfds.
I do see #13 if running the example from the repo. needs more look. but your issue is resolved


Getting java.sql.SQLException when calling export method

I'm getting java.sql.SQLException: Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY when calling export method.
This method seems to finish successfully. I got the email message with attached zip file, but its content has only 'CREATE' statements, there aren't 'INSERT' statements.

Hello, @mavortius please can you provide the following information:

complete stack trace
the configuration properties for mysql-backup4j
and other details that might help in debugging, including modification of library logic if any

Regards

Hi @SeunMatt,
This is the stack trace:
java.sql.SQLException: Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY. 	at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129) 	at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97) 	at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) 	at com.mysql.cj.jdbc.result.ResultSetImpl.last(ResultSetImpl.java:1711) 	at com.smattme.MysqlExportService.getDataInsertStatement(MysqlExportService.java:170) 	at com.smattme.MysqlExportService.exportToSql(MysqlExportService.java:292) 	at com.smattme.MysqlExportService.export(MysqlExportService.java:349) 	at br.com.proinde.databasebackupservice.AutoBackupScheduler.backup(AutoBackupScheduler.java:50) 	at br.com.proinde.databasebackupservice.AutoBackupScheduler.runBackup(AutoBackupScheduler.java:28) 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 	at java.lang.reflect.Method.invoke(Method.java:498) 	at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84) 	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748)
An interesting thing is that exception happens 50 times consecutively (50 it's the total number of tables and views in my database).
And this is the configuration I'm using for mysql-backup4j:
`
Properties props = new Properties();
props.setProperty(MysqlExportService.DB_NAME, "my_db");
props.setProperty(MysqlExportService.DB_USERNAME, "root");
props.setProperty(MysqlExportService.DB_PASSWORD, "root_password");
props.setProperty(MysqlExportService.EMAIL_HOST, "mail_host");
props.setProperty(MysqlExportService.EMAIL_PORT, "587");
props.setProperty(MysqlExportService.EMAIL_USERNAME, "mail_user");
props.setProperty(MysqlExportService.EMAIL_PASSWORD, "password");
props.setProperty(MysqlExportService.EMAIL_FROM, "user@mail.com");
props.setProperty(MysqlExportService.EMAIL_TO, "to_user@mail.com");

props.setProperty(MysqlExportService.TEMP_DIR, new File("external").getPath());
MysqlExportService mysqlExportService = new MysqlExportService(props);
mysqlExportService.export();
mysqlExportService.clearTempFiles(false);

`
It's not so complex, just using as it is in blog's library.

The size of the sql script generated file has only 6KB, this size isn't right because the sql script file generated manually by mysqldump for my database is up to 35MB. As I said before, the content of that "wrong" file has only CREATE instructions not INSERT for data, while the generated sql script file by mysqldump has INSERT instructions too.

hi, @SeunMatt I am also facing the same issue.
The SQL file generated by the library has only create table instructions and it is missing insert data instructions

Hello @pulkitsharva,
I will look into it, hopefully, this weekend. Do check back by then.
Thanks

Hello @pulkitsharva  and @mavortius this issue has been fixed in version 1.2.0

Hello @pulkitsharva and @mavortius this issue has been fixed in version 1.2.0

Thanks for your work!


bug: ionic 5 -  Native: tried calling...

Bug Report
Ionic version:

[x] 5.x
Current behavior:

getting a series of `Native: tried calling (StatusBar.statusDefault/Spashscreen.hide()/Android Permissions) but Cordova is not available. Make sure to include cordova.js or run in a device/simulator. I am running this on a native device.
Expected behavior:

not to get these errors as they are causing side effects especially when this.platform.is('cordova') is returning false.
Steps to reproduce:

Related code:

insert short code snippets here

Other information:

Ionic info:

Ionic:

   Ionic CLI                     : 6.1.0 (/Users/me/.config/yarn/global/node_modules/@ionic/cli)
   Ionic Framework               : @ionic/angular 5.0.4
   @angular-devkit/build-angular : 0.801.2
   @angular-devkit/schematics    : 8.3.25
   @angular/cli                  : 8.3.25
   @ionic/angular-toolkit        : 2.2.0

Cordova:

   Cordova CLI       : 9.0.0<EMAIL_ADDRESS>   Cordova Platforms : android 8.1.0, ios 5.1.1
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 4.1.3, (and 17 other plugins)

Utility:

   cordova-res : 0.9.0
   native-run  : 0.3.0

System:

   Android SDK Tools : 26.1.1 (/Users/me/Library/Android/sdk)
   ios-deploy        : 1.10.0
   ios-sim           : 8.0.2
   NodeJS            : v13.8.0 (/usr/local/Cellar/node/13.8.0/bin/node)
   npm               : 6.13.7
   OS                : macOS Mojave
   Xcode             : Xcode 11.3.1 Build version 11C504

Thanks for the issue. Is cordova.js being included in your output bundle's HTML file?

I don't know, I wasn't having this issue before I upgraded to v5. so maybe in the upgrade someone got changed? How would I check for this?

You can either just check Web Inspector to see if it is getting loaded. Ionic Framework does not manage Cordova dependencies, so it is likely something is wrong in the build process.

In that case it is not, anything related to the cordova is not getting loaded/called

Thanks for the follow up. Can you provide a repo with the code required to reproduce this issue?

Sure, I will do that, it might be after the weekend, as I am sick and unable to think straight

So I the error comes when I launch on android with $ ionic cordova run android --device --livereload with ionic 4.x this was never an issue, but, now with ionic 5.0.4 it appears that it is not being compiled correctly?

Ah ok that's good to know. This might be an issue with https://github.com/ionic-team/angular-toolkit instead. Ionic Framework does not manage including Cordova in your apps.
There was an older issue with cordova.js not being included. I would ensure you have the latest version of @ionic/angular-toolkit installed. If the issue persists, I would recommend opening an issue on the repo I linked to. Thanks!


AsyncRx: Avoid closure allocations in Linq-operators when only the source-observable is captured.

This avoids quite a few allocations of closures for Linq-operator-creation when the only object that would have been captured is the source-observable. More closure-allocation improvements may follow.

LGTM. We can also mark lambdas without a closure as static from now on.

I'll update this PR tomorrow to enable C# 9

I'll update this PR tomorrow to enable C# 9

Did it in a separate PR in #1365 because it'll need separate review w.r.t. all the CI properties. @clairernovotny Would you please have a look?

Lambdas have been marked static.


Generate json files for course pages in ocw-hugo-themes

In addition to the current html output for course pages we should generate a json version for each page and resource which will be easier to parse. This will be saved in the same folders as the original pages and resources. The json representation of each page will be publically available by appending /data.json to the page.

@abeglova can this be closed?


Any plans for North Star Crossing on the double rail on v5.0?

Quad-rail has a nice junction. Do you plan to make a north start shape for the double rail?

No.  Complicated junctions provide no practical benefit in a regular grid.  Simple U-turn "merging" junctions provide all the performance necessary.


feat: schema: feature-gate deny_unknown_fields

This is a backwards-compatible change to the schema package which makes serde(deny_unknown_fields) optional.
It's feature-gated and not set by default.
cargo test --features allow-unknown-fields will run the new test_allow_unknown_fields().
I believe this test illustrates the use-case clearly in code, but a bit more explanation: this has been a real-world problem for us (Levana) - we have bots which are written in Rust and consume messages from contracts. They do share the same "message" library code, but oftentimes we need to stagger their deployment (e.g. deploy contracts with new fields for the frontend, and we do not want to immediately deploy new bots or indexer services). deny_unknown_fields causes the bots to then break, since they are unaware of the new fields - but they don't need or use those new fields at all. We want to allow it.
Tbh I'm a bit surprised this hasn't come up more in the wild, but that may be due to most clients using languages other than Rust which are not bound by the serde constraints (such as Typescript which does not error out on unknown fields.)

Thanks for bringing this up. I think the only reason deny_unknown_fields was ever introduced is the generated schema and the generated TypeScript types. At decoding level we don't even want the behaviour. I wonder if there is a better fix for it, e.g. by tweaking the schema/code generation only without affecting serde itself.

interesting... do you have more info for how deny_unknown_fields affects the schema generation? I'm not familiar with that - but if we could remove deny_unknown_fields altogether, that would be nicer, might be worth looking into :)

See https://github.com/CosmWasm/cosmwasm/issues/1307

oh wait - this PR isn't quite right... it requires that the caller have the feature, since it's just generated from the proc macro... not ready for merging yet, will ping for re-review

@webmaster128 - it's fixed and ready for review
It's a bit too time consuming for me to dig deeper on "try to get rid of deny_unknown_fields altogether" right now. What do you think about merging this in as a stop-gap, and opening a new tracking issue to link here if someone wants to pick it up and fix more holistically?
No pressure ofc, we can point at our fork for now if need-be :)

I was thinking about a different short term solution: Create an optional argument like this: #[cw_serde(deny_unknown_fields=false)]. This then is a non-breaking change we can release in CosmWasm 2.1. Changing behaviour with features is usually not great since it easily goes wrong in more complex setups, such as e.g. the macro being used in a library. Also the feature is not additive, which is a requirement for Cargo features.

Create an optional argument like this: #[cw_serde(deny_unknown_fields=false)]

sorry, not following what you mean there.. the compiler didn't like this when I tested it

Also the feature is not additive, which is a requirement for Cargo features

Ok, I've made it additive in https://github.com/CosmWasm/cosmwasm/pull/2017/commits/0837c366366ae1573d790aaaa82e68ba0f17dad0
to test now it's with cargo test --no-default-features
imho this is a bit harder to reason about since it has to control it by setting default-features = false in the dependency... I could imagine a future dev wondering what that's about - but not a biggie. If it lands with this approach, all good. If you'd like to close this PR and just note it as some sortof request for the future, also all good :)

I'd also vote for the #[cw_serde(deny_unknown_fields=false)] version. Then we can add more arguments in the future and the change can be applied more granular.
The problem with using a feature here is that any transitive dependency enabling it will enable it for your crate, affecting all of your schemas.

sorry, not following what you mean there.. the compiler didn't like this when I tested it

Works fine for me:
#[cw_serde(deny_unknown_fields = false)]
pub struct State {
    pub count: i32,
}

Of course, at the moment it is just ignored.
What needs to be done here is to parse the attr param of the cw_serde macro, pass that into cw_serde_impl and check for the deny_unknown_fields value

ahhh, I see what you're saying now. Yes, I agree, that's much nicer :)

I'm going to go ahead and close this PR... not sure if I'll get around to opening one with that other approach, but if so, I'll link here for reference

I'll open an issue to track it though


Feature: Optimise the reset  parameter receiving module

SetClusterResetArgs(args *RunArgs) => SetClusterResetArgs(args *ResetArgs)

Please assign this and #1203 to me.

Please assign this and #1203 to me.


[New Model]: Shared Aspect for UUID v4

Model Description
UUIDs are used very often. From personal knowledge I can say: I do often copy them. As Johannes proposed extracting them in PR #295, we already created PR #296
Relevant Standards
RFC 4122
Example Data
urn:uuid:48878d48-6f1d-47f5-8ded-a441d0d879df
MS1 Criteria

[ ] The proposed aspect model does not exist already
[ ] The proposed aspect model does not extend an existing aspect but introduces completely new functionality
[ ] The proposal references a Catena-X use case
[ ] Relevant standards are mentioned/linked
[ ] A first draft of the data structure is provided in an example

@Modelling_Team


Support for Importing to IA from ChilloutVR

This task requires:

Deconstruction of an Animator based on Layer Name.

Because CVR handles things based on a Single Animator, the implementation I had in mind was an Expectation that Layers that need to be converted to start with [LayerType]

Example: [FX] My Toggles and [Gesture] My Hands

Better Animator Deconstruction and Reconstruction

https://github.com/VoyVivika/Intermediate-Avatar/issues/1


Plan wizard review: Source, target providers, move selected VMs and add popover with VMs list

The Plan wizard review contains following changes:

Moves selected-VMs up.
Adds source and target providers
Selected VMs is shown as link with the list of VMs using a Popover.

Resolves https://github.com/konveyor/virt-ui/issues/220, resolves https://github.com/konveyor/virt-ui/issues/221, resolves https://github.com/konveyor/virt-ui/issues/222

This looks great @gildub!


Missing icon field does not fail validation step

Icon is required for all three of the publishing entities, thus the validation check should enforce.

@konoart Can you tell me more about what you're seeing with problems with the icon? Validation checks appear to be working with the sample data I'm trying.

@creativedrewy it's about a media with purpose = icon

@konoart can you give a little more context about what data issues you are seeing? I'm just not seeing the ability to mint NFTs without the "icon" value.

@creativedrewy , sure. We have a releases submitted: https://czt544ueexwyz55ohcy73l3x45uvfzaldl7llsfux2mec7l2aw2a.arweave.net/FmfecoQl7Yz3rjix_a9352lS5Asa_rXItL6YQX16BbQ
It doesn't have a media with purpose = icon that's why it's failing.