Running the mnist example with SMAC tuner results in an error

Environment:

NNI version: 1.8
NNI mode (local|remote|pai):local
Client OS:Fedora32
Server OS (for remote mode only):
Python version: 3.8.5
PyTorch/TensorFlow version: TensorFlow2.3.0
Is conda/virtualenv/venv used?: conda
Is running in Docker?:No

Log message:

nnimanager.log:
[10/8/2020, 8:33:21 PM] INFO [ 'Datastore initialization done' ] [10/8/2020, 8:33:21 PM] INFO [ 'RestServer start' ] [10/8/2020, 8:33:21 PM] INFO [ 'Construct local machine training service.' ] [10/8/2020, 8:33:21 PM] INFO [ 'RestServer base port is 8080' ] [10/8/2020, 8:33:21 PM] INFO [ 'Rest server listening on: http://<IP_ADDRESS>:8080' ] [10/8/2020, 8:33:22 PM] INFO [ 'NNIManager setClusterMetadata, key: local_config, value: {"useActiveGpu":true}' ] [10/8/2020, 8:33:22 PM] INFO [ 'Specified GPU indices: undefined' ] [10/8/2020, 8:33:22 PM] INFO [ 'NNIManager setClusterMetadata, key: trial_config, value: {"command":"python3 mnist.py","codeDir":"/home/fu-workstation/Downloads/nni/examples/trials/mnist-tfv2/.","gpuNum":1}' ] [10/8/2020, 8:33:22 PM] INFO [ 'required GPU number is 1' ] [10/8/2020, 8:33:22 PM] INFO [ 'Starting experiment: rnlQhc8m' ] [10/8/2020, 8:33:22 PM] INFO [ 'Change NNIManager status from: INITIALIZED to: RUNNING' ] [10/8/2020, 8:33:22 PM] INFO [ 'Add event listeners' ] [10/8/2020, 8:33:22 PM] INFO [ 'Run local machine training service.' ] [10/8/2020, 8:33:22 PM] WARNING [ 'gpu_metrics file does not exist!' ] [10/8/2020, 8:33:27 PM] ERROR [ 'Dispatcher error: This socket has been ended by the other party' ] [10/8/2020, 8:33:27 PM] ERROR [ 'Error: Dispatcher stream error, tuner may have crashed.\n    at EventEmitter.dispatcher.onError (/home/fu-workstation/anaconda3/envs/tf23/nni/core/nnimanager.js:509:32)\n    at EventEmitter.emit (events.js:182:13)\n    at Socket.IpcInterface.outgoingStream.on (/home/fu-workstation/anaconda3/envs/tf23/nni/core/ipcInterface.js:41:72)\n    at Socket.emit (events.js:182:13)\n    at Socket.writeAfterFIN [as write] (net.js:405:8)\n    at IpcInterface.sendCommand (/home/fu-workstation/anaconda3/envs/tf23/nni/core/ipcInterface.js:48:38)\n    at NNIManager.pingDispatcher (/home/fu-workstation/anaconda3/envs/tf23/nni/core/nnimanager.js:358:29)' ] [10/8/2020, 8:33:27 PM] INFO [ 'Change NNIManager status from: RUNNING to: ERROR' ] [10/8/2020, 8:33:27 PM] WARNING [ 'Commands jammed in buffer!' ]
dispatcher.log:

[10/08/2020, 08:33:23 PM] INFO (smac_AutoML/Thread-1) update search space in SMAC.
[10/08/2020, 08:33:23 PM] INFO (smac_AutoML/Thread-1) SMAC call: /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/__main__.py --exp_params eyJhdXRob3JOYW1lIjoiZGVmYXVsdCIsImV4cGVyaW1lbnROYW1lIjoiZXhhbXBsZV9tbmlzdF9ib2hiIiwidHJpYWxDb25jdXJyZW5jeSI6MSwibWF4RXhlY0R1cmF0aW9uIjozNjAwMCwibWF4VHJpYWxOdW0iOjEwMDAsInRyYWluaW5nU2VydmljZVBsYXRmb3JtIjoibG9jYWwiLCJ0dW5lciI6eyJidWlsdGluVHVuZXJOYW1lIjoiU01BQyIsImNsYXNzQXJncyI6eyJvcHRpbWl6ZV9tb2RlIjoibWF4aW1pemUiLCJjb25maWdfZGVkdXAiOnRydWV9fSwidmVyc2lvbkNoZWNrIjp0cnVlLCJjbHVzdGVyTWV0YURhdGEiOlt7ImtleSI6ImNvZGVEaXIiLCJ2YWx1ZSI6Ii9ob21lL2Z1LXdvcmtzdGF0aW9uL0Rvd25sb2Fkcy9ubmkvZXhhbXBsZXMvdHJpYWxzL21uaXN0LXRmdjIvLiJ9LHsia2V5IjoiY29tbWFuZCIsInZhbHVlIjoicHl0aG9uMyBtbmlzdC5weSJ9XX0=
[10/08/2020, 08:33:23 PM] PRINT INFO:	Reading scenario file: scenario.txt

[10/08/2020, 08:33:23 PM] PRINT INFO:	Output to smac3-output_2020-10-08_20:33:23_055107

What issue meet, what's expected?:
When I try to run SMAC tuner by using the following config.yml file(check in the reproduce error section). The status of the nni dashboard changes to ERROR

How to reproduce it?:
In the nni examples run mnist-tfv2 with the below config.yml file
experimentName: example_mnist_bohb
trialConcurrency: 1
maxExecDuration: 10h
maxTrialNum: 1000
#choice: local, remote, pai
trainingServicePlatform: local
searchSpacePath: search_space.json
#choice: true, false
useAnnotation: false
tuner:
  builtinTunerName: SMAC
  classArgs:
    optimize_mode: maximize
    config_dedup: True
trial:
  command: python3 mnist.py
  codeDir: .
  gpuNum: 1
localConfig:
  useActiveGpu: True

Additional information:

@AkshayRoyal , I have tried your configuration and failed to reproduce your problem. It is likely that SMAC has not been successfully installed in your system.
First, please check the output of this command nnictl package install --name=SMAC for installing SMAC. Is there error message there?
Second, it is strange that tuner is crashed, but there is no error message in dispatcher.log. Could you run nnictl log stderr <exp-id> to check whether there is error message there?

@QuanluZhang . This is the output for nnictl package install --name=SMAC
  Cloning https://github.com/QuanluZhang/ConfigSpace.git to /tmp/pip-req-build-dyp8rglt
Requirement already satisfied (use --upgrade to upgrade): ConfigSpaceNNI==0.4.7 from git+https://github.com/QuanluZhang/ConfigSpace.git in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from -r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1))
Collecting git+https://github.com/QuanluZhang/SMAC3.git (from -r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2))
  Cloning https://github.com/QuanluZhang/SMAC3.git to /tmp/pip-req-build-2beoi7to
Requirement already satisfied (use --upgrade to upgrade): smac==0.8.0 from git+https://github.com/QuanluZhang/SMAC3.git in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from -r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2))
Requirement already satisfied: numpy in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from ConfigSpaceNNI==0.4.7->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1)) (1.19.1)
Requirement already satisfied: pyparsing in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from ConfigSpaceNNI==0.4.7->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1)) (2.4.7)
Requirement already satisfied: typing in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from ConfigSpaceNNI==0.4.7->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1)) (<IP_ADDRESS>)
Requirement already satisfied: Cython in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from ConfigSpaceNNI==0.4.7->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1)) (0.29.21)
Requirement already satisfied: setuptools in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (49.6.0.post20200814)
Requirement already satisfied: scipy>=0.18.1 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.5.2)
Requirement already satisfied: six in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.15.0)
Requirement already satisfied: psutil in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (5.7.2)
Requirement already satisfied: pynisher>=0.4.1 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.6.1)
Requirement already satisfied: scikit-learn>=0.18.0 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.23.2)
Requirement already satisfied: pyrfr>=0.5.0 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.8.0)
Requirement already satisfied: sphinx in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (3.2.1)
Requirement already satisfied: sphinx_rtd_theme in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.5.0)
Requirement already satisfied: joblib in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.16.0)
Requirement already satisfied: docutils>=0.3 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from pynisher>=0.4.1->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.16)
Requirement already satisfied: threadpoolctl>=2.0.0 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from scikit-learn>=0.18.0->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.1.0)
Requirement already satisfied: sphinxcontrib-qthelp in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.3)
Requirement already satisfied: alabaster<0.8,>=0.7 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.7.12)
Requirement already satisfied: sphinxcontrib-serializinghtml in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.1.4)
Requirement already satisfied: requests>=2.5.0 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.24.0)
Requirement already satisfied: sphinxcontrib-devhelp in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.2)
Requirement already satisfied: Pygments>=2.0 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.7.1)
Requirement already satisfied: packaging in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (20.4)
Requirement already satisfied: Jinja2>=2.3 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.11.2)
Requirement already satisfied: snowballstemmer>=1.1 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.0.0)
Requirement already satisfied: sphinxcontrib-htmlhelp in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.3)
Requirement already satisfied: babel>=1.3 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.8.0)
Requirement already satisfied: sphinxcontrib-applehelp in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.2)
Requirement already satisfied: imagesize in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.2.0)
Requirement already satisfied: sphinxcontrib-jsmath in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.1)
Requirement already satisfied: idna<3,>=2.5 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from requests>=2.5.0->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.10)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from requests>=2.5.0->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.25.10)
Requirement already satisfied: chardet<4,>=3.0.2 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from requests>=2.5.0->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (3.0.4)
Requirement already satisfied: certifi>=2017.4.17 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from requests>=2.5.0->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2020.6.20)
Requirement already satisfied: MarkupSafe>=0.23 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from Jinja2>=2.3->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.1.1)
Requirement already satisfied: pytz>=2015.7 in ./anaconda3/envs/tf23/lib/python3.8/site-packages (from babel>=1.3->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2020.1)
Building wheels for collected packages: ConfigSpaceNNI, smac
  Building wheel for ConfigSpaceNNI (setup.py) ... done
  Created wheel for ConfigSpaceNNI: filename=ConfigSpaceNNI-0.4.7-cp38-cp38-linux_x86_64.whl size=4300769 sha256=7f0d8a83f9d80dbfeabdcefc3232c0f18e9c54b5de47472a17a20283bf325774
  Stored in directory: /tmp/pip-ephem-wheel-cache-wqgaf4zc/wheels/ee/77/ac/d55b9b65449fb09ca265beddcb8f33c10bb557e964b6b05cea
  Building wheel for smac (setup.py) ... done
  Created wheel for smac: filename=smac-0.8.0-py3-none-any.whl size=144817 sha256=d93b5acf9a3ae2e06f4e9f085ffe6b7fb9ebc39f4936d491feedb1c0bea8b796
  Stored in directory: /tmp/pip-ephem-wheel-cache-wqgaf4zc/wheels/36/1e/b2/791232ed991a9fe2d1932108a8fd0a3fde5d6d0a23d01d8536
Successfully built ConfigSpaceNNI smac
ERROR: name SMAC already installed
ERROR: installation failed!

And this is the output for nnictl log stderr
  self.re = re.compile(self.reString)
-----------------------------------------------------------------------
                Experiment start time 2020-10-09 08:55:36
-----------------------------------------------------------------------
Error: Dispatcher stream error, tuner may have crashed.
    at EventEmitter.dispatcher.onError (/home/fu-workstation/anaconda3/envs/tf23/nni/core/nnimanager.js:509:32)
    at EventEmitter.emit (events.js:182:13)
    at Socket.IpcInterface.outgoingStream.on (/home/fu-workstation/anaconda3/envs/tf23/nni/core/ipcInterface.js:41:72)
    at Socket.emit (events.js:182:13)
    at Socket.writeAfterFIN [as write] (net.js:405:8)
    at IpcInterface.sendCommand (/home/fu-workstation/anaconda3/envs/tf23/nni/core/ipcInterface.js:48:38)
    at NNIManager.pingDispatcher (/home/fu-workstation/anaconda3/envs/tf23/nni/core/nnimanager.js:358:29)```

I also tried removing the SMAC package using nnictl package uninstall SMAC which successfully removed SMAC package.
Then I tried installing SMAC using nnictl package install --name SMAC which gave this output
(tf23) [fu-workstation@localhost mnist-tfv2]$ nnictl package install --name SMAC
Collecting git+https://github.com/QuanluZhang/ConfigSpace.git (from -r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1))
  Cloning https://github.com/QuanluZhang/ConfigSpace.git to /tmp/pip-req-build-09fx0qnu
Requirement already satisfied (use --upgrade to upgrade): ConfigSpaceNNI==0.4.7 from git+https://github.com/QuanluZhang/ConfigSpace.git in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from -r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1))
Collecting git+https://github.com/QuanluZhang/SMAC3.git (from -r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2))
  Cloning https://github.com/QuanluZhang/SMAC3.git to /tmp/pip-req-build-jem4936a
Requirement already satisfied (use --upgrade to upgrade): smac==0.8.0 from git+https://github.com/QuanluZhang/SMAC3.git in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from -r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2))
Requirement already satisfied: numpy in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from ConfigSpaceNNI==0.4.7->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1)) (1.19.1)
Requirement already satisfied: pyparsing in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from ConfigSpaceNNI==0.4.7->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1)) (2.4.7)
Requirement already satisfied: typing in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from ConfigSpaceNNI==0.4.7->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1)) (<IP_ADDRESS>)
Requirement already satisfied: Cython in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from ConfigSpaceNNI==0.4.7->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 1)) (0.29.21)
Requirement already satisfied: setuptools in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (49.6.0.post20200814)
Requirement already satisfied: scipy>=0.18.1 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.5.2)
Requirement already satisfied: six in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.15.0)
Requirement already satisfied: psutil in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (5.7.2)
Requirement already satisfied: pynisher>=0.4.1 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.6.1)
Requirement already satisfied: scikit-learn>=0.18.0 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.23.2)
Requirement already satisfied: pyrfr>=0.5.0 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.8.0)
Requirement already satisfied: sphinx in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (3.2.1)
Requirement already satisfied: sphinx_rtd_theme in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.5.0)
Requirement already satisfied: joblib in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.16.0)
Requirement already satisfied: docutils>=0.3 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from pynisher>=0.4.1->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.16)
Requirement already satisfied: threadpoolctl>=2.0.0 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from scikit-learn>=0.18.0->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.1.0)
Requirement already satisfied: sphinxcontrib-devhelp in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.2)
Requirement already satisfied: sphinxcontrib-applehelp in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.2)
Requirement already satisfied: sphinxcontrib-htmlhelp in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.3)
Requirement already satisfied: requests>=2.5.0 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.24.0)
Requirement already satisfied: snowballstemmer>=1.1 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.0.0)
Requirement already satisfied: alabaster<0.8,>=0.7 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (0.7.12)
Requirement already satisfied: Jinja2>=2.3 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.11.2)
Requirement already satisfied: sphinxcontrib-jsmath in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.1)
Requirement already satisfied: Pygments>=2.0 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.7.1)
Requirement already satisfied: packaging in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (20.4)
Requirement already satisfied: sphinxcontrib-qthelp in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.0.3)
Requirement already satisfied: sphinxcontrib-serializinghtml in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.1.4)
Requirement already satisfied: babel>=1.3 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.8.0)
Requirement already satisfied: imagesize in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.2.0)
Requirement already satisfied: idna<3,>=2.5 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from requests>=2.5.0->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2.10)
Requirement already satisfied: certifi>=2017.4.17 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from requests>=2.5.0->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2020.6.20)
Requirement already satisfied: chardet<4,>=3.0.2 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from requests>=2.5.0->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (3.0.4)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from requests>=2.5.0->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.25.10)
Requirement already satisfied: MarkupSafe>=0.23 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from Jinja2>=2.3->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (1.1.1)
Requirement already satisfied: pytz>=2015.7 in /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages (from babel>=1.3->sphinx->smac==0.8.0->-r /home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/nni/smac_tuner/requirements.txt (line 2)) (2020.1)
Building wheels for collected packages: ConfigSpaceNNI, smac
  Building wheel for ConfigSpaceNNI (setup.py) ... done
  Created wheel for ConfigSpaceNNI: filename=ConfigSpaceNNI-0.4.7-cp38-cp38-linux_x86_64.whl size=4300755 sha256=fef0b516cab0879af3928b067dc7ae88d276119c78cb4235085e26b166446ce5
  Stored in directory: /tmp/pip-ephem-wheel-cache-ud_01zjy/wheels/ee/77/ac/d55b9b65449fb09ca265beddcb8f33c10bb557e964b6b05cea
  Building wheel for smac (setup.py) ... done
  Created wheel for smac: filename=smac-0.8.0-py3-none-any.whl size=144817 sha256=0a353f248e5fce170dd51cd5a2612936df48b41bdca668c90e3acbacf5c9bd7d
  Stored in directory: /tmp/pip-ephem-wheel-cache-ud_01zjy/wheels/36/1e/b2/791232ed991a9fe2d1932108a8fd0a3fde5d6d0a23d01d8536
Successfully built ConfigSpaceNNI smac
SMAC installed!

Also, I checked with nnictl package list and the output was
nnictl package list
+-----------------+------------+-----------+--------=-------------+------------------------------------------+
|      Name       |    Type    | Installed |      Class Name      |               Module Name                |
+-----------------+------------+-----------+----------------------+------------------------------------------+
| SMAC            | tuners     | Yes       | SMACTuner            | nni.smac_tuner.smac_tuner                |
| PPOTuner        | tuners     | No        | PPOTuner             | nni.ppo_tuner.ppo_tuner                  |
| BOHB            | advisors   | Yes       | BOHB                 | nni.bohb_advisor.bohb_advisor            |
+-----------------+------------+-----------+----------------------+------------------------------------------+

After that I reran nnictl create --config config.yml which resulted in
nnictl create --config config.yml
INFO:  expand searchSpacePath: search_space.json to /home/fu-workstation/Downloads/nni/examples/trials/mnist-tfv2/search_space.json
INFO:  expand codeDir: . to /home/fu-workstation/Downloads/nni/examples/trials/mnist-tfv2/.
/home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/pyparsing.py:3190: FutureWarning: Possible set intersection at position 3
  self.re = re.compile(self.reString)
INFO:  Starting restful server...
INFO:  Successfully started Restful server!
INFO:  Setting local config...
INFO:  Successfully set local config!
INFO:  Starting experiment...
INFO:  Successfully started experiment!
------------------------------------------------------------------------------------
The experiment id is IsZUHonS
The Web UI urls are: http://<IP_ADDRESS>:8080   http://<IP_ADDRESS>:8080   http://<IP_ADDRESS>:8080
------------------------------------------------------------------------------------

You can use these commands to get more information about the experiment
------------------------------------------------------------------------------------
         commands                       description
1. nnictl experiment show        show the information of experiments
2. nnictl trial ls               list all of trial jobs
3. nnictl top                    monitor the status of running experiments
4. nnictl log stderr             show stderr log content
5. nnictl log stdout             show stdout log content
6. nnictl stop                   stop an experiment
7. nnictl trial kill             kill a trial job by id
8. nnictl --help                 get help information about nnictl
------------------------------------------------------------------------------------
Command reference document https://nni.readthedocs.io/en/latest/Tutorial/Nnictl.html
------------------------------------------------------------------------------------

where the config.yml file contained this
authorName: NNI Example
experimentName: MNIST TF v2.x
trialConcurrency: 1
maxExecDuration: 1h
maxTrialNum: 10
trainingServicePlatform: local  # choices: local, remote, pai
searchSpacePath: search_space.json
useAnnotation: false
tuner:
    builtinTunerName: SMAC   # choices: TPE, Random, Anneal, Evolution, BatchTuner, MetisTuner,
                            #          GPTuner, SMAC (SMAC should be installed through nnictl)
    classArgs:
        optimize_mode: maximize  # choices: maximize, minimize
trial:
  command: python3 mnist.py
  codeDir: .
  gpuNum: 1
localConfig:
  useActiveGpu: True

This is how I was again able to reproduce the issue.
Also, I forgot to mention that I was able to run other tuners and advisors too but SMAC didn't work.

@AkshayRoyal , thanks for the detailed test and description. The failure might be induced by fedora system. Could you run the command python3 -m unittest test_builtin_tuners.BuiltinTunersTestCase.test_smac under the directory src/sdk/pynni/tests to check the output info of the test?

Hi @QuanluZhang. Thanks for your prompt response.
The output for the command you mentioned is
python3 -m unittest test_builtin_tuners.BuiltinTunersTestCase.test_smac
[10/python3 -m unittest test_builtin_tuners.BuiltinTunersTestCase.test_smac
[10/09/2020, 12:06:10 PM] WARNING (nni.protocol) IPC pipeline not exists, maybe you are importing tuner/assessor from trial code?
/home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/pyparsing.py:3190: FutureWarning: Possible set intersection at position 3
 self.re = re.compile(self.reString)
INFO:smac_AutoML:update search space in SMAC.
INFO:smac_AutoML:SMAC call: python3 -m unittest test_builtin_tuners.BuiltinTunersTestCase.test_smac
Segmentation fault (core dumped)09/2020, 12:06:10 PM] WARNING (nni.protocol) IPC pipeline not exists, maybe you are importing tuner/assessor from trial code?
/home/fu-workstation/anaconda3/envs/tf23/lib/python3.8/site-packages/pyparsing.py:3190: FutureWarning: Possible set intersection at position 3
 self.re = re.compile(self.reString)
INFO:smac_AutoML:update search space in SMAC.
INFO:smac_AutoML:SMAC call: python3 -m unittest test_builtin_tuners.BuiltinTunersTestCase.test_smac
Segmentation fault (core dumped)

@AkshayRoyal , we reproduced your problem in a fedora docker container. We are checking whether we can make it work.

Hi @QuanluZhang, Is there any update regarding the issue?

I got the same error when I was using SMAC tuner.  Checked that SMAC was successfully installed and was using Ubuntu 20.04.

@AkshayRoyal @inspurwusixuan We found that this is due to the use of swig 4.0 in these Linux release versions, a temporary solution is to downgrade the swig version and reinstall pyrfr.
The following issue https://github.com/automl/SMAC3/issues/545 from the original SMAC3 repo may help you.


Fixed where argument coercion

Summary of the changes (Less than 80 chars)

Fixed where argument coercion.

Closes #5594

when is this expected to be released? or can we already get a pre-release version with this fix?

It's available in 14.0.0-p.119 and later releases.


onboarding: Backfill a month of messages for new users.

(instead of a week)
There are still caps like 1000 messages total and 20 unread, but we're a bit more flexible about time.

I chatted with @alya a bit about this and we settled on 3 months being reasonable, so changing this to that and then merging, thanks @showell!


Maintenance of fmri_connectivity module

Module to maintain
Website: https://school-brainhack.github.io/modules/fmri_connectivity/
Code: https://github.com/school-brainhack/school-brainhack.github.io/tree/main/content/en/modules/fmri_connectivity
Work to be done
Please ensure:

[ ] links, resources and exercises reflect the state-of-the-art
[ ] videos are of good quality and reflect the materials.

If any update / re-write of the module is needed, feel free to suggest alternative material in a comment!
If you think major changes are needed, we suggest you open an issue for new modules.

I am happy to look at this module

Hi @Davi1990, how are you getting on with maintenance of this module? Do you need any help? Just a reminder that we are hoping to have these done by April 21st

Hi @clarkenj thanks for reaching out. I have been working on the PR of the new dMRI and mne module. I am gonna finish this up asap

Hi @clarkenj I just finished to review the material. Overall everything looks good, video for me is good enough and Pierre have done a very good job explaining the framework.
I worked on updated the jupyter notebook and polish it a bit. I think it looks much better. I've just submitted a PR.
Please let me know
Dave


Implement best-practice Source documentation

See https://docs.google.com/document/d/1UKyjA0nfNyvDIiF86YEeskV5_pZ_kP07AoDHrDUq8Xo/edit#heading=h.los3tdhhh2fb for the general template, though I took a few liberties as I was actually writing it up.
Changes
Adds end-user documentation for the RabbitMQ Source.

📖  End user documentation
📖  Moved contributor documentation to DEVELOPMENT.md

/kind documentation
Release Note

Added user-facing documentation for the RabbitMQ source

Docs

Will update the sources docs to point to this page once merged.

/assign @abrennan89 @n3wscott @lionelvillard
/hold
Want to give a chance to review and see if this provides the documentation level we expect before submitting.

/assign @abrennan89 @n3wscott @lionelvillard
/hold
Want to give a chance to review and see if this provides the documentation level we expect before submitting.

Updated.
You can preview here:
https://github.com/evankanderson/eventing-rabbitmq/tree/gold-star/source

Updated.
You can preview here:
https://github.com/evankanderson/eventing-rabbitmq/tree/gold-star/source

I tried out a different arrangement here, but I think Ashleigh is also going to try out something more dramatic in the medium-term in parallel to this.
Feel free to approve this PR or #217 as preferred.
/hold cancel

I tried out a different arrangement here, but I think Ashleigh is also going to try out something more dramatic in the medium-term in parallel to this.
Feel free to approve this PR or #217 as preferred.
/hold cancel

We will have to add a linter to knobots that knows about asciidoc as this gains traction.

We will have to add a linter to knobots that knows about asciidoc as this gains traction.


Add changelog.md to .prettierignore

Is your feature request related to a problem? Please describe.
Our vtex setup --tooling command and templates should have a .prettierignore file which makes prettier ignore certain files. Since our CHANGELOG.md is made by hand, it can result in rebase conflicts if people have prettier re-formatting the file over and over again.
Describe the solution you'd like

Make vtex setup add a .prettierignore to a project.
Add changelog.md to .prettierignore.

Describe alternatives you've considered
Let people do whatever they please, which is not always the best idea.
Additional context
n/a

No chance to have a md format in this file case to just remove the black lines that cause the rebase issues? cc @lucasecdb

not stale

not staleee :sad-cat:


LOOP-2458 Fix slow status bar update

https://tidepool.atlassian.net/browse/LOOP-2458
Add modificationCounter/anchorKey indices to prevent slow data access
Move settings data decoding from data access queue into utility queue
Clearly return empty array when store query limit is <= 0

Build LW PR: https://github.com/tidepool-org/LoopWorkspace/pull/411

Build LW PR: https://github.com/tidepool-org/LoopWorkspace/pull/411

@ps2 Yes, anything that synchronously waits for read or write access to the dosing decisions or settings stores will block. This fixes that.


Ocasionally Commit & Push fails with "Actual command not found"

Type: Bug
Ocasionally I face the following error

Have pending changes
Click  Commit & Push
See error notification
Next attempt works without issues

Developer Tools
10:54:07.622 notificationsAlerts.ts:40 Error: Actual command not found, wanted to execute git.commit /30
    at r.h (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:153:189812)
c @ notificationsAlerts.ts:40

GIT Output
2024-05-07 10:54:04.887 [info] > git config --get commit.template [94ms]
2024-05-07 10:54:04.956 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/feature/<REDACTED> refs/remotes/feature/<REDACTED> [130ms]
2024-05-07 10:54:05.090 [info] > git status -z -uall [118ms]
2024-05-07 10:54:05.236 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/feature/<REDACTED> [114ms]
2024-05-07 10:54:05.380 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/feature/<REDACTED> [119ms]
2024-05-07 10:54:05.531 [info] > git config --local branch.feature/<REDACTED>.vscode-merge-base [94ms]
2024-05-07 10:54:05.531 [warning] git config failed: Failed to execute git
2024-05-07 10:54:05.647 [info] > git reflog refs/heads/feature/<REDACTED> --grep-reflog=branch: Created from *. [95ms]

VS Code version: Code 1.89.0 (b58957e67ee1e712cebf466b995adf4c5307b2bd, 2024-05-01T02:09:22.859Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-1270P (16 x 2496)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.67GB (11.14GB free)

Process Argv
--folder-uri file:///c%3A/sources/Repos/FLT --crash-reporter-id 0ed2dc76-86cb-4e82-89ae-a98b71ec0a3f

Screen Reader
no

VM
0%

Extensions (15)

Extension
Author (truncated)
Version

vscode-tailwindcss
bra
0.10.5

copilot
Git
1.187.0

copilot-chat
Git
0.15.0

vscode-github-actions
git
0.26.2

rainbow-csv
mec
3.11.0

vscode-docker
ms-
1.29.1

vscode-dotnet-runtime
ms-
2.0.3

vscode-edge-devtools
ms-
2.1.5

data-workspace-vscode
ms-
0.5.0

mssql
ms-
1.22.1

sql-bindings-vscode
ms-
0.4.0

sql-database-projects-vscode
ms-
1.4.1

live-server
ms-
0.4.13

powershell
ms-
2024.2.1

vscode-thunder-client
ran
2.22.1

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
showvideot:31016892
chatpanelc:31018788
dsvsc021:30996838
724cj586:31013169
pythoncenvpt:31022790
fchga941:31038042
dwnewjupytercf:31035177

I experienced this error today. I was unable to commit with VSCode, but when I opened the repository with another git manager (I used GitExternsions), I was able to commit the changes which were generating the Actual command not found error in VSCode described above, presumably the CLI or another app would have also worked. After the successful commit with GitExtensions, committing within VSCode once again worked as expected.


Strange Behavior in Terminal/command window

Issue Type: Bug
Description:
When a terminal window is opened, there's no cursor next to the prompt.  Start to type and the prompt disappears and the typed command appears ... still no cursor.
Expected behavior:
Cursor should appear next to the prompt and typed commands should appear at the cursor.
Steps:
user: open VS Code
user: open a project
user: open a terminal window (ctrl+` )
system: opens terminal window
system prompt appears
there is no cursor
user: start to type a command
system: prompt disappears
typed letters appear
still no cursor
user: finish typing command and press Enter
system: starts to execute the command
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz (8 x 3392)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_offsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.98GB (3.20GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (2)

Extension
Author (truncated)
Version

tslint
eg2
1.0.43

debugger-for-chrome
msj
4.11.3

This is a bug in Windows 10 1809, unfortunately we have no way to work around the issue so you will need to wait until you get the next version of Windows 10 (1903).
/duplicate https://github.com/Microsoft/vscode/issues/57803


On IGN youtube-dl directly on the .mp4 file does not work

When doing :
youtube-dl http://assets3.ign.com/videos/zencoder/2016/03/02/960/7d9b7ef1402046631b6e954a1a004d9c-1500000-1456932076.mp4 --verbose
The script seems to remain blocked on : 'Downloading webpage'
but using the webpage where is the video, works fine:
youtube-dl http://www.ign.com/videos/2016/03/02/hitman-official-season-premiere-trailer
Here is the following output with verbose for:
youtube-dl http://assets3.ign.com/videos/zencoder/2016/03/02/960/7d9b7ef1402046631b6e954a1a004d9c-1500000-1456932076.mp4 --verbose :
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'http://assets3.ign.com/videos/zencoder/2016/03/02/960/7d9b7ef1402046631b6e954a1a004d9c-1500000-1456932076.mp4', u'--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.03.18
[debug] Git HEAD: 0a9c4ec
[debug] Python version 2.7.10 - Darwin-15.0.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 2.8.6, ffprobe 2.8.6, rtmpdump 2.4
[debug] Proxy map: {}
[ign.com] 7d9b7ef1402046631b6e954a1a004d9c-1500000-1456932076.mp4: Downloading webpage

I believe it's not stuck. It may be downloading the actual video, which is 24 MB in size. It will probably try to interpret it as a webpage which to extract a video URL from. That will probably fail. In any case, if you have the final video URL, why use youtube-dl at all? curl or wget work fine.

Actually the behavior was the same with the 'skip download' flag. But it seems to work now, may be it was due to the network on which I was. Well, thanks, I close the issue.


toggle terminal has wrong behavior when words are selected by user

OS/Web Information

Web Browser: Chrome
Local OS: Windows10 (10.0.18363 N/A build 18363)
Remote OS: Ubuntu18.04
Remote Architecture: x64
code-server --version: 3.9.2 109d2ce3247869eaeab67aa7e5423503ec9eb859

Steps to Reproduce

first of all, setup this shortcut:

  {
    "key": "ctrl+`",
    "command":"workbench.action.terminal.toggleTerminal"
  },

open a file and input random text
select any word (or words)
press "ctrl+`"

(this bug only happens when it has selected words)
e.g.

Expected

toggle code-server ingergrated terminal and when open, the terminal should be focused.
Actual

always focus on text editor while there are words selected by user, nothing happened.
Screenshot

Notes

This issue can be reproduced in VS Code: Yes/No No

I was able to reproduce in 3.9.3 using code-server locally in Chrome. I even tried changing the when  clause for the shortcut, but that didn't fix it.
code-server
https://user-images.githubusercontent.com/3806031/115756346-f8198580-a352-11eb-9561-b8e6bc9df19e.mov
Codespaces
I was able to reproduce in Codespaces which means it's an upstream issue.
Nice job finding this bug!
https://user-images.githubusercontent.com/3806031/115758695-4418fa00-a354-11eb-87a0-42a5db454fdf.mov


⚠ api.piste.gouv.fr healthcheck has degraded performance

In cfa2dab, api.piste.gouv.fr healthcheck (https://api.piste.gouv.fr/cassation/judilibre/v1.0/healthcheck) experienced degraded performance:

HTTP code: 200
Response time: 2883 ms

Resolved: api.piste.gouv.fr healthcheck performance has improved in 0083336.


AMS v3 AES Encryption support timeline

Is there plan to support AES 256 encryption in AMS v3? If so, can you share when it'll be available?

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

ID: d0e62a40-3aaf-82ea-2bbe-81894c7e7728
Version Independent ID: 28422148-8483-572b-5d4f-1064970d408d
Content: Encrypting your content with storage encryption using AMS REST API
Content Source: articles/media-services/previous/media-services-rest-storage-encryption.md
Service: media-services
Sub-service: rest-v2
GitHub Login: @Juliako
Microsoft Alias: juliako

@farooqkh  Thanks for the question! We are investigating and will update you shortly.

Hi @farooqkh AES-256 is not planned for V3 SDK. It was available in V2 because at the time, Azure Storage did not handle server side encryption at rest like it does now. For this reason, V3 offers backwards compatibility for assets that were encrypted client side before Azure Storage offered this behavior default. Should you still like the idea of client side encryption, the team is looking for feedback for supplying the encryption key in the request headers.
We'll update the doc so that it better reflects the general purpose that AES-256 encryption is now handled server side. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Swift Compiler Error (Xcode): Type 'UIApplication' does not conform to protocol 'TikTokURLOpener'

This error appears inside the generated 'TikTokURLOpener'. By replacing the function open(...) with
func open(_ url: URL, options: [UIApplication.OpenExternalURLOptionsKey : Any], completionHandler completion: (@MainActor @Sendable (Bool) -> Void)?)
in the generated class the problem gets fixed for me. That's a very dirty solution I know! But since I am not a Swift developer I have no clue how to fix it properly, so that the class will be generated correctly. Would be lovely if someone can fix this who is more experienced in Swift than me🪲

+1

+1

I have the same problem any updates?


Cannot manually add images to TV show episodes

The drag and drop area doesn't seam to appear when editing an episode

This is not high on my todo list, because this only applies to non-api episodes, but I'd accept a pull request on this issue!


Handle certificate-authority in kube config

Kube configs supports certificate-authority-data, which kr8s handles, and certificate-authority, which is just a path to a cert file, and kr8s doesn't handle. This PR adds support for that. This unblocks our ability to use dask-kubernetes locally.
Closes: https://github.com/kr8s-org/kr8s/issues/175

Thanks for bearing with me through the reviews!

Thanks for bearing with me through the reviews!

My pleasure! That kind of feedback is my favorite thing about OSS contribution. Thanks for the merge!

Sure that would be great. I've just released v0.8.19. Now that things are more stable we can probably drop the hard pinning and go for >=0.8.19


set mellanox reg key

Reason for Change:

Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Notes:

Does mellanox driver require reboot? I agree with @rbtr that we probably shouldn't be setting this in CNS, but if it requires a reboot then we definitely cannot set this with CNS.

This seems like underlying infra config, and I'm not sure it should be CNS's job to configure prerequisites like this. Shouldn't this responsibility lie with the orchestrator which expects to use CNS/CNI?

This script/code to set PriorityVLANTag already been added to Atlas code (https://msazure.visualstudio.com/One/_git/SF-SeaBreeze?path=%2Fsrc%2Fscripts%2FAtlasVMSetup.20220112.ps1&_a=contents&version=GBmain) but it seems it gets executed at starting of cluster but eventually value get reset so we want to make it part of CNS to make sure mellanox adapter's value is always set

Does mellanox driver require reboot? I agree with @rbtr that we probably shouldn't be setting this in CNS, but if it requires a reboot then we definitely cannot set this with CNS.

yes for version 3 it requires reboot. Let me confirm with Paul again. May I know why we cannot execute this in CNS if it requires reboot. Just curious.

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree [company="Microsoft"]

@microsoft-github-policy-service agree company="Microsoft"

@microsoft-github-policy-service agree company="Microsoft"

This seems like underlying infra config, and I'm not sure it should be CNS's job to configure prerequisites like this. Shouldn't this responsibility lie with the orchestrator which expects to use CNS/CNI?

That's a great point, we have tried this, but the setting gets un-set eventually, either due to live migration of the node underneath the VM, or otherwise, so we can't rely on it being set once and done, we'll have to keep setting it in CNS to make sure

And VM hosting team is unwilling / unable to set it to the values we need by default across Azure
Vivek Bhanu is his name

Does mellanox driver require reboot? I agree with @rbtr that we probably shouldn't be setting this in CNS, but if it requires a reboot then we definitely cannot set this with CNS.

A reboot of the network adapter is needed on one older version Mellanox x3
The VM does not need to be rebooted

Hi @ashvindeodhar , I was thinking to put the setmellanoxadapter function call into the CreateorUpdateNetworkContainer
Reason being, we would hit the same issue here, of live migration (or any other reason that the priorityvlantag gets reset by something out of our stack), failing the datapath
If we set the mellanox adapter each time, then there's a chance when the priorityvlantag is reset by some live-migration or anything else, createNC call would fix it right away, instead of restarting CNS

Hi @ashvindeodhar , I was thinking to put the setmellanoxadapter function call into the CreateorUpdateNetworkContainer Reason being, we would hit the same issue here, of live migration (or any other reason that the priorityvlantag gets reset by something out of our stack), failing the datapath
If we set the mellanox adapter each time, then there's a chance when the priorityvlantag is reset by some live-migration or anything else, createNC call would fix it right away, instead of restarting CNS

@pjohnst5 yes this is why I had added the sdn arp mac reg key at the time of getNC call to CNS. https://github.com/Azure/azure-container-networking/commit/a1f804a912f0f1975fd82a574f74d7afbae1fc83 @tamilmani1989 any idea why that was moved to main func in CNS?

Does setting this registry key affect singletenancy scenarios? I see its set for all scenarios.

The downside of setting this in CNI and not by orchestrator bootup script is that if in future something changes like registry value changes for different version of Mellanox, then we have to deal with supporting all versions based on what used.

Hi @ashvindeodhar , I was thinking to put the setmellanoxadapter function call into the CreateorUpdateNetworkContainer Reason being, we would hit the same issue here, of live migration (or any other reason that the priorityvlantag gets reset by something out of our stack), failing the datapath
If we set the mellanox adapter each time, then there's a chance when the priorityvlantag is reset by some live-migration or anything else, createNC call would fix it right away, instead of restarting CNS

@pjohnst5 yes this is why I had added the sdn arp mac reg key at the time of getNC call to CNS. a1f804a @tamilmani1989 any idea why that was moved to main func in CNS?

putting in createorupdatenc indirectly dependent on CNI to execute sequentially. Now that we removed lock acquiring at beginning of cni process, it can execute parallel which may call setting registry key multiple times which leads to hns restarts multiple times

I remain opposed to this kind of underlying infrastructure configuration being CNS's responsibility at all.
However, if it were, it must be in a startup/preflight and guaranteed to only execute once per process. If the config becomes unset such that we can't do our job anymore, we should crash out so that it is reset during reinitialization.

This seems like underlying infra config, and I'm not sure it should be CNS's job to configure prerequisites like this. Shouldn't this responsibility lie with the orchestrator which expects to use CNS/CNI?

That's a great point, we have tried this, but the setting gets un-set eventually, either due to live migration of the node underneath the VM, or otherwise, so we can't rely on it being set once and done, we'll have to keep setting it in CNS to make sure

That some registry flags get unset during a live migration kinda sounds like a bug with live migration, no? And if something else is randomly resetting the value, we need to understand who and why and ask them to stop, maybe? Otherwise we just fight over the reg key.

Rajvi is following up with Vivek Bhanu and Michael Nanakul as to why the registry key is reset in the first place

@rajvinar are you not a member of our GitHub team? You will need to join that so that the workflows will run.

@rajvinar are you not a member of our GitHub team? You will need to join that so that the workflows will run.

ohh let me do that.. thanks for info

I think this looks good, will wait for Ramiro to sign off on it as well before giving an official approval

Yeah so I confirmed with @thatmattlong offline that AKS doesn't use multitenant windows scenarios, so they don't need this change
So the only confirmed place we need this is if config.ChannelMode == cns.Direct, I think we should add that 'if'


Run SHA-256 test vectors on circuit

For #880
Attempting to run the SHA-256 test vectors on the circuit. Two problems I'd like help on (@blaxill ?):

I can't figure out how long the circuit is expected to run; test1 ("abc", 1 block, 3 bytes) takes 64*1+17 cycles, but test2 (2 blocks, 14 bytes) takes 64*2+21. For bigger tests I can't tell, because...
When I try to run test3, the circuit doesn't ever switch the "done" flag to 1, even when run for 500 cycles, and as far as I can tell doesn't ever get to the correct answer. I also tried running a 4-block test (the 4-byte word derived from "abcd" repeated 48 times) with the same result; it didn't ever seem to finish the computation.

I am marking this "ready for review" because it will be affected by the reorganization discussed in #893 and the failing test is currently commented out, so it's probably easiest to just merge it now and then uncomment the test once the bug is fixed. Also, fixing the bug might be easier on top of this PR!


Space not needed for Network Share

[In the location of the network share there is a space between file:// and the share that doesn't need to be there.

]

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

ID: e59013ef-aae3-ee84-8bc3-8d2ad0c52e36
Version Independent ID: f4e73402-3baf-a72b-96c5-cee4f04b8298
Content: Configure IE mode Policies
Content Source: edgeenterprise/edge-ie-mode-policies.md
Product: microsoft-edge
GitHub Login: @AndreaLBarr
Microsoft Alias: collw

@woodsonf Thanks for the feedback!  The documentation has been updated to remove the extra space.


zero升级到最新版本，etcd注册出现问题

我etcd对外暴露 49175,49178,49179端口
启动项目出现如下错误
{"level":"warn","ts":"2021-07-02T15:11:12.531+0800","logger":"etcd-client","caller":"v3@v3.5.0/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00034c000/#initially=[<IP_ADDRESS>:49175;<IP_ADDRESS>:49178;<IP_ADDRESS>:49179]","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:2379: connectex: No connection could be made because the target machine actively refused it.""}

问一下问题是怎么解决的

同问


Remove temp state because uc_upgrade now works on Studio without tempstate

JIRA: ZAPP-1362

Ive been testing this and it appears to be working well. Leaning towards approving but am going to run through some more use cases to make sure.

Paul was not wrong we need to test this well, but in general it's a right thing.

I have tested this for matter and zigbee apps. Went through the matter application upgrade process with Michael Rupp from the matter team as well showing how it passes now.

@tecimovic @brdandu
we need testing for this change or else any change after is a risk, right?


Fix #3763: Docs - include the topic field in the address example with…

Type of change

Documentation

Description
Minimal improvement to the documentation to cover the use of the topic: field in the address resource.
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@jenmalloy @lulf I pulled out a separate example for topic/subscription.  How does this look?

LGTM, but does the tooling allow for these includes to be used @jenmalloy or do the examples have to be inline in the doc for it to work?

My intent was to follow the existing practice with regards to file inclusions etc so there should be no new demands on the tooling.  Did I make a mistake?

@k-wall I can't remember fully, but iirc we started move includes inline for some reason it was easier to keep in sync for @jenmalloy . I'm fine with using includes if it works though.

@k-wall @lulf seems like the includes are ok, so reapproving. Thanks for the discussion!


UPDATE statements with string literal from of the same column fails

Describe the bug
When issuing a pretty simple update against a table, we get a syntax error, but it should work.
Error message/log
ERROR:  Failed to run the query

Caused by:
  sql parser error: Expected =, found: version at line:1, column:23
Near "update foo set"

To Reproduce
create table foo as (select 'abc' as version);

update foo set version = 'def' where version = 'abc';

Expected behavior
I'd expect the correct row in the table to be updated
How did you deploy RisingWave?
Docker compose (locally)
The version of RisingWave

risingwave_development=> select version();
                                       version
-------------------------------------------------------------------------------------
 PostgreSQL 13.14.0-RisingWave-1.9.1-rc.1 (2f44407cfa3430d1d31ce9a0d0fcb31547408d8b)
(1 row)

Additional context
No response

Thanks for your feedback!
create table foo as (select 'abc' as "version");

update foo set "version" = 'def' where "version" = 'abc';

It is because our sql tokenizer handles 'version' as a reserved word instead of an identifier.
A quick workaround is to use "" wrapping up the name to prevent ambiguity.
However, this indeed causes some inconvenience and we'll need to fix this ultimately.


Documentation for Anchors

Create user-facing docs on how to create/modify/delete anchors via the UI and API

Just noting for the UI we should add a new 'Anchors' section under the Planning section here: https://nasa-ammos.github.io/aerie-docs/category/planning/
Similarly for the API we should add a new 'Anchors' section under the Planning section here: https://nasa-ammos.github.io/aerie-docs/api/examples/planning/introduction/


Add Habbo to sites

Unfortunately, the URL is different for every region

Aside from the minor JSON issue (trailing comma in the domains array), this PR looks good. I'm hoping to push a major update to the site's backend shortly which would eliminate the need to run gulp to build the changes into HTML files, so I'm holding off merging this right away. If it looks like that will take more time than expected, I'll merge the PR first.


Module not found: Error: Can't resolve 'react-dom/client' in '~/Chrome Extensions/my-app/node_modules/react-konva-utils/es'

This is the error I got after upgrading konva:
ERROR in ./node_modules/react-konva-utils/es/html.js 13:0-40
Module not found: Error: Can't resolve 'react-dom/client' in '~/Chrome Extensions/my-app/node_modules/react-konva-utils/es'
 @ ./node_modules/react-konva-utils/es/index.js 1:0-30 1:0-30
 @ ./src/components/ui/BackgroundBlur.tsx 14:0-50 26:32-36
 @ ./src/components/ui/index.ts 7:0-64 8:0-84
 @ ./src/components/SiteImage.tsx 7:0-55 58:28-42
 @ ./src/components/index.ts 21:0-51 21:0-51
 @ ./src/App.tsx 7:0-67 21:68-81 23:32-37 24:32-39
 @ ./src/popup.tsx 3:0-24 7:36-39

before upgrading
"konva": "^8.3.5",
"react-konva": "^17.0.2-5",
"react-konva-utils": "^0.2.0",

after upgrading
"konva": "^8.3.10",
"react-konva": "^18.2.1",
"react-konva-utils": "^0.3.0",

I was importing Html like:
import { Html } from 'react-konva-utils'

but it gave error so I started importing like:
import { Html } from 'react-konva-utils/es/index'

It still gives the same error.
Even es/html doesn't work & gives some weird mumbo-jumbo.
What's the issue?

The last version of react-konva-utils work only with react version 18.
You may keep using previous version of the library with react version 17.


How to use Watcher / WatcherClient over tcp/ip network? (ex. cloud - local)

How to use Watcher / WatcherClient over tcp/ip network?
Watcher seems to ZMQ server, and WatcherClient is ZMQ Client, but there is no API/Interface to config server IP address.
Do I need to implement a class that inherits from WatcherClient?

We are currently exposing port in constructor but you are absolutely correct that we need to have IP address as well. This is almost trivial change and we will add very soon!

I’m just curious whether ssh port tunneling from a remote server to the local host would work in this case??
This would be a workaround at this moment until TCP/IP support is made, but not sure whether ZMQ is compatible with port forwarding. Any idea?


Improve documentation on how to write an EF Core provider

Currently we have something very brief at https://docs.microsoft.com/ef/core/providers/writing-a-provider pointing to @ajcvickers's blog.
It would be good to update this to cover:

Support for EF Core 2.1 features
The mechanics of setting up spec tests (e.g. https://github.com/dotnet/efcore/issues/27107#issuecomment-1004923695)
The mechanics of adding provider specific extension methods

Whether this should be in a blog post or if it needs to be part of the documentation is something we can discuss, but I would be inclined to have it in the actual documentation.

I'd like to express my preference for including the guide on how to create one's own EF Core database provider in the documentation as well. It's way more authoritative than a blog post. I'm just trying to figure out going by the old version of the docs, can you provide a rundown of the changes or a super rough estimate for when 3.1.0 might land?

I'd like to write a scaffolding only provider around edmx files in order to fill the gap for all of us having existing edmx files that we want to keep around in order to create entities and DbContexts.
Any information that could allow me to start would be very much appreciated.

Suggestion from @ErikEJ on https://github.com/dotnet/efcore/issues/20793#issuecomment-621943308

It would lower the barrier to have a "template/null" provider to use as a starting point. But of course it can quickly become stale.

Ideally this would be built as part of CI, to keep it in at least minimal sync with EF...

@roji do you think there would be any value in this?

Yeah, I think it would... Our docs repo has a set of samples - which now even get built in CI - so it could live there. On the other hand, if we put it in the normal repo it would naturally evolve as we change EF Core...

I think it is better to fix it to depend on a released version of EF Core, and then just update on new release (if needed at all)

Releases to consider

LTS release
Current release (stable)
Current preview

I think current preview would provide slightly lesser value. If I am writing a provider from scratch, I would want to depend on stable release so I can build my provider and release it. It would be easy after 3.1 to move to next major release for providers even with breaking changes. The issue with targeting previews would be constantly moving target. If EF Core added some API in one preview but changed it in another preview (we love API reviews), then provider has unnecessary effort to keep changing things when writing the core provider at the same time.

@smitpatel exactly my experience/pain during EF 7 previews

I think we should be much more stable now than we used to be - but I agree that there's not that much value to a provider template that tracks previews. So maybe just tracking the current stable release is enough (an additional one for LTS seems to be a bit overkill)? If so, then just putting it in our doc repo under samples should be good...
On another note, I assume we're discussing about a relational provider template - or do we think that a non-relational sample is valuable as well?
Are you interested in doing this @ErikEJ?

@roji yes, the relational. I could just base it on something similar to the initial commit I mentioned above. A no-name ANSI SQL provider...

If we put it in the main repo, then it would evolve along with the other providers and there will still always be a branch/tag to get the snapshot of the provider that aligns with a given release.

Good point, but should the initial commit not target 3.1?

Yeah, that would be ideal.

@ajcvickers the point made above is that the main value of this is for the latest stable release, since that's what provider writers are likely to target. If that is so, then the template would depend on the latest released version and not on the latest code in master... and we'd evolve it for every release manually, a bit like how we're supposed to do for the doc samples.

The repo to host is less important. The sample should use package references rather than project references.

@smitpatel good point - just let me know which repo you prefer 😊

If we agree to use package references, I'd vote for putting it in the docs repo. It really is a sample, and has no value being in the main repo.

@ErikEJ We discussed this and we're thinking that we could try this out on https://github.com/efcore first to see what it looks like and how it evolves. We could potentially move it somewhere else later.

Yes, I will discuss details in the newly created repo there...

Are there any plans to have the docs updated for EFCore5?
The blog it points to is for EFCore1.1! Is the doc still valid? I cannot find DatabaseProviderServices?
I searched in the linked example providers such as SQL Server, npsql, etc but could not find DatabaseProviderServices or RelationalDatabaseProviderServices anywhere in them...
Any ideas? I really need to write a provider but haven't a clue how to or where to start?
Any help would be really appreciated.
Many thanks,
David.

@dellams we're indeed lacking good documentation on how to write a provider... Assuming you're looking to develop a provider for a relational database, it's recommended you start with the Npgsql or Pomelo MySQL providers, as these are external projects that aren't part of the EF Core repo. Where relevant, the other providers (Sqlite, SQL Server) can also be consulted.
Start by looking at the different services implemented by these providers, and getting familiar with the general architecture of EF Core. We can then help out with any specific questions.

Yes, thank you, I have already checked them out and was surprised with just how much work and how complex it was to write a provider. I was hoping you could provide a simple bare bones template with the minimum needed to implement a provider?
Do you know when some up to date documentation will be created for this?
What I am trying to do is something a bit more special than just a relational provider, I am attempting to integrate EFCore into the OASIS API I have been building, which integrates all blockchains, holochain, cloud, db's, networks, platforms, APIs, etc.
I would love to get some support with this very valuable project, I feel once people understood what I am building a LOT would come and help me build it! :)
https://github.com/NextGenSoftwareUK/Our-World-OASIS-API-HoloNET-HoloUnity-And-.NET-HDK
It would be super cool and powerful to have this abstraction API using EFCore making it super easy to bridge everything to everything through one simple ORM (I love EF and have worked with it many years being a big fan of .NET since its initial release many years ago just after I graduated from University in 2002.) :)
I have worked as a IT consultant/contractor in London building commercial .NET applications of all sizes in all markets, etc so have experience of most of the amazing .NET stack since I have grown as a developer along with .NET... you could say we grew up together! ;-)
BIG FAN! :) Keep up the great work, so happy it is Open Source now and cross platform,... very excited and passionate to help grow the .NET ecosystem with you guys...
I hope to get on the .NET Foundation soon... is that something you guys could help with? When you all understand the wonders I plan to do for the .NET community I think you would want to help me help you... ;-)
Many thanks,
David.

@dellams you may find the series of commits in the develop branch here useful: https://github.com/GibraltarSoftware/VistaDB.EFCore

Great thank you. Is this an example of the steps bones minimum needed? 🙂

It depends...

@dellams sounds like you're describing F# Type Providers

One of the providers that is stalled out is FileContextCore.  The fact that there are so many breaking changes between major versions means that ongoing maintenance of providers is very labor intensive especially when there is no documentation.

I have a need to create many EF Core providers and decided to create a template repo for this purpose.  It is still a work in progress (i.e. need to get passing unit tests going), but am wondering if this repo would be something that the community would be interested in?  And also if it might go a ways toward solving this open issue?
The readme describes the concept of this sample provider.

@DaveRMaltby I do think we skeleton/template provider is a good thing to have, as a starting point for people writing providers.
Some specific points come to mind when looking at your repo; in particular, many services are being overridden that would only be needed in relatively advanced scenarios (e.g. SqlExpressionFactory only for custom SQL expressions, QueryTranslationPostprocessorFactory only for certain advanced scenarios, etc.). I'd advise going with a more minimum approach, implementing only services which a typical provider would have to override, rather than everything.

@DaveRMaltby I do think we skeleton/template provider is a good thing to have, as a starting point for people writing providers.
Some specific points come to mind when looking at your repo; in particular, many services are being overridden that would only be needed in relatively advanced scenarios (e.g. SqlExpressionFactory only for custom SQL expressions, QueryTranslationPostprocessorFactory only for certain advanced scenarios, etc.). I'd advise going with a more minimum approach, implementing only services which a typical provider would have to override, rather than everything.

@roji, thank you for the feedback.  Yes, your advice points to the issue that I'm struggling with and I'm sure others who have no idea about the nature of the services offered here.  I just used the Npgsql, Pomelo MySQL and  SQLite providers as a basis to copy from for this template repo without understanding their purposes.  I was trying to get at least one of the tests in EFCore.Relational.Specification.Tests to pass.  So far, I have been unsucessful in that endevour and it has been overwhelming as just simply adding the EFCore.SampleProvider.FunctionalTests.Query tests amounts to 443 tests.
Anyhow, I believe now that I need to take a completely different approach.    I've now stepped back and am going to take one of the many EF Core providers that I plan to write and create a few unit tests based off of the examples in Getting Started with EF Core.  Getting those CRUD tests to pass will give me the understanding and basis for the bare minimum services that are needed.  Later, I will add more advanced features to this provider as needed (eventually, adding the migrations/scaffolding that I also need).  Ultimately, I'll try to circle around and update the SampleProvider to provide a skeleton/template for others to make use. (And also I hope to provide descriptions about the services as well)
Can you possibly provide a quick list of services that you know are required just to achieve the first step mentioned above of getting simple CRUD unit tests to pass?  Thank you.

@DaveRMaltby Maybe some of the initial commits here could help? https://github.com/GibraltarSoftware/VistaDB.EFCore/compare/main...develop

@DaveRMaltby it's unfortunate that we don't have better docs for provider writers - it really is something we want to improve, but tends to be de-prioritized in favor of user-facing features. However, we're here to help you out with any questions - please don't hesitate to ask.

@DaveRMaltby it's unfortunate that we don't have better docs for provider writers - it really is something we want to improve, but tends to be de-prioritized in favor of user-facing features. However, we're here to help you out with any questions - please don't hesitate to ask.

@ErikEJ and @roji, other priorities took me away from this topic.  I'm trying to focus again here on providing a useful template repo for the community.  I don't like the direction that I was initially going there.  I'm now thinking that such a template repo should just be able to take any full fledged ADO.NET data provider (that supports .NET Core, of course) as it basis without needing much else.  Is this a naive statement?  I will likely try to go in this direction, as it may allow most of the specific database logic for anyone who needs to create an EF Core provider to be placed in their own ADO.NET data provider and then use this template repo to get most of the way there quickly.

You could also take a look at FileBaseContext which is probably one of the simpler providers out there.  Maybe @dualbios can provide some tips on creating a provider from scratch.
There's also preliminary work being done on a provider for LiteDB at https://github.com/mbdavid/LiteDB/issues/1198 which might be of interest.

@DaveRMaltby I'm not quite sure what you mean with "may allow most of the specific database logic for anyone who needs to create an EF Core provider to be placed in their own ADO.NET data provider and then use this template repo to get most of the way there very quickly"; there's typically various database-specific logic that has to go into each EF provider, which does not belong in the lower-level ADO.NET provider (e.g. how to produce various SQL constructs). The idea of "general ADO.NET-compatible EF provider" which would somehow just work with any ADO.NET provider simply doesn't work.
I think the main value in a template here would be to have a minimal provider sample which implements the services that must be overridden (or would typically be overridden for most providers). This would only provide a starting point for new providers, or for understanding how a provider looks like.
Note also that a minimal relational (ADO.NET-based) EF provider looks very different from a non-relational provider; for example, a relational EF provider typically needs to have its version of QuerySqlGenerator, which non-relational provider obviously don't need. I agree it's worth concentrating on a relational template; non-relational providers in general can be extremely different based on the database being targeted, and there's not likely to be a lot of commonality there.

@roji and @ErikEJ, I didn't forget about this.  I have finally completed what I was referring to above.  I have taken and built a custom EF Core provider that depends on a SQLite ADO.NET provider.  Of course, I knew that there would be some custom code that is unique to support the SQLite provider, but it doesn't seem that much as you can see in MyCustom EF Core provider repo.
See what yáll think.  Look at the README for this repo.  I've tried to logically break up what is needed into 4 steps.  The basic unit tests are passing for me.
Note:  It builds against EF Core 6.x, but I only did that because currently my product is using that version.  If/when you want to add this into an EF Core repo, of course we'll rev it up to the latest version.
Anyhow, let me know if you want more of my involvement here.  For my company's use, I have 4 providers to implement and will be working on those efforts, unless you need something further here.  Thanks for the guidance!

So is it a correct statement that the critical part is working outwards from the ...ServiceCollectionExtensions classes' "IServiceCollection AddEntityFramework..." section, and create your versions of those classes listed there as needed? And that InMemoryServiceCollectionExtensions.cs or CosmosServiceCollectionExtensions.cs is the version probably close to the minimum needed to implement?

So is it a correct statement that the critical part is working outwards from the ...ServiceCollectionExtensions classes' "IServiceCollection AddEntityFramework..." section, and create your versions of those classes listed there as needed? And that InMemoryServiceCollectionExtensions.cs or CosmosServiceCollectionExtensions.cs is the version probably close to the minimum needed to implement?

Honestly, I'm still not an expert and got a lot of guidance from ChatGPT.  I asked it to indicate the minimal classes required.  Anyhow, the ServiceCollectionExtensions class does register your provider services that the Entity Framework will use via DI for itself.   It is only your DbContext derived classes (BloggingContext in my unit tests) that end up kicking off the framework to do things using your provider registered services.  Anyhow, this was the minimal classes that I found was need to get the GettingStartedTests running with the SQLite in-memory ADO.NET provider.  Note:  This hasn't been reviewed by @roji and @ErikEJ as far as know, so this example may be missing things.


Removing noise model check in Simulator initialization

Addresses issue #4170 by removing NOISE_MODEL_LIKE check in sparse_simulator.py and updates tests accordingly.

@googlebot I signed it!


bake exercises in organic chemistry

Issue: https://github.com/openstax/cnx-recipes/issues/4749

Will be resolved within https://github.com/openstax/cookbook/pull/100. I'm closing this PR.


GH-33 Allows package to build for iOS

This does not solve the entire problem for #33, but is a good first step. Specifically, it allows example to build for iOS.
Known issues:

iOS simulator does not open QR scan process

Second commit addresses the issue described in #31.

Missing:
For iOS:
<key>NSCameraUsageDescription</key>
<string>Camera permission is required for barcode scanning.</string>

See: https://pub.dev/packages/barcode_scan


[Q]SOURCE compile - luarocks version

according to..
https://docs.konghq.com/install/source/?_ga=2.21260667.1520554348.1549842280-884864243.1549842280
Why should I use luarocks 2.4.3? any reason???
I compiled kong with luarocks 3.4.0
It also good work.
sorry for poor english.

Hello @hellower,
Kong works well with LuaRocks 2 and 3. As you've seen yourself, there shouldn't have any problems with using LR3.


Java.Lang.NoClassDefFoundError

Getting the following error when running the android build -
Java.Lang.NoClassDefFoundError: 'Failed resolution of: Lcom/google/android/gms/common/internal/zzbp;'
And this is from the logs -
11-08 11:09:06.309 E/AndroidRuntime(16071): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.common.internal.zzbp" on path: DexPathList[[zip file "/data/app/uk.gov.cardiff.CardiffGov.Android-Me5H2YwmgUAAxym26dJW2w==/base.apk"],nativeLibraryDirectories=[/data/app/uk.gov.cardiff.CardiffGov.Android-Me5H2YwmgUAAxym26dJW2w==/lib/arm64, /data/app/uk.gov.cardiff.CardiffGov.Android-Me5H2YwmgUAAxym26dJW2w==/base.apk!/lib/arm64-v8a, /system/lib64, /system/product/lib64]]

This doesn't seem to be related to the plugin

@rdelrosario  Pretty sure it is, all i done was add the plugin.
Was building and running fine before hand.
When i have time i'll create a test project and see if i get the same result

Try latest version just published a new one.
On Fri, Jan 10, 2020, 10:15 AM Ieuan Walker<EMAIL_ADDRESS>wrote:

@rdelrosario https://github.com/rdelrosario Pretty sure it is, all i
done was add the plugin.
Was building and running fine before hand.
When i have time i'll create a test project and see if i get the same
result
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CrossGeeks/AzurePushNotificationPlugin/issues/31?email_source=notifications&email_token=AATOAJYCUBDQFDVTBUA53TTQ5B7J3A5CNFSM4JKV6JR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIUBJWA#issuecomment-573052120,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATOAJ2H2PIUGEZJQAKXTSDQ5B7J3ANCNFSM4JKV6JRQ
.


Better value printing

For debugging I've enabled logging and I end up with something like this from my PostgreSQL query

SELECT * FROM "v_orders" WHERE ("v_orders"."month" = $1) ORDER BY "v_orders"."due" DESC ["TIMESTAMP (binary) \0\u{02}\u{11}(÷_@\0)"]

That's not very usable as I have no idea what got passed to the month parameter.  Is there some way to enhance this so that it prints out the human readable value?

This is specific to each driver (they determine the description string). DatabaseKit just prints it. Please open on the respective repo, thanks!


Update vhost crate + fix test compilation

Use the vhost crate, from the branch that is going to be merged upstream.
This PR also fixes tests not compiling due to different vm-memory version.

LGTM


Fixing the design of login page.

Description
The login and registration page has a design issue where Resume Builder is not visible.
Please assign me this issue under GSSOC'23.
Screenshots

Additional information
No response

Please assign this project to me. i will fix the issue

Issue has been resolved !


FEATURE: Validations and Styles

Both client and server side validations have applied with FluentValidation and jQuery Unobstructive. Bootstrap navbar menu created with Hamburger visual.

Please, attach screenshots of your result with hamburger menu. And I still insist on using this template for PRs.

Hambuger-Menu1
Hambuger-Menu2


Hyperion docker add amd64 support?

I've recently moved from a Pi4 to a NUC and would love to use your docker on amd64.
I've added the repository and the log file acknowledged the new git as expected:
21-12-12 18:56:47 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/bradsjm/hassio-addons repository
But the Hyperion add-on does not show up for selection at the bottom of the Add-on Store as expected.

As a NUC user I would be interested as well.


fixes to beginner guide

Validation Status: Successful
JobID: 2c742ba3-4a83-478b-adce-cb39914dc28b

Articles to review
The articles impacted by this PR were staged review at:

http://taco.visualstudio.com/en-us/docs/get-started-first-mobile-app/

I added tweaks to a huge pull request that came in from a Marketing Vendor.
The pull request had some great material in it, but I made a number of tweaks to stay consistent with our governing mission to reduce friction and complexity and to get folks as successful as possible.
I cleaned up a lot of passive constructions to make the content more engaging, friendly, and active in voice and reintroduced parts that supported data that we received during a two day UX study with customers.


Spelling: "stripped" should be"striped"

A common spelling mistake here when referring to "striped" swap files (files in a stripe) - mistakenly referred to here as "stripped."

@GeoffMaciolek : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @GeoffMaciolek , thanks for catching this typo! You're correction is accurate :)
Thanks  for improving our documentation! #sign-off
Masha from the SQL Docs team


Ability to specify extra fields for generated model

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 18 (22.22%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 66.182%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

plugin/modelgen/models.go
4
18
22.22%

Files with Coverage Reduction
New Missed Lines
%

plugin/modelgen/models.go
1
73.13%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
4047

Relevant Lines:
6115

💛  - Coveralls


Update Chrome and Chromeviewer to 84 version

Tool information

Tool name: Chrome and Chromeviewer
Add or update? Update
Desired version: Latest (84)

Question, Bug, or Feature?:
Feature
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[x] Ubuntu 20.04 LTS
[ ] Windows Server 2016 R2
[x] Windows Server 2019

Hello!
We install the latest available version of Google Chrome and Chrome Driver on every image-generation and update images on weekly basis.
Chrome 84 should be available in a week.

Great!
Thank you @maxim-lobanov

It looks like there are some issues with the deployment of Chrome and the webdriver:
> ng e2e "--protractor-config=e2e/protractor-ci.conf.js"
...
[22:41:06] I/update - chromedriver: unzipping chromedriver_84.0.4147.30.zip
...
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
: Compiled successfully.
[22:41:18] I/launcher - Running 1 instances of WebDriver
[22:41:18] I/direct - Using ChromeDriver directly...
[22:41:18] E/launcher - session not created: This version of ChromeDriver only supports Chrome version 84
  (Driver info: chromedriver=84.0.4147.30 (48b3e868b4cc0aa7e8149519690b6f6949e110a8-refs/branch-heads/4147@{#310}),platform=Linux 5.3.0-1032-azure x86_64)
[22:41:18] E/launcher - SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 84

This is my workflow:
# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions

name: Node.js CI

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  build:

    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [12.x, 14.x]

    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v2-beta
        with:
          node-version: ${{ matrix.node-version }}
      - uses: actions/cache@v2
        with:
          path: ~/.npm
          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
          restore-keys: |
            ${{ runner.os }}-node-
      - run: npm ci
      - run: npm run build
      - run: npm run test -- --no-watch --no-progress --browsers=ChromeHeadlessCI
      - run: npm run e2e -- --protractor-config=e2e/protractor-ci.conf.js

@magneticflux- ,
Currently, the following versions are installed: Google Chrome 83.0.4103.116, ChromeDriver 83.0.4103.39
The next image will contain: Google Chrome 84.0.4147.89, ChromeDriver 84.0.4147.30
You code is trying to update ChromeDriver in runtime to 84.0.4147.30. After this update, Chrome and ChromeDriver become incompatible.
[22:41:06] I/update - chromedriver: unzipping chromedriver_84.0.4147.30.zip

I suggest to avoid updates in runtime and use pre-installed versions. If you prefer to update ChromeDriver in runtime, you have to update Google Chrome too

I see, I assumed the environment variables set for the drivers were standard for Protractor and that it would use them if they exist. I added these options to my protractor.conf.js to use the variables:
exports.config = {
  // ...
  chromeDriver: process.env.CHROMEWEBDRIVER + '/chromedriver',
  geckoDriver: process.env.GECKOWEBDRIVER + '/geckodriver',
  // ...
}

I see, I assumed the environment variables set for the drivers were standard for Protractor and that it would use them if they exist. I added these options to my protractor.conf.js to use the variables:
exports.config = {
  // ...
  chromeDriver: process.env.CHROMEWEBDRIVER + '/chromedriver',
  geckoDriver: process.env.GECKOWEBDRIVER + '/geckodriver',
  // ...
}

Hi @magneticflux- ,
Maybe I'm missing something, but does this avoid protractor updating chromedriver will running e2e tests? (Thanks!)

@bpz Unfortunately it doesn't, but it's pretty quick to update and Protractor doesn't use the updated version.

Sorry for late update. Chrome and Chrome Driver 84 were deployed everywhere previous week. Closing feature but please let us know if you have any questions

Thanks @maxim-lobanov, my issue is now solved :)))

This is an update to my previous solution: https://github.com/actions/virtual-environments/issues/1275#issuecomment-662242402
In protractor.conf.js:
// If in CI, webdrivers are installed globally
if (process.env.CI) {
  exports.config.chromeDriver = '/usr/bin/chromedriver';
  exports.config.geckoDriver = '/usr/bin/geckodriver';
}

In your workflow:
npm run e2e -- --protractor-config=e2e/protractor-ci.conf.js --webdriver-update=false

I ran into strange problems with my previous solution and this fixed them (somehow).


Permissions required is incorrect.

The document states the following:
Permissions required
_When you start replication for the first time, the logged-in user must be assigned the following roles:
Owner or Contributor and User Access Administrator on the Azure Migrate project's Resource Group and the target Resource Group
For the subsequent replications, the logged-in user must be assigned the following roles:
Owner or Contributor on the Azure Migrate project's Resource Group and the target Resource Group
In addition to the roles described above, the logged-in user would need the following permission at a subscription level - Microsoft.Resources/subscriptions/resourceGroups/read_

While you need this, you also need access to Microsoft Entra (Azure AD) to view service principals. Without this, you get a permissions error that DOES not provide this information. You need to look through developer logs to know that is a requirement. Please add to the documentation that users starting replication need access to view service principals.

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

ID: 01a1f427-d0c0-762c-9300-6e01dd57642e
Version Independent ID: 9726ba4e-0c0a-2c1e-b17e-232017954c21
Content: Agentless replication of VMware virtual machines concepts - Azure Migrate
Content Source: articles/migrate/concepts-vmware-agentless-migration.md
Service: azure-migrate
GitHub Login: @piyushdhore-microsoft
Microsoft Alias: piyushdhore

Attaching a screenshot of the error

Attaching error in the portal:

Attaching error from dev logs

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

Thanks!


UI of pager is not updated correctly when there are changes on the items-array using myObservableArray.setItem(...,...)

Hello,
at first, thank you for creating this plugin, it will help us a lot for our project.
After playing around with the plugin for a while, I have some trouble when initializing the pager.
I try to dynamically fill the pager with content that is getting loaded from the server, but the content gets visible only when navigating to another page and back.
Here is what I am doing:
<pager:Pager id="pager" items="{{ items }}">
    <pager:Pager.itemTemplate>
        <ScrollView>
            <GridLayout rows="auto,auto,*" columns="*" backgroundColor="#DBE8C1">
                <Label row="0" text="{{ title }}"/>
                <Label row="1" text="{{ text }}"/>
            </GridLayout>
        </ScrollView>
    </pager:Pager.itemTemplate>
</pager:Pager>

exports.vmMain = observableModule.fromObject({
    selectedIndex: 0,
    items: new observableArrayModule.ObservableArray(),

    loadStoryChapters: function () {
        var self = this;

        ffHttpModule.startHttpRequest(
            ...
            //success callback
            function(response) {
               self.set("items", new observableArrayModule.ObservableArray(response.listItems));

               //does not work correctly, title and text are visible after navigating to another page and back
               self.get('items').setItem(
                   0,
                   { id: "..." title: "First item", text: "This is the text of the first item..." }
               );
            }
        );
    }
});

When using this code for a ListView, the data is shown as expected, so the source of this problem really seems to be somewhere in the pager implementation.
I hope this can be fixed.

pager not updating the page after response


Can't modify tasks

Hi
Since the last update, I'm enable to modify "old" tasks or to add some tags to new tasks :(

Hi :)
Here's a Test Board I just created.
It was even impossible to create some new task :(
The "Create task" windows opens, but nothing is saved when I use the Save button
Test.zip

So there were a few small issues that caused this that should now be fixed in 13.0.1. Let me know if you still encounter issues.
In addition I'll mention that the extension doesn't currently allow you to create two tasks with the same name, or have an empty task name, or have an empty tag. If any of the restrictions is not satisfied, there is currently no visual indication that you should edit the inputs, but the task won't save (and there won't be a popup saying that the task has saved). I believe in your test board in particular it wouldn't save because you had the task name field empty. :)

Hi
Ok, it's working again, many thx :)