wifi: esp_wifi_set_storage 1231 wifi is not init

I would like https://github.com/espressif/esp32-at/issues/6 to be read and reopened since it is NOT solved at all. That issue was closed out of irritation. Please try to compile and run this firmware with the latest esp-idf and fix the bug.

Hi @gokr ,
We have fix it,please try it again.If you have any problem,please feel free to let us know.Thanks.

Ok, I will try it, great!

Ok, now I have tested this and... well, yes, now it works but I have two other problems. First of all, in order to get "ready" I had to make the changes for the UART described here:
https://www.esp32.com/viewtopic.php?f=2&t=1103&hilit=AT+commands&start=40
...then when I do it all and "make monitor" it shows everything up to "ready" but when I type in "AT" etc it doesn't answer anything back.
However, if I then switch IDF_PATH to the old 2.0-rc1 - then it works just fine. So I am guessing something is off with "make monitor" in the submodule esp-idf?

@gokr
you do not need to switch back to older IDF for run "monitor"
if you use the actually IDF
monitor goes to simple_monitor
and the new monitor now is new
you can use
make simple_monitor
cause monitor is new and do just in time not support CR LF after send the command.
https://github.com/espressif/esp-idf/commit/02fdf8271de3a6db2ab9d4d6f023c160c84ebdbe
( scroll down to the comments )
@xcguang
AT Example now it runs like it must. thank you
best wishes
rudi ;-)

$ make monitor
MONITOR
--- idf_monitor on COM27 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:3464
load:0x40078000,len:7828
load:0x40080000,len:252
0x40080000: _WindowOverflow4 at ??:?
entry 0x40080034
0x40080034: _WindowOverflow4 at ??:?
I (43) boot: ESP-IDF v2.0-rc1-296-g02fdf82 2nd stage bootloader
I (44) boot: compile time 16:13:37
I (44) boot: Enabling RNG early entropy source...
I (64) boot: SPI Speed : 40MHz
I (77) boot: SPI Mode : DIO
I (89) boot: SPI Flash Size : 4MB
I (101) boot: Partition Table:
I (113) boot: ## Label Usage Type ST Offset Length
I (135) boot: 0 phy_init RF data 01 01 0000f000 00001000
I (159) boot: 1 ota_0 OTA app 00 10 00010000 000ea000
I (182) boot: 2 nvs WiFi data 01 02 000fa000 00016000
I (205) boot: 3 ota_1 OTA app 00 11 00110000 000ea000
I (228) boot: 4 otadata OTA data 01 00 001fd000 00003000
I (252) boot: End of partition table
I (265) boot: Disabling RNG early entropy source...
I (282) boot: Loading app partition at offset 00010000
I (1450) boot: segment 0: paddr=0x00010018 vaddr=0x00000000 size=0x0ffe8 ( 65512)
I (1450) boot: segment 1: paddr=0x00020008 vaddr=0x3f400010 size=0x19e78 (106104) map
I (1467) boot: segment 2: paddr=0x00039e88 vaddr=0x3ffb0000 size=0x02190 ( 8592) load
I (1497) boot: segment 3: paddr=0x0003c020 vaddr=0x40080000 size=0x00400 ( 1024) load
0x40080000: _WindowOverflow4 at ??:?
I (1520) boot: segment 4: paddr=0x0003c428 vaddr=0x40080400 size=0x1a70c (108300) load
I (1598) boot: segment 5: paddr=0x00056b3c vaddr=0x400c0000 size=0x00034 ( 52) load
I (1599) boot: segment 6: paddr=0x00056b78 vaddr=0x00000000 size=0x09490 ( 38032)
I (1615) boot: segment 7: paddr=0x00060010 vaddr=0x400d0018 size=0x78f08 (495368) map
0x400d0018: _stext at ??:?
I (1642) cpu_start: Pro cpu up.
I (1653) cpu_start: Single core mode
I (1667) heap_alloc_caps: Initializing. RAM available for dynamic allocation:
I (1690) heap_alloc_caps: At 3FFAE2A0 len 00001D60 (7 KiB): DRAM
I (1711) heap_alloc_caps: At 3FFBA6B0 len 00025950 (150 KiB): DRAM
I (1732) heap_alloc_caps: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (1753) heap_alloc_caps: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (1775) heap_alloc_caps: At 4009AB0C len 000054F4 (21 KiB): IRAM
I (1796) cpu_start: Pro cpu start user code
[0;32}I (1856) cpu_start: Starting scheduler on PRO CPU.
eMbeddedHome 2017
I (1868) uart: queue free spaces: 10
I (1906) wifi: wifi firmware version: 0b5b6e7
I (1906) wifi: config NVS flash: enabled
I (1906) wifi: config nano formating: disabled
I (1911) wifi: Init dynamic tx buffer num: 32
I (1912) wifi: wifi driver task: 3ffc3060, prio:23, stack:3584
I (1917) wifi: Init static rx buffer num: 10
I (1921) wifi: Init dynamic rx buffer num: 0
I (1925) wifi: Init rx ampdu len mblock:7
I (1928) wifi: Init lldesc rx ampdu entry mblock:4
I (1933) wifi: wifi power manager task: 0x3ffc8408 prio: 21 stack: 2560
I (1939) wifi: wifi timer task: 3ffc9488, prio:22, stack:3584
E (1945) phy_init: PHY data partition validated
I (1968) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0
I (1969) wifi: Init ampdu: 1
I (1969) wifi: Init ampdu: 1
I (1969) wifi: mode : sta (24:0a:c4:04:5c:8c) + softAP (24:0a:c4:04:5c:8d)
ready
--- idf_monitor (1.0) - ESP-IDF monitor tool
--- based on miniterm from pySerial
--- Ctrl+] Exit program
--- Ctrl+T Menu escape key, followed by:
--- Menu keys:
--- Ctrl+T Send the menu character itself to remote
--- Ctrl+] Send the exit character itself to remote
--- Ctrl+R Reset target board via RTS line
--- Ctrl+F Run 'make flash' to build & flash
--- Ctrl+A Run 'make app-flash to build & flash app

simple_monitor

$ make simple_monitor
--- forcing DTR inactive
--- forcing RTS inactive
--- Miniterm on COM27  115200,8,N,1 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun  8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:3464
load:0x40078000,len:7828
load:0x40080000,len:252
entry 0x40080034
[0;32mI (44) boot: ESP-IDF v2.0-rc1-296-g02fdf82 2nd stage bootloader[0m
[0;32mI (44) boot: compile time 16:13:37[0m
[0;32mI (45) boot: Enabling RNG early entropy source...[0m
[0;32mI (65) boot: SPI Speed      : 40MHz[0m
[0;32mI (78) boot: SPI Mode       : DIO[0m
[0;32mI (90) boot: SPI Flash Size : 4MB[0m
[0;32mI (102) boot: Partition Table:[0m
[0;32mI (114) boot: ## Label            Usage          Type ST Offset   Length[0m
[0;32mI (136) boot:  0 phy_init         RF data          01 01 0000f000 00001000[0m
[0;32mI (160) boot:  1 ota_0            OTA app          00 10 00010000 000ea000[0m
[0;32mI (183) boot:  2 nvs              WiFi data        01 02 000fa000 00016000[0m
[0;32mI (206) boot:  3 ota_1            OTA app          00 11 00110000 000ea000[0m
[0;32mI (229) boot:  4 otadata          OTA data         01 00 001fd000 00003000[0m
[0;32mI (253) boot: End of partition table[0m
[0;32mI (266) boot: Disabling RNG early entropy source...[0m
[0;32mI (283) boot: Loading app partition at offset 00010000[0m
[0;32mI (1450) boot: segment 0: paddr=0x00010018 vaddr=0x00000000 size=0x0ffe8 ( 65512) [0m
[0;32mI (1451) boot: segment 1: paddr=0x00020008 vaddr=0x3f400010 size=0x19e78 (106104) map[0m
[0;32mI (1468) boot: segment 2: paddr=0x00039e88 vaddr=0x3ffb0000 size=0x02190 (  8592) load[0m
[0;32mI (1498) boot: segment 3: paddr=0x0003c020 vaddr=0x40080000 size=0x00400 (  1024) load[0m
[0;32mI (1521) boot: segment 4: paddr=0x0003c428 vaddr=0x40080400 size=0x1a70c (108300) load[0m
[0;32mI (1599) boot: segment 5: paddr=0x00056b3c vaddr=0x400c0000 size=0x00034 (    52) load[0m
[0;32mI (1600) boot: segment 6: paddr=0x00056b78 vaddr=0x00000000 size=0x09490 ( 38032) [0m
[0;32mI (1616) boot: segment 7: paddr=0x00060010 vaddr=0x400d0018 size=0x78f08 (495368) map[0m
[0;32mI (1643) cpu_start: Pro cpu up.[0m
[0;32mI (1654) cpu_start: Single core mode[0m
[0;32mI (1668) heap_alloc_caps: Initializing. RAM available for dynamic allocation:[0m
[0;32mI (1691) heap_alloc_caps: At 3FFAE2A0 len 00001D60 (7 KiB): DRAM[0m
[0;32mI (1712) heap_alloc_caps: At 3FFBA6B0 len 00025950 (150 KiB): DRAM[0m
[0;32mI (1733) heap_alloc_caps: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM[0m
[0;32mI (1754) heap_alloc_caps: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM[0m
[0;32mI (1776) heap_alloc_caps: At 4009AB0C len 000054F4 (21 KiB): IRAM[0m
[0;32mI (1796) cpu_start: Pro cpu start user code[0m
[0;32}I (1857) cpu_start: Starting scheduler on PRO CPU.[0m
eMbeddedHome 2017
[0;32mI (1869) uart: queue free spaces: 10[0m
I (1907) wifi: wifi firmware version: 0b5b6e7
I (1907) wifi: config NVS flash: enabled
I (1907) wifi: config nano formating: disabled
I (1912) wifi: Init dynamic tx buffer num: 32
I (1913) wifi: wifi driver task: 3ffc3060, prio:23, stack:3584
I (1918) wifi: Init static rx buffer num: 10
I (1922) wifi: Init dynamic rx buffer num: 0
I (1926) wifi: Init rx ampdu len mblock:7
I (1929) wifi: Init lldesc rx ampdu entry mblock:4
I (1934) wifi: wifi power manager task: 0x3ffc8408 prio: 21 stack: 2560
I (1941) wifi: wifi timer task: 3ffc9488, prio:22, stack:3584
[0;31mE (1946) phy_init: PHY data partition validated[0m
[0;32mI (1969) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0[0m
I (1970) wifi: Init ampdu: 1
I (1970) wifi: Init ampdu: 1
I (1970) wifi: mode : sta (24:0a:c4:04:5c:8c) + softAP (24:0a:c4:04:5c:8d)
ready
AT+GMR
AT version:<IP_ADDRESS>(Mar 16 2017 19:02:43)
SDK version:v2.0-rc1-296-g02fdf82
compile time:Mar 17 2017 13:03:48
OK

Works


Improve look of prayer requests by changing how requests are split and styled.

The look of prayer requests (both on the index and show pages) could be greatly improved by changing the way that they are displayed when they're over or under 36 characters and need to be split or not to be split so that they fit on the page properly. We could lighten the color of the "..." continued symbols at the end of the header of a prayer request and we could also omit the continued symbols when the request is under 36 characters.
This issue serves as documentation of these changes.

Before and After Screenshot


New training dataset with saved model

Hi,
Would it affect the accuracy if I were to use a new training dataset with a saved model?
Let's say I have trained and saved a model with training dataset A.
Can I use a new training dataset B to resume training? Or should I always append new training data to dataset A and retrain everything?

The accuracy depends on how related are the domains A and B. If they are close, the performance will probably be high. If they are very different, the performance will likely decrease.
You can continue a training but changing the data. You should set the config.py for loading a model, set RELOAD_DATASET to False and change the TEXT_FILES (and/or optionally the DATA_ROOT_PATH) to point the new training data.

G

It may be a regular behavior. As the new domain is unknown by the model, it may cause the model to get "confused", increasing its loss.
However, this can also mask an irregular behaviour. You can test it by resuming the training with the same domain/dataset and observe whether there are these loss fluctuations.

I was actually resuming training with the same dataset and configurations..


[Solved] Bunch of erros on fresh installation via source using nodejs (as root user)

Node version:
nodejs 10.16.3
Steps Followed:
Install node.js
git clone https://github.com/bkimminich/juice-shop.git
cd juice-shop
npm install (only has to be done before first start or when you change the source code)
npm start
`npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>Critical vulnerability fix in v5.0.0. See https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/
npm WARN deprecated<EMAIL_ADDRESS>Security update: Versions below 3.0.0 are deprecated.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>use String.prototype.padStart()

<EMAIL_ADDRESS>install /opt/juice-shop/node_modules/iltorb
detect-libc prebuild-install || node-gyp rebuild

prebuild-install WARN install No prebuilt binaries found (target=10.16.3 runtime=node arch=x64 platform=linux)
make: Entering directory '/opt/juice-shop/node_modules/iltorb/build'
CC(target) Release/obj.target/iltorb/brotli/common/dictionary.o
CC(target) Release/obj.target/iltorb/brotli/dec/bit_reader.o
CC(target) Release/obj.target/iltorb/brotli/dec/decode.o
../brotli/dec/decode.c: In function ‘BrotliDecoderDecompressStream’:
../brotli/dec/decode.c:2013:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->state = BROTLI_STATE_METABLOCK_BEGIN;
~^~~~~~~~~~~~~~~~~~~~~~
../brotli/dec/decode.c:2015:7: note: here
case BROTLI_STATE_METABLOCK_BEGIN:
^~~~
../brotli/dec/decode.c:2018:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->state = BROTLI_STATE_METABLOCK_HEADER;
~^~~~~~~~~~~~~~~~~~~~~~~
../brotli/dec/decode.c:2020:7: note: here
case BROTLI_STATE_METABLOCK_HEADER:
^~~~
../brotli/dec/decode.c:2089:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->state = BROTLI_STATE_HUFFMAN_CODE_1;
~^~~~~~~~~~~~~~~~~~~~~
../brotli/dec/decode.c:2091:7: note: here
case BROTLI_STATE_HUFFMAN_CODE_1: {
^~~~
../brotli/dec/decode.c:2096:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->state = BROTLI_STATE_HUFFMAN_CODE_2;
~^~~~~~~~~~~~~~~~~~~~~
../brotli/dec/decode.c:2099:7: note: here
case BROTLI_STATE_HUFFMAN_CODE_2: {
^~~~
../brotli/dec/decode.c:2104:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->state = BROTLI_STATE_HUFFMAN_CODE_3;
~^~~~~~~~~~~~~~~~~~~~~
../brotli/dec/decode.c:2107:7: note: here
case BROTLI_STATE_HUFFMAN_CODE_3: {
^~~~
../brotli/dec/decode.c:2119:45: warning: this statement may fall through [-Wimplicit-fallthrough=]
case BROTLI_STATE_METABLOCK_HEADER_2: {
^
../brotli/dec/decode.c:2142:7: note: here
case BROTLI_STATE_CONTEXT_MODES:
^~~~
../brotli/dec/decode.c:2147:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->state = BROTLI_STATE_CONTEXT_MAP_1;
~^~~~~~~~~~~~~~~~~~~~
../brotli/dec/decode.c:2149:7: note: here
case BROTLI_STATE_CONTEXT_MAP_1:
^~~~
../brotli/dec/decode.c:2157:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->state = BROTLI_STATE_CONTEXT_MAP_2;
~^~~~~~~~~~~~~~~~~~~~
../brotli/dec/decode.c:2159:7: note: here
case BROTLI_STATE_CONTEXT_MAP_2:
^~~~
../brotli/dec/decode.c:2185:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->state = BROTLI_STATE_TREE_GROUP;
~^~~~~~~~~~~~~~~~~
../brotli/dec/decode.c:2187:7: note: here
case BROTLI_STATE_TREE_GROUP:
^~~~
../brotli/dec/decode.c:2281:18: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->state = BROTLI_STATE_DONE;
~^~~~~~~~~~~
../brotli/dec/decode.c:2283:7: note: here
case BROTLI_STATE_DONE:
^~~~
../brotli/dec/decode.c: In function ‘DecodeMetaBlockLength’:
../brotli/dec/decode.c:193:38: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_metablock_header = BROTLI_STATE_METABLOCK_HEADER_EMPTY;
~^~~~~~~~~
../brotli/dec/decode.c:196:7: note: here
case BROTLI_STATE_METABLOCK_HEADER_EMPTY:
^~~~
../brotli/dec/decode.c:204:38: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_metablock_header = BROTLI_STATE_METABLOCK_HEADER_NIBBLES;
~^~~~~~~~~~~
../brotli/dec/decode.c:207:7: note: here
case BROTLI_STATE_METABLOCK_HEADER_NIBBLES:
^~~~
../brotli/dec/decode.c:218:38: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_metablock_header = BROTLI_STATE_METABLOCK_HEADER_SIZE;
~^~~~~~~~
../brotli/dec/decode.c:221:7: note: here
case BROTLI_STATE_METABLOCK_HEADER_SIZE:
^~~~
../brotli/dec/decode.c:233:38: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_metablock_header =
~^
BROTLI_STATE_METABLOCK_HEADER_UNCOMPRESSED;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../brotli/dec/decode.c:237:7: note: here
case BROTLI_STATE_METABLOCK_HEADER_UNCOMPRESSED:
^~
../brotli/dec/decode.c:255:38: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_metablock_header = BROTLI_STATE_METABLOCK_HEADER_BYTES;
~^
../brotli/dec/decode.c:258:7: note: here
case BROTLI_STATE_METABLOCK_HEADER_BYTES:
^~
../brotli/dec/decode.c:267:38: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_metablock_header = BROTLI_STATE_METABLOCK_HEADER_METADATA;
~^~
../brotli/dec/decode.c:270:7: note: here
case BROTLI_STATE_METABLOCK_HEADER_METADATA:
^~
../brotli/dec/decode.c: In function ‘CopyUncompressedBlockToOutput’:
../brotli/dec/decode.c:1317:34: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_uncompressed = BROTLI_STATE_UNCOMPRESSED_WRITE;
~^~~~~
../brotli/dec/decode.c:1320:7: note: here
case BROTLI_STATE_UNCOMPRESSED_WRITE: {
^~~~
../brotli/dec/decode.c: In function ‘DecodeVarLenUint8’:
../brotli/dec/decode.c:139:10: warning: this statement may fall through [-Wimplicit-fallthrough=]
if (bits == 0) {
^
../brotli/dec/decode.c:145:5: note: here
case BROTLI_STATE_DECODE_UINT8_SHORT:
^~~~
../brotli/dec/decode.c:156:14: warning: this statement may fall through [-Wimplicit-fallthrough=]
value = bits;
~^~
../brotli/dec/decode.c:159:5: note: here
case BROTLI_STATE_DECODE_UINT8_LONG:
^~
../brotli/dec/decode.c: In function ‘ReadHuffmanCode’:
../brotli/dec/decode.c:703:12: warning: this statement may fall through [-Wimplicit-fallthrough=]
if (s->sub_loop_counter != 1) {
^
../brotli/dec/decode.c:715:7: note: here
case BROTLI_STATE_HUFFMAN_SIMPLE_SIZE:
^~~~
../brotli/dec/decode.c:721:29: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->sub_loop_counter = 0;
^
../brotli/dec/decode.c:723:7: note: here
case BROTLI_STATE_HUFFMAN_SIMPLE_READ: {
^~
../brotli/dec/decode.c:723:46: warning: this statement may fall through [-Wimplicit-fallthrough=]
case BROTLI_STATE_HUFFMAN_SIMPLE_READ: {
^
../brotli/dec/decode.c:731:7: note: here
case BROTLI_STATE_HUFFMAN_SIMPLE_BUILD: {
^~
../brotli/dec/decode.c:772:29: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_huffman = BROTLI_STATE_HUFFMAN_LENGTH_SYMBOLS;
^~~
../brotli/dec/decode.c:775:7: note: here
case BROTLI_STATE_HUFFMAN_LENGTH_SYMBOLS: {
^~~~
../brotli/dec/decode.c: In function ‘DecodeContextMap’:
../brotli/dec/decode.c:949:31: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_context_map = BROTLI_STATE_CONTEXT_MAP_READ_PREFIX;
^~~~~~~~~~~~~~
../brotli/dec/decode.c:951:5: note: here
case BROTLI_STATE_CONTEXT_MAP_READ_PREFIX: {
^~~~
../brotli/dec/decode.c:951:48: warning: this statement may fall through [-Wimplicit-fallthrough=]
case BROTLI_STATE_CONTEXT_MAP_READ_PREFIX: {
^
../brotli/dec/decode.c:969:5: note: here
case BROTLI_STATE_CONTEXT_MAP_HUFFMAN:
^~~~
../brotli/dec/decode.c:974:31: warning: this statement may fall through [-Wimplicit-fallthrough=]
s->substate_context_map = BROTLI_STATE_CONTEXT_MAP_DECODE;
^~~~~~~~~
../brotli/dec/decode.c:976:5: note: here
case BROTLI_STATE_CONTEXT_MAP_DECODE: {
^~~~
../brotli/dec/decode.c:976:43: warning: this statement may fall through [-Wimplicit-fallthrough=]
case BROTLI_STATE_CONTEXT_MAP_DECODE: {
^
../brotli/dec/decode.c:1024:5: note: here
case BROTLI_STATE_CONTEXT_MAP_TRANSFORM: {
^~~~
CC(target) Release/obj.target/iltorb/brotli/dec/huffman.o
CC(target) Release/obj.target/iltorb/brotli/dec/state.o
CC(target) Release/obj.target/iltorb/brotli/enc/backward_references.o
CC(target) Release/obj.target/iltorb/brotli/enc/backward_references_hq.o
CC(target) Release/obj.target/iltorb/brotli/enc/bit_cost.o
CC(target) Release/obj.target/iltorb/brotli/enc/block_splitter.o
In file included from ../brotli/enc/./block_splitter.h:14,
from ../brotli/enc/block_splitter.c:9:
../brotli/enc/./block_splitter_inc.h: In function ‘SplitByteVectorLiteral’:
../brotli/enc/./block_splitter_inc.h:403:61: warning: ‘’ in boolean context, suggest ‘&&’ instead [-Wint-in-bool-context]
double* insert_cost = BROTLI_ALLOC(m, double, data_size * num_histograms);
../brotli/enc/././memory.h:43:5: note: in definition of macro ‘BROTLI_ALLOC’
((N) ? ((T*)BrotliAllocate((M), (N) * sizeof(T))) : NULL)
^
../brotli/enc/./block_splitter_inc.h:405:62: warning: ‘’ in boolean context, suggest ‘&&’ instead [-Wint-in-bool-context]
uint8_t switch_signal = BROTLI_ALLOC(m, uint8_t, length * bitmaplen);
../brotli/enc/././memory.h:43:5: note: in definition of macro ‘BROTLI_ALLOC’
((N) ? ((T*)BrotliAllocate((M), (N) * sizeof(T))) : NULL)
^
../brotli/enc/./block_splitter_inc.h: In function ‘SplitByteVectorCommand’:
../brotli/enc/./block_splitter_inc.h:403:61: warning: ‘’ in boolean context, suggest ‘&&’ instead [-Wint-in-bool-context]
double insert_cost = BROTLI_ALLOC(m, double, data_size * num_histograms);
../brotli/enc/././memory.h:43:5: note: in definition of macro ‘BROTLI_ALLOC’
((N) ? ((T*)BrotliAllocate((M), (N) * sizeof(T))) : NULL)
^
../brotli/enc/./block_splitter_inc.h:405:62: warning: ‘’ in boolean context, suggest ‘&&’ instead [-Wint-in-bool-context]
uint8_t switch_signal = BROTLI_ALLOC(m, uint8_t, length * bitmaplen);
../brotli/enc/././memory.h:43:5: note: in definition of macro ‘BROTLI_ALLOC’
((N) ? ((T*)BrotliAllocate((M), (N) * sizeof(T))) : NULL)
^
../brotli/enc/./block_splitter_inc.h: In function ‘SplitByteVectorDistance’:
../brotli/enc/./block_splitter_inc.h:403:61: warning: ‘’ in boolean context, suggest ‘&&’ instead [-Wint-in-bool-context]
double insert_cost = BROTLI_ALLOC(m, double, data_size * num_histograms);
../brotli/enc/././memory.h:43:5: note: in definition of macro ‘BROTLI_ALLOC’
((N) ? ((T*)BrotliAllocate((M), (N) * sizeof(T))) : NULL)
^
../brotli/enc/./block_splitter_inc.h:405:62: warning: ‘’ in boolean context, suggest ‘&&’ instead [-Wint-in-bool-context]
uint8_t switch_signal = BROTLI_ALLOC(m, uint8_t, length * bitmaplen);
../brotli/enc/././memory.h:43:5: note: in definition of macro ‘BROTLI_ALLOC’
((N) ? ((T*)BrotliAllocate((M), (N) * sizeof(T))) : NULL)
^
CC(target) Release/obj.target/iltorb/brotli/enc/brotli_bit_stream.o
CC(target) Release/obj.target/iltorb/brotli/enc/cluster.o
CC(target) Release/obj.target/iltorb/brotli/enc/compress_fragment.o
CC(target) Release/obj.target/iltorb/brotli/enc/compress_fragment_two_pass.o
CC(target) Release/obj.target/iltorb/brotli/enc/dictionary_hash.o
CC(target) Release/obj.target/iltorb/brotli/enc/encode.o
CC(target) Release/obj.target/iltorb/brotli/enc/entropy_encode.o
CC(target) Release/obj.target/iltorb/brotli/enc/histogram.o
CC(target) Release/obj.target/iltorb/brotli/enc/literal_cost.o
CC(target) Release/obj.target/iltorb/brotli/enc/memory.o
CC(target) Release/obj.target/iltorb/brotli/enc/metablock.o
In file included from ../brotli/enc/././block_splitter.h:14,
from ../brotli/enc/./metablock.h:14,
from ../brotli/enc/metablock.c:10:
../brotli/enc/metablock.c: In function ‘ContextBlockSplitterFinishBlock’:
../brotli/enc/metablock.c:279:45: warning: ‘’ in boolean context, suggest ‘&&’ instead [-Wint-in-bool-context]
BROTLI_ALLOC(m, HistogramLiteral, 2 * num_contexts);
../brotli/enc/./././memory.h:43:5: note: in definition of macro ‘BROTLI_ALLOC’
((N) ? ((T)BrotliAllocate((M), (N) * sizeof(T))) : NULL)
^
CC(target) Release/obj.target/iltorb/brotli/enc/static_dict.o
CC(target) Release/obj.target/iltorb/brotli/enc/utf8_util.o
CXX(target) Release/obj.target/iltorb/src/common/allocator.o
In file included from ../src/common/allocator.cc:2:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type]
, reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
^
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/common/allocator.cc:2:
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:
/root/.node-gyp/10.16.3/include/node/node_object_wrap.h:84:78:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
CXX(target) Release/obj.target/iltorb/src/common/stream_coder.o
In file included from ../src/common/stream_coder.h:5,
from ../src/common/stream_coder.cc:1:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker)’:
../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type]
, reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
^
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/common/stream_coder.h:5,
from ../src/common/stream_coder.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:
/root/.node-gyp/10.16.3/include/node/node_object_wrap.h:84:78:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
CXX(target) Release/obj.target/iltorb/src/dec/stream_decode.o
In file included from ../src/dec/stream_decode.h:4,
from ../src/dec/stream_decode.cc:1:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker)’:
../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type]
, reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
^
../src/dec/stream_decode.cc: In constructor ‘StreamDecode::StreamDecode(v8::Localv8::Object)’:
../src/dec/stream_decode.cc:14:81: warning: ‘v8::Localv8::Object v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
Local dictionary = Nan::Get(params, key).ToLocalChecked()->ToObject();
^
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/dec/stream_decode.h:4,
from ../src/dec/stream_decode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:10046:15: note: declared here
Local Value::ToObject() const {
^~~~~
../src/dec/stream_decode.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE StreamDecode::New(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/dec/stream_decode.cc:40:58: warning: ‘v8::Localv8::Object v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
StreamDecode* obj = new StreamDecode(info[0]->ToObject());
^
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/dec/stream_decode.h:4,
from ../src/dec/stream_decode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:10046:15: note: declared here
Local Value::ToObject() const {
^~~~~
../src/dec/stream_decode.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE StreamDecode::Transform(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/dec/stream_decode.cc:48:44: warning: ‘v8::Localv8::Object v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
Local buffer = info[0]->ToObject();
^
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/dec/stream_decode.h:4,
from ../src/dec/stream_decode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:10046:15: note: declared here
Local Value::ToObject() const {
^~~~~
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:
/root/.node-gyp/10.16.3/include/node/node_object_wrap.h:84:78:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
CXX(target) Release/obj.target/iltorb/src/dec/stream_decode_worker.o
In file included from ../src/dec/stream_decode_worker.h:4,
from ../src/dec/stream_decode_worker.cc:1:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker)’:
../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type]
, reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
^
../src/dec/stream_decode_worker.cc: In member function ‘virtual void StreamDecodeWorker::HandleOKCallback()’:
../src/dec/stream_decode_worker.cc:46:27: warning: ‘v8::Localv8::Value Nan::Callback::Call(int, v8::Localv8::Value) const’ is deprecated [-Wdeprecated-declarations]
callback->Call(1, argv);
^
In file included from ../src/dec/stream_decode_worker.h:4,
from ../src/dec/stream_decode_worker.cc:1:
../../nan/nan.h:1740:3: note: declared here
Call(int argc, v8::Localv8::Value argv[]) const {
^~~~
../src/dec/stream_decode_worker.cc:52:27: warning: ‘v8::Localv8::Value Nan::Callback::Call(int, v8::Localv8::Value) const’ is deprecated [-Wdeprecated-declarations]
callback->Call(2, argv);
^
In file included from ../src/dec/stream_decode_worker.h:4,
from ../src/dec/stream_decode_worker.cc:1:
../../nan/nan.h:1740:3: note: declared here
Call(int argc, v8::Localv8::Value argv[]) const {
^~~~
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/dec/stream_decode_worker.h:4,
from ../src/dec/stream_decode_worker.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:
/root/.node-gyp/10.16.3/include/node/node_object_wrap.h:84:78:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
CXX(target) Release/obj.target/iltorb/src/enc/stream_encode.o
In file included from ../src/enc/stream_encode.h:4,
from ../src/enc/stream_encode.cc:1:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker)’:
../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type]
, reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
^
../src/enc/stream_encode.cc: In constructor ‘StreamEncode::StreamEncode(v8::Localv8::Object)’:
../src/enc/stream_encode.cc:14:62: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
val = Nan::Get(params, key).ToLocalChecked()->Int32Value();
^
In file included from /root/.node-gyp/10.16.3/include/node/v8.h:26,
from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/enc/stream_encode.h:4,
from ../src/enc/stream_encode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
^~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^~~~~~~~~~
../src/enc/stream_encode.cc:20:62: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
val = Nan::Get(params, key).ToLocalChecked()->Int32Value();
^
In file included from /root/.node-gyp/10.16.3/include/node/v8.h:26,
from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/enc/stream_encode.h:4,
from ../src/enc/stream_encode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
^~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^~~~~~~~~~
../src/enc/stream_encode.cc:26:62: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
val = Nan::Get(params, key).ToLocalChecked()->Int32Value();
^
In file included from /root/.node-gyp/10.16.3/include/node/v8.h:26,
from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/enc/stream_encode.h:4,
from ../src/enc/stream_encode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
^~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^~~~~~~~~~
../src/enc/stream_encode.cc:32:62: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
val = Nan::Get(params, key).ToLocalChecked()->Int32Value();
^
In file included from /root/.node-gyp/10.16.3/include/node/v8.h:26,
from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/enc/stream_encode.h:4,
from ../src/enc/stream_encode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
^~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^~~~~~~~~~
../src/enc/stream_encode.cc:44:62: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
val = Nan::Get(params, key).ToLocalChecked()->Int32Value();
^
In file included from /root/.node-gyp/10.16.3/include/node/v8.h:26,
from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/enc/stream_encode.h:4,
from ../src/enc/stream_encode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
^~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^~~~~~~~~~
../src/enc/stream_encode.cc:50:81: warning: ‘v8::Localv8::Object v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
Local dictionary = Nan::Get(params, key).ToLocalChecked()->ToObject();
^
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/enc/stream_encode.h:4,
from ../src/enc/stream_encode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:10046:15: note: declared here
Local Value::ToObject() const {
^~~~~
../src/enc/stream_encode.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE StreamEncode::New(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/enc/stream_encode.cc:76:58: warning: ‘v8::Localv8::Object v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
StreamEncode* obj = new StreamEncode(info[0]->ToObject());
^
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/enc/stream_encode.h:4,
from ../src/enc/stream_encode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:10046:15: note: declared here
Local Value::ToObject() const {
^~~~~
../src/enc/stream_encode.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE StreamEncode::Transform(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/enc/stream_encode.cc:84:44: warning: ‘v8::Localv8::Object v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
Local buffer = info[0]->ToObject();
^
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/enc/stream_encode.h:4,
from ../src/enc/stream_encode.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h:10046:15: note: declared here
Local Value::ToObject() const {
^~~~~
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:
/root/.node-gyp/10.16.3/include/node/node_object_wrap.h:84:78:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
CXX(target) Release/obj.target/iltorb/src/enc/stream_encode_worker.o
In file included from ../src/enc/stream_encode_worker.h:4,
from ../src/enc/stream_encode_worker.cc:1:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker)’:
../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type]
, reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
^
../src/enc/stream_encode_worker.cc: In member function ‘virtual void StreamEncodeWorker::HandleOKCallback()’:
../src/enc/stream_encode_worker.cc:47:27: warning: ‘v8::Localv8::Value Nan::Callback::Call(int, v8::Localv8::Value) const’ is deprecated [-Wdeprecated-declarations]
callback->Call(1, argv);
^
In file included from ../src/enc/stream_encode_worker.h:4,
from ../src/enc/stream_encode_worker.cc:1:
../../nan/nan.h:1740:3: note: declared here
Call(int argc, v8::Localv8::Value argv[]) const {
^~~~
../src/enc/stream_encode_worker.cc:53:27: warning: ‘v8::Localv8::Value Nan::Callback::Call(int, v8::Localv8::Value) const’ is deprecated [-Wdeprecated-declarations]
callback->Call(2, argv);
^
In file included from ../src/enc/stream_encode_worker.h:4,
from ../src/enc/stream_encode_worker.cc:1:
../../nan/nan.h:1740:3: note: declared here
Call(int argc, v8::Localv8::Value argv[]) const {
^~~~
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/enc/stream_encode_worker.h:4,
from ../src/enc/stream_encode_worker.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:
/root/.node-gyp/10.16.3/include/node/node_object_wrap.h:84:78:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
CXX(target) Release/obj.target/iltorb/src/iltorb.o
In file included from ../src/iltorb.cc:1:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker)’:
../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type]
, reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
^
In file included from ../../nan/nan.h:54,
from ../src/iltorb.cc:1:
../src/iltorb.cc: At global scope:
/root/.node-gyp/10.16.3/include/node/node.h:573:43: warning: cast between incompatible function types from ‘void ()(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void ()(v8::Localv8::Object)’} to ‘node::addon_register_func’ {aka ‘void ()(v8::Localv8::Object, v8::Localv8::Value, void)’} [-Wcast-function-type]
(node::addon_register_func) (regfunc),
^
/root/.node-gyp/10.16.3/include/node/node.h:607:3: note: in expansion of macro ‘NODE_MODULE_X’
NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
^~~~~~~~~~~~~
../src/iltorb.cc:12:1: note: in expansion of macro ‘NODE_MODULE’
NODE_MODULE(iltorb, Init)
^~~~~~~~~~~
In file included from /root/.node-gyp/10.16.3/include/node/node.h:63,
from ../../nan/nan.h:54,
from ../src/iltorb.cc:1:
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:
/root/.node-gyp/10.16.3/include/node/node_object_wrap.h:84:78:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/root/.node-gyp/10.16.3/include/node/v8.h: In instantiation of ‘void v8::PersistentBase::SetWeak(P, typename v8::WeakCallbackInfo::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/root/.node-gyp/10.16.3/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
SOLINK_MODULE(target) Release/obj.target/iltorb.node
COPY Release/iltorb.node
COPY ../build/bindings/iltorb.node
TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/opt/juice-shop/node_modules/iltorb/build'

<EMAIL_ADDRESS>install /opt/juice-shop/node_modules/libxmljs2
node-pre-gyp install --fallback-to-build --loglevel http

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp http GET https://github.com/marudor/libxmljs2/releases/download/v0.21.4/node-v64-linux-x64-glibc.tar.gz
node-pre-gyp http 200 https://github.com/marudor/libxmljs2/releases/download/v0.21.4/node-v64-linux-x64-glibc.tar.gz
[libxmljs2] Success: "/opt/juice-shop/node_modules/libxmljs2/build/Release/xmljs.node" is installed via remote

<EMAIL_ADDRESS>install /opt/juice-shop/node_modules/sqlite3
node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download
[sqlite3] Success: "/opt/juice-shop/node_modules/sqlite3/lib/binding/node-v64-linux-x64/node_sqlite3.node" is installed via remote

<EMAIL_ADDRESS>postinstall /opt/juice-shop/node_modules/core-js
node scripts/postinstall || echo "ignore"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:

https://opencollective.com/core-js
https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

<EMAIL_ADDRESS>postinstall /opt/juice-shop/node_modules/funding
node bin/funding.js

npm WARN lifecycle<EMAIL_ADDRESS>cannot run in wd<EMAIL_ADDRESS>cd frontend && npm install && cd .. && npm run build (wd=/opt/juice-shop)
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^7.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 1414 packages from 1702 contributors and audited 881258 packages in 62.183s
found 11 vulnerabilities (2 low, 5 moderate, 3 high, 1 critical)
run npm audit fix to fix them, or npm audit for details`
then ran
npm audit fix --foce
npm start
npm WARN lifecycle<EMAIL_ADDRESS>cannot run in wd<EMAIL_ADDRESS>cd frontend && npm install && cd .. && npm run build (wd=/opt/juice-shop)
any idea what is wrong ?
Regards

First of all, you shouldn't run npm audit fix because then you might repair stuff that it purposefully broken and insecure in the application. Also, the installation seems to gave gone fine, all the warnings seem to be just noise from dependencies trying to bootstrap.
I don't know why  cd frontend && npm install && cd .. && npm run build would fail for you during the postinstall step. Can you get more error details from your OS on that one maybe?

I'm using parrot OS latest version. I think it should be the case .

I can't really help you with that without any further error logs or stacktraces etc. I recommend you try the pre-packaged .tgz for Linux from our GH-Releases page as a fallback.

very strange , I just logged into my parrato os with user instead of root  and followed same step given on github for source and working directory /home/myuser/juice-shop". it worked with out any issue. Before that I logged in as root user and working directory was "/opt/juice-shop"  and I got above error. So far I can think of that there is a check for uid which check if user is root then it wont proceed. But goin through the package.json file I  dindt find such instruction either. Could you please help how do I proceed with root user instead of a normal user.
Regards

You essentially just confirmed that the application works on your computer... We cannot support specific user or permission questions which might depend on a myriad of individual settings on someones PC. Sorry.

Issue has been identifies :) . if any one wants to setup juice-shop repository use it at your risk . nmp / node.js does allowed to install packages as root due to its own structure.
Solution as root user Installation
Install node.js in your system if not already installed
git clone https://github.com/bkimminich/juice-shop.git
cd juice-shop
npm install -g --unsafe-perm=true --allow-root
npm start
Browse to http://localhost:3000

For the record, I totally not recommend to install the Juice Shop in global scope with -g ... ...

I've removed -g (global) option its not necessary as well.
Regards

try:
npm install --unsafe-perm=true --allow-root --force


Lewis. Can you clean up the Example2 header so I can merge this with the curriculum? Thanks.


PromiseKit framework detection

I'm trying to build the PromiseKit with punic.
The problem is that PromiseKit has a Extension folder which contains a lot of project with extension to some system frameworks.
Carthage doesn't build thees projects and only build the main project.
Is this a problem with the framework detection or does Carthage do something else?
For me building all of them sort of is expected behaviour, but many of them fail. I added all of them to my skip list, but thats a lot of project to at there.
To test the behaviour please remove the skips.
punic.yaml
defaults:
  configuration: Release
  platform: iOS
  xcode-version: 8.2.1
skips:
  - [ iOS, PromiseKit, PMKAccounts.xcodeproj]
  - [ iOS, PromiseKit, PMKAlamofire.xcodeproj]
  - [ iOS, PromiseKit, PMKAddressBook.xcodeproj]
  - [ iOS, PromiseKit, PMKAssetsLibrary.xcodeproj]
  - [ iOS, PromiseKit, PMKAVFoundation.xcodeproj]
  - [ iOS, PromiseKit, PMKBolts.xcodeproj]
  - [ iOS, PromiseKit, PMKCloudKit.xcodeproj]
  - [ iOS, PromiseKit, PMKCoreBluetooth.xcodeproj]
  - [ iOS, PromiseKit, PMKCoreLocation.xcodeproj]
  - [ iOS, PromiseKit, PMKEventKit.xcodeproj]
  - [ iOS, PromiseKit, PMKFoundation.xcodeproj]
  - [ iOS, PromiseKit, PMKMapKit.xcodeproj]
  - [ iOS, PromiseKit, PMKMessagesUI.xcodeproj]
  - [ iOS, PromiseKit, PMKOMGHTTPURLRQ.xcodeproj]
  - [ iOS, PromiseKit, PMKPhotos.xcodeproj]
  - [ iOS, PromiseKit, PMKQuartzCore.xcodeproj]
  - [ iOS, PromiseKit, PMKSocial.xcodeproj]
  - [ iOS, PromiseKit, PMKStoreKit.xcodeproj]
  - [ iOS, PromiseKit, PMKSystemConfiguration.xcodeproj]
  - [ iOS, PromiseKit, PMKUIKit.xcodeproj]
  - [ iOS, PromiseKit, PMKWatchConnectivity.xcodeproj]

Cartfile
github "hyperoslo/Whisper"
github "onevcat/Kingfisher"
github "marmelroy/PhoneNumberKit"
github "marmelroy/Interpolate"s
github "Alamofire/Alamofire"
github "mxcl/PromiseKit"
github "realm/realm-cocoa"
github "bustoutsolutions/siesta"
github "JohnSundell/Unbox"

Cartfile.resolved
github "Alamofire/Alamofire" "4.2.0"
github "marmelroy/Interpolate" "0.4.0"
github "onevcat/Kingfisher" "3.2.4"
github "marmelroy/PhoneNumberKit" "1.2.1"
github "mxcl/PromiseKit" "4.1.3"
github "JohnSundell/Unbox" "2.3.0"
github "hyperoslo/Whisper" "4.0.0"
github "realm/realm-cocoa" "v2.1.2"
github "bustoutsolutions/siesta" "1.0.1"

Thanks a lot for your work btw. This is much nice, cleaner and most importantly faster than Carthage.

Thanks for all the issues and pull requests. They're very much appreciated. I've been on vacation and am only now able to resolve PRs and issues. Thanks for your patience.

PromiseKit is a very strange project and of a type I haven't seen before. Each extension has its own Cartfile. I need to figure out how to support this but it won't necessarily be soon I'm afraid.

No problems.
One can still add skip lists.

Ah I see. You don't want the extensions built. OK. Definitely low priority for now - but interesting. Seems they've added support for this to Carthage but not sure if it's documented yet.


fixed #610

fixed  issue #610
as mentionned on #610 by William-H, I replaced the value of the dom from  "Bfrtip" tp lBfrtip" on the js/custom.js  , so that the data will be loaded correctly and can be exported as we Excel or Pdf AND the button ' show entries' will not disappear.
tables_dynamic.html.
js/custom.js
A simple Demo  : Before and After
# Before :

                                                                  # **After :**

Approved, thank you @selimgnaoui !


Add VS Code to Microsoft AutoUpdate

As the macOS administrator in my org, I'd like to be able to control updates using MS AutoUpdate along with deadlines and channel features.

<EMAIL_ADDRESS>


Notebook example doesn’t work

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=463

Invalid report


set user to authData after new password set

Fix #609
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0cee8db). Click here to learn what that means.
The diff coverage is 50%.

@@            Coverage Diff            @@
##             master     #616   +/-   ##
=========================================
  Coverage          ?   89.19%
=========================================
  Files             ?       69
  Lines             ?     3221
  Branches          ?      612
=========================================
  Hits              ?     2873
  Misses            ?      330
  Partials          ?       18

Impacted Files
Coverage Δ

.../aws-amplify-react/src/Auth/RequireNewPassword.jsx
94.11% <50%> (ø)

Continue to review full report at Codecov.

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


AIX build box 1 not successfully building

Leaving this open because I've had some issues with build-ppc-osuosl-ppc64-aix-1, and will start properly logging everything in here as I'm starting to lose track. Build machine build-ppc-osuosl-ppc64-aix-2 has been generally ok as far as I can tell.

Are both machines configured with the same playbook?

Are your failures on JDK11, looking like this?
https://github.com/eclipse/openj9/issues/2468
In setup of OpenJ9 pull request jobs, I could never get a successful jdk11 compile on aix.

@sxa555 could you let me know some details please so I can take a look for you?

I suspect that given what @sej-jackson has found that a library (presumably a dependency of something else) has got updated when I was prototyping some changes for java11 on that machine. Should be easy enough to fix. @mleipe Yes they were originally but I was using the -1 machine to test extra setup which was required for java 11 building and during that likely caused the breakage (the risk of that happening was why I only touched one machine of course)
I will look at either dropping the version of gmp or allowing a later libgccto be installed on that machine (although it's surprising that yum left it in that state)

@jdekonin No I haven't hit that particular failure (yet) At the moment our machines don't have a suitable autoconf that JDK11 likes (See this log) so I almost certainly just haven't got as a far as that error but thanks for the heads-up!

Downloaded https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/gmp/gmp-5.1.3-2.aix6.1.ppc.rpm then:
# rpm -Uvh --oldpackage gmp-6.1.2-1.aix6.1.ppc.rpm gmp-5.1.3-2.aix6.1.ppc.rpm
warning: package gmp-6.1.2-1.ppc was already added, skipping gmp-5.1.3-2.ppc
Preparing...                ########################################### [100%]
        package gmp-6.1.2-1.ppc is already installed
# yum downgrade gmp-6.1.2-1.aix6.1.ppc.rpm gmp-5.1.3-2.aix6.1.ppc.rpm
Setting up Downgrade Process
AIX_Toolbox                                                     | 2.9 kB  00:00:00
AIX_Toolbox/primary_db                                          | 1.1 MB  00:00:03
AIX_Toolbox_71                                                  | 2.9 kB  00:00:00
AIX_Toolbox_71/primary_db                                       |  13 kB  00:00:00
AIX_Toolbox_noarch                                              | 2.9 kB  00:00:00
AIX_Toolbox_noarch/primary_db                                   |  51 kB  00:00:00
Examining gmp-6.1.2-1.aix6.1.ppc.rpm: gmp-6.1.2-1.ppc
Only Upgrade available on package: gmp-6.1.2-1.ppc
Examining gmp-5.1.3-2.aix6.1.ppc.rpm: gmp-5.1.3-2.ppc
Resolving Dependencies
--> Running transaction check
---> Package gmp.ppc 0:5.1.3-2 will be a downgrade
---> Package gmp.ppc 0:6.1.2-1 will be erased
--> Finished Dependency Resolution

Dependencies Resolved

=======================================================================================
 Package       Arch          Version           Repository                         Size
=======================================================================================
Downgrading:
 gmp           ppc           5.1.3-2           /gmp-5.1.3-2.aix6.1.ppc           2.6 M

Transaction Summary
=======================================================================================
Downgrade     1 Package

Total size: 2.6 M
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : gmp-5.1.3-2.ppc                                                     1/2
  Cleanup    : gmp-6.1.2-1.ppc                                                     2/2

Removed:
  gmp.ppc 0:6.1.2-1

Installed:
  gmp.ppc 0:5.1.3-2

Complete!
#

JDK8+HotSpot has built on ok the machine

JDK11+OpenJ9 failed prior to installing these dependencies via yum:

autoconf

All working ... Closing :-D

Also killed an apparently defunct jenkins slave process that was holding the CPU load at almost 10 on the machine:
# ps -fu jenkins
     UID      PID     PPID   C    STIME    TTY  TIME CMD
 jenkins  9699536        1 431   Nov 02      - 13901:28 java -jar remoting.jar -workDir

Killed multiple processes today:
     UID      PID     PPID   C    STIME    TTY  TIME CMD
 jenkins  9633954        1   0   Dec 11      -  0:00 /ramdisk0/build/workspace/Grinder/openjdkbinary/j2sdk-image/bin/../bin/java -cp /ramdisk0/build/workspace/Grinder/jvmtest/openjdk_regression/work/classes/ja
 jenkins  6029718        1   0   Dec 11      -  0:00 /ramdisk0/build/workspace/Grinder/openjdkbinary/j2sdk-image/bin/../bin/java -cp /ramdisk0/build/workspace/Grinder/jvmtest/openjdk_regression/work/classes/ja
 jenkins  6160736        1   0   Nov 15      -  0:00 /ramdisk0/build/workspace/openjdk11_j9_openjdktest_ppc64_aix/openjdkbinary/j2sdk-image/bin/../bin/java -cp /ramdisk0/build/workspace/openjdk11_j9_openjdktes
 jenkins  8323494        1   0   Dec 11      -  0:00 /ramdisk0/build/workspace/Grinder/openjdkbinary/j2sdk-image/bin/../bin/java -cp /ramdisk0/build/workspace/Grinder/jvmtest/openjdk_regression/work/classes/ja
$


ChannelMultiple raises exception if there are no outputs

This example creates a ChannelMultiple, then writes to its input channel without adding any outputs:
import asyncio_channel, asyncio
async def main():
    src = asyncio_channel.create_channel()
    mult = asyncio_channel.create_multiple(src)
    await src.put(42)
asyncio.get_event_loop().run_until_complete(main())

I would expect this to simply drop the message with no errors.  A ChannelMultiple with 2 outputs sends 2 messages; a ChannelMultiple with 1 output sends 1 message; so a ChannelMultiple with 0 outputs should send 0 messages.
Instead, I get:
Task exception was never retrieved
future: <Task finished name='Task-2' coro=<_start() done, defined at /Users/comex/src/asyncio-channel/asyncio_channel/_create_multiple.py:16> exception=ValueError('Set of coroutines/Futures is empty.')>
Traceback (most recent call last):
  File "/Users/comex/src/asyncio-channel/asyncio_channel/_create_multiple.py", line 22, in _start
    await wait_all(*(_put(ch, x) for ch, _ in outs))
  File "/Users/comex/src/asyncio-channel/asyncio_channel/_util.py", line 23, in wait_all
    done, pending = await wait(tasks, timeout=timeout)
  File<EMAIL_ADDRESS>line 413, in wait
    raise ValueError('Set of coroutines/Futures is empty.')
ValueError: Set of coroutines/Futures is empty.

Hello, thanks for reporting this.  Sorry that I did not see this until now.  Apparently my notification settings were off.

Fix has been released in v0.9.1


Diagram error or misunderstanding on J533

Hello, on the J533 Diagram, the pinout for "To Adapter Board" is what I assume to be the car harness j533 plug.
The counting and display of those pins are wrong.

theyre going
1 3 5
2 4 6
when its supposed to be
1   2   3
11 12 13
Please look at how the pinout for "TO j533" is displayed as that is how VW counts their pins on the car harness side

The adapter board has two connectors on it,<PHONE_NUMBER> and 966871-1. 966871-1 number scheme is 1 2 3, 11 12 13, but the numbering scheme for<PHONE_NUMBER> is 1 3 5, 2 4 6. The J533 harness connects to the adapter board with connector part number<PHONE_NUMBER> which is why it is on the harness schematic this way.
You can find the adapter board here, https://github.com/commaai/neo/tree/master/car_harness/boards/VW

what is the point of the "adapter board?"

The J533 harness from your shop does not use this "adapter board" but rather a normal wire-wire plug
I am trying to find the pinout used for the j533 DEV harness sold on your shop.
I already have one installed but I'd like to know which buss's are filtered/tapped/etc

hello,<PHONE_NUMBER> is the PN listed in the PDF, not<PHONE_NUMBER>.
i only noticed this after buying<PHONE_NUMBER>........
the PCB counterpart of<PHONE_NUMBER> is<PHONE_NUMBER>

wait now im confused. mouser says<PHONE_NUMBER> is the right mating connector. i have confirmed by PN that<PHONE_NUMBER> is what i ordered, and it is NOT the same as the one on my comma PCB
@vanillagorillaa did you guys change the production J533 connector?
if so, can you update the PDF or drop the new PN here?
i am trying to make a module to add some functionality to OP

yeah just triple checked,<PHONE_NUMBER> is what i bought, and it is different than that of the connector on my genuine comma ai j533 adapter PCB from the harness purchased with my C3.
any help?


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

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

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-01-13-09-43-29 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-01-13-09-43-29

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


poor example of setting https for linux Vm on azure

[Enter feedback here]
Every example on ms docs should be provided as cloud shell and as using the portal UI.
and sorry for the strong feedback but not everyone is a backend expert proficient with cloud shell.
I found it impossible to set a LInux VM with HTTPS. I super simple to do it on the web app service, but with VM is not.
How to add https on a linux VM ubuntu using the portal? Seems no tutorial at all.

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

ID: 996eb4d1-198e-a69a-b9c5-d247db46d025
Version Independent ID: 5bfe27b3-22e9-efa8-6a1c-3637aa39a049
Content: Tutorial: Secure a web server with TLS/SSL certificates - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/tutorial-secure-web-server.md
Service: virtual-machines
GitHub Login: @cynthn
Microsoft Alias: cynthn

@jcdsr
Thanks for your feedback! We will investigate and update as appropriate.

We will now close this issue. If you are still seeing this issue, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


map files contains absolute filenames

In the previous version this names where relativ

And path mapping is not working any longer in Windows enviroment

fixed with https://github.com/qooxdoo/qooxdoo-compiler/pull/672


*: fix typo in CONTRIBUTING.md

Signed-off-by: dvermd<EMAIL_ADDRESS>
What problem does this PR solve?
Problem Summary: There's a typo on the "Slack" link in CONTRIBUTING.md
What is changed and how it works?
What's Changed:
Related changes
Check List
Tests

No code

Release note

No release note

/merge


Command to remove lorri gc-roots

So this is really a Nix issue (how to triage gc roots across a system?), but now that I am spawning lorri's everywhere to watch my things I'm finding that managing my gcroots is a bit of a pain.  Firstly looking up the paths corresponding to a given project (or the other way around) is not rocket science but introduces enough of a disconnect to cause friction.  Introducing 3 gcroots per project is also a factor,
making a list of gc roots seem more intimidating than it really is :).
I don't mean to complain, but this seems like something that could have a good solution (perhaps) as part of lorri and for everyone's benefit.
Any plans/thoughts on this front?
I suppose a basic "here is the gc roots for this project" as entries in lorri info would be a start,
and perhaps a simple "clear the eval cache" (phrased better) subcommand?

Since we’ve removed the .lorri directory from the project and are moving to hashed project paths as gcroot names, the disconnect is gonna be even bigger.
How about adding a plumbing command for now, lorri rm-gc-roots_ [--for <nix file>] (defaulting to .) until we get a better overview of what users need in practice?

I would like to give my point of view to this issue:
It would be a nice feature if lorri could show an overview of all current used gc roots with the ability to select one or more and remove these gc roots.
For example:
$ lorri gc-roots --show
  1: /home/user/projects/example1
  2: /tmp/test-lorri1
  3: /home/user/projects/deprecated-project

$ lorri gc-roots --delete 3

My use case is that I want to remove gc roots of testing environments or deprecated projects I used, so an "overview" command is definitely necessary in my opinion.
I would love to help with this kind of feature, once the cli design is set.
BTW: Very nice work with this project!

This is a good candidate for contribution. Implementing the plumbing command I mentioned above should be fairly easy.
Any takers? :)

For me personally it would be sufficient if lorri just kept a reference to the source in the gcroot.  Then I can use a normal bash script to produce a list of used and unused gcroots.
For that I guess adding something like this would be the way to go?  (No idea whether that compiles, I don't really speak Rust)
--- a/src/project.rs
+++ b/src/project.rs
@@ -41,6 +41,8 @@ impl Project {
         let project_gc_root = gc_root_dir.join(&hash).join("gc_root");

         std::fs::create_dir_all(&project_gc_root)?;
+        let mut file = File::create(gc_root_dir.join("ref"))?;
+        file.write_all(nix_file.as_path().as_os_str().as_bytes())?;

         Ok(Project {
             nix_file,

For each new gcroot this would create a file which contains the path to the shell.nix that it was created with
$ cat ~/.cache/lorri/gc_roots/<hash>/gc_root/ref
/path/to/shell.nix

In principle ref could also be a symlink to shell.nix but I don't know whether there are any adversary interactions with being a gcroot.


Expose both security events and journal records on project history

Once #6339 is merged, the "History" tab for project management will contain the event security log instead of the project journal. We should look at re-exposing the project journal, possibly as a second table on that same tab.
cc @nlhkabu

I would appreciate your feedback on this @ewdurbin and @dstufft, as I understand that this was briefly discussed on Slack.
@brainwane - would you consider this part of the security milestone, or out of scope?

@nlhkabu Since the project journal at warehouse/templates/manage/history.html currently displays new releases and removed releases, and since #6339 does not include that info, I think we have 2 choices:
a: don't merge #6339 yet -- wait until we have a new PR that adds events for upload or removal of a specific release/file to the event security log, then merge #6339 and then immediately merge the new PR
b. re-expose the project journal (possibly via a rename from "history" to something else)
@woodruffw @nlhkabu which of these do you think will take less time/redundancy?

The second option (re-exposing the journal) would probably take less time; I could do it as part of #6339. OTOH it would take about the same amount of time to just add those events to the audit log, so I could do that instead (and that would fit more cleanly into the changeset).

My preference here would be to add those events to the audit log to avoid a temporary situation where we have duplicate "history" tables.

I think it's reasonable to maintain both tables. Journals could be noted as effectively an implementation detail that will be replaced by the Security History.

Journals could be noted as effectively an implementation detail that will be replaced by the Security History

You mean that we should add some help text or a badge to explain that we plan on deprecating this?  That works for me :)

OK, that's fine with me.

Added the remaining events in #6339 and re-added the old journal table as a separate tab, so closing this.


Add missing check for /original_metadata for edge case

User story
As a developer, I want to check that /original_metadata exists, so I can ensure correct files are not overwritten.
This check is only missing in 1 edge case: If metadata record exists in S3 but not DocDB, and was not picked up by lambda function, and /original_metadata was already copied.
Other appropriate cases already have the check.
Acceptance criteria
Given that a metadata record file exists in S3 but not in DocDB...

[ ]  ...and /original_metadata does not exist, the top-level core jsons are copied and then overwritten/synced with metadata.nd.json
[ ]  ...and /original_metadata already exists, the top-level core jsons are not copied to /original_metadata, and the top level jsons are still synced with metadata.nd.json

Sprint Ready Checklist

[ ] 1. Acceptance criteria defined
[ ] 2. Team understands acceptance criteria
[ ] 3. Team has defined solution / steps to satisfy acceptance criteria
[ ] 4. Acceptance criteria is verifiable / testable
[ ] 5. External / 3rd Party dependencies identified
[ ] 6. Ticket is prioritized and sized

Notes
Add any helpful notes here.

There is additional edge case where /original_metadata was not created (when another service created metadata.nd.json and lambda already pushed it to docdb).
Given that metadata.nd.json is already in sync in S3 and in DocDB,

[ ] but /original_metadata does not exist, the top-level core jsons are copied and then synced with metadata.nd.json core fields
[ ] and /original_metadata already exists, log that everything is already in sync

When data is copied from one bucket to another (existing /original_metadata is copied, but metadata.nd.json is not), the indexer may overwrite /original_metadata depending on the datestamps in the filenames.
Consider making the datestamp used in the filename more granular or not overwrite original_metadata files if they already exist.
@jtyoung84


feat(component): add steps modal

Infos

Task
What is being delivered?
New component that wraps atom-modal, the atom steps modal.
What impacts?
New component created.
Reversal plan
Re-release to the previous stable version and revert on main branch
Evidences
Media(images, gifs or videos) that shows the result of your work.

@jowjow22 We need to add a complete description for this pull request too

answering this question https://github.com/juntossomosmais/atomium/pull/599#discussion_r1821461002 @felipefialho i created a new property that allows the user choose when the modal should close on finish or not 24fbe27


time: TestAfterQueuing fails on windows builders:

The TestAfterQueuing fails on windows builders recently:
http://build.golang.org/log/b9cb3c3357a4a8d874bf0669d6ee52f39f0be277
http://build.golang.org/log/62b0ebbe08b4b4b099b301a426e793286c2ed155
http://build.golang.org/log/bb3bbce19d8e09e3377629c491ca584faecc8ed0
with
--- FAIL: TestAfterQueuing (2.46s)
	sleep_test.go:235: attempt 0 failed: After(160ms) arrived at 532.1925ms, expected [150ms,360ms]
	sleep_test.go:235: attempt 1 failed: after slot 3, expected 1
	sleep_test.go:235: attempt 2 failed: after slot 3, expected 1
	sleep_test.go:239: after slot 3, expected 1
FAIL
FAIL	time	5.842s

The test does not fail for me here. But I suspect builders are CPU busy building Go and running tests - we are running both windows-386 and windows-amd64 in parallel. I added code similar to runtime/pprof/cpuHogger to TestAfterQueuing and I can make TestAfterQueuing fail on VM here (not on real hardware). I suggest we increase delta to 200 * Millisecond (It is 100 * Millisecond at this moment). That fixes my failure. It might make builders more reliable. How does that sound?
Alex

I think for the new style builders, the 386 and amd64 are building on
different VMs.

Correct. Each Windows build is isolated.

Yes, builders are running in separate VMs now. Thanks for correcting me @minux and @bradfitz. I am not sure why this test fails more often in VMs.
Like I mentioned before, I can break this test reliably if I add this:
diff --git a/src/time/sleep.go b/src/time/sleep.go
index e7a2ee2..673d433 100644
--- a/src/time/sleep.go
+++ b/src/time/sleep.go
@@ -97,8 +97,10 @@ func sendTime(c interface{}, seq uintptr) {
 	// Used in NewTicker, dropping sends on the floor is
 	// the desired behavior when the reader gets behind,
 	// because the sends are periodic.
+	t := Now()
+	print("sendTime: t=", t.String(), "\n")
 	select {
-	case c.(chan Time) <- Now():
+	case c.(chan Time) <- t:
 	default:
 	}
 }
diff --git a/src/time/sleep_test.go b/src/time/sleep_test.go
index 2fce753..508f689 100644
--- a/src/time/sleep_test.go
+++ b/src/time/sleep_test.go
@@ -220,10 +220,60 @@ func TestAfterStop(t *testing.T) {
 	}
 }

+var (
+	salt1 = 0
+	salt2 = 0
+)
+
+func cpuHog1() {
+	foo := salt1
+	for i := 0; i < 1e5; i++ {
+		if foo > 0 {
+			foo *= foo
+		} else {
+			foo *= foo + 1
+		}
+	}
+	salt1 = foo
+}
+
+func cpuHog2() {
+	foo := salt2
+	for i := 0; i < 1e5; i++ {
+		if foo > 0 {
+			foo *= foo
+		} else {
+			foo *= foo + 2
+		}
+	}
+	salt2 = foo
+}
+
+func cpuHogger(f func()) {
+	// We only need to get one 100 Hz clock tick, so we've got
+	// a 25x safety buffer.
+	// But do at least 500 iterations (which should take about 100ms),
+	// otherwise TestCPUProfileMultithreaded can fail if only one
+	// thread is scheduled during the 250ms period.
+	t0 := Now()
+	for i := 0; i < 500 || Since(t0) < 5000*Millisecond; i++ {
+		f()
+	}
+}
+
 func TestAfterQueuing(t *testing.T) {
+	go func() {
+		c := make(chan int)
+		go func() {
+			cpuHogger(cpuHog1)
+			c <- 1
+		}()
+		cpuHogger(cpuHog2)
+		<-c
+	}()
 	// This test flakes out on some systems,
 	// so we'll try it a few times before declaring it a failure.
-	const attempts = 3
+	const attempts = 1
 	err := errors.New("!=nil")
 	for i := 0; i < attempts && err != nil; i++ {
 		delta := 100 * Millisecond
@@ -247,7 +297,9 @@ type afterResult struct {
 }

 func await(slot int, result chan<- afterResult, ac <-chan Time) {
-	result <- afterResult{slot, <-ac}
+	t := <-ac
+	print("await: t=", t.String(), "\n")
+	result <- afterResult{slot, t}
 }

 func testAfterQueuing(t *testing.T, delta Duration) error {

the output
C:\>u:\test -test.short -test.v -test.run=TestAfterQueuing
=== RUN TestAfterQueuing
sendTime: t=2015-05-04 22:44:37.4667308 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4667308 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4677073 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4677073 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4677073 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4677073 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4686838 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4686838 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4686838 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4686838 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4686838 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4696603 -0700 PDT
sendTime: t=2015-05-04 22:44:37.4696603 -0700 PDT
await: t=2015-05-04 22:44:37.4667308 -0700 PDT
await: t=2015-05-04 22:44:37.4686838 -0700 PDT
await: t=2015-05-04 22:44:37.4677073 -0700 PDT
await: t=2015-05-04 22:44:37.4686838 -0700 PDT
await: t=2015-05-04 22:44:37.4686838 -0700 PDT
await: t=2015-05-04 22:44:37.4686838 -0700 PDT
await: t=2015-05-04 22:44:37.4677073 -0700 PDT
await: t=2015-05-04 22:44:37.4667308 -0700 PDT
await: t=2015-05-04 22:44:37.4677073 -0700 PDT
await: t=2015-05-04 22:44:37.4686838 -0700 PDT
await: t=2015-05-04 22:44:37.4696603 -0700 PDT
await: t=2015-05-04 22:44:37.4677073 -0700 PDT
await: t=2015-05-04 22:44:37.4696603 -0700 PDT
--- FAIL: TestAfterQueuing (0.23s)
        sleep_test.go:285: attempt 0 failed: After calls returned out of order: [0 5 3 6 6 6 1 1 2 7 9 4 8]
        sleep_test.go:289: After calls returned out of order: [0 5 3 6 6 6 1 1 2 7 9 4 8]
FAIL

Timers are fired fine - I tested this by adding debug prints in runtime/time.go (not shown). But then when sendTime puts timer events in the channel (returned by time.After), the events are received (in await) out of order - see the output. I think it just the way our scheduler works when there is some runnable code or, perhaps, when in VM. I don't know why this only happens on windows. Perhaps it is to do with Windows time granularity being around 15ms.
The only thing I can think of is to increase delta further from 100ms to 200ms or even more. This makes adjusted test PASS.
Looking for suggestions. Thank you.
Alex
@dvyukov @randall77

OpenBSD is still flaky too, even after bumping retries up to 100ms (#9903, d12b532).  It probably makes sense that for a second retry (i.e., third attempt) we can try an even longer delta period, like 500ms or a full second.  Since the tests are only occasionally flaky right now, an extra conservative delta duration shouldn't affect our average testing times much.
Overall, the test as written is just inherently flaky.  There's no guarantee the await goroutines will execute in the desired order.  They might get scheduled across multiple CPUs or even just get scheduled out of order on a single CPU.
An alternative non-flaky way to write the test would be to select on all of the time.After channels (probably using reflect.Select) and make sure that if the runtime chooses to receive from time.After(N*delta) then we need to either have already received from all of the shorter duration timeouts or receiving from them now should not block.

Thank you @mdempsky for the input. I agree with your conclusions, that it is reasonable to increase delta up to 0.5s or 1s. These flukes are exception to the rule and shouldn't increase test time too much.  I will see what others say and send the change after.
Alex

It looks like general heavy load can throw this test off.  Is there any way to get this test run in isolation?  Maybe in test/... somewhere instead of a Test* (which gets run in parallel with lots of other stuff?).

I really don't want package specific tests to be placed under /test.
Tests under /test are supposed to test the compiler and to a lesser extent,
the runtime.

Can we use testing.TestMain somehow?
Alex

The problem is that on multiple core machines, go test -short std will
build and
run multiple tests in parallel. It's not about contention from tests in the
same
package.

The problem is that on multiple core machines, go test -short std
will build and run multiple tests in parallel.

I'm not sure that's happening on our builders, but regardless the test shouldn't care.
Let's focus on making the test robust and not running it in isolation.


Remove Qblox Cluster

This PR simplify the Qblox instruments removing the necessity of  Cluster, see PR https://github.com/qiboteam/qibolab/pull/702

You might want to mention https://github.com/qiboteam/qibolab/pull/702

Perfect, thanks @stavros11.


New version of GRaNIE integration

viash run src/methods/multi_omics/granie/config.vsh.yaml runs through for me now.

python is not installed in the container and not needed for GRaNIE. Running this with 5 GB will also not be enough unless the data is tiny.


NTR: regulation of transcription involved in carbohydrate catabolism

Hello,
I'd like a term to describe the regulation of transcription of sets of genes involved in carbohydrate catabolism - gylcolysis, in particular.
Reference: PMID: 19995986
This new term would replace IMP annotations made to several different phenotypes to protein Q9NP71.
Thanks,
Pascale
Reported by: pgaudet
Original Ticket: geneontology/ontology-requests/11035

We already had:
rdfs:label "regulation of carbohydrate metabolic process by regulation of transcription from RNA polymerase II promoter"^^xsd:string
id "GO:1900402"^^xsd:string
has_obo_namespace "biological_process"^^xsd:string
definition "A regulation of transcription from RNA polymerase II promoter that results in regulation of carbohydrate metabolic process."^^xsd:string
has_exact_synonym "regulation of carbohydrate metabolism by regulation of transcription from RNA polymerase II promoter"^^xsd:string
created_by "mah"^^xsd:string
creation_date "2012-04-20T02:45:27Z"^^xsd:string
I fixed its logical def ->
'regulation of transcription from RNA polymerase II promoter'
and (regulates some 'carbohydrate metabolic process')
And added
rdfs:label "regulation of carbohydrate catabolic process by regulation of transcription from RNA polymerase II promoter"
has_obo_namespace "biological_process"^^xsd:string
definition "A regulation of transcription from RNA polymerase II promoter that results in regulation of carbohydrate catabloism."^^xsd:string
has_exact_synonym "regulation of carbohydrate catabolism by regulation of transcription from RNA polymerase II promoter"^^xsd:string
created_by "dos"^^xsd:string
creation_date "2017-01-31T14:46:21Z"^^xsd:dateTime
EquivalentTo: 'regulation of transcription from RNA polymerase II promoter'
and (regulates some 'carbohydrate catabolic process')
=> automated classification under:
'regulation of carbohydrate catabolic process'
'regulation of carbohydrate metabolic process by regulation of transcription from RNA polymerase II promoter'
@pgaudet  - discovered this ticket - lost during transition from SourceForge.  Hope above fix is good (TG template has issues).

Looks like it addresses it !
Thanks, Pascale


Bending Effekt F200

We are working with the Realsense F200 camera and encountered a problem with generated pointclouds based on the code below. We tested the camera on a flat surface , but the resulting point cloud seems to bend towards the camera. I attached two examples, one of them showing a flat surface. The second image contains the realsense box, also with the bending effekt.
There seems to be a problem with the way the SDK interprets the depth informations.
Flat Surface:

Rectangle Box:

...
const float depth_scale = dev.get_depth_scale();
const rs::intrinsics depth_intrin = dev.get_stream_intrinsics(rs::stream::depth);

auto depth = reinterpret_cast<const uint16_t *>(dev.get_frame_data(rs::stream::depth));
for (int y = 0; y < depth_intrin.height; ++y)
		{
			for (int x = 0; x < depth_intrin.width; ++x)
			{
				if (uint16_t d = *depth++)
				{
					const rs::float3 point = depth_intrin.deproject({ static_cast<float>(x),static_cast<float>(y) }, d*depth_scale);
					pointCloud.push_back(point);
				}
			}
		}

Maybe the rs::intrinsics you get from the device do not match the actual intrinsics of the cameras.
The deproject function does some basic projective geometry and the undistortion with the model (brown-conrady).
I had a similar problem when using the unofficial library from https://github.com/teknotus/depthview where i had to correct the distances by myself. Since you have to do some calculations based on the camera intrinsics. Being lazy while calibrating gave me the same effect.
the base streams are with lens distortion so you can use them for calibration.
You could try the pointcloud sample (#3) and see if the effect is in there too. My camera seems fine but i put my intrinsic values in instead of taking it from the camera.
tl;dr
my bet is on bad calibration.

On the F200 the cameras interfaces are claimed by the video 4 linux drivers, and usually put in a permissions group for video, but the calibration is handled by another interface which shows up as raw access, and is given permissions a normal user wouldn't have. There are udev rules in /config that might fix this by making the USB endpoint read/write rather than the default of no access at all. I also noticed when reading through the calibration code that there is a TODO for supporting resolutions other than 640x480.

I did some more tests with different cameras. Some stored calibration seem to be nearly perfect. However, others needed some manual calibration with a cheesboard.
The undistorted ir stream seems to be correct now, still there are problems with the depth information.
The bending effekt at the corners becomes visible when using the whole depth image ( not just the part, that is also visible by the color camera). This might be a limitation of the depth image.
I measured the distances computet by different cameras within the color rectangle. Some of them differ in 2 cm ( constant over the area).
As this effect does occure depending on the camera used, I'm wondering whether the orientation of the projector couses difference in the depth image. As far as i know the camera and the projected image need to be calibrated (probably by intel during production); depending on the forces applied to the circuit during assembling this might change the relation between camera and projector which does finally lead to slightly changes in the measured distances.
The question is, how to deal with the effects.

The distance measured depends on the sensors temperature. There is a model for the difference based on the temperature measured by the sensor itself. Please make sure both cameras are running roughly at the same temperature by either letting both cool down (around an hour for mine) or let them run for a while before measuring (mine was stable after around 45 minutes - as a rule of thumb).
The relation of the RGB and IR sensor (the extrinsics you can actually calibrate) are not relevant for the distance measurement. Only for mapping the color and depth.
I'm not sure if the orientation of the IR sensor wrt the laser projector makes a difference. If that is the case you'd have to measure the offset and have to add it manually, i guess.

@Rennschnitzl Correct in your statement about temperature and performance, although there is host-side correction for this which updates the ASIC directly.
@teknotus You reminded us that we need to cleanup a few TODOs in the code -- namely that they aren't entirely accurate (non-640x480 modes should work on F200 now).
The underlying issue at hand is that one of the cameras documented in this thread probably left the factory without being properly calibrated (or was physically dropped, bent, or warped). There's little corrective action we can take in librealsense -- the per-camera calibration stored in device memory should yield correct intrinsics in all cases with no manual intervention needed by developers (such as checkerboard recalibration). The best we can offer is that you can try emailing<EMAIL_ADDRESS>for a replacement F200. Hope that helps!

My interpretation of the temperature update code was that it was replacing
the on camera in RAM calibration. It seems like this could use a manual
calibration to temporarily fix the output via a library. The factory
calibration is probably a full order of magnitude better than a manual at
home calibration and follows the camera to every computer it is attached
to, so replacing is better of course.

@teknotus Correct, there are some minor adjustments made on the host side to correct for thermal drift, but in fact these updated intrinsics are not given back to users of the library. We double and triple checked with our internal hardware team, but the recomputed coefficients are used to stabilize the ASIC algorithm and have minimal effect on the projection (e.g. shifting principal point by a thousanth of a pixel), which doesn't explain the massive discrepancies documented in the images above. This is only a problem for F200 and now all compensation is done in hardware for SR300.

@ddiakopoulos  I tested another camera, same effect, but not as strong. I'm wondering: is the intrinsic calibration performed by Intel or by creative ? During the assembling process by creative, the camera might be exposed to (minimal) pressure.
A bended circuit leads to a shift (alpha) of the projected patterns. The camera does calculate the depth information based on the location of each pattern in the image. As the pattern position shifts, the camera assumes a wrong distance ( crossing between camera ray and the expected ray for a given pattern).

You may correct me if I'm wrong but I believe this leads to the blending effect.
In order to use this technology for scientific projects it might be useful to have a method to correct this effect. (I'm unsure about the SR300 solving this problem entirely, as it seems to use the same technology )

@ddiakopoulos "but in fact these updated intrinsics are not given back to users of the library." So the intrinsics i get from the camera are no longer valid after the temperature-correction kicks in since the values changed? So retrieving the intrinsics from the camera again wouldn't make a difference?
Which does affect all of the projection functions since you have to pass them the intrinsics, right?
Or am I missing something?

@Wollimayer
First, I think a basic "check" is to try the Realsense SDK and see if you're still having issues. If so, there's an actual hardware problem and you should contact Intel support for warranty/support information. If that fixes it, then we've an actual librealsense bug.
Second, I think we should check if this bending is within the expected tolerances for shipped F200 units. @ddiakopoulos
Third, I think this may just unfortunate, expected behavior. I don't believe we currently offer a method of re-calibrating the device in either the RSSDK or librealsense. The cameras are factory-calibrated, but there exist challenges to maintaining calibration and there's the possibility that certain cameras will fall out of calibration for some of the following

Mechanical impulses causing intrinsics or extrinsics changes, such as bending of the stiffener or shifting of the lens. The cameras are designed with a stiffener, but it's possible that mechanical impulses (e.g. dropping) might knock the device out of calibration.
Un-modeled temperature changes. We currently have a real-time loop running a temperature correction model that adjusts intrinsics. If you subject the device to strong or non-uniform temperature sources, this might cause this loop to fail.
Reflection & multipath. If you have a highly reflective or specular environment, self-reflections in the scene might cause ambiguities.
Un-modeled pressure changes. I won't talk about details, but our device can be sensitive to strong ambient pressure changes. There's sensors and logic to compensate for this but you never know.

Un-modeled pressure changes. I won't talk about details, but our
device can be sensitive to strong ambient pressure changes. There's sensors
and logic to compensate for this but you never know.

Does this mean it has a barometer? I don't think I know enough to use that
information for correcting an image, but the raw data from a barometer
would be useful for unrelated applications.

The ambient pressure change compensation is hard-coded into the chip -- there is no barometer and no compensation should be required on the part of the camera user.


Integrate new ml/amaranth_lib with ml/main

Writing tests for ml/amaranth_lib modified the functionality of some functions, and even resulted in the addition and removal of functions altogether. As a result, ml/main now calls functions that don't exist or that may no longer function as expected

Implemented in https://github.com/googleinterns/amaranth/pull/2/commits/8492f974b1d07e04194e80b78c8a03815b2ec546


slow display on big dashboard

Hello
i use Grafana 2.6.0 plugin grafana-zabbix 2.5.1 and api zabbix 2.2.8.
I meet slow display on big dashboard it can reach ten minutes.

Hello! Which time period are you use?

7 days

If you need only last value, try to set Override relative time option in Time range tab. For example, for 1h (1 hour).

Hello @alexanderzobnin
I now use grafana 2.6 with zabbix 3.0.1.
I steel meet slow display of big dashboard on long period of tim with lot of data from zabbix history table like 7 days.
I installe grafana 3.0 beta with zabbix plugin to test the performance, and i saw great upgrade on cache but not on the frst time i get lot of data.

Unfortunately, Zabbix can't reduce time series on server side. So if you need to show long periods like 7 days may be better to use trends (set trends period in datasource config).

Looking into my own performance I noticed that for each data series in each graph of each page the plugin is going through the authentication process to pull data from the Zabbix server. Is it possible to share sessions and authenticate once per page load? This should affect pages with lots of graphs and/or data series. I'm not sure if this breaks the way grafana is set up but it seems like it would help a lot in some cases

@slick666 strange. Do you use grafana-zabbix 3.0?


Fix erorrs in apache thrift compatibility

There are some errors in current Apache thrift compatibility in a thrift_sasl module - these changes remain from the previous version. This errors led to issue in impyla: https://github.com/cloudera/impyla/issues/268

I wonder if in the interest of compatibility with older thrift libraries we want to determine the method calls in a way that works with thrift 0.10 and 0.9

Is there some progress on this issue or can you merge it?

@wesm ping

@gregrahn can someone test this out and make a release of the package?

@wesm 👍

+1 for a release soon if possible since latest versions pyhive and impyla have incompatible versions of thrift_sasl at the moment

@dknupp give you updated impyla to 0.14.1 on 2018-02-23, is this still an open issue?

impyla 0.14.1 pins thrift_sasl to 0.2.1 so it works but its still not possible to update thrift_sasl for other libraries that need it (PyHive with kerberos support and maybe others) so i think this is still an issue until a new release is made.


[fix](auto bucket) fix auto buckets calc using the first k partition #41675

cherry pick from #41675

run buildall