Only cpu ram getting used...

I was playing with fine-tuning notebook mentioned in README (bnb-4bit-training.ipynb) with just one change: Instead of fine-tuning specified EleutherAI/gpt-neox-20b model, I was doing the same for a much smaller, TheBloke/guanaco-7B-HF which is itself a merged model based on guanaco-7b.
Instead of using V100's gpu ram, it uses cpu ram only (12GB) and crashes (model files are more than 12GB).
Am I missing something here? Why gpu ram is not being used?

Maybe you should check the BNB debug messages. If bnb is loading libbitsandbytes_cpu.so instead of libbitsandbytes_cuda117.so, then it could only run on CPU ram
===================================BUG REPORT===================================
Welcome to bitsandbytes. For bug reports, please run

python -m bitsandbytes

 and submit this information together with your error trace to: https://github.com/TimDettmers/bitsandbytes/issues
================================================================================
bin /mnt/workspace/your_friend/project/qlora/.env/lib/python3.10/site-packages/bitsandbytes/libbitsandbytes_cuda117.so
CUDA SETUP: CUDA runtime path found: /mnt/workspace/your_friend/project/qlora/.env/lib/libcudart.so.11.0
CUDA SETUP: Highest compute capability among GPUs detected: 8.6
CUDA SETUP: Detected CUDA version 117
CUDA SETUP: Loading binary /mnt/workspace/your_friend/project/qlora/.env/lib/python3.10/site-packages/bitsandbytes/libbitsandbytes_cuda117.so...

Checked this... it seems cuda.so is found ad gpu should have been used. Also verified the same with following commands/code:
! nvidia-smi
Thu Jun  1 06:48:58 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.85.12    Driver Version: 525.85.12    CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Tesla T4            Off  | 00000000:00:04.0 Off |                    0 |
| N/A   44C    P8     9W /  70W |      0MiB / 15360MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

!nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Wed_Sep_21_10:33:58_PDT_2022
Cuda compilation tools, release 11.8, V11.8.89
Build cuda_11.8.r11.8/compiler.31833905_0

import torch
torch.cuda.is_available()

True

Runtime logs before crashing:
Downloading shards: 100%
2/2 [01:20<00:00, 37.03s/it]
Downloading (…)l-00001-of-00002.bin: 100%
9.98G/9.98G [00:58<00:00, 104MB/s]
Downloading (…)l-00002-of-00002.bin: 100%
3.50G/3.50G [00:21<00:00, 260MB/s]

===================================BUG REPORT===================================
Welcome to bitsandbytes. For bug reports, please run

python -m bitsandbytes

 and submit this information together with your error trace to: https://github.com/TimDettmers/bitsandbytes/issues
================================================================================
bin /usr/local/lib/python3.10/dist-packages/bitsandbytes/libbitsandbytes_cuda118.so
CUDA_SETUP: WARNING! libcudart.so not found in any environmental path. Searching in backup paths...
CUDA SETUP: CUDA runtime path found: /usr/local/cuda/lib64/libcudart.so
CUDA SETUP: Highest compute capability among GPUs detected: 7.5
CUDA SETUP: Detected CUDA version 118
CUDA SETUP: Loading binary /usr/local/lib/python3.10/dist-packages/bitsandbytes/libbitsandbytes_cuda118.so...

/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: /usr/lib64-nvidia did not contain ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] as expected! Searching further paths...
  warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/sys/fs/cgroup/memory.events /var/colab/cgroup/jupyter-children/memory.events')}
  warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('//<IP_ADDRESS>'), PosixPath('http'), PosixPath('8013')}
  warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('--logtostderr --listen_host=<IP_ADDRESS> --target_host=<IP_ADDRESS> --tunnel_background_save_url=https'), PosixPath('//colab.research.google.com/tun/m/cc48301118ce562b961b3c22d803539adc1e0c19/gpu-t4-s-2aklubdnrh0vd --tunnel_background_save_delay=10s --tunnel_periodic_background_save_frequency=30m0s --enable_output_coalescing=true --output_coalescing_required=true')}
  warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/env/python')}
  warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('//ipykernel.pylab.backend_inline'), PosixPath('module')}
  warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: Found duplicate ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] files: {PosixPath('/usr/local/cuda/lib64/libcudart.so'), PosixPath('/usr/local/cuda/lib64/libcudart.so.11.0')}.. We'll flip a coin and try one of these, in order to fail forward.
Either way, this might cause trouble in the future:
If you get `CUDA error: invalid device function` errors, the above might be the cause and the solution is to make sure only one ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] in the paths that we search based on your env.
  warn(msg)

Loading checkpoint shards: 0%
0/2 [00:00<?, ?it/s]


Remove InterruptionEventLoop and other refactorings...

This larger draft PR is intended to facilitate discussion about the ongoing design efforts for the dynamical module. Once we reach a consensus around this next phase of design, this will be broken up into substantially smaller PRs.

@eb8680 , is this entirely subsumed by #361 and #356 ?

Closing in favor of #361 and follow-up PRs


2 different form to ejecute ICAP

the important change are in ICAP class
-I added a validation for this case of responses (Line 244-247)

-separate the headers  and calculate the length of it to improve the resquest
-a shot explication of the process of encapsulation(comments)
i prefer you main class,more simple.
and my ICAP/HTTP request maybe don´t work on other server
sorry, i speak spanish. i try to be understandable.
thanks

Thanks for the pull request.
Although your solution is not wrong, I think I'll close this for now. I can see that this could work in some cases, but I'm not confident, that it is a universally working solution, as you point out yourself.
I will think of a way to maybe make it more modular on what the "accept" and "deny" cases should be. Or maybe just let this be some reference code, and let others improve on it.


Create views for Student

Please describe the issue and addacceptance criteria

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


FreeBSD CI builds failing on Cirrus CI

It looks that free version of Cirrus CI cannot be used anymore to test FreeBSD builds.
Maybe it is time to test FreeBSD using VM on Github...
https://github.com/marketplace/actions/freebsd-vm

Additionally there may be added OpenBSD builds: https://github.com/vmactions/openbsd-vm

It is now integrated in CI builds:
https://github.com/Siskin-framework/Builder/blob/master/.github/workflows/rebol.yml
Builds for OpenBSD, FreeBSD and DragonflyBSD are now included in releases:
https://github.com/Oldes/Rebol3/releases/tag/3.17.0


