build and run problems[Bug]

here as the ApacheTVM site will not allow links.
Computer
I’m running on Ubuntu 18.04 LTS. Windows is not possible for me as I do not have access to Visual studio Enterprise 2019 and most of the download websites are blocked by my companies firewall. My Ubuntu 18.04 LTS has no restrictions. I want to test deployment onto Xilinx FPGAs.
Why I’m evaluating Apache TVM
I’m looking for a tool to port trained machine learning onto various targets including FPGAs, and Apache TVM:
•	Has a lot of relevant major companies backing it
•	Has a lot of active current contributors on GIT
•	Aims to solve many of the problems we are interested in
•	Claims to support pipelining and parallelism, so implementing a CNN with parallel units in each layer and a pipeline stage for each CNN layer may be possible.
•	Has a stage which optimises CNN layers by combining them were possible
The good
The only thing that I have got to work is compiling the V8 code from the website:
https://tvm.apache.org/download
Following the instructions in the page
https://tvm.apache.org/docs/install/from_source.html
Proposal 1
Page:
https://tvm.apache.org/docs/install/from_source.html
Is too complex becuase there are many different options and some such as conda are not chronological on the page. I propose providing a page like this:
https://tlcpack.ai/
With options for:
•	Windows Mac Linux
•	Development, source, docker, docker prebuilt
•	Conda pip source
•	Options for the common flags that are likely be changed
•	etc
Use the options to write a script file with a set of chronological commands to install Apache TVM, with comments stating what is happening.
The script file has the benefit that they can be run as part of a nightly build to verify that the various software builds compile. The builds provide versions of TVM that can be used to verify the commands in the tutorials. The tutorials should be run as part of the nightly build. These tests, which consist of builds followed by tutorial tests, can all be run in parallel on different virtual machines.
Problem 1 Hello world does not work (The first TVM command in the first tutorial)
Successfully installing the v0.8 from the https://tvm.apache.org/download tvm (Ubuntu 18.04.6 LTS, x64, no GPU, with LLVM, miniconda)
To familiarise myself with Apache TVM I decided to run the  tutorial.
The onnx download works, but the first line running ApacheTVM fails, so I can’t get past the first tvm  step in the first tutorial. It appears that the example onnx example is too a message. Error output:
https://tvm.apache.org/docs/install/from_source.html
wget https://github.com/onnx/models/raw/main/vision/classification/resnet/model/resnet50-v2-7.onnx
(tvm-build) dlaod@dlaod-HP:~/apachetvm/apache-tvm-src-v0.8.0.rc0$ tvmc compile \

--target "llvm"
--output resnet50-v2-7-tvm.tar
resnet50-v2-7.onnx
[13:57:32] /home/dlaod/apachetvm/apache-tvm-src-v0.8.0.rc0/src/target/target_kind.cc:164: Warning: Unable to detect CUDA version, default to "-mcpu=sm_20" instead
[13:57:32] /home/dlaod/apachetvm/apache-tvm-src-v0.8.0.rc0/src/target/target_kind.cc:190: Warning: Unable to detect ROCm compute arch, default to "-mcpu=gfx900" instead
[13:57:32] /home/dlaod/apachetvm/apache-tvm-src-v0.8.0.rc0/src/target/target_kind.cc:204: Warning: Unable to detect ROCm version, assuming >= 3.5
[13:57:32] /home/dlaod/apachetvm/apache-tvm-src-v0.8.0.rc0/src/target/target_kind.cc:164: Warning: Unable to detect CUDA version, default to "-mcpu=sm_20" instead
[13:57:32] /home/dlaod/apachetvm/apache-tvm-src-v0.8.0.rc0/src/target/target_kind.cc:190: Warning: Unable to detect ROCm compute arch, default to "-mcpu=gfx900" instead
[13:57:32] /home/dlaod/apachetvm/apache-tvm-src-v0.8.0.rc0/src/target/target_kind.cc:204: Warning: Unable to detect ROCm version, assuming >= 3.5
[libprotobuf ERROR google/protobuf/io/coded_stream.cc:207] A protocol message was rejected because it was too big (more than 67108864 bytes).  To increase the limit (or to disable these warnings), see CodedInputStream::SetTotalBytesLimit() in google/protobuf/io/coded_stream.h.
Traceback (most recent call last):
File "/home/dlaod/.local/bin/tvmc", line 33, in
sys.exit(load_entry_point('tvm==0.8.0', 'console_scripts', 'tvmc')())
File "/home/dlaod/.local/lib/python3.6/site-packages/tvm-0.8.0-py3.6-linux-x86_64.egg/tvm/driver/tvmc/main.py", line 94, in main
sys.exit(_main(sys.argv[1:]))
File "/home/dlaod/.local/lib/python3.6/site-packages/tvm-0.8.0-py3.6-linux-x86_64.egg/tvm/driver/tvmc/main.py", line 87, in _main
return args.func(args)
File "/home/dlaod/.local/lib/python3.6/site-packages/tvm-0.8.0-py3.6-linux-x86_64.egg/tvm/driver/tvmc/compiler.py", line 137, in drive_compile
tvmc_model = frontends.load_model(args.FILE, args.model_format, args.input_shapes)
File "/home/dlaod/.local/lib/python3.6/site-packages/tvm-0.8.0-py3.6-linux-x86_64.egg/tvm/driver/tvmc/frontends.py", line 404, in load_model
mod, params = frontend.load(path, shape_dict, **kwargs)
File "/home/dlaod/.local/lib/python3.6/site-packages/tvm-0.8.0-py3.6-linux-x86_64.egg/tvm/driver/tvmc/frontends.py", line 169, in load
model = onnx.load(path)
File "/home/dlaod/.local/lib/python3.6/site-packages/onnx/init.py", line 115, in load_model
model = load_model_from_string(s, format=format)
File "/home/dlaod/.local/lib/python3.6/site-packages/onnx/init.py", line 152, in load_model_from_string
return _deserialize(s, ModelProto())
File "/home/dlaod/.local/lib/python3.6/site-packages/onnx/init.py", line 95, in _deserialize
decoded = cast(Optional[int], proto.ParseFromString(s))
google.protobuf.message.DecodeError: Error parsing message
(tvm-build) dlaod@dlaod-HP:~/apachetvm/apache-tvm-src-v0.8.0.rc0$

Problem 2 Docker does not build with conda
I thought I’d try a second build of Apache TVM to see if it would run, but Apache TVM will not build.
Building docker does not work, even though I have the correct python version because conda has the wrong python version.
Install conda as recommended in
https://tvm.apache.org/docs/install/from_source.html
(without the following activate tline it says that everything is upto date, but the tutorial fails)
Conda activate tvm-build
https://tlcpack.ai/
states v0.8 Linux Conda No cuda
conda install tlcpack -c tlcpack
without conda my python is 3.7.11
in conda my python is 3.10.4
error message running
(tvm-build) dlaod@dlaod-HP:~/apachetvm/docker/conda$ conda install tlcpack -c tlcpack
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: |
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:
Specifications:

tlcpack -> python[version='>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0']

Your python: python=3.10
If python is on the left-most side of the chain, that's the version you've asked for.
When python appears to the right, that indicates that the thing on the left is somehow
not available for the python version you are constrained to. Note that conda will not
change your python version to a different minor version unless you explicitly specify
that.
The following specifications were found to be incompatible with your system:

feature:/linux-64::__glibc==2.27=0
feature:|@/linux-64::__glibc==2.27=0

Your installed version is: 2.27
(tvm-build) dlaod@dlaod-HP:~/apachetvm/docker/conda$ python --version
Python 3.10.4
(tvm-build) dlaod@dlaod-HP:~/apachetvm/docker/conda$
Problem 3 Docker NO conda
In v8 dir
docker ci_cpu
states this script does not work in python 3.6 the minimum is 3.7. The python installed on the computer is 3.7.11. The python being downloaded as part of the docker computer is 3.6.
Selecting previously unselected package python3.6-dev.
Preparing to unpack .../07-python3.6-dev_3.6.9-1~18.04ubuntu1.7_amd64.deb ...
Unpacking python3.6-dev (3.6.9-1~18.04ubuntu1.7) ...
Selecting previously unselected package python3-dev.
Preparing to unpack .../08-python3-dev_3.6.7-1~18.04_amd64.deb ...
Unpacking python3-dev (3.6.7-1~18.04) ...
Selecting previously unselected package python3-pkg-resources.
Preparing to unpack .../09-python3-pkg-resources_39.0.1-2_all.deb ...
Unpacking python3-pkg-resources (39.0.1-2) ...
Selecting previously unselected package python3-setuptools.
Preparing to unpack .../10-python3-setuptools_39.0.1-2_all.deb ...
Unpacking python3-setuptools (39.0.1-2) ...
Setting up python3-pkg-resources (39.0.1-2) ...
Setting up libexpat1-dev:amd64 (2.2.5-3ubuntu0.7) ...
Setting up python3-lib2to3 (3.6.9-1~18.04) ...
Setting up python3-distutils (3.6.9-1~18.04) ...
Setting up libpython3.6:amd64 (3.6.9-1~18.04ubuntu1.7) ...
Setting up libpython3.6-dev:amd64 (3.6.9-1~18.04ubuntu1.7) ...
Setting up python3-setuptools (39.0.1-2) ...
Setting up python3.6-dev (3.6.9-1~18.04ubuntu1.7) ...
Setting up dh-python (3.20180325ubuntu2) ...
Setting up libpython3-dev:amd64 (3.6.7-1~18.04) ...
Setting up python3-dev (3.6.7-1~18.04) ...
Processing triggers for libc-bin (2.27-3ubuntu1.5) ...
ERROR: This script does not work on Python 3.6 The minimum supported Python version is 3.7. Please use https://bootstrap.pypa.io/pip/3.6/get-pip.py instead.
The command '/bin/sh -c bash /install/ubuntu1804_install_python.sh' returned a non-zero code: 1
ERROR: docker build failed.
(base) dlaod@dlaod-HP:~/apachetvm/apache-tvm-src-v0.8.0.rc0$ python --version
Python 3.7.11
(base) dlaod@dlaod-HP:~/apachetvm/apache-tvm-src-v0.8.0.rc0$
Problem 4 Docker images are not available
I thought I’d try a third build of Apache TVM to see if it would run, but Apache TVM will not build.
This is external really, but the downloads of the prebuilt docker do not work.
https://hub.docker.com/r/tlcpack/ci-cpu
(base) dlaod@dlaod-HP:~/apachetvm/docker/prebuilt$ docker pull tlcpack/ci-cpu
Using default tag: latest
Error response from daemon: manifest for tlcpack/ci-cpu:latest not found: manifest unknown: manifest unknown
(base) dlaod@dlaod-HP:~/apachetvm/docker/prebuilt$
Problem 5 Docker for Vitis does not work
As the introduction does not work I thought I’d skip the introduction and go straight to FPGA synthesis. Again the docker build does not work, but in a different way. Apache TVM document:
•	tvm/docs/how_to/deploy/vitis_ai.rst
But 'https://apt.kitware.com/ubuntu bionic InRelease' is not signed or the public key cannot be obtained.
tvm$ ./docker/build.sh demo_vitis_ai bash
(base) dlaod@dlaod-HP:~/apachetvm/vitis/tvm$ ./docker/build.sh demo_vitis_ai bash
Using default context path: /home/dlaod/apachetvm/vitis/tvm/docker
WORKSPACE: /home/dlaod/apachetvm/vitis/tvm/docker/../
CI_DOCKER_EXTRA_PARAMS:
COMMAND: bash --allow-unauthenticated
CONTAINER_TYPE: demo_vitis_ai
BUILD_TAG: tvm
DOCKER CONTAINER NAME: tvm.demo_vitis_ai
DOCKER_IMAGE_TAG: latest
DOCKER_IMG_SPEC: tvm.demo_vitis_ai:latest
Building container (tvm.demo_vitis_ai)...
Sending build context to Docker daemon    235kB
Step 1/19 : FROM xilinx/vitis-ai:1.4.916
---> a325686c45a3
Step 2/19 : RUN apt-get update --fix-missing
---> Running in f5acf8b929e9
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:4 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1,344 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB]
Get:7 http://ppa.launchpad.net/timsc/opencv-3.4/ubuntu bionic InRelease [15.9 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [29.8 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [3,167 kB]
Get:12 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic InRelease [20.8 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [2,272 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [942 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [12.9 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [12.2 kB]
Get:17 https://apt.kitware.com/ubuntu bionic InRelease [11.0 kB]
Get:18 http://ppa.launchpad.net/timsc/opencv-3.4/ubuntu bionic/main amd64 Packages [11.1 kB]
Get:19 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [21.1 kB]
Get:20 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [1,496 kB]
Err:17 https://apt.kitware.com/ubuntu bionic InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6AF7F09730B3F0A4
Get:21 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [2,732 kB]
Get:22 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic/main amd64 Packages [50.4 kB]
Get:23 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [909 kB]
Reading package lists... Done
W: GPG error: https://apt.kitware.com/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6AF7F09730B3F0A4
E: The repository 'https://apt.kitware.com/ubuntu bionic InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
The command '/bin/sh -c apt-get update --fix-missing' returned a non-zero code: 100
ERROR: docker build failed.
(base) dlaod@dlaod-HP:~/apachetvm/vitis/tvm$ ./docker/build.sh demo_vitis_ai bash
tried:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6AF7F09730B3F0A4
then rerunning ./docker/build.sh demo_vitis_ai bash
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 30B3F0A4
then rerunning ./docker/build.sh demo_vitis_ai bash
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 6AF7F09730B3F0A4
then rerunning ./docker/build.sh demo_vitis_ai bash
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 30B3F0A4
then rerunning ./docker/build.sh demo_vitis_ai bash
And some other versions of the above. They day the key exists and is not updated
wget -O - https://apt.kitware.com/keys/kitware-archive-latest.asc 2>/dev/null | gpg --dearmor - | sudo tee /usr/share/keyrings/kitware-archive-keyring.gpg >/dev/null
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 7EA0A9C3F273FCD8
sudo apt-get update
then rerunning ./docker/build.sh demo_vitis_ai bash
adding
/etc/apt/apt.conf.d/99myown
with line
APT::Get::AllowUnauthenticated "true";
then rerunning ./docker/build.sh demo_vitis_ai bash
apt-get update --allow-unauthenticated
then rerunning ./docker/build.sh demo_vitis_ai bash
sudo apt-get update --allow-insecure-repositories
then rerunning ./docker/build.sh demo_vitis_ai bash
tried modifiying
apps/microtvm/reference-vm/zephyr/base-box/base_box_setup.sh
docker/install/ubuntu_install_zephyr.sh
but the code is not run
Proposal 2
I recommend verifying all the above in nightly build script files on blank virtual machines, so problems can be identified as they occur:
•	External dependencies can mean that https://tvm.apache.org/download works one day and fails the next, and needs to be fixed.
•	Blank virtual machines mean that the build is not dependant on things that have previously been manually fixed and forgotten to be added to the script files.
•	I believe that Jenkins can schedule things like this for you and many other combinations of  tools and script files.

Unclear what the problem is.


improved the .hbl command

Added links to freakyhax and ninjhax, corrected some grammar mistakes and overall phrased it a bit clearer.

👍


New to github but want to contribute with translations

Hi,
I'd like to contribute to Turkish translations for plugin and website. I already completed, can you please guide me to push codes?
Best,
Kerem

Hi there,
Thank you for the help.
For the plugin: https://github.com/burocratik/outdated-browser/tree/feature/languages, just fork and add the new language
For the site: https://github.com/burocratik/outdated-browser/tree/feature/languages-website , for and add language.
If you having problems you can always write the translation here and I will add the files ;)
Cheers
Alex

Hi Alex,
I just commit these. I could not test properly because php is not installed on my machine. Hope everything is OK.
plugin:
https://github.com/keremdemirer/outdated-browser/commit/8d386b5ec7e4663fa3740189378c2a8f515149f0
website:
https://github.com/keremdemirer/outdated-browser/commit/278fc312f98810fa023f00d37d73c1f112e748ca
Cheers,
Kerem

@keremdemirer
Thank you so much, will do asap.


rna-transcription: make object-based and add starter implementation

Changed rna-transcription to have an object based implementation (see issue #177) and added starter implementation as it is currently the second exercise in the new ordering (see issue #178).

Looks good! I'm not sure whether I prefer returning null vs throwing an unimplemented exception in the stubbed implementation - I feel like null could in general lead to a confusing error message when the tests are first run, and that the thrown exception route gives us more control over that messaging and experience. What do you think, Frida? I don't feel particularly strongly either way so I'm happy to go with whatever you decide, just let me know :)

I didn't think about that, thanks for mentioning it! :) An exception is probably better. Do you think UnsupportedOperationException with message "Method has not been implemented yet" would be okay?

@FridaTveit that exception type sounds good to me, and to others!

Thanks, @FridaTveit!


Hardware acceleration RPI4 FFmpeg

I'm trying to get to work hardware acceleration on my Raspberry pi 4-64. I'm using FFmpeg and AFAIK hwaccel can be reached by using OpenMAX or V4L2-M2M.
After '--enable-omx' and 'enable-omx-rpi' for FFmpeg, build fails with error: 'OMX_Core.h not found'. If I will provide manually omx headers, then it will compile but FFmpeg encoding will fail due to missing libraries: bcm_host.so and libopenmaxil.so
I have tried reverting to userlandby DISABLE_VC4GRAPHICS = "1", it produced bcm_host.so, but not libopenmaxil.so. I have tried different combinations of virtual providers and graphics settings but without success.
Is it possible to access omx hardware acceleration on RPI4-64?
Steps to reproduce the issue:

Download latest Poky distro, meta-openembedded, meta-raspberrypi
Enable omx, omx-rpi support for FFmpeg
Link headers for FFmpeg
Build and try to use h264_omx

How do I get missing library libopenmaxil.so and everything I need for hwaccel?
poky master: commit 5d47cdf448b6cff5bb7cc5b0ba0426b8235ec478
meta-openembedded master: commit daa50331352c1f75da3a8ef6458ae3ddf94ef863
meta-raspberrypi master: commit 8d163dd844c3737d1557395c1eb512ebac86bdc0
BTW, by using V4L2-M2M, I'm getting green shadows on the resulting video. Maybe can someone point me in the right direction?

Userland doesn't support 64bit compilation - see https://github.com/raspberrypi/userland/issues/314. Maybe using precompiled binaries would work but that's a route we haven't tested it for a while (at least I didn't).

Thanks, I built a 32-bit version and now I'm able to use hardware encoding. Thanks.


Fix allOf wrong type error message

Synopsis
When allOf was not an array, library was returning an error saying anyOf must be of an array. This PR fixes this.

@xeipuuv @johandorland can you guys please take a look?

anyone alive here ?

Hello,
This repository is not maintained anymore, the new one is https://github.com/gojsonschema/gojsonschema, could you submit your PR on this one? Thank you!

@Surfoo done https://github.com/gojsonschema/gojsonschema/pull/3


Renaming SqlQuery to just Query to be shorter.

Small change, last one in this branch before I switch to forked repository.
@enisoc

Heh I'd actually prefer going longer / more specific - QueryService, for easy grepping.

The stubs generated by proto compiler now are:
QueryClient
QueryServer
I don't mind going to QueryServiceClient and QueryServiceServer, but I thought that was a bit long... Who else has an opinion? :)

In that case, I vote for "service Query".
Or we could go the other way and rename SqlQuery to StructuredSqlQueryLanguage. That reminds me, I need to stop by the automated ATM machine later...

How about Tablet or VTTablet? Kind of in line with VTGate.

I like VTTablet, will do that.

Hum VTTablet is just too big of a change, then have to rename query.proto to vttablet.proto, and it gets out of hand... I think I'll stick to Query.


fix finding files

For python it over rides and does not append. Thanks!

Current coverage is 94.64%

Merging #116 into master will increase coverage by +14.93% as of 3ab1876

@@            master    #116   diff @@
======================================
  Files            1      21    +20
  Stmts          350    1325   +975
  Branches         0     139   +139
  Methods          0       0
======================================
+ Hit            279    1254   +975
  Partial          0       0
  Missed          71      71

Review entire Coverage Diff as of 3ab1876

Powered by Codecov. Updated on successful CI builds.

Thanks!

👍 Thank you!


Support RKE2 deployments

Overview
RKE2 is a Kubernetes distribution developed by Rancher that targets Governments.
Several community members have expressed a desire to use RKE2 with some of them running into trouble. This ticket is to experiment and provide a clear path forward for users wanting to leverage RKE2.

I think initially this will just be experimentation and validating everything works with RKE2. Given RKE2 seems to be a full Kubernetes deployment where its deployed to a running machine, it might be possible to include an infrastructure option in the sandbox project in the form of VMs.


CanadaBot forking across projects

I've created an issue upstream to get their thoughts on this.
From the issue:

I'd like to understand PRB0t's behaviour with respect to forks a little better. After playing around a little bit, my team and I were able to make a bit of a mess using PRB0t. Check out this PR. Unfortunately, I deleted the repo that the PR is based on, so we can't look at it anymore 😢

When I was originally working on PRB0t (CanadaBot in our case), I forked the repo from a fork of ore-ero. The graph looks like:

canada-ca/ore-ero > VilleDeMontreal/ore-ero > canada-bit/ore-ero

I then used CanadaBot to submit a PR to canada-ca/ore-ero.

What does the community think is the best way for PRB0t to handle these types of situations? Should it be deleting it's fork every single time and then reforking? Should it just attempt to sync its fork with the upstream?

I'll keep an eye on this issue @BassamAjam. Right now, I don't have the perfect solution. I think a good short term fix is to just ensure that the upstream for CanadaBots fork is canada-ca/ore-ero, which is easy to do.

How does it work?  Our instance of PRBot (Canada-bot) has a clone of the repo.  But it's never updated.

It's a little weird, but CanadaBot submits a PR to its fork from the master of the upstream, then it merges it. This is meant to occur every time, but the way the error handling is done, I think it can fail half way through, without updating the forks master.
I've opened an issue to track this.

I've spoken with the creator of PRB0t regarding this issue. He is totally aware of it and open to solutions. I think in the near term, we can probably just deal with it, but longer term we have several options, which I'll post in the previously mentioned issue.

I've fixed this in CanadaBot. Forks are deleted after every pull request is submitted.


[Bug]: Empty table click to modify result set page crashes

ODC version
odc423
OB version

What happened?

What did you expect to happen?
The page will not crash
How can we reproduce it (as minimally and precisely as possible)?
Click to modify the result set in an empty table
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit d159ed302f3b0dc56ea571c7166e65cf8a72ae94
------
咏和
Sun Dec 10 10:59:51 2023 +0800

pass


Add cancelling capability to push non-backpressure aware path

Currently non-backpressure aware Streams run until the event stream itself stops

This can be implemented simply & performantly in the same way the short circuiting is implemented in allMatch etc.

Create a specific Throwable with FillInStackTrace overwriten to represent a cancelled Stream, handle the cancellation in each Operator (throwing it upwards) and finally mark the Stream as cancelled at the top level in Spouts.

Doesn't seem to feasible as many of the key APIs are user controlled for convenience (e.g. Spouts.async)


docs: Add user guide for Zulip on Linux - Fixes: #3359.

I couldn't find any other links to other user documentation like Zulip on Windows or Zulip on Android under templates/zerver/help/index.md
Do I have to add that link to somewhere else?

@akashnimare thoughts on whether this approach makes sense?  I kinda think our current system with sorta 1 article for the app (with maybe subsections for platform-specific things) makes more sense.

Okay, so there could be two approaches -
a) If we go with the current one -

then we could make a new section after Installation guides something like Tips for using Desktop App

and then could make three sub-sections (Linux/macOS/Windows) and the put the content of this PR in Linux section.
b) The other approach is to have three different sections like -

I would prefer the first approach here.

Yeah, I agree.  Closing this as not in line with where we want to go here.


Doesn't available in Homebrew

Could be nice to have this software in homebrew 👍
https://brew.sh/

@herau SpotMenu is available via Homebrew Cask (https://caskroom.github.io/)

@camden thanks a lot !

Hey @camden how does this homebrew cask work? I mean I know how to install stuff using it, but how does it know where to download the latest version of SpotMenu from?

@kmikiy I just find your app and I like it. I happen to install it with brew cask, and it isn't the latest version. So I dig into brew cask a little bit. It seems the version is controlled in this file, but I'm not sure. If it is how brew cask works, you may need to update this file once you get a new release.

Indeed it doesn't have the latest version.
Also, installation through it should be added to README since it's the easiest way to install the app.

@lucasbento I've updated it to download 1.6 following these instructions. I'm guessing it will be available once the Pull Request is accepted.
Update: it has been accepted

@kmikiy: just installed with it, works good, thanks!

Perfect 🙌🏻
Also I updated the README.
Thank you for your contribution.


Issues with signinPopup and signinRedirect methods in Next.js v13.0.5 app

Hi there, hope you are doing great!
First and foremost, thank you for your contributions to the open source community!
I have encountered a blocker issue regarding the signinPopup method from the useAuth hook, when passing the popupWindowTarget: '_self' to the AuthProviderProps.
Here's the code:

src/AuthProvider.tsx

import { useEffect, useState } from 'react';
import type { AuthProviderProps } from 'react-oidc-context';
import { AuthProvider as OIDCProvider } from 'react-oidc-context';
import { WebStorageStateStore } from 'oidc-client-ts';

const OIDC_CONFIG: AuthProviderProps = {
  authority: process.env.NEXT_PUBLIC_MICROSOFT_AUTHORITY,
  client_id: process.env.NEXT_PUBLIC_MICROSOFT_CLIENT_ID,
  redirect_uri: process.env.NEXT_PUBLIC_MICROSOFT_REDIRECT_URI,
  popup_redirect_uri: process.env.NEXT_PUBLIC_MICROSOFT_REDIRECT_URI, // http://localhost:3000
  scope: process.env.NEXT_PUBLIC_MICROSOFT_SCOPE,
  post_logout_redirect_uri: process.env.NEXT_PUBLIC_MICROSOFT_REDIRECT_URI, // http://localhost:3000
  response_type: 'code',
  popupWindowTarget: '_self',
};

export function AuthProvider({ children }: AuthProviderProps) {
  const [config, setConfig] = useState<AuthProviderProps>({ ...OIDC_CONFIG });

  const [timestamp, setTimeStamp] = useState(Date.now());

  useEffect(() => {
    setTimeStamp(Date.now());

    setConfig({
      ...OIDC_CONFIG,
      userStore: new WebStorageStateStore({
        store: window.localStorage,
      }),
    });
  }, []);

// We use the timestamp state to re-render entire OIDCProvider and its children from scratch after first reload
// Since, otherwise, the OIDCProvider does not recognize that the config has been updated with the new userStore
// and the session is never stored in the localStorage

  return (
    <OIDCProvider {...config} key={timestamp}>
      {children}
    </OIDCProvider>
  );
}

src/_app.tsx

import type { ReactNode } from 'react';
import type { NextPage } from 'next';
import type { AppProps } from 'next/app';
import type { UserConfig } from 'next-i18next';
import { appWithTranslation } from 'next-i18next';
import { ThemeProvider } from 'styled-components';

import '$/yup';

import '$/styles/fonts.css';

import i18nConfig from '$/../next-i18next.config';
import { AuthProvider } from '$/auth/AuthProvider';
import GlobalStyle from '$/styles/global';
import themes from '$/styles/themes';

export type NextPageWithLayout<P = Record<string, unknown>> = NextPage<P> & {
  getLayout?: (page: ReactNode) => ReactNode;
};

type AppPropsWithLayout = AppProps & {
  Component: NextPageWithLayout;
};

function App({ Component, pageProps }: AppPropsWithLayout) {
  const getLayout = Component?.getLayout ?? ((page: ReactNode) => page);

  return (
    <AuthProvider>
      <ThemeProvider theme={themes.light}>
        <GlobalStyle />
        {getLayout(<Component {...pageProps} />)}
      </ThemeProvider>
    </AuthProvider>
  );
}

export default appWithTranslation(App, i18nConfig as UserConfig);

src/pages/login.tsx (from where the method signinPopup is called):

import { useAuth } from 'react-oidc-context';

const LoginPage: NextPageWithLayout = () => {
  const auth = useAuth();

  async function handleLogin() {
    await auth.signinPopup();
  }

  return (
      <Container>
          <Title>Login</Title>
          <AccountButton platform={'Microsoft 365'} onClick={handleLogin} />
      </Container>
  );
};

src/pages/index.tsx (the redirect_uri page, which is needed since Next.js shows a 404 error otherwise, thus blocking the auth flow)

export default function CallbackPage() {
  return <></>;
}

Expected result:

After entering our credentials, the user session is successfully stored in the local storage, and is also redirected to the /login page (from where it triggered the sign-in flow), and any components calling the useAuth hook are re-rendered, since its isAuthenticated flag is now set to true.

Obtained result:

After entering our credentials in the Microsoft pop-up (which now occupies the whole window correctly, due to the popupWindowTarget: '_self'), we are kept in the redirect_uri page, with the query params still in it:

Workaround #1:

Avoiding the usage of popupWindowTarget in the AuthProviderProps eliminates the issue: the user is redirected back to our /login page, with no query params in it, and the user session is stored in the local storage

Nonetheless, this workaround will not work for us, since we don't want a pop-up, but rather a page.
We have also tried replacing signinPopup with signinRedirect without any additional configuration, but to no avail. It also leaves us in the same redirect_uri (empty) page:

Workaround #2:

Using signinRedirect does work, but only if we remove the localStorage as our chosen store, and let oidc-client-ts use the default sessionStorage

src/AuthProvider.tsx

import type { AuthProviderProps } from 'react-oidc-context';
import { AuthProvider as OIDCProvider } from 'react-oidc-context';

import type { AuthProviderProps } from 'react-oidc-context';

const OIDC_CONFIG: AuthProviderProps = {
  authority: process.env.NEXT_PUBLIC_MICROSOFT_AUTHORITY,
  client_id: process.env.NEXT_PUBLIC_MICROSOFT_CLIENT_ID,
  redirect_uri: process.env.NEXT_PUBLIC_MICROSOFT_REDIRECT_URI,
  popup_redirect_uri: process.env.NEXT_PUBLIC_MICROSOFT_REDIRECT_URI,
  scope: process.env.NEXT_PUBLIC_MICROSOFT_SCOPE,
  refreshTokenAllowedScope: process.env.NEXT_PUBLIC_MICROSOFT_SCOPE,
  post_logout_redirect_uri: process.env.NEXT_PUBLIC_MICROSOFT_REDIRECT_URI,
  response_type: 'code',
};

export function AuthProvider({ children }: AuthProviderProps) {
  return <OIDCProvider {...OIDC_CONFIG}>{children}</OIDCProvider>;
}

src/pages/index.tsx (the redirect_uri page, which is needed since Next.js shows a 404 error otherwise, thus blocking the auth flow)

import { useEffect } from 'react';
import { useRouter } from 'next/router';

import { PATHS } from '$/constants/paths';

export default function MicrosoftCallbackPage() {
  const { push } = useRouter();

  useEffect(() => {
    void push(PATHS.HOME);
  }, [push]);

  return <></>;
}

Is there something we are missing in our implementation? Our ideal scenario would be to be able to use signinRedirect + localStorage.
Stack used:

next v13.0.5
oidc-client-ts v^2.2.2
react-oidc-context v^2.2.2

First of all signinPopup is intended to be used when you want to have a popup window. As you do not want it, do not use it :-)
The signinRedirect is for what you want. You will need to provide more details why you can not use localStorage and need to use  sessionStorage. I am using  localStorage + signinRedirect successfully.

Hi @pamapa, thanks for your fast reply!
Is localStorage + signinRedirect working for you in a Next.js project? Could you share a snippet showing how you have configured the AuthProvider and passed localStorage as your preferred store?
Either signinPopup with popupWindowTarget: '_self' or signinRedirect works for us.
We first tried with signinPopup but seeing that setting popupWindowTarget to '_self'  broke the functionality for us, we moved away to signinRedirect. That is why I have mentioned both approaches in this issue.
I will create a codesandbox reproducing the issue and link it here so that you can check it out.

@pamapa here's a codesandbox where you can reproduce the error.
While developing the codesandbox I realized of a workaround, although since the library is said to handle SSR properly, I still consider that this is a bug.
I have created three different components:

A Wrapper, which makes sure that the entire contents within _app.tsx are only shown after the first render, so the app behaves "like" a client-side-only app. This is actually part of the workaround. Without this wrapper, the session is never stored within the localStorage.

An AuthProviderWithoutState, which which uses react-oidc-context's AuthProvider and sets its configuration properties right away, including the userStore as localStorage. This should be wrapped with the Wrapper component. Otherwise, the app does not compile as the expected "window is not defined" error is shown.

An AuthProviderWithState, which uses react-oidc-context's AuthProvider and sets its configuration properties as a state, since window is not defined before the first render. This component can be used with our without Wrapper, of course, but it does not work as the auth session is never stored in the localStorage, only in the sessionStorage.

This is basically what the bug is about: with Next.js, it does not seem possible to set localStorage as our preferred userStore, unless we only show _app.tsx after the first render, which is what the Wrapper is taking care of. It should be possible to simply set the configuration object as a state, after the initial render...
Just for the sake of brevity, here's the code of the Wrapper, the AuthProviderWithState, and the AuthProviderWithoutState:

src/wrapper/index.tsx

src/auth/index.tsx

import { InMemoryWebStorage, WebStorageStateStore } from "oidc-client-ts";
import { useEffect, useState } from "react";
import type { AuthProviderProps } from "react-oidc-context";
import { AuthProvider as OIDCProvider } from "react-oidc-context";

export const OIDC_CONFIG: AuthProviderProps = {
  authority: process.env.NEXT_PUBLIC_AUTHORITY as string,
  client_id: process.env.NEXT_PUBLIC_CLIENT_ID as string,
  redirect_uri: process.env.NEXT_PUBLIC_REDIRECT_URI as string,
  popup_redirect_uri: process.env.NEXT_PUBLIC_REDIRECT_URI as string,
  scope: process.env.NEXT_PUBLIC_SCOPE as string,
  refreshTokenAllowedScope: process.env.NEXT_PUBLIC_SCOPE as string,
  post_logout_redirect_uri: process.env.NEXT_PUBLIC_REDIRECT_URI as string,
  response_type: "code",
  onSigninCallback() {
    window.history.replaceState({}, document.title, window.location.pathname);
  },
};

export function AuthProviderWithState({ children }: AuthProviderProps) {
  const [config, setConfig] = useState<AuthProviderProps>({ ...OIDC_CONFIG });

  useEffect(() => {
    setConfig({
      ...OIDC_CONFIG,
      userStore: new WebStorageStateStore({
        store: window.localStorage ?? InMemoryWebStorage,
      }),
    });
  }, []);

  return <OIDCProvider {...config}>{children}</OIDCProvider>;
}

export function AuthProviderWithoutState({ children }: AuthProviderProps) {
  return (
    <OIDCProvider
      {...{
        ...OIDC_CONFIG,
        userStore: new WebStorageStateStore({
          store: window.localStorage ?? InMemoryWebStorage,
        }),
      }}
    >
      {children}
    </OIDCProvider>
  );
}

window is not defined

I guess you are receiving this error when netxjs pre-renders your application on the server side (SSR). See #414.

Thanks for pointing me in the right direction @pamapa.
I had already seen that issue before creating this one, but totally overlooked globalThis?. which is what fixes it for me.
I will leave the full fix here, in case it can help anyone else:
import type { AuthProviderProps } from 'react-oidc-context';
import { AuthProvider as OIDCProvider } from 'react-oidc-context';
import { InMemoryWebStorage, WebStorageStateStore } from 'oidc-client-ts';

import { OIDC_CONFIG } from './constants';

export function AuthProvider({ children }: AuthProviderProps) {
  return (
    <OIDCProvider
      {...OIDC_CONFIG}
      userStore={
        new WebStorageStateStore({
          store: globalThis?.window?.localStorage ?? InMemoryWebStorage,
        })
      }
    >
      {children}
    </OIDCProvider>
  );
}


Re-design Vulnerability details page

🗣 Description
Re-design the current Vulnerability details page. Completes issues: #2306, #2307, #2308, #2309

💭 Motivation and context
Change makes for a better user interface for the Vulnerability details page.

🧪 Testing

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[ ] Tests have been added and/or modified to cover the changes in this PR.
[ ] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

@ameliav , upon review please move forward with merging the Vuln details page in its current state. We will Issue separate tickets to support the notes section and the CWE name. They both require more detailed planning.

Some of the TODO comments in the code are a bit disconcerting (e.g. //TODO: change this to something else??)

Understandable. There are just a few things about the new tables that don't match the rest of the code base. The column names for one thing use snake case instead of camel case. This adds confusion to development when displaying detailed information from API responses. I think we should make these changes before the new tables are deployed to production.
I'll create an issue and link it.

@cduhn17  TODOs captured here.
https://github.com/cisagov/crossfeed/issues/2521
https://github.com/cisagov/crossfeed/issues/2522
https://github.com/cisagov/crossfeed/issues/2523
https://github.com/cisagov/crossfeed/issues/2524


Error in  Protect and call a web API on Azure AD 'invalid client id'

Error "invalid_client: 70002 - [2021-07-29 11:26:28Z]: AADSTS70002: The provided request must include a 'client_secret' input parameter"

Please provide us with the following information:

This issue is for the sample

    - [ ] 1-1) Sign-in with Azure AD
    - [ ] 1-2) Sign-in with Azure AD B2C
    - [ ] 2-1) Acquire a Token and call Microsoft Graph
    - [X ] 3-1) Protect and call a web API on Azure AD
    - [ ] 3-2) Protect and call a web API on Azure AD B2C
    - [ ]   4) Deploy to Azure Storage and App Service
    - [ ] 5-1) Call a web API using App Roles
    - [ ] 5-2) Call a web API using Security Groups
    - [ ] 6-1) Call a multi-tenant web API
    - [ ] 7-1) Call Microsoft Graph using on-behalf-of flow
    - [ ] 7-2) Call a web API using Proof of Possession tokens

This issue is for a

    - [X ] bug report -> please search issues before submitting
    - [ ] question
    - [ ] feature request
    - [ ] documentation issue or request

Minimal steps to reproduce
-login button
-after I redirect in microsoft login and successfully authenticated , it redirects me again in the homepage

Any log messages given by the failure
invalid_client: 70002 - [2021-07-29 11:26:28Z]: AADSTS70002: The provided request must include a 'client_secret' input parameter Trace ID: cb197be3-0850-4322-82b1-c18a4b480f00
Correlation ID: be4946fd-1a44-46b6-ad2e-345a1b09bdfa
Timestamp: 2021-07-29 11:26:28Z - Correlation ID: be4946fd-1a44-46b6-ad2e-345a1b09bdfa - Trace ID: cb197be3-0850-4322-82b1-c18a4b480f00

Expected/desired behavior

Library version

Browser and version

Chrome, Edge, Firefox, Safari?

Mention any other details that might be useful

Thanks! We'll be in touch soon.

@Lawliet0727 looks like this is an app registration issue. Can you please confirm that, on Azure portal > App Registration > Your app > Authentication, the app is registered as "single page application", not "web"?

@Lawliet0727 looks like this is an app registration issue. Can you please confirm that, on Azure portal > App Registration > Your app > Authentication, the app is registered as "single page application", not "web"?

This is correct, the issue now are resolved I mistakenly register my app as "Web" and when I changed it on "SPA" it working fine.
Thanks @derisen


Maker has no attribute  - Version 0.7.9

I am not a Linux or python guy -so I am open to the fact I may be doing something wrong.
simply command wemo status generates error when reaching a maker
root@raspberrypi:/home/pi/WEMO# wemo status
Switch: Front Porch     0
Traceback (most recent call last):
File "/usr/local/bin/wemo", line 9, in
load_entry_point('ouimeaux==0.7.9-r0', 'console_scripts', 'wemo')()
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/cli.py", line 361, in wemo
args.func(args)
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/cli.py", line 260, in status
scan(args, on_switch, on_motion, on_bridge, on_maker)
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/cli.py", line 29, in scan
env.start()
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/environment.py", line 82, in start
self._process_device(dev, cache=False)
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/environment.py", line 184, in _process_device
callback(device)
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/cli.py", line 238, in on_maker
if maker.switch_mode:
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/device/maker.py", line 54, in switch_mode
return self.maker_attribs['switchmode']
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/device/maker.py", line 32, in maker_attribs
makerresp = self.deviceevent.GetAttributes().get('attributeList')
AttributeError: 'Maker' object has no attribute 'deviceevent'
via python

print env.get_maker(env.list_makers()[1])
<WeMo Maker "Garage Door - Small">
print env.get_maker(env.list_makers()[1]).sensor_state
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/device/maker.py", line 50, in sensor_state
return self.maker_attribs['sensorstate']
File "/usr/local/lib/python2.7/dist-packages/ouimeaux-0.7.9_r0-py2.7.egg/ouimeaux/device/maker.py", line 32, in maker_attribs
makerresp = self.deviceevent.GetAttributes().get('attributeList')
AttributeError: 'Maker' object has no attribute 'deviceevent'

On a separate note, I believe the maker device should support the toggle() function as is coded for the switch.

Nope, that's legitimate! In order to support the new firmware, that service was removed. We'll certainly have to fix it.
You're right, the Maker should have toggle().

Made issue #85 for Maker.toggle().

Commenting out the following line in /devices/init.py restored the Maker attributes and removed the error.
if svcname != "deviceevent":

I am a newbie to this also, but it appears that the maker does not produce any sensor signals or events. Is this a known issue?

Commenting out the following line in /devices/init.py restored the Maker attributes and removed the error.
if svcname != "deviceevent":
From: johnrayfield<EMAIL_ADDRESS>Sent: Monday, May 25, 2015 5:34 PM
To: iancmcc/ouimeaux
Cc: dejab
Subject: Re: [ouimeaux] Maker has no attribute - Version 0.7.9 (#84)
I am a newbie to this also, but it appears that the maker does not produce any sensor signals or events. Is this a known issue?
—
Reply to this email directly or view it on GitHub https://github.com/iancmcc/ouimeaux/issues/84#issuecomment-105342321 .  https://github.com/notifications/beacon/ALCc4ghhClOSjA5ZBGmdbNgFSUQlHN8sks5oM7cDgaJpZM4Dyges.gif


Complete sso_bypass.sh

All of the issues were addressed. If user specify anything that is not -h, -e, or -d will get an error including running without input. Issue 3 was addressed by requiring user to specify the key value (password/account/...) when using the -e and -d options.


Abandonware, any alternatives?

Can somebody point to a maintained fork of this library? Maybe we could provide THERE some updates of our own. I have a fix or two already but why bothering making here a pull request when I see some hanging for five years already...

I'm going to run with my fork for a while. I need some stuff I submitted as a PR.


Keyboard Customize [FEATURE]

Describe the feature
Your application is really exciting. Is it possible to customise the keyboard control buttons?
Describe the use case
No response
Additional information
No response

I'm having the same issue. It would be really helpful!


⚠ Bofrost.at has degraded performance

In 8d135db, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1382 ms

Resolved: Bofrost.at performance has improved in 1f0365c.


Code samples for SlackAttachment

Hi,
still me...could you please provide some code samples for SlackAttachment to see how to format nice looking messages ?

All done, it looks great !...worked like a charm, made the mapping between your API and slack guidelines at https://api.slack.com/docs/message-attachments to better understanf what each field means

i think should better add a wiki sections explaining more details about your api. what do you think? @adriens

Yep, Wiki or a new markdown on the project, referenced by the README.md ... 'cause i love to read markdown from the welcome page, i find that very convenient ;-p ... but it's just my personal preference <3

...an another approach would to complete javadoc qui some dummy code sample

...and to finish...and another idea would to reference projects that use your project so real code samples could be seen.
As soon as i've published my little project, i'll let you know and quote your project anyway :smile_cat:

javadoc and extended readme looks great to me

Yep, for me too :+1:

can you help me with javadoc?

Sure, i'll can make you some PR as soon as i will have publushed the BOT. As i'm doing this on evenings and WEs, stuff is not going so fast... but you already probably know the deal about that too :smile_cat: , don't you ?

The ```1.0```` of my project is about to be released.
Remains me to write a little linkedIn article and i'll can help you with javadoc 👍

Article written @gpedro , see https://www.linkedin.com/pulse/birthdays-bots-slack-travis-ci-cron-jobs-all-free-fun-adrien-sales/!


Code to export VCF for joint release HT

This is adapted from gnomad_qc/v4/create_release/validate_and_export_vcf.py, largely simplified to work with joint release HT structure and fields.
Test runs: f339d641fb7f462fbfd25e360deceb3c
91e3f2b117244cb2bda6af6eaddc3f2d

@mike-w-wilson Newer version of code back to you, new test: https://console.cloud.google.com/dataproc/jobs/611c6be455554fc185b3624e7658cf1c?region=us-central1&project=broad-mpg-gnomad


German translation

Ping @kaibrueckers.

Just for the record, here is the ideal way of working (for me, at least):

Fork the repository on GitHub;
Open a de branch from gh-pages branch;
Copy index.md to de/index.md;
Translate it. :)

Sounds good to me ;)
I think I'll already start this weekend, if you have any other tips for me, just let me know.

Same, if you have an question, be sure to ask. :)

ping me if you need help @kaibrueckers

@kaibrueckers I think we should do the work on one fork/branch and cleary separate our work, to not collide, shouldn't we? So we could review each others commits. As you already forked this project, I would suggest contributing to your fork.

@altembo Sounds like a plan, I had to delete my fork because of some misconfigurations on my side. Bear with me, I'm quite new to this "collaboration-style" type of working with git. Would be great if you can give me some advice on how we should proceed now.

@kaibrueckers Me, too ;-) So then let me do the fork, I added you as a Collaborator to my fork. Until we separate our work to not work on the same thing the same time, there should not be any merge problems for us. I will no setup the branch and ping you agian

@kaibrueckers checkout my fork of this project and make sure to switch to the "de" branch. As suggested i copied the file to de/index.md.
If you don't mind I would start from the beginning to commenting, so your part will be from architecture till the end. Ok?

@kaibrueckers I just pushed a test-translation to the 'de' branch. So the next step would be to review it (by u ;-)). If it passed, comment it, if not, comment it, too :P Make sure to push your commit as far as you finished a section. I think one commit per section should be fine.

Great, thanks. Alright, I already translated some of the introductory stuff, so I'll go through your version and make some suggestions if necessary. I'll start working on it again tonight :)

Oh damn, I knew it would have been better to let you start from the beginning ;-( Lets meet in Gitter for further communication/discussion, you should have got an invitation from HugoGiraudel

Los @kaibrueckers gib gas, ich will deutsch lesen :P

Wir sind dran, es zieht sich gerade etwas ;)

@davidhellmann hilfe ist immer gern gesehen ;-)

Glaub ich.  Aber was müsste ich denn tun wenn ich helfen soll?

@davidhellmann Ja uns (zumindest mir :>) im Moment leider auch. Sofern Du Zeit hast schnapp Dir ein unübersetztes Kapitel (= kein Branch vorhanden) in meinem Fork, erstell nen Branch und push Ihn damit wir sehen das Du dran arbeitest. Und wenn Du fertig übersetzt hast machst nen PullRequest auf.

Ich muss mal schauen. Ich verspreche jetzt mal nichts hab es aber mit auf dem Schirm, ok?!

 It's been almost 3 month now since your last conversation.
Are you still working on this? If not, I would like to complete the work you've done so far.
Just leave me a message :)

I'm move next week from
cologne to salzburg and the last weeks/months were stressful and I've no time for anything. Sorry :/
best from the DB Train
David Hellmann
Art Director & Frontend Developer
50931 cologne
Germany
———
CONTACT
—<EMAIL_ADDRESS>— http://davidhellmann.com
SOCIAL ACCOUNTS
— http://twitter.com/davidhellmann
— http://pinterest.com/davidhellmann
— http://instagram.com/davidhellmann
OTHER SITES
— http://makebetterwebsites.com
— http://makebettershirts.com
— http://superb.li
On Thu, Apr 30, 2015 at 7:51 PM, Moritz Kröger<EMAIL_ADDRESS>wrote:

Hey guys (@davidhellmann, @kaibrueckers  & @altembo),
how is your progress? It's been almost 3 month now since your last conversation.
Are you still working on this? If not, I would like to complete the work you've done so far.
Just leave me a message :)
Reply to this email directly or view it on GitHub:
https://github.com/HugoGiraudel/sass-guidelines/issues/88#issuecomment-97896852

Alright, gotcha.
@HugoGiraudel and I agreed on that I will just continue and take over the german translation for now. Unless someone of you says otherwise though. Then we can still merge our progress :)

@morkro:
Ye, translation is kind of frozen right now. Everytime I want to continue something else blocks me.
I added you as a collaborator to my fork, so you can continue/review our work.

Thanks @altembo.
I already forked it myself though as I was talking with Hugo :( I guessed you may not answer so quick.
But still, I took a look into your work and will add some of it. Of course with credits to you guys.
When you find the time to continue, just leave me a message here :) Then we find a solution how to proceed. Is that okay for you guys?

@morkro
Okay, but then we should freeze the work on my branch completely and continue working on your fork instead (when we return). fyi @kaibrueckers , @davidhellmann

Alright. Drop me a line when you return ;)

@morkro was ist bisher schon fertig, ich möchte auch ein bisschen mitwirken

Hey @qcon,
Ich bin mittlerweile fertig und muss nur noch kleine Korrekturen vornehmen. :)
Montag/Dienstag kommt der Pull-Request!

okay, top. Hab' s grad in deinen Fork entdeckt. Super arbeit, Danke!

Danke :)


Correct the usage example of pushState

This should fix #64

Thanks for the PR!
I've decided to fix it the way we discussed it in #64.
Having these location options at the top level options object seems simpler and it's the most typical usage of cherrytree.
The fix is here https://github.com/QubitProducts/cherrytree/pull/66
I'll release a new (backwards incompatible) version in a few mins.


Remove DescriptorSetBuilder, use descriptor writes directly

Changelog:
- **Breaking** `DescriptorWrite` is renamed to `WriteDescriptorSet` to match Vulkan, and moved into the main `descriptor_set` module.
- **Breaking** The constructors of `WriteDescriptorSet` are no longer unsafe. Added convenience constructors for writing non-arrayed bindings.
- **Breaking** Descriptor sets are no longer constructed using a builder, but with an iterator of `WriteDescriptorSet` items. See in the examples how this is used.
  - `PersistentDescriptorSet::start` has been replaced with three constructors, `new`, `new_variable` and `new_with_pool`. Each of these takes an iterator of `WriteDescriptorSet`.
  - `SingleLayoutDescSetPool::next` takes an iterator of `WriteDescriptorSet` as well.

This PR changes how descriptor sets are constructed, which will probably break a lot of existing code. But it allows for some things that were not possible before:

It is possible to leave some descriptors unset, if the shader does not use them. This is especially important if PARTIALLY_BOUND support is added later.
push_descriptor_set can be applied incrementally, like it was intended by the spec.
It makes it easier to add support for updating existing descriptor sets (after constructing/using them), which allows more efficient usage and is also needed for UPDATE_AFTER_BIND. For this to work, descriptor sets need some kind of locking mechanism to prevent updates when the descriptor set is in use.

I realised that PersistentDescriptorSet and SingleLayoutDescSet have a lot of code in common, so I created a new DescriptorSetInner type to handle the common behaviour. This type is not public, it's only an implementation detail.
After this PR, I will be investigating whether I can add support for the VK_KHR_descriptor_update_template extension, which was promoted to Vulkan 1.1. This extension introduces an alternative way to update descriptor sets that reads the data directly from a buffer on the host (CPU), which can be more efficient than constructing WriteDescriptorSet objects.

The constructors of WriteDescriptorSet are no longer unsafe

The main threat of this change is that if the user skips some bindings in use in the shader's code, that would lead to UB, as far as I understand.

It is legal to leave some descriptors unset, if the shader doesn't use them. And if the shader does use them, then the changes made to check_descriptor_sets_validity in #1744 should ensure that this error is caught.

@Rua Ok, then I have an opposite question. If the shader has some explicit binding in layout, and this binding is not in use dynamically in the shader's code, and we have a descriptor set with an empty record for this binding, does this situation considered as valid by the "check_descriptor_sets_validity" procedure?

This would not be considered valid, so an error should occur. The check uses the DescriptorRequirements information that is generated from the shader (by Vulkano-shaders or at runtime). This information is based on static analysis of the shader code, where any potential usage means that the binding is required. It's is more or less the same as what the spec says on the subject:

Descriptors in each bound descriptor set, specified via vkCmdBindDescriptorSets, must be valid if they are statically used by the VkPipeline bound to the pipeline bind point used by this command

The spec does allow a descriptor to remain unset if the descriptor is statically used (the shader accesses the binding, or explicitly declares it in its interface) but is not dynamically used (because the inputs cause the descriptor to not be accessed). But this is only allowed when the binding is created with the PARTIALLY_BOUND flag set, which Vulkano doesn't support yet (see #1743).

@Rua ok, I almost finished testing, but I have one(hopefully) last thing to clarify.
If a have a binding with variable descriptors in my layout("runtime array"), and I set variable descriptors count during the pipeline creation to let say 2, and then I'm going to fill the array with only 1 descriptor. Also, during the pipeline creation I also specified two immutable samplers for this array.
What write operations should I preform for this binding? This configuration works on my end when I do a single image_view_array write only. But I was thinking that I also has to fill array's tail with the none_array writes, isn't it?

If you only have 1 descriptor, then you don't need none_array for the second one. none_array is only needed for descriptors that are actually going to be used. Also, it should be invalid to give none_array to the same binding as image_view_array; the writes for each binding must be of the same (correct) type.

So if you try this, there should be an error.

Confirmed. That's what I got. Thanks for clarifications!

@Rua PR merged. Excellent work! :rocket:


Capitalize Single for all section links

Capitalize Single for all section links

Description of the change:
Reason for the change:
Link to original source:
@ksigler7

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Complete for: https://github.com/sendgrid/docs/issues/2846

Hello @hmbrown64,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


💥New upstream release 0.3.31💥

💥 New upstream release 0.3.31 💥
CHANGELOGS -
Debian Package -

Reverted "pulseaudio-module-bluetooth conflicts with PipeWire-pulse #17"
Give feedback whether should I conflict the same or not?
For more see : #17

roc-toolkit, openfec package added.

PipeWire -

Fixes for alsa-lib 1.2.5
New pulseaudio modules: module-avahi-zeroconf,
module-pipe-source, module-roc-sink, module-roc-source
JACK has seen massive stability improvements. Locking
and correctness wrt to callbacks and has been reworked. Also
thread priorities have improved.
Handle various crashes and lockups when running out of file
descriptors.
Bluetooth now uses a hardware database to disable
non-working features on listed devices.
Scheduling quantum and rate can now be changed dynamically
with pw-metadata.
Many bugfixes and improvements.
For more : https://gitlab.freedesktop.org/pipewire/pipewire/-/releases

https://gitlab.freedesktop.org/pipewire/pipewire/-/releases#0.3.32  👀👀👀👀👀👀

@pablodz  wait some hours, It will be up.

@pablodz  sorry... but I'll up new version tomorrow. I want to wait for some time.. pipewire is not compiling, this is an upstream issue..  The release will not be from the tag 0.3.32 but with some more commits.

@souravdas142 don't worry, take your time

Tried to install from PPA, everything is ok and pipewire update to the latest version
libpipewire-0.3-0 is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
But the pactl info show the version is used
Server Name: PulseAudio (on PipeWire 0.3.25)
and the new lib such libpipewire-module-filter-chain doesn't include
is this true?? Or not how to update correctly to the newest version ?

@maxorbase  Assuming you did read all instructions from readme. whatever I wan't not to make this convertion long, so just giving the instruction here. do the command sudo apt install gstreamer1.0-pipewire libpipewire-0.3-{0,dev,modules} libspa-0.2-{bluetooth,dev,jack,modules} pipewire{,-{audio-client-libraries,pulse,media-session,bin,locales,tests}} and enable , restart the all pipewire based services. systemctl --user --now enable pipewire{,-pulse}.{socket,service} pipewire-media-session.service and then systemctl --user restart pipewire{,-pulse}.{socket,service} pipewire-media-session.service

I did everything in README and again do this for your instruction
all package installed
gstreamer1.0-pipewire is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
libpipewire-0.3-0 is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
libpipewire-0.3-dev is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
libpipewire-0.3-modules is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
libspa-0.2-bluetooth is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
libspa-0.2-dev is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
libspa-0.2-jack is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
libspa-0.2-modules is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
pipewire is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
pipewire-audio-client-libraries is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
pipewire-bin is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
pipewire-locales is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
pipewire-media-session is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
pipewire-pulse is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
pipewire-tests is already the newest version (0.3.32+dfsg1-1ubuntu21.04).
After all pactl info show still
Server Name: PulseAudio (on PipeWire 0.3.25)

delete /etc/pipewire disable pipewire services for user systemctl --user disable --now ... then enable systemctl --user enable --now ... if still not solve, restart your machine...

1-delete all config, disable all service and restart doesn't work
2-purge pipewire and pulsaudio, reinstall both
3-purge pipewire and install debian exprimental version
4- purge debian version and delete all config and folder, reinstall agian from ppa
all of this doesn't work
I'm confusing how this happened

1-delete all config, disable all service and restart doesn't work
2-purge pipewire and pulsaudio, reinstall both
3-purge pipewire and install debian exprimental version
4- purge debian version and delete all config and folder, reinstall agian from ppa
all of this doesn't work
I'm confusing how this happened

After install or reinstall you'll need to reboot your PC

1-delete all config, disable all service and restart doesn't work
2-purge pipewire and pulsaudio, reinstall both
3-purge pipewire and install debian exprimental version
4- purge debian version and delete all config and folder, reinstall agian from ppa
all of this doesn't work
I'm confusing how this happened

After install or reinstall you'll need to reboot your PC

After any change even small change reboot pc

any status ? @pablodz

any status @maxorbase
your distro name, version and desktop ?

@maxorbase

Server Name: PulseAudio (on PipeWire 0.3.25)

From this line, Its clear pipewire still using its older server ? did you remove all configs from both /etc/ and ~/.config ? did you disable all services using systemctl --user disable ... and enable them after installing latest version from this ppa ?
There is no issue here.

any status @maxorbase
your distro name, version and desktop ?

Operating System: Kubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-25-generic
OS Type: 64-bit
Graphics Platform: X11

@maxorbase

Server Name: PulseAudio (on PipeWire 0.3.25)

From this line, Its clear pipewire still using its older server ? did you remove all configs from both /etc/ and ~/.config ? did you disable all services using systemctl --user disable ... and enable them after installing latest version from this ppa ?
There is no issue here.

I think I found the problem
there are two patch for services when i search for the pipewire-media-session.service and others services
1-/usr/lib/systemd/user/
the services in this location is new and located pipewire in ExecStart=/usr/bin/pipewire
2/usr/local/lib/systemd/user/
the date of modified service in this location is too old(When the system was installed) and  located pipewire in ExecStart=/usr/local/bin/pipewire
the systemctl --user enable .... Created symlink from second location service Which is both an older pipewire version and an older services

@maxorbase  I'm curious about from where you get 0.3.25 ? Its not from official one right ? the package was build with PREFIX=/usr/local . Its not the behaviour from official or mine. I am suspecting it was install from other external source right ? the packages from this ppa is fully compatible with official one not from the external  bad built. Now it seems to me I was wasted my time in this. So please stop wasting my time further. Thank you.

@maxorbase I'm curious about from where you get 0.3.25 ? Its not from official one right ? the package was build with PREFIX=/usr/local . Its not the behaviour from official or mine. I am suspecting it was install from other external source right ? the packages from this ppa is fully compatible with official one not from the external bad built. Now it seems to me I was wasted my time in this. So please stop wasting my time further. Thank you.

Thank you for such a wonderful gift , remove all pipewire file in local and eveything back to normal


ctix not creating root index.ts

I have a project with different folders under "src"
ctix create successfully creates the index.ts file for all folders
except for the index.ts of the root "src" folder that should export all of the other files.
running ctix single seems to work fine and it creates the index.ts file
on another project i had to put a dummy file with export {} in the "src" folder which then caused ctix to create the index file correctly, but for this project it doesnt help

@sirpy Hi,
I think that your problem raise cause from skipEmptyDir option.
See skipEmptyDir option at docs

@imjuni i tried that already no help

@sirpy Hi,
I add new option startAt on #50, use new option startAt.
Thank you!


Translate the website to French

Clone the repo
Enter the project and run yarn
Go into the folder translations
Copy the file of the language you know into a new file
Use ISO 639-1 language code as file name
Open the new file and do the translation
Add the language you translated to nuxt.config.js under modules['nuxt-i18n'].locales
Run yarn lint (or npm run lint)  to see that your changes are consistent with the projects coding style
Run yarn dev and open the web-browser at http://localhost:3000
Change to your translated language in the right dropdown menu and see that the translation looks good.
Submit the pull request
Happiness :-)

Can I work on this too?

Wow, sure. If you know French too - go ahead :-)

Hey @maccyber I have made a pull request. Kindly let me know what you think


freehand tool doesn't expose pointNearTool

Prerequisites

[x] Are you running the latest version?
[x] Are you reporting to the correct repository?

For more information, see the CONTRIBUTING guide.
Description
The other tools I consume from imageTools expose a pointNearTool function which allows me to check if a mouse click is near tool data in a way which is specific to the tool itself. I've been using this to write an eraser tool, which I'd be happy to contribute back if there's interest. However, the freehand roi tool doesn't expose this function. If I'm right, please confirm, this would just be adding pointNearTool to https://github.com/cornerstonejs/cornerstoneTools/blob/master/src/imageTools/freehand.js#L1163. Happy to get a PR together for that, just let me know if I'm on the right track.
Steps to Reproduce

inspect cornerstoneTools.freehand

Expected behavior: It includes a pointNearTool function
Actual behavior: It doesn't
Codepen With Reproduction of Issue: https://codepen.io/dlwire/pen/bKOmqx

Basic Template

@JamesAPetts Mind including that in your next update?

@swederik , sure thing, I'll get on this with the next push!
A global eraser tool sounds really useful @dlwrie!
Thanks,
JamesAPetts

This should be solved by PR #431.


shelby chrome ext

everything looks great. I will suggest in you HTML file, I would separate the Script tag and style tag and put them on his own file then invoked in your HTML file. It makes it look cleaner and better organized. Cheers!!

overall really awesome. I would definitely move the styling to it's own external stylesheet. Generally speaking, the rule of thumb s that each file has one purpose or thing that it's in charge of.
HTML = structure of the page
CSS = styling of the page / layout
JS = engine of the page (make fun things happen, like color change on mouseover!)
In order to make your CSS into an external page:

Create a styles.css file

In the head of the html file, add the following tag:
 <link rel="stylesheet" href="styles.css">

Cut and paste everything inside your style tag to the styles.css file

Save both files and remove the style tag from the HTML page


⚠ Bofrost.lu has degraded performance

In 087f0da, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2356 ms

Resolved: Bofrost.lu performance has improved in dd531bb after 6 minutes.


Add recovery action for windows service

golang.org/x/sys/windows/svc/mgr has implemented recovery action and related method.
This PR set default recovery action for windows service.
Ref: https://godoc.org/golang.org/x/sys/windows/svc/mgr

@takama  Could you please have this PR reviewed?

thanks


Put the documentation alphabetically

Whilst the documentation could be improved alot in general, I appreciate doing it is very time-consuming, but one thing that could help a lot is just ordering the side bar(functions/methods etc) alphabetically...

yes that's a good idea
However, it is difficult to do it now that version 3 is being developed.
I will quickly develop version 3 and apply it to new documents.


Settings: apply Mica backdrop

Description of the new feature / enhancement
Let's use Mica as backdrop for Settings.
Scenario when this would be used?
Pretty UI.
https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.media.micabackdrop

https://github.com/microsoft/microsoft-ui-xaml/pull/8139

@niels9001 just tried to Build a branch of mine today and it gave some errors:

All of them are pointing to O:\GitHub\PowerToys\src\modules\MeasureTool\MeasureToolUI\obj\x64\Debug\XamlTypeInfo.g file.
Think that's a consequence of this issue, or something else?


Update to 2.5-0

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


RangeSelector not working on HighStock

When the range selector is part of a highstocks chart, it is rendered correctly, but the buttons/handles don't move when selected with mouse.

I have written a demo about HighStock before which may help you: https://codepen.io/weizhenye/pen/mWxZEv


setup-python@v5 broken on self-hosted runner

I hit https://github.com/actions/setup-python/issues/819 on a fresh self-hosted runner.   We might have to revert to v4 until that's fixed (there is a PR but don't know if it is getting any traction, it was 2 weeks ago).

OK, I see, I got distracted last month and never created a fresh autobuild runner with February's Patch Tuesday updates, still running the January one, which still had python installed when the setup-python action was updated from v4 to v5.

Annoying that it makes a node deprecation warning for every job though.  I hope they do something about this issue, unlike the actions/toolkit#1311 issue (which the fact that they never did anything about that made me think they don't really care that much about Windows self-hosted runners)

Looks like they might have fixed this in main branch.  Once they update v5 we could probably finally revert this.

https://github.com/actions/setup-python/releases/tag/v5.2.0 - guess I can make a new runner and test it (since mingw-packages uses setup-python@v5) and open a PR here if it works.


Error loading file: Not a diagram file draw.io

I have recently created a diagram, which takes me to two pages.
Now i am trying to open the file but this error pop ups: Error loading file: Not a diagram file draw.io.
Thank you

Can you attach the file?

@davidjgraph can I have your email please?

@davidjgraph
Can you please share your email adress?

@davidjgraph can you please share your email address?
Thank you.

https://drive.google.com/file/d/1sEjmf8dIreuZBYgY-VkEq8H5mxjXopFr/view?usp=drivesdk

@davidjgraph please check the flowchart file.
https://drive.google.com/file/d/1sEjmf8dIreuZBYgY-VkEq8H5mxjXopFr/view?usp=drivesdk

@ashrafteleb can you please check it out.
Thank you.

Please find the attached file.
On Sun, Jun 7, 2020, 18:50 David Benson<EMAIL_ADDRESS>wrote:

Can you attach the file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jgraph/drawio/issues/964#issuecomment-640222081, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALFQVNGFT7WAHOQUOLHHIZLRVOLJFANCNFSM4NXA5H2Q
.


Bug: Crash when running Xcode Previews

Description
rules_xcodeproj appears to crash when running some Xcode Previews that a similar project built using XcodeGen previews with no problem.
Reproduction steps
Requires bazelisk & Xcode 15 to be installed.
preview-demo.zip

bazel run xcodeproj && xed PreviewDemo.xcodeproj
Navigate to ModuleA.swift
Press command-option-P to refresh the Xcode Previews canvas

This should crash the preview with a EXC_BAD_ACCESS (SIGSEGV).

The backtrace looks like this for me:
Thread 0 Crashed:
0   libswiftCore.dylib            	       0x192c8b6d8 0x1929c5000 + 2909912
1   libswiftCore.dylib            	       0x192cb32c8 0x1929c5000 + 3072712
2   libswiftCore.dylib            	       0x192cab05c 0x1929c5000 + 3039324
3   ModuleA.1.preview-thunk.dylib 	       0x10e952a88 lazy protocol witness table accessor for type ModuleBView<ModuleAReducer.Action> and conformance ModuleBView<A> + 72
4   ModuleA.1.preview-thunk.dylib 	       0x10e952908 PreviewView.__preview__body.getter + 120 (ModuleA.swift:21)
5   ModuleA.sandbox               	       0x1045ab778 protocol witness for View.body.getter in conformance PreviewView + 12
6   SwiftUI                       	       0x1c4b4e7f4 0x1c4371000 + 8247284
7   SwiftUI                       	       0x1c586bec4 0x1c4371000 + 21999300
8   SwiftUI                       	       0x1c586bc38 0x1c4371000 + 21998648
9   SwiftUI                       	       0x1c5374abc 0x1c4371000 + 16792252

Building and running works in both Xcode (cmd-R with the ModuleA scheme) and the command line (bazel run ModuleA.sandbox).
Expected behavior
The preview should render correctly and not crash, as it does in the XcodeGen example, and as it does if I change the contents of the preview to something simpler:
#Preview {
    Text("Hello world")
}

rules_xcodeproj version
1.14.2
Xcode version
15.1
Bazel version
7.0.0
rules_apple version
3.1.1
rules_swift version
1.13.0
Additional information
XcodeGen renders this preview just fine. To try it out, run these steps:

Install XcodeGen: brew install xcodegen
Generate and open the project: xcodegen && xed PreviewDemo.xcodeproj
Navigate to ModuleA.swift
Press command-option-P to refresh the Xcode Previews canvas

Some small changes can work around the previews crash

I also see the same crash with the legacy project generation mode:

Thank you for the detailed repro. Hopefully with that I'll be able to see what we are doing differently and find a fix.
FYI, I'm on holiday until Jan 2, so I might not look at this until at least then

No rush, have a nice holiday break!

Here's another type of crash that may or may not be related to the first. It has to do with environment objects not propagating correctly across source code that's in different modules and files.
preview-demo-2.zip
It may be easiest to start with this one since it doesn't require rules_swift_package_manager or any 3rd party libraries, just 3 files across 2 modules:
ModuleB: [ModuleB.swift]
ModuleA: [ModuleA.swift, MyView1.swift]

Same repro steps as the original issue for both rules_xcodeproj and XcodeGen variants.
For rules_xcodeproj, if I inline all 3 files into ModuleA.swift the preview doesn't crash. When it does crash, here's what the back trace looks like:
Thread 0 Crashed:
0   libswiftCore.dylib                     0x1929f3938 0x1929c5000 + 190776
1   SwiftUI                                0x1c540bd14 0x1c4371000 + 17411348
2   SwiftUI                                0x1c540bc34 0x1c4371000 + 17411124
3   ModuleA.sandbox                        0x1002dd340 CurrentColor.provider.getter + 148
4   ModuleA.sandbox                        0x1002dce24 CurrentColor.wrappedValue.getter + 120
5   ModuleA.sandbox                        0x1002dcd8c CurrentColorModifier.color.getter + 124
6   ModuleA.sandbox                        0x1002dd184 CurrentColorModifier.body(content:) + 296
7   ModuleA.sandbox                        0x1002dd2a4 protocol witness for ViewModifier.body(content:) in conformance CurrentColorModifier + 20

Changing the XcodeGen to match bazel (using a static library instead of a framework) results in the same crash:
targets:
  ModuleB:
    type: library.static

So I would say the second crash isn't really a rules_xcodeproj issue.

I can't get the first example to work when changing it the same way, but I feel it's the same issue, static linking versus dynamic.

Thanks for looking into this @brentleyjones! Would you suggest setting linkstatic = False on the swift_librarys then? Is there a way to do that only when building for Xcode Previews? How else would you suggest fixing this?

I would suggest using ios_framework to make similar target.

Ok making an ios_framework for all modules fixes both examples:
 swift_library(
     name = "ModuleB_library",
     module_name = "ModuleB",
     srcs = ["ModuleB.swift"],
     visibility = ["//visibility:public"],
+    alwayslink = True,
+)
+
+ios_framework(
+    name = "ModuleB_framework",
+    bundle_id = "com.jpsim.framework.ModuleB",
+    families = ["iphone"],
+    infoplists = ["Framework-Info.plist"],
+    minimum_os_version = "16.0",
+    visibility = ["//visibility:public"],
+    deps = [":ModuleB_library"],
 )

 swift_library(
@@ -20,6 +31,18 @@ swift_library(
     srcs = ["ModuleA.swift", "MyView1.swift"],
     visibility = ["//visibility:public"],
     deps = ["ModuleB_library"],
+    alwayslink = True,
+)
+
+ios_framework(
+    name = "ModuleA_framework",
+    bundle_id = "com.jpsim.framework.ModuleA",
+    families = ["iphone"],
+    frameworks = ["ModuleB_framework"],
+    infoplists = ["Framework-Info.plist"],
+    minimum_os_version = "16.0",
+    visibility = ["//visibility:public"],
+    deps = ["ModuleA_library"],
 )

 ios_application(
@@ -30,6 +53,7 @@ ios_application(
     minimum_os_version = "16.0",
     visibility = ["//visibility:public"],
     deps = ["ModuleA_library"],
+    frameworks = ["ModuleA_framework"]
 )

The fact that previews mostly work but crash in surprising ways without this is pretty unfortunate.
Is there a way to diagnose this in rules_xcodeproj itself?

The fact that previews mostly work but crash in surprising ways without this is pretty unfortunate.

But it does so without rules_xcodeproj, so you should be able to create a reproducer and file a bug against the Swift repo?

Is there a way to diagnose this in rules_xcodeproj itself?

Not really sure what you are asking. But this has nothing to do with rules_xcodeproj, so I would simplify your repro if you are digging into it more.

But it does so without rules_xcodeproj, so you should be able to create a reproducer and file a bug against the Swift repo?

Yes, there's an Xcode / Swift bug here I think.

Not really sure what you are asking. But this has nothing to do with rules_xcodeproj, so I would simplify your repro if you are digging into it more.

I guess if the issue is just a bug in Swift / Xcode then there's nothing to do, but if it's a user error to have a module graph without an equivalent dynamic frameworks, then it would be useful if rules_xcodeproj diagnosed that misconfiguration when building for Xcode Previews.

I've been trying to apply your suggestions to have dynamic frameworks for every module, but ran into what I think is a rules_xcodeproj bug having to do with framework search path ordering here: https://github.com/MobileNativeFoundation/rules_xcodeproj/issues/2846

Going to close this since this seems to be specific to the Swift compiler/runtime.


RISCV-DV and OpenTitan Vendoring Updates

Also includes a minor bugfix to delete the .ccf inclusion in Ibex DV coverage runs because IMC does not allow two different coverage databases to merge with different .ccf files -in our case cover.ccf from Ibex DV and None from RISCV-DV-

Looks fine, but it also looks like the 2nd vendoring commit failed CI: do you know what happened there?

I believe it is about a verilator lint failure about ram_1p_scr module.
2022-04-04T09:00:51.3243396Z ERROR: %Warning-UNOPTFLAT: ../src/lowrisc_prim_ram_1p_scr_0.1/rtl/prim_ram_1p_scr.sv:116:25: Signal unoptimizable: Feedback to clock or circular logic: 'ibex_top_tracing.u_ibex_top.gen_rams.gen_rams_inner[0].tag_bank.addr_scr'
2022-04-04T09:00:51.3244353Z   116 |   logic [AddrWidth-1:0] addr_scr;
2022-04-04T09:00:51.3244792Z       |                         ^~~~~~~~
2022-04-04T09:00:51.3245297Z                     ... Use "/* verilator lint_off UNOPTFLAT */" and lint_on around source to disable this message.
2022-04-04T09:00:51.3246004Z                     ../src/lowrisc_prim_ram_1p_scr_0.1/rtl/prim_ram_1p_scr.sv:116:25:      Example path: ibex_top_tracing.u_ibex_top.gen_rams.gen_rams_inner[0].tag_bank.addr_scr
2022-04-04T09:00:51.3246728Z                     ../src/lowrisc_prim_ram_1p_scr_0.1/rtl/prim_ram_1p_scr.sv:142:19:      Example path: ASSIGNW
2022-04-04T09:00:51.3247434Z                     ../src/lowrisc_prim_ram_1p_scr_0.1/rtl/prim_ram_1p_scr.sv:141:25:      Example path: ibex_top_tracing.u_ibex_top.gen_rams.gen_rams_inner[0].tag_bank.addr_mux
2022-04-04T09:00:51.3248418Z                     ../src/lowrisc_prim_ram_1p_scr_0.1/rtl/prim_ram_1p_scr.sv:163:21:      Example path: ASSIGNW
2022-04-04T09:00:51.3249137Z                     ../src/lowrisc_prim_ram_1p_scr_0.1/rtl/prim_ram_1p_scr.sv:116:25:      Example path: ibex_top_tracing.u_ibex_top.gen_rams.gen_rams_inner[0].tag_bank.addr_scr
2022-04-04T09:00:51.3249749Z %Error: Exiting due to 1 warning(s)

Apparently last commit in prim_ram_1p_scr changes the place of a mux after scrambling instead of before scrambling and when we are not enabling scrambling in ICache (as we do in OpenTitan, see https://github.com/lowRISC/ibex/issues/1475) the logic gets circular. I'll open up a PR in OpenTitan to fix it.


gender field

A single artist, 67622 Feliza Bursztyn, has the gender "female" not "Female", which is bothersome when trying to do data mining. I would recommend changing all to consistent caps.

There are multiple cases for same values in gender field, yea. :-(

While 67622 does not have female anymore, there are still (even in the latest data dump) cases where this is not the same, for example, 131916, "Yente (Eugenia Crenovich)", has female instead of Female.

Apologies - we have merged in the code that fixes this but it won't be updated until the next update (scheduled for Tuesday). We will be lowercasing these going forward.

Awesome. I think https://github.com/MuseumofModernArt/collection/pull/23 can also be closed then.

The latest release has this information standardized to lowercase.


EventDetailFragment automatically move to a section without scrolling

Describe the bug
In EventDetailFragment, sometimes it automatically moved to a below section before user trying to scroll or do something
Screenshots

Would you like to work on the issue?
Yes

Just add android:descendantFocusability="blocksDescendants in the organiser container


[Bug]: The Run code lens does not work for services

Description
$title only appears in versions after 2201.9.2. The code lens works as expected in versions 2201.8.6 and 2201.9.1. Additionally, it works as expected on Windows OS.
Steps to Reproduce

Create a new Ballerina project using the service template bal new -t service.
Start the service using the Run code lens.

Affected Version(s)
2201.9.2 onwards
OS, DB, other environment details and versions
OS: macOS 14.5 23F79
JDK: openjdk 17.0.8 2023-07-18
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

This is now fixed with the vs-code v4.7.3 release.
Uploading Screen Recording 2024-07-19 at 10.48.04.mov…

@Dilhasha can we close this?

Fixed with https://github.com/wso2-enterprise/vscode-extensions/pull/3371
Hence closing.


does not work with SSR in production mode (nuxt build)

When application is in development mode tiny slider works perfectly, but when I want to build my app it doesn't work.
Above is my code. A did everything the same as it is in the readme file.
 I didnt import tiny-slider's css styles.


Fix: Address broken install script

This patch should address #43 , #41 , #36 , and #38 . The previous refactor of the scripts/install-sdk.sh script inadvertently removed the actual installation step while introducing a typo.

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/flutter?version=dev:d163a373381f602c62eb0255ec43c37ebd43a4c9

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/flutter?version=dev:d163a373381f602c62eb0255ec43c37ebd43a4c9

Your orb has been published to the CircleCI Orb Registry.
You can view your published orb on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/flutter?version=2.0.4

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/flutter?version=dev:d163a373381f602c62eb0255ec43c37ebd43a4c9


ci: add job for running ci tests

PR adds ability to run e2e tests from the addonfactory-ucc-generator repository

@artemrys : not in this PR :-) But feel free to add Jira task for that

@artemrys I am ok with merging this repo to the main repo. I don't see that this CI job would make any harm. Of course, it will be removed, but we don't have it even planned yet? Until that moment, we can utilize the help of written tests.

Okay, let's live like that for now, we will plan this move for the next Q.

:tada: This PR is included in version 1.29.2 :tada:
The release is available on:

v1.29.2
GitHub release

Your semantic-release bot :package::rocket:


Option to limit scope of role linting

Issue Type

Feature request

Desired Behaviour
Currently, if executing ansible-lint from a precommit hook in a role, the only option is to lint all of the files, including those that have not changed.  Ideally there would be some way of saying "lint only these files within the role."
Maybe a --limit or --include flag that would mirror the --exclude flag?  Alternatively a flag to set the base directory for the role, and then linting the files listed as positional arguments could work, but that seems like it would be more difficult to implement, as well as breaking existing functionality.

I recommend using ansible-review for this kind of thing - it's exactly what it's designed for.

Pull requests welcome that implement this behaviour though.

I've found that if you pass in the '--exclude=/' option it will limit linting to the individual file


cant resolve Generative agent

cloned the repo.
in example/phaser
npm install
added 1307 packages, and audited 1320 packages in 22s
Failed to compile.
Module not found: Error: Can't resolve 'generative-agents' in '\generative-agents\examples\phaser\src'
ERROR in ./src/Game.tsx 7:0-74
Module not found: Error: Can't resolve 'generative-agents' in '\generative-agents\examples\phaser\src'
ERROR in ./src/pages/test.tsx 6:0-55
Module not found: Error: Can't resolve 'generative-agents' in '\generative-agents\examples\phaser\src\pages'
ERROR in ./src/phaserClasses/AgentCharacter.ts 5:0-48
Module not found: Error: Can't resolve 'generative-agents' in '\generative-agents\examples\phaser\src\phaserClasses'
webpack compiled with 3 errors
ERROR in src/AgentChat.tsx:2:23
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | import React, { useState } from "react";

2 | import { Agent } from "generative-agents";
|                       ^^^^^^^^^^^^^^^^^^^
3 | import { XCircle } from "lucide-react";
4 |
5 | type AgentChatProps = {

ERROR in src/AgentDisplay.tsx:2:23
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | // AgentDisplay.tsx

2 | import { Agent } from "generative-agents";
|                       ^^^^^^^^^^^^^^^^^^^
3 | import React, { useEffect, useState } from "react";
4 |
5 | type AgentDisplayProps = {

ERROR in src/data/world.ts:1:27
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.

1 | import { Rectangle } from "generative-agents";
|                           ^^^^^^^^^^^^^^^^^^^
2 |
3 | export const locations: Rectangle[] = [
4 |   {

ERROR in src/Game.tsx:3:55
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | import React, { useRef, useState } from "react";
2 | import PhaserGame from "./phaserGame";

3 | import { Agent, AgentEngine, buildSpatialWorld } from "generative-agents";
|                                                       ^^^^^^^^^^^^^^^^^^^
4 |
5 | import { agentsData } from "./data/agents";
6 | import AgentDisplay from "./AgentDisplay";

ERROR in src/pages/test.tsx:2:36
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | import React, { useRef } from "react";

2 | import { Agent, AgentEngine } from "generative-agents";
|                                    ^^^^^^^^^^^^^^^^^^^
3 |
4 | interface Props {
5 |   openaiKey: string;

ERROR in src/phaserClasses/AgentCharacter.ts:3:36
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | import Phaser from "phaser";
2 | import BubbleText from "./BubbleText";

3 | import { Agent, AgentEvents } from "generative-agents";
|                                    ^^^^^^^^^^^^^^^^^^^
4 | import { locations } from "../data/world";
5 |
6 | class AgentCharacter extends Phaser.GameObjects.Sprite {

ERROR in src/phaserClasses/AgentCharacter.ts:126:13
TS7006: Parameter 'word' implicitly has an 'any' type.
124 |     return this.agent.id
125 |       .split("_")

126 |       .map((word) => word[0])
|             ^^^^
127 |       .join("")
128 |       .toUpperCase();
129 |   }

ERROR in src/phaserGame.tsx:4:23
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
Failed to compile.
Module not found: Error: Can't resolve 'generative-agents' in 'C:\Users\erikc\source\repos\generative-agents\examples\phaser\src'
ERROR in ./src/Game.tsx 7:0-74
Module not found: Error: Can't resolve 'generative-agents' in 'C:\Users\erikc\source\repos\generative-agents\examples\phaser\src'
ERROR in ./src/pages/test.tsx 6:0-55
Module not found: Error: Can't resolve 'generative-agents' in 'C:\Users\erikc\source\repos\generative-agents\examples\phaser\src\pages'
ERROR in ./src/phaserClasses/AgentCharacter.ts 5:0-48
Module not found: Error: Can't resolve 'generative-agents' in 'C:\Users\erikc\source\repos\generative-agents\examples\phaser\src\phaserClasses'
webpack compiled with 3 errors
ERROR in src/AgentChat.tsx:2:23
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | import React, { useState } from "react";

2 | import { Agent } from "generative-agents";
|                       ^^^^^^^^^^^^^^^^^^^
3 | import { XCircle } from "lucide-react";
4 |
5 | type AgentChatProps = {

ERROR in src/AgentDisplay.tsx:2:23
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | // AgentDisplay.tsx

2 | import { Agent } from "generative-agents";
|                       ^^^^^^^^^^^^^^^^^^^
3 | import React, { useEffect, useState } from "react";
4 |
5 | type AgentDisplayProps = {

ERROR in src/data/world.ts:1:27
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.

1 | import { Rectangle } from "generative-agents";
|                           ^^^^^^^^^^^^^^^^^^^
2 |
3 | export const locations: Rectangle[] = [
4 |   {

ERROR in src/Game.tsx:3:55
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | import React, { useRef, useState } from "react";
2 | import PhaserGame from "./phaserGame";

3 | import { Agent, AgentEngine, buildSpatialWorld } from "generative-agents";
|                                                       ^^^^^^^^^^^^^^^^^^^
4 |
5 | import { agentsData } from "./data/agents";
6 | import AgentDisplay from "./AgentDisplay";

ERROR in src/pages/test.tsx:2:36
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | import React, { useRef } from "react";

2 | import { Agent, AgentEngine } from "generative-agents";
|                                    ^^^^^^^^^^^^^^^^^^^
3 |
4 | interface Props {
5 |   openaiKey: string;

ERROR in src/phaserClasses/AgentCharacter.ts:3:36
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | import Phaser from "phaser";
2 | import BubbleText from "./BubbleText";

3 | import { Agent, AgentEvents } from "generative-agents";
|                                    ^^^^^^^^^^^^^^^^^^^
4 | import { locations } from "../data/world";
5 |
6 | class AgentCharacter extends Phaser.GameObjects.Sprite {

ERROR in src/phaserClasses/AgentCharacter.ts:126:13
TS7006: Parameter 'word' implicitly has an 'any' type.
124 |     return this.agent.id
125 |       .split("_")

126 |       .map((word) => word[0])
|             ^^^^
127 |       .join("")
128 |       .toUpperCase();
129 |   }

ERROR in src/phaserGame.tsx:4:23
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
2 | import Phaser from "phaser";
3 | import { MainScene } from "./scenes/MainScene";

4 | import { Agent } from "generative-agents";
|                       ^^^^^^^^^^^^^^^^^^^
5 |
6 | interface Props {
7 |   agents: Agent[];

ERROR in src/scenes/MainScene.ts:2:23
TS2307: Cannot find module 'generative-agents' or its corresponding type declarations.
1 | import Phaser from "phaser";

2 | import { Agent } from "generative-agents";
|                       ^^^^^^^^^^^^^^^^^^^
3 | import AgentCharacter from "../phaserClasses/AgentCharacter";
4 | import { agentsData } from "../data/agents";
5 | import { locations } from "../data/world";

@DarokCx that is because the package "generative-agents" is a local package and not available via NPM right now. We plan to publish it soon but till then, you have to clone the whole thing. Once you clone the whole repo -
install and build the core/typescript
yarn install
yarn build

next up create a link to the package
yarn link

After that, go to examples/phaser and link the package
yarn link generative-agents

now do yarn install and yarn start
A bit cumbersome. I will see to add a package.

ok, we published it as a package here - https://npmjs.com/package/generative-agents
will update the docs.