Undefined symbol when importing pyecvl.ecvl

Hi!
After following the documentation and installing pyecvl(0.3.0) successfully, the following error appears when importing pyecvl.ecvl:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages/pyecvl-0.3.0-py3.8-linux-x86_64.egg/pyecvl/ecvl.py", line 21, in <module>
    from . import _core
ImportError: /home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages/pyecvl-0.3.0-py3.8-linux-x86_64.egg/pyecvl/_core.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZN4ecvl17AugmentationParam3re_E

Seems that something is wrong with the binding. Does it have any quick solution?

That symbol comes from libecvl_eddl, an optional ECVL library that adds support for EDDL. Have you installed ECVL 0.2.1 with EDDL support (i.e., with the -DECVL_BUILD_EDDL=ON CMake setting)? If not, you should disable EDDL support in PyECVL by exporting the ECVL_EDDL environment variable to off or false.

Hi, Simone.
You were right. Something failed linking libecvl_eddl . Once made that and checked everything that you told me this is the output of running python3 setup.py install
running install
running bdist_egg
running egg_info
writing pyecvl.egg-info/PKG-INFO
writing dependency_links to pyecvl.egg-info/dependency_links.txt
writing requirements to pyecvl.egg-info/requires.txt
writing top-level names to pyecvl.egg-info/top_level.txt
reading manifest file 'pyecvl.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'pyecvl.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
running build_ext
building 'pyecvl._core' extension
/usr/bin/gcc-8 -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Isrc -I/home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages/pybind11/include -I/home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages/pybind11/include -I/home/rasanro1/installs/install_eddl/include -I/home/rasanro1/installs/install_ecvl/include -I/home/rasanro1/.conda/envs/eddl/include/python3.8 -c src/_core.cpp -o build/temp.linux-x86_64-3.8/src/_core.o -std=c++17 -fvisibility=hidden -DECVL_WITH_DICOM -DECVL_EDDL
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
In file included from src/_core.cpp:5:
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h: In constructor ‘ecvl::Image::Image()’:
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h:160:33: warning: ‘ecvl::Image::spacings_’ will be initialized after [-Wreorder]
     std::vector<float>          spacings_;          /**< @brief Space between pixels/voxels. */
                                 ^~~~~~~~~
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h:125:33: warning:   ‘std::vector<int> ecvl::Image::strides_’ [-Wreorder]
     std::vector<int>            strides_;           /**< @brief Vector of Image strides. */
                                 ^~~~~~~~
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h:260:5: warning:   when initialized here [-Wreorder]
     Image() :
     ^~~~~
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h: In constructor ‘ecvl::Image::Image(const std::vector<int>&, ecvl::DataType, std::__cxx11::string, ecvl::ColorType, const std::vector<float>&, ecvl::Device)’:
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h:160:33: warning: ‘ecvl::Image::spacings_’ will be initialized after [-Wreorder]
     std::vector<float>          spacings_;          /**< @brief Space between pixels/voxels. */
                                 ^~~~~~~~~
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h:125:33: warning:   ‘std::vector<int> ecvl::Image::strides_’ [-Wreorder]
     std::vector<int>            strides_;           /**< @brief Vector of Image strides. */
                                 ^~~~~~~~
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h:281:5: warning:   when initialized here [-Wreorder]
     Image(const std::vector<int>& dims, DataType elemtype, std::string channels, ColorType colortype,
     ^~~~~
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h: In copy constructor ‘ecvl::Image::Image(const ecvl::Image&)’:
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h:160:33: warning: ‘ecvl::Image::spacings_’ will be initialized after [-Wreorder]
     std::vector<float>          spacings_;          /**< @brief Space between pixels/voxels. */
                                 ^~~~~~~~~
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h:125:33: warning:   ‘std::vector<int> ecvl::Image::strides_’ [-Wreorder]
     std::vector<int>            strides_;           /**< @brief Vector of Image strides. */
                                 ^~~~~~~~
/home/rasanro1/installs/install_ecvl/include/ecvl/core/image.h:309:5: warning:   when initialized here [-Wreorder]
     Image(const Image& img) :
     ^~~~~
In file included from src/func_binder.hpp:28,
                 from src/_core.cpp:7:
/home/rasanro1/installs/install_ecvl/include/ecvl/support_eddl.h: In constructor ‘ecvl::DLDataset::DLDataset(const std::filesystem::__cxx11::path&, int, ecvl::DatasetAugmentations, ecvl::ColorType, ecvl::ColorType, bool)’:
/home/rasanro1/installs/install_ecvl/include/ecvl/support_eddl.h:70:26: warning: ‘ecvl::DLDataset::augs_’ will be initialized after [-Wreorder]
     DatasetAugmentations augs_; /**< @brief ecvl::DatasetAugmentations to be applied to the Dataset images (and ground truth if exist) for each split. */
                          ^~~~~
/home/rasanro1/installs/install_ecvl/include/ecvl/support_eddl.h:68:15: warning:   ‘ecvl::ColorType ecvl::DLDataset::ctype_’ [-Wreorder]
     ColorType ctype_; /**< @brief ecvl::ColorType of the Dataset images. */
               ^~~~~~
In file included from src/func_binder.hpp:28,
                 from src/_core.cpp:7:
/home/rasanro1/installs/install_ecvl/include/ecvl/support_eddl.h:81:5: warning:   when initialized here [-Wreorder]
     DLDataset(const std::filesystem::path& filename,
     ^~~~~~~~~
/usr/bin/g++-8 -pthread -shared -B /home/rasanro1/.conda/envs/eddl/compiler_compat -L/home/rasanro1/.conda/envs/eddl/lib -Wl,-rpath=/home/rasanro1/.conda/envs/eddl/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/src/_core.o -L/home/rasanro1/installs/install_opencv/lib -L/home/rasanro1/installs/install_eddl/lib -L/home/rasanro1/installs/install_ecvl/lib -Wl,-R/home/rasanro1/installs/install_eddl/lib -Wl,-R/home/rasanro1/installs/install_ecvl/lib -ldataset -lecvl_core -lopencv_core -lopencv_imgcodecs -lopencv_imgproc -lopencv_photo -lstdc++fs -lyaml-cpp -ldcmdata -ldcmimage -ldcmimgle -ldcmjpeg -li2d -lijg8 -lijg12 -lijg16 -loflog -lofstd -lecvl_eddl -leddl -o build/lib.linux-x86_64-3.8/pyecvl/_core.cpython-38-x86_64-linux-gnu.so
/home/rasanro1/.conda/envs/eddl/compiler_compat/ld: /home/rasanro1/installs/install_opencv/lib/libopencv_imgproc.so: .dynsym local symbol at index 2 (>= sh_info of 2)
/home/rasanro1/.conda/envs/eddl/compiler_compat/ld: /home/rasanro1/installs/install_opencv/lib/libopencv_imgproc.so: .dynsym local symbol at index 3 (>= sh_info of 2)
/home/rasanro1/.conda/envs/eddl/compiler_compat/ld: /home/rasanro1/installs/install_opencv/lib/libopencv_imgproc.so: .dynsym local symbol at index 4 (>= sh_info of 2)
/home/rasanro1/.conda/envs/eddl/compiler_compat/ld: /home/rasanro1/installs/install_opencv/lib/libopencv_photo.so: .dynsym local symbol at index 2 (>= sh_info of 2)
/home/rasanro1/.conda/envs/eddl/compiler_compat/ld: /home/rasanro1/installs/install_opencv/lib/libopencv_photo.so: .dynsym local symbol at index 3 (>= sh_info of 2)
/home/rasanro1/.conda/envs/eddl/compiler_compat/ld: /home/rasanro1/installs/install_opencv/lib/libopencv_photo.so: .dynsym local symbol at index 4 (>= sh_info of 2)
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/pyecvl
copying build/lib.linux-x86_64-3.8/pyecvl/version.py -> build/bdist.linux-x86_64/egg/pyecvl
copying build/lib.linux-x86_64-3.8/pyecvl/_core.cpython-38-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/egg/pyecvl
copying build/lib.linux-x86_64-3.8/pyecvl/__init__.py -> build/bdist.linux-x86_64/egg/pyecvl
copying build/lib.linux-x86_64-3.8/pyecvl/ecvl.py -> build/bdist.linux-x86_64/egg/pyecvl
byte-compiling build/bdist.linux-x86_64/egg/pyecvl/version.py to version.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/pyecvl/__init__.py to __init__.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/pyecvl/ecvl.py to ecvl.cpython-38.pyc
creating stub loader for pyecvl/_core.cpython-38-x86_64-linux-gnu.so
byte-compiling build/bdist.linux-x86_64/egg/pyecvl/_core.py to _core.cpython-38.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying pyecvl.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying pyecvl.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying pyecvl.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying pyecvl.egg-info/not-zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
copying pyecvl.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying pyecvl.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt
creating dist
creating 'dist/pyecvl-0.3.0-py3.8-linux-x86_64.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing pyecvl-0.3.0-py3.8-linux-x86_64.egg
creating /home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages/pyecvl-0.3.0-py3.8-linux-x86_64.egg
Extracting pyecvl-0.3.0-py3.8-linux-x86_64.egg to /home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages
Adding pyecvl 0.3.0 to easy-install.pth file

Installed /home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages/pyecvl-0.3.0-py3.8-linux-x86_64.egg
Processing dependencies for pyecvl==0.3.0
Searching for numpy==1.18.4
Best match: numpy 1.18.4
Adding numpy 1.18.4 to easy-install.pth file
Installing f2py script to /home/rasanro1/.conda/envs/eddl/bin
Installing f2py3 script to /home/rasanro1/.conda/envs/eddl/bin
Installing f2py3.8 script to /home/rasanro1/.conda/envs/eddl/bin

Using /home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages
Searching for pybind11==2.5.0
Best match: pybind11 2.5.0
Adding pybind11 2.5.0 to easy-install.pth file

Using /home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages
Searching for setuptools==46.4.0.post20200518
Best match: setuptools 46.4.0.post20200518
Adding setuptools 46.4.0.post20200518 to easy-install.pth file
Installing easy_install script to /home/rasanro1/.conda/envs/eddl/bin

Using /home/rasanro1/.conda/envs/eddl/lib/python3.8/site-packages
Finished processing dependencies for pyecvl==0.3.0

When trying to import now import pyeddl.eddl the following error appears:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/rasanro1/temp/pyecvl/pyecvl/ecvl.py", line 21, in <module>
    from . import _core
ImportError: cannot import name '_core' from 'pyecvl' (/home/rasanro1/temp/pyecvl/pyecvl/__init__.py)

Any idea on this error?

Are you in the pyecvl source directory? Move to some other directory and try the import again. If you are in the source directory, the local pyecvl dir takes precedence, and naturally there is no extension file there.

That was it!
Thanks a lot. I'm closing the issue.


extension config should consider  different operating systems

VS code version: 1.32.2
OS version: windows 10
feature description：
Because:
I use sync-setting extension, but sync config have a little problem.
for example, the markdown-pdf extension require chrome runtime. chrome file path setting to markdown-pdf:executablePath key, but different systems have different file path, so sync-setting extension synced the value of markdown-pdf:executablePath key is invalid. there are many similar config key of plugins：gitProjectManager.baseProjectsFolders path，prolog.executablePath path,
terminal.integrated.shell.windows path, and so on.
So:
I think the question have two solution.
one, extension author coding related config path, add multiple path configuration items，take markdown-pdf extension as an example, the config relate path：
{
   "win32ExecutablePath": "C:\\application\\chrome.exe",
   "linuxExecutablePath": "/usr/bin/chrome",
   "osxExecutablePath": "/usr/bin/chrome"
}

two. vscode provide built-in support, detail: extension author declare the config item:runTimePath to FilePath type. vscode mapping to filePath Object for the value runTimePath config item that user input to setting UI interface.
filePath Object example:
{
   // os type: Specific path
   "win32": "C:\\application\\xx.exe"
}

Everything for the sync-setting.
End

label should add to sync-setting.

Please file issue against https://github.com/shanalikhan/code-settings-sync/issues


Port changes to TLS docs from #2597

Noticed a couple typos that I fixed in this PR(AE setting commented out in the TLS section and fixed header), so we'll want to pull those over into the 1.9 branch to resolve merge conflicts.

Originally posted by @kelseiv in https://github.com/influxdata/docs-v2/pull/2597#discussion_r639331403

See #2597.


New user does not have access to the entire dashboard history

First install on linux Debian Buster
cd /usr/local/bin/
sudo wget -O /usr/local/bin/gitea https://dl.gitea.io/gitea/1.9.4/gitea-1.9.4-linux-amd64
Then Ugrade :
sudo wget -O /usr/local/bin/gitea https://dl.gitea.io/gitea/1.10.0-rc1/gitea-1.10.0-rc1-linux-amd64
And :
sudo wget -O /usr/local/bin/gitea https://dl.gitea.io/gitea/1.10.2/gitea-1.10.2-linux-amd64
Gitea : 1.10.2 built with GNU Make 4.1, go1.13.5 : bindata, sqlite, sqlite_unlock_notify
Git : 2.20.1

[ ] MSSQL -> I use MariaDB

Can you reproduce the bug at https://try.gitea.io:

[ ] No because i'm not admin, i can't create :
First a Organisation,
Then add a dépot to the Organisation,
Then create a group and add user, make commits ..

Now, create a new user, and, add the new user to the group.
The new user can't see the old history from dashboard
If a new commit income, new user can see the new commit from dashboard
My tutorial for install Gitea (in french) :
https://wiki.visionduweb.fr/index.php?title=Installer_un_serveur_Git_avec_Gitea#Installer_Gitea_depuis_les_sources
Step for log :
https://docs.gitea.io/en-us/logging-configuration/
I did not understand well, nor advanced in this direction. The logs therefore remain obscure. If necessary, please accompany me to obtain the desired logs.

.. add user to organisation team

Now, create a new user, and, add the new user to organisation team.
The new user can't see the old history from dashboard

The dashboard is for user notifications, not for a project's history. It's normal that a user starts with no notifications.

Ok, in use, it can be understood as well.
I had felt it, for that I had tested to push two new commit, which were well visible.
On the other hand, it is not so obvious to note, once we have a few users who are all well notified, on the dashboard, and, that a new user, him, arrives with an empty space.
I spent a lot of time figuring out how to update the information for the new user, thinking, along the lines of other users, that I could do something.
So it's not a bug, so much the better.
It seems "obvious" now.
I remain on my hunger by thinking that I could have allowed this new user to get the history from his dashboard.

think we can close this issue?


Best approach for removing circular references

I have a scenario where I save a model with associations to another scope variable. Theres is a deep watch - $scope.$watch('thing', true) - on this variable that MUST remain.
Since my model has associations, there are circular references to its parents, children, etc. This causes a maximum callstack error in angular.
What is the best approach to "serialize" the model in this instance - what I want is the model properties only and no associations.

You can serialize the model using $encode (is not really serializing, is making it a plain object). That should get rid of every circular reference to associations, scopes, types, etc.

Closing as solved.


Helm plugin usage drops kube-context flag

Hello,
According to this page, the flag kube-context is dropped when using a plugin:
https://github.com/helm/helm/blob/master/docs/plugins.md
Can anyone explain the reason?
Thanks!

The context is dropped because with the useTunnel flag, a tunnel to Tiller is provided.
Is there a particular use case where this flag might be useful for a Helm plugin?


Ban Shadow Tag from Monotype

http://www.smogon.com/forums/threads/sm-monotype-suspect-shadow-tag.3618857/page-3#post-7559213

Oh well

ok thanks @TheImmortal for sniping me


defineStore doesn't respect readonly ref returned from storeSetup fn

Reproduction
Define a store
// myStore.js
import { defineStore } from 'pinia'
import { ref, readonly } from 'vue'

export default defineStore('myStore', () => {
  const x = ref(0)
  // ..
  return { x: readonly(x) }  // << readonly
})

Then consume the store
<!-- App.vue -->
<script setup>
import useMyStore from './path/to/myStore.js'
const store = useMyStore()
</script>
<template>
  <a @click='++store.x'> {{ store.x }} </a>
  <!-- what happens if users click to mutate a readonly ref ? -->
</template>

Expected behavior
I expected that vue will show warnings in web console when the anchor is clicked
Actual behavior
when the anchor is clicked, store.x gets mutated; no warnings in web console.
Additional information
deps
"pinia": "^2.0.5",
"vue": "^3.2.16",

Thanks.

readonly is for reactive: https://v3.vuejs.org/api/basic-reactivity.html#readonly

readonly is for reactive: https://v3.vuejs.org/api/basic-reactivity.html#readonly

@posva the docs you mentioned: 'readonly takes a reactive OR a ref '😂
ex. readonly for a ref
https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgcmVhZG9ubHkgfSBmcm9tICd2dWUnXG5cbmNvbnN0IHogPSByZWYoMCk7XG5jb25zdCByZWFkb25seVogPSByZWFkb25seSh6KTtcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIDxidXR0b24gQGNsaWNrPScrK3JlYWRvbmx5Wic+IGluY3IgcmVhZG9ubHlaIDwvYnV0dG9uPlxuICA8IS0tIHZ1ZSB3aWxsIHdhcm4gb24gdXNlcnMgY2xpY2sgLS0+XG4gIDwhLS0gU2V0IG9wZXJhdGlvbiBvbiBrZXkgXCJ2YWx1ZVwiIGZhaWxlZDogdGFyZ2V0IGlzIHJlYWRvbmx5LiAtLT5cbjwvdGVtcGxhdGU+IiwiaW1wb3J0LW1hcC5qc29uIjoie1xuICBcImltcG9ydHNcIjoge1xuICAgIFwidnVlXCI6IFwiaHR0cHM6Ly9zZmMudnVlanMub3JnL3Z1ZS5ydW50aW1lLmVzbS1icm93c2VyLmpzXCJcbiAgfVxufSJ9

@posva my temp. workaround is using a no-setter computed ref
// myStore.js
import { defineStore } from 'pinia'
import { ref, computed } from 'vue'

export default defineStore('myStore', () => {
  const x = ref(0)
  // ..
  return { x: computed(() => x.value) } // << no-setter = readonly
})

and users will get a warning on mutating x as expected
<!-- App.vue -->
<script setup>
import useMyStore from './path/to/myStore.js'
const store = useMyStore()
</script>
<template>
  <button @click='++store.x'> {{ store.x }} </button>
  <!-- vue will warn when users click -->
  <!-- Write operation failed: computed value is readonly -->
</template>

Seems like a Vue issue: https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgcmVhZG9ubHksIHJlYWN0aXZlIH0gZnJvbSAndnVlJ1xuXG5jb25zdCB6ID0gcmVmKDApO1xuY29uc3QgcmVhZG9ubHlaID0gcmVhZG9ubHkoeik7XG4gIGNvbnN0IHN0b3JlID0gcmVhY3RpdmUoe30pXG4gIHN0b3JlLnJlYWQgPSByZWFkb25seVpcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIHt7IHogfX1cbiAgPGJ1dHRvbiBAY2xpY2s9Jysrc3RvcmUucmVhZCc+IGluY3IgcmVhZG9ubHlaIDwvYnV0dG9uPlxuICA8IS0tIHZ1ZSB3aWxsIHdhcm4gb24gdXNlcnMgY2xpY2sgLS0+XG4gIDwhLS0gU2V0IG9wZXJhdGlvbiBvbiBrZXkgXCJ2YWx1ZVwiIGZhaWxlZDogdGFyZ2V0IGlzIHJlYWRvbmx5LiAtLT5cbjwvdGVtcGxhdGU+IiwiaW1wb3J0LW1hcC5qc29uIjoie1xuICBcImltcG9ydHNcIjoge1xuICAgIFwidnVlXCI6IFwiaHR0cHM6Ly9zZmMudnVlanMub3JnL3Z1ZS5ydW50aW1lLmVzbS1icm93c2VyLmpzXCJcbiAgfVxufSJ9
Or maybe it's intended, I will have to check

Seems like a Vue issue: https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgcmVhZG9ubHksIHJlYWN0aXZlIH0gZnJvbSAndnVlJ1xuXG5jb25zdCB6ID0gcmVmKDApO1xuY29uc3QgcmVhZG9ubHlaID0gcmVhZG9ubHkoeik7XG4gIGNvbnN0IHN0b3JlID0gcmVhY3RpdmUoe30pXG4gIHN0b3JlLnJlYWQgPSByZWFkb25seVpcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIHt7IHogfX1cbiAgPGJ1dHRvbiBAY2xpY2s9Jysrc3RvcmUucmVhZCc+IGluY3IgcmVhZG9ubHlaIDwvYnV0dG9uPlxuICA8IS0tIHZ1ZSB3aWxsIHdhcm4gb24gdXNlcnMgY2xpY2sgLS0+XG4gIDwhLS0gU2V0IG9wZXJhdGlvbiBvbiBrZXkgXCJ2YWx1ZVwiIGZhaWxlZDogdGFyZ2V0IGlzIHJlYWRvbmx5LiAtLT5cbjwvdGVtcGxhdGU+IiwiaW1wb3J0LW1hcC5qc29uIjoie1xuICBcImltcG9ydHNcIjoge1xuICAgIFwidnVlXCI6IFwiaHR0cHM6Ly9zZmMudnVlanMub3JnL3Z1ZS5ydW50aW1lLmVzbS1icm93c2VyLmpzXCJcbiAgfVxufSJ9
Or maybe it's intended, I will have to check

@posva thanks. but its not quite related to my original issue ( my issue is on ref itself, not 'reactive property is a ref' ), let me illustrate the issue in another way, I expected that pinia store respects readonly refs just like how vue provide/inject mechanism. ex:
Provider
<!-- App.vue -->
<script setup>
import { ref, readonly, provide } from 'vue'
import MyComp from './MyComp.vue'

const x = ref(0);
provide('x', readonly(x));  // analog : return { x: readonly(x) } in storeSetup fn
</script>

<template>
  <MyComp></MyComp>
</template>

Then, in injectors
<!-- MyComp.vue -->
<script setup>
import { inject } from 'vue'

const x = inject('x');  // analog :  get `x` from store
</script>

<template>
  {{ x }}
  <button @click='++x'> incr x </button>
  <!-- vue will warn when users click -->
  <!-- Set operation on key "value" failed: target is readonly. -->
</template>

demo : https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgcmVhZG9ubHksIHByb3ZpZGUgfSBmcm9tICd2dWUnXG5pbXBvcnQgTXlDb21wIGZyb20gJy4vTXlDb21wLnZ1ZSdcblxuY29uc3QgeCA9IHJlZigwKTtcbnByb3ZpZGUoJ3gnLCByZWFkb25seSh4KSk7ICAvLyBwcm92aWRlIGEgcmVhZG9ubHkgcmVmXG48L3NjcmlwdD5cblxuPHRlbXBsYXRlPlxuICA8TXlDb21wPjwvTXlDb21wPlxuPC90ZW1wbGF0ZT4iLCJpbXBvcnQtbWFwLmpzb24iOiJ7XG4gIFwiaW1wb3J0c1wiOiB7XG4gICAgXCJ2dWVcIjogXCJodHRwczovL3NmYy52dWVqcy5vcmcvdnVlLnJ1bnRpbWUuZXNtLWJyb3dzZXIuanNcIlxuICB9XG59IiwiTXlDb21wLnZ1ZSI6IjxzY3JpcHQgc2V0dXA+XG5pbXBvcnQgeyBpbmplY3QgfSBmcm9tICd2dWUnXG4gIFxuY29uc3QgeCA9IGluamVjdCgneCcpO1xuPC9zY3JpcHQ+XG5cbjx0ZW1wbGF0ZT5cbiAge3sgeCB9fVxuICA8YnV0dG9uIEBjbGljaz0nKyt4Jz4gaW5jciB4IDwvYnV0dG9uPlxuICA8IS0tIHZ1ZSB3aWxsIHdhcm4gd2hlbiB1c2VycyBjbGljayAtLT5cbiAgPCEtLSBTZXQgb3BlcmF0aW9uIG9uIGtleSBcInZhbHVlXCIgZmFpbGVkOiB0YXJnZXQgaXMgcmVhZG9ubHkuIC0tPlxuPC90ZW1wbGF0ZT4ifQ==

It’s how pinia worka

It’s how pinia worka

@posva thanks, good hint. Here's my new understanding:
When we call useMyStore(), it ultimately returns a reactive() wrapping the obj returned from storeSetup fn;
import { isReactive } from 'vue'
import useMyStore from './myStore.js'
const store = useMyStore()
isReactive(store) // true

Since vue doesn't preserve readonly(aRef) semantic for reactive property ( value is auto unwrapped on access when it is a ref ), to prevent returned refs from mutating, we can use no-setter ComputedRef instead ( https://github.com/posva/pinia/issues/872#issuecomment-985988052 )
Right?

Seems like a Vue issue: https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgcmVhZG9ubHksIHJlYWN0aXZlIH0gZnJvbSAndnVlJ1xuXG5jb25zdCB6ID0gcmVmKDApO1xuY29uc3QgcmVhZG9ubHlaID0gcmVhZG9ubHkoeik7XG4gIGNvbnN0IHN0b3JlID0gcmVhY3RpdmUoe30pXG4gIHN0b3JlLnJlYWQgPSByZWFkb25seVpcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIHt7IHogfX1cbiAgPGJ1dHRvbiBAY2xpY2s9Jysrc3RvcmUucmVhZCc+IGluY3IgcmVhZG9ubHlaIDwvYnV0dG9uPlxuICA8IS0tIHZ1ZSB3aWxsIHdhcm4gb24gdXNlcnMgY2xpY2sgLS0+XG4gIDwhLS0gU2V0IG9wZXJhdGlvbiBvbiBrZXkgXCJ2YWx1ZVwiIGZhaWxlZDogdGFyZ2V0IGlzIHJlYWRvbmx5LiAtLT5cbjwvdGVtcGxhdGU+IiwiaW1wb3J0LW1hcC5qc29uIjoie1xuICBcImltcG9ydHNcIjoge1xuICAgIFwidnVlXCI6IFwiaHR0cHM6Ly9zZmMudnVlanMub3JnL3Z1ZS5ydW50aW1lLmVzbS1icm93c2VyLmpzXCJcbiAgfVxufSJ9
Or maybe it's intended, I will have to check

@posva it's not intended, this is actually a vue reactivity bug, may fix by https://github.com/vuejs/vue-next/pull/5048

Don't know if this is useful to anyone, but I found this trying to find out if this is possible, and it turns out returning a readonly ref works just fine with Pinia nowadays! Only the typings are wrong when using the readonly ref in a setup block using storeToRefs.
So (using an updated version of the example in the OP here):
// myStore.js
import { defineStore } from 'pinia'
import { ref, readonly } from 'vue'

export default defineStore('myStore', () => {
  const x = ref(0)
  // ..
  return { x: readonly(x) }  // << readonly
})

<!-- App.vue -->
<script setup>
import useMyStore from './path/to/myStore.js'
const { x } = storeToRefs(useMyStore())
// This ^ is typed wrong! Is now Ref<boolean>, should be Readonly<Ref<boolean>>
</script>
<template>
  <a @click='++x'> {{ x }} </a>
  <!--
    When user triggers mutating of a readonly ref, Vue warns in the console:
    "Set operation on key "value" failed: target is readonly."
  -->
</template>

Related: #2574


Selector is not showing correctly in HA App

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
v2.1.1
Last working release (if known):
Browser and Operating System:
Mac OS - Safari and HA App
iOS - Safari and HA App

Description of problem:
I'm using your Service call tile feature with with selectors for input select / select. On Mac OS and iOS Safari it is show correctly without problems.  I double checked on my old test iPhone and it's working fine on Home Assistant app on that which means whatever is causing this is inconsistent across similar environments. You're on the latest version of the MacOS/iOS Home Assistant apps right?
From the error message either the hass object is undefined, it doesn't have a states object, or the select.harmony_hub_activities entity ID is not present in the states object. Of these the hass object being undefined makes the most sense, but at the same time makes no sense since the entire card should fail to render if the hass object is not present.
Could you go back to the web inspector and take a screenshot of what should be the selector? I'm trying to figure out why it only partially rendered before throwing the error, since it should have thrown that error before it rendered anything. Here's my example one up through the first option:

I've also been working on a significant refactor for v3.0.0 that affects some of the code that calls hass.states. Could you enable Show beta versions in HACS and try using v3.0.0-dev.019? It may inadvertently have fixed the issue if this is because of some weird logic in the old string interpolation system I'm ripping out in favor of nunjucks.

Okay this is really strange. I was waiting about over 1 week to report this issue. Several restarts and cache cleaning didn't resolve this. Now I reporting this and over night the problem ist gone and the card ist working correctly and no more errors in web inspector. Sorry for bother you and taking your time for that.
Now I have only a feature request. :D It would be nice if it is also working with 'select' entities and not only with 'input_select' entities. With select entities the status is shown be right but I can't change it. But first at all I close this one.
Thanks anyway


Can't pick theme files in editor & crash using 'default' in custom theme

I'm using godot 3.0.
Here is the theme:
default.theme.txt
(remove the .txt)
then in the project.godot file set the theme:
theme/custom="res://Theme/default.theme"
You have to do this by hand as the editor only allow you to select a *.tres or *.res file, of which *.theme is likely the only one that should be available here - this is one bug.
Now, this will cause a crash because when you supply "default" in the theme, it looks to take the value from the default theme, which is only created if the custom_theme fails to load, so its looking for defaults in the default theme which has not been instantiated - hence we get a null pointer access. - this is the second (and more show stopping) bug.
Finally, if the theme is incomplete I get a lot of crashes as the default value returned is 0 in the case of a theme value not being configured.
edit: btw, is there a way to get godot to create theme files? I'm having to reverse engineer this myself as I cant seem to find out how.

In Godot  3.2.dev.custom_build. 6d6d43714 I can set to as theme ".theme" file
Provided theme file is incomplete and broken.
It need a folder "Theme" with "popup_window.png" inside.
It only shows this errors, but doesn't crash editor
ERROR: open: Unrecognized binary resource file: res://Theme/default.theme.
   At: core/io/resource_format_binary.cpp:848.
ERROR: load: Condition ' err != OK ' is true. returned: RES()
   At: core/io/resource_loader.cpp:208.
ERROR: _load: Failed loading resource: res://Theme/default.theme.
   At: core/io/resource_loader.cpp:278.
ERROR: load_resource: Condition ' !res.is_valid() ' is true. returned: ERR_CANT_OPEN
   At: editor/editor_node.cpp:632.

Fixed in 3.2


multiple instance -> resuming has no effect

Hello, i'm using 1 instance on a page, then I dynamically load a layer (via load())
This also triggers:

pausing the first instance
creating a new instance (with different ID and Nav selector for my layer)

This is working fine. Instance 1 does not fire and instance 2 is firing with correct page target
then when I close the layer, I unbind my instance 2 (confirmed by debug mode) and resume my instance 1 (also confirmed by debug mode). And then nothing. The instance 1 does not fire anymore.
Im using jquery firebug plugin and I can see that the event is still bind to the element.
I try to check where its stuck, but so far no success. Do you have any clue ?
Thank you
EDIT: i think its somehow losing the bind on scroll event as the function infscr_scroll() is no longer firing

Can you please send through a link to this in action? Sounds pretty weird, but I'm sure it's something easy we can fix!

aya, shame on me |:
I was not using the option "infid". Thus all my instances were using default instance id: 0....
Its now working fine

Glad to know it's working now! Let me know if you need anything else!


Just an Idea. Can you put android and ios folders together into one folder called "output" ?

Proposal
Just an Idea. Can you put android and ios folders together into one folder called "output" ? If in the future someone creates another platform the project structure will be messy. Thank you for your time. It's just a suggestion.

duplicate of https://github.com/flutter/flutter/issues/71400

Closing as duplicate of https://github.com/flutter/flutter/issues/71400.


qemu: backport 9p-darwin to v6.2.0

Motivation for this change
Backports 9p-darwin functionality from upstream v9 patchset (https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg05978.html) to v6.2.0.
Please note that the final commit in the backported patchset includes a utimensat fallback, which will be needed until macOS SDK reaches 10.13 (https://github.com/NixOS/nixpkgs/issues/101229). I'll be more than happy to rebase/edit that particular final patch as needed once 7.0-rc hits, to ease that upgrade.
Addresses changes proposed by #122420.
@domenkozar @alyssais
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

nixpkgs-review is giving me all kinds of noisy errors because of other upstream stuff, but:
macOS:
$ nix-build $NIXPKGS -A qemu
/nix/store/d8whkgmadif7yx3qrjdsc661scnkax57-qemu-6.2.0

NixOS:
$ nix-build $NIXPKGS -A qemu
/nix/store/87myhvvhyj9nl4djcwif2bl0b9l69qyw-qemu-6.2.0

And from the qemu source directory on macOS, the 9pfs synth tests appear to pass with the new build too.
$ export QTEST_QEMU_BINARY=/nix/store/d8whkgmadif7yx3qrjdsc661scnkax57-qemu-6.2.0/bin/qemu-system-x86_64
$ cd build
$ tests/qtest/qos-test -m slow
....
# End of x86_64 tests

Result of nixpkgs-review pr 162243 run on x86_64-darwin 1

11 packages marked as broken and skipped:

alpine-make-vm-image
cloud-init
cloud-utils
multibootusb
python310Packages.guestfs
python39Packages.guestfs
qemu_full
qemu_xen
qemu_xen-light
qemu_xen_4_10
qemu_xen_4_10-light

1 package failed to build:

python310Packages.cot

8 packages built:

colima
cot (python39Packages.cot)
lima
out-of-tree
qemu
qemu-utils
qemu_kvm
qemu_test

Result of nixpkgs-review pr 162243 run on x86_64-linux 1

8 packages marked as broken and skipped:

aqemu
linuxKernel.packages.hardkernel_4_14.virtualbox
linuxPackages_hardkernel_latest.virtualbox
multibootusb
qemu_xen
qemu_xen-light
qemu_xen_4_10
qemu_xen_4_10-light

1 package blacklisted:

tests.nixos-functions.nixosTest-test

48 packages built:

alpine-make-vm-image
cloud-init
cloud-utils
colima
cot (python39Packages.cot)
diffoscope
gnome.gnome-boxes
libguestfs
lima
linuxKernel.packages.linux_4_14.virtualbox
linuxPackages_4_14_hardened.virtualbox (linuxKernel.packages.linux_4_14_hardened.virtualbox)
linuxKernel.packages.linux_4_19.virtualbox
linuxPackages_4_19_hardened.virtualbox (linuxKernel.packages.linux_4_19_hardened.virtualbox)
linuxKernel.packages.linux_4_4.virtualbox
linuxKernel.packages.linux_4_9.virtualbox
linuxKernel.packages.linux_5_10.virtualbox
linuxPackages_5_10_hardened.virtualbox (linuxKernel.packages.linux_5_10_hardened.virtualbox)
linuxPackages.virtualbox (linuxKernel.packages.linux_5_15.virtualbox)
linuxPackages_hardened.virtualbox (linuxPackages_5_15_hardened.virtualbox)
linuxPackages_latest.virtualbox (linuxKernel.packages.linux_5_16.virtualbox)
linuxKernel.packages.linux_5_4.virtualbox
linuxPackages_5_4_hardened.virtualbox (linuxKernel.packages.linux_5_4_hardened.virtualbox)
linuxPackages_latest-libre.virtualbox (linuxKernel.packages.linux_latest_libre.virtualbox)
linuxPackages-libre.virtualbox (linuxKernel.packages.linux_libre.virtualbox)
linuxPackages_lqx.virtualbox (linuxKernel.packages.linux_lqx.virtualbox)
linuxPackages_testing_bcachefs.virtualbox (linuxKernel.packages.linux_testing_bcachefs.virtualbox)
linuxPackages_xanmod.virtualbox (linuxKernel.packages.linux_xanmod.virtualbox)
linuxPackages_zen.virtualbox (linuxKernel.packages.linux_zen.virtualbox)
open-watcom-bin
open-watcom-bin-unwrapped
out-of-tree
python310Packages.cot
python310Packages.guestfs
python39Packages.guestfs
qemu
qemu-utils
qemu_full
qemu_kvm
qemu_test
qtemu
quickemu
solo5
tests.trivial-builders.references
vagrant
virtualbox
virtualboxHardened
virtualboxHeadless
virtualboxWithExtpack

Builds for me, macos 10.15, along with the passthru test. Don't really know how to test this feature though. Any suggestions?

This is one piece of a many-part puzzle to solve various other issues, so you're right to ask how to test it.
For nix users, https://github.com/NixOS/nixpkgs/issues/108984 is the most relevant set of use cases, but this only solves one of multiple set of issues (finally merging all the random QEMU patches and forks mentioned there into nixpkgs).
To test a smaller use case of whether this version of QEMU integrates 9p correctly, https://github.com/containers/podman/issues/13256 is probably your best bet. Unfortunately, it still requires fixing podman on nixpkgs. You can probably test it for now if you use homebrew's podman and nix's QEMU.

@risicle if you rebase qowoz's podman4-gvproxy from #161130 on top of my qemu branch from this PR and build that version of podman on top of this qemu:
$ podman machine init --volume /Users/yourusername:/mnt/yourusername
$ podman machine start
$ podman machine ssh
$ cd /mnt/yourusername
$ ls

You should be able to see your home directory from there!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/performant-graphical-vm-via-qemu/17895/3

Hah.. Thanks for your detailed instructions @willcohen but after half an hour of messing around with it I realized of course it's not going to work on the mac I'm currently working on - it's virtualized itself. Anyway, builds & unit tests still pass as far as I can test :+1:

Seems to work fine, previously podman/qemu would error trying to mount a volume.
podman machine init --now --volume /Users/zowoq:/mnt/zowoq
Extracting compressed file
Image resized.
Machine init complete
INFO[0000] waiting for clients...
INFO[0000] new connection from  to /tmp/podman/qemu_podman-machine-default.sock
Waiting for VM ...
qemu-system-x86_64: -virtfs local,path=/Users/zowoq,mount_tag=vol0,security_model=mapped-xattr: There is no option group 'virtfs'
qemu-system-x86_64: -virtfs local,path=/Users/zowoq,mount_tag=vol0,security_model=mapped-xattr: virtfs support is disabled
Error: dial unix /tmp/podman/podman-machine-default_ready.sock: connect: no such file or directory
ERRO[0003] cannot receive packets from , disconnecting: cannot read size from socket: EOF
ERRO[0003] cannot read size from socket: EOF

@ofborg build qemu

You should be able to see your home directory from there!

This worked for me, on macos 12.2.1, with this branch's qemu and the podman on master (thanks to #161130).

I could successfully mount volumes natively using this backport and the Podman branch from https://github.com/containers/podman/pull/13409/ on my m1 mac.
Amazing stuff:+1:.

@alyssais
Just force-pushed some changes.

Each of the commits is broken out now (for easier picking-and-choosing, as well as a cleaner potential switchover to the per-commit URL fetchpatch style of gitlab whenever the PR gets merged.)
All the changes which don't apply cleanly have been broken out into patch files.
Because the second commit (which also stopped applying cleanly) is now a patch file, the sed changes are no longer needed before building.

This can either be merged as is (and then I can prepare a smaller subsequent PR to point the nine patches to QEMU upstream), or we can wait till whenever it gets merged and I'll force push one more time. I'm not sure on timeline for when that merge would happen. The 9p maintainer submitted this latest pull request incorporating these changes this morning.

@alyssais 9p-darwin has been merged upstream. I've updated the PR to pull from the official qemu-project/qemu repo. I think this PR is finalized now.

Result of nixpkgs-review pr 162243 run on x86_64-darwin 1

1 package marked as broken and skipped:

alpine-make-vm-image

1 package failed to build:

python310Packages.cot

8 packages built:

colima
cot (python39Packages.cot)
lima
out-of-tree
qemu
qemu-utils
qemu_kvm
qemu_test

@willcohen sorry to put you through another round of this, but could we apply the patches unconditionally?  It makes maintenance easier, because it means I'll notice e.g. patches that fail to apply immediately when updating from Linux.

Of course. Will revise.

@alyssais oh wait, I remember why I did this now. If I try to apply these patches on top of 9p-ignore-noatime, they fail:
unpacking source archive /nix/store/1rnwb2yy7n64y86hakkb0acrkp65a9pf-qemu-6.2.0.tar.xz
source root is qemu-6.2.0
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file qemu-6.2.0/roms/edk2/UnitTestFrameworkPkg/Library/CmockaLib/cmocka/tests/test_wildcard.c
patching sources
applying patch /nix/store/9acf6z50qqingjpn8i6bw9r5d85nxzhg-fix-qemu-ga.patch
patching file qga/commands-posix.c
Hunk #1 succeeded at 109 with fuzz 2.
applying patch /nix/store/k5ncmjr0jf0rkkgb8ndml1f36knv3njv-9p-ignore-noatime.patch
patching file hw/9pfs/9p.c
Hunk #1 succeeded at 137 (offset 10 lines).
applying patch /nix/store/ra37ssglh8dds19fbr0ymq2qnizr5bxl-7e3e20d89129614f4a7b2451fe321cc6ccca3b76.diff
patching file include/ui/clipboard.h
Hunk #1 succeeded at 218 with fuzz 1 (offset 31 lines).
patching file ui/clipboard.c
Hunk #1 succeeded at 114 (offset 41 lines).
patching file ui/cocoa.m
applying patch /nix/store/0zbyxfcpbw93380jzfky5gkpayfzamdq-e0bd743bb2dd4985791d4de880446bdbb4e04fed.patch
patching file fsdev/file-op-9p.h
patching file hw/9pfs/9p-local.c
patching file hw/9pfs/9p.c
patching file include/qemu/xattr.h
applying patch /nix/store/nm69lx0icsnx7s0ad18yz8l38gml9mss-rename-9p-util.patch
patching file hw/9pfs/9p-util-linux.c (renamed from hw/9pfs/9p-util.c)
patching file hw/9pfs/meson.build
applying patch /nix/store/pqcdyn6gvkwndnsm5i9m43ykb0ahnpji-f41db099c71151291c269bf48ad006de9cbd9ca6.patch
patching file hw/9pfs/9p-proxy.c
patching file hw/9pfs/9p-synth.c
Hunk #1 succeeded at 427 (offset -12 lines).
patching file hw/9pfs/9p.c
Hunk #1 succeeded at 1312 (offset -1 lines).
Hunk #2 succeeded at 3524 (offset -1 lines).
applying patch /nix/store/05l0gl7zfpk9xin41srpcv8x8cdd5ja9-6b3b279bd670c6a2fa23c9049820c814f0e2c846.patch
patching file hw/9pfs/9p-local.c
patching file hw/9pfs/9p-proxy.c
patching file hw/9pfs/9p-synth.c
Hunk #1 succeeded at 222 with fuzz 2 (offset -12 lines).
patching file hw/9pfs/9p-util.h
patching file hw/9pfs/9p.c
Hunk #2 succeeded at 2281 (offset -1 lines).
Hunk #3 succeeded at 2420 (offset -1 lines).
Hunk #4 succeeded at 2481 (offset -1 lines).
patching file hw/9pfs/codir.c
Hunk #2 succeeded at 169 (offset 1 line).
applying patch /nix/store/2zi4jkf6apny80mjvsnysf9y39hkvcjh-67a71e3b71a2834d028031a92e76eb9444e423c6.patch
patching file hw/9pfs/9p-util.h
patching file hw/9pfs/9p.c
Hunk #1 FAILED at 138.
Hunk #2 succeeded at 170 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file hw/9pfs/9p.c.rej
error: builder for '/nix/store/prrnyklwp6cbymighad5d8w6fk79q0qi-qemu-6.2.0.drv' failed with exit code 1;
       last 10 log lines:
       > Hunk #3 succeeded at 2420 (offset -1 lines).
       > Hunk #4 succeeded at 2481 (offset -1 lines).
       > patching file hw/9pfs/codir.c
       > Hunk #2 succeeded at 169 (offset 1 line).
       > applying patch /nix/store/2zi4jkf6apny80mjvsnysf9y39hkvcjh-67a71e3b71a2834d028031a92e76eb9444e423c6.patch
       > patching file hw/9pfs/9p-util.h
       > patching file hw/9pfs/9p.c
       > Hunk #1 FAILED at 138.
       > Hunk #2 succeeded at 170 (offset -1 lines).
       > 1 out of 2 hunks FAILED -- saving rejects to file hw/9pfs/9p.c.rej
       For full logs, run 'nix log /nix/store/prrnyklwp6cbymighad5d8w6fk79q0qi-qemu-6.2.0.drv'.

Is that patch going to keep being needed? If so, it's going to break with 7.0 too based on 9p-darwin. If so, I can also update it to apply AFTER these ones, so you'll be able to retain it with the version bump.

Is that patch going to keep being needed?

Let me have a look into it.  I'll try to get you an answer tonight.

More specifically, this is why it conflicts: https://gitlab.com/qemu-project/qemu/-/commit/67a71e3b71a2834d028031a92e76eb9444e423c6
9p-darwin patch set moves the deleted code to a new location, so the patch will need to take that into account if it's still needed on Linux. I don't know enough about what it's doing to assess whether it's still important, though, but if so, I'm happy to modify the file for this PR.

Upon a non-exhaustive search, I'm not currently seeing that that patch ever got finalized into the kernel, though it's extremely possible that I missed it. That said, as I'm not familiar with the NixOS tests in question, I can't tell if it's still applicable anymore either.

@alyssais I can't figure out why the patch WOULDN'T still be needed, so I went ahead and updated it to work on a post 9p-darwin setup, and removed the conditional application of the patches

Result of nixpkgs-review pr 162243 run on x86_64-darwin 1

1 package marked as broken and skipped:

alpine-make-vm-image

1 package failed to build:

python310Packages.cot

8 packages built:

colima
cot (python39Packages.cot)
lima
out-of-tree
qemu
qemu-utils
qemu_kvm
qemu_test

My initial testing implies that the patch isn't needed any more, but I need to investigate to be sure.  But since you've done the work anyway to rebase it, there's no reason to make you wait while I investigate.  Thanks so much!

Thanks!


How to control the key IDs generated by AMUSE

I am cautiously rewriting the multiples module to use data structures like encounters and streamline the design, but to retain the physics I think works, and I want to be able to check frequently that I haven't materially changed the module's operation by writing a verbose test script and comparing the output with the original multiples code.  Eventually this will fail as features are added, but while I am simply refactoring I need to know I haven't changed anything.
The verbose output involves printing out particle sets of multiple systems.  Unfortunately, it appears that the keys used for particles are randomly generated each time the (unchanged) script runs.  Does anyone know how to force AMUSE to generate the same key names each time around?

You could pre-generate a set of keys (a list of numbers) and pass it to a particle set with the keyword 'keys=':
p = Particles(5)
keys = p.key
q = Particles(keys=keys)

Perhaps more useful in your case would be to pass a simpler key generator:
from amuse.datamodel import Particles
from amuse.datamodel.base import BasicUniqueKeyGenerator
n = 10
p = Particles(n, keys_generator=BasicUniqueKeyGenerator())
q = Particles(n, keys_generator=BasicUniqueKeyGenerator(
    lowest_unique_key=p.key.min())
)

But please note that this is risky when creating/deleting particles as they might get the same key if you don't pass the correct lowest_unique_key...


Using the plugin to stream to RTSP server

Hi, I'm planning to connect a color Basler camera to my Jetson Xavier NX with Cuda support. The Jetson will then host an RTSP server so that I can stream the camera output in gray on my computer. Does this plugin have RTSP server feature with the camera? If so, could you provide the command to do this? Thank you in advance.
My Jetson Xavier NX is running on JetPack 4.6 Ubuntu 18.04 with built-in Python 3.6

The plugin itself just contains an element to capture from the camera. However, GStreamer offers a RTSP server you can use along with this element:gstreamer/subprojects/gst-rtsp-server at main · GStreamer/gstreamergithub.comThe simplest way to get started is to use one of their examples:gstreamer/subprojects/gst-rtsp-server/examples/test-launch.c at main · GStreamer/gstreamergithub.comMichaelOn 11 Nov 2023, at 08:38, Danish Shukor @.***> wrote:
Hi, I'm planning to connect a Basler camera with my Jetson Xavier NX with Cuda support. The Jetson will then host an RTSP server so that I can stream the camera output on my computer. Does this plugin have RTSP server feature with the camera? If so, could you provide the command to do this? Thank you in advance.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Aite thank you!

@dnshshkr did you manage to get it to work? I am having trouble configuring it to work...


There are certain SaaS subscriptions purchased but it does not delete after several retries

Error message:
Failed to delete resource group G7CR-MSMarketplace-RG: Deletion of resource group 'G7CR-MSMarketplace-RG' failed as resources with identifiers 'Microsoft.SaaS/resources/ss01' could not be deleted. The provisioning state of the resource group will be rolled back. The tracking Id is '9b7d3e16-8dbb-4443-bef8-07457d7647ca'. Please check audit logs for more details. (Code: ResourceGroupDeletionBlocked) An invalid response code was detected. (Code: Forbidden, Target: /subscriptions/3771426a-689b-4039-9929-fb0786b7f9d7/resourceGroups/G7CR-MSMarketplace-RG/providers/Microsoft.SaaS/resources/ss01)
[Enter feedback here]

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

ID: cb2b6abc-0b2b-75b3-25d8-06591d7eb8cc
Version Independent ID: 7d78e0e3-eaf2-2002-24d2-268d49f8e907
Content: Managing the SaaS subscription life cycle
Content Source: articles/marketplace/partner-center-portal/pc-saas-fulfillment-life-cycle.md
Service: marketplace
Sub-service: partnercenter-marketplace-publisher
GitHub Login: @arifgani
Microsoft Alias: argani

@g7crservice-sajid-f Thank you for reaching out to us. We will look into this and get back to you soon.

@g7crservice-sajid-f Sometimes it takes time to delete the resource, but the best action here is to open a ticket with our dedicated Marketplace support team for them to look into it - https://partner.microsoft.com/en-US/support/v2/?stage=1


Why there are "each" versions of functions?

I think it could be simplified so that one could do:
type PageData struct {
	Link    string   `pagser:"a->attr(href)"`
	Links   []string `pagser:"a->attr(href)"`
}

The package could inspect the type associated with the tag and if it is slice, automatically assume "each" behavior. In general I think all functions should be returning slices, which then optionally are converted to an individual value (by default the first one, but you could set using ->Eq some other index).

It like a good idea.


Create additional .svg icons to load

Story
As a User
I want to associate a node with an .svg file
So I can recognize the node at a glance
Acceptance Criteria
Add 20+ new .svgs to the project.

This issue needs a bit more definition and scoping now, as context about how this feature should work is not clear.

Another version of this story lives https://github.com/opentecture/mindmapping/issues/30.
Closing this one.


Exception

@Override
public void failure(TwitterException exception) {
//         progressDialog.hide();
Toast.makeText(Download_Auto.this, "Request Failed: Check your internet connection", Toast.LENGTH_SHORT).show();
}
exception due to twitter key . how can i get twitter key ???

Hello, visit https://developer.twitter.com/en/apps to create a new app and thereby get a key and secret.

Developers account not approved

Twitter developer account?

yes developer account they need info i gave but not approved

Oh. I can't really tell what caused that. But you can reach out to Twitter Support for help.

Please help me for approval of twitter developers account

Hey. I don't work with twitter. Reach out to their customer support.

okay  thank you

You are welcome.


Support PNPM?

Any chance wrangler2 can support PNPM? It's much faster and has better support for workspaces which pairs nicely with workers using a micro-service approach. Currently, npx wrangler@beta init fails as it defaults to npm.

Yeah, I think we can/should do this. Our yarn integration could also use some work. Thanks for filing this, it had slipped my mind!

I'm interested in working on this. Is this file the only one that needs updating?
One approach could be updating this file to support hasPnpmLock, but I don't think this logic currently supports monorepos as the lock file will often be in a parent directory.
Another approach could be to allow passing in the package manager as a flag and setting npm as the default using yargs. This file could be simplified to do a check to see if the system supports('<package_manager>') and a conditional to use the right package manager object (eg. YarnPackageManager, PnpmPackageManager).
What do you think @threepointone ?

There's some nuance here we might want to revisit. For example, if you use pnpm dlx wrangler init <name> we want to make sure it sets up a pnpm project. (This is separate from looking for the lockfile, which won't exist when the above command is called.). yarn doesn't have a direct executor like npx and pnpm dlx, so maybe that's ok.
I don't think we should add any new flags, we should be able to detect what's executing the command and take a call from there.


fix(audit, auditTime): audit and auditTime emit last value after source completes

Description:
Adjust audit operator to emit the last value when source completes
Related issue (if exists):
#5730

Thanks, @alexsherekin!


Multiple error messages (Implements #70)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the main branch for v2.x (or to a previous version branch)
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] All tests are passing
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
This is an initial implementation of the proposal described in #70. Please provide feedback on this initial version, so it can be refined and applied to all input based components.

Due to issues in pushing code from SIX, Closing this PR in favour of #88


fix: rename Job and JobSpec module

What this PR does / why we need it:

KubeflowOrgV1TFJob and KubeflowOrgV1TFJobSpec do not exist in kubeflow.training module
KubeflowOrgV1PyTorchJob and KubeflowOrgV1PyTorchJobSpec do not exist in kubeflow.training module

Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Fixes #
Checklist:

[x] KubeflowOrgV1TFJob changed to V1TFJob
[x] KubeflowOrgV1TFJobSpec changed V1TFJobSpec
[x] KubeflowOrgV1PyTorchJob changed to V1PyTorchJob
[x] KubeflowOrgV1PyTorchJobSpec changed V1PyTorchJobSpec

which sdk version are you using?

"""
    Kubeflow Training SDK

    Python SDK for Kubeflow Training  # noqa: E501

    The version of the OpenAPI document: v1.4.0
    Generated by: https://openapi-generator.tech
"""

I am still at v1.4.0. I thought I had the most recent one.

Please try https://pypi.org/project/kubeflow-training/1.5.0rc0/

```python
"""
    Kubeflow Training SDK

    Python SDK for Kubeflow Training  # noqa: E501

    The version of the OpenAPI document: v1.4.0
    Generated by: https://openapi-generator.tech
"""

I am still at v1.4.0. I thought I had the most recent one.


Add GreenShah Theme

Dark-Green Theme

@yazdipour,
Thanks for having already signed the Contribution License Agreement. Your agreement has not been validated yet. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

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

Thanks for this new theme. I'll add it into the pack.

What is the image you choose as background? I am referring to the screenshot on the visualstudio store page. Really liked that one!

@levigeers I don't have the image right now, but you can set background with ClaudiaIDE extension

@yazdipour yup I already have Claudia for a while, but I really liked that picture you had. Do you know what "type" of picture that was? Like what catagory? Then I can google something like that. Thanks for replying that fast by the way!!

@levigeers I did an image search with my old screenshot and I found that this website is using it


support custom marshal/unmarshal/hashroot

Similar to json custom marshaling and unmarshaling, if a type already defines receivers that make it a Marshaler and Unmarshaler, use those receivers when that type is encountered by the generator.
This is particularly useful because fastssz doesn't provide a uint256 type, etc
e.g.:
type Foo struct {
  FieldOne Bar
}

type Bar struct {
  ssz.Unmarshaler
  ssz.Marshaler
  ssz.HashRoot
  ... unexported fields ...
}

sszgen should be able to create a serializer for Foo that calls Bar.MarshalSSZTo etc wherever appropriate.

More specifically, it'd be great if i could import https://github.com/holiman/uint256
and then use *uint256.Int fields in a struct
and then generate ssz encoding for that struct

This feature is already available (example).

when trying to use the imported type i get:
$ ./gen.sh
[ERR]: failed to encode SSZFile_v1: failed to encode TotalRewards: could not find struct with name 'Int'

where the struct has:
import "github.com/holiman/uint256"
type SSZFile_v1 struct {
  Test *uint256.Int
}

Ah I just noticed that holiman's library doesn't implement HashTreeRootWith :cry:

Managed to get it working with a wrapper. Holiman's MarshalSSZTo implementation is incompatible, interestingly, and I had to do some man-in-the-middle stuff.


👮🏽 Constrain RuboCop to ~> 0.40.0

This will prevent TravisCI builds from failing when RuboCop rules change
drastically in MINOR versions. PATCH versions will still be allowed to
be pulled automatically.
👮 👮 👮
Fix #124.

LGTM 👍

LGTM


Doble validation on "unique:" validation

Laravel Rest Api Version
^2.3
Laravel Version
^10.10
PHP Version
8.1.24
Database Driver & Version
MySQL 8.0.32
Description
At the time of creating a user and applying the unique rule: users, email, the validation is being performed before creating the record and after the record has been created, which is causing the error 'The mutate.0.attributes.email field has already been registered.'
Steps To Reproduce
Rules of validation
`
public function createRules(\Lomkit\Rest\Http\Requests\RestRequest $request)
{
    return [
        'name' => 'required|string|max:255',
        'email' => 'required|email|max:150|unique:users,email',
    ];
}

`
Mutation:
{
    "mutate": [
        {
            "operation": "create",
            "attributes": {
                "name": "test",
                "email"<EMAIL_ADDRESS>            }
        }
    ]
}

Edit 10/11/2023 21:06:00 :

Debugging, I find that the issue arises in the new Hooks features.

Hello @amendozaaguiar thanks for your feedback
Effectively there is a bug coming with the new feature, i'm on it, will publish a fix in less than an hour 😄
Have a nice day !


Add support for impish (21.10)

Allow deploying the charm with series impish.

Test has timed out, but I could not figure out the cause.  It seems to be happening in this one too.  There is no manual trigger for a re-run, however. Any idea?

@dannf there's conflicts that seem to be resolved?

it almost feels like it needs a rebase from master?

and i believe will need an update to charmcraft.yaml

I just rebased the branch in top of current master and it seems ok. We still have a few months of supported impish, so it seems worth of a merge.

impish is EOL for two weeks now, so this is obsolete.


lightstep: allow file-less access token option

Signed-off-by: Kuat Yessenov<EMAIL_ADDRESS>This allows self-contained bootstrap without extra token files.

/retest


proposal

What version of Go are you using (go version)?

$ go version

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?

What did you expect to see?
What did you see instead?

Sorry, created this inadvertently.


[new locale] Added locale ug-cn

Hey guys, sorry for the back and forth. I think this will be ready for merge.
Thanks for @JLHwung for mentioning unicode cldr data. It's now compatible with unicode cldr.

Hi there, I don't think my code caused the failure, travis is failed because of this error:
Running "transpile-raw" task
The following options have been renamed — please update your config: entry -> input
>> error transpiling Error: Unknown option found: moduleName. Allowed keys: input, legacy, treeshake, acorn, context, moduleContext, plugins, onwarn, watch, cache, preferConst, experimentalDynamicImport, entry, external, extend, amd, banner, footer, intro, format, outro, sourcemap, sourcemapFile, name, globals, interop, legacy, freeze, indent, strict, noConflict, paths, exports, file, pureExternalModules
>>     at Object.generate (/home/travis/build/moment/moment/node_modules/rollup/dist/rollup.js:19112:44)
>>     at /home/travis/build/moment/moment/tasks/transpile.js:74:27
>>     at process._tickCallback (internal/process/next_tick.js:109:7)
Warning: Unknown option found: moduleName. Allowed keys: input, legacy, treeshake, acorn, context, moduleContext, plugins, onwarn, watch, cache, preferConst, experimentalDynamicImport, entry, external, extend, amd, banner, footer, intro, format, outro, sourcemap, sourcemapFile, name, globals, interop, legacy, freeze, indent, strict, noConflict, paths, exports, file, pureExternalModules Use --force to continue.

The travis failure is irrelevant and fixed by #4371.

ok Thanks.


[WIP][review this thing already]Spatial AQ

The people who need to look at it know about it, so I'm not going to explain.
I've forgotten most of what it did anyway because its been gathering rust for so long.

Review of activity.rs and/or #2247
Sorry for taking so long on this review. The actual bulk of the comments are on the original tree you referred me to on Feb. 18. The older pull request looked like a WIP with lots of partial checkpoint commits and reverts and so on, and not something cleaned up for review. Obviously when just looking at the files on the tip of a branch, it's hard to know which parts are things you were actually working on and which issues were pre-existing in the code, so apologies if I comment on stuff that is not your fault.
Big picture:
There is a lot going on here, and it is headed in a different direction than David Barr, Guillaume, and I have been pushing things. Our goal is to move the psychovisual tuning into a place where each component is able to be understood separately, and makes sense in a consistent overall framework. Your work mixes a lot of things (which in and of itself is not bad), but does not show clear justifications, measurements, or at least document the testing that went into each of those things (which is the part that I am less excited about). That makes it really hard for others (specifically, me) to evaluate. It would also make it hard for other people to pick up and work on your stuff.
There are three specific things that we know work well:

Weighting distortion by pixel variance (actual variance!) raised to the 1/3rd power, scaled by some overall tuning constant (see x264 and also Jean-Marc's Journal of Dubious Results). There's literally years of work showing that this produces good results.

A measure of temporal RDO that also scales distortion in a manner consistent with the original x264 work. There are grounds to believe that what x264 did could be done better, but so far we have (a) not actually implemented the original correctly and (b) achieved worse results. Guillaume had work to move us in this direction, picking a scale factor that matches the original x264 implementation and achieving superior results to the current ad-hoc method, in a framework that makes consistent sense with all of the other pieces of the puzzle.

Quantizer (actual quantizer, not quantizer index) adjustments are directly proportional to the square root of distortion scaling.

You have combined (1) and (2) in a measure that sums them instead of multiplying them, which doesn't match my first inclination (to multiply independent contributing factors instead of summing them).
To help think about which approach is more likely to be a useful model, one experiment to consider is the "completely still scene" test. Imagine a constant image shown for N frames. Obviously the best way to code this is to spend all your bits on the initial keyframe, and then SKIP everything in all subsequent frames. If you hold the bitrate constant and increase the number of frames showing the still image, the quantizers used for the initial frame should decrease. Specifically, one would expect the quantizer to decrease by a uniform factor in all blocks. That is true under the multiplicative combination scheme, but it is not true under additive one.
You are also introducing a new, non-variance based measure to replace (1). Maybe your proposal is actually better, but I don't have any way to tell. What I would want to see to judge that are some experiments or test results on how that compares to the variance-based measure we know gives good results. Specifically, how just that piece compares.
With respect to (3), I tried to take a peek into segmentation.rs (even though that wasn't the file you asked me to review) to try to figure out how you were coming up with quantizer offsets from this, but you seem to be operating on quantizer indices directly, and doing so in a linear relation relative to what you scale distortion by. The quantizer index to quantizer mapping tables in AV1 are not consistent, in the sense that the relationship is linear for some sections of the table and exponential for others. So trying to make adjustments to those indices directly confounds analysis, and will be suboptimal for some part of the curve.
There's still some work to do to unravel the quantizer table mapping in AV1. My original hope was that we could just do whatever we wanted to pick quantizers and then figure out how to map that to quantizer indices, but because segmentation only gives us a single offset to quantizer index for all six ({AC,DC}x{color plane}) quantizers, we can only approximate that. That means we need a combined measure for the mismatch between the quantizers we want and the quantizers we can actually achieve with AV1. The "average quantizer theory" I had been working on in av1-metric.pdf is one approach to doing that, but there are still emperical measurements that need to be done to support that (specifically, getting average AC and DC variance of the prediction residual in each plane with our chosen chroma scalings and the efficacy of AV1's predictors, and seeing how that varies with quantizer). If I (or anyone else who wants to help) can make progress on that, though, it also directly extends to supporting quantization matrices in the future.
I think the optimization you are doing in segmentation.rs to pick segment quantizers is over-complicated, too. A much simplier approach is to pick one segment for the base quantizer and two segments for a somewhat larger and somewhat smaller quantizer. If you know your distortion scaling, then you know what quantizers to use, based on (3) above. That is something that I have used in the past and know works. You can expand that to adjust the number of segments at higher or lower bitrates (it's a vector quantization problem), but the above is enough to get good results. I would start there and then worry about making something more complicated once things are working and everyone is happy with them (and again, this is something you can test and show improvements for in isolation).
Small picture:
activity.rs:39
Why are you always adding (1 << act_granularity) instead of rounding up?
activity.rs:68
Feels like we ought to have an iterator method on PlaneRegion for this, but that's a larger refactor and mostly irrelevant to what you're trying to accomplish.
activity.rs:102
You're skipping (x < 2) && (y < 2) in the loop above (a total of 22 == 4 pixels), but subtracting 44 == 16 from the number of pixels here. That does not seem correct.
activity.rs:103
old_avg_var is not a variance, since you are summing the L1 norm of transform coefficients. Please do not call it one.
activity.rs:136:
There is no comment above that refers to this.
activity.rs:138
What is going on here?
activity.rs:141
Again, the way you are using this, these are not variances at all (I honestly have no idea what these are). Please do not call them variances.
activity.rs:144
I am guessing that the choice of granularity == importance block size is intentional, but this code looks like it would be hopelessly broken if they ever differed. You are doing an accumulation in *x (also, please do not shadow your loop counter like this... I know, I know, Rust, but I still think it's bad form in this instance), but then adding *x repeatedly to avg_var. The only way this can hope to make sense is if *x is used exactly once, which would not be true if importance block size was larger than granularity. If importance block size is smaller than granularity, then you are only going to add temporal activity to some small fraction of the variance entries.
So if the two have to match, why not make that explicit, instead of giving people the false hope that they could be different? It would also let you zip up an iterator over the variances array, instead of using this complicated get_mut/match construct.
activity.rs:154
What is this trying to accomplish?
It looks like maybe you are trying to group things into 8 bins, but the way you have done this, the bins are not equal sizes. Also, the "max" statistic is incredibly sensitive to outliers, and I don't think this is going to be the best way to accomplish what you are trying to do.
activity.rs:175
It would be good to have a name for "dec_width" that is common in both this and the routine above, since it is the same value serving the same purpose. I'm not sure "dec_width" is a good name ("dec" is easily confused with "decoder", although I guess you meant "decimate", but it's still a pretty generic name).
activity.rs:158
Please use an iterator for this... the whole get_mut/match construct here is totally unnecessary.
acitvity.rs:188
Where does all of the magic here come from? (and why are we repeating complex calculations that are static for the whole frame on every lookup into this array?)
activity.rs:183
This also isn't returning a variance. Please don't call it one.

I see that this has not progressed much since its inception :P

Given that there have been 2 years worth of commits, some of which have majorly rewritten the variance and distortion code, rebasing this ended up being too difficult. Based on the review suggestions, I ended up cherry-picking portions of this changeset against master in #2921.


Yan MB-6376 Make Milmove Header Storybook Dynamic

Description
Explain a little about the changes at a high level.
Reviewer Notes
Please verify that it is ok Memory Router the way I am using it.
Check my css please!
Setup
Add any steps or code to run in this section to help others prepare to run your code:
make storybook

Under Components, Headers, MilMove Header, Milmove
Code Review Verification Steps

[x] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[x] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Warnings

:warning:

It looks like you are attempting to bypass a linter rule, which is not within
security compliance rules.
** Contains a rule that is not in the permitted eslint list. You are free to disable only: (
no-underscore-dangle
,prefer-object-spread
,object-shorthand
,camelcase
,react/jsx-props-no-spreading
,react/destructuring-assignment
,react/forbid-prop-types
,react/prefer-stateless-function
,react/sort-comp
,import/no-extraneous-dependencies
,import/order
,import/prefer-default-export
,import/no-named-as-default
) **
Please remove the bypass code and address the underlying issue. cc: @transcom/Truss-Pamplemoose

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-6376

  Generated by :no_entry_sign: dangerJS against c97eef4ee991f74ae914222c6537ce02db669cd7

Warnings

:warning:

It looks like you are attempting to bypass a linter rule, which is not within
security compliance rules.
** Contains a rule that is not in the permitted eslint list. You are free to disable only: (
no-underscore-dangle
,prefer-object-spread
,object-shorthand
,camelcase
,react/jsx-props-no-spreading
,react/destructuring-assignment
,react/forbid-prop-types
,react/prefer-stateless-function
,react/sort-comp
,import/no-extraneous-dependencies
,import/order
,import/prefer-default-export
,import/no-named-as-default
) **
Please remove the bypass code and address the underlying issue. cc: @transcom/Truss-Pamplemoose

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-6376

  Generated by :no_entry_sign: dangerJS against c97eef4ee991f74ae914222c6537ce02db669cd7


FW-1019 Create script to setup language for local dev work

These changes add a script to create a language with some basic words, phrases, and an alphabet for frontend development.  This script could be added to in the future as more items are needed.
To run the script after starting up the backend/initial setup, run the command from the frontend directory:
npm run local:language:setup
To remove the created language run the command from the frontend directory:
npm run local:language:teardown

Can one of the admins verify this patch?

Checked again this morning and stack trace above was most likely due to cruddy wifi. Script works fine, just need to tackle the issue of dir for cloning :)

Checked again this morning and stack trace above was most likely due to cruddy wifi. Script works fine, just need to tackle the issue of dir for cloning :)

Updated the pull request to include the changes requested. Batch/Utils is now stored in a temp folder and I have added checking to ensure the git clone completes sucessfully.
Thanks @davidlacho!


createNodeArray always makes a new nodeArray when given a nodeArray

fixes #59115

@typescript-bot perf test this

I suspect this will be bad for other cases where reuse is actually intended, and I’m not sure whether that will show up on the perf suite, but we can see. I think it would probably be better to have just the one call we identified in checker.ts do something different to ensure it always creates a new NodeArray.

@typescript-bot perf test this


Failue in case that the very last two points of a track have exactly the same location

One of my tracks contains two exactly same located waypoints at the very end of the track. In this case the algortihm fails. I have made a test and a hack solution which solves this case, see
https://github.com/graphhopper/map-matching/commit/992998dd829815f4cebc2961c828b49b9affc844
This hack solves the problem I had. I didn't test if two consecutive nodes at an arbitrary location somewhere in between the first and the last waypoint of a track would be also a problem and if the change would work in such a case.

Do you have an example where this occurs?

Sorry, currently I can't reproduce the issue any more. Maybe because of the recent change in maxSearchMultiplier=50 to maxSearchMultiplier=100. I'll need to do some more tests, but his may take a while.

I have tried a lot to reproduce the issue without success. I have changed too much in the meantime (OSM input file, graphhopper-web, parameters).

Ok, feel free to reopen at any time :)


Add a Write-Up for January 2018 - Alexa

Team members will produce a write-up of the most important things they have worked on since last Community Meeting, the problems they have found and what they plan to do in the next weeks (that can be a bit blurry, and that's fine). These write-ups will be published as a blog post for the community to review on Monday before Friday's meeting.
Create your own Write-Up for Community Meeting 06 using the same structure as https://raw.githubusercontent.com/aragon/aragon-wiki/master/docs/meetings/community/write-ups/cm06/tatu.md
Must be submitted by end of day, Thursday 1st of February 2018!

Operations:

Organized and Booked Q1 Team Offsite
Worked on finding payment service providers
Met with our new law firm to set up payment in ETH and ANT
Sent final reports from December to our accountants to close out FY2017
Making payments to service providers, ordering equipment for the team, paying conference sponsorships and community awards and lots of small details like that.
January Payroll

Next:

Work with our accountants to finalize and audit FY2017 reporting
Help get payroll application and automated payment to Lawyers off the ground
Start on Q2 Offsite
Work on finalizing logistics for Q1 Events/Meetups/Conferences


Add ChildBuilder::commands method

Objective
Access the Commands directly from within a with_children closure.
Solution
Add a .commands() method to ChildBuilder to access Commands directly.

parent.commands().insert_resource(ImportantLocation(entity)); I wonder what it means to insert a resource into a parent?

I agree with @Ixentus and imagine that this could be quite confusing. In the case of your documentation example, I think it would be clearer to remember the entity and insert the resource later on after spawning.
Do you have other use cases where you need command access inside the with_children closure?

While this doesn't expose anything that's not already possible through ChildBuilder::add_command, as mentioned above I think it isn't a good api to expose as it can bring errors.
I would prefer to have specialised functions on the ChildBuilder to issue the commands you want, with a clear name.

Would it help if the method name said it wasn't attached to the parent? Something like commands_unattached_to_parent or raw_commands? Another alternative is to make a method commands_without_parent(|commands| ...) but adding another layer of closures seemed pointless.
And yes, this doesn't formally add anything that ChildBuilder::add_command doesn't already do, so if you don't like this method, then that one should also be removed.
For my use case, I think storing the entity in a local to run after the fact breaks the locality of reading, making it harder to understand what the code is doing. The declared local, setting the local, and then actually inserting the resource with the local will all be in completely different locations. Like, they are multiple screens away.

And yes, this doesn't formally add anything that ChildBuilder::add_command doesn't already do, so if you don't like this method, then that one should also be removed.

There's something to be said for both "make the hard things hard" and "there should be only one way to do things". I think Ixentus raises an important point about the confusion this could induce.
In general I'm not thrilled with the level of mental hoops required to work with ChildBuilder. My preference is to deprecate it completely in favor of relations (#1627), but that's a long way off.

So if I understand correctly, you're adding Commands to the Childbuilder to use Commands inside it. However you can trivially do this by adding a second mut Commands to the system parameters:
fn setup_locations(mut commands: Commands, mut commandsb: Commands) {
    commands
        .spawn()
        .insert(Transform::from_xyz(1.0, 0.0, 0.0))
        .insert(GlobalTransform::default())
        .with_children(|parent| {
            let entity = parent
                .spawn()
                .insert(Transform::from_xyz(1.0, 0.0, 0.0))
                .insert(GlobalTransform::default())
                .id();

            commandsb.insert_resource(ImportantLocation(entity));
        });
}

I'm not sure this is even documented though, so this PR made sense :)

I don't forsee this being approved, so I'm going to close it. Do note that the underlying motivation is still there, and that add_command still exists with the same footguns.


[CONTROLLER-RECORDER]fix domain state error

Phenomenon and reproduction steps
Root cause and solution
if get cloud data, recorder should update domain state info in any case
Impactions
Test method
Affected branch(es)

main

Checklist

[ ] Dependencies update required
[ ] Common bug (similar problem in other repo)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Disable Left Click trigger for Context Menu

This PR will disable the left-click trigger for the context menu, as part of https://github.com/iterative/vscode-dvc/issues/2256
It also moves the header components to a sub-folder to help navigation a bit.

I'll fix what's missing. With what's been merged back from the other PR, there shouldn't be much left.

Re-opened the wrong PR


Make MetricPusher Disposable

MetricPusher should dispose internal HttpClient in case it was created by the pusher to avoid resource leaks.

Comment were addressed


Traffic Proportion Metrics

I have been following the progressive rollout features across multiple projects for some time now. I was very interested when I saw this repo as a direct extension to Knative. As I was reading the design document I noticed this question raised and I felt compelled to share (if helpful) some prior art that may be useful.

Per each stage, how do we detect the end?
I have not found out the way to detect the correct traffic proportion has been really assigned to the revision. For example, I want to distribute 50% of the traffic to Revision A by configuring the Route. Which parameter can we check to indicate there is actually 50% of the traffic going to Revision A? If anyone knows how we can do it, please leave your suggestions here.

In Argo Rollouts there are customizable Analysis Templates which support several providers including prometheus.
https://argoproj.github.io/argo-rollouts/features/analysis/#background-analysis
With the prometheus specific provider you can use istio_requests_total (when using istio) to determine the total request and how they are being routed. I believe this is the same datasource that Kiali uses for all it's visualizations.
Flagger also has an integration for Istio and Contour with a metrics option in analysis named request-success-rate. I haven't dived into their source code yet to see where this metric is pulled specifically from but it may be worth investigating.
https://fluxcd.io/flagger/tutorials/istio-progressive-delivery/#bootstrap
I am excited to see where this extension goes! I would love to see more features from Argo Rollouts and Flagger added over time!

@wSedlacek Thank you for the useful comments and your attention to this repo.
In the design doc, I listed several principles to implement this feature: try to use the existing code or features as much as possible, and try to change the components as few as possible.
I added a similar CRD in this repo to the one Rollout that argo uses to manage the progress to shift the traffic, control the percentage and the target number of replicas for each step, until 100% of the traffic has been shifted to the new revision.
You can try out this extension: https://github.com/knative-extensions/serving-progressive-rollout/blob/main/DEVELOPMENT.md based on the serving you installed.
However, we have already cut the release for 1.13: https://github.com/knative-extensions/serving-progressive-rollout/releases/tag/knative-v1.13.3


Recognize arbitrary Json responses

Currently the s1st parser serializes json responses with automatically: https://github.com/zalando/swagger1st/blob/183cba7e30e62da6a23df9078e7062830885d72e/src/io/sarnowski/swagger1st/parser.clj#L344
Unfortunately this happens only if the content type matches "application/json" exactly. In other words

"application/problem+json"
"application/json; charset=UTF-8"
...

are not recognized and hence not serialized.
Swagger1st should either support all possible json formats (like https://github.com/ring-clojure/ring-json) or not none at all.

I think #45 and #49 are related


Pushing to new Version

Hi Jordan,
thanks for making the AOSP-Picker available. Would you mind updating it? This should be easy as only language files were updated since the current master of your repository. More languange support is always better.
Thanks.

Hi there daMihe,
Sure, I'll make sure to update it as soon as I get a chance (probably within the next week or so).
Hope that's okay.
Thanks,
Jordan

Hi Jordan,
yes sure it's okay.
Thanks for your quick reaction,
Michael

I've now updated to the latest version 🎉
Please let me know if any issues but for now I'll close this off.
Thanks,
Jordan

Thanks for your effort. I'm sorry to say i can't use it. Gradle simply can't resolve it. 1.0.1 works but not version 1.0.2. If looking to the bintray maven at https://dl.bintray.com/jordanrobinson/maven/uk/co/jordanrobinson/android-color-picker/ i can see inside 1.0.1 more files (-javadoc.jar, -sources.jar, .pom) than in 1.0.2. This may be the cause for it (especially pom-file?).

Michael

Ah, sorry! Bintray changed their upload process and interface, so I wasn't sure if I'd done it right.
I've manually uploaded a new pom, are you okay to try it now and let me know?
Thanks,
Jordan

Thank you, now it works fine. Just for your reference: i'm/we're using it here: https://bitbucket.org/frigus02/car-report (PR there is ready to include...)
Thanks again for your quick reaction,
Michael

Great! Glad to help 😄


Epic Retro Noir Blanche

Hi mate, I finished the mod of my theme. Everything should be in order. Thumbnail is in the folder. Thanks again. J

Beautiful


[DO NOT MANUAL MERGE] Release Qualification

Trigger release qualification jobs
none

@silverdev: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-auth-default

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silverdev: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-auth-default

prow/daily-e2e-rbac-no_auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-no_auth-default

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silverdev: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-auth-default

prow/daily-e2e-rbac-no_auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-no_auth-default

prow/daily-e2e-rbac-no_auth.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silverdev: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-auth-default

prow/daily-e2e-rbac-no_auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-no_auth-default

prow/daily-e2e-rbac-no_auth.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-no_auth

prow/daily-e2e-rbac-auth.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silverdev: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-auth-default

prow/daily-e2e-rbac-no_auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-no_auth-default

prow/daily-e2e-rbac-no_auth.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-no_auth

prow/daily-e2e-rbac-auth.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-auth

prow/daily-e2e-cluster_wide-auth.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-cluster_wide-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silverdev: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-auth-default

prow/daily-e2e-rbac-no_auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-no_auth-default

prow/daily-e2e-rbac-no_auth.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-no_auth

prow/daily-e2e-rbac-auth.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-rbac-auth

prow/daily-e2e-cluster_wide-auth.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-cluster_wide-auth

prow/daily-e2e-cluster_wide-auth-default.sh
e3d9366be370ad3469fb7eabee0adfb32191166b
link
/test daily-e2e-cluster_wide-auth-default

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Style fails to load in Kali

Issue Description
King-Phisher client GUI style fails to load in Kali Linux Rolling Edition.
Reproduction Steps

Start King Phisher in Kali Linux

Environment Details
Host OS: Kali 2 Rolling Edition
Linux kali 4.7.0-kali1-amd64 #1 SMP Debian 4.7.5-1kali3 (2016-09-29) x86_64 GNU/Linux
Error Details / Stack Trace
root@kali:~# python3 /opt/king-phisher/KingPhisher -L DEBUG
WARNING  it is not necessary to run the king phisher client as root
DEBUG    king phisher version: 1.5.2-beta (rev: 6ff175b1) python version: 3.5.2
DEBUG    client running in process: 6824 main tid: 0x7f428eb1b700
DEBUG    using ui data from glade file: /opt/king-phisher/data/client/king_phisher/king-phisher-client.ui
DEBUG    gi.repository GLib version: 2.50.0
DEBUG    gi.repository GObject version: 3.22.0
DEBUG    gi.repository Gtk version: 3.22.1
DEBUG    gi.repository VTE version: 2.91
DEBUG    matplotlib version: 1.5.3
INFO     loading the config from disk
INFO     loading 2 plugins
DEBUG    plugin 'check_for_updates' has been loaded
DEBUG    plugin 'data_collection' has been loaded
DEBUG    client loaded in 0.01 seconds
DEBUG    resetting the gtk-theme-name property to it's default value
DEBUG    resetting the gtk-icon-theme-name property to it's default value
DEBUG    loading style from css file: /opt/king-phisher/data/client/king_phisher/style/theme.v2.css
ERROR    css parser error (not a number) in /opt/king-phisher/data/client/king_phisher/style/theme.v2.css:98
ERROR    css parser error (Expected a string.) in /opt/king-phisher/data/client/king_phisher/style/theme.v2.css:98
ERROR    there was an error parsing the css file, it will not be applied as a style provider

@wolfthefallen my wild guess is that this line might need to be updated to font-weight instead of font. Don't forget that the CSS is generated from the SCSS file.

This has been fixed and is now sitting pretty in the dev branch.


Do not support numbers longer than 32bits

When trying to calculate stuff will result in numbers bigger than 32bits, overflow happens as shown below

Same for anding operation  as shown

Not sure if this completely solves your problem but you can use bignumber to get around at least one example here:


Boolean and hole operations: make sure the parts are in-proximity of each other

If the user is trying to Union two parts, but they are not touching, the operation should fail. The Part::isCollidingWithPart method can be used to check for collisions (https://codetocad.github.io/CodeToCAD/docs.html#Part_isCollidingWithPart).
This need a regression test for all providers.

This is resolved by #267


能添加一个颜色选择器吗

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome<IP_ADDRESS>

确实，没有颜色选择器，没有色板

me too


Docker and Make file

This PR:

Updates versions of orbit-db and ipfs
Adds a Dockerfile and Makefile

Context: I'm going to be doing some side by side testing of bind and orbitdns to determine the feasibility of swapping it out for a small LAN "lab"

Keep me informed on the results. Unfortunately I have't worked on orbitdns very much after coming across some serious flaws in the design... Thinking about doing a similar system to how Ethereum ports normal domains over to ENS names. :)

Can you tell me a bit more about the flaws in the design?

@aphelionz The way independent naming system links clear net domains requires the end user attempting to resolve the name to have a clearnet DNS connection. The idea was to be able to operate in any environment operating, as long as a connection to OrbitDB is established. I would have to revise this model, where a root TLD operating would have to valid the DNS TXT record for the correct INS name, then signing a record pointing the Orbitdns proxy domain to the INS name.
Example:
Example.com -> TXT record (INS name/provable key),
(In orbitdns) .clearnet root receives a request. Root signs example.com.clearnet. Root checks the domain to see if the TXT has been removed (revoking internal authority).
Additional modules will have to be made to properly provide root TLD operators with the capability to automate the process.
That being said I need to revise a lot of code to make the process of adding these new functionalities.
INS being a cryptographically provable name space similar to IPNS. With addition capabilities such as updating signing keys, or multisignature keys along with multiple records/dns capabilities.


ACLableSyncedObjectEnabled

The ACLableSyncedObjectEnabled parameter now allows customer admins to run the Enable-RemoteMailbox cmdlet and specify the object be an ACLableSyncedMailboxUser.  The documentation should be updated to provide this information for customers. -Kelly

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

ID: fb103c0b-9021-3a77-0bf6-601df9a0fe38
Version Independent ID: 561d8c53-5019-4a31-efa1-c2b635818f5a
Content: New-RemoteMailbox (exchange)
Content Source: exchange/exchange-ps/exchange/federation-and-hybrid/New-RemoteMailbox.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

Based on this issue and #566, I updated the ACLableSyncedObjectEnabled parameter/switch descriptions in Enable-RemoteMailbox, New-RemoveMailbox, Set-RemoteMailbox, and Set-Organization.


datadog_scaler: handle mising { on dd query

It's probably nice to handle the error gracefully rather than panic in case of unexpected datadog scaler query
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Tests have been added
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[ ] Changelog has been updated and is aligned with our changelog requirements

Fixes #2625

Thanks for working on this! This looks good to me. 👍

/run-e2e datadog*


Installation Error (Windows 10)

Please answer the following before submitting your issue:
Note: Please include any substantial examples (debug session output,
stacktraces, etc) as linked gists.

What version of Delve are you using (dlv version)? None

What version of Go are you using? (go version)? 1.10.3

What operating system and processor architecture are you using?
Windows 10 - 64bits

What did you do?
I'm trying to manually install dlv with the command:
go get -u github.com/derekparker/delve/cmd/dlv

What did you expect to see? Successful installation.

What did you see instead?

There is no tracking information for the current branch.
Please specify which branch you want to merge with.See git-pull(1) for details.

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=origin/<branch> master```

Try deleting $GOPATH/src/github.com/derekparker/delve/ and then doing the go get again. Either way this is a problem with your setup, not a bug in delve.


Explore functionality?

I would like to suggest a functionality that I miss very much in your page: an exploration functionality.
When one first browses the webpage there are no papers on display, and the search box user-experience assumes the user already knows what they are looking for. It would be great if the page had a view with the latest/most-cited, papers, or an initial network view, etc.

Thank you for your feedback. In the case that you are unfamiliar with the topic, our review paper is a good place for you to get started. You may also play with the "feeling lucky" button.
We have experimented with citation count with Google Scholar, but Google isn't friendly with bots. If you have a suggestion, please let us know!