[   22.052644] mmcblk0: error -84 transferring data, sector 9208136, nr 64, cmd response 0x900, card status 0xb00
[   22.062781] mmcblk0: retrying using single block read
[   22.140789] print_req_error: I/O error, dev mmcblk0, sector 9208176
[   22.180447] print_req_error: I/O error, dev mmcblk0, sector 9208177
[   22.354926] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   22.364341] mmcblk0: error -84 transferring data, sector 9434264, nr 8, cmd response 0x900, card status 0x0
[   22.534199] mmcblk0: error -84 transferring data, sector 7993344, nr 32, cmd response 0x900, card status 0xb00
[   22.544279] mmcblk0: retrying using single block read
[   22.624856] mmcblk0: error -84 transferring data, sector 7929888, nr 384, cmd response 0x900, card status 0xb00
[   22.635024] mmcblk0: retrying using single block read
[   22.770672] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   22.835501] gasket: module is from the staging directory, the quality is unknown, you have been warned.
[   22.855913] apex: module is from the staging directory, the quality is unknown, you have been warned.
[   22.873504] apex 0001:01:00.0: can't enable device: BAR 0 [mem 0x00000000-0x00003fff 64bit pref] not claimed
[   22.874439] galcore: loading out-of-tree module taints kernel.
[   22.883588] apex 0001:01:00.0: BAR 2: assigned [mem 0x20100000-0x201fffff 64bit pref]
[   22.897975] apex 0001:01:00.0: BAR 0: assigned [mem 0x20200000-0x20203fff 64bit pref]
[   22.901029] Galcore version <IP_ADDRESS>6507
[   22.905993] apex 0001:01:00.0: enabling device (0000 -> 0002)
[   22.918778] Can't support > 32 bit dma.
[   22.925044] Can't support > 32 bit dma.
[   23.000933] wlan: loading driver v<IP_ADDRESS>
[   23.005973] hif_pci_probe:, con_mode= 0x0
[   23.010102] PCI device id is 003e :003e
[   23.014877] hif_pci 0000:01:00.0: BAR 0: assigned [mem 0x18000000-0x181fffff 64bit]
[   23.023735] hif_pci 0000:01:00.0: enabling device (0000 -> 0002)
[   23.032273]
[   23.032273]  hif_pci_configure : num_desired MSI set to 1
[   23.044267] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[   23.403780] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   23.479153] mmcblk0: error -84 transferring data, sector 9453384, nr 64, cmd response 0x900, card status 0xb00
[   23.560036] hif_pci_probe: ramdump base 0xffff800025200000 size 2095136
[   23.652985] mmcblk0: error -84 transferring data, sector 9453384, nr 64, cmd response 0x900, card status 0xb00
[   23.830509] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   23.874503] mmcblk0: error -84 transferring data, sector 9453384, nr 64, cmd response 0x900, card status 0xb00
[   23.884826] NUM_DEV=1 FWMODE=0x2 FWSUBMODE=0x0 FWBR_BUF 0
[   24.047941] mmcblk0: error -84 transferring data, sector 8001096, nr 136, cmd response 0x900, card status 0xb00
[   24.058104] mmcblk0: retrying using single block read
[   24.209000] mmcblk0: error -84 transferring data, sector 9453384, nr 64, cmd response 0x900, card status 0xb00
[   24.219075] mmcblk0: retrying using single block read
[   24.392160] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   24.433863] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   24.443286] mmcblk0: error -84 transferring data, sector 8001208, nr 8, cmd response 0x900, card status 0x0
[   24.480394] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   24.627215] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   24.636752] mmcblk0: error -84 transferring data, sector 8001208, nr 8, cmd response 0x900, card status 0x0
[   24.842231] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   24.851714] mmcblk0: error -84 transferring data, sector 8001208, nr 8, cmd response 0x900, card status 0x0
[   24.891879] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   25.037809] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   25.083113] mmcblk0: error -84 transferring data, sector 7927808, nr 1024, cmd response 0x900, card status 0xb00
[   25.093365] mmcblk0: retrying using single block read
[   25.200002] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   25.381448] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   25.993616] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   26.375390] print_req_error: 41 callbacks suppressed
[   26.375394] print_req_error: I/O error, dev mmcblk0, sector 7928471
[   26.420105] print_req_error: I/O error, dev mmcblk0, sector 7928472
[   26.458646] print_req_error: I/O error, dev mmcblk0, sector 7928473
[   26.498383] print_req_error: I/O error, dev mmcblk0, sector 7928474
[   26.540155] print_req_error: I/O error, dev mmcblk0, sector 7928486
[   26.584213] print_req_error: I/O error, dev mmcblk0, sector 7928515
[   26.626290] print_req_error: I/O error, dev mmcblk0, sector 7928528
[   26.669537] print_req_error: I/O error, dev mmcblk0, sector 7928553
[   26.712305] print_req_error: I/O error, dev mmcblk0, sector 7928576
[   26.752656] print_req_error: I/O error, dev mmcblk0, sector 7928580
[   26.975225] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   27.079619] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   27.089034] mmcblk0: error -84 transferring data, sector 8001208, nr 8, cmd response 0x900, card status 0x0
[   27.098904] mmcblk0: retrying using single block read
[   27.236666] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   27.279154] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   27.288643] mmcblk0: error -84 transferring data, sector 9453424, nr 8, cmd response 0x900, card status 0x0
[   27.507350] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   27.516834] mmcblk0: error -84 transferring data, sector 7927984, nr 8, cmd response 0x900, card status 0x0
[   27.686636] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   27.759863] mmcblk0: error -84 transferring data, sector 6310568, nr 32, cmd response 0x900, card status 0xb00
[   27.921833] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   27.936591] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   27.946004] mmcblk0: error -84 transferring data, sector 7927984, nr 8, cmd response 0x900, card status 0x0
[   27.955930] mmcblk0: retrying using single block read
[   28.028176] mmcblk0: error -84 transferring data, sector 6310568, nr 32, cmd response 0x900, card status 0xb00
[   28.038257] mmcblk0: retrying using single block read
[   28.071716] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   28.151480] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   28.189085] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   28.201692] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   28.274231] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   28.283706] mmcblk0: error -84 transferring data, sector 7927992, nr 8, cmd response 0x900, card status 0x0
[   28.457384] mmcblk0: error -84 transferring data, sector 7452352, nr 144, cmd response 0x900, card status 0xb00
[   28.632894] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   28.642371] mmcblk0: error -84 transferring data, sector 6310568, nr 8, cmd response 0x900, card status 0x0
[   28.652181] mmcblk0: retrying using single block read
[   28.757396] mmcblk0: error -84 transferring data, sector 7452352, nr 144, cmd response 0x900, card status 0xb00
[   28.767569] mmcblk0: retrying using single block read
[   29.105593] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   29.115073] mmcblk0: error -84 transferring data, sector 7927992, nr 8, cmd response 0x900, card status 0x0
[   29.124885] mmcblk0: retrying using single block read
[   29.168312] mmcblk0: error -84 transferring data, sector 8961216, nr 144, cmd response 0x900, card status 0xb00
[   29.180601] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   29.379233] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   29.391995] mmcblk0: error -84 transferring data, sector 8961216, nr 144, cmd response 0x900, card status 0xb00
[   29.600677] mmcblk0: error -84 transferring data, sector 7452192, nr 160, cmd response 0x900, card status 0xb00
[   29.770984] mmcblk0: error -84 transferring data, sector 8961216, nr 144, cmd response 0x900, card status 0xb00
[   29.781153] mmcblk0: retrying using single block read
[   29.889740] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   30.069571] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   30.078985] mmcblk0: error -84 transferring data, sector 7928008, nr 8, cmd response 0x900, card status 0x0
[   30.088856] mmcblk0: retrying using single block read
[   30.126471] mmcblk0: error -84 transferring data, sector 7452192, nr 160, cmd response 0x900, card status 0xb00
[   30.136640] mmcblk0: retrying using single block read
[   30.225641] mmcblk0: error -84 transferring data, sector 8959008, nr 248, cmd response 0x900, card status 0xb00
[   30.400642] mmcblk0: error -84 transferring data, sector 8959008, nr 248, cmd response 0x900, card status 0xb00
[   30.578869] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   30.622927] mmcblk0: error -84 transferring data, sector 8959008, nr 248, cmd response 0x900, card status 0xb00
[   30.633089] mmcblk0: retrying using single block read
[   30.670347] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   30.801740] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   30.811226] mmcblk0: error -84 transferring data, sector 7928048, nr 8, cmd response 0x900, card status 0x0
[   30.821086] mmcblk0: retrying using single block read
[   30.898092] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   30.943948] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   30.984101] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   30.993514] mmcblk0: error -84 transferring data, sector 7928048, nr 8, cmd response 0x900, card status 0x0
[   31.173192] mmcblk0: error -84 transferring data, sector 6986112, nr 32, cmd response 0x900, card status 0xb00
[   31.183272] mmcblk0: retrying using single block read
[   31.190418] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   31.263881] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   31.282904] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   31.324937] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   31.368154] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   31.377570] mmcblk0: error -84 transferring data, sector 6986112, nr 8, cmd response 0x900, card status 0x0
[   31.557923] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   31.567342] mmcblk0: error -84 transferring data, sector 6986112, nr 8, cmd response 0x900, card status 0x0
[   31.579228] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   31.749591] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   31.759062] mmcblk0: error -84 transferring data, sector 6986112, nr 8, cmd response 0x900, card status 0x0
[   31.933341] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   31.972876] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   31.985732] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   31.995145] mmcblk0: error -84 transferring data, sector 6986112, nr 8, cmd response 0x900, card status 0x0
[   32.199582] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   32.212648] mmcblk0: error -84 transferring data, sector 4963432, nr 56, cmd response 0x900, card status 0xb00
[   32.414572] mmcblk0: error -84 transferring data, sector 4963432, nr 56, cmd response 0x900, card status 0xb00
[   32.453968] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   32.593407] mmcblk0: error -84 transferring data, sector 6986344, nr 136, cmd response 0x900, card status 0xb00
[   32.603576] mmcblk0: retrying using single block read
[   32.672420] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   32.684818] print_req_error: 34 callbacks suppressed
[   32.684821] print_req_error: I/O error, dev mmcblk0, sector 6986360
[   32.727674] print_req_error: I/O error, dev mmcblk0, sector 6986361
[   32.766691] print_req_error: I/O error, dev mmcblk0, sector 6986362
[   32.804572] print_req_error: I/O error, dev mmcblk0, sector 6986363
[   32.844201] print_req_error: I/O error, dev mmcblk0, sector 6986370
[   32.883209] print_req_error: I/O error, dev mmcblk0, sector 6986372
[   32.921021] print_req_error: I/O error, dev mmcblk0, sector 6986373
[   32.959974] print_req_error: I/O error, dev mmcblk0, sector 6986374
[   33.002336] print_req_error: I/O error, dev mmcblk0, sector 6986412
[   33.040112] print_req_error: I/O error, dev mmcblk0, sector 6986413
[   33.080288] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   33.188722] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   33.232575] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   33.242012] mmcblk0: error -84 transferring data, sector 7928112, nr 8, cmd response 0x900, card status 0x0
[   33.408621] mmcblk0: error -84 transferring data, sector 7928112, nr 8, cmd response 0x900, card status 0xb00
[   33.649806] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   33.864041] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   34.035024] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   34.204739] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   34.249614] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   34.259093] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0x0
[   34.430696] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   34.442705] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   34.644998] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   34.814309] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   34.823881] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0x0
[   34.992320] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   35.167758] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   35.344987] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   35.354410] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0x0
[   35.394446] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   35.538973] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   35.708277] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   35.920822] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   35.930817] mmcblk0: retrying using single block read
[   36.037092] mmcblk0: error -84 transferring data, sector 7928200, nr 8, cmd response 0x900, card status 0xb00
[   36.047084] mmcblk0: retrying using single block read
[   36.086255] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   36.125504] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   36.138312] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   36.239570] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   36.479886] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   36.519583] mmcblk0: error -84 transferring data, sector 5283040, nr 144, cmd response 0x900, card status 0xb00
[   36.690801] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   36.700790] mmcblk0: retrying using single block read
[   36.774757] mmcblk0: error -84 transferring data, sector 8324176, nr 144, cmd response 0x900, card status 0xb00
[   36.784865] mmcblk0: retrying using single block read
[   36.950912] mmcblk0: error -84 transferring data, sector 8220464, nr 136, cmd response 0x900, card status 0xb00
[   36.961090] mmcblk0: retrying using single block read
[   37.237197] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   37.394860] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   37.404346] mmcblk0: error -84 transferring data, sector 5308328, nr 8, cmd response 0x900, card status 0x0
[   37.578843] mmcblk0: error -84 transferring data, sector 7928208, nr 8, cmd response 0x900, card status 0xb00
[   37.754458] mmcblk0: error -84 transferring data, sector 5756216, nr 32, cmd response 0x900, card status 0xb00
[   37.764542] mmcblk0: retrying using single block read
[   37.843165] print_req_error: 21 callbacks suppressed
[   37.843169] print_req_error: I/O error, dev mmcblk0, sector 5756242
[   37.989824] mmcblk0: error -84 transferring data, sector 5780368, nr 72, cmd response 0x900, card status 0xb00
[   38.162058] mmcblk0: error -84 transferring data, sector 5781896, nr 136, cmd response 0x900, card status 0xb00
[   38.172231] mmcblk0: retrying using single block read
[   38.257124] print_req_error: I/O error, dev mmcblk0, sector 5781949
[   38.297490] print_req_error: I/O error, dev mmcblk0, sector 5781958
[   38.333030] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   38.345532] print_req_error: I/O error, dev mmcblk0, sector 5781959
[   38.354137] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   38.392474] print_req_error: I/O error, dev mmcblk0, sector 5781960
[   38.431355] print_req_error: I/O error, dev mmcblk0, sector 5781962
[   38.471205] print_req_error: I/O error, dev mmcblk0, sector 5781964
[   38.511222] print_req_error: I/O error, dev mmcblk0, sector 5781971
[   38.550890] print_req_error: I/O error, dev mmcblk0, sector 5781972
[   38.589969] print_req_error: I/O error, dev mmcblk0, sector 5781975
[   38.790725] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   38.974391] mmcblk0: error -84 transferring data, sector 6938336, nr 224, cmd response 0x900, card status 0xb00
[   38.984555] mmcblk0: retrying using single block read
[   38.991741] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   39.077055] mmcblk0: error -84 transferring data, sector 8959008, nr 8, cmd response 0x900, card status 0xb00
[   39.087059] mmcblk0: retrying using single block read
[   39.126655] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   39.166791] mmcblk0: error -84 transferring data, sector 7928208, nr 8, cmd response 0x900, card status 0xb00
[   39.176781] mmcblk0: retrying using single block read
[   39.250253] mmcblk0: error -84 transferring data, sector 5308328, nr 8, cmd response 0x900, card status 0xb00
[   39.260248] mmcblk0: retrying using single block read
[   39.333620] mmcblk0: error -84 transferring data, sector 5283040, nr 144, cmd response 0x900, card status 0xb00
[   39.343727] mmcblk0: retrying using single block read
[   39.717401] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   39.842821] mmcblk0: error -84 transferring data, sector 7461040, nr 144, cmd response 0x900, card status 0xb00
[   39.853013] mmcblk0: retrying using single block read
[   40.085112] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   40.191285] mmcblk0: error -84 transferring data, sector 7043760, nr 24, cmd response 0x900, card status 0xb00
[   40.201402] mmcblk0: retrying using single block read
[   40.234473] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   40.349744] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   40.592661] mmcblk0: error -84 transferring data, sector 5781600, nr 224, cmd response 0x900, card status 0xb00
[   40.604853] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   40.773489] mmcblk0: error -84 transferring data, sector 6646368, nr 136, cmd response 0x900, card status 0xb00
[   40.783662] mmcblk0: retrying using single block read
[   40.884503] mmcblk0: error -84 transferring data, sector 6543424, nr 32, cmd response 0x900, card status 0xb00
[   40.894536] mmcblk0: retrying using single block read
[   40.939951] mmcblk0: error -84 transferring data, sector 5756344, nr 144, cmd response 0x900, card status 0xb00
[   40.950119] mmcblk0: retrying using single block read
[   41.042407] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   41.143243] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   41.329653] mmcblk0: error -84 transferring data, sector 5780368, nr 72, cmd response 0x900, card status 0xb00
[   41.601869] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   41.678042] mmcblk0: error -84 transferring data, sector 7928216, nr 8, cmd response 0x900, card status 0xb00
[   41.850541] mmcblk0: error -84 transferring data, sector 6846880, nr 96, cmd response 0x900, card status 0xb00
[   41.860628] mmcblk0: retrying using single block read
[   42.148214] mmcblk0: error -84 transferring data, sector 8220192, nr 224, cmd response 0x900, card status 0xb00
[   42.158383] mmcblk0: retrying using single block read
[   42.275544] mmcblk0: error -84 transferring data, sector 7458848, nr 224, cmd response 0x900, card status 0xb00
[   42.285740] mmcblk0: retrying using single block read
[   42.442836] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   42.476172] mmcblk0: error -84 transferring data, sector 5780368, nr 72, cmd response 0x900, card status 0xb00
[   42.486284] mmcblk0: retrying using single block read
[   42.660684] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   42.677490] mmcblk0: error -84 transferring data, sector 5781600, nr 224, cmd response 0x900, card status 0xb00
[   42.687650] mmcblk0: retrying using single block read
[   42.846908] print_req_error: 64 callbacks suppressed
[   42.846912] print_req_error: I/O error, dev mmcblk0, sector 5781705
[   42.905970] print_req_error: I/O error, dev mmcblk0, sector 5781777
[   42.921558] mmcblk0: error -84 transferring data, sector 5281824, nr 224, cmd response 0x900, card status 0xb00
[   42.931668] mmcblk0: retrying using single block read
[   43.030857] print_req_error: I/O error, dev mmcblk0, sector 5281968
[   43.069444] print_req_error: I/O error, dev mmcblk0, sector 5281969
[   43.109061] print_req_error: I/O error, dev mmcblk0, sector 5281970
[   43.148804] print_req_error: I/O error, dev mmcblk0, sector 5281971
[   43.190881] print_req_error: I/O error, dev mmcblk0, sector 5281989
[   43.230740] print_req_error: I/O error, dev mmcblk0, sector 5281991
[   43.269290] print_req_error: I/O error, dev mmcblk0, sector 5281992
[   43.287766] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   43.364913] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   43.575403] mmcblk0: error -84 transferring data, sector 6161952, nr 32, cmd response 0x900, card status 0xb00
[   43.748638] mmcblk0: error -84 transferring data, sector 6386624, nr 32, cmd response 0x900, card status 0xb00
[   43.758660] mmcblk0: retrying using single block read
[   43.835399] print_req_error: I/O error, dev mmcblk0, sector 6386649
[   43.844810] mmcblk0: error -84 transferring data, sector 5756248, nr 96, cmd response 0x900, card status 0xb00
[   44.017096] mmcblk0: error -84 transferring data, sector 8319008, nr 224, cmd response 0x900, card status 0xb00
[   44.027265] mmcblk0: retrying using single block read
[   44.247206] mmcblk0: error -84 transferring data, sector 6543480, nr 256, cmd response 0x900, card status 0xb00
[   44.420695] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   44.430109] mmcblk0: error -84 transferring data, sector 5781600, nr 8, cmd response 0x900, card status 0x0
[   44.439984] mmcblk0: retrying using single block read
[   44.515589] mmcblk0: error -84 transferring data, sector 7928216, nr 8, cmd response 0x900, card status 0xb00
[   44.525522] mmcblk0: retrying using single block read
[   44.692437] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   44.705502] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   44.743901] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   44.790311] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   44.799787] mmcblk0: error -84 transferring data, sector 5780408, nr 8, cmd response 0x900, card status 0x0
[   44.972871] mmcblk0: error -84 transferring data, sector 7928216, nr 8, cmd response 0x900, card status 0xb00
[   44.982867] mmcblk0: retrying using single block read
[   45.024227] mmcblk0: error -84 transferring data, sector 7446008, nr 136, cmd response 0x900, card status 0xb00
[   45.034395] mmcblk0: retrying using single block read
[   45.220547] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   45.255863] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   45.296839] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   45.517520] mmcblk0: error -84 transferring data, sector 6543480, nr 256, cmd response 0x900, card status 0xb00
[   45.689443] mmcblk0: error -84 transferring data, sector 5756248, nr 96, cmd response 0x900, card status 0xb00
[   45.699526] mmcblk0: retrying using single block read
[   45.825802] mmcblk0: error -84 transferring data, sector 6161952, nr 32, cmd response 0x900, card status 0xb00
[   45.835884] mmcblk0: retrying using single block read
[   45.879790] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   45.990973] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   46.034203] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   46.077308] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   46.119154] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   46.128622] mmcblk0: error -84 transferring data, sector 6388752, nr 32, cmd response 0x900, card status 0x0
[   46.294368] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   46.309336] mmcblk0: error -84 transferring data, sector 6161984, nr 72, cmd response 0x900, card status 0xb00
[   46.319356] mmcblk0: retrying using single block read
[   46.568672] mmcblk0: error -84 transferring data, sector 8220416, nr 48, cmd response 0x900, card status 0xb00
[   46.578754] mmcblk0: retrying using single block read
[   46.585890] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   46.635523] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   46.644998] mmcblk0: error -84 transferring data, sector 7446136, nr 8, cmd response 0x900, card status 0x0
[   46.654809] mmcblk0: retrying using single block read
[   46.661941] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   46.702242] mmcblk0: error -84 transferring data, sector 6543480, nr 256, cmd response 0x900, card status 0xb00
[   46.712411] mmcblk0: retrying using single block read
[   46.867156] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   46.876707] mmcblk0: error -84 transferring data, sector 5780408, nr 8, cmd response 0x900, card status 0x0
[   46.886595] mmcblk0: retrying using single block read
[   46.958807] mmcblk0: error -84 transferring data, sector 6646296, nr 72, cmd response 0x900, card status 0xb00
[   46.968827] mmcblk0: retrying using single block read
[   47.053102] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   47.227657] mmcblk0: error -84 transferring data, sector 6646560, nr 32, cmd response 0x900, card status 0xb00
[   47.400548] mmcblk0: error -84 transferring data, sector 6643776, nr 32, cmd response 0x900, card status 0xb00
[   47.410631] mmcblk0: retrying using single block read
[   47.490070] mmcblk0: error -84 transferring data, sector 6162040, nr 8, cmd response 0x900, card status 0xb00
[   47.500065] mmcblk0: retrying using single block read
[   47.507202] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   47.580520] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   47.589935] mmcblk0: error -84 transferring data, sector 7043760, nr 8, cmd response 0x900, card status 0x0
[   47.599865] mmcblk0: retrying using single block read
[   47.673645] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   47.715183] mmcblk0: error -84 transferring data, sector 6646560, nr 32, cmd response 0x900, card status 0xb00
[   47.890583] mmcblk0: error -84 transferring data, sector 7445536, nr 224, cmd response 0x900, card status 0xb00
[   47.900756] mmcblk0: retrying using single block read
[   47.943878] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   47.982166] print_req_error: 34 callbacks suppressed
[   47.982170] print_req_error: I/O error, dev mmcblk0, sector 7445544
[   48.027312] print_req_error: I/O error, dev mmcblk0, sector 7445553
[   48.074077] print_req_error: I/O error, dev mmcblk0, sector 7445590
[   48.138584] print_req_error: I/O error, dev mmcblk0, sector 7445716
[   48.179018] print_req_error: I/O error, dev mmcblk0, sector 7445720
[   48.218038] print_req_error: I/O error, dev mmcblk0, sector 7445723
[   48.258802] print_req_error: I/O error, dev mmcblk0, sector 7445729
[   48.271951] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   48.416229] mmcblk0: error -84 transferring data, sector 5282048, nr 256, cmd response 0x900, card status 0xb00
[   48.587433] mmcblk0: error -84 transferring data, sector 6770568, nr 32, cmd response 0x900, card status 0xb00
[   48.597519] mmcblk0: retrying using single block read
[   48.670273] print_req_error: I/O error, dev mmcblk0, sector 6770569
[   48.711560] print_req_error: I/O error, dev mmcblk0, sector 6770584
[   48.751594] print_req_error: I/O error, dev mmcblk0, sector 6770586
[   48.793259] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   48.802737] mmcblk0: error -84 transferring data, sector 7928280, nr 8, cmd response 0x900, card status 0x0
[   48.973062] mmcblk0: error -84 transferring data, sector 6646560, nr 32, cmd response 0x900, card status 0xb00
[   48.983144] mmcblk0: retrying using single block read
[   49.099383] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   49.138435] mmcblk0: error -84 transferring data, sector 6646560, nr 8, cmd response 0x900, card status 0xb00
[   49.312406] mmcblk0: error -84 transferring data, sector 6770568, nr 8, cmd response 0x900, card status 0xb00
[   49.322404] mmcblk0: retrying using single block read
[   49.396827] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   49.406243] mmcblk0: error -84 transferring data, sector 7928280, nr 8, cmd response 0x900, card status 0x0
[   49.416107] mmcblk0: retrying using single block read
[   49.488235] mmcblk0: error -84 transferring data, sector 5282048, nr 256, cmd response 0x900, card status 0xb00
[   49.498404] mmcblk0: retrying using single block read
[   49.655088] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   49.698123] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   49.769564] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   49.782626] mmcblk0: error -84 transferring data, sector 6646560, nr 8, cmd response 0x900, card status 0xb00
[   49.952479] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   49.996751] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   50.006226] mmcblk0: error -84 transferring data, sector 8220520, nr 8, cmd response 0x900, card status 0x0
[   50.181373] mmcblk0: error -84 transferring data, sector 6646560, nr 8, cmd response 0x900, card status 0xb00
[   50.191359] mmcblk0: retrying using single block read
[   50.266815] mmcblk0: error -84 transferring data, sector 6381656, nr 32, cmd response 0x900, card status 0xb00
[   50.276838] mmcblk0: retrying using single block read
[   50.354869] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   50.364345] mmcblk0: error -84 transferring data, sector 8220520, nr 8, cmd response 0x900, card status 0x0
[   50.570932] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   50.613978] mmcblk0: error -84 transferring data, sector 6381744, nr 136, cmd response 0x900, card status 0xb00
[   50.784867] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   50.794285] mmcblk0: error -84 transferring data, sector 8220520, nr 8, cmd response 0x900, card status 0x0
[   50.804158] mmcblk0: retrying using single block read
[   50.912616] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   50.954320] mmcblk0: error -84 transferring data, sector 6381744, nr 136, cmd response 0x900, card status 0xb00
[   50.964544] mmcblk0: retrying using single block read
[   51.087325] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   51.188173] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   51.334335] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   51.478913] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   51.488388] mmcblk0: error -84 transferring data, sector 7928320, nr 8, cmd response 0x900, card status 0x0
[   51.498198] mmcblk0: retrying using single block read
[   51.538474] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   51.579417] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   51.621459] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   51.630874] mmcblk0: error -84 transferring data, sector 7928320, nr 8, cmd response 0x900, card status 0x0
[   51.840015] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   51.849491] mmcblk0: error -84 transferring data, sector 7928320, nr 8, cmd response 0x900, card status 0x0
[   52.020318] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   52.029841] mmcblk0: error -84 transferring data, sector 7928320, nr 8, cmd response 0x900, card status 0x0
[   52.206694] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   52.254260] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   52.263740] mmcblk0: error -84 transferring data, sector 7928320, nr 8, cmd response 0x900, card status 0x0
[   52.451599] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   52.461079] mmcblk0: error -84 transferring data, sector 6268112, nr 32, cmd response 0x900, card status 0x0
[   52.644173] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   52.653664] mmcblk0: error -84 transferring data, sector 7928320, nr 8, cmd response 0x900, card status 0x0
[   52.663496] mmcblk0: retrying using single block read
[   52.744384] hif_pci 0000:01:00.0: loading /lib/firmware/qwlan30.bin failed with error -5
[   52.745136] mmcblk0: error -84 transferring data, sector 6268112, nr 32, cmd response 0x900, card status 0xb00
[   52.752500] hif_pci 0000:01:00.0: Falling back to user helper
[   52.958229] mmcblk0: error -84 transferring data, sector 5281968, nr 8, cmd response 0x900, card status 0xb00
[   53.162378] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   53.171923] mmcblk0: error -84 transferring data, sector 5281968, nr 8, cmd response 0x900, card status 0x0
[   53.181854] mmcblk0: retrying using single block read
[   53.252909] print_req_error: 25 callbacks suppressed
[   53.252912] print_req_error: I/O error, dev mmcblk0, sector 5281968
[   53.299536] print_req_error: I/O error, dev mmcblk0, sector 5281969
[   53.337444] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   53.349925] print_req_error: I/O error, dev mmcblk0, sector 5281970
[   53.357954] mmcblk0: error -84 transferring data, sector 6268144, nr 120, cmd response 0x900, card status 0xb00
[   53.368238] mmcblk0: retrying using single block read
[   53.412907] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[   53.450737] print_req_error: I/O error, dev mmcblk0, sector 6268201
[   53.493261] print_req_error: I/O error, dev mmcblk0, sector 6268234
[   53.531068] print_req_error: I/O error, dev mmcblk0, sector 6268235
[   53.570779] print_req_error: I/O error, dev mmcblk0, sector 6268238
[   53.608697] print_req_error: I/O error, dev mmcblk0, sector 6268240
[   53.648376] print_req_error: I/O error, dev mmcblk0, sector 6268248
[   53.689488] mmcblk0: error -84 transferring data, sector 6268248, nr 8, cmd response 0x900, card status 0xb00
[   53.699479] mmcblk0: retrying using single block read
[   53.767451] print_req_error: I/O error, dev mmcblk0, sector 6268248
[  113.666721] Reset Device
[  113.671430] hif_pci_probe: HIF PCI Free needs to happen here
[  113.677303] hif_pci: probe of 0000:01:00.0 failed with error -5
[  126.180299] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  126.224730] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  126.234161] mmcblk0: error -84 transferring data, sector 7043760, nr 8, cmd response 0x900, card status 0x0
[  126.244053] mmcblk0: retrying using single block read
[  126.313753] print_req_error: I/O error, dev mmcblk0, sector 7043764
[  126.355745] print_req_error: I/O error, dev mmcblk0, sector 7043766
[  126.362621] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  126.405225] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  126.447305] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  126.520981] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  126.530398] mmcblk0: error -84 transferring data, sector 8220520, nr 8, cmd response 0x900, card status 0x0
[  126.703265] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  126.712678] mmcblk0: error -84 transferring data, sector 5781600, nr 8, cmd response 0x900, card status 0x0
[  126.722559] mmcblk0: retrying using single block read
[  126.799165] print_req_error: I/O error, dev mmcblk0, sector 5781607
[  126.805838] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  126.815373] mmcblk0: error -84 transferring data, sector 5308328, nr 8, cmd response 0x900, card status 0x0
[  126.825258] mmcblk0: retrying using single block read
[  126.894630] print_req_error: I/O error, dev mmcblk0, sector 5308330
[  126.902161] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  126.911709] mmcblk0: error -84 transferring data, sector 8220520, nr 8, cmd response 0x900, card status 0x0
[  127.084100] mmcblk0: error -84 transferring data, sector 9453512, nr 24, cmd response 0x900, card status 0xb00
[  127.094130] mmcblk0: retrying using single block read
[  127.128656] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  127.173235] print_req_error: I/O error, dev mmcblk0, sector 9453520
[  127.240151] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  127.284367] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  127.295796] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  127.334588] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  127.378632] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  127.447901] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  127.457379] mmcblk0: error -84 transferring data, sector 5780408, nr 8, cmd response 0x900, card status 0x0
[  127.628744] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  127.638218] mmcblk0: error -84 transferring data, sector 5781600, nr 8, cmd response 0x900, card status 0x0
[  127.648027] mmcblk0: retrying using single block read
[  127.719884] print_req_error: I/O error, dev mmcblk0, sector 5781607
[  127.726508] mmcblk0: error -84 transferring data, sector 6770568, nr 8, cmd response 0x900, card status 0xb00
[  127.736556] mmcblk0: retrying using single block read
[  127.743745] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  127.813990] print_req_error: I/O error, dev mmcblk0, sector 6770569
[  127.821258] mmcblk0: error -84 transferring data, sector 5970736, nr 32, cmd response 0x900, card status 0xb00
[  127.831397] mmcblk0: retrying using single block read
[  127.901673] print_req_error: I/O error, dev mmcblk0, sector 5970738
[  127.939953] print_req_error: I/O error, dev mmcblk0, sector 5970744
[  127.979853] print_req_error: I/O error, dev mmcblk0, sector 5970755
[  128.018962] mmcblk0: error -84 transferring data, sector 6960704, nr 32, cmd response 0x900, card status 0xb00
[  128.029043] mmcblk0: retrying using single block read
[  128.069698] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  128.079111] mmcblk0: error -84 transferring data, sector 8220520, nr 8, cmd response 0x900, card status 0x0
[  128.088986] mmcblk0: retrying using single block read
[  128.190274] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  128.263799] mmcblk0: error -84 transferring data, sector 5780408, nr 8, cmd response 0x900, card status 0xb00
[  128.273734] mmcblk0: retrying using single block read
[  128.375907] mmcblk0: error -84 transferring data, sector 9453528, nr 8, cmd response 0x900, card status 0xb00
[  128.385839] mmcblk0: retrying using single block read
[  128.455725] mmcblk0: error -84 transferring data, sector 5281968, nr 8, cmd response 0x900, card status 0xb00
[  128.465658] mmcblk0: retrying using single block read
[  128.631964] mmcblk0: error -84 transferring data, sector 6962128, nr 144, cmd response 0x900, card status 0xb00
[  128.642071] mmcblk0: retrying using single block read
[  128.649263] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  129.144212] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  129.210284] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  129.606738] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  129.876258] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  129.953022] mmcblk0: error -84 transferring data, sector 5970736, nr 8, cmd response 0x900, card status 0xb00
[  129.963005] mmcblk0: retrying using single block read
[  130.001811] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  130.074914] mmcblk0: error -84 transferring data, sector 6311456, nr 32, cmd response 0x900, card status 0xb00
[  130.245511] mmcblk0: error -84 transferring data, sector 6311456, nr 32, cmd response 0x900, card status 0xb00
[  130.255593] mmcblk0: retrying using single block read
[  130.332200] mmcblk0: error -84 transferring data, sector 6308768, nr 32, cmd response 0x900, card status 0xb00
[  130.342281] mmcblk0: retrying using single block read
[  130.478870] mmcblk0: error -84 transferring data, sector 6308800, nr 40, cmd response 0x900, card status 0xb00
[  130.649459] mmcblk0: error -84 transferring data, sector 6308800, nr 40, cmd response 0x900, card status 0xb00
[  130.659539] mmcblk0: retrying using single block read
[  130.825118] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  130.839312] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  130.877073] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  130.889785] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  130.899197] mmcblk0: error -84 transferring data, sector 6308832, nr 8, cmd response 0x900, card status 0x0
[  130.909123] mmcblk0: retrying using single block read
[  130.946685] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  131.021925] mmcblk0: error -84 transferring data, sector 8240128, nr 32, cmd response 0x900, card status 0xb00
[  131.191381] mmcblk0: error -84 transferring data, sector 8240128, nr 32, cmd response 0x900, card status 0xb00
[  131.201462] mmcblk0: retrying using single block read
[  131.275989] mmcblk0: error -84 transferring data, sector 8240576, nr 136, cmd response 0x900, card status 0xb00
[  131.286156] mmcblk0: retrying using single block read
[  131.351136] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  131.363530] print_req_error: 55 callbacks suppressed
[  131.363533] print_req_error: I/O error, dev mmcblk0, sector 8240577
[  131.378582] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  131.417183] print_req_error: I/O error, dev mmcblk0, sector 8240592
[  131.458095] print_req_error: I/O error, dev mmcblk0, sector 8240609
[  131.496668] print_req_error: I/O error, dev mmcblk0, sector 8240617
[  131.535621] print_req_error: I/O error, dev mmcblk0, sector 8240618
[  131.574604] print_req_error: I/O error, dev mmcblk0, sector 8240620
[  131.608788] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  131.621185] print_req_error: I/O error, dev mmcblk0, sector 8240624
[  131.660137] print_req_error: I/O error, dev mmcblk0, sector 8240625
[  131.697961] print_req_error: I/O error, dev mmcblk0, sector 8240626
[  131.736785] print_req_error: I/O error, dev mmcblk0, sector 8240627
[  132.037891] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  132.072842] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  132.154400] mmcblk0: error -84 transferring data, sector 8240160, nr 224, cmd response 0x900, card status 0xb00
[  132.329293] mmcblk0: error -84 transferring data, sector 8240160, nr 224, cmd response 0x900, card status 0xb00
[  132.339461] mmcblk0: retrying using single block read
[  132.749766] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  132.855692] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  132.928836] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  132.970999] mmcblk0: error -84 transferring data, sector 8271872, nr 32, cmd response 0x900, card status 0xb00
[  133.138454] mmcblk0: error -84 transferring data, sector 8271872, nr 32, cmd response 0x900, card status 0xb00
[  133.148536] mmcblk0: retrying using single block read
[  133.256057] mmcblk0: error -84 transferring data, sector 8273488, nr 136, cmd response 0x900, card status 0xb00
[  133.427511] mmcblk0: error -84 transferring data, sector 8273488, nr 136, cmd response 0x900, card status 0xb00
[  133.437679] mmcblk0: retrying using single block read
[  133.716662] mmcblk0: error -84 transferring data, sector 8271904, nr 224, cmd response 0x900, card status 0xb00
[  133.728845] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  133.895658] mmcblk0: error -84 transferring data, sector 8271904, nr 224, cmd response 0x900, card status 0xb00
[  133.905827] mmcblk0: retrying using single block read
[  134.066530] mmcblk0: error -84 transferring data, sector 6960736, nr 224, cmd response 0x900, card status 0xb00
[  134.235546] mmcblk0: error -84 transferring data, sector 6960736, nr 224, cmd response 0x900, card status 0xb00
[  134.245714] mmcblk0: retrying using single block read
[  134.820774] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  134.927606] mmcblk0: error -84 transferring data, sector 8286720, nr 32, cmd response 0x900, card status 0xb00
[  135.101275] mmcblk0: error -84 transferring data, sector 8286720, nr 32, cmd response 0x900, card status 0xb00
[  135.111295] mmcblk0: retrying using single block read
[  135.253034] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  135.290809] mmcblk0: error -84 transferring data, sector 8286976, nr 136, cmd response 0x900, card status 0xb00
[  135.463047] mmcblk0: error -84 transferring data, sector 8286976, nr 136, cmd response 0x900, card status 0xb00
[  135.473216] mmcblk0: retrying using single block read
[  135.573617] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  136.013244] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  136.214757] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  136.280781] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  136.388728] print_req_error: 82 callbacks suppressed
[  136.388732] print_req_error: I/O error, dev mmcblk0, sector 8287077
[  136.431794] print_req_error: I/O error, dev mmcblk0, sector 8287081
[  136.476750] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  136.518726] mmcblk0: error -84 transferring data, sector 8286752, nr 224, cmd response 0x900, card status 0xb00
[  136.697105] mmcblk0: error -84 transferring data, sector 8286752, nr 224, cmd response 0x900, card status 0xb00
[  136.879450] mmcblk0: error -84 transferring data, sector 8286752, nr 224, cmd response 0x900, card status 0xb00
[  137.086355] mmcblk0: error -84 transferring data, sector 8286752, nr 224, cmd response 0x900, card status 0xb00
[  137.096526] mmcblk0: retrying using single block read
[  137.176276] print_req_error: I/O error, dev mmcblk0, sector 8286768
[  137.226355] print_req_error: I/O error, dev mmcblk0, sector 8286786
[  137.284698] print_req_error: I/O error, dev mmcblk0, sector 8286864
[  137.332287] print_req_error: I/O error, dev mmcblk0, sector 8286898
[  137.374639] print_req_error: I/O error, dev mmcblk0, sector 8286909
[  137.413640] print_req_error: I/O error, dev mmcblk0, sector 8286912
[  137.454697] print_req_error: I/O error, dev mmcblk0, sector 8286917
[  137.495814] print_req_error: I/O error, dev mmcblk0, sector 8286928
[  137.614945] mmcblk0: error -84 transferring data, sector 9479280, nr 72, cmd response 0x900, card status 0xb00
[  137.625050] mmcblk0: retrying using single block read
[  137.756277] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  138.120133] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  138.165480] mmcblk0: error -84 transferring data, sector 9479336, nr 8, cmd response 0x900, card status 0xb00
[  138.177489] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!
[  138.345236] mmcblk0: error -84 transferring data, sector 9479336, nr 8, cmd response 0x900, card status 0xb00
[  138.355231] mmcblk0: retrying using single block read
[  138.427722] sdhci-esdhc-imx 30b40000.usdhc: warning! HS400 strobe DLL status REF not lock!

