Rancher Agent stuck on "INFO: Deleting container rancher-agent"

I am facing a strange problem while trying to get a RHEL Atomic Host to be detected by the interface. After copy-pasting the agent installer docker command, the agent never finishes and the host is not detected; here is the log:
INFO: Running Agent Registration Process, CATTLE_URL=http://172.xx.x.xxx:8080/v1
INFO: Checking for Docker version >= 1.6.0
INFO: Found Server version: 1.6.2
INFO: docker version: Client version: 1.6.0
INFO: docker version: Client API version: 1.18
INFO: docker version: Go version (client): go1.4.2
INFO: docker version: Git commit (client): 4749651
INFO: docker version: OS/Arch (client): linux/amd64
INFO: docker version: Server version: 1.6.2
INFO: docker version: Server API version: 1.18
INFO: docker version: Go version (server): go1.4.2
INFO: docker version: Git commit (server): ba1f6c3/1.6.2
INFO: docker version: OS/Arch (server): linux/amd64
INFO: docker info: Containers: 11
INFO: docker info: Images: 29
INFO: docker info: Storage Driver: devicemapper
INFO: docker info: Pool Name: rah_tweb1-docker--pool
INFO: docker info: Pool Blocksize: 65.54 kB
INFO: docker info: Backing Filesystem: xfs
INFO: docker info: Data file:
INFO: docker info: Metadata file:
INFO: docker info: Data Space Used: 1.076 GB
INFO: docker info: Data Space Total: 37.15 GB
INFO: docker info: Data Space Available: 36.08 GB
INFO: docker info: Metadata Space Used: 2.9 MB
INFO: docker info: Metadata Space Total: 46.14 MB
INFO: docker info: Metadata Space Available: 43.24 MB
INFO: docker info: Udev Sync Supported: true
INFO: docker info: Library Version: 1.02.93-RHEL7 (2015-01-28)
INFO: docker info: Execution Driver: native-0.2
INFO: docker info: Kernel Version: 3.10.0-229.7.2.el7.x86_64
INFO: docker info: Operating System: Red Hat Enterprise Linux
INFO: docker info: CPUs: 4
INFO: docker info: Total Memory: 1.791 GiB
INFO: docker info: Name: tweb1.example.com
INFO: docker info: ID: VOUD:2MGF:PDN5:N3O4:PCGH:XGFP:DKAB:GZH6:Y3JS:YKBM:5YSK:DLDL
INFO: Attempting to connect to: http://172.xx.xx.xxx:8080/v1
INFO: http://172.xx.xx.xxx:8080/v1 is accessible
INFO: Inspecting host capabilities
INFO: System: true
INFO: Host writable: true
INFO: Token: xxxxxxxx
INFO: Running registration
INFO: Printing Environment
INFO: ENV: CATTLE_ACCESS_KEY=73B871E16E7D0EA68252
INFO: ENV: CATTLE_AGENT_IP=172.xx.x.xx
INFO: ENV: CATTLE_HOME=/var/lib/cattle
INFO: ENV: CATTLE_REGISTRATION_ACCESS_KEY=registrationToken
INFO: ENV: CATTLE_REGISTRATION_SECRET_KEY=xxxxxxx
INFO: ENV: CATTLE_SECRET_KEY=xxxxxxx
INFO: ENV: CATTLE_SYSTEMD=true
INFO: ENV: CATTLE_URL=http://172.xx.x.xxx:8080/v1
INFO: ENV: DETECTED_CATTLE_AGENT_IP=172.xx.x.xx
INFO: ENV: RANCHER_AGENT_IMAGE=rancher/agent:v0.7.9
INFO: Deleting container rancher-agent
INFO: Deleting container rancher-agent

After this point, the last line keeps repeating; as if in an infinite loop.

Well obviously I get this:
Error response from daemon: no such id: rancher-agent

As there is no such rancher-agent container running.

@burhan I know it's been awhile, but have you been able to get a RHEL Atomic Host to be added into Rancher. Are you still facing the same issues? If not, I'll be closing this.

I am encountering same issue with Debian Jessie on OVH VPS.

I'm presently encountering the same issue with my container. Any solution?

@manthis Can you provide more details on your OS type and Rancher setup?

Similar problem here but no infinite loop
I started the agent the following way:
sudo docker run --name=rancher-agent --add-host=X.X.ca:<IP_ADDRESS>  -d --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent:v1.0.1 http://X.X:8080/v1/scripts/8DA3971F45AE0BB324DD:1464354000000:UCw3cFPQmcYFvhDHSyzQ
Here is the log:
INFO: Running Agent Registration Process, CATTLE_URL=http://X.X.ca:8080/v1
INFO: Checking for Docker version >= 1.6.0
INFO: Found Server version: 1.11.1
INFO: docker version: Client version: 1.6.0
INFO: docker version: Client API version: 1.18
INFO: docker version: Go version (client): go1.4.2
INFO: docker version: Git commit (client): 4749651
INFO: docker version: OS/Arch (client): linux/amd64
INFO: docker version: Server version: 1.11.1
INFO: docker version: Server API version: 1.23
INFO: docker version: Go version (server): go1.5.4
INFO: docker version: Git commit (server): 5604cbe
INFO: docker version: OS/Arch (server): linux/amd64
INFO: docker info: Containers: 19
INFO: docker info: Images: 181
INFO: docker info: Storage Driver: devicemapper
INFO: docker info: Pool Name: docker-8:2-5636491-pool
INFO: docker info: Pool Blocksize: 65.54 kB
INFO: docker info: Base Device Size: 107.4 GB
INFO: docker info: Backing Filesystem: xfs
INFO: docker info: Data file: /dev/loop0
INFO: docker info: Metadata file: /dev/loop1
INFO: docker info: Data Space Used: 10.94 GB
INFO: docker info: Data Space Total: 107.4 GB
INFO: docker info: Data Space Available: 96.44 GB
INFO: docker info: Metadata Space Used: 16.26 MB
INFO: docker info: Metadata Space Total: 2.147 GB
INFO: docker info: Metadata Space Available: 2.131 GB
INFO: docker info: Udev Sync Supported: true
INFO: docker info: Deferred Removal Enabled: false
INFO: docker info: Deferred Deletion Enabled: false
INFO: docker info: Deferred Deleted Device Count: 0
INFO: docker info: Data loop file: /var/lib/docker/devicemapper/devicemapper/data
INFO: docker info: Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
INFO: docker info: Library Version: 1.02.107-RHEL7 (2015-12-01)
INFO: docker info: Execution Driver:
INFO: docker info: Kernel Version: 3.10.0-229.20.1.el7.x86_64
INFO: docker info: Operating System: CentOS Linux 7 (Core)
INFO: docker info: CPUs: 4
INFO: docker info: Total Memory: 11.57 GiB
INFO: docker info: Name: capamhc
INFO: docker info: ID: TILT:YU5G:COCP:WKQJ:UR2V:EIGG:YTBH:FHYJ:MIQW:NIST:QSEH:G3OI
INFO: docker info: Http Proxy:
INFO: docker info: Https Proxy:
INFO: docker info: No Proxy:
INFO: Attempting to connect to: http://X.X.ca:8080/v1
INFO: http://capamhc.iric.ca:8080/v1 is accessible
INFO: Inspecting host capabilities
INFO: System: true
INFO: Host writable: true
INFO: Token: xxxxxxxx
INFO: Running registration
INFO: Printing Environment
INFO: ENV: CATTLE_ACCESS_KEY=03A64976D87FBFDD8D12
INFO: ENV: CATTLE_AGENT_IP=<IP_ADDRESS>
INFO: ENV: CATTLE_HOME=/var/lib/cattle
INFO: ENV: CATTLE_REGISTRATION_ACCESS_KEY=registrationToken
INFO: ENV: CATTLE_REGISTRATION_SECRET_KEY=xxxxxxx
INFO: ENV: CATTLE_SECRET_KEY=xxxxxxx
INFO: ENV: CATTLE_SYSTEMD=true
INFO: ENV: CATTLE_URL=http://X.X.ca:8080/v1
INFO: ENV: DETECTED_CATTLE_AGENT_IP=<IP_ADDRESS>
INFO: ENV: RANCHER_AGENT_IMAGE=rancher/agent:v1.0.1
INFO: Deleting container rancher-agent

Can you explain why you added this part into the command? --add-host=X.X.ca:<IP_ADDRESS>

This rancher-agent is on the same node as the server. The computer is in a private network in 10.0.0.X. It can be reached with a public host name and ip    X.X.ca:132.X.X.X
I added this --add-host=X.X.ca:<IP_ADDRESS> because the firewall/routing at my institution is doesn`t allow me to loop back using my public IP.
With this host entry the rancher-agent can reach the rancher-server.
Other rancher-agents on the public network can connect without an issue to the rancher-server.
Mathieu Courcelles, Ph.D. Bio-informatique
Associé de recherche, Centre d’analyse protéomique avancée
IRIC - Institut de recherche en immunologie et cancérologie
Université de Montréal
From: Denise
Sent: Wednesday, June 01, 2016 6:45 PM
To: rancher/rancher
Cc: courcelm ; Manual
Subject: Re: [rancher/rancher] Rancher Agent stuck on "INFO: Deleting container rancher-agent" (#1737)
Can you explain why you added this part into the command? --add-host=X.X.ca:<IP_ADDRESS>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I got the same issue and managed to solve it. Do not add --name rancher-agent, this command creates a container named rancher-agent and exits. When you set the name it removes itself :)

@courcelm I didn't catch the --name rancher-agent in your command.
http://docs.rancher.com/rancher/latest/en/faqs/agents/#what-are-reasons-why-rancher-agent-would-fail-to-start

Yup removing --name rancher-agent  avoid INFO: Deleting container rancher-agent.
However my --add-host  seems not to be propagated to all the containers rancher-agent start which create other issues.
I decided to use another host to avoid these issues.
Thanks for your help!


[Feature Request]: Handle exceptions in SimpleDirectoryReader and continue loading other files

Feature Description
Currently, if there is a file in the directory that cannot be read, the entire loading process fails. It would be convenient to have an option to handle these exceptions gracefully and continue reading in other files.
This feature could be implemented as an additional parameter in the SimpleDirectoryReader, such as ignore_errors=True. When this parameter is set, the reader should log an error message for the problematic file and proceed with reading the remaining files in the directory.
I found the two parameter "errors" and "raise_on_error" but they don't seem to have the effect I described above. Maybe I am configuring them wrong?
Reason
Currently, LamaIndex does not support skipping over unreadable files when reading from a directory, causing the entire document loading process to fail if any single file is problematic. To write robust applications relying document ingestion, one has to manually iterate over the files, handling the errors one-by-one, which adds some boilerplate code.
Value of Feature
This feature would make apps more resilient to errors in the default document reading process. Users could still implement custom error handling.

Sorry about that, found the bug in my code...


Fix failing tests with WebGL Validation

Fixes #2373.

Everything looks good otherwise.

@pjcozzi @mramato This is ready for another review.

Looks good.


How to report health check results to influxdb?

App.Metrics.AspNetCore.Health 2.0.0

App.Metrics.AspNetCore.Health 2.0.0

Duplicate https://github.com/AppMetrics/Health/issues/9


Discord support

ready to use

What does it do? Can you document it in the appropriate file in the docs directory?

While - for testing - not merge :-)

https://discordapp.com/ ?

@sohje - I know roughly what discord is, but what does it do here? Notification only? Controlling the bot?...

@DBa2016 notify and controlling

You will end up duplicating a lot of code here to give discord the same functionality as telegram.
This is why I have suggested that the code to generate events and respond to commands be separated from the actual communication method.
So we could have discordbot and telegrambot that just handle the communication aspect of things, while another class passes information to/from these bots.

Love the concept though. We should not have to be forced to use Telegram just to get this functionality.
Would like to see handlers for Telegram, Discord, Email, Other common messaging apps, all sharing the same basic alert generation/command response base code.

I have significant concerns about this, in that discord support duplicates a lot of the code in telegram_handler.py. Which means any time we want to change it, we have to change both.
OK to go ahead with this approach for now, but ultimately we should make discord and telegram handlers just look after communicating with discord/telegram, and leave the processing of commands and generation of events to a separate class.

Same as @Gobberwart , is there better way to organize code?

I think there are two options:

move the logic into a base class, from which telegram, discord, and whateverelse handlers can be derived. The handlers should then only include code specific to facilitate the communication between the handler and the messenger.
move the logic into "control handler" or similar class which processes events generated/emitted by the particular comunication class.

There might be other options which reduce code duplication, I just don't se them right now :)
Both approaches would even allow web interfaces to run over the same logic... As for email - I don't think this would be particularly useful, but it does not hurt either.
If we don't do this, every bug fix or enhancement we do in a control interface will need to be duplicated (including the logic!) to all other control interfaces.
If no objections are xpressed, I can start implementing option 2 - however, a code freeze for Telegram (and discord) code will be needed for this.

approve PR and try make joining to your concept :-)

@DBa2016 Agreed, let's move on.

👍

./setup.sh -r
Traceback (most recent call last):
File "pokecli.py", line 47, in
from pokemongo_bot import PokemonGoBot, TreeConfigBuilder
File "/home/dev/Poke/PokemonGo-Bot/pokemongo_bot/init.py", line 22, in
import cell_workers
File "/home/dev/Poke/PokemonGo-Bot/pokemongo_bot/cell_workers/init.py", line 26, in
from telegram_task import TelegramTask
File "/home/dev/Poke/PokemonGo-Bot/pokemongo_bot/cell_workers/telegram_task.py", line 10, in
from pokemongo_bot.event_handlers import TelegramHandler
File "/home/dev/Poke/PokemonGo-Bot/pokemongo_bot/event_handlers/init.py", line 5, in
from discord_handler import DiscordHandler
File "/home/dev/Poke/PokemonGo-Bot/pokemongo_bot/event_handlers/discord_handler.py", line 7, in
import discord_simple
ImportError: No module named discord_simple


Use Java 14 (latest GA). Upgrade Gradle. Use ParallelGC by default

Java 14 has significant improvements compared to Java 8, and quite a few improvements compared to Java 11.
Java 11 and Java 14 are equally production-ready. The "LTS" label is given by vendors to their specific distributions (binaries) where they provide long term support.

I didn't touch Scala because currently the Scala bench is not using plain OpenJDK image. It is using some other 3rd-party custom image that I am not familiar with.
I'd defer to a Scala expert instead.


problem in pip3 install tronapi

hi
when i run pip3 install tronapi  i have this error
Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-sazbbhmf/cytoolz/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-4at3hdbj-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-sazbbhmf/cytoolz/
what is problem ?

building 'cytoolz.dicttoolz' extension
creating build/temp.linux-x86_64-3.6
creating build/temp.linux-x86_64-3.6/cytoolz
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python3.6m -c cytoolz/dicttoolz.c -o build/temp.linux-x86_64-3.6/cytoolz/dicttoolz.o
cytoolz/dicttoolz.c:17:20: fatal error: Python.h: No such file or directory
#include "Python.h"
^
compilation terminated.
error: command 'gcc' failed with exit status 1
----------------------------------------

Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-586ukv17/cytoolz/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-ouf9ljji-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-586ukv17/cytoolz/

building 'cytoolz.dicttoolz' extension
creating build/temp.linux-x86_64-3.6
creating build/temp.linux-x86_64-3.6/cytoolz
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python3.6m -c cytoolz/dicttoolz.c -o build/temp.linux-x86_64-3.6/cytoolz/dicttoolz.o
cytoolz/dicttoolz.c:17:20: fatal error: Python.h: No such file or directory
#include "Python.h"
^
compilation terminated.
error: command 'gcc' failed with exit status 1
----------------------------------------

Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-586ukv17/cytoolz/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-ouf9ljji-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-586ukv17/cytoolz/

i have this error too
do you find a solution ?

i have this error too
do you find a solution ?

Do you have the Python header files installed?
Try running the command (for CentOS):
yum install python-devel

Or for Debian/Ubuntu:
apt-get install python-dev

Do you have the Python header files installed?
Try running the command (for CentOS):
yum install python-devel

Or for Debian/Ubuntu:
apt-get install python-dev

@ansmirnov
CentOS Linux 8 - AppStream                      0.0  B/s |   0  B     00:00
Errors during downloading metadata for repository 'appstream':

Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=stock [Could not resolve host: mirrorlist.centos.org]
Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=stock [Could not resolve host: mirrorlist.centos.org]

@ansmirnov
CentOS Linux 8 - AppStream                      0.0  B/s |   0  B     00:00
Errors during downloading metadata for repository 'appstream':

Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=stock [Could not resolve host: mirrorlist.centos.org]
Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=stock [Could not resolve host: mirrorlist.centos.org]

@mahdilou99
It looks like a network problem. DNS is not configured correctly.

@mahdilou99
It looks like a network problem. DNS is not configured correctly.

Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
epel/x86_64/metalink                                     |  16 kB     00:00

EA4: <IP_ADDRESS>
cpanel-addons-production-feed: <IP_ADDRESS>
cpanel-plugins: <IP_ADDRESS>
base: centosmirror.netcup.net
epel: ftp.plusline.net
extras: mirror.checkdomain.de
updates: mirror.checkdomain.de
EA4                                                      | 2.9 kB     00:00
cpanel-addons-production-feed                            | 2.9 kB     00:00
cpanel-plugins                                           | 2.9 kB     00:00
base                                                     | 3.6 kB     00:00
epel                                                     | 4.7 kB     00:00
extras                                                   | 2.9 kB     00:00
mysql-connectors-community                               | 2.6 kB     00:00
mysql-tools-community                                    | 2.6 kB     00:00
mysql57-community                                        | 2.6 kB     00:00
updates                                                  | 2.9 kB     00:00
(1/2): epel/x86_64/updateinfo                              | 1.0 MB   00:00
(2/2): epel/x86_64/primary_db                              | 6.9 MB   00:00
Package python-devel-2.7.5-90.el7.x86_64 already installed and latest version
Nothing to do
@ansmirnov

Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
epel/x86_64/metalink                                     |  16 kB     00:00

EA4: <IP_ADDRESS>
cpanel-addons-production-feed: <IP_ADDRESS>
cpanel-plugins: <IP_ADDRESS>
base: centosmirror.netcup.net
epel: ftp.plusline.net
extras: mirror.checkdomain.de
updates: mirror.checkdomain.de
EA4                                                      | 2.9 kB     00:00
cpanel-addons-production-feed                            | 2.9 kB     00:00
cpanel-plugins                                           | 2.9 kB     00:00
base                                                     | 3.6 kB     00:00
epel                                                     | 4.7 kB     00:00
extras                                                   | 2.9 kB     00:00
mysql-connectors-community                               | 2.6 kB     00:00
mysql-tools-community                                    | 2.6 kB     00:00
mysql57-community                                        | 2.6 kB     00:00
updates                                                  | 2.9 kB     00:00
(1/2): epel/x86_64/updateinfo                              | 1.0 MB   00:00
(2/2): epel/x86_64/primary_db                              | 6.9 MB   00:00
Package python-devel-2.7.5-90.el7.x86_64 already installed and latest version
Nothing to do
@ansmirnov

You have installed python-devel version 2.7 but you are using pip version 3.6.
Try running the following command and install the correct version of python-devel.
yum search python-devel

You have installed python-devel version 2.7 but you are using pip version 3.6.
Try running the following command and install the correct version of python-devel.
yum search python-devel

@ansmirnov thanks
yum install python3-devel
worked and install good

@ansmirnov thanks
yum install python3-devel
worked and install good

Not enough time, work with the library, we will soon restore work

If sudo apt-get install python3-dev does not solved this problem you can try sudo apt-get install build-essential it helped me.


Xcode6 and iOS8 crash due UIViewControllerHierarchyInconsistency

Using SAMTextView component via storyboard, Xcode5 was ok. When compiled with Xcode6 and run under iOS8, app crashes:
*** Terminating app due to uncaught exception 'UIViewControllerHierarchyInconsistency', reason: 'child view controller:UICompatibilityInputViewController: 0x18b58560 should have parent view controller:MyViewController: 0x178d5620 but requested parent is:UIInputWindowController: 0x169fc600'
Haven't found a fix yet, stack overflow seemed to suggest removing component from superview and/or not using storyboard at all. Still researching, but hoping "you" (anyone) could suggest a fix right away.

Found the problem: storyboard contained a toolbar that was set to textView.inputAccessoryView in code. Worked ok with Xcode5, but crashes with Xcode6. Problem has nothing to do with SAMTextView, therefore this case can be closed. Sorry for the trouble!

Well, one more time with the fix: I still create toolbar in storyBoard (I'm visual person, things are easier when I see them), but I "reset" the parentViewController with a call to removeFromSuperview. Seems to work.
@property (weak, nonatomic) IBOutlet UIToolbar *keyboardToolbar;
[self.keyboardToolbar removeFromSuperview];
self.feedbackText.inputAccessoryView = self.keyboardToolbar;


feat: Add build step on migration files to reduce file size from ts-node

Overview
This pull request adds a build process into the migration files, which will remove dependencies to ts-node when running up and down command.
Caveats
Any migration files created with migration:create command should always be renamed to .ts manually, since the migration script doesn't have native TypeScript support.

I'll some quick check on this to better understand the caveats we just made.
Thank you for the hard work!

:rocket: PR was released in v0.2.0 :rocket:

This causes hiccups:
❯ docker-compose run app yarn run migration:up
Starting dwatori_mongo_1 ... done
yarn run v1.22.5
$ migrate-mongo up && npm run migration:status
(node:30) Warning: Accessing non-existent property 'MongoError' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
ERROR: Could not migrate up<PHONE_NUMBER>1813-seed.js: Unexpected token 'export' /usr/src/app/migrations/20201204021813-seed.js:53
export {};
^^^^^^

SyntaxError: Unexpected token 'export'
    at wrapSafe (internal/modules/cjs/loader.js:979:16)
    at Module._compile (internal/modules/cjs/loader.js:1027:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.loadMigration (/usr/src/app/node_modules/migrate-mongo/lib/env/migrationsDir.js:97:12)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async migrateItem (/usr/src/app/node_modules/migrate-mongo/lib/actions/up.js:18:25)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I've changed the build target to es2019 and still have no lucks.
Please advice @namchee.


use direct port manipulation when switching receivers - toggle the two outputs at once

Hey @sheaivey,
I've noticed that switching the two receivers is made using 2 arduino digitalWrite. These are convenient functions but not very efficient - as we want both outputs to switch instantly a direct port manipulation would be better but the problem is that some conditions have to be met for it to be efficient:

both outputs should be on the same port
a subroutine has to be written by the user
Thats why i've hidden this behind a define - people using A0 and A1 can just uncomment it and they get instant switching.

Here is an example benchmark: https://www.baldengineer.com/digitalwrite-on-a-logic-analyzer.html
What do you think?

I tried fast switching out and it was a big improvement, nice work!!
I made a before and after video and even in dvr it's an improvement, you can't see the switching in dvrt.
Before: https://youtu.be/Yjy420Z2moU
After: https://youtu.be/V8zjIiTATdw

@jelle737 thanks for making a video. looks great.

ok i made it universal as long as both outputs are on the same port (it doesnt make sense to use if it isnt on the same port anyway). thanks @jelle737 for feedback.
now the setReceiver takes a little longer as the bit operations arent defined but it doesnt matter as long as both the outputs are switched at the same time.

Wow great job!

Please review the and fix any conflicts then I will merge in your changes.

rebased the changes @sheaivey

I've implemented this in #106.

It might be a good idea to veryfy, if the two signals are not activated  both at once on osciloscope.. The two output drivers might short out for a short period of time during the switch, since it take some time for the switch to close.
It might be completely unrelated, but my goggles started to have wierd random image dropouts, seems like the receivers are somehow damaged.

Closing as it is now implemented in release v2.0


Add continuous releases

This will create and continuously update a GitHub release called
"latest" that holds the artifacts produced in the latest run CI test
job on the main branch. The text body of the release will be updated to
reflect the changes in CHANGELOG.md.
Closes #36

While this isn't perfect, nor have I even tested with using tagged releases, like we will do for real versions, but it does solve the super immediate need and so I'll merge. It might be that I'll have to rework quite a bit to make it work for the normal releases too... let's see, but for now, we get "latestlies", like nightlies but for every build :)


Initial FFI Draft

What was changed
Initial impl of bridge FFI. This is still in development so lacks a lot of docs.
Why?
Go and others need a C API to communicate with core.
Notes

See #248
This adds a bridge set of protos which is essentially just the Core trait wrapped in proto form. It also provides a gRPC stream service proto.
This adds a bridge-ffi crate which exposes core over C API
This may add a bridge-grpc crate which exposes core over a gRPC stream
We have discussed and decided that protobuf is the encoding language of choice. The serialization/deserialization on both sides of the boundary comes with a known performance cost.

This performance cost already exists in core as protobuf is already being used as the encoding between core and lang
If we want to improve this, I suggest either https://google.github.io/flatbuffers/ or https://capnproto.org/, both of which operate on byte arrays without explicit serialization and have decent cross-language support

Since core calls are async, we have chosen C function pointer callbacks to report results. There are upsides and downsides to this approach:

Anything can be built on callbacks, including event loops or whatever
Callbacks do require the lang to respect speed inside the callback. The Rust thread is held up while a callback is executed, so lang must do what it needs to do inside the callback to get the data on its other thread for working (resolve a JS promise, put on a Go channel, etc).
As most C APIs do, we allow user data in the callback. This helps callers access data inside the callback and is a very common approach.
We could have done an event loop, but you essentially are using function pointers anyways, the only difference is you've now made the response handling single threaded which doesn't benefit languages that can use more than one thread.

This includes a Go example and may include examples of other languages. The examples may not ever be in the final product, we just need to prove things work

The gRPC service definition looks like it isn't used yet - and my understanding is it won't be until (if) we actually expose a gRPC endpoint, correct?

@Sushisource - Correct. I included the service definition because the encapsulation of request/response as proto is partially driven by that use case, and I wanted to explain my thoughts on using a stream there instead of unary RPC calls. I also want SDK langs to consider, when being designed, that they may be asked to communicate w/ core over in addition to C.
But it is not used today though I expect a bridge-grpc crate to come about soon. There will have to be some more thoughts around server connection reuse across streams so each stream doesn't represent a separate gRPC instance, but that may be affected by your new potential work separating the client from the core instance.
Or maybe a bridge-web crate which includes gRPC capabilities but also a web socket + proto json equivalent (using gRPC from a browser is annoying).

The Go code might make sense to have in another repo, but I can kinda go either way on that one.

The Go code might make sense to have in another repo, but I can kinda go either way on that one.

@Sushisource - I'd rather just delete it instead of letting it grow stale in a separate repo. I would also be willing to show how to use this with, say, .Net here (it'd only take a couple hours probably). But once someone actually uses this crate, it definitely makes sense to have that serve as the canonical example/usage instead of this. This was more for vetting.

@cretz Ya, sounds good to me. Let's just delete it before merging then. It might be nice to keep for reference, maybe just publish it to another branch that we can leave around for a bit?

I am closing this draft PR in favor of a real PR.


Upgrade intl-messageformat-parser depdendency to 1.1.x

Otherwise, here's the error:
npm install<EMAIL_ADDRESS>npm WARN unmet dependency [...]/node_modules/intl-messageformat requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency [...]/node_modules/intl-messageformat-parser,
npm WARN unmet dependency which is version 1.1.0
<EMAIL_ADDRESS>node_modules/intl-messageformat-parser

This will be upgraded soon. For the time being you'll need to allow this package to have its own copy of the parser.

This is in PR #102

Closing since PR #102 has been merged.


Adding the 2.3 version dashboards

Merged to master. @roydahan we can backport to 1.0 after you approve it is tested.


Give hash, get metadata, download missing, seed

Is it possible to
Give infohash -> download metadata from the network -> check the integrity of the local files based on the metadata -> download the missing/corrupted pieces -> seed the data on the network
???

Yes, it would be very nice if the download does not start over again.

This isn't possible yet. PR welcome!
Closing as duplicate of https://github.com/feross/webtorrent/issues/276


Support serializing to Vec with unknown seq/map length

When the sequence is done it should go back and write the length in the correct spot.
Though variably encoding the length may make this less feasible - cc #75.

Is that a problem in practice? I think the majority of binary serialization formats have problems supporting unknown lengths.

I'm not sure how useful this.  How many people encode using different types than they decode?

If I'm understanding this suggestion correctly, it would resolve #245. I thought this could be implemented by tracking the index into our underlying vec when creating a Compound, then going back and updating the appropriate size at that starting index in the vec during the SerializeMap::end method.
The trouble is all of the serialization methods in bincode are generic over the std::Write trait, which doesn't allow the type of access we need into the underlying vec. I'm not sure if there is a better way to handle this? Or if perhaps there are additional trait bounds that would help here without limiting the API too much?

Any Idea when this will get  any kind of fix? :(

@MTRNord so far there has not been a proposed solution that does not come with significant drawbacks. Implementing this is held up until we can identify an implementation that doesn't come with those drawbacks.

This issue should be reopened. It's still a big problem, particularly when working with structs involving serde's flatten feature.

We have decided to declare this issue out of scope.
Bincode only officially supports types that serialize to a known length, and the initial proposed solution of going back and rewriting the correct length after serializing the sequence both causes issues with varint encoded lengths, and can not be made general as it can not be assumed that any given writer supports Seek, and specializing for Vec<u8> would incur unacceptable performance penalties for common usecases.


[FB Messenger] Why is the bot not receiving the "messaging_handovers" event from Messenger API?

Bot Info

SDK Platform: .NET
SDK Version: 3.11
Active Channels: Facebook
Deployment Environment: ngrok

Issue Description
I am trying to implement Facebook handover protocol to forward the messages to the page by passing the thread control to the page inbox using app id as in docs<PHONE_NUMBER>30900), the control is passed successfully, however, the bot do not receive any messaging_handovers event even if the app is already subscribed to it.
As we need to know when the event is received to log it, as well as receive the event when the admin mark the conversation as done and pass the control back to the bot.
Code Example
Follow Facebook guide to enable forward to agent https://developers.facebook.com/docs/messenger-platform/handover-protocol/pass-thread-control#page_inbox
Reproduction Steps

Send call to Facebook to send control to page
Wait for event on MessagesController

Expected Behavior
Receieve an activity with channel data related to webhook

Could you please post your code so we can try to reproduce?

I was able to talk to Facebook about it, and to solve the issue, they told me to listen for the standby event and ignore the messages.
What is happening is after passing the control to the page inbox, the bots becomes the secondary controller and it will receive messages of type standby, and by having a proxy before the botframework connector we can ignore these.

Glad you were able to find a solution, good luck!

@etbuilder any chance you can share some sample code for how you implemented this?  I have exactly the same requirement.

We enabled standy-by Webhook events on our Facebook app, then in our proxy we just check if the message type is standby we ignore it.
The facebook app webhook is connected to our proxy, in the proxy we check raw messages coming from facebook, and based on type we simply forward them to the botconnecter url .
Code in the proxy
if (IsStandByEvent(webhookRequestJson)) {                 return req.CreateResponse(HttpStatusCode.OK);             }
`private static bool IsStandByEvent(dynamic request) {
try {
if (request?.entry?[0]?.standby?[0] != null) {
return true;
}
} catch {
}
        return false;
    }`

@etbuilder Thanks for that. Exactly what I needed :)

You are welcome, you can ping me any time :)

Hey.  Have you got an example of the proxy you built between FB and the Bot Connector? Cannot get mine working.
Thanks
Gary

Sure thing
ours is Http trigger azure function
if (req.GetQueryString("hub.mode") == "subscribe" && req.GetQueryString("hub.verify_token") == token) {
                log.Info($"Recieved Validation Request From Facebook with Challenge {Convert.ToInt32(req.GetQueryString("hub.challenge"))}");
                return req.CreateResponse(HttpStatusCode.OK, Convert.ToInt32(req.GetQueryString("hub.challenge")));
            }

jsonContent = await req.Content.ReadAsStringAsync();
webhookRequestJson = JsonConvert.DeserializeObject(jsonContent);

Then we clone the request removing x-liveupgrade and return the response
// forward request to appropriate webhook
forwardRequest = req.Clone(targetWebhook, log);
response = await RouteRequest(forwardRequest, log);

(!response.IsSuccessStatusCode) {
                        log.Error("response was not successful" + response.StatusCode);
 }

return response;

public static HttpRequestMessage Clone(this HttpRequestMessage req, string newUri, TraceWriter log) {
            HttpRequestMessage clone = new HttpRequestMessage(req.Method, newUri);

            if (req.Method != HttpMethod.Get) {
                clone.Content = req.Content;
            }
            clone.Version = req.Version;

            foreach (KeyValuePair<string, object> prop in req.Properties) {
                clone.Properties.Add(prop);
            }

            foreach (KeyValuePair<string, IEnumerable<string>> header in req.Headers) {
                if (header.Key == "X-LiveUpgrade") {
                    continue;
                }

                clone.Headers.TryAddWithoutValidation(header.Key, header.Value);
            }

            //foreach (KeyValuePair<string, IEnumerable<string>> header in clone.Headers)
            //{
            //    log.Info($"header.Key {header.Key}, header.Value {string.Join(",", header.Value.ToArray())}");
            //}

            clone.Headers.Host = new Uri(newUri).Authority;

            return clone;
        }

@etbuilder great, thanks! and it is in here that you are checking if the message is a standby message and ignoring if necessary?

@etbuilder Thanks again for the above.  I am struggling to get it compiling. Looks like a few methods are missing, like RouteRequest and it doesn't seem to like GetQueryString either. Would you be able to share a more complete sample?  Sorry to be a pain, just looking forward to getting this working :)

public static string GetQueryString(this HttpRequestMessage request, string key) {
            var queryStrings = request.GetQueryNameValuePairs();
            if (queryStrings == null)
                return null;

            var match = queryStrings.FirstOrDefault(kv => string.Compare(kv.Key, key, true) == 0);
            if (string.IsNullOrEmpty(match.Value))
                return null;

            return match.Value;
        }

public static async Task<HttpResponseMessage> RouteRequest(HttpRequestMessage forwardRequest, TraceWriter log) {
            HttpClient client = new HttpClient();
            HttpResponseMessage response = await client.SendAsync(forwardRequest);

            // log any failure messages in a table for checking later on
            //
            //
            if (!response.IsSuccessStatusCode) {
                //await InsertDeadRequest(response.ToString(), "backend webhook error", log);
                log.Info($"Failed {response.ToString()}");
            }

            return response;
        }

Answering the previous question, the answer is yes.

@etbuilder Thanks for your help. I just got this working perfectly. Really appreciate the directions on this :) I'll blog about it soon and give you a shout out when I do. You got a twitter handle / blog I can use to reference you?

@etbuilder Hey. I just ran a quick test and it looks like the standby messages are not sent to the bot directly, even when the proxy is not in place, as long as you have not subscribed to that webhook in Facebook.  With this being the case, how come you needed the proxy in the first place?

Hello @etbuilder I'm working to a chatbot that needs the operator handover. I'm using as primary my chatbot app and as secondary the InBox of facebook. Anyway I see many strange behaves... It seems that if I operate from the facebook business manager to change the handover status from ARCHIVE (that as far as I understood means chatbot) and InBox (that is the operator) or viceversa, this status is automatically changed by facebook without any apparent reason and without sending any web_hook message. Moreover, the pass_thread message seems to have always the same data, app_id of the main one, both if you pass from main to secondary that from secondary to main. This seems to be a bug.
Basically, handover seems totally unstable.
Did you experienced the same?
Thanks

Hey,
Once you pass thread control from main to page, are you using the page inbox app id "263902037430900", if the pass is successful you should receive success (I don't think in this case you will receive a web-hook event).
Once you press "Done" on a message from the inbox, you should receive the event, but, the issue is that bot-connector drops it. If you need this event, you need to intercept all calls from the web-hook between Facebook and bot-connector and check if its handover event, forward it directly to your API endpoint.
Further, if you pass thread control to inbox, you will still receive any postback events from bot-connector like button clicks, to resolve this issue, you have to subscribe to standby events, and when you intercept the webhook messages, you can have your logic in which we simply drop them and not forwarding them to the bot-connector.

Hi  @etbuilder, thanks for your reply. In my case, the issue is on facebook it self: even if I disconnect all the webhook and api management for handover, I see that facebook switches from ARCHIVE to INBOX the conversation, automatically. That seems a facebook bug. My question is if someone experienced this behave.
Thanks

Have you set your configuration for the page, app as primary and page inbox as secondary?

Sure. I see the events and previously it was working. suddenly, it started to switch back to INBOX even if I selected ARCHIVE. Once I select ARCHIVE it correctly moves back to ARCHIVED folder, but after the first message is sent to the BOT it goes back to INBOX. This happens also without BotBuilder.

I found that Facebook Messenger support pass thread control from human manager to bot when the conversation was set 'done' by the human. However I don't know the case if a page has several page managers. My experience is that bot receives call back thread control only when ALL page manager set conversation to 'done'. It's not realistic since several page managers but normally only one is active.
Anyone have solution?

@etbuilder I am looking for an equivalent code sample for NodeJS/Javascript. Can you help?

plz anyone help with this similar issue
https://github.com/Microsoft/BotBuilder/issues/1465

@garypretty Did you end up doing a blog about this issue? I'm having the same problem, and was seeing if there was a way to solve this without the use of a proxy. I guess the in the bot builder there is no way to know if a message comes after the thread has been passed to the inbox? Like in the MessagesController for example.

@bhushanvadgave @sharmadine
I created a gist with an example, I made it quick and dirty for now - but it works
https://gist.github.com/amitbend/9c2109603f8913ab46470e3bea3be7c2

@etbuilder Hello, could you help me build the proxy like you built it? I am trying to build one in this issue: https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/issues/7


Pass options to Accio as comments in the Package.swift file, 2nd implementation proposal

This PR contains a new implementation proposal based on the discussion in https://github.com/JamitLabs/Accio/pull/55

@acecilia Thank you for the updated request. Will have a detailed look when I have more time, but looks good overall when skipping through it. Just one question: How are the new available options being used during the build process? I couldn't see where the service is being used as of now ...

@Dschee

How are the new available options being used during the build process?

Thats the golden question... When I tried to implement it, it was not that easy: I could not find a unique place to consume the service. I will give you an example: think about implementing the source option for the integration. The requirements are as follows:

Step1: the project does not need to be build, only checked out somewhere.
Step2: the Xcode project from the dependency has to be added to the main Xcode project.

At the moment, after resolving the dependency tree and building the frameworks, the only information that is passed to Step2 (in which the integration in the main Xcode project happens) is an array of FrameworkProduct. Such information is not enough for the Xcode integration step to do the right thing when the dependency is integrated using code.
I found a similar problem when thinking about the other options: a bigger refactor is needed to accommodate them, is not just about an additive change to the source code.
As a result, I think is better to keep this PR small, and refactor the code as the new options (source, static...) are introduced.

I basically agree on all points. I just think we should not merge this into the stable branch until at least one user-facing feature is using the new service. If there's any downside with this suggestion, I'm perfectly fine with creating a separate branch where you can merge the service already, e.g. if you wanted to keep each feature in a separate PR. But maybe it's enough if you just add the first API into this PR and we merge it then?

Super. Yes please, can you create a branch? And I think I can easily update my existing PR adding cocoapods integration, and merge it also in this new branch. And when you feel is ready you can move it to stable.

@acecilia I just gave you contributor rights, so you should now be able to create branches yourself. How about that? :)

🔥

@Dschee I am not being able to create branches, and I am not sure if I am doing something wrong. I am trying to push a new branch to the repo with the command git -c credential.helper= push -u origin work/additional-parameters-as-comments (the credential helper thing comes from https://stackoverflow.com/a/44033298) and putting my github user and password in the command line prompt, but this is the result:
Pushing to https://github.com/JamitLabs/Accio.git
remote: Permission to JamitLabs/Accio.git denied to acecilia.
fatal: unable to access 'https://github.com/JamitLabs/Accio.git/': The requested URL returned error: 403

Oh wait, let me try again, I just received the invitation email

Working now, thanks @Dschee

Regarding git help, I personally use https://git-fork.com/ as a GUI and can only recommend it. Amazing software and it's free, too. Also, I'm using the recommended way via SSH keys for authentication. See here for additional details. Maybe you want to try that, too.
Having that said, regarding the PR & branches, here's how I meant it: You can open as many work/... branches as you wish, no need for PRs there. But I recommend you to define a branch, maybe something like work/manifest-improvements, and put your current basic logic in there (without a PR, just push your renamed branch). Then, you can work on specific uses of this basic logic and post a PR targeting your work branch. This way, we can review one or multiple usages of the basic logic and merge them one by one once they are ready. After at least one usage is merged to your work branch, you can post a PR targeting the stable branch with your work branch. Then, I think, we can review the thing as a whole and merge it to stable and continue on from there.
I hope I could clarify the process. Feel free to ask me any questions if I missed something.


Document scope.

This doc only valid for adding blob storage. not valid for ADLS GEN1 and ADLS GEN2.

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

ID: 5be42fb6-e850-0990-de22-409392cb9e87
Version Independent ID: 5339ee18-6c77-1be3-e5ca-5cfd074a834d
Content: Add additional Azure storage accounts to HDInsight
Content Source: articles/hdinsight/hdinsight-hadoop-add-storage.md
Service: hdinsight
GitHub Login: @hrasheed-msft
Microsoft Alias: hrasheed

@anssenfang1 Yes, this document is valid for only Azure Storage.
For using Azure Data Lake Storage, you may refer the following links:
Using Azure Data Lake Storage Gen1
Using Azure Data Lake Storage Gen2
Hope this helps.

Please add the notes, otherwise customer may feel confusion.
Thanks
Anssen
From: CHEEKATLAPRADEEP-MSFT<EMAIL_ADDRESS>Sent: Friday, March 15, 2019 1:23 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Anssen Fang<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Document scope. (#27274)
@anssenfang1https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fanssenfang1&data=02|01|Anssen.Fang%40microsoft.com|e21c8271bf6e4f76e2c808d6a90653fc|72f988bf86f141af91ab2d7cd011db47|1|0|636882241977821368&sdata=xZwCjWfj%2FhaK8pfTokCRVVjSF9b8u9K9Q0FB9Tma8J8%3D&reserved=0 Yes, this document is valid for only Azure Storage.
For using Azure Data Lake Storage, you may refer the following links:
Using Azure Data Lake Storage Gen1https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fhdinsight%2Fhdinsight-hadoop-use-data-lake-store%3Ftoc%3D%252Fen-us%252Fazure%252Fhdinsight%252Fhadoop%252FTOC.json%26bc%3D%252Fen-us%252Fazure%252Fbread%252Ftoc.json&data=02|01|Anssen.Fang%40microsoft.com|e21c8271bf6e4f76e2c808d6a90653fc|72f988bf86f141af91ab2d7cd011db47|1|0|636882241977821368&sdata=UpMlm5vckfOUBIauZpNM7HyvyEgOYeJOw4CJ1QXGiJ8%3D&reserved=0
Using Azure Data Lake Storage Gen2https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fhdinsight%2Fhdinsight-hadoop-use-data-lake-storage-gen2&data=02|01|Anssen.Fang%40microsoft.com|e21c8271bf6e4f76e2c808d6a90653fc|72f988bf86f141af91ab2d7cd011db47|1|0|636882241977831381&sdata=zcN933%2BjV2z1G%2B%2FX1SVW6NjyFCvcVeRH5ex%2BoW9bSfs%3D&reserved=0
Hope this helps.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F27274%23issuecomment-473162792&data=02|01|Anssen.Fang%40microsoft.com|e21c8271bf6e4f76e2c808d6a90653fc|72f988bf86f141af91ab2d7cd011db47|1|0|636882241977841389&sdata=YLTnbrEcmc4RsOagPdoVYHL5jy7%2Fm%2FAO6Aa7JozPgtg%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAqiS-qVJmmLW7gDRwa7PZExafYmPR4X5ks5vWy5EgaJpZM4b1odA&data=02|01|Anssen.Fang%40microsoft.com|e21c8271bf6e4f76e2c808d6a90653fc|72f988bf86f141af91ab2d7cd011db47|1|0|636882241977841389&sdata=Eat4LTOdEn2Cux8t4qTghTknEdpKFhorvJCt%2FnziOKg%3D&reserved=0.

@anssenfang1 Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.
@hrasheed-msft Could you please look into this issue?


docker ps -a doesn't list container who removal failed

After I tried to remove a ceph-osd container which creates some btrfs subvolumes in the container file system the removal of the container failed.
core@core-03 ~ $ docker rm ceph-osd
Error response from daemon: Cannot destroy container 35dd46b1fdfb: Driver btrfs failed to remove root filesystem 35dd46b1fdfbaf283a35620748b60cb81929e36fb8afbdac174f92ce94ecd815: Failed to destroy btrfs snapshot: directory not empty

There is already a issue related to the removal of btrfs subvolumes: #4100
Docker also removes the container from docker ps -a like the container was successfully removed. If you doesn't notice the error message of docker rm you have no chance to remove the probably big subvolume because you also lose the container id.

Do you have a list of files in /var/lib/docker/container? Does those files still exist in that directory?

closing as dup of https://github.com/docker/docker/issues/6746


Applied istio peer authentication STRICT policy, 502 bad gateway error in the browser

Bug Description
When Istio Peer Authentication STRICT mode applied, getting 502 bad gateway error in the browser where as same application works with Peer Authentication PERMISSIVE mode.  Is there anything else am i missing to configure for STRICT mode ?
My environment details.
Istio 1.16.1
AWS EKS 1.24
AWS ALB Ingress Controller v2.4.5
AWS Application Load balancer ingress
Version
kubectl version --short
Client Version: v1.20.0
Server Version: v1.24.8-eks-ffeb93d

Additional Information
No response

Need more details. Are you doing ALB -> Pod with STRICT? ALB doesn't speak mtls so that is expected

Thanks for your response.  traffic flow is  AWS ALB --> AWS ec2-Instance --> K8s-Service -->K8s Pod

if you are in STRICT mTLS then it only accepts requests with mTLS. So the ALB/AWS ec2 instance probably don't so they are rejected.

You can follow https://cloud.google.com/architecture/exposing-service-mesh-apps-through-gke-ingress. Note this is for GKE but the same applies to AWS


Are the msbuild sdk nuget package dependencies necessary

While looking at the latest available Traversal package on nuget.org, I noticed that the package contains empty dependency groups for net40 and netstandard2.0. While this is just for cosmetics, I wonder if we want to omit them instead by setting <SuppressDependenciesWhenPacking>true</SuppressDependenciesWhenPacking> in the project files.
Happy to submit a PR.

Technically it doesn't matter since Microsoft.Build.Traversal is a NuGet-based MSBuild Project SDK and during "restore" of this kind of package, NuGet does not respect dependencies or target framework compatibility.  I'm pretty sure you can't add a <PackageReference /> to that kind of package either.
But if you want to submit a PR, I'll gladly accept it 😄

Technically it doesn't matter since Microsoft.Build.Traversal is a NuGet-based MSBuild Project SDK and during "restore" of this kind of package, NuGet does not respect dependencies or target framework compatibility.

While NuGet doesn't respect it, we do have some tools that inspect packages and their dependencies, i.e. ApiCompat, or SBRP. I will submit a PR to suppress the dependencies.


Pass customStyles to filler's

customStyle.dayButtonFiller is implemented but the styles were not passed to the Day

@cornedor Thank for the PR and sorry for the late response. This has recently been added to master and will be available on the next release. Now you can specify dayCircleFiller and eventIndicatorFiller


Well-behaved Arbitrary instances for Plutus types with implicit predicates on acceptable values

Area

[ ] Plutus Foundation Related to the GHC plugin, Haskell-to-Plutus compiler, on-chain code
[x] Plutus Application Framework Related to the Plutus application backend (PAB), emulator, Plutus libraries
[ ] Marlowe Related to Marlowe
[ ] Other Any other topic (Playgrounds, etc.)

Describe the feature you'd like
Currently, there is no standard suite of Arbitrary instances that seem to actually be suitable for testing smart-contracts -
Plutus.PAB.Arbitrary has some generic-based instances which are suitable for some of the types,
but in particular, this isn't sufficient to generate well-behaved values of Value.
For example with the generic Arbitrary instance - the following property will fail:
propReflEq :: Value -> Bool
propReflEq x = x == x

with value:
(Map {unMap = [(,Map {unMap = []}),(,Map {unMap = [(0xcd,-1),(\"\",-2)]})]})"

It would be useful to have a (better-located) module with more well-behaved instances.
A possible instance
for now Value, we have the following instance. A library-suitable instance may want a more particular implementation, and an impl of shrink ...
instance Arbitrary Value where
  arbitrary = foldMap (Tuple.Extra.uncurry3 Value.singleton) <$> arbitrary

I'm not sure if this is strictly correct since, for example, maybe it's technically valid to have a value such as in txInfoForge, with both positive and negative values of a given AssetClass... The exact expectations aren't clear.
Alternatively / Additionally
Modules with types such as Value should export functions to check/make an existing value well-behaved. normalizeValue, which is not exported from Plutus.V1.Ledger.Value is a (partial) example of this.

Hi! Thanks for the issue!
Yeah, the current instance of Value is very rudimentary and is not actually properly used for tests at current moment.
Feel free to open a PR with your proposed instance!

Which package and module should orphan Arbitrary instances go?
Perhaps Plutus.Contract.Test.Arbitrary? Or somewhere else?

Yep, Plutus.Contract.Test.Arbitrary sounds good.


SIGSEGV on php-fpm

Laravel Version: 5.5.2
PHP Version: 7.1.7

Description:

error : SIGSEGV

on /var/log/php-fpm/7.1/error.log
[06-Sep-2017 12:12:25] WARNING: [pool www] child 19250 exited on signal 11 (SIGSEGV) after 1.315077 seconds from start
[06-Sep-2017 12:12:25] NOTICE: [pool www] child 19263 started

core dump

#0  0x00007f3196dc96fa in nr_php_scope_get () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_wrapper.c:118
#1  0x00007f3196d9bd38 in nr_laravel_router_method_with_request () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/fw_laravel.c:804
#2  0x00007f3196dc8b56 in nr_zend_call_orig_execute_special () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_user_instrument.c:62
#3  0x00007f3196daeb04 in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1117
#4  0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#5  0x00000000006393f5 in ?? ()
#6  0x00000000005e86cb in execute_ex ()
#7  0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#8  0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#9  0x00000000006393f5 in ?? ()
#10 0x00000000005e86cb in execute_ex ()
#11 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#12 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#13 0x00000000006393f5 in ?? ()
#14 0x00000000005e86cb in execute_ex ()
#15 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#16 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#17 0x00000000006393f5 in ?? ()
#18 0x00000000005e86cb in execute_ex ()
#19 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#20 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#21 0x00000000006393f5 in ?? ()
#22 0x00000000005e86cb in execute_ex ()
#23 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#24 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#25 0x00000000006393f5 in ?? ()
#26 0x00000000005e86cb in execute_ex ()
#27 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#28 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#29 0x00000000006393f5 in ?? ()
#30 0x00000000005e86cb in execute_ex ()
#31 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#32 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#33 0x00000000006393f5 in ?? ()
#34 0x00000000005e86cb in execute_ex ()
#35 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#36 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#37 0x00000000006393f5 in ?? ()
#38 0x00000000005e86cb in execute_ex ()
#39 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#40 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#41 0x00000000006393f5 in ?? ()
#42 0x00000000005e86cb in execute_ex ()
#43 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#44 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#45 0x00000000006393f5 in ?? ()
#46 0x00000000005e86cb in execute_ex ()
#47 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#48 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#49 0x00000000006393f5 in ?? ()
#50 0x00000000005e86cb in execute_ex ()
#51 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#52 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#53 0x00000000006393f5 in ?? ()
#54 0x00000000005e86cb in execute_ex ()
#55 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#56 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
---Type <return> to continue, or q <return> to quit---
#57 0x00000000006393f5 in ?? ()
#58 0x00000000005e86cb in execute_ex ()
#59 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#60 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#61 0x00000000006393f5 in ?? ()
#62 0x00000000005e86cb in execute_ex ()
#63 0x00007f3196dc8afa in nr_zend_call_orig_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_user_instrument.c:49
#64 0x00007f3196d9a937 in nr_laravel5_middleware_handle () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/fw_laravel.c:643
#65 0x00007f3196dc8b56 in nr_zend_call_orig_execute_special () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_user_instrument.c:62
#66 0x00007f3196daeb04 in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1117
#67 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#68 0x00000000006393f5 in ?? ()
#69 0x00000000005e86cb in execute_ex ()
#70 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#71 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#72 0x00000000006393f5 in ?? ()
#73 0x00000000005e86cb in execute_ex ()
#74 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#75 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#76 0x00000000006393f5 in ?? ()
#77 0x00000000005e86cb in execute_ex ()
#78 0x00007f3196dc8afa in nr_zend_call_orig_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_user_instrument.c:49
#79 0x00007f3196d9a937 in nr_laravel5_middleware_handle () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/fw_laravel.c:643
#80 0x00007f3196dc8b56 in nr_zend_call_orig_execute_special () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_user_instrument.c:62
#81 0x00007f3196daeb04 in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1117
#82 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#83 0x00000000006393f5 in ?? ()
#84 0x00000000005e86cb in execute_ex ()
#85 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#86 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#87 0x00000000006393f5 in ?? ()
#88 0x00000000005e86cb in execute_ex ()
#89 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#90 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#91 0x00000000006393f5 in ?? ()
#92 0x00000000005e86cb in execute_ex ()
#93 0x00007f3196dc8afa in nr_zend_call_orig_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_user_instrument.c:49
#94 0x00007f3196d9a937 in nr_laravel5_middleware_handle () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/fw_laravel.c:643
#95 0x00007f3196dc8b56 in nr_zend_call_orig_execute_special () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_user_instrument.c:62
#96 0x00007f3196daeb04 in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1117
#97 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#98 0x00000000006393f5 in ?? ()
#99 0x00000000005e86cb in execute_ex ()
#100 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#101 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#102 0x00000000006393f5 in ?? ()
#103 0x00000000005e86cb in execute_ex ()
#104 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#105 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#106 0x00000000006393f5 in ?? ()
#107 0x00000000005e86cb in execute_ex ()
#108 0x00007f3196dc8afa in nr_zend_call_orig_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_user_instrument.c:49
#109 0x00007f3196d9a937 in nr_laravel5_middleware_handle () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/fw_laravel.c:643
#110 0x00007f3196dc8b56 in nr_zend_call_orig_execute_special () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_user_instrument.c:62
#111 0x00007f3196daeb04 in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1117
#112 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#113 0x00000000006393f5 in ?? ()
---Type <return> to continue, or q <return> to quit---
#114 0x00000000005e86cb in execute_ex ()
#115 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#116 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#117 0x00000000006393f5 in ?? ()
#118 0x00000000005e86cb in execute_ex ()
#119 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#120 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#121 0x00000000006393f5 in ?? ()
#122 0x00000000005e86cb in execute_ex ()
#123 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#124 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#125 0x00000000006393f5 in ?? ()
#126 0x00000000005e86cb in execute_ex ()
#127 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#128 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#129 0x00000000006393f5 in ?? ()
#130 0x00000000005e86cb in execute_ex ()
#131 0x00007f3196daee1b in nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1187
#132 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#133 0x00000000006393f5 in ?? ()
#134 0x00000000005e86cb in execute_ex ()
#135 0x00007f3196daef5a in nr_php_execute_file () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:847
#136 nr_php_execute_enabled () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1069
#137 0x00007f3196daf462 in nr_php_execute () at /home/hudson/slave-workspace/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_execute.c:1297
#138 0x000000000063b884 in zend_execute ()
#139 0x00000000005a3694 in zend_execute_scripts ()
#140 0x0000000000543748 in php_execute_script ()
#141 0x000000000042cc6c in ?? ()
#142 0x00007f31a9a7bb35 in __libc_start_main () from /lib64/libc.so.6
#143 0x000000000042dd75 in _start ()

Environments

reverse proxy : nginx(1.11.3)
cgi :  php-fpm

Steps To Reproduce:

nginx + php-fpm + laravel5.5

laravel5.4 do not occur

Please ask on the forums, this repo is for bug reporting only. You can use https://laracasts.com/discuss or https://laravel.io/forum which are forums with a very large community of developers helping each other.


[NumberField] Component and Hook

[x] I have followed (at least) the PR section of the contributing guide.

Closes #185.
👉 https://deploy-preview-186--base-ui.netlify.app/base-ui/react-number-field/
TODO:

[ ] Decide on locale (part of format?) and inputWheelScrub prop names
[ ] Complete tests
[ ] Documentation

Rebased on HEAD. It seems to fix Circle CI, I don't know why.

@michaldudak yeah you're right, previously it was 2px but I must have changed something that reverted it back to 1px. Will fix.

Thank you @colmtuite!

Seems like we don't have the teleport threshold thingy prop on ScrubAreaCursor yet? Are you planning to add that?

Yes, will add.

Should scrubbing start from where the pointer was when scrubbing began, or when the pointer direction changes during scrubbing? Idk how to explain wtf I'm on about here 🤣 It's noticeable when min and max are set. If you set max, then scrub way beyond the max value, you need to scrub all the way back down before the value decrements. Perhaps it could begin decrementing immediately when the pointer direction changes?

No I know exactly what you're talking about because I intentionally made it work the way it currently does 😆 . I don't know if it's correct but it felt more right to me — but if you scrub too far it takes too long to "get back" indeed.
https://github.com/mui/base-ui/pull/186/files#diff-baaa930fa9d9c0612e404a05ea9e8e510a5f4122cd1348a24f94eecdce5cd1c4R118-R122

The largeStep logic seems odd to me. I expected it to just increment/decrement the value by whatever the largeStep value is?

The step logic in react-aria & the current NumberField not only increments but also snaps, at least for integer values (the default). So largeStep also snaps — but I'm not sure if that's right?

smallStep doesn't seem to be working for me. Nothing happens when I hold cmd and then increment/decrement.

Yeah, I made it 1 by default, so it doesn't do anything. It doesn't work with the default integer formatting. It's useful for currencies, percentages, etc.

List of source code updates needed

Fix the “magnifier” appearing on iOS when press-holding the stepper buttons.
Add teleportDistance (or other name) prop to loop closer to the input compared to the viewport.
Potentially limit the “scrub past“ distance when a max/min is specified, so it doesn't take too long to "get back".
Potentially remove snapping behavior for smallStep and largeStep. Set smallStep to 0.1 by default if the formatting style is not integer - @colmtuite
Fix bug when there’s a “-“ and you can’t type “-“ again when all content has been selected to be overwritten (e.g. paste).
Fix virtual cursor being too big when zooming (cmd+ or pinch-zoom). It should invert the scale to match the OS size.
Fix 1px sensitivity to 2px for scrub area, and add sensitivity prop.
Add Home and End key support if min/max are specified.
Add displayName to Contexts.
Ensure all imports use the path rather than the top-level barrel.
Cache Intl.NumberFormat usage.
Match various nits/conventions pointed out by Olivier.

Decisions from a recent call:

Agreed to just change the scrub min/max thing. There was one other issue mentioned, but James couldn't remember what it was. So the plan is to change it, then test again.
Do some research to see if cmd/ctrl is the best key for smallStep. Perhaps alt/option is better?
Internationalisation: passing functions and stuff needs to be added.

@colmtuite

Already changed
Given only Chakra seems to have this, I couldn't find any info about it. I don't think it matters really — I asked Claude and its first thought was Alt not Meta, if that has any bearing. But it said it doesn't really matter overall.

Internationalisation: passing functions and stuff needs to be added.

Can you elaborate more here? The format prop doesn't accept a function in that it only accepts Intl.NumberFormat, but do you want to enable them to format the input however they like as well? (I believe Chakra does this.)
We might be missing props similar to validate (accepts a function) and validationBehavior (string) from react-aria, however.

@atomiks

I asked Claude and its first thought was Alt

Ok yeah my first thought was Alt also. If that's the only info we have, and both point to Alt, I guess let's go with Alt.

do you want to enable them to format the input however they like as well

No this was just a note I took from our call, not sure what you meant when you were talking about formatting, internationalisation, and functions. I remember you saying some piece of work around internationalisation is still incomplete?

@colmtuite

Ok yeah my first thought was Alt also. If that's the only info we have, and both point to Alt, I guess let's go with Alt.

Alright, will change 👍

I remember you saying some piece of work around internationalisation is still incomplete?

Yeah there were some bugs remaining with the parsing and validation functions, but I should have fixed most of them in the recent commits. However these are only internal and not part of any API.


filter: add grpc upstream stats

Description: Add upstream_rq_time histogram to grpc stats
Risk Level: Medium
Testing: unit test + manual test
Docs Changes: add note about enable_upstream_stats
Release Notes: added
Parially Fixes #9169

cc @kyessenov

Not sure why the docs are failing :thinking:

All good for me I think

@Sh4d1 Do not force-push to PR branches please. It makes reviewing changes much more difficult.

/retest

/azp retest

@ggreenway it was only a rebase :smile:

/azp run envoy-presubmit

@Sh4d1 Don't rebase. Please merge instead. We squash the commits when the PR is merged so the extra history doesn't hurt anything. But when people force-push, there's not a way to automatically see that it is only a rebase. As described in https://github.com/envoyproxy/envoy/blob/master/CONTRIBUTING.md:

Once you submit a PR, please do not rebase it. It's much easier to review if subsequent commits are new commits and/or merges. We squash rebase the final merged commit so the number of commits you have in the PR don't matter.

/azp run envoy-presubmit (macOS)

@ggreenway okay! Sorry I missed that part, my bad :roll_eyes:

@envoyproxy/api-shepherds PTAL


24px - Copy

#119
https://www.figma.com/file/2rjsQp42uKvzPXzLZIqOeA/Octicons-v2-Source?node-id=746%3A2588

@edokoa I prefer the third version from the left.
@colebemis this metaphor ties into a question @edokoa had earlier:

Clippy icon: It's similar to 'copy' in meaning, right now it's in the viewer, but not in the 32px source. Should we add this icon to the set even if it's substituted by 'copy'?

Is this version of the copy icon the direction we want to go for the "copy" metaphor or should we continue to include clippy too?

Earlier we chose to abandon this metaphor in favor of the clipboard metaphor. I must have for got to remove this remove the viewer. Sorry for the confusion @edokoa.


Add flag to set TFTP block size.

Sometimes increase of TFTP block size helps to speed up TFTP transfer.
It will be grate to have such flag in SMEE.
If understand correctly it's already supported by a library that SMEE is using: https://github.com/tinkerbell/ipxedust/blob/main/cmd.go#L117C2-L117C2
Thanks.

Thank you for quick response. Works g8.


[Improvement] [UI] Better if cancelling the editing of an existing feed simulation without any changes won't give a pop up to confirm

== Steps to Recreate ==

Start the editor, go to event simulator and the select 'Feed Simulation'
Create a feed simulation with 'CSV file' as the simulation and save.
Click 'Edit' of the created simulation and press 'Cancel' to exit without doing any modifications.

== Actual Result ==
Popup will be displayed by asking to confirm where to discard the changes or not even there're no changes.

== Suggestion ==
Better if the pop up won't display if the user haven't done any changes for simulation.

@maneeshaheshan fixed in PR https://github.com/wso2/carbon-analytics/pull/426 please review and close

Hi @dnwick ,
Existing from the editing mode of a simulation by clicking the close button at top right corner was fixed. But existing by clicking the 'Cancel' button needs to be fix.

@dnwick can you check this and confirm.

This fixed now


change init to be consistent with set_lora_modem() doc

I've been trying to get the Adafruit LoRa Radio RFM95W to work for a while, and found this bit to be inconsistent with the documentation in the sx1276_7_8_9, and was what prevented the radio from working

For the sx1276/7/8/9, the RadioKind reset() sets the Semtech chip in sleep mode to ensure that henceforth it is configured as a LoRa radio.  All settings of state after that ensure LoRa mode is maintained:

impl LoRaMode {
/// Mode value, including LoRa flag
pub fn value(self) -> u8 {
(self as u8) | 0x80u8
}
}

self.ensure_ready(RadioMode::Sleep).await?; does nothing for the sx1276/7/8/9 RadioKind;

changing the API init() function affects all LoRa chips, not just the sx1276/7/8/9.  Changes should be restricted to the RadioKind implementation.

It is not clear to me at this point that the current implementation is out of spec, nor why the RFM95W fails to initialize properly.
If it needs to be pushed into sleep twice to be properly initialized, consider a change to the sx1276/7/8/9 radio kind reset() function to do it there.  Also, add a new board type for this board in mod_params.rs and only call the extra sleep() call for that board type.

The problem was that set_suspend was called after the reset, but before the set_lora_modem. Perhaps set_sleep should be set inside set_lora_modem in the sx126X impl? I don't have other chips to test this on, only these feathers.
I forgot ensure_ready doesn't do anything, although the init routine in the RadioHead Arduino library I based this change on does call a register read to check if sleep was properly entered.
    // Set sleep mode, so we can also set LORA mode:
    spiWrite(RH_RF95_REG_01_OP_MODE, RH_RF95_MODE_SLEEP | RH_RF95_LONG_RANGE_MODE);
    delay(10); // Wait for sleep mode to take over from say, CAD
    // Check we are in sleep mode, with LORA set
    if (spiRead(RH_RF95_REG_01_OP_MODE) != (RH_RF95_MODE_SLEEP | RH_RF95_LONG_RANGE_MODE))
    {
//	Serial.println(spiRead(RH_RF95_REG_01_OP_MODE), HEX);
	return false; // No device present?
    }

I'll add a board type once I figure out some of the other specifics, as I had to comment out set_oscillator to get it to work as well.

As you run into additional issues with the Feather boards, I'd be glad to help brainstorm solutions here.  I expect there will be unique properties across LoRa boards of a given kind, and hope that the architecture has enough flexibility to provide support.  Where the architecture falls short, it will be enhanced.
Also, if you are interested, there is a group chat on LoRaWAN/LoRa for Rust, which often touches on lora-phy and LoRaWAN 1.0.4:
https://matrix.to/#/#public-lora-wan-rs:matrix.org

Please address an updated PR to lora-phy v2.0.0.


Fixed rediscluster schedule source.

This PR removes MGET command from a cluster source, because it's not available in clustering mode.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.27%. Comparing base (dce4dac) to head (1315cef).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #62      +/-   ##
===========================================
- Coverage    96.34%   96.27%   -0.07%
===========================================
  Files            7        7
  Lines          219      215       -4
===========================================
- Hits           211      207       -4
  Misses           8        8

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


Cancellation token passed to provideReferences is never cancelled

VSCode Version: 0.10.11
OS Version: OS X

The cancellation token passed to vscode.ReferenceProvider#provideReferences appears to not get cancelled ever - and in particular, not get cancelled when the Find References panel is closed by the user.
Since Find References can require an expensive compute operation to be needed, this is particularly unfortunate.  In the vscode-go extension, this user command spawns a process which can in pathological cases take more than a minute (and use 100% of multiple cores).  A user can easily do Find References multiple times (because they see no results being returned), causing multiple of these processes to be spawned.
Are there any documented semantics for the cancelation token's passed to these higher level language service APIs?  Is there some case where the provideReferences cancellation token will actually be cancelled?

I don't get the cancellation event when using the Escape key, only when pressing the x of the references widget.

nice find.


switching to us-east-1 breaks the installer

Hi, after having installed succesfully many times to eu-west-1, I can't seem to get it installed in us-east-1, even if I give it the region 'us-east-1b'. I have manually inspected for any ghost artifacts, but the destroy script cleans up ok. I spent around 3 hours playing with this, only to conclude something is different between these regions.
I have not changed anything in cluster.yaml but the region and az.

is the AMI ID used for coreos valid in us-east-1 ?
On Wed, Feb 10, 2016 at 11:34 AM, Maurice Faber<EMAIL_ADDRESS>wrote:

Hi, after having installed succesfully many times to eu-west-1, I can't
seem to get it installed in us-east-1, even if I give it the region
'us-east-1b'. I have manually inspected for any ghost artifacts, but the
destroy script cleans up ok. I spent around 3 hours playing with this, only
to conclude something is different between these regions.
I have not changed anything in cluster.yaml but the region and az.
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/coreos-kubernetes/issues/273.

It is blackboxed into the setup. Dunno. Probably selected based on region through a helper.

On 10 feb. 2016, at 23:27, somejfn<EMAIL_ADDRESS>wrote:
is the AMI ID used for coreos valid in us-east-1 ?
On Wed, Feb 10, 2016 at 11:34 AM, Maurice Faber<EMAIL_ADDRESS>wrote:

Hi, after having installed succesfully many times to eu-west-1, I can't
seem to get it installed in us-east-1, even if I give it the region
'us-east-1b'. I have manually inspected for any ghost artifacts, but the
destroy script cleans up ok. I spent around 3 hours playing with this, only
to conclude something is different between these regions.
I have not changed anything in cluster.yaml but the region and az.
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/coreos-kubernetes/issues/273.

—
Reply to this email directly or view it on GitHub.

Yeah, that is retrieved through coreosutil.GetAMIData(channel)

/cc @colhom

@morriz what is the symptom? Does the cloudformation make it to the Creating phase? Error in the events tab?
Are you using custom artifacts that you uploaded yourself, or the coreos hosted artifacts?

Hi, tnx for coming back so quickly. I have to say the go scripts don't give back much, only that the creation of the instance fails. Can you give me instructions how to generate more?
But it is like I said. I use the 'coreos-kubernetes' github repo as is, and only changed the region.

On 18 feb. 2016, at 20:30, colhom<EMAIL_ADDRESS>wrote:
@morriz https://github.com/morriz what is the symptom? Does the cloudformation make it to the Creating phase? Error in the events tab?
Are you using custom artifacts that you uploaded yourself, or the coreos hosted artifacts?
—
Reply to this email directly or view it on GitHub https://github.com/coreos/coreos-kubernetes/issues/273#issuecomment-185880401.

Morriz: Could you log into aws console and look for the cloudformation that kube-aws is creating? It will be the same name as your cluster name parameter.
When/if you find it, look in the events tab for events with failed statuses.

It complains about a key pair not existing, the pair that I used to succesfully create the stack in eu-west-1...weird. I assumed  the key pair would be for all regions. Now let me see where I can add it to another region...got any hints?

On 19 feb. 2016, at 02:54, colhom<EMAIL_ADDRESS>wrote:
Morriz: Could you log into aws console and look for the cloudformation that kube-aws is creating? It will be the same name as your cluster name parameter.
When/if you find it, look in the events tab for events with failed statuses.
—
Reply to this email directly or view it on GitHub https://github.com/coreos/coreos-kubernetes/issues/273#issuecomment-186009746.

Nevermind, it's good now. Darn my cross region noobness ;p

On 20 feb. 2016, at 14:01, Maurice Faber<EMAIL_ADDRESS>wrote:
It complains about a key pair not existing, the pair that I used to succesfully create the stack in eu-west-1...weird. I assumed  the key pair would be for all regions. Now let me see where I can add it to another region...got any hints?

On 19 feb. 2016, at 02:54, colhom<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Morriz: Could you log into aws console and look for the cloudformation that kube-aws is creating? It will be the same name as your cluster name parameter.
When/if you find it, look in the events tab for events with failed statuses.
—
Reply to this email directly or view it on GitHub https://github.com/coreos/coreos-kubernetes/issues/273#issuecomment-186009746.


Update GitHub Actions Runner to at least v2.302.1 by 2023-03-15

Another month, another upgrade. See https://github.com/iree-org/iree/issues/11876 for making this less toilsome
https://github.com/actions/runner/releases/tag/v2.302.1

I fixed this, but forgot to close the issue


Add latest issues and regenerate opam files

This little PR

adds the latest two issues found by @Lucccyo and @shym
regenerates the included opam files - as the bump to dune 3.0 in #255 apparently causes changes in the output :shrug:

CI seems happy (modulo network failures) so I'll merge.


Improve polling capabilities in o.a.s.testing.clients

Patch for https://issues.apache.org/jira/browse/SLING-6853

@volteanu, as the patch was applied, can you close this PR?


Issue viewing morph animations for assets converted from glTF2.0 to usdz with Reality Converter

There are 3 assets from the glTF2.0 sample assets repo that rely on morphs. Reality Converter will convert them to .usdz however when trying to view the assets or animations in usdview, I can't see the asset.
Here are the converted .usdz files for reference:

AnimatedMorphCube
AnimatedMorphSphere
MorphStressTest

I've run usdchecker on these assets however it returns with Success! so it's not clear to me if this is a limitation of Reality Converter or something else. Happy to do some leg work on this if needed but I'm not sure where to start

Dear Andy,
I’d like to note, that the AnimatedMorphCube

 animates not only between the two morph targets, but also mixes in the original cube (so, there are 3 states)
The morph animation is not supported in the Space-Bar-Preview in macOS Finder (a different renderer than used by Preview.app)
Nor does it work in AR Quick Look on iOS/iPadOS 16.3/16.4 beta

I assume the other samples you mentioned, have similar trouble, as documented by Apple here
https://developer.apple.com/documentation/realitykit/validating-usd-files?changes=_3￼
Validating feature support for USD files | Apple Developer Documentation
developer.apple.com
—
Thomas Kumlehn

Am 25.02.2023 um 19:22 schrieb Andy @.***>:
There are 3 assets from the glTF2.0 sample assets repo https://github.com/KhronosGroup/glTF-Sample-Models/tree/master/2.0 that rely on morphs. Reality Converter https://developer.apple.com/augmented-reality/tools/ will convert them to .usdz however when trying to view the assets or animations in usdview, I can't see the asset.
Here are the converted .usdz files for reference:
AnimatedMorphCube https://github.com/beersandrew/assets/tree/add-test-assets-from-gltf/test_assets/AnimatedMorphCube
AnimatedMorphSphere https://github.com/beersandrew/assets/tree/add-test-assets-from-gltf/test_assets/AnimatedMorphSphere
MorphStressTest https://github.com/beersandrew/assets/tree/add-test-assets-from-gltf/test_assets/MorphStressTest
It's not clear to me if this is a limitation of Reality Converter or something else. Happy to do some leg work on this if needed but I'm not sure where to start
—
Reply to this email directly, view it on GitHub https://github.com/usd-wg/assets/issues/34, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAR6XYJI5FH6OYC7AAKINLWZJEXLANCNFSM6AAAAAAVH7WFT4.
You are receiving this because you are subscribed to this thread.

Dear Andy,
I’d like to note, that the AnimatedMorphCube

 animates not only between the two morph targets, but also mixes in the original cube (so, there are 3 states)
The morph animation is not supported in the Space-Bar-Preview in macOS Finder (a different renderer than used by Preview.app)
Nor does it work in AR Quick Look on iOS/iPadOS 16.3/16.4 beta

I assume the other samples you mentioned, have similar trouble, as documented by Apple here
https://developer.apple.com/documentation/realitykit/validating-usd-files?changes=_3￼
Validating feature support for USD files | Apple Developer Documentation
developer.apple.com
Best wishes
Thomas Kumlehn
@.***

Am 25.02.2023 um 19:22 schrieb Andy @.***>:
There are 3 assets from the glTF2.0 sample assets repo https://github.com/KhronosGroup/glTF-Sample-Models/tree/master/2.0 that rely on morphs. Reality Converter https://developer.apple.com/augmented-reality/tools/ will convert them to .usdz however when trying to view the assets or animations in usdview, I can't see the asset.
Here are the converted .usdz files for reference:
AnimatedMorphCube https://github.com/beersandrew/assets/tree/add-test-assets-from-gltf/test_assets/AnimatedMorphCube
AnimatedMorphSphere https://github.com/beersandrew/assets/tree/add-test-assets-from-gltf/test_assets/AnimatedMorphSphere
MorphStressTest https://github.com/beersandrew/assets/tree/add-test-assets-from-gltf/test_assets/MorphStressTest
It's not clear to me if this is a limitation of Reality Converter or something else. Happy to do some leg work on this if needed but I'm not sure where to start
—
Reply to this email directly, view it on GitHub https://github.com/usd-wg/assets/issues/34, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAR6XYJI5FH6OYC7AAKINLWZJEXLANCNFSM6AAAAAAVH7WFT4.
You are receiving this because you are subscribed to this thread.

Thanks for the info Thomas. This might turn into some note or documentation that overall morphs are not supported (at least from Reality Converter). I'm pretty new to this space and I see a lot of descriptive information on the site you listed about what is and what isn't supported from Apple's side, is there something there that would point to morphs not working? I naively just looked for morphs on that page so maybe it's categorized as some other word in that documentation.
I know another conversion tool guc was brought up from the working group, so maybe I can try that tool and see if morphs will translate properly from there and maybe it would be helpful to list out all of the properties or qualities we look for when converting from one asset to another and how each converter performs with them.
Anyway thanks a lot for testing and taking a look
Best,
Andy

It’s often also called Blendshape and that is currently not supported by RealityKit
Thomas Kumlehn
@.***

Am 01.03.2023 um 13:43 schrieb Andy @.***>:
Thanks for the info Thomas. This might turn into some note or documentation that overall morphs are not supported (at least from Reality Converter). I'm pretty new to this space and I see a lot of descriptive information on the site you listed about what is and what isn't supported from Apple's side, is there something there that would point to morphs not working? I naively just looked for morphs on that page so maybe it's categorized as some other word in that documentation.
I know another conversion tool guc was brought up from the working group, so maybe I can try that tool and see if morphs will translate properly from there and maybe it would be helpful to list out all of the properties or qualities we look for when converting from one asset to another and how each converter performs with them.
Anyway thanks a lot for testing and taking a look
Best,
Andy
—
Reply to this email directly, view it on GitHub https://github.com/usd-wg/assets/issues/34#issuecomment-1450089999, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAR6X4JXB7LGKH5POEKVGDWZ5AAZANCNFSM6AAAAAAVH7WFT4.
You are receiving this because you commented.


Deepti dk datetime improvement

Description
DateTime component updated for create-event-modal
Fixes #
How to test?
storybook
Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] This PR is ready to be merged and not breaking any other functionality

doesnt work as intended


Add a middleware to encode/decode MessagePack payloads

Heavily based on the Json Middleware. Uses https://github.com/lexmag/msgpax as the engine.

🔥 🔥 🔥 💜
@elixir-tesla/core Please take a look.

🚀 💜