Replace docker 1.8.1 with docker 1.11.0-dev run would failed to run container

I have old environment with Fedora 21 Atomic (integrated with docker 1.8.1).
Since I am helping debug the issue https://github.com/docker/docker/pull/20829
I need to compier the docker code into 1.11.0-dev binary, and then replace that 1.8.1 daemon with 1.11.0-dev to verify if that #20829 fix the volume plugin issue.
I found the new binary would not run simple containers
[**Note: I did not use volume-driver here]
The following is about when run  docker-1.11.0-dev info
Containers: 6
 Running: 0
 Paused: 0
 Stopped: 6
Images: 10
Server Version: 1.11.0-dev
Storage Driver: devicemapper
 Pool Name: docker-docker--pool
 Pool Blocksize: 524.3 kB
 Base Device Size: 107.4 GB
 Backing Filesystem: xfs
 Data file:
 Metadata file:
 Data Space Used: 245.4 MB
 Data Space Total: 2.147 GB
 Data Space Available: 1.902 GB
 Metadata Space Used: 147.5 kB
 Metadata Space Total: 8.389 MB
 Metadata Space Available: 8.241 MB
 Udev Sync Supported: false
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Library Version: 1.02.82 (2013-10-04)
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: rexray local
 Network: null host bridge
Kernel Version: 3.17.4-301.fc21.x86_64
Operating System: Fedora 21 (Twenty One)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955 GiB
Name: sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal
ID: YG5J:AFK2:E7OI:ALFE:PQUV:FOG2:ZX4K:SZQZ:GTOG:QP2Q:E2GE:HN3N
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 15
 Goroutines: 22
 System Time: 2016-03-02T09:51:20.613804637Z
 EventsListeners: 0
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

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

Compier docker master branch code into binary
Replace systemd service bin start to use the new binary( for example 1.11.0-dev)
as following

ExecStart=/home/fedora/docker-1.11.0-dev daemon -D -H fd:// \
          -H tcp://<IP_ADDRESS>:2375 \
          $OPTIONS \
          $DOCKER_STORAGE_OPTIONS \
          $DOCKER_NETWORK_OPTIONS \
          $INSECURE_REGISTRY
LimitNOFILE=1048576

And then start docker.

Just run  docker run -it busybox sh

It would failed with
Mar 02 10:00:00 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T10:00:00.633076264Z" level=debug msg="Client and server don't have the same version (client: 1.8.1.fc21, server: 1.11.0-dev)"
Mar 02 10:00:00 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T10:00:00.631870148Z" level=debug msg="GET /v1.20/images/json"
Mar 02 10:00:00 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T10:00:00.616856128Z" level=debug msg="Calling GET /v1.20/images/json"
Mar 02 09:56:55 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:55.185038887Z" level=error msg="Handler for POST /v1.23/containers/eedf7d2a7afcb8313ed9c7a8bf7034048993a3b964182b3c31d7ead3f5d69848/start returned error: devmapper: Error mounting '/dev/mapper/docker-253:0-4202207-c800ec8253154755d449fa8189b3bcc70db270d0a9a42fe5e3274a42f4f6b740' on '/var/lib/docker/devicemapper/mnt/c800ec8253154755d449fa8189b3bcc70db270d0a9a42fe5e3274a42f4f6b740': no such file or directory"
Mar 02 09:56:55 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:55.183696354Z" level=error msg="Error unmounting container eedf7d2a7afcb8313ed9c7a8bf7034048993a3b964182b3c31d7ead3f5d69848: invalid argument"
Mar 02 09:56:55 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:55.175278808Z" level=error msg="devmapper: Error unmounting device c800ec8253154755d449fa8189b3bcc70db270d0a9a42fe5e3274a42f4f6b740: invalid argument"
Mar 02 09:56:55 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:55.174295362Z" level=debug msg="devmapper: UnmountDevice(hash=c800ec8253154755d449fa8189b3bcc70db270d0a9a42fe5e3274a42f4f6b740) END"
Mar 02 09:56:55 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:55.173728081Z" level=debug msg="devmapper: Unmount(/var/lib/docker/devicemapper/mnt/c800ec8253154755d449fa8189b3bcc70db270d0a9a42fe5e3274a42f4f6b740)"
Mar 02 09:56:55 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:55.172077400Z" level=warning msg="devmapper: Mount count of device went negative. Put() called without matching Get(). Resetting count to 0"
Mar 02 09:56:55 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:55.171592162Z" level=debug msg="devmapper: UnmountDevice(hash=c800ec8253154755d449fa8189b3bcc70db270d0a9a42fe5e3274a42f4f6b740)"
Mar 02 09:56:55 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:55.161107759Z" level=warning msg="failed to cleanup ipc mounts:\nfailed to umount /var/lib/docker/containers/eedf7d2a7afcb8313ed9c7a8bf7034048993a3b964182b3c31d7ead3f5d69848/shm: no such file or directory"
Mar 02 09:56:54 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:54.838224332Z" level=debug msg="devmapper: activateDeviceIfNeeded(c800ec8253154755d449fa8189b3bcc70db270d0a9a42fe5e3274a42f4f6b740)"
Mar 02 09:56:54 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:54.658059181Z" level=debug msg="POST /v1.23/containers/eedf7d2a7afcb8313ed9c7a8bf7034048993a3b964182b3c31d7ead3f5d69848/start"
Mar 02 09:56:54 sw-s5lcdlw5ktj-0-jserl73ppvan-swarm-node-lscjkrmyn6rx.novalocal docker-1.11.0-dev[2999]: time="2016-03-02T09:56:54.645789098Z" level=debug msg="Calling POST /v1.23/containers/eedf

Describe the results you received:
the new binary could not start containers
Describe the results you expected:
I would expect new docker binary  can start containers
Provide additional info you think is important:
nothing else

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

ping @thaJeztah  if you know about it :)   Thanks

I think you should try to build a dynamic binary; Udev Sync Supported: false is probably the cause here, due to a really old version of device mapper. Running without Udev Sync is known to result in data-loss and corruption on devmapper.
(Also note that Fedora 21 is EOL'd and we no longer build binaries for that, but that shouldn't be an issue if you're building yourself)

@thaJeztah I used make BINDDIR=. binary ways, I did not know when you talked about dynamic binary
Could you tell me what's way for that to build ?
Also for Udev Sync Supported: false, I searched a similar issue, but what I want was to verify #20829 fix, So it is needed to have docker binary running on atomic. Or else, it can not guarantee, it fixed that issue.

ping @thaJeztah  if you know how to build a dynamic binary. (as comments above) :)