Hi, The issue is not because of the Older Dev Board as I have the board older than yours working fine with 5.3.
Seems to be there is some issue with emmc as per: https://community.nxp.com/t5/i-MX-Processors/mmcblk1-error-110-transferring-data/m-p/314873#M41477
I am not sure how to fix this one. I would suggest to RMA the product if you have the warranty and try to flash the board always with the latest software only. Thanks!


[Dashboard] [Home] Your Data

[x] Displays up to 8 datasets.
[x] Displays favorited + most recently updated datasets first.
[x] Displays a placeholder / invitation to upload a dataset if the user hasn't created any dataset yet.
[x] Allows ordering and filtering within the module.
[x] Displays a link to "View all your datasets" that links to the datasets page.
[x] Bulk actions are not allowed, so datasets are not selectable.
[x] Datasets in that module are not selectable.
[x] If a quick action changes the number of datasets a reload should be triggered.

Vamos! 👏👏👏


ziti-edge-tunnel: Update image and use jq for livenessProbe

Hi @qrkourier,
This is a follow up of #171. Now that we have jq installed, lets change the livenessProbe command.

Much thanks!


Script - IPv6 for Azure virtual network with two VMs

#please-hold be published for IPv6 for Azure VNET public preview on April 22.
#please-hold

creating a new pr and closing this PR. Thanks!


