Theming chapter: zcml needs some changes to run

Hi,
sorry I didn't find a good descriptive Headline for this ticket. From what I know and can say everything is still to fuzzy for me to identify the real problem.
I was going to the "Create a Plone theme python package" section of the Theming chapter.
I was running into a problem on with the configure.zcml file. This file that is created by mrbob looks like this: http://pastie.org/10933402
If I use the file like that, an 'AttributeError: readDataFile' when I test the package. See
http://pastie.org/pastes/10933360/ for full log.
It seems to be related to using the attribute 'post_handler' on registerProfile vs. using the an extra importStep  which runs the post install code.
I took the configure.zcml from the accompanying collective/plonetheme.tango (https://git.io/v6ndD), which fixed the problem.
I added a note how to solve this problem for now to succesfully finish this part of the training (https://github.com/plone/training/pull/197/commits/765df0422e4e272d46d2653518953d8b1827715f). But I think there is a general problem here, which needs to be solved.

Closing as obsolete. It is not clear what, if anything, needs to be done. Please reopen with sufficient details to take action.


Nordic BLE fails assertion when logging is enabled

Describe the bug
When logging is enabled on a BLE peripheral and data is being sent, and the assertion here fails.
This still happens even when I enable CONFIG_FORCE_NO_ASSERT.
To Reproduce
I don't have a minimal reproduction yet, and reproducing my exact setup is a bit complicated (honestly I don't expect anyone to fully replicate this, and I'll try to provide as much info so people can quickly filter out the unimportant bits). The full background is that this is a split keyboard using the ZMK Firmware, which for 2 halves of a board it uses a BLE connection to send the keypress data across. Here's the repo for the board. The specific board name is fissure_left (which uses a nrf52840 module). The specific Zephyr version used is f2e12d55a1 in this branch. When I encounter the problem, I build the board fissure_left with logging on (edit: I'm only using RTT logging, but disabling RTT and using the USB UART backend also produces a crash), attach the Jlink probe for the debug log, wait for the connection to happen, and press a key on the peripheral side. (log is provided in the corresponding section)
Expected behavior
No assertion happens, the split keyboard half communicates fine with the central half, but with logging to the probe.
Impact
Major annoyance. Normally logging is not enabled (especially for the peripheral side), but I needed to investigate some issue which leads to spurious resetting. This can certainly be done with backtrace information when the system resets, but having logging will definitely help.
Logs and console output
*** Booting Zephyr OS build 02c77d4cc96a  ***

[00:00:00.319,122] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.319,152] <inf> fs_nvs: alloc wra: 0, f68
[00:00:00.319,152] <inf> fs_nvs: data wra: 0, f8
[00:00:00.320,739] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.320,953] <dbg> zmk: ble_profiles_handle_set: Setting BLE value profiles/0
[00:00:00.321,105] <dbg> zmk: ble_profiles_handle_set: Loaded CB:C9:A8:EA:32:1E (random) address for profile 0
[00:00:00.326,354] <dbg> zmk: zmk_ble_ready: ready? 0
[00:00:00.326,354] <dbg> zmk: update_advertising: advertising from 0 to 2
[00:00:00.331,817] <dbg> zmk: bvd_sample_fetch: ADC raw 2450 ~ 1794 mV => 3588 mV
[00:00:00.331,817] <dbg> zmk: bvd_sample_fetch: Percent: 7
[00:00:00.331,817] <dbg> zmk: zmk_battery_update: Setting BAS GATT battery level to 7.
[00:00:00.332,458] <inf> zmk: Welcome to ZMK!

[00:00:03.467,224] <dbg> zmk: connected: Connected thread: 0x200037e0
[00:00:03.467,346] <dbg> zmk: connected: Connected CB:C9:A8:EA:32:1E (random)
[00:00:03.468,627] <dbg> zmk: update_advertising: advertising from 0 to 0
[00:00:03.468,627] <dbg> zmk: connected: Active profile connected
[00:00:03.469,604] <dbg> zmk: get_selected_endpoint: Only BLE is ready.
[00:00:03.768,341] <dbg> zmk: split_svc_pos_state_ccc: value 1
[00:00:03.768,524] <dbg> zmk: security_changed: Security changed: CB:C9:A8:EA:32:1E (random) level 2
[00:00:09.039,642] <dbg> zmk: kscan_gpio_read: Sending event at 0,19 state on
[00:00:09.039,733] <dbg> zmk: zmk_kscan_process_msgq: Row: 0, col: 19, position: 36, pressed: true
[00:00:09.039,764] <dbg> zmk: split_listener:
ASSERTION FAIL [next] @ WEST_TOPDIR/zephyr/subsys/bluetooth/controller/ll_sw/nordic/lll/lll.c:653

[00:00:09.106,262] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000004  r2/a3:  0x00000003
[00:00:09.106,262] <err> os: r3/a4:  0x20003128 r12/ip:  0xdfffebbc r14/lr:  0x0001b691[0m
[00:00:09.106,262] <err> os:  xpsr:  0x41000028
[00:00:09.106,292] <err> os: Faulting instruction address (r15/pc): 0x0001b69c
[00:00:09.106,323] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:09.106,323] <err> os: Fault during interrupt handling

[00:00:09.106,353] <err> os: Current thread: 0x20003bd0 (unknown)
[00:00:09.428,588] <err> os: Halting system

Environment (please complete the following information):

OS: Arch (updated in ~1 week)
Toolchain: GNUARMEMB
Commits used are provided above

Additional context
N/A
As suggested by @Emil-Gydesen-Bose in Discord, cc'ing @cvinayak

@crides Lets analyse the issue by lowering the default IRQ priorities, which you can do by having a file <your application folder>/dts/arm/nordic/override.dtsi with the following one line in it:
#define NRF_DEFAULT_IRQ_PRIORITY 5

Please let me know the outcome...

So I'm not sure if I followed the directions correctly, but for ZMK it basically has the top level directory, the zephyr directory created from the west.yml and the app directory for the actual sources (I believe the latter 2 are common for standalone Zephyr projects?). I tried putting that in all 3 locations, and directly changing the default value of NRF_DEFAULT_IRQ_PRIORITY in dts/arm/nordic/nrf_common.dtsi to 5, all 4 produced the same result as described in the issue.

@crides maybe the simplest way is to just edit zephyr/dts/arm/nordic/nrf_common.dtsi and make the change there.

Like I mentioned, I did, and it also didn't change anything

Check your zephyr.dts file that you will find alongwith your zephyr.hex file that the priorities are 0x5, if that is the case I need to think other reasons that can delay the controller's execution at priority value 1.

Typically build/zephyr/zephyr.dts

Yes, I checked and they are all 5

@crides  It is difficult to analyse without reproducing the issue at my side.

Is there any directed advertising active during the assertion?
Use the below to debug, to rule out interrupt latencies due to irq_lock  CONFIG_ZERO_LATENCY_IRQS=y
  CONFIG_BT_CTLR_ZLI=y

@crides ping

I got the ping, but I'm fairly busy for the last 2 days. I'll try to see if I can get some testing done tonight or tomorrow night

@crides Any updates? I have some code changes which I think could help, unless you are able to reproduce the issue consistently and then test these changes, I will not be able to upstream a fix.

Sorry for the delay. I finally have some time to test.
Using the configs
CONFIG_ZERO_LATENCY_IRQS=y
CONFIG_BT_CTLR_ZLI=y

doesn't change anything, and there's advertising ongoing when the assert happens, but it's non advertising

@crides Thank for confirming the assertion, please upload full console logs when possible to help me analyze the scenarios.
Meanwhile I have a draft change (guess work), please cherry-pick the commit to your zephyr base and let me know if the assertion still happens.
PR: https://github.com/zephyrproject-rtos/zephyr/pull/44711

Thanks for confirming and helping to resolve the issue.
No hurry, I would be away too, hence, it is ok if you report back on Monday.

Okay I merged and tested, the logs seem the same. So I set CONFIG_BT_LOG_LEVEL_DBG=y and the log is here:
ble.log

@crides Please increase CONFIG_BT_CTLR_RX_PRIO_STACK_SIZE to some high value like 1024 and check if you still get an assertion. I am suspecting that enabling logging needs more stack size in each active thread, you may increase all CONFIG_*_STACK_SIZE  Kconfig to high value and check using the following to ensure stack usage is within limits.
CONFIG_THREAD_ANALYZER=y
CONFIG_THREAD_ANALYZER_AUTO=y
CONFIG_THREAD_ANALYZER_AUTO_INTERVAL=5
CONFIG_THREAD_NAME=y

@crides The listed stack usage seem ok, but the main stack and ISR stack are not being listed. Please increase CONFIG_MAIN_STACK_SIZE and CONFIG_ISR_STACK_SIZE both to 2048 bytes and check again if the thread analyzer can list their usage.
I want to rule out stack overflows which can lead to undetermined behaviors.
@carlescufi who can help with, why thread analyzer does not list main and ISR stack usage?

Not sure if this helps, but I slightly dug into what happens right before the assert happens. I added a logging line right after here:
    LOG_WRN("avail %d %d", MFIFO_AVAIL_COUNT_GET(prep), e != 0);

, and it produces the following results (I'm not sure if I'm understanding it incorrectly, but I felt like the AVAIL_COUNT is reversed?):
[00:00:08.829,010] <dbg> zmk: split_listener:
[00:00:08.842,376] <wrn> bt_ctlr_ull: avail 0 1
[00:00:08.849,884] <wrn> bt_ctlr_ull: avail 1 1
[00:00:08.857,391] <wrn> bt_ctlr_ull: avail 2 1
[00:00:08.864,868] <wrn> bt_ctlr_ull: avail 3 1
[00:00:08.872,375] <wrn> bt_ctlr_ull: avail 4 1
[00:00:08.879,882] <wrn> bt_ctlr_ull: avail 5 1
[00:00:08.887,390] <wrn> bt_ctlr_ull: avail 6 1
[00:00:08.894,866] <wrn> bt_ctlr_ull: avail 7 0
ASSERTION FAIL [next] @ WEST_TOPDIR/zephyr/subsys/bluetooth/controller/ll_sw/nordic/lll/lll.c:653

[00:00:08.894,897] <err> os: r0/a1:  0x00000003  r1/a2:  0x0000000c  r2/a3:  0x0000000b
[00:00:08.894,927] <err> os: r3/a4:  0x200036f0 r12/ip:  0xdfffdbbc r14/lr:  0x0001c01d
[00:00:08.894,927] <err> os:  xpsr:  0x61000028
[00:00:08.894,927] <err> os: Faulting instruction address (r15/pc): 0x0001c028
[00:00:08.894,958] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:08.894,989] <err> os: Fault during interrupt handling

[00:00:08.895,019] <err> os: Current thread: 0x20004390 (idle 00)
[00:00:09.378,784] <err> os: Halting system

Notice each log line is separated by 7.5ms, i.e. 1 connection interval. So for some reason the prep LLL event queue is not getting consumed, and I can't figure out what caused that now (there's too much radio related code and the search paths diverge really quickly :sweat_smile:)

[00:00:08.829,010] zmk: split_listener:

So this is a split keyboard, and there are 2 devices. The peripheral side establishes connection to the central side to send keypress changes using bt_gatt_notify

@crides I have another PR I was thinking was good, but had no reason to upstream it but please check if the changes in #42678 helps avoid the assertion you see. Thank you in advance for all the help.

I'm still in the process of merging the PR, as now LVGL is moved as a module, I'll need to see how to get this working in ZMK (as currently the way it's setup is a bit weird). I'll let you know the results later

@crides You should cherry-pick the 2 commits https://github.com/zephyrproject-rtos/zephyr/pull/42678/commits/f6aea92dacbe184f476f115103a6647ab64e9c91 and https://github.com/zephyrproject-rtos/zephyr/pull/42678/commits/8fb0be52b59db702ec5201e9e54197c11e67a76a so that there is minimal change to the source base used to reproduce the issue. Will also avoid migrating the application to other upstream changes.

Okay that works, but the assertion remains the same (now it's on line 654 due to the commits).

@crides ok, please provide your zephyr.map file to review if Controller's global variables could be overrun into.

zephyr.map.txt

I do not see anything suspicious in the map file.

So, the problem is resolved.. The cause is that an application stack size is set too low, basically throwing the BLE stack stuff into the void.
Now my question would be, is there any related debugging/error reporting utility related to this? If Zephyr can know the stack usage (somehow), it shouldn't be hard to detect a "stack overflow" when switching out of a task? The stack analyzer seems useful for tuning down the stack allocation, but not for determining if it's enough.

@crides Thanks for following up and help resolve the issue. I do not think there is any runtime detection of the stack overflow other than SoC/Architecture supported CONFIG_MPU_STACK_GUARD, please check if this option catches your issue.

Yep it does:
[00:00:05.407,745] <dbg> zmk: split_listener:
[00:00:05.407,836] <err> os: ***** MPU FAULT *****
[00:00:05.407,836] <err> os:   Stacking error (context area might be not valid)
[00:00:05.407,836] <err> os:   Data Access Violation
[00:00:05.407,867] <err> os:   MMFAR Address: 0x20007238
[00:00:05.407,867] <err> os: r0/a1:  0x2000c780  r1/a2:  0x20008000  r2/a3:  0x00000013
[00:00:05.407,897] <err> os: r3/a4:  0x0000c00d r12/ip:  0x00000002 r14/lr:  0x00000000
[00:00:05.407,897] <err> os:  xpsr:  0x61000000
[00:00:05.407,897] <err> os: Faulting instruction address (r15/pc): 0x0002a6b6
[00:00:05.407,958] <err> os: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
[00:00:05.407,989] <err> os: Current thread: 0x20001270 (unknown)
[00:00:05.766,113] <err> os: Halting system

Would still need some digging after this point to know what exactly caused the problem, but I think this would be a good start to find the problem. Thanks!


add rqt default config and add launch-file to bringup

as everyone is using a different rqt perspective for their respective debug job...doesn't make too much sense to add one to cob_bringup....


refactor

This PR just introduces some refactoring of existing code without any breaking changes.

Coverage increased (+4.2%) to 87.5% when pulling 5f96cc6ae8634450bf8b03e75379eb185dfe4440 on refactor into abd4d914cfefca37cf0fd45cd318ce839f0ae356 on master.


Program fails at 1-2 hours due to lack of memory

Description
The program runs well for 1-2 hours, and then fails. The failure message mentions memory allocation, but I should have more than enough ram. Here is the error message:
<--- Last few GCs --->
t of marking 77 ms) (average mu = 0.226, current mu = 0.114) alloca[28112:000001B8ACB04470]  3894656 ms: Mark-sweep 2045.5 (2061.8) -> 2044.4 (2060.7) MB, 78.5 / 0.0 ms  (+ 0.0 ms in 1 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 78 ms) (average mu = 0.134, current mu = 0.019) finali[28112:000001B8ACB04470]  3894740 ms: Mark-sweep 2045.4 (2061.7) -> 2045.4 (2062.7) MB, 79.8 / 0.0 ms  (average mu = 0.093, current mu = 0.050) allocation failure scavenge might not succeed
<--- JS stacktrace --->
==== JS stack trace =========================================
0: ExitFrame [pc: 00007FF796CB106C]

Security context: 0x0195739c08d1
1: toString [00000365647B1AA1] [buffer.js:~774] [pc=00000044DD4D53F0](this=0x0331f5fc0b69 ,0x0322e97c04b1 ,0x0322e97c04b1 ,0x0322e97c04b1 )
2: arguments adaptor frame: 0->3
3: _write [00000072550F2241] [D:\downloads\3080 buyer\node_modules\ws\lib\receiver.js:~73] [pc=00000044DD...
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 00007FF796115F0F napi_wrap+114095
2: 00007FF7960C0B96 v8::base::CPU::has_sse+66998
3: 00007FF7960C1996 v8::base::CPU::has_sse+70582
4: 00007FF7968D6E9E v8::Isolate::ReportExternalAllocationLimitReached+94
5: 00007FF7968BEF71 v8::SharedArrayBuffer::Externalize+833
6: 00007FF79678B1DC v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1436
7: 00007FF796796410 v8::internal::Heap::ProtectUnprotectedMemoryChunks+1312
8: 00007FF796792F34 v8::internal::Heap::PageFlagsAreConsistent+3204
9: 00007FF796788733 v8::internal::Heap::CollectGarbage+1283
10: 00007FF796786DA4 v8::internal::Heap::AddRetainedMap+2452
11: 00007FF7967AEA2B v8::internal::Factory::NewRawOneByteString+91
12: 00007FF7967B1732 v8::internal::Factory::NewStringFromUtf8+130
13: 00007FF7968D376A v8::String::NewFromUtf8+298
14: 00007FF795FE7821 node::tracing::TraceEventHelper::SetAgent+40561
15: 00007FF7960D956D v8::internal::Malloced::operator delete+2829
16: 00007FF796CB106C v8::internal::SetupIsolateDelegate::SetupHeap+45852
17: 00000044DD4D53F0
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR<EMAIL_ADDRESS>start: npm run build && node build/index.js
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Yeah it does this for me, I just use forever which you can get by doing npm -g install forever and then start the script with this:
forever start build/index.js
then if you type forever logs and copy the log file name into a powershell window you can watch the log run
like:
C:\nvidia>forever logs
info:    Logs for running Forever processes
data:        script                   logfile
data:    [0] C:\nvidia\build\index.js C:\Users\aweav.forever\autY.log
Get-Content  C:\nvidia\build\index.js C:\Users\aweav.forever\autY.log –Wait

I believe #139 fixes this.
Also @zerocarbthirty, nice work around!

@Doridian, do you mind confirming? Looks like it's relevant to that issue.

Thanks, that seems to have fixed the issue for me. I will report back in a few more hours to confirm.

Yeah, #139 should have fixed this


Hi, I want to know how I can use traffic signal!

Hi, I bought the traffic signal on internet.
this consists of basic LED light (red, yellow, green)
but the camera can't recognize these lights.
this sometimes recognize red light.
I saw your videos many times and I guess that the problem is light spread but not exactly.
I want to buy same model you used but It's difficult to find it and get it.
maybe It's my last question.
How can I solve this problem?
  this is my traffic light !
Thank you :)
Merry christmas :))

The classifier included in the folder is for the traffic light I used. You need to retrain the classifier for the object you want to detect. For the stop sign, on the other hand, I trained that classifier with actual stop sign images, that should work in a generic way.

Thank you for your helpful answer!
and I want to try to make classifier file and I've read the reference site you wrote.
and I wonder if how can I note the name of traffic light like red, green in the classfier?
the reference site only teaches me how I can train the picture and make a file.
Danke!

You could threshold images using RGB or HSV model.
May it help~

First you need to locate the traffic light region. I took a short cut, light is based on the position. If you do thresholding, then keep a copy of color images when receiving the stream.

First Train your classifier to know your Trafic light ( the Hardware ) then  use thresholding when the Hardware Detects
Thanks


Pylance crashes when starting, no features are available

Environment data

Language Server version: v2020.10.2
OS and version: local = Mac Catalina 10.15.7, remote via SSH = Ubuntu 16.04.7 LTS
Python version: Anaconda 3.8.5

Expected behaviour
pylance runs without crashing, all features are accessible
Actual behaviour
Install Pylance, set Pylance as Language server. Open Python file. Pylance seems to crash. No suggestions, linting, or any features described are available. Some errors are present in Python Language Server output window.
Downgrading to 2020.9.4 (or 2020.8.2 or 2020.8.3) as suggested in #142 or #321 results in the same error.
Logs

[Info  - 7:28:23 PM] Pylance language server 2020.10.2 (pyright d6db7c90) starting
[Info  - 7:28:23 PM] Server root directory: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist
[Info  - 7:28:23 PM] No configuration file found.
[Info  - 7:28:23 PM] Setting pythonPath for service "project": "/home/jok120/anaconda3/envs/tmp_project/bin/python"
Search paths found for configured python interpreter:
  /home/jok120/build/amber16/lib/python2.7/site-packages
  /home/jok120/anaconda3/envs/tmp_project/lib/python3.8
  /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/lib-dynload
  /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages
  /home/jok120/dev_project
[Error - 7:28:23 PM] stubPath /home/jok120/project/typings is not a valid directory.
[Info  - 7:28:23 PM] Assuming Python version 3.8
[Info  - 7:28:23 PM] Assuming Python platform Linux
[Info  - 7:28:23 PM] Searching for source files
[Info  - 7:28:23 PM] Found 33 source files
[Info  - 7:28:23 PM] Background analysis(1) root directory: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist
[Info  - 7:28:23 PM] Background analysis(1) started
Background analysis message: setConfigOptions
Background analysis message: setTrackedFiles
[FG] parsing: /home/jok120/project/project/utils/download.py (58ms)
[FG] parsing: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/2and3/builtins.pyi [fs read 2ms] (92ms)
[FG] binding: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/2and3/builtins.pyi (52ms)
[FG] binding: /home/jok120/project/project/utils/download.py (7ms)
Background analysis message: markAllFilesDirty
Background analysis message: setFileOpened
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: analyze
[BG(1)] analyzing: /home/jok120/project/project/utils/download.py ...
[BG(1)]   parsing: /home/jok120/project/project/utils/download.py (61ms)
[BG(1)]   parsing: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/2and3/builtins.pyi [fs read 2ms] (101ms)
[BG(1)]   binding: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/2and3/builtins.pyi (36ms)
[BG(1)]   binding: /home/jok120/project/project/utils/download.py (5ms)
[BG(1)]   checking: /home/jok120/project/project/utils/download.py ...
[BG(1)]     parsing: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/2and3/_typeshed/__init__.pyi [fs read 1ms] (13ms)
[BG(1)]     binding: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/2and3/_typeshed/__init__.pyi (1ms)
[BG(1)]     parsing: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/third_party/2and3/typing_extensions.pyi [fs read 0ms] (3ms)
[BG(1)]     binding: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/third_party/2and3/typing_extensions.pyi (1ms)
[BG(1)]     parsing: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/typing.pyi [fs read 0ms] (26ms)
[BG(1)]     binding: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/typing.pyi (10ms)
[BG(1)]     parsing: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/multiprocessing/__init__.pyi [fs read 0ms] (10ms)
[BG(1)]     binding: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/multiprocessing/__init__.pyi (1ms)
[BG(1)]     parsing: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/os/__init__.pyi [fs read 0ms] (16ms)
[BG(1)]     binding: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/os/__init__.pyi (10ms)
[BG(1)]     parsing: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/glob.pyi [fs read 1ms] (1ms)
[BG(1)]     binding: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/glob.pyi (1ms)
[BG(1)]     parsing: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/abc.pyi [fs read 1ms] (1ms)
[BG(1)]     binding: /home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/typeshed-fallback/stdlib/3/abc.pyi (0ms)
[BG(1)]     parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/__init__.py [fs read 0ms] (21ms)
[BG(1)]     binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/__init__.py ...
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/__init__.py [fs read 0ms] (2ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/__init__.py ...
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/checkers.py [fs read 0ms] (2ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/checkers.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/logger.py [fs read 0ms] (11ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/logger.py (3ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/settings.py [fs read 0ms] (3ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/settings.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/misctools.py [fs read 0ms] (31ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/misctools.py (5ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/pathtools.py [fs read 0ms] (20ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/pathtools.py (3ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/doctools.py [fs read 0ms] (2ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/doctools.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/catchall.py [fs read 1ms] (22ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/catchall.py (4ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/utilities/__init__.py (113ms)
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/kdtree/__init__.py [fs read 0ms] (0ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/kdtree/__init__.py (0ms)
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/atomic/__init__.py [fs read 0ms] (4ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/atomic/__init__.py ...

[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/compare.py [fs read 0ms] (22ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/compare.py (11ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/localpdb.py [fs read 0ms] (4ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/localpdb.py (2ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/wwpdb.py [fs read 0ms] (3ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/wwpdb.py (3ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/pdbclusters.py [fs read 0ms] (1ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/pdbclusters.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/blastpdb.py [fs read 0ms] (6ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/blastpdb.py (2ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/psiblast.py [fs read 0ms] (4ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/psiblast.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/blastpdbUniProtKB.py [fs read 0ms] (7ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/blastpdbUniProtKB.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/pdbligands.py [fs read 1ms] (2ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/pdbligands.py (2ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/functions.py [fs read 0ms] (8ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/functions.py (3ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/header.py [fs read 1ms] (7ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/header.py (5ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/dssp.py [fs read 0ms] (1ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/dssp.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/stride.py [fs read 0ms] (1ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/stride.py (0ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/pdbfile.py [fs read 0ms] (15ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/pdbfile.py (8ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/emdfile.py [fs read 0ms] (5ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/emdfile.py (3ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/ciffile.py [fs read 0ms] (3ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/ciffile.py (2ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/starfile.py [fs read 0ms] (6ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/starfile.py (2ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/proteins/__init__.py (149ms)
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/measure/__init__.py [fs read 0ms] (1ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/measure/__init__.py ...
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/measure/measure.py [fs read 0ms] (7ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/measure/measure.py (4ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/measure/contacts.py [fs read 0ms] (7ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/measure/contacts.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/measure/transform.py [fs read 0ms] (4ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/measure/transform.py (1ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/measure/__init__.py (25ms)
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/__init__.py [fs read 0ms] (0ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/__init__.py ...
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/pfam.py [fs read 1ms] (6ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/pfam.py (5ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/uniprot.py [fs read 0ms] (1ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/uniprot.py (0ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/cath.py [fs read 0ms] (5ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/cath.py (3ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/dali.py [fs read 0ms] (6ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/dali.py (4ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/goa.py [fs read 0ms] (7ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/goa.py (7ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/database/__init__.py (44ms)
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/__init__.py [fs read 0ms] (1ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/__init__.py ...
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/msa.py [fs read 0ms] (8ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/msa.py (6ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/msafile.py [fs read 0ms] (8ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/msafile.py (4ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/analysis.py [fs read 0ms] (8ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/analysis.py (4ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/plotting.py [fs read 0ms] (2ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/plotting.py (8ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/sequence.py [fs read 0ms] (1ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/sequence.py (1ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/sequence/__init__.py (51ms)
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/dynamics/__init__.py [fs read 0ms] (4ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/dynamics/__init__.py ...

[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/functions.py [fs read 0ms] (3ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/functions.py ...
[BG(1)]           parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/ensemble.py [fs read 0ms] (4ms)
[BG(1)]           binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/ensemble.py ...
[BG(1)]             parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/conformation.py [fs read 1ms] (7ms)
[BG(1)]             binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/conformation.py (1ms)
[BG(1)]           binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/ensemble.py (12ms)
[BG(1)]           parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/pdbensemble.py [fs read 0ms] (3ms)
[BG(1)]           binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/pdbensemble.py (4ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/functions.py (26ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/ensemble/__init__.py (29ms)
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/__init__.py [fs read 1ms] (1ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/__init__.py ...
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/trajbase.py [fs read 1ms] (2ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/trajbase.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/trajectory.py [fs read 0ms] (2ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/trajectory.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/dcdfile.py [fs read 1ms] (4ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/dcdfile.py (2ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/frame.py [fs read 0ms] (1ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/frame.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/psffile.py [fs read 0ms] (1ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/psffile.py (1ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/trajectory/__init__.py (16ms)
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/__init__.py [fs read 0ms] (1ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/__init__.py ...
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/hic.py [fs read 0ms] (14ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/hic.py (3ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/norm.py [fs read 0ms] (1ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/norm.py (0ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/cluster.py [fs read 0ms] (4ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/cluster.py (1ms)
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/functions.py [fs read 0ms] (2ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/functions.py (0ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/chromatin/__init__.py (25ms)
[BG(1)]       parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/domain_decomposition/__init__.py [fs read 0ms] (1ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/domain_decomposition/__init__.py ...
[BG(1)]         parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/domain_decomposition/spectrus.py [fs read 0ms] (1ms)
[BG(1)]         binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/domain_decomposition/spectrus.py (0ms)
[BG(1)]       binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/domain_decomposition/__init__.py (1ms)
[BG(1)]     binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/prody/__init__.py (799ms)
[BG(1)]     parsing: /home/jok120/project/project/utils/errors.py [fs read 0ms] (3ms)
[BG(1)]     binding: /home/jok120/project/project/utils/errors.py (1ms)
[BG(1)]     parsing: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/tqdm/__init__.py [fs read 0ms] (1ms)
[BG(1)]     binding: /home/jok120/anaconda3/envs/tmp_project/lib/python3.8/site-packages/tqdm/__init__.py (1ms)

<--- Last few GCs --->

[32110:0x7f1884000ab0]    20664 ms: Scavenge 2031.9 (2038.4) -> 2031.7 (2045.2) MB, 5.4 / 0.0 ms  (average mu = 0.199, current mu = 0.239) allocation failure
[32110:0x7f1884000ab0]    20674 ms: Scavenge 2036.3 (2045.4) -> 2036.9 (2046.2) MB, 8.0 / 0.0 ms  (average mu = 0.199, current mu = 0.239) allocation failure
[32110:0x7f1884000ab0]    20682 ms: Scavenge 2036.9 (2046.2) -> 2036.3 (2060.4) MB, 8.5 / 0.0 ms  (average mu = 0.199, current mu = 0.239) allocation failure

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x1376259]
Security context: 0x20bc5729af51 <JSObject>
    1: _skipToEndOfStringLiteral [0x1fbb9ed51109] [/home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/pyright.bundle.js:~1] [pc=0x2f4b0b94a7cd](this=0x00e9b34ffcd9 <JSObject>,6)
    2: _handleString [0x1fbb9ed50d81] [/home/jok120/.vscode-server/extensions/ms-python.vscode-pylance-2020.10.2/dist/pyright.bundle.js:1] [bytecode=0x2a152a4a...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x9dab70 node::Abort() [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
 2: 0x9dbd26 node::OnFatalError(char const*, char const*) [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
 3: 0xb3b18e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
 4: 0xb3b509 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
 5: 0xce68a5  [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
 6: 0xce6f36 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
 7: 0xcf2dca v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
 8: 0xcf3cd5 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
 9: 0xcf537f v8::internal::Heap::HandleGCRequest() [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
10: 0xca4364 v8::internal::StackGuard::HandleInterrupts() [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
11: 0xff2d67 v8::internal::Runtime_StackGuard(int, unsigned long*, v8::internal::Isolate*) [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
12: 0x1376259  [/home/jok120/.vscode-server/bin/d2e414d9e4239a252d1ab117bd7067f125afd80a/node]
[Info  - 7:28:46 PM] Connection to server got closed. Server will restart.
[Error - 7:28:46 PM] Request textDocument/codeAction failed.
Error: Connection got disposed.
    at Object.dispose (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:47:368894)
    at Object.dispose (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:1:309496)
    at _.handleConnectionClosed (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:1:309708)
    at _.handleConnectionClosed (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:47:320424)
    at t (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:1:307817)
    at invoke (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:1:467265)
    at o.fire (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:1:468026)
    at Q (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:47:358467)
    at invoke (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:1:467265)
    at o.fire (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:1:468026)
    at l.fireClose (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:47:348946)
    at ChildProcess.<anonymous> (/home/jok120/.vscode-server/extensions/ms-python.python-2020.9.114305/out/client/extension.js:1:210030)
    at ChildProcess.emit (events.js:228:7)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
[Info  - 7:28:47 PM] Pylance language server 2020.10.2 (pyright d6db7c90) starting
...

This repeats 5 times before VSCode tells me The Python Tools server crashed 5 times in the last 3 minutes. The server will not be restarted..
Code Snippet / Additional information
I am using an SSH development workflow.
Thank you in advance for the help.

Your issue says you're on a Mac, but the logs indicate a Linux system; are you running this remotely or in a docker container such that there's a memory limit? From the GC info, it seems like it's hitting about exactly 2 GB of memory used before crashing.
Unfortunate that the trace cut off the JS stack trace; that'd be the best method to check if this is some sort of parser bug (since that's where it's stuck, it seems).
The 2 GB is suspicious, but if this is the full trace log output, this isn't exactly a lot of files to have analyzed before hitting a memory limit.

Thanks for your quick response!
Yes, I am using a SSH remote development environment and am accessing my Linux workstation using my VSCode on my macbook. I am not using Docker. I'm not aware of any 2GB limit. My workstation should have about 64GB of RAM.
Do you mean to say that there are some more logs I could provide?

No, I just mean that if it's truncated, then it might not show that there are an unusual number of files processed, for example.
Now that I look it up, the default memory limit for node is 2 GB, so this fits with a general OOM.
Is your project + environment somewhere we can test it? It seems like too few files analyzed to have hit the memory limit.

I have my code repository available here but haven't made a reproducible environment anywhere. I also haven't really shared a full development env like that before, though I am a little familiar with Docker containers. Would something like a docker container with my repo + dependencies installed be best for sharing it with you?

If you're using conda, you should be able to write conda list --export to a file to export the deps you have installed.

Sure, here is the output from conda list --export. Just let me know how I can assist.
_libgcc_mutex=0.1=conda_forge
_openmp_mutex=4.5=1_gnu
astroid=2.4.2=py38h32f6830_1
attrs=20.2.0=pyh9f0ad1d_0
autopep8=1.5.4=pyh9f0ad1d_0
backcall=0.2.0=pyh9f0ad1d_0
backports=1.0=py_2
backports.functools_lru_cache=1.6.1=py_0
biopython=1.77=pypi_0
blas=2.16=mkl
boxsdk=2.10.0=pypi_0
ca-certificates=2020.6.20=hecda079_0
certifi=2020.6.20=py38h924ce5b_2
chardet=3.0.4=pypi_0
cudatoolkit=10.2.89=hfd86e86_1
cycler=0.10.0=pypi_0
decorator=4.4.2=py_0
freetype=2.10.3=he06d7ca_0
idna=2.10=pypi_0
iniconfig=1.1.1=pyh9f0ad1d_0
intel-openmp=2020.2=254
ipykernel=5.3.4=py38h23f93f0_0
ipython=7.18.1=py38h1cdfbd6_0
ipython_genutils=0.2.0=py_1
isort=5.6.4=py_0
jedi=0.15.2=py38_0
jpeg=9d=h516909a_0
jupyter_client=6.1.7=py_0
jupyter_core=4.6.3=py38h32f6830_1
kiwisolver=1.2.0=pypi_0
lazy-object-proxy=1.4.3=py38h1e0a361_2
lcms2=2.11=hbd6801e_0
ld_impl_linux-64=2.34=hc38a660_9
libblas=3.8.0=16_mkl
libcblas=3.8.0=16_mkl
libffi=3.2.1=he1b5a44_1007
libgcc-ng=9.3.0=h24d8f2e_16
libgfortran-ng=7.5.0=hdf63c60_16
libgomp=9.3.0=h24d8f2e_16
liblapack=3.8.0=16_mkl
liblapacke=3.8.0=16_mkl
libopenblas=0.3.10=pthreads_hb3c22a3_4
libpng=1.6.37=hed695b0_2
libsodium=1.0.18=h516909a_1
libstdcxx-ng=9.3.0=hdf63c60_16
libtiff=4.1.0=hc7e4089_6
libuv=1.40.0=hd18ef5c_0
libwebp-base=1.1.0=h516909a_3
lz4-c=1.9.2=he1b5a44_3
matplotlib=3.3.2=pypi_0
mccabe=0.6.1=py_1
mkl=2020.2=256
more-itertools=8.5.0=py_0
nb_conda_kernels=2.3.0=py38h32f6830_1
ncurses=6.2=he1b5a44_1
ninja=1.10.1=hfc4b9b4_2
numpy=1.19.1=py38hbc27379_2
olefile=0.46=py_0
openssl=1.1.1h=h516909a_0
packaging=20.4=pyh9f0ad1d_0
pandas=1.1.3=pypi_0
parso=0.5.2=py_0
pexpect=4.8.0=py38h32f6830_1
pickleshare=0.7.5=py38h32f6830_1001
pillow=8.0.0=py38h9776b28_0
pip=20.2.2=py_0
pluggy=0.13.1=py38h924ce5b_3
prody=1.10.11=pypi_0
prompt-toolkit=3.0.7=py_0
ptyprocess=0.6.0=py_1001
py=1.9.0=pyh9f0ad1d_0
py3dmol=0.8.1=pypi_0
pycodestyle=2.6.0=pyh9f0ad1d_0
pygments=2.7.1=py_0
pylint=2.6.0=py38h32f6830_1
pymol=2.4.0=pypi_0
pyparsing=2.4.7=pyh9f0ad1d_0
pytest=6.1.1=py38h924ce5b_1
python=3.8.5=h1103e12_7_cpython
python-dateutil=2.8.1=py_0
python_abi=3.8=1_cp38
pytorch=1.7.0=py3.8_cuda10.2.89_cudnn7.6.5_0
pytz=2020.1=pypi_0
pyzmq=19.0.2=py38ha71036d_1
readline=8.0=he28a2e2_2
requests=2.24.0=pypi_0
requests-toolbelt=0.9.1=pypi_0
rope=0.18.0=pyh9f0ad1d_0
scipy=1.5.2=py38h8c5af15_0
seaborn=0.11.0=pypi_0
setuptools=49.6.0=py38h32f6830_0
sidechainnet=0+unknown=dev_0
six=1.15.0=pyh9f0ad1d_0
sqlite=3.33.0=h4cf870e_0
tk=8.6.10=hed695b0_0
toml=0.10.1=pyh9f0ad1d_0
torchaudio=0.7.0=py38
torchvision=0.8.1=py38_cu102
tornado=6.0.4=py38h1e0a361_1
tqdm=4.48.2=pyh9f0ad1d_0
traitlets=5.0.4=py_1
typing_extensions=<IP_ADDRESS>=py_0
urllib3=1.25.10=pypi_0
wcwidth=0.2.5=pyh9f0ad1d_2
wheel=0.35.1=pyh9f0ad1d_0
wrapt=1.12.1=pypi_0
xz=5.2.5=h516909a_1
yapf=0.30.0=pyh9f0ad1d_0
zeromq=4.3.3=he1b5a44_2
zlib=1.2.11=h516909a_1009
zstd=1.4.5=h6597ccf_2

@johnathanking Is this still occurring?

@johnathanking Is this still occurring?

Thanks for asking, @savannahostrowski. It has started working!

Thanks for asking, @savannahostrowski. It has started working!

Amazing! Thanks for checking. I'll close this but let us know if it pops up again.

Amazing! Thanks for checking. I'll close this but let us know if it pops up again.


vscode server can not launch

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:  1.86
OS Version:  CentOS Linux release 7.9.2009 (Core)

Steps to Reproduce:

open remote ssh and connect
It show the message Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib64/libstdc++.so.6.0.19

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

me too, remote server cant connect, after vscode update

https://github.com/microsoft/vscode/issues/203967
1.86 not support centos7 ,wc

prerequisites said  the 1.86.0 requires glibc 2.28, while centos 7/ rhel 7 use 2.17.  does vscode really need glibc 2.28? can we ignore the version check? 😠

prerequisites said the 1.86.0 requires glibc 2.28, while centos 7/ rhel 7 use 2.17. does vscode really need glibc 2.28? can we ignore the version check? 😠

Maybe you can try version 1.85 https://code.visualstudio.com/updates/v1_85, it works for me. Cheers.

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:  1.86
OS Version:  CentOS Linux release 7.9.2009 (Core)

Steps to Reproduce:

open remote ssh and connect
It show the message Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib64/libstdc++.so.6.0.19

Same thing, same version of VS code, on OS: Sonoma 14.3

Getting the below error after vscode update to 1.86.0
XXXX@XXXXXXX~ $ lsb_release -a
LSB Version:    :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID: OracleServer
Description:    Oracle Linux Server release 7.9
Release:        7.9
Codename:       n/a
XXXX@XXXXXXX ~ $ cat ~/.vscode-server/.05047486b6df5eb8d44b2ecd70ea3bdf775fd937.log
Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib64/libstdc++.so.6.0.19
Warning: Missing GLIBC >= 2.28! from /usr/lib64/libc-2.17.so
Error: Missing required dependencies. Please refer to our FAQ https://aka.ms/vscode-remote/faq/old-linux for additional information.

Check the workaround here: https://github.com/npurson/vscode-server-toolchain-workaround.

Check the workaround here: https://github.com/npurson/vscode-server-toolchain-workaround.

This work 👯

https://github.com/microsoft/vscode/issues/203375

fucking!!! wasting time


Logistical transporters do not disconnect with redstone

Dev 176 and 177's (haven't tested the others) Logistical Transporters (and variants) do not disconnect when applying a redstone signal (regardless of their redstone configuration).
I don't know if this is intended or a bug, so reporting for safety's sake.

If this is intended, could you clarify what is the effect of toggling redstone sensitivity on a logistical transporter?


[BUG] xgcm.transport should check that the input is datarray

Currently you can do something like:
...
grid.transform(ds, ...)

It then fails with some obscure dtype failure. We should have a check that the input is a dataarray.
Just noting this here since that came up during the siparcs meeting
cc @andersy005 @jdldeauna

Ill add a proper code example tomorrow. My brain is done for today

It appears that the target levels are being checked in input_handling decorator, but phi and theta aren't being checked to make sure they are of the right type.
https://github.com/xgcm/xgcm/blob/b68a4c70fdb8ade2e7462a958c810a07b0fbcfdb/xgcm/transform.py#L180-L190

Oh I see. Let me try to submit a PR fixing this.


Emit RPC stats from the browser

Currently stats are emitted on the server for each RPC call but my project now has the use case of understanding how long an RPC call lasts on the client (we want to measure the over the wire time).

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

Hey, sorry about that. Tried to rebase but Github closed it for some reason 🤷♂. Trying to fix it now

So it looks like github only gives me access to your fork if you have an open PR here, so I can't push my rebased branch to it to fix this. I've pushed it to a branch in this repo; push that branch to your fork and re-open this when you get a chance 👍


OfxParserException : Invalid Transaction Amount

When you want to parse an OFX file from a Belgian bank (e.g. FORTIS),
you have an 'Invalid Transaction Amount' exception from Ofx parser.
The transaction amounts are represented with a comma as decimal point.
Client Traceback (most recent call last):
File "/media/data/openerp/server/openerp/addons/web/http.py", line 204, in dispatch
response["result"] = method(self, **self.params)
File "/media/data/openerp/server/openerp/addons/web/controllers/main.py", line 1129, in call_button
action = self._call_kw(req, model, method, args, {})
File "/media/data/openerp/server/openerp/addons/web/controllers/main.py", line 1117, in _call_kw
return getattr(req.session.model(model), method)(*args, **kwargs)
File "/media/data/openerp/server/openerp/addons/web/session.py", line 42, in proxy
result = self.proxy.execute_kw(self.session._db, self.session._uid, self.session._password, self.model, method, args, kw)
File "/media/data/openerp/server/openerp/addons/web/session.py", line 30, in proxy_method
result = self.session.send(self.service_name, method, *args)
File "/media/data/openerp/server/openerp/addons/web/session.py", line 103, in send
raise xmlrpclib.Fault(openerp.tools.ustr(e), formatted_info)
Server Traceback (most recent call last):
File "/media/data/openerp/server/openerp/addons/web/session.py", line 89, in send
return openerp.netsvc.dispatch_rpc(service_name, method, args)
File "/media/data/openerp/server/openerp/netsvc.py", line 292, in dispatch_rpc
result = ExportService.getService(service_name).dispatch(method, params)
File "/media/data/openerp/server/openerp/service/web_services.py", line 626, in dispatch
res = fn(db, uid, *params)
File "/media/data/openerp/server/openerp/osv/osv.py", line 190, in execute_kw
return self.execute(db, uid, obj, method, *args, **kw or {})
File "/media/data/openerp/server/openerp/osv/osv.py", line 132, in wrapper
return f(self, dbname, *args, **kwargs)
File "/media/data/openerp/server/openerp/osv/osv.py", line 199, in execute
res = self.execute_cr(cr, uid, obj, method, *args, **kw)
File "/media/data/openerp/server/openerp/osv/osv.py", line 187, in execute_cr
return getattr(object, method)(cr, uid, *args, **kw)
File "/media/data/openerp/addons/account_statement_base_import/wizard/import_statement.py", line 108, in import_statement
context=context
File "/media/data/openerp/addons/account_statement_base_import/statement.py", line 150, in statement_import
result_row_list = parser.parse(file_stream)
File "/media/data/openerp/addons/account_statement_base_import/parser/parser.py", line 148, in parse
self.parse(*args, **kwargs)
File "/media/data/openerp/addons/account_statement_ofx_import/parser/ofx_parser.py", line 69, in parse
ofx = ofxparse.OfxParser.parse(file(ofx_file.name))
File "/usr/local/lib/python2.7/dist-packages/ofxparse-0.14-py2.7.egg/ofxparse/ofxparse.py", line 345, in parse
ofx_obj.accounts += cls.parseStmtrs(stmtrs_ofx, AccountType.Bank)
File "/usr/local/lib/python2.7/dist-packages/ofxparse-0.14-py2.7.egg/ofxparse/ofxparse.py", line 646, in parseStmtrs
account.statement = cls.parseStatement(stmtrs_ofx)
File "/usr/local/lib/python2.7/dist-packages/ofxparse-0.14-py2.7.egg/ofxparse/ofxparse.py", line 736, in parseStatement
cls_.parseTransaction(transaction_ofx))
File "/usr/local/lib/python2.7/dist-packages/ofxparse-0.14-py2.7.egg/ofxparse/ofxparse.py", line 792, in parseTransaction
six.u("Invalid Transaction Amount: '%s'") % amt_tag.contents[0])
OfxParserException: Invalid Transaction Amount: '-72,00'

Thanks to some contributors ofxparse has better handling of commas as decimals, but I can't speak to how bug-free it is.  Hopefully it works for your use case!


Data set choice: pay attention to use unbalanced data

Data sets with 50% anomalies are not anomaly detection!
More data sets does not mean more meaningful results, because "garbage in, garbage out".
One of the big problems with current anomaly detection research is that we do not use good data sets to evaluate results, hence everything works sometimes by chance, and there is little systematic benefits observable because the data sets are not properly labeled as anomalies.
I am by now convinced that from most of the commonly used data sets, you cannot draw meaningful conclusions because of unsuitable labeling.

Dear Prof. Schubert, thanks for the note. Big fan of your work, e.g., ELKI and DAMI evaluation.
We fully agree with the quality issue(s) in current outlier research, although among the 55 datasets we only have parkinson which is not below 50% outliers. We debated a bit on whether to include this, and finally decided to follow the tradition to include it.
It should not affect the results too much for a few reasons:

one dataset will not play a major role in the analysis
(again) the conclusions are mainly based on the statistical analysis
we also add 7 new datasets (all with 5% anomalies) to enrich the testbed

We are happy to remove parkinson and redo the analysis for the results in the next revision. Thanks again for the heads up.
Please also share any additional thoughts for the paper (https://www.andrew.cmu.edu/user/yuezhao2/papers/22-preprint-adbench.pdf). Appreciate that!

Over 50% would be even more weird, but in fact anything beyond 5% is unrealistic! If you would use anomaly detection in a business setting, and you had even 5% anomalies in your measurements, your system would be unusable. In a realistic scenario, you will likely have <1% or <0.1% anomalies (and even much less when considering time series as individual points - at a measurement rate of 100 Hz, 1% anomalies would mean one anomaly per second), if your consider that an anomaly may mean the machine failed, or the resulting product is defect. To be useful in practical applications, the methods must be evaluated on a scenario where anomalies are very rare.
And class labels are usually unsuitable for outlier detection. Classes themselves may have outliers, and a rare class does not need to be outliers, but can be a highly concentrated blob - or undetectable, because the class is distributed everywhere. Classification data must only be used with care for anomaly detection - and with close human inspection of the results. Outlier detection researchers must stop treating data as a black box, and caring only about the evaluation score; instead they must verify the proposed methods can solve a real  problem, not just overfit some benchmark data with parameter tuning.
I only had a brief look, and in my opinion the paper essentially shows that we can_not_ learn much from this benchmark. Almost all methods are tied within the critical difference; i.e., outlier benchmarks needs to be improved in quality, not quantity.
For example, there is the huge repository of "outlier" data sets at Monash university: https://researchdata.edu.au/datasets-outlier-detection/1370700 with 12338 datasets (missing from your table 1; e.g., On normalization and algorithm selection for unsupervised outlier detection, Sevvandi Kandanaarachchi, Mario A. Munoz, Rob J. Hyndman, Kate Smith-Miles) - in my opinion it suffers from the same problem that the majority of data sets are "distractors", and the entire signal gets lost by adding all those automatically collected data sets; so that in the end we do not learn that much on the algorithms, but rather that our data set collection is unsuitable.
What we need is an "imagenet moment" for anomaly detection: someone that labels a lot of data for actual rare anomalies, instead of abusing data from other domains, downsampling it, and then just looking at the resulting score, and ignoring the real task for this data set.

That is a great point! That is exactly why we pick 5% as a threshold for new datasets (although they are still adapted).
Regarding the absence of more realistic datasets, this is a long-overdue problem. It may be even worse for other data types like graphs, where researchers often inject anomalies to detect. It will be nice if we could collaboratively design some large-scale benchmark datasets. However, it is not an easy task. According to my personal experience with multiple Canadian banks, both the data and the labels are hard to acquire, let alone be released for research.
I may also point to some additional thoughts. First, outliers may be a collection of interesting samples, so the exact percentage is hard to define. 5% sounds nice but it can vary...and maybe 10% also happens in some real-world applications. Second, the number of benchmark datasets still helps, since many of these adapted datasets have naturally semantic meaning. For instance, the binary classification of a rare disease often makes sense in the outlier detection setting. With a large number of datasets, we could run statistical analysis. But I agree more consideration should be put into grouping different datasets. Another reason for considering all these datasets is since many outlier papers are based on a subset of them, our paper reveals that none of these unsupervised methods are actually statistically better. Of course, other interesting points on different perspectives of OD are also discussed in the paper. Happy to see more thoughts on them :)
Again, want to say thanks to your work since a considerate number of datasets in ADBench is based on your DAMI repository and the meta-analysis paper by OSU (https://ir.library.oregonstate.edu/concern/datasets/47429f155?locale=en). Honestly, I think nearly all outlier detection benchmarks are based on these datasets for now, and the values are still high.
I do wish we could collaborate on building more "image-net" benchmark datasets for outlier detection, which can be either based on industry support or more carefully review and selection on existing datasets. I feel many of the existing ones are still suited for outlier detection, given the definition of outliers is naturally vague.
All in all, thanks for interesting discussion and hope to collaborate on something toward this direction. Large-scale analysis and benchmark indeed lays the foundation for fair comparison and model selection. Some of our recent papers are for this (https://openreview.net/forum?id=KCd-3Pz8VjM) :)


Edge function with non 200 response doesn't include response body

Bug report
Describe the bug
When I try to return an error response I get this error:
FunctionsHttpError: Edge Function returned a non-2xx status code
but the response body that I sent from the function is not included.
I try to return the error like this:
...
} catch (error) {
    return new Response(JSON.stringify({
      error: error.message
    }), {
      headers: { ...corsHeaders, 'Content-Type': 'application/json' },
      status: 500,
    })
  }

To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Setup a new edge function with a non 200 response
Start function local
try to call the function via the supabase sdk
See the error

Expected behavior
I expected to get the error message back that I set in the response body.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: macOS
Browser:  chrome
Version of supabase-js: 2.8.0
Version of Node.js: 19.6.0

Additional context
Add any other context about the problem here.

Actually, there's already an issue for it #45. Closing this in favor of the older issue.


Appends 'capitalone/' to all docker images path

Change log

Docker images are fetched from capitalone/ as opposed to earlier

Issue
docker-compose up -d gives error of image not found, as it tries to find docker.io/library/hygieia-* instead of capitalone/hygieia-*
Test Case
docker-compose up -d shouldn't give any image not found exceptions.

@acsrujan - i just tested mon and it worked fine, can you attach tge session with the error?

@jimzucker Uploading the screenshot.

I found a similar issue reported earlier, here: https://github.com/capitalone/Hygieia/issues/168

Did you do a mvn clean package docker:build before this?
Sent from my iPhone
On Apr 27, 2016, at 07:52, Srujan Akmarthi <notifications<EMAIL_ADDRESS>wrote:
@jimzuckerhttps://github.com/jimzucker Uploading the screenshot.
[screen shot 2016-04-27 at 8 10 29 pm]https://cloud.githubusercontent.com/assets/12155020/14856417/96354a54-0cb5-11e6-9376-4e7e7264ab36.png
I found a similar issue reported earlier, here: #168https://github.com/capitalone/Hygieia/issues/168

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/capitalone/Hygieia/pull/529#issuecomment-215108947

@jimzucker
Yes, mvn docker:build helped. Thanks. Not from Java background.


Small fix for the height property when set to auto

Elements with auto height should not be allowed to shrink

@dclaux,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Fix for downloading the Linux linkerd2 binaries

Downloading the linkerd2 client binary failed on the missing architecture suffix in the URL (eg. -amd64).
This is only the case for the Linux client, and adm64 + arm64 are the only available architectures.
This PR fixes downloading the linux linkerd2 clients on amd64 and arm64.
Description
Adds a conditional check on the Arch and updates the download URL accordingly.
Motivation and Context
This fixes running arkade install linkerd on a linux client.
How Has This Been Tested?
Tested by building arkade on a Linux x86_64 machine.
go build main.go install linkerd
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Thank you for the PR. I think I'd feel more comfortable about merging if you also added a commit with a unit test. You'll see how we've done it for the other apps.

Thank you for the PR. I think I'd feel more comfortable about merging if you also added a commit with a unit test. You'll see how we've done it for the other apps.

@alexellis sure thing! I've added a test for the Linkerd download.

@alexellis sure thing! I've added a test for the Linkerd download.

This is great, thank you for adding the test, just one more thing to do: squash those commits into one.
Here is my video on how to do it. https://www.youtube.com/watch?v=8j0H6urZ-bU

This is great, thank you for adding the test, just one more thing to do: squash those commits into one.
Here is my video on how to do it. https://www.youtube.com/watch?v=8j0H6urZ-bU


[FEATURE REQUEST] Ability to provide a WrapMode to ImageBufAlgo::fit

Hello again,
This is pretty much in the same vein as https://github.com/OpenImageIO/oiio/issues/2479
Whereby using ImageBufAlgo::fit, with exact=true, results in warp being called with a wrap mode of WrapBlack.
And my proposed solution would also be to allow an optional argument of wrap=WrapBlack for ImageBufAlgo::fit.
If you'd agree with that, and are comftable, I could make a PR with both changes at the same time?
Many thanks

Closed due to merge of #2341


Ot visual widget proposal

Motivation
Adds widgets for diagnostics, for use in Jupyter notebooks.
Changes proposed
Adding new user interactivity to model diagnostics.
Test Plan
Tests forthcoming. This is already a big change.
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] The title of my pull request is a short description of the requested changes.

Looks like we will need to update the GH actions to include per-file ignores for flake8.
https://flake8.pycqa.org/en/latest/user/options.html#cmdoption-flake8-per-file-ignores
I've added the # flake8: noqa flag  to ignore the modules with escape characters it does not have rules for.

Looking at the GH actions, it looks like we are using ufmt to ensure black and usort have been run on the files for linting purposes. I've installed ufmt and run it on the files for this PR, and it shows not formatting errors. I also ran black and usort with no errors, so I'm not sure why the linting step is not passing.

Thanks for doing this, looks like lint passes now :) I probably won't review the source code very closely, but give us some time this week to play around with it and lightly stress test it before merging.

@jpchen Thanks for the fix. The code for the individual widgets all follow the pattern outlined below.

compute the data needed for the widget
transform the computed data into a Bokeh ColumnDataSource
create figure(s)
create glyphs
create annotations
create a help page for the widget
modify the document the widget exists in and

bind data to the glyphs and glyphs to the figure(s)
bind annotations to the figure(s)
create widgets (buttons, lists etc)
create callbacks from the widgets to update the figure(s)
reset figures if needed

show the widget

When you run the Widgets.ipynb, you will see how each one will render in the notebook. This is still just a proposal, which is why it is not in src. I look forward to the stress testing and further updating of the widgets

This is one of the items I am going to close in favor of a new issue that encapsulates all the visual diagnostics tools in one place.

SGTM

closing in favor of a new issue outlining the tools


Add schema

Link to discussion on Slack

@rezrah No, the attributes I added just came from my own research on schema.org. If there's someone internally with more knowledge on these specific schemas then I'd gladly have them look over it


Missing quick fix in .vue files

Hi,
I've been experimenting with volar lately for our vue 3 apps, and I must say I'm very impressed!! :) Especially about the component typing (props and emits) in the template - this has been the big missing feature of Vetur.
I've discovered a number of minor issues, so I'll report them as separate issues. First I'm missing the quick fix (ctrl + .) command in .vue files. I'm using it all the time to add missing imports, so it would be great to have :).

hi @gertqin, small problems sometimes have a big impact on DX, so these are all important.
thanks for reporting these!

Supported in 0.22.0.

It works great, but I've found one case where it doesn't: in script setup if there is no import statement

If there is an import statement, then it works. :)

@gertqin Thanks to let me know, I will fix this. :)


Charm blocks legacy relation if it cannot connect to database

Updating the endpoints will block the relation if it cannot connect and get the version of the database. I don't think we can clear the status. We should most probably retry the hook until connectivity recovers.

Yeah, that blocked status is not being cleared. We should work on something like you commented on.

@dragomirp the initial links points nowhere. Did we remove those blocking status?

@dragomirp the initial links points nowhere. Did we remove those blocking status?

No, it's still here: https://github.com/canonical/postgresql-operator/blob/8c47bae588ba2c77c95a33f613a6d2ebe82197a9/src/relations/db.py#L322-L329

IMHO, we should replace it to Error for now... and juju resolve will be a way to re-try when PG is up... WDYT?

I don't think we should be calling the DB here at all, we should get the version from the snap.

Good point. Is it safe during the charm refresh? Snap is new on the first unit / but Primary DB is still old, etc.

Data is set (I'm not sure it's updated) per unit, so each unit should report its own PG version.


Support new TigerBeetle functionality

Requires #24
Problem
query_accounts and query_transfers TigerBeetle requests (and QueryFilter) not yet supported.
Solution
Implement:

QueryFilter record;
query_accounts request;
query_transfers request.

FCM
Support new TigerBeetle functionality (#26)

- add `QueryFilter`
- impl `Client::query_accounts` and `Client::query_transfers`


reshape after view is wrong

Describe the bug
Linear followed by a view leads to incorrect result, tensorflowjs complains shape mismatch [NULL, output_size]. changing
    reshape = keras.layers.Reshape([-1], name=tf_name) to match the input shape seems to fix the problem
To Reproduce
Snippet of your code
x = x.view(self.batch_size, -1)
self.output = nn.Linear(x.shape[1], output_size)

I find the same problem,so how can you handle it?

https://github.com/nerox8664/pytorch2keras/pull/77
had a pull request, fixed my problem but didn't get merged


Replace regexes with proper IPFS path validation

As suggested in https://github.com/ipfs/notes/issues/92#issuecomment-172135885 and  https://github.com/lidel/ipfs-firefox-addon/issues/43 we should stop using regexes for detecting IPFS paths  and come up with something more future-proof that involves js-multiaddr and js-multihash.
First step would be to create internal PoC in lib/ipfs-path-validation.js with isValidIPFSPath(path) method  and then refactor addon to use it instead of  gateways.IPFS_RESOURCE and protocols.IPFS_PATH regexes.

I've been updating on ipfs-chrome-station and ended up publishing is-ipfs to check if the hashes and urls are valid or not using js-multihash.
Let me know if you also want to use it and if there is anything I can add there to make it more helpful :)

A quick brain dump on this.
It should be trivial, but in current Firefox ecosystem it is not. :crying_cat_face:
For some background, a quote from this discussion:

What mozilla did was creating a different CommonJS (and not up to date with the latest spec) environment than node. So no, it's not node.js and it doesn't claim to be, it just happens to use the same base API. It doesn't do any hard checks, yes, but it doesn't claim to be compatible with the "engine" "nodejs", which all packages on npm are assumed to be compatible with by default (which is not true, afaik).
It means that most npm packages aren't usable out of the box.

In short, even if a library does not use Node-specific APIs, module resolution is broken in subtle ways:
const isIPFS = require('is-ipfs')

ends with:
Message: Module `is-ipfs` is not found at resource://gre/modules/commonjs/is-ipfs.js

I did some experiments and relative paths work fine, for example:
const isIPFS = require('../node_modules/is-ipfs/index.js')

produces a new error this time for its dependency:
Message: Module `bs58` is not found at resource://gre/modules/commonjs/bs58.js

Ok,  it should be possible to go over every dependency and fix require paths via sed/awk, but overriding files in node_modules feels dirty.
WebExtensions (https://github.com/lidel/ipfs-firefox-addon/issues/20) won't be ready any time soon, so it needs to be solved somehow. I'll look into this in spare time.

They say here that it just work: https://developer.mozilla.org/en-US/Add-ons/SDK/Tutorials/Using_third-party_modules_(jpm)

It "just works" for a limited number of  modules that are tagged with jetpack.
Everything else is trial & error and requires manual workarounds I described (if you are lucky).
This mess is one of reasons why WebExtensions are developed as an alternative to current addon ecosystem.

Ok, deep into a rabbit hole: CommonJS is unable to load multihashes via relative paths
(is-ipfs, bs58 and base-x seem to load fine, or at least did not produce any error yet)
const isIPFS = require('../node_modules/is-ipfs')
const b58 = require('../node_modules/bs58/index.js')
const baseX = require('../node_modules/base-x/index.js')
const multihashes = require('../node_modules/multihashes/dist/multihashes.js')

multihashes package seems to be invisible to CommonJS from Firefox
(perhaps due to the lack of index.js?):
Message: Module `multihashes` is not found at resource://gre/modules/commonjs/multihashes.js

At this point I stopped. It does not seem to work for anything bigger than 'hello world' and there is a multitude of open tickets for NPM support:

https://bugzilla.mozilla.org/show_bug.cgi?id=1168238
https://bugzilla.mozilla.org/show_bug.cgi?id=1231453
https://bugzilla.mozilla.org/show_bug.cgi?id=1187958
https://github.com/mozilla-jetpack/jpm/issues/5#issuecomment-33917757

It's just broken and I don't think it will be fixed for old SDK – all development goes into WebExtensions these days. It will probably be solved there.

I've read that alternative way to run NPM packages in Firefox is via Browserify shims.
I gave it a try and it works fine:
browserify -r is-ipfs -s module.exports > lib/is-ipfs.js

const isIPFS = require('./is-ipfs.js')
isIPFS.multihash('QmYjtig7VJQ6XsnUjqqJvj7QaMcCAwtrgNdahSiFofrE7o')

console.log: ipfs-firefox-addon: is-ipfs-test:true

There are two downsides:

All NPM dependencies are concatenated and wrapped in one big file:

-rw-r--r-- 1 lidel lidel 53K Feb  9 19:07 lib/is-ipfs.js

When used extensively, addons have hard time going trough Review Process (example – this addon got rejected for 43K shim)

I think I'll give it a try, following the feedback from linked example (avoiding redundant shims etc).

Ok, so Firefox SDK provides some Node-compatible libraries, but under different names.
Luckily JPM supports name overrides via package.json:
+"jetpack": {
+    "overrides": {
+        "buffer": "sdk/io/buffer"
+    }
+  },

Having that, I was able to hot-swap the implementation and remove all shims:
browserify -r is-ipfs -im --no-builtins -s module.exports > lib/npm/is-ipfs.js

Produced:
-rw-r--r-- 1 lidel lidel 7.7K Feb  9 22:25 lib/npm/is-ipfs.js

This contains only multihash-related code and should be easier to review :balloon:

Oh, sorry I wasn't following this thread, but glad that you got it working :)
Do you think we should publish the browserified version too on is-ipfs?

No, npm package is enough. I have it as a dependency in package.json and automatically convert it to the Firefox-compatible form during the build step.
I'll leave it this way as a workaround until Firefox gets proper npm package support in new API called WebExtensions (https://github.com/lidel/ipfs-firefox-addon/issues/20).


bug fix and add images

The "Miami" issue fixed. Originally we were requesting hotels with 2022 availability.
The ticketmaster API pull has been change to only filter for concerts not sporting events.
Updated the ticketmaster pull to include an image of the specific artist.

Reviewed and approved


Upcoming change: Not counting photos and links in 140 character count

"The social media company will soon stop counting photos and links as part of its 140-character limit for messages, according to a person familiar with the matter." (Source)
Will this library be updated to match these changes?

Update: It's official.  Any thoughts on if and when this library will be updated?  Thanks! :)

any ideas how to handle this changes? are you familiar with other Gems that might already updated for this change?

I haven't looked for other related gems.  However, the library seemed to count characters accurately before, and this change simplifies the system instead of complicating it.  The actual changes are probably actually pretty simple - the more involved part would be putting together updated unit tests.  From what I recall, Twitter is phasing this in for users over the coming months, so it's low-priority for me until it's deployed for everyone.  If at that point Twitter hasn't updated this library, I guess I'll just have to jump in and do it myself. :/

Is Twitter planning to update this when the new system is rolled out? We have been relying on this for years to provide instant feedback to users on Tweet length and validity as they are creating Tweets. While, as @rinogo commented, tweaking the current code is quite feasible, it would be very nice to be able to keep relying on an official library.

Looking into our plans for this at the moment.

Yes.
I work at Twitter on the tweet composer and the upcoming changes that were
announced. We use this library as well in our own products, including the
Twitter service that rejects tweets when they are too long.
I'm not sure what date exactly, but the library will get updated to do the
correct thing.
Tom
On Jun 1, 2016 8:16 AM, "Andy Piper"<EMAIL_ADDRESS>wrote:

Looking into our plans for this at the moment.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/twitter/twitter-text/issues/117#issuecomment-223025706,
or mute the thread
https://github.com/notifications/unsubscribe/AACKBGdgJ0j7YzGx7NvI1_-qWSgDRcJzks5qHaIwgaJpZM4Igslw
.

Any idea when this update will go live?

According to https://dev.twitter.com/overview/api/upcoming-changes-to-tweets
The rules of tweet text counting are still the same, they don't automatically give you back characters unless you change the way you create the tweet when you call status/update. Specifically,

If your app attaches images using media_ids param instead of injecting urls in the tweet text, then you won't pay a 24 char penalty anymore (when available)
Your app can inject a quote tweet (retweet with comment) using attachment_url param (when available) instead of adding a tweet's link, so it would not count against 140. Note you can't do two attachments, you either have media_ids or attachment_url.
If your app strips leading @mentions from the beginning of the status and instead relies on the auto_populate_reply_metadata param + in_reply_to_status_id param to generate up to 50 implicit reply mentions at the beginning of the extended tweet (when available) then the auto generated reply names don't count against your 140.

What is not changing - any @mentions or links you place in the status text will still be counted against 140 like always. The only way to get the benefit is to use the new metadata params.
twitter-text is more about calculating the length of the status part of the tweet, not the tweet + optional prefixes and attachments. So I don't know that we need to change anything in this library. Do you have any suggestions after reading that document?
Notice I said when available in every case - these new modes are not enabled yet. I don't know the launch plan exactly, stay tuned. I just want to you be aware that twitter-text probably won't need to be changed to accommodate this.

My understanding of that doc is that if I want to send a regular tweet (not a reply/DM) with @mentions at the start of my update, I will just add those mentions at the start of my text and send them. There is no talk in that doc of another param for @mentions. So what you are saying is I need to preprocess my message before I send it to twitter-text?

The changes do not affect creating an original tweet with @mentions in it. You would still do that the same way as today. It only adds an alternate way you can prepend up to 50 users in a reply without losing characters.
If you want to prepend any @mentions to the beginning of an original tweet, they count against the 140 and you may as well use twitter-text to count them as you would today.

@brianc-sprout if you are creating a new Tweet, then @mentions (at the beginning of the Tweet or anywhere else inside it) will count towards 140.
If you reply-to an existing Tweet (note that the Tweet must still exist or the status update will fail), and supply the new auto_populate_reply_metadata value, then any existing @mentions will be moved out of the 140 on the server side. You are still limited to 140 characters, including any new @mentions you may add to the new text.
Currently I'm inclined to agree with @twuttke that twitter-text may not need significant updates since the way we handle link shortening etc will be the same, the text value handed to statuses/update will continue to be 140 characters even if the underlying value in resulting Tweet object may end up larger due to @mentions prepended on the server side, and the trailing media or attachment URL.
We will continue to work with the community and share any updates if we make them internally around this library, but we don't have specific dates to share at this stage.

Thanks for your insights and the helpful discussion, everyone!
I think I agree with @twuttke and @andypiper - this library may not be the right place to solve this problem.  The task of separating a Tweet's text from the associated metadata (e.g. media_ids, auto_populate_reply_metadata, and in_reply_to_status_id) is not the responsibility of this library.
For those of us maintaining legacy apps (or building new ones), it might be useful to highlight what seems to be a philosophical shift at Twitter.  In the distant past, a Tweet was seen as a string of raw text (often supplied via SMS) that Twitter would parse to add extra functionality to - adding links for @mentions, hashtags, URLs, etc.  It seems that these changes (and the "near future" changes with attachment_url) continue the trend of moving away from "raw text" typed in by the user and instead favoring "raw text" with associated metadata.  While this may seem obvious, the implication is that we should likely be designing/upgrading our apps with separate UI elements to acquire media URLs, the attachment URL, etc.

Thanks @twuttke and @andypiper . I had read an earlier form of their doc and it was nebulous where all the new @mentions fit in. The most recent doc makes it much clearer that it is only for replies.

(NB I was the author of the doc, so can only apologize for any confusion!) 😄

@andypiper - I'm not sure if you were the same one who made the updates to the original doc, but regardless, thanks to whomever added the bit hinting about the similar "near future" changes with attachment_url.  Very helpful to have a longer-term vision of where the API is headed.


istio-ingressgateway fails on reconcile after modifying it's Deployment by adding unsigned image to the pods when Warden is present

Needs re-estimation as it doesn't ONLY involve Warden
Conditions:

Warden and it's label on istio-system namespace present in the cluster

Description
If user modifies istio-ingressgateway Deployment by adding container with unsigned image it ends up being blocked by Warden. In such scenario Istio reconciliation fails and the IstioCR ends up in the Error state.
EDIT: applies also to istiod

Expected result
istio-ingressgateway is reconciled back to the proper state and IstioCR does not end up in the Error state. Reconciliation does not fail.

Actual result
istio-ingressgateway is not reconciled back to the proper state and ends up hanged in CrashLoopBackOff state with IstioCR in the Error state. Also the reconciliation fails.

Steps to reproduce

Add another container to the istio-ingressgateway Deployment's pods spec with unsigned image which will be blocked by Warden (example: busybox:latest)

      - image: busybox:latest
        imagePullPolicy: IfNotPresent
        name: somename
      - ... #ig containers defined here

Remove old replicaset for istio-ingressgateway
Restart Istio Operator to trigger the reconciliation

After initial investigation, for now I can say the following:

It is not related to Warden. It will happen on every Istio Deployment or Daemonset when one of the Pods will not get status Running. Either it's caused by warden or anything else
Istio uses Helm to install the Istio components
There is no way to control related behavior from our code level

write a troubleshooting guide how to fix that manually.


Mongo Shell VsCode

Repro steps:
db.Users.aggregate( [ { $match : { "UserName" : "test" } } ] );
Action: cosmosDB.executeMongoCommand
Error type: ENOENT
Error Message: Could not find Mongo shell. Make sure it is on your path or you have set the 'mongo.shell.path' VS Code setting to point to the Mongo shell executable file. Attempted command: "C:\Program Files\MongoDB\Server\4.0\bin"
Version: 0.8.0
OS: win32

You would need the path to contain the exe file. In this case, C:\Program Files\MongoDB\Server\4.0\bin\ mongo.exe .
Let us know if that solves your problem.

I added the following path "C:\Program Files\MongoDB\Server\4.0\bin\mongo" and it worked.
There is no folder in bin called mongo.  I'm assuming its referencingthe executable called mongo which is a bit misleading as the variable refers to the path, not file.

I'm glad it worked, thanks for letting us know.  I did do some refinements to make this clearer, and also added code so we will accept either the folder or the file (#844), so hopefully this will be less confusing from now on.  Thanks for taking the time to report the issue, you've improved the experience for everyone.


Add query operation

Hello. I found this library very cool and useful. Now I want to migrate from FSharp.Data, but didn't find cool feature with query params. So I diceded add it by myself :)
http {
  GET  "someUrl"
  query ["q1", "Query1"
         "q2", "Query2"]
}

Finally I merged your PR. Thanks a lot :)


2023.1: Improvements to Ceph docs & more examples

docs: Minor Ceph changes
docs: Include encryption at rest in Ceph OSD example
docs: Add an example of Ceph messenger v2 encryption at rest
multinode: Revert to default Ceph release & tag

Still draft?

Still draft?

Waiting for Jack to test the secure bit.


⚠ ClamAV has degraded performance

In d40d110, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 598 ms

Resolved: ClamAV performance has improved in aeab8a7.


Store Tiller's releases in ConfigMap

Tiller should store each release inside of a ConfigMap object that is in Tiller's namespace (default helm) and uses a predictable label pattern.
We need to be able to re-construct the history of a release, so as a release is upgraded, we need to store a snapshot of the release. We might be able to do this by treating the ConfigMap as a series of immutable records, and just use labels and annotations to fetch the current ones.

Per the community stand-up meeting today, moving this to Alpha.3.

Wouldn't this make more sense as third-party resource perhaps? It would seem that would be more flexible, as you can define your own schema, rather than being limited to a map[string]string.


How  to get full path apps icon ?

Another Q anyone figure out where "/opt/share/webappservice/apps_icon/FirstScreen/11101200001/250x250.png" or any of the icons actually reside? Would be awesome in an app to show these

That's works for me!
{
"method":"ms.channel.emit",
"params":{
"event":"ed.apps.icon",
"to":"host",
"data":{
"iconPath":path_to_icon,
}
}

Thanks @cHicHillo, It runs on device but not on Post Man

It Not working for me.


Test for docker before attempting to run a container

Test for docker using ping() before attempting any docker operations. If this fails we know docker is unavailable and we can fail with a more descriptive error. Admittedly many people who hit this are running in a docker container so will likely know what this means but there's also users running locally who don't have docker and this will hopefully benefit them.
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

@iain-b this can be closed now right?

yeah it's merged upstream


fp16/bf16 is much slower than fp32

I tested fp16 and bf16 training performance on Intel(R) Xeon(R) Gold 6242 CPU @ 2.80GHz CPU, which I guess does not support fp16 or bf16 computation, however, the training went through without throwing me any errors, but the performance was much worse than fp32. I was wondering how TensorFlow handles such case, i.e. running fp16 or bf16 on a Intel(R) Xeon(R) Gold 6242 CPU @ 2.80GHz CPU.

@zhao1157,
Could you please provide the code you have used or the commands you have run to test the performance and also the TensorFlow version you are using? Thanks!

Tf version tested: 1.14.0 and 2.2.0
Code used: https://github.com/tensorflow/benchmarks/tree/master/scripts/tf_cnn_benchmarks
Command for testing fp32: python tf_cnn_benchmarks.py --input_preprocessor=default --optimizer=sgd --batch_size=50 --data_name=imagenet --model=resnet50 --variable_update=replicated --device=cpu --data_format=NHWC
Command for testing fp16: python tf_cnn_benchmarks.py --input_preprocessor=default --optimizer=sgd --batch_size=50 --data_name=imagenet --model=resnet50 --variable_update=replicated --device=cpu --data_format=NHWC --fp16_loss_scale=500 --use_fp16=True --fp16_vars=False --fp16_inc_loss_scale_every_n=10 --fp16_enable_auto_loss_scale=True
As for bf16, I used Intel's MLPerf v0.7 code https://github.com/mlperf/training_results_v0.7/tree/master/Intel/benchmarks/resnet/1-node-8s-cpx-1-tensorflow/mlperf_resnet, and in run_and_time.sh, we have to set use_bfloat16 True or False to comparing the performance of bf16 and fp32.

Apologies for the delay in response but readme file helps explain the discrepancy.
tf_cnn_benchmarks is no longer maintained. Although it will run with TensorFlow 2, it was written and optimized for TensorFlow 1, and has not been maintained since TensorFlow 2 was released.