@HackToday oh! I meant to answer that; you can build deb or rpm packages using make deb / make rpm. By default, all supported distros are built (see https://github.com/docker/docker/tree/master/contrib/builder/rpm/amd64 and https://github.com/docker/docker/tree/master/contrib/builder/deb/amd64).
If you want to build only for specific distro, use the DOCKER_BUILD_PKGS env-var, for example, to build a deb package for Ubuntu Xenial;
DOCKER_BUILD_PKGS=ubuntu-xenial make deb

Those builds are run in a container (so you should have docker running), but the results are put in the bundles directory on your host;
tree bundles/
bundles/
├── 1.12.0-dev
│   ├── build-deb
│   │   ├── docker.log
│   │   ├── test.log
│   │   └── ubuntu-xenial
│   │       ├── Dockerfile.build
│   │       ├── docker-engine_1.12.0~dev~git20160518.202625.0.1691fe6-0~xenial.dsc
│   │       ├── docker-engine_1.12.0~dev~git20160518.202625.0.1691fe6-0~xenial.tar.gz
│   │       ├── docker-engine_1.12.0~dev~git20160518.202625.0.1691fe6-0~xenial_amd64.changes
│   │       └── docker-engine_1.12.0~dev~git20160518.202625.0.1691fe6-0~xenial_amd64.deb
│   ├── dynbinary
│   ├── dynbinary-client
│   │   ├── docker -> docker-1.12.0-dev
│   │   ├── docker-1.12.0-dev
│   │   ├── docker-1.12.0-dev.md5
│   │   └── docker-1.12.0-dev.sha256
│   └── dynbinary-daemon
│       ├── dockerd -> dockerd-1.12.0-dev
│       ├── dockerd-1.12.0-dev
│       ├── dockerd-1.12.0-dev.md5
│       └── dockerd-1.12.0-dev.sha256
└── latest -> 1.12.0-dev

Given that Fedora 21 is not longer supported, you may need to add a docker file for that in the "builder" directory, similar to https://github.com/docker/docker/blob/master/contrib/builder/rpm/amd64/fedora-22/Dockerfile
I'll close this issue, because I think your question is answered, but feel free to comment after I closed 👍


Updating role action spaces after k means

When I was reading the update_role_action_spaces function in rode_controller.py I was a bit confused. It would be super helpful if you can clear my doubts!
Here's part of the code:
spaces = []
for space_i ,space in enumerate(o_spaces):
            _space = copy.deepcopy(space)
            _space[0] = 0.
            _space[1] = 0.

            if _space.sum() == 2.:
                spaces.append(o_spaces[space_i])
            if _space.sum() >= 3:
                _space[:6] = 1.
                spaces.append(_space)

In my understanding, this code segment is trying to discard outliers (cluster containing a single action, not counting no-op and stop). So the code adds the action space in the loop to spaces only if _space.sum() >= 2.
What I am confused about is why when _space.sum() >= 3, we do _space[:6] = 1.? Does that mean we do not allow any role that can only attack/heal?
Thank you.

Yeah you are right. This part of code is for the SMAC benchmark. Some role action spaces do not include move actions. Actions in SMAC tasks are not available sometimes (maybe as you know, in the buffer, PyMARL stores masks showing which actions are available). Roles that do not include move actions sometimes do not include any available actions. To solve this problem, we let all role action spaces contain moving actions, because at least some of them are available.

Hi, anxiaonuoxyz. We do this because, sometimes, after removing outliers, there is only a few (1 oor 2) roles. In this case, it will make little difference if we run the role-based structure, especially when there is only one role. We copy role action spaces to address this problem.

Hi, anxiaonuoxyz. We do this because, sometimes, after removing outliers, there is only a few (1 oor 2) roles. In this case, it will make little difference if we run the role-based structure, especially when there is only one role. We copy role action spaces to address this problem.

Thank you very much for your answer, thank you for answering my question, if you have time, can you help me answer the question about transfer (I just asked a new question), thank you very much!


Not able to open Edit Yaml of Namespace under a cluster's Projects/Namespace

On master-head commit id: f33188d

Go to Cluster --> Projects/Namespace --> 'Edit YAML' a namespace
Page is stuck in loading
Error in console

TypeError: Cannot read property 'doneOverride' of null
    at f.r (index.vue?7c0a:1)
    at f.t._render (vue.runtime.esm.js:3548)
    at f.r (vue.runtime.esm.js:4066)
    at _n.get (vue.runtime.esm.js:4479)
    at _n.run (vue.runtime.esm.js:4554)
    at gn (vue.runtime.esm.js:4310)
    at Array.<anonymous> (vue.runtime.esm.js:1980)
    at ie (vue.runtime.esm.js:1906)

@sowmyav27 I can't reproduce this - are you doing this as an non-admin?

@nwmac I just hit this, cluster needs to be non-local. Issue is caused by a 403 when trying to fetch the namespace

Reopening because of https://github.com/rancher/dashboard/issues/3500#issuecomment-882455995

I wasn't able to reproduce this, downstream cluster (k3s on digital ocean) or otherwise. I tried with admin, restricted admin, and standard users with cluster owner and member roles, and wasn't able to create a situation in which the active user had 'Edit as YAML' as an option on a namespace they couldn't fetch... @richard-cox do you have any more details on how you reproduced this? The issue appears to be more specific than just any namespace in a downstream cluster.

My local cluster is a tad old (Jul 14, 2021). Are you on a newer version? If so perhaps there was a backend issue that's been fixed and this should go back to test.
To confirm, the Edit as YAML button is always visible however when clicking on it then the 403 to k8s/clusters/c-m-c37649bb/api/v1/namespaces/<name> happens

I am using a shiny-new rancher install so maybe it is a recent backend fix. I'm going to move this back to test, then.

On master-head commit id: 9e0d1b2

Able to do an Edit Yaml of namespace of a downstream cluster with no errors.


T019 - Molecular dynamics simulation

Details

Talktorial ID: 019
Title: Molecular dynamics simulation
Original authors: Pietro Gerletti
Reviewer(s): Mareike Leja, David Schaller
Date of review: 09/2020-present

Content review

Potential labels or categories (e.g. machine learning, small molecules, online APIs): interaction, small molecule, protein
One line summary: Perform a molecular dynamics simulation of the SARS-CoV-2 main protease in complex with an inhibitor.
[x] The table of contents reflects the talktorial story-line; order of #, ##, ### headers is correct
[x] URLs are linked with meaningful words, instead of pasting the URL directly or linking words like here.
[x] I have spell-checked the notebook
[x] Images have enough resolution to be rendered with quality, without being too heavy.
[x] All figures have a description
[x] Markdown cell content is still in-line with code cell output (whenever results are discussed)
[x] I have checked that cell outputs are not incredibly long (this applies also to DataFrames)
[x] Formatting looks correctly on the Sphinx render (bold, italics, figure placing)

Code review

Time it took to execute (approx.):
[x] Variable and function names follow snake case rules (e.g. a_variable_name vs aVariableName)
[x] Spacing follows PEP8 (run Black on the code cells if needed)
[x] Code line are under 99 characters each (run black -l 99)
[x] Comments are useful and well placed
[x] There are no unpythonic idioms like for i in range(len(list)) (see slides)
[x] All 3rd party dependencies are listed at the top of the notebook
[x] I have marked all code cell with output referenced in markdown cells with the label # TODO: CI
[ ] I have identified potential candidates for a code refactor / useful functions
[x] All import ... lines are at the top (practice part) cell, ordered by standard library / 3rd party packages / our own (teachopencadd.*)
[x] I have update the relative paths to absolute paths.
List here unfamiliar libraries you find in the imports and their intended use:

Hey @jaimergp,
I could not render with sphinx easily because this notebook is probably missing in some sort of configuration file. How can I include it?

Hey @jaimergp,
I could not render with sphinx easily because this notebook is probably missing in some sort of configuration file. How can I include it?

Check docs/talktorials and create the correaponding nblink file there!

@AndreaVolkamer Everything works well as notebook, colab notebook or html :tada:
Ready for review!

@Mika-Le - your talktorials final index will be T019. Could you please at some point update this PR according to that (let me know if you need help)?

@Mika-Le the talktorial is GREAT!!! Very easy to follow and very good explanations, well done!
I've added my feedback above.
MD simulations are very complex and require quite some tools/libraries, and I think the depth you are covering is great. Since - especially in the practical part some people might still want to know more about the individual steps or libraries, could you please include the links to those there again.
[Note, I did only go through it on reviewnb, without running it on colab, I'll do that as soon as time allows]

Hi @AndreaVolkamer, thank you for the great feedback. I updated the notebook, it is ready to be reviewed again.

Hi @AndreaVolkamer, thank you for the great feedback. I updated the notebook, it is ready to be reviewed again.

@Mika-Le very well done (@schallerdavid), the notebook is great! I only added tiny textual adaptions.
Unfortunately, I couldn't get it running on colab due to the mentioned GLIBCXX_3.4.26 import error. I tried some fixes from this link, but after the rdkit error was fixed, I got a No module named 'mdtraj.formats.dcd' error?
Maybe @jaimergp since you looked into colab for the other course you have a fix in hand?
As soon as the colab thing is solved, the notebook is ready to be merged!

@Mika-Le very well done (@schallerdavid), the notebook is great! I only added tiny textual adaptions.
Unfortunately, I couldn't get it running on colab due to the mentioned GLIBCXX_3.4.26 import error. I tried some fixes from this link, but after the rdkit error was fixed, I got a No module named 'mdtraj.formats.dcd' error?
Maybe @jaimergp since you looked into colab for the other course you have a fix in hand?
As soon as the colab thing is solved, the notebook is ready to be merged!

As per our chat, the issue is solved but we can't make sure it works reliably right now because Anaconda.org servers are a bit irresponsive now and installation fails. We have decided to reconvene in a week, since by then openmmforcefields might be on conda forge already (and does not suffer from server issues since it runs on separate network).

As per our chat, the issue is solved but we can't make sure it works reliably right now because Anaconda.org servers are a bit irresponsive now and installation fails. We have decided to reconvene in a week, since by then openmmforcefields might be on conda forge already (and does not suffer from server issues since it runs on separate network).

openmmforcefields not yet on conda-forge due to blocking https://github.com/openmm/openmmforcefields/pull/151. We'll wait a bit so we can merge with a conda-forge only env!

@jaimergp,
everything works out with installing only via conda-forge 🎉. I would be done from my side.

This is awesome! I am sure OpenMM users will like this material a lot! Thanks for putting it together!
I have added some minor comments that do not change the outcome or purpose of the talktorial, just some technical details we need to take into account.

Ping me again when the comments are addressed so I resolve the conflicts and merge!

Thanks @Mika-Le! 🚀


[Subtask] Propose a draft design to add OceanBase JDBC Catalog Support

Describe the subtask
This issue tracks the design work for the OceanBase JDBC catalog.
Parent issue
#4848

Here is the design document. Please feel free to leave your comments.
https://docs.google.com/document/d/19IQNeh-tXmgOIbDuy8yMSoqDpl-jp26HjvlR5ByeQLY/edit?usp=sharing

The design looks fine overall. I'm going to close this issue, thanks @yuanoOo for bringing it up


[Bug] If you accidentally click multiple playlists, it is possible to open multiple of them

This can make it hard to get back to the main menu as you will have to back out of every opened one

Repro Steps:

Tap a playlist that has a larger amount of songs
The app will probably hang at that moment
While it hangs tap another playlist

Expected Results
The first playlist should only be loaded in
Actual Results
All playlists tapped are loaded in
Potential Solution
Change up the ordering of how we load in new data for each playlist. More so, navigate immediately to our playlist and throw some loading indicator on the songs list while they come in. Also, when a playlist is tapped, potentially set a flag that blocks all other playlists from being tapped.


Support UTF8 field data

Add ability to use the ^FH command so that utf8 characters can be used in field data.

Using command("^FH^CI28") at the beginning of a label seems to affect all subsequent data


Parity mismatch between API and zip

Describe the bug
In our parity test, the assert fails because what's returned from the API doesn't match what we hardcoded to expect.
Which normally would be fine--we'd just update what to expect.
Except when we do that, then the assert fails because what's in the zip doesn't match what we hardcoded to expect.
To Reproduce
Get vulns for org.bouncycastle:bcprov-jdk15on:1.57 from both the API and the zip and compare.
Expected behaviour
They should match.
Screenshots

Just to confirm, the 'Actual' in your first screenshot is from the OSV API, and the 'Actual' in the second is from the zip / bucket download?
Looking at a few of the records in the zip right now, it looks like they should match the API responses.
I suspect you might be detecting the changes on the API side before the data is finished exporting to the GCP bucket. The export job runs once an hour, so you're probably pulling the old version of a record if you download it as soon as the API response changes.

An hour lag explains it. Just wanted to make sure you were aware of it. Typically the parity-check job passes, so we don't stress about it when it fails.


Cannot provision the openshift cluster

Follow the document - https://github.com/openshift/hive/blob/master/docs/using-hive.md to clone the latest hive code and use hiveutil to create the openshift cluster. It always throws Still waiting for the Kubernetes API: Get https://api.clyang-oc-cluster.clyang.de:6443/version?timeout=32s: dial tcp <IP_ADDRESS>:6443: connect: connection refused. The three master nodes and one bootstrap node are created in aws.
Append more detailed log information:
time="2019-10-14T07:40:07Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.clyang-oc-cluster.clyang.de:6443/version?timeout=32s: dial tcp <IP_ADDRESS>:6443: connect: connection refused"
time="2019-10-14T07:40:07Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.clyang-oc-cluster.clyang.de:6443/version?timeout=32s: dial tcp <IP_ADDRESS>:6443: connect: connection refused"
time="2019-10-14T07:40:41Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.clyang-oc-cluster.clyang.de:6443/version?timeout=32s: dial tcp <IP_ADDRESS>:6443: connect: connection refused"
time="2019-10-14T07:40:41Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.clyang-oc-cluster.clyang.de:6443/version?timeout=32s: dial tcp <IP_ADDRESS>:6443: connect: connection refused"
time="2019-10-14T07:40:41Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.clyang-oc-cluster.clyang.de:6443/version?timeout=32s: dial tcp <IP_ADDRESS>:6443: connect: connection refused"
time="2019-10-14T07:41:15Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.clyang-oc-cluster.clyang.de:6443/version?timeout=32s: dial tcp <IP_ADDRESS>:6443: connect: connection refused"
time="2019-10-14T07:41:15Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.clyang-oc-cluster.clyang.de:6443/version?timeout=32s: dial tcp <IP_ADDRESS>:6443: connect: connection refused"
time="2019-10-14T07:41:15Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.clyang-oc-cluster.clyang.de:6443/version?timeout=32s: dial tcp <IP_ADDRESS>:6443: connect: connection refused"
time="2019-10-14T07:41:29Z" level=debug msg="Fetching \"Install Config\"..."
time="2019-10-14T07:41:29Z" level=debug msg="Loading \"Install Config\"..."
time="2019-10-14T07:41:29Z" level=debug msg="Fetching \"Install Config\"..."
time="2019-10-14T07:41:29Z" level=debug msg="Fetching \"Install Config\"..."
time="2019-10-14T07:41:29Z" level=debug msg="Loading \"Install Config\"..."
time="2019-10-14T07:41:29Z" level=debug msg="Loading \"Install Config\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"SSH Key\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"SSH Key\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Base Domain\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Base Domain\"..."
time="2019-10-14T07:41:29Z" level=debug msg="    Loading \"Platform\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Cluster Name\"..."
time="2019-10-14T07:41:29Z" level=debug msg="    Loading \"Base Domain\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Pull Secret\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Platform\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"SSH Key\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Base Domain\"..."
time="2019-10-14T07:41:29Z" level=debug msg="    Loading \"Platform\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Cluster Name\"..."
time="2019-10-14T07:41:29Z" level=debug msg="    Loading \"Base Domain\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Pull Secret\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Platform\"..."
time="2019-10-14T07:41:29Z" level=debug msg="Using \"Install Config\" loaded from state file"
time="2019-10-14T07:41:29Z" level=debug msg="Reusing previously-fetched \"Install Config\""
time="2019-10-14T07:41:29Z" level=debug msg="    Loading \"Platform\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Cluster Name\"..."
time="2019-10-14T07:41:29Z" level=debug msg="    Loading \"Base Domain\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Pull Secret\"..."
time="2019-10-14T07:41:29Z" level=debug msg="  Loading \"Platform\"..."
time="2019-10-14T07:41:29Z" level=debug msg="Using \"Install Config\" loaded from state file"
time="2019-10-14T07:41:29Z" level=debug msg="Reusing previously-fetched \"Install Config\""
time="2019-10-14T07:41:29Z" level=debug msg="Using \"Install Config\" loaded from state file"
time="2019-10-14T07:41:29Z" level=debug msg="Reusing previously-fetched \"Install Config\""
time="2019-10-14T07:41:29Z" level=info msg="Pulling debug logs from the bootstrap machine"
time="2019-10-14T07:41:29Z" level=error msg="Attempted to gather debug logs after installation failure: failed to create SSH client, ensure the proper ssh key is in your keyring or specify with --key: failed to initialize the SSH agent: failed to read directory \"/root/.ssh\": open /root/.ssh: no such file or directory"
time="2019-10-14T07:41:29Z" level=fatal msg="Bootstrap failed to complete: waiting for Kubernetes API: context deadline exceeded"
time="2019-10-14T07:41:29Z" level=info msg="Pulling debug logs from the bootstrap machine"
time="2019-10-14T07:41:29Z" level=error msg="Attempted to gather debug logs after installation failure: failed to create SSH client, ensure the proper ssh key is in your keyring or specify with --key: failed to initialize the SSH agent: failed to read directory \"/root/.ssh\": open /root/.ssh: no such file or directory"
time="2019-10-14T07:41:29Z" level=fatal msg="Bootstrap failed to complete: waiting for Kubernetes API: context deadline exceeded"
time="2019-10-14T07:41:29Z" level=info msg="Pulling debug logs from the bootstrap machine"
time="2019-10-14T07:41:29Z" level=error msg="Attempted to gather debug logs after installation failure: failed to create SSH client, ensure the proper ssh key is in your keyring or specify with --key: failed to initialize the SSH agent: failed to read directory \"/root/.ssh\": open /root/.ssh: no such file or directory"

I have tried use openshift/installer to install openshift cluster with the same configuration and credentials as using by hive. it can create the cluster successfully in AWS cloud.
Any comments? Thanks.

The usual cause of that result is an inappropriate pull secret.

@staebler Thanks for your insight. Yes. you are correct. I can have Openshift installed successfully after refresh the pull secret.
BTW, How to debug to find such error? I tried to access the aws bookstrap host by using ssh. it is failed with Permission denied even if the 22 port is accessible for bootstrap node.

You should be able to ssh into the bootstrap host. Are you using the private key corresponding to the public key specified in the clusterdeployment? Are you using the core user?

You should be able to ssh into the bootstrap host. Are you using the private key corresponding to the public key specified in the clusterdeployment? Are you using the core user?

Thanks for your response. It is working now when I used the core user with public key.

Thanks for your shared information. it is clear for me now.


Check Unicode chars on all platforms

Ensure that unicode characters are printing correctly on all platforms and versions.

Windows and Linux working good.  Can't check Mac.  But the way I'm doing it now, it should work.  Going to close this now and will reopen if I have reason to believe Mac is not working correctly.


Upgrade hyper to version 1.2

This PR updates hyper to the 1.0 API. As a necessity, it also further decouples ourselves from diesel's version of BigDecimal through some ugly copy&paste, but these changes ensure that we are no longer dependent on other crates using our preferred version of BigDecimal.

I screwed up when I merged this - it is actually merged, not just closed


lane_context does not have :hash_with_strings return type so laneContext() in Swift doesn't work

This is not documented and may or may not be broken 🙃

My fastlane env:
Stack

Key
Value

OS
10.13.4

Ruby
2.3.1

Bundler?
false

Git
git version 2.15.1 (Apple Git-101)

Installation Source
~/.gem/bin/fastlane

Host
Mac OS X 10.13.4 (17E199)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.3.1_2/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.3

@doruvil Are you able to send me what your Fastfile.swift looks like? I want to try and duplicate your situation

@joshdholtz
I have simplified the Fastfile.swift
as much as possible in order to help you detect the problem.
Fastfile.swift.zipPlease replace the:

HockeyApp API Token
keychain password
project name
Xcode scheme
bundle id -> provisioning profile matching


Tree queries

Hi aMOPel, I've been working on some highlighting queries based off of this repository's grammar. They're currently in development over at https://github.com/helix-editor/helix/pull/6123: once they're done I can PR them to this repo, neovim, and anywhere else that uses tree-sitter.

Hi :)
I honestly am pretty stuck on the last few syntax nodes. Unless somebody is gonna help me with that grammar, who has a better understanding of tree sitter I probably won't finish it.
Your efforts are probably better spent on
https://github.com/alaviss/tree-sitter-nim/tree/rewrite

I saw that, I'll probably rewrite the queries for it once alaviss finishes (originally I wrote them for alaviss's first grammar).
Did you manage to find any good documentation for tree-sitter when you were working on the grammar? I've been writing the queries by reading through other existing queries and grammars and sort of guessing how they should be written, for lack of anything better to base them off of: which hasn't worked terribly well. I've been having a particularly hard time with keywords: they have to line up with the grammar.js file somehow and I haven't quite figured out how.

it looked like objects are the big thing missing?

I've made issues describing the missing features.
One big thing missing are the complex expressions, ie if-expressions etc. And another thing are the various parentheses. There is this construct called "par" in the grammar spec which works like this:
let a = (
  echo "hi"
  5
)
echo a
# prints
# hi
# 5

But there are also the arbitrary parentheses around expressions like
let a = (1+1)*2

It's a pain to disambiguate those from tuples and function calls, but probably doable.
The complex expressions are the big thing I got stuck on though.
Also another big issue is that the grammar.js is so big and complex now, that the resulting parser is absolutely enormous in size. What's pushed right now is 15MB large. When I added more things it grew to 28MB or something.

Did you manage to find any good documentation for tree-sitter when you were working on the grammar?

Can't say so. I haven't even written any queries myself. Your best bet is probably to take inspiration from preexisting code. The nvim-treesitter repo has a huge collection of queries you could probably learn a lot from those.

TIL about par, I don't think I've ever seen that in practice.
By any chance, do you know of a good way to throw this grammar at an example file to generate syntax trees like in tests/corpus? I think neovim has some support for it on their devel branch but it'd be nice if I could just use the grammar directly.

do you know of a good way to throw this grammar at an example file to generate syntax

https://tree-sitter.github.io/tree-sitter/creating-parsers#command-parse
This will parse the file and generate the AST.
I don't know if this helps you but
https://nim-lang.github.io/Nim/macros.html#treeRepr%2CNimNode
This can give you the AST from parser of the Nim compiler
If your questions was about good example files to parse:
https://github.com/nim-lang/Nim/blob/devel/compiler/parser.nim
How about this one?

Also, how do you build parser.c

https://tree-sitter.github.io/tree-sitter/creating-parsers#command-generate

Thanks, I got tree-sitter dumping trees, which is pretty helpful.
On further testing the highlighting doesn't work as well as I thought it did: there's a lot of edge cases, incorrect tree representations, and occasional errors (mostly around type declarations). It's still better than no highlighting though...

If it's just about highlights in neovim, I am using this plugin atm:
https://github.com/alaviss/nim.nvim

If you care enough you could make an issue listing the failing edge cases, and I could have a look at it

I actually fixed some issues with the type descriptions etc.
If you still find something, please report it.
I tested it on various large files from the nim repo and it did everything except complex expressions (like if expressions, case expressions etc.) and par (parentheses to group things like - (a + b)).

I'll open issues for any new problems I find :+1:

Btw I have written some highlight queries that comply with the nvim tree sitter interface. Gonna push later

pushed on a new branch
https://github.com/aMOPel/tree-sitter-nim/blob/nvim_treesitter_queries/queries/highlights.scm

Oh shoot, I wish I saw this earlier. I rewrote my Helix queries to work with object and concept types and generally be less jank (currently pushed at https://github.com/helix-editor/helix/pull/6123).
I have some known issues with my queries:

Modules like std/[one, two] will get highlighted as variables (while std/one is fine)
tuple[one, two: string] and tuple[one: string, two: string] are highlighted incorrectly (seq[seq[int]] is fine
I couldn't figure out a way to distinguish between variables and types in case statements (if there isn't one, probably should do it by case)

Mmm, note to self, helix and nvim-treesitter queries have reversed precedence (later entries override in nvim, vice versa for helix)


Pagination for collection and dir_s_mkdir error

I am using this plugin in newest version: 2.1.0. Unfortunately after jekyll serve I've got error:
jekyll 3.8.5 | Error:  File exists @ dir_s_mkdir - /media/data/projects/test/_site/freebies/index.html

Important part of my _config.yml:
plugins:
  - jekyll-paginate-v2

collections:
  freebies:
    output: true
    permalink: /freebies/:path/

pagination:
  enabled: true
  permalink: '/page/:num/'
  sort_reverse: true
  per_page: 3
  trail:
    before: 2
    after: 2

autopages:
  enabled: true
  collections:
    enabled: true
    title: 'Posts in collection :coll' # :coll is replaced by the collection name
    permalink: '/:coll'

defaults:
  - scope:
      path: ""
      type: "freebies"
    values:
      layout: "freebies-post"

My freebies posts are located in "_freebies" directory (I've got 4 files here - only markdowns). I don't have in my project file described in error log like: "freebies/index.html".
What is weird here is that structure work's until option pagination->per_page is bigger than count of files inside my collection.
Do you have any idea what I can do here?

Pagination: Complete, processed 6 pagination page(s)
jekyll 3.8.5 | Error:  File exists @ dir_s_mkdir - /Users/thomasvaeth/barber-jekyll/_site/tag/squid/index.html

Just wanted to say that I got the same error. Pagination was set at 6 posts per page, but I had 12 posts. Downgrading to v2.0.0 worked for me.

Same problem over here, downgrading to v2.0.0 is the current workaround o/

Is there any chance that this issue could be addressed? I'm currently running Jekyll 4 (and thus pulling master because I need f8664cf68b59de823b88d4e6b1b985457f2c13af), so downgrading isn't an option.

I just pulled @ashmaroli's PR as a patch into a branch off master and can confirm that it fixes this issue.
I am running Jekyll 4 (and thus master since I need e3cc120b739dcadda87dd732e25c69622472514c from 10 days ago), so downgrading isn't an option.

Could you please upgrade to https://rubygems.org/gems/jekyll-paginate-v2/versions/3.0.0 and test again for me?

Works like a charm for me, thanks @sverrirs 👌 💯

The problem seems to happened again with the error message:
mkdir': File exists @ dir_s_mkdir
jekyll-3.9.2 and ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux-musl]


Add enpoints to get members info for tier

This PR gives https://github.com/opencollective/opencollective-frontend/pull/1844 the data it needs to display members of a tier and some statistics about them.

Coverage decreased (-0.1%) to 64.649% when pulling ccbfbb6f91a43e2384b6c45bc18932f6770a6025 on feat/contributors-grid into 1ef43c25b9a3e326e2467f95a97c91c44c2c12ae on master.


ENH: Impossible to provide a callable for gradient * vector products in opt.newton_krylov

Is your feature request related to a problem? Please describe.
I am routinely using scipy's opt.newton_krylov non linear solver for finding the critical point of a function (I solve grad(f) = 0).
In most cases, it is working very well. In some cases however, I suspect that in those cases, the finite difference scheme that is used by scipy to compute derivative informations suffers from massive cancellation. In particular, I am reffering to lines 1456-1464 of _nonlin.py copied below.
def matvec(self, v):
    nv = norm(v)
    if nv == 0:
        return 0*v
    sc = self.omega / nv
    r = (self.func(self.x0 + sc*v) - self.f0) / sc
    if not np.all(np.isfinite(r)) and np.all(np.isfinite(v)):
        raise ValueError('Function returned non-finite results')
    return r

Describe the solution you'd like.
It so happens thaf for my particular problem, I can compute the gradient * vector product easily without these massive cancellation. I would like to be able to provide this information to the solver. This functionnality already exists in scipy.optimize.minimize via the hessp argument.
Describe alternatives you've considered.
I considered overloading the KrylovJacobian class, but I felt I wasn't familiar enough with scipy to succeed.
Additional context (e.g. screenshots, GIFs)
This probably falls under the following umbrella issue :
Better routines for large-scale root finding (Trac #1790) #2309

EDIT : I managed to get this functionnality using the downstream scipy.optimize.root.nonlin.nonlin_solve and defining my own class deriving from KrylovJacobian. This felt a bit hacky though, mostly as I had been previously using the top level "scipy.optimize.root". Maybe this could be a more standard feature, maybe not. I'll leave it to the more experienced scipy team to decide :-).

@gabrielfougeron : if you are interested, a PR would still be welcome.

@dschmitz89 Thanks for the notification.
Over the last few months, I've changed my mind about this topic thanks for a progressively better understanding of the inner workings of JFNK as implemented in scipy.
More precisely, the code I've come up with (and still use in https://github.com/gabrielfougeron/choreo) looks like this.
class ExactKrylovJacobian(scipy.optimize.nonlin.KrylovJacobian):

    def __init__(self,exactgrad, rdiff=None, method='lgmres', inner_maxiter=20,inner_M=None, outer_k=10, **kw):

        scipy.optimize.nonlin.KrylovJacobian.__init__(self, rdiff, method, inner_maxiter,inner_M, outer_k, **kw)
        self.exactgrad = exactgrad

    def matvec(self, v):
        return self.exactgrad(self.x0,v)

    def rmatvec(self, v):
        return self.exactgrad(self.x0,v)

The modifications are so minor that I now doubt it is useful to define and document a whole new class.
However, I do believe that the functionality would benefit from better documentation. It was quite a journey to eventually realize that so few lines of code would provide this feature.
I'm not aware of the discussions within the scipy developer community regarding documentation style. Maybe it could be a good idea to break down the page https://docs.scipy.org/doc/scipy/tutorial/optimize.html which has become quite cluttered over the years, into a gallery of examples à la https://networkx.org/documentation/stable/auto_examples/index.html
What do you think?


[IC-622] Make bignum equality a bit more performant

... by doing a pointer comparison first, and when not equal
proceed as usual (except when both are compact, the result
is false, as we already checked for identity).
Well, I conjecture that this helps, and the actual cycle counts w.r.t. our benchmarks indicate an improvement of -0.3%, so I guess this could go in.
The discussion happened in JIRA, but the gist is captured in the PR.

  (func $B_eq (type 11) (param $a i32) (param $b i32) (result i32)
    local.get $a
    local.get $b
    i32.eq
    if (result i32)  ;; label = @1
      i32.const 1
    else
      local.get $a
      local.get $b
      i32.or
      i32.const 1
      i32.and
      if (result i32)  ;; label = @2
        local.get $a
        i32.const 1
        i32.and
        if (result i32)  ;; label = @3
          local.get $a
        else
          local.get $a
          i64.extend_i32_s
          i64.const 1
          i64.shr_s
          call $bigint_of_int64
        end
        local.get $b
        i32.const 1
        i32.and
        if (result i32)  ;; label = @3
          local.get $b
        else
          local.get $b
          i64.extend_i32_s
          i64.const 1
          i64.shr_s
          call $bigint_of_int64
        end
        call $bigint_eq
      else
        i32.const 0
      end
    end)


Using javy to compile and distribute a wasm file

I'm using javy in a github actions to publish a wasm file for a library under public domain license.
is it ok to do so?
do I need to credits javy somehow?
thank you
links:
https://github.com/rawpixel-vincent/obfuscate-mail#web-assembly-binary-wasi-compatible
https://github.com/rawpixel-vincent/obfuscate-mail/actions/runs/3211785785/workflow

Javy in licensed under Apache 2.0, so I believe this is fine.


Don't suggest bundle name as possible replacement for symbol links

Bug/issue #, if applicable: rdar://125964139
Summary
This fixes a confusing diagnostic solution when a misspelled link matches the also misspelled bundle name (specified in an Info.plist)
Dependencies
None
Testing
In a any project with some module documentation:

Add a documentation catalog with an Info.plist file that specifies a misspelled version of the module name for "CFBundleDisplayName".
In any content, for example a documentation comment or an article, write a symbol link using the misspelled version of the module name.
Build documentation for the project.

The diagnostic about the unresolved link should only suggest to replace the misspelled name with the correctly spelled module name.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] ~ Updated documentation if necessary~ Not applicable

@swift-ci please test


Add Open in CartoDB to the dataset public pages

Let's add a button close to the likes with the same style that says, OPEN IN CARTODB.

grey one right?

yep

but with our style, not the one on the one click website.

:+1:

Developing this feature and checking with @matallo, we found we have a bug with the importer (#3626).
So one-click won't work with SQL API urls until we fix that :(.


/var/run/docker.sock mount in containers refuse connection after daemon hot upgrade

Output of docker version:
Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   e29d696
 Built:        Mon May 16 06:21:25 2016
 OS/Arch:      linux/amd64
 Experimental: true

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   e29d696
 Built:        Mon May 16 06:21:25 2016
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:
Containers: 12
 Running: 6
 Paused: 0
 Stopped: 6
Images: 9
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 75
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay bridge null host
Kernel Version: 3.13.0-32-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 992.5 MiB
Name: cce2610ec7aa247048a35ecdbdc616338-node2
ID: C7W5:3DNC:QNKF:F3FW:MXGW:LMN3:25PB:4MM6:PBCL:YRWN:QLAJ:GWA4
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 49
 Goroutines: 120
 System Time: 2016-05-17T19:40:08.476257757+08:00
 EventsListeners: 2
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: true
Cluster store: etcd://<IP_ADDRESS>:2379/cce2610ec7aa247048a35ecdbdc616338
Cluster advertise: <IP_ADDRESS>:2376

Steps to reproduce the issue:

start docker deamon in Experimental mode to use hot upgrade
docker run -v /var/run/docker.sock:/var/run/docker.sock -itd docker
attach the "docker in docker" container and use docker commander, no problem.
kill the docker daemon thread and rerun docker daemon
reattach to the container before, can not connect to /var/run/docker.sock

Describe the results you received:
dial unix /var/run/docker.sock: connect: connection refused

Because the /var/run/docker.sock mount not update after daemon thread restart, there is the old unix socket file mounted in container, however the docker daemon listen on a new unix socket file.
Describe the results you expected:
Docker daemon should auto update /var/run/docker.sock mount, thus application can listen on the latest daemon API, and do something such as service-discovery, docker-plugins,etc.
Additional information you deem important (e.g. issue happens only occasionally):
Many docker-plugins(network, volume, ipam) run in containers use the /var/run/docker.sock to communicate with docker daemon, so hot-upgrade should assure this socket file be mount correctly after daemon thread restart.

Thanks @BSWANG! I'll add this to the 1.12 milestone (as it relates to https://github.com/docker/docker/issues/2658)
/cc @crosbymichael

Yes, the daemon will need to reopen the same inode for a bind mount to work, not delete and recreate.

You can't reuse an existing unix domain socket file. You have to unlink it. The only way you could get this to work is to pass the open file descriptor to the new process. On systemd this wouldn't be an issue as that's already how systemd does it (passes it on start). But for non-systemd systems, docker will have to hand the file descriptor off.

We will try our best to find a good solution to fix this but its not necessarily a pre req for completing the daemon restore feature.  Its an advanced usecase and if the fix is too complicated, it maybe better to to do a workaround like not mounting the socket but bind mounting the directory where the socket is created.  That will solve your issue today and in the future.

Do you have any workable suggestions for how to achieve the workaround you suggest, @crosbymichael?  Bind-mounting all of /var/run is a non-starter (for reasons that are hopefully obvious), moving the socket to a subdirectory breaks all the default tools (wedging an env var into every process on a system is surprisingly hard to do, especially when you can't necessarily just reboot machines with wild abandon), and the Docker upstart config doesn't support multiple -H options in DOCKER_OPTS.

and the Docker upstart config doesn't support multiple -H options in DOCKER_OPTS.

@mpalmer you could configure the -H through a daemon.json configuration file instead of through upstart https://docs.docker.com/engine/reference/commandline/dockerd/#/daemon-configuration-file

Let me close this ticket for now, as it looks like it went stale.


[ORM] Automated setting of parent object in has_many <-> has_one relationship doesn't respect polymorphic has_one

Affected Version
3.7.1
Description
In GridFieldDetailForm_ItemRequest::ItemEditForm(), in contexts where the GridField sits under the parent has_one objects CMS interface (i.e. Member has_many Cars and Car has one Member - Security > Member > John Smith > Cars` GridField) the objects foreign key and ID are identified and set automatically, then the corresponding CMS field is made read-only.
This is done around lines 389 - 408 in  GridFieldDetailForm_ItemRequest::ItemEditForm():
		// If we are creating a new record in a has-many list, then
		// pre-populate the record's foreign key.
		if($list instanceof HasManyList && !$this->record->isInDB()) {
			$key = $list->getForeignKey();
			$id = $list->getForeignID();
			$this->record->$key = $id;
		}

		$fields = $this->component->getFields();
		if(!$fields) $fields = $this->record->getCMSFields();

		// If we are creating a new record in a has-many list, then
		// Disable the form field as it has no effect.
		if($list instanceof HasManyList) {
			$key = $list->getForeignKey();

			if($field = $fields->dataFieldByName($key)) {
				$fields->makeFieldReadonly($field);
			}
		}

This doesn't seem to work correctly when the has_one on the other side of the relationship is polymorphic. In this context, the foreign ID field will be set (e.g. ParentID) but nothing is done to set the foreign class (e.g. ParentClass)?
Am I correct in thinking this is a bug (in which case I can provide more details and examples) or am I missing something?

Yep, we should have an additional condition for instanceof PolymorphicHasManyList right?

@tractorcow ,
Yes I think so, the below modifications seem to solve the issue for me. They follow the same basis as the current code (automatically setting the relationship fields and making them read only, but they consider polymorphic relationships as well):
		// If we are creating a new record in a has-many list, then
		// pre-populate the record's foreign key.
		if ($list instanceof PolymorphicHasManyList && !$this->record->isInDB()) {
			$idKey = $list->getForeignKey();
			$classKey = substr($idKey, 0, -2) . "Class";
			$class = $list->getForeignClass();
			$id = $list->getForeignID();
			$this->record->$classKey = $class;
			$this->record->$idKey = $id;
		} else if ($list instanceof HasManyList && !$this->record->isInDB()) {
			$key = $list->getForeignKey();
			$id = $list->getForeignID();
			$this->record->$key = $id;
		}

		$fields = $this->component->getFields();
		if(!$fields) $fields = $this->record->getCMSFields();

		// If we are creating a new record in a has-many list, then
		// Disable the form field as it has no effect.

		if ($list instanceof PolymorphicHasManyList) {
			$idKey = $list->getForeignKey();
			$classKey = substr($idKey, 0, -2) . "Class";
			if($classField = $fields->dataFieldByName($classKey)) {
				$fields->makeFieldReadonly($classField);
			}
			if($idField = $fields->dataFieldByName($idKey)) {
				$fields->makeFieldReadonly($idField);
			}
		} else if($list instanceof HasManyList) {
			$key = $list->getForeignKey();
			if($field = $fields->dataFieldByName($key)) {
				$fields->makeFieldReadonly($field);
			}
		}

What do you think? Is there a better was of getting the separate foreign key fields instead of doing string manipulation like that?
I could submit a PR for this if you are happy  with it, I just need to know what branch you need me to make it against, 3, 3.7, more or less specific?
Cheers,
Joe

@HARVS1789UK Unfortunately, SilverStripe 3 has entered limited support, which means we'll only release security fixes for it from now on.
If this still affects affects SilverStripe 4, feel free to do a PR against the 4 branch if you want.

I actually had a similar problem earlier; I think instead of simply setting just the parent id / class, I think the component really needs the ability to specify a default map of field values to assign on construction. I had custom built a component with a setInitialFields setter.

Resolved in #10297, which will ship in 4.12.0.


plasticity: 24.2.4 -> 24.2.6

Format with nixfmt style

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build plasticity

Please include a link to the diff and changelog in the update commit.
Example: https://github.com/NixOS/nixpkgs/pull/358120/commits/d403617d1876593375ab1f438470eb88590cab71

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 357411

x86_64-linux

:white_check_mark: 1 package built:

plasticity

aarch64-linux

x86_64-darwin

aarch64-darwin

Hi, @GaetanLepage
Is not OSS Software.
You can see on github is empty : https://github.com/nkallen/plasticity
Diff not exist & Changelog too. Maybe I didn't find it after all.
Best Regards


master build error

HI,
I am facing below problem while running react-native run-android

Task :app:processDebugResources FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugResources'.

Android resource linking failed
/home/ubunto/.gradle/caches/transforms-1/files-1.1/drawee-1.10.0.aar/bfe2e3ba3748905ed6faebb6039cbe7e/res/values/values.xml:3:5-58:857: AAPT: error: resource android:attr/fontVariationSettings not found.

/home/ubunto/.gradle/caches/transforms-1/files-1.1/drawee-1.10.0.aar/bfe2e3ba3748905ed6faebb6039cbe7e/res/values/values.xml:3:5-58:857: AAPT: error: resource android:attr/ttcIndex not found.
error: failed linking references.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 33s
Please look into this and reply.
Regards
dk venkatesh babu

I found the same problem.

Hello! Thanks @dkvbabu for filing this.
I see the same thing on my own machine, and we're seeing it also in CI. The exact same commit that's in master now built just fine when I originally pushed it:
https://travis-ci.org/zulip/zulip-mobile/builds/546002328
so this seems to be a change somewhere in our dependencies. It's unfortunate that we seem to be exposed to a change uploaded by dependency's maintainer causing our own build to behave differently and fail.
I'm looking into fixing the immediate issue now.

Update: this isn't totally trivial to fix, awkwardly.
The required step to fix it seems to be to bump compileSdkVersion to 28:
https://github.com/flutter/flutter/issues/27226#issuecomment-458650933
Apparently the cause is that some dependency (drawee, I guess) began to use, at compile time, a feature introduced in API 28.
And indeed, that resolves this error.

But then there's another error (and using cd android && ./gradlew :assembleDebug --continue to have the build plow past the first error, one can confirm that this error is already present on master, so it's not caused by the compileSdkVersion bump):
* What went wrong:
Execution failed for task ':app:mergeExtDexDebug'.
> com.android.build.api.transform.TransformException: java.lang.RuntimeException: java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
  Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
  Program type already present: android.support.v4.app.INotificationSideChannel

That, in turn, is helpfully explained here:
material-components/material-components-android#103
Apparently it's caused by some dependency upgrading from the Android Support Library to AndroidX while we're still on the Support Library (or alternatively vice versa.)
The Android folks have helpfully provided a feature in the Android build toolchain that will magically take care of this... for dependencies that come via Maven. They aren't designing for RN or for dependencies through NPM; and so when we have dependencies that we compile from source, they effectively assume that those dependencies are part of our codebase and we can just upgrade them ourselves.
Anyway, the feature they do provide is to put this into gradle.properties:
android.useAndroidX=true
android.enableJetifier=true

It magically converts references within Maven dependencies to the Android Support Library (android.support.annotation etc.) into references to AndroidX (androidx.annotation etc.).
If I apply that, the DexArchiveMergeException goes away...

...but then there's a new class of error. Four of our NPM-based dependencies, from the RN ecosystem, get compile errors. They look like this:
/home/greg/z/mobile/node_modules/rn-fetch-blob/android/src/main/java/com/RNFetchBlob/Response/RNFetchBlobFileResp.java:3: error: package android.support.annotation does not exist
import android.support.annotation.NonNull;
                                 ^
...
/home/greg/z/mobile/node_modules/rn-fetch-blob/android/src/main/java/com/RNFetchBlob/Response/RNFetchBlobFileResp.java:80: error: cannot find symbol
        public long read(@NonNull Buffer sink, long byteCount) throws IOException {
                          ^
  symbol:   class NonNull

They all seem to be failures to find various android.support libraries.
Still working on that one. It'd be straightforward to do with a small patch to each of these dependencies (and Android Studio is eager to make those changes for me, even)... but patching our dependencies isn't a normal thing in our build process, so actually doing that isn't straightforward.
Next thing I expect to try is upgrading those particular dependencies -- crossing fingers that each one of the four (a) has made a newer release that makes this switch, (b) has such a release that doesn't break something else for us due to whatever random other changes they've made.

Next thing I expect to try is upgrading those particular dependencies -- crossing fingers that each one of the four (a) has made a newer release that makes this switch, (b) has such a release that doesn't break something else for us due to whatever random other changes they've made.

Welp, first one I look at, there's a PR for it just today: react-native-community/react-native-image-picker#1102
So... that's hopeful! Looks likely :crossed_fingers: it'll land soon, and then perhaps a release. Though then there's still the risk the unrelated changes that release pulls in will break something else... and also I haven't yet looked at the other three. Hmm.

Aha, located what looks like the key discussion of this upstream:
facebook/react-native#25293
That's from going back to the root-cause issue, as I mentioned above:

It's unfortunate that we seem to be exposed to a change uploaded by dependency's maintainer causing our own build to behave differently and fail.

Some good details in that thread. In particular, we've scrupulously written down actual concrete versions in our build.gradle for all our dependencies (except RN itself, whose version we control through npm.) And searching through build.gradle files in our dependencies:
$ find android/ node_modules/ -name build.gradle | xargs grep --color=auto -P '(?<!com.facebook.react:react-native:)\+'

I'm pleasantly surprised to find that all but one of them have been equally careful!
The one exception is react-native-device-info:
$ cat node_modules/react-native-device-info/android/build.gradle
// ...
def DEFAULT_GOOGLE_PLAY_SERVICES_VERSION    = "+"

// ...
dependencies {
    def googlePlayServicesVersion = project.hasProperty('googlePlayServicesVersion') ? project.googlePlayServicesVersion : DEFAULT_GOOGLE_PLAY_SERVICES_VERSION
// ...
    compile "com.google.android.gms:play-services-gcm:$googlePlayServicesVersion"
}

Happily the problem is fixed upstream there, as of yesterday:
react-native-community/react-native-device-info#693
So: I'm going to hold off on attempting the AndroidX stuff (people say RN isn't ready for it before 0.60 anyway), and also hold off on the compileSdkVersion bump (though that should be smooth, and I may try it right after getting things working), and just deal with the react-native-device-info issue.

Oof, we're on react-native-device-info version 0.21.5; the release with that fix is 2.1.2. That's a lot of version bumps, and signals two separate rounds of breaking changes.
(v0.21.5 is only just over a year old! 2018-04-09.)
So I'll first try to work around in a limited way without an upgrade. Then can attempt an upgrade after our build is working again -- it'd be good to refresh our dependencies in general.

Fixed! @dkvbabu @wsupajirakit please rebase and try again, and confirm that it's working for you too.
Some handy discussion at https://github.com/react-native-community/react-native-device-info/pull/693#issuecomment-503142535 of how to diagnose the issue (with ./gradlew -q app:dependencies).
Also in the same comment, a workaround that's a bit of a bigger hammer than I ended up using. I did this, to activate the specific logic that the react-native-device-info library's build.gradle has to control the version:
+project(":react-native-device-info").beforeEvaluate {
+    ext.googlePlayServicesVersion = "16.1.0"
+}

The workaround suggested in that comment would, IIUC, simply force any dependency's wildcard reference to use a particular version:
configurations.all {
    resolutionStrategy.force 'com.google.android.gms:play-services-gcm:16.1.0'
}

Thanks. It is fine now.
Regards
dk venkatesh babu

From: Greg Price<EMAIL_ADDRESS>Sent: Wednesday, June 19, 2019 5:28 AM
To: zulip/zulip-mobile
Cc: dkvbabu; Mention
Subject: Re: [zulip/zulip-mobile] master build error (#3526)
Fixed! @dkvbabuhttps://github.com/dkvbabu @wsupajirakithttps://github.com/wsupajirakit please rebase and try again, and confirm that it's working for you too.
Some handy discussion at react-native-community/react-native-device-info#693 (comment)https://github.com/react-native-community/react-native-device-info/pull/693#issuecomment-503142535 of how to diagnose the issue (with ./gradlew -q app:dependencies).
Also in the same comment, a workaround that's a bit of a bigger hammer than I ended up using. I did this, to activate the specific logic that the react-native-device-info library's build.gradle has to control the version:
+project(":react-native-device-info").beforeEvaluate {

ext.googlePlayServicesVersion = "16.1.0"
+}

The workaround suggested in that comment would, IIUC, simply force any dependency's wildcard reference to use a particular version:
configurations.all {
resolutionStrategy.force 'com.google.android.gms:play-services-gcm:16.1.0'
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/zulip/zulip-mobile/issues/3526?email_source=notifications&email_token=ACPPERVBVMNYRGAD54N2HHDP3FZBZA5CNFSM4HY5YCQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYAJIGY#issuecomment-503354395, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACPPERSXXK2S7GYQX7SHISTP3FZBZANCNFSM4HY5YCQQ.


Current build is failing showing failing in Modules Catalog

Current build is failing showing failing in Modules Catalog

Can you look at why last build failed ? I want all our modules showing clean builds where possible

Sure Matt.

#66 terraform-ibm-ocp-vpc TF script condition restored. Based on my understanding from module commit history, Sean was working on  licence config updates.


Create Bash Script for switching between organizations

Context: I am creating a bash script to automate the process of switching between organizations on a developer’s local development environment. So that developer’s can save time while developing.
The script will do the following:

Prompts the user for environment variables if none are detected in .zshrc.
Changes the environment variable to the other organization in .zshrc.
Changes ORG variable in docker-compose.yml

Note: The script will be in the scripts directory in the project repository once complete

I finished the bash script and tested it on my local machine. I just need to make sure the script works on others machines.
Here is how the script looks when the user first runs it

Here is how the script looks when the user has run the script a second time

I requested and received feedback on the script from multiple people.
I added the following:

Ensure the provided directory exists and includes the instance-files subdirectory.
The script can now be run from the root directory of complaint_manager.
Provide more meaningful messages when using the script.

Here is the link to the script with updated changes: link


Occasional "list index out of range" on line 98 in default.py.

Probably just an overlooked potential scenario. Here is the line:
for element in data[1][2][2]:

Fixed.


ajax:success render partial exponential

I have in create.js.erb the next:
$('.comment_box form').bind('ajax:success', function() {
$("<%= escape_javascript(render(:partial => 'create_index'))%>").hide().prependTo($(this).closest(".comments_column").eq(0)).fadeIn(1500);
alert("Success!");
});
When I click submit button the first time, render the partial 1 time(working fine).
The problem its that if I  click the submit button a second time, render the last partial and previous partial( 3 partials). If I submit button 3 times, the last data plus 3 before partials and so on...
I want submit 1 partial for each submit button. Why happen this?

The reason it's running multiple times is because you're binding to the success event every time the ajax:success event fires. You should only bind it once, so that it is triggered once every time it fires. Check out this article, part 1 and part 2 for a more in-depth explanation and examples.

Thank you, I have follow your article, but I dont find the side for send one time the binding for each submit. How bind I one time for each submit?

With your example above, you shouldn't include the .bind() in the create.js.erb, because it will be called every time the form is submitted. Just remove the bind entirely and instead make your create.je.erb like this:
$("<%= escape_javascript(render(:partial => 'create_index'))%>").hide().prependTo($('.comment_box form').closest(".comments_column").eq(0)).fadeIn(1500);
alert("Success!");

That works if you only have a submit form. In my case I have many forms in the same page with the same class .comments_column you can see a example that working in jquery but dont working for jquery-ujs :(.
http://jsfiddle.net/minitech/aC92Q/8/
If you have a only a form with a button submit working fine. But if you have more forms with the same class dont working because create the comment in the same columns if you submit other different form.
Any idea?
Thank you very much JangoSteve

For something like that, you probably want to pass a unique identifier so that you know which to append to. For example, your form could have something like (pseudo-code):
<%= form_tag, ..., :class => 'comment_box', :id => comment.id do %>
<%= hidden_field :form_id, comment.id %>
...

Then in your js.erb:
form = $('#<%= params[:form_id] %>');
$("<%= escape_javascript(render(:partial => 'create_index'))%>").hide().prependTo(form.closest(".comments_column").eq(0)).fadeIn(1500);
alert("Success!");

Hopefully this is enough to get you going.

Wouuuu now working fine. Thats is :D I have create unique id in each form with:
:html => { :id => "#{post.id}" }) and now only working for closest post.id :D
Thank you JangoSteve

:-)


flush CDN cache on deploy

Problem
When deploying /latest with Shipit, there's no way for the CDN to know these are new files because the file name for the zip is the same causing changes to take up to 24 hours.
Solution: Add a command to shipit.yml to flush the cache on deploy.
https://github.com/Shopify/slate/blob/master/shipit.yml
More information
To flush the cache on deploy takes a certain credential that I will have to ask Edgescale about.

Fixed in #178


oss-fuzz has found an undefined shift (by -5) in libjxl

Hi, this image:
www.rollthepotato.net/~john/clusterfuzz-testcase-minimized-pngsave_buffer_fuzzer-5360982477111296
Produces this error in oss-fuzz:
  | /src/jpeg-xl/lib/jxl/dec_modular.cc:471:47: runtime error: shift exponent -5 is negative
  | #0 0x1434953 in jxl::ModularFrameDecoder::FinalizeDecoding(jxl::PassesDecoderState*, jxl::ThreadPool*, jxl::ImageBundle*) jpeg-xl/lib/jxl/dec_modular.cc:0
  | #1 0x1387e5e in jxl::FrameDecoder::Flush() jpeg-xl/lib/jxl/dec_frame.cc:814:3
  | #2 0x137f603 in jxl::FrameDecoder::FinalizeFrame() jpeg-xl/lib/jxl/dec_frame.cc:849:3
  | #3 0x104eadf in jxl::(anonymous namespace)::JxlDecoderProcessInternal(JxlDecoderStruct*, unsigned char const*, unsigned long) jpeg-xl/lib/jxl/decode.cc:1155:30
  | #4 0x104c287 in JxlDecoderProcessInput jpeg-xl/lib/jxl/decode.cc:1668:14
...

Not very important, but it should probably be fixed.

I wonder how a bitstream managed to get a -5 there. Will have a look later.

hmm, I tried this from main just now running djxl from asan and msan builds and it only gets to -1 there. Didn't see uninitialized memory in msan run. @jcupitt do you know what version of jxl is that report from?

I think it's the sync from two weeks ago (current github):
https://gitlab.com/wg1/jpeg-xl/-/compare/040eae8105b61b312a67791213091103f4c0d034...30ea86ab4c1f1b98c21967a2e3d72a51fe77e454

It was a weird combination of modular transforms (something the encoder doesn't do) where multi-channel Palette is done after Squeeze, and inverse Palette had a bug where it wouldn't correctly set the hshift/vshift of the reconstructed channels, causing inverse Squeeze to potentially make them go negative.
https://github.com/libjxl/libjxl/pull/35 should fix it.


Support SSG?

Can we generate all the mermaid graphs during build time?

If you want that you should see the repo for the docs on the oficial roolup repo

Could you share the link? @emersonbottero  Didn't find any related content:

In the mean time, I am considering using the markdown-it-mermaid plugin so in the end, the mermaid graphs can be generated during the vite-press building step.

Found another thread: https://github.com/mermaid-js/mermaid/issues/3650, seems it's very hard.


Minor fixes (proposal)

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thank you for your interest.
We have a policy of not accepting PRs which are merely cosmetic in nature, but there are plenty of features on the backlog if you want to get involved at a deeper level...


Setup Intermediate Pin

TLS Settings taken over from #178 thanks to @IndianaDschones
I will take this over here as we also adapted the TLS Config, as it is less restrictive on the CDN for Distribution


This problem occurred when I upgraded to react 18

I'm getting the same error and wanted to post an issue. It seems someone else got it.

Yes, Leva isn't fully compatible with React 18 yet. But this throws a warning in dev mode and that's it for now, so nothing critical.

Yes, Leva isn't fully compatible with React 18 yet. But this throws a warning in dev mode and that's it for now, so nothing critical.

nothing critical? I think the app will run on some kind of compatibility mode for backwards compatibility instead of just displaying a warning.

@baranelitez what's the question?

There's an ongoing PR for React 18.

If you mount Leva yourself as in here, you'll suppress the warning.

If you let Leva auto mount, then only the panel will behave as in React 17.


Update concept-behaviors.md

Q
A

Is bugfix?
✔/❌

New feature?
✔/❌

Breaks BC?
✔/❌

Tests pass?
✔/❌

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

Thanks.


feat: Forget-Password,User-Activate and Email Service integrated

In this PR
Email service is done using Sendgrid dynamic templates
User Activation is now a feature and integrated with mail
Forget password is done which sends a email containing reset password link ,from where password can be reseted

Codecov Report

Merging #6 (02ca7d4) into main (c3d2819) will decrease coverage by 7.06%.
The diff coverage is 8.82%.

@@             Coverage Diff              @@
##               main       #6      +/-   ##
============================================
- Coverage     62.76%   55.69%   -7.07%
- Complexity      229      232       +3
============================================
  Files            61       65       +4
  Lines           913     1045     +132
  Branches         56       68      +12
============================================
+ Hits            573      582       +9
- Misses          316      438     +122
- Partials         24       25       +1

Impacted Files
Coverage Δ

.../delta/codecharacter/server/auth/AuthController.kt
28.57% <0.00%> (-38.10%)
:arrow_down:

.../server/auth/reset_password/ResetPasswordEntity.kt
0.00% <0.00%> (ø)

.../delta/codecharacter/server/user/UserController.kt
40.00% <0.00%> (-4.45%)
:arrow_down:

.../server/user/activate_user/ActivationUserEntity.kt
0.00% <0.00%> (ø)

...delta/codecharacter/server/user/SendGridService.kt
4.00% <4.00%> (ø)

...lin/delta/codecharacter/server/user/UserService.kt
8.53% <10.34%> (-0.73%)
:arrow_down:

...lin/delta/codecharacter/server/auth/AuthService.kt
16.66% <11.42%> (-19.05%)
:arrow_down:

...elta/codecharacter/server/config/SendGridConfig.kt
66.66% <66.66%> (ø)

...haracter/server/config/WebSecurityConfiguration.kt
76.92% <100.00%> (ø)

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 c3d2819...02ca7d4. Read the comment docs.


Aborted (core dumped) in LearnedUnigramCandidateSampler

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf2.17.0 tf2.16.1
Custom code
Yes
OS platform and distribution
Ubuntu 20.04
Mobile device
No response
Python version
3.11
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
On specific inputs,tf.raw_ops.LearnedUnigramCandidateSampler triggers crash.
Standalone code to reproduce the issue
import tensorflow as tf

true_classes = tf.constant([], dtype=tf.int64)
num_true =<PHONE_NUMBER>247644003
num_sampled = 126
unique = False
range_max =<PHONE_NUMBER>93039093
seed = 8997
seed2 = 0

tf.raw_ops.LearnedUnigramCandidateSampler(
    true_classes=true_classes,
    num_true=num_true,
    num_sampled=num_sampled,
    unique=unique,
    range_max=range_max,
    seed=seed,
    seed2=seed2,
    name=None
)

Relevant log output
2024-12-17 11:36:29.305345: W tensorflow/core/framework/op_kernel.cc:1816] OP_REQUIRES failed at candidate_sampler_ops.cc:37 : INVALID_ARGUMENT: Attr num_true has value<PHONE_NUMBER>247644003 out of range for an int32
2024-12-17 11:36:29.305378: F external/local_tsl/tsl/lib/random/weighted_picker.cc:28] Check failed: N >= 0 (0 vs. -2090015755)
Aborted (core dumped)

I tried running your code on Colab using the TensorFlow nightly version and encountered the same issue. Please find the gist here for reference.
Thank you


Update TweakScale to new repo by pellinor0.

As per #821, TweakScale has a new maintainer, and a new repo location.  This commit indexes that.
Attn @pellinor0, to check that everything here looks good.
Installed mod information (while it's not shown, v1.52 is taggedas being for KSP 0.90):
$ ckan.exe show TweakScale

TweakScale - Rescale Everything!: TweakScale lets you change the size of a part. Not just that, but it will figure out how much fuel is in the resized part. And if it's an engine, it will become more powerful by scaling it bigger, or weaker by scaling it smaller.

Module info:
- version:	v1.52
- authors:	Biotronic, pellinor
- status:	stable
- license:	WTFPL

Depends:
- ModuleManager, min:

Provides:
- TweakScale

Resources:
- homepage: http://forum.kerbalspaceprogram.com/threads/112693
- kerbalstuff: https://kerbalstuff.com/mod/344/TweakScale - Rescale Everything!
- repository: https://github.com/pellinor0/TweakScale

Showing 45 installed files:
- GameData/TweakScale
- GameData/TweakScale/BananaForScale_TweakScale.cfg
- GameData/TweakScale/MechJeb_TweakScale.cfg
- GameData/TweakScale/SpaceplanePlus_TweakScale.cfg
- GameData/TweakScale/DefaultScales.cfg
- GameData/TweakScale/KAX_TweakScale.cfg
- GameData/TweakScale/TVPP_TweakScale.cfg
- GameData/TweakScale/UKLD_TweakScale.cfg
- GameData/TweakScale/SDHI_SMS_TweakScale.cfg
- GameData/TweakScale/NP_TweakScale.cfg
- GameData/TweakScale/DeadlyReentry_TweakScale.cfg
- GameData/TweakScale/KW_TweakScale.cfg
- GameData/TweakScale/SXT_TweakScale.cfg
- GameData/TweakScale/Tantares_TweakScale.cfg
- GameData/TweakScale/TAC_Tweakscale.cfg
- GameData/TweakScale/TALCargo_TweakScale.cfg
- GameData/TweakScale/RLA_TweakScale.cfg
- GameData/TweakScale/Warp_TweakScale.cfg
- GameData/TweakScale/RealFuels_TweakScale.cfg
- GameData/TweakScale/FireSpitter_TweakScale.cfg
- GameData/TweakScale/KOSMOS_TweakScale.cfg
- GameData/TweakScale/KAS_TweakScale.cfg
- GameData/TweakScale/RealChute_TweakScale.cfg
- GameData/TweakScale/Karbonite_TweakScale.cfg
- GameData/TweakScale/ScaleExponents.cfg
- GameData/TweakScale/B9_TweakScale.cfg
- GameData/TweakScale/KH_SSE_TweakScale.cfg
- GameData/TweakScale/KSPX_TweakScale.cfg
- GameData/TweakScale/LLL_TweakScale.cfg
- GameData/TweakScale/plugins
- GameData/TweakScale/plugins/000Dummy.cfg
- GameData/TweakScale/plugins/Scale.dll
- GameData/TweakScale/plugins/KSPAPIExtensions.dll
- GameData/TweakScale/plugins/Licence.txt
- GameData/TweakScale/plugins/Scale_Redist.dll
- GameData/TweakScale/plugins/Scale_Editor.dll
- GameData/TweakScale/BetterRovemates_TweakScale.cfg
- GameData/TweakScale/AIES_TweakScale.cfg
- GameData/TweakScale/FusTek_TweakScale.cfg
- GameData/TweakScale/Kethane_TweakScale.cfg
- GameData/TweakScale/TweakScale.version
- GameData/TweakScale/NASA_TweakScale.cfg
- GameData/TweakScale/Squad_TweakScale.cfg
- GameData/TweakScale/NFT_TweakScale.cfg
- GameData/TweakScale/KSO_TweakScale.cfg

Closes #821.

Looks good to me.
Just one more question. As I understand CKAN auto-detects new versions. Where does it draw this information from (since there is version data in several places)?

@pellinor0 : In this case, it'll auto-detect from KerbalStuff releases. The KS API is really easy for our bots to use, so that's what I've chained this to:
"$kref" : "#/ckan/kerbalstuff/344"

The target version of KSP is actually read from KSP-AVC. This means you can have code that targets both 0.90 and 1.00 (when it exists), even though KS to the best of my knowledge lets you only specify a single KSP target:
"$vref" : "#/ckan/ksp-avc",

~ pjf

And since we've got a :+1: from @pellinor0 , I'm calling that code review, and merging. :)
The bot should have the new version indexed in a couple of minutes. Long live TweakScale! :)


Pretrainig Roberta for a Different Language than English, Using own data

Could someone help me with how to follow this guide https://github.com/pytorch/fairseq/blob/master/examples/roberta/README.pretraining.md to pretrain roberta for Turkish language. I tried a turkish dataset and did all the rest instructions same as in guide but I guess some of the files are English related. So which steps I should skip or maybe add in order to pretrain a model for Turkish language. I am quite new wiith the topic so a clear set of intructions would be great.
Thanks in advance

The readme provides examples for training your own dataset. If you have specific errors, please post those, this is a bit too vague

Hi @huihuifan  you are right. Actually I am going to close the issue with a reference to this #https://github.com/pytorch/fairseq/issues/1417  issue I opened and was answered. I believe it might be helpful for those search for a similar problem.

Thanks @ceatlinar !


Bump to Next 12

Upgrades to Next 12.
Tried enabling concurrentFeatures: true, but ran into https://github.com/vercel/next.js/issues/30714.

seems fine.


SimpleEspNowConnection missing return value

It is set to return a bool but never returns anything, which breaks compilation
bool SimpleEspNowConnection::DeviceMessageBuffer::deleteBuffer(const uint8_t *device, long id)
{
    for(int i = 0;i<MaxBufferSize; i++)
    {
      if(_dbo[i] != NULL && memcmp(_dbo[i]->_device, device, 6) == 0 && _dbo[i]->_id == id)
      {
        delete _dbo[i];
        _dbo[i] = NULL;
      }
    }
}

.../Arduino/libraries/SimpleEspNowConnection/src/SimpleEspNowConnection.cpp: In member function 'bool SimpleEspNowConnection::DeviceMessageBuffer::deleteBuffer(const uint8_t*, long int)':
.../Arduino/libraries/SimpleEspNowConnection/src/SimpleEspNowConnection.cpp:195:1: error: no return statement in function returning non-void [-Werror=return-type]
  195 | }
      | ^
cc1plus: some warnings being treated as errors

exit status 1

Compilation error: exit status 1

Thanks

bool SimpleEspNowConnection::DeviceMessageBuffer::deleteBuffer(const uint8_t *device, long id)
{
for(int i = 0;i<MaxBufferSize; i++)
{
if(_dbo[i] != NULL && memcmp(_dbo[i]->_device, device, 6) == 0 && _dbo[i]->_id == id)
{
delete _dbo[i];
_dbo[i] = NULL;
}
}
retrun true
}

Still a couple of minor problems.
Try this:
bool SimpleEspNowConnection::DeviceMessageBuffer::deleteBuffer(const uint8_t *device, long id)
{
for(int i = 0;i<MaxBufferSize; i++)
{
if(_dbo[i] != NULL && memcmp(_dbo[i]->_device, device, 6) == 0 && _dbo[i]->_id == id)
{
delete _dbo[i];
_dbo[i] = NULL;
}
}
return true;
}

I'll leave this here #18


Android Manifest RTL issue.

Encountered this issue after building with android.

If you don't care about RTL support in your app, you can add this to your config.xml to avoid the conflict
 <edit-config file="app/src/main/AndroidManifest.xml" mode="merge" target="/manifest/application">
    <application android:supportsRtl="false" />
 </edit-config>


image-cache-it and pager require nativescript-permissions and date-fns

The plugins @nativescript/image-cache-it and @triniwiz/nativescript-pager both require nativescript-permissions and date-fns, even though those dependencys are never used.

Seems like a packaging issue , will fix.

image-cache-it should be fixed now - @triniwiz if you pull latest you can bump a patch for pager as well to close this.

pager published with fix in 13.0.4 now as well.


Implement todict and fromdict for ASE calculator

Contributor (creator of pull-request) checklist

[x] Tests updated (for new features and bugfixes)?
[ ] ~Documentation updated (for new features)?~
[ ] ~Issue referenced (for PRs that solve an issue)?~

Reviewer checklist

[ ] CHANGELOG updated with public API or any other important changes?

📚 Documentation preview 📚: https://metatensor--472.org.readthedocs.build/en/472/

I did not realize this was dumped at every timestep. Agreed that this is not ideal. If the user gave us the path to a model, saving the path again makes sense, not sure how we should handle the case where the user gives a large in-memory model.

Yeah, it looks like this gets called at every timestep: https://gitlab.com/ase/ase/-/blob/master/ase/io/trajectory.py#LC174. I don't think this gets used by particularly serious MD codes, so maybe this is completely fine, but it should probably at least be documented in case someone wonders why their .traj files are extremely huge...

Okay, I saw your comment now. As far as I know, this is not a required interface for ase.  The only thing you need to have is a parameters dict (but it doesn't matter particularly what's in there). So one might want to write something informative there, like where we found the model that made up the calculator, but unless we have a pressing need to implement the todict/fromdict interface, I personally wouldn't bother keeping it around and having it potentially cause issues.

I've updated the code to store the model path in todict, which should solve the size issue. The error message should also point users who need this to work to save the model in a file themself.

As far as I know, this is not a required interface for ase.

It is part of the interface and used by some of the code in ASE =/. I agree that we should not be implementing everything just for fun, but the idea is also that this project should be usable by people outside the lab, who might not take the time to report issues if something is broken for them. It seems to me that this code is simple enough to not add too much maintenance work in the future =)

Sounds good -- what I meant is that ase (as far as I know, as discussed in Slack) doesn't expect these functions to do anything very well-defined, and I think in principle one can get away with only todict and not fromdict. I think this is a good compromise, we can always adjust further if user needs arise. Once the pipeline is done, this can be merged. Thank you!

codecov is not behaving today ...


Add support for getting Funding wallet addresses in Bitfinex

The Bitfinex API implementation is hardcoded to use the exchange wallet to get an address. I would like to extend this to support returning addresses for the Bitfinex funding wallet. Given that the GetAddress method is in the ExchangeAPI and is common to all Exchange implementation I'm just wondering what the best way to implement this would be ? The two simple options I see are

Add a new method only to the BitfinexAPI code to expose this
Add an optional parameter to GetDepositAddressAsync allowing the wallet name to be specified

e.g.
public virtual async Task<ExchangeDepositDetails> GetDepositAddressAsync(string currency, bool forceRegenerate = false, walletName = "")
Neither feels like a great option. I'm happy to make the change and submit the PR but would welcome any comments or suggestions on the best way to implement this.

Closing old issues, someone can submit pr if this is still an issue


Flake8 rule 'F821' reported an invalid point

Flake8 reported an invalid point for the rule F821, with the messge undefined name 'text'.
Debug information:
Atom version: 1.26.1
Flake8 version: 3.3.0 (mccabe: 0.6.1, pycodestyle: 2.3.1, pyflakes: 1.5.0) CPython 3.6.0 on Darwin

This is unlikely to be a bug in the parsing of flake8's output here, but it is possible. Are you able to share the file in the state that shows this error? If not, can you create a minimal reproduction case that you can share?
If this turns out to be a bug in flake8 it will need to be forwarded on to them before it is fixed.


ism330dhcx: sensor initialisation fails if sensor is in unknown state

Describe the bug
Said sensors initialisation function ism330dhcx_init_chip does not work properly if the sensor ends up in some unknown state where it does not function properly. The function tries to first read chip ID which will fail and then fail the initialisation.
An easy fix for this is to move ism330dhcx_reset_set before ism330dhcx_device_id_get.
To Reproduce
No specific reproduce method, the sensor just ended up randomly in a state where all reads return zeros or carbage until power cycling the sensor.
Expected behavior
Sensor initialisation should reset badly behaving sensor and carry on with initialisation.
Impact
The impact was small because I could power cycle the system but in feature that will not be possible and the sensor will get stuck un-initialisable.
Logs and console output
None
Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK
Version 3.3.0 (problem persist in newer versions)
NXP LPC55S69

Additional context
I could have fixed this myself and made a pull request but it is possible that more sensors than this use the same logic and can experience the same issue. Someone should probably look into this.

@avisconti please take a look


Fix macOS patches

Removed fix-widevine patch
Fixed visibility.cc type error
 no viable conversion from returned value of type 'unique_ptr<base::ListValue, default_delete<base::ListValue>>' to function return type 'unique_ptr<base::Value, default_delete<base::Value>>'

Fixed memory_mapped_file error (probably this error exists only on 10.11)
memory_mapped_file_posix.cc:119:26: error: non-constant-expression cannot be narrowed from type 'size_t' (aka 'unsigned long') to 'off_t' (aka 'long long') in initializer list

Don't merge it yet. I think my mapped_file fix isn't really a fix.
Chromium started to hang indefinitely (in uninterruptible state) so only system restart is able to kill it.

or may be it is a different problem, because according to:
https://chromium.googlesource.com/chromium/src/+/0413fd9f7c660ba7504dade7bb838862f138348e/base/files/memory_mapped_file_posix.cc#104
it is supposed to fallback to manual mode on everything that is not APFS.
So, this version is unstable for some other reason.

nope. Still crashing. So it's definitely something else.

Alright. Let me know when it's ready to be reviewed.

It is ready.
The problem is not with my patches. But I need someone else to confirm it.

@tectiv3 I can. Just let me get your build image.

@tectiv3 This PR builds and doesn't crash, but #315 still persists

@Artur96 it doesn't crash for me immediately. First time it did after a couple of hours of actively using it.

The formatting looks fine, but I don't have the time to review the changes themselves to see how it works.
If you know how to reproduce the issue, you could try building with debug symbols and running a debugger. If you aren't able to diagnose the issue or resolve it, I can merge the changes and then create a new issue for this problem.

@Artur96 it's been two days, how does it work for you so far?

@Artur96 Do you have a method to reproduce the crash or a stack trace? I would like to see if that crash will happen on my build.
The only patches I can tell that deal with TemplateURLRef directly are inox-patchset/0008-restore-classic-ntp.patch and ungoogled-chromium/disable-google-host-detection.patch. Though, nothing particularly stands out that could cause a crash in either of them.

@Artur96 does it actually crash? Because for me it's just freezing and ps reporting main chromium process is in uninterruptible wait (UE status).

@tectiv3 It did actually crash, I have a crash report.
@Eloston Unfortunately, not really. I was using the omnibox to perform a search.

for me it also freezing on search

Could you guys try removing ungoogled-chromium/add-flag-for-search-engine-collection.patch and see if the crash still happens? If it does, try different combinations that include ungoogled-chromium/disable-google-host-detection.patch and patches/inox-patchset/0008-restore-classic-ntp.patch (these last two patches involve Template URLs in some form, but they don't modify them to the same level as the search collection patch).
Also, does the freezing happen consistently on every search, are there some fixed conditions that make it freeze/crash, or is it seemingly random?

I am not sure, cause first time I built and run it - it was couple of hours before it froze, but now I do remember it was on search.
I'll try it now.

Disabled ungoogled-chromium/add-flag-for-search-engine-collection.patch.
So far so good...

Hmm, If @Artur96 can confirm, then I will investigate the patch.

@Eloston So far the most probable way of inducing the crash is by typing webrtc test into the omnibar and clicking on the first result in DuckDuckGo. I'll try building without the mentioned patch and see if the crash still occurs.

@Artur96 What is that first result that you find on DuckDuckGo? Perhaps that page is causing the issue.

@Eloston https://test.webrtc.org/, it doesn't always cause a crash.

Still good on my side, doesn't crash on any DuckDuckGo query.
@Artur96 can you please upload your crashpad patch? I'm very eager to try it.

Sorry to interrupt you guys, just wanted to let you know how much we, Mac users, appreciate your efforts. Ungoogled Chromium has been my main browser for a while now.
Thanks a a lot for your hard work!

@tectiv3 I've submitted a PR to your fork

@Artur96 running it now, all good!

I've uploaded my build here: https://github.com/tectiv3/ungoogled-chromium-binaries/releases/tag/64.0.3282.186-1

Alright, so here's what I'm going to do: I'll merge this PR first, and then @Artur96's fix for crashpad can be submitted as another PR. Then, I will create another issue to deal with the search collection bug.

@tectiv3 removing ungoogled-chromium/add-flag-for-search-engine-collection.patch does fix the crash.

@tectiv3 @Artur96 If you guys could check out #338, that would be great. I'm close to finishing the other changes for 64.0.3282.186-1, and would like to ensure that macOS support works.

okay, building it now

So far so good.