rtm_connect does not pass all arguments when reconnecting

Description
After starting an RTM session, if there is an error which results in a reconnect, the call to rtm_connect does not pass the value of rtm_start to the reconnect call.
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
slackclient version: 1.2.x 1.3.x
python version: Python 3.6
OS version(s): Windows 10
Steps to reproduce:

Start an RTM session with auto_reconnect True and with_team_state False
slack_client.rtm_connect(with_team_state=False,auto_reconnect=True)
Call rtm_read()
Wait for a reconnect to occur (enterprise/large team) - cannot exactly reproduce

Expected result:
If "with_team_state" is False, it is expected that this boolean is passed to rtm_connect when it is called again upon restart (due to error or exception)
Actual result:
the call to rtm_connect only passes reconect=True to the function and not any other kwargs
Attachments:
From server.py websocket_safe_read() which is called from client.py rtm_read()
https://github.com/slackapi/python-slackclient/blob/07cce9bf15bee2e5151e88374f700fab46381d3d/slackclient/server.py
            except WebSocketConnectionClosedException as e:
                logging.debug("RTM disconnected")
                self.connected = False
                if self.auto_reconnect:
                    self.rtm_connect(reconnect=True)

This also occurs in server.py send_to_websocket()
        try:
            data = json.dumps(data)
            self.websocket.send(data)
        except Exception:
            self.rtm_connect(reconnect=True)

