Kernel restarting: The kernel appears to have died. It will restart automatically.

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Hi Folks,
Whenever I run my .ipynb, the kernel is interrupted at the cell 31. I've tried with many search such as:
uninstall & reinstall
    ipykernel
    ipython
    jupyter_client
    jupyter_core
    traitlets
    ipython_genutils

conda install ipykernel --update-deps --force-reinstall
python -m pip install traitlets==4.3.3 --force-reinstall
python -m pip install pyzmq==19.0.2 --force-reinstall

...from the following sources: stackoverflow, github, github
But still no hope. I got the same issue with VSCode Jupyter notebook on pure Win10.
Any help please!?
With thanks - BK
VS Code Version
Version: 1.64.2 (user setup) Commit: f80445acd5a3dadef24aa209168452a3d97cc326 Date: 2022-02-09T22:02:28.252Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.18362
Jupyter Extension Version
WSL: Ubuntu-18.04. v2022.1.1301854968, Win10
Jupyter logs
Info 22:18:06: Dispose Kernel process
Error 22:18:06: Raw kernel process exited code: undefined
Error 22:18:06: Error in waiting for cell to complete [Error: Canceled future for execute_request message before replies were done
	at t.KernelShellFutureHandler.dispose (/home/bruce/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:51:432353)
	at /home/bruce/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:307599
	at Map.forEach (<anonymous>)
	at y._clearKernelState (/home/bruce/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:307585)
	at y.dispose (/home/bruce/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:66:301017)
	at /home/bruce/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:51:194444
	at t.swallowExceptions (/home/bruce/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:16:2495)
	at dispose (/home/bruce/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:51:194423)
	at t.RawSession.dispose (/home/bruce/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/out/client/extension.js:113:303296)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)]
Info 22:18:06: Cancel all remaining cells due to dead kernel

Coding Language and Runtime Version
Python 3.9.7
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
conda 4.10.3
Running Jupyter locally or remotely?
Local

@BinhKieu82
Thanks for filing this issue,

Please install the Pre-release version of the extension (this contains all of the latest fixes)

We'll be releasing a new version of the exension in a few days (with the pre-release you don't have to wait)

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to verbose
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel.

Whenever I run my .ipynb, the kernel is interrupted at the cell 31. I've tried with many search such as:

Please could you send a copy of the notebook.

Does this issue repro, when you run any other notebook with a simple cell such as print("hello World")

Its possible you are using some package thats gettig called in the 3rd cell thats causing the kernel to die.

Does this issue repro outside VS Code, when using Jupyter Notebook?

Please provide the complete output from the Jupyter output panel, not just the error, I'll nee to see what's going on before things fall over and what was executed.

Hi @DonJayamanne ,
Here are the files as requested
Please could you enable logging as follows:
wsl_vscode_jupyter_log.txt
Please could you send a copy of the notebook.
14_creating_synthetics.zip
Does this issue repro, when you run any other notebook with a simple cell such as print("hello World")
No, I can run other notebook smoothly
Its possible you are using some package thats getting called in the 3rd cell thats causing the kernel to die.
I'm not sure about this
Please install the Pre-release version of the extension (this contains all of the latest fixes)
We'll be releasing a new version of the exension in a few days (with the pre-release you don't have to wait)
You meant jupyter-notebook extension on VScode? I will try it soonest
Anything that you need, just let me know.
Thank you - BK

Can you try to run this same notebook in classic Jupyter Notebook against the same python environment.
Please install Jupyter into /home/bruce/anaconda3/envs/devito & run it using python -m jupyter notebook and try running your notebook, looks like there are problems with the package.
Let me know if this works or not (i.e. whether this works outside VS Code, in classic Jupyter Notebook against the same Conda Environment).

Please could you provide the environment yml file
Activate the devito environment in the terminal using conda activate devito
Then run the command conda env export > environment.yml and upload the environment.yml file here.

Also, please note there are errors in the output, evidence of the fact that the packakge doesn't work or needs to be re-installed.
Please consider re-installing this package

qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.

Fatal Python error: Aborted

I tried running jupyter on my Chrome browser on the same conda env, it also stopped at the same cell. Below is the yaml file.
environment-dev.zip
Let me try recreate the env. What i'm scare is, as you pointed out, the conflict among libs. If it is true, then how can i overcome that

stopped at the same cell

looks like this isn't an issue with vascode itself,as you get the same problems outside vscode.

how can i overcome that

id suggest stack overflow or the repo specific to the package you are using.
thanks for the information provided, closing as this isn't an issue caused by vscode

Thanks @DonJayamanne, at least we can conclude that the IDE is innocent :). Let's close this issue

@BinhKieu82 have you managed to resolve this issue?
Btw, I checked your yml file, it didn't contain everything, it was pointing to a requirements.txt file which wasn't in the zip file.

Hey guys! i'm having the same issue.
And my setup is basically identic to the Binh's one.
Im using the latest tensorflow version (2.8) and the latests CUDA and cudNN (my GPU: NVIDIA GTX 1060). Python Kernel's version is 3.10.4
Curently i'm developing GANS to draw faces....but due to this kernel issue i'm trying with a simple MNIST based NN and when i reach the point of training the network my Kernel just die.
This is my VScode log:
Error: Canceled future for execute_request message before replies were done
at t.KernelShellFutureHandler.dispose (c:\Users\Jacopo.vscode\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:1204175)
at c:\Users\Jacopo.vscode\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:1223227
at Map.forEach ()
at v._clearKernelState (c:\Users\Jacopo.vscode\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:1223212)
at v.dispose (c:\Users\Jacopo.vscode\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:1216694)
at c:\Users\Jacopo.vscode\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:533674
at t.swallowExceptions (c:\Users\Jacopo.vscode\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:913059)
at dispose (c:\Users\Jacopo.vscode\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:533652)
at t.RawSession.dispose (c:\Users\Jacopo.vscode\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:537330)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
Also: the same code run on my girlfriend's Jupyter Notebook, but not on mine. Then i tryed to force TF to work just with the CPU, i was able to do that using this code:
import os
import tensorflow as tf
os.environ['CUDA_VISIBLE_DEVICES'] = '-1'
if tf.test.gpu_device_name():
print('GPU found')
else:
print("No GPU found")
#No GPU found
And it works! so the problem occour when i try to use TF-gpu....problem is that i dont know how to fix this. My PATH variables are set just fine. I really dont know where to start.
P.S. sorry if my english is bad.

Hey guys,
I just had a similar problem. I tried to configure my GPU yesterday with TensorFlow and it appeared to have worked when trying this code in jupyter notebook:
import TensorFlow as tf
print(tf.version)
print(len(tf.config.list_physical_devices('GPU'))>0)
but when I tried to train a convolutional neural net today my kernel stopped. When reading the error message I found in my anaconda prompt:
Could not locate zlibwapi.dll. Please make sure it is in your library path!
I looked solutions to this problem and found this forum:
https://forums.developer.nvidia.com/t/zlib-dll-for-latest-cudnn-in-official-install-guide-is-missing/197630
where the last comment said:
In NVIDIA website, they referred to zlibwapi.dll- I was able to locate this file in “C:\Program Files\Microsoft Office\root\Office16\ODBC Drivers\Salesforce\lib” (I installed using Microsoft 365 x64 in windows 11) and copy pasted this file into “C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.6\bin” I was able to run Tensorflow 2.8.0 thereafter
So I simply did this and it worked!

where the last comment said: In NVIDIA website, they referred to zlibwapi.dll- I was able to locate this file in “C:\Program Files\Microsoft Office\root\Office16\ODBC Drivers\Salesforce\lib” (I installed using Microsoft 365 x64 in windows 11) and copy pasted this file into “C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.6\bin” I was able to run Tensorflow 2.8.0 thereafter
So I simply did this and it worked!

It works for me! Thank you!

Hey guys, I just had a similar problem. I tried to configure my GPU yesterday with TensorFlow and it appeared to have worked when trying this code in jupyter notebook: import TensorFlow as tf print(tf.version) print(len(tf.config.list_physical_devices('GPU'))>0)
but when I tried to train a convolutional neural net today my kernel stopped. When reading the error message I found in my anaconda prompt: Could not locate zlibwapi.dll. Please make sure it is in your library path!
I looked for solutions to this problem and found this forum: https://forums.developer.nvidia.com/t/zlib-dll-for-latest-cudnn-in-official-install-guide-is-missing/197630
where the last comment said: In NVIDIA website, they referred to zlibwapi.dll- I was able to locate this file in “C:\Program Files\Microsoft Office\root\Office16\ODBC Drivers\Salesforce\lib” (I installed using Microsoft 365 x64 in windows 11) and copy pasted this file into “C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.6\bin” I was able to run Tensorflow 2.8.0 thereafter
So I simply did this and it worked!

Saved my life! Thank you.

Kernel dies when I try to run inference using Numpyro (based on JAX). All previous code, including imports, is fine. Any hints? I'm using CPU on Mac.

Kernel dies when I try to run inference using Numpyro

Please could you file an issue for this. Also, please test whether the same code works in regular Jupyter Notebook or Jupyter lab. Its most likely its failing there as well. If not, please do file an issue and we'll take a look and try to get you unbloked

every time whenever i open note book with tensorflow it says kernal restarting

This is caused by incorrectly installed tensorflow package, users have run into this issue a number of times.
i world suggest reinstalling tendorflow and all dependencies or creating anew python environment, if you were to run Jupyter against the same environment you’d run into the same issue, meaning it’s not an issue in vscode but your environment.


No KML export of BuildingInstallations modelled as ImplicitGeometry?

Dear developers,
A question to you, as I could not find it in the documentation (or I may have missed it) of the 3DCityDB (3.x).
I have a number of LoD2 buildings. Additionally, they have some (outer) BuildingInstallations which are modelled geometrically via lod2ImplicitRepresentation (using MultiSurfaces).
I can validate the CityGML input file in the 3DCityDB importer, I can import it correctly into the 3DCityDB, but I cannot export the BuildingInstallations using the 3DCityDB KML exporter.
Is is a bug or it is just not supported?
If I model each BuildingInstallation "as usual" via lod2Geometry (again, using MultiSurfaces), than it the exporter works as expected.
If needed, I can provide an exerpt of the CityGML file. Let me know!

Hi @gioagu, well, it should work but it seems like we never tested this scenario. Would be great if you can provide us some test data so that we can fix this issue. Does the CityGML export work correctly?

Here you go.
This is exported from the 3DCityDB. I'd say, yes, the exporter works.
There are for each building 3 BuildingInstallations. They look like spheres on top of the buildings.
The lowest one is modelled as lod2Geometry, the other 2 as lod2ImplicitGeometries (Solid and MultiSurface, respectively).
In FZK you can visualise them easily.
The KMZ exporter only exports the first one.
The zipped CityGML file is attached: Test_mini_out.zip

Thanks @gioagu. I checked the current implementation. Implicit geometries are only considered by the KML/COLLADA/glTF exporter if they are modelled for top-level features (such as frn:CityFurniture or gen:GenericCityObject) but not for nested sub-features such as bldg:BuildingInstallation.
So, the KML/COLLADA/glTF exporter needs to be enhanced to support your test dataset correctly. I am going to work on it, but it may take a bit more time. I will post updates here.

Fixed in master branch (1177b6657fc963cbb51c3fd1f5aadb32f5189757). Below the exported model is shown in Google Earth.

Closing. Feel free to reopen if the issue still occurs.


Authorization Failed invalid

Hi
link is browsable but failed authorization, can anyone advise?
regards
Authorizing Identifier cloud.klaveren7.be Using Challenge Type http-01
Writing challenge answer to D:\Websites\webdav.well-known/acme-challenge/pR-Xx1
HqBIJdCc5x6KcOWM0kEIBudZlTjHEX3q8hP2g
Writing web.config to add extensionless mime type to D:\Websites\webdav.well-kn
own\acme-challenge\web.config
Answer should now be browsable at http://cloud.klaveren7.be/.well-known/acme-cha
llenge/pR-Xx1HqBIJdCc5x6KcOWM0kEIBudZlTjHEX3q8hP2g
Submitting answer
Refreshing authorization
Refreshing authorization
Authorization Result: invalid
Authorization Failed invalid

The ACME server was probably unable to reach http://cloud.klaveren7.be/.well-kno
wn/acme-challenge/pR-Xx1HqBIJdCc5x6KcOWM0kEIBudZlTjHEX3q8hP2g
Check in a browser to see if the answer file is being served correctly.
Authorize failed: This could be caused by IIS not being setup to handle extensio
nless static files.Here's how to fix that:
1.In IIS manager goto Site/ Server->Handler Mappings->View Ordered List
2.Move the StaticFile mapping above the ExtensionlessUrlHandler mappings. (like
this http://i.stack.imgur.com/nkvrL.png)
3.If you need to make changes to your web.config file, update the one at D:\Soft
ware\letsencrypt\web_config.xml

I meet the same problem, I have set done, But it doesn't work on. How to slove it,Please help me ...

You need to do at least what kdhoe1 did, tell us the error and the URL that should be available.
If not all we can do is tell you to try a service like: https://www.infobyip.com/httpservertest.php


add ioniq 18 hybrid

fingerprint

All PRs should be made against master.

not master-ci
should be made master right?


bt: host: fix stack overflow and improve timing performance for ECC emulation

This PR fixes issues (1) and (3) reported here, i.e.

Without the increase in CONFIG_BT_LONG_WQ_STACK_SIZE all Bluetooth pairings on the nRF53 and nRF54 series will fail on target
There's nearly a 10x increase in pairing time (takes up to 10 seconds) which is not only really bad, but will also lead to timeouts on tests on hardware as well

and also potentially reduce issue (4), i.e.

There's a significant increase in memory as pointed out by https://github.com/zephyrproject-rtos/zephyr/pull/79931#issuecomment-2504945185

@sjanc if/when the CI is green, can you please launch AutoPTS?

And assuming that the tests are green, I think it would be good to fast-track merging this. Not sure if it'd be ok to add the Hotfix label, since this isn't fixing direct upstream CI breakage, but it is definitely unblocking other kinds of testing and potentially fixing downstream CI issues.

#AutoPTS run zephyr nrf53 SM

Scheduled PR https://github.com/zephyrproject-rtos/zephyr/pull/82217#issuecomment-2505692340, board: nrf53, estimated start time: 10:53:12, test case count: 71, estimated duration: 0Test cases to be runSM/CEN/PROT/BV-01-CSM/CEN/JW/BV-05-CSM/CEN/JW/BI-04-CSM/CEN/JW/BI-01-CSM/CEN/PKE/BV-01-CSM/CEN/PKE/BV-04-CSM/CEN/PKE/BI-01-CSM/CEN/PKE/BI-02-CSM/CEN/OOB/BV-01-CSM/CEN/OOB/BV-03-CSM/CEN/OOB/BV-09-CSM/CEN/OOB/BI-01-CSM/CEN/EKS/BV-01-CSM/CEN/EKS/BI-01-CSM/CEN/SIGN/BV-01-CSM/CEN/SIGN/BV-03-CSM/CEN/SIGN/BI-01-CSM/CEN/KDU/BV-04-CSM/CEN/KDU/BV-05-CSM/CEN/KDU/BV-06-CSM/CEN/KDU/BV-10-CSM/CEN/KDU/BV-11-CSM/CEN/KDU/BI-04-CSM/CEN/PIS/BV-02-CSM/CEN/PIS/BV-03-CSM/CEN/SCJW/BV-01-CSM/CEN/SCJW/BV-04-CSM/CEN/SCJW/BI-01-CSM/CEN/SCPK/BV-01-CSM/CEN/SCPK/BV-04-CSM/CEN/SCPK/BI-01-CSM/CEN/SCPK/BI-02-CSM/CEN/SCOB/BV-01-CSM/CEN/SCOB/BV-04-CSM/CEN/SCOB/BI-01-CSM/CEN/SCOB/BI-04-CSM/PER/PROT/BV-02-CSM/PER/JW/BV-02-CSM/PER/JW/BI-03-CSM/PER/JW/BI-02-CSM/PER/PKE/BV-02-CSM/PER/PKE/BV-05-CSM/PER/PKE/BI-03-CSM/PER/OOB/BV-02-CSM/PER/OOB/BV-04-CSM/PER/OOB/BV-10-CSM/PER/OOB/BI-02-CSM/PER/EKS/BV-02-CSM/PER/EKS/BI-02-CSM/PER/KDU/BV-01-CSM/PER/KDU/BV-02-CSM/PER/KDU/BV-03-CSM/PER/KDU/BV-07-CSM/PER/KDU/BV-08-CSM/PER/KDU/BV-09-CSM/PER/KDU/BI-02-CSM/PER/KDU/BI-03-CSM/PER/KDU/BI-04-CSM/PER/PIS/BV-01-CSM/PER/PIS/BV-02-CSM/PER/SCJW/BV-02-CSM/PER/SCJW/BV-03-CSM/PER/SCJW/BI-02-CSM/PER/SCPK/BV-02-CSM/PER/SCPK/BV-03-CSM/PER/SCPK/BI-03-CSM/PER/SCPK/BI-04-CSM/PER/SCOB/BV-02-CSM/PER/SCOB/BV-03-CSM/PER/SCOB/BI-02-CSM/PER/SCOB/BI-03-C

A hotfix for the (unrelated) CI failure is here: #82222

AutoPTS Bot results:
Failed tests (2)SM      SM/CEN/KDU/BI-04-C              FAILSM      SM/PER/KDU/BI-04-C              FAIL
Successful tests (69)SM      SM/CEN/EKS/BI-01-C              PASSSM      SM/CEN/EKS/BV-01-C              PASSSM      SM/CEN/JW/BI-01-C               PASSSM      SM/CEN/JW/BI-04-C               PASSSM      SM/CEN/JW/BV-05-C               PASSSM      SM/CEN/KDU/BV-04-C              PASSSM      SM/CEN/KDU/BV-05-C              PASSSM      SM/CEN/KDU/BV-06-C              PASSSM      SM/CEN/KDU/BV-10-C              PASSSM      SM/CEN/KDU/BV-11-C              PASSSM      SM/CEN/OOB/BI-01-C              PASSSM      SM/CEN/OOB/BV-01-C              PASSSM      SM/CEN/OOB/BV-03-C              PASSSM      SM/CEN/OOB/BV-09-C              PASSSM      SM/CEN/PIS/BV-02-C              PASSSM      SM/CEN/PIS/BV-03-C              PASSSM      SM/CEN/PKE/BI-01-C              PASSSM      SM/CEN/PKE/BI-02-C              PASSSM      SM/CEN/PKE/BV-01-C              PASSSM      SM/CEN/PKE/BV-04-C              PASSSM      SM/CEN/PROT/BV-01-C             PASSSM      SM/CEN/SCJW/BI-01-C             PASSSM      SM/CEN/SCJW/BV-01-C             PASSSM      SM/CEN/SCJW/BV-04-C             PASSSM      SM/CEN/SCOB/BI-01-C             PASSSM      SM/CEN/SCOB/BI-04-C             PASSSM      SM/CEN/SCOB/BV-01-C             PASSSM      SM/CEN/SCOB/BV-04-C             PASSSM      SM/CEN/SCPK/BI-01-C             PASSSM      SM/CEN/SCPK/BI-02-C             PASSSM      SM/CEN/SCPK/BV-01-C             PASSSM      SM/CEN/SCPK/BV-04-C             PASSSM      SM/CEN/SIGN/BI-01-C             PASSSM      SM/CEN/SIGN/BV-01-C             PASSSM      SM/CEN/SIGN/BV-03-C             PASSSM      SM/PER/EKS/BI-02-C              PASSSM      SM/PER/EKS/BV-02-C              PASSSM      SM/PER/JW/BI-02-C               PASSSM      SM/PER/JW/BI-03-C               PASSSM      SM/PER/JW/BV-02-C               PASSSM      SM/PER/KDU/BI-02-C              PASSSM      SM/PER/KDU/BI-03-C              PASSSM      SM/PER/KDU/BV-01-C              PASSSM      SM/PER/KDU/BV-02-C              PASSSM      SM/PER/KDU/BV-03-C              PASSSM      SM/PER/KDU/BV-07-C              PASSSM      SM/PER/KDU/BV-08-C              PASSSM      SM/PER/KDU/BV-09-C              PASSSM      SM/PER/OOB/BI-02-C              PASSSM      SM/PER/OOB/BV-02-C              PASSSM      SM/PER/OOB/BV-04-C              PASSSM      SM/PER/OOB/BV-10-C              PASSSM      SM/PER/PIS/BV-01-C              PASSSM      SM/PER/PIS/BV-02-C              PASSSM      SM/PER/PKE/BI-03-C              PASSSM      SM/PER/PKE/BV-02-C              PASSSM      SM/PER/PKE/BV-05-C              PASSSM      SM/PER/PROT/BV-02-C             PASSSM      SM/PER/SCJW/BI-02-C             PASSSM      SM/PER/SCJW/BV-02-C             PASSSM      SM/PER/SCJW/BV-03-C             PASSSM      SM/PER/SCOB/BI-02-C             PASSSM      SM/PER/SCOB/BI-03-C             PASSSM      SM/PER/SCOB/BV-02-C             PASSSM      SM/PER/SCOB/BV-03-C             PASSSM      SM/PER/SCPK/BI-03-C             PASSSM      SM/PER/SCPK/BI-04-C             PASSSM      SM/PER/SCPK/BV-02-C             PASSSM      SM/PER/SCPK/BV-03-C             PASS

@fabiobaltieri here's a follow-up for the results of west build -p always -b nrf52dk/nrf52832 samples/bluetooth/peripheral_hids on different branches:

main

Memory region         Used Size  Region Size  %age Used
           FLASH:      203988 B       512 KB     38.91%
             RAM:       30904 B        64 KB     47.16%
        IDT_LIST:          0 GB        32 KB      0.00%

tinycrypt (as you reported in 79931)

Memory region         Used Size  Region Size  %age Used
           FLASH:      181116 B       512 KB     34.55%
             RAM:       29240 B        64 KB     44.62%
        IDT_LIST:          0 GB        32 KB      0.00%

this PR

Memory region         Used Size  Region Size  %age Used
           FLASH:      191408 B       512 KB     36.51%
             RAM:       30968 B        64 KB     47.25%
        IDT_LIST:          0 GB        32 KB      0.00%

The ROM increase is half of what it was with #79931.

@valeriosetti cool, thanks for the followup.

Added the Hotfix label, since I think this falls under what's defined here: https://docs.zephyrproject.org/latest/project/dev_env_and_tools.html#hotfix


Make collision behavior transient

Description
It looks like the current collision behavior is persistent, meaning once an agent collides, it remains in a collided state for the rest of the episode (until sim.reset() is called). If agents are penalized for collisions and the collision behavior = 'ignore', this creates unintended effects for learning, as it becomes difficult to assign credit to the specific state that was "bad".
This PR aims to make the collision behavior transient, resetting the collision state at the start of each timestep. This ensures that the indicator function for collision in the info tensor is only true if the agent collided at the current timestep. The info tensor is used to define rewards as a linear combination of the collision, off_road and goal achieved metrics.

Here's the case I'm worried about: if the teleport mode is on, the vehicle might teleport back

Do you have an experiment suggesting that this aids with credit assignment?

Here's the case I'm worried about: if the teleport mode is on, the vehicle might teleport back

Yes, that seems problematic.
I only really care about the info tensor, since I am using that to define the rewards per step. There may be a more principled way to achieve this


EOF: Missing coverage for max sizes

For EOFCreate and RETURNCONTRACT I've changed client code to increase the max sizes for containers, max code size, etc; and it doesn't cause any tests to fail

same for some EIP3540 constants about Max values


Updated README.md

Closes #56

@surchs Which branch are u on?

@rmanaem I am looking at this PR: https://github.com/neurobagel/query-tool/pull/57/files?short_path=b335630#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5

@surchs I reckon it's a GitHub bug/issue cause the README.md renders just fine in the main branch


malware detection ???????

I use qengine to obfucase my "hello world" program, windows defender mark my "hello world" application is malware

lol


Add graph gradation

CheckList

[x] Add gradation
[x] Resize graph y axis
[x] Update dummy data

LGTM, did you like this design? @Taewan-P

LGTM as well


Collecting coverage changes code behavior

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
The code snipet below prints "bar" when "--coverage" is on.
If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.
https://gist.github.com/dkwingsmt/c2ee75b0c6c141594eafc38e984ffa28
What is the expected behavior?
The code snipet above should print "foo bar" when "--coverage" is on.
This is the behavior when running the module directly using babel-node or jest without "--coverage".
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

macOS 10.12.5
npm 3.10.10
node 6.11.0
jest  20.0.4

Could you setup the repro on repl.it?

I tried to copy in the code above since I am having a similar issue, but it doesn't repro when changing to CommonJS module syntax: https://repl.it/JkIT/3
If you just pull the ZIP file it repros for me though:

To add to this, if I enable collectCoverage, the debug output shows babel running, but if I don't, it doesn't. It looks like Istanbul is using/adding Babel behind the scenes and maybe not respecting some local config.
jest.config.js
{
  transform: {},
  collectCoverage: true,
}

.babelrc
{
  "presets": []
}

> DEBUG="*" yarn test

@alexkrolick in order to collect coverage information the source must be instrumented somehow.
The simplified flow goes like this:

Read the file.
Check if the file exists in the cache system, if it does it'll return it.
If not in cache, it'll check if it should transform the file (if you got babel-jest defined it will check wether this file should be transformed by it).
Transformers can opt-in to instrument the source, jest will check if it did.
If it did not, it runs the following logic:
https://github.com/facebook/jest/blob/16431b5ae65660090a4d4c71f6aca02e733ac62e/packages/jest-runtime/src/script_transformer.js#L165-L183

It is important to note that if you don't have babel-jest setup to transform your .js files the 5th step is still going to happen.
Also important to note is that even though it loads babel to do the actual instrumentation (using https://github.com/istanbuljs/babel-plugin-istanbul) it will not load any other presets or plugins, note that babelrc is false.
To figure out what is happening to the test code I would check what the instrumented file looks like.
Using jest --showConfig | grep cacheDir open up cacheDirectory. It's likely full of stuff so delete all of it to make this process easier. Run jest mod --coverage and investigate the contents of the subfolders, the file is likely in a place like this: /jest_dx/jest-transform-cache-9e486021251b86ce0446e8cbaefa62ac-a3baf8c1fc3eaea71dae99bd022c8f3f/30/mod_305357bb728f3bca55747cb780b94dfc.
Hopefully it'll shed some light to why it changes the behavior of the script.

I tested it again today and the output is normal now (foo bar), probably due to some fixes.
I'm closing this issue. Thanks to everyone who offered help.

Great to hear, thanks for reporting back to us @dkwingsmt! 😄


TensorFlow installation apt commands is wrong

URL(s) with the issue:
https://www.tensorflow.org/install/gpu
Description of issue (what needs changing):

change your language to chinese simplified from the upright corner.
in the apt installation commands for Ubuntu 18.04 (CUDA 10), last step shown below is wrong:

  # Install TensorRT. Requires that libcudnn7 is installed above.
    sudo apt-get update && \
            && sudo apt-get install -y --no-install-recommends libnvinfer-dev=5.1.5-1+cuda10.0

there is a syntax error--> && \ &&
libnvinfer5=5.1.5-1+cuda10.0  should be installed first before libnvinfer-dev=5.1.5-1+cuda10.0
just change the commands to the same as what is shown in english-language website.

Thanks. Direct link to zh-cn page: https://tensorflow.google.cn/install/gpu?hl=zh-cn
This has been fixed in the source file but translations lag behind. Will be updated on next translation job.


Suppress weight labels from rendering

Adds a extensible options array to accomplish this.

Thanks for your PR, much appreciated :+1:
I think having this feature makes perfect sense, but I have to admit I'm not a big fan of the current implementation.
The related code autogenerates an edge label. I think it makes more sense to split this code off and possibly pass a custom instance into the dot exporter.
See also https://github.com/clue/graph/issues/114 and #14.

Feel free to re-implement. I just needed a quick way to turn off those annoying labels in dot. Merge or discard--up to you.

Didn't mean to discourage your contribution, this PR is much appreciated :+1:
I think it makes perfect sense to omit the weight in certain cases. And it probably also makes sense to omit the other edges attributes (flow and capacity) in similar cases.
What do you think about this?

I agree. This was the intent of implementing a simple associative array so that you can extend it into any number of "toggle switch" options.
If you don't like the direct access within the class, we could implement a getOption() method that checks if it's set (false if not) and returns the value. We could then wrap all conditional output in a getOption() call beforehand, and give a list of valid options for use.

I'm sure this is going to sufficient once https://github.com/clue/graph/issues/114 has been implemented.
This would mean we would have to specify which attributes get exported which way. This is certainly beyond our control for special attributes, so I think it makes more sense to provide a simple "export mathematical properties like previously"-implementation and a "do not export anything"-implementation and an interface for custom implementations.


Add remaining setters to PassOptions

Need setters for everything used by optimization-options.h. Follow existing patterns.

fixed


Add python tests

All tests are right now performed at the C library level.

What about writing all tests in Python?

My plan for the future is to test almost everything in python. This way I test the python code too and also the tests are more pleasant to write. I will keep the existing C tests anyway and I will add tests in C only if I'm not sure if the error is in the python wrappers or the C code.

Added first tests in 9d03218619d96faabcac894e6b54ed9868948be9


Roll engine 496fd3acb57a..bc3bd709c7f9 (1 commits)

https://github.com/flutter/engine/compare/496fd3acb57a...bc3bd709c7f9
git log 496fd3acb57ab97f9b83b35d22636ee67bf2b5b2..bc3bd709c7f9ef099485f85c30d108707b89107e --no-merges --oneline
bc3bd709c Roll src/third_party/skia 4dfbc9e68528..2f9297dff115 (4 commits) (flutter/engine#8812)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (amirha@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


Day62: LeetCode-1624. Largest Substring Between Two Equal Characters - HashTable

Largest Substring Between Two Equal Characters
https://leetcode.com/problems/largest-substring-between-two-equal-characters/
Given a string s, return the length of the longest substring between two equal characters, excluding the two characters. If there is no such substring return -1.
A substring is a contiguous sequence of characters within a string.

Example 1:
Input: s = "aa"
Output: 0
Explanation: The optimal substring here is an empty substring between the two 'a's.
Example 2:
Input: s = "abca"
Output: 2
Explanation: The optimal substring here is "bc".
Example 3:
Input: s = "cbzxy"
Output: -1
Explanation: There are no characters that appear twice in s.


correctly handle making a cert for a CNAME

got my understanding for how this works from https://letsencrypt.org/2019/10/09/onboarding-your-customers-with-lets-encrypt-and-acme.html#the-advantages-of-a-cname


Automate and Extend Employee Onboarding

Mission URL: https://developers.sap.com/mission.cp-starter-ibpm-employeeonboarding.html
Tutorial 2, Step 4
User is told to fill the Attributes of workflow but they are already filled

Yeah, there has been recent release of the workflow sample application where the workflow properties are auto filled. Will publish the updated tutorial soon!

@ArchanaShukla Please update issue when updated, and then @arpitjindal97 please close the issue


Question regarding regenerate button

Hi there!
in the admin UI the UUID field is displayed with a regenerate button for the UUID on the field.  This button is also displayed if the field itself is disabled.
For our usecase we would require to disable this regenerate option in the UI as we only want the UUID to be auto generated on component creation or if the value itself is set via API. We would require that once the UUID is set on a component it is not possible to change it again via admin UI.
Is there currenty an option to achieve this?
Thanks in advance! If there is anything unclear, just let me know!

Hi there!
in the admin UI the UUID field is displayed with a regenerate button for the UUID on the field. This button is also displayed if the field itself is disabled.
For our usecase we would require to disable this regenerate option in the UI as we only want the UUID to be auto generated on component creation or if the value itself is set via API. We would require that once the UUID is set on a component it is not possible to change it again via admin UI.
Is there currenty an option to achieve this?
Thanks in advance! If there is anything unclear, just let me know!

Thanks for your feedback. Currently there's no option to achieve this. I'll work on this feature enhancement.

Thanks, works great! :)


Allow pathlib.Paths in args

Thank you for this project!
subprocess.run allows pathlib.Paths in args, but to use tee-subprocess (in a type-safe manner) I have to convert paths to strings.

Thanks, and thanks for pointing that out. I can add path-like support for shell invocations

@adamtheturtle to clarify, you're talking about passing a PathLike object or a sequence containing a path-like (presumably as the first argument) into a non-shell invocation, correct?

Thank you @thearchitector for the response. Yes, that's right. Though, the "presumably" does not match my experience. For example, my code might look like:
my_file = pathlib.Path("some_file.py")
tee_subprocess.run(args=["mypy", my_file])

FWIW my precise usage is at https://github.com/adamtheturtle/sybil-extras/blob/196162894a34112848656de997829a32a64b247a/src/sybil_extras/evaluators/shell_evaluator.py#L164.

@adamtheturtle I made a new release, which should cover your use case. I also (hopefully) improved the static typing quite a bit, so you should have better overloads when dealing with shell vs. non-shell invocations and text/binary outputs.

Fantastic, thank you!


Chrome app doesn't send /bye on close.

Is this fixed in #424?

There are 2 issues.

If you close the app window, no bye message is sent, because onbeforeunload is not available in Chrome Apps
Sync xhr is not available in Chrome apps, so even when you hit hangup, the messages don't get sent.

I started working on these but it isn't as simple as changing the xhr to async, because there is a specific ordering we need, and we need to finish the work before the window closes. I'll continue to work on a fix.

Is there a solution for the first issue?
On Thu, Jan 29, 2015 at 1:09 PM, Chuck Hays<EMAIL_ADDRESS>wrote:

There are 2 issues.

If you close the app window, no bye message is sent, because
onbeforeunload is not available in Chrome Apps
Sync xhr is not available in Chrome apps, so even when you hit
hangup, the messages don't get sent.

I started working on these but it isn't as simple as changing the xhr to
async, because there is a specific ordering we need, and we need to finish
the work before the window closes. I'll continue to work on a fix.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleChrome/webrtc/issues/437#issuecomment-72104433.

--
Jiayang Liu

The background.js file can detect when the window closes, and can do the cleanup. This is how it can be hooked up:
https://github.com/chuckhays/webrtc/commit/e1a48f5ce5cd08b3addb18e6ac83e64bf784939f
The next step is to re-arrange things so the needed context is still available. Chrome starts disposing objects that we still need in order to make the ending calls.

Is there a bug for this in the apprtc repo?


net/zerotier: Update to new Zerotier version

Zerotier version 1.2.8 has been out for a couple of weeks now, any chance of a plugin update?
Paging @dharrigan ;)

@StrikerTwo the plugin is not really related to the package version, nobody seems to update FreeBSD port

Ah, thanks. I emailed the package maintainer and the updated FreeBSD port is ready:
https://github.com/skunkwerks/ports/commit/3aec72f27367c90db052df1f8fc94954ce6d5d61
https://reviews.freebsd.org/D15133
Now what? ;)

@StrikerTwo wait for 18.1.9 hopefully. would you mind testing the new package version up front? I can provide a build in 1-2 days. Are you running amd64/OpenSSL or another combo?
PS: thanks to @dch for the update!

Sure, I can test it. amd64/OpenSSL is fine.

First part of the puzzle: https://github.com/opnsense/ports/commit/ff99edfa44

@fichtner Looking good! Install went without problems and connections work just fine.

@StrikerTwo super, let's ship this in 18.1.9 then. no further action needed. :)


Include message body in debug logs for error responses

@raman325 it would be nice to get this merged and referenced in HA update so we can do more productive troubleshooting.

Thanks @raman325


ReteetionPolicy and IsDefault updates

Per Issue #9081

Docs Build status updates of commit 755184f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-RetentionPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-MailboxPlan.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-RetentionPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[shardformer] fix test error that group is not registered when shard the model.

📌 Checklist before creating the PR

[x] I have created an issue for this PR for traceability
[x] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[x] I have added relevant tags if possible for us to better distinguish different PRs

🚨 Issue number

Link this PR to your issue with words like fixed to automatically close the linked issue upon merge
e.g. fixed #1234, closed #1234, resolved #1234

#5205
📝 What does this PR do?

Summarize your work here.
if you have any plots/diagrams/screenshots/tables, please attach them here.

fix test error that group is not registered when shard the model.
💥 Checklist before requesting a review

[x] I have linked my PR to an issue (instruction)
[x] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[x] I have performed a self-review of my code
[x] I have added thorough tests.
[x] I have added docstrings for all the functions/methods I implemented

⭐ Do you enjoy contributing to Colossal-AI?

[x] 🌝 Yes, I do.
[ ] 🌚 No, I don't.

Tell us more if you don't enjoy contributing to Colossal-AI.

All tests have passed.


Added Orbs token

Orbs is a public blockchain infrastructure designed for businesses looking at trust as a competitive strategy. With blockchains as the new standard for an impartial third-party source of verification, solutions can give strong guarantees that will make them more attractive to their users and ecosystem partners. To accommodate business needs, Orbs is pioneering a hybrid consensus architecture, keeping businesses in control of costs, governance and guaranteed performance, while still capturing the disruption of a truly decentralized Proof-of-Stake ecosystem with a permissionless validator pool. Founded in 2017, Orbs is being developed by a dedicated team of more than 50 people out of its offices in Tel Aviv, Israel; San Francisco, California; Singapore; and Seoul, South Korea. Orbs was named Gartner's “Cool Vendor in Blockchain Technology” for 2018.
Github: https://github.com/orbs-network/
Website: https://www.orbs.com
Telegram: https://t.me/orbs_network
Twitter: https://twitter.com/orbs_network
LINE (Japan): https://line.me/R/ti/p/%40vrf9558a
Etherscan (token has neutral reputation): https://etherscan.io/token/0xff56cc6b1e6ded347aa0b7676c85ab0b3d08b0fa
Contract (with verified source code) on Etherscan: https://etherscan.io/address/0xff56cc6b1e6ded347aa0b7676c85ab0b3d08b0fa
Tal Kol (Orbs co-founder) Talk at ABS 2019: https://www.youtube.com/watch?v=Moz6tObGQQs
Tal Kol Talk at NOAH 2019: https://www.youtube.com/watch?v=N4btt3F4o70
CoinBoys interview: https://thecoinboys.com/index.php/2019/07/30/coin-boys-podcast-orbs/
Tal Kol on Block TV: https://www.youtube.com/watch?v=-rMVgY_OGoI

Hello, joining the request to add this ERC20 token.
Thank you :)

Hi @avilanthe1 - I would like to merge this request but there is a new requirement that the logo has to be in SVG format. Can I ask you to add it as a replacement for the PNG one? Thanks

Already on the list


support to set  livenessProbe and readinessProbe for a apps

we need to set health check for the pod , it's better to have a way to support this, can we define this in Acornfile

That's already supported: https://docs.acorn.io/reference/acornfile#probes-probe

Also better docs here: https://docs.acorn.io/authoring/containers#probes


Remove Decompose pass gate argument

The gate argument to the transpiler pass :class:~.Decompose was deprecated in Terra 0.19 and is now removed.

ups. duplicated https://github.com/Qiskit/qiskit-terra/pull/9325

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 84.889%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
66516

Relevant Lines:
78356

💛  - Coveralls


Solution of Valid_Mountain_Problem in Python

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #1011
Replace issue_no with the issue number which is fixed in this PR
Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@apran-vs add test cases

I already add test case
Please recheck

@apran-vs where have u added??

In the main python file.
I added 4 test case.

@apran-vs are u in slack??

If yes then go through the messages

Yes but there are many messages.
So can you give some ideas how to add test case??

@apran-vs go through the pinned messages

@apran-vs add main function

please check updated file

@apran-vs u haven't placed it in a folder. Place it


"base table" not defined

Because the phrase "base table" is not defined, the reader has to guess the meaning and/or read other documents that might define the meaning.
It could mean only the table in the FROM clause, or that table and any table INNER JOINed, or something else.
[Enter feedback here]

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

ID: caab144e-f326-f6b7-aa87-0589c39a9f57
Version Independent ID: 8b5406c8-9083-af2f-015c-ccbbb502cad6
Content: Modify Data Through a View - SQL Server
Content Source: docs/relational-databases/views/modify-data-through-a-view.md
Product: sql
Technology: table-view-index
GitHub Login: @stevestein
Microsoft Alias: sstein

@jdeehrnth -- thank you for your feedback.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@stevestein -- please look into this issue.

@jdeehrnth - thanks for the feedback. Because the content is about views, the base table is the table the view is based on, so not sure how much more info we can add here. If the view is based on multiple tables, the article points out that you can update, but not add or delete rows.
Hope that helps.

#please-close


Somewhat heavy rework. Fixed several bugs/inconsistencies and added new functionality.

Fixes:

Fixed bad cast which caused errors.
Abandoned layers no longer regenerate. The next dug layer will always be deeper than the last.
Fixed old mine layers remaining active when the player abandons a colony (especially during The Archonexus quest)
Fixed "Bring Up" option on the main lift sending items out of bounds (items despawned)
Fixed mining shafts and lifts ignoring storages which shared a space with conduits (or other buildings)
Fixed underground ritual success failing to spawn pawns who would join the colony

Changes:

Reduced mining shaft base power consumption to 200. If there are no powered layers, this is the amount that will be used.
Changed minimum consumption when 1 layer is powered (to 300 instead of 1200)

New stuff:

The "Ore density" of new layers is now configurable in mod options and can range from 0 to any number.
Added map size of 125 tiles (between 75 and 200)
Which layers receive power is now configurable. You can disable the power to some layers and the power they would have received will be split between the remaining layers instead. Power to all layers can be cut.
Underground lifts can send items to other layers as well as to the surface
The primary shaft and all lifts now transfer items independently from one-another instead of all going to the same globally set layer. This option can be set to "None" for that shaft/lift to ignore storages. (ex. layer at 10m can send items to 30m, which is set to send items to the surface, or whatever.)

Dev:
Added button in dev mode that resets some variables in UndergroundManager (the map component) causing all existing underground shafts to re-link to the first existing mining shaft found. Not useful at the moment but has the potential to fix some bad game states.

Actually I'm going to squash things so the main repo doesn't have 100000 commits.
Ik spam is bad but I will close and reopen this for the sake of orderliness and request again with the squashed branch containing all changes.


Completed Assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Completed answers to assignment-2 questions.
What did you learn from the changes you have made?
I learned how to review and critically evaluate code.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
N/A
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
N/A
How were these changes tested?
N/A
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[X ] I can confirm that my changes are working as intended

A1 and A2 complete


Can we reset Hex code on Broadlink TC2 switch?

I have 4 TC2 switches. 3 of them work just fine. But another one got a problem. this one always listens to other switches. Example, If I turn on the broken one only. It can turn on and off, perfectly. Somehow, if I turn on the broken one and turn on or turn off other switches. The broken one also turns off with a little bit delay every time, on any normal switch. It seems like the broken one will turn off on any RF code that it has received.
So, Can we reset the hex code on the broken one? or it did like that because it's broken?
Please give me some idea.
Thank you in advance.

Sounds like you'll need to get in touch with Broadlink sorry!

I have 4 TC2 switches. 3 of them work just fine. But another one got a problem. this one always listens to other switches. Example, If I turn on the broken one only. It can turn on and off, perfectly. Somehow, if I turn on the broken one and turn on or turn off other switches. The broken one also turns off with a little bit delay every time, on any normal switch. It seems like the broken one will turn off on any RF code that it has received.
So, Can we reset the hex code on the broken one? or it did like that because it's broken?
Please give me some idea.
Thank you in advance.

@kamum26 Have you solve the issue? I have the same problem and looking for a fix.


App should warn user on actions that will clear game

The user should be warned if they select new game or Quit in the middle of an existing game.

Fixed in PR #6


add command: powershell.executeFile

This command should kick start a terminal and run powershell to execute the current script.

done!


Head tracking threshold

Hi, when i change my head direction (left to right and invert), i have a strange effect.
A little threshold i needed to detect new move direction.
This give me a bad feeling.

I have this problem in each samples.

Hi there,
What kind of a device do you have? Have you tried the Oculus apps - do they work well? Asking about Oculus because we use the Oculus SDK for head tracking.

Hi, yes oculus native apps works well and unity app too, perfect head tracking.
I have a note4 and gear vr stuff.
I m an unity dev, and i want to migrate to your framework, but i need to check some requirements.
I your samples, i have a little tracking effect when make little moves left to right.

No idea ?
Do you have the same problem ?

I have no idea. Will run few tests and probably come up with some logs that could help identify the problem.
In the meantime, could you let me know what happens if you change in activity_jni.h "typedef GVRActivityT GVRActivity;" to "typedef GVRActivityT GVRActivity;"? Thanks.

Hi perhaps a type mistake you want i change typedef to the same ?
I tried on change this :
//typedef GVRActivityT GVRActivity;
typedef GVRActivityT GVRActivity;
But no effect.

Yeah, I think those were the lines he was referring to.  The OculusHeadRotation line uses the Oculus code for sensor fusion and predicted head movement.  The KSensorHeadRotation uses code we originally had for sensor fusion.  We switched to the Oculus code because it had better prediction and filtering.  The OculusHeadRotation code is using the same vrapi any Oculus app ends up using so theoretically there shouldn't be any difference between a gvrf app and a native oculus app.
we're open to suggestions.

@ethernyEonian, your issue is rather unique and I don't know where to start. I can add logging to various places and the whole process will most likely take numerous iterations. Are you willing to help me out with testing various builds and sending back the logs?
Another suggestion: what happens if you run the samples without the phone being docked into GearVR? To allow the apps to run in this case, you can either enable developer mode in the GearVR Service or you could just comment out the line containing "com.samsung.android.vr.application.mode" in the android manifest.

Hi, yes i can send you logs. What i need to do ? Pull the new code and restart app ?
For you suggestion : i tried but it's difficult to see that on a little screen, but it seems to be the same.

For starters you can do a "adb shell dumpsys" and send me the output. I am having doubts your problem has anything to do with the head-tracking.
I will see what logs I can enable and add and will send you a link to a branch in my forked repo.

You could also capture the complete output of "adb logcat -v threadtime V:*" when you start some of the GVRF apps that exhibits the problem you describe.

could you give me an email address to send you my logs, i don't want to put this in public area. Thank you.

Sure, you can send to<EMAIL_ADDRESS>

Do you see this strange effect when you are moving your head left/right very slowly? Is it any different to when you move your head at normal speed? How about when you try to move fast?

When i do long moves (slow or fast) it's ok.
It's when i make little moves left to right like if you have a parkinson disease (very small moves).
I have a move log entry when i make long moves, but not with this kind of "parkinson disease" move.

@ethernyEonian, can you try this change request and see if it improves things?
https://github.com/Samsung/GearVRf/pull/268

Yes i tried.
It's better but i have always the problem but smaller
On Thu, Oct 8, 2015 at 7:47 PM, thomasflynn<EMAIL_ADDRESS>wrote:

@ethernyEonian https://github.com/ethernyEonian, can you try this
change request and see if it improves things?
#268 https://github.com/Samsung/GearVRf/pull/268
—
Reply to this email directly or view it on GitHub
https://github.com/Samsung/GearVRf/issues/262#issuecomment-146718119.

alright, well, perhaps we're on the right track.  merged the change.  Mihail is on PTO tomorrow, but he'll continue to work with you on this.

Hi, i m working of a use of your lib in clojure.
When i run the application i have this log :
Perhaps this talk you. I m lost :)
I checked the content of my apk and all is the same as in one of your final
sample apk.
D/NativeLibraryHelper(  925): Successfully fsync
/data/app/vmdl1746303542.tmp/lib/arm/libgvrf.so
D/NativeLibraryHelper(  925): Successfully fsync
/data/app/vmdl1746303542.tmp/lib/arm/libvrapi.so
I/ActivityManager(  925): Start proc
29792:com.samsung.android.app.vrsetupwizardstub/u0a43 for broadcast-3
com.samsung.android.app.vrsetupwizardstub/.system.PackageIntentReceiver
V/BroadcastQueue(  925): [background] Process cur broadcast
BroadcastRecord{10cc6702 u0 android.intent.action.PACKAGE_REMOVED}
DELIVERED for app ProcessRecord{1bf6a813
29792:com.samsung.android.app.vrsetupwizardstub/u0a43}
I/ActivityManager(  925): Start proc
29812:com.samsung.android.app.vrsetupwizard/u0a217 for broadcast-3
com.samsung.android.app.vrsetupwizard/.system.PackageIntentReceiver
V/BroadcastQueue(  925): [background] Process cur broadcast
BroadcastRecord{10cc6702 u0 android.intent.action.PACKAGE_REMOVED}
DELIVERED for app ProcessRecord{211df14e
29812:com.samsung.android.app.vrsetupwizard/u0a217}
D/RCPManagerService(  925):  PackageReceiver onReceive() bundle
Bundle[{com.samsung.android.vr.application.mode=vr_only}]
I/VrApi   (30001): ----------- vrapi_Initialize ----------
I/LocalPreferences(30001): ovr_InitLocalPreferences
D/OvrConsole(30001): !!#######!! Registering console receiver
D/VrApp   (30001): com.oculus.vrappframework.VrApp@3e7140d0 surfaceCreated()
I/VrApi   (30001): ---------- vrapi_EnterVrMode ----------
I/VrApi   (30001): vrapi_EnterVrMode: defaulting to docked due to lack of
dock events
I/VrApi   (30001): vrapi_EnterVrMode: defaulting to mounted due to lack of
mount events
F/art     (30001): sart/runtime/check_jni.cc:65]   native: #08 pc 0000a93c
/data/app/test.leindroid.sample.debug-2/lib/arm/libvrapi.so (???)
F/art     (30001): sart/runtime/check_jni.cc:65]   native: #09 pc 00010cdc
/data/app/test.leindroid.sample.debug-2/lib/arm/libvrapi.so
(vrapi_EnterVrMode+164)
F/art     (30001): sart/runtime/check_jni.cc:65]   native: #10 pc 0011a5e0
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::EnterVrMode()+144)
F/art     (30001): sart/runtime/check_jni.cc:65]   native: #11 pc 0011eb8c
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::HandleVrModeChanges()+72)
F/art     (30001): sart/runtime/check_jni.cc:65]   native: #12 pc 0011b15c
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::Command(char const*)+384)
F/art     (30001): sart/runtime/check_jni.cc:65]   native: #13 pc 0011c008
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::VrThreadFunction()+1104)
F/art     (30001): sart/runtime/check_jni.cc:65]   native: #14 pc 0011d3a8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::ThreadStarter(OVR::Thread*, void*)+8)
F/art     (30001): sart/runtime/check_jni.cc:65]   native: #15 pc 00139cc8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
F/art     (30001): sart/runtime/check_jni.cc:65]   native: #16 pc 0013a0d0
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #12 pc 0000a93c
/data/app/test.leindroid.sample.debug-2/lib/arm/libvrapi.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #13 pc 00010cdc
/data/app/test.leindroid.sample.debug-2/lib/arm/libvrapi.so
(vrapi_EnterVrMode+164)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #14 pc 0011a5e0
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::EnterVrMode()+144)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #15 pc 0011eb8c
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::HandleVrModeChanges()+72)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #16 pc 0011b15c
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::Command(char const*)+384)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #17 pc 0011c008
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::VrThreadFunction()+1104)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #18 pc 0011d3a8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::ThreadStarter(OVR::Thread*, void*)+8)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #19 pc 00139cc8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #20 pc 0013a0d0
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   at java.lang.String
com.oculus.vrapi.VrApi.getApplicationName(android.app.Activity)
(VrApi.java:183)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #02 pc 0013afb8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #03 pc 0013080c
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::ovrMessageQueue::PostMessage(char const*, bool, bool)+432)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #04 pc 00130ae4
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::ovrMessageQueue::SendPrintf(char const*, ...)+116)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #05 pc 00127a3d
/data/dalvik-cache/arm/data@app@test.leindroid.sample.debug-2<EMAIL_ADDRESS>(Java_com_oculus_vrappframework_VrApp_nativeSurfaceCreated__JLandroid_view_Surface_2+120)
F/art     (30001): sart/runtime/runtime.cc:292]   at
com.oculus.vrappframework.VrApp.nativeSurfaceCreated(Native method)
F/art     (30001): sart/runtime/runtime.cc:292]   at
com.oculus.vrappframework.VrApp.surfaceCreated(VrApp.java:75)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #12 pc 0000a93c
/data/app/test.leindroid.sample.debug-2/lib/arm/libvrapi.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #13 pc 00010cdc
/data/app/test.leindroid.sample.debug-2/lib/arm/libvrapi.so
(vrapi_EnterVrMode+164)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #14 pc 0011a5e0
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::EnterVrMode()+144)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #15 pc 0011eb8c
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::HandleVrModeChanges()+72)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #16 pc 0011b15c
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::Command(char const*)+384)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #17 pc 0011c008
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::VrThreadFunction()+1104)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #18 pc 0011d3a8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::ThreadStarter(OVR::Thread*, void*)+8)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #19 pc 00139cc8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #20 pc 0013a0d0
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #02 pc 0013afb8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #03 pc 00130ce8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::ovrMessageQueue::SleepUntilMessage()+72)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #04 pc 00130f30
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::TalkToJava::TtjThreadFunction()+292)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #05 pc 00130f74
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::TalkToJava::ThreadStarter(OVR::Thread*, void*)+32)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #06 pc 00139cc8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
F/art     (30001): sart/runtime/runtime.cc:292]   native: #07 pc 0013a0d0
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so (???)
I/DEBUG   (  328):     #11 pc 0000a93c
/data/app/test.leindroid.sample.debug-2/lib/arm/libvrapi.so
I/DEBUG   (  328):     #12 pc 00010cdc
/data/app/test.leindroid.sample.debug-2/lib/arm/libvrapi.so
(vrapi_EnterVrMode+164)
I/DEBUG   (  328):     #13 pc 0011a5e0
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::EnterVrMode()+144)
I/DEBUG   (  328):     #14 pc 0011eb8c
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::HandleVrModeChanges()+72)
I/DEBUG   (  328):     #15 pc 0011b15c
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::Command(char const*)+384)
I/DEBUG   (  328):     #16 pc 0011c008
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::VrThreadFunction()+1104)
I/DEBUG   (  328):     #17 pc 0011d3a8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
(OVR::AppLocal::ThreadStarter(OVR::Thread*, void*)+8)
I/DEBUG   (  328):     #18 pc 00139cc8
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
I/DEBUG   (  328):     #19 pc 0013a0d0
/data/app/test.leindroid.sample.debug-2/lib/arm/libgvrf.so
I/ActivityManager(  925): Killing
29792:com.samsung.android.app.vrsetupwizardstub/u0a43 (adj 15): emptyCount
##31
D/ActivityManager(  925): isAutoRunBlockedApp::
com.samsung.android.app.vrsetupwizardstub, Auto Run ON
I/ActivityManager(  925): Killing
29812:com.samsung.android.app.vrsetupwizard/u0a217 (adj 15): emptyCount ##31
D/ActivityManager(  925): isAutoRunBlockedApp::
com.samsung.android.app.vrsetupwizard, Auto Run ON
I/ActivityManager(  925): Start proc
30459:com.samsung.android.app.vrsetupwizardstub/u0a43 for broadcast-3
com.samsung.android.app.vrsetupwizardstub/.system.PackageIntentReceiver
V/BroadcastQueue(  925): [background] Process cur broadcast
BroadcastRecord{2e7c8489 u0 android.intent.action.PACKAGE_ADDED} DELIVERED
for app ProcessRecord{65c5c8e
30459:com.samsung.android.app.vrsetupwizardstub/u0a43}
I/ActivityManager(  925): Start proc
30478:com.samsung.android.app.vrsetupwizard/u0a217 for broadcast-3
com.samsung.android.app.vrsetupwizard/.system.PackageIntentReceiver
V/BroadcastQueue(  925): [background] Process cur broadcast
BroadcastRecord{2e7c8489 u0 android.intent.action.PACKAGE_ADDED} DELIVERED
for app ProcessRecord{23cc2354
30478:com.samsung.android.app.vrsetupwizard/u0a217}
I/ActivityManager(  925): Killing
30459:com.samsung.android.app.vrsetupwizardstub/u0a43 (adj 15): emptyCount
##31
D/ActivityManager(  925): isAutoRunBlockedApp::
com.samsung.android.app.vrsetupwizardstub, Auto Run ON
I/ActivityManager(  925): Killing
30478:com.samsung.android.app.vrsetupwizard/u0a217 (adj 15): emptyCount ##31
D/ActivityManager(  925): isAutoRunBlockedApp::
com.samsung.android.app.vrsetupwizard, Auto Run ON
I/ActivityManager(  925): Start proc
30968:com.samsung.android.app.vrsetupwizardstub/u0a43 for broadcast-3
com.samsung.android.app.vrsetupwizardstub/.system.PackageIntentReceiver
V/BroadcastQueue(  925): [background] Process cur broadcast
BroadcastRecord{1157a4f6 u0 android.intent.action.PACKAGE_REPLACED}
DELIVERED for app ProcessRecord{22d860f7
30968:com.samsung.android.app.vrsetupwizardstub/u0a43}
I/ActivityManager(  925): Start proc
30983:com.samsung.android.app.vrsetupwizard/u0a217 for broadcast-3
com.samsung.android.app.vrsetupwizard/.system.PackageIntentReceiver
V/BroadcastQueue(  925): [background] Process cur broadcast
BroadcastRecord{1157a4f6 u0 android.intent.action.PACKAGE_REPLACED}
DELIVERED for app ProcessRecord{39b6bb64
30983:com.samsung.android.app.vrsetupwizard/u0a217}
I/ActivityManager(  925): Killing
30968:com.samsung.android.app.vrsetupwizardstub/u0a43 (adj 15): emptyCount
##31
D/ActivityManager(  925): isAutoRunBlockedApp::
com.samsung.android.app.vrsetupwizardstub, Auto Run ON
I/ActivityManager(  925): Killing
30983:com.samsung.android.app.vrsetupwizard/u0a217 (adj 15): emptyCount ##31
D/ActivityManager(  925): isAutoRunBlockedApp::
com.samsung.android.app.vrsetupwizard, Auto Run ON
On Thu, Oct 8, 2015 at 9:08 PM, thomasflynn<EMAIL_ADDRESS>wrote:

alright, well, perhaps we're on the right track. merged the change. Mihail
is on PTO tomorrow, but he'll continue to work with you on this.
—
Reply to this email directly or view it on GitHub
https://github.com/Samsung/GearVRf/issues/262#issuecomment-146729458.

Any new for this issue ?

We found the low-hanging fruit and fixed that. I will continue to look into this but I don't have anything at the moment.

Cool thank you !
On Tue, Oct 13, 2015 at 11:48 AM, Mihail<EMAIL_ADDRESS>wrote:

We found the low-hanging fruit and fixed that. I will continue to look
into this but I don't have anything at the moment.
—
Reply to this email directly or view it on GitHub
https://github.com/Samsung/GearVRf/issues/262#issuecomment-147756400.

Hi again. I created a branch in my repo with an experimental commit that tries to improve the head-tracking latency further. It seems to slightly help but I am just not sensitive enough to be certain. Please let me know whether you see an improvement, if any. Thanks.
The repo&branch here: https://github.com/liaxim/GearVRf/tree/issue-262

We have applied the head-model too; pr #312.


[opentitantool] add commands to support ECDSA code-signing operations

Implement the ECDSA-equivalent commands for the same RSA operations currently supported.

Fixed by https://github.com/lowRISC/opentitan/pull/22576.
Fixed by https://github.com/lowRISC/opentitan/pull/21594.


BUG: utils.testing.get_locales()

Line 334: raw_locales = [] deletes the data received from locale_getter, so the return from this function is always a blank list.
  try:
        raw_locales = locale_getter()
    except:
        return None

    try:
        # raw_locales is "\n" seperated list of locales
        # it may contain non-decodable parts, so split
        # extract what we can and then rejoin.
        raw_locales = []
        for x in raw_locales:
            try:
                raw_locales.append(str(x, encoding=pd.options.display.encoding))
            except:
                pass
    except TypeError:
        pass

    if prefix is None:
        return _valid_locales(raw_locales, normalize)

    found = re.compile('%s.*' % prefix).findall('\n'.join(raw_locales))
    return _valid_locales(found, normalize)

https://github.com/pydata/pandas/blob/8d2818e32d0bbb50e183ccb5724c391e4f604670/pandas/util/testing.py#L334

it DOES run, but you have to override the locale; see the .travis.yml which sets the env variable which travis interprets.

see the install section: https://travis-ci.org/pydata/pandas/jobs/55924400

hmm, looking at the code it does seem that it is overriden...

I tried that in a test branch.  The problem is the code in pandas.utils.get_locales().
You get the locales:
raw_locales = locale_getter()
Next line that runs is:
raw_locales = []
So the function never returns any locales.
I made the fix in:
https://github.com/dstephens99/pandas/commit/4b1e35deb27d1795a5d269751d034f3196d6bff9
And the Travis test has a bunch of errors in TestGoogle (because it wasn't running before).
https://travis-ci.org/dstephens99/pandas/jobs/56178961

I'm fixing up the data-readers code, when I finish I'll make a pull request to update the pandas data / test_data code, then a pull request to fix this bug.

@dstephens99 ok, gr8!


fix: update default URL

Hey @john681611 this merge request is to update the default URL for the registry to now point at the main release rather than develop.


No dependencies returned when one of multiple build tools fails

When an analysis target has multiple build tools, and one of these build tools relates to a dependency analyser that either cannot be found, or is unsupported, Macaron will report no dependencies, thereby potentially discarding legitimate results from the others.
For example, apache/flink reveals two build tools: maven and pip. As pip is not supported, the dependencies found for maven are not returned and therefore not analysed.
A solution to this problem is to continue analysis when a build tool fails, as long as there is at least one other build tool that succeeds.

Closed via https://github.com/oracle/macaron/pull/748


Support for including Web Workers

My reference for this issue is Yew's multi_thread example which requires two WASM binaries. One for the actual application and one for the Web Worker.
Up until now building applications with web workers has been a real pain but with trunk we have the chance to turn this around.
Requirements
The following is an objective list of problems that need to be solved to support Web Workers.
1. Multiple binary targets
Trunk should handle crates with multiple binary targets gracefully.
Currently, invoking trunk serve on the aforementioned example results in this error:
could not read file `$TARGET/wasm32-unknown-unknown/debug/multi_thread.wasm`
📡 server running at http://<IP_ADDRESS>:8080/
  ❌ build finished with errors

The multi_thread.wasm could not be found because there are two WASM binaries called app.wasm and worker.wasm.
While it isn't strictly related to this issue, I think this behaviour could be improved.
2. Letting the app know where to find the Web Worker
Because of how Web Worker are created[link] we need to know the URL of the worker's Javascript file while compiling the app.
3. Building Web Workers with the required Javascript code to start them
Trunk currently runs wasm-bindgen with --target=web. The generated js code exports an initializer function which needs to be called to start the program. This doesn't work for Web Workers as they need to be self-executing.
Proposal
This is just one potential way of solving the issues mentioned above to get the discussion started.
Since Trunk already has a config file, I think it makes perfect sense to use it for this.
We add a new section to [build], let's call it "targets", which is used to configure binary targets.
To take care of 3., we can simply build the WASM with --target=no-modules.
Since we still want to have normal binaries, let's give each target a type key with the following two values:

"script" - The default value, this represents the current strategy.
Builds the binary with --target=web and includes it in index.html.
"worker" - The new strategy which builds the value with --target=no-modules.
The output is moved to dist/ but not added to index.html

For 2. we need to allow targets to side-step hashing so we can assign static URLs to them.
In the future this could use a similar approach to #9 so we don't miss out on caching, but for now we can just add a key "output" to the target which manually sets the output path.
This is what it would look like when applied to the multi_thread example:
[build.targets.app]
type = "script"

[build.targets.worker]
type = "worker"
output = "worker.js"

Trunk should reject projects with multiple binaries (without appropriate configuration) outright and point the user to documentation on the subject.
It might be tempting to guess which binary is which based on certain keywords (like "app" and "worker") but this probably does more harm than good in the long run.
This satisfies 1..

This is quite a high priority feature for Yew and I would love to help out with this.

@siku2 this is really excellent. Thanks for opening the issue. Everything you've proposed above makes sense, and seems quite doable. I would like to propose a slight modification.
One thing that I've been trying to stick to with the overall design of Trunk is to keep the required amount of config as minimal as possible, and wherever we can, keep assets & build instructions in the source HTML. I will admit that this pattern is obviously not best for everything, but it may actually work quite nicely with this web workers system.
drive from index.html
I would propose that we update the source HTML requirements to allow for the inclusion of the following pattern:
<html>
  <head>
    <link rel="trunk-app" data-trunk-bin="app" href="path/to/Cargo.toml"/>
    <link rel="trunk-worker" data-trunk-bin="worker" href="path/to/Cargo.toml"/>
  </head>
</html>

The implications of adopting this pattern is that we would no longer really need or want the --manifest-path or -p/--package options (which we were discussing elsewhere). This might be nice, as the only thing which users would need to be configured would be the path to the Cargo.toml and we are already using the cargo metadata crate which gives us the paths to the target dir and everything else we need, so that might be nice.
This would be a breaking change. However, now is the time for changes like that. I actually considered using this pattern originally, but I wasn't 100% sure about it. This new requirement for web workers definitely makes me lean more in that direction.
Now, to be sure, we will still have the Trunk.toml and such. This will just simplify things a bit so that users only need to have this info declared in their index.html file, and then they're off to the races.
questions / feedback

@siku2 (and anyone else): I'm interested to know what you think about rel="trunk-app" & data-trunk-bin="app" patterns.

does this sort of pattern make sense? Is it intuitive?
do you think we should adopt a different nomenclature? I like using the rel & data* attributes as they are standard HTML attributes, and and perfect for things of this nature. Doesn't diverge for normal HTML patterns.

@martinkavik any thoughts on the above items as well?

@siku2 this also makes me realize that we should be leveraging the info from cargo-metadata to determine the name bin for locating the WASM output. So far, I've just been a normalized form of the crate's name, however that will obviously not work in every case. I'll open a bug for this bit.

does this sort of pattern make sense? Is it intuitive?

I love the idea of using index.html as the main configuration source for "how to put the app together" and Trunk.toml mainly for command line flags.
There still needs to be an attribute to specify the output path to satisfy the second requirement.
The only nitpick I have is that "href" should be optional and if specified, may point to the parent directory of  Cargo.toml instead so as to minimise verbosity.
The same idea could be used for the path to index.html so that  trunk -- some/path is the same as trunk -- some/path/index.html if some/path is a directory.
This would remove the need for a --package flag entirely (assuming that the dist dir is relative to index.html).

There still needs to be an attribute to specify the output path to satisfy the second requirement.

Do you mind expounding a bit more on what our requirements are for this? Mainly:

outside of the context of Trunk, how were workers loaded previously in the Yew ecosystem?
isn't it still required that there be a JS loader which loads & executes the WASM Worker?
if the above is true, then wouldn't it be fine to continue to compile the worker with --target=web (as that would handle the importing and initialization)?
it seems that such is not the case based on your statements above, so what am I overlooking?

As far as the optional href bits, I can agree. I am tempted to say that the entire <link .../> should be optional, and it should just default to the cargo package in the CWD, and use the default bin for that package.

for multiple bins, the user will be directed to include a link in the HTML with the appropriate rel="trunk-app" data-trunk-bin="binfoo" attrs.
then we can have a nice sane default (package in CWD), drop the --manifest-path/-p/--package opts, and the only thing the user will normally need to point to is the index.html if it is not in the CWD.

Agreed on supporting the pattern of pointing to the dir of the index.html. Same for Cargo.toml.

This would remove the need for a --package flag entirely (assuming that the dist dir is relative to index.html).

Agreed that it would remove the need for the --package flag; however the dist dir currently defaults to the CWD. I'm tempted to say that the most logical default would be the parent dir of the Cargo.toml given that the location of the index.html can change from project to project. Having it default to the parent dir of the Cargo.toml would potentially cut down on surprises even more. The two locations will be the same a majority of the time as well, I would wager.

outside of the context of Trunk, how were workers loaded previously in the Yew ecosystem?

The worker binary is generated using:
wasm-bindgen --target no-modules --out-name worker  path/to/wasm

The output is then included in the server directory.
When we want to start the Web Worker we call new Worker("/worker.js") where "/worker.js" is the URL of the js file generated by the previous command.
The app needs to know the exact location of the worker script in order to start it. The easiest way to achieve this for now is through 2..

isn't it still required that there be a JS loader which loads & executes the WASM Worker?

Yes, but Yew already handles this internally. This isn't something I think Trunk should do automatically because Web Workers are very often created dynamically.

if the above is true, then wouldn't it be fine to continue to compile the worker with --target=web (as that would handle the importing and initialization)?

No, we're talking about the worker itself here. The worker script needs to set up everything by itself, we don't have the ability to call the "init" function. --target=no-modules uses an IIFE to self-execute.

As far as the optional href bits, I can agree. I am tempted to say that the entire <link .../> should be optional, and it should just default to the cargo package in the CWD, and use the default bin for that package.

It should definitely be optional! No need to introduce the complexity for simple apps.

I'm tempted to say that the most logical default would be the parent dir of the Cargo.toml given that the location of the index.html can change from project to project. Having it default to the parent dir of the Cargo.toml would potentially cut down on surprises even more. The two locations will be the same a majority of the time as well, I would wager.

The issue there is that you might want to support something like this in the future:
my_app/
  src/
  Cargo.toml

my_worker/
  src/
  Cargo.toml

index.html

where index.html contains:
<link rel="trunk-app" href="my_app" />
<link rel="trunk-worker" href="my_worker" />

Where do you place the dist directory now?
I realize my suggestion of placing it relative to the index file isn't ideal for a setup like this:
static/
  index.html

src/

Cargo.toml

which would result in static/dist...
For now I guess placing it relative to Cargo.toml is the better option.

@MartinKavik any thoughts on the above items as well?

I would definitely use index.html instead of commands / config files to make the configuration more declarative and to keep it in one place.

However HTML is pretty dangerous because it's untyped so we will need good linters and error messages in the future and make it as simple as possible. (That's why I was planning to use Rust instead of HTML in Seeder btw.)

According to MDN docs - "WebAssembly is not yet integrated with

For now I guess placing it relative to Cargo.toml is the better option.

@siku2 your example of having two different crates — one for the app and another for the worker —  is definitely a good one, and I had considered that, and I drew the same conclusion you did, so sounds like that may indeed be best.

The biggest problem with no-modules is that it doesn't support JS snippets.

@siku2 thanks for all of the info on the worker setup and all. That makes sense. I'll do some experimentation to see if there may be a simple way to solve these issues. Hopefully we can cross this bridge without a JS bundler ... we'll see.

@MartinKavik great feedback. I agree on most points.

it looks like the preferred tag should be script instead of link to make it future-proof

The main reason I chose to use links here is because ultimately the output HTML (which is what the browser will load) doesn't even include the links at all. Trunk uses the links as "directives" but then removes them from the DOM and then writes the script tag for the JS loader, indirectly loading the WASM. So I think in this case, we might already be doing what you suggested. The links are ultimately transformed into script tags by Trunk.

Ok, a distillation of action items so far coming in my next comment:

Ok, one more item of discussion here. Related to some general ideas in #3, some from #28, I'm thinking that we might want to do for the HTML portion of these updates is to stick with <link ...> as much as possible, which will typically then be transformed into some other HTML in the end.
Right now, Trunk only uses the special rel="trunk-dist" when linking to a resource which should just be copied into the dist dir, and then removed from the HTML. We definitely want a general pattern which will survive growth and evolution. As such, perhaps we just keep this as simple as possible, while leaving room for growth, and go with rel="rust". This link type could support the following data-* attrs:

data-bin="{binName}": an optional attr which declares the specific bin to be included. This would be superfluous for single-bin crates. It can be omitted and will just default to the one bin of the crate. If the crate has 0 or more than 1 bins, Trunk will emit an error with some help info on what to do.
data-worker: an optional attr which takes no value. In combination with data-bin, it denotes that the specified bin should be included as a web worker. If this is not specified, then the Rust bin will be treated as the app entrypoint. Trunk will emit an error if more than 1 entrypoints exist.

With the above proposal, the HTML links would now look like this:
<html>
  <head>
    <link rel="rust" data-bin="app" href="path/to/Cargo.toml"/>
    <link rel="rust" data-bin="worker" data-worker href="path/to/Cargo.toml"/>
  </head>
</html>

I know that specifying an href= can seem tedious ... but as I've analyzed all of the different possibilities here, I feel like it is a small price to pay to just require the href= attr, and sidestep the many misconfiguration & confusion issues over defaults, paths and all that. The href will always be relative to the index.html itself.
This pattern will then set the precedent for future link types. Potentially including WASM modules from other languages. Transpiled JS/TS ... whatever. Simple links with simple rel attrs, and then data attrs which can customize their behavior.
Thoughts?

A fucking killer combo on the above for JS/TS would be:
<link rel="js" data-build-command="build" data-watch="js/src,ts/src" href="path/to/package.json"/>

With this, Trunk would be able to build JS & TS apps (or any other JS offshoot language), and include their artifacts in the dist dir, and also properly reference the web-ready JS (hashed and all) in the output HTML.

rel="js" would cover standard JS, TS and pretty much any other JS offshoot language, as long as it includes a package.json and has a script (in the package.json) which can be reliably invoked to produce an artifact.
data-build-script="{script}" would be an optional package.json script, defaulting to build. So npm run build practically speaking.
data-watch={path,path,path} would be a set of comma-separated paths for Trunk to watch which will trigger builds specifically for the JS app when changes are detected under the specified paths.

This is the first JS/TS integration option which I've felt ok about. Hype!

I'll do some experimentation to see if there may be a simple way to solve these issues. Hopefully we can cross this bridge without a JS bundler ... we'll see.

I think using no-modules for now is perfectly fine because that's what we've been using so far. I'll do some more testing on this end too!

Right now, Trunk only uses the special <link rel="trunk-dist" href=".."/> when linking to a resource which should just be copied into the dist dir, and is then removed from the HTML. We definitely want a general pattern which will survive growth and evolution. As such, perhaps we just keep this as simple as possible and go with rel="rust". This link type could support the following data-* attrs:

Perhaps, to avoid confusion, we could use a custom element like <trunk-link rel="dist" href=".." />. This is still perfectly valid HTML and allows us to use custom attributes without the data- prefix which makes it more flexible.
The main benefit here is that this creates a visible contrast between the parts that will be included in the final HTML file and the parts that are stripped by Trunk.
Additionally, when a user tries to use the index.html file outside of trunk it will generate a less confusing error message.
Speaking of errors, this should make the creation of a trunk check type of lint easier because we have a distinction between "normal" HTML and special syntax for trunk.
It's also not necessary to use the custom element for everything. For instance, it makes sense for trunk to handle Sass in <link> tags implicitly.
Other than that, I really like this approach!

know that specifying an href= can seem tedious ... but as I've analyzed all of the different possibilities here, I feel like it is a small price to pay to just require the href= attr. What we gain is that we sidestep the many misconfigurations and confusions over defaults, what is actually being referred to &c. The href will always be relative to the index.html itself. This will also make it intuitive for being able to include the app from one crate, and then potentially multiple workers from other crates.

I don't see how there is any chance for misconfiguration by making href optional. In most cases href is just "./Cargo.toml" or even worse just "." if we allow specifying the parent directory.
The only case where specifying the Cargo.toml explicitly is necessary is when there are crates that aren't part of the same  workspaces.
If we look at the example I used before:
my_app/
  src/
  Cargo.toml

my_worker/
  src/
  Cargo.toml

Cargo.toml  <- added this file to define the workspace
index.html

Thanks to the workspace, running cargo build --bin my_app works in the root directory.
So the following index.html should work:
<html>
  <head>
    <!-- Using the custom element proposal from above -->
    <trunk-link type="rust" bin="my_app" />
    <trunk-link type="rust" bin="my_worker" data-worker />
  </head>
</html>

I think this is much cleaner than this:
<html>
  <head>
    <link rel="rust" bin="my_app" href="./my_app/Cargo.toml" />
    <link rel="rust" bin="my_worker" data-worker href="./my_worker/Cargo.toml" />
  </head>
</html>

It's even worse when we're dealing with a single crate with multiple binary targets because then href just lists the same path twice (or more if we have multiple workers).

I feel like we haven't really tackled the second issue yet.
Some alternative approaches I've considered:

Having trunk set an environment variable with the name of the output and using the env!() to read it at compile-time has the problem that Rust doesn't automatically detect changes to env vars unless explicitly forcing it using a build script.
Writing an element into the HTML file which is then read at runtime causes unnecessary overhead and end up being very verbose.

So, the way I see it, until we have the trunk library which can take care of this, using a pre-determined output name is the best solution.

And finally:

imagine we've split our app into WASM parts to improve performance by lazy loading - what is "app" and "worker" in this example? I would declare them the same way, only allow to optionally "mark" one of them as the main/entry/start/mount point

@MartinKavik makes a good point here. The reason I singled out Web Workers here is because of their special requirements.
Other types of binaries don't necessarily have to:

be self-executing
avoid using ES6 modules because many browsers don't yet support it

Having a "preset" for workers seems very reasonable because of this.
This isn't to say that we shouldn't support other types, but depending on what they do they might have entirely different requirements.
One potential use case I can think of is using a separate binary as a library which is loaded at runtime. In this case we would want it to be compiled with --target=web so we can using it as an ES6 module.
With the current design it should be fairly easy to add such a functionality in the future.

Ok, once #73 lands, @siku2 this feature will be ready to implement. I've already got the src/pipelines/rust_worker.rs module in place as a placeholder for when we are ready to hack on this.

Just to mention that an implementation which is compatible with audio worklets (which are somewhat similar to web workers but may have some specific scope restrictions) would be very cool.

@rfwatson do you mind sharing some info on what you would expect Trunk to need to do in order to support audio worklets? If you want to open a new issue for it as well, that would be fine. Once I have some additional cycles I'll of course do some research on this :). Thanks in advance.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4238

Questions ?
Please refer to the Backport tool documentation


Number of parameter doesn't match the paper; plus init_weights doesn't initialize bias weights

In table 1 of the original paper - 'Large Scale GAN Training for High Fidelity Natural Image Synthesis' the authors claim number of parameters to be in the range of 80M while this repository reports only about 4.3M parameters for 32X32 images i.e. CIFAR-10 images. Do anyone know where this discrepancy is cropping in from?
Also the init_weights function in the BigGAN.py only initializes the weight parameters. One should also initialize the bias parameters.
Finally I fail to assert which dataset Table1 of the the original paper - 'Large Scale GAN Training for High Fidelity Natural Image Synthesis' refers to.

Param nums
Reported parameter counts are for models at the relevant resolutions. Models for lower resolutions have fewer layers, can be less wide, and therefore have fewer parameters.

init_weights
The biases are already zero-initialized, there's no need to override their inits.

table 1
Table 1 is for ImageNet, the primary dataset used in the paper.


I want to contribute but...

Can you write something about how to run the project? I guess the .env.example file is not finished yet, or I didn't understand it. :D

Sure, I'll add the .env.example properly

I've added them kindly let me know if you have any other questions.

Thank you


JavaCodeCompletion module fails to compile because of API change

It seems that an API change on JDT.LS project is incompatible with our codebase.

To solve that, I'm going to split this into 2 sub-tasks:

Using the tag version 1.23.0 instead of the snapshot one. That will solve the issue.
Unfortunately, tagged versions get stale after some months (see https://github.com/eclipse/eclipse.jdt.ls/issues/1970) So, we need to update our codebase accordingly with the API changes

### Acceptance criteria
- [ ] https://github.com/kiegroup/kie-tools/pull/1626
- [ ] https://github.com/kiegroup/kie-tools/pull/1663
- [ ] https://github.com/kiegroup/kie-tools/pull/1688
- [ ] Update our codebase accordingly with the API changes (Using TypeHierarchy message?)

Duplicate

Waiting on https://github.com/eclipse/eclipse.jdt.ls/pull/2033


fix(namespace): didn't reload namespaces from DB after the full sync

Namespaces would store inside DB if the repl-namespace-enabled was set to yes.
Then replicas will intercept and parse the increment replication log to
see if it needs to reload namespaces. But it won't have the namespace update log
when doing the full sync, so we need to reload from DB once the full replication is done.
This closes #2520

But it won't have the namespace update log when doing the full sync, so we need to reload from DB once the full replication is done.

Can you point out the reason here?

But it won't have the namespace update log when doing the full sync, so we need to reload from DB once the full replication is done.

Can you point out the reason here?

What's the meaning of this comment? Do you mean why the full sync won't propagate the namespace change log?

Do you mean why the full sync won't propagate the namespace change log?


Fix wrapping column issue on the home page

Fixes https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/pull/1814#issuecomment-1157177386

Deploying as 2.69.0


Apply License

We are missing a LICENSE for the project.

want to talk with Catherine about this @joeydong ?


ALF Automation

Brackets: Please merge this pull request created by ALF. @ArturOledzki @pantkowiak @rajjain FYI

Travis is again failing here because of the API limit. I am going ahead with the merge as it is a single string change.


Windows Dockerfile example?

Do you guys know if you can run the dockerfile from a windows host?  Not really an issue I guess but not sure where to ask / put this request?
Thanks

Hey @ril3y! I'm not too familiar with docker but @EderSantana might be of help as he wrote the original file

I've tested docker on mac and linux. the way it works on mac should be similar to what it does on windows. You will install a virtual machine and the docker container will use to create an Ubuntu environment for you.

Yah I have ran docker on Windows and it works pretty well. I was more
wondering about how to get the ui to work with Windows windowing system. I
will see if I can get it working. Thanks
On Sun, Oct 2, 2016, 3:26 PM Eder Santana<EMAIL_ADDRESS>wrote:

I've tested docker on mac and linux. the way it works on mac should be
similar to what it does on windows. You will install a virtual machine and
the docker container will use to create an Ubuntu environment for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ntasfi/PyGame-Learning-Environment/issues/19#issuecomment-250989957,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOJMzBlzbMwlKRR6yswGjpw3-Lf09dCks5qwAVegaJpZM4KJgCg
.

oh, I see. Well I have never used X11 forwarding on windows. But I saw friends doing that before. there must be a way(tm)
let us know if you find it :)

Closing because of inactivity.


[CP] [Impeller] Fix stroke cap drawing not correct

issue_link
https://github.com/flutter/flutter/issues/119810
Commit Hash
24fd06e
Target
stable
pr_link
https://github.com/flutter/engine/pull/39481
Impacted Users
For user using impeller to draw path
Impact Description
Impact when user uses impeller to draw stroke path. Without this patch they will see a one-side cap, which is not expected

Workaround
Seems no workaround.
Risk
low
Test Coverage
yes
Validation Steps
Using impeller to draw a stroke path, and set the cap to StrokeCap.round,  expected to see both side cap rendering is good.
void main() {
  runApp(CustomPaint(
    painter: MyPainter(),
  ));
}

class MyPainter extends CustomPainter {
  @override
  void paint(Canvas canvas, Size size) {
    Paint paint = Paint()
      ..color = Colors.red
      ..strokeWidth = 20
      ..strokeCap = StrokeCap.round;
    canvas.drawLine(const Offset(100, 100), const Offset(200, 100), paint);
  }

  @override
  bool shouldRepaint(covariant CustomPainter oldDelegate) {
    return true;
  }
}

cc @zanderso @bdero

Friendly ping for @zanderso, @bdero or @jonahwilliams to take a look at this cherry-pick.

This was a good fix, but since it is late in the cycle, and the fix is available in betas 3.8 and 3.9 (and soon 3.10), the risk/benefit speaks against accepting this CP against 3.7, even though the risk is likely very small. So I would say not lgtm, but big thanks to @luckysmg for spotting this and fixing it. Our next stable will be very polished!

Thanks for the feedback @zanderso and thank you for the cherry-pick request @luckysmg, closing this cherry-pick request.


Remove async/await

It'd be nicer on users if it were written in ES5 promises. Related to https://github.com/ianstormtaylor/metascraper/issues/7. Current implementation relies on a regenerator runtime from Babel to support async/await.

Fixed in 0.1.1!

Awesome, cheers 😄