Unsupported gpu architecture 'compute_61' on luarocks install cutorch

Dear all
I have a issue when install cutorch. The computer is ubuntu 16, the GPU card is nvidia GTX 1070. I have install CUDA 8.0, cuDNN 5.1. When I install cutorch, I got the following issue:
-- Build files have been written to: /tmp/luarocks_cutorch-scm-1-7995/cutorch/build
[ 1%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCReduceApplyUtils.cu.o
[ 2%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCHalf.cu.o
[ 3%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensorMath.cu.o
[ 4%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCStorage.cu.o
[ 5%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensorCopy.cu.o
[ 7%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCBlas.cu.o
[ 8%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCStorageCopy.cu.o
[ 9%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensor.cu.o
nvcc fatal : Unsupported gpu architecture 'compute_61'
CMake Error at THC_generated_THCHalf.cu.o.cmake:207 (message):
Error generating
/tmp/luarocks_cutorch-scm-1-7995/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCHalf.cu.o

if you have CUDA 8.0 it should not complain like this. CUDA 7.5 and below will give this error message.
Paste the full log of install (you only pasted the last few lines)

./deviceQuery Starting...
CUDA Device Query (Runtime API) version (CUDART static linking)
Detected 1 CUDA Capable device(s)
Device 0: "GeForce GTX 1070"
CUDA Driver Version / Runtime Version          8.0 / 8.0
CUDA Capability Major/Minor version number:    6.1
Total amount of global memory:                 8110 MBytes<PHONE_NUMBER> bytes)
(15) Multiprocessors, (128) CUDA Cores/MP:     1920 CUDA Cores
GPU Max Clock rate:                            1683 MHz (1.68 GHz)
Memory Clock rate:                             4004 Mhz
Memory Bus Width:                              256-bit
L2 Cache Size:                                 2097152 bytes
Maximum Texture Dimension Size (x,y,z)         1D=(131072), 2D=(131072, 65536), 3D=(16384, 16384, 16384)
Maximum Layered 1D Texture Size, (num) layers  1D=(32768), 2048 layers
Maximum Layered 2D Texture Size, (num) layers  2D=(32768, 32768), 2048 layers
Total amount of constant memory:               65536 bytes
Total amount of shared memory per block:       49152 bytes
Total number of registers available per block: 65536
Warp size:                                     32
Maximum number of threads per multiprocessor:  2048
Maximum number of threads per block:           1024
Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
Max dimension size of a grid size    (x,y,z):<PHONE_NUMBER>, 65535, 65535)
Maximum memory pitch:<PHONE_NUMBER> bytes
Texture alignment:                             512 bytes
Concurrent copy and kernel execution:          Yes with 2 copy engine(s)
Run time limit on kernels:                     No
Integrated GPU sharing Host Memory:            No
Support host page-locked memory mapping:       Yes
Alignment requirement for Surfaces:            Yes
Device has ECC support:                        Disabled
Device supports Unified Addressing (UVA):      Yes
Device PCI Domain ID / Bus ID / location ID:   0 / 1 / 0
Compute Mode:
< Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >
deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 8.0, CUDA Runtime Version = 8.0, NumDevs = 1, Device0 = GeForce GTX 1070
Result = PASS
The full error logs are:  seems cutorch found CUDA 7.5 instead of 8.0
Found CUDA on your machine. Installing CUDA packages
Warning: unmatched variable LUALIB
cmake -E make_directory build && cd build && cmake .. -DLUALIB= -DCMAKE_CXX_FLAGS=${CMAKE_CXX_FLAGS} -DCMAKE_BUILD_TYPE=Release -DCMAKE_PREFIX_PATH="/home/torch/install/bin/.." -DCMAKE_INSTALL_PREFIX="/home/torch/install/lib/luarocks/rocks/cutorch/scm-1" && make -j$(getconf _NPROCESSORS_ONLN) install
-- Found Torch7 in /home/torch/install
-- Found gcc >=5 and CUDA <= 7.5, adding workaround C++ flags
-- MAGMA not found. Compiling without MAGMA support
-- Autodetected CUDA architecture(s): 6.1
-- got cuda version 7.5
-- Found CUDA with FP16 support, compiling with torch.CudaHalfTensor
-- Configuring done
-- Generating done
-- Build files have been written to: /home/torch/extra/cutorch/build
[  2%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCReduceApplyUtils.cu.o
[  5%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCBlas.cu.o
[  7%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensorCopy.cu.o
[ 10%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCHalf.cu.o
[ 12%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensor.cu.o
[ 15%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensorMath.cu.o
[ 17%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCStorage.cu.o
[ 20%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir/THC_generated_THCStorageCopy.cu.o
nvcc fatal   : Unsupported gpu architecture 'compute_61'
CMake Error at THC_generated_THCStorageCopy.cu.o.cmake:207 (message):
Error generating
/home/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCStorageCopy.cu.o
lib/THC/CMakeFiles/THC.dir/build.make:84: recipe for target 'lib/THC/CMakeFiles/THC.dir/THC_generated_THCStorageCopy.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/THC_generated_THCStorageCopy.cu.o] Error 1
make[2]: *** Waiting for unfinished jobs....
nvcc fatal   : Unsupported gpu architecture 'compute_61'
CMake Error at THC_generated_THCTensorCopy.cu.o.cmake:207 (message):
Error generating
/home/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorCopy.cu.o
nvcc fatal   : Unsupported gpu architecture 'compute_61'
CMake Error at THC_generated_THCTensorMath.cu.o.cmake:207 (message):
Error generating
/home/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMath.cu.o
lib/THC/CMakeFiles/THC.dir/build.make:98: recipe for target 'lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensorCopy.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensorCopy.cu.o] Error 1
lib/THC/CMakeFiles/THC.dir/build.make:105: recipe for target 'lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensorMath.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensorMath.cu.o] Error 1
nvcc fatal   : Unsupported gpu architecture 'compute_61'
nvcc fatal   : Unsupported gpu architecture 'compute_61'
CMake Error at THC_generated_THCStorage.cu.o.cmake:207 (message):
Error generating
/home/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCStorage.cu.o
CMake Error at THC_generated_THCBlas.cu.o.cmake:207 (message):
Error generating
/home/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCBlas.cu.o
lib/THC/CMakeFiles/THC.dir/build.make:77: recipe for target 'lib/THC/CMakeFiles/THC.dir/THC_generated_THCStorage.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/THC_generated_THCStorage.cu.o] Error 1
lib/THC/CMakeFiles/THC.dir/build.make:70: recipe for target 'lib/THC/CMakeFiles/THC.dir/THC_generated_THCBlas.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/THC_generated_THCBlas.cu.o] Error 1
nvcc fatal   : Unsupported gpu architecture 'compute_61'
CMake Error at THC_generated_THCReduceApplyUtils.cu.o.cmake:207 (message):
Error generating
/home/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCReduceApplyUtils.cu.o
lib/THC/CMakeFiles/THC.dir/build.make:63: recipe for target 'lib/THC/CMakeFiles/THC.dir/THC_generated_THCReduceApplyUtils.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/THC_generated_THCReduceApplyUtils.cu.o] Error 1
nvcc fatal   : Unsupported gpu architecture 'compute_61'
CMake Error at THC_generated_THCTensor.cu.o.cmake:207 (message):
Error generating
/home/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensor.cu.o
lib/THC/CMakeFiles/THC.dir/build.make:91: recipe for target 'lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensor.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/THC_generated_THCTensor.cu.o] Error 1
nvcc fatal   : Unsupported gpu architecture 'compute_61'
CMake Error at THC_generated_THCHalf.cu.o.cmake:207 (message):
Error generating
/home/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCHalf.cu.o
lib/THC/CMakeFiles/THC.dir/build.make:231: recipe for target 'lib/THC/CMakeFiles/THC.dir/THC_generated_THCHalf.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/THC_generated_THCHalf.cu.o] Error 1
CMakeFiles/Makefile2:172: recipe for target 'lib/THC/CMakeFiles/THC.dir/all' failed
make[1]: *** [lib/THC/CMakeFiles/THC.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
Error: Build error: Failed building.

yes, please install 8.0 rather than 7.5, or remove 7.5 from your system completely.

Completely remove 7.5 package works! Thanks.

How to completely remove 7.5 package from  Ubuntu ?

@soumith I have cuda 9.1 and still I am facing the same problem. Can you please suggest me something.


Revision "sklearn-iris-predictor-default-00001" failed with message: Unable to fetch image "docker.io/seldonio/mlserver:0.5.3": failed to resolve image to digest: Get "https://index.docker.io/v2/": context deadline exceeded

Hi, I am trying to build a inferenceserver using below example set
https://github.com/yingding/kf-examples/blob/main/kserve_example.ipynb
And getting below error -
Revision "sklearn-iris-predictor-default-00001" failed with message: Unable to fetch image "docker.io/seldonio/mlserver:0.5.3": failed to resolve image to digest: Get "https://index.docker.io/v2/": context deadline exceeded
I was thinking to build my custom seldonio/mlserver:0.5.3 in our private image repo. Can someone help mr how to do that, can I directly create a InferenceService using yaml configuration where I can provide storageUri and my custom  mlserver image

@vinayK34 It might be a network problem. The documentation for building custom runtime can be found on the kserve website. Also refer serving runtime.

Is their way to run this runtime server in our private repository and point to that specific server runtime instead of docker.io

@sivanantha321 Is their way to run this runtime server in our private repository and point to that specific server runtime instead of docker.io

You can update serving runtimes to point to your images in private repository. For example https://github.com/kserve/kserve/blob/65cb2216540ca5f97d47c4e278325bf6a8fb32e1/config/runtimes/kserve-sklearnserver.yaml#L17

same

@vinayK34 can you provide predictor pod logs?

I see similar issue , do we have a solution for this ?

Hi @sivanantha321 @yuzisun I have tried that one also, created my own ClusterServingRuntime apiVersion: serving.kserve.io/v1alpha1 kind: ClusterServingRuntime metadata: name: kserve-sklearnserver-vinay spec: supportedModelFormats: - name: sklearn version: "1" autoSelect: true containers: - name: kserve-container image: url/seldonio-mlserver:0.5.3 args: - --model_name={{.Name}} - --model_dir=/mnt/models - --http_port=8080 resources: requests: cpu: "1" memory: 2Gi limits: cpu: "1" memory: 2Gi
But still my inferenceservice are in failed state. I see the revision event that says - InternalError 14s revision-controller failed to update deployment "example-sklearn-isvc-v2-predictor-default-00001-deployment": Operation cannot be fulfilled on deployments.apps "example-sklearn-isvc-v2-predictor-default-00001-deployment": the object has been modified; please apply your changes to the latest version and try again

I think it worked that error is benign, it is an internal retry when there are version conflicts.

Let us know if this is still an issue


Make Select a controlled component

Did not notice this right away, but the component is not controlled. If onSelect is not passed to control some state outside of the component, it's not supposed have any effect when selecting an option.
value should be a mandatory prop, with the possibility to pass undefined

On Radix side, this is not how it's handled.
If value is undefined, then the component is considered as uncontrolled and manage it's own state with no regard of onSelect value.
I'll push more stories to allow you to be more precise on what behavior is not as intended.

Maybe I don't see the whole picture but IMO it can simplify the code in some cases but in general there are some downsides:

It can lead to bugs where you think you have a controlled component but you forgot to pass the value and you end up with duplicated state.
It becomes more code and work to make all components work in a coherent way (including components which don't use radix-ui)

I'm not completely opposed to it, but I haven't used uncontrolled components in a very long time and maybe I'm missing the upsides.
I would be in favour of fully controlled components just because it's an easier mental model if all of our components behave th


Patch pandas dependency for fastparquet=0.7.0

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

xref https://github.com/dask/dask/pull/7907, https://github.com/conda-forge/fastparquet-feedstock/pull/47
cc @martindurant

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks James! 😄
Can you please run show_diff.py from the recipe directory and share the results?

Below is the full show_diff.py output. The fastparquet diff looks right, but I'm not sure where
linux-64::libkml-1.3.0-h238a007_1014.tar.bz2
-    "expat >=2.3.0,<2.4.0a0",
+    "expat >=2.3.0,<3.0.0a0",

and
win-64::tiledb-py-0.9.2-py36_vc14hdd3148d_0.tar.bz2
-  "features": "vc14",
win-64::tiledb-py-0.9.2-py37_vc14h756c2e0_0.tar.bz2
-  "features": "vc14",
win-64::tiledb-py-0.9.2-py38_vc14h528aa4e_0.tar.bz2
-  "features": "vc14",
win-64::tiledb-py-0.9.2-py39_vc14he219d82_0.tar.bz2
-  "features": "vc14",

are coming from

Full output:
(conda-forge-repodata-patches) ➜  conda-forge-repodata-patches-feedstock git:(fastparquet-0.7.0) python recipe/show_diff.py
Downloading: https://conda.anaconda.org/conda-forge/noarch/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/noarch/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-64/repodata.json.bz2
linux-64::fastparquet-0.7.0-py36h4d9540e_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-64::fastparquet-0.7.0-py37h6f94858_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-64::fastparquet-0.7.0-py38hb5d20a5_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-64::fastparquet-0.7.0-py39hce5d2b2_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-64::libkml-1.3.0-h238a007_1014.tar.bz2
-    "expat >=2.3.0,<2.4.0a0",
+    "expat >=2.3.0,<3.0.0a0",
Downloading: https://conda.anaconda.org/conda-forge/linux-armv7l/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-armv7l/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-aarch64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-aarch64/repodata.json.bz2
linux-aarch64::fastparquet-0.7.0-py36hbe810f4_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-aarch64::fastparquet-0.7.0-py37h32d76ca_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-aarch64::fastparquet-0.7.0-py38h5c1ee58_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-aarch64::fastparquet-0.7.0-py39h5cfbcb9_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-aarch64::libkml-1.3.0-h019b1a7_1014.tar.bz2
-    "expat >=2.3.0,<2.4.0a0",
+    "expat >=2.3.0,<3.0.0a0",
Downloading: https://conda.anaconda.org/conda-forge/linux-ppc64le/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-ppc64le/repodata.json.bz2
linux-ppc64le::fastparquet-0.7.0-py36ha96d7dc_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-ppc64le::fastparquet-0.7.0-py37he662d02_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-ppc64le::fastparquet-0.7.0-py38h9d9f2af_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-ppc64le::fastparquet-0.7.0-py39h3084282_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
linux-ppc64le::libkml-1.3.0-hc41e6c6_1014.tar.bz2
-    "expat >=2.3.0,<2.4.0a0",
+    "expat >=2.3.0,<3.0.0a0",
Downloading: https://conda.anaconda.org/conda-forge/osx-64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/osx-64/repodata.json.bz2
osx-64::fastparquet-0.7.0-py36hab44bd3_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
osx-64::fastparquet-0.7.0-py37h238668a_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
osx-64::fastparquet-0.7.0-py38h0793694_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
osx-64::fastparquet-0.7.0-py39hc89836e_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
osx-64::libkml-1.3.0-h8fd9edb_1014.tar.bz2
-    "expat >=2.3.0,<2.4.0a0",
+    "expat >=2.3.0,<3.0.0a0",
Downloading: https://conda.anaconda.org/conda-forge/osx-arm64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/osx-arm64/repodata.json.bz2
osx-arm64::fastparquet-0.7.0-py38h691f20f_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
osx-arm64::fastparquet-0.7.0-py39h20ef057_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
osx-arm64::libkml-1.3.0-h893ab4d_1014.tar.bz2
-    "expat >=2.3.0,<2.4.0a0",
+    "expat >=2.3.0,<3.0.0a0",
Downloading: https://conda.anaconda.org/conda-forge/win-32/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-32/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-64/repodata.json.bz2
win-64::fastparquet-0.7.0-py36h68f0c41_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
win-64::fastparquet-0.7.0-py37hebb4d16_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
win-64::fastparquet-0.7.0-py38hcb5f9af_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
win-64::fastparquet-0.7.0-py39h5d4886f_0.tar.bz2
-    "pandas >=0.19",
+    "pandas >=1.0.0",
win-64::libkml-1.3.0-h9859afa_1014.tar.bz2
-    "expat >=2.3.0,<2.4.0a0",
+    "expat >=2.3.0,<3.0.0a0",
win-64::tiledb-py-0.9.2-py36_vc14hdd3148d_0.tar.bz2
-  "features": "vc14",
win-64::tiledb-py-0.9.2-py37_vc14h756c2e0_0.tar.bz2
-  "features": "vc14",
win-64::tiledb-py-0.9.2-py38_vc14h528aa4e_0.tar.bz2
-  "features": "vc14",
win-64::tiledb-py-0.9.2-py39_vc14he219d82_0.tar.bz2
-  "features": "vc14",

@conda-forge/core , do we know why these other patches are showing up? From the change in this PR, it's not clear how this would have caused those. So assuming they are showing up for another reason.

This has been happening. Idk specifically about those diffs but we've been merging anyways.

Interesting thanks for the context Matt 🙂
It does make me worry a little bit that maybe some older patches might not be getting applied (cc @chenghlee in case you have insights here :)

Going to go ahead and merge, but it would be good to investigate this issue more later

Thanks James! 😄


Master doc page out of date?

https://tokio-rs.github.io/mio/doc/mio/
This shows the latest version as being 0.8.0. Is this not being updated?

I don't think so. Are you using it? Or can we remove it from the readme?

I am not using it, I just noticed it when I happened to click the link. I don't know if it should be removed or not.


build: pin remaining unpinned third-party Docker images

This avoids uncontrolled changes to build dependencies sneaking into our Docker image builds, and is considered best practice.
The Docker Hub expresses both an "index digest" and a "manifest digest". I have used the latter, as this seemed the correct thing to do.

I am not sure about the difference between an index hash and a manifest hash, but it seems the Renovate bot always updates the hash to the index hash, even when we provide the manifest hash.


Set relative chaincode path in fabric.json config file

Dear Developers,
I am trying to separate the benchmark artifacts from the code-base of Caliper. The directory structure I am trying to build is the following:
.
├── benchmarks
│   └── simple
│       ├── config.json
│       ├── contract
│           └── simple
│               └── simpletest.go
│       ├── fabric.json
│       ├── main.js
│       ├── node_modules
│           ├── ...
│       ├── open.js
│       ├── package.json
│       └── query.js
├── caliper
│   ├── ...

The first steps I took was separating the *.json and *.js files of the simple benchmark (so the contract and network paths remained the same). I performed the following in my new benchmarks/simple folder:

npm init && npm install commander fs-extra --save to run main.js
Changing the path of the network config file and callbacks in config.json to "config": "../benchmarks/simple/fabric.json" and "callback" : "../benchmarks/simple/open.js" since these should be relative to the Caliper root directory.
Changing the Caliper root path in main.js on line 43 to var absCaliperDir = path.join(__dirname, '../../caliper');

So far so good, I could install & instantiate the chaincode from its original caliper/src/contract/fabric/simple directory.
After this, I relocated the chaincode to my benchmarks/simple/contract/simple directory and changed the chaincode path in fabric.json to the following:
"chaincodes": [{"id": "simple", "path": "../../benchmarks/simple/contract/simple", "language":"golang", "version": "v0", "channel": "mychannel"}],
Based on the original path, I thought this should be relative to the caliper/src folder.
But running the benchmark gives the following error:
# Instantiate chaincode......
info: [EventHub.js]: _connect - options {"grpc.ssl_target_name_override":"peer0.org1.example.com","grpc.default_authority":"peer0.org1.example.com"}
error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: 2 UNKNOWN: Error starting container: Failed to generate platform-specific docker build: Error returned from build: 1 "can't load package: package ../../benchmarks/simple/contract/simple: open /benchmarks/simple/contract/simple: no such file or directory
can't load package: package ../../benchmarks/simple/contract/simple: open /benchmarks/simple/contract/simple: no such file or directory
"
    at new createStatusError (/home/klenik/Projects/caliper/node_modules/grpc/src/client.js:64:15)
    at /home/klenik/Projects/caliper/node_modules/grpc/src/client.js:573:15

I am lost at this point, since I do not know where this path is being rejected. On the client (SDK) side or the Fabric (peer) side? Did I miss something? How can I deploy chaincodes from outside your contract/fabric directory?
Thanks for the help!

So I realized, that go chaincodes must be stored inside somewhere $GOPATH/src. So I tried setting GOPATH to the root of my benchmark directory, and renamed my contract folder to src:
GOPATH=~/Projects/benchmarks/simple node main.js
Then the chaincode path in fabric.json should be simply simple. However, when the install-chaincode-request is assembled, GOPATH is the Caliper root folder. I guess somewhere in the code-base it is set to the root folder (could not find the location so far).
So the real question is, can I configure the GOPATH before running main.js, or is it hardwired into the code-base?

Hi,
You are correct, now the GOPATH is set to the root folder. The code can be found in util.js (line69). You can change it to read GOPATH from environment or configuration file.


Version.json file needs updating

The version.json file on root of the repo is lagging behind a couple of releases. When downloading release v0.13.0 the file shows v0.11.0...
Not sure if this should be updated to the newest pre-release, ordinary release or be done as prep for the upcomming v0.14.0

AB#28242


digdag server --ignore-schedules

follow-up: https://github.com/treasure-data/digdag/pull/1048#issuecomment-476484645
Fix https://github.com/treasure-data/digdag/issues/1062

I left one comment on https://github.com/treasure-data/digdag/issues/1062. Please take a look.

Left a comment on #1062

Instead, digdag push --draft option will be considered. see #1062. it Let me close.


[Class modifiers] VM service protocol support

Probably makes sense to be able to detect what modifiers are on a class from a Class instance.

//cc @bkonyi @derekxu16


GitHub Pages for Documentation

It looks like the gh-pages branch was abandoned. Is this something that should be created going forward? As a user, it feels like the documentation could be presented better and building a page for documentation might be the best way to do that

You can see the abandoned site at rbenv.org.

I will work on this unless I hear otherwise.

You're welcome to suggest some documentation. How did you plan to document things?
We would probably want to have said documentation in a separate repo named rbenv.github.io. But you're welcome to send a PR for the gh-pages branch in this repo first.

@mislav I plan on porting the readme into an easy to follow "getting started," then look at expanding it to cover rbenv's features.
I'm thinking something Jekyll based, but I'll be sure to get your feedback on the PR.

Thanks


Add Github Action for testing on darwin

See https://github.com/Senzing/template-go/issues/76

Pull requests:

https://github.com/Senzing/observe/pull/35


Create api proxy #85

Closes #85

After an investigation by @markdavison, it was verified that the proxy continued to work even if another schema is broken.
That renders this work useless, as we are now confident in deploying it together with the 3rd party schemas.
/cc @bdmason


bash: line 166: TEMPLATES: bad array subscript

Hi Guys,
can anyone help?
root@proxmox:~# bash -c "$(wget -qLO - https://github.com/whiskerz007/proxmox_tuya-convert_container/raw/master/create_container.sh)"
[INFO] Using 'local-lvm' for storage location.
[INFO] Using 'wlp0s20f3' wireless interface.
[INFO] Container ID is 108.
Updating LXC template list...
Downloading LXC template...
bash: line 166: TEMPLATES: bad array subscript
root@proxmox:~#

The issue is the Debian OS version, you can use this:
pveam update
pveam available -section system | grep debian-12

to check the os version and than create a fork to OSVERSION to your debian version

Hi Olivier, thank you for trying to help me.
that's the output:
pveam available -section system | grep debian-12
system          debian-12-standard_12.7-1_amd64.tar.zst
i tried the following:

I downloaded all the scripts
In the create_container.sh i changed line 160 to OSVERSION=${OSTYPE}-12
i uploaded the files to my proxmox
I startet the create_container.sh
This was the output:

root@proxmox:~/proxmox_tuya-convert_container-master# ./create_container.sh
[INFO] Using 'local-lvm' for storage location.
[INFO] Using 'wlp0s20f3' wireless interface.
[INFO] Container ID is 108.
Updating LXC template list...
Downloading LXC template...
Creating LXC container...
Starting LXC container...
Customizing container OS...
Updating container OS...
Installing prerequisites...
Cloning tuya-convert...
Configuring tuya-convert...
./configure_tuya-convert.sh: line 12: iw: command not found
[ERROR:LXC] 127@68 Unknown failure occured.
[ERROR] 127@218 Unknown failure occured.
Logical volume "vm-108-disk-0" successfully removed.
root@proxmox:~/proxmox_tuya-convert_container-master#
Anymore ideas? :-(

Ok, the container is created. Thank You very much!
But there is a little confusion. What does ist mean? Deprecation? Should i do something? Please look below.
 _Installing collected packages: sslpsk, tornado, pycryptodomex, paho-mqtt
  _DEPRECATION: sslpsk is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559_
  Running setup.py install for sslpsk ... done
Successfully installed paho-mqtt-2.1.0 pycryptodomex-3.21.0 sslpsk-1.0.0 tornado-6.4.1
Customizing OS...
Cleanup...
[INFO] Successfully created tuya-convert LXC to 108._

Now i will order plugs again and try out my new tuya convert-container :-)

:-( No success. I think there is a prolem with tuya convert. I had the same errors on many different ways. I give up or do you have any ideas?
`Debian GNU/Linux 12 lxc-TuyaConvert tty1

  ******************************
    The tuya-convert files are
    shared using samba at
    <IP_ADDRESS>
  ******************************

  Login using the following credentials
    username: root
    password: tuya

lxc-TuyaConvert login: root
Password:
Linux lxc-TuyaConvert 6.8.12-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-2 (2024-09-05T10:03Z) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Nov 16 19:55:26 CET 2024 on tty1
tuya-convert v2.4.6
Checking for network interface wlp0s20f3... Found.
Checking UDP port 53... Available.
Checking UDP port 67... Available.
Checking TCP port 80... Available.
Checking TCP port 443... Available.
Checking UDP port 6666... Available.
Checking UDP port 6667... Available.
Checking TCP port 1883... Available.
Checking TCP port 8886... Available.
======================================================
  Starting AP in a screen.
  Starting web server in a screen
  Starting Mosquitto in a screen
  Starting PSK frontend in a screen
  Starting Tuya Discovery in a screen

======================================================

IMPORTANT
1. Connect any other device (a smartphone or something) to the WIFI vtrust-flash
   This step is IMPORTANT otherwise the smartconfig may not work!
2. Put your IoT device in autoconfig/smartconfig/pairing mode (LED will blink fast). This is usually done by pressing and holding the primary button of the device
   Make sure nothing else is plugged into your IoT device while attempting to flash.
3. Press ENTER to continue

======================================================
Starting smart config pairing procedure
Waiting for the device to install the intermediate firmware
Traceback (most recent call last):
  File "/root/tuya-convert/scripts/./smartconfig/main.py", line 15, in <module>
    from smartconfig import smartconfig
  File "/root/tuya-convert/scripts/smartconfig/smartconfig.py", line 43, in <module>
    from multicast import multicast_head, encode_multicast_body
  File "/root/tuya-convert/scripts/smartconfig/multicast.py", line 12, in <module>
    from Cryptodome.Cipher import AES
ModuleNotFoundError: No module named 'Cryptodome'
........................................................................................................................
Timed out while waiting for the device to (re)connect
======================================================
Attempting to diagnose the issue...
No ESP82xx based devices connected according to your wifi log.
Here is a list of all the MAC addresses that connected:
6a:8f:ba:b6:ab:fa

If you see your IoT device in this list, it is not an ESP82xx based device.
Otherwise, another issue may be preventing it from connecting.
For additional information, check the *.log files inside the scripts folder.
Please include these logs when opening a new issue on our GitHub issue tracker.
======================================================
Do you want to try flashing another device? [y/N] n
======================================================
Cleaning up...
No screen session found.
No screen session found.
No screen session found.
Closing AP
Exiting...
tuya-convert exited with code:0

Debian GNU/Linux 12 lxc-TuyaConvert tty1

  ******************************
    The tuya-convert files are
    shared using samba at
    <IP_ADDRESS>
  ******************************

  Login using the following credentials
    username: root
    password: tuya

lxc-TuyaConvert login:

Hey there was still an error in the script. I patched that now, just recreate the container the same way as before


There is something wrong about the results. Loss, RMSE, MAPE all is zero.

Log directory: ./experiments/lstm/GLA/
2024-07-24 14:05:42,361 - Namespace(device='cuda:0', dataset='GLA', years='2019', model_name='lstm', seed=2024, bs=32, seq_len=12, horizon=12, input_dim=3, output_dim=1, mode='train', max_epochs=100, patience=30, init_dim=32, hid_dim=64, end_dim=512, layer=2, lrate=0.001, wdecay=0.0001, dropout=0.1, clip_grad_value=5)
2024-07-24 14:05:55,062 - Data shape: (105120, 3834, 3)
2024-07-24 14:06:07,772 - Sample num: 63058, Batch num: 1970
2024-07-24 14:06:20,460 - Sample num: 21019, Batch num: 656
2024-07-24 14:06:33,156 - Sample num: 21020, Batch num: 656
2024-07-24 14:06:34,185 - The number of parameters: 97932
2024-07-24 14:06:34,185 - Start training!
Check mask value tensor(0)
2024-07-24 14:13:28,434 - Epoch: 001, Train Loss: 0.0000, Train RMSE: 0.0000, Train MAPE: 0.0000, Valid Loss: 0.0000, Valid RMSE: 0.0000, Valid MAPE: 0.0000, Train Time: 310.5966s/epoch, Valid Time: 103.6521s, LR: 1.0000e-03
2024-07-24 14:13:28,438 - Val loss decrease from inf to 0.0000
2024-07-24 14:20:24,661 - Epoch: 002, Train Loss: 0.0000, Train RMSE: 0.0000, Train MAPE: 0.0000, Valid Loss: 0.0000, Valid RMSE: 0.0000, Valid MAPE: 0.0000, Train Time: 312.5177s/epoch, Valid Time: 103.7053s, LR: 1.0000e-03
2024-07-24 14:27:27,512 - Epoch: 003, Train Loss: 0.0000, Train RMSE: 0.0000, Train MAPE: 0.0000, Valid Loss: 0.0000, Valid RMSE: 0.0000, Valid MAPE: 0.0000, Train Time: 317.2444s/epoch, Valid Time: 105.6064s, LR: 1.0000e-03
2024-07-24 14:34:31,354 - Epoch: 004, Train Loss: 0.0000, Train RMSE: 0.0000, Train MAPE: 0.0000, Valid Loss: 0.0000, Valid RMSE: 0.0000, Valid MAPE: 0.0000, Train Time: 320.2488s/epoch, Valid Time: 103.5923s, LR: 1.0000e-03
2024-07-24 14:41:35,001 - Epoch: 005, Train Loss: 0.0000, Train RMSE: 0.0000, Train MAPE: 0.0000, Valid Loss: 0.0000, Valid RMSE: 0.0000, Valid MAPE: 0.0000, Train Time: 317.7777s/epoch, Valid Time: 105.8682s, LR: 1.0000e-03

Hi, could you please provide more information, e.g., the environment, what you have modified. thanks.

Hi, could you please provide more information, e.g., the environment, what you have modified.

I’ve solved the problem, because the torch version. Thanks for your excellent work.

Have solved.


Call Filter or Sort on a Realm List: 'This method may only be called on RLMArray instances retrieved from an RLMRealm'

Goals
Filter a Realm List.
Expected Results
Turn a List into a Results object.
Actual Results
RLMException
'This method may only be called on RLMArray instances retrieved from an RLMRealm'
Steps for others to Reproduce
Running filter or sort on a list object:
list.filter("isDeleted == false")
Further running:
debugPrint(list.realm)
Prints nil.
Code Sample
let exercisesForWorkout = List<Exercise>()

var exercisesForWorkoutFilterSorted: Results<Exercise> {
    get { return exercisesForWorkout.filter("isDeleted == false") }
}

Version of Realm and Tooling
Realm framework version: 10.1.4
Realm Object Server version: MongoDB
Xcode version: 12.2
iOS/OSX version: 14.2
Dependency manager + version: ?

So it seems the issue was trying to filter / sort on a List when the parent Object hasn't been added to Realm yet.
I had to
try! realm.write {
    realm.add(obj)
}

Before I could:
obj.list.filter(query)

You can close this.


a set problem

can you elaborate a bit more on your problem, what is not working as expected? It is correct that arrays are converted to objects (to support observability), see also: https://mobxjs.github.io/mobx/best/pitfalls.html, first item

Closing for inactivity.
@allces, feel free to reopen if you hame some reproducible example


Allow file URL to be specified as manifest for riff system install

Fixes https://github.com/projectriff/riff/issues/1036

This should also allow a file URL to be specified as manifest for riff namespace init.

Sorry, I still can't get namespace init to work with a file URL.
It works without file:/// prefix both as C:\Users\trisberg\Downloads\pfs-files\manifest.yaml and as C:/Users/trisberg/Downloads/pfs-files/manifest.yaml
PS C:\Users\trisberg> riff namespace init test --no-secret --manifest file:///C:\Users\trisberg\Downloads\pfs-files\manifest.yaml
Initializing namespace "test"

Applying riff-cnb-buildtemplate-0.1.0-66c3cc7a6054c438d8505b30cf4772a9.yaml in namespace "test"
error: the path "file:\\C:\\Users\\trisberg\\Downloads\\pfs-files\\riff-cnb-buildtemplate-0.1.0-66c3cc7a6054c438d8505b30cf4772a9.yaml" cannot be accessed: CreateFile file:\C:\Users\trisberg\Downloads\pfs-files\riff-cnb-buildtemplate-0.1.0-66c3cc7a6054c438d8505b30cf4772a9.yaml: The filename, directory name, or volume label syntax is incorrect.

Error: exit status 1

Merged as squashed 41409f51


Manage docker version on runner instance

Hi
We are using this module for some time now but recently around a month ago runner instances updated docker versions from 19.03 to 20.10.1 and this is causing us some issues. I am trying to find if there is a config which can tell gitlab runner which docker version to install.
Following is the config that we are using:
module "runner" {
  source  = "npalm/gitlab-runner/aws"
  version = "4.10.0"

  aws_region                      = "eu-west-1"
  environment                     = "on-demand-runners"
  enable_gitlab_runner_ssh_access = true
  docker_machine_instance_type    = "m5.xlarge"

  vpc_id                   = aws_vpc.gitlab.id
  subnet_ids_gitlab_runner = [aws_subnet.private_subnet_a.id, aws_subnet.private_subnet_b.id, aws_subnet.private_subnet_c.id, ]
  subnet_id_runners        = aws_subnet.private_subnet_a.id

  runners_name          = var.runners_name
  runners_gitlab_url    = var.runners_gitlab_url
  runners_concurrent    = 30
  runners_idle_time     = 3000

  ssh_key_pair = aws_key_pair.key.key_name

  gitlab_runner_registration_config = {
    run_untagged       = true
    registration_token = var.registration_token
    tag_list           = ""
    description        = ""
    locked_to_project  = ""
    maximum_timeout    = ""
  }

  runners_privileged         = "true"
  runners_additional_volumes = ["/var/run/docker.sock:/var/run/docker.sock", "/artifacts:/artifacts"]

  docker_machine_options = ["amazonec2-root-size=100"]
}

Thanks

At the moment the docker version of the runner agent is not configurable, docker is installed via a user data script, see https://github.com/npalm/terraform-aws-gitlab-runner/blob/develop/template/gitlab-runner.tpl  In your case it looks like your are using docker-machien and the docker version is provided via docker machine. Please feel free to suggest via an issue or PR any improvement that you have in mind.

At the moment the docker version of the runner agent is not configurable, docker is installed via a user data script, see https://github.com/npalm/terraform-aws-gitlab-runner/blob/develop/template/gitlab-runner.tpl  In your case it looks like your are using docker-machien and the docker version is provided via docker machine. Please feel free to suggest via an issue or PR any improvement that you have in mind.

Short update, we using sometimes dind to fix the version. Still having the issue?

Could be nice to have an explicit docker version in the config or use the version proposed by the package manager.


Add russian words from examples into translations

dig - translates as 'копать'
dig a hole - translates as 'выкопать яму'
but you write translation 'выкопать'  in ru write question - it treats as mistake

=====>   slap    <=====
Write the translation...
tm team, [23 Nov 2021, 14:48:02]:
пощечина
Chto ti skazal' ?!?!, [23 Nov 2021, 14:48:02]:
❌ The translation was
"похлопать, шлепок"


fix(designer-ui): Ensure isAdvanced: false tokens are shown if far down in a list

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Bug fix

What is the current behavior? (You can also link to an open issue here)

If a set of token outputs from an action has the first six as isAdvanced: true and then some output after that has isAdvanced: false, that output should be shown without clicking "See more"; however, it is currently not.

What is the new behavior (if this is a feature change)?

The first six isAdvanced: false tokens will be shown. (I explicitly split out the logic into a helper to make it easier to test.)

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No

Please Include Screenshots or Videos of the intended change:

N/A

why can't "Visibility: important" be used for this? Why are we adding another concept for this?


The same CSS files are injected several times when switching pages

🐛 Bug Report
I noticed a strange bug when switching pages (Home -> Docs -> Blog) CSS styles are duplicated (re-injected as I understand it correctly).
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

Open devtools and focus on styles (body eg)

Open Home page (https://v2.docusaurus.io/) and we can already see that the styles are duplicated!

Alright, go ahead, click on Docs (https://v2.docusaurus.io/docs/introduction) in navbar and check the styles in devtools again, now the styles are duplicated several times (+3 new)!

Expected behavior
Styles should not be duplicated (re-injected) when moving to other pages.
Actual Behavior
For some reason, the same styles are injected, which overridden the earlier ones.
Reproducible Demo
See To Reproduce section.

Well, it's mostly because of https://github.com/facebook/docusaurus/blob/6204d9a9ec1a64cdbee53ca02c785da3380bf73e/packages/docusaurus-theme-classic/src/theme/Layout/styles.css#L8-L23
First of all, this requires a high level understanding of how webpack works.
The thing is, webpack mini-css-extract-plugin create one css file per js file and then the splitChunk try to cleverly take out a common one if possible but the algorithm is much more complicated than that because it tries to minimize number of request too https://webpack.js.org/plugins/split-chunks-plugin/#defaults
So https://v2.docusaurus.io/docs/introduction and https://v2.docusaurus.io/ actually both depends on Layout (which depends on that css) and both have their own extra css
This is just an illustration but i guess this can serve the purpose
Example /docs/introduction requires final css like this
.body {
  margin: 0;
}
.content {
   flex: 1 0 auto;
}

And / final required css is like this
.body {
  margin: 0;
}
.github {
   color: red
}

Here is the question. Do you think webpack will take out the common body { margin: 0;} ?
Such that if i go to /docs/introduction, it will request a.css and this common.css ? and if i go to /, it will just request b.css since common.css has been loaded before
Turns out that it doesn't, because the common.css is too small. and its just better to focus on one css request on first initial page load, thats why the reinjection happens.
Actually this is not happening to CSS only, there are lot of duplicated JS out there for all generated webpack projects.

One solution is to move https://github.com/facebook/docusaurus/blob/6204d9a9ec1a64cdbee53ca02c785da3380bf73e/packages/docusaurus-theme-classic/src/theme/Layout/styles.css#L8-L23 to main bundle.
That's why people nowadays use css-in-js, it has better tree shaking ✌

It's what you said was true, it's weird behavior by webpack though. Reinjecting styles is a bad idea as precedence ordering matters. And I'd assume webpack wouldn't reinject the same style module again if the module has already been loaded before.
Regardless, this issue is probably something to do with webpack.

Another solution is to extract all css into single file. But that is not a good idea as well since that means a lot of unused css in certain page. All has pros and cons.
I dont think this should be called as a bug, its not breaking any website. In fact, requesting one css file is better than requesting two files. Its also very small in size. It just happens to be the body selector so its noticeable.
Still better than going to https://docusaurus.io/docs/en/tutorial-setup and https://docusaurus.io/en/. Everytime new big css file is requested.

It's what you said was true, it's weird behavior by webpack though. Reinjecting styles is a bad idea as precedence ordering matters. And I'd assume webpack wouldn't reinject the same style module again if the module has already been loaded before.
Regardless, this issue is probably something to do with webpack.

But its actually two different files.
Page a need a.css
.body {
  margin: 0;
}
.content {
   flex: 1 0 auto;
}

Page b need b.css
.body {
  margin: 0;
}
.github {
   color: red
}

That's why going from pageA to pageB kinda override the same css.

In fact, I am observing such a issue in reusable components.
I have a Showcase component that is used on the home page and on the Users page.
If I go to the first page first, and why go to the latter and look at devtools, I will see the following result:

Let me put more investigation sometimes next week

I did an investigation. So the assumption was right, our best solution could possibly be grouping all the css file only into one file. Otherwise, code-splitting CSS will result all of above.
I just checked Gatsby https://github.com/gatsbyjs/gatsby/blob/67d8b6be93bb4971dadf6aa8e305af2b53560155/packages/gatsby/src/utils/webpack.config.js#L494-L506 and Vuepress https://github.com/vuejs/vuepress/blob/d2fef5d8f6f00aca13b5594c6084a54e1c8c3b18/packages/%40vuepress/core/lib/node/webpack/createBaseConfig.js#L275-L291
They all created one css file only 😢
A very particular interesting stuff is that code-splitting css might cause issue on ordering

If we don't want to do this, there's no good solution to fix this problem :)

Yeah I agree. CSS is usually small in comparison to JS and it's ok to not split it.


Added Feature/workerpipe

added JenkinsFile for the worker app
Currently, it only has a working stage for build job using mock steps

First mock


Wallet data Storage in Mobile's internal storage

The mediator and Edge agent wallet's data is stored in system's directory : ~/.indy_client/wallet
Is this Wallet's data being stored anywhere in the Mobile phone's internal storage ? If yes, then how to access those files or view them in storage of phones ?

I'm closing this as I found the data folder which was apparently hidden in android device(internal storage folder), but isn't hidden in the emulator.


Some observations after 290k steps

Hello,
After training for 290k (and still going) on 2 GPUs, I have decided to test conversion.
Results so far:
-- Conversion to M seen (but not seen in HifiGan):

F seen to M seen -- very similar to the src F seen
M seen to M seen -- very similar to the src M seen
F unseen to M seen -- very similar to the src F seen
M unseen to M seen -- pretty similar to the tgt M seen

So, 4 is pretty good, whilst 1-3 are similar to the source, not the target.
My setup is the same as yours, used Freevc with SR pre training.
Dataset has 110 VCTK speakers in total (including 40 custom speakers).
Is this the question of more training? Or HifiGan not trained on custom speakers?
UPDATE:
-- Conversion to M seen (also seen in HifiGan):

F unseen to M seen -- pretty similar to the tgt M seen
M unseen to M seen -- pretty similar to the tgt M seen

So, it seems like the issue is with Vocoder -- it must be trained on all dataset beforehand.

Btw, eval section of the tensorboard shows nothing.

Tested on my 290k checkpoint and it can convert properly. I guess your problem might be caused by dataset imbalance (i.e. data of some tgt speakers are too little compared to other speakers).
Eval section of the tensorboard is not empty. Maybe you did not tick on '<log_dir>/eval' on the bottom left corner of tensorboard.

Indeed my custom dataset has fewer total time per speaker (about 600-700 seconds) than VCTK speakers. But why male to male conversion works OK for the custom speakers.
I guess I have to level out the data for all speakers.

No idea. (＠_＠;)

I don't think this is the case -- as in the original VCTK you have speakers ranging from 600 seconds to 1000 seconds. I'll try with the vocoder trained on the joint dataset and see whether this is the actual reason why conversion isn't consistent for additional speakers.

I did click on <log_dir>/eval.
g/ losses are all empty for eval

Btw, eval section of the tensorboard shows nothing. Is this expected?

@skol101 , You did haven't wrote eval loss to tensorboard in train.py


how to do Feature embedding visualization?

hi，author！I noticed the feature visualization in Figure 2 in the paper, I would like to ask for the plotting details here, is it convenient to provide some plotting source code to help?

Hi,
Please reach out to my email. I can send the Jupyter notebook to you.

Hi,
thanks for the amazing work. Can you also share the jupyter notebook with me? I am also looking to visualize the feature embeddings.


Update librdkafka?

The version of librdkafka seems fixed at 1.4.2, which is about a year and a half old at this point. Any reason not to use a newer version? Maybe this can be incorporated into CI?
Also, all the examples show compiling librdkafka from source. Any reason not to install it with a package manager?

@chuck-alt-delete yeah that shouldn't be an issue.  To run the tests with a new version the only update is to https://github.com/SeisoLLC/zeek-kafka/blob/main/docker/docker-compose.yml#L49

Thanks Jon!
Sort of related is:

https://github.com/SeisoLLC/zeek-kafka/issues/33

If docker image artifacts are published somewhere, maybe it makes sense to have images with different versions of zeek and different versions of librdkafka so people can pull off the shelf what version they need?


Fix constant redefinition warning

Hi,
Here is a commit to fix a warning that I got in my Rails application while using this gem.
...config/initializers/emarsys.rb:39: warning: already initialized constant Emarsys::FieldMapping::ATTRIBUTES
...bundle/ruby/2.3.0/gems/emarsys-0.3.4/lib/emarsys/field_mapping.rb:4: warning: previous definition of ATTRIBUTES was here
Loading production environment (Rails 4.2.8)

DANGER: this is a breaking change, because I replaced the constant definition by a method call!
Thanks!

@my-kel i'm wary of merging a breaking change like this. Why do you need to redefine the constant in your application? The default field-mappings for the standard Emarsys fields should be left intact and merely added to in 99% of cases, no?

@mungler I just followed the ge documentation (README.md) and got this warning. Here is the part I followed...
# Add to the Mapping-Constant
Emarsys::FieldMapping::ATTRIBUTES << {:id => 100, :identifier => 'user_id', :name => "User-ID"}

@my-kel closing in favour of https://github.com/Absolventa/emarsys-rb/pull/52 which builds on your work here 👍


R&D / Change Project.ReleaseDate

In general, projects without ReleaseDates are not needed.
So, the data type will be not nullable and everything without ReleaseDates must be purged.
Dixi.

I've changed my mind.


Is king under attack prop

Hi!
Is there a simple way to add isKingAttacked in exported JSON?
It would be really helpful to show notifications about such events for players on screen.
As far as I looked into it there is no simple way to determine it straight from FEN 😓

I cant read API properly, there is already such prop
Sorry I'm super empty minded sometimes 🤫

I cant read API properly, there is already such prop
Sorry I'm super empty minded sometimes 🤫


Comms for this (1 1/2 weeks to communicate before event), Ideally end of week 2

What
Things to prep:
PRE

email to attendees with prep material. For example, urls etc.
Write some blurb for ticket tailor, session description, platforms, how long, session type
Write some blurb for socials: slack, x-gov slack, linkedin, x, internal mailing list, mailchimp

DURING

retro consistency board

POST

Github discussion roundup

Why
Done when

[ ] Create asset for eventbrite and/or mailchimp
[ ] Create copy for eventbrite and/or mailchimp
[ ] Create copy for slack posts
[ ] Share...

Proposed date: Monday 18th March, afternoon 1:30-3pm


chore: update claim page faq copy

Summary of changes
Provide a detailed description of proposed changes.

update copy within FAQ section for Tangle Airdrop Claim page

@vutuanlinh2k2 or @devpavan04  could you assist me with adding URL links to mentions of Edgeware and Tangle Testnet Leaderboard within the section?

Proposed area of change
Put an x in the boxes that apply.

[ ] apps/bridge-dapp
[ ] apps/hubble-stats
[ ] apps/stats-dapp
[x] apps/tangle-dapp
[ ] apps/testnet-leaderboard
[ ] apps/faucet
[ ] apps/zk-explorer
[ ] libs/webb-ui-components

Reference issue to close (if applicable)
Specify any issues that can be closed from these changes (e.g. Closes #233).

Closes

Screen Recording
If possible provide a screen recording of proposed change.

Code Checklist
Please be sure to add .stories documentation if any additions are made to libs/webb-ui-components.

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

@monaiuu can you show me where to add those links

@monaiuu can you show me where to add those links

Add https://www.edgeware.io/ to Edgeware.

Add https://leaderboard.tangle.tools/ to Tangle Incentivized Testnet Campagin & Tangle Testnet Leaderboard.

(I was unsure how to do it since the FAQ file is in .ts rather than .tsx format)

Idea: We may want to move away from defining the FAQ as a constant, and maybe use React components, ie. FAQItem especially if we want embedded things on its contents, like links:
<FAQItem title="Some title here">
  Some content here

  Learn more
</FAQItem>

I do think that the constant approach keeps it more centralized, but it may not be as beneficial if the content/FAQ items won't be changing regularly.

CC @thomivy for extra checking (PR any new updates)


Final updates to 1.0.10

Removed Get-AppByName.ps1
Added Get-EnterpriseAppByName.ps1
Added Get-RegisteredAppByName.ps1
Fixed logging in New-SelfSignedCert to surpress IO.Directory output and now usign custom output
Added counter for self-signed cert creation
Fixed documnetation in New-ServicePrincipalObject.ps1
Added new parameters GetEnterpriseApp and GetRegisteredApp
Changed function names from GetAppByName to GetEnterpriseApp
Added new function for GetRegisteredApp
Updated manifest file to remove 'Get-AppByName' and add 'Get-EnterpriseApp' and 'Get-RegisteredApp'
Updated Changlog

Rejecting due to two files not being updated


Chap3 Reproduction

Hi Aurélien,
In chapter 3 with the MNIST dataset, I was trying to reproduce what you've done but the result doesn't seem to match to yours. I have the seeds set to be 42 but still got no luck. Could it be the dataset was changed or I didn't reshuffle the dataset?
Thanks and stay safe.
J

Hey @TurquoiseA .
I got the same as well. Any luck?


How to execute the re-run shell script after its been generated.

Hi,
I have followed the documentation available here: https://v7.webdriver.io/docs/wdio-rerun-service/#re-run-vs-retry
I am getting the expected output of a json file and a Shell script. So far so good.
              [RerunService, {                 rerunDataDir: 'output/wdio-rerun-service',                 rerunScriptPath: 'output/wdio-rerun-script.sh',                 ignoredTags: ['@wip', '@web'],             }],
The piece I am having trouble with is how to incorporate this into my run command/ package.json?
I tried this kind of thing within my scripts:
 "wdio-rerun-ios": "MOBILE_OS=IOS wdio run src/config/wdio.local.conf.ts && output/wdio-rerun-script.sh"
then running yarn run wdio-rerun-ios
It, however, basically ignores the re-run script and the other way around it says it can't find the wdio config so that's a non-starter.
If anyone can point me in the right direction or to some useful documentation around this in general it would be greatly appreciated.
I realise this is not really an issue with the service but maybe an oversight in the docs/ or at least worthy of an example.
Thanks

@suleytron Thanks for opening an issue. Yes, this aspect could use some clarification.
This is how I do it in my project:
Assuming rerun.sh was generated, I have a secondary shell script that only initiates the rerun if its below a certain threshold of failures (no point in rerunning a suite that's almost completely bombed, something else would be afoot):
#!/usr/bin/env bash
MAX_TO_RERUN=${MAX_TO_RERUN:=250}
if [ -f "rerun.sh" ]; then
  echo "[rerun.sh] file exits, checking total failures."
  NUMBER_OF_FAILURES=$(grep "\-\-spec" -o rerun.sh | wc -l | xargs)
	if [ "$MAX_TO_RERUN" -gt "$NUMBER_OF_FAILURES" ]; then
    echo "Re-running $NUMBER_OF_FAILURES failed scenarios!"
    . ./rerun.sh
	else
    echo "Skipping re-run, expected < $MAX_TO_RERUN failures to qualify execution for re-run, got $NUMBER_OF_FAILURES failures."
	fi
else
  echo "No [rerun.sh] file exits, skipping re-run!"
fi

I then have an attempt-rerun script in my package.json:
    "attempt-rerun": ". ./attemptRerun.sh"

Which I then run in my actual execution script after the primary test run:
npm run "$CUCUMBER_PROFILE"
npm run attempt-rerun

There's certainly no hard and fast rule for how to do this, but I think we do need to make it obvious WDIO will not automatically rerun failed scenarios without any intervention.

@suleytron and @esaari PR for documentation is up!


[WIP] Add support of dynamic table names

Fixes #373
Problem
Currently table name should be known at compile time, even if query is designed to be dynamic by default. There's no way to define runtime table name.
Solution
Introduce StaticName and DynamicName.
At compile time Ast is normalized and generated query is printed to output (DynamicName is parsed as wildcard (tree.toString) within curly braces e.g. .. FROM ${tableName} ..)
Then it fallbacks to dynamic expanding (so we can replace DynamicName with StaticName here).
Since such approach requires twice call of idiom.translate I've decided to introduce querySchemaDynamicName (maybe better name?). Hence dynamic table name approach will be applied only if users explicitly required this.
Checklist

[ ] Unit test all changes
[ ] Update README.md if applicable
[x] Add [WIP] to the pull request title if it's work in progress
[ ] Squash commits that aren't meaningful changes
[ ] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

Closing in favor of #1020


cannot display images when using custom blueprint

I am creating a custom modular that is essentially an image gallery. I used this  page as a reference when creating my blueprint for the gallery.
https://learn.getgrav.org/forms/blueprints/how-to-add-file-upload
Now in my twig template, after I add images to my module, I can dump my list of images and see each image and its properties, ie. name and path. However, when I try to reference those properties, I get null values.
How can I dump an array, ie. dump(image), and get:
array:1 [
<EMAIL_ADDRESS>=> array:4 [
"name" => "logo.png"
"type" => "image/png"
"size" => 53440
"path" =><EMAIL_ADDRESS>]
but then dump a property, ie. dump(image.path), and get null?

I've solved my own problem. I fault my lack of knowledge in accessing complex objects in Twig.
This post lead me to solve my problem: https://getgrav.org/forum#!/?image upload blueprints
Basically, when looping through my images, I needed to access each image by its key.
here is the loop in my View:
			{% for key, item in image.image %}

			{% endfor %}

Good to see you solved, closing

How media_directory() works? Gives me this error
 Twig_Error_Runtime
An exception has been thrown during the rendering of a template ("Object of class Grav\Common\Page\Media could not be converted to string").

Alright: issues/1545

@klihelp It returns Media object, see how to use it in https://learn.getgrav.org/content/media


PI-8301 fixed some wrong translation

Coverage remained the same at 21.428% when pulling f35194b35a58867e7aef6bacfd40942fdff4a809 on PI-8301-wrong-translations into 6c661a597a82c329b935208f8120c13d3b6f2235 on master.


refactor(core): Simplifed Registry interface, drop MetricType

Codecov Report
Patch coverage: 98.88% and project coverage change: -0.29% :warning:

Comparison is base (8adddfd) 100.00% compared to head (efd89df) 99.71%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##                 2.x       #9      +/-   ##
=============================================
- Coverage     100.00%   99.71%   -0.29%
- Complexity        92      125      +33
=============================================
  Files             21       24       +3
  Lines            526      700     +174
=============================================
+ Hits             526      698     +172
- Misses             0        2       +2

Files Changed
Coverage Δ

src/Collector/ByType/GaugeCollector.php
100.00% <ø> (ø)

src/Collector/ByType/HistogramCollector.php
100.00% <ø> (ø)

src/Metric/Summary.php
90.47% <90.47%> (ø)

src/Collector/ByType/SummaryCollector.php
100.00% <100.00%> (ø)

src/Collector/CollectorFactory.php
100.00% <100.00%> (ø)

src/Storage/InMemory/InMemoryStorage.php
100.00% <100.00%> (ø)

src/Storage/InMemory/InMemorySummary.php
100.00% <100.00%> (ø)

src/Storage/StorageTesting.php
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Test Kotlin 2.1.0-Beta2 in CI

Tests compatibility of current Poko main branch with the new Kotlin beta version.

java.lang.NoSuchMethodError: 'org.gradle.api.provider.Property org.jetbrains.kotlin.gradle.dsl.KotlinCommonCompilerToolOptions.getExtraWarnings()'

This is thrown with 2.1.0-Beta2. I think this means we just won't be able to make 2.1 and 2.0 compatible, much like 2.0 and 1.9. Unless there's some Gradle magic we can do?

That stack trace is weird. Isn't it KGP calling into itself that is causing the exception? Are there two KGPs on the Gradle classpath or something?

This code:
https://github.com/drewhamilton/Poko/blob/4e710feff6d2d35633bb27865b33cfca34864ad5/sample/settings.gradle.kts#L76-L84
Needs to also live here:
https://github.com/drewhamilton/Poko/blob/4e710feff6d2d35633bb27865b33cfca34864ad5/sample/buildSrc/settings.gradle.kts#L3-L5
Otherwise the buildSrc uses the enclosing project's libs.version.toml's KGP, whereas the sample itself uses the overridden KGP. This puts two copies onto the buildscript classpath which can cause a split-brain problem with classes from both being loaded at the same time producing otherwise impossible NSMEs and NCDFEs.

I can send a PR for that later, if you don't get to it first.

Ouch. Good find, fixed.


feat: support Chrome 63

Puppeteer needs to be mostly functional with stable chrome. The first
stable chrome that will be supported will be Chrome 63.
This patch:

adds backwards compatibility with Chrome 63 (currently, it's only the
renamed request interception protocol call)
whitelists a few tests to be ran only on Chrome 64+
adds a new unit-chrome-63 command that runs unit tests against
Chrome M63
adds a travis job to run tests against Chrome 63.

Over time, when Chrome 63 will be promoted to beta, we'll switch to
support Chrome Beta, and eventually Chrome Stable.

Closing this since we missed the chrome 63 target for now.

Any idea when its going to be back?

@Bnaya we're aiming for M64 now.


Stop inheriting from QiskitTestCase

What is the expected enhancement?
Per the discussion here, it makes more sense for ibmq tests to be more self-contained, especially since qiskit.test is being deprecated.

5


Check CPU compatibility?

I noticed yesterday that our NEONSDK YugaByte unit tests are failing on the build machine:
λ docker ps -a
CONTAINER ID   IMAGE                                    COMMAND                  CREATED          STATUS                      PORTS     NAMES
8a2ad592e08f   yugabytedb/yugabyte:<IP_ADDRESS>-b4          "/sbin/tini -- /home…"   32 minutes ago   Exited (1) 32 minutes ago             yb-tserver-n1
d5de3a48d0bf   yugabytedb/yugabyte:<IP_ADDRESS>-b4          "/sbin/tini -- /home…"   32 minutes ago   Exited (1) 32 minutes ago             yb-master-n1
6757a0c340b9   ghcr.io/neonrelease-dev/neon-clocksync   "/docker-entrypoint.…"   33 minutes ago   Exited (0) 33 minutes ago             elegant_swanson

C:\Temp
λ docker logs 8a2ad592e08f
Not implemented (yb/util/init.cc:69): The CPU on this system (AMD Opteron(tm) Processor 6176 SE) does not support the SSE4.2 instruction set which is required for running YB.

It looks like the processors on this machine are about 12 years old which explains this.
https://www.cpu-world.com/CPUs/K10/AMD-Opteron 6176 SE - OS6176YETCEGO.html
@marcusbooyah: It doesn't look like we ever deploy YugaByte during cluster setup, so we should be OK, right?
Otherwise, we'd need to add a cluster prepare/setup step that checks for CPU compatibility,

FYI: This machine also doesn't support nested virtualization which is breaking the Hyper-V unit tests.  I'm not going to worry about this; we'll do unit tests on the other runner/jumpbox machines.

CLOSING: We're not going to support CPUs this old.


Add cron-job test for VM image builds

Supersedes packit/deployment#552

@majamassarini sorry for the confusion, I must've forgotten to remove the validation from the deployment repository when I moved it out :D


Tile coordinate (x, y) on WSI

There are several places to use tile coordinates in the tile and slide encoder pipeline. Is the tile coordinate (x, y) the top left point or central point of a tile on a WSI that are expected in the pipeline?

Hi thanks for reaching out. We are currently working on releasing more details on the tiling process. It will probably come out by next week. Please stay tuned.

Hi, do you have an update on the tiling process?

Hi, do you have an update on the tiling process?

Thank you for the patience! We have now released the tiling scripts! Please check this guide!


os/exec: data race between StdoutPipe and Wait

Problem
If you are reading from cmd.StdoutPipe() and call cmd.Wait() concurrent you get a race condition.
I needed some time to find this in my code, but once I knew what I was looking for I found the same problem in other codebases, blogposts, ect.
This is really similar to: https://github.com/golang/go/issues/9307
I am quite sure I am not the first one to find this, but I could not find a matching issue, please close this if there is one.
Example
Here is a little example.
I did not constructed it, I actually found it in a blog post.
package main

import (
	"bufio"
	"fmt"
	"os"
	"os/exec"
)

func main() {
	cmdName := "echo"
	cmdArgs := []string{"hello", "world"}

	cmd := exec.Command(cmdName, cmdArgs...)
	cmdReader, err := cmd.StdoutPipe()
	if err != nil {
		fmt.Fprintln(os.Stderr, "Error creating StdoutPipe for Cmd", err)
		os.Exit(1)
	}

	scanner := bufio.NewScanner(cmdReader)
	go func() {
		for scanner.Scan() {
			fmt.Printf("%s\n", scanner.Text())
		}
	}()

	err = cmd.Start()
	if err != nil {
		fmt.Fprintln(os.Stderr, "Error starting Cmd", err)
		os.Exit(1)
	}

	err = cmd.Wait()
	if err != nil {
		fmt.Fprintln(os.Stderr, "Error waiting for Cmd", err)
		os.Exit(1)
	}
}

Here you can see it failing on  different CI / Go versions: https://github.com/xxorde/race
What version of Go are you using (go version)?

1.6.x
1.7.x
1.8.x
master

What operating system and processor architecture are you using (go env)?
linux, amd64

/cc @ianlancetaylor

Could you please paste the data race report here. Thanks.
On Fri, 24 Mar 2017, 10:00 Brad Fitzpatrick<EMAIL_ADDRESS>wrote:

/cc @ianlancetaylor https://github.com/ianlancetaylor
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/19685#issuecomment-288886092, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcA89SewVYFUnq2mBkVG87xGqUjCKTks5rovlvgaJpZM4MneFa
.

% go run --race main.go                                                                                :(
hello world
==================
WARNING: DATA RACE
Write at 0x00c42009a120 by main goroutine:
  os.(*file).close()
      /usr/local/go/src/os/file_unix.go:143 +0x124
  os.(*File).Close()
      /usr/local/go/src/os/file_unix.go:132 +0x55
  os/exec.(*Cmd).closeDescriptors()
      /usr/local/go/src/os/exec/exec.go:262 +0x67
  os/exec.(*Cmd).Wait()
      /usr/local/go/src/os/exec/exec.go:447 +0x2bd
  main.main()
      /home/sosna/src/go/src/github.com/xxorde/race/main.go:37 +0x257

Previous read at 0x00c42009a120 by goroutine 6:
  os.(*File).read()
      /usr/local/go/src/os/file_unix.go:228 +0x50
  os.(*File).Read()
      /usr/local/go/src/os/file.go:101 +0x6f
  bufio.(*Scanner).Scan()
      /usr/local/go/src/bufio/scan.go:208 +0x526
  main.main.func1()
      /home/sosna/src/go/src/github.com/xxorde/race/main.go:26 +0x47

Goroutine 6 (finished) created at:
  main.main()
      /home/sosna/src/go/src/github.com/xxorde/race/main.go:29 +0x21e
==================
Found 1 data race(s)
exit status 66

@xxorde I think (although not an expert on this) @ianlancetaylor's comment is relevant here. i.e. you
need to be explicit that you've completed the read before waiting (should really be error handling in the scanner go routine):
package main

import (
	"bufio"
	"fmt"
	"os"
	"os/exec"
)

func main() {
	cmdName := "echo"
	cmdArgs := []string{"hello", "world"}

	cmd := exec.Command(cmdName, cmdArgs...)
	cmdReader, err := cmd.StdoutPipe()
	if err != nil {
		fmt.Fprintln(os.Stderr, "Error creating StdoutPipe for Cmd", err)
		os.Exit(1)
	}

	done := make(chan struct{})

	scanner := bufio.NewScanner(cmdReader)
	go func() {
		for scanner.Scan() {
			fmt.Printf("%s\n", scanner.Text())
		}

		done <- struct{}{}
	}()

	err = cmd.Start()
	if err != nil {
		fmt.Fprintln(os.Stderr, "Error starting Cmd", err)
		os.Exit(1)
	}

	<-done

	err = cmd.Wait()
	if err != nil {
		fmt.Fprintln(os.Stderr, "Error waiting for Cmd", err)
		os.Exit(1)
	}
}

@myitcv thank you for this hint. I will most likely do exactly this in my own code.
The problem why I consider this still as a bug is that this behavior is not obvious to most users.
My whole point was that I wanted to wait for the read to finish and I used  cmd.Wait() because it seemed to be THE intended way to do. A quick search on google confirmed that other people make the same assumption.

@xxorde again I'll defer to wiser heads on this, but I'm not sure this is a bug in implementation or documentation:
https://godoc.org/os/exec#Cmd.Wait

Wait waits for the command to exit

If c.Stdin is not an *os.File, Wait also waits for the I/O loop copying from c.Stdin into the process's standard input to complete.

Critically it waits for the command to exit. When this happens:

Wait releases any resources associated with the Cmd.

which implies it will tidy up the stdout and stderr pipes (if set). The race occurs if you still happen to be reading from the pipe when this tidy up happens.
By making it explicit that you're finished reading (which will happen either when you choose (i.e. you don't want to read all the output) or when you reach EOF when the command exits) you can then call Wait.

I can't reproduce the race anymore with the race detector with the example program. Maybe https://github.com/golang/go/issues/7970 fixed this?

Thanks for looking at this.  I agree: I think this is fixed in 1.9.  The closely related problem #18874 is not fixed, but this one should be OK now.

The docs need a update though.
https://godoc.org/os/exec#Cmd.StderrPipe
Wait will close the pipe after seeing the command exit, so most callers need not close the pipe themselves; however, an implication is that it is incorrect to call Wait before all reads from the pipe have completed.

@nhooyr I think the docs are OK.  It's still a logical error, it just doesn't lead to a race condition.  If you call Wait before all the reads have completed, then the current in-progress read will complete, but any remaining data on the pipe will be lost.

Fair enough.

Hi just came accross this issue in my code. Partly because of copying the code from one of the faulty examples available on the internet.
So to summarise this thread, this is a non-issue that appeared because the code makes some wrong assumptions about the cmd.Wait(), am I correct??
If yes then is @myitcv suggested code work-around of acquiring a channel and releasing a channel the correct way to go about it fixing this...
https://github.com/golang/go/issues/19685#issuecomment-288949629

@eff-kay Nobody really tracks discussions on closed issues.  More importantly, you didn't show us the code, so I don't know what you are seeing.  In general, yes, you need some sort of coordination between a goroutine reading from a pipe from a subprocess, and waiting for the subprocess.  Using a channel will work, and there are other possibilities.  If you are looking for help with your code, I recommend that you use a forum rather than a discussion on a closed issue; see https://golang.org/wiki/Questions .


Queue & Set should implement ArrayAccess

As mentioned in https://github.com/php-ds/polyfill/issues/72, Queue and Set implement ArrayAccess methods, but don't report it.

Quite the oversight, thank you.


Added Dockerfile

closes #7

package-lock.json file is not needed, there are no changes to the package.json file

Thank you for the contribution, the Dockerfile has now been added


Cynthia server

First step of the server programming tutorial: modified DataServelet.java file to change the response to /data URLs

I found this on Sherry's PR as well that commits from previous PR is included. Please consider start work on a new branch since it's not dependent on the work of the previous PR. Thanks!


[W5.8b][W13-A1]Dominic Kenn Lim

Add more NFR to DeveloperGuide.

@dominickenn
NFR (and requirements in general) should be as precise as possible.
Avoid adjectives like easy, fast, intuitive etc.,
Instead, use precise statements like response time should be 1 second, detailed help which shows all options should be present
Some comments added. Please ack & close the PR after reading comments.

Acknowledged.


chore: update ansi-regex

SUMMARY

fix synk issue here: https://app.snyk.io/vuln/SNYK-JS-ANSIREGEX-1583908
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

🏷 preset:2023.25


Add Logging into 2.0

Disabled by default. Enabling will install Fluentd
[ ] Support for ability to configure cluster-wide logging of stdout/err of containers and workloads
[ ] Support for ability to configure project-wide logging of stdout/err of containers and workloads
[ ]Support for ability to configure workload logging of a specific directory
[ ] Support for following Log Targets
[ ] Rancher embedded logging - Experimental and used for testing
[ ]  ElasticSearch
[ ]  Splunk
[ ] Syslog
[ ]  Kafka

Version - 2.0 master 2/23
Verified added - bug will be entered separately from this issue.

Fluent Bit!


Increase Charging Plan Slots to more than 42 hours if more data is available

Is your feature request related to a problem? Please describe.
I'm developing a Energy Forecast service where there is price data available for 48 hours or even 96 hours (paid). For now it is not possible to see all those forecasted hours. Therefore I'm also not sure if this information is used for planned charging.
Describe the solution you'd like
If there is more data available then 42 hours in the future I would like to see and use of all it.
Additional context
for more context see my little introduction to the tool: https://github.com/evcc-io/evcc/discussions/14211

Fixed in master

Sorry, I had to revert https://github.com/evcc-io/evcc/commit/fc377138d1debfea0d4bfc749911f1be580bf73b, it was a wrong fix. That said: I do not see any limitation to 48 slots in the code.

In the frontend only 42 hours are shown. I guess that 48 hours are used. It would be awesome if 96 of forecast or more could be used if available (and bonus: shown in the frontend).


Add: Allow Separation of Menus into their own files

Allow menus to be in their own files. Each menu should be under /Menus/[MenuName]

Closing as this has been added


more style changes

👷 Deploy Preview for johare-cv processing.

Name
Link

🔨 Latest commit
75ffd5a2b68d0d014041891d894d7c7fa4dde5d4

🔍 Latest deploy log
https://app.netlify.com/sites/johare-cv/deploys/65f8ab82d5037c00086455bc


Do not expose mutable collections from FHIR BuildItems

BuildItems should not expose mutable collections because they are consumed from concurrent threads. Mutability does not seem to be required here. Making the properties immutable would simplify the reasoning about the code.
This applies at least to

Dstu2PropertiesBuildItem
R5PropertiesBuildItem
R4PropertiesBuildItem
Dstu3PropertiesBuildItem

@ppalaga
The idea here is to allow the user to add FHIR resources to the FHIR context before recording.  See https://wiki.hl7.org/FHIR_Custom_Resources

Fixed via 623e0456c074b26d1ca53cd2baf28b17c23257b3


Cannot use embedded forms on the app

Hello,
I've been working on an application using the webapp starter, and have been trying to get an embedded form to work. My project structure is very similar to the one found in examples/camunda-spring-boot-starter-example-webapp. I tried creating a folder src/main/webapp/forms with a file greetingForm.html , and modifying sample.bpmn so that the user task "do something" has form key app:embedded:forms/greetingForm.html, but I get a CORS error displayed when trying to view the form in the Tasklist.
We experienced a similar problem with a non-spring-boot Camunda project, and the issue went away when we used an META-INF/process.xml without any configuration, like:
<?xml version="1.0" encoding="UTF-8" ?>
<process-application
    xmlns="http://www.camunda.org/schema/1.0/ProcessApplication"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <process-archive>
    <process-engine>default</process-engine>
    <properties>
    </properties>
  </process-archive>
</process-application>

but the same approach doesn't seem to work here. The problem seems to involve the contextPath being null in the response below, which is obtained by tasklist app when using the API endpoint /api/engine/engine/default/task/1408
{"key":"embedded:app:forms/greetingForm.html","contextPath":null}

Can embedded forms work with the spring boot webapp starter? Is this a bug, pending feature, or something I'm missing? Thanks!

Hi.
IMHO: never tried that. Could you please provide an example project (on github)?

Am 07.02.2016 um 10:47 schrieb Kiyan Ahmadizadeh<EMAIL_ADDRESS>Hello,
I've been working on an application using the webapp starter, and have been trying to get an embedded form to work. My project structure is very similar to the one found in examples/camunda-spring-boot-starter-example-webapp. I tried creating a folder src/main/webapp/forms with a file greetingForm.html , and modifying sample.bpmn so that the user task "do something" has form key app:embedded:forms/greetingForm.html, but I get a CORS error displayed when trying to view the form in the Tasklist.
We experienced a similar problem with a non-spring-boot Camunda project, and the issue went away when we used an META-INF/process.xml without any configuration, like:

default

but the same approach doesn't seem to work here. The problem seems to involve the contextPath being null in the response below, which is obtained by tasklist app when using the API endpoint /api/engine/engine/default/task/1408
{"key":"embedded:app:forms/greetingForm.html","contextPath":null}
Can embedded forms work with the spring boot webapp starter? Is this a bug, pending feature, or something I'm missing? Thanks!
—
Reply to this email directly or view it on GitHub.

Sure! Please checkout my fork of the repo, branch embedded-forms off tag 1.1.0 (the version we're using, but this same problem exists on master).
examples/camunda-spring-boot-starter-example-webapp has been modified so that sample.bpmn uses an embedded form in the "do something" task. The form is located at src/main/webapp/greetingForm.html. If you start the example with mvn spring-boot:run, make your way to the tasklist, start the Sample process, and click on the task that's assigned to you when the process starts (I use the notification about the task being assigned to me that pops up in the bottom right) you encounter the error.
Thanks for the help!

If it helps, I'm working off of this example from the Camunda docs.

We have a workaround, but I tracked down more of an exact cause using my debugger and wanted to share. Because there is no process engine application (sometimes called a process archive) associated with the SpringAutoDeployment, the context path for the application cannot be retrieved, and this results in the embedded form key not being translated.
More precisely, the relevant portion of the call stack in Camunda 7.4 looks like:
....
ManagementServiceImpl#getProcessApplicationForDeployment(String): 86
ApplicationContextPathUtil#getApplicationPathForDeployment(ProcessEngine, String): 42
TaskResourceImpl#getForm(): 197

The TaskResourceImpl tries to set the context path in the FormDto that gets returned as the response to the task form endpoint. ApplicationContextPathUtil tries to retrieve the context path by querying the ManagementServiceImpl for the process application name. The management service returns null for the process application name, because there is no process application associated with the deployment. As a result, ApplicationContextPathUtil returns null for the context path, this is what gets set in the FormDto, and as a result the frontend cannot translate the form key into an actual URL.
If it were possible to associate a process application / process archive with the auto-created deployment, I believe that would resolve the issue.
Hope this helps. Please at-me if I can answer any questions.

I think it would be a good idea to use an ProcessApplication, see
https://forum.camunda.org/t/formkey-resolve-embedded-app-fails-with-spring-boot/479
https://docs.camunda.org/manual/7.4/user-guide/process-applications/the-process-application-class/#the-embeddedprocessapplication

This might also solve #53 ... we just use processapplication.deploy instead of implementing our own resource-parser

Fixed by #76
Using the SpringBootProcessApplication
@SpringBootApplication
public class MyApp extends SpringBootProcessApplication {}

fixes this issue by adding a servletContextPath="/"property to the application which is used by the formService to resolve the ":app:" identifier.

Well, the same problem occurs for me when using Spring Boot 2.0.2, but setting server.servlet.contextPath doesn't fix it for me. I don't even get an error in my server log, just an invalid HTTP request to http://localhost:8080/forms/ergebnis-lesen.html?noCache=1529563649812&taskId=f5ddea46-751e-11e8-870f-aced5cb84e54&userId=demo
I am using the camunda-bpm-spring-boot-starter-webapp-ee with version 3.0.0.

I would suggest to raise a support ticket


Extend Android onboarding documentation

Description
Updated the onboarding documentation for Android (mitm.it) with the Android 12 flow and a added a link to the Android network security config.
Checklist

[x] I have updated tests where applicable.
[ ] I have added an entry to the CHANGELOG.

Thanks! 🍰 😃


Duplicate/delete bug, likely caused by files not reloading

Describe the bug
Often when duplicating a key from the tree view, it only duplicates some of the translations. In the example below, it correctly copied the dutch and french translations, but not the German or English ones. Looking at the .json files, both those keys contain empty strings.

This is with the 'keepFulfilled' setting set to 'true'. Which is important, because I'm pretty sure that's why those 2 translations contain empty strings.
The issue I think, is that it does duplicate all those translations, but only detects and reloads some of the translation files. It then writes an empty string to the ones it didn't reload. See the output log below. It writes to all 4, detects updates and reloads only the 'nl' and 'fr' files, then writes again to 'en' and 'de'.
When I change 'keepFulfilled' to false, it doesn't write the empty strings to the files, but i do see that it doesn't properly reload the files.
The below, maybe slightly too long, gif shows how it initially only reloads the Dutch translations, and later when setting the 'search4' key it reloaded all except the German language.

I'm having some issues with deleting keys as well. But I suspect this has the same cause. Due to files not being reloaded it thinks the key is still there and later writes empty strings again, recreating the keys.
Extension Version
i18n Ally v1.8.1
Framework/i18n package you are using
ngx-translate
To Reproduce
Steps to reproduce the behavior:

Have a few different language files. We have 4, each containing about 2500 keys.
With 'keepFulfilled' off, duplicate a key. For me, chances are like 90% that it won't reload all translation files. Causing some translations to appear empty.
If you open and save those files manually, it will reload them and show the new state.
Do step 2 again with 'keepFulfilled' turned on.
The files that it didn't reload will actually have an empty string written as values to the duplicated key.

I have changed the writing logic a little, hope it solves this problem.
The fix is released in v1.8.2, please check it out!

Currently on vacation, but I should have some time next week to try it out.
Or the week after that, but it shouldn't take any longer than that. Will definitely let you know once I had a chance to try it.

Okay, I got back to work today.
I updated to the latest 1.9.1 version, but unfortunately it seems that the issue is still there. I duplicated a key, but it still didn't reload every translation file.
The only difference is that it didn't immediately write again with empty keys. But the empty keys will still be saved during any following write action, like duplicating or adding another key.

@JohanBeekers Thanks. I'll test it out again.

Hi @JohanBeekers Sorry for the delay, I have just back from my vacation. But it seems I can not reproduce the problem. Can you share me a minimal repo or more info? Thanks.


Check NULL values

Hakuin does not check NULL values before attempting to extract columns. This may lead to wrong results.
Hakuin should check NULL values in a similar fashion as it checks ASCII values, i.e., first on the column level and then on the row level.

Implemented in 68bb301


[PAGOPA-1066] update iban crud: added description to iban_master

List of Changes

added field description to iban_master table

Motivation and Context

different descriptions for the same iban

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

update_code

update_code

update_code

update_code


Pin @polkadot/util to 8.7.1

Resolves a node dependency error with @polkadot/util when onboarding mrc to relay chain:
./scripts/init.sh onboard-mrc
$ node onboard.js ws://<IP_ADDRESS>:9944 //Alice 2000 0x0000000000000000000000000000000000000000000000000000000000000000003a77d4735bb84db7e6f90d76314e6eb59bb760dfe7d89a6de0be673410c7ac1303170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400 /tmp/mrc/onboard/mrc-local-2000.wasm
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-augment/node_modules/@polkadot/util
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-augment/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/util-crypto/node_modules/@polkadot/util
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-augment/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/util-crypto/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-provider/node_modules/@polkadot/util
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-augment/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/util-crypto/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-provider/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api-derive/node_modules/@polkadot/util
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-augment/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/util-crypto/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-provider/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api-derive/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-core/node_modules/@polkadot/util
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-augment/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/util-crypto/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-provider/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api-derive/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-core/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types/node_modules/@polkadot/util
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-augment/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/util-crypto/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-provider/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api-derive/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-core/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types-create/node_modules/@polkadot/util
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-augment/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/util-crypto/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-provider/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api-derive/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-core/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types-create/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types-codec/node_modules/@polkadot/util
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-augment/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/util-crypto/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-provider/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/api-derive/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/rpc-core/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types-create/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types-codec/node_modules/@polkadot/util
	cjs 8.7.1	/Users/johnmela/code/mrc/scripts/js/onboard/node_modules/@polkadot/types-known/node_modules/@polkadot/util

I was matching the version yarn was installing, which worked for me local. I can try the latest and see if it runs and tests pass if you'd like

@johnmela Ship it for now. We can do a pass on all the packages to upgrade later.


compiling OCGCore

CMake Error: CMake can not determine linker language for target: ocgcore
CMake Error: Cannot determine link language for target "ocgcore".
-- Generating done
-- Build files have been written to: /root/ygosharp/OCGCore
root@Host:~/ygosharp/OCGCore# cmake *.txt >> log2.txt
CMake Error at CMakeLists.txt:116 (add_library):
Cannot find source file:
ygopro-core/card.cpp

Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
.hxx .in .txx
CMake Error: CMake can not determine linker language for target: ocgcore
CMake Error: Cannot determine link language for target "ocgcore".

It looks like the ygopro-core/card.cpp file is missing.
Did you also download the git submodules ?
If you are using the command line, you can use these commands:
git submodule init
git submodule update

Hello @IceYGO
about submodules (continuing this thread) :
you need to sign with a github login to recurse-clone them, which is disabled since at least 3 years iirc.
Is this intended ?
ygopro-core leads to a 404.