and I'm not sure why but rtm_connect is called without arguments (thus using defaults) in the init method of Server if connect=False is not passed to Server when instantiating it.

Hi @fwump38, Thanks a lot for reporting this issue. This is indeed a v1 bug. I've opened a PR to get this resolved.
I noticed in your report that you're using Python 3.6. I wanted to let you know that using RTM has been significantly improved in v2. If you need any help migrating please let me know and I'd be happy to assist.

@fwump38 I've released a fixed via 1.3.2. Please take a look and confirm if this resolves the issue you were seeing.


AzureFileCopyV4 has modified destination path

Question, Bug, or Feature?
Type: Bug
Enter Task Name: AzureFileCopyV4
Environment

Server - Azure Pipelines

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:
Account: become-education/Development  Release for AccountsCenter-CD > Release-154

Issue Description
Destination path for file copy into storage account blob is correct on V3 but wrong on V4.
The command captured in the log is:
##[command] & "AzCopy\AzCopy.exe" copy "D:\a\r1\a_AccountsCenter-CI\drop" "https://b3m3accountstest.blob.core.windows.net/`$web"  --log-level=INFO --recursive
With V3 the files end up here:  https://b3m3accountstest.blob.core.windows.net/$web
With V4 the files end up here:  https://b3m3accountstest.blob.core.windows.net/$web/drop
Task logs
tasklog_8.log
tasklog_7.log

@davidmw AzureFileCopy4 uses azcopy v10 module vs v7 module in AzureFileCopy3. For task version 4 you can set source as D:\a\r1\a_AccountsCenter-CI\drop\* which will copy contents instead of whole directory

Why has there been a change through commit 0e9c3c69d2e3c7be17b69dd27cb77f44ebf75e9b on Utility.ps1 where the destination path gets a "/" suffixed to it? This makes the copying of files to be made to a VD which is clearly a breaking change and thus rendering our core pipeline functionality to not work as expected.

@marksolbergerbjorkerot to make it consistent with V3 of task. VDs are not getting created in V4 of Task https://developercommunity.visualstudio.com/content/problem/1109500/azure-file-copy-task-drops-file-name-when-using-pr.html

We are facing a similar issue where blob prefixes are handled differently between 4.175.4 and 4.175.4:
As a disclaimer ... we might have been using the task a bit strange/wrong in the first place but nevertheless the behavior changes and our build/release broke.
We had roughly the following settings:
"SourcePath": "$(Build.ArtifactStagingDirectory)/OData/OData.Web.zip",
"BlobPrefix": "$(Build.BuildNumber)/OData.Web.zip",

which previously resulted in
& "AzCopy\AzCopy.exe" copy "D:\a\1\a\OData\OData.Web.zip" "https://xxx.blob.core.windows.net/odata/2<IP_ADDRESS>/OData.Web.zip"  --log-level=INFO --recursive
and now in
& "AzCopy\AzCopy.exe" copy "D:\a\1\a\OData\OData.Web.zip" "https://xxx.blob.core.windows.net/odata/2<IP_ADDRESS>/OData.Web.zip/"  --log-level=INFO --recursive
which causes the final blob url to change from
"https://xxx.blob.core.windows.net/odata/2<IP_ADDRESS>/OData.Web.zip"
to
"https://xxx.blob.core.windows.net/odata/2<IP_ADDRESS>/OData.Web.zip/OData.Web.zip"

(Like @sopelt)
We deploy 'immutable versioned zip files' from a DevOps release pipeline.
e.g. ACC-SomeProductApi-b20201002.4-v<IP_ADDRESS>7-d9e95a1.zip
Recent change breaks this.
Currently we get a blob in the form folder/file.zip
ACC-SomeProductApi-b20201002.4-v<IP_ADDRESS>7-d9e95a1/SomeProductApi.zip

we are reverting this change for now. sorry for inconvenience caused

This will get deployed by end of this week. Closing this issue


Add nda.ac.jp for National Defense Academy

This address is only used for email addresses.

@denshiruko lib/domains/jp/ac/nda: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@denshiruko Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


overlay crashes the game after update 5.01

Title. Game runs normally until you go into any gameplay mode.

Look here for dev-response on identical issue


Optional Forces for ObjectManipulator

Overview
When ObjectManipulator is used on an object with a RigidBody, using forces for near manipulation is now optional and defaults to off. This makes near manipulation of these kinds of objects feel much more responsive.
See issue #8051 for more background.
Changes

Fixes: #8051

Verification
Please help verify that existing samples continue to work. Especially the hands interaction sample.

For other reviewers, turn off whitespace diffing for this change (otherwise the indentation throws off the default diffing rules)

/azp run

Running tests to see how this change affects the test timings

@thalbern do you or @MenelvagorMilsom have any background/history for why we haven't used direct RigidBody.set* functionality in the past?

Otherwise the change seems reasonable - the fact that it has a flag which we can use to flip to the opposite behavior is good as well.
@julenka FYI

Pinged @thalbern offline for historical context

These changes look good to me code-wise, trying to find an appx to test resulting behavior now.

/azp run

Looks like our pipeline does not generate a hololens 2 appx, will follow up for an appx to test

I noticed something strange - while manipulating the green Platonic gameobject in the hand interaction scene in your branch there's a massive performance drop

I compared with latest mrtk_development and it doesn't happen there - though i can't really see how it can be related to your change as it's only happening for me with that one gameobject (has app bar attached)

I noticed something strange - while manipulating the green Platonic gameobject in the hand interaction scene in your branch there's a massive performance drop

I compared with latest mrtk_development and it doesn't happen there - though i can't really see how it can be related to your change as it's only happening for me with that one gameobject (has app bar attached)

neverming! @MenelvagorMilsom  just pointed out this is happening because the manipulated gameobject is selected in the editor as well

@MenelvagorMilsom just pointed out this is happening because the manipulated gameobject is selected in the editor as well

Also @thalbern and @julenka, I think you both already know this, but I just wanted to mention that this new code path is only active if the object being manipulated has a RigidBody and you're interacting with it using near interactions. This was the only case where the lag issue was noticeable.
If the object does not have a RigidBody, or if you're interacting through far interactions, it will still be using the same code path as before.

Tested on device, it feels okay, though when I pick up the cubes or coffee cup I noticed that the movement is not as smooth as I am used to -- the cubes jitter a bit more than normal. Knowing the code change that was made, it makes sense. Can we add an option to smooth that motion so it is not jumpy, and use that as the default? We may be able to re-use existing smoothing code elsewhere in MRTK.

Thank you very much for testing @julenka and for providing feedback. I wanted to add some comments on the smoothing request.
First, I just wanted to verify that you were testing the new code path. I know that may sound like a silly thing to ask, but there are two coffee cups in the  HandInteractionExamples scene and only the one on the right has a RigidBody. So if you are detecting a lack of smoothness on both of them, I believe something else has changed. But if you're detecting a lack of smoothness the the right coffee mug, but the one on the left, then that would be due to the new approach.
Next, I just wanted to mention that IMHO we should be careful about the amount of smoothing we apply for direct manipulation. Obviously we don't want the object jittering, which I agree it currently can do and I'd like to see that improved. But I want to be careful that we don't introduce so much smoothing that it no longer feels like we're directly holding the object. Ideally it would look exactly the same with and without a RigidBody applied.
That brings me to the last point. ObjectManipulator has a method called SmoothTo. This method is the one that is responsible for all of the smoothing done in the regular code path. However, I could never get SmoothTo to work with the RigidBody code path.  Bashfully, I'll admit that I found this confusing and I didn't know where to look for answers. I would love for @thalbern or maybe @keveleigh  or anyone else on the team with physics knowledge could look more into it.
To be honest, the main reason I didn't try harder to solve this is because I didn't want to lose the feeling of being "directly connected" to the hand. Also, it's worth noting that RigidBody has some some smoothing options of its own. The methods called in this PR (RigidBody.MovePosition and RigidBody.MoveRotation) both honor any Interpolation settings applied to the RigidBody. So we could look at figuring out how to apply the SmoothTo function to the RigidBody methods, and we could also look at turning on Unity's Interpolation for the one coffee cup that has a RigidBody. I would absolutely welcome input and help on either approach.

Well, I spoke to soon. I just decided to go back and spend more time on the SmoothTo issue and I fixed it right away. 😏 Sometimes all it takes is walking away for a day. I think what I was doing wrong was applying SmoothTo to the HostTransform instead of the RigidBody. And since the RigidBody moves the transform, things were jumping all over the place.
So, the good news is that I have smoothing working on the RigidBody. The bad news is it now feels "disconnected" from the hand to me again.
Here are some short videos to demonstrate. The first is with smoothing off:

Notice how the coffee cup just plows right through the boxes. Even sends one of them flying. This is what I'd expect if I'm holding the coffee cup and flailing it with my arms. 😁
Now here's with smoothing on:

Notice the lag when I move the cup? It also gets stuck on objects, like when I'm going through the lander. This doesn't feel attached to my hand at all. And this is with smoothing set at the minimum values possible:

If I leave the SmoothTo code in there but turn Smoothing off in the inspector, I get the same behavior as having SmoothTo commented out. So I'm going to update my PR with those changes. But it might be nice to understand at some point why SmoothTo results in such a disconnected feeling even with tiny (0.0001) lerp times.

Well, sorry to pause yet again, but I just realized that if I add SmoothTo back into the Near Manipulation path then it will be applied to both Far and Near manipulations. I don't think this is right. I think Smoothing (and the behavior demonstrated in the second video above) is correct for Far manipulations. Just not for Near ones.
If the user has to turn Smoothing off to make Near manipulations feel correct, then Far manipulations will no longer feel correct.
Waiting on input from the team.

Unfortunately today I accidentally broke the link to my repository. (Long story, but It's saying "unknown repository".)
It looks like the PR is open and still valid, but if we want to make any of the changes above I may need to start the PR over. I do still have the files in a branch so the changes aren't lost. I just broke the connection from this PR to the original branch in my fork. :(

First, I just wanted to verify that you were testing the new code path. I know that may sound like a silly thing to ask, but there are two coffee cups in the HandInteractionExamples scene and only the one on the right has a RigidBody. So if you are detecting a lack of smoothness on both of them, I believe something else has changed. But if you're only detecting a lack of smoothness the the right coffee mug, that would be due to the new approach.

Yes, I was using the coffee cup with the rigidbody, which is where I noticed the jumpy behavior.
RE: should we use default smoothing on or off:

I have not spent much time with direct manipulation of objects as rigidbodies, but you have! Therefore I believe you have more relevant experience here. As long as we can turn smoothing on for the rigidbody case, I'm okay with having smoothing off by default for rigidbodies specifically.
Please leave non-rigidbody smoothing on. For non-physics interaction we have found that people prefer smooth behavior even if it is a little disconnected from the hand.

Pleas feel free to open up a new pr, we can close this one. Sorry to hear you lost your branch.

Closing in favor of #8204


Use LinuxAdmin::SubscriptionManager directly.

Depends on https://github.com/ManageIQ/linux_admin/pull/197 and a new release of linux_admin v1.2.0
LinuxAdmin::RegistrationSystem can't auto-detect the type when using SubscriptionManager with a proxy due to its need to use the proxy info to validate that it is registered.
Since RHN is no longer supported, we can use the SubscriptionManager class directly.
Also, pass the registration options (proxy info) to the registered? method since it is required when using a proxy.
Add linux_admin to the Gemfile since we use it directly.
https://bugzilla.redhat.com/show_bug.cgi?id=1518695

Gaprindashvili backport details:
$ git log -1
commit 6a0532f72226251ec6a8bb35daa60217ee0438dc
Author: Nick Carboni<EMAIL_ADDRESS>Date:   Wed Dec 6 18:29:20 2017 -0500

    Merge pull request #16610 from bdunne/subscription_manager_with_a_proxy

    Use LinuxAdmin::SubscriptionManager directly.
    (cherry picked from commit 1bfd713ca66128d1dc4254e35d69c8bbf7e57830)

    https://bugzilla.redhat.com/show_bug.cgi?id=1524580


Can We add zoom functionality ? Is it possible ?

Hello Adam,
Can We add zooming feature so that user can draw with perfection ? What we will have to do to achieve zooming functionality ?
Waiting for your answer.
thanks.

For Loose Leaf, I found the best way to handle zoom was to set a transform on the view itself. Don't resize the frame to change the size, but just setting a CGAffineScaleTransform from a pan gesture works great.

Ok, I will try...


mvn version

I'm not sure if we can build a project with maven under 3.8.6
@h1alexbel take a look, please

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 2min)

@l3r8yJ thanks!


added lxml to the pip install example since it is required

Description: The trello dataloader example didn't work without an additional dependency installed - lxml
Issue: na

thanks @byronsalty!


german language file added, translations done first iteration

let's bring the pirates to germany! :)
I created a german language file 'publishable/lang/de/voyager.php' that currently contains all the existing translation keys from the master branch.
All english ui messages have been translated - exeptions: Where the same word in german is being used. Stuff like "Check Box" or "Text Area" does not have a german correspondance so I used the english words in this case, actually just like Bruno (@akazorg) did for the portuguese version.
I used his and the english translations as a blueprint for the german translations to try to have a corresponding style.

Hi guys, I fixed the StyleCI stuff (three spaces at end of line) guess the codeclimate stuff (Similar Code found) can be ignored, I can fix the "Line exceeds 120 characters; " error if you like

You may ignore CodeClimate 😄

Looks good, merging in. 👍
Thanks for the pull request.

nice!


Handle null value on linechart

Hello,
I need to handle null values on linechart...

Hi, sorry, not at the moment...
But I will do my best to add this but at the moment, the the background gradient is drawn in one shape. To support this, the shape would have to be cut into several parts.

I've started some work here: https://github.com/brett-estabrook/Microcharts/tree/feature/36-null-value-support
It has a test chart that adds null values dynamically. It currently supports, Lines, Line Area, and Splines.


Clean up event listeners on anim clip destroy

Fixes https://github.com/playcanvas/engine/issues/5259
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

Would be good to fully verify this fix before merging.... (nice fix tho!)

I've asked the client to send over details where we can test this fix in a larger project with a large number of sprites, scene changing etc.

Checked against the clients larger project and no visual issues can be seen in areas where there's heavy sprite usuage


reporting_method = mqtt-smarthome

implements #6

On a side note, I'm not sure if it is meaningful to publish momentary states as retained messages but Hey, that's up to you and your mqtt-smarthome.
Also forgive me for asking but where do you see the advantages of mqtt-smarthome vs. Homie? I've helped extend the Homie convention and your opinion about the advantages and disadvantages would be very interesting. Best!

Publishing retained does make sense from my point of view. As an example: Imagine a Webfrontend that connects to the MQTT Broker and wants to show sensor data. Without retain it would have to wait until the next message arrives or it would need some kind of backend that caches states - with retained messages there is no need for that. On MQTT-Smarthome we publish everything retained except for set commands and "one shot events" (like e.g. a button presses).
About the pros and cons of Homie and MQTT-Smarthome: If you want we can talk via phone, I think that's easier. Will send you my number. Main thing why I stick to mqtt-smarthome: It's one year older than homie and I already got it running and we made a bunch of interfaces before the Homie project started. Another big difference is that mqtt-smarthome is kind a "unopinionated"  and doesn't care about meta-data (like descriptions of datapoint types, assignments to rooms or functions and so on). Stuff like this is handled on another layer in the mqtt-smarthome concept, in my case mainly through my script-engine (https://github.com/hobbyquaker/mqtt-scripts)

Hey Sebastian,
just so we are clear, you've removed the many connected state changes and said you are going to stick with 0 and 2 only, the code contains 0 and 1 messages. Which is the right one?

thought about that again and came to the conclusion that 1 fits better :)

Okay then, here we go!
Thanks for the addition! Happy to get further feedback from your side ;)


about find element by name

find_element_by_name and more method at lasted version is invalid,   In response to this problem you have some of their own plans?

it needs to be updated to find_element_by_accessibility_id. i believe @dpgraham has been working on this already.


Photo duplicats & Wrong property for sorting in database

Hi all, thanks for the great lib!
I installed Lychee and followed all instructions. All required extensions are added, and .ini file is changed to follow your recommendations. Anyhow odd behavior is noticed during a month long use:

Sometimes same photo get uploaded multiple times. Once this happens, same photo(or sometimes photos) will be uploaded with next few bulk uploads. I noticed once that problematic photos that got duplicated were saved in "data" folder. After cleaning it everything worked as a charm. Last time duplication has been happened, this folder didn't contain any photos. Any idea what can be wrong?

Also Settings->Diagnostics shows the warning: Wrong property for sorting in database.

Full Diagnostics:
Diagnostics
Warning: Dropbox import not working. No property for dropboxKey.
Error: Wrong property for sorting in database
System Information
Lychee Version:  3.0.1
DB Version:      030001
System:          Linux
PHP Version:     5.6
MySQL Version:   50542
Imagick:         -
Imagick Active:  1
Imagick Version: -
GD Version:      bundled (2.1.0 compatible)
Plugins:

Is this issue still present? I'm not sure what's casing it.

Can't reproduce. More information needed.


Accept [lon,lat] points

Current code breaks when the third Euler angle isn't specified

fixed in v0.1


Compatibility with extract-text-webpack-plugin

Hi,
When I try to use this ngx-swiper-wrapper module in my current project where  extract-text-webpack-plugin is currently configured to extract CSS , I am getting the below error.
Error: Child compilation failed:
Module build failed: Error: "extract-text-webpack-plugin" loader is used without the corresponding plugin, refer
to https://github.com/webpack/extract-text-webpack-plugin for the usage example
at Object.module.exports.pitch (C:\Angular2Apps\SPC\node_modules\extract-text-webpack-plugin\loader.js:27:9):
The error comes up the moment I import the ngx-swiper-wrapper into the module file.
If I remove the import statement for ngx-swiper-wrapper, my current code compiles properly without any errors.
Any idea what I should do to get this error resolved?

There should not be anything that libraries need to do to be compatible with extract text plugin. The CSS file provided by this library is pure CSS and has no errors. So really hard to say what could be the problem specially since the error message does not say anything about the actual error.


VPN Client to site: Cannot ping to VM in VPC

CLOUDSTACK VERSION
<IP_ADDRESS>
SUMMARY
I am experiencing an issue with the VPN Client to Site functionality. I am using the DrayTek Smart VPN Client to connect to the VPN, and the connection is successful. I receive an IP address (<IP_ADDRESS>) for the VPN interface on my PC, and I can ping to <IP_ADDRESS> successfully. There are two scenarios:

If I enable "Use default gateway on remote network," I can ping the VMs in the VPC, but I lose internet connection from my PC.
If I disable "Use default gateway on remote network," I cannot ping the VMs in the VPC, but the internet connection on my PC remains operational.

I also attempted to set up a VPN connection on Windows, and the result is the same as case 1 when using the DrayTek VPN app.
STEPS TO REPRODUCE

Create a non-redundant VPC.
Create a network tier.
Create a VM in the network tier (ACL default_allow).
Enable VPN site-to-site gateway.
Create an S2S VPN connection.
Enable VPN client-to-site on IP source NAT.
Create a user for the VPN.
Connect to the VPN using two methods: DrayTek App and VPN connection in Windows.

EXPECTED RESULTS
If I disable "Use default gateway on remote network," I should be able to ping the VMs in the VPC, and the internet connection on my PC should still work.
I am unsure how to check or verify this from any source. Please provide assistance; thanks for any ideas!

I have discovered a new clue.
The steps to reproduce is the same, but for VPC with a CIDR of <IP_ADDRESS>/16 or <IP_ADDRESS>/16, the VPN C2S does not work. On the contrary, for VPCs with a CIDR of 10.x.0.0/16, it is okay. The issue seems to be related to CIDR, but currently, I cannot change CIDR for the already created VPC as it is in use. Is there any way for the VPN C2S to still function with the CIDR <IP_ADDRESS>/16 as it is currently?

@tuanhoangth1603 , you would have to set a route for the VPC subnet in your local machine.
As of now updateing the CIDR of a VPC is not allowed because multiple tiers might be using it.

I have discovered a new clue. The steps to reproduce is the same, but for VPC with a CIDR of <IP_ADDRESS>/16 or <IP_ADDRESS>/16, the VPN C2S does not work. On the contrary, for VPCs with a CIDR of 10.x.0.0/16, it is okay. The issue seems to be related to CIDR, but currently, I cannot change CIDR for the already created VPC as it is in use. Is there any way for the VPN C2S to still function with the CIDR <IP_ADDRESS>/16 as it is currently?

so, it seems the issue is because your IP (<IP_ADDRESS>) is in the VPC CIDR (<IP_ADDRESS>/16).
There is no API to update CIDR of existing VPC, as @DaanHoogland mentioned.
You can try to update CIDR by manual database change to a smaller CIDR (for example <IP_ADDRESS>/20, or /22), and restart VPC with cleanup.
I have not tested it, maybe some other changes are required.

@tuanhoangth1603
I am closing this issue. please feel free to reopen it or create new issue.


Rollback body if inside an unloaded block & fix for autostep when autostepping in a corner

Hi, sorry for this addressing two things at once
Feel free to close this - and potentially address one or both of the issues with your own changes
The first change: I add the option isBodyInsideUnloadedBlock which rolls back the body to before the changes made by the tick if the body is inside an unloaded block. There's an early out in the main noa tick if the player co-ordinates aren't located in a loaded chunk but this has a few drawbacks:

The body will end up 1 physics tick inside the unloaded chunk, and so will end up inside a block if one exists
It doesn't check the corners of the player
It does nothing for non-player bodies

This logic could have been implemented elsewhere but it felt cleanest here. Unsure how it would be called in noa - personally I'm checking the corners of the body for the local player and just the middle of the base for all other bodies.
The second change is the logic for bail if no movement happened in the originally blocked direction
Before the change, if a player walks into a corner and one of the "walls" is one block high and one is more than that, the player won't autostep the "wall" that is one block high. With this change, the player does.

Hi, sorry for the late reply. I see what you mean about needing to prevent objects from  entering unloaded chunks, but I think it should be handled inside the main engine logic, rather than here - because this engine in principle doesn't know what chunks are or what it means for a block to be loaded or not, it's just meant to handle the interpolation.
With that said, in thinking about how best to solve this, it occurred to me that the simplest solution might be to just have the main engine treat unloaded blocks as being solid. That way any entity trying to move into an unloaded region would just bump into an invisible wall, which in principle shouldn't affect gameplay if it's happening "at the edge of the world" far from the player.
Can you think of any problems that would cause? The only think that occurs to me is that it would obviate the way entities in unloaded chunks currently fall off the world, meaning they eventually get culled, but that's not a very good mechanic anyway - it would probably be better for game clients to actively do something with entities like that (either because they do their own checking when chunks are unloaded, or because the engine dispatches an event for it.)

That sounds like a cleaner approach
The main issue I see is players would lose their vertical momentum when falling onto the top of an unloaded chunk but this isn't a concern in most games (and would always be corrected by server side movement in multiplayer games regardless)

Indeed, makes sense - flexibility+perf is better if not all games want it
Feel free to close!


Radar graph generated with values different from the data placed in the data array.

I try to plot a Radar graph with values up to 100 with 10 angles. My data has values between 50 and 100 but when the graph is generated the values are much smaller on the scale. I'm generating this graphic into a pdf file.
I'm using version 3.4.1. What am I doing wrong? Thanks.

@guiac do you have an interactive reproduce of this issue? What are you expecting the axis limits to be?

I expect this behavior https://jsfiddle.net/guiac/mrdyza9x/4/ , but the graphic is generated in the way of the image posted in the previous message.

Are you sure you are using v3.4.1 of the lib since your legend and scale config are v2 syntax and seem to work since I dont see a legend

My guess is that it tries to generate the pdf asap so the animations are still running and in the center, if you disable the animations or set the animation time to 0 it should resolve your issue.
Also your scale and legend config are wrong, they are in V2 syntax, see migration guide on how to change your code to V3: https://www.chartjs.org/docs/master/getting-started/v3-migration.html

I believe @LeeLenaleee is correct. Disabling the animations would be the solution here

Thanks for the tip @LeeLenaleee and @etimberg , I did the test setting the animation duration to 0 and the problem continued, I also made the changes you suggested from version 3. Any other tips? I imagine the problem might be something like stepSize or min and max parameter. But when I made these changes the graph was plotted with disproportionate scale at each angle.

That setting will only stop animations for the tension property. Try setting animations: false, instead

When I create the chart with these settings it is plotted as in the attached image. So I believe that the problem is not the animations parameter, but some problem with scale.

Please create a jsfiddle or equivalent to reproduce the issue


[dv/alert_handler] auto alert response

This PR fixed #16374, where it is recommended to use alert auto-response instead of a nonblocking sequence.
Signed-off-by: Cindy Chen<EMAIL_ADDRESS>

LGTM


Start CDH service before kata-agent

Based on kata agent PR which requires CDH socket to be available as part of kata-agent initialisation -  https://github.com/kata-containers/kata-containers/pull/10481

should be fixed w/ #2143