Reference implementation of Estimator and Sampler Primitives

Summary
Continued https://github.com/Qiskit/qiskit-terra/pull/7651.
I am not sure why, but the CI was broken and I try to recreate it as a new PR.
Details and comments
Co-authored-by: Takashi Imamichi<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

143 of 160 (89.38%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 83.611%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/quantum_info/primitives/estimator.py
49
52
94.23%

qiskit/quantum_info/primitives/sampler.py
42
46
91.3%

qiskit/quantum_info/primitives/utils.py
48
58
82.76%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
52558

Relevant Lines:
62860

💛  - Coveralls

@jakelishman Thank you. I think the candidates are

qiskit.quantum_info.primitives
qiskit.primitives
qiskit.provider.fake_provider

Note that this PR does not depend on any providers and backend.
I think quantum_info is not only simple data structure. For example, quantum_info is often used like statevector_simulator with Statevector(QuantumCircuit). quantum_info also contains Statevector.expectation_value() to compute expectation values.
What do you think @ajavadia @levbishop ? I don't have a strong opinion on where to place it, so I will follow your opinion.
(Not related, but I also would like to have an immutable quantum circuit.)

It doesn't matter too much whether this PR depends on specific backends or providers

If it is the content of qiskit.provider, it is natural that it should be a subclass of Provider or Backend. I just wanted to emphasize the point that this PR has no relation to them. I agree that it is close to provider.
After this PR is merged, we will make Sampler and Estimator for Aer. At this time we might want to put it under qiskit.providers.aer.primitives. It seems like a good idea to create qiskit.providers.primitives.

I do agree with keeping qiskit.quantum_info to performing low-level quantum info tasks (matrix manipulations).
So previously we have defined qiskit.primitives and put BaseSampler and BaseEstimator there. The purpose of this particular PR is to provide a reference Qiskit implementation (i.e. a Sampler that given circuits produces quasi-probability distributions, and an Estimator that given circuits+observables produces expectation values). Then every provider is free to provide its own implementation in whatever way it wants.
To me, since we already have qiskit.primitives, it makes sense to put this reference implementation there too. That is the most discoverable place to me. Though qiskit.providers would be a runner-up choice for me. I agree it shouldn't be in qiskit.quantum_info

Slightly out of left-field: do these reference implementations need to be in Terra?  If we put them in Terra, people will use them as if they're simulators, and we don't want them to - I'd have thought we'd want them to use Aer's (to be written) versions for that, and fragmenting the simulator space is hard when we sometimes struggle for resources with only Aer.
If they're primarily meant to be illustrative, perhaps a full tutorial with documentation might be a good place?

I personally believe that when the number of qubits are not large, or by default, this reference implementation will be used. I think Estimator will be used in VQE in the future, but it will not be a good situation to provide only dependencies on Aer and other providers such as runtime. In other words, I think it will be used in VQE as much as BasicAer tests are used in VQE.

I'd also be curious to compare the performance of the quantum_info based expectation value simulation vs aer. After #7702 the gap between Statevector.expectation_value() and Aer's SaveExpectationValue should be smaller for cpu based simulations even for a larger number of qubits (well up to about 30-32, after that you'd need aer's mpi support or a different simulation method because quantum_info only can work with local memory).

Slightly out of left-field: do these reference implementations need to be in Terra? If we put them in Terra, people will use them as if they're simulators, and we don't want them to - I'd have thought we'd want them to use Aer's (to be written) versions for that, and fragmenting the simulator space is hard when we sometimes struggle for resources with only Aer. I'd vote to maintain a separation between "things that are code we expect you to use" and "this is example code for you to write your own" - the latter is more documentation than library code.
If they're primarily meant to be illustrative, perhaps a full tutorial with documentation might be a good place?

I think quantum_info is performant enough for moderate numbers of qubits. This implementation is quite light-weight (most of it is tests), so I don't think there is harm in having it in terra so it is "batteries-included".
I also think we should treat BasicAer as qiskit's reference implementation of a Backend (I still think it should use quantum_info under the hood). But then the structure will be Qiskit Terra defines a bunch of base classes, and ships with some basic concrete implementations of them: BaseProvider, BaseBackend, BaseSampler, BaseEstimator, and in the future BaseIntegrator and BaseDiscriminator.

Sure, if they're being written with the intent that they'll actually be run as code, I'm happy for them to be in Terra.

@ajavadia Thank you for your review. I updated and replied.

I made a patch to fix an issue of sampler. https://github.com/ikkoham/qiskit-terra/pull/48

We will update parameter names of __call__, e.g., circuits → circuit_indices.

We will update parameter names of call, e.g., circuits → circuit_indices.

Yes. That requires updating the base class as well, so I'll put that in a separate PR.


new term: metastatic

HI, is the concept of "metastatic" with in the scope of OGMS? Note, I can attend a future call to discuss these requests, if you prefer.
Thanks,
Randi

Use  http://purl.obolibrary.org/obo/PATO_0002098


Nvidia DPX2: run imagenet-console successfully ,but imagenet-camera gets errors

I can run imagenet-console successfully on DPX2.
when I use C920 webcam and run imagenet-camera, it comes up with the errors below:
I guess I've already loaded the model and get the class result(in the terminal log). however, I cannot open the display window and see the result.
./imagenet-camera
imagenet-camera
args (1):  0 [./imagenet-camera]
[gstreamer] initialized gstreamer, version <IP_ADDRESS>
[gstreamer] gstreamer decoder pipeline string:
v4l2src device=/dev/video0 ! video/x-raw, width=(int)1920, height=(int)1080, format=RGB ! videoconvert ! video/x-raw, format=RGB ! videoconvert !appsink name=mysink
imagenet-camera:  successfully initialized video device
width:  1920
height:  1080
depth:  24 (bpp)
imageNet -- loading classification network model from:
-- prototxt     networks/googlenet.prototxt
-- model        networks/bvlc_googlenet.caffemodel
-- class_labels networks/ilsvrc12_synset_words.txt
-- input_blob   'data'
-- output_blob  'prob'
-- batch_size   2
[GIE]  TensorRT version 3.0.2, build 3002
[GIE]  attempting to open cache file networks/bvlc_googlenet.caffemodel.2.tensorcache
[GIE]  loading network profile from cache... networks/bvlc_googlenet.caffemodel.2.tensorcache
nvrm_gpu: Bug 200215060 workaround enabled.
[GIE]  platform does not have FP16 support.
[GIE]  networks/bvlc_googlenet.caffemodel loaded
[GIE]  CUDA engine context initialized with 2 bindings
[GIE]  networks/bvlc_googlenet.caffemodel input  binding index:  0
[GIE]  networks/bvlc_googlenet.caffemodel input  dims (b=2 c=3 h=224 w=224) size=1204224
[cuda]  cudaAllocMapped 1204224 bytes, CPU 0x1053e0000 GPU 0x1053e0000
[GIE]  networks/bvlc_googlenet.caffemodel output 0 prob  binding index:  1
[GIE]  networks/bvlc_googlenet.caffemodel output 0 prob  dims (b=2 c=1000 h=1 w=1) size=8000
[cuda]  cudaAllocMapped 8000 bytes, CPU 0x1055e0000 GPU 0x1055e0000
networks/bvlc_googlenet.caffemodel initialized.
[GIE]  networks/bvlc_googlenet.caffemodel loaded
imageNet -- loaded 1000 class info entries
networks/bvlc_googlenet.caffemodel initialized.
default X screen 0:   3200 x 1080
[OpenGL]  glDisplay display window initialized
[OpenGL]   creating 1920x1080 texture
loaded image  fontmapA.png  (256 x<PHONE_NUMBER> bytes
[cuda]  cudaAllocMapped 2097152 bytes, CPU 0x1057e0000 GPU 0x1057e0000
[cuda]  cudaAllocMapped 8192 bytes, CPU 0x1055e2000 GPU 0x1055e2000
[gstreamer] gstreamer transitioning pipeline to GST_STATE_PLAYING
[gstreamer] gstreamer changed state from NULL to READY ==> mysink
[gstreamer] gstreamer changed state from NULL to READY ==> videoconvert1
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter1
[gstreamer] gstreamer changed state from NULL to READY ==> videoconvert0
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter0
[gstreamer] gstreamer changed state from NULL to READY ==> v4l2src0
[gstreamer] gstreamer changed state from NULL to READY ==> pipeline0
[gstreamer] gstreamer changed state from READY to PAUSED ==> videoconvert1
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter1
[gstreamer] gstreamer changed state from READY to PAUSED ==> videoconvert0
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter0
[gstreamer] gstreamer stream status CREATE ==> src
[gstreamer] gstreamer changed state from READY to PAUSED ==> v4l2src0
[gstreamer] gstreamer changed state from READY to PAUSED ==> pipeline0
[gstreamer] gstreamer stream status ENTER ==> src
[gstreamer] gstreamer msg new-clock ==> pipeline0
[gstreamer] gstreamer msg stream-start ==> pipeline0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> videoconvert1
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter1
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> videoconvert0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> v4l2src0
imagenet-camera:  camera open for streaming
[gstreamer] gstreamer decoder onPreroll
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x1059e0000 GPU 0x1059e0000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x105fd0000 GPU 0x105fd0000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x1065c0000 GPU 0x1065c0000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x106bb0000 GPU 0x106bb0000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x1071a0000 GPU 0x1071a0000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x107790000 GPU 0x107790000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x107d80000 GPU 0x107d80000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x108370000 GPU 0x108370000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x108960000 GPU 0x108960000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x108f50000 GPU 0x108f50000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x109540000 GPU 0x109540000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x109b30000 GPU 0x109b30000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x10a120000 GPU 0x10a120000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x10a710000 GPU 0x10a710000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x10ad00000 GPU 0x10ad00000
[cuda]  cudaAllocMapped 6220800 bytes, CPU 0x10b2f0000 GPU 0x10b2f0000
[cuda]   gstreamer camera -- allocated 16 ringbuffers, 6220800 bytes each
[gstreamer] gstreamer changed state from READY to PAUSED ==> mysink
[gstreamer] gstreamer msg async-done ==> pipeline0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> mysink
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> pipeline0
[cuda]   gstreamer camera -- allocated 16 RGBA ringbuffers
[gstreamer] gstreamer msg qos ==> v4l2src0
class 0526 - 0.107836  (desk)
class 0527 - 0.125700  (desktop computer)
class 0553 - 0.030763  (file, file cabinet, filing cabinet)
class 0620 - 0.016277  (laptop, laptop computer)
class 0632 - 0.011526  (loudspeaker, speaker, speaker unit, loudspeaker system, speaker system)
class 0651 - 0.056109  (microwave, microwave oven)
class 0664 - 0.244295  (monitor)
class 0673 - 0.048897  (mouse, computer mouse)
class 0713 - 0.010147  (photocopier)
class 0745 - 0.014054  (projector)
class 0760 - 0.019738  (refrigerator, icebox)
class 0782 - 0.066791  (screen, CRT screen)
class 0811 - 0.015403  (space heater)
class 0851 - 0.012936  (television, television system)
imagenet-camera:  24.42952% class #664 (monitor)
[cuda]   cudaGraphicsGLRegisterBuffer(&mInteropCUDA, mDMA, cudaGraphicsRegisterFlagsWriteDiscard)
[cuda]      operation not supported (error 71) (hex 0x47)
[cuda]      /home/nvidia/data/src/jetson-inference/util/display/glTexture.cpp:253
[cuda]   cudaGetLastError()
[cuda]      operation not supported (error 71) (hex 0x47)
[cuda]      /home/nvidia/data/src/jetson-inference/util/cuda/cudaRGB.cu:62
[cuda]   cudaRGBToRGBAf((uchar3*)input, (float4*)mRGBA[mLatestRGBA], mWidth, mHeight)
[cuda]      operation not supported (error 71) (hex 0x47)

Hi Patrick, it looks like the part that is failing is the CUDA->OpenGL interopability that copies the camera video from CUDA into OpenGL texture.  I don't have a DRIVE PX system so I am unable to debug, but if you take out the interop stuff and copy it through the CPU it should work..
-------- Original message --------
From: Patrick-Woo<EMAIL_ADDRESS>Date: 5/15/18 8:14 AM (GMT-05:00)
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [dusty-nv/jetson-inference] Nvidia DPX2: run imagenet-console successfully ,but imagenet-camera gets errors (#232)
I can run imagenet-console successfully on DPX2.
when I use C920 webcam and run imagenet-camera, it comes up with the errors below:
I guess I've already loaded the model and get the class result(in the terminal log). however, I cannot open the display window and see the result.
./imagenet-camera
imagenet-camera
args (1): 0 [./imagenet-camera]
[gstreamer] initialized gstreamer, version <IP_ADDRESS>
[gstreamer] gstreamer decoder pipeline string:
v4l2src device=/dev/video0 ! video/x-raw, width=(int)1920, height=(int)1080, format=RGB ! videoconvert ! video/x-raw, format=RGB ! videoconvert !appsink name=mysink
imagenet-camera: successfully initialized video device
width: 1920
height: 1080
depth: 24 (bpp)
imageNet -- loading classification network model from:
-- prototxt networks/googlenet.prototxt
-- model networks/bvlc_googlenet.caffemodel
-- class_labels networks/ilsvrc12_synset_words.txt
-- input_blob 'data'
-- output_blob 'prob'
-- batch_size 2
[GIE] TensorRT version 3.0.2, build 3002
[GIE] attempting to open cache file networks/bvlc_googlenet.caffemodel.2.tensorcache
[GIE] loading network profile from cache... networks/bvlc_googlenet.caffemodel.2.tensorcache
nvrm_gpu: Bug 200215060 workaround enabled.
[GIE] platform does not have FP16 support.
[GIE] networks/bvlc_googlenet.caffemodel loaded
[GIE] CUDA engine context initialized with 2 bindings
[GIE] networks/bvlc_googlenet.caffemodel input binding index: 0
[GIE] networks/bvlc_googlenet.caffemodel input dims (b=2 c=3 h=224 w=224) size=1204224
[cuda] cudaAllocMapped 1204224 bytes, CPU 0x1053e0000 GPU 0x1053e0000
[GIE] networks/bvlc_googlenet.caffemodel output 0 prob binding index: 1
[GIE] networks/bvlc_googlenet.caffemodel output 0 prob dims (b=2 c=1000 h=1 w=1) size=8000
[cuda] cudaAllocMapped 8000 bytes, CPU 0x1055e0000 GPU 0x1055e0000
networks/bvlc_googlenet.caffemodel initialized.
[GIE] networks/bvlc_googlenet.caffemodel loaded
imageNet -- loaded 1000 class info entries
networks/bvlc_googlenet.caffemodel initialized.
default X screen 0: 3200 x 1080
[OpenGL] glDisplay display window initialized
[OpenGL] creating 1920x1080 texture
loaded image fontmapA.png (256 x<PHONE_NUMBER> bytes
[cuda] cudaAllocMapped 2097152 bytes, CPU 0x1057e0000 GPU 0x1057e0000
[cuda] cudaAllocMapped 8192 bytes, CPU 0x1055e2000 GPU 0x1055e2000
[gstreamer] gstreamer transitioning pipeline to GST_STATE_PLAYING
[gstreamer] gstreamer changed state from NULL to READY ==> mysink
[gstreamer] gstreamer changed state from NULL to READY ==> videoconvert1
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter1
[gstreamer] gstreamer changed state from NULL to READY ==> videoconvert0
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter0
[gstreamer] gstreamer changed state from NULL to READY ==> v4l2src0
[gstreamer] gstreamer changed state from NULL to READY ==> pipeline0
[gstreamer] gstreamer changed state from READY to PAUSED ==> videoconvert1
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter1
[gstreamer] gstreamer changed state from READY to PAUSED ==> videoconvert0
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter0
[gstreamer] gstreamer stream status CREATE ==> src
[gstreamer] gstreamer changed state from READY to PAUSED ==> v4l2src0
[gstreamer] gstreamer changed state from READY to PAUSED ==> pipeline0
[gstreamer] gstreamer stream status ENTER ==> src
[gstreamer] gstreamer msg new-clock ==> pipeline0
[gstreamer] gstreamer msg stream-start ==> pipeline0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> videoconvert1
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter1
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> videoconvert0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> v4l2src0
imagenet-camera: camera open for streaming
[gstreamer] gstreamer decoder onPreroll
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x1059e0000 GPU 0x1059e0000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x105fd0000 GPU 0x105fd0000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x1065c0000 GPU 0x1065c0000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x106bb0000 GPU 0x106bb0000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x1071a0000 GPU 0x1071a0000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x107790000 GPU 0x107790000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x107d80000 GPU 0x107d80000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x108370000 GPU 0x108370000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x108960000 GPU 0x108960000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x108f50000 GPU 0x108f50000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x109540000 GPU 0x109540000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x109b30000 GPU 0x109b30000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x10a120000 GPU 0x10a120000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x10a710000 GPU 0x10a710000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x10ad00000 GPU 0x10ad00000
[cuda] cudaAllocMapped 6220800 bytes, CPU 0x10b2f0000 GPU 0x10b2f0000
[cuda] gstreamer camera -- allocated 16 ringbuffers, 6220800 bytes each
[gstreamer] gstreamer changed state from READY to PAUSED ==> mysink
[gstreamer] gstreamer msg async-done ==> pipeline0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> mysink
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> pipeline0
[cuda] gstreamer camera -- allocated 16 RGBA ringbuffers
[gstreamer] gstreamer msg qos ==> v4l2src0
class 0526 - 0.107836 (desk)
class 0527 - 0.125700 (desktop computer)
class 0553 - 0.030763 (file, file cabinet, filing cabinet)
class 0620 - 0.016277 (laptop, laptop computer)
class 0632 - 0.011526 (loudspeaker, speaker, speaker unit, loudspeaker system, speaker system)
class 0651 - 0.056109 (microwave, microwave oven)
class 0664 - 0.244295 (monitor)
class 0673 - 0.048897 (mouse, computer mouse)
class 0713 - 0.010147 (photocopier)
class 0745 - 0.014054 (projector)
class 0760 - 0.019738 (refrigerator, icebox)
class 0782 - 0.066791 (screen, CRT screen)
class 0811 - 0.015403 (space heater)
class 0851 - 0.012936 (television, television system)
imagenet-camera: 24.42952% class #664 (monitor)
[cuda] cudaGraphicsGLRegisterBuffer(&mInteropCUDA, mDMA, cudaGraphicsRegisterFlagsWriteDiscard)
[cuda] operation not supported (error 71) (hex 0x47)
[cuda] /home/nvidia/data/src/jetson-inference/util/display/glTexture.cpp:253
[cuda] cudaGetLastError()
[cuda] operation not supported (error 71) (hex 0x47)
[cuda] /home/nvidia/data/src/jetson-inference/util/cuda/cudaRGB.cu:62
[cuda] cudaRGBToRGBAf((uchar3*)input, (float4*)mRGBA[mLatestRGBA], mWidth, mHeight)
[cuda] operation not supported (error 71) (hex 0x47)

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/232, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOpDK-zYT3x3MgrNoBXoI5MWPvqcxibQks5tysZ4gaJpZM4T_bet.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

thank you for your prompt reply. could you please tell me how to use cpu to copy the video out? I am less familiar with cpp and only have experence with caffe modeling. thank you in advance.

You should be able to use the glTexture::UploadCPU() function to do it:   https://github.com/dusty-nv/jetson-inference/blob/e168b746d540fd739a6fa6ba652b5a5e8c6ffa08/util/display/glTexture.h#L53
Pass in the pointer of the buffer that you want to end up in the texture.
From: Patrick-Woo<EMAIL_ADDRESS>Sent: Tuesday, May 15, 2018 8:14 PM
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Dustin Franklin<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [dusty-nv/jetson-inference] Nvidia DPX2: run imagenet-console successfully ,but imagenet-camera gets errors (#232)
thank you for your prompt reply. could you please tell me how to use cpu to copy the video out? I am less familiar with cpp and only have experence with caffe modeling. thank you in advance.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/232#issuecomment-389354253, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOpDK7hySz1bA3Ppsjt2K2PjreIcxaiVks5ty287gaJpZM4T_bet.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

@dusty-nv
thank you for your reply and I am still confused about how to "Pass in the pointer of the buffer that you want to end up in the texture."
I could see there is a uploadCPU function. but where should I use this function?could you pls give me some sample code?
I have to show my leader PX2 can be used to do classification before the end of this week.  it is quit difficult for me(less cpp knowledge) to understand your source code in such a short time. So, if you could provide me with the code, I will be really really appreciated.

@dusty-nv please do me a faviour and present me some sample code. thank you in advance.

Comment out lines 197-207 of imagenet-camera.cpp:   https://github.com/dusty-nv/jetson-inference/blob/e168b746d540fd739a6fa6ba652b5a5e8c6ffa08/imagenet-camera/imagenet-camera.cpp#L197
and replace with the following:
/*void* tex_map = texture->MapCUDA();

if( tex_map != NULL )
{
	cudaMemcpy(tex_map, imgRGBA, texture->GetSize(), cudaMemcpyDeviceToDevice);
	texture->Unmap();
}*/

CUDA(cudaDeviceSynchronize());
texture->UploadCPU(imageRGBA);

The performance hit may not be very good from not using GL interop.  I am not sure why the interop isn't work on DRIVE PX, perhaps it is related to multiple GPUs.

@dusty-nv
Thank you for your time. I am really really appreciated.
However, after I replace the code you offered and compile it successfully, a new error message occurs when I run imagenet_camera in the bin folder.
source code:
CUDA(cudaDeviceSynchronize());
texture->UploadCPU(imageRGBA);   //imageRGBA should be imgRGBA I guess
error message:
[cuda]   gstreamer camera -- allocated 16 ringbuffers, 2764800 bytes each
[gstreamer] gstreamer changed state from READY to PAUSED ==> mysink
[gstreamer] gstreamer msg async-done ==> pipeline0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> mysink
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> pipeline0
[cuda]   gstreamer camera -- allocated 16 RGBA ringbuffers
class 0410 - 0.014961  (apiary, bee house)
class 0446 - 0.025046  (binder, ring-binder)
class 0478 - 0.047681  (carton)
class 0526 - 0.015736  (desk)
class 0527 - 0.027656  (desktop computer)
class 0549 - 0.040431  (envelope)
class 0553 - 0.024300  (file, file cabinet, filing cabinet)
class 0664 - 0.011072  (monitor)
class 0681 - 0.014861  (notebook, notebook computer)
class 0713 - 0.185375  (photocopier)
class 0742 - 0.252791  (printer)
class 0745 - 0.043518  (projector)
class 0760 - 0.048958  (refrigerator, icebox)
class 0782 - 0.018003  (screen, CRT screen)
class 0922 - 0.015056  (menu)
imagenet-camera:  25.27907% class #742 (printer)
Segmentation fault (core dumped)

@Patrick-Woo please change imagenet-camera.cpp:154 to reflect the following:
if( !camera->ConvertRGBA(imgCUDA, &imgRGBA, true) )
This will make sure that imgRGBA is accessible from CPU.  Sorry for forgetting about that detail earlier.

It really works.  Thank you so much.
without your help, I could not finish my job before the deadline.  Again, thank you very much.


[Feature] Add takeFirst()

takeEvery() and takeLatest() are already implemented, whereas takeFirst() is not.
fork(function* () {
  while (true) {
    const action = yield take(ACTION_TYPE)
    yield call(doSomethingAsync, action)
  }
})

I want to simplify it into:
(The signature concept is the same as takeEvery() or takeLatest())
takeFirst(ACTION_TYPE, function* (action) {
  yield call(doSomethingAsync, action)
})

I prefer builtin takeFirst() API to third-party ones.

However, I also think it should be limitted by user interface disabling rather than saga.
<button disabled={state.pending}>Submit</button>

We also need the takeFirst effect. Adding the logic on the component may be a good idea in some cases, yet it adds some complexity on components, which can be easily removed using this new effect.

@jpetitcolas
Its easily implemented on the user-side with implementation provided by @mpyw . I would suggest creating ur own set of saga helpers anyway, so you can add it to those and import them just like effects - just from the other module.
There are no plans at the moment to expand on the built-in 'helpers', as the focus is on something else and the time is rly limited. That being said - I would love to create more robust helpers library in the future.


Enhance progress monitoring accuracy

Some complex tasks (e.g. data transfer) produce hierarchy of progress tasks (series of nested beginTask/subTask/done).
We need to track this progress hierarchically (restore previous states after done).
Otherwise we loose progress info in many cases. Moreover it may disable possibility to cancel active job.

Can be tested in data transfer tasks

Data trasfer progress bar displays information correctly, but Background Tasks bar - no (no operations to display at this time.)

It is ok.
I think this ticket is more for devs.


Rename "Attack Indicators" plugin to "Attack Styles"

Motivated by a visitor on Discord who didn't realise this was the plugin he was looking for when he asked us to add it. The label needs to describe the plugin's scope more clearly.
This pr also renames code references for clarity, although not the keyName of course.

Can you rewrite the commit history to have the renaming in 1 commit and the toggle in second commit?

History rewritten, take a look when you're ready ☝


import optuna_fast_fanova error in googl colab

I am not sure if I install the package correctly.
I installed optuna-fast-fanova in google colab.
When I imported FanovaImportanceEvaluator,
there was an error message as below.

Environment: Google Colab (CPU).
Code:
!pip install optuna-fast-fanova

import optuna
from optuna_fast_fanova import FanovaImportanceEvaluator
def objective(trial):
x = trial.suggest_float("x", -10, 10)
y = trial.suggest_int("y", -10, 10)
return x ** 2 + y
if name == "main":
study = optuna.create_study()
study.optimize(objective, n_trials=1000)
importance = optuna.importance.get_param_importances(
study, evaluator=FanovaImportanceEvaluator()
)
print(importance)

Error message
/usr/lib/python3.7/importlib/_bootstrap.py:219: RuntimeWarning: sklearn.tree._criterion.Criterion size changed, may indicate binary incompatibility. Expected 328 from C header, got 352 from PyObject
return f(*args, **kwds)
ValueError                                Traceback (most recent call last)
 in ()
1 import optuna
----> 2 from optuna_fast_fanova import FanovaImportanceEvaluator
3
4
5 def objective(trial):
2 frames
/usr/local/lib/python3.7/dist-packages/optuna_fast_fanova/init.py in ()
----> 1 from optuna_fast_fanova._evaluator import FanovaImportanceEvaluator  # NOQA
2
3
4 version = "0.0.2"
/usr/local/lib/python3.7/dist-packages/optuna_fast_fanova/_evaluator.py in ()
18 from sklearn.ensemble import RandomForestRegressor
19
---> 20 from optuna_fast_fanova._fanova import FanovaTree
21
22
/usr/local/lib/python3.7/dist-packages/optuna_fast_fanova/_fanova.pyx in init optuna_fast_fanova._fanova()
ValueError: sklearn.tree._criterion.ClassificationCriterion size changed, may indicate binary incompatibility. Expected 1168 from C header, got 368 from PyObject

Thank you for using the library and reporting the bug!
As a temporary fix, maybe you can re-install optuna-fast-fanova like the following:
$ pip install --pre Cython
$ pip uninstall optuna-fast-fanova
$ pip install optuna-fast-fanova

@c-bata
Thank you for sharing the solution.
I have try it but there is an error as below.
!pip install --pre Cython
!pip uninstall optuna-fast-fanova
!pip install optuna-fast-fanova

import numpy
import optuna
import cython
import sklearn

print(f"numpy version:   {numpy.__version__}")
print(f"optuna version:  {optuna.__version__}")
print(f"cython version:  {cython.__version__}")
print(f"sklearn version: {sklearn.__version__}")

numpy version:   1.21.6
optuna version:  2.10.1
cython version:  0.29.30
sklearn version: 1.0.2
import optuna
from optuna_fast_fanova import FanovaImportanceEvaluator

def objective(trial):
    x = trial.suggest_float("x", -10, 10)
    y = trial.suggest_int("y", -10, 10)
    return x ** 2 + y

if __name__ == "__main__":
    study = optuna.create_study()
    study.optimize(objective, n_trials=1000)

    importance = optuna.importance.get_param_importances(
        study, evaluator=FanovaImportanceEvaluator()
    )
    print(importance)

/usr/lib/python3.7/importlib/_bootstrap.py:219: RuntimeWarning: sklearn.tree._criterion.Criterion size changed, may indicate binary incompatibility. Expected 328 from C header, got 352 from PyObject
return f(*args, **kwds)
ValueError                                Traceback (most recent call last)
 in ()
1 import optuna
----> 2 from optuna_fast_fanova import FanovaImportanceEvaluator
3
4
5 def objective(trial):
2 frames
/usr/local/lib/python3.7/dist-packages/optuna_fast_fanova/_fanova.pyx in init optuna_fast_fanova._fanova()
ValueError: sklearn.tree._criterion.ClassificationCriterion size changed, may indicate binary incompatibility. Expected 1168 from C header, got 368 from PyObject

Thank you for your quick reply!
optuna-fast-fanova requires Cython v3.0.0 alpha release, but seemingly the command pip install --pre Cython is skipped since there is  Cython==0.29.30. Could you try to execute following command?
!pip install Cython==3.0.0a10   # or pip install -U --pre Cython
!pip uninstall optuna-fast-fanova
!pip install optuna-fast-fanova


Docker image size of the compute node is very large

Steps to reproduce
Check size of docker image neondatabase/compute-node:latest
Expected result
A value much less than 500 MB
Actual result
500+ MB
Environment
Any

Stripping the useless  .debug_pubnames and .debug_pubtypes sections from the rust binaries would help a little, see https://github.com/neondatabase/neon/pull/2514. That PR doesn't change the docker build, but we could add a similar step in there.
$ ls -lh target/release/compute_ctl
-rwxr-xr-x 2 heikki heikki 114M Sep 30 22:52 target/release/compute_ctl
$ objcopy -R .debug_pubnames -R .debug_pubtypes -p target/release/compute_ctl
$ ls -lh target/release/compute_ctl
-rwxr-xr-x 2 heikki heikki 88M Sep 30 22:52 target/release/compute_ctl


Support specifying an upgrade function and parameters in upgradeProxy

Need a mechanism to be able to initialize state when upgrading so that it is part of the upgrade transaction.
Otherwise users would need to protect with some form of access control so they could do this in a separate transaction.
For example, adding a new state variable otherValue in version 2 and needing a safe way to initialize it on upgrade.
    function upgradeV2(uint256 initialValue) public {
        require (!_upgradeV2, "Box: already upgraded to V2");
        _upgradeV2 = true;

        otherValue = initialValue;
    }

Additionaly in docs we should provide an example of using an upgrade function and how to appropriately guard it so that it is only called once.
There have been two recent issues in the forum where community members have tried to protect an upgrade function with the initializer modifer.

https://forum.openzeppelin.com/t/error-upgrading-smart-contracts/3679
https://forum.openzeppelin.com/t/add-new-state-variable-to-base-contract-for-upgradeable-contracts/3502

Example of a guarded upgrade: https://forum.openzeppelin.com/t/error-upgrading-smart-contracts/3679/2?u=abcoathup

Hi, is this still the case with UUPSUpgradeable?


feat: multicard support for linux offscren render

Add support for multiple video cards through an environment variable FLO_CARD that can be set to the number of the card.
Example:
# Run with /dev/dri/card1
FLO_CARD=1 cargo run

This fixes a error on my machine, I don't have card0, it begins from card1. So, when I run some code without this changes it tries to get card0 by default and It doesn't work.

:+1: This seems like a sensible change to me.
I think an improvement would be to scan for devices if card0 is missing but the ability to override the default choice makes sense anyway if there are multiple options.
I didn't think this was something that could actually happen, and haven't been able to find out why yet which I think I need to know before trying to scan for the correct device file (Google has a whole bunch of people with a similar issue with other software but I can't see any explanation of how this happens)


How are the tests supposed to be run?

Description and motivation
There are currently no main() functions for the tests, which makes it difficult for beginners.
Unlike the examples where everything is just straightforward.
Proposed solution
Document the tests and how are they supposed to be used.
Alternatives and other information
Make a main.py file for the tests folder.

Hi @ZhenmingYu :
we use pytest for unit tests, which does not need any main.py file. We use a number of common developmental tools which can be installed with pip install -r requirements-dev.txt
To run the full test suite simply do (from the command line):
make pytest
To run individual test files, you can use, e.g.
pytest -v -s tests/test_presets.py
Individual tests can be run by giving the name, e.g.:
pytest -v -s tests/test_presets.py::PresetTest_TTv2IdealizedPreset::test_tile_preset
You can also look up the documentation of pytest

Reopening the issue, because we should indeed add this to the  documentation @kaoutar55

@maljoras  agree. I will add a section about examples in the public documentation.


[openssl] build failure

Package: openssl[core]:x64-windows -> 3.0.5#5
Host Environment

Host: x64-windows
Compiler: MSVC 19.32.31332.0
vcpkg-tool version: 2022-10-12-b586c2752f75bcc3f6a243749e9a0d94d0d93ccd
vcpkg-scripts version: 0321a8422 2022-10-16 (8 hours ago)

To Reproduce
vcpkg install paho-mqttpp3
Failure logs
-- Using cached openssl-openssl-openssl-3.0.5.tar.gz.
-- Cleaning sources at C:/ToolChain/vcpkg/buildtrees/openssl/src/nssl-3.0.5-df50913d32.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/ToolChain/vcpkg/downloads/openssl-openssl-openssl-3.0.5.tar.gz
-- Applying patch C:/ToolChain/vcpkg/ports/openssl/windows/flags.patch
-- Using source at C:/ToolChain/vcpkg/buildtrees/openssl/src/nssl-3.0.5-df50913d32.clean
-- Using cached strawberry-perl-<IP_ADDRESS>-32bit.zip.
-- Downloading https://www.nasm.us/pub/nasm/releasebuilds/2.15.05/win32/nasm-2.15.05-win32.zip;https://fossies.org/windows/misc/nasm-2.15.05-win32.zip -> nasm-2.15.05-win32.zip...
-- Downloading
https://download.qt.io/official_releases/jom/jom_1_1_3.zip;https://mirrors.ocf.berkeley.edu/qt/official_releases/jom/jom_1_1_3.zip -> jom_1_1_3.zip...
-- Getting CMake variables for x64-windows
-- Copying openssl release source files...
-- Copying openssl release source files... done
-- Configure x64-windows-rel
-- Configure x64-windows-rel done
-- Build x64-windows-rel
-- Build x64-windows-rel done
-- Copying openssl debug source files...

Skipped 2429 lines
...

crypto\chacha\chacha-x86_64.asm:3658: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3662: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3662: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3663: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3663: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3664: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3664: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3665: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3665: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3669: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3673: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3673: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3674: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3674: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3675: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3675: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3676: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3676: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3680: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3684: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3684: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3685: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3685: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3686: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3686: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3687: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3687: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3691: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3693: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3694: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3694: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3695: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3695: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3696: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3699: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3700: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3701: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3702: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3704: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3709: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3709: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3710: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3710: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3712: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3714: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3714: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3715: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3715: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3716: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3716: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3717: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3717: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3718: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3718: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3719: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3719: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3720: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3720: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3721: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3721: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3722: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3722: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3723: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3723: error: comma, colon, decorator or end of line expected after operand
crypto\chacha\chacha-x86_64.asm:3724: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3726: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3727: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3728: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3731: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3732: error: label `ChaCha20_8xvl' inconsistently redefined
crypto\chacha\chacha-x86_64.asm:3281: info: label `ChaCha20_8xvl' originally defined here
crypto\chacha\chacha-x86_64.asm:3732: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3736: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3748: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3749: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3751: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3752: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3754: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3758: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3760: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3764: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3766: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3767: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3768: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3769: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3770: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3771: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3772: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3773: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3774: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3775: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3776: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3777: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3779: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3780: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3781: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3782: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3783: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3784: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3786: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3793: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3794: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3795: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3796: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3797: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3798: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3799: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3800: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3801: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3802: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3803: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3817: error: label `se_handler' inconsistently redefined
crypto\chacha\chacha-x86_64.asm:3736: info: label `se_handler' originally defined here
crypto\chacha\chacha-x86_64.asm:3817: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3821: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3833: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3834: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3836: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3837: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3839: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3840: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3844: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3846: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3847: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3848: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3853: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3854: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\chacha\chacha-x86_64.asm:3860: error: label `simd_handler' inconsistently redefined
crypto\chacha\chacha-x86_64.asm:3821: info: label `simd_handler' originally defined here
crypto\chacha\chacha-x86_64.asm:3860: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3862: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3901: error: label `simd_handler.pdata' inconsistently redefined
crypto\chacha\chacha-x86_64.asm:3863: info: label `simd_handler.pdata' originally defined here
crypto\chacha\chacha-x86_64.asm:3901: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3904: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3908: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3914: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3920: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3925: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3930: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3935: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3941: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3947: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3953: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3959: error: parser: instruction expected
crypto\chacha\chacha-x86_64.asm:3960: warning: label alone on a line without a colon might be in error [-w+label-orphan]
jom: C:\ToolChain\vcpkg\buildtrees\openssl\x64-windows-dbg\Makefile [crypto\chacha\libcrypto-shlib-chacha-x86_64.obj] Error 1
jom: C:\ToolChain\vcpkg\buildtrees\openssl\x64-windows-dbg\makefile [build_libs] Error 2

Additional context

Thanks,
Well, I run into this issue on my office computer, it works pretty fine on my personal computer. It's hard to say whether it's caused by firewall or anti-virus or something else or not, cause i have no idea how to locate the problem. I checked the logs in the "buildtree" folder and try to install with --debug option,but it's all just about some compilation error of openssl. Is there any more debug utility or install options i can take to analyse?

THIS works for me.


Update general-cs-quiz.ts#4

Summary of changes
Computational Thinking, an important part of Basic CS theory is necessary, and thus added to the repo.
Checklist

[X] I have read and followed the contribution guidelines.
[X] I have read through the Code of Conduct and agree to abide by the rules.
[X] This PR is for one of the available issues and is not a PR for an issue already assigned to someone else.
[X] My PR title has a short descriptive name so the maintainers can get an idea of what the PR is about.
[X] I have provided a summary of my changes.

closing due to inactivity


Delete/disable profile heading?

How can we either remove or delete the profiles header:
" A Man of 52 years, from United States, York Rhode island"
" A Woman of 33 years, from United States, Witchita Kansas"

Please delete this line _protected/app/system/modules/user/controllers/ProfileController.php, L81-L82 -> https://github.com/pH7Software/pH7-Social-Dating-CMS/blob/90b7ad361287ceb00b0d90d8c0c3a13b041a2048/_protected/app/system/modules/user/controllers/ProfileController.php#L81-L82
Or this one _protected/app/system/modules/cool-profile-page/controllers/MainController.php, L62-L63 -> https://github.com/pH7Software/pH7-Social-Dating-CMS/blob/90b7ad361287ceb00b0d90d8c0c3a13b041a2048/_protected/app/system/modules/cool-profile-page/controllers/MainController.php#L62-L63 if the "Dating-Style Profile Page" module is enabled.


Feature/back 13 folders api and notes api fixes

This is not the full update!
There is still some functionality to add, and it will be added soon in next PR

Is it only my problem, that the tests don't pass


Move to using bun's builtin soft_delete mechanism

ref: https://bun.uptrace.dev/guide/soft-deletes.html#introduction

This will require some kind of migration path.

After much deliberation during our community call ( dated 26th March, ref: minutes ), this comes as a tech debt item which does not really add much value to users, it's decided to use bun's soft_delete mechanism in upcoming features however we do not plan to refactor the existing code in the near future.


fugue support reset secret requires get, put, and delete bucket policy

What

add s3:GetBucketPolicy
add s3:PutBucketPolicy

Why
resetting a secret requires the ability to unlock a buckets policy.

👍


Add MindTagger evaluation utilities

Should we focus on the hold out set? What are the important metrics to users wanting to refine their DSRs?

I think this is pretty important -- I'm finishing a (pretty rough) Corpus class in dd-biolib so that we can load some benchmark datasets for the entity bio-hackathon. It would be great to see some nicer feedback than just P/R/F1 on the dev set, though I'm not certain what that feedback should look like.


Connecting...

I cannot seem to establish a connection between the program and Google. After entering in my credentials, I am in a perpetual connecting phase with no option to reenter account information or otherwise.
OS: Windows 10 N
YakYak v14.4.4 and v1.4.3
What I have tried:

Uninstall and reinstall with different versions
Disabled all firewalls
Installed on my macbook (macOS sierra) with same results, except I can access navigation for the program to logout and try the connection again or a different account (did both which yielded the same results)

Any and all help would be greatly appreciated!

check this issue
https://github.com/yakyak/yakyak/issues/640

I'm having the same problem.  Just installed the newest version two days ago, and it looked as if it was going to work.  Now it just hangs at "Connecting" with the three animated dots below it.
Come on, folks.  Can't we get a WORKING Hangouts client for Linux?  You know, something reliable, because I need this for my work.

You need to have at least one chat in hangouts before connecting. Go to the web ui and start a chat with anyone and then it should connect.

@roncemer does @zaphod777 tip solves the problem?
if not can you press Ctrl + Alt + I and check if there are any exceptions on the console tab

Me too. Just install this in my (K)ubuntu laptop via snap. And get "Connecting..." forever.
Nothing in devtools console.


Video has a black bar at the bottom when "config.onlySquareImagesFromCamera = false"

Describe the bug
Video has a black bar at the bottom when "config.onlySquareImagesFromCamera = false"
To Reproduce
Steps to reproduce the behavior:

set config.onlySquareImagesFromCamera = false
Take a video with the camera
On the trim video/choose cover page, the video has a black bar attached below it
The black bar does not disappear

Expected behavior
The video should play perfectly fine without a black bar below it.
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Device: [e.g. iPhone8]
OS: [e.g. iOS13.0]

Installation Type

Cocoapods

Additional context
Add any other context about the problem here.

@BballerKim facing same issue, any update on it?

@VishalSharma91 I was unable to find a solution, were you? @NikKovIos any advice by any chance

I have the same problem. Should we wait for an update?

Fixed 46abe699ec11a7d32898f3cddb64d98fee32e8cf


Some fixes for parallel configuration when project isolation is enabled

Fixes #?
Context
In particular, add some thread safety to parts of the build script execution infrastructure.
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Add license information to pom xml

Please add license info into pom.xml it will fix https://github.com/jk1/Gradle-License-Report/issues/322

to which pom? I can see it here

Sorry, my bad, did not notice that one.


Compute metadata based on viz to reduce properties

The DataFrame is computed on demand, without having to precompute features
from the original data. This removes the clone of the data. It also allows using the
cartodb_id from original data.
This fixes #317.

@Jesus89, using negative cartodb_id was on purpose. How was that affecting the tests?

OK. If this is a feature we should update the interactivity tests. Let me do it

I updated this PR with @davidmanzanares' one.

:+1:


#941 - added ABS deep linking in the endpoints expolorer

resolves #941

Pull Request Test Coverage Report for Build 1175

18 of 20 (90.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.8%) to 54.23%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/app/client/src/data/sagas/endpointSagas.ts
11
13
84.62%

Totals

Change from base Build 1171:
0.8%

Covered Lines:
4267

Relevant Lines:
7103

💛  - Coveralls


[DC-831] Update Operational PII Field CR to New Base Class & Rules Dir

Original work done on branch bg/dc_831

It looks good to me. Thanks for the updates, Brenda!


Version 0.3.5 can't get encrypted data, but version 0.3.2 can

Reproduce on Android, untest on iOS:

Clone my example, make sure react-native-mmkv-storage version is 0.3.5
Run project
Enter username and password, check Save data
Press Log in
If you see Login success, kill app
Open app and expect username and password in TextInputs but no
Install version 0.3.2 and run project => Username and password show up

First of all thank you for this package.
Still impossible to read data encrypted with version 0.3.7 or 0.3.5 (work with 0.3.2).
It works only (with version 0.3.7) if I downgrade mmkv-static version to 1.1.2 (instead of 1.2.2)

@LeDevFou Maybe it got broken again, I had fixed it in v0.3.6 I will see what is happening. Its only not working on android or ios too?

Sorry I can't test with IOS.
I tested on a real device and it gives the same result.
This seems to come from an error with the 1.2.X version of mmkv.  Whatever the version (0.3.2 ... 0.3.7) it works with version 1.1.X but none of them works with 1.2.X.

@ammarahm-ed
After some testing I noticed that the problem comes from with the boolean values only.
The problem seems come from MMKV which does not store correctly boolean.
https://github.com/Tencent/MMKV/issues/529
During my tests I noticed a small problem in the file "IDStore.java".
        HashMap<String, Object> child = new HashMap<>();
        child.put("ID", ID);
        child.put("encrypted", encrypted);
-       child.put(alias, alias); // <= quotes are missing
+       child.put("alias", alias);
        IdStore.put(ID, child);

@LeDevFou Seems like it has been fixed in the dev branch and nice catch! i just fixed the alias problem, you were right. alias value was passed as the key, that can be another reason for being unable to find the encrypted storage.


Fix content tests; run tests via GitHub Actions

The PR fixes the test that checks code examples in the _content/tour directory and adds GitHub Actions workflow to run tests on each PR or push to the main branch.
Now, running go test -v ./... works flawlessly.
I have divided the PR into separate logical commits to facilitate review. Each commit corresponds to one logical change.
Changes:

Fixed TestContent to work with //go:build build constraint. It's worth mentioning that the tour from Go team's uses // +build comments, but this gotour uses //go:build (introduced here #45). Thus, TestContent has been adapted to work with //go:build.
Moved content_test.go to the root because go test skips the _content folder when detecting tests.
Renamed TestContent to TestContentTour.
Retained only one content_test.go that checks examples for all languages.
Added the missing OMIT to all code snippets.
Added the build constraint nobuild to code snippets that cannot be compiled via go build.
Added the build constraint norun to code snippets that cannot be executed. Note that we cannot use no-run (with a hyphen) as a build constraint name.

We would need to review this together before I can accept it. I don't run any tests since the code was taken from the Go team and I don't update it. I just check the site and publish.
I'm not adverse but we will need to jump on a call.

@ardan-bkennedy I updated the PR's description with extended explanation. Hope this clarifies changes a bit.

It's too big and I want to review this with you if I'm going to accept it. I'll ping you during the week

Give me a PR to the bill/testing branch please.

Give me a PR to the bill/testing branch please.

Changed base branch to the bill/testing.

Hello @ardan-bkennedy,
I noticed that you merged into the bill/testing branch. Is there a chance this PR will be merged into the main branch?

I could not get the tests to work. When I run go test ./... everything hangs. I have not had the time to review why.

The tests are not hanging; they are just slow. I changed the test to target only the eng directory (see the PR #262), and it took 50 seconds to complete:
❯ go test ./...
?       github.com/ardanlabs/gotour/cmd/markdown-to-site        [no test files]
?       github.com/ardanlabs/gotour/cmd/tour    [no test files]
?       github.com/ardanlabs/gotour/internal/tour       [no test files]
?       github.com/ardanlabs/gotour/internal/socket     [no test files]
ok      github.com/ardanlabs/gotour     49.456s
ok      github.com/ardanlabs/gotour/internal/webtest    (cached)


[TuyaLan] Failed to discover [NAME] (ID) in time but will keep looking.

I could get the ID, KEY, setup properly but I can't get work properly. I shared my logs:
[2020-1-19 23:15:19] [TuyaLan] Initializing TuyaLan platform...
[2020-1-19 23:15:22] [TuyaLan] Starting discovery...
[2020-1-19 23:15:22] Homebridge is running on port 51826.
[TuyaAccessory] Discovery started.
[2020-1-19 23:16:22] [TuyaLan] Failed to discover [NAME] (ID) in time but will keep looking.

Update your homebridge-tuya-lan to 1.5.0-rc.12. To do this, run npm i -g<EMAIL_ADDRESS>

Update your homebridge-tuya-lan to 1.5.0-rc.12. To do this, run npm i -g<EMAIL_ADDRESS><

Attempting to run that update yields:

npm ERR! code ENOLOCAL
npm ERR! Could not install from<EMAIL_ADDRESS>as it does not contain a package.json
<

My mistake, run the command again but remove "AMoo-Miki/" from it so:
npm i -g<EMAIL_ADDRESS>

Confirmed. Was receiving the same error but tried @tom-23 's recommended update and it now works. Issue can be closed.


chore: update deps

Updating deps to avoid merging in dependabot PRs one by one and save CI cycles

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-11-10T21:31:42.962+0000

Duration: 8 min 45 sec

Steps errors
Expand to view the steps failures

run tests

Took 1 min 1 sec . View more details here
Description: .ci/scripts/run-test-in-docker.sh

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test all : Re-trigger the build for all the stages.

There are more PRs open regarding outdated deps. I will close this PR and address deps update altogether after fixing the CI issue too.


Update Document

Add the method update to the repository which will call Firestore's update method.

Please assign this issue to me
I have added the Firestore's update method and just going to create a PR

Alright @maddy020 , thanks!
If you need help with something, let me know
By the way, before you commit the code in your local repository, make sure you have husky set up:
npm install

npm run prepare

I have already created a PR  and it has merged


[0.12] Descriptions as strings

Based on #238 (The first two commits)
ref: graphql/graphql-js#927
BREAKING CHANGE: This does not parse descriptions from comments by default anymore and the value of description in Nodes changed from string to StringValueNode

Coverage decreased (-0.08%) to 92.765% when pulling 88e2ed4ea0e66651b1e2e6343e29be16cb2f6c97 on danez:012-descriptions into 94525c00252696b47673db1ca56fe0436c5949be on webonyx:master.


docs(autoware_multi_object_tracker): update input_channels schema with default values

Description
add missing default values to fix https://autowarefoundation.github.io/autoware.universe/main/perception/autoware_multi_object_tracker/
Related links

Link
https://github.com/autowarefoundation/autoware.universe/pull/8179

How was this PR tested?
Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

@technolojin
Hi Lee-san, could you add the word in the dictionary :)
Warning: Unknown word (pointpainitng)
perception/autoware_multi_object_tracker/schema/input_channels.schema.json:114:24 Unknown word (pointpainitng)
perception/autoware_multi_object_tracker/schema/input_channels.schema.json:188:24 Unknown word (pointpainitng)
Warning: Unknown word (pointpainitng)

@vividf
Thank you for your remind. https://github.com/autowarefoundation/autoware.universe/pull/8515


Improve ICS test bootstrapping

Closes: #XXX
Description

This PR updates the latest Gaia used in the CI, from v11 to v12.
It also fixes an issue when bootstrapping a consumer chain by explicitly setting the gas used when submitting the governance proposal.
It also improves the setup by querying the proposal in order to verify if it is in voting period before voting, and if the proposal passed before starting the consumer chain.

PR author checklist:

[ ] Added changelog entry, using unclog.
[x] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Amazing, thanks so much 🎉


Firewalld

Hi,
After some test it seem that firewalld don't block IP from the IPSET if you add the IP with the ipset command....
This guy need that you add your entry with the firewall-cmd or he will just ignore everything...
Atm I have build my own bouncer to manage that, but it could be interesting to add firewalld support in the bouncer, and then just add firewalld in the mode option...
This are all the command that I use to manage my blocklist with firewalld, you will need those to adapt the bouncer :
On start :
#remove ipset from firewalld
/bin/firewall-cmd --permanent --zone=drop --remove-source=ipset:crowdsec-blacklists
#remove ipset
/bin/firewall-cmd --permanent --delete-ipset=crowdsec-blacklists
#reload config
/bin/firewall-cmd --reload

#recreate ipset
/bin/firewall-cmd --permanent --new-ipset=crowdsec-blacklists --type=hash:net
#add the ipset to the drop zone on firewalld
/bin/firewall-cmd  --permanent --zone=drop --add-source=ipset:crowdsec-blacklists
#reload config
/bin/firewall-cmd --reload

After that get the full banlist with startup=true on LAPI
Keep only the add, and remove all duplicate entry.
Then 2 solutions, I have made the choice to write the banlist to a tmp file, and then import that list with that command
/bin/firewall-cmd --ipset=crowdsec-blacklists --add-entries-from-file=/tmp/banlist
#save config
/bin/firewall-cmd --runtime-to-permanent

or you can just add each entry 1 by 1 :
firewall-cmd --ipset=crowdsec-blacklists --add-entry=<ip>
#save config
/bin/firewall-cmd --runtime-to-permanent

After that on each check, just get the partial banlist with startup=false on LAPI
Remove duplicate entry, and here I have made the choice to write the add / del entry to 2 tmp files, and import them.
#add
/bin/firewall-cmd --ipset=crowdsec-blacklists --add-entries-from-file=/tmp/banlist_add
#del
/bin/firewall-cmd --ipset=crowdsec-blacklists --remove-entries-from-file=/tmp/banlist_del
#save
/bin/firewall-cmd --runtime-to-permanent

But you can do the same by adding / removing each ip one by one
#add
firewall-cmd --ipset=crowdsec-blacklists --add-entry=<ip>
#del
firewall-cmd --ipset=crowdsec-blacklists --remove-entry=<ip>
#save the configuration after that
/bin/firewall-cmd --runtime-to-permanent

On stop you can remove the ipset
#remove ipset from firewalld
/bin/firewall-cmd --permanent --zone=drop --remove-source=ipset:crowdsec-blacklists
#remove ipset
/bin/firewall-cmd --permanent --delete-ipset=crowdsec-blacklists
#reload config
/bin/firewall-cmd --reload

Note, it seem that firewalld don't like timeout. This is why on my side I clear everything on start/stop, and once / 24H I do a full reset with startup=true and remove / add the ipset...

For information, after multiple month of using my custom bouncer to use this setup I have to point out some issue.
First, when you add new decisions with /bin/firewall-cmd --ipset=crowdsec-blacklists --add-entries-from-file=/tmp/banlist_add then firewall will clear the whole set during the time he is importing the new IP.
This mean for 1 or 2s everything is open... Not nice... Acceptable when you run your bouncer once every 5min, but not if you run it every 20s...
Another point, the memory usage can grow very very fast, in this setup for firewalld.
It seem that this is fixed in the most recent firewalld version, but on debian11 it's not the case atm.
Debian suggest to move to nftables / firewalld here but honestly it's not a good solution atm...
And nftables have other issue (if you want to use the crowdsec-fw-bouncer-nftable), like if you want to ban a whole netrange, this fail if you have already some IP from this netrange in the set...
In the end, it seem that the good old iptables / ipset / shorewall work far better for me...


Update Set-OrganizationConfig.md

Adding the flag for AuditDisabled & description.

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/organization/Set-OrganizationConfig.md
:x:Error

Details

:x:Error

Details

sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCrawledProperty.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppInstance.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchLinksDatabase.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSpelltuning.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPAppInstance.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/Test-SPProjectWebInstance.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/Stop-SPDistributedCacheServiceInstance.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/Update-SPAppInstance.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/Add-SPAppDeniedEndpoint.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/Add-FASTSearchSpelltuning.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/sharepoint-server.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSpelltuningStatus.md
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md
:warning:Warning

Details

skype/skype-ps/skype/Remove-CsPlatformServiceSettings.md
:warning:Warning

Details

skype/skype-ps/skype/Get-CsAdditionalInternalDomain.md
:warning:Warning

Details

skype/skype-ps/skype/New-CsAdditionalInternalDomain.md
:warning:Warning

Details

skype/skype-ps/skype/Remove-CsAdditionalInternalDomain.md
:warning:Warning

Details

skype/skype-ps/skype/Get-CsPlatformServiceSettings.md
:warning:Warning

Details

skype/skype-ps/skype/Get-CsHybridApplicationEndpoint.md
:warning:Warning

Details

skype/skype-ps/skype/Remove-CsHybridApplicationEndpoint.md
:warning:Warning

Details

skype/skype-ps/skype/Set-CsPlatformServiceSettings.md
:warning:Warning

Details

skype/skype-ps/skype/Set-CsHybridApplicationEndpoint.md
:warning:Warning

Details

skype/skype-ps/skype/New-CsHybridApplicationEndpoint.md
:warning:Warning

Details

skype/skype-ps/skype/New-CsPlatformServiceSettings.md
:warning:Warning

Details

exchange/exchange-ps/exchange/organization/Set-OrganizationConfig.md

[Error] Unable to load file: exchange-ps/exchange/organization/Set-OrganizationConfig.md via processor: AzureCliDocumentProcessor: :2069:(1588) '```yaml
Type: $true | $false
Parameter (All)
Al...'
Invalid yaml: expected simple key-value pairs

[Error] Markdown.MAML.Transformer.HelpSchemaException: :2069:(1588) '```yaml
Type: $true | $false
Parameter (All)
Al...'
Invalid yaml: expected simple key-value pairs
at Microsoft.DocAsCode.Build.Engine.SingleDocumentBuilder.GetInnerContexts(DocumentBuildParameters parameters, IEnumerable1 processors, TemplateProcessor templateProcessor, IHostServiceCreator creator) at Microsoft.DocAsCode.Build.Engine.SingleDocumentBuilder.BuildCore(DocumentBuildParameters parameters) at Microsoft.DocAsCode.Build.Engine.DocumentBuilder.BuildCore(DocumentBuildParameters parameter, IMarkdownServiceProvider markdownServiceProvider, BuildInfo currentBuildInfo, BuildInfo lastBuildInfo) at Microsoft.DocAsCode.Build.Engine.DocumentBuilder.Build(IList1 parameters, String outputDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument(BuildJsonConfig config, TemplateManager templateManager, String baseDirectory, String outputDirectory, String pluginDirectory, String templateDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument()

sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataCrawledProperty.md

Line 140: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Set.FASTSearchMetadataCrawledProperty.md).

sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppInstance.md

Line 179: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Restart-SPAppInstanceJobs.md).

sharepoint/sharepoint-ps/sharepoint-server/New-SPEnterpriseSearchLinksDatabase.md

Line 214: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Repartition-SPEnterpriseSearchLinksDatabases.md).

sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchSpelltuning.md

Line 50: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Reset-FASTSearchSpelltuning.md).

sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPAppInstance.md

Line 125: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Restart-SPAppInstanceJobs.md).

sharepoint/sharepoint-ps/sharepoint-server/Test-SPProjectWebInstance.md

Line 103: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Mount-SPProjectWebInstance.md).

sharepoint/sharepoint-ps/sharepoint-server/Stop-SPDistributedCacheServiceInstance.md

Line 85: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Remove-SPDistributedCacheServiceInstanceOnLocalServer.md).
Line 87: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Add-SPDistributedCacheServiceInstanceOnLocalServer.md).

sharepoint/sharepoint-ps/sharepoint-server/Update-SPAppInstance.md

Line 142: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Restart-SPAppInstanceJobs.md).

sharepoint/sharepoint-ps/sharepoint-server/Add-SPAppDeniedEndpoint.md

Line 124: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Clear-SPAppDeniedEndpoints.md).
Line 126: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Get-SPAppDeniedEndpoints.md).

sharepoint/sharepoint-ps/sharepoint-server/Add-FASTSearchSpelltuning.md

Line 50: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Reset-FASTSearchSpelltuning.md).

sharepoint/sharepoint-ps/sharepoint-server/sharepoint-server.md

Line 151: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/ConvertTo-SPOMigrationEncryptedPackage.md).
Line 154: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/ConvertTo-SPOMigrationTargetedPackage.md).

sharepoint/sharepoint-ps/sharepoint-server/Get-FASTSearchSpelltuningStatus.md

Line 44: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-server/Reset-FASTSearchSpelltuning.md).

sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md

Line 58: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-online/Get-SPO365LinkSettings.md).
Line 292: [Warning] Invalid file link:(~/sharepoint-ps/sharepoint-online/Set-SPO365LinkSettings.md).

skype/skype-ps/skype/Remove-CsPlatformServiceSettings.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/Get-CsAdditionalInternalDomain.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/New-CsAdditionalInternalDomain.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/Remove-CsAdditionalInternalDomain.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/Get-CsPlatformServiceSettings.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/Get-CsHybridApplicationEndpoint.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/Remove-CsHybridApplicationEndpoint.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/Set-CsPlatformServiceSettings.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/Set-CsHybridApplicationEndpoint.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/New-CsHybridApplicationEndpoint.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

skype/skype-ps/skype/New-CsPlatformServiceSettings.md

Line 1: [Warning] Invalid yaml header: (Line: 2, Col: 11, Idx: 67) - (Line: 2, Col: 11, Idx: 67): Mapping values are not allowed in this context.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Support for @supports syntax

The @supports syntax used in Bootstrap 4 is not supported.
When trying to compile it an exception is thrown:
Stack trace:
line 113 of /lib/php-css-parser/Parser.php: Sabberworm\CSS\Parsing\SourceException thrown
line 197 of /lib/php-css-parser/Parser.php: call to Sabberworm\CSS\Parser->parseList()
line 119 of /lib/php-css-parser/Parser.php: call to Sabberworm\CSS\Parser->parseAtRule()
line 96 of /lib/php-css-parser/Parser.php: call to Sabberworm\CSS\Parser->parseListItem()
line 87 of /lib/php-css-parser/Parser.php: call to Sabberworm\CSS\Parser->parseList()
line 82 of /lib/php-css-parser/Parser.php: call to Sabberworm\CSS\Parser->parseDocument()
line 61 of /testcss.php: call to Sabberworm\CSS\Parser->parse()
Exception - Unexpected end of document [line no: 23]

Seems to be working for me. Can you provide a more elaborated example?

@raxbg Maybe you’re parsing in lenient mode? @supports is currently unsupported so this issue is valid IMHO.

Yes, I will probably work on this some time soon because I will need it 😄

Yep, I find the issue is in strict mode only.  In lenient mode, @media and @supports are parsed correctly.  In strict mode, an exception is thrown for either (and also any at-rule with nested rules, such as @keyframes and @document).
E.g. with the current code base the following test added to AtRuleBlockListTest will fail:
    /**
     * @test
     *
     * @param string $css
     *
     * @dataProvider mediaRuleDataProvider
     */
    public function parsesMediaRuleInStrictMode($css)
    {
        (new Parser($css, Settings::create()->beStrict()))->parse();

        self::assertTrue(true); // no exception was thrown
    }

The failure is:
Sabberworm\CSS\Parsing\UnexpectedTokenException: Identifier expected. Got “}” [line no: 1]

Perhaps it is simply that the final closing } isn't being consumed - it is clearly triggering the completion of the at-rule, otherwise subsequent rules would end up inside the at-rule (which they don't) - so the parser ends up seeing it again, but in lenient mode silently ignores this double-vision.
See also #75.
Note that @font-face is fine, but that doesn't have nested rules, just property-value pairs.


[Documentation] Section 6.18 Uses "PDF" in place of "PSD".

I think there's a minor typo in the documentation that accidentally interchanges "PSD" with "PDF".
OpenImageIO 1.8 Programmer Documentation
25 Mar 2017
Page 107

Section 6.18 PSD
PSD is the file format used for storing Adobe PhotoShop images. OpenImageIO provides limited read abilities for PDF, but not currently the ability to write PSD files.

Note the use of the acronym "PDF" in that passage. Unless I'm mistaken, I think it should be "PSD" as there is no other mention of "PDF" file types within the context of Section 6.18.

Thanks for catching! I will fix.


Cleanup router

This includes:
Trying to get everything into one callback method
Naming controller methods correctly
correct createUser and Stamp methods/urls
Update javascript file if above changes
This will break the controller API, so version will need to go up accordingly.

Once this is done, it will leave the template for the default router file.


Adding cached image service to Add Tile layer not working

On adding cached image service to Add Tile layer not working, get the following error:
"Invalid Tiled Map Service URL"
tried to add a cached image service layer (all layers in WAB 1.1 in local state plane).
Cached image service is in state plane with custom tiling scheme

Robert replied in geonet that image services are not supported.


Blank CSV File Created

Issue summary
I'm creating an export with values from the database and up to a certain number of rows it works perfectly, then when one extra row is added, the CSV returned is blank.
I've checked the data of that row and it is just a string, also, using offsets in the database query I've managed to add the row in fine with a smaller set of data.
So, it's not the data format that's the problem and I'm at a loss.
I've tried using $writer->insertOne() and also $writer->insertAll() but have exactly the same results.
Is there some kind of limit when adding to a file that I don't know about? I am not getting any error logs on the server.
For additional info, there are 9 columns each with a short string of text (avg 2 characters). Depending on the dataset, the limit is somewhere around the 50 row mark
System informations
(In case of a bug report Please complete the table below)

Information
Description

League\Csv version
8.1.0

PHP/HHVM version
5.6

OS Platform
Linux

Standalone code, or other way to reproduce the problem
For me, any dataset of over 50 rows with the amount of data described above is causing the problem.
I am not getting any error logs on the server
    $exportFilePath = $this->createExportFile('questions');
    $writer = Writer::createFromPath($exportFilePath);
    $headings = [
        'Campaign Name',
        'Location Name',
        'Address 1',
        'City',
        'State',
        'Zip',
        'Assessment Date',
        'Question',
        'Answer'
    ];
    $writer->insertOne($headings);

    $questionsData = $this->getQuestionsExportData();

    foreach ($questionsData as $data) {

        $dataRow = [
            $data->campaignName,
            $data->locationName,
            $data->locationAddress,
            $data->locationCity,
            $data->locationState,
            $data->locationZip,
            $data->completed,
            $data->questionText,
            $data->answerText,
        ];
        $writer->insertOne($dataRow);
    }

    return \Response::download($exportFilePath);

Expected result
CSV file with all rows with data
Actual result
Empty CSV file

Hi @Britic, thanks for the report. From your code I fail to see how you can be sure that the behaviour you are reporting comes from the League\Csv package ?
return \Response::download($exportFilePath);

you seems to give your exportFilePath to a download method both of which are not produced by the package. Since I don't know how these (methods/functions) works I can not debug your issue maybe try to do what you've describe using only the package functionnalities then I'll be able to fix what needs to be fix ... if the issue still remains.

Thanks for your response.
return \Response::download($exportFilePath);
is a Laravel function for returning the file for download. I understand that's not under your control, but even ignoring that, the file on the server remains completely blank.
When I replace any use of writer with the native functions, I get the expected file download.
`
public function questionsExport()
{
$exportFilePath = $this->createExportFile('questions');
$handle = fopen($exportFilePath, 'w+');
//$writer = Writer::createFromPath($exportFilePath);
    $headings = [
        'Campaign Name',
        'Location Name',
        'Address 1',
        'City',
        'State',
        'Zip',
        'Assessment Date',
        'Question',
        'Answer'
    ];
    //$writer->insertOne($headings);
    fputcsv($handle, $headings);

    $questionsData = $this->getQuestionsExportData();

    foreach ($questionsData as $data) {

        /* @var $assessment \App\Assessment */
        $dataRow = [
            $data->campaignName,
            $data->locationName,
            $data->locationAddress,
            $data->locationCity,
            $data->locationState,
            $data->locationZip,
            $data->completed,
            $data->questionText,
            $data->answerText,
        ];
        //$writer->insertOne($dataRow);
        fputcsv($handle, $dataRow);
    }

    $headers = array(
        'Content-Type' => 'text/csv',
    );

    return \Response::download($exportFilePath, null, $headers);
}

`
If you want to close this issue as I can't confirm where the error lies, then that's no problem.

hmm what your are doing is very complicated.
There's a simple article on how to use League\Csv  with Laravel you shoud check.
I hope it does answer your question.


Revert template until after rfc

As discussed in #3860, templates was merged without going through the RFC process. @ssokolow has raised some useful comments which need to be settled before the template system can be put back in.
#3859 was another relevant issue.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+
Thanks @ehiggs for staying on top of this! If you need any help writing an RFC please just let me know, I'd be eager to see this in Cargo :)

:pushpin: Commit b998130 has been approved by alexcrichton

@ehiggs oh so some further steps we'll need to take on this are:

Send a PR to the rust-1.17.0 branch of this repo with these same contents
Send a PR to rust-lang/rust to update the cargo submodule on rust's master branch
Send a PR to rust-.ang/rust for the beta branch as well

I certainly don't mind doing these as well, but if you're interested in learning the process it's just a few PRs and I'd also be more than happy to r+!

Ok, I'll take a look at doing this.

:hourglass: Testing commit b998130 with merge ec67e38...

:broken_heart: Test failed - status-travis

homu job failed with error: component download failed for rust-std-mipsel-unknown-linux-gnu. Seems a transient failure.

@bors: retry
On Thu, Mar 30, 2017 at 11:02 AM, Ewan Higgs<EMAIL_ADDRESS>wrote:

homu job failed with error: component download failed for
rust-std-mipsel-unknown-linux-gnu. Seems a transient failure.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/cargo/pull/3878#issuecomment-290475449, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAD95DNNI4B6tFsIaQJRLuqG5fbrWDd7ks5rq-AdgaJpZM4MtgzV
.

:hourglass: Testing commit b998130 with merge f4584ab...

:broken_heart: Test failed - status-appveyor

@bors: retry
On Thu, Mar 30, 2017 at 12:10 PM, bors<EMAIL_ADDRESS>wrote:

💔 Test failed - status-appveyor
https://ci.appveyor.com/project/rust-lang-libs/cargo/build/1.0.1528
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/cargo/pull/3878#issuecomment-290495918, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAD95Dve-4tZs2-4SdfEpmfSYciHROLqks5rq-_-gaJpZM4MtgzV
.

:hourglass: Testing commit b998130 with merge a07912a...

:broken_heart: Test failed - status-travis

@bors: retry
On Mar 30, 2017 11:58 PM, "bors"<EMAIL_ADDRESS>wrote:

💔 Test failed - status-travis
https://travis-ci.org/rust-lang/cargo/builds/217047804
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/cargo/pull/3878#issuecomment-290624169, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAD95CMGPN3Vb0Yb3aHjJ0GdsLZNWXDjks5rrJXugaJpZM4MtgzV
.

:hourglass: Testing commit b998130 with merge d3d3d3f...

:broken_heart: Test failed - status-travis

@bors: retry
On Fri, Mar 31, 2017 at 1:10 AM, bors<EMAIL_ADDRESS>wrote:

💔 Test failed - status-travis
https://travis-ci.org/rust-lang/cargo/builds/217063308
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/cargo/pull/3878#issuecomment-290634860, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAD95Dug-YatsgwMrr2cm4xr_Yr-DOP7ks5rrKbUgaJpZM4MtgzV
.

:hourglass: Testing commit b998130 with merge f53fec0...

Is this number of retries normal?

Not really, sometimes @bors just really doesn't like us :(

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing f53fec02fbb2b2075cb791f3773fd4547b0d1032 to master...

Pre-rfc thread is here


sver updates

This PR contains sver updates for:

golang 1.19
add go workspace
update mage and mage dependencies
update Depfile (vault, sver, goreleaser, linter, test)
update depandabot dependencies
GitHub Action updates addressing https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
change tests to reside in _test package namespace
fix gh-action-entrypoint.sh to address https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.0%) to 51.111%

Totals

Change from base Build<PHONE_NUMBER>:
-0.0%

Covered Lines:
184

Relevant Lines:
360

💛  - Coveralls


How to filter down with "exact" match?

I went through the readme extensively but could not find what I am looking for.
it seems that by default if I do
itemsJS.search({
  filters: [
     brands: ['toshi']
  ]
});

Every entries with brands

toshi
toshiba
kitoshi

will be returned as results.
Is there a way to only return entries which have the brand toshi?

Hey @regisphilibert, as far as I remember when I designed ItemsJS the filters should work in the "exact" mode. This behaviour sounds like a bug. I'll check it out in about 7 days

Hey @regisphilibert, I've told to you I'll check it out in 7 days. Sorry I didn't have time. It's on my todo list though

Don't worry about it, we put a workaround in place and it works great for now. Thanks for keeping me in the loop though!

What was the workaround @regisphilibert ? By coincidence I experienced the "bug" as well, just now.
Will issue a PR to fix it. it only happens when your data, brands in this case, is just a string (so no collection).


Manual scanner sensor

Is there a way to manually add an RSSI sensor as a participant in the set of trackers known to bermuda?  I have a number of wall tablets set up with the HA companion app, with the app configured as an ibeacon monitor.  This creates an entity in hass for each tablet with attributes for each detected ble mac and the current estimated distance (which can presumably be used to back out the raw RSSI)?  Those attributes can then be extracted out into their own dedicated sensor entities in hass.
Hoping to find a way to leverage those entities alongside other esp32 ble trackers throughout my house
Possibly related to #193

Howdy! Thanks for your suggestion. If you take a look at #327 you'll get the overall picture. In short - it might work well if the HA Companion app chose to implement the HA standard HaBaseScanner in the app, then it should work automatically.
Hacking around converting entities into scanner data would be quite circuitous, and wouldn't be something I'd accept into Bermuda. Converting from the distance estimate back to rssi requires knowing the reference power and the attenuation used in the original equation, plus we would probably have to make some fairly inaccurate assumptions about the timestamps of the advertisements, plus if we don't have the full content of the advertisement it reduces other functionality, too.
The other app and custom integration mentioned in #193 and #327 may still be a possibility, as described.
I'll close this ticket since the other two already address the likely options, but feel free to raise any questions you might have after looking them over.


Handle the invalidate OOB push message.

Description

Provides a register callback that if set will be called when the client receives a key invalidate message from the server.

Checklist

[ ] Does npm test pass with this change (including linting)?
[ ] Is the new or changed code fully tested?
[ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

this should probably be closed and https://github.com/redis/node-redis/pull/2735 used instead.


Add AWS Codebuild support

Purpose
Add AWS Codebuild support
Notable Changes
No
Tests and Risks?
New tests

Closes #216

This is a good PR, shoutout to you @drazisil for killing it on adding CI support

This has been deployed