Update kubernetes-cni to v0.8.7

What this PR does / why we need it:
This PR is a proposal to update the kubernetes-cni to v0.8.7. The upstream Kubernetes is currently updating CNI from v0.8.6 to v0.8.7 for all supported releases.
The minimum version is still v0.8.6, but I think this is a nice-to-have change that shouldn't have side-effects.
Does this PR introduce a user-facing change?:
Update kubernetes-cni to v0.8.7

/assign @kron4eg

@kron4eg I forgot to update fixtures, PTAL again.

/cherrypick release/v1.0


Refactor the use of deprecated onKeyPress

Description
We have uses of onKeyPress in the application that need to be updated. It is used in the Clickable, ButtonCard, and TextInputWithBadges components. Keydown is an alternative to keypress.
Resource for Keyboard Events: https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code
Resource for Keyboard Events in React: https://reactjs.org/docs/events.html#keyboard-events

Acceptance Criteria
Update anywhere that onKeyPress is used.
How to Contribute
Please review the contributing documentation beforehand.
Steps to Contribute:

Fork the repository.
Clone it to your local system.
Create a new branch.
Make your changes. Make sure that tests are still passing. To update snapshot tests, run npm run test -- -u and include the updated tests in your commit.
Commit your changes.   For example, refactor: <component_name> tests.
Push up your changes. In GitHub, click the compare & pull request button to begin drafting your pull request.
Fill out the pull request form and attach the "ready for review" label when complete.

Hi @nataliepina, I'd love to grab this issue!


Any ways to Displays an Authenticated images in AdaptiveCards ?

Platform
What platform is your issue or question related to? (Delete other platforms).
Nodejs
host
Are you an author (like sending something to Outlook), or a host that is rendering your own cards?
Version of SDK
Bot builder v3
Issue
Based on adaptive cards schema document looks like we should use URL property where value should be direct URL to the image Or Data URIs are already supported by the nodejs Adaptive Card renderer.
I have BOT web app built using bot builder v3 sdk. I am planning to use adaptive cards to display users profile images which are stored on our secured server (most likely behind the firewall or azure blog storage ) and these are not available anonymously.
I would like to know if Adaptive Card's renderer will be able to parse/download authenticated images
if they are using same Bot Framework authentication
{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "Image",
            "style": "Person",
            "url": "",
            "size": "Small"
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.0"
}

Hi @rjgmail88, are you rendering the cards yourself using WebChat, or are these bot messages expected to work inside Teams or other clients?
If you're rendering the cards yourself using WebChat, you should be able to use our existing APIs to custom render Image elements and append authorization headers or inject custom logic along the way.
If your cards are expected to work in Teams, I'm not sure this is a supported feature right now. I see you have another issue on Data URIs, is this related, or would that feature work for both your issues?

Hey @matthidinger ,
Sorry I forgot to mention about the channels. We are using MS teams , Cortana for azure bot service. However, the plan is to go towards WebChat channel as well so we can drop this bot on our WebApps.
Can you point me to document or sample for existing APIs to custom render Image elements and append authorization headers
For MS teams bot we are using this Ms Graph AI to pull  users profile image.  But this API gives us raw bytes & I am not able to get it working with URI format & base64 conversation seems to be incorrect.
Here is the code.
let **dataBuffer** = new Buffer(body); --- body = binary data of an image.
let **dataBase64** =  new Buffer(**dataBuffer**).toString('base64');
const imagData = 'data:image/png;base64,' +**dataBase64**;

Few questions we would like to know:

In case of images , is Adaptive cards render resolving/downloading bobs & sending back to Ms teams , cortana to just render HTML or it's up to clients ( ms teams ) to handle it ?
If bot builder nodejs sdk is responsible to do this rendering then is there a way to use custom bot authentication to pull such images on the fly ?

@matthidinger Is there a solution for this yet? We are storing images in SharePoint and want to show them on Adaptive Cards in Teams. It works fine if the user is logged in to SharePoint but the images don't load if the user is not signed in. Any way to handle this scenario?

@billbliss this would be a question for you.

Have any more details on this been worked out?  I'm having a similar issue trying to use the adaptive cards designer and render an image from MS Graph API

Hi folks, I'm going to close this as a duplicate of #4763 - but we don't have a plan to solve it just yet. It is higher up on the priority stack though, so hopefully we can make some traction on it in 2021.

Dupe of #4763


Hardcoded TASK_HEIGHT_MAX does not look good on side bar.

Hi I have a 60 px width sidebar with but the task Icons are just 28 PX hight witch create tiny floating icons in a large side bar.
I did this dirty fix to fill my needs https://github.com/FredericGuilbault/fbpanel/commit/e52e17d0e9df342c702cf501ca97c978df2f90c8?diff=split
It defenitely look better:

But that would be great to have something clean.

Try not using bitmap icons at all. Pick a theme with all SVG icons.
And might be modify the code of fbpanel to display SVG.
And for enforcement make fbpanel accept only svg icons.
Just an idea


use $(which python3) in install.sh & cluster/up-generic.sh

Tested, merged.
also see https://github.com/PLEBNET-PLAYGROUND/plebnet-playground-docker/issues/128


Not all tasks run with --jobs=2 and SideEffect

This issue was originally created at: 2008-07-26 13:42:35.
This issue was reported by: gregnoel.
gregnoel said at 2008-07-26 13:42:35

Consider this SConstruct:
env = Environment()
env.Command('file2', 'log', 'cat >$TARGET $SOURCE')
env.SideEffect('log', env.Command('file1', [],
'echo >$TARGET data1; echo >log updated file1'))
Running 'scons -Q' produces the desired result (although the space after the '>'
is unexpected):
echo > file1 data1; echo >log updated file1
cat > file2 log
Running 'scons -Qc' also produces the desired result:
Removed file1
Removed log
Removed file2
However, running 'scons -Q --jobs=2' produces an unexpected result:
echo > file1 data1; echo >log updated file1
and the second command is MIA.  Running 'scons -Q --jobs=2' again finds the
second command:
cat > file2 log
This SConscript is used as an example in the Users' Guide; fixing it would be a
really good thing...

stevenknight said at 2008-07-26 14:42:43

Created an attachment (id=457)
Update test/SideEffect/parallel.py script demonstrating bug

stevenknight said at 2008-07-26 14:56:00

Okay, this is a definite bug.
It would have been caught if our test/SideEffect/parallel.py script had been a
little more real.  The SConstruct configuration in that script was already
configured in a way that triggers this bug, but the script itself didn't check
to see if the build of "log.out" actually succeeded, it only checked to see if
the entries in "log.txt" indicated things happened in the right order... :-(
I've attached a copy of the script that contains modifications demonstrating the
bug.
The issue here is that if you use a SideEffect() file as the source of another
Builder, it works fine in -j1 but not in parallel.  I'm assigning this to
Benoit, since he has deeper knowledge of how the Taskmaster should handle
parallel builds.
By way of a head start, I'm appending a context diff below of the
taskmastertrace output from running Greg's configuration with -j1 (the first,
longer, successful run) and -j2.  In the failing -j2 case, the SideEffect() file
(log) is already in "executing" state, which means we later treat it as already
handled.  This apparently means that the ref_count of the "file2" target that
depends on "log" never gets decremented, and it drops out of the search for
another node to execute, making Taskmaster think everything has finished.
I'm escalating this to 1.0.x P2.  For 1.0, I'll probably just comment out the
relevant section of Greg's new SideEffect() chapter in the User's Guide, in
favor of just documenting the current safe use as an interlock when multiple
commands might update the same file.
*** trace.1     Sat Jul 26 14:07:30 2008
--- trace.2     Sat Jul 26 14:07:42 2008

*** 19,53 ****
Taskmaster: Looking for a node to evaluate
Taskmaster:     Considering node <no_state   0   'file2'> and its children:
! Taskmaster:        <no_state   0   'log'>
Taskmaster:        <no_state   0   '/bin/cat'>
Taskmaster:  ['log', '/bin/cat']
Taskmaster:      adjusting ref count: <pending    1   'file2'>
Taskmaster:      adjusting ref count: <pending    2   'file2'>

Taskmaster:     Considering node <no_state   0   'log'> and its children:
Taskmaster:        <executed   0   'file1'>
Taskmaster: Evaluating <pending    0   'log'>

Taskmaster: Looking for a node to evaluate
Taskmaster:     Considering node <no_state   0   '/bin/cat'> and its children:
Taskmaster: Evaluating <pending    0   '/bin/cat'>

Taskmaster: Looking for a node to evaluate
! Taskmaster:     Considering node <pending    0   'file2'> and its children:
! Taskmaster:        <up_to_date 0   'log'>
! Taskmaster:        <up_to_date 0   '/bin/cat'>
! Taskmaster: Evaluating <pending    0   'file2'>

Taskmaster: Looking for a node to evaluate
Taskmaster:     Considering node <pending    0   '.'> and its children:
Taskmaster:        <up_to_date 0   'SConstruct'>
Taskmaster:        <executed   0   'file1'>
Taskmaster:        <executed   0   'file2'>
Taskmaster:        <up_to_date 0   'log'>
Taskmaster: Evaluating <pending    0   '.'>

Taskmaster: Looking for a node to evaluate

Taskmaster:     Considering node <up_to_date 0   'log'> and its children:
Taskmaster:        already handled (executed)
Taskmaster: No candidate anymore.

--- 19,38 ----
Taskmaster: Looking for a node to evaluate
Taskmaster:     Considering node <no_state   0   'file2'> and its children:
! Taskmaster:        <executing  0   'log'>
Taskmaster:        <no_state   0   '/bin/cat'>
Taskmaster:  ['log', '/bin/cat']
Taskmaster:      adjusting ref count: <pending    1   'file2'>
Taskmaster:      adjusting ref count: <pending    2   'file2'>
Taskmaster:     Considering node <no_state   0   '/bin/cat'> and its children:
Taskmaster: Evaluating <pending    0   '/bin/cat'>
Taskmaster: Looking for a node to evaluate
! Taskmaster:     Considering node <executing  0   'log'> and its children:
! Taskmaster:        already handled (executed)
! Taskmaster: No candidate anymore.
Taskmaster: Looking for a node to evaluate
Taskmaster: No candidate anymore.

stevenknight said at 2008-07-26 14:56:34

Actually updating the Priority and Target milestone fields like I said I would.

gregnoel said at 2008-09-02 15:23:01

Move unfinished 1.0.x issues to 1.1.

stevenknight said at 2008-10-17 05:59:03

Update target milestone to 1.2.

gregnoel said at 2008-12-04 17:41:09

1.2 is frozen; issues that didn't make it into 1.2 are moved to 1.3.

gregnoel said at 2010-01-20 03:36:10

Not completed in time for the 1.3 release; move to 2.1 p1.

garyo said at 2011-03-10 18:03:13

Benoit is no longer involved with the SCons project, reassigning his issues back
to triage.

garyo said at 2012-09-01 10:01:49

Bumping all old issues targeted for past releases to 2.x.

ajf58 said at 2014-07-07 11:21:02

Works for me using SCons 2.3.0 on Linux.
$ scons -Q
echo > file1 data1; echo >log updated file1
cat > file2 log
$ scons -Qc
Removed file1
Removed log
Removed file2
$ scons -Q --jobs=2
echo > file1 data1; echo >log updated file1
cat > file2 log
Suggest marking as resolved (fixed).

dirkbaechle said at 2014-07-12 03:43:38

When patching the test/SideEffect/parallel.py as suggested by Steven, it fails on
my system (Ubuntu LTS 14.04 LTS, Python 2.7, SCons 2.3.2). So we can't close this
right now, it definitely needs further investigation and a fix that lets the
extended test pass.

stevenknight attached parallel.py at 2008-07-26 14:42:43.

Update test/SideEffect/parallel.py script demonstrating bug

I just tried this, because it's the same example that is in a User Guide chapter (as noted in the initial filing), which is being excluded from the guide presumably because of this issue.  It seems to work fine.  What's more, the extended testcase, if ported to Python3, also passes. How to proceed?  Close-as-fixed? Update the testcase and close? Other?  And in particular - what to do with the userguide chapter?  I don't know where in the order it was intended to be.

Yes.
I think update the extended testcase attach to this issue.
Then close as fixed in 4.0.1+


changed service definition to fit symfony 3 requirements

related links

http://symfony.com/doc/current/components/dependency_injection/factories.html
http://stackoverflow.com/questions/34881570/convert-factory-class-and-factory-method-to-factory-in-services-xml

Thanks for all your work and maintaining! :)


Archive copy files does not copy folders

Should a folder be matched by a copy file re pattern it is not copied. This should be changed so it is.

Addressed in #134


micro sometimes truncates files to 0B when running out of disk space

Description of the problem or steps to reproduce
When disk space is low, micro will sometimes delete the contents of files it opens, along with micro's settings.json (results in "Error reading settings.json, Unexpected EOF")
Unfortunately, I don't have an exact sequence of steps to reproduce, but this mishap occured thrice or more to me already, so I am pretty confident in the validity of this report.
Specifications

Version: 2.0.8-dev.15
Commit hash: 530041ac
OS: Linux
Terminal: Konsole

Hello, I have encountered this issue multiple times, sometimes it also truncates the current source file I am working on and I lose all my work.


⚠ Bofrost.de has degraded performance

In 01550e0, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1284 ms

Resolved: Bofrost.de performance has improved in a36af70 after 6 minutes.


update rnncell synops calculation

Updating LSTMCell and GRUCell synops calculation,
Previously the reshape of ifgo/rzn for the LSTM/GRU blocks assumed batch=1 and flattened the hidden features.
Changed to arbitrary batch size.
No difference in output for the unittests or LSTM example for mackey_glass.

@korneelf1 Can you check over these changes to see if they look correct?


fails to parse if the name is an email address

><EMAIL_ADDRESS><EMAIL_ADDRESS>null
><EMAIL_ADDRESS><EMAIL_ADDRESS>null
><EMAIL_ADDRESS><EMAIL_ADDRESS>null

The following options should be useful to address the issue:

atInDisplayName - Allow the @ character in the display name of the email address. Default: false


containers in docker 1.11 does not get same MTU as host

This issue is the same/similar to the issues documented in #22028 and #12565, and is being opened under a new issue at the request of @thaJeztah.

BUG REPORT INFORMATION
Output of docker version:
Client:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:40:36 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:40:36 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 8
 Running: 8
 Paused: 0
 Stopped: 0
Images: 8
Server Version: 1.11.0
Storage Driver: devicemapper
 Pool Name: docker-253:1-260061060-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 2.418 GB
 Data Space Total: 107.4 GB
 Data Space Available: 79.62 GB
 Metadata Space Used: 6.398 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.141 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-12-01)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 3.10.0-327.13.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.64 GiB
Name: summit-training-gse.novalocal
ID: JOSZ:IGGB:P4V5:ADQH:HSZM:XFFE:TSNR:LUWM:FQAC:N6FC:TZOM:GNKC
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.):
Docker running in a CentOS 7.2 VM on RedHat RDO (Liberty) OpenStack cloud.
Steps to reproduce the issue:

Create a docker container
Compare MTU on container with MTU on host
Try a command such as apt-get update that would typically have large packets that might fragment

Describe the results you received:
Host interface info:
eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> **mtu 1400** qdisc pfifo_fast state UP qlen 1000
Container interface info:
eth0@if32: <BROADCAST,MULTICAST,UP,LOWER_UP> **mtu 1500** qdisc noqueue state UP group default
Requests originating from the container that have packets larger than 1400 are dropped
Describe the results you expected:
I would expect functionality on par with pre-1.10 docker, where users could expect networking to work without user intervention in the form of setting the MTU on the daemon (since there is no sysconfig or other environmental configuration mechanism, this literally means editing the service script), editing the docker related iptables rules, or adjusting the MTU on the container.
Additional information you deem important (e.g. issue happens only occasionally):
The other tickets referenced have identified a couple workarounds including setting the --mtu flag on the docker daemon.  That didn't work for us.  After dropping the container and image, adjusting daemon args, and starting the container again, the MTU in the container remained at 1500 while host was 1400.
Our workaround involves inserting an iptables rule to mangle the packets in transit between the host and container:
iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS  --clamp-mss-to-pmtu
(see: https://www.frozentux.net/iptables-tutorial/chunkyhtml/x4721.html)
I wouldn't consider any of the workarounds referenced to be a fix for this issue.  In my opinion, the fix for the issue is to have the container MTU match host interface MTU upon container creation without user intervention.

After dropping the container and image, adjusting daemon args, and starting the container again, the MTU in the container remained at 1500 while host was 1400.

Hm, that wasn't clear from your previous comment; how did you set the --mtu for the daemon, and are you sure this setting was picked up by the daemon? Did you use a drop-in file for systemd? Have you run systemctl daemon-reload after making those changes?
Adding --mtu 300 to my daemon options, and running a container, this looks to work for me;
docker run --rm debian:jessie sh -c "ip a | grep mtu"
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1
4: ip6gre0@NONE: <NOARP> mtu 1448 qdisc noop state DOWN group default qlen 1
11: eth0@if12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 300 qdisc noqueue state UP group default

I just confirmed proper functioning of the --mtu flag in our lab, so that was a red herring.

In my opinion, the fix for the issue is to have the container MTU match host interface MTU upon container creation without user intervention.

Setting the container MTU to the host MTU is a hack. We shouldn't be implementing hacks to solve network issues.
What if your box has a second route, with an MTU bigger than the default route, your containers will still have issues using this alternate route.
The proper solution is to figure out why PTMU discovery is apparently not working.

I'm also seeing this issue in a Docker-on-OpenStack environment. The host instance has MTU 1400, Docker brings up docker0 with MTU 1500, network performance suffers.

Setting the container MTU to the host MTU is a hack. We shouldn't be implementing hacks to solve network issues.

Agreed, but reverting commit fd9d7c0 would allow many/most common use cases (container host with a single network interface) to work again without user intervention to set the MTU.

network performance suffers

Do you have any evidence to support this? Unless you've turned PMTU discovery off, once the kernel has found the MTU, it should persist it, and effectively your MTU becomes 1400.

Yes, I have a system demonstrating this available to me now.
The hypervisor host has MTU 1500. Instance traffic is VXLAN encapsulated which means the instances get a lower MTU set, i.e. the 1400 shown here. (This is similar to the IPSEC encapsulation scenario at the start of this issue.)
root@trusty-instance:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether fa:16:3e:77:15:ec brd ff:ff:ff:ff:ff:ff
3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether 02:42:49:1d:61:c3 brd ff:ff:ff:ff:ff:ff
9: veth9d6a511: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default
    link/ether 2a:dc:b6:b3:b1:c0 brd ff:ff:ff:ff:ff:ff

Docker containers set the MTU to 1500:
root@8a9c9641a12e:/# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
8: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether 02:42:c0:a8:03:01 brd ff:ff:ff:ff:ff:ff

and large transfers hang after the initial handshake:
root@8a9c9641a12e:/# apt-get update
Ign http://archive.ubuntu.com trusty InRelease
12% [Waiting for headers]

tcpdump shows no ICMP fragmentation-needed packets on any of the interfaces.
net.ipv4.ip_no_pmtu_disc = 0 on the instance and the hypervisor host.
If I set --mtu=1400 or do docker run --net=host then the problem does not appear. It's due to Docker using a Linux bridge with a too-large MTU. Looks like this issue too: https://github.com/docker/docker/issues/12565#issuecomment-95226447
Let me know if there's anything else I can provide to help.

hanging isn't the same as degradation. hanging is almost always indicative of something blocking icmp packets. I've tested this scenario and was never able to replicate any issues (on a vanilla box, with no tweaks). How customized is the host? Your prompt looks like you're running ubuntu trusty. Is this stock trusty, or a modified distribution, where did it come from, etc?

I've seen the exact situation with Docker on OpenStack. Performance suffers, building an image with apt-get upgrade can take hours. We were setting the --mtu flag manually and restarting the docker server but with Docker 1.12 and docker-machine, it's become problematic.

docker run --rm debian:jessie sh -c "ip a | grep mtu" does give me the expected MTU value as configured in with the --mtu flag in docker 1.11.2 and 1.12.x ...
... but doing a run or up through a compose setup (using default network_mode and no custom network config) the networks created (br-xxxxxxx) will use 1500 MTU regardless of the --mtu flag. (1500). docker-compose run --rm myservice sh -c "ip a | grep mtu" says 1500.

Simple workaround for OpenStack: (I will use 1450 MTU in this example)
Make sure to pass the correct --mtu=1450 to the deamon so the host network gets the right mtu.
The bridge networks created by compose will still get the default 1500 mtu.
We can fix this by overriding the default network in the compose file (version 2)
networks:
  default:
    driver: bridge
    driver_opts:
      com.docker.network.driver.mtu: 1450

You probably have to manually delete the old network created by compose as you will probably see a message like ERROR: Network "<network_name>" needs to be recreated - options have changed. This need to be done every time you do any changes to the network. (optionally you can get compose to use a different network name so you are not obstructed by this issue as a quick fix if you have a lot of hosts to work with)
This is equivalent of doing a docker network create -o "com.docker.network.driver.mtu"="1450" <network_name>, so if you prefer to manage your networks manually, this is what you do.
Just overriding the default network to your manually created external network is also easy.
networks:
  default:
    external:
      name: <network_name>

When creating bridge networks manually, do not get confused by the initial mtu set on the interface. It will report an mtu of 1500, but as soon as you run containers, the values will adjust.

The same issues as described by @einarf above persists in Docker 1.12 (should thus add the 1.12 label as well)!

From  @jxstanford comment, if I undertood correctly, the original problem reported by this issue turned not to be a real problem:

I just confirmed proper functioning of the --mtu flag in our lab, so that was a red herring.

Therefore I believe this issue should be closed.
@einarf Regarding your unexpected mtu value, please be aware the docker daemon --mtu flag only affects the default bridge network.
We do not have a --mtu first class flag for docker network create command yet, so the way user can set the mtu for a custom network is via options:
docker network create --opt com.docker.network.driver.mtu=<value> <nw name>
Same should be possible in your compose file via driver_opts field.
If not please open a dedicated issue for that.

@aboch Yep, that is all covered in my last post :)

Thanks @aboch @einarf for confirmation. Lets close this issue.

Maybe i'm missing something, but is the title of this issue, "containers in docker 1.11 does not get same MTU as host" actually addressed?  Yes, --mtu works, but that's a work-around for Docker not determining the correct MTU on its own.

@dsmiley
In another PR (will update later when I find it) it was decided to drop the behavior where the mtu for the containers running on the default bridge network would be inherited from the host (there were valid concerns with that approach and @phemmer  IIRC lead the discussion).
Based on that we would not restore the original behavior which is what this issue was initially asking.
As it usually happens, other issues piled on this one. In this case they were due to incorrect assumption that the --mtu option was not working or that it would affect user-defined networks.
Given the original request won't be addressed and the other two sub-issues were addressed, we decided to close this issue.
Besides this, there in fact seems to be an outstanding issue about path MTU discovery, but there are already more specific issues opened for that.


Make sync_all API format to sync-all

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
curent api format: /v1/storages/sync_all
it should be:
/v1/storages/sync-all
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Dolphin(release/branch) version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

@PravinRanjan10 please check this

fixed in #211


Parse nodeIDs

This change allows for a parsing of note IDs. This is the first step in allowing (eventually) the automatic storing of the created note ID in the markdown file.

@benjamin-weller could you explain where these noteIDs come from? Why are they added and what is generating them, the markdown would be hand written most of the time. I may be missing some context here

These note IDs are uniquely generated by Anki (example:
)
See the note/card ID section of the browser search documentation here.
IIUC these IDs uniquely identify the note in question; as such you could eventually update a specific note given its parsed note ID.
How I intend to eventually allow for updating of already created notes:

Parse noteId out of the comments (this change)
When creating the deck/uploading the cards to Anki via AnkiConnect simply check and see if a note ID is set when we parsed the card from markdown (if the ID is set, and isn't some sentinel value then let's call AnkiConnect to update the card instead of trying to create it, see here: )

Now that there's a way for us to update notes, I would like to have a way for us to automatically insert the note IDs into the markdown during the deck/note creation command.
How I intend to get/insert the note ID into markdown:

Call Anki: Send To Deck (or other creation command) in VS Code
This creation command will eventually call AnkiConnect to create the notes via addNotes:

Following the creation, AnkiConnect will respond to us with the note IDs of the created notes, I would then insert these IDs into the markdown via the edit API

Hey @benjamin-weller great work on making a start on this, I wasn't ignoring it was just the holidays and I didn't have time to look over this. Hopefully I should have a bit more time now.
Thinking about the workflow here...
Someone will create a note in VS Code, when they send it to Anki, AnkiConnect gives us an ID back in the response I believe. Are you planning to take the ID and insert it back into the markdown once sent? (I understand this PR doesn't deal with that right now)
Do you have an idea how this comment will look like?

100% no worries, you've been very responsive before and honestly I have no expectations around super prompt responses, this is OSS; not much money changing hands here.

Someone will create a note in VS Code, when they send it to Anki, AnkiConnect gives us an ID back in the response I believe. Are you planning to take the ID and insert it back into the markdown once sent? (I understand this PR doesn't deal with that right now)

Yes, that's the ultimate goal
Yes the comment should look like <!-- notecardId: ###### --> or <!-- notecardId = ###### -->. I've generally tried to be tolerant of spaces in my regex.

Looks good, ive just noticed the CI isn't checking linting, so i may need to sort that out before i merge this

Hey @benjamin-weller, maybe im doing something wrong here but could you explain why noteId isn't coming through when I test it?

I've also realised this repo doesn't support proper linting so im going to sort that out. I will PR it, you may need to rebase apologies in advance

Sounds good I'll rebase here.
The unit tests pass and that's what I tested against, can you give me a direction as to how to set up your testing environment?
Is it like building a trial/test version of the extension and installing that?

Sure
https://github.com/jasonwilliams/anki/blob/main/CONTRIBUTING.md#debugging
I clicked "Run & Debug" icon on the left, then clicked the play button next to "Run Extension".
This should launch another instance of VSCode, I used that to test. In the original instance you should be able to set breakpoints and inspect the code

Preliminary investigation is leading me to confusing places:

I'll continue to debug.

I don't know why the regex wasn't working with my previous setup, but I manually tested, and ran the unit tests both pass.
Here's what I get during manual debugging:

Awesome work thanks, I’ll take another look. Also it seems there’s a conflict with package.json, you may need to try and rebase

Your lockfile causes conflicts, like its trying to set it back to version 1, what version of nodejs/npm are you using? Everything else seems ok

Ok, I'm relatively new to the git flow, please let me know if my changes here match up and can be merged.

LGTM

Hey @benjamin-weller now this is merged what are your next steps?

I've outlined what I intend to do next here.


1.0.3 breaks my storybook config styles

So I recently tried upgrading to from 1.0.2 to 1.0.3 and all the modular styles seemed to get broken. I'm running pretty much stock standard storybook config, with your preset addon.
// .storybook/main.js

module.exports = {
  stories: ['../src/**/*.stories.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx)'],
  addons: [
    '@storybook/addon-links',
    '@storybook/addon-essentials',
    '@storybook/addon-knobs',
    'storybook-css-modules-preset',
  ],
};

dep versions:
"@storybook/addon-actions": "^6.0.28",
"@storybook/addon-essentials": "^6.0.28",
"@storybook/addon-knobs": "^6.0.28",
"@storybook/addon-links": "^6.0.28",
"@storybook/react": "^6.0.28",
"storybook-css-modules-preset": "^1.0.3",

my guess is this regex change broke the css-loader's rules for detecting css module files:
https://github.com/Negan1911/storybook-css-modules-preset/commit/77860b22e8617deaf06188dd542cbe0a22ef1011

Thanks for the issue, i'll downgrade and investigate a way to cover both issues!


Merge account feature creating more accounts

I had multiple USDC accounts and wanted to merge them. After hitting 'merge tokens', the USDC accounts were still there and I ended up with multiples of all my other token accounts. I have tried a few more times and still have double of most tokens and even FIVE of one of them.

This is intended. The merge feature should be renamed to "Create associated token accounts", since it no longer removes token accounts (which is a dangerous operation).

It certainly should be renamed because this is terrible UX.


Use get_word so that the word is the same as in core.confirm

Problem
Build a CompletionResponse in the following way:
local label = cursor_before_line .. suggestions
-- CompletionResponse
{
  label = label,
  word = label,
  textEdit = {
    range = {
      start = { line = line, character = character },
      ['end'] = { line = line, character = character },
    },
    newText = suggestions,
  },
}

When cursor_before_line is e and suggestions is mail, ghost_text will show ail and will be missing a character m.
However, when you preview it from <Tab>, the mail is displayed correctly.
Solution
Use get_word so that the word is the same as in core.confirm

This only works if there's a word field in the CompletionResponse, but it often isn't—certainly not if the completion comes from cmp-omni.
I've came up with another attempt to fix the same issue:
diff --git a/lua/cmp/view/ghost_text_view.lua b/lua/cmp/view/ghost_text_view.lua
index 19c9513..1af7ad9 100644
--- a/lua/cmp/view/ghost_text_view.lua
+++ b/lua/cmp/view/ghost_text_view.lua
@@ -88,6 +88,12 @@ ghost_text_view.text_gen = function(self, line, cursor_col)
   if self.entry:get_completion_item().insertTextFormat == types.lsp.InsertTextFormat.Snippet then
     word = tostring(snippet.parse(word))
   end
+
+  local irange = self.entry:get_insert_range()
+  if irange and self.entry.source_insert_range.start.line == irange.start.line then
+    word = string.sub(line, self.entry:get_offset(), irange.start.character) .. word
+  end
+
   local word_clen = vim.str_utfindex(word)
   local cword = string.sub(line, self.entry:get_offset(), cursor_col)
   local cword_clen = vim.str_utfindex(cword)

Since cword is set as string.sub(line, self.entry:get_offset(), cursor_col), word also needs to start with the characters between self.entry:get_offset() and the start of the insert range, if the insert range doesn't start at offset. Which it doesn't for completions coming from python3complete#Complete via cmp-omni, those look like this:
  {
    label = "service_command(service_name)",
    labelDetails = {},
    textEdit = {
      newText = "ice_command(",
      range = {
        ["end"] = {
          character = 12,
          line = 456
        },
        start = {
          character = 12,
          line = 456
        }
      }
    }
  }

This is after typing "serv" and triggering completions. newText doesn't contain the "serv", it just appends stuff to the end.
(Also, with such textEdits, replacing is completely broken because of the silly heuristic introduced in https://github.com/hrsh7th/nvim-cmp/pull/1177)


Add .TECH logo to website

We've partnered with .TECH to offer free domains to everyone that's a part of Hack Club. Formal announcement will be made soon about this.

This was closed by #227

Ah, good catch. Thanks!
On Sun, Apr 17, 2016 at 10:50 AM, Max Wofford<EMAIL_ADDRESS>wrote:

Closed #224 https://github.com/hackclub/website/issues/224.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/hackclub/website/issues/224#event-630439770

--
Zach Latta
https://zachlatta.com http://zachlatta.com


Incorrect formatting of some PMCIDs in EPMC's submission

Describe the bug
Some PMC references in the EPMC data are not formatted properly.
Observed behaviour
The data team has generated evidence from grounded co occurrences based on 22.01EPMC submission.
Of the 9 746 463 evidence strings, 2 of them have failed validation due to the pmcIds field.
An example: 'pmcIds': ['PMCPMC7610745']. The duplication of PMC is causing the error in both cases.
Expected behaviour
No validation error should be returned. We want to have the right prefix for the PMCIDs.
To Reproduce
Steps to reproduce the behaviour:

Clone the 21.04 branch of the evidence data source parsers (https://github.com/opentargets/evidence_datasource_parsers/tree/il-22.04/modules)
Follow the instructions to reproduce the environment
Run the EPMC evidence generation rule like snakemake epmc --cores all
See error

Additional context
Although the impact of the error is minimal, this causes our evidence generation pipeline to fail because we do not allow any validation error to occur.
We have decided that we do not want to write specific logic to address this in the code, we rather expect this fix to come from the data.

@saha-shyamasree I haven't checked how frequent this is on the whole co occurrences/matches sets. Could you please investigate?

@DSuveges @ireneisdoomed: I just checked the data. It's coming from the original XML provided by the PMC.
As I mentioned during the monthly meeting, the XML file formats have changed while implementing the incremental approach. I can confirm that the new file does not have this issue. So I will request to get back to this example when I submit the new data and check/confirm you are getting these anymore.


Updating state with useSearchParams on Select component causes multiple reenders

Description
When using Nexjjs's useSearchParams hook with Select component causes multiple reenders.
Link to Reproduction (or Detailed Explanation)
https://use-search-param-ark.vercel.app/search-param
Steps to Reproduce

Go to the reproduction
Open console
Change the select value

Ark UI Version
1.0.0
Framework

[X] React
[ ] Solid
[ ] Vue

Browser
Chrome
Additional Information
GitHub Repo: https://github.com/juliomuhlbauer/use-search-param-ark

https://github.com/chakra-ui/ark/assets/53458125/1473c7f6-570c-4c97-a581-3bf8f001e180

Also, it would be cool seeing an example of integrating Nextjs with url on state

I looked into this deeply today and found that it's a Next.js bug
https://github.com/vercel/next.js/issues/43691
https://github.com/vercel/next.js/issues/49881
In the meantime, you can use the good'ol history.pushState
const handleChange = (details) => {
        const params = new URLSearchParams(searchParams)
        params.set('city', value[0])
       // workaround until Next.js fix
        window.history.pushState(
          {},
          '',
          `/search-param?${params.toString()}`
         )
     }
}

But how do I read from the url with Nextjs? It would cause hydration problems

I opened an issue on Nextjs: https://github.com/vercel/next.js/issues/58684


Allow duplication of existing item [Suggestion]

Currently stock must be listed on an individual item basis, adding the ability to clone or duplicate listings for modification afterwards ensures quick listing of inventory.

Yes definitely. This will be for a version post 1.0.

Done


Update app-only-auth-powershell-v2.md

Docs Build status updates of commit 0632880:
:clock10: Full build: the average full build time is 17 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 0632880:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 59cbf1a:
:clock10: Full build: the average full build time is 17 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 59cbf1a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 6e77e72:
:clock10: Full build: the average full build time is 17 min(s) 46 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 6e77e72:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-BackendEngineExceptionError] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@Chris Davis<EMAIL_ADDRESS>as FYI about this build error.
Regards
Navin Gupta |  Program Manager II | Exchange Online
Check out the new EXO PowerShell V2 cmdlets -  https://aka.ms/exops-docs
From: opbld32<EMAIL_ADDRESS>Sent: Thursday, June 25, 2020 11:23 PM
To: MicrosoftDocs/office-docs-powershell<EMAIL_ADDRESS>Cc: Navin Gupta<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/office-docs-powershell] Update app-only-auth-powershell-v2.md (#5996)
Docs Build status updates of commit 6e77e72https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnavgupta1208%2Foffice-docs-powershell%2Fcommits%2F6e77e72616e6488f1880809d8fd9ca6b9986cf0f&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041006633&sdata=HPdg6T1kd60znqY%2FRKv1Z35dKZR47L69ouajS9a9Ur4%3D&reserved=0:
❌ Validation status: errors
Please follow instructions herehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fen-us%2Fhelp%2Fonboard%2Ffaq%3Fbranch%3Dmaster%23build--publish&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041006633&sdata=kNDcRr1Gv4Tz69Ccwsjd0OQMFvMdTf8Fh7T17PGvKvw%3D&reserved=0 which may help to resolve issue.
File
Status
Preview URL
Details
❌Error
Details

[Error-BackendEngineExceptionError] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build reporthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopbuildstorageprod.blob.core.windows.net%2Freport%2F2020%255C6%255C25%255C3603fd28-efce-f87f-e986-fc8a694fc312%255CPullRequest%255C202006251730444050-5996%255Cworkflow_report.html%3Fsv%3D2016-05-31%26sr%3Db%26sig%3DuNXQU5L6pr7G80ZY1dr%252FfB1QLSJA8BZV%252FaenCABQmxQ%253D%26st%3D2020-06-25T17%253A48%253A06Z%26se%3D2020-07-26T17%253A53%253A06Z%26sp%3Dr&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041016628&sdata=ergFP03h0vCwlELe26gL3qVBg7Gz9eMJL5GXZdx2I8k%3D&reserved=0.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions herehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fteams.microsoft.com%2Fl%2Fmessage%2F19%3A7ecffca1166a4a3986fed528cf0870ee%40thread.skype%2F1590030602688%3FtenantId%3D72f988bf-86f1-41af-91ab-2d7cd011db47%26groupId%3Dde9ddba4-2574-4830-87ed-41668c07a1ca%26parentMessageId%3D1590030602688%26teamName%3DDocs%2520Support%26channelName%3DGeneral%26createdTime%3D1590030602688&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041016628&sdata=Q62V%2B5OjA8QZwQvTZPcPCK%2BFW1FVaavK7GTMapgln%2Fk%3D&reserved=0 to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link reporthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fops.microsoft.com%2F%23%2Frepos%2F3603fd28-efce-f87f-e986-fc8a694fc312%3FtabName%3Dbrokenlinks&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041026620&sdata=jQZXifQ1b9wEHFObQG6gX7rr8Pa%2F0x1vPUgfIoK8aio%3D&reserved=0.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructionshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fen-us%2Fhelp%2Fonboard%2Ffaq%3Fbranch%3Dmaster%26tabs%3Dpr-validation-error-solution%23q-why-do-i-get-pr-validation-result-with-cryptic-error-or-warning-messages-not-related-to-the-changes-i-make-in-my-working-branch&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041026620&sdata=v36z%2B8%2B4ZJdzYnD3ZbPamqttBk4bOjVHKxim33hbBaM%3D&reserved=0 to resolve them.
For any questions, please:

Try searching in the Docs contributor and Admin Guidehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fen-us%2Fsearch%2F%3Fsearch%3D%26category%3DAll%26scope%3Dhelp-docs%26category%3DAll%26branch%3Dmaster&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041036612&sdata=clvDgU3%2ByUzQvi4SGiPjJeIXqA%2FAxtVOemFHWeoazro%3D&reserved=0
See the frequently asked questionshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.docs.microsoft.com%2Fen-us%2Fhelp%2Fonboard%2Ffaq%3Fbranch%3Dmaster&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041036612&sdata=3%2BwJQPZ1D9hrXZYYmlX5AwcQySOsXDXuEfbTZARuFjI%3D&reserved=0
Post your question in the Docs support channelhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fteams.microsoft.com%2Fl%2Fchannel%2F19%253a7ecffca1166a4a3986fed528cf0870ee%2540thread.skype%2FGeneral%3FgroupId%3Dde9ddba4-2574-4830-87ed-41668c07a1ca%26tenantId%3D72f98bf-86f1-41af-91ab-2d7cd011db47&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041046606&sdata=ylcsptsChJuhpprcHvnFxF9%2FOi1yPqZEc7NQ9DHKdxg%3D&reserved=0

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fpull%2F5996%23issuecomment-649729920&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041046606&sdata=rt0t2mrpd3hmpPnuaj2MvtYd%2BP6xrxyQ8YVVXvsgv2c%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMFUVNN4QNI2SFVOIJFNQVLRYOFJDANCNFSM4OHTZ3BQ&data=02|01|Navin.Gupta%40microsoft.com|e6b509c6914a40b3175008d81930a6f7|72f988bf86f141af91ab2d7cd011db47|0|0|637287044041056603&sdata=U6LRSzVVHUYBdQFmFjtmjtOCXY4MJECUqOyRqdn4Teg%3D&reserved=0.

Docs Build status updates of commit 6e77e72:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 513d935:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 6e77e72:
:clock10: Full build: the average full build time is 17 min(s) 46 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 6e77e72:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 513d935:
:clock10: Full build: the average full build time is 17 min(s) 44 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 513d935:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit dd29363:
:clock10: Full build: the average full build time is 17 min(s) 43 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit dd29363:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Fix typos in Windows 11 memory limits

Heading is Windows 11, but table entries are Windows 10, this is probably a typo.

@MSDN-WhiteKnight : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks for your contribution! I've merged your changes and they should be live soon.


cmd/scriggo: support transformation of package-less programs into programs

Implement a tool that, given:

a Scriggofile
a Scriggo script

generates a program source code that is 100% compatible with Go.
The Scriggofile must have a limitation: packages imported using main cannot have uncapitalize or selective importing. This allow to transform
IMPORT mypkg AS MAIN

into
import . "mypkg"

The script source code must be transformed in the following ways:

it's content must be encapsulated into a main function into a main package
functions defined using the script syntax must be converted to function literals assigned to variables
if the last statement of the script is an expression statement not valid in Go, such expression must be assigned to the blank identifier

Support for scripts has been removed in the commit f423f045394dc5364d9de0ec94413cc26af34a6c. Close this issue.


evaluation related----whether there are other methods that run in python environment to evaluate the weights or not

If there are other methods that run in python environment to evaluate the weights, please tell me as soon as possible, thank you very much!!!!!!!!!!!

hi, @xiangwentao666, I didn't get you. please give more details about "evaluate the weights"

Thank you so much for your timely reply!
I've finished all the three training stages, and also finished the inference process on all datasets. What I want to do right now is to evaluate the masks generated during the inference process, which could be done by running the scripts in the folder named "eval". However, the files in the "eval" folder are in the format of Matlab(each ends with ".m") and software "Matlab" might need to be installed(I'm actually not familiar with Matlab). So, I would like to ask you whether there exist other ways to accomplish the same purpose as the ".m" scripts can do.

hi, @xiangwentao666, I didn't get you. please give more details about "evaluate the weights"

Thank you so much for your timely reply!
I've finished all the three training stages, and also finished the inference process on all datasets. What I want to do right now is to evaluate the masks generated during the inference process, which could be done by running the scripts in the folder named "eval". However, the files in the "eval" folder are in the format of Matlab(each ends with ".m") and software "Matlab" might need to be installed(I'm actually not familiar with Matlab). So, I would like to ask you whether there exist other ways to accomplish the same purpose as the ".m" scripts can do.

Hi, @xiangwentao666
Thanks for your reaching out. There are two alternatives:

as for UVOS task, you can use evaluation toolbox of DAVIS: https://github.com/fperazzi/davis
as for VSOD task, you can use evaluation toolbox of VPS with small modifications: https://github.com/GewelsJI/VPS/tree/main/eval

Hope these resource helps you a lot.
Best.

Hi, @xiangwentao666
Thanks for your reaching out. There are two alternatives:

as for UVOS task, you can use evaluation toolbox of DAVIS: https://github.com/fperazzi/davis
as for VSOD task, you can use evaluation toolbox of VPS with small modifications: https://github.com/GewelsJI/VPS/tree/main/eval

Hope these resource helps you a lot.
Best.

Wow, detailed and helpful!
The solutions you mentioned will be considered, and actually I'm new to this area and new to research, so there could be many mistakes or much trouble.
Thank you for your reply and your patience!
AGAIN, thanks a million!!!!!!!!!!

Welcome. This issue has been solved.


Optimized Sha256 version working with u4

Hi!
I've been working on a new version of the sha256 on-chain script that works using u4 as basic unit size.
In the process of doing it I created some interesting optimized lookup tables that are used by the algorithm, and some more that I could not use because of stack limitation, but still might be usefull for other parts.
This is the comparisson between the current sha256 algo and the new one.

Algorithm
Current
New
Gain

sha256(32)
516K
344K
33%

sha256(80)
1043K
759K
27%

Great improvements! Thank you very much


Expand introductory JS project's array steps

My gf is going through the JS curriculum, and the first review project immediately starts off with constructing a loop to iterate through an array.
The introductory project teaches a LOT of loops, but only touches on array indices in a couple of steps. We may want to expand those steps - perhaps something like adding another loop instruction to loop through an array?

Maybe also include a for...of loop? Thought I taught that in there but apparently not.

Maybe also include a for...of loop? Thought I taught that in there but apparently not.

it's in there, but it may need reinforcement like the other things


Known valueAtDeviceReset : (208466.7) > known cumulative value (0) cannot proceed

Hello together,
maybe any can instruct me, how to handle this. I had a small crash and now i received this errors.
What can I do ?

Thanks for support
Thomas

hi, did yo have a look at he fax this error is explained there :)

hi, did you have a look at the faq this error is explained there :)

I had a look, but I don't understood what exactly to do


arch: cxd56xx: Use spinlock API in cxd56_uart.c

Summary

This commit improves cxd56_uart performance in SMP mode.

Impact

This commit affects SMP mode only.

Testing

Tested with spresense:smp

@jerpelea

LGTM but it is still building


How to open another one port when the original one does not exist

I'm trying to connect to an USB port that connect to a HMI to read data.
When I try to connect, the error shows "Error= Error: No such file or directory, cannot open /dev/ttyUSB0".
So I have to check list of /dev by using command and correct to another port like "/dev/ttyUSB1".
I would like to ask whether there is a better way to check the port exist inside my program by if...else... ?
Here is my code for this issue:
var serialPort = require("serialport");
var portOfHMI = new serialPort("/dev/ttyUSB0", {
    baudRate: 9600,
    dataBits: 8,
    parity: "none",
    stopBits: 1
});
portOfHMI.on("error", function (err) {
    console.log("Error= " + err.message);
 });
portOfHMI.on("data", function (data) {
    console.log("Data= " + data);
 });

Error= Error: No such file or directory, cannot open /dev/ttyUSB0

And, my version list is over here:

<EMAIL_ADDRESS>Node.js v14.16.0
Debian 9 OS
Beaglebone like Hardware

Hi @chungkai1029,
I think you might want to try searching for and selecting the device based on the vendor and product id of the device you are trying to communicate with.
For example we use something like:
async find(...devices) {
   let portList = await SerialPort.list();

   let found_devices = [];

   this.debugLog("focus.find: portList:", portList, "devices:", devices);

   for (let port of portList) {
     for (let device of devices) {
       if (
         parseInt("0x" + port.productId) == device.usb.productId &&
         parseInt("0x" + port.vendorId) == device.usb.vendorId
       ) {
         let newPort = Object.assign({}, port);
         newPort.device = device;
         found_devices.push(newPort);
       }
     }
   }

   this.debugLog("focus.find: found_devices:", found_devices);

   return found_devices;
 }

We have a few supported devices so store these in the 'devices' with appropriate device.usb.productId and device.usb.vendorId values.  If you are targetting just a single device you could simplify the code a little.
By seaching based on the IDs we only try to interact with supported devices and don't risk either trying to connect to a missing device or sending messages to someone else's kit.
This should address your issue above, and should also help make the code work on different operating systems which use different port names.
hope this helps
Gaz

Hi @chungkai1029 are you still facing any issues?  or is there any extra info that may be helpful?

Hi @GazHank , it's really helpful for me to use.
Thanks for your helping.


feat(eth-bytecode-db): update verifier alliance schema to v1

Updated verifier alliance migration and entity crates to use the latest v1 verifier-alliance database schema: https://github.com/verifier-alliance/database-specs/blob/master/database.sql
Updated verification-common library to support the latest schema
Initialized verifier-alliance-database crate responsible for all verifier-alliance data manipulations. Eth-bytecode-db will make use of it in the next PRs

Note: eth-bytecode-db was not updated and still uses v0 schema

@coderabbitai full review


Test packet relaying on ordered channels

Summary
In preparation for releasing ICA on the hub, we would like to do some testing that channel ordering works as expected in Hermes.
Proposal

set up ordered channels between 2 chains
provoke out-of-order packet relaying by either manually instrumenting the relayer code to drop the first event out of a batch, or by evicting transactions from thee node's mempool before they commit to the blockchain

Stretch goal:

benchmark the scalability properties of Hermes by deploying it on a server similar to real-world operator use, and assess how many channels can Hermes relay gracefully on such a machine

the bottleneck will likely be the chain software, not Hermes: confirm that by isolating the networks on machines separate from the one where Hermes is running.

Acceptance Criteria

capture a packet ordering corner-case in an automated test using the Rust framework

ensure that Hermes enforces ordering by looking at packet sequence numbers on an ordered channel

For Admin Use

[X] Not duplicate issue
[X] Appropriate labels applied
[x] Appropriate milestone (priority) applied
[x] Appropriate contributors tagged
[X] Contributor assigned/self-assigned

Testing this in a real setup appears to require a modified Gaia with the transfer module hacked to use ordered channels.
I guess we should go for a test case simulating out-or-order packet relaying in the test framework.

I have setup a Gaia branch that support ordered transfer channel at https://github.com/informalsystems/gaia/tree/v6.0.1-ordered.
Currently the Nix build at Cosmos.nix is not working due to the replace directive being ignored by the Nix Go builder: https://github.com/informalsystems/cosmos.nix/pull/63
You can still build the Go project manually, and expose the custom gaiad in $PATH. Then replace the bootstrap channel code from Order::Unordered to Order::Ordered.
After this you should see the some tests like test_ibc_transfer still passing, but tests like test_clear_packet failing. In particular, test_clear_packet would keep retrying because worker_stubborn_strategy is being used here.

Great progress!

After this you should see the some tests like test_ibc_transfer still passing, but tests like test_clear_packet failing. In particular, test_clear_packet would keep retrying because worker_stubborn_strategy is being used here.

Is test_clear_packet failing because (as we expected) Hermes submits out-of-order packets on the ordered channel? If so, then I would consider the first part of this issue done:

[x] find a way to reliably test ordered channels with Hermes

does Hermes relay correctly on ordered channels? Answer seems to be no.

One proposal for next steps that would be sensible is:

[ ] make Hermes aware of ordered channel errors, specifically:

Hermes relaying logic should be aware of channel ordering, namely, it should be aware when a packet relaying fails due to out-of-order submission
this can probably be achieved by having a specific error-case matching as we do for account sequence mismatch errors

[ ] make Hermes avoid retrying upon (out-of-order packet submission) failure occurs,

in other words, Hermes should not retry stubbornly

[ ] instead of stubborn retry, upon encountering the failure, the relayer packet worker should:

(a) trigger packet clearing immediately if clear_interval = 0 i.e., if periodic packet clearing is turned off, or
(b) drop the packet events and simply wait if clear_interval > 0, until periodic packet clearing kicks in

[ ] add a test that asserts that Hermes can correctly recover from out-of-order packet submission; this test would be similar to test_clear_packet except both packets that are sent should be relayed.

Any thoughts?

Notes on testing that relaying packets is done in order with @seanchen1991.

git clone git@github.com:informalsystems/gaia.git
git checkout v6.0.1-ordered
make install to install the patched gaiad binary

$ gaiad version
v6.0.1-ordered-34e6f66a3d729a36f51c9a7f5ffd211bcd1cd90c

switch to ibc-rs@master

using the patch below, all the assertions should pass in the following test
cargo test -- test_clear_packet

$ git diff
diff --git a/tools/integration-test/src/bootstrap/binary/channel.rs b/tools/integration-test/src/bootstrap/binary/channel.rs
index a07f9592..79886c79 100644
--- a/tools/integration-test/src/bootstrap/binary/channel.rs
+++ b/tools/integration-test/src/bootstrap/binary/channel.rs
@@ -82,7 +82,7 @@ pub fn bootstrap_channel_with_connection<ChainA: ChainHandle, ChainB: ChainHandl

     let channel = Channel::new(
         connection.connection.clone(),
-        Order::Unordered,
+        Order::Ordered,
         port_a.0.clone(),
         port_b.0.clone(),
         None,
diff --git a/tools/integration-test/src/tests/clear_packet.rs b/tools/integration-test/src/tests/clear_packet.rs
index ec9d0331..a9ff109e 100644
--- a/tools/integration-test/src/tests/clear_packet.rs
+++ b/tools/integration-test/src/tests/clear_packet.rs
@@ -14,7 +14,7 @@ impl TestOverrides for ClearPacketTest {
     fn modify_relayer_config(&self, config: &mut Config) {
         // Disabling clear_on_start should make the relayer not
         // relay any packet it missed before starting.
-        config.mode.packets.clear_on_start = false;
+        config.mode.packets.clear_on_start = true;
         config.mode.packets.clear_interval = 0;
     }

@@ -110,7 +110,7 @@ impl BinaryChannelTest for ClearPacketTest {
         // Wallet on chain B should only receive the second IBC transfer
         chains.node_b.chain_driver().assert_eventual_wallet_amount(
             &wallet_b.as_ref(),
-            amount2,
+            amount2 + amount1,
             &denom_b.as_ref(),
         )?;


Simplify only one property class conflict with polymorphism

Autorest.PowerShell will simplify the output to the child class if the output type only have one property. But this will conflict when the output is a base class of polymorphism.
Such as: SAPSizingRecommendationResult. The output type will be DeploymentType

The issue is duplicated with https://github.com/Azure/autorest.powershell/issues/952.


Split Parsing Config into separate package and use Pydantic

Separate package makes use outside databricks possible
Should only be file IO to read yaml -> get job config object
Requires some caching mechanism to not read the same config over and over again if the file was not changed
As pydantic allows for very easy schema generation, we might should include the schema in the repo and set the schema comment by default:

---
# yaml-language-server: $schema=GITHUBHURL

https://docs.pydantic.dev/latest/concepts/pydantic_settings/#parsing-environment-variable-values
Maybe use pydantic_settings?

I would place this in libraries/fabricks-config or so


Help Request: Using it without vue-loader

hey I am new to vue, I was wondering if I could easily translate the .vue component into normal JavaScript.
Can someone help me with that?

later, we will update to support this.


Enable device flag allowing to list all devices and select a specific one

allows to call
$ depthai_demo.py -dev list
Using depthai module from:  /home/vandavv/dev/luxonis/venvs/demo/lib/python3.8/site-packages/depthai.cpython-38-x86_64-linux-gnu.so
Depthai version installed:  <IP_ADDRESS>
Available devices:
[0] 14442C10A182BFD200 [X_LINK_UNBOOTED]
[1] 14442C1061EBAACE00 [X_LINK_UNBOOTED]

to list all devices or run the demo script on a specific device
$ depthai_demo.py -dev 14442C10A182BFD200

This will be nice to have - thanks.

@VanDavv only a nitpick but what if we rather do: --list / -l for this operation as its very common across all CLI programs.
And also then no need to special parse the -dev argument for this particular string.

@themarpe it makes no difference to me, but I would name it then --dev-list to be more specific about what does the param do. Although in this form it's pretty much the same as --dev list so basically a matter if we want to have a space or a dash there :slightly_smiling_face:

@VanDavv the param name being more descriptive here IMO doesn't help as once you have to checkup the actual param which to use for certain action, it doesn't matter that much anymore (from terms of speed / ease of use).
On the other hand, just trying out something which works almost everywhere else, is much faster.
But it might not be the best action for this parameter, maybe a list of examples/functionality/... would be better?
Either way, using -l I'd be nice in an appropriate case. Not sure which one would be more suitable.
I guess we can leave it as is for now


NEXT_NO_ROUTES_MANIFEST error during npm run tf-next

I tried following the setup guide but my build failed:
package.json excerpts:
{
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "tf-next": "tf-next build"
  },
...
  "dependencies": {
    "next": "^10.0.6",
    "react": "17.0.1",
  }
...
}

Running $ npm run tf-next produces this output:
><EMAIL_ADDRESS>tf-next /Users/sebastian/development/app
> tf-next build

Installing dependencies...
yarn install v1.22.4
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
success Saved lockfile.
✨  Done in 12.19s.
Running "yarn run build"
yarn run v1.22.4
$ next build
Loaded env from /private/var/folders/k0/41_ltq_d1v571z67g9bjb2h00000gn/T/tmp-75327-inHXi38AbvJA/.env.local
info  - Creating an optimized production build
info  - Compiled successfully
info  - Collecting page data
info  - Generating static pages (6/6)
info  - Finalizing page optimization

Page                                Size     First Load JS
┌ ○ /                               806 B          68.4 kB
├   /_app                           0 B            62.7 kB
├ ○ /404                            2.77 kB        65.5 kB
├ λ /api/s3-upload-token            0 B            62.7 kB
├ ○ /checkout                   5.18 kB        72.8 kB
├ ○ /reading                    95 kB           163 kB
├   └ css/4f6d1999152a411e8da4.css  135 B
└ ○ /review                     1.47 kB        69.1 kB
+ First Load JS shared by all       62.7 kB
  ├ chunks/commons.2ac29a.js        13.3 kB
  ├ chunks/framework.9d5241.js      41.8 kB
  ├ chunks/main.3ff250.js           6.32 kB
  ├ chunks/pages/_app.ce9584.js     545 B
  ├ chunks/webpack.50bee0.js        751 B
  └ css/a0d15b181925e64a7258.css    2.7 kB

λ  (Lambda)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)  automatically rendered as static HTML (uses no initial props)
●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)
   (ISR)     incremental static regeneration (uses revalidate in getStaticProps)

✨  Done in 20.38s.
Build failed:
NowBuildError: A "routes-manifest.json" couldn't be found. This is normally caused by a misconfiguration in your project.
Please check the following, and reach out to support if you cannot resolve the problem:
  1. If present, be sure your `build` script in "package.json" calls `next build`.  2. Navigate to your project's settings in the Vercel dashboard, and verify that the "Build Command" is not overridden, or that it calls `next build`.  3. Navigate to your project's settings in the Vercel dashboard, and verify that the "Output Directory" is not overridden. Note that `next export` does **not** require you change this setting, even if you customize the `next export` output directory.
    at Object.getRoutesManifest (/Users/sebastian/development/app/node_modules/@dealmore/next-tf/dist/index.js:37244:15)
    at async Object.build (/Users/sebastian/development/app/node_modules/@dealmore/next-tf/dist/index.js:35211:28)
    at async Object.buildCommand [as default] (/Users/sebastian/development/app/node_modules/tf-next/dist/commands/build.js:121:29) {
  hideStackTrace: true,
  code: 'NEXT_NO_ROUTES_MANIFEST',
  link: 'https://err.sh/vercel/vercel/now-next-routes-manifest',
  action: undefined
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>tf-next: `tf-next build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>tf-next script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/sebastian/.npm/_logs/2021-02-14T00_24_15_009Z-debug.log

Other local versions:
$ npm -v
6.14.5
$ node -v
v12.18.1

Figured it out:
I had  in my next.config.js:
module.exports = {
  distDir: 'build',
  }

removing the destDir solved the issue and the build completes:
...
✨  Done in 22.20s.
Traced Next.js serverless functions for external files in: 1745.201ms
Compressed shared serverless function files: 1385.656ms
All serverless functions created in: 73.771ms
409352 total bytes
Build successful!


docs: add config files documentation

Overview
Closes https://github.com/celestiaorg/orchestrator-relayer/issues/584
Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Summary by CodeRabbit

Documentation

Updated deployment command for Blobstream contract, simplifying parameters and clarifying usage.
Revised CLI command for starting the orchestrator, emphasizing flag precedence and config file location.
Modified relayer start command, emphasizing use of TOML config file and clarifying passphrase prompt.

Codecov Report

Merging #585 (b5f8fe6) into main (29598b1) will decrease coverage by 0.01%.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #585      +/-   ##
==========================================
- Coverage   26.64%   26.63%   -0.01%
==========================================
  Files          29       29
  Lines        2961     2962       +1
==========================================
  Hits          789      789
- Misses       2077     2078       +1
  Partials       95       95

see 1 file with indirect coverage changes


Add another unit test and also genetic algs

@FlyingGraysons Two things. We don't want a getting started markdown file. We are moving all tutorials to the site. Next, we don't need the tic tac toe genetic algorithm. That was just a fun little test that I made. It shouldnt be in the library.
Plz take those two things out.


Feature: copy code clipboard

It would be nice to copy the current code of an account to the clipboard. It would be a big ux improvement in combination with KDE connect or other clipboard share apps or when you want to sign in on the same device. And I think this is no security problem.

I just had exactly the same thought. A simple tap would suffice

:-) This was the first feature request. Alread discussed! See #1

@cornelinux Oh I didn't see this, sorry. Should I close this and write there? ;)
I my opinion you can't prevent people from logging in on the same device. But if people using clipboard sharing apps like KDE Connect,... there is no security problem at all. And one can show a toast notification like "Don't sign in on this device"...

This repo seems to be unmaintained, but there is a active fork, which is also in F-Droid: https://github.com/kckrinke/onetimepad


Enhancement: in JSON output mode, return error messages as JSON

Raised from #2285
In JSON output mode, we should return error messages as JSON so that they can be handled accordingly.
This is a breaking change and can be included in v4 later this year.

Hey folks, we could introduce this functionality behind an option so that it's not a breaking change. In v3, users could flip the option to enable this setting. In v4 we'd change the default option value which would be the breaking change. The cool thing about this approach is that we can implement all the code already and minimize the amount of work needed to go to v4.
/cc: @plamber

Let's start with introducing it behind an option in a backwards-compatible manner first and then have a separate issue for changing the default value of this option for v4.

This capability is definitely going to simplify further the output handling when scripting. How do we want to call this flag?

I started working on it and named the flag printErrorsAsPlainText.

@waldekmastykarz.
After you finished this implementation I would like to update the samples I created with this new capability. Do we have to create an issue for each sample or can we create a bulk issue updating my samples in one shot?

The implementation is complete and released in preview. If it's a similar change across the board, then for simplicity we could create a single issue to update all samples to avoid unnecessary issue management.


unknown-feature-proc-macro-span-shri

https://substrate.stackexchange.com/questions/5379/how-do-i-fix-a-failed-build-error-e0635-unknown-feature-proc-macro-span-shri

rustup default stable solved it


Recycled view holders retain old auto-sized size.

Check out Toolbar.SavedState compared to its neighbors above and below. Framework bug?

cc @chrisbanes

This can be easily reproduced by searching for "View" and then doing moderate flings down to the bottom and then back up. Usually the 4th or 5th item from the top will retain the smaller size from the recycled views.

Got a 100% repro case. On a Nexus 4 emulator, search "Toolbar", rotate left, scroll to bottom, rotate right, scroll to top.


once() method for CDP events

There are a few instances of this pattern appearing in our code, used to listen for a single occurrence of an event:
const eventHandler = (params) => {
  cdpClient.Page.removeEventListener('frameStoppedLoading', eventHandler);
  // ... Do stuff ...
};

cdpClient.Page.addEventListener('frameStoppedLoading', eventHandler);

We could add a .once() method to encapsulate this pattern instead:
const params = await cdpClient.Page.once('frameStoppedLoading');
// ... Do stuff ...

Implemented via Deferred


examples: ui element usage examples

Adds a collection of small self-contained examples for our various UI elements. In a follow-up, it might make sense to have our API docs point to these examples as a the source of truth (instead of inlining marimo-embed).
Adds a pointer to these examples and the API docs to marimo tutorial intro.

looks great.
@akshayka we could easily create a new mkdocs block: /// marimo-embed-file | examples/ui/array.py


[csolution] Add support for linker script preprocessing in cproject.yml and cbuildgen

Relates to https://github.com/Open-CMSIS-Pack/devtools/issues/655
Overview: https://github.com/Open-CMSIS-Pack/devtools/blob/main/tools/projmgr/docs/Manual/Linker-Script-Management.md
Linker node:
https://github.com/Open-CMSIS-Pack/devtools/blob/main/tools/projmgr/docs/Manual/YML-Input-Format.md#linker
Step one: manual specification of script running pre-include pre-processing with existing/user specified regions_<device>.h or regions_<board>.h

Included in CMSIS-Toolbox starting 1.7.0

@ReinhardKeil could you please add this new node to the documentation:
Under misc: a node Library: was added to the schema and processing.
example:
 build-types:
    - type: Debug
      compiler: GCC
      misc:
        - Library:
          - -lm
          - -lc
          - -lgcc
          - -lnosys

schema:
"Library": { "$ref": "#/definitions/ArrayOfStrings", "description": "List of Linker flags for libraries handling" },


puppet 7.29.0 and 8.5.0 sink my arithmetic battleship!

Describe the Bug
Using a negative value with the Integer type assertion on a class causes a rather surprising pops error.
Example code which triggers the error:
  Integer[-1] $slowlog_log_slower_than                           = 10000,

from
https://github.com/voxpupuli/puppet-redis/blob/e8ca35a403653a2dac60dd93afd33cca4f9c2d2e/manifests/init.pp#L432
causes
       error during compilation: The parameter '$slowlog_log_slower_than' must be a literal type, not a Puppet::Pops::Model::AccessExpression (file: /home/jhoblitt/github/lsst-control/spec/fixtures/modules/redis/manifests/init.pp, line: 432, column: 15) on node foreman.cp.lsst.org

Expected Behavior
I expect my battleship to float!
Steps to Reproduce
Steps to reproduce the behavior:

configure CI with a pessimistic version constraint which allows 7.29.0
have code which uses Integer[<a filthy no good negative integer>]
run ci

Environment

Version 7.29.0
gha ubuntu latest runner

I also hit the same problem triggered by some definitions in puppet-rabbitmq ( https://github.com/voxpupuli/puppet-rabbitmq/blob/2605e305cc730f77fbb41c76a763cb471f7d66ce/manifests/init.pp#L435-L436 ), in our CI jobs which now uses puppet-agent-7.29.0-1.el9.x86_64 and CentOS 9 Stream.

Just for the sake of completeness, as the title only refers to 7.29.0: This also fails on 8.5.0 (seen with rabbitmq and dhcp modules)

Sry for commenting in this allready closed issue but does someone else experience this behaviour with agent 7.23 and server 7.16?
As far as I understand only agents with version 7.29.0 should be impacted but i can observice the problematic behaviour on many hosts with an agent <7.29.0.

Just 2 cents, I had to remove cache folder on the master in order to make it work after downgrade to agent's 7.28

For everyone having the same issue. If your puppet agent on your puppetserver is 7.29 this seems to impact all other agents connection to this master. Downgrade the package, clear the cache and reboot server. After that it works again.
@seqizz thank you for mentioning the cache folder!

May I know any update (especially ETA of the fixed version) about this problem ?
I can't access the jira ticket (maybe I need to request access ? I used to have a different account but lost access to it when I leave my prev. company)

For everyone having the same issue. If your puppet agent on your puppetserver is 7.29 this seems to impact all other agents connection to this master. Downgrade the package, clear the cache and reboot server. After that it works again. @seqizz thank you for mentioning the cache folder!

As 8.5.1 agent is out now, I only needed to restart the puppetmaster (8.5.0) in order to have it fix the error.


chore(main): release 1.5.0

:robot: I have created a release beep boop
1.5.0 (2024-04-30)
Features

add spanish greeting (#39) (cf71ea3)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/andtsang/github-actions-adventure/releases/tag/v1.5.0 :sunflower:


Create React App Fails - CoreJS postinstall error

Describe the bug
Trying to run create-react-app via the following command:
 npx create-react-app test-nginx-deploy
The process starts but produces the following errors:
npx: installed 99 in 13.005s

Creating a new React app in C:\Users\jeff.barfield\Documents\B&R Fun\nginx Testing\test-nginx-deploy.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...

C:\Users\jeff.barfield\Documents\B&R Fun\nginx Testing\test-nginx-deploy\react-scripts -> C:\Users\jeff.barfield\Documents\B&R Fun\nginx Testing\test-nginx-deploy\node_modules\react-scripts\bin\react-scripts.js

><EMAIL_ADDRESS>postinstall C:\Users\jeff.barfield\Documents\B&R Fun\nginx Testing\test-nginx-deploy\node_modules\react-scripts\node_modules\babel-runtime\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"

><EMAIL_ADDRESS>postinstall C:\Users\jeff.barfield\Documents\B&R Fun\nginx Testing\test-nginx-deploy\node_modules\react-scripts\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"

><EMAIL_ADDRESS>postinstall C:\Users\jeff.barfield\Documents\B&R Fun\nginx Testing\test-nginx-deploy\node_modules\react-scripts\node_modules\core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"

+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>added 1591 packages from 750 contributors in 117.738s
Missing dependencies in package.json

Did you try recovering your dependencies?

Yes
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

current version of create-react-app: 3.4.1
running from C:\Users\jeff.barfield\AppData\Roaming\npm-cache_npx\14772\node_modules\create-react-app
System:
OS: Windows 10 10.0.18363
CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Binaries:
Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.18362.449.0
Internet Explorer: 11.0.18362.1
npmPackages:
react: Not Found
react-dom: Not Found
react-scripts: Not Found
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce

(Write your steps here:)

Expected behavior

I should get the default create react app application.
Actual behavior

I get a partial project with the following file structure:

and the following in node_modules:

Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Facing same issue here. Can you guys let me know how to fix this.

Have the same issue here. Please let me know how to fix

Have the same issue here. Please let me know how to fix

Have the same issue here. Please let me know how to fix

I could not fix it, so reinstalled nodejs ...this time 32 bit msi. and now its creating the creat-react-app correctly....but the postinstall error persists ( even on successful creation of create-react-app)
so it seems we should consider this as warning and look for issue somwhere else.


__overrides

See https://github.com/NixOS/nix/blob/master/src/libexpr/eval.cc#L820-L827
Fixes eval-okay-overrides

Ah @jwiegley I just finished it!

@jwiegley My solution is to simply prefer attributes from an __overrides over other attributes by changing the use of M.insert to an appropriate M.insertWith. Not sure which way would end up being cleaner so feel free to ignore my PR. :smile:

Interestingly I noticed this feature isn't used at all in nixpkgs. I want to send a PR to upstream nix deprecating it since it adds useless complexity IMO.

As pointed out by @kmicklas, the code I wrote for this doesn't handle inherit __overrides yet.


Eslint error: Fragment not found in 'vue-frag'

Hey,
I get this error when importing fragment in a component:

Workaround is to import like this:
import Frag from 'vue-frag'
(...)
  components: {
    Fragment: Frag.Fragment,
  }

Edit: strike the workaround, it got rid of the error, but the plugin stopped working. Just disabling eslint instead for now.

Maybe esModuleInterop is not enabled?
If not, can you provide a minimal reproduction?
I can't help you with the information you provided so far.

I'm not working on that project anymore, so I'm sorry, but I can't really answer your suggestion or provide a minimal repro. It is a Vue 2 TS project, so it's quite possible that the problem is esModuleInterop not being enabled. I just reported it here because I didn't see anything similar from other packages, so if it is some TS setting causing it, it might warrant a comment in the readme or something.

It's standard TypeScript practice to enable esModuleInterop when using import statements that compile to CommonJS.
Closing this out as un-actionable since you can't provide more information.


terminal.assertMatches not behaving as expected when testing input

Describe the bug
When testing if the initial formatting of a block containing input is correct with assertMatches, it throws an error but shows the same strings in the error message.
To Reproduce
Steps to reproduce the behavior:

This simple test method can be used to (hopefully) reproduce this issue:

@Test
    fun `test for input formatting`() {
        testSession { terminal ->
            section {
                input()
            }.runUntilSignal {
                terminal.assertMatches { text("\\e[7m ") }         //inside the text is the code for the cursors blinking
            }
        }
    }

Run the test, it should fail and display the same strings for the actual and the expected like this:

Expected behavior
As both strings displayed in the error are exactly the same (and tests that use stripFormatting confirm that except for formatting everything matches), such a test should run.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: MacOS
Version 1.1.2

Additional context
I know that such a test is 'faking' the input method with a text field and manually putting in ansi codes but there is no other method to test against. Maybe a function could be added to test input and handle all ansi codes

Update: using the invert function instead of manually putting in the ansi code for blinking (\e[7m) fixes this issue


Django2 path in documentation

Hi there. Stepping through the documentation.
Should this:
url(r'^s3upload/', include('s3upload.urls')),
Become this?
path('s3upload/', include('s3upload.urls')),

Hmm. Now getting this error profile-pic-form/ ^get_upload_params/ [name='s3upload']

Hmm. Now getting this error:
Django tried these URL patterns, in this order:

[name='homepage']
profile-pic-form/ ^get_upload_params/ [name='s3upload']

Hi @HashRocketSyntax,
We're on Django 2.0 and use the first version you posted.
I'm afraid we can only offer support in terms of bugs and not Django/installation support so I'm going to close this issue.
I hope you got/get it working!
Darian

@djm What he means is that the syntax url( is no longer supported in Django. You must use path(

@shacker Thanks, fixed in https://github.com/yunojuno/django-s3-upload/commit/e9d4dba7a653378e90f312034f0bd29acdfbbcb5


Waypoint not working on Mini 2

Describe the bug
Hi!
I need to test the waypoint mission using a DJI Mini 2 drone. When I go to settings>waypoint this message is shown in a toast:

Not support Waypoint2.0

What am I doing wrong? I know that DJI Mobile SDK 4.16.4 does not support waypoint navigation for Mini 2, but MissionManager should overcome this problem.
Thank you
Steps To Reproduce
No response
Screenshots
No response
Smartphone
- Device: [Samsung Galaxy S23]

Additional context
No response

Right. Check the code and enable MissionManager for your model.


Bulk Imports: Remote end closed connection without response

My Environment

ArangoDB Version:        3.6.6
Storage Engine:             RocksDB
Deployment Mode:        Cluster
Deployment Strategy:   ArangoDB Starter
Configuration:              3 machines
Infrastructure:               own
Operating System:        CentOS 7.3
Total RAM in your machine:        64Gb each
Disks in use:        HDD

Component, Query & Data
Affected feature:
python-arango import_bulk function
AQL query (if applicable):
AQL explain and/or profile (if applicable):
Dataset:
1 million
Size of your Dataset on disk:
30G
Replication Factor & Number of Shards (Cluster only):
3
Steps to reproduce

Problem:
2020-09-26 02:07:32,740 - test.py[line:42] - ERROR - When importing 60: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 677, in urlopen
chunked=chunked,
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 426, in _make_request
six.raise_from(e, None)
File "", line 3, in raise_from
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request
httplib_response = conn.getresponse()
File "/usr/local/lib/python3.7/http/client.py", line 1344, in getresponse
response.begin()
File "/usr/local/lib/python3.7/http/client.py", line 306, in begin
version, status, reason = self._read_status()
File "/usr/local/lib/python3.7/http/client.py", line 275, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
timeout=timeout
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 727, in urlopen
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 403, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/local/lib/python3.7/site-packages/urllib3/packages/six.py", line 734, in reraise
raise value.with_traceback(tb)
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 677, in urlopen
chunked=chunked,
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 426, in _make_request
six.raise_from(e, None)
File "", line 3, in raise_from
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request
httplib_response = conn.getresponse()
File "/usr/local/lib/python3.7/http/client.py", line 1344, in getresponse
response.begin()
File "/usr/local/lib/python3.7/http/client.py", line 306, in begin
version, status, reason = self._read_status()
File "/usr/local/lib/python3.7/http/client.py", line 275, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/work/test.py", line 40, in test
builder.import_updated()
File "/work/test.py", line 1199, in import_updated
result = this_collection.import_bulk(self.grab_batch(elements, batch_size), on_duplicate='ignore', halt_on_error=False, details=True)
File "/usr/local/lib/python3.7/site-packages/arango/collection.py", line 2257, in import_bulk
return self._execute(request, response_handler)
File "/usr/local/lib/python3.7/site-packages/arango/api.py", line 66, in _execute
return self._executor.execute(request, response_handler)
File "/usr/local/lib/python3.7/site-packages/arango/executor.py", line 81, in execute
resp = self._conn.send_request(request)
File "/usr/local/lib/python3.7/site-packages/arango/connection.py", line 161, in send_request
auth=self._auth
File "/usr/local/lib/python3.7/site-packages/arango/http.py", line 109, in send_request
auth=auth
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 530, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 643, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 498, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
Expected result:

Hi @mathsyouth,
Did the server crash during the bulk import?
If so, could you please provide the server log of that time interval?

@maxkernbach Thanks for your reply. The server didn't crash during the bulk import. However, the server's 98% memory was utilized when the error happened. There wasn't any information in the server log during the time interval.

We expected a segfault or OOM crash on the server-side, but if it's still up and running after your bulk import request, then it must be something else. How large is the payload that you try to send? Any very large documents? There's a limit around 750MB at which I would expect the server to reject the request. Did you try to import the data by other means, i.e. without python-arango? We wonder if it's driver related or something more generic.

@Simran-B The overall payload is nearly 800 MB. However, even though I tried to split the large documents into 4 or 5 batches of small documents and the first 3 or 4 batches could be sent successfully, the last one or two would make the error reproduced again. I just used python-arango, not other drivers.

I assume this is related: #12896


Doc: Pubsub scaler, document relation between stabilizationWindowSeconds and metrics sample rate

https://github.com/kedacore/keda-docs/blob/c01eb795c151838f559a486219e2e79bdab36daa/content/docs/2.14/scalers/gcp-pub-sub.md?plain=1#L35
I'm wondering if you can document a recommendation for the value of  stabilizationWindowSeconds given that the underlying pubsub metrics are sampled only every 60s and can take up to 120s to update.
Otherwise, this might unnecessarily scale to the max due to the rate at which the metric updates

@ls-urs-keller makes sense, are you willing to update docs with the details?