csfm.so: undefined symbol: cs_di_chol

Hi I built the "python setup.py build" without any problem but when trying "bin/opensfm_run_all data/berlin/" I get the following error:
~/OpenSfM$ bin/opensfm_run_all data/berlin/
Traceback (most recent call last):
  File "/home/mohammad/OpenSfM/bin/opensfm", line 10, in <module>
    from opensfm import commands
  File "/home/mohammad/OpenSfM/opensfm/commands/__init__.py", line 2, in <module>
    import extract_metadata
  File "/home/mohammad/OpenSfM/opensfm/commands/extract_metadata.py", line 5, in <module>
    from opensfm import dataset
  File "/home/mohammad/OpenSfM/opensfm/dataset.py", line 12, in <module>
    from opensfm import io
  File "/home/mohammad/OpenSfM/opensfm/io.py", line 10, in <module>
    from opensfm import features
  File "/home/mohammad/OpenSfM/opensfm/features.py", line 7, in <module>
    import csfm
ImportError: /home/mohammad/OpenSfM/opensfm/csfm.so: undefined symbol: cs_di_chol

Based on your previous replies in the net it is related to "ceres solver" but I already reinstalled it based on the guide at their page. Any ideas?
This is how the build went on:

~/OpenSfM$ python setup.py build
Configuring...
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Try OpenMP C flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Try OpenMP CXX flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Found OpenMP: -fopenmp
-- Looking for dgemm_
-- Looking for dgemm_ - found
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- A library with BLAS API found.
-- Looking for cheev_
-- Looking for cheev_ - found
-- A library with LAPACK API found.
-- A library with BLAS API found.
-- Found AMD library: /usr/lib/x86_64-linux-gnu/libamd.so
-- Found AMD header in: /usr/include/suitesparse
-- Found CAMD library: /usr/lib/x86_64-linux-gnu/libcamd.so
-- Found CAMD header in: /usr/include/suitesparse
-- Found COLAMD library: /usr/lib/x86_64-linux-gnu/libcolamd.so
-- Found COLAMD header in: /usr/include/suitesparse
-- Found CCOLAMD library: /usr/lib/x86_64-linux-gnu/libccolamd.so
-- Found CCOLAMD header in: /usr/include/suitesparse
-- Found CHOLMOD library: /usr/lib/x86_64-linux-gnu/libcholmod.so
-- Found CHOLMOD header in: /usr/include/suitesparse
-- Found SuiteSparseQR library: /usr/lib/x86_64-linux-gnu/libspqr.so
-- Found SuiteSparseQR header in: /usr/include/suitesparse
-- Found Intel Thread Building Blocks (TBB) library: /usr/lib/x86_64-linux-gnu/libtbb.so, assuming SuiteSparseQR was compiled with TBB.
-- Found Intel Thread Building Blocks (TBB) Malloc library: /usr/lib/x86_64-linux-gnu/libtbbmalloc.so
-- Found SuiteSparse_config library: /usr/lib/x86_64-linux-gnu/libsuitesparseconfig.so
-- Found SuiteSparse_config header in: /usr/include/suitesparse
-- Adding librt: /usr/lib/x86_64-linux-gnu/librt.so to SuiteSparse_config libraries (required on Linux & Unix [not OSX] if SuiteSparse is compiled with timing).
-- Did not find METIS library (optional SuiteSparse dependency)
-- Found SuiteSparse: TRUE (found version "4.4.6")
-- Found Eigen: /usr/local/include/eigen3 (found version "3.2.10")
-- Found ceres: /usr/local/lib/libceres.a
-- No preference for use of exported gflags CMake configuration set, and no hints for include/library directories provided. Defaulting to preferring an installed/exported gflags CMake configuration if available.
-- Found installed version of gflags: /usr/local/lib/cmake/gflags
-- Detected gflags version: 2.2.0
-- Found Gflags: /usr/local/include
-- Found Glog: /usr/include
-- Found CUDA: /usr/local/cuda (found suitable exact version "8.0")
-- Found OpenCV: /usr/local (found suitable version "3.2.0", minimum required is "3.2.0")
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   python
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.12")
-- Found PythonInterp: /usr/bin/python2.7 (found version "2.7.12")
-- Found NumPy: version "1.12.1" /home/mohammad/.local/lib/python2.7/site-packages/numpy/core/include
-- Configuring done
-- Generating done
-- Build files have been written to: /home/mohammad/OpenSfM/cmake_build
Compiling extension...
Scanning dependencies of target akaze
Scanning dependencies of target gtest
Scanning dependencies of target vl
[  2%] Building CXX object CMakeFiles/gtest.dir/third_party/gtest/gmock_gtest_all.cc.o
[  4%] Building CXX object CMakeFiles/gtest.dir/third_party/gtest/gmock_main.cc.o
[  6%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/mathop.c.o
[  8%] Building CXX object CMakeFiles/akaze.dir/third_party/akaze/lib/AKAZE.cpp.o
[ 10%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/hikmeans.c.o
[ 12%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/quickshift.c.o
[ 14%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/getopt_long.c.o
[ 16%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/rodrigues.c.o
[ 18%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/scalespace.c.o
[ 20%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/imopv_sse2.c.o
[ 22%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/covdet.c.o
[ 24%] Building CXX object CMakeFiles/akaze.dir/third_party/akaze/lib/fed.cpp.o
[ 26%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/svmdataset.c.o
[ 28%] Building CXX object CMakeFiles/akaze.dir/third_party/akaze/lib/nldiffusion_functions.cpp.o
[ 30%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/generic.c.o
[ 32%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/lbp.c.o
[ 34%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/pgm.c.o
[ 36%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/dsift.c.o
[ 38%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/ikmeans.c.o
[ 40%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/slic.c.o
[ 42%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/fisher.c.o
[ 44%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/imopv.c.o
[ 46%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/svm.c.o
[ 48%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/mathop_avx.c.o
[ 51%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/vlad.c.o
[ 53%] Building CXX object CMakeFiles/akaze.dir/third_party/akaze/lib/utils.cpp.o
[ 55%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/host.c.o
[ 57%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/homkermap.c.o
[ 59%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/random.c.o
[ 61%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/kmeans.c.o
[ 63%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/mathop_sse2.c.o
[ 65%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/gmm.c.o
[ 67%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/sift.c.o
[ 69%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/kdtree.c.o
[ 71%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/stringop.c.o
[ 73%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/aib.c.o
[ 75%] Linking CXX static library libakaze.a
[ 75%] Built target akaze
[ 77%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/mser.c.o
[ 79%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/hog.c.o
[ 81%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/liop.c.o
[ 83%] Building C object CMakeFiles/vl.dir/third_party/vlfeat/vl/array.c.o
[ 85%] Linking C static library libvl.a
[ 85%] Built target vl
Scanning dependencies of target csfm
[ 87%] Building CXX object CMakeFiles/csfm.dir/csfm.cc.o
[ 89%] Linking CXX static library libgtest.a
[ 89%] Built target gtest
Scanning dependencies of target testing_main
[ 91%] Building CXX object CMakeFiles/testing_main.dir/testing_main.cc.o
[ 93%] Linking CXX static library libtesting_main.a
[ 93%] Built target testing_main
Scanning dependencies of target depthmap_test
[ 95%] Building CXX object CMakeFiles/depthmap_test.dir/depthmap_test.cc.o
[ 97%] Linking CXX executable depthmap_test
[ 97%] Built target depthmap_test
[100%] Linking CXX shared library /home/mohammad/OpenSfM/opensfm/csfm.so
[100%] Built target csfm
Building package
running build
running build_py
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/opensfm
copying opensfm/dense.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/dataset.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/unionfind.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/multiview.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/video.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/exif.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/align.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/transformations.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/__init__.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/context.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/reconstruction.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/geotag_from_gpx.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/sensors.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/matching.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/geo.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/features.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/mesh.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/io.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/config.py -> build/lib.linux-x86_64-2.7/opensfm
copying opensfm/types.py -> build/lib.linux-x86_64-2.7/opensfm
creating build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/match_features.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/reconstruct.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/compute_depthmaps.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/__init__.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/export_ply.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/extract_metadata.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/create_tracks.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/detect_features.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/export_visualsfm.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/export_openmvs.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/mesh.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/commands/undistort.py -> build/lib.linux-x86_64-2.7/opensfm/commands
copying opensfm/csfm.so -> build/lib.linux-x86_64-2.7/opensfm
creating build/lib.linux-x86_64-2.7/opensfm/data
copying opensfm/data/sensor_data.json -> build/lib.linux-x86_64-2.7/opensfm/data
running build_scripts
creating build/scripts-2.7
copying bin/opensfm_run_all -> build/scripts-2.7
copying and adjusting bin/opensfm -> build/scripts-2.7
changing mode of build/scripts-2.7/opensfm from 664 to 775

Related to #41

@smmmmi i don't know what the problem is. I can only think of linking problems.
Did you make sure to use the -fPIC option when building Ceres?
The configuration command should look like this
cd path/to/ceres-solver-1.10.0/build
cmake .. -DCMAKE_C_FLAGS=-fPIC -DCMAKE_CXX_FLAGS=-fPIC -DBUILD_EXAMPLES=OFF -DBUILD_TESTING=OFF
make install

Hi,
I have the same error. After searching  via Internet I didn't found any solution.
I have Ubuntu 16.04. There was no repository for libsuitesparse library available, so I had to download package from source and install everything via make install.
I made installation by your Dockfile script.
Could you help me please, what should be useful to provide?

I tried the hint @paulinus gave but I got the same ImportError.
Issue remains open!

To totally remove paste build I delete directories build and cmake_build, but I don't know is it enough?

Ok, I think that's ubuntu 16 related problem.
And the solution is to user docker-ce in order to run all files in docker.
Guys install docker and build image with Dockerfile, than use it as container with docker run.
Sorry for the question, because the solution was obvious, but not for me, as I didn't have any experience with docker. Please, @mapillary-ci , insert some description in README file, why to use docker, and not to install everything in system by our own. Thanx for the good lib!

Same problem on Ubuntu 14. Is docker still the only solution?

@nlpguyz I have just fixed this error. The last thing I did before it worked was to build ceres as a shared library. Before that I also built SuiteSparse and CXSparse from source.

@rjeli Thanks for the information. I got it to work using docker. Now I will try to build ceres as a shared library. thanks.

I also encountered this problem. What happened in my case was that I had updated to the newest version of ceres-solver and then I started getting the error. So, I reverted back to ceres-solver-1.10.0 and it fixed the problem. Hope that helps someone!

It still does not work for me... I get  "opensfm/csfm.so: undefined symbol: cs_di_chol" ...
I tried everything above:

"docker build ."
building SuiteSparse and CXSparse from source (I think cs_di_chol should be in there -> I could see it at least in this lib, eg. I used " nm -gC libcxsparse.a |grep cs_di_chol"  => One should get  ... "T cs_di_chol" which means it is defined, but one line below I got "U cs_di_chol" which means it is undefined and totally contradictionary)
manual build (based on docker)
went back to ceres-solver-1.10.0  (there is some note in the commits saying that cxsparse can be replaced eigen in that version)

My personal guess is that there are issues with the libraries and linking. I recently install opencv and the contrib stuff, this also required similar libs. Spend lots of time on it. Any help appreciated.

Must be a dummy question, but how did you guys managed to build with Cuda. I have Cuda installed on my machine and it works fine with Tensorflow and darknet yolo. But when I build Opensfm, the compile log did not have that Cuda line:
-- Found CUDA: /usr/local/cuda (found suitable exact version "8.0")

Could anyone shed some lights? @smmmmi

@hy9be, opensfm does not use Cuda


New Xenium 5K output bundle incompatible with Squidpy

Description

Hello, Squidpy seems not to read the newly released Xenium 5K data (https://www.10xgenomics.com/datasets/preview-data-xenium-prime-gene-expression) correctly. In particular, the function sdata.write(zarr_path) outputs AssertionError: only one path". As a result, the transcripts folder under points folder is empty. How to address this issue? Any advice would be highly appreciated. Look forward to learning your expertise at your earliest convenience. Thank you so much.
...
Minimal reproducible example

ls ./Data/Raw/Xenium_Prime_Human_Lymph_Node_Reactive_FFPE_outs
# analysis.zarr.zip		gene_groups.csv
# analysis_summary.html		gene_panel.json
# cell_boundaries.csv.gz		he_image.ome.tif
# cell_boundaries.parquet		he_imagealignment.csv
# cell_feature_matrix.h5		metrics_summary.csv
# cell_feature_matrix.zarr.zip	morphology.ome.tif
# cell_groups.csv			morphology_focus
# cells.csv.gz			nucleus_boundaries.csv.gz
# cells.parquet			nucleus_boundaries.parquet
# cells.zarr.zip			transcripts.parquet
# experiment.xenium		transcripts.zarr.zip

import spatialdata as sd
from spatialdata_io import xenium
import matplotlib.pyplot as plt
import seaborn as sns
import scanpy as sc
import squidpy as sq
xenium_path = "./Data/Raw/Xenium_Prime_Human_Lymph_Node_Reactive_FFPE_outs"
sdata = xenium(xenium_path)
zarr_path = "./Data/Derived/Xenium_5K_Human_Lymph_Node"
sdata.write(zarr_path)

Traceback

"sdata.write(zarr_path)
/Users/xyz/.pyenv/versions/3.9.19/lib/python3.9/site-packages/tifffile/tifffile.py:9437: UserWarning: <tifffile.TiffPage 0 @16> reading array from closed file
  warnings.warn(
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/xyz/.pyenv/versions/3.9.19/lib/python3.9/site-packages/spatialdata/_core/spatialdata.py", line 1159, in write
    self._write_element(
  File "/Users/xyz/.pyenv/versions/3.9.19/lib/python3.9/site-packages/spatialdata/_core/spatialdata.py", line 1207, in _write_element
    write_points(points=element, group=element_type_group, name=element_name, format=parsed["points"])
  File "/Users/xyz/.pyenv/versions/3.9.19/lib/python3.9/site-packages/spatialdata/_io/io_points.py", line 74, in write_points
    points.to_parquet(path)
  File "/Users/xyz/.pyenv/versions/3.9.19/lib/python3.9/site-packages/dask/dataframe/core.py", line 5642, in to_parquet
    return to_parquet(self, path, *args, **kwargs)
  File "/Users/xyz/.pyenv/versions/3.9.19/lib/python3.9/site-packages/dask/dataframe/io/parquet/core.py", line 851, in to_parquet
    assert len(_paths) == 1, "only one path"
AssertionError: only one path"

Version

print(squidpy.__version__)

1.6.1
...

Hello team, any updates on this issue? With gratitude.


Code Sign error: No code signing identities found: No valid signing identities

Hello guys, i'm having this issue and i really dont know how to fix it!, any idea?
Check dependencies
Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “(null)” were found.
CodeSign error: code signing is required for product type 'Framework' in SDK 'iOS 8.4'
Thank you

Forget it!, i fixed it!


Dropdown - event.stopPropagation prevents dropdown from opening

Describe the bug
On stopping event propagation on Dropdown onClick prevents the dropdown items from opening.
To Reproduce
Suppose I have a div with an onClick listener and Dropdown component is it's child. I want to prevent the propagation of click event on dropdown menu icon from reaching the  onClick listener on it's parent div.
While using the below snippet, the dropdown won't open.
<div onClick={() => doSomething()}
  <Dropdown
    onClick={(e) => {
      e.stopPropagation();
    }}
  >
    <Dropdown.Item>Item</Dropdown.Item>
  </Dropdown>
  {/* ... /}
</div>

Expected behavior
Dropdown items should open and stop the event from propagating.
Project information:

Tailwind: 3.0.0
Flowbite: 1.4.7
Flowbite React: 0.1.2
Type: CRA

Thank you for reporting this issue. However, we regret to inform you that we won't be able to address it for the following reasons:

The reported issue refers to an unsupported old version of our project.
Our team was unable to reproduce the problem with the information provided.
Insufficient information was provided to conduct a thorough investigation.

We recommend upgrading to the latest version and submitting a new issue if the problem persists. Thank you for your understanding.

any update ?


Can't open exe

https://imgur.com/yrFeugK

Hey. I think this could have been either a decency issue or an issue with the program failing to make itself always on top or disabling quick edit.
Please try v.1.0.3 which I pushed just now. FastStronghold is now self contained meaning all dependencies are included, so if that was the problem that should be resolved. And failure of the window setting itself always on top and disabling quick edit should now be handled properly. So if that was the problem that should be resolved now too.
Please let me know if it resolved your issues.

v1.0.3 has resolved the problem.


File upload from InputStream directly

I try to upload file from internal Uri using ContentResolver. I have got filename and Uri (I can open inputstream over ContentResolver) but I have no File.
There's a stream and a filename inside UploadTaskRequest but I cannot access them.
The only workaround I found is to create temporary file.
Could you please consider about create alternative way of UploadTaskRequest initialization?

I second this.
It'd be better if we can call upload with (a list of) InputStream(s), instead of (a list of) File(s).

Would be really useful if added!


Restore ConfigurationReaderTest

Since the ConfigurationReader class was moved from SuperElastix Core to Applications its Unit tests are not in any project anymore.

done in #122


WebService Target httpPost body starts with BOM in case of UTF-8

Hi Jarek (co slychac)
Could you fix stream to not include BOM, it messes up first parameter of httpPost body
here is more details about the problem (from someone else):
http://nlog-forum.1685105.n2.nabble.com/WebService-target-HttpPost-and-HttpGet-not-working-td7577418.html

Duplicate of #212


Update for 1.13.1

on start all it's ok but we try to modify a value (to hand/entity/blocks...) that give us a message error said the value don't change we can't edit.
so can you update ?
thanks

Spigot --rev 1.13.1
PowerNBT version <IP_ADDRESS>
All works fine
Please attach your log file.

nothing in my log only in game:

If it is any help

Thank you! I will try to reproduce this error again

I have found the issue. findMethodByReturnType is finding the first method in NBTBase that returns NBTBase. This now finds NBTBase:createTag(byte). I will see if I can fix this without breaking version independence.


BCL API review feedback: Remove basePath argument from Configuration/ConfigurationBuilder constructor

Currently the Configuration constructor takes a string basePath argument that can be flown to all its associated file-system based configuration sources for convenience. But this entangles the layering (at least conceptually) because we want Configuration to be available even in platforms in there is no concept of a file system available to the application.
One proposal is to remove the argument from the Configuration constructor (this will become the ConfigurationBuilder when we make the changes to split the builder into its own class per #194) and pass it to the individual sources.
We could alternatively consider replacing this argument with a more abstract way to represent the location of configuration files.

Superseded by #233.


src/ based layout breaks pytest

During Debian package build, the pytest test cases can easily be executed by running this command in the root directory:
python3 -m pytest -ra tests/functional tests/unit

Commit 1daf13fd01cf87ecad0fb623e7c7f1ca02e3b902 switches the project to an src/ based layout and breaks this way of running pytest. Specifying --rootdir does not help.

We use nox to run out tests. That ensure we have the required dependencies met to run the tests in a virtualenv and we also install the plugin into that virtualenv.
How does Debian handle any other src based layout python project?

if you dont want to install the plugin, you can set the PYTHONPATH to src/

On Debian, all dependencies are installed via Debian package. The Debian source package defines all build dependencies that are installed before the package build starts. Then the package is build: configure, build, test, install. These steps depend on the used build system. During the test phase, the code from the working directory is tested. There are also autopkgtest tests that will run test cases against installed packages.
The Debian source package must be self-contained and only depend on code specfied in the build dependencies. It must not fetch data from the Internet. So pip is a no-go.

Setting PYTHONPATH does not work:
$ PYTHONPATH=src/ python3 -m pytest -ra tests/functional tests/unit
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/pytest.py", line 102, in <module>
    raise SystemExit(pytest.main())
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 65, in main
    config = _prepareconfig(args, plugins)
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 213, in _prepareconfig
    return pluginmanager.hook.pytest_cmdline_parse(
  File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83, in <lambda>
    self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 203, in _multicall
    gen.send(outcome)
  File "/usr/lib/python3/dist-packages/_pytest/helpconfig.py", line 94, in pytest_cmdline_parse
    config = outcome.get_result()
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 789, in pytest_cmdline_parse
    self.parse(args)
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 997, in parse
    self._preparse(args, addopts=addopts)
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 943, in _preparse
    self.pluginmanager.load_setuptools_entrypoints("pytest11")
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 297, in load_setuptools_entrypoints
    plugin = ep.load()
  File "/usr/lib/python3.8/importlib/metadata.py", line 77, in load
    module = import_module(match.group('module'))
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'saltfactories.plugin'

And if you make that python path variable the full path to src?
There aren't any more pytest plugins that use src layout being built by Debian?
That way we would know how we could fix this.

I cannot remember that I packaged a Python module that used src. I checked a bunch of packaged pytest plugins, but all checked do not run test cases during build:

python-pytest-benchmark
pytest-cookies
python-pytest-cov
pytest-django
pytest-expect

And if you make that python path variable the full path to src?

I figured out why I got this stack trace: It was caused by an older system installed version of pytest-salt-factories.
When trying to build in a clean environment, I end up in a dependency rabbit burrow: We have in Debian unstable:

python3-pytest 6.0.2-2
python3-pytest-helpers-namespace 2019.1.8-1

pytest-salt-factories needs python3-pytest-helpers-namespace >= 2020.3.24 which needs Pytest >= 6.1.1. I am calling it day now.

I can probably cut another release pytest-helpers-namespace if I see that I can lower the pytest dependency.

That would be great.

FTR, I have the Debian package pytest-salt-factories 0.121.1-1 with working pytest on Debian unstable: https://salsa.debian.org/salt-team/pytest-salt-factories/-/commits/master-next
I can use this pytest-salt-factories 0.121.1-1 package combined with the Debian unstable packaging of salt to successfully run the pytest on the salt master branch during Debian package build.

Just noticed that this package also requires Pytest >= 6.1.1

Despite that I was able to use python3-pytest 6.0.2-2, but I am only running the functional and unit tests.

Dropped pytest requirement to 6.0.0 for pytest-helpers-namespace and released v2021.4.29
Will drop it on pytest-salt-factories too.

Done. Both plugins now require PyTest 6.0.0

Thanks. I successfully tested the master branch with pytest-helpers-namespace 2021.4.29-1 using:
PYTHONPATH=src python3 -m pytest -ra tests/functional tests/unit

So setting PYTHONPATH=src allows running pytests after the layout change.


Set up new round via websocket, resolves #34

@itsniezwe could you review please? Note that there were some issues with the CardDeckServiceTest that I was unable to resolve, would be good if you could have a look.


New Script Theme, and export(String, MULTILINE) support.

Changed the scripting IDE Theme to match the Dark theme more. Added supp...ort for export(String, "Multiline") var some_string = ""

Any chances of this being submitted any time soon? I am actually relying on this with my project, and I recall people wishing for this feature to be added asap as well.

In my opinion, scripting theme does not match, it's unreadable.

Could you please split this pull-request?
Thanks a lot!

actually yeah, splitting is appreciated, the multiline patch i can merge right away, theme not for now as ndee and other guys are working on a new one, so the current black one is not final yet

Hey all, sorry for the late reply. My emails, I rarely check. As for why most things went wrong, it's a sad fact that I was working with a new setup etc, no need to explain.
I'll just make a separate pull request for the multiline since I take it you haven't merged it yet because my pull request wasn't split. As such I'll let the theme be as is, no need to bother with that anymore given your information @reduz :)


comment out fastlane test archiving

Description
Currently cirrus is failing the mac deploy gallery test because fastlane is looking for a version of the Google Cloud SDK newer than that on the docker image. Re-building the docker image is complicated, so I am temporarily commenting out the offending step. Note, that this test will still fail on the next published release until the issue is resolved:  https://github.com/flutter/flutter/issues/43204.

FYI you can use Dockerfile as CI Environment with Cirrus for easier upgrades.

deploy_gallery-macos passed, so I will land this


Makefile: Format nicer by removing whitelines

{% if .. %}
You can drop all these white lines being created by using -:
{%- if .. %} removes whitespace before the IF
{% if .. -%} removes whitespace after the IF

fixed by #144


ng build fails with "No errors"

OS?

Windows 10

Versions.

angular-cli: 1.0.0-beta.25.5
node: 6.9.2

Repro steps.

App was created using angular-cli, I changed quite a bit, but the build failure actually occured when I tried pushing to heroku, the build still works on my computer, I tried copying the project to a different folder and running npm install and then the build failed there too.
I also tried creating an empty app using angular-cli it also fails to build that app as well!!

The log given by the failure.

No errors
Error: No errors
at validate (C:\Projects\Typescript\meeet - Copy\node_modules\extract-text-webpack-plugin\schema\validator.js:10:9)
at Function.ExtractTextPlugin.extract (C:\Projects\Typescript\meeet - Copy\node_modules\extract-text-webpack-plugin\index.js:188:3)
at C:\Projects\Typescript\meeet - Copy\node_modules\angular-cli\models\webpack-build-utils.js:72:77
at Array.map (native)
at Object.makeCssLoaders (C:\Projects\Typescript\meeet - Copy\node_modules\angular-cli\models\webpack-build-utils.js:69:53)
at Object.getWebpackCommonConfig (C:\Projects\Typescript\meeet - Copy\node_modules\angular-cli\models\webpack-build-common.js:77:65)
at new NgCliWebpackConfig (C:\Projects\Typescript\meeet - Copy\node_modules\angular-cli\models\webpack-config.js:24:49)
at Class.run (C:\Projects\Typescript\meeet - Copy\node_modules\angular-cli\tasks\build-webpack.js:20:22)
at Class.buildRun (C:\Projects\Typescript\meeet - Copy\node_modules\angular-cli\commands\build.run.js:49:22)
at Class.run (C:\Projects\Typescript\meeet - Copy\node_modules\angular-cli\commands\build.js:38:47)
at Class. (C:\Projects\Typescript\meeet - Copy\node_modules\angular-cli\ember-cli\lib\models\command.js:147:17)
at process._tickCallback (internal/process/next_tick.js:103:7)

Mention any other details that might be useful.

package.json:
{
"name": "somename",
"version": "0.0.0",
"license": "MIT",
"engines": {
"node": "6.9.2",
"npm": "3.10.9"
},
"angular-cli": {},
"scripts": {
"ng": "ng",
"start": "node bin/server/server.js",
"lint": "tslint "src/server//*.ts" --project src/server/tsconfig.json --type-check && tslint "src/client//*.ts" --project src/client/tsconfig.json --type-check",
"postinstall": "node node_modules/gulp/bin/gulp.js build"
},
"private": true,
"dependencies": {
"@angular/common": "^2.4.3",
"@angular/compiler": "^2.3.1",
"@angular/compiler-cli": "^2.3.1",
"@angular/core": "^2.4.3",
"@angular/forms": "^2.3.1",
"@angular/http": "^2.3.1",
"@angular/material": "^2.0.0-beta.1",
"@angular/platform-browser": "^2.3.1",
"@angular/platform-browser-dynamic": "^2.3.1",
"@angular/router": "^3.3.1",
"@types/core-js": "^0.9.35",
"@types/express": "^4.0.34",
"@types/jasmine": "2.5.38",
"@types/materialize-css": "^0.97.33",
"angular-cli": "1.0.0-beta.25.5",
"angular2-materialize": "^6.4.0",
"codelyzer": "~2.0.0-beta.1",
"core-js": "^2.4.1",
"express": "^4.14.0",
"gulp": "^3.9.1",
"gulp-exec": "^2.1.3",
"gulp-shell": "^0.5.2",
"gulp-sourcemaps": "^2.4.0",
"gulp-typescript": "^3.1.4",
"jquery": "^2.2.4",
"materialize-css": "^0.97.8",
"pg": "^6.1.2",
"protractor": "~4.0.13",
"reflect-metadata": "^0.1.9",
"routing-controllers": "^0.6.9",
"rxjs": "^5.0.3",
"ts-helpers": "^1.1.1",
"ts-node": "1.2.1",
"tslint": "^4.3.0",
"typeorm": "0.0.7",
"typescript": "^2.1.5",
"zone.js": "^0.6.26"
}
}

Dupe of: https://github.com/angular/angular-cli/issues/4264

Failed finding it with google, thanks!


The Big Catch Up

Liking the pr name
On Tue, May 26, 2020, 9:49 PM Nicholas Licitra<EMAIL_ADDRESS>wrote:

Merged #11 https://github.com/room-haus/room.haus/pull/11 into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/room-haus/room.haus/pull/11#event-3376050993, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7QMEIIASUZCDVXZTAWJ63RTRWTFANCNFSM4NLRX5IQ
.


macOS 版安装似乎无效

在macOS 的QQ中按照manual部署了本插件加载器和美化插件，但是重启QQ之后没有变化，不知道是加载器没有装对还是插件没有装对，有没有什么检测方法

BetterQQNT数据目录被我写死了获取环境变量的BETTTERQQNT_PROFILE与C:\BetterQQNT目录，没有对其他系统进行适配（（
然而默认系统并没有BETTTERQQNT_PROFILE变量，在非Windows系统下会尝试读取C:\BetterQQNT目录导致报错（
你可以用终端运行QQNT看看输出是否有关于BetterQQNT的输出

尝试使用新发布的0.1.0版本解决？https://github.com/mo-jinran/BetterQQNT/releases/tag/0.1.0

BetterQQNT数据目录被我写死了获取环境变量的BETTTERQQNT_PROFILE与C:\BetterQQNT目录，没有对其他系统进行适配（（
然而默认系统并没有BETTTERQQNT_PROFILE变量，在非Windows系统下会尝试读取C:\BetterQQNT目录导致报错（
你可以用终端运行QQNT看看输出是否有关于BetterQQNT的输出

我已经export了环境变量，也把代码里写的默认路径改成了我macOS下的路径

我查看了QQ的启动日志，没找到与BetterQQNT相关的输出信息
默认	12:29:58.724118+0800	QQ	Requesting container lookup; personaid = -1, type = NOPERSONA, name = <unknown>, origin [pid = 0, personaid = 0], proximate [pid = 0, personaid = 0], class = 2, identifier = <private>, group_identifier = <private>, create = 0, temp = 0, euid = 501, uid = 501
默认	12:29:58.724176+0800	QQ	Query; personaid = -1, type = NOPERSONA, name = <unknown>, origin [pid = 0, personaid = 0], proximate [pid = 0, personaid = 0], euid = 501, uid = 501, query = <private>
默认	12:29:58.727453+0800	QQ	container_query_get_single_result: success
默认	12:29:58.727540+0800	QQ	Consuming sandbox extension; path = [<private>], key = 0
默认	12:29:58.727631+0800	QQ	Consuming sandbox extension; path = [<private>], key = 0
默认	12:29:58.727680+0800	QQ	Revoking sandbox extension; key = 0
默认	12:29:58.727751+0800	QQ	container_create_or_lookup_for_platform: success
默认	12:29:58.727833+0800	QQ	Revoking sandbox extension; key = 0
默认	12:29:58.796521+0800	QQ	server port 0x00002c0b, session port 0x00002c0b
默认	12:29:58.816134+0800	QQ	New connection 0x1a312f main
默认	12:29:58.824029+0800	QQ	CHECKIN: pid=95918
默认	12:29:58.828365+0800	QQ	Received configuration update from daemon (initial)
默认	12:29:58.834753+0800	QQ	CHECKEDIN: pid=95918 asn=0x0-0x1189188 foreground=1
默认	12:29:58.840363+0800	QQ	FRONTLOGGING: version 1
默认	12:29:58.840435+0800	QQ	Registered, pid=95918 ASN=0x0,0x1189188
默认	12:29:58.843794+0800	QQ	BringForward: pid=95918 asn=0x0-0x1189188 bringForward=1 foreground=1 uiElement=0 launchedByLS=1 modifiersCount=1 allDisabled=0
默认	12:29:58.843838+0800	QQ	BringFrontModifier: pid=95918 asn=0x0-0x1189188 Modifier 0 hideAfter=0 hideOthers=0 dontMakeFrontmost=0 mouseDown=0/0 seed=0/0
默认	12:29:58.843884+0800	QQ	BringForward: pid=95918 asn=0x0-0x1189188
默认	12:29:58.843916+0800	QQ	SetFrontProcess: asn=0x0-0x1189188 options=0
默认	12:29:58.861644+0800	QQ	Current system appearance, (HLTB: 1), (SLS: 0)
默认	12:29:58.865566+0800	QQ	No persisted cache on this platform.
默认	12:29:58.866812+0800	QQ	Failed to copy the SysCfgDict MG key with error: 0
默认	12:29:58.874962+0800	QQ	Current system appearance, (HLTB: 1), (SLS: 0)
默认	12:29:58.877008+0800	QQ	Post-registration system appearance: (HLTB: 1)
错误	12:29:59.051083+0800	QQ	<SKPaymentQueue: 0x11800849c80>: No observers found that respond to "paymentQueue:shouldAddStorePayment:forProduct:", will not check for purchase intents
默认	12:29:59.052223+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:29:59.085427+0800	QQ	sf changed: <private>
默认	12:29:59.136764+0800	QQ	networkd_settings_read_from_file initialized networkd settings by reading plist directly
默认	12:29:59.137600+0800	QQ	networkd_settings_read_from_file initialized networkd settings by reading plist directly
默认	12:29:59.138308+0800	QQ	nw_path_evaluator_start [6DDF3ACE-EB82-45D6-90D6-AB2FB3D8854B <NULL> generic, attribution: developer]
	path: satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns
默认	12:29:59.152498+0800	QQ	{"msg":"CLLocationManager", "event":"activity", "_cmd":"initWithEffectiveBundleIdentifier:bundlePath:delegate:silo:", "self":"0x118010a9b40", "identifier":"", "bundlePath":""}
默认	12:29:59.152590+0800	QQ	{"msg":"state transition", "event":"state_transition", "state":"LocationManager", "id":"0x118010a9b40", "property":"init", "new":{"trackRunInfoEnabled":false,"previousAuthorizationStatusValid":false,"paused":false,"requestingLocation":false,"updatingVehicleSpeed":false,"desiredAccuracy":100,"allowsBackgroundLocationUpdates":false,"dynamicAccuracyReductionEnabled":false,"distanceFilter":-1,"allowsLocationPrompts":true,"activityType":0,"groundAltitudeEnabled":false,"pausesLocationUpdatesAutomatically":1,"fusionInfoEnabled":false,"isAuthorizedForWidgetUpdates":false,"updatingVehicleHeading":false,"batchingLocation":false,"showsBackgroundLocationIndicator":false,"updatingLocation":false,"requestingRanging":false,"updatingHeading":false,"previousAuthorizationStatus":0,"allowsMapCorrection":true,"matchInfoEnabled":false,"allowsAlteredAccessoryLocations":false,"updatingRanging":false,"limitsPrecision":false,"courtesyPromptNeeded":false,"headingFilter":1}}
默认	12:29:59.152622+0800	QQ	{"msg":"state transition", "event":"state_transition", "state":"LocationManager", "id":"0x118010a9b40", "property":"lifecycle", "old":"0x0", "new":"0x11801068b20"}
默认	12:29:59.152650+0800	QQ	{"msg":"client allocated", "client":"0x11800816bc0"}
默认	12:29:59.152688+0800	QQ	{"msg":"_CLClientCreateConnection", "event":"activity", "client":"0x11800816bc0"}
默认	12:29:59.153788+0800	QQ	{"msg":"Sending cached messages to daemon", "event":"activity"}
默认	12:29:59.156862+0800	QQ	#Warning Location connection invalid!

默认	12:29:59.167722+0800	QQ	notify_get_state check indicated test daemon not ready.
默认	12:29:59.167920+0800	QQ	notify_get_state check indicated test daemon not ready.
默认	12:29:59.168087+0800	QQ	notify_get_state check indicated test daemon not ready.
默认	12:29:59.185982+0800	QQ	ApplePersistenceIgnoreState: Existing state will not be touched.
错误	12:30:02.662306+0800	QQ	CGSWindowShmemCreateWithPort failed on port 0
默认	12:30:02.674937+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:02.675031+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:02.788918+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:02.788985+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:02.957273+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:02.957335+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:03.210010+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:03.210078+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:03.297362+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:03.297425+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:03.506541+0800	QQ	SetFrontProcess: asn=0x0-0x1189188 options=1
默认	12:30:03.510567+0800	QQ	order window front conditionally: d8b8 related: 0
默认	12:30:03.511033+0800	QQ	SetFrontProcess: asn=0x0-0x1189188 options=1
默认	12:30:03.513887+0800	QQ	order window front conditionally: d8b8 related: 0
默认	12:30:03.521522+0800	QQ	order window front conditionally: d8b8 related: 0
默认	12:30:03.521917+0800	QQ	order window front conditionally: d8b8 related: 0
错误	12:30:03.533253+0800	QQ	open flag(s) 0x01000000 are reserved for VFS use and do not affect behaviour when passed to sqlite3_open_v2
错误	12:30:03.533371+0800	QQ	cannot open file at line 46922 of [554764a6e7]
错误	12:30:03.533410+0800	QQ	os_unix.c:46922: (2) open(/private/var/db/DetachedSignatures) - No such file or directory
默认	12:30:03.661986+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:03.662044+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:03.951105+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:03.951172+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:03.966022+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:03.966089+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:07.526504+0800	QQ	TSM AdjustCapsLockLEDForKeyTransitionHandling - _ISSetPhysicalKeyboardCapsLockLED Inhibit
故障	12:30:09.234797+0800	QQ	Registration timer expired, but client is still registering!
默认	12:30:09.781610+0800	QQ	LSExceptions shared instance invalidated for timeout.
默认	12:30:10.124924+0800	QQ	Released connection: AEE9E430-C55E-434A-A837-1F1BC9DF07F5
{
    UUID = "AEE9E430-C55E-434A-A837-1F1BC9DF07F5";
    caller = "HIToolbox: _TISCopyAttachedKeyboardLanguages + 82";
    dispatchQueue = 0;
    eventCount = 0;
    eventMask = 0;
    port = 136951;
    resetCount = 0;
    runloop = 0;
    services =     (
<PHONE_NUMBER>,
<PHONE_NUMBER>,
<PHONE_NUMBER>
    );
    virtualServices =     (
    );
}
默认	12:30:10.163378+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:10.163472+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:10.433748+0800	QQ	SetFrontProcess: asn=0x0-0x1189188 options=1
默认	12:30:10.439224+0800	QQ	order window front conditionally: d8b9 related: 0
默认	12:30:10.439770+0800	QQ	SetFrontProcess: asn=0x0-0x1189188 options=1
默认	12:30:10.443276+0800	QQ	order window front conditionally: d8b9 related: 0
默认	12:30:10.466809+0800	QQ	order window front conditionally: d8b9 related: 0
默认	12:30:10.467384+0800	QQ	order window front conditionally: d8b9 related: 0
默认	12:30:10.491679+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:10.491761+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:10.607836+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:10.607940+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:10.920238+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:10.920337+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:10.973161+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:10.973253+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:11.078643+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:11.078737+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:11.083539+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:11.083630+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:11.102910+0800	QQ	Invalidate NSApp effectiveAppearance
默认	12:30:11.102998+0800	QQ	NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x118004eae80
 (
    "<NSAquaAppearance: 0x118004eb000>",
    "<NSSystemAppearance: 0x118004ea100>"
)>
默认	12:30:12.166465+0800	QQ	order window: d8b8 op: 1 relative: d8b9 related: 0
默认	12:30:12.166563+0800	QQ	order window: d8b9 op: 0 relative: 0 related: 0
默认	12:30:12.210618+0800	QQ	order window: d8b9 op: 0 relative: 0 related: 0
错误	12:30:12.213592+0800	QQ	CGSWindowShmemCreateWithPort failed on port 0
默认	12:30:12.436599+0800	QQ	NotifyToken::RegisterDispatch(user.uid.501.com.apple.LaunchServices.database) fired for session key <private>
默认	12:30:04.501902+0800	QQ ScreenCapture plugin	Requesting container lookup; personaid = -1, type = NOPERSONA, name = <unknown>, origin [pid = 0, personaid = 0], proximate [pid = 0, personaid = 0], class = 2, identifier = <private>, group_identifier = <private>, create = 0, temp = 0, euid = 501, uid = 501
默认	12:30:04.501952+0800	QQ ScreenCapture plugin	Query; personaid = -1, type = NOPERSONA, name = <unknown>, origin [pid = 0, personaid = 0], proximate [pid = 0, personaid = 0], euid = 501, uid = 501, query = <private>
默认	12:30:04.504810+0800	QQ ScreenCapture plugin	container_query_get_single_result: success
默认	12:30:04.504861+0800	QQ ScreenCapture plugin	Consuming sandbox extension; path = [<private>], key = 0
默认	12:30:04.504906+0800	QQ ScreenCapture plugin	Consuming sandbox extension; path = [<private>], key = 0
默认	12:30:04.504939+0800	QQ ScreenCapture plugin	Revoking sandbox extension; key = 0
默认	12:30:04.504966+0800	QQ ScreenCapture plugin	container_create_or_lookup_for_platform: success
默认	12:30:04.504981+0800	QQ ScreenCapture plugin	Revoking sandbox extension; key = 0
默认	12:30:04.508230+0800	QQ ScreenCapture plugin	networkd_settings_read_from_file initialized networkd settings by reading plist directly
默认	12:30:04.508616+0800	QQ ScreenCapture plugin	networkd_settings_read_from_file initialized networkd settings by reading plist directly
默认	12:30:04.515080+0800	QQ ScreenCapture plugin	CocoaLumberjack: Warning: Usage of DDTTYLogger detected when DDOSLogger is available and can be used! Please consider migrating to DDOSLogger.

默认	12:30:04.568550+0800	QQ ScreenCapture plugin	Failed to copy the SysCfgDict MG key with error: 0
默认	12:30:04.570379+0800	QQ ScreenCapture plugin	Current system appearance, (HLTB: 1), (SLS: 0)
默认	12:30:04.571325+0800	QQ ScreenCapture plugin	Post-registration system appearance: (HLTB: 1)
默认	12:30:04.576689+0800	QQ ScreenCapture plugin	Received configuration update from daemon (initial)
默认	12:30:04.616590+0800	QQ ScreenCapture plugin	Registering for test daemon availability notify post.
默认	12:30:04.616736+0800	QQ ScreenCapture plugin	notify_get_state check indicated test daemon not ready.
默认	12:30:04.616863+0800	QQ ScreenCapture plugin	notify_get_state check indicated test daemon not ready.
默认	12:30:04.616965+0800	QQ ScreenCapture plugin	notify_get_state check indicated test daemon not ready.

已尝试兼容，根据 https://github.com/mo-jinran/BetterQQNT/issues/29 反馈结果，应该可以正常使用


[incubator-kie-issues#804] Fix flaky test

Fix https://github.com/apache/incubator-kie-issues/issues/804
(checked locally with 2000000 iterations)

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

for pull request checks
Please add comment: Jenkins retest this

for a specific pull request check
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] tests

for a full downstream build

for jenkins job: please add comment: Jenkins run fdb
for github actions job: add the label run_fdb

a compile downstream build please  add comment: Jenkins run cdb

an upstream build please add comment: Jenkins run upstream

for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch

for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main

for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-main

for quarkus lts checks
Run checks against Quarkus lts branch
Please add comment: Jenkins run quarkus-lts

for a specific quarkus lts check
Run checks against Quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts

for native checks
Run native checks
Please add comment: Jenkins run native

for a specific native check
Run native checks
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native

for native lts checks
Run native checks against quarkus lts branch
Please add comment: Jenkins run native-lts

for a specific native lts check
Run native checks against quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native-lts

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@yurloc
For this test I want to be sure that any randomly distributed probability will work.
The root problem is: how to split a double (the initial probability) into three random doubles.
If, by chance, you have a better solution, please suggest it, I'll gladly use it


Cross namespace volume data source in PVC

Describe the feature you'd like to have
kubernete 1.26 is allowing cross namespace volume data sources in PVC. According to the doc, you must enable the CrossNamespaceVolumeDataSource feature gate for the csi-provisioner. So I'm assuming ceph-csi need to support this feature?
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#cross-namespace-data-sources
What is the value to the end user? (why is it a priority?)
End users can leverage ceph's COW clone feature across different namespace. Currently it both source and destination pvc need to be on same namespace

Looks a valid request, picking it up!

Hello,
I'm permit myself to contact you about this issue.
Indeed I have some use case where I need this capabilities : copy ceph pvc or snapshots between namespace.
Is there any plan to implement this function ?
I have found this, can be used as an exemple ?
https://github.com/kubernetes-csi/external-provisioner/blob/master/pkg/controller/controller.go#L853
Thank you in advance

Thanks for reverting @benth42 .. indeed we can try to enable it here, however please note that the functionality (CrossNamespaceVolumeDataSource) in the controller is ALPHA and default to OFF

Thanks to you.  It would be very great.
Yes I know for the ALPHA status. (Hower I image and hope that it will be confirmed)

+1 Would really be useful for our company as well.

@humblec do you have any plan to continue working on this one?


Provide an initial setup for XiCore protocol implementation

This PR is for adding an initial setup for XiCore protocol implementation.
Please let me know what you think about the names of the classes and the sample usage convention in the AppDelegate.
If the proposal matches the architecture goal we can proceed with XiCore protocol implementation in the following PR's.

@mmatoszko Cool, that was quick!
I should have time to give this a proper look through later today or tomorrow. 👍

@mmatoszko let me know your thoughts on those other couple of points; If this has to be a slightly bigger PR that's fine, it's pretty smooth reviewing I think.

@cmyr I aligned to your suggestions, thank you 👍
Is there anything more we should consider doing before merging this PR?

Happily, there are super nice and well defined naming conventions for Swift which we can use 😄
According to that, I would suggest going with renaming just the things which are only in the scope of the classes changed in this issue, that is:
Connection -> RPCSending.
Renamings of:
CoreRPC -> CoreConnection
and
CoreConnection -> abettername
should be rather tackled separately.
When it comes to a class which implements the RPCSending, AKA abettername I'm still undecided 😅
Maybe we could just go with RPCSender, so we have something like this:
protocol RPCSending {
}

class RPCSender: RPCSending {
}

It strongly depends whether or not there's gonna be more classes which implement that protocol.
Opinions? Please let me know if anything is not clear enough 😃

So my basic thinking here is that we want to support future types of connection that don't use stdin/stdout.
To think about this concretely: iOS does not allow a process to spawn subprocesses, which means the current way that we talk to xi-core won't work on iOS. At 'some point' we expect xi-core to become a library, that exposes a C interface. We'll write a swift wrapper for that. We'll then want to implement this RPCSending trait for that wrapper (or maybe for some other type that interfaces with that wrapper; to be decided).
Another example: maybe instead of stdio, we use Berkley Sockets, and run xi-core in a dedicated thread; in this case we would want to have some equivalent of the current CoreConnection class, but it would be communicating over sockets instead of over stdin/stdout; but this would also implement RPCSending.
Is that helpful?

Loud and clear thank you 👌
Is it ok for you if we tackle the small renamings here, and then do the big renamings in a different PR?
This one grew too big already. I’m a huge fan of splitting big problems into smaller ones ☺

@mmatoszko sure, that works for me!


Don't send a status_request extension in a CertificateRequest message

If a TLSv1.3 server configured to respond to the status_request extension
also attempted to send a CertificateRequest then it was incorrectly
inserting a non zero length status_request extension into that message.
The TLSv1.3 RFC does allow that extension in that message but it must
always be zero length.
In fact we should not be sending the extension at all in that message
because we don't support it.
Fixes #9767
In order to detect this in a test we also Teach TLSProxy how to parse CertificateRequest messages.

The fix for this was easy - but the test was non trivial, because TLSProxy did not know how to parse CertificateRequest messages!

Travis red cross is unrelated (another instance of the log length being exceeded - ouch).

Pushed to master and 1.1.1. Thanks.


Design and create Vuex

This week I will be adding a Vuex State for the signup page.
https://nuxtjs.org/docs/directory-structure/store/
https://vuex.vuejs.org/


duplicate URL's

In the section "Revised documentation for task sequence variables", the links to the two new articles go to to the same URL.

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

ID: 22765ffe-cef8-a88f-5f71-00caf9b47046
Version Independent ID: cb5ad492-39d1-f63d-0bd2-7f3a0b1d8af0
Content: What's new in version 1806 - Configuration Manager
Content Source: sccm/core/plan-design/changes/whats-new-in-version-1806.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @cmolstad. Do you want to try clicking Edit on that article and submit the change? See Contribute for the basic steps. The first link should point to this article: https://docs.microsoft.com/sccm/osd/understand/using-task-sequence-variables.

Change submitted!
On 8/23/2018 4:15:53 PM, Aaron Czechowski<EMAIL_ADDRESS>wrote:
Thanks @cmolstad [https://github.com/cmolstad]. Do you want to try clicking Edit on that article and submit the change? See Contribute [https://docs.microsoft.com/en-us/sccm/core/understand/use-docs#bkmk_contribute] for the basic steps. The first link should point to this article: https://docs.microsoft.com/sccm/osd/understand/using-task-sequence-variables [https://docs.microsoft.com/sccm/osd/understand/using-task-sequence-variables].
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [https://github.com/MicrosoftDocs/SCCMdocs/issues/782#issuecomment-415573585], or mute the thread [https://github.com/notifications/unsubscribe-auth/AbdjU7idTY8wYuICfrAPBt89uVouEtOPks5uTxuJgaJpZM4WKU_E].

Hi @cmolstad, thanks for your willingness to help, but I haven't seen any pull requests yet. Make sure you create the pull request after you propose the change.

Sorry about that.  I just did a pull request a bit ago and it said I could merge it without issues so I did that.

Something's awry. There's no pull request (even closed). Go through the process again, and make sure to create the pull request. There are actually two buttons for Create pull request. See Step 5 of the Basic steps to contribute to SCCMdocs.
We're almost there! Thanks for sticking with this. The first time is always a good learning experience.

@aczechowski This issue should be fixed. Verified the links are now valid for the referenced articles.

Thanks @jocasti for catching this. Yes, it was fixed by #787. Closing


Store conversation data

Hi, I am using Bot framework to build a bot application, where I need to store the conversation data in a cosmos db or any other database so that at any point of time i can access those data and display them whenever necessary. I want to know where to put all the code snippets necessary for this step. I tried integrating it with redis-cli, but i could not find any relevant data or code explaining this. Please help me asap.
I found this code:
Please help me find all the fields that are used in this code segment.

Currently, there is no easy way to save conversation. There is a PR going on. It works, but the direction it is going is not very visionary, thus, we put it aside and back to the drawing board.

Please refer to #365 for tracking.


PARQUET-882: Improve Application Version parsing

@wesm, the file data/nation.dict-malformed.parquet you added to fix PARQUET-816 has an invalid created_by string parquet-mr.
The corresponding test is failing in this patch because of this. Can you tell me how this file was generated? Thanks.

It was created by an early version of parquet-mr (prior to 1.2.8). I believe we'll need to be robust to this

I had to use boost::regex since std::regex seems to have issues on a MacOS with these regular expressions.
https://travis-ci.org/apache/parquet-cpp/builds/203466061

@xhochy if we are going to do another RC, perhaps we should pull in this patch?

We should include this in the next RC.


nitunit: hanging indents on markdown lists recognized as code block

In the following example, "2nd level 2nd line" is reported as an invalid Nit code block by nitunit. Both syntaxes used in the following example are legal according http://daringfireball.net/projects/markdown/syntax#list
Note that both syntax are supported correctly by nitdoc.
# Some title
#
# * 1st level.
# 1st level 2nd line # OK
#  * 2nd level.
#    2nd level 2nd line # Not OK
#  * Other 2nd level.
# Other 2nd level 2nd line # OK
fun foo do print "asdf"

As of now, we can use the alternative syntax for a simple case. However I do not see how to do multiple paragraph per point:
# Some title
#
# * 1st level.
#  * 2nd level.
#    2nd level 2nd line
#
#    2nd level 2nd paragraph # ?
fun foo do print "asdf"

From previous exchange, maybe the trigger for a code block should be 4 spaces more than the previous indent?
Bug encountered in #1323.

Nice catch, nitunit is actually using the old md parser found in docdown.nit.
A rapid git grep "import docdown" gives us:
src/test_docdown.nit:20:import docdown
src/testing/testing_doc.nit:19:intrude import docdown

I propose to get rid of these parser and use the markdown lib as the rest of the Nit stack.
@privat: you were pretty attached to this parser, any objections?

I did not remember that the old md parser was still used. You can scrap it as you wish.

It was left as this to ensure compatibility with existing nitunit tests. A lot of existing docunits are not real markdown complient and thus, not tested.
I'm making the switch right now, let's see how many tests are missed.


How to actually pass the custom_conf into the container?

#Question
#Description of issue
Where does that file /share/telegraf.conf for custom_conf actually come from?
Apart from this normal usability confusion, wouldn't it be perhaps a nice idea if one could just supply a snipped of the config file (or optionally the whole thing) via a here-document in the config.yaml/config.json options?
#Ideas to fix
Allow adding extra snippets via the addon config.
Logs
<!--- please past the logs here ---!>

I did find the right path. I looked in the wrong 'root' directory. (I created share under '/config' accidentally)
But I have not yet crafted a complete and correct conf file.
Feel free to close the issue. I can make it work. But I have to say, working with snippets based on the auto-generated conf file sure feels nicer...
Cheers and thanks

i'll take a look at this and get back to you properly soon

I did find the right path. I looked in the wrong 'root' directory. (I created share under /config accidentally)
But I have not yet crafted a complete and correct conf file.
Feel free to close the issue. I can make it work. But I have to say, working with snippets based on the auto-generated conf file sure feels nicer...
Cheers and thanks

sorry for the long wait, i've had a look into this and am not quite sure how to implement this, would you have any ideas on how this could be done?

I would just paste the custom bit of the config at the end of the generated file.
Maybe even pass in the text blob as a here document style YAML value in the config editor.

I'm playing around with addon stuff a bit myself right now. Perhaps I come up with an idea...
https://github.com/tbaumann/homeassistant-addons


[Packaging] APT repository sign doesn't work on Debian trixie

Describe the bug, including details regarding any error messages, version, and platform.
https://github.com/ursacomputing/crossbow/actions/runs/12491251505/job/34857011325#step:17:589
  Err:1 file:/host/dev/release/../../dev/tasks/linux-packages/apt/repositories/debian trixie InRelease
    The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1729E5EF3EF74D10
  Hit:2 http://deb.debian.org/debian trixie InRelease
  Hit:3 http://deb.debian.org/debian trixie-updates InRelease
  Hit:4 http://deb.debian.org/debian-security trixie-security InRelease
  Get:5 http://deb.debian.org/debian trixie/non-free amd64 Packages [98.7 kB]
  Get:6 http://deb.debian.org/debian trixie/contrib amd64 Packages [51.0 kB]
  Reading package lists...
  Warning: file:/host/dev/release/../../dev/tasks/linux-packages/apt/repositories/debian/dists/trixie/InRelease: The key(s) in the keyring /usr/share/keyrings/apache-arrow-apt-source.gpg are ignored as the file has an unsupported filetype.
  Warning: GPG error: file:/host/dev/release/../../dev/tasks/linux-packages/apt/repositories/debian trixie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1729E5EF3EF74D10
  Error: The repository 'file:/host/dev/release/../../dev/tasks/linux-packages/apt/repositories/debian trixie InRelease' is not signed.
  rake aborted!

Component(s)
Packaging

how is the KEYS file generated? I can't seem to find where we generate /dev/tasks/linux-packages/KEYS:
   + gpg --no-default-keyring --keyring /usr/share/keyrings/apache-arrow-apt-source.gpg --import /host/dev/release/../../dev/tasks/linux-packages/KEYS
  gpg: directory '/root/.gnupg' created
  gpg: /root/.gnupg/trustdb.gpg: trustdb created
  gpg: key 1729E5EF3EF74D10: public key "Test<EMAIL_ADDRESS>imported
  gpg: Total number processed: 1
  gpg:               imported: 1

Ah, it's generated here: https://github.com/apache/arrow/blob/f5c340be342a427b8ef10e51e9d10fc6013c5b4c/dev/tasks/linux-packages/github.linux.yml#L101-L108
FYI: This happens with the current released apache-arrow-apt-source too: https://github.com/groonga/groonga/actions/runs/12499316173/job/34876380693?pr=2166#step:10:506
9.523 Err:4 https://apache.jfrog.io/artifactory/arrow/debian trixie InRelease
9.523   The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 91D18FCF079F8007
10.02 Get:5 https://packages.groonga.org/debian trixie InRelease [9539 B]
10.45 Warning: https://apache.jfrog.io/artifactory/arrow/debian/dists/trixie/InRelease: The key(s) in the keyring /usr/share/keyrings/apache-arrow-apt-source.gpg are ignored as the file has an unsupported filetype.
10.45 Warning: GPG error: https://apache.jfrog.io/artifactory/arrow/debian trixie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 91D18FCF079F8007
10.45 Error: The repository 'https://apache.jfrog.io/artifactory/arrow/debian trixie InRelease' is not signed.

I thought that this problem and the current released apache-arrow-apt-source have the same problem but it may be a different problem...

How to generate apache-arrow-apt-source.gpg: https://github.com/apache/arrow/blob/f5c340be342a427b8ef10e51e9d10fc6013c5b4c/dev/tasks/linux-packages/apache-arrow-apt-source/debian/rules#L13-L16

It seems like a different issue but the 91D18FCF079F8007 seems to be your public key, right? (below extracted from the public keys file)
sig          91D18FCF079F8007 2010-08-30  Kouhei Sutou<EMAIL_ADDRESS>

Yes. It's my public key used for the latest release.
https://salsa.debian.org/apt-team/apt/-/merge_requests/409/diffs#e3f4163114eae4ff41ebb44a774fddac10b4e6a7_0_122 may be related. We're using the "GPG keybox database" format but it accepts only the "OpenPGP Public Key" formats.
Hmm. It seems that we need to use dearmor-ed format for keyring: https://salsa.debian.org/apt-team/apt/-/merge_requests/409/diffs#e3f4163114eae4ff41ebb44a774fddac10b4e6a7_0_96

Ah, the merge request may not be related.
https://salsa.debian.org/apt-team/apt/-/merge_requests/407 may be related.

Issue resolved by pull request 45131
https://github.com/apache/arrow/pull/45131


"Prejmer" commune is listed in the drop-down menu

Description:
The commune is listed in the drop-down menu according to the law
Preconditions : the website (https://peviitor-ro.github.io/ui.orase/) is up and runing. After every step delete the text you typed from the search bar.

Step 1
Type "Prejmer" in the search bar.

Expected results
The location is listed in the drop-down menu as "Prejmer, Brașov"


How can I set a value externally in the Select Dropdown?

Case
I have a select list of items A, B and C. And through a button I want the selected item to be item C.
How can I change the value selected outside the SelectDropdown element?
Thanks in advance!

if you are asking to set a default value you can use defaultValue, If you are asking for a method that you can call it by using the ref, It's not implemented yet I think it's an important feature to be added I'll work on it.

if you are asking to set a default value you can use defaultValue, If you are asking for a method that you can call it by using the ref, It's not implemented yet I think it's an important feature to be added I'll work on it.

Hi Adel! Yes, I'm asking for a method that I can call it using a ref. Not the defaultValue.
I achieved that feature with #72.

selectIndex(index) this function is added in v3.0.0 to select an option from outside the component using a ref

Great! Thanks @AdelRedaa97 🎉


Include -> ThenInclude on List / Collection Navigation Property accesses the List and not the item contained within

Posting this as it took me ages to find issue #6560 which resolved this problem.
Hopefully this title contains more useful keywords for anyone else searching for the issue.
Short story is it's an intellisense bug, so type your lambda as if it was passing on a object and get on with your day. 🛩

Please if you hit this provide your feedback on the actual issue https://github.com/dotnet/roslyn/issues/8237 so that the Roslyn team can prioritize it.


Improving css of the pages of sorting and also debugging the page linking

I would like to improve the css of the sorting pages when we have to enter the number ..so i would like to improve the styling of theat pages and also there is some pages that are not properly link

The issue is already assigned, kindly look for some other issue!


required in allOf is NOT checked

cd to folder contains the jsonschema_issue.json and jsonschema_issue.py, run with:

python jsonschema_issue.py

expect validation fails, but it actually passed.

reference:

jsonschema_issue.py

import json

from jsonschema.validators import Draft4Validator
from jsonschema.exceptions import ValidationError

resp = '{"HostId": "example.com"}'

schema_file = 'jsonschema_issue.json'
with open(schema_file, 'r') as loadFile:
    schema = json.load(loadFile)

validator = Draft4Validator(schema)
try:
    validator.validate(json.loads(resp))
except ValidationError as e:
    print(e)
else:
    print("pass")

jsonschema_issue.json

{
    "allOf": [
        {
        "properties": {
            "RequestId": {"type": "string", "pattern": "abcd"},
            "required": ["RequestId"]
            }
        },
        {
        "properties": {
            "HostId": {"type": "string", "pattern": "example.com"},
            "required": ["HostId"]
            }
        }
    ]
}

if resp in jsonschema_issue.py:
resp = '{"RequestId": "abcd"}'

expect failure, but actual pass.
for the follow case:
resp = '{"RequestId": "abc2d", "HostId": "example.com"}'

the result is right.

Hi @lzq420241, there are still many many things here that look like they're not necessary for the bug report.
Ideally what's here should be exactly 1 line: validate(someobjectliteral, someinstanceliteral).
Does your issue still happen if you remove "type": "object" from your schema? If so, please remove it, and any other lines that are not required to reproduce.
Does your issue still happen if you don't use refs? If so please remove and inline them.

update to possible least code.

And the rest of the things I mentioned? Are you saying you've tested removing them and they then don't allow you to reproduce?

I have remove all the unrelated fields, the issue still exists.

@lzq420241 that isn't at all the case. Please read the article I linked very very carefully.
Here is what you should have provided, by iteratively deleting pieces of your code and schema, until you likely end up with something like:
from jsonschema.validators import Draft4Validator
Draft4Validator(
    {
        "allOf": [
            {
                "properties": {
                    "RequestId": {},
                    "required": ["RequestId"]
                }
            }
        ]
    },
).validate(
    {}
)

All I did were start combining your files and deleting lines, making sure the behavior was the same, until it was obvious what the issue was -- that you put required inside your properties, instead of alongside it.
Please do read that SSCCE article, it's what you should do when reporting an issue on any repository.

@Julian, sorry for waste your time, and thanks for your help.
I should be more careful and do as SSCCE told.


Convert *_sycl_native_ext into a proper Python module.

Adds an init.py to top-level *_sycl_native_ext folders.
Removes the init.py inside the _*_sycl folder.
Removes the superfluous setup.py inside the *_sycl_native_ext folders.
Updates dpcpp_framework to use the new *_sycl_native_ext module.

Two individual setup.py (black_scholes and pairwise_distance) removed. Tests passed with no issue. Changes merged.


Can't use RaggedTensor in @tf.function input_signature.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: no
TensorFlow installed from (source or binary): no
TensorFlow version (use command below): 2.0.1
Python version: 3.7.3
Bazel version (if compiling from source): -
GCC/Compiler version (if compiling from source): -
CUDA/cuDNN version: -
GPU model and memory: -

Describe the current behavior
It is not possible to pass a tf.RaggedTensor as a tf.function input signature, and therefore use it with e.g. Tensorflow Serving.
Describe the expected behavior
It should be possible to pass a tf.RaggedTensor as a tf.function input signature.
Code to reproduce the issue
import tensorflow as tf

class MyModule(tf.Module):
    def __init__(self):
        super(MyModule, self).__init__()
        tf.saved_model.save(
            self,
            "/tmp/foomodel/001",
            signatures={
                tf.saved_model.DEFAULT_SERVING_SIGNATURE_DEF_KEY: self.some_method,
            },
        )

    @tf.function(input_signature=[
        tf.TensorSpec((None, ), dtype=tf.int64),
        tf.RaggedTensorSpec((None, None), dtype=tf.string),
    ])
    def some_method(self, dense, ragged):
        return tf.constant(["foobar"], dtype=tf.string)

m = MyModule()
dense = tf.constant([[1,2]], dtype=tf.int64)
ragged = tf.ragged.constant([["foo"], ["foo", "bar"]], dtype=tf.string)
some_result = m.some_method(dense, ragged)
print(f"some_result => {some_result}")

#ValueError: Python inputs incompatible with input_signature:
# inputs: (
#    tf.Tensor([[1 2]], shape=(1, 2), dtype=int64),
#    <tf.RaggedTensor [[b'foo'], [b'foo', b'bar']]>)
#  input_signature: (
#    TensorSpec(shape=(None,), dtype=tf.int64, name=None),
#    RaggedTensorSpec(TensorShape([None, None]), tf.string, 1, tf.int64))

I have tried on colab with TF version 2.0 ,2.2.0-dev20200218 and was able to reproduce the issue.Please, find the gist here. Thanks!

@stefanondisponibile I am able to pass  tf.RaggedTensor as a tf.function input signature. Please find the gist here.

@gowthamkpr  yeah, you're right, but the problem is (if I'm not missing something here), that once exported and loaded into Tensorflow Serving, you won't be able to pass a RaggedTensor directly: you can see this also in your example by adding a cell doing this:
loaded = tf.saved_model.load("/tmp/foomodel/001")
print(loaded.signatures[tf.saved_model.DEFAULT_SERVING_SIGNATURE_DEF_KEY]._arg_keywords)
# ['ragged', 'ragged_1']

# Or inspect with saved_model_cli:
# !saved_model_cli show --dir /tmp/foomodel/001 --all
#
# MetaGraphDef with tag-set: 'serve' contains the following SignatureDefs:
#
# signature_def['__saved_model_init_op']:
#   The given SavedModel SignatureDef contains the following input(s):
#   The given SavedModel SignatureDef contains the following output(s):
#     outputs['__saved_model_init_op'] tensor_info:
#         dtype: DT_INVALID
#         shape: unknown_rank
#         name: NoOp
#   Method name is:
#
# signature_def['serving_default']:
#   The given SavedModel SignatureDef contains the following input(s):
#     inputs['ragged'] tensor_info:
#         dtype: DT_STRING
#         shape: (-1)
#         name: serving_default_ragged:0
#     inputs['ragged_1'] tensor_info:
#         dtype: DT_INT64
#         shape: (-1)
#         name: serving_default_ragged_1:0
#   The given SavedModel SignatureDef contains the following output(s):
#     outputs['output_0'] tensor_info:
#         dtype: DT_STRING
#         shape: (1)
#         name: PartitionedCall:0
#   Method name is: tensorflow/serving/predict
#
# Defined Functions:
#   Function Name: 'some_method'
#     Option #1
#       Callable with:
#         Argument #1
#           DType: RaggedTensorSpec
#           Value: RaggedTensorSpec(TensorShape([None, None]), tf.string, 1, tf.int64)

As you can see, the ragged input will be split into two different dense ones: ragged and ragged_1, respectively representing the ragged values and row splits.
I am currently working around this by computing values and row splits from my ragged inputs, and then building up my tf.RaggedTensor.from_row_splits inside the served function, but I found it strange that the compatibility with ragged tensors wasn't full.
What do you think?

@stefanondisponibile This issue title and the initial description was misleading. Please create a new issue pointing to the issue that you are facinga and we can have a chat. Thanks!


ERR! Unable to execute

Running
projen new ovosskill --from https://github.com/asasasas/asasasas.git --retrofit
results in:
installing external module https://github.com/asasasas/asasasas.git...
Error: Command failed: npm install --save --save-dev -f --no-package-lock --prefix="/home/ovos/.local/share/mycroft/skills" https://github.com/aaa/asasasasas.git
npm WARN using --force Recommended protections disabled.
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/ovos/.npm/_cacache/tmp/git-clonejemoST/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/ovos/.npm/_cacache/tmp/git-clonejemoST/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

That isn't the correct command. Per the README, you should be running the following in your skill's directory:
projen new ovosskill --from "@mikejgray/ovos-skill-projen@latest" --retrofit


Update LAB_02_Implementing_security_solutions_hybrid_scenarios.md

Module/Lab: 00
Exercise: 00
Fixes # .
Changes proposed in this pull request:

Relevant Issues link

closed


DeleteVolume success/failure if volume is replicated and marked "Secondary"

NOTE: This is specific to Ceph-CSI, but looking at what the generic rule would be from a VolumeReplication perspective
Currently if a volume is demoted or marked Secondary from the VolumeReplication CR perspective, and a subsequent delete volume request is sent, it fails to delete the volume and returns errors to the k8s API server.
The Volume replication and remote volume is managed internal to the storage system and, as it currently stands, the garbage collection of a remote Secondary is also a storage system responsibility. Thus, the expectation is that, when a PV is deleted, but is internally Secondary on the system, the delete volume succeeds and the backing volume is finally garbage collected once the Primary instance is deleted.
If the above holds true, request that ceph-csi start checking image info/status and determine if it is mirrored and secondary to return required success for such images. I would assume ceph-csi still garbage collects the OMaps as that is not cleared when the remote image is deleted, and a DeleteVolume would be the last opportunity to do so on the local storage instance.

@ShyamsundarR I was thinking about the below items to keeps the things generic

When VR is created add finalizers for the PVC to avoid deleting the PVC if the replication is enabled
When VR is deleted send DisableReplication Request and remove finalizers  (revert back https://github.com/csi-addons/volume-replication-operator/pull/94)

If the storage does not allow disabling let the VR and PVC stay in Deleting state and Reconciliation will take care of removing it

If someone wants to remove the resources after doing failback from a cluster. They can simply send a request to delete the resources and let the Reconciler take care of deleting them.

With the above approach, I think most of the storage providers will take care of handling things internally
Now from the cephcsi side if the image is in the secondary state the image cannot be disabled and also it cannot be deleted. pre-req for Delete and Disable is that image needs to be in a primary state.

@ShyamsundarR I was thinking about the below items to keeps the things generic
* When VR is created add finalizers for the PVC to avoid deleting the PVC if the replication is enabled

* When VR is deleted send DisableReplication Request and remove finalizers  (revert back [replication: disable replication if its primary state #94](https://github.com/csi-addons/volume-replication-operator/pull/94))

Why will a Secondary image be disabled for replication? The primary controls the operation, right? So again, disable as secondary should be a no-op in this case.

  * If the storage does not allow disabling let the VR and PVC stay in Deleting state and Reconciliation will take care of removing it

* If someone wants to remove the resources after doing failback from a cluster. They can simply send a request to delete the resources and let the Reconciler take care of deleting them.

Which reconciler would act on the delete?

With the above approach, I think most of the storage providers will take care of handling things internally
Now from the cephcsi side if the image is in the secondary state the image cannot be disabled and also it cannot be deleted. pre-req for Delete and Disable is that image needs to be in a primary state.

This will not work for other orchestration services. For ceph-csi as a result VR cannot be deleted when image is secondary (as disable will fail), which will result in PVC not being deleted as VR finalizer would hold it in place. What is the recourse for the user to ensure these can be deleted?
The ground rules are that storage manages the life cycle of the volume on the Secondary. So deletion when secondary should succeed. We cannot let PVs and PVCs linger on the Secondary, as these need to be cleaned up for a future restore of the workload.

@ShyamsundarR I was thinking about the below items to keeps the things generic
* When VR is created add finalizers for the PVC to avoid deleting the PVC if the replication is enabled

* When VR is deleted send DisableReplication Request and remove finalizers  (revert back [replication: disable replication if its primary state #94](https://github.com/csi-addons/volume-replication-operator/pull/94))

Why will a Secondary image be disabled for replication? The primary controls the operation, right? So again, disable as secondary should be a no-op in this case.

Yes or else we will end up in other problems if both the

  * If the storage does not allow disabling let the VR and PVC stay in Deleting state and Reconciliation will take care of removing it

* If someone wants to remove the resources after doing failback from a cluster. They can simply send a request to delete the resources and let the Reconciler take care of deleting them.

Which reconciler would act on the delete?

PVC Reconciler and VR Reconciler

With the above approach, I think most of the storage providers will take care of handling things internally
Now from the cephcsi side if the image is in the secondary state the image cannot be disabled and also it cannot be deleted. pre-req for Delete and Disable is that image needs to be in a primary state.

This will not work for other orchestration services. For ceph-csi as a result VR cannot be deleted when image is secondary (as disable will fail), which will result in PVC not being deleted as VR finalizer would hold it in place. What is the recourse for the user to ensure these can be deleted?

If the images are secondary on both sites the VR, PVC deletion fails and as  the VR deletion fails, Now he will know the reason and he makes the VR state as primary and Delete  the VR and PVC

The ground rules are that storage manages the life cycle of the volume on the Secondary. So deletion when secondary should succeed. We cannot let PVs and PVCs linger on the Secondary, as these need to be cleaned up for a future restore of the workload.

This is something the orchestration services decide and to clean up the resources. As I mentioned above only the volume replication is stopped the image will get auto-deleted and the corresponding VR and PVC and PV will also get deleted

update from the meeting
Volume replication

Add finalizer to the PVC when VR is created and delete the finalizers when VR is deleted
Revert back https://github.com/csi-addons/volume-replication-operator/pull/94

CSI

Garbage collect the OMAP objects when PVC is deleted and the image is healthy secondary(skip image deletion)
Return success for DisableReplcation if the local image is healthy secondary (let the VR deletion on healthy primary cleanup the image on the remote site)

@ShyamsundarR anything missed?

update from the meeting
Volume replication
* Add finalizer to the PVC when VR is created and delete the finalizers when VR is deleted

* Revert back [replication: disable replication if its primary state #94](https://github.com/csi-addons/volume-replication-operator/pull/94)

CSI
* Garbage collect the OMAP objects when PVC is deleted and the image is healthy secondary(skip image deletion)

* Return success for DisableReplcation if the local image is healthy secondary (let the VR deletion on healthy primary cleanup the image on the remote site)

@ShyamsundarR anything missed?

Ack!
Behavior would be as follows:

VR deleted as Secondary would call disable to storage provider (ensuring storage provider is in Secondary state, i.e it should ensure on delete that storage provider state is the same as VR spec.state, so that storage provider can take the right action)

Storage provider decides to do nothing, as image is secondary and hence actions of disable are a No-OP

VR deletion triggers PVC finalizer deletion, and possibly PVC deletion, leading to PV deletion

Storage provider decides to garbage collect any artifacts, and possibly excluds garbage collecting the image as it is a "healthy" secondary and will be garbage collected by the primary instance

CSI PR is up for review. once its merged will close this one.

all the required PR's are merged!! closing it.


[Event Request] Codeunit 12 "Gen. Jnl.-Post Line" - Function "HandleBill" - New Event OnHandleBillOnBeforeModifyOldCustLedgEntry

Hello, we need the possibility to extend the Function "HandleBill" on "Gen. Jnl.-Post Line" Codeunit (12) as follows:
    [Scope('OnPrem')]
    procedure HandleBill(var CustLedgEntry: Record "Cust. Ledger Entry"; IsUnApply: Boolean)
    var
        OldCustLedgEntry2: Record "Cust. Ledger Entry";
        DtldCustLedgEntry: Record "Detailed Cust. Ledg. Entry";
        IsHandled: Boolean;
    begin
        IsHandled := false;
        OnBeforeHandleBill(CustLedgEntry, IsUnApply, IsHandled);
        if IsHandled then
            exit;

        OldCustLedgEntry2.Reset();
        OldCustLedgEntry2.SetCurrentKey("Document Type", "Document No.", "Document Occurrence", "Customer No.", Open);
        OldCustLedgEntry2.SetRange("Document Type", CustLedgEntry."Document Type to Close");
        OldCustLedgEntry2.SetRange("Document No.", CustLedgEntry."Document No. to Close");
        OldCustLedgEntry2.SetRange("Document Occurrence", CustLedgEntry."Document Occurrence to Close");
        OldCustLedgEntry2.SetRange("Customer No.", CustLedgEntry."Customer No.");
        OldCustLedgEntry2.SetRange(Open, true);
        if OldCustLedgEntry2.FindFirst() then begin
            if IsUnApply then begin
                if CustLedgEntry."Bank Receipt Issued" then begin
                    OnHandleBillOnBeforeUpdateCustLedgEntryBankRcpt(OldCustLedgEntry2, CustLedgEntry, IsUnApply);
                    UpdateCustLedgEntryBankRcpt(OldCustLedgEntry2, CustLedgEntry);
                    OnHandleBillOnAfterUpdateCustLedgEntryBankRcpt(OldCustLedgEntry2, CustLedgEntry, IsUnApply);
                    OldCustLedgEntry2."Allow Issue" := true;

                    //new-s
                    OnHandleBillOnBeforeModifyOldCustLedgEntry(OldCustLedgEntry2, CustLedgEntry, IsUnApply);
                    //new-e

                    OldCustLedgEntry2.Modify();
                    ClearCustLedgEntryBankRcpt(CustLedgEntry);
                    CustLedgEntry.Modify();
                    UpdDtldCustLedgEntryBankRcpt(OldCustLedgEntry2."Entry No.", true);
                end;
            end else begin
                OnHandleBillOnBeforeUpdateCustLedgEntryBankRcpt(OldCustLedgEntry2, CustLedgEntry, IsUnApply);
                UpdateCustLedgEntryBankRcpt(CustLedgEntry, OldCustLedgEntry2);
                OnHandleBillOnAfterUpdateCustLedgEntryBankRcpt(OldCustLedgEntry2, CustLedgEntry, IsUnApply);
                CustLedgEntry.Modify();
                ClearCustLedgEntryBankRcpt(OldCustLedgEntry2);
                OldCustLedgEntry2."Allow Issue" := false;

                //new-s
                OnHandleBillOnBeforeModifyOldCustLedgEntry(OldCustLedgEntry2, CustLedgEntry, IsUnApply);
                //new-e

                OldCustLedgEntry2.Modify();
                UpdDtldCustLedgEntryBankRcpt(OldCustLedgEntry2."Entry No.", false);
            end;
        end;

        OnAfterHandleBill(CustLedgEntry, IsUnApply);
    end;

    [IntegrationEvent(false, false)]
    local procedure OnHandleBillOnBeforeModifyOldCustLedgEntry(var OldCustLedgEntry2: Record "Cust. Ledger Entry"; CustLedgEntry: Record "Cust. Ledger Entry"; IsUnApply: Boolean)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11010.


The avatar rotates itself on the x axis on a computer with low resources

With the new version of Ecctrl, does anyone have problems with the avatar on a low-resource computer? The problem I have is that when I move the avatar, it starts to rotate in the X axe without control.
https://github.com/pmndrs/ecctrl/assets/51931450/bffbe116-7dd9-43dd-a56b-e4f8ff0ce4e4

I have had same issue.
But, I fixed this issue.
My discord username: metaverse1112

I have had same issue.
But, I fixed this issue.
My discord username: metaverse1112

Thank you, I already sent you the friend request

You could disable the autoBalance

You could disable the autoBalance

Thank you so much!.


Clicking "make changes" in Dev Drive Insights causes Dev Home to crash

Dev Home version
0.1501.547.0
Windows build number
No response
Other software
No response
Steps to reproduce the bug
Navigate to Dev Drive Insights
Have a package cache suggestion
Click "Make the change"
Click "Make changes" on the modal

Expected result
The caches should be moved and Dev Home shouldn't crash
Actual result
Dev Home hangs and crashes. My assumption is because the default auto-filled file path doesn't exist. This PR would be good to check out: #3287
Included System Information
No response
Included Extensions Information
No response

An update: Dev Home hung but came back to life and moved the caches:

@cinnamon-msft what is the size of the cache that was moved- I am thinking if this is a dupe of https://github.com/microsoft/devhome/issues/2925