first draft of privatelink docs

Closes #9314.
Waiting for UI to be finalized for some steps.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/858e6f6a7c0708073fe02867b2cf7bb11eb4a3cb/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

cockroachcloud/connect-to-your-cluster.md, line 124 at r1 (raw file):
Previously, lnhsingh (Lauren Hirata Singh) wrote…
This link only works if you had selected VPC Peering in the above step. Since you have two sets of instructions here (one for AWS and one for GCP), can you add in the filtering logic here as well so you just select one of the tabs once and then the rest of the instructions is filtered for you?

I'm struggling with getting the links to the filtered sections to work correctly. Everything I've tried seems to break the formatting somehow. I think the best solution might be to just link to the ### Establish VPC Peering or AWS PrivateLink heading unless you know of a better way.

cockroachcloud/connect-to-your-cluster.md, line 124 at r1 (raw file):
Previously, lnhsingh (Lauren Hirata Singh) wrote…
This link only works if you had selected VPC Peering in the above step. Since you have two sets of instructions here (one for AWS and one for GCP), can you add in the filtering logic here as well so you just select one of the tabs once and then the rest of the instructions is filtered for you?

I'm struggling with getting the links to the filtered sections to work correctly. Everything I've tried seems to break the formatting somehow. I think the best solution might be to just link to the ### Establish VPC Peering or AWS PrivateLink heading unless you know of a better way.

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/70078d22c793c27bafd7d218e28f31b66d88225e/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/70078d22c793c27bafd7d218e28f31b66d88225e/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1842bbda9fcfa6e948d79338fe8c7b080bef30fe/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1842bbda9fcfa6e948d79338fe8c7b080bef30fe/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1842bbda9fcfa6e948d79338fe8c7b080bef30fe/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1842bbda9fcfa6e948d79338fe8c7b080bef30fe/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a1976481dcbe22b543da876f0083202f4acef290/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a1976481dcbe22b543da876f0083202f4acef290/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e0a41ed37e578bb41e12a1cd111083d262d04ce8/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e0a41ed37e578bb41e12a1cd111083d262d04ce8/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/465a2e05dc440f1ee1f13e2f75eb92f8d37dae7d/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/465a2e05dc440f1ee1f13e2f75eb92f8d37dae7d/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

cc: @tommy @rsadres if interested

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/480be52c5eefcd99c19a28d1c529c1d4201c4a62/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/97b3e489ca930da75f83585d3428b41307a4e82c/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7bea847f792a77fd0760c9dc27bf81e13c2a126e/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ef4af076e85dca9bf9b6d488584f94079067f963/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

cc: @j-low for awareness

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9bba157a45b6cfaab04b1daa837c37bfbdcd083d/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/02711d8d3e2b9d283f308e924f4d7a2fbe6f5c4b/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md
cockroachcloud/security-overview.md

Nice @gemma-shay this is looking good! I just noticed a nit:

The tab between VPC Peering and AWS PrivateLink seems misaligned (link)

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e814b7b16123e4b013dc99a6c2e2624750e22705/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/create-your-cluster.md
cockroachcloud/network-authorization.md
cockroachcloud/security-overview.md


cassandra instrumentation: spans for prepare method never ends

Describe the bug
Sleuth 3.1.5.
In cassandra instrumentation spans for "execute*" method ends in TraceRequestTracker, but for "prepare*" method span never ends. TraceRequestTracker does not intercept results for prepare methods.

@mp911de do you recall this problem? Most likely we will have the same one in Spring Data Cassandra if it is here in Sleuth

Good catch. That's fixed in Spring Data Cassandra already:
https://github.com/spring-projects/spring-data-cassandra/blob/f0f6895ebb1586ed2bd34bdfab8d793ea9829c5b/spring-data-cassandra/src/main/java/org/springframework/data/cassandra/observability/CqlSessionObservationInterceptor.java#L76-L96

Please upgrade to Micrometer Tracing. Spring Cloud Sleuth is feature complete and out of OSS support.


High Memory usage from "Unknown Sensor" spam

Hi
After some days of usage, Hass Workstation Service is using lot of RAM. (It goes up to 1GB).
RAM usage is reset after a reboot of the service.
After inspecting the log, it seems that an unknown sensor is spaming the service.
{"@t":"2022-01-07T02:26:16.8829444Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":35}
{"@t":"2022-01-07T02:26:17.8878644Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":35}
{"@t":"2022-01-07T02:26:18.8878253Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":18}
{"@t":"2022-01-07T02:26:19.9047531Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":4}
{"@t":"2022-01-07T02:26:20.9214253Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":63}
{"@t":"2022-01-07T02:26:21.9360861Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":63}
{"@t":"2022-01-07T02:26:22.9497412Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":18}
{"@t":"2022-01-07T02:26:23.9635656Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":35}
{"@t":"2022-01-07T02:26:24.9812101Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":9}
{"@t":"2022-01-07T02:26:25.9952912Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":63}
{"@t":"2022-01-07T02:26:26.9956998Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":9}
{"@t":"2022-01-07T02:26:28.0104629Z","@m":"Unknown sensor","@i":"ab184f9e","@l":"Error","threadId":18}

Hi! Thanks for creating an issue. Could you post the contents of your configured-sensors.json? You can find it by using the "Config files" button in the UI. Sounds like something strange is in there.

see below
[{"Type":"ActiveWindowSensor","Id":"f3325dd5-5299-4bcd-a4f4-5a99f0290057","Name":"ActiveWindow","Query":null,"UpdateInterval":5,"WindowName":null},{"Type":"LastActiveSensor","Id":"11b56fe6-75e1-4c64-a686-fb6beb1431b1","Name":"LastActive","Query":null,"UpdateInterval":15,"WindowName":null},{"Type":"WMIQuerySensor","Id":"c0331e55-5809-4d4d-8698-2a65d0ec055d","Name":"WMIQuerySensor","Query":"Select * from Win32_Process Where Name = \u0027nbminer.exe\u0027","UpdateInterval":10,"WindowName":null},{"Type":"GpuTemperatureSensor","Id":"8d3323f5-9e6e-4bff-ab79-73f36fab87c1","Name":"GPUTemperature","Query":null,"UpdateInterval":10,"WindowName":null},{"Type":"WMIQuerySensor","Id":"db7e1d47-3d11-4d7e-979a-4509ce494e03","Name":"controllersensor","Query":"SELECT Present FROM Win32_PnPEntity WHERE Name=\u0027HID-compliant game controller\u0027","UpdateInterval":15,"WindowName":null}]

I'm also getting this. And it seems like one or more of the sensors stops updating in HA at the same time.

Having the same issue, here is my log configured-sensors.json
[{"Type":"SessionStateSensor","Id":"8cfa6db9-428d-4444-9133-1c9f138d3a60","Name":"Session state","Query":null,"Scope":null,"UpdateInterval":5,"WindowName":null},{"Type":"CPULoadSensor","Id":"c1f4b72c-08d7-4a47-a5bd-6484c4bf7e92","Name":"CPU load","Query":"SELECT PercentProcessorTime FROM Win32_PerfFormattedData_PerfOS_Processor","Scope":"","UpdateInterval":5,"WindowName":null},{"Type":"GpuLoadSensor","Id":"1129031d-7eab-4b63-8643-b0567b1d0f99","Name":"GPU load","Query":null,"Scope":null,"UpdateInterval":5,"WindowName":null},{"Type":"GpuTemperatureSensor","Id":"7b905028-891b-451f-a48f-dc55291a1dd7","Name":"GPU temperature","Query":null,"Scope":null,"UpdateInterval":5,"WindowName":null},{"Type":"MemoryUsageSensor","Id":"d9907ffc-3e77-4234-b0c8-fcbd38e3f6fd","Name":"RAM usage","Query":"SELECT FreePhysicalMemory,TotalVisibleMemorySize FROM Win32_OperatingSystem","Scope":"","UpdateInterval":10,"WindowName":null},{"Type":"NamedWindowSensor","Id":"71ff6bc3-a706-4db6-8ead-d79b3135a64a","Name":"Forza","Query":null,"Scope":null,"UpdateInterval":5,"WindowName":"forza"}]


⚠ Bofrost.at has degraded performance

In 9f15e16, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 883 ms

Resolved: Bofrost.at performance has improved in 9a37757.


Added possibility of setting PLATFORM manually.

Hey,
I just cloned the repo and fired make which ended up with:
$ make
gcc -D_GNU_SOURCE -DDEFAULT -c src/ssmem.c -O3 -Wall -I./include
Archive name = libssmem.a
ar -r libssmem.a ssmem.o
rm -f *.o
gcc -D_GNU_SOURCE -DDEFAULT -c src/ssmem_test.c -O3 -Wall -I./include
In file included from src/ssmem_test.c:57:0:
./include/utils.h: In function ‘get_cluster’:
./include/utils.h:296:22: error: ‘CORES_PER_SOCKET’ undeclared (first use in this function)
     return thread_id/CORES_PER_SOCKET;
                      ^
./include/utils.h:296:22: note: each undeclared identifier is reported only once for each function it appears in
src/ssmem_test.c: In function ‘test’:
src/ssmem_test.c:190:11: error: ‘the_cores’ undeclared (first use in this function)
   set_cpu(the_cores[ID]);
           ^
src/ssmem_test.c: In function ‘main’:
src/ssmem_test.c:289:11: error: ‘the_cores’ undeclared (first use in this function)
   set_cpu(the_cores[0]);
           ^
Makefile:96: recipe for target 'ssmem_test.o' failed
make: *** [ssmem_test.o] Error 1

After looking at utils.h file I realized, that my platform (COREi7) hasn't been properly detected - instead DEFAULT platform was loaded, but there are no defines for it in utils.h.
So I've added code to change platform manually.
In the end you should probably detect the platform somehow else, e.g. by parsing lscpu | grep "Model name" output.

I actually removed set_cpu() from ssmem_test and removed the corresponding platform definitions. Both the library and the test should compile now without any changes in the Makefile. Pinning threads to cores does not add something to this test. Thanks for pointing out the compilation issue.


(BUG) Adalight with Arduino and Rpi2 is eating up memory

On Rpi2 openelec i have installed hyperion. Everything is working but the hyperion is constantly eating up the memory so long until kodi crashes. If i kill hyperiond the memory stops falling. I have a sample file if needed to test this. Maybee this is a bug with usb or. something since I do not use gpio pins but am using adalight with arduino.
My config is beginning with:
// Automatically generated configuration file for 'Hyperion daemon'
// Generated by: HyperCon (The Hyperion deamon configuration file builder
{
/// Device configuration contains the following fields:
/// * 'name'       : The user friendly name of the device (only used for display purposes)
/// * 'type'       : The type of the device or leds (known types for now are 'ws2801', 'ldp8806',
///                  'lpd6803', 'sedu', 'adalight', 'lightpack', 'test' and 'none')
/// * 'output'     : The output specification depends on selected device. This can for example be the
///                  device specifier, device serial number, or the output file name
/// * 'rate'       : The baudrate of the output to the device
/// * 'colorOrder' : The order of the color bytes ('rgb', 'rbg', 'bgr', etc.).
"device" :
{
"name"       : "MyPi",
"type"       : "adalight",
///	"output"     : "/dev/ttyUSB_FTDI",
"output"     : "/dev/ttyACM0",
///	"output"     : "/dev/ttyUSB0",
"rate"       : 115200,
"colorOrder" : "rgb"
},
/// Color manipulation configuration used to tune the output colors to specific surroundings.
/// The configuration contains a list of color-transforms. Each transform contains the

After doing some further observation I have seen that this happens on every video in Kodi if you use as video player OMX player.
If you start hyperion with the config above then the memory is constant 'leaking'. I think the problem is ACM0.

Another note:
If you stop and start kodi again the memory gets free again.
OpenELEC:~ # systemctl stop kodi
OpenELEC:~ # systemctl start kodi
After further looking into this I saw that if I remove the addon from rpi script.service.hyperion then memory stops leaking even if in background hyperiond is running but then the lights are not working.
1.So i think in  addon script.service.hyperion there is the problem that is constant using memory.
2. Is there any other way to run hyperion on Rpi2 with external controller (like arduino) and adalight?


SparkSetupMainController failing due to missing bundle

When I try to create an instance of SparkSetupMainController the following line throws an exception:
NSBundle *bundle = [NSBundle bundleWithURL:[[NSBundle mainBundle] URLForResource:@"SparkSetup" withExtension:@"bundle"]];
The exception seems to indicate that the bundle is nil.
` -[NSBundle initWithURL:]: nil URL argument"``
I am using Cocoapods to load the Spark-Setup dependency. I have tried using the latest released cocoapod (0.3.2) and the head of master and have the same problem with both.

Strange.
Can you take a look at this example project:
https://github.com/spark/spark-setup-ios-example
as a reference on how to use the SparkSetup lib - maybe you've done something wrong.
let me know if that works for you

The example project works (although I had to replace all the println calls with print to compile it with xcode7).
I've been comparing the items in the Build Phases between my project and the example and I noticed that the example project contains a bunch of items under the 'Copy Bundle Resources' section including fonts and the main storyboard. When I look at my project I don't have any of the same items listed in that section, except for a LaunchScreen.xib. I have other images and things that I added to my project.
Do you know how those items got added to that build phase? I would assume that it's supposed to be taken care of by Cocoapods. Do you know what would cause the the resources to not be added for me?
One other question. I have been trying to use Carthage more and more for dependencies. Do you know  if the SparkSetup library can be built as a framework and imported using Carthage instead of Cocoapods?

Oh by the way, I also had to change the angle brackets around the header files to quotes, in SparkSetup.h, in order to compile my project. Not sure if that is also telling of a setup problem...

Yea, project needs updating to Swift 2.1/iOS9.1/Xcode 7.1 - shouldn't be a big issue (XCode got 'convert to modern swift' auto refactoring option)

I am not sure about the copy bundle resources issue - what I'd recommend is removing 'SparkSetup' and/or 'Spark-SDK' from PODFILE running pod install and then re-adding it and running pod install again - I found that it solves those kind of issues usually. Be sure you have the latest cocoapods version (gem install cocoapods)

Carthage - I want to look into that, It is certainly in my backlog, I am sure Cloud SDK can be compiled as a framework, device setup should too (but might be more tricky because of the resources).
Feel free to try it out yourself and send a PR if you manage to get it done. I think it shouldn't be too complicated. It'll be awesome to have Carthage support.

Brackets vs quotes - that's weird. Did you configure the bridging headers correctly? Is your project swift/Obj-C?

I've been running into the same issue but have fixed it for myself. One of the problems is that in my Swift project, I've turned on CocoaPods use_frameworks! to enable the use of some external Swift libraries. Because of this, the bundle isn't properly located (see the announcement for CocoaPods 0.36 where this change was made: http://blog.cocoapods.org/CocoaPods-0.36/)
I'll have to verify that this is the change that fixed the problem (I've messed with the setup code a bit now trying to get it to work), but you can change [NSBundle mainBundle]  to [NSBundle bundleForClass: [self class]] and ensure that the "Copy Bundle Resources" Build Phase of the SparkSetup framework includes SparkSetup.bundle so that the actual bundle is found.

Just wanted to say I discovered this same thing earlier tonight. I removed use_frameworks! from my Podfile and that fixed the issue. Mine is also a swift/obj-c project but I'm actually not using Cocoapods to pull in any frameworks (I'm using Carthage for that) so it looks like I don't need the use_frameworks! flag.
I am glad to hear you fixed this though. Thanks!

PR merged, thanks!

Is there a demo of this working?
I can get my project to build and go on a device, but I cannot successfully create an archive with use_frameworks!.


Implement Sticky Navbar

Description:
Currently, the navbar in the project does not stick when users scroll, making it challenging to access certain functionalities such as changing color modes or downloading stylesheets. To improve the user experience, we need to implement a sticky navbar that remains fixed at the top of the page even during scrolling.
Expected Solution:
To address this issue, we need to add the functionality for the navbar to become sticky on scroll. This will allow users to access the navbar and its associated functionalities at all times, regardless of their position on the page.
@blackmann

@Nunyaklah please go ahead


Create snapshot in pFDA

Background
We need to create a snapshot inside pFDA.
Approach
Since there seem to be 2 major workflows (cpu & gpu), I think we will create 2 snapshots. These will need to have the following dependencies:

git
docker

Prequisites

[x] Access to pFDA
[ ] Access to pFDA workstations
[x] #6

The app has been converted to a Workstation


Homeassistant seems to work after 0.46 upgrade, but zwave times out

HASS.io latest version, host 0.8, supervisor 0.36,  on Raspberry Pi 3
Description of problem:
Everything in Home assistant seems to work as before the upgrade from 0.45 to 0.46, but the 2 zwave switches I currently use don't respond anymore and seem to time out. Have rebooted a few times, but error is consistent.
This is from the Home-assistant.log
2017-06-07 18:11:44 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "uvloop/future.pyx", line 374, in uvloop.loop.BaseTask._fast_step (uvloop/loop.c:112704)
File "/usr/lib/python3.5/site-packages/homeassistant/components/discovery.py", line 118, in scan_devices
results = yield from hass.async_add_job(_discover, netdisco)
File "uvloop/future.pyx", line 230, in iter (uvloop/loop.c:110600)
File "uvloop/future.pyx", line 432, in uvloop.loop.BaseTask._fast_wakeup (uvloop/loop.c:113980)
File "uvloop/future.pyx", line 101, in uvloop.loop.BaseFuture._result_impl (uvloop/loop.c:108900)
File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.5/site-packages/homeassistant/components/discovery.py", line 144, in _discover
netdisco.scan()
File "/usr/lib/python3.5/site-packages/netdisco/discovery.py", line 69, in scan
self.daikin.scan()
File "/usr/lib/python3.5/site-packages/netdisco/daikin.py", line 32, in scan
self.update()
File "/usr/lib/python3.5/site-packages/netdisco/daikin.py", line 50, in update
sock.sendto(DISCOVERY_MSG, (DISCOVERY_ADDRESS, UDP_DST_PORT))
OSError: [Errno 101] Network unreachable
2017-06-07 18:39:01 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
and these a few lines from OZW.log:
2017-06-07 18:37:20.771 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2017-06-07 18:37:20.772 Info, Node003, SwitchBinary::Set - Setting node 3 to On
2017-06-07 18:37:20.772 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0x27, 0x3f
2017-06-07 18:37:20.772 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x28, 0xce
2017-06-07 18:37:20.772 Detail,
2017-06-07 18:37:20.772 Info, Node003, Sending (Send) message (Callback ID=0x27, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0x27, 0x3f
2017-06-07 18:37:21.773 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-06-07 18:37:21.773 Detail, Node003, Removing current message
2017-06-07 18:37:21.773 Detail, Node003, Notification: Notification - TimeOut
2017-06-07 18:37:21.778 Detail,

Today I got it working again. I have two 'identical' Neo Coolcam switches and after giving one of them a friendly name the zwave switches started responding again. I don't understand why that is, but I changed one of the names because both had the same name in the dashboard and it confused me and I couldn't see which of the 2 I was operating. Could the fact that both had the same (system assigned ) name have confused Home Assistant?

Unfortunately, the system only worked for a few hours and then back to the same problem again, time out on my Zwave switches. Here is the latest OZW log:
2017-06-10 13:12:36.255 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2017-06-10 13:12:36.256 Info, Node003, SwitchBinary::Set - Setting node 3 to On
2017-06-10 13:12:36.256 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0x2b, 0x33
2017-06-10 13:12:36.256 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x2c, 0xca
2017-06-10 13:12:36.256 Detail,
2017-06-10 13:12:36.256 Info, Node003, Sending (Send) message (Callback ID=0x2b, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0x2b, 0x33
2017-06-10 13:12:37.257 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-06-10 13:12:37.257 Detail, Node003, Removing current message
2017-06-10 13:12:37.257 Detail, Node003, Notification: Notification - TimeOut
2017-06-10 13:12:37.262 Detail,
2017-06-10 13:12:37.262 Info, Node003, Sending (Send) message (Callback ID=0x2c, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x2c, 0xca
2017-06-10 13:12:38.262 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-06-10 13:12:38.262 Detail, Node003, Removing current message
2017-06-10 13:12:38.262 Detail, Node003, Notification: Notification - TimeOut

Today I changed the switch zwave setting to polling every time. Reboot and the switch worked! However, after a little while (1 hour or so) the switch didn't respond again. A pattern is starting to emerge where the switch works after a reboot, but then stops after a little while. I am completely baffled.

Today I decided to make a completely new start, took a new SD card, started with a fresh HASS.io image, rebooted a few times until I could see all zwave devices (to which I added a Fibaro switch just to make sure it had nothing to do with the Neo Coolcam switches) and it worked. For a little while.......
Same issue still, zwave times out again!

Please post the attributes of the zwave entity that does not work.

Hi, thanks for your response. Not sure what attributes you are looking for, I'll copy all attributes for the 2 Neo coolcam switches that I see in the entities page. Please let me know if this is not what you need and where I can find the info you are looking for.
Entity	State	Attributes
group.all_switches	off	order: 1
auto: true
entity_id: switch.fibaro_system_fgs212_switch_3kw_switch_5_0,switch.fibaro_system_fgs212_switch_3kw_switch_5_0_3,switch.fibaro_system_fgs212_switch_3kw_switch_5_0_2,switch.neo_coolcam_power_plug_12a_switch_3_0,switch.neo_coolcam_power_plug_12a_switch_4_0
hidden: true
friendly_name: all switches
sensor.neo_coolcam_power_plug_12a_alarm_level_3_1	0	friendly_name: Neo CoolCam Power plug 12A Alarm Level
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_alarm_level_4_1	0	friendly_name: Neo CoolCam Power plug 12A Alarm Level
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_alarm_type_3_0	0	friendly_name: Neo CoolCam Power plug 12A Alarm Type
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_alarm_type_4_0	0	friendly_name: Neo CoolCam Power plug 12A Alarm Type
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_current_3_20	0.0	friendly_name: Neo CoolCam Power plug 12A Current
unit_of_measurement: A
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_current_4_20	0.0	friendly_name: Neo CoolCam Power plug 12A Current
unit_of_measurement: A
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_energy_3_0	0.1	friendly_name: Neo CoolCam Power plug 12A Energy
unit_of_measurement: kWh
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_energy_4_0	0.0	friendly_name: Neo CoolCam Power plug 12A Energy
unit_of_measurement: kWh
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_exporting_3_32	False	friendly_name: Neo CoolCam Power plug 12A Exporting
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_exporting_4_32	False	friendly_name: Neo CoolCam Power plug 12A Exporting
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_interval_3_10	301	friendly_name: Neo CoolCam Power plug 12A Interval
unit_of_measurement: seconds
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_interval_3_18	301	friendly_name: Neo CoolCam Power plug 12A Interval
unit_of_measurement: seconds
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_interval_3_2	301	friendly_name: Neo CoolCam Power plug 12A Interval
unit_of_measurement: seconds
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_interval_3_22	301	friendly_name: Neo CoolCam Power plug 12A Interval
unit_of_measurement: seconds
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_interval_4_10	301	friendly_name: Neo CoolCam Power plug 12A Interval
unit_of_measurement: seconds
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_interval_4_18	301	friendly_name: Neo CoolCam Power plug 12A Interval
unit_of_measurement: seconds
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_interval_4_2	301	friendly_name: Neo CoolCam Power plug 12A Interval
unit_of_measurement: seconds
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_interval_4_22	301	friendly_name: Neo CoolCam Power plug 12A Interval
unit_of_measurement: seconds
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_power_3_8	0.0	friendly_name: Neo CoolCam Power plug 12A Power
unit_of_measurement: W
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_power_4_8	0.0	friendly_name: Neo CoolCam Power plug 12A Power
unit_of_measurement: W
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_power_management_3_11	254	friendly_name: Neo CoolCam Power plug 12A Power Management
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_power_management_4_11	254	friendly_name: Neo CoolCam Power plug 12A Power Management
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_previous_reading_3_1	0.1	friendly_name: Neo CoolCam Power plug 12A Previous Reading
unit_of_measurement: kWh
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_previous_reading_3_17	237.99	friendly_name: Neo CoolCam Power plug 12A Previous Reading
unit_of_measurement: V
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_previous_reading_3_21	0.0	friendly_name: Neo CoolCam Power plug 12A Previous Reading
unit_of_measurement: A
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_previous_reading_3_9	0.0	friendly_name: Neo CoolCam Power plug 12A Previous Reading
unit_of_measurement: W
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_previous_reading_4_1	0.0	friendly_name: Neo CoolCam Power plug 12A Previous Reading
unit_of_measurement: kWh
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_previous_reading_4_17	234.44	friendly_name: Neo CoolCam Power plug 12A Previous Reading
unit_of_measurement: V
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_previous_reading_4_21	0.0	friendly_name: Neo CoolCam Power plug 12A Previous Reading
unit_of_measurement: A
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_previous_reading_4_9	0.0	friendly_name: Neo CoolCam Power plug 12A Previous Reading
unit_of_measurement: W
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_sourcenodeid_3_2	0	friendly_name: Neo CoolCam Power plug 12A SourceNodeId
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_sourcenodeid_4_2	0	friendly_name: Neo CoolCam Power plug 12A SourceNodeId
node_id: 4
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_voltage_3_16	237.63	friendly_name: Neo CoolCam Power plug 12A Voltage
unit_of_measurement: V
node_id: 3
power_consumption: 0
sensor.neo_coolcam_power_plug_12a_voltage_4_16	233.97	friendly_name: Neo CoolCam Power plug 12A Voltage
unit_of_measurement: V
node_id: 4
power_consumption: 0
switch.fibaro_system_fgs212_switch_3kw_switch_5_0	off	friendly_name: FIBARO System FGS212 Switch 3kW Switch
node_id: 5
switch.fibaro_system_fgs212_switch_3kw_switch_5_0_2	off	friendly_name: FIBARO System FGS212 Switch 3kW Switch
node_id: 5
switch.fibaro_system_fgs212_switch_3kw_switch_5_0_3	off	friendly_name: FIBARO System FGS212 Switch 3kW Switch
node_id: 5
switch.neo_coolcam_power_plug_12a_switch_3_0	off	friendly_name: GardenSwitch
node_id: 3
power_consumption: 0
switch.neo_coolcam_power_plug_12a_switch_4_0	off	friendly_name: Neo CoolCam Power plug 12A Switch
node_id: 4
power_consumption: 0

Ok, not those, the zwave.device_name entity attributes

Ok, these I believe?
zwave.__2	Sleeping (Probe)	is_info_received: false
is_zwave_plus: false
averageResponseRTT: 0
receivedUnsolicited: 0
receivedCnt: 0
max_baud_rate: 40000
is_ready: false
node_name:
manufacturer_name:
receivedTS: 2017-06-11 15:52:36:151
averageRequestRTT: 0
is_failed: false
receivedDups: 0
capabilities: beaming
lastResponseRTT: 0
sentTS: 2017-06-11 15:52:37:587
friendly_name:
product_name:
is_awake: false
sentFailed: 1
lastRequestRTT: 0
query_stage: Probe
node_id: 2
retries: 0
sentCnt: 1
zwave.aeotec_zw090_zstick_gen5_eu_1	Ready	is_info_received: true
is_zwave_plus: false
averageResponseRTT: 0
receivedUnsolicited: 0
receivedCnt: 0
max_baud_rate: 40000
query_stage: Complete
node_name: Aeotec ZW090 Z-Stick Gen5 EU
manufacturer_name: Aeotec
receivedTS: 2017-06-11 15:52:36:139
averageRequestRTT: 0
is_failed: false
receivedDups: 0
capabilities: beaming,primaryController,listening
neighbors: 3,4,5
lastResponseRTT: 0
sentTS: 2017-06-11 15:52:37:581
friendly_name: Aeotec ZW090 Z-Stick Gen5 EU
product_name: ZW090 Z-Stick Gen5 EU
is_awake: true
sentFailed: 0
lastRequestRTT: 0
is_ready: true
node_id: 1
retries: 0
sentCnt: 1
zwave.fibaro_system_fgs212_switch_3kw_5	Ready	is_info_received: true
is_zwave_plus: false
averageResponseRTT: 36
receivedUnsolicited: 1
receivedCnt: 14
max_baud_rate: 40000
query_stage: Complete
node_name: FIBARO System FGS212 Switch 3kW
manufacturer_name: FIBARO System
receivedTS: 2017-06-11 15:56:44:484
averageRequestRTT: 27
is_failed: false
receivedDups: 1
capabilities: routing,beaming,listening
neighbors: 1,3,4
lastResponseRTT: 37
sentTS: 2017-06-11 15:56:44:446
friendly_name: FIBARO System FGS212 Switch 3kW
product_name: FGS212 Switch 3kW
is_awake: true
sentFailed: 0
lastRequestRTT: 28
is_ready: true
node_id: 5
retries: 0
sentCnt: 24
zwave.neo_coolcam_power_plug_12a_3	Ready	is_info_received: true
is_zwave_plus: true
averageResponseRTT: 114
receivedUnsolicited: 872
receivedCnt: 890
max_baud_rate: 40000
query_stage: Complete
node_name: Neo CoolCam Power plug 12A
manufacturer_name: Neo CoolCam
receivedTS: 2017-06-11 18:41:25:201
averageRequestRTT: 34
is_failed: false
receivedDups: 59
capabilities: routing,beaming,listening
neighbors: 1,5
lastResponseRTT: 48
sentTS: 2017-06-11 22:02:09:708
friendly_name: Neo CoolCam Power plug 12A
product_name: Power plug 12A
is_awake: true
sentFailed: 0
lastRequestRTT: 38
is_ready: true
node_id: 3
retries: 0
sentCnt: 19
zwave.neo_coolcam_power_plug_12a_4	Ready	is_info_received: true
is_zwave_plus: true
averageResponseRTT: 50
receivedUnsolicited: 140
receivedCnt: 151
max_baud_rate: 40000
query_stage: Complete
node_name: Neo CoolCam Power plug 12A
manufacturer_name: Neo CoolCam
receivedTS: 2017-06-11 18:43:26:821
averageRequestRTT: 28
is_failed: false
receivedDups: 0
capabilities: routing,beaming,listening
neighbors: 1,5
lastResponseRTT: 55
sentTS: 2017-06-11 15:52:53:217
friendly_name: Neo CoolCam Power plug 12A
product_name: Power plug 12A
is_awake: true
sentFailed: 0
lastRequestRTT: 29
is_ready: true
node_id: 4
retries: 1
sentCnt: 16

Today I saw that updates of the Hass.io supervisor and Homeassistant were available. I first updated the supervisor to 0.37 and after that my zwave seems to work again.
Thanks a lot for your great work.

@turbokongen: Sorry, but I have to re-open this issue again. Although the system worked fine for a little while, deterioration started creeping back-in and currently my zwave devices will only work for a few hours after each reboot. I can't find any error messages. Just see that my zwave devices are timing out. The fact that the system worked fine after the update to the HASS.io Supervisor 0.37 makes me think the issue sits somewhere in the docker environment, with a memory leak or file size that's growing out of control?

OK, here is an update on what I have found to date: I have 2 Neo Coolcam power plugs in my Zwave network. In the standard configuration these power plugs send a report (voltage, power, current, status etc.) every 5 minutes. As this causes the home_assistant_v2.db to grow superfast I decided to disable the regular status report from these plugs. To my surprise this has resolved my Zwave becoming unresponsive issue and my system has been running continuously for a few days now.
When my Zwave was unresponsive (time out of the zwave communication) everything else seemed to continued working fine in Homeassistant, and my thinking is that the problem might lie in the communication with/through my AEON LABS Z-STICK Z-wave USB stick gen5. The USB stick on my Raspberry Pi 3 is on /dev/ttyAMC0. I would be happy to do further monitoring/logging if somebody can tell me what to do next to get to the bottom of this problem.

@turbokongen: A similar issue came up in the HA Configuration forum under the topic: Z Wave mesh stopping working.
Other users report very similar issues and I have the feeling that the problem is possibly induced by heavy data traffic in the zwave network. Perhaps the Pi3 USB buffer is not emptied quickly enough by HA? To throttle the data flow I lowered the USB baudrate a few days ago and my zwave hasn’t crashed (timed out)since. In the (Putty) terminal I give this command: stty -F /dev/ttyACM0 57600. Only problem is that this doesn’t ‘stick’, and I have to do this after every reboot.

Hey @RonaldvE  and @turbokongen I have similar issue. Setup is:

Hassio.io 0.50.2 on x86 system.
Zwave AeonLab Z Stick S2
Fibaro Wall Plug FGWPE/F-101
FIBARO MOTION SENSOR FGMS-001

After some time, communication between the z-wave devices doesn't work any more. I belive:
2017-08-06 13:30:14.059 Info, Node007, Sending (Send) message (Callback ID=0x3b, Expected Reply=0x04) - MeterCmd_Get (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x32, 0x01, 0x00, 0x25, 0x3b, 0xcf
2017-08-06 13:30:15.060 Error, Node007, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-06 13:30:15.060 Detail, Node007, Removing current message
2017-08-06 13:30:15.060 Detail, Node007, Notification: Notification - TimeOut

To be the relevant part of the log file. Restarting Hassio solves the issue for some hours. But it eventually comes back. Also excluding and including the devices from the z-wave network helps for a short period off time.

Here is a link to the forums post @RonaldvE talked about.
https://community.home-assistant.io/t/z-wave-mesh-stopping-working/21682/10

Just to add to this.  I had everything setup and working (and had been for months).  Then all of a sudden, I noticed that nothing was working.  All nodes are timing out, seeing this:
2017-08-23 21:46:45.176 Error, Node066, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-23 21:46:45.176 Detail, Node066, Removing current message
2017-08-23 21:46:45.176 Detail, Node066, Notification: Notification - TimeOut
2017-08-23 21:46:45.183 Detail,
2017-08-23 21:46:45.183 Info, Node067, Sending (NoOp) message (Callback ID=0x1d, Expected Reply=0x13) - NoOperation_Set (Node=67): 0x01, 0x09, 0x00, 0x13, 0x43, 0x02, 0x00, 0x00, 0x25, 0x1d, 0x9c

It's for all nodes.
I'm running everything off an Intel NUC, so I'm not sure that it's an issue with Rpi's
My setup is:
Home Assistant (Docker) 0.50.2 on x86 system.
Zwave AeonLab Z Stick G5

OK, glad to be able to report that the problem has been resolved. Turned out to be a power supply issue. Not the powersupply itself, but the USB cable feeding my Pi3! Replacing the cable solved the problem and zwave is rock solid now, no more time outs.

In my experience its best to power usb devices via a self powered usb hub. I use the hub below to power an rfxcom and the aeon labs z-stick.


(PoC Work) Deploy ASP.NET and have the hello world shown by it

Action Plan: ASP.NET Website with Static Files and API Backend
Overview:
The goal is to build a website using ASP.NET Core, serve static HTML and JavaScript files generated by Websim.ai, and handle backend actions using ASP.NET API endpoints. JavaScript will be used to call the APIs for any dynamic operations such as user authentication or data processing.

Steps:

Set up an ASP.NET Core website

Create a new ASP.NET Core project in Visual Studio (or preferred IDE).
Ensure that static file serving is enabled in Startup.cs:app.UseStaticFiles();

Generate frontend (HTML, CSS, JS) with Websim.ai

Use Websim.ai to generate the initial frontend content.
Save the generated static files (HTML, JS, CSS) into the wwwroot folder of the ASP.NET project.

Serve static files

ASP.NET Core will serve the static files from the wwwroot folder.
Ensure the site correctly serves these files when accessed via a browser (e.g., /index.html).

Create ASP.NET API for backend actions

Set up ASP.NET Core API controllers for handling backend logic (e.g., user registration, login, etc.).
Use Entity Framework Core or other methods for database interactions, if necessary.
Example API action for registration:[HttpPost("register")]
public IActionResult Register([FromBody] RegisterModel model)
{
    // Handle user registration
    // Return an appropriate response (e.g., success or error)
}

Call APIs from static HTML via JavaScript

Use Fetch API or AJAX in the generated HTML/JS to interact with the ASP.NET API endpoints.
Example JavaScript for calling the registration API:fetch('/api/auth/register', {
    method: 'POST',
    headers: {
        'Content-Type': 'application/json',
    },
    body: JSON.stringify({ username: 'test', password: 'password123' }),
}).then(response => response.json())
  .then(result => console.log(result));

Handle authentication and authorization

Implement user authentication (e.g., using JWT or Cookie Authentication).
Protect API endpoints with authorization attributes in the controllers.
Example of a protected API endpoint:[Authorize]
[HttpGet("user-data")]
public IActionResult GetUserData()
{
    return Ok(new { message = "Secure data" });
}

Manage frontend state via JavaScript

Use localStorage, sessionStorage, or cookies to store authentication tokens or session data.
Ensure secure token management for sensitive operations (e.g., login).

Summary:

Serve static content (HTML, JS, CSS) with ASP.NET Core.
Build API endpoints for backend functionality.
Use JavaScript in the static files to call the APIs.

1 done, continue with deployment and writing deployment instructions

done: deployment and writing deployment instructions

2 done: Generate frontend (HTML, CSS, JS) with Websim.ai

3 done: Serve static files

4 done, the rest seems simple enough


3.2.1 does not have entry in CHANGES.md

In the changelog file, there is no entry for the release of v3.2.1, even though there was a non-trivial change.

I'll be happy to accept a PR that explains the change if you'd like. Thanks :)


CNV-29082: Make "View alert" on Overview > Alerts card work

📝 Description
Fixes:
https://issues.redhat.com/browse/CNV-29082
Make clicking on View alert link to a specific alert work, accessible on Virtualization > Overview > Alerts card > Warnings.
How to reproduce a bug/test this PR:
You need to clone the monitoring repo: https://github.com/openshift/monitoring-plugin
Then you just need to add it as the plugin and run that together with this repo, so that Observe appears in the main menu in the UI. If you need help/more details, feel free to ask me.
🎥 Demo
Before:
https://github.com/kubevirt-ui/kubevirt-plugin/assets/13417815/71a86c22-caf4-4ce3-bd2d-45709ac97679
After:
https://github.com/kubevirt-ui/kubevirt-plugin/assets/13417815/dfc998a7-36a0-4f95-ac6c-c7286321295e

@avivtur @metalice @pcbailey @upalatucci @vojtechszocs please review

/lgtm

/cherry-pick release-4.13


Error posting activity to bot in web chat

Describe the bug
I am unable to test a bot on a Mac. I have tried C# and Node bots with and without LUIS capabilities, and even the base bot is unable to chat in the Web Chat window.
Version

Version:  2.1.2
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0

Browser

[x] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[x] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Create a new bot using the templates
Run the bot
Open web chat and send a message
Message fails with an internal server error:

[09:57:39 AM]POST201/v3/conversations
[09:57:39 AM]POST500/v3/directline/conversations/8d8197af-071a-4462-be5d-9700f0b63aec%7Clivechat/activities
An error occurred posting activity to the bot. Internal Server Error
[09:57:42 AM]POST500/v3/directline/conversations/8d8197af-071a-4462-be5d-9700f0b63aec%7Clivechat/activities
An error occurred posting activity to the bot. Internal Server Error
[09:59:30 AM]POST500/v3/directline/conversations/8d8197af-071a-4462-be5d-9700f0b63aec%7Clivechat/activities
An error occurred posting activity to the bot. Internal Server Error

Expected behavior

Be able to chat with a bot
Screenshots

Node bot without language:

Node bot with language:

Additional context

I have confirmed that the same bot works on Windows (using the same Git repo).

Hi @rschuetzler,
Are you using MacOS Monterey? A change was made in that version of the OS that claimed port 5000 for a Mac feature, which in turn caused this bug in Composer. A fix was made and rolled out in a nightly release, but I'm not sure if that's made it to stable yet.
You could try enabling preview versions of Composer in the interim. Otherwise, the Windows and Linux versions should also work fine.

That was the issue, and the pre-release fixed it. Thank you!


Error when navigating back to a tab that has been closed

Navigate away from a tab
Close that tab
navigation-history:back

Atom Version: 1.4.3
System: Mac OS X 10.10.5
Thrown From: navigation-history package, v0.1.8
Stack Trace
Uncaught Error: Adding a pane item with URI '/[...]/app/helpers/base_crud_helper.rb' that has already been destroyed
At /Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:331

Error: Adding a pane item with URI '/[...]/app/helpers/base_crud_helper.rb' that has already been destroyed
    at Pane.module.exports.Pane.addItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:331:15)
    at Pane.module.exports.Pane.activateItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:315:14)
    at Object.module.exports.jumpTo (/[...]/.atom/packages/navigation-history/lib/main.coffee:42:23)
    at Object.module.exports.jumpBack (/[...]/.atom/packages/navigation-history/lib/main.coffee:29:6)
    at atom-text-editor.disposables.add.atom.commands.add.navigation-history:back (/[...]/.atom/packages/navigation-history/lib/main.coffee:18:38)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:536:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:359:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands
     -0:49.3.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:48.2.0 core:save (atom-text-editor.editor.is-focused)
  2x -0:46.2.0 navigation-history:back (atom-text-editor.editor.is-focused)
     -0:34.2.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -0:34.2.0 core:cancel (atom-text-editor.editor.is-focused)
  3x -0:33 navigation-history:forward (atom-text-editor.editor.is-focused)
  2x -0:30.4.0 navigation-history:back (atom-text-editor.editor.is-focused)
     -0:27.7.0 navigation-history:forward (atom-text-editor.editor.is-focused)
     -0:26.5.0 core:move-to-bottom (atom-text-editor.editor.is-focused)
  2x -0:25.9.0 navigation-history:back (atom-text-editor.editor.is-focused)
  3x -0:24.2.0 navigation-history:forward (atom-text-editor.editor.is-focused)
  2x -0:22.8.0 navigation-history:back (atom-text-editor.editor.is-focused)
     -0:21.9.0 navigation-history:forward (atom-text-editor.editor.is-focused)
  2x -0:21.6.0 navigation-history:back (atom-text-editor.editor.is-focused)
     -0:20.5.0 navigation-history:forward (atom-text-editor.editor.is-focused)
  5x -0:20.1.0 navigation-history:back (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "seti-icons",
      "linter-rails-best-practices"
    ],
    "themes": [
      "one-dark-ui",
      "twilight-syntax"
    ]
  },
  "navigation-history": {}
}

Installed Packages
# User
autoclose-html, v0.20.0
browser-plus, v0.0.54
emmet, v2.4.1
file-icons, v1.6.14
language-slim, v0.5.0
linter, v1.11.3
linter-bootlint, v1.0.0
linter-csslint, v1.2.0
linter-erb, v1.0.2
linter-htmlhint, v1.0.2
linter-ruby, v1.2.1
linter-slim, v1.0.0
navigation-history, v0.1.8
open-recent, v5.0.0
recent-files-fuzzy-finder, v0.2.4
remote-edit, v1.8.24
symbol-gen, v1.0.0
twilight-syntax, v0.7.0

# Dev
No dev packages

In my case such problem disappear when I uninstalled emmet package. I don't know why?

Duplicate of https://github.com/Tyriar/navigation-history/issues/7


Vision: Repository reorganization

Repo structure

Break down frame_support and sp_runtime into smaller pieces
Create a new folder called pallets that sits next to frame and move all pallets into it. frame folder should only contain non pallets

Semver and publishing to crates.io

Register/reserve crate names. In case they are taken, we should try to get them
In this order of priority we should semver and move to crates.io

frame
primitives
pallets

Semver and publishing to crates.io

You know that this is already being worked on?

Register/reserve crate names. In case they are taken, we should try to get them

And this was also already done?

The reason for this issue is to have a hub of the work being done, unless there is another one that I haven't found.

Semver and publishing to crates.io

You know that this is already being worked on?

I know that there are some efforts on that direction, but I am not fully aware of the status or how to follow it.

Register/reserve crate names. In case they are taken, we should try to get them

And this was also already done?

No, I didn't know. We can mark this as done then.

I know that there are some efforts on that direction, but I am not fully aware of the status or how to follow it.

https://github.com/paritytech/parity-publish


CLI Tool

add an example tool for the shell

@zellyn  it seems that there are many new PRs, can you spend time to take a look? Thx!

@roberChen I have mixed feelings about a lot of the other PRs that introduce a million browsers I've never heard of, and can't test ¯\_(ツ)_/¯


BREAKING CHANGE: update to eye v11.1.0\n\nBREAKING CHANGE: This update includes breaking changes to eye.

BREAKING CHANGE: update to eye v11.1.0\n\nBREAKING CHANGE: This update includes breaking changes to eye.

:tada: This PR is included in version 18.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v18.0.0

Your semantic-release bot :package::rocket:


Error with buildOptimizer - Object prototype may only be an Object or null: undefined

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

Computer-2016:ng2-stompjs-angular7 kdeepak$ node --version
v10.0.0
Computer-2016:ng2-stompjs-angular7 kdeepak$ npm --version
6.4.1
Computer-2016:ng2-stompjs-angular7 kdeepak$ ng --version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 7.0.4
Node: 10.0.0
OS: darwin x64
Angular: 7.0.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.10.4
@angular-devkit/build-angular     0.10.4
@angular-devkit/build-optimizer   0.10.4
@angular-devkit/build-webpack     0.10.4
@angular-devkit/core              7.0.4
@angular-devkit/schematics        7.0.4
@angular/cli                      7.0.4
@ngtools/webpack                  7.0.4
@schematics/angular               7.0.4
@schematics/update                0.10.4
rxjs                              6.3.3
typescript                        3.1.6
webpack                           4.19.1

OS Details: Mac OS X Yosemite 10.10.5

Repro steps

I am trying to use<EMAIL_ADDRESS>in a fresh Angular 7 project.
A minimal code is at https://github.com/stomp-js/ng2-stompjs-angular7
Steps to create this application at https://stomp-js.github.io/guide/ng2-stompjs/2018/11/04/ng2-stomp-with-angular7.html (quite verbose, as it is targeted to new users).
This application works correctly in non-prod mode and fails in ng serve --prod with an error
in browser console.
Setting "buildOptimizer": false in angular.json bypasses the issue.
The log given by the failure

main.bc446c9c469d7dfebf1f.js:formatted:13561 Uncaught TypeError: Object prototype may only be an Object or null: undefined
at setPrototypeOf ()
at o (main.bc446c9c469d7dfebf1f.js:formatted:13561)
at main.bc446c9c469d7dfebf1f.js:formatted:20679
at Module.zUnb (main.bc446c9c469d7dfebf1f.js:formatted:20681)
at f (runtime.ec2944dd8b20ec099bf3.js:1)
at Object.0 (main.bc446c9c469d7dfebf1f.js:formatted:274)
at f (runtime.ec2944dd8b20ec099bf3.js:1)
at t (runtime.ec2944dd8b20ec099bf3.js:1)
at Array.r [as push] (runtime.ec2944dd8b20ec099bf3.js:1)
at main.bc446c9c469d7dfebf1f.js:formatted:1
Screen shots from formatted code (in Chrome):

Desired functionality

I expected that if code works without buildOptimizer it should work with it.
Mention any other details that might be useful

sample repo at https://github.com/stomp-js/ng2-stompjs-angular7
steps to create this application at https://stomp-js.github.io/guide/ng2-stompjs/2018/11/04/ng2-stomp-with-angular7.html
https://github.com/stomp-js/ng2-stompjs/ (branch v7) that generated<EMAIL_ADDRESS>link to original issue https://github.com/stomp-js/ng2-stompjs/issues/103

Many thanks for getting back. I had figured out that if the underlying library entry point was shifted from modules to WebPack packaged single file - this issue was by passed. I had since moved all underlying library usage accordingly. That is the reason the issue is no longer reproducible.
Many thanks for you hard work, it is really appreciated.


Runelite creates windows folders in my home folder on Linux

Question
Answer

Java Version
openjdk version "1.8.0_172"

Operating System
Arch Linux btw

Runelite creates 2 folders in my $HOME dir:

$HOME/"C:"
$HOME/"C:\Users\Adam"

In the "C:\Users\Adam" folder, there is a .runelite folder, which has a logs dir.
This folder has a launcher.log, which just contains some update logs.

Update your launcher to latest version.

But my name is not Adam :thinking:

Yeah, this was known issue that was already resolved, but, you need to manually update the launcher.

Ah okay, thanks!


Create draft vaccination records in browser session

This updates how vaccination recording and editing is build to use the new DraftVaccinationRecord class instead of storing draft records in the database. This implements the behaviour in the prototype where users can make numerous changes before committing the changes.
This will also result in there being no more draft records in the database so a follow up change will be made to remove them.
See individual commits for more details.

I hit an exception when i was recording a new vaccination and hit Edit on the vaccine row of Check and confirm:

I hit an exception when i was recording a new vaccination and hit Edit on the vaccine row of Check and confirm:

Ah looks like we're missing test coverage for that, I'll add one now.


Fix saving preferences

A recent bug was introduced where the preferences were not being saved if Return or "ok" was clicked in the preferences dialog.  This PR fixes so that preferences are saved if Return or "ok" are clicked.  The escape function still works to cancel any changes made in the dialog.

Thanks Pam LGTM!


Does cilium support kata?

question
I read the article about eBPF, it can be used to reduce the memory cost by replace pod sidecar with cilium.
But it looks like the implementation needs the container share kernel with eBPF.
So for the runtime which as own kernel, does it work?

@pchaigno is that means Cilium can works with Kata without the eBPF ?

You can't run Cilium without eBPF. But at this point most OSes have the minimum eBPF features required for Cilium (Linux v4.9+).


OADP-1057: CloudStorageLocation Prefix/CACert support

Related to https://github.com/openshift/openshift-velero-plugin/pull/199
In order to avoid conflict with velero expected folders, new validations has been added.
Change Summary

bl.CloudStorage now support Prefix/CACert fields
New validation errors when Prefix is not specified and backupImages is not false.BackupLocation must have velero prefix when backupImages is not set to false

BackupLocation must have cloud storage prefix when backupImages is not set to false

Convert BSL/VSL validation reconciler into a function called from ValidateDataProtectionCR function

Testing instructions
Prerequisites:

https://mobb.ninja/docs/misc/oadp/rosa-sts/

Substitute operator install steps in prerequiste for the following operator-sdk run command.
To try this patch, get operator-sdk and run
export OADP_TEST_NS=openshift-adp
(oc create namespace $OADP_TEST_NS || true) && \
operator-sdk run bundle ghcr.io/kaovilai/oadp-operator:csl-prefix-bundle --namespace $OADP_TEST_NS

cleanup
operator-sdk cleanup oadp-operator --namespace $OADP_TEST_NS

After cleanup, you will have to create dpa again.
Example DPA
cat << EOF | oc create -f -
apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
  name: ${CLUSTER_NAME}-dpa
  namespace: openshift-adp
spec:
  features:
    dataMover:
      enable: false
  backupLocations:
  - bucket:
      cloudStorageRef:
        name: ${CLUSTER_NAME}-oadp
      credential:
        key: credentials
        name: cloud-credentials
      default: true
      prefix: velero # added capability in oadp-operator#1126 PR
      config:
        region: ${REGION}
  configuration:
    velero:
      defaultPlugins:
      - openshift
      - aws
      - csi
    restic:
      enable: false
  unsupportedOverrides:
    openshiftPluginImageFqin: ghcr.io/kaovilai/openshift-velero-plugin:sts
EOF

dev notes
bundle build command
IMG=ghcr.io/kaovilai/oadp-operator:csl-prefix-support-operator BUNDLE_IMG=ghcr.io/kaovilai/oadp-operator:csl-prefix-bundle make docker-build docker-push bundle bundle-build bundle-push

validated working :D

/retest

/retest

/retest

/retest

/retest

/retest

/hold
for https://github.com/openshift/openshift-velero-plugin/pull/199 to merge first

/unhold

/lgtm

/cherry-pick oadp-1.2


Add offset guessing for UDP on IPv6 "unconnected" sends.

What does this PR do?
Similar to #6307 but for IPv6 UDP sends, this adds the ability to extract addresses and ports for UDP sends that are "unconnected" (meaning they haven't received a reply yet).
Motivation
Improving IPv6 and UDP coverage of network tracer.
Additional Notes
The 7th and later arguments to a function on x86_64 are stored on the stack, which is why the macro for PT_REGS_PARM7 is so complicated. See https://eli.thegreenplace.net/2011/09/06/stack-frame-layout-on-x86-64 for more information.
I was unable to use a public IPv6 destination address for offset guessing because the agent dev VM does not have a default IPv6 route. This is likely a common setup, so I worked around it by using link-local and multicast addresses.
Describe your test plan
Added test comparable to IPv4 version. It passes in the agent VM.

Moving to DRAFT. This is complicated by the fact that the flowi6 parameter shifts from the 9th argument to the 7th at kernel 4.7. This is easily handled by runtime compilation, but not prebuilt binaries.

Moving to DRAFT. This is complicated by the fact that the flowi6 parameter shifts from the 9th argument to the 7th at kernel 4.7. This is easily handled by runtime compilation, but not prebuilt binaries.

Found a solution for both prebuilt and runtime compiled versions.


Transitional Background images

The TCEI StoryMap project (https://storymaps.arcgis.com/stories/a4e825956b4a402ebe13dbceeba66321, reach out for credentials) demonstrates a nice animation between slides. Each slide has a full image background, and then does a fancy transition to the next slide and its background image.
This issue is to support full background images for slides or panels, and to adopt a slick transition animation when moving between two slides.

Consideration: Multiple slides using the same image should not have any transition effect.


Add 'Cancel' button (or any custom button)

Is it possible to add an extra button? I need a 'cancel' button that will do Coloris.close(true);

Read the documentation closing-the-color-picker

You just need to set the closeButton option to true to display the close button. And if you want it to say "Cancel" instead of "Close" then change it with the closeLabel option.

You just need to set the closeButton option to true to display the close button. And if you want it to say "Cancel" instead of "Close" then change it with the closeLabel option.

But I want all three buttons at the same time - reset, cancel, close, is it possible?

It is not possible to have all three buttons out of the box, but you can add it yourself with a little Javascript and CSS. Try this:
Coloris.ready(() => {
  const picker = document.getElementById('clr-picker');
  const button = document.createElement('button');

  picker.appendChild(button);
  button.setAttribute('type', 'button');
  button.classList.add('clr-custom-reset');
  button.textContent = 'Reset';
  button.addEventListener('click', () => {
    Coloris.close(true);
  });
});

And to style the new button:
.clr-custom-reset {
  order: 2;
  height: 24px;
  margin: 0 20px 20px 0;
  padding: 0 20px;
  border: 0;
  border-radius: 12px;
  color: #fff;
  background-color: #666;
  font-family: inherit;
  font-size: 12px;
  font-weight: 400;
  cursor: pointer;
}

Thanks! This is exactly what I wanted.

If you want to add content over the color area, you will have to call Coloris.updatePosition() after.


zalohuj.si

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a new site support request
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that none of provided URLs violate any copyrights or contain any DRM to the best of my knowledge
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and am willing to share it if required

Region
No response
Example URLs
Single item: https://zalohuj.si/public-file/38d7ea4e1379d/
Provide a description that is worded well enough to be understood
A free download site that may have one of the largest video database in Czech republic.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://zalohuj.si/public-file/38d7ea4e1379d/']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [0b6f829b1] (zip)
[debug] Python 3.9.2 (CPython x86_64 64bit) - Linux-5.10.0-26-amd64-x86_64-with-glibc2.31 (OpenSSL 1.1.1w  11 Sep 2023, glibc 2.31)
[debug] exe versions: ffmpeg 4.3.6-0, ffprobe 4.3.6-0
[debug] Optional libraries: Cryptodome-3.9.7, certifi-2020.12.05, pyxattr-0.7.2, requests-2.25.1, secretstorage-3.3.1, sqlite3-3.34.1, urllib3-1.26.5
[debug] Proxy map: {}
[debug] Request Handlers: urllib
[debug] Loaded 1792 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds)
[generic] Extracting URL: https://zalohuj.si/public-file/38d7ea4e1379d/
[generic] 38d7ea4e1379d: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] 38d7ea4e1379d: Extracting information
[debug] Looking for embeds
ERROR: Unsupported URL: https://zalohuj.si/public-file/38d7ea4e1379d/
Traceback (most recent call last):
  File "/usr/local/bin/yt-dlp/yt_dlp/YoutubeDL.py", line 1581, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/bin/yt-dlp/yt_dlp/YoutubeDL.py", line 1716, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 717, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/generic.py", line 2531, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://zalohuj.si/public-file/38d7ea4e1379d/

This site looks like it is primarily used for piracy and therefore cannot be supported. If you have reason to believe otherwise, please provid evidence


Disable Re-Login Attempts

There is no documented option to disable auto login attempts in case of invalid username and password. Now if it happens by mistake you get your account locked in matter of seconds. awscli shouldn't reattempt by default as standard identity policies these days lock account on consecutive 3 invalid attempts.
It should be disabled by default and give an option to enable auto re-attempts, or should give an option to disable login re-attempts if enabled by default.

@atifrasheed79 good catch. Re-attempting with a saved password is guaranteed to fail. The cleverness of trying to handle interactive and stored config is biting back 😄
I'll take a look at this. Should be a quick fix.

Thanks for your quick action @AlainODea :) Appreciate it.


Flash on image loaded

I'm experiencing a 'flash' and distorted text, after images are loaded inside a GridView, with an appbar with a title, using a custom loadingWidget. You need to close and open the app again to see the flash. See this minimal example:
import 'package:flutter/material.dart';
import 'package:flutter_advanced_networkimage/provider.dart';
import 'package:flutter_advanced_networkimage/transition.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'My App',
      home: Scaffold(
        appBar: AppBar(
          title: Text('NOTICE FLASH HERE 1TIME LOADED'),
        ),
        body: GridView.builder(
          itemCount: 50,
          gridDelegate:
              SliverGridDelegateWithFixedCrossAxisCount(crossAxisCount: 3),
          itemBuilder: (context, index) {
            return TransitionToImage(
              image: AdvancedNetworkImage(
                  'https://sample-videos.com/img/Sample-jpg-image-500kb.jpg'),
              loadingWidget: Container(color: Colors.red),
            );
          },
        ),
      ),
    );
  }
}

Version info:
flutter --version
Flutter 1.2.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 8661d8aecd (2 weeks ago) • 2019-02-14 19:19:53 -0800
Engine • revision 3757390fa4
Tools • Dart 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

I'm testing on an iPhone 7 device.

I tried now to return Image.network inside builder, and it's super buggy..

Yeah, the loading widget will disappear immediately and fade in image. For the fullscreen loading widget, it looks like flashing. I can add fade out transition for loading widget.

I find it strange that this interferes with the AppBar title text, and from the issue i made on Flutter, it seem there is some kind of other issue. But fade out ( and in? ) transition for loading view would still be cool.
Update: I tested now on a Simulator ( iPhone XR 12.1 ) and the problem is not here. Maybe it's only on real devices ( or just my phone iPhone 7 12.1.4 ).

The issue seem to come from adding:
<key>io.flutter.embedded_views_preview</key>
<true/>

to info.plist, so i will close this now and hope that the Flutter team will fix this.


Add Pod Eviction Reason To Event Details

Now that #319 is merged and the log messages from the descheduler include the reason for evicting pods it would be nice if the k8s events created would also include the reason too.
Looks like all that would be needed it to adjust the code in these two functions to make this happen.
https://github.com/kubernetes-sigs/descheduler/blob/305801dd0e8a6f31d6e7cdb91b4e639b3b5b4d35/pkg/descheduler/evictions/evictions.go#L128
https://github.com/kubernetes-sigs/descheduler/blob/305801dd0e8a6f31d6e7cdb91b4e639b3b5b4d35/pkg/descheduler/evictions/evictions.go#L153

/kind feature
I might try to work on this, but if someone has time then please don't wait for me.

/assign

/close
Implemented in #321


Bugfix/tb bugfix 0102

这个 PR 实现什么功能/修复什么问题:

elastic skus add region_ext_id & zone_ext_id
disk delete condition validator
huawei oss client read http ProxyFromEnvironment
network operations add action log
account create bugfix

是否需要 backport 到之前的 release 分支:

release/2.13
release/2.14
release/3.0

/area region
/cc @swordqiu @yousong @ioito

Codecov Report

Merging #4509 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #4509      +/-   ##
=========================================
- Coverage    6.83%   6.82%   -0.01%
=========================================
  Files         522     522
  Lines       88574   88598      +24
=========================================
- Hits         6054    6050       -4
- Misses      82016   82042      +26
- Partials      504     506       +2

Flag
Coverage Δ

#aFlag
6.82% <0%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/compute/models/elasticcache_skus.go
4.21% <0%> (-0.23%)
:arrow_down:

pkg/compute/models/cloudaccounts.go
0.86% <0%> (-0.01%)
:arrow_down:

pkg/compute/models/disks.go
0.58% <0%> (-0.01%)
:arrow_down:

pkg/cloudcommon/db/lockman/fifo.go
80% <0%> (-10%)
:arrow_down:

pkg/appsrv/response.go
66.15% <0%> (-3.08%)
:arrow_down:

Continue to review full report at Codecov.

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

/lgtm

/lgtm

/lgtm

/lgtm

/approve


curl in verification section of module 8 throws error regarding 'setting certificate verify locations'

When I execute the following curl command in the Verification section of Module 8 from the home directory of each controller instance, curl --cacert ca.pem https://${KUBERNETES_PUBLIC_ADDRESS}:6443/version, I get the following error:

curl: (77) error setting certificate verify locations:
CAfile: ca.pem
CApath: /etc/ssl/certs

However, when I execute the curl command with the path to the ca.pem file, I get the expected outcome. curl --cacert /etc/etcd/ca.pem https://${KUBERNETES_PUBLIC_ADDRESS}:6443/version
Question: Should this curl command be amended or did I miss some step regarding the CAPath?
tl;dr:

Works as expected: curl --cacert /etc/etcd/ca.pem https://${KUBERNETES_PUBLIC_ADDRESS}:6443/version
Doesn't work as expected: curl --cacert ca.pem https://${KUBERNETES_PUBLIC_ADDRESS}:6443/version

Also stumbled over that but then I read the section again and noticed the note earlier:

The compute instances created in this tutorial will not have permission to complete this section. Run the following commands from the same machine used to create the compute instances.


Include a store's listings in the Discover Tab

As the title suggests. These listings should been seen when the 'All Stores' pull-down is selected.
Stretch features: remove the 'Follow/Unfollow' and 'Block' tabs when hovering over... or grey them out?

@drwasho  It would be nice to hover and see edit/clone/delete on your own items (like it currently works on your store page)

@morebrownies yeah definitely!

Bumping this to a feature-complete requirement. I can see users thinking that they're node is offline because they can't see their listings in the Discover tab.

I think this is a server issue, not a client issue. The client doesn't do anything to stop you from seeing your own items in discover, they're just never sent from the server.
I will open an issue on the server.


Unicode characters break installation in develop.py

Hi,
The below code fails when a script contains Unicode symbols. io.open uses the encoding returned by locale.getpreferredencoding, which isn't always UTF-8. Is there a way to set the preferred encoding globally in the setup.py file to work around this?
Thanks!
https://github.com/pypa/setuptools/blob/master/setuptools/command/develop.py#L186-187

@msto If you want to set the locale globally, can you just use locale.setlocale in your setup script?

That said, looking at this, I'm guessing we should try to detect PEP 263 encodings rather than just guessing.
We should be able to do all the same checks that Python does to determine source file encoding, and fall back to the locale encoding if none of them work. I think that's the most sensible thing to do.


CMake Fixup

[x] Formatting and some rearrangement.
[x] Fix #119.
[x] Fix #121.
[x] Add compiler warning flags.
[x] Make Sugar a subtree instead of a submodule?

Catch has been updated to fix a warning on gcc.

Coverage remained the same at 45.033% when pulling b47f2bc680a872120726f1d7b011ed6e49060bc2 on cmake-fix into 68a37c1ea28c32bef151c17d4c8b7f85e1d11e0d on master.

Coverage remained the same at 45.033% when pulling 5320d2b57c48bdfaed6c873fc75d703f104428d4 on cmake-fix into 68a37c1ea28c32bef151c17d4c8b7f85e1d11e0d on master.

Coverage remained the same at 45.033% when pulling 50902d194bc87baf48c42fe5a5db993882a50fba on cmake-fix into 68a37c1ea28c32bef151c17d4c8b7f85e1d11e0d on master.

Coverage remained the same at 45.033% when pulling a832c947d307d99e49f1e2b381160d019b9062c9 on cmake-fix into 68a37c1ea28c32bef151c17d4c8b7f85e1d11e0d on master.

If I was being picky, I'd ask that all 5 of those points were split into separate PRQs :p
I'm not sure about this Sugar thing, and certainly not sure about it being a subtree rather than a submodule. Can you expand on your reasoning for it?

@CaptainHayashi and I thought making subtrees out of Sugar and the GSL (in his branch) would avoid noobs having problems by not getting the submodules. I do see the downsides too. I have no strong feelings one way or the other.
Sugar is quite large, and I'm not using most of it. My justification for it isn't terribly strong. My personal style is to pull in modules rather than write essentially the same thing myself.
I'm currently not touching the warning flags for the MSVC build, because I'm not sure what I want to do with it yet.
Sugar also has a module for collecting source files, because the standard ways of globbing your source files don't work well in CMake (which is why we currently list every source file). I'll look into it.

What @DinCahill said—we've tangled ourselves in knots in URY with submodules before, and it doesn't at all seem worth it in this case.  What exactly are the disadvantages to using subtree merge over submodules?

@DinCahill is this ready to merge?  It's been sitting here for a while

Ready other than the subtree/submodule issue.

Still not a fan of the subtree, I think. Although I don't actually care, so do whatever :p

I'll update libraries in separate commits in future ❤

But muh history

Can we merge this?

don't care anymore


Add a GitHub Workflow as CI run

CircleCI is limiting how many runs we can do, which results in pipelines
randomly failing when we've used up the credits for this month.
Let's add a github workflow instead. Unfortunately github workflows are
a bit of a toy api, no support for YAML anchors or extending other jobs,
so there's a lot of duplication needed to get a job to do something.
The actions added in this patch help a bit to make the jobs easier to
understand (copied from libwacom).
This only runs on Ubuntu right now.

Sigh, github doesn't run the workflow on a MR unless there's already a workflow file, so this will simply not run. The result for this commit is in my personal fork though: https://github.com/whot/libratbag/actions/runs/1534040822

LGTM

Minor note, I've duplicated the actions to this repo. We could use libwacom's actions directly with
- uses: linuxwacom/libwacom/.github/actions/pkginstall@master

I'm a bit unsure whether we should since I don't want to have to maintain those actions with a public API. But I guess we could just use @sha instead of @master so we don't have to worry about breakage? Not sure yet, any opinions?


get error every second with predis 2.2

Laravel Version
10.48.12
PHP Version
8.2.5
Database Driver & Version
postgresql 15
Description
i get error after update predis to : "predis/predis": "^2.2"
vendor/composer/../predis/predis/src/Command/ZSetRemove.php): Failed to open stream: No such file or directory
vendor/composer/ClassLoader.php:571)
every second get this error
Steps To Reproduce
laravel new bug-report --github="--public"

Hey there, thanks for reporting this issue.
We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here?
Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.
laravel new bug-report --github="--public"

Do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue.
Thanks!

duplicate of https://github.com/laravel/horizon/issues/1459


Implement type-erased scheduler and sender types

 Issue by ericniebler
Wednesday Jul 20, 2022 at 19:16 GMT
Originally opened as https://github.com/NVIDIA/stdexec/issues/543

None

dupe of #35


Exceptions

This is not a complete pull request , but I wanted to get your opinion
Thought it would be a good idea to separate the huge exceptions file into more manageable chunks that would be easier to read and maintain.
there are a few things I'm not sure about

not sure the way I'm importing everything in the init file  is the best way to do it
related to 1 . would it be better to use separate namespaces for different exception types rather than dumping all of them in the same namespace ?
i.e.

exceptions.enum.CantRenameEnum
exceptions.function.SarkNoFunction

rather than
exceptions.CantRenameEnum
exceptions.SarkNoFunction

naming convention : some of the exceptions start with SarkError prefix or similiar  and some don't.
I was thinking of making it more uniform , maybe remove the SarkError in most cases or add some other prefix/postfix
I'm specifically talking about the enum exceptions.
SarkErrorAddEnumMemberFailed would make sense as  AddEnumMemberFailed ( considering most of the other enum exceptions don't have SarkError prefix  )
but SarkErrorEnumMemberName would probably have to be EnumMemberNameError to make it clear it's an error
what do you think ?

Thanks for the suggestion, but I much prefer having the exceptions separated from the rest of the code.
Putting the exceptions in each and every module causes dependency hell.
As for namespaces, that might be a good point, but I am not sure how to make it usable (without users going all from X import *)
As for the naming - you are absolutely right. I would be delighted to rename most of those into better names. But I would hate to break compatibility with existing code. The only feasible solution here IMO is aliasing the exceptions with newer names, as I don't know a way to state that a name is deprecated in a meaningful manner.
As for aliases - while they can make some code more readable, the duplication would be a bit hellish too.
If you have better ideas, I'd be happy to hear. I am pretty sure that I have "name conflicts" in the exceptions file as it is...

Closing this as I am not going to move the exceptions to different files.


Update porting overview and dependencies section

In line with some adjusted guidance for the 3.0 release

The build report has a broken link introduced because of the removal of one of the headings. I'll look at the overall changes now.

Also, don't know if you looked at the comments for this article before since CSAT is not great:
https://commenthubprod.azurewebsites.net/Verbatims?Status=All&HasBugs=All&Search=TopicKey&Value=9200f719-6da7-74f8-4b57-4534c6bd3551&BucketName=Kudos%2CRant%2CContent-Accuracy%2CContent-BadExample%2CContent-Incomplete%2CContent-NeedExample%2CLoc-BadMT%2CLoc-HelpExperience%2CLoc-NeedsLoc%2CLoc-Other%2CLoc-PrefersENU%2CProduct%2CLoc-Translation%2CPresentation-BrokenLink%2CPresentation-StyleVisuals%2CSite-CannotFind%2CSite-Feature%2CSite-FeedbackControl&Take=20

@mairaw

Also, don't know if you looked at the comments for this article before since CSAT is not great:

This should make some of that better, but since we don't really have any actual tooling to help with porting (at least not anything supported) beyond migrating to PackageReference there isn't much to do

@mairaw this one is ready from my perspective

Is this ready for a new review @cartermp?

Yep!
On Wed, Oct 2, 2019, at 21:36, Maira Wenzel wrote:

Is this ready for a new review @cartermp https://github.com/cartermp?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dotnet/docs/pull/14621?email_source=notifications&email_token=ABQEJTXMYAAADTTLXQELGCDQMVZEBA5CNFSM4IZZ6NZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAG6QEA#issuecomment-537782288, or mute the thread https://github.com/notifications/unsubscribe-auth/ABQEJTRYKJLMYSAYWF5OGYDQMVZEBANCNFSM4IZZ6NZA.

@cartermp I gave this a quick read this morning.  Other than Maira's one question and the merge conflicts, I think it's ready.


Allow both sidebars on one side.

https://github.com/microsoft/vscode/issues/108264#issuecomment-1553223336:

Previously requested in #142742 by @heartacker but that issue was ultimately closed by @sbatten  as out of scope.

In which case, @gjsjohnmurray, I'd like to close this as a duplicate, but I'd also like the other issue to be re-triaged.

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Make CheckWidths accept zero-width UIntLiterals

Fixes #508

This change seems to lead to a zero-width Vec issue in the Chisel tests. Looking into it

(Well I think this one combined with the one where Chisel emits zero width UInts)

@colinschmidt Can you confirm this works?

Here's the Chisel branch, looking in to the Chisel test failure: https://github.com/ucb-bar/chisel3/tree/one-entry-enum

Thanks @jackkoenig I'll test with that branch and this firrtl branch

Hmm I got a bunch of these errors:
======== Starting Transform CheckWidths$ ========
[error] (run-main-0) firrtl.passes.PassExceptions:
[error] firrtl.passes.CheckWidths$TailWidthException:  @[Decoupled.scala<EMAIL_ADDRESS>[module FinishQueue] Parameter 1 in tail operator is larger than input width 1.
[error] firrtl.passes.CheckWidths$TailWidthException:  @[Decoupled.scala<EMAIL_ADDRESS>[module FinishQueue_1] Parameter 1 in tail operator is larger than input width 1.
[error] firrtl.passes.CheckWidths$TailWidthException:  @[Decoupled.scala<EMAIL_ADDRESS>[module FinishQueue_2] Parameter 1 in tail operator is larger than input width 1.
[error] firrtl.passes.CheckWidths$TailWidthException:  @[Decoupled.scala<EMAIL_ADDRESS>[module Queue_16] Parameter 1 in tail operator is larger than input width 1.
[error] firrtl.passes.CheckWidths$TailWidthException:  @[Decoupled.scala<EMAIL_ADDRESS>[module Queue_17] Parameter 1 in tail operator is larger than input width 1.
[error] firrtl.passes.CheckWidths$TailWidthException:  @[Decoupled.scala<EMAIL_ADDRESS>[module Queue_127] Parameter 1 in tail operator is larger than input width 1.

It seems like there might be some hidden zero-width wire problems in Firrtl, perhaps we should just patch Chisel by not emitting zero-width for 1-entry Enums and at least fix THAT problem

I added a testcase that currently fails so that a fix for it (and possibly other issues) can accompany this change.

No updates, I think it's a lingering problem

I rebased and cleaned up. The previously failing Vec test works now; should we consider merging this now @jackkoenig?


[HUDI-653] Add JMX Report Config to Doc

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
Add JMX Report Config to doc
Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@XuQianJin-Stars Would you please only update the docs under _docs and please not update the docs under 0.5.0/0.5.1. Thanks.

@XuQianJin-Stars Would you please only update the docs under _docs and please not update the docs under 0.5.0/0.5.1. Thanks.

well，Let me change it.


Release 0.9?

I'm a OS researcher and I would like to use loxilb as a benchmark for BPF in a paper. I noticed 0.8 was a while a go. Do you think it would be possible to tag 0.9? This would give me a well-specified version to reference.

We will bump the version soon to 0.9. Since we kept waiting for a few features, 0.9 got delayed.

Release 0.9.0 is now available. If you have any issues, please raise an issue or contact us via slack.

Thanks!


client should preserve "ase_errors" for Errors

The fast server has this note:
                /*
                 * The marshaling of Errors is a little sketchy, owing partly to
                 * the history of Fast and partly to the sketchy definition of
                 * Errors in JavaScript.  The goal is to allow the client
                 * program to reconstitute an Error object that looks like the
                 * one we have here.
                 *
                 * We need to provide at least "name" and "message" to make it
                 * look like a JavaScript Error.  As a departure from the
                 * previous implementation, we do not provide the "stack" field.
                 * It's way too confusing for the client to wind up with an
                 * Error whose stacktrace is from a different program on a
                 * different system.  (The filenames and line numbers in the
                 * stack trace may not even exist on the client system, and
                 * they certainly may not refer to the same files and line
                 * numbers even if they do exist.)
                 *
                 * We provide "info" as VError.info() because this is the modern
                 * way to provide information properties on Errors.
                 *
                 * We provide "context" and "ase_errors" because the old Fast
                 * implementation did so.  "context" is how old Fast servers
                 * would specify error metadata (before VError.info() existed).
                 * "ase_errors" is a private implementation property of
                 * MultiError, and we never should have exposed it, but things
                 * potentially do depend on it.
                 */

That pretty much explains the background for this issue.  Specifically, the electric-moray test suite (and potentially electric-moray's consumers, by extension) depends on "ase_errors".  However, while the Fast server preserves it as mentioned in the comment, the client does not.  The client only preserves "context".  This was just an oversight.  We should fix the client to preserve "ase_errors" for compatibility with consumers like electric-moray.

I tested the change by running the full test suite (including compatibility test suite) with Node 0.10.48 on SmartOS.  (There's no reason to believe any of this is version- or platform-specific.)


Why 90 degree rotations are not allowed for macro

Hi, according to NETLIST_FORMAT, 90 degree rotations are not allowed for macro. May I know the reason?

This is a design rule.
If you rotate a macro by 90 degrees, it will change the orientation of the poly and fin direction of that macro, causing misalignment.
In the design, the poly and fin direction for all macros and standard cells must align. Therefore, 90-degree rotations are not allowed.


Add Users to Organizations

We need to create a field to add Users into a Organization. This field is called members.
In the "Invite more people" field, we can only asks for a email address and try to relate that user with this Organization and send a email telling to the user that he was joined. If the users doesnt exists on speakerfight we can just return an error telling that this user needs to sign up before be invited in a organization.

Hey @luanfonceca can I help with this one?

Yeah, sure! If you need some help please come to http://gitter.im/luanfonceca

Hey @luanfonceca what do you think about adding members with some membership types, like Owner? That way I believe that queries will be easier to get members, and still keeping the ownership info, and why not enable more than one owner per org. Let me know if you just want to keep the created_by field and create a members relation.


Data discrepancy found

Invalid release year 3003 for Lost in Translation it should be 2003 😃

Thanks for feedback! Well spotted! it has been fixed in release v1.0.0

Jon Done!


Add Babel support to the project

This task includes adding Babel to the project to transpile all ES-6 code that is being added. You should include a .babelrc config file with the following configuration:-
{
  "presets": [
    ["@babel/env", {
      "targets": {
        "node": "current"
      }
    }]
  ],
  "plugins": [
    "@babel/plugin-proposal-class-properties",
    "@babel/plugin-proposal-object-rest-spread"
  ]
}

Can I do this?


Debugger support for Windows ARM 64?

Are there plans to add Dubugger support for ARM 64 devices?
Thanks,

There are definitely plans, but we don't have an exact date/release that we are targeting yet. This is tracked with #3006.

This is good news. I'm waiting to get a surface pro x on this plugin to work in VSCode ARM.


Add section on identifying datatype modalities with suffixes

Further to #45, we discussed formalising the modality suffixes for files / folders that go in datatype folders. Here modality is like a sub-datatype, for example ephys is a datatype but patch-clamp electrophysiology and extracellular electrophysiology are modalities, both of which go in the ephys folder.
In general, people are unlikely to collect conflicting datatypes in the same session. However, it is possible (e.g. single-unit + extracellular physiology for validation). In this case we decided to reccomend using modality suffixies, similar to BIDS.
For example an organisation could be:
sub-001/ses-001/ephys/sub-001_ses-001_patchclamp/...
sub-001/ses-001/ephys/sub-001_ses-001_ecephys

In Neuroblueprint, we could have a dropdown that explains this. This is quite an edge case so we can be careful not to distract people with it if they do not need to know. I wonder if we should even, down the line, have an FAQ or Advanced usage section where we put edge cases like this.
An example dropdown menu content:
It is possible that you may collect two different modalities that full under the same datatype within a single session. For example, it is possible that intracellular patch-recordings may be collected at the same time as extracellular probe recordings. Or, [some other imaging example].

In this case, it is recommended to distinguish these two modalities using one of the mandated suffixes below. In this instance, it is permitted to break with key-value pair formatting to add the suffix.

For example,
rawdata
  sub-001
    ses-001
        funcimg
              <two example filenames e.g. sub-001_ses_001_run-001_modality.bin with two separate modalities>.

The list of permitted modality suffixes is:
(need to check bids. We would need for:

patch clamp
extracellular ephys
surface recordings (?)
lots of imaging)

Closed as furthered in #57, we will not go down this route.


Set up new browser tests that use localhost

This PR is an extension of https://github.com/cfpb/cfgov-refresh/pull/4407.
Here's what we've done:

Copied the current tests in test/browser_tests/cucumber/ to test/browser_tests/cucumber-new/ (hence all the new files below).
Modified the new tests to use localhost:8000 instead of tox.
Added some new Regs3K tests.
Created a gulp test:acceptance:new task for running the new browser tests. Specific specs can be run with gulp test:acceptance:new --specs=regulations-search.feature.

Travis will continue running the legacy tests via gulp test:acceptance. Once we set up Jenkins to build public GitHub PRs, we'll delete the legacy tests.
Testing

Pull down branch
Get your local version of cf.gov running at http://localhost:8000
Ensure that the following env vars are set (they should already be in your .env file):

export TEST_HTTP_HOST=localhost
export DJANGO_HTTP_PORT=8000

Run gulp test:acceptance:new

Notes

Removing the ability to test with tox necessitates taking that step out of Travis, which has the side benefit of saving several minutes per Travis build

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[x] Code follows the standards laid out in the development playbook
[x] Passes all existing automated tests
[x] Any change in functionality is tested
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[x] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[x] Reviewers requested with the Reviewers tool :arrow_right:

Please clarify because the original PR Notes is confusing/contradicting what was said in FEWD meeting today: Does this PR still keep the tox environment for use on Travis for PRs?

Please clarify because the original PR Notes is confusing/contradicting what was said in FEWD meeting today: Does this PR still keep the tox environment for use on Travis for PRs?

Yes. From the OP:

Travis will continue running the legacy tests via gulp test:acceptance. Once we set up Jenkins to build public GitHub PRs, we'll delete the legacy tests.

Question! With the new tests, can we still run them with all the options documented on this page, such as in this section? https://cfpb.github.io/cfgov-refresh/browser-acceptance-tests/#manual-test-configuration

Question! With the new tests, can we still run them with all the options documented on this page, such as in this section? https://cfpb.github.io/cfgov-refresh/browser-acceptance-tests/#manual-test-configuration

@cat Yes, it appears everything works the same way in that regard.