DHCP connections

Great code.  I integrated it with FAUXMOESP.
The issue I have is, I cannot connect  unless I do a static advanced setup - then commit.
Once that is done and I reboot - it connects very well.  I can change the ip , gateway and it still works fine.
However, if i scan and select the SSID then enter the password - it times out...
Any ides what might be the cause?
Thanks
Joe

Not really...would have to see logs at least. Most likely is a problem with the access point.

Ok,
I have several other esp8266 devices and using other code they connect and get an ip with no problems.
I tried a few different esp devices and they behaved the same.
I can see it attempting to connect  but eventually times out..
The codes seem to work well with each other.  The Code provides 2 Alexa devices by emulating a wemo switch...
The code below is what I am using:
Thanks for having a look...
Joe
-----------------------------------------------code-------------------------------------
#include <Arduino.h>
#include <ESP8266WiFi.h>
#include <ESPSerialWiFiManager.h>
#include "fauxmoESP.h"
#define SERIAL_BAUDRATE                 115200
fauxmoESP fauxmo;
#define Flex2_PIN 13 // d7=gpio13
#define Flex1_PIN 5 //d1 =gpio5
void callback(uint8_t device_id, const char * device_name, bool state) {
Serial.printf("[MAIN] %s state: %s\n", device_name, state ? "ON" : "OFF");
if ( (strcmp(device_name, "Flex1") == 0) ) {
if (state) {
  digitalWrite(Flex1_PIN, HIGH);
} else {
  digitalWrite(Flex1_PIN, LOW);
}

}
if ( (strcmp(device_name, "Flex2") == 0) ) {
// adjust the Flex immediately!
if (state) {
digitalWrite(Flex2_PIN, HIGH);
} else {
digitalWrite(Flex2_PIN, LOW);
}
}
}
void setup() {
pinMode(Flex2_PIN, OUTPUT);
digitalWrite(Flex2_PIN, LOW);//
pinMode(Flex1_PIN, OUTPUT);
digitalWrite(Flex1_PIN, LOW);
//Create the manager object
ESPSerialWiFiManager esp = ESPSerialWiFiManager();
//void setup(){
//Initialize the serial connection. This is required.
Serial.begin(115200);
//Complete manager init (this will init WiFi and EEPROM)
esp.begin();
//If desired at beginnging, show manager menu
//This will timeout after 10 seconds
esp.run_menu(10);
// Fauxmo
fauxmo.addDevice("Flex2");
fauxmo.addDevice("Flex1");
fauxmo.onMessage(callback);
}
void loop() {
fauxmo.handle();
}

What's the IP of your DHCP host?
On Tue, Mar 7, 2017 at 9:52 PM, joeman2116<EMAIL_ADDRESS>wrote:

Ok,
I have several other esp8266 devices and using other code they connect and
get an ip with no problems.
I tried a few different esp devices and they behaved the same.
I can see it attempting to connect but eventually times out..
The codes seem to work well with each other. The Code provides 2 Alexa
devices by emulating a wemo switch...
The code below is what I am using:
Thanks for having a look...
Joe
-----------------------------------------------code---------
#include <Arduino.h>
#include <ESP8266WiFi.h>
#include <ESPSerialWiFiManager.h>
#include "fauxmoESP.h"
#define SERIAL_BAUDRATE 115200
fauxmoESP fauxmo;
#define Flex2_PIN 13 // d7=gpio13
#define Flex1_PIN 5 //d1 =gpio5
void callback(uint8_t device_id, const char * device_name, bool state) {
Serial.printf("[MAIN] %s state: %s\n", device_name, state ? "ON" : "OFF");
if ( (strcmp(device_name, "Flex1") == 0) ) {
if (state) {
digitalWrite(Flex1_PIN, HIGH);
} else {
digitalWrite(Flex1_PIN, LOW);
}
}
if ( (strcmp(device_name, "Flex2") == 0) ) {
// adjust the Flex immediately!
if (state) {
digitalWrite(Flex2_PIN, HIGH);
} else {
digitalWrite(Flex2_PIN, LOW);
}
}
}
void setup() {
pinMode(Flex2_PIN, OUTPUT);
digitalWrite(Flex2_PIN, LOW);//
pinMode(Flex1_PIN, OUTPUT);
digitalWrite(Flex1_PIN, LOW);
//Create the manager object
ESPSerialWiFiManager esp = ESPSerialWiFiManager();
//void setup(){
//Initialize the serial connection. This is required.
Serial.begin(115200);
//Complete manager init (this will init WiFi and EEPROM)
esp.begin();
//If desired at beginnging, show manager menu
//This will timeout after 10 seconds
esp.run_menu(10);
// Fauxmo
fauxmo.addDevice("Flex2");
fauxmo.addDevice("Flex1");
fauxmo.onMessage(callback);
}
void loop() {
fauxmo.handle();
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-284931041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6reGnXc6M8M9ACqcTRqbvRZVnsmeks5rjhfzgaJpZM4MWTAc
.

<IP_ADDRESS> (router ip) dhcp host

Send me the serial log of when you use advanced mode and it does work.
Please remember to blank out the wifi password :)
On Mar 7, 2017 9:56 PM, "joeman2116"<EMAIL_ADDRESS>wrote:

<IP_ADDRESS> (router ip) dhcp host
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-284931549,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6mKKzvDHc4GkbNfbTW12Os0TxlPJks5rjhjDgaJpZM4MWTAc
.

.....
Connection Sucessful
Current Network Details:
SSID: ASUS66ujoe
IP Address: <IP_ADDRESS>
MAC address: 33:6C:29:7F:CF:5C
Subnet Mask: <IP_ADDRESS>
Gateway: <IP_ADDRESS>
DNS 1: <IP_ADDRESS>
DNS 2: <IP_ADDRESS>
Did you mean the above?  - from my serial monitor

I meant ALL of it. Not just the final details.
On Mar 7, 2017 10:04 PM, "joeman2116"<EMAIL_ADDRESS>wrote:

.....
Connection Sucessful Current Network Details: SSID: ASUS66ujoe
IP Address: <IP_ADDRESS>
MAC address: 33:6C:29:7F:CF:5C
Subnet Mask: <IP_ADDRESS>
Gateway: <IP_ADDRESS>
DNS 1: <IP_ADDRESS>
DNS 2: <IP_ADDRESS>
Did you mean the above? - from my serial monitor
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-284932810,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6oiV3Am3TMdOcr_RLnLcHscezzY8ks5rjhqogaJpZM4MWTAc
.

Sorry, here is the complete screen

I just tried to connect to another router and got the same results.. Only connects with a static ip advanced configuration
joe

Very weird... What version of the ESP arduino core are you using and what
actual board are you using?
On Tue, Mar 7, 2017 at 10:47 PM, joeman2116<EMAIL_ADDRESS>wrote:

I just tried to connect to another router and got the same results.. Only
connects with a static ip advanced configuration
joe
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-284938707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6rN19IDTgRR5RiQDd4B6I6sThQW7ks5rjiTegaJpZM4MWTAc
.

board is using an esp8266 12 d1 mini
Not sure where to find info on core?
I have several other nodemcu - i could program - ?

Honestly, I'm not sure. It should work with DHCP. Go into the arduino
boards manager and search for ESP8266 and tell me what version it says
there.
On Tue, Mar 7, 2017 at 10:53 PM, joeman2116<EMAIL_ADDRESS>wrote:

board is using an esp8266 12 d1 mini
Not sure where to find info on core?
I have several other nodemcu - i could program - ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-284939489,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6mkco2Getvt6gJEq0sKY4TWtN87Gks5rjiZCgaJpZM4MWTAc
.

The board manager says:
esp8266- builtin by Simon peter is ver 1.0.0
On Wed, Mar 8, 2017 at 12:58 AM, Adam Haile<EMAIL_ADDRESS>wrote:

Honestly, I'm not sure. It should work with DHCP. Go into the arduino
boards manager and search for ESP8266 and tell me what version it says
there.
On Tue, Mar 7, 2017 at 10:53 PM, joeman2116<EMAIL_ADDRESS>wrote:

board is using an esp8266 12 d1 mini
Not sure where to find info on core?
I have several other nodemcu - i could program - ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284939489>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6mkco2Getvt6gJEq0sKY4TWtN87Gks5rjiZCgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-284947220,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWDpY60xvqOxesOR4VnR19L-hzmzcI7uks5rjjWOgaJpZM4MWTAc
.

Current official release is 2.3.0: https://github.com/esp8266/Arduino
That is the only version my library supports.
On Wed, Mar 8, 2017 at 8:45 AM, joeman2116<EMAIL_ADDRESS>wrote:

The board manager says:
esp8266- builtin by Simon peter is ver 1.0.0
On Wed, Mar 8, 2017 at 12:58 AM, Adam Haile<EMAIL_ADDRESS>wrote:

Honestly, I'm not sure. It should work with DHCP. Go into the arduino
boards manager and search for ESP8266 and tell me what version it says
there.
On Tue, Mar 7, 2017 at 10:53 PM, joeman2116<EMAIL_ADDRESS>wrote:

board is using an esp8266 12 d1 mini
Not sure where to find info on core?
I have several other nodemcu - i could program - ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284939489>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6mkco2Getvt6gJEq0sKY4TWtN87Gks5rjiZCgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284947220>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AWDpY60xvqOxesOR4VnR19L-hzmzcI7uks5rjjWOgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-285044044,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6gMtt4a5lOszrZrs84nnI9V0hYWlks5rjrEJgaJpZM4MWTAc
.

Just as a test I loaded a new arduino ide v 1.81 with the latest core etc
Compiled - and upload fine
hit the reset and menu came up on serial monitor
selected 1 to scan and it found my wifi ssid fine
Entered password
said connecting to my wifi name
a bunch of dots then said Failed connecting to AP.
Did a static and advanced - then a commit----- logged in perfect..
joe
On Wed, Mar 8, 2017 at 9:52 AM, Adam Haile<EMAIL_ADDRESS>wrote:

Current official release is 2.3.0: https://github.com/esp8266/Arduino
That is the only version my library supports.
On Wed, Mar 8, 2017 at 8:45 AM, joeman2116<EMAIL_ADDRESS>wrote:

The board manager says:
esp8266- builtin by Simon peter is ver 1.0.0
On Wed, Mar 8, 2017 at 12:58 AM, Adam Haile<EMAIL_ADDRESS>wrote:

Honestly, I'm not sure. It should work with DHCP. Go into the arduino
boards manager and search for ESP8266 and tell me what version it says
there.
On Tue, Mar 7, 2017 at 10:53 PM, joeman2116<EMAIL_ADDRESS>wrote:

board is using an esp8266 12 d1 mini
Not sure where to find info on core?
I have several other nodemcu - i could program - ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284939489>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6mkco2Getvt6gJEq0sKY4TWtN87Gks5rjiZCgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284947220>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AWDpY60xvqOxesOR4VnR19L-hzmzcI7uks5rjjWOgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-285044044>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6gMtt4a5lOszrZrs84nnI9V0hYWlks5rjrEJgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-285045652,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWDpY-q9Cv7u8seql_0T5OUpjte_8ihUks5rjrKhgaJpZM4MWTAc
.

Just setup a guest account - with no password and it connected fine and got
a dhcp ip ok.
Changed to encrypted wpa and wpa2 - failed log in.
How do i erase the eeprom - ?
When i do a static with a new ip and dns etc , then do a commit - it still
remembers the old settings
joe
On Wed, Mar 8, 2017 at 11:38 AM, joe basque<EMAIL_ADDRESS>wrote:

Just as a test I loaded a new arduino ide v 1.81 with the latest core etc
Compiled - and upload fine
hit the reset and menu came up on serial monitor
selected 1 to scan and it found my wifi ssid fine
Entered password
said connecting to my wifi name
a bunch of dots then said Failed connecting to AP.
Did a static and advanced - then a commit----- logged in perfect..
joe
On Wed, Mar 8, 2017 at 9:52 AM, Adam Haile<EMAIL_ADDRESS>wrote:

Current official release is 2.3.0: https://github.com/esp8266/Arduino
That is the only version my library supports.
On Wed, Mar 8, 2017 at 8:45 AM, joeman2116<EMAIL_ADDRESS>wrote:

The board manager says:
esp8266- builtin by Simon peter is ver 1.0.0
On Wed, Mar 8, 2017 at 12:58 AM, Adam Haile<EMAIL_ADDRESS>wrote:

Honestly, I'm not sure. It should work with DHCP. Go into the arduino
boards manager and search for ESP8266 and tell me what version it says
there.
On Tue, Mar 7, 2017 at 10:53 PM, joeman2116<EMAIL_ADDRESS>

wrote:

board is using an esp8266 12 d1 mini
Not sure where to find info on core?
I have several other nodemcu - i could program - ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284939489>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6mkco2Getvt6gJEq0sKY4TWtN87Gks5rjiZCgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284947220>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AWDpY60xvqOxesOR4VnR19L-hzmzcI7uks5rjjWOgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/
issues/14#issuecomment-285044044>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA6a6gMtt
4a5lOszrZrs84nnI9V0hYWlks5rjrEJgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-285045652,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWDpY-q9Cv7u8seql_0T5OUpjte_8ihUks5rjrKhgaJpZM4MWTAc
.

Choose option 4 (disconnect) then option 5 (commit) and that will clear out
the settings. Must be something with your specific wifi access point. I
used WPA all the time without issue. What model is it?
On Wed, Mar 8, 2017 at 10:58 AM, joeman2116<EMAIL_ADDRESS>wrote:

Just setup a guest account - with no password and it connected fine and got
a dhcp ip ok.
Changed to encrypted wpa and wpa2 - failed log in.
How do i erase the eeprom - ?
When i do a static with a new ip and dns etc , then do a commit - it still
remembers the old settings
joe
On Wed, Mar 8, 2017 at 11:38 AM, joe basque<EMAIL_ADDRESS>wrote:

Just as a test I loaded a new arduino ide v 1.81 with the latest core etc
Compiled - and upload fine
hit the reset and menu came up on serial monitor
selected 1 to scan and it found my wifi ssid fine
Entered password
said connecting to my wifi name
a bunch of dots then said Failed connecting to AP.
Did a static and advanced - then a commit----- logged in perfect..
joe
On Wed, Mar 8, 2017 at 9:52 AM, Adam Haile<EMAIL_ADDRESS>wrote:

Current official release is 2.3.0: https://github.com/esp8266/Arduino
That is the only version my library supports.
On Wed, Mar 8, 2017 at 8:45 AM, joeman2116<EMAIL_ADDRESS>wrote:

The board manager says:
esp8266- builtin by Simon peter is ver 1.0.0
On Wed, Mar 8, 2017 at 12:58 AM, Adam Haile<EMAIL_ADDRESS>

wrote:

Honestly, I'm not sure. It should work with DHCP. Go into the
arduino
boards manager and search for ESP8266 and tell me what version it
says
there.
On Tue, Mar 7, 2017 at 10:53 PM, joeman2116 <
<EMAIL_ADDRESS>

wrote:

board is using an esp8266 12 d1 mini
Not sure where to find info on core?
I have several other nodemcu - i could program - ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284939489>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6mkco2Getvt6gJEq0sKY4TWtN87Gks5rjiZCgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284947220>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AWDpY60xvqOxesOR4VnR19L-hzmzcI7uks5rjjWOgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/
issues/14#issuecomment-285044044>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA6a6gMtt
4a5lOszrZrs84nnI9V0hYWlks5rjrEJgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-285045652>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWDpY-q9Cv7u8seql_
0T5OUpjte_8ihUks5rjrKhgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-285081440,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6gTOgdZ5tQJV58W9yEl725FqJXPVks5rjtAwgaJpZM4MWTAc
.

Wooo - It worked
The solution seems to  be i needed to 4 disconnect and 5 commit.
It appears it was remembering the dhcp connect with a bad pw - so  select 4
and 5 cleared all...
Once i did that i did a scan , selected my wifi and entered the password --
logged in!!!!
Rebooted  and it got a dhcp ip --- fine..
Thanks for your help.....
One more question:
I use fauxmoesp to select Alexa (2)devices called flex and flex1... with
your code and it works great....
I was wondering if you might know how to have the alexa device names
selectable on a menu ?
It would be great if one could just use a menu like your wifi code to
select  new names.
The idea is to be able to give a esp module to someone and use it on teir
wifi- which your code allows.
But also so they could change the name of the alexa device name device to
something more meaning full to them
joe
On Wed, Mar 8, 2017 at 12:02 PM, Adam Haile<EMAIL_ADDRESS>wrote:

Choose option 4 (disconnect) then option 5 (commit) and that will clear out
the settings. Must be something with your specific wifi access point. I
used WPA all the time without issue. What model is it?
On Wed, Mar 8, 2017 at 10:58 AM, joeman2116<EMAIL_ADDRESS>wrote:

Just setup a guest account - with no password and it connected fine and
got
a dhcp ip ok.
Changed to encrypted wpa and wpa2 - failed log in.
How do i erase the eeprom - ?
When i do a static with a new ip and dns etc , then do a commit - it
still
remembers the old settings
joe
On Wed, Mar 8, 2017 at 11:38 AM, joe basque<EMAIL_ADDRESS>wrote:

Just as a test I loaded a new arduino ide v 1.81 with the latest core
etc
Compiled - and upload fine
hit the reset and menu came up on serial monitor
selected 1 to scan and it found my wifi ssid fine
Entered password
said connecting to my wifi name
a bunch of dots then said Failed connecting to AP.
Did a static and advanced - then a commit----- logged in perfect..
joe
On Wed, Mar 8, 2017 at 9:52 AM, Adam Haile<EMAIL_ADDRESS>wrote:

Current official release is 2.3.0: https://github.com/esp8266/Arduino
That is the only version my library supports.
On Wed, Mar 8, 2017 at 8:45 AM, joeman2116<EMAIL_ADDRESS>wrote:

The board manager says:
esp8266- builtin by Simon peter is ver 1.0.0
On Wed, Mar 8, 2017 at 12:58 AM, Adam Haile <
<EMAIL_ADDRESS>

wrote:

Honestly, I'm not sure. It should work with DHCP. Go into the
arduino
boards manager and search for ESP8266 and tell me what version it
says
there.
On Tue, Mar 7, 2017 at 10:53 PM, joeman2116 <
<EMAIL_ADDRESS>

wrote:

board is using an esp8266 12 d1 mini
Not sure where to find info on core?
I have several other nodemcu - i could program - ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284939489>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6mkco2Getvt6gJEq0sKY4TWtN87Gks5rjiZCgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284947220>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AWDpY60xvqOxesOR4VnR19L-hzmzcI7uks5rjjWOgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/
issues/14#issuecomment-285044044>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA6a6gMtt
4a5lOszrZrs84nnI9V0hYWlks5rjrEJgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-285045652>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWDpY-q9Cv7u8seql_
0T5OUpjte_8ihUks5rjrKhgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-285081440>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6gTOgdZ5tQJV58W9yEl725FqJXPVks5rjtAwgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-285082542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWDpY67DAcBwRAknL4Hd1pCRT-n7Rkkeks5rjtEDgaJpZM4MWTAc
.

Right now, no... though I've had requests for opening up that menu to
custom things.
I think what I may do in the future is pull all the menu stuff out into a
separate class that can be passed to the WiFi manager but then you could
continue to build your own menus with it.
On Wed, Mar 8, 2017 at 11:18 AM, joeman2116<EMAIL_ADDRESS>wrote:

Wooo - It worked
The solution seems to be i needed to 4 disconnect and 5 commit.
It appears it was remembering the dhcp connect with a bad pw - so select 4
and 5 cleared all...
Once i did that i did a scan , selected my wifi and entered the password --
logged in!!!!
Rebooted and it got a dhcp ip --- fine..
Thanks for your help.....
One more question:
I use fauxmoesp to select Alexa (2)devices called flex and flex1... with
your code and it works great....
I was wondering if you might know how to have the alexa device names
selectable on a menu ?
It would be great if one could just use a menu like your wifi code to
select new names.
The idea is to be able to give a esp module to someone and use it on teir
wifi- which your code allows.
But also so they could change the name of the alexa device name device to
something more meaning full to them
joe
On Wed, Mar 8, 2017 at 12:02 PM, Adam Haile<EMAIL_ADDRESS>wrote:

Choose option 4 (disconnect) then option 5 (commit) and that will clear
out
the settings. Must be something with your specific wifi access point. I
used WPA all the time without issue. What model is it?
On Wed, Mar 8, 2017 at 10:58 AM, joeman2116<EMAIL_ADDRESS>wrote:

Just setup a guest account - with no password and it connected fine and
got
a dhcp ip ok.
Changed to encrypted wpa and wpa2 - failed log in.
How do i erase the eeprom - ?
When i do a static with a new ip and dns etc , then do a commit - it
still
remembers the old settings
joe
On Wed, Mar 8, 2017 at 11:38 AM, joe basque<EMAIL_ADDRESS>wrote:

Just as a test I loaded a new arduino ide v 1.81 with the latest core
etc
Compiled - and upload fine
hit the reset and menu came up on serial monitor
selected 1 to scan and it found my wifi ssid fine
Entered password
said connecting to my wifi name
a bunch of dots then said Failed connecting to AP.
Did a static and advanced - then a commit----- logged in perfect..
joe
On Wed, Mar 8, 2017 at 9:52 AM, Adam Haile<EMAIL_ADDRESS>

wrote:

Current official release is 2.3.0: https://github.com/esp8266/
Arduino
That is the only version my library supports.
On Wed, Mar 8, 2017 at 8:45 AM, joeman2116 <
<EMAIL_ADDRESS>wrote:

The board manager says:
esp8266- builtin by Simon peter is ver 1.0.0
On Wed, Mar 8, 2017 at 12:58 AM, Adam Haile <
<EMAIL_ADDRESS>

wrote:

Honestly, I'm not sure. It should work with DHCP. Go into the
arduino
boards manager and search for ESP8266 and tell me what version
it
says
there.
On Tue, Mar 7, 2017 at 10:53 PM, joeman2116 <
<EMAIL_ADDRESS>

wrote:

board is using an esp8266 12 d1 mini
Not sure where to find info on core?
I have several other nodemcu - i could program - ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284939489>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6mkco2Getvt6gJEq0sKY4TWtN87Gks5rjiZCgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-284947220>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AWDpY60xvqOxesOR4VnR19L-hzmzcI7uks5rjjWOgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/
issues/14#issuecomment-285044044>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA6a6gMtt
4a5lOszrZrs84nnI9V0hYWlks5rjrEJgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-285045652>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AWDpY-q9Cv7u8seql_
0T5OUpjte_8ihUks5rjrKhgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-285081440>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6gTOgdZ5tQJV58W9yEl725FqJXPVks5rjtAwgaJpZM4MWTAc>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/
14#issuecomment-285082542>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWDpY67DAcBwRAknL4Hd1pCRT-n7Rkkeks5rjtEDgaJpZM4MWTAc>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/ESPSerialWiFiManager/issues/14#issuecomment-285087556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6pUUX2HgNmxi_Nd0CT9WVShpoTobks5rjtTcgaJpZM4MWTAc
.


config: set default preview image size limit to 5mb

closes https://github.com/inveniosoftware/cookiecutter-invenio-rdm/issues/179

Open Questions
While we do not have IIIF or any better performing previewer... is 5 MB a sensible limit? before it was set to 500KB, which was making it fail for mostly every file.
IMPORTANT NOTE: Remember to merge this commit also to v5 branch for it to be included in the release.

Question: Is the 5mb for the IIIF previewer?

No, the IIIF previewer is deactivated by default because of https://github.com/inveniosoftware/invenio-iiif/issues/43. i.e. it works externally but seems not to work for the landing page? Dan might have more details.
This limit is for the simple_image previewer: https://github.com/inveniosoftware/invenio-previewer/blob/master/invenio_previewer/extensions/simple_image.py#L22
We might want to remove the config variable once the IIIF is working.


docs: Document writing SCM version to file

Following #99

Plan to move the documentation to PDM, and leave a link in this README to refer to it. Thanks


Make mxGraph available for asynchronous apps

I want to display a process graph with mxGraph. The hierarchical layout perfectly fits my need. Unfortunately, mxGraph uses document.write to manipulate the DOM. This doesn't work in my Polymer app which makes heavy use of asynchronity.

Doesn't work specifically how?

Sorry for the very unspecific explanation, I was short in time.
I've written a wrapping custom element whose only purpose is to set the mxBasePath variable and to include the mxClient.js file. This custom element is (HTML-) imported into another custom element which should render a graph.
In Chromes Console the following message is logged multiple times when starting this app: "Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.".

How did you include the mxClient.js file?

mxGraph uses document.write to manipulate the DOM

Really!? Holly crap! Back to 00x?

No, we do not use document.write in the production mxClient.js file, only in the development mxClient.js file and this can easily be changed on line 314 in mxClient.js.

I'm so sorry, I really had a dev file in place. Thank you very much, Alder!
But there are still some questions I'm facing using the production version of mxGraph:

My first try to get a production version was to npm install it. But version 3.7.5 can't be built on my machine because of issue 83.
Even if npm install would work, I can't use it without fürther adaptions. In my app, I've an app folder which is delivered to the client by express. Unfortunately, the node_modules folder is a sibling of the app folder and thus wouldn't make it to the client.
So I downloaded a release and copied the files mxClient.min.js and css/common.css into app/elements/mxgraph. A custom component mxgraph-scripts.html consists of only two script tags, the first one setting mxBasePath, the other one pointing to the minified mxClient file. That currently does the trick.
In my Polymer scenario, which makes heavy use of custom components and thus document-fragments, I got an error while moving the mouse over the graph. The error was caused by calling window.getComputedStyle passing a ´document-fragment(which is not anHTMLElement). According to MDN, passing a non HTMLElementobject togetComputedStyleresults in an error. So I modified mxGraph'sgetOffsetmethod to skip the call ofmxUtils.getCurrentStyleif the current node is not anHTMLElement`.

I would appreciate to have a proper "installation" of mxGraph. The best solution for me would be to have a bower component (which builds ;) ). Additionally, it would be cool to have a <jgraph-mxgraph> custom element.
Regarding the error calling getComputedStyle on non HTMLELements I could provide a PR fixing mxUtils.getCurrentStyle.

Please file one ticket per subject.

I would have done this once we discussed the best approach or best-practice. But if you insist:

issue 107 (error with document-fragments)
issue 108 (Bower component)
issue 109 (Custom component)


Create FOSS_Tech.json

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Thank you for your contribution. Currently we are not allowing for communities to have their own LinkFree Profile as the commit and LinkFree Profile needs to match (the author of the Pull Request), so I will need to close this Pull Request.

Thank you for your contribution. Currently we are not allowing for communities to have their own LinkFree Profile as the commit and LinkFree Profile needs to match (the author of the Pull Request), so I will need to close this Pull Request.

Actually I was teaching a session regarding open source and How to create linkfree profile to community member and newbie coders .


Update CONTRIBUTING.md

use editable repo url as remote

Using SSH provides a better workflow, but I worry that occasional GitHub users may not have keys associated to their account, leading to confusing errors at the CLI. Experienced users presumably recognize the difference and diverge from the guide accordingly.

I have no opinion on the matter, @ndr-qef, so I trust your decision to either merge or close.

This is what the current directions yields if I try to push to said remote:
$ git push bukzor HEAD
Username for 'https://github.com': bukzor
Password for<EMAIL_ADDRESS>remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/bukzor/homebrew-cask/'

There's no password that will cause this to succeed, which is a much more confusing failure mode.
This is why I updated the directions. The scenario you're worried about (no ssh keys enabled/active) gives a more familiar and more googlable failure mode.
$ ssh-add -D
All identities removed.

$ git remote show -n buck
* remote buck
  Push  URL: git@github.com:bukzor/homebrew-cask.git

$ git push buck HEAD
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

GitHub should grant write access when you login with your account credentials (ref.). Perhaps there is a problem on your end?

Enabling 2FA means that a simple password doesn't work:
https://help.github.com/articles/which-remote-url-should-i-use/#cloning-with-https-recommended
According to that blog though, you're doing it right. https is the recommended clone url, apparently.

Should we close this, then, since we’re doing it the recommend way?

Yes. The segment being discussed is written with a particular concern for beginners (“fork with the ‘Fork’ button”), and I feel comfortable assuming that contributors with a working GitHub setup will ignore it.
@bukzor, while we should leave the current procedure intact, I feel that there is room for expanding it to cover SSH urls as you recommed. We will follow up if someone else raises the issue here or over IRC.


Move tutors aren't updated

The tutors in the server, I believe, unless I missed something, aren't updated to gen 8, so I'm unable to get expanding force on my galarian Slowbro and other gen 8 tutor moves are unavailable

I believe this was fixed. If this is still an issue, please recomment on this. Thanks!


How to simulate the BW fluctuation?

Hi!How could I simulate the network enviroment like Figure 3 and trace the true bandwidth?

The trace files are included in https://github.com/hongzimao/pensieve/blob/master/traces/README.md. You can load the trace for the simulator in https://github.com/hongzimao/pensieve/tree/master/sim. IIRC, figure 3a is a synthetic trace to showcase and motivate the problem with a fixed ABR scheme (i.e., too conservative in sawtooth bandwidth trace). You can generate similar trace and load it to the simulator.


FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox

What happened:
CNI failed to set up network:
Jan 29 06:41:25.617: INFO: At 2021-01-29 06:36:50 +0000 UTC - event for webserver-deployment-5575796f8f-k92dd: {kubelet 2884k8s001} Started: Started container httpd
Jan 29 06:41:25.617: INFO: At 2021-01-29 06:37:08 +0000 UTC - event for webserver-deployment-5575796f8f-9jj9z: {kubelet 2884k8s000} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "678fa65619f0dd4c0434d2b4e510bd99930bc62e8ea4b64ea8a5f79a73b20f6a": unexpected end of JSON input
Jan 29 06:41:25.617: INFO: At 2021-01-29 06:37:10 +0000 UTC - event for webserver-deployment-5575796f8f-6rbcl: {kubelet 2884k8s000} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "cb4c4d0e705d57ac9da1eae9a42e2bb421dca03484fa8e0260672425feb55f15": unexpected end of JSON input
Jan 29 06:41:25.617: INFO: At 2021-01-29 06:37:10 +0000 UTC - event for webserver-deployment-5575796f8f-dtc4x: {kubelet 2884k8s000} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a20980651ba231f652be02984d594aa661c613d440b8dd740d4073f2bfa4d50b": unexpected end of JSON input
Jan 29 06:41:25.617: INFO: At 2021-01-29 06:37:10 +0000 UTC - event for webserver-deployment-5575796f8f-jjdlr: {kubelet 2884k8s000} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "ba151015cc98dd643d424bf2eafaa71855fb4fb6b75fbb24bb4ea2616f964faf": unexpected end of JSON input
Jan 29 06:41:25.617: INFO: At 2021-01-29 06:37:10 +0000 UTC - event for webserver-deployment-5575796f8f-pst6x: {kubelet 2884k8s000} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "5f40817e69457ddc2b907adfd182969bea93f24e337c84675d578aaeb17d2eb1": unexpected end of JSON input

Containerd failed to create the pod:
E0129 06:38:50.213490    4316 remote_runtime.go:251] StartContainer "1054e8a1180749dbb37097a5f985003ca3afb2036099f5df05020a5a9053a4ac" from runtime service failed: rpc error: code = Unknown desc = failed to create containerd task: hcsshim::CreateComputeSystem 1054e8a1180749dbb37097a5f985003ca3afb2036099f5df05020a5a9053a4ac: context deadline exceeded
(extra info: {"Owner":"containerd-shim-runhcs-v1.exe","SchemaVersion":{"Major":2,"Minor":1},"Container":{"GuestOs":{"HostName":"pod-adoption"},"Storage":{"Layers":[{"Id":"7b371bd9-de2e-5dc3-ae86-4d3d0378f6c6","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\113"},{"Id":"d83ac863-b163-5ceb-95c5-ac65bf7a39e3","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\112"},{"Id":"fd86a0ef-4ae8-5be6-b6bd-9e46685ad393","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\110"},{"Id":"9b944c46-c035-5757-9412-5fecc883941a","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\109"},{"Id":"9dee6370-72a7-5b65-af00-e08eeeaa1ef7","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\108"},{"Id":"77c8d266-544f-5418-b4e9-f49715060db9","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\107"},{"Id":"fa4d9b3a-212e-5b70-a9e6-bb1412fd1e53","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\106"},{"Id":"cc368b4b-70a7-5da3-aff7-b91d843db78a","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\105"},{"Id":"b7023ad6-4285-5a05-8998-e1c9c6bc6e49","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\104"},{"Id":"9c171b78-a39b-5e34-873e-04ab1b164bb7","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\79"},{"Id":"75b3f965-edc8-5443-ac0b-77f329589f05","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\78"},{"Id":"bc445432-f548-5054-b865-43ca4d3a32af","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\77"},{"Id":"e1a4a38f-7885-56a7-898b-96c1ceaf5cd5","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\76"},{"Id":"51c30dea-6447-5859-a549-0801b0fbf76c","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\75"},{"Id":"defbcf4b-cdf1-5e89-8198-0fe14410cffc","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\74"},{"Id":"b4e8aa06-2c0c-5738-80d8-af374eba772e","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\73"},{"Id":"59bb3c04-8829-58cb-ab1c-0aef684466cf","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\72"},{"Id":"a2ee96d5-66f6-5a9b-b0d4-384112c9e269","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\71"},{"Id":"2f347625-13a3-5633-badb-6868ea928ff9","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\70"},{"Id":"b03a06fa-412f-5917-a1f1-657de8a3bcc3","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\69"},{"Id":"83621030-7522-570b-ab7c-cf9c5898f09c","Path":"C:\\ProgramData\\containerd\\root\\io.containerd.snapshotter.v1.windows\\snapshots\\62"}],"Path":"\\\\?\\Volume{f8cd70db-970c-40de-aaaf-c07998d35301}\\"},"MappedDirectories":[{"HostPath":"c:\\var\\lib\\kubelet\\pods\\8cacd155-a5f4-4c8a-b73c-9d3eb47469be\\containers\\pod-adoption\\c6e401e7","ContainerPath":"c:\\dev\\termination-log"},{"HostPath":"c:\\var\\lib\\kubelet\\pods\\8cacd155-a5f4-4c8a-b73c-9d3eb47469be\\volumes\\kubernetes.io~secret\\default-token-tmjhm","ContainerPath":"c:\\var\\run\\secrets\\kubernetes.io\\serviceaccount","ReadOnly":true}],"Networking":{"Namespace":"36666c6e-cdde-4370-bfd1-a36911baa06a"}},"ShouldTerminateOnLastHandleClosed":true}): unknown

kubelet logs: https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd/1355027170874888192/artifacts/2884k8s000/
K8s reference issue: https://github.com/kubernetes/kubernetes/issues/98574
What you expected to happen:
The pods are created and network is set up
How to reproduce it:
We use the following aks-engine template:
https://raw.githubusercontent.com/kubernetes-sigs/windows-testing/master/job-templates/kubernetes_containerd_master.json
Orchestrator and Version (e.g. Kubernetes, Docker):
kubernetes 1.21 alpha
Containerd 1.4.3
Operating System (Linux/Windows):
Windows
Kernel (e.g. uanme -a for Linux or $(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion for Windows):
Microsoft Windows NT 10.0.17763.0
Source        Description      HotFixID      InstalledBy          InstalledOn

2884k8s000    Update           KB4578966                          10/13/2020 12:00:00 AM
2884k8s000    Security Update  KB4577667                          10/13/2020 12:00:00 AM
2884k8s000    Security Update  KB4586793     2884k8s000\azureuser 11/12/2020 12:00:00 AM
Anything else we need to know?:
[Miscellaneous information that will assist in solving the issue.]
This appears to be a transient issue.  The tests pass regularly: https://testgrid.k8s.io/sig-windows-releases#aks-engine-azure-windows-master-containerd
Unfortunately the logs for the cni with containerd end up in the wrong place, We made a fix to collect these but it hasn't been rolled out yet.

We are using azure cni v1.2.2.  We updated to this version for this fix: https://github.com/Azure/azure-container-networking/pull/755
/cc @abelhu

We are using azure cni v1.2.2.  We updated to this version for this fix: https://github.com/Azure/azure-container-networking/pull/755
/cc @abelhu

@jsturtevant  could you keep a cluster around next time this repros? Tried just now to repro with that aks-engine template but am getting the error:
"VM has reported a failure when processing extension 'cse-master-0'. Error message: "Enable failed: failed to execute command: command terminated with exit status=30\n[stdout]\nTue Mar 16 22:39:37 UTC 2021,k8s-master-31826720-0\n\n[stderr]\n"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot"

It is infrequent enough that it is tough to keep around since it runs in our CI.  You can find the logs for the last failure at https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd/1371779449283940352/artifacts/
Is there any chance if we move to a new version this would be fixed?

Any chance you could include azure-vnet.log* in those logs? Saw that you made a fix to collect them.
A new version would most likely not fix the issue, we have a hunch about where this error is coming from but a repro cluster or azure-vnet.log files will help us confirm that

looks like we are not collecting them properly, I will fix that and come back once it repos again.  Thanks for taking a look!

We ran into this error on a docker set up and have the logs:
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/101047/pull-kubernetes-e2e-aks-engine-windows-dockershim/1382477437496987648
Node logs: https://gcsweb.k8s.io/gcs/kubernetes-jenkins/pr-logs/pull/101047/pull-kubernetes-e2e-aks-engine-windows-dockershim/1382477437496987648/artifacts/3211k8s001/
kubelet logs:
E0415 00:12:03.779223    4804 cni.go:361] "Error adding pod to network" err="unexpected end of JSON input" pod="proxy-1266/agnhost" podSandboxID={Type:docker ID:1b26a44d1ff76beee4636d0eff169f9e86f165bacc03442ec13caeb01cde1849} podNetnsPath="none" networkType="azure-vnet" networkName="azure"
E0415 00:12:05.053625    4804 cni.go:361] "Error adding pod to network" err="unexpected end of JSON input" pod="secrets-9868/pod-secrets-c7d208cb-fbdc-4a8c-8513-deb65f3a8ac2" podSandboxID={Type:docker ID:647b2b42ce372f07237d37e3f544fc44f2d4dcb8064c8c3448e355dceb4a9183} podNetnsPath="container:c680bc6c2bc353912b4cff65b3f9ee7f134115ac4b63e9c14c85029890d014e4" networkType="azure-vnet" networkName="azure"
E0415 00:12:05.053625    4804 cni_windows.go:59] "Got error while adding to cni network" err="unexpected end of JSON input"
I0415 00:12:05.053625    4804 docker_sandbox.go:401] "Failed to read pod IP from plugin/docker" err="networkPlugin cni failed on the status hook for pod \"pod-secrets-c7d208cb-fbdc-4a8c-8513-deb65f3a8ac2_secrets-9868\": unexpected end of JSON input"

E0415 00:12:09.111571    4804 remote_runtime.go:116] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to set up sandbox container \"1b26a44d1ff76beee4636d0eff169f9e86f165bacc03442ec13caeb01cde1849\" network for pod \"agnhost\": networkPlugin cni failed to set up pod \"agnhost_proxy-1266\" network: unexpected end of JSON input"
E0415 00:12:09.111655    4804 kuberuntime_sandbox.go:68] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to set up sandbox container \"1b26a44d1ff76beee4636d0eff169f9e86f165bacc03442ec13caeb01cde1849\" network for pod \"agnhost\": networkPlugin cni failed to set up pod \"agnhost_proxy-1266\" network: unexpected end of JSON input" pod="proxy-1266/agnhost"
E0415 00:12:09.111655    4804 kuberuntime_manager.go:790] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to set up sandbox container \"1b26a44d1ff76beee4636d0eff169f9e86f165bacc03442ec13caeb01cde1849\" network for pod \"agnhost\": networkPlugin cni failed to set up pod \"agnhost_proxy-1266\" network: unexpected end of JSON input" pod="proxy-1266/agnhost"
E0415 00:12:09.111869    4804 pod_workers.go:190] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"agnhost_proxy-1266(c26fba48-d37e-4c71-ac5e-9fdeb6a782a0)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"agnhost_proxy-1266(c26fba48-d37e-4c71-ac5e-9fdeb6a782a0)\\\": rpc error: code = Unknown desc = failed to set up sandbox container \\\"1b26a44d1ff76beee4636d0eff169f9e86f165bacc03442ec13caeb01cde1849\\\" network for pod \\\"agnhost\\\": networkPlugin cni failed to set up pod \\\"agnhost_proxy-1266\\\" network: unexpected end of JSON input\"" pod="proxy-1266/agnhost" podUID=c26fba48-d37e-4c71-ac5e-9fdeb6a782a0

Azure vnet logs:
2021/04/15 00:12:02 [16100] [cni] Failed to lock store: timed out locking store.
2021/04/15 00:12:02 [16100] Failed to initialize key-value store of network plugin, err:timed out locking store.
2021/04/15 00:12:02 [16100] Report plugin error
2021/04/15 00:12:02 [16100] [Azure-Utils] Get-Process -Id 16100
2021/04/15 00:12:02 [16100] Read from Lock file:6996
2021/04/15 00:12:02 [16100] [Azure-Utils] Get-Process -Id 6996|Format-List
2021/04/15 00:12:02 [8076] [cni] Failed to lock store: timed out locking store.
2021/04/15 00:12:02 [8076] Failed to initialize key-value store of network plugin, err:timed out locking store.
2021/04/15 00:12:03 [8076] Report plugin error
2021/04/15 00:12:03 [8076] [Azure-Utils] Get-Process -Id 8076
2021/04/15 00:12:03 [8076] Read from Lock file:6996
2021/04/15 00:12:03 [8076] [Azure-Utils] Get-Process -Id 6996|Format-List
2021/04/15 00:12:03 [16100] Process is not running. Output:, Error exit status 1:Get-Process : Cannot find a process with the process identifier 6996.
At line:1 char:1
+ Get-Process -Id 6996|Format-List
+ ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (6996:Int32) [Get-Process], ProcessCommandException
    + FullyQualifiedErrorId : NoProcessFoundForGivenId,Microsoft.PowerShell.Commands.GetProcessCommand

2021/04/15 00:12:03 [16100] [CNI] Removing lock file as process holding lock exited
2021/04/15 00:12:03 [11216] Connected to telemetry service
2021/04/15 00:12:03 [11216] [cni-net] Plugin azure-vnet version v1.2.8.

@pjohnst5 thanks for bearing with us. Finally collecting the correct logs and have the repo here:
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-e2e-aks-engine-windows-containerd/1385422187535536128
kubelet logs:
Apr 23 03:26:22.164: INFO: At 2021-04-23 03:22:54 +0000 UTC - event for pod2: {kubelet 2726k8s001} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "620e1db49cbfe06e6b6db4fb887a23998523f2a8368e069efe525e96dafee7da": unexpected end of JSON input
Apr 23 03:26:22.164: INFO: At 2021-04-23 03:24:17 +0000 UTC - event for pod2: {kubelet 2726k8s001} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "9a0d72403a2e3f96a16431fbbcc36bbebc340ae6ca6248d0b76ac7089fe1d418": unexpected end of JSON input
Apr 23 03:26:22.164: INFO: At 2021-04-23 03:25:43 +0000 UTC - event for pod2: {kubelet 2726k8s001} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox

Full Node logs: https://gcsweb.k8s.io/gcs/kubernetes-jenkins/pr-logs/pull/101357/pull-kubernetes-e2e-aks-engine-windows-containerd/1385422187535536128/artifacts/2726k8s001/
Azure cni logs around the time of the error:
2021/04/23 03:25:57 [12052] [cni] reboot time 2021-04-23 03:05:38 +0000 UTC storeLockFile mod time 2021-04-23 03:20:45.0425544 +0000 UTC
2021/04/23 03:26:00 [3812] [cni] Failed to lock store: timed out locking store.
2021/04/23 03:26:00 [3812] Failed to initialize key-value store of network plugin, err:timed out locking store.
2021/04/23 03:26:00 [3812] Report plugin error
2021/04/23 03:26:00 [3812] [Azure-Utils] Get-Process -Id 3812
2021/04/23 03:26:02 [3812] Read from Lock file:10720
2021/04/23 03:26:02 [3812] [Azure-Utils] Get-Process -Id 10720|Format-List
2021/04/23 03:26:05 [3812] [CNI] Process name is azure-vnet
2021/04/23 03:26:05 [3812] Plugin store is nil
2021/04/23 03:26:05 [5084] Formatted Boot time: 2021-04-23 03:05:38
2021/04/23 03:26:05 [5084] [Azure-Utils] ver
2021/04/23 03:26:05 [5084] Formatted Boot time: 2021-04-23 03:05:38
2021/04/23 03:26:05 [5084] [cni] reboot time 2021-04-23 03:05:38 +0000 UTC storeLockFile mod time 2021-04-23 03:20:45.0425544 +0000 UTC
2021/04/23 03:26:20 [12988] [cni] Failed to lock store: timed out locking store.
2021/04/23 03:26:20 [12988] Failed to initialize key-value store of network plugin, err:timed out locking store.
2021/04/23 03:26:20 [12988] Report plugin error
2021/04/23 03:26:20 [12988] [Azure-Utils] Get-Process -Id 12988
2021/04/23 03:26:21 [12956] [cni] Failed to lock store: timed out locking store.
2021/04/23 03:26:21 [12956] Failed to initialize key-value store of network plugin, err:timed out locking store.
2021/04/23 03:26:21 [12956] Report plugin error
2021/04/23 03:26:21 [12052] [cni] Failed to lock store: timed out locking store.
2021/04/23 03:26:21 [12052] Failed to initialize key-value store of network plugin, err:timed out locking store.
2021/04/23 03:26:21 [12956] [Azure-Utils] Get-Process -Id 12956
2021/04/23 03:26:21 [12052] Report plugin error
2021/04/23 03:26:21 [12052] [Azure-Utils] Get-Process -Id 12052
2021/04/23 03:26:27 [12988] Read from Lock file:10720
2021/04/23 03:26:27 [12988] [Azure-Utils] Get-Process -Id 10720|Format-List
2021/04/23 03:26:27 [12956] Read from Lock file:10720
2021/04/23 03:26:27 [12956] [Azure-Utils] Get-Process -Id 10720|Format-List
2021/04/23 03:26:31 [12988] [CNI] Process name is azure-vnet
2021/04/23 03:26:31 [12988] Plugin store is nil
2021/04/23 03:26:31 [12052] Read from Lock file:10720
2021/04/23 03:26:31 [12052] [Azure-Utils] Get-Process -Id 10720|Format-List
2021/04/23 03:26:32 [5084] [cni] Failed to lock store: timed out locking store.
2021/04/23 03:26:32 [5084] Failed to initialize key-value store of network plugin, err:timed out locking store.
2021/04/23 03:26:32 [5084] Report plugin error
2021/04/23 03:26:32 [5084] [Azure-Utils] Get-Process -Id 5084
2021/04/23 03:26:32 [12956] [CNI] Process name is azure-vnet
2021/04/23 03:26:32 [12956] Plugin store is nil
2021/04/23 03:26:33 [12336] Formatted Boot time: 2021-04-23 03:05:38
2021/04/23 03:26:33 [12336] [Azure-Utils] ver
2021/04/23 03:26:36 [12336] Formatted Boot time: 2021-04-23 03:05:38
2021/04/23 03:26:36 [12336] [cni] reboot time 2021-04-23 03:05:38 +0000 UTC storeLockFile mod time 2021-04-23 03:20:45.0425544 +0000 UTC
2021/04/23 03:26:36 [12052] [CNI] Process name is azure-vnet
2021/04/23 03:26:36 [12052] Plugin store is nil
2021/04/23 03:26:36 [9864] Formatted Boot time: 2021-04-23 03:05:38
2021/04/23 03:26:36 [9864] [Azure-Utils] ver
2021/04/23 03:26:37 [6260] Formatted Boot time: 2021-04-23 03:05:38
2021/04/23 03:26:37 [6260] [Azure-Utils] ver
2021/04/23 03:26:37 [9864] Formatted Boot time: 2021-04-23 03:05:38
2021/04/23 03:26:37 [9864] [cni] reboot time 2021-04-23 03:05:38 +0000 UTC storeLockFile mod time 2021-04-23 03:20:45.0425544 +0000 UTC

Another set of logs here: https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd/1386603695029882880/

This occurred again today: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd/1389914005534937088

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd-1-21/1392291059656036352

There are two different issues happening.  The first one that has the error message
2021/04/15 00:12:02 [8076] Failed to initialize key-value store of network plugin, err:timed out locking store.
Is caused by a locking issue in HNS.  This should be resolved by including the following reg key: https://github.com/Azure/aks-engine/blob/4df58659df4a787c3cb954d02f38ed5964dda8af/vhd/packer/configure-windows-vhd.ps1#L302-L303
I will open a separate issue for the second issue

Upon looking at it and further discussion, we found that the logs from https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-aks-engine-azure-master-windows-containerd-1-21/1392291059656036352
Delete call where hcn throws error:
2021/05/12 02:19:52 [1356] [net] Deleting hcn endpoint with id: d3f5213b-abc6-4bea-8f1f-d3f3105a67ea
2021/05/12 02:19:52 [1356] [net] Failed to delete endpoint 1ab00986-eth0, err:Failed to remove hcn endpoint: d3f5213b-abc6-4bea-8f1f-d3f3105a67ea from namespace: c8d629dc-c5f5-4c91-8eb6-f79652d45254 due to error: hcnOpenNamespace failed in Win32: Element not found. (0x490) {"Success":false,"Error":"Element not found. ","ErrorCode":2147943568}.

One Delete call where hcn hangs:
2021/05/12 02:20:08 [1484] [net] Deleting hcn endpoint with id: bde45abd-00a6-4fe5-920a-1414b2ec23f0
2021/05/12 02:20:19 [8636] Formatted Boot time: 2021-05-12 01:42:35
2021/05/12 02:20:19 [8636] Formatted Boot time: 2021-05-12 01:42:35
2021/05/12 02:20:19 [8636] [cni] reboot time 2021-05-12 01:42:35 +0000 UTC store

We are seeing the same issue on our AKS cluster. The only difference is that we do NOT see HCN related hangs.
In our case, within a three and half window, we observed 46 times of such occurrence. We constantly spin up pods to process job so although the percentage may seems low, the sheer number of times this is happening is still alarming. PS in our environment, this is happening on windows node.
I do have the instruction to clean up if this is happening on Linux node, but no instruction to clean up for Windows nodes. Also I would like to find root cause and address it. It probably is not feasible to do manual clean up due to the frequency and time of day this is happening. Thanks!

Having the same issue. Some pods starts on the node and some don't.
We use calico as CNI and it worked perfectly on 1.19.7 and now I try to upgrade to 1.20.7 and I get the same issue.
@chrye what instructions do you have to clean this up on linux?

Having the same problem on AKS using cluster version 1.20.7 and Azure CNI plugin.
some pods start and some don't, and getting the same warning
Warning  FailedCreatePodSandBox  16s   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox

I managed to solve this, the problem for me was that I had both the calico CNI and linkerd at the same time.
The main problem was that linkerd started before calico did and even if it came online the CNI didn't understand that and pod restarts didn't solve the issue.
In our case we added a init container to linkerd that waited for the calico CNI to add it's conflist before linkerd could start.
https://github.com/linkerd/linkerd2/pull/5916
In short this error can mean many things but I hope this is a hint for someone else.
I would recommend to start to look in /host/etc/cni/net.d/and try to understand whats happening there.

After upgrading AKS to version 1.21.2 my pod creation problem was resolved.

@naeemdhby unfortunately I am not aware of Linux debugging instructions.
This issue is tracking Windows OS, could you open another issue to track Linux with details that you are seeing? Feel free to CC me and I'll ping the right people who could take a look.

We have identified one fix for a deadlock issue in HNS which is already checked into active branch, that could cause this. The fix needs to be backported to older OS releases.

Just to make sure, is the fix released for WS2019?

We are still observing this issue on Windows Server 2019.

KB5015880 is the cumulative update for Windows Server 2019 containing one fix. However, there could be other reasons that causes a similar error message.
We recommend Windows Server 2022 as it contains other fixes and improvements that are not included in Windows Server 2019.

@daschott updating to WS2022 is not an option for us I'm afraid, as we are using this in our test environment where we need to publish Docker images based on 1809, which isn't supported on 2022.

@daschott could you please provide an update on this issue? Has it been fixed on Server 2019? We will soon need to update our AKS to 1.23.x which was forcing us into these issues. Using 2022 is not an option for us, sadly.

👋🤖

If anyone is still experiencing this issue (or a similar one in another CNI module) the root cause for us was a daemon set pod that was constantly exiting/restarting on one particular node, with kubelet maxing out a CPU core. As the pod exited with code 0, it bypassed CrashLoopBackOff. After fixing this, we stopped seeing these errors (except immediately after a node reboot when similar conditions are present). Indeed this does seem to be a side effect of the load from Windows containers being restarted, and appears to affect other CSI drivers, so not sure this project is the right place for this issue.

@reopen Issue is still reproduced in our AKS with windows nodes.


install required bundler on travis

Travis CI is currently failing on ruby 2.3.0 due to missing the required
version of bundler. Therefore we install the required version of bundler
before the install step runs 'bundle install'.

Did not fix the problem


relp rebind feature

Description
currently relp connections use a persistent connection that is once established and will only be established on an error. this is good performance wise for lsh_01 but for balancing queues relp server that receives data this is not sufficient.
Use case or motivation behind the feature request
in case multiple lsh_01 instances end up into a single relp server by a network load balancer bad decisions, this will cause the said relp server to receive all the traffic and rest of the load balancer target servers none and therefore the performance will be degraded.
Related issues

Additional context

kin_02 might have this implemented with rlp_01


SessionCreatedEvent not fired correctly

When using the org.springframework.session.web.http.SessionEventHttpSessionListenerAdapter in combination with a HttpSessionListener, the SessionCreatedEvent is not captured. The SessionDestroyedEvent works fine.

Add relevant test
Add documentation on how to configure a SessionEventHttpSessionListenerAdapter and how to use HttpSessionListener.

Merged to main using 92798da3f8c2154dc0a3147cc08c7bab72eeac1f


OPID Monitoring BugFixes

Fix issue when opids may have been cleared from node but not pool.
Do not increase opid count when executing as another app may have created an operation.

This needs more testing for the added invalid address handling in payment processor.
Clone patch-15 branch for testing on testnet or on mainnet if you are brave :)

@hellcatz how will this work with pplnt? will the shares end up being removed since that address didn't actually mine the round?

Yes, the shares will be "reduced" but still converted to the "invalidAddress" in config.


Sometimes tabline shows buffer is modified when it's not

I use different colors in tabline for modified buffers. Sometimes I modify something on the buffer and the color changes fine. But when I save the buffer, it doesn't change to normal.
I have following in my airline theme:
let g:airline#themes#ronakg#palette.tabline = {
            \ 'airline_tab': ['#eeeeee', '#005f87' , 255, 31, '' ],
            \ 'airline_tabfill': ['#eeeeee', '#005f87' , 255, 237, '' ],
            \ 'airline_tabsel': ['#eeeeee', '#005f87' , 24, 255, '' ],
            \ 'airline_tabmod':  [ '#eeeeee' , '#005f87' , 255, 160, '' ],
            \ 'airline_tabmod_unsel':  [ '#eeeeee' , '#005f87' , 255, 167, '' ],
            \ }

Is this reproducible?

It also happens with official dark theme. But I cannot always reproduce it.
I opted to set modified detection to zero.

There have been reports like that in the past. However since this seems to be so unreliably and I haven't noticed it, I can't fix it. Note, I fixed a similar bug that involved switching tabs about a month ago. So please make sure you are using the latest versions.

I'll keep this open, so hopefully someone can report here reproducible instructions.

It improved with commit #1047.
Yes. I have latest version.

Yes, it's reproducible. Let me know what logs should I collect.

These are the steps I follow to reproduce the issue.

Open buffer 1
Open buffer 2
Switch to buffer 1, modify it. Undo.
Airline now thinks buffer 1 is modified.
Switch to buffer 2, buffer 1 switches to normal.
Modify buffer 2. Undo. Problem is not seen here.

My vim setup is here - https://github.com/ronakg/dotfiles

One more data point - I change the background color of mode section on statusline too based on buffer's status. That seems to be working fine, it doesn't think that the buffer is modified when it's not.

I also have the same problem, I could reproduce the problem by:

insert a new line, bufferline color changed(in my case: from grey -> yellow) and + symbol append at the end of the filename.
undo the change with u, + symbol disappear but the color remains the same(yellow).
If I switch to another buffer and then switch back, then the color reset to grey as it is expected

or:

search anything with easy-motion, color of buffer changed(grey->yellow)
switch to another buffer and switch back could reset the color

I'm able to the reproduce issue with @ronakg 's steps, but only when editing Go files with vim-go plugin enabled. With any other filetype, or without vim-go, airline sets the correct color.

Everybody who has the problem, can you please check PR #1057 and report back? Thanks!

@illicium Thanks for the patch, let's see if this fixes the problem for the people affected.

PR #1057 solved my issue, thanks :+1:

It's all good now. Thanks.


Update flake nixpkgs revision

Newer nixpkgs revisions need GST_PLUGIN_SYSTEM_PATH_1_0 set. Keeping stuff working with the latest nixpkgs helps with packaging and getting mesa versions to match.

oh so this was the reason it didnt find with newer versions? where did u find this btw?


Make Domains to Cache configurable

Make domains to cache configurable via ENV. The implements the framework to also limit caching to certain prefixes to the path.

What is still required is some testing and I'd like to revisit the way we talk to the CH hosts.
See: https://github.com/replicate/cluster/pull/1284 <-- This needs work to use current L2 cache, It is an example of how it could work straight to origin.
This allows us to send the URI as:
/r8//path which means we only need to update the map or in some cases the rewrite rule to enable more domains (and it could cache any domain not just GCS with ease).

This PR is missing prefix matching tests. I would also like to consider not setting a default in GetDomtainsToCache. Also GetDomainsToCache is a bad function name, I'd like it to be CacheDomains to match the option.

Texts still need to be fixed. Additionally work to warm the cache using the new scheme will be needed prior to releasing this


resetForm not working

in chrome v46,int resetForm()  function unhighlight is no work,not remove errorClass.
I tracked on line 468 the elements  variable is an object,this should be the Array of it.
http://jsfiddle.net/1t5nzoq2/

Thanks for reporting.
Just to make sure we are talking about the same problem:

open http://jsfiddle.net/1t5nzoq2/
click SAVE
click RESET
-> expected: the form should render as on the initial page load
-> actual: form control still has red borders and label still are rendered in red color
Can you confirm that?

I get the same problem in FF43. Are you willing to provide a failling unit test?

Update: I just found a typo in your Fiddle which seems to be the culprit.
fixed version at http://jsfiddle.net/1t5nzoq2/
this
    unhighlight: function (element, errorClass) {
        $(element).closest('.control-group').removeClass(errorClass).removeClass('has-success');
    },

should be
    unhighlight: function (element, errorClass) {
        $(element).closest('.form-group').removeClass(errorClass).removeClass('has-success');
    },

fixed version at http://jsfiddle.net/1t5nzoq2/

should be this instead: http://jsfiddle.net/1t5nzoq2/1/

whatever ;-)

Sorry,My issue is found to appear in the model of the form, and then found that the general form of the page is the case, I think that both sides are the same, so ...
Please see my latest code,http://jsfiddle.net/1t5nzoq2/3/

open modal
click save button
close modal
open modal again

form control still has red borders and label still are rendered in red color.

@chaodongyue it is just a missconfiguration.
The modal event you are using only executes after the modal components are already hidden.
So for your validation to work, you have two alternatives:

Instead of using the modal event "hidden.bs.modal", use "hide.bs.modal";
Or overwrite the ignore property with an empty string to the validation configuration, see the code http://jsfiddle.net/1t5nzoq2/5/;

@staabm I don't know if this would be a bug or not, but shouldn't the validation message also be kept, since the ignore property is filtering the input that is hidden?

@dkrahn  Thank you very much, I finally know what happened


Ghost Sonos speakers appearing - advise please

Issue

Hi there. So I recently gave away 3 older Sonos speakers.
They disappeared from my Sonos System (when logging into my account online) after they were activated by the friends I gave them to. So In the Sonos app and online in my Sonos account those speakers are gone.
HOWEVER in the hoops plugin they still appear. I have even uninstalled and reinstalled the plugin.
Hoping for some guidance (or) for the ability to tell it to ignore certain speakers.
Appreciate any feedback you can give me.
Log Messages

Debug Files

Try power-cycling all your zone players and after that restarting Homebridge.

To clarify, I should turn them all off and then turn them all back on or power cycle of them one at a time?Sent from my iPhoneOn May 5, 2023, at 5:30 PM, Erik Baauw @.***> wrote:
Try power-cycling all your zone players and after that restarting Homebridge.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Shouldn’t matter.

I basically killed the power to all of the rooms waited five minutes and turned all the power back onThis also rebooted the Home bridgeNo change the legacy three speakers are still there? :(Sent from my iPhoneOn May 5, 2023, at 5:50 PM, Erik Baauw @.***> wrote:
Shouldn’t matter.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Any thoughts?

On May 5, 2023, at 5:50 PM, Erik Baauw @.***> wrote:
Shouldn’t matter.
—
Reply to this email directly, view it on GitHub https://github.com/ebaauw/homebridge-zp/issues/205#issuecomment-1536821059, or unsubscribe https://github.com/notifications/unsubscribe-auth/APXMKNHWK6KQH7V5JXCEED3XEVY4HANCNFSM6AAAAAAXXSSPM4.
You are receiving this because you authored the thread.

I have even uninstalled and reinstalled the plugin.

Did you start Homebridge without the plugin installed?  If not, the ghost zone players might be left behind in cachedAccessories.

Beware that if you do that, all your HomeKit ZP accessories with be reset, losing any associations to HomeKit rooms, groups, scenes, and automations.  The Homebridge UI allows you to remove individual accessories from cachedAccessories.

Any chance you can send me a link wit a little more info on how to do that - thats what I have been looking for but haven’t seen anything like that.
Also THANK you so much for your guidance and assistance.

On May 8, 2023, at 2:35 PM, Erik Baauw @.***> wrote:
Beware that if you do that, all your HomeKit ZP accessories with be reset, losing any associations to HomeKit rooms, groups, scenes, and automations. The Homebridge UI allows you to remove individual accessories from cachedAccessories.
—
Reply to this email directly, view it on GitHub https://github.com/ebaauw/homebridge-zp/issues/205#issuecomment-1538852413, or unsubscribe https://github.com/notifications/unsubscribe-auth/APXMKNDCDDPLVXCRGLFJUVDXFE4HXANCNFSM6AAAAAAXXSSPM4.
You are receiving this because you authored the thread.

It's Manage Cached Accessories under Homebridge Settings.  You need a standard Homebridge installation managed by the UI to see that option.

Thanksjust to be clear the whole cache it will rebuild based on what it can find right?Sent from my iPhoneOn May 8, 2023, at 8:35 PM, Erik Baauw @.***> wrote:
It's Manage Cached Accessories under Homebridge Settings.  You need a standard Homebridge installation managed by the UI to see that option.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

This worked! Thank you. Sent from my iPhoneOn May 8, 2023, at 8:35 PM, Erik Baauw @.***> wrote:
It's Manage Cached Accessories under Homebridge Settings.  You need a standard Homebridge installation managed by the UI to see that option.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


chore, refactor(egen): tpuv5e_gemma_peft_finetuning_and_serving notebook fix

Following are the changes included in this PR:

adds colab enterprise
removes boiler plate
fixes according to template
changes region to location
edits future tense appropriately.

REQUIRED: Fill out the below checklists or remove if irrelevant

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[ ] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

If you are opening a PR for Community Notebooks under the notebooks/community folder:

[ ] This notebook has been added to the CODEOWNERS file under the Community Notebooks section, pointing to the author or the author's team.
[ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

If you are opening a PR for Community Content under the community-content folder:

[ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
[ ] The main content directory has been added to the CODEOWNERS file under the Community Content section, pointing to the author or the author's team.
[ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

/gcbrun

/gcbrun

This notebook is erroring at the kaggle dataset access with the following error
"You don't have permission to access resource at URL: https://www.kaggle.com/models/keras/gemma/keras/gemma_2b_en/2"


Spelling fix #971

Signed-off-by: Zoheb Ahmed<EMAIL_ADDRESS>Description
This PR fixes #971
Signed commits

[x] Yes, I signed my commits.

Thank you @oneknucklehead


TypeError: Cannot read property 'id' of null

Seeing many errors like below, as Walt user at ToT. Believe this error has been around for at least a week or two.
Uncaught (in promise) TypeError: Cannot read property 'id' of null
    at CollectionProxy._processUpdate (storage-proxy.js:248)
    at CollectionProxy._processUpdates (storage-proxy.js:164)
    at CollectionProxy._onUpdate (storage-proxy.js:147)
    at callback (storage-proxy.js:81)
    at PECInnerPort.ParticleExecutionContext._apiPort.onSimpleCallback (particle-execution-context.js:67)
    at PECInnerPort._handle (api-channel.js:178)
    at MessagePort.APIPort._port.onmessage (api-channel.js:90)
_processUpdate @ storage-proxy.js:248
_processUpdates @ storage-proxy.js:164
_onUpdate @ storage-proxy.js:147
callback @ storage-proxy.js:81
ParticleExecutionContext._apiPort.onSimpleCallback @ particle-execution-context.js:67
_handle @ api-channel.js:178
APIPort._port.onmessage @ api-channel.js:90

At https://github.com/PolymerLabs/arcs/blob/master/runtime/particle-execution-host.js#L57 an event structure is expected that is {handle, data: {value, keys}, particleId}
However, at https://github.com/PolymerLabs/arcs/blob/master/runtime/storage-proxy.js#L312 the data object is constructed like so  let data = {id, keys};
I believe value in the former is intended to match id in the latter, but the expansions don't match.

I intended to pass id as id. So the bug is in particle-execution-host. There's a test that covers storage-proxy doing the right thing, but no tests invoked that logic in particle-execution-host 😞


Roll Flutter Engine from b4b4c15d3a60 to 57cbf08589df (2 revisions)

https://github.com/flutter/engine/compare/b4b4c15d3a60...57cbf08589df
2023-02-23<EMAIL_ADDRESS>Roll Skia from 1b2d815e9778 to fff6c987d803 (2 revisions) (flutter/engine#39823)
2023-02-23<EMAIL_ADDRESS>Roll Skia from a321a8750271 to 1b2d815e9778 (5 revisions) (flutter/engine#39821)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC chinmaygarde@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


TaskChain fix

fixes #5847

@amaltaro, Alan,  please review (still need to be tested).

Ok, this patch touches quite a lot of the base common code, we need to be careful merging it.
Seangchan, are all these changes really needed to fix the real problem? For example, why do we need to build the full (un)mergedLFN? Why do we care about runs?
Sorrry, I'm just scared of pushing these changes to testbed without having it in private machines first :-(

Hi Alan, Actually the code in WMCore is not really broken. However it assumes set the acquisition era to set like this,
"AcquisitionEra" : {"Task1" :  "acquision1",  "Task1" :  "acquision1" }

That should set AcquisitionEra correctly in creation time. However, I think it is not good to set that way.
The rule I implied is, if lower level value is not set, select parent value. other wise select whatever it is set in the spec for that task.
The change seems a lot but mostly moving the function to task level from workflow level, so it will allow the properties by task if the different task has different values for that property.
Yes I agree that we shouldn't merge this before we test in vm. I am updating the code in reqmgr2-dev.cern.ch

What is the different between setupGeneratorTask and setupTask methods.
The reason I asked whether LumiList value need to be set for both or setupTask, it seems currently set in setupTask

Yes, it makes sense to move to task level. About setupGeneratorTask, it creates a task without input dataset, like MC from scratch, usually the first task of a TaskChain request, but not always the case.

Yes, it makes sense to move to task level. About setupGeneratorTask, it creates a task without input dataset, like MC from scratch, usually the first task of a TaskChain request, but not always the case.

So we don't need the lumi mask for that, right? But is it ok to move the setLumiMask outside the setTask?
It looks more general and lumi mask is only controlled by the parameter regard less the type of the Task.

Exactly, we don't need lumiMask for setupGenerator. If the parameter is provided inside tasks, doesn't it make more sense to setup lumiMask inside the tasks?
LumiList parameter can also be provided in the main dict (outside tasks), but maybe we can simply drop that...

My tired eye cannot see anymore problems here :) Let me know when you have the final version in a VM and agent, so I can fire a bunch of requests for the weekend.

You are right, I moved the setting up inside the setupTask. Also update the code in reqmgr2-dev.cern.ch
Feel free to make a request and test. Thanks,

To check,
First, we need to created request but not assigned first.
 I thought your are taking a rest. :smile: Don't have to run it now.  Enjoy the weekend.

So far so good. A TaskChain workflow created without any complaints. Now a bunch assigned.
... and now, time to chill out :)

Ok, test workflows successfully ran without any apparent issues. Thanks!

Thanks Alan for testing.


Licensing clarification: igh ethercat userspace library is LGPL

From the documentation:
https://gitlab.com/etherlab.org/ethercat/-/jobs/artifacts/stable-1.5/raw/documentation/ethercat_doc.pdf?job=documentation
1.2 License
The master code is released under the terms and conditions of the GNU General Public
License (GPL [4]), version 2. Other developers, that want to use EtherCAT with Linux
systems, are invited to use the master code or even participate on development.
To allow static linking of userspace application against the master’s application inter-
face (see chapter 3), the userspace library (see section 7.2) is licensed under the terms
and conditions of the GNU Lesser General Public License (LGPL [5]), version 2.1.

Thanks for the pointer, should be fixed now.


Implement TLS 1.3 ciphers

This PR fixes the current issue of missing ciphers when Caddy is configured with TLS 1.3 enabled after compiling it against the latest commit:
● caddy.service - Caddy HTTP/2 web server
   Loaded: loaded (/etc/systemd/system/caddy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2019-02-26 07:22:32 CET; 16min ago
     Docs: https://caddyserver.com/docs
  Process: 11181 ExecStart=/usr/local/bin/caddy -agree -email<EMAIL_ADDRESS>-http2 -log /opt/caddy/log -root /opt/caddy/webroot -conf /opt/caddy/Caddyfile (code=exited, status=1/FAILURE)
 Main PID: 11181 (code=exited, status=1/FAILURE)
      CPU: 23ms

Feb 26 07:22:32 debian systemd[1]: Started Caddy HTTP/2 web server.
Feb 26 07:22:32 debian caddy[11181]: 2019/02/26 07:22:32 /opt/caddy/snippets/ecc-tls-wildcard:6 - Error during parsing: Wrong cipher name or cipher not supported: 'TLS13-AES-128-GCM-SHA256'
Feb 26 07:22:32 debian systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Feb 26 07:22:32 debian systemd[1]: caddy.service: Unit entered failed state.
Feb 26 07:22:32 debian systemd[1]: caddy.service: Failed with result 'exit-code'.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Is there a reason, you haven't put CHACHA20 Cipher to first position under "nonAESNI"?
AFAIK, non AESNI devices benefit from this one specifically.

@Henrocker I copied the changes directly from your patch, haha. :-P
https://hnrk.io/md/caddy.patch

Is there a reason, you haven't put CHACHA20 Cipher to first position under "nonAESNI"?
AFAIK, non AESNI devices benefit from this one specifically.

Good catch! I forgot to copy over that change from your patch when I first created my PR. I just pushed a commit to fix the order of non-AESNI ciphers.

@mholt Caddy can't be launched if you compile it from the current master branch, so it would be cool if you could merge this PR asap.

// CipherSuites is a list of supported cipher suites for TLS versions up to
// TLS 1.2. If CipherSuites is nil, a default list of secure cipher suites
// is used, with a preference order based on hardware performance. The
// default cipher suites might change over Go versions. Note that TLS 1.3
// ciphersuites are not configurable.

https://github.com/golang/go/issues/29349

@elcore Why did you close the PR? These changes are necessary in order for Caddy to support TLS 1.3. Please read the error message I posted.

@whalehub You cannot configure TLS 1.3 ciphers! Please read the Go documentation I have provided you from crypto/tls

@elcore I read it. Now please read my PR. Caddy's TLS 1.3 feature does not work if you do not include the code from this PR.

@elcore Oh, I see what you mean now. The TLS 1.3 ciphers have to be removed from the Caddyfile if you want TLS 1.3 to work with the current master branch.

The problem is that you write TLS13-AES-128-GCM-SHA256 in your Caddyfile.
But caddy doesn't recognize that value.
With this PR, caddy will recognize the cipher name and it will run with your Caddyfile.
But the cipher configuration doesn't work.
So please don't add TLS 1.3 ciphers in ciphers option in your Caddyfile.

Let's break down your error message Error during parsing: Wrong cipher name or cipher not supported: 'TLS13-AES-128-GCM-SHA256'
Error during parsing:

We have an error during parsing

Wrong cipher name or cipher not supported

You cannot add TLS13-AES-128-GCM-SHA256 as it is not part of SupportedCiphersMap

You cannot configure TLS 1.3 ciphers with Go 1.12. Thus it does not make sense to add TLS 1.3 ciphers to your Caddyfile are they are non configurable.,
This does not work:
tls.Config{
	CipherSuites: []uint16{tls.TLS_AES_256_GCM_SHA384},
	MinVersion:   tls.VersionTLS13,
}

I see you have edited/deleted your old comment.


What are the meaning of POSMAP_FIX_RATE, OFFSET_FIX_RATE, NME.rate ?

POSMAP_FIX_RATE OFFSET_FIX_RATE:
https://github.com/MCG-NJU/SADRNet/blob/8c0741713bd2ae5c66506659a5b0ae5c99cacc9a/src/configs/config_SADRN_v2_eval.py#L3-L4
NME.rate:
https://github.com/MCG-NJU/SADRNet/blob/a5e6fac904c66711a6e9457fc603bd7b6d348d21/src/model/loss.py#L67-L69

POSMAP_FIX_RATE and OFFSET_FIX_RATE are used to roughly scale the value to [0 , 1].
NME.rate was used to control the weights of loss items but no longer used now.


DBZ-5197 Add the Maven wrapper files generated by mvn wrapper:wrapper

In a project that uses Maven and often changes the required version, it might be easier to use Maven Wrapper (https://maven.apache.org/wrapper/) which allows you to pin the Maven version and lets users run Maven commands as usual by using ./mvnw which will download the right version of Maven automatically and execute with it.
We use the Gradle wrapper in all of our projects to great effect, it's nice that Maven has this option officially supported as well.
The relevant files can be generated with the command:
mvn wrapper:wrapper -Dmaven=3.8.4
Please close and disregard the ticket/PR if there is no intention to use it, but it can definitely make contributors' lives easier.

@alwaysbemark Thanks for the proposal. I, personally, do not use that but that does not mean it can be usefule for other contributors.


WIP callmemaybe refactoring

Don't spawn a separate thread for each connection.
Instead use one thread per safekeeper, that iterates over all connections and sends callback requests for them.

-Use tokio postgres to connect to the pageserver, to avoid spawning a new thread for each connection.

Mpsc changed to crossbeam due to
https://doc.rust-lang.org/nightly/std/sync/mpsc/struct.Receiver.html#known-issues

Thanks for the patch! I'll look into it tomorrow.


Endpoint page: improve formatting

Cherry-picked from #2906 (conflicts with that)
Partly addresses #2837 but does not resolve it

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against c1fe91ab677a1c572e16dd136984b668ec9fbf7f

This pull request introduces 1 alert when merging c1fe91ab677a1c572e16dd136984b668ec9fbf7f into 89ee5d1cb185334e95e97a3d29d18af3f08f3c54 - view on LGTM.com
new alerts:

1 for Unused variable, import, function or class

Comment posted by LGTM.com

Huh, I'm guessing it's preserving the scroll position after the navigation. Is that happening in #2906 too?

Staging app for #2906 isn't loading for me 🤔

I pushed some updates. Will see if it fixes Heroku.


Bump base-tech Kafka to 2.1.0

JIRA: https://jira.mesosphere.com/browse/DCOS-47818

Looks great :+1: :shipit:

Thanks for the reviews - we won't merge now as we want to merge with https://github.com/mesosphere/dcos-kafka-service/pull/387 in one go.

Thanks for the reviews - we won't merge now as we want to merge with #387 in one go.

@wavesoft said this is fine to merge! Nice job @mhrabovcin and thanks for reviews folks!


Dynamic image update is not working properly

Since<EMAIL_ADDRESS>is not possible to dynamically update an image.
Prerequisites:

Angular 13
<EMAIL_ADDRESS>
Steps

Clone the repo
Run the Angular application
Change the image by clicking on the links

Current behavior
The image changes only in the img tag and not in the ixImg directive tag
Expected behavior
The image should also change in the ixImg tag.

Hello!
Thank you for bringing this to our attention - we've made a note of the issue, and our team will be looking into it. We'll post any updates to this thread.

Any news for this bug ?
Does anyone have any suggestion to workaround the issue ?
Thanks in advance

Hey @pilomat - no updates as of yet as our team has been heads down on some other work lately. We are planning on looking into this soon after.
For now my best suggestion is to downgrade the library to v1.1.7 until we can look into this more.


Switch Component animation not working when using react-navigation on Android

Description
Switch animation is not working on toggle inside a screen using react-navigation on Android.
I'm not sure if this is the right place to report this problem (if the issue is in the Switch component code or React Navigation lib). I tried to take a look at the Switch code but I didn't even find where the animation occurs. I already created an Issue in https://github.com/react-navigation/react-navigation/issues/8658 (July 30), but still without a response.
React Native version:
I'm using Expo, so npx react-native info result is:
System:
    OS: Windows 10 10.0.18362
    CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
    Memory: 2.10 GB / 7.88 GB
  Binaries:
    Node: 12.14.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK: Not Found
    Windows SDK: Not Found
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-193.69<IP_ADDRESS>21437
    Visual Studio: Not Found
  Languages:
    Java: Not Found
    Python: Not Found
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz => 0.63.2
    react-native-windows: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

And expo diagnostics:
  Expo CLI 3.28.0 environment info:
    System:
      OS: Windows 10 10.0.18362
    Binaries:
      Node: 12.14.1 - C:\Program Files\nodejs\node.EXE
      Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
      npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
    IDEs:
      Android Studio: Version  <IP_ADDRESS> AI-193.69<IP_ADDRESS>21437
    npmPackages:
      expo: ^39.0.0 => 39.0.3
      react: 16.13.1 => 16.13.1
      react-dom: 16.13.1 => 16.13.1
      react-native: https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz => 0.63.2
      react-native-web: ~0.13.7 => 0.13.16
    Expo Workflow: managed

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Create a Screen using React Navigation lib.
Create a Switch
Toggle Switch

Expected Results
I expect Switch animation to work properly on toggle when using react-navigation.
Snack, code example, screenshot, or link to a repository:

Snack with navigation (bug)
Snack without navigation (ok)

Same issue here

Sorry to hear you're facing this. However, this doesn't look like a regression in React Native - you're saying that without the extra library, the core component behaves as you'd expect. I encourage you to follow up with the library's maintainer, possibly give them a ping on Discord/Twitter.

Ok. Anyway, thanks for the guidance  :smiley:

Hmmm.... I am using the React Navigation in my App, but I ain't using it where the switch animation is not working. I change the value, and there is no animation.
I won't be able to fill the issue now as I am filled with work, but this looks like (also?) a RN issue.


[Webhooks: ScaleHost] Scaling down multiple hosts is unsuccessful

Rancher Versions:
Server: Master
**Docker Version:**v1.13.1
**OS and where are the hosts located? (cloud, bare metal, etc):**Ubuntu, Cloud
**Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)**Single node
**Environment Type: (Cattle/Kubernetes/Swarm/Mesos)**Cattle
Steps to Reproduce:

Create a setup with multiple hosts and label test=value
Create a webhook to scale down host 2 hosts and label test=value with mostRecent/LeastRecent deleteOption
Execute the webhook

Results:
Only one host is deleted although the request is to delete 2 hosts
The request is directed to delete the same host twice instead of two different hosts.
Logs below:
time="2017-02-27T22:13:16Z" level=info msg="Deleting most recently created hosts"
time="2017-02-27T22:13:16Z" level=info msg="Deleting host 1h7"
time="2017-02-27T22:13:16Z" level=info msg="Deleting host 1h7"

Tested with master. Created a webhook to scale down mostRecent hosts by 3. All 3 recent hosts were deleted as expected.
time="2017-03-01T00:03:48Z" level=info msg="Listing webhooks"
time="2017-03-01T00:04:05Z" level=info msg="Deleting most recently created hosts"
time="2017-03-01T00:04:05Z" level=info msg="Deleting host 1h21"
time="2017-03-01T00:04:05Z" level=info msg="Deleting host 1h20"
time="2017-03-01T00:04:05Z" level=info msg="Deleting host 1h19"


Incorrect render after minimize and restore

When using tmux, the pane lines disappear after minimizing and restoring the command prompt window. I would expect the lines to remain. The workaround at the moment is to restart tmux. I'm not sure if this affects other programs as well.
Steps to reproduce:

tmux
ctrl+b, %
Minimize window
Restore window

Before:

After:

Version 1607 (OS Build 14393.10)

Other workaround is to use a better terminal like rxvt and an X server (or another solution is PuTTY + ssh, which is a little bit harder to set up working on startup, imo).  Here's a link to some instructions: https://github.com/Microsoft/BashOnWindows/issues/741#issuecomment-237325357

I do see that minimizing and restoring the console does corrupt tmux a bit (it places the cursor after any output which shifts the entire tmux display up by one).
Though, by default, C-r should redraw tmux, and looks to me like it fixes the issue for me. (it may be remapped in your .tmux.conf)
@pqvst Which font are you using? I've noticed another tmux pane separator bug that seems to be connected to the selected font, but more data would help me pin it down.

Ah, thanks for the C-r tip @zadjii-msft. I'm using Consolas. I tried switching to Courier New, but same problem there.

Thanks for the discussion.
Closing this issue since:

This issue has been fixed since it was originally posted
This is the WSL issues repo, but this is an issue in Console which has its own Console GitHub Repo
GitHub doesn't allow issues to be moved between repos, preserving posters' identity :(

If you have further asks/issues, please file new issues on our Console GitHub Repo.

@bitcrazed
sorry for getting this old pr up but the issue in the console repo is still open and not solved.
You said it has been fixed? If yes can you tell me how?
Thanks in regards

TBH I don't think this one was ever solved - I think Rich was just copy-pasting and bulk moving old issues from this repo.
If you have a current repro, I'm happy to help investigate over at the Console repo.


feat(templating) add ability to compose templates that are defined in the same html that composes them

In reference this associated stackoverflow question
I would like to propose that aurelia have the ability to compose templates that are defined in the same html that composes them.  This would be in contrast to the current restriction (correct me if I'm wrong) that composed templates must be defined in their own separate html file.
The proposed html could look like this, though I note there are plenty of other potential ways to do this:
<template>
    <template name="myTemplate">
        ${a-property-on-containers-binding-context}
    </template>

    <compose view="myTemplate"/>
</template>

PS -- I would be great if the containing bindingContext (including override) would be automatically, or at least easily, accessible to a template defined in this manner, that is, one that is defined as a "subtemplate" of another.

It sounds like a reasonable request.

Stale since 2016

Let's keep this open for now. It's a low priority but might be something we could do in vNext.


Update Documentation

as new PR has been merged so we need to update Documentation
1.Update Feature Descriptions: Add information about the newly merged features, explaining their functionality and usage. Ensure that all the new updates are covered clearly for users and developers.
2.Modify API Documentation: If the new PR involved backend changes or new routes, ensure those API endpoints are documented with details like request methods, parameters, and responses.
3.Update Setup Instructions: If the new changes affect installation, setup, or configuration processes, modify the documentation to reflect the new steps or requirements.
4.Add Screenshots or Examples: If the PR involves UI changes, include updated screenshots or usage examples to provide a visual guide for users.

I'll take this up, if it's still open.

Also just looked at the existing documentation. It can and should be better than what is currently obtainable. I'd even suggest moving the entire docs to a proper static site generator, like Mintlify.

@kenudeh, assigned! You can work on this....

That's great! I'll review the new PR you referenced to get an idea of everything.

Working on it already @danieltayal07


Update Auto rest specs for KeyVault

Update output folder path keyvault readme to match new directory structure for dataplane libraries.

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@dsgouda @shahabhijeet This PR is very specific to .NET folder structure. So, I am assigning this to you for review and approval.

@deepak, we will have to update our mapping in database and once we have done that, this is good to be merged.