Error when resizing image for inference using trained model on Jetson TX2 - seeking advice

Hello,
When I try to perform inference by reducing the image size, an error occurs.
change_size_config = yolact_edge_config.copy({
    'name': 'change_size_config',
    'dataset': test_dataset,
    'max_iter': 1,
    'lr_steps': (4500, 7500),

    # Image Size
    'max_size': 480,
})

I used this to conduct the training:
root@nvidia-desktop:/app/yolact_edge# python3 train.py --config=change_size_config --save_folder=/share/test/ --num_workers=0 --resume=/share/test/yolact_edge_54_800000.pth --batch_size=1 --start_iter=0
2023-03-03 14:37:28.798146: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.10.2
WARNING:tensorflow:Deprecation warnings have been disabled. Set TF_ENABLE_DEPRECATION_WARNINGS=1 to re-enable them.
[03/03 14:37:37 yolact.train]: Args: train.py --config=change_size_config --save_folder=/share/test/ --num_workers=0 --resume=/share/test/yolact_edge_54_800000.pth --batch_size=1 --start_iter=0
loading annotations into memory...
Done (t=0.00s)
creating index...
index created!
loading annotations into memory...
Done (t=0.00s)
creating index...
index created!
[03/03 14:37:56 yolact.train]: Resuming training, loading /share/test/yolact_edge_54_800000.pth...
[03/03 14:37:58 yolact.train]: Begin training!
/app/yolact_edge/yolact_edge/utils/augmentations.py:414: VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (which is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or shapes) is deprecated. If you meant to do this, you must specify 'dtype=object' when creating the ndarray
  mode = random.choice(self.sample_options)
[03/03 14:38:12 yolact.train]: eta: 0:00:00  epoch: 0  iter: 0  B: 3.032  M: 7.972  C: 9.760  S: 9.037  T: 29.801  time: 13.694  data_time: 0.000  lr: 0.000100  max_mem: 944M

However, when I try to perform inference using the resulting .pth file, an error occurs:
root@nvidia-desktop:/app/yolact_edge# python3 eval.py --config=change_size_config --use_fp16_tensorrt --trained_model=/share/test/change_size_config_0_1.pth  --score_threshold=0.3 --top_k=100  --image=/share/test/test.jpg
[03/03 14:38:57 yolact.eval]: Loading model...
[03/03 14:39:15 yolact.eval]: Model loaded.
[03/03 14:39:15 yolact.eval]: Converting to TensorRT...
[03/03 14:39:15 yolact.eval]: Converting backbone to TensorRT...
[03/03 14:40:23 yolact.eval]: Converting protonet to TensorRT...
[03/03 14:40:34 yolact.eval]: Converting FPN to TensorRT...
Warning: Encountered known unsupported method torch.zeros
[03/03 14:40:49 yolact.eval]: Converting PredictionModule to TensorRT...
[03/03 14:41:14 yolact.eval]: Converted to TensorRT.
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1045, condition: profileMinDims.d[i] <= dimensions.d[i]
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1045, condition: profileMinDims.d[i] <= dimensions.d[i]
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1045, condition: profileMinDims.d[i] <= dimensions.d[i]

Has anyone been able to change the size and perform inference successfully?
By the way, here's my environment:
Jetson TX2
nvcr.io/nvidia/l4t-base:r32.4.3

https://github.com/haotian-liu/yolact_edge/issues/37#issuecomment-766462942
I changed not only max_size but also pred_scales, discard_box_height, etc. according to this description.
https://github.com/haotian-liu/yolact_edge/issues/110
https://github.com/haotian-liu/yolact_edge/issues/123
input_sizes = [
        (1, 256, 69, 69),
        (1, 256, 35, 35),
        (1, 256, 18, 18),
        (1, 256, 9, 9),
        (1, 256, 5, 5),
]

I was told that input_sizes also needed to be changed, so I estimated from the mood of the values that the sizes were P3~P7 and changed them.
I asked ChatGPT about the size.
If ResNet101 is used as the backbone and a 350x350 image is input to RetinaNet, the output sizes of P3 to P7 would be as follows:

P3: (44, 44)
P4: (22, 22)
P5: (11, 11)
P6: (6, 6)
P7: (3, 3)
Since ResNet101 is a deeper model with more layers, it can extract more sophisticated feature representations. However, when the input size is smaller, RetinaNet generates smaller feature maps, resulting in smaller output sizes for P3 to P7 compared to when ResNet50 is used as the backbone.

However, this still produced an error
2023-03-27 08:04:30,624 - INFO - cam1:rtsp://<IP_ADDRESS>:8554/mystream1 open
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1045, condition: profileMinDims.d[i] <= dimensions.d[i]
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1045, condition: profileMinDims.d[i] <= dimensions.d[i]
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1045, condition: profileMinDims.d[i] <= dimensions.d[i]
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1044, condition: profileMaxDims.d[i] >= dimensions.d[i]
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1044, condition: profileMaxDims.d[i] >= dimensions.d[i]
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1044, condition: profileMaxDims.d[i] >= dimensions.d[i]
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1044, condition: profileMaxDims.d[i] >= dimensions.d[i]
[TensorRT] ERROR: Parameter check failed at: engine.cpp::setBindingDimensions::1044, condition: profileMaxDims.d[i] >= dimensions.d[i]
2023-03-27 08:04:31,429 - WARNING - ExternalDeviceSetting exit: <class 'RuntimeError'> shape '[1, 19248, 11]' is invalid for input of size 85338 <traceback object at 0x7ed5d18808>
2023-03-27 08:04:31,434 - INFO - loader exit
2023-03-27 08:04:31,435 - WARNING - AppSetting.ChangeHandler exit: <class 'RuntimeError'> shape '[1, 19248, 11]' is invalid for input of size 85338 <traceback object at 0x7ed5d18808>
Traceback (most recent call last):
  File "/app/parkingdetectcabin/__main__.py", line 28, in <module>
    r = ParkingDetectCabin().main()
  File "/app/parkingdetectcabin/classes/parking_detect_cabin.py", line 112, in main
    result_list = analytics_cabin.detect(frame=frame_dict, disp= (self.app_setting.disp or self.app_setting.web_stream), frame_rate=frame_rate)
  File "/app/parkingdetectcabin/classes/domain/interactor/analytics_cabin.py", line 137, in detect
    detect_result = zip(frame.keys(), frame.values(), [self.model.detect(v[0], verbose=0, camera_index=k) for k, v in frame.items()])
  File "/app/parkingdetectcabin/classes/domain/interactor/analytics_cabin.py", line 137, in <listcomp>
    detect_result = zip(frame.keys(), frame.values(), [self.model.detect(v[0], verbose=0, camera_index=k) for k, v in frame.items()])
  File "/app/parkingdetectcabin/classes/domain/model/segment_model_from_yolact_edge.py", line 247, in detect
    net_outs = self.yolact(batch, extras=extras)
  File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/torch/nn/parallel/data_parallel.py", line 165, in forward
    return self.module(*inputs[0], **kwargs[0])
  File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/app/parkingdetectcabin/classes/core/yolact_edge/yolact_edge/yolact.py", line 1802, in forward
    outs_wrapper["pred_outs"] = self.detect(pred_outs)
  File "/app/parkingdetectcabin/classes/core/yolact_edge/yolact_edge/layers/functions/detection.py", line 71, in __call__
    conf_preds = conf_data.view(batch_size, num_priors, self.num_classes).transpose(2, 1).contiguous()
RuntimeError: shape '[1, 19248, 11]' is invalid for input of size 85338

I found the following settings listed elsewhere, but they do not work.
'pred_scales': [[int(x[0] / yolact_base_config.max_size * 350)] for x in yolact_base_config.backbone.pred_scales],

I set up the following and it worked for all sizes except 550
    'max_size': 416,
    'discard_box_width': 4 / 416,
    'discard_box_height': 4 / 416,
    'backbone': yolact_base_config.backbone.copy({
        # Must be changed according to the size of the feature map
        'pred_scales': [[floor(x[0] * (416 / yolact_base_config.max_size))] for x in yolact_base_config.backbone.pred_scales],
    }),


[FEATURE] Want to add up the build pipeline that runs on every PR

Why do we need this improvement?
As while merging up a PR it will give us an overview that after merging up the PR is the project building up correctly it will run on every new PR that is been raised up by somewone.
How will this change help?
As the maintainer before merging up the PR will have a look that is that project building up correctly or some edge case are falling apart
Screenshots
No response
How could it be implemented/designed?
By Initisilising up an Check_build.yml file inside which I will describe up the logic for that build.
🚧 Breaking changes
Yes
👀 Have you checked for similar open issues?

[X] I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to work on this issue?
Yes I am willing to submit a PR!

Hey @abhay-raj19, we already have netlify build preview action that runs on each PR and we are able to detect build errors through that workflow.


Fuzzy logic on name fields matching

Current Implementation
On https://www.coronawarn.app/de/blog/2021-12-20-cwa-2-15/ it says: Nutzer*innen sollten unbedingt darauf achten, dass der Name, der im Zertifikat, das sie zur Überprüfung benutzen wollen, hinterlegt ist, EXAKT dem Namen entspricht, den sie im Buchungssystem angegeben haben. Ist das nicht der Fall, können sie das entsprechende Zertifikat in der Corona-Warn-App nicht auswählen.
Suggested Enhancement
Implement a fuzzy logic /regexp that mathes even if the name is not exactly the same.
Expected Benefits
Some people have multiple givennames but they only use one (Rufname). And you won't type four givennames when you buy a concert ticket. Most times this will even exceed the field limits. So matching parts of the name would be very helpfull for those people.

If possible, a good idea.

Thanks for your suggestion @kroerig. We have created an internal ticket for it and will raise this topic internally.
Internal Tracking ID: EXPOSUREAPP-11299

Corona-Warn-App Open Source Team

@kroerig  Thanks for creating this wishlist item. With the implementation of a fault tolerant name handling in version 2.19 we would suggest closing this issue. Best wishes, DS

Corona-Warn-App Open Source Team
EXPOSUREAPP-11617
EXPOSUREAPP-11618

Closing this issue as suggested since there was no further activity.

Corona-Warn-App Open Source Team


fix: Use rejectUnauthorzed instead of strictSSL

Even though they should be the same thing, strictSSL was not working but rejectUnauthorized does.
frrom #390 but with added tests

coverage: 98.802%. remained the same
when pulling 34fd1d3130377f6c04b675ade01c92a312f90b17 on lholmquist:rejectUnathorizedWithTests
into 271304a9a1dc7a76074b5627df8cd77a76b64776 on nodeshift:main.


Forced d2 rolls do not force a result

Calling Box.roll("1d2@2"), it flips a coin, but the coin lands on either the 1 or 2 side. The promise result still shows a value of 2 and a label of "2", with reason as "forced" or "natural", but half the time the graphics will show that the coin landed on 1.
All the other sizes I tested work as expected (d3, d4, d6, d10, d12, d20, d100).
Version tested: 0.0.12
Browser: Firefox 122.0 (64-bit)
OS: Linux/NixOS

Update: I also found that rolling a natural (non-forced) "1d2" results in "1" over 90% of the time (should be about 50%). And the few times it lands on "2" graphically, it usually shows a value of "1" in the promise result.


Invariant loads are not hoisted out of loops

Currently Cranelift will not hoist invariant loads outside of loops, meaning that an invariant load is reloaded on each iteration of the loop. For example with this code:
(module
  (memory 0)
  (func $add_all (param $ptr i32) (param $len i32) (result i32)
    (local $result i32)
    loop $l
      (local.set $result
        (i32.add
          (local.get $result)
          (i32.load (local.get $ptr))
        )
      )

      (local.set $ptr
        (i32.add
          (local.get $ptr)
          (i32.const 4)
        )
      )

      (br_if $l
        (local.tee $len
          (i32.sub
            (local.get $len)
            (i32.const 1)
          )
        )
      )
    end
    (local.get $result)
  )
)

this machine code is generated on x86_64:
$ wasmtime compile foo.wat && objdump -S foo.cwasm

foo.cwasm:     file format elf64-x86-64

Disassembly of section .text:

0000000000000000 <_wasm_function_0>:
       0:       55                      push   %rbp
       1:       48 89 e5                mov    %rsp,%rbp
       4:       31 c0                   xor    %eax,%eax
       6:       49 89 c9                mov    %rcx,%r9
       9:       48 8b 4f 50             mov    0x50(%rdi),%rcx
       d:       44 8b c2                mov    %edx,%r8d
      10:       42 8b 4c 01 00          mov    0x0(%rcx,%r8,1),%ecx
      15:       41 83 e9 01             sub    $0x1,%r9d
      19:       01 c8                   add    %ecx,%eax
      1b:       83 c2 04                add    $0x4,%edx
      1e:       45 85 c9                test   %r9d,%r9d
      21:       0f 85 e2 ff ff ff       jne    9 <_wasm_function_0+0x9>
      27:       48 89 ec                mov    %rbp,%rsp
      2a:       5d                      pop    %rbp
      2b:       c3                      retq
        ...

The instruction at 9 is loading the base pointer of memory from the VMContext, in %rdi, into %rcx. This load happens on all iterations of the loop, however.
The Cranelift function being lowered here is (according to RUST_LOG):
function u0:0(i64 vmctx, i64, i32, i32) -> i32 fast {
    gv0 = vmctx
    gv1 = load.i64 notrap aligned readonly gv0+8
    gv2 = load.i64 notrap aligned gv1
    gv3 = vmctx
    gv4 = load.i64 notrap aligned readonly gv3+80
    stack_limit = gv2

                                block0(v0: i64, v1: i64, v2: i32, v3: i32):
@001f                               v5 = iconst.i32 0
@0021                               jump block2(v5, v2, v3)  ; v5 = 0

                                block2(v6: i32, v7: i32, v15: i32):
@0027                               v9 = load.i64 notrap aligned readonly v0+80
@0027                               v8 = uextend.i64 v7
@0027                               v10 = iadd v9, v8
@0027                               v11 = load.i32 little heap v10
@0036                               v16 = iconst.i32 1
@0038                               v17 = isub v15, v16  ; v16 = 1
@002a                               v12 = iadd v6, v11
                                    v4 -> v12
@002f                               v13 = iconst.i32 4
@0031                               v14 = iadd v7, v13  ; v13 = 4
@003b                               brif v17, block2(v12, v14, v17), block4

                                block4:
@003d                               jump block3

                                block3:
@0040                               jump block1

                                block1:
@0040                               return v12
}

Specifically the instruction v9 = load.i64 notrap aligned readonly v0+80 is not hoisted outside of the loop, despite it being readonly, notrap, and v0 not being dependent on any loop value.

Ideally this line should cause loads with notrap and readonly to be considered pure, and thus hoistable. I can look into this eventually if someone else doesn't get to it first (just wanted to point to that line as a starting point).

Brief debugging my part reveals that line is working as intended but here, during loop hoisting, the argument to the load instruction, v0, is listed as:
 629 [cranelift/codegen/src/egraph/elaborate.rs:408] &value = ElaboratedValue {
 630     in_block: block2,
 631     value: v0,
 632 }

where I think in_block: block2 is preventing the hoist?

While I'm not sure that https://github.com/bytecodealliance/wasmtime/pull/5960 is 100% correct it fixes the issue here at least


federated catalogues None error

Description
if I set federated catalogues to None, i run into this error on /collections/metadata:main, what is the best way to deactivate federated catalogues?

Environment

operating system: docker/ubuntu
Python version:
pycsw version: latest

seems better to remove the full key in stead of making it empty
https://github.com/geopython/pycsw/blob/ac81aa8f3c362b8fa76439bb94189c943cffb267/pycsw/ogc/api/records.py#L1021

Thanks @pvgenuchten. Would the following work instead?
diff --git a/pycsw/ogc/api/records.py b/pycsw/ogc/api/records.py
index 83c3179e..59c077ac 100644
--- a/pycsw/ogc/api/records.py
+++ b/pycsw/ogc/api/records.py
@@ -1018,7 +1018,7 @@ class API:
         }

         if collection_name == 'metadata:main':
-            if 'federatedcatalogues' in self.config:
+            if self.config.get('federatedcatalogues') is not None:
                 LOGGER.debug('Adding federated catalogues')
                 collection_info['federatedCatalogues'] = []
                 for fc in self.config.get('federatedcatalogues', []):

yes it would work, updating pr


Address Bar Spoofing Tests + Remediation

Task/Issue URL: https://app.asana.com/0/72649045549333/1205794884403778/f
Description
The browser implementation of the address bar updating functionality is currently vulnerable to an Address Bar Spoofing vulnerability. In this PR I integrate all of our known address bar spoofing tests, including a fix for the basic auth address bar spoofing issues where someone can hide the domain portion of the address bar by prepending fake basic auth credentials to the domain.
In the fix, I simply strip the username/password fields from the address bar which forces the browser to prompt for username/password. This is consistent with our other browser implementations on macOS and iOS.
Steps to test this PR
Security Tests

[ ] run maestro test .maestro/security_tests/0_all.yaml
[ ] ensure all tests are passing

Basic Auth

[ ] visit a page that actually requires basic auth<EMAIL_ADDRESS>[ ] check that username/password are stripped from address bar
[ ] check that the username/password prompt is still raised
[ ] visit a page that doesn't require basic auth<EMAIL_ADDRESS>[ ] check that username/password are stripped from the address bar
[ ] no username/password prompt is raised.

Thanks @marcosholgado - I wasn't expecting anyone to take a look at this yet, it should've been a draft but I've opened a task to get permission to create a branch and will close this fork for now.


Can't pip install gcloud with Python 3.4 and pip 6.x

I was porting WAL-E to Python 3.4 and things were working well (perhaps because of newer versions of pip on my Fedora Linux installation), however, an older version of pip seen in the wild on servers (the 6.x series) doesn't seem to work. Is there an adjustment that would allow even 6.x era pip to function?
A transcript follows:
$ sudo pip-3.4 install gcloud
You are using pip version 6.1.1, however version 8.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Collecting gcloud
  Using cached gcloud-0.17.0.tar.gz
Collecting httplib2>=0.9.1 (from gcloud)
  Using cached httplib2-0.9.2.zip
Collecting googleapis-common-protos (from gcloud)
  Using cached googleapis-common-protos-1.2.0.tar.gz
Collecting oauth2client>=2.0.1 (from gcloud)
  Using cached oauth2client-2.2.0.tar.gz
Collecting protobuf!=3.0.0.b2.post1,>=3.0.0b2 (from gcloud)
  Could not find a version that satisfies the requirement protobuf!=3.0.0.b2.post1,>=3.0.0b2 (from gcloud) (from versions: 2.0.0b0, 2.0.3, 2.3.0, 2.4.1, 2.5.0, 2.6.0, 2.6.1, 3.0.0a2, 3.0.0a3, 3.0.0b1, 3.0.0b1.post1, 3.0.0b1.post2, 3.0.0b2, 3.0.0b2.post1, 3.0.0b2.post2, 3.0.0b3, 3.0.0b4)
  No matching distribution found for protobuf!=3.0.0.b2.post1,>=3.0.0b2 (from gcloud)

I got this issue as well, yesterday, on Python 3.5, but today it's working. Looks like there is a new version on pip. Thank you.
I wanted to point out, though, that the gcloud home page still states the Py2.7 is required, and specifically asks the user to verify that they have 2.7 before continuing.
https://cloud.google.com/sdk/docs/quickstart-mac-os-x

@waleedka RE: "the gcloud home page", gcloud-python != gcloud, but thanks for the heads up

Thanks for the clarification. I realized that as well when I tried to install the gcloud sdk on py3 and it didn't work :(

@fdr Please LMK if this is still an issue.


Front - V1 - iOS - Get the form from the Wordpress

• Get the form in the wordpress
• Create the different components


IMX Low-Latency Mode

Hi
Is it possible to read and/or set IMX Low-Latency Mode for DFK 38UX267 on Linux? I found that /tiscamera/data/uvc-extensions/usb37.xml contains this field, so my guess is that it is possible with DFK 37U cameras.

Yes
(Short answer... )
You may check with tcam-capture.
Stefan

Hi Stefan,
I checked all the properties, including the special tab, in tcam-capture, but did not find this option. Where this option is supposed to be?
BTW, tcam-ctrl --save does not list the option. I am using 0.13.1 version of tiscamera.
Maxim

You are right, it is missing in the UVC Extension for 38U cameras. I asked engineers to add this.
You could compile tiscamera with
cmake -DTCAM_ARAVIS_USB_VISION=ON -DBUILD_ARAVIS=ON ..
and access the camera by the USB3Vision interface by passing the serialnumber as "nnnnnnnn-aravis" to the tcambin / tcamsrc. You can select the camera in tcam-capture accordingly.  Doing so, you will see all available camera properties.
Stefan

Thanks Stefan. May I ask to add Trigger overlap option to UVC, please? Or should I create another issue for this?
I follow the build instructions and use the definitions you suggested, but build fails at
[  0%] Performing configure step for 'aravis'
/bin/sh: 1: /home/user/projects/tiscamera/external/aravis/autogen.sh: not found
external/CMakeFiles/aravis.dir/build.make:125: recipe for target 'external/aravis-prefix/src/aravis-stamp/aravis-configure' failed
make[2]: *** [external/aravis-prefix/src/aravis-stamp/aravis-configure] Error 127
CMakeFiles/Makefile2:656: recipe for target 'external/CMakeFiles/aravis.dir/all' failed
make[1]: *** [external/CMakeFiles/aravis.dir/all] Error 2
Makefile:170: recipe for target 'all' failed
make: *** [all] Error 2
However autogen.sh does exists:
$ ls -l /home/user/projects/tiscamera/external/aravis/autogen.sh
-rwxrwxr-x 1 user user 1289 Jun  2 10:51 /home/user/projects/tiscamera/external/aravis/autogen.sh
$ cmake --version
cmake version 3.19.4
BTW, I updated the repository to the latest master revision.
Maxim

I forwarded the trigger overlap request to the colleagues.
We found, that the DFK 38UX267 is the only DFK 38U camera, that does not export the IMX Low Latency Property by UVC. To be fixed. I will come back to you.
Regarding building: You may delete the build directory content first:
cd build
rm * -rf
cmake -DTCAM_ARAVIS_USB_VISION=ON -DBUILD_ARAVIS=ON ..
make -j30
sudo make install

(-j30 allows make to use up to 30 threads).
Stefan

Hi Maxim
One addition: The firmware team states, that Trigger Overlap is not an UVC control. Therefore, it wont be added.
Stefan

Hi Stefan,
Alas, I could not compile tiscamera:
$ mkdir build_usb3_vision
$ cd build_usb3_vision
$ cmake -DTCAM_ARAVIS_USB_VISION=ON -DBUILD_ARAVIS=ON ..
...
-- Configuring done
-- Generating done
$ make -j30
....
[ 45%] Performing configure step for 'aravis'
/bin/sh: 1: /home/user/projects/tiscamera/external/aravis/autogen.sh: not found
external/CMakeFiles/aravis.dir/build.make:125: recipe for target 'external/aravis-prefix/src/aravis-stamp/aravis-configure' failed
make[2]: *** [external/aravis-prefix/src/aravis-stamp/aravis-configure] Error 127
CMakeFiles/Makefile2:656: recipe for target 'external/CMakeFiles/aravis.dir/all' failed
make[1]: *** [external/CMakeFiles/aravis.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Hi Maxim
that is strange. It worked perfectly on my Ubuntu.
I suggest to clone the project again:
git clone https://github.com/TheImagingSource/tiscamera.git tis-usb3vision
cd tis-usb3vision
sudo ./scripts/install-dependencies.sh --compilation --runtime
mkdir build
cd build
cmake -DTCAM_ARAVIS_USB_VISION=ON -DBUILD_ARAVIS=ON ..
make -j 30
sudo make install

Stefan

Hi Stefan,
The cause of the build failure is that my git config had core.autocrlf set to true for some reasons. It changed line endings and broke all the scripts in the repository. So I could build and install tiscamera with aravis. However, I still could not find IMX option in tcam-capture. I looked for this option in the Special tab.
The new firmware will be nice. Will the export of IMX Low Latency Mode be the only change in this update?
Maxim

Hello Maxim
Please send me the output of tcam-ctrl -l
Stefan

Hi Stefan
$ tcam-ctrl -l
Model: DFK 38UX267 Serial: 18914001 Type: v4l2
Model: DFK 38UX267 Serial: 18914003 Type: v4l2
Model: DFK 38UX267 Serial: 18914001 Type: aravis
Model: DFK 38UX267 Serial: 18914003 Type: aravis
Maxim

Hello Maxim
that looks very good.
Now you should be able to use
tcam-ctrl -p 18914001-aravis
and see much more properties compared with the output of
tcam-ctrl -p 18914001-v4l2
Stefan

Hi Stefan
Indeed, I get much more properties, including IMX low latency and Trigger Overlap. The most of these properties are not documented. Are they supposed to be available to user?
All these properties are in INVALID_PORPETY group. What does it mean? Is it possible to change IMX low latency and Trigger Overlap properties?
Maxim

Hi Maxim
"invalid property group" means only, that tcam-ctrl does not how to group these properties. But it is possible to change the values. Uhm... Trigger Overlap is readonly.
Do you see the same properties in tcam-capture too?
Stefan

Hi Stefan,
Only when I run:
$tcam-capture --serial=18914001-aravis
I do not see these options when run:
$tcam-capture
When change TriggerOverlap, tcam-capture froze. After that tcam-ctrl -p 18914001-aravis stopped to return anything, but tcam-ctrl -p 18914001 does work.
The same happens when use tcam-ctrl --load 18914001-aravis conf.json, where conf.json is output of tcam-ctrl --save with the IMX property set to true and TriggerOveralp set to Off:
$tcam-ctrl --load 18914001-aravis conf.json # runs for quite a while
Loading: aravis.json
$echo $?
0
$tcam-ctrl --save 18914001-aravis
{
"properties": null,
"serial": "18914003",
"version": "v0.1"
}
Maxim

Hello Maxim
tcam-capture should show the camera twice, once with aravis and once with v4l2. You should be able to select it from the device combobox. Or your can start tcam-capture with "tcam-capture --reset", then you will see the standard device selection dialog.
You can not set Trigger Overlap. That is a read only property and shows only, whether you can trigger now.
Stefan

Hi Stefan,
I can not set IMX low latency trigger mode as well. Is it what you are expecting?
Maxim

Hello Maxim
you should be able to set that as boolean value. Does tcam-capture show it?  However, I learned, that the DFK 38UX267 has an outdated firmware. Please send me a request to support at theimagingsource.com, so I can send the new firmware to you. The zip file will contain the fwpack file, which is the firmware file and the "33update.exe", which is the Windows firmware update program.
After firmware update, the IMX Low Latency Mode is available in v4l2 too.
I wonder, why this IMX Low Latency Mode is so important to you.
Stefan

Hi Stefan,
Thank you a lot for your support! I have sent the request via the contact form on theimagingsource.com. I want to stream pairs of synchronous frames from two cameras, so there is a requirement that frames arrive with low latency and the cameras start exposure at the same time (as much as possible).
Kind Regards,
Maxim

Hello Maxim
I will handle your request as soon as possible.
In v4l2 IMX Low Latency will be available, Trigger Overlay not. In USB3Vision both are available.
I suppose, you use an external trigger source and have the camera wired to it via the Hirose connector. On software trigger the IMX Low Latency Mode has no effect.
Stefan


MultiK2 Unity

Hello, bro.
Really good idea. You deserve congratulations!!
It is not an issue, I just wanted to know if there is any prevision for it be available for production.
Also, have you tested to know if the api works with Unity 5? I think it could be a good feature.
I am trying to make it.
Cheers!!

Hello,
local sensor usage will hopefully reach "release preview" state before end of this month.
network sensor usage - end of April (soonest)
I haven't tested integration of MultiK2 with Unity - it wasn't goal of this library. I am all open to integration / adjustment for Unity but I do not use it = feedback from people utilizing Unity is needed atm.

I can confirm it integrates well with Unity.


fixes compatibility with older node versions

submitted to fix compatibility with older node versions, specifically fixes the following:
Error loading command .../particle-cli/commands/KeyCommands.js SyntaxError: Unexpected token (
Error loading command .../particle-cli/commands/SerialCommand.js SyntaxError: In strict mode code, functions can only be declared at top level or immediately within another function.

weird!  any issue with merging this pr?

Thanks for the fix. It's merged. No issues but the weirdness of having several branches and doing complex merges...


[Bug]: Cannot read partitions metadata table from bigquery

What happened?
Hello,
I wanted to read partitions metadata from bigquery table project_id.dataset_id.INFORMATION_SCHEMA.PARTITIONS using ReadFromBigQuery. Unfortunately, this function raises an error:
RuntimeError: apitools.base.py.exceptions.HttpNotFoundError: HttpError accessing <https://bigquery.googleapis.com/bigquery/v2/projects/[project_id]/jobs?alt=json>: response: <{'vary': 'Origin, X-Origin, Referer', 'content-type': 'application/json; charset=UTF-8', 'date': 'Mon, 19 Dec 2022 17:02:59 GMT', 'server': 'ESF', 'cache-control': 'private', 'x-xss-protection': '0', 'x-frame-options': 'SAMEORIGIN', 'x-content-type-options': 'nosniff', 'transfer-encoding': 'chunked', 'status': '404', 'content-length': '388', '-content-encoding': 'gzip'}>, content <{
  "error": {
    "code": 404,
    "message": "Not found: Dataset [project_id]:`[table_name] was not found in location EU",
    "errors": [
      {
        "message": "Not found: Dataset [project_id]:`[table_name] was not found in location EU",
        "domain": "global",
        "reason": "notFound"
      }
    ],
    "status": "NOT_FOUND"
  }
}
> [while running '[11]: FindPreviousPartitionDate/Read/SDFBoundedSourceReader/ParDo(SDFBoundedSourceDoFn)/SplitAndSizeRestriction']

The part of code that causes the error:
"FindPreviousPartitionDate" >> beam.io.ReadFromBigQuery(
    query="SELECT * FROM `[project_id].[dataset_id].INFORMATION_SCHEMA.PARTITIONS`",
    use_standard_sql=True,
    flatten_results=False
)

I replaced my actual project id and dataset id with tokens [project_id], [dataset_id].
I've tested it with beam versions 2.36.0 and 2.43.0 using direct and dataflow runners. Also tried running it with different argument values like method, or use_standard_sql, but it doesn't help.
Do you know if it is possible to read from this table using ReadFromBigQuery
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[X] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[X] Component: Google Cloud Dataflow Runner

I used apache_beam 2.53.0 and this bug still exists.
It's a common use case that metada of a BigQuery table is required in the query.
Not only INFORMATION_SCHEMA but also _partitiondate is required in the many cases. For example,
select _partitiondate, * from xxxx
The same query can be executed successfully using bigquery client library. The reason I want to do it using apache beam is because I want to convert to complex SQL joins to PTransform so that it can be executed in parallel to improve the performance.
However, I have to work around it for now.
Hopefully it can be fixed as soon as possible.


Achilles analysis_id cannot be found

In a recent commit all casing was made lowercase, however this throws errors when processing the Achilles analysis. Column analysis_id cannot be found, as the list of achilles details is in uppercase (using Achilles 1.7.2).
It was fixed when I made analysis_id (2x) and category uppercase.
https://github.com/OHDSI/AresIndexer/blob/7bcaa9a56af7a1b4f73e50ea8901dbd22830031b/R/BuildNetworkPerformanceIndex.R#L41-L42

Apologies, I need to get AresIndexer using a development branch. If you move to the development branch of Achilles that fix has been made there.

This is still an issue, even using develop branch of AresIndexer.  I got it to work by using develop branch of Achilles.


Working on the same functionality

Hi,
It seems that we are working on the same functionality... reading and writing MSG files with C# .NET.... the only thing is that I'm somewhat further ahead in implementing functionality.
You can find my project overhere (also used OpenMCDF) --> https://github.com/Sicos1977/MSGWriter
And you can find an MSGReader overhere (That uses COM) --> https://github.com/Sicos1977/MSGReader

I took a look at both. I support reading MSGs without using COM, but I still need to work on writing. It appears that you have two separate projects for reading and writing?

My main goal is also to support reading with the MSGWriter. I just needed a new name so MSGWriter was the obvious choice. But first I finish the writing part and then also change the MSGWriter to support reading. Writing MSG files is the hard part because MSG is a rather complex format to produce.

Oh I'm aware. I actually began writing it for one specific use case, which was reading the IPM.Note format. I've been meaning to support more formats, but I haven't had much time.

I know the problem... everyone (including managers) think that writing a tool that looks rather simple from the outside (It only reads an e-mail) is done in a few days. Bu they never see the complexity that is behind that rather simple thing :-)


Executor failed on job ownership

Receiving the following error via pinlog:

executor failed to renew job ownership on time

I'm having trouble resolving this and was wondering if you know perhaps anything about it?
The job is a CommandLineJob that does an ssh to another box. The job runs about 30 minutes, then the script finished, but pinball then fails with above.
I don't think it's the ServerAliveInterval, I've tried that.

@Tjorriemorrie it will be better if you can paste the stack trace here.

also, the err msg you pasted will only show up if the previous execution of a job failed to renew the ownership. Basically, the message is printed when preparing the current execution of a job.
closing it for now, let me know if you still need any help here.


doc: add security page and description

add Security Report page and short description
add secrity report guideline in contibution

[ ] add the security option to community secondary menu

Could u paster/show the screenshot in PR comment info?
Also sync the EN doc after the CN done

add security guide page

security report page EN version

security report page CN version


1.4.3 getContinuation is not being recognized in typescript from search results

Expected Behavior
Search response type should have getContinuation method
Current Behavior

Steps to Reproduce
Just do a search in any typescript file and try to access getContinuation
Checklist

[x] I am running the latest version
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed
[x] I have provided sufficient information

The release is still not fixed

The release is still not fixed

Sorry about that — I labeled this as fixed because, technically, this has already been fixed; but only in the dev version. See #65.


installation issue on LinuxMint LMDE 2 Betsy

$ ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
libtoolize: copying file `build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
autoreconf: running: /usr/bin/autoconf --force
configure.ac:15: error: possibly undefined macro: LT_SYS_DLSEARCH_PATH
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:16: error: possibly undefined macro: LT_SYS_MODULE_EXT
autoreconf: /usr/bin/autoconf failed with exit status: 1

bash and libffi-dev are installed.
Any idea, why this occurs?

Hmm, LT_SYS_DLSEARCH_PATH should be available because of the minimum version check.
What version of libtool is this?

$ libtool --version
libtool (GNU libtool) 2.4.2
Written by Gordon Matzigkeit<EMAIL_ADDRESS>1996

I really have no idea, I downloaded 2.4.2 and that is defined:
$ grep 'AC_DEFUN.*LT_SYS_DLSEARCH_PATH' libtool-2.4.2/libltdl/m4/ltdl.m4
AC_DEFUN([LT_SYS_DLSEARCH_PATH],

Can you check if your ltdl.m4 looks sane? It's in /usr/share/aclocal/ on my system.

Well, there seems to be no package on my system that installs ltdl.m4:
$ dpkg-query --search  ltdl.m4
dpkg-query: no path found matching pattern *ltdl.m4*

Packages installing in /usr/share/aclocal:
$ dpkg-query --search '/usr/share/aclocal/*' | awk '{ print $1; }' | sort | uniq | rev | cut -c 2- | rev
autoconf-archive
gettext
gnome-common
gthumb-data
intltool
libexpat1-dev:amd64
libfreetype6-dev
libgconf2-dev
libglib2.0-dev
libgstreamer0.10-dev
libgtk2.0-dev
libgtk-3-dev:amd64
libtool
libwayland-dev
libxml2-dev:amd64
pkg-config
shtool
xfonts-utils
xtrans-dev

The file is missing. It does not get installed by the  libtool package:
$ dpkg --status libtool | grep Version
Version: 2.4.2-1.11
$ dpkg --listfiles libtool
/.
/usr
/usr/bin
/usr/bin/libtoolize
/usr/share
/usr/share/aclocal
/usr/share/aclocal/argz.m4
/usr/share/aclocal/ltversion.m4
/usr/share/aclocal/lt~obsolete.m4
/usr/share/aclocal/libtool.m4
/usr/share/aclocal/ltoptions.m4
/usr/share/aclocal/ltsugar.m4
/usr/share/libtool
/usr/share/libtool/config
/usr/share/libtool/config/install-sh
/usr/share/libtool/config/compile
/usr/share/libtool/config/ltmain.sh
/usr/share/libtool/config/depcomp
/usr/share/libtool/config/missing
/usr/share/doc
/usr/share/doc/libtool
/usr/share/doc/libtool/README.gz
/usr/share/doc/libtool/copyright
/usr/share/doc/libtool/NEWS.gz
/usr/share/doc/libtool/TODO.gz
/usr/share/doc/libtool/README.Debian
/usr/share/doc/libtool/AUTHORS
/usr/share/doc/libtool/changelog.Debian.gz
/usr/share/doc/libtool/THANKS.gz
/usr/share/doc/libtool/changelog.gz
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/libtoolize.1.gz
/usr/share/libtool/config/config.guess
/usr/share/libtool/config/config.sub

It does not get installed by libtool-bin either (Why two packages?):
$ dpkg --status libtool-bin | grep Version
Version: 2.4.2-1.11
$ dpkg --listfiles libtool-bin
/.
/usr
/usr/bin
/usr/bin/libtool
/usr/share
/usr/share/doc
/usr/share/doc/libtool-bin
/usr/share/doc/libtool-bin/copyright
/usr/share/doc/libtool-bin/changelog.Debian.gz
/usr/share/doc/libtool-bin/changelog.gz
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/libtool.1.gz

So, it is clear that the package manager refuses to install this file. Therefore, I just ransacked the file from https://raw.githubusercontent.com/frida/libtool/master/m4/ltdl.m4 and dumped it in /usr/share/aclocal, after which everything compiled and installed fine:
$ ls  -lh /usr/local/lib/ctypes.*
-rwxr-xr-x 1 root staff 922 May  2 23:17 /usr/local/lib/ctypes.la
-rwxr-xr-x 1 root staff 72K May  2 23:17 /usr/local/lib/ctypes.so

Thanks for the help! I think that the installation should be ok now.

That is very strange! That is definitely a bug with your distribution's libtool package, hopefully the maintainer will fix it if you file a bug with them.

In case someone gets a similar issue, you are supposed to install the libltdl-devpackage on Debian/Ubuntu to get ltdl.m4.

In case someone gets a similar issue, you are supposed to install the libltdl-devpackage on Debian/Ubuntu to get ltdl.m4.


bounty: Edwards-curve Digital Signature Algorithm (EdDSA)

Bounty description
Implement the Edwards-curve Digital Signature Algorithm (EdDSA) for ronkathon. EdDSA is a modern digital signature scheme, and this implementation should focus on the Edwards25519 curve variant.
Implementation requirements

[ ] Implement key generation for Ed25519 curve

Generate public / private key pairs
Ensure proper key formatting and encoding

[ ] Implement the EdDSA signing function, following the EdDSA specification for Ed25519

Implement proper message preprocessing
Generate valid signatures

[ ] Implement the EdDSA sig verification function
[ ] Implement proper error handling and input validation
[ ] Create comprehensive unit tests, including test vectors from the EdDSA specification;

Test various message lengths and edge cases

Bonus features

[ ] Add a benchmarking suite to test performance
[ ] Implement batch signature verification for improved efficiency

Resources
RFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA)
Curve25519: new Diffie-Hellman speed records
EdDSA for more curves
The Ed25519 signature scheme
Criteria
Bounties will be rewarded based on the following criteria:

Correctness and security: A thorough review of the implementation should convince our team that they are correct and secure, with all requirements met.
Code clarity and quality: Succinct, easy-to-follow code with appropriate naming conventions. Utilize Rust’s type system for flexibility and security (e.g., compile-time checks where possible), and avoid external crates. Optimizations should be a lower priority than clarity, but can be included behind a feature flag as a bonus.
Documentation quality: Provide comprehensive README’s, Cargo docs, and inline comments where code itself is not self-explanatory. Prioritize clarity and readability.

name: implementation of EdDSA
about: Implement the Edwards-curve Digital Signature Algorithm (EdDSA) for ronkathon. EdDSA is a modern digital signature scheme, and this implementation should focus on the Edwards25519 curve variant.
title: EdDSA implementation
labels: Bounty 💰
assignees:

Bounty description
Implement the Edwards-curve Digital Signature Algorithm (EdDSA) for ronkathon. EdDSA is a modern digital signature scheme, and this implementation should focus on the Edwards25519 curve variant.
Implementation requirements

[ ] Implement key generation for Ed25519 curve

Generate public / private key pairs
Ensure proper key formatting and encoding

[ ] Implement the EdDSA signing function, following the EdDSA specification for Ed25519

Implement proper message preprocessing
Generate valid signatures

[ ] Implement the EdDSA sig verification function
[ ] Implement proper error handling and input validation
[ ] Create comprehensive unit tests, including test vectors from the EdDSA specification;

Test various message lengths and edge cases

Bonus features

[ ] Add a benchmarking suite to test performance
[ ] Implement batch signature verification for improved efficiency

Resources
RFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA)
Curve25519: new Diffie-Hellman speed records
EdDSA for more curves
The Ed25519 signature scheme
Criteria
Bounties will be rewarded based on the following criteria:

Correctness and security: A thorough review of the implementation should convince our team that they are correct and secure, with all requirements met.
Code clarity and quality: Succinct, easy-to-follow code with appropriate naming conventions. Utilize Rust’s type system for flexibility and security (e.g., compile-time checks where possible), and avoid external crates. Optimizations should be a lower priority than clarity, but can be included behind a feature flag as a bonus.
Documentation quality: Provide comprehensive README’s, Cargo docs, and inline comments where code itself is not self-explanatory. Prioritize clarity and readability.

@0xJepsen this is my attempt at turning this into a proper bounty, please provide feedback or update the issue with this if appropriate!
cc: @Autoparallel + @thor314

Can I take this up? @0xJepsen

I am working on this is that is not an issue.

@mrdaybird can you compare your intention against: https://github.com/pluto/ronkathon/pull/125
I'd love to carry #125 across into main. Perhaps we can get EdDSA done alongside this?a

Assigned nonetheless

This sounds good to me. Go ahead and cook on what you're interested in cooking in :)
If there is a crossover episode into #125 that'd be based.

@brunny-eth Just pinging you since this is a bounty issue.

This is still a bounty. Bot removed a label inadvertently and I typoed the color formatting in the label 🤕


[NO MERGE] Test improvements

Pull request to test in .net continuous integration server.

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

:+1: :dancer:

retest this please


fixed MDM OMA-URI for CommercialID

fixed MDM OMA-URI for CommercialID
from Provider/ProviderID/CommercialID to the correct one Provider/MS DM Server/CommercialID

@okieselbach That value (MS DM Server) is only for Intune, but the sentence applies to generic MDM configuration. I changed the generic back and added a sentence about Intune

okay this is a complete description and the best way then, I like it!


Azure vm migration material

Hi Friends,
Could any body please share material related to migrating on premises vm to Azure.
Regards,
Sreedhar

Hi,
please fallow link
https://docs.microsoft.com/en-us/azure/site-recovery/migrate-tutorial-on-premises-azure

@Sreedhar, I think it's clear, pls close this issue.


it is still 111MB... can it possibly be smaller?

the React app is 300MB, and I remember at work, I got an external hard drive that was a PCI card type hard drive and it was 300MB capacity.
The Nano version, after npm i is still 111MB...  can it possibly be smaller, like 30MB?  111MB... the 3-D fish tank app in the early 2000s https://serenescreen.com/v2/ was only about 1.6MB.
video demo of it: https://serenescreen.com/v2/video/vid/hhd/18726_Mac_01_analog.mp4?v=2

I believe this is an issue of Javascript development in 2020 w/ NPM and its node_modules system. Your production build should be nowhere near that size however. Closing for now.


Automated cherry pick of #6782: fix: Add '/version' handler for notify

Cherry pick of #6782 on release/3.1.
#6782: fix: Add '/version' handler for notify

Codecov Report

Merging #6784 into release/3.1 will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           release/3.1   #6784   +/-   ##
===========================================
  Coverage         7.48%   7.49%
===========================================
  Files              585     585
  Lines            98953   98954    +1
===========================================
+ Hits              7411    7420    +9
+ Misses           90970   90961    -9
- Partials           572     573    +1

Flag
Coverage Δ

#aFlag
7.49% <0.00%> (+<0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudcommon/policy/resources.go
0.00% <ø> (ø)

pkg/cloudprovider/objectstore.go
2.51% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/guestdrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/compute/models/buckets.go
1.24% <0.00%> (ø)

pkg/compute/models/guestdisks.go
0.58% <ø> (+0.01%)
:arrow_up:

pkg/compute/models/secgroups.go
1.90% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/snapshots.go
1.56% <0.00%> (+<0.01%)
:arrow_up:

pkg/hostman/hostinfo/hostinfo.go
0.00% <0.00%> (ø)

pkg/hostman/isolated_device/isolated_device.go
3.22% <0.00%> (-0.06%)
:arrow_down:

pkg/util/rbacutils/policyset.go
75.00% <0.00%> (+9.78%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5591bbe...65b1fba. Read the comment docs.


Product variant "Storefront Presentation"-modal not loading when there are more than 500 PropertyGroups

PHP Version
8.3
Shopware Version
<IP_ADDRESS>
Affected area / extension
Platform(Default)
Expected behaviour
When you have more than 500 PropertyGroups, and you open the "Storefront presentation"-modal in the product-variant overview in the administration it should work all the time.
Actual behaviour
When you open the modal, it keeps being in a "loading"-state.

After some debugging it turns out the api limit shopware.api.max_limit, which is default 500, limits the results of the PropertyGroups.
It loads all PropertyGroups here:
https://github.com/shopware/shopware/blob/e591422fb2720dcd24d9646f61437a8d2c857a96/src/Administration/Resources/app/administration/src/module/sw-product/view/sw-product-detail-variants/index.js#L160
Then filters it here: https://github.com/shopware/shopware/blob/e591422fb2720dcd24d9646f61437a8d2c857a96/src/Administration/Resources/app/administration/src/module/sw-product/view/sw-product-detail-variants/index.js#L79
and the result of that is being passed down to the modal.
This means if the propertyGroup used to create the product-variants is loaded in, the modal will work. Otherwise it will keep being in a "loading" state.
How to reproduce

Create 1000 property groups
Have a shopware.api.max_limit-config of 500 (default Shopware)
Create a product with variants
Open the "Storefront Presentation"-modal

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-38113
[created from NEXT-38113, comment 491642]


Add predicate to Unique() filter

This should fix the issue #51

Codecov Report

Merging #52 into master will decrease coverage by 1.7%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #52      +/-   ##
==========================================
- Coverage   86.93%   85.23%   -1.71%
==========================================
  Files          15       15
  Lines         995      982      -13
==========================================
- Hits          865      837      -28
- Misses        130      145      +15

Impacted Files
Coverage Δ

src/library.jl
93.19% <100%> (+0.28%)
:arrow_up:

src/reduce.jl
67.85% <0%> (-27.06%)
:arrow_down:

src/simd.jl
75% <0%> (-9.38%)
:arrow_down:

src/processes.jl
91.11% <0%> (-1.49%)
:arrow_down:

src/core.jl
68.24% <0%> (-0.15%)
:arrow_down:

src/show.jl
94.87% <0%> (-0.05%)
:arrow_down:

src/comprehensions.jl
90% <0%> (+13.07%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 73c90d9...33d3ce2. Read the comment docs.

(It's kind of annoying that GitHub does not have multi-line suggestion...)
By the way, can check Allow edits from maintainers. next time so that I can push the change?  I think you see something like this in the right sidebar:

this seems like an endless process of checking for so few lines of codes!

I think it's good to go now.  Thanks for being patient :)

It's already set ?

Oh, it was?  Then maybe I can't push it through GitHub web UI.  I guess I'll try using my git client next time.


shell: Add shell_exec and shell tests

This adds shell_exec which can be used to execute commands directly
without the use of a console which is useful for both testing as well
as interfacing with applications/upper layer which would like to have
access to shell commands directly.
Signed-off-by: Luiz Augusto von Dentz<EMAIL_ADDRESS>

A couple of comments:
Make it super clear in the documentation that the shell commands are not a formal API or something that can be considered stable. I.e. anyone writing code that uses the command strings should be prepared for that code to stop working at some point.
Secondly, make it clear in the documentation that C string literals cannot be passed to this function because it modifies the input (by inserting nul characters to terminate each command line argument). Instead, the caller will need to do something like "char cmd[] = "my command"; shell_exec(cmd);"

@nashif Tests are now included.

As discussed in the previous patch by @Vudentz, using IP stack diagnostic functions is a more direct way. We don't have such functions well defined, but un-static-izing functions used by net shell was a first step in that direction.

These changes are definitely good improvements to the shell system, and yep, if direct access to net subsystem functions will be closed, can serve as a (somewhat hackish) fallback for that too.

Im not directly targeting any changes to net_shell.h right now, though this offer an alternative to having the callback handler exposed in headers like that I guess we need a proper discussion on what are the benefit vs shell_exec.


Traceparent is missed in CloudEventFactory.buildBaseCloudEvent

Traceparent from UCloudEventAttributes should be added to CloudEventBuilder if present.
Also it's missed in UCloudEvent.fromMessage()

@jefftindall  Thanks for taking this issue. However, the issue is not fully fixed, as mentioned in issue description,  traceparent is missed in UCloudEvent.fromMessage()

@jefftindall please address. sorry @dddj698 didn't verify that point

It was a test! 😄  @dddj698 passed 🏆
I have published a new PR after re-reading the issue in it's entirety.  Unit test updated as well.

@jefftindall  thank you!

Closing again :-)


fix(duckconfig): remove validation logic for unsupported old compiler

No longer necessary because currently support >=20180910.1.0.
https://github.com/cybozu/duck/blob/bf3515cde06b041238f4d5321a557880072d2815/package.json#L63

Codecov Report

Merging #752 (01c2b61) into master (bf3515c) will increase coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #752      +/-   ##
==========================================
+ Coverage   50.19%   50.29%   +0.09%
==========================================
  Files          24       24
  Lines        1040     1034       -6
  Branches      201      199       -2
==========================================
- Hits          522      520       -2
+ Misses        470      466       -4
  Partials       48       48

Impacted Files
Coverage Δ

src/duckconfig.ts
4.76% <ø> (-3.58%)
:arrow_down:


Alpha Scissor does not cast shadows with depth_draw_opaque, even though manually discarding does

Godot version
3.4.3.stable
System information
Windows 10, GLES3, GTX 980Ti
Issue description
As far as I understand, using alpha scissor should just discard transparent pixels, which means it should be able to cast shadows using "depth_draw_opaque", but it doesn't.

Alpha Scissor:
shader_type spatial;
render_mode depth_draw_opaque, cull_disabled;
uniform vec4 albedo : hint_color;
uniform sampler2D texture_albedo : hint_albedo;
uniform float alpha_scissor_threshold;

void fragment() {
	vec4 albedo_tex = texture(texture_albedo, UV);
	ALBEDO = albedo.rgb * albedo_tex.rgb;
	ALPHA = albedo.a * albedo_tex.a;
	ALPHA_SCISSOR=alpha_scissor_threshold;
}

Manual Discard:
shader_type spatial;
render_mode depth_draw_opaque, cull_disabled;
uniform vec4 albedo : hint_color;
uniform sampler2D texture_albedo : hint_albedo;
uniform float alpha_scissor_threshold;

void fragment() {
	vec4 albedo_tex = texture(texture_albedo, UV);
	ALBEDO = albedo.rgb * albedo_tex.rgb;
	if (albedo.a * albedo_tex.a < alpha_scissor_threshold)
		discard;
}

It seems that as soon as "ALPHA" gets set in a shader, even if it's just set to "1.0" shadow casting is disabled in "depth_draw_opaque" mode.
EDIT: I'm guessing the shader compiler looks for the ALPHA keywords and puts everything that has it in the transparent render queue? But if both ALPHA and ALPHA SCISSOR is present and depth_draw_opaque is set, I don't think it should send it to the transparent render queue.
Steps to reproduce
Try out the shaders listed above or open the attached project.
Minimal reproduction project
Alpha Scissor Tests.zip

What happens when you use ´depth_draw_alpha_prepass´ instead?

@Calinou Are you sure this should be catehorized as a bug? I am fairly certain that without the alpha depth prepass this is intended behaviour.

Well yes it works with depth_draw_alpha_prepass, my point is that it should work without, since there is no alpha, it's supposed to just be discarding.

I also agree with Arnklit that the transparent pipeline should not be used here. It lowers performance and causes transparency sorting issues.

I think I see what the problem is: The moment you use ALPHA in your shader SceneShaderForwardClustered sets uses_alpha to true, which in turn causes RenderForwardClustered::_geometry_instance_add_surface_with_material to not set the depth and shadow flags unless you also use depth_pre_pass.
I could make a PR to re-enable depth and shadows when people use ALPHA_SCISSOR in their shader code. If necessary people could still turn it back off with the depth_draw_never or depth_test_disabled flags.

I think I see what the problem is: The moment you use ALPHA in your shader SceneShaderForwardClustered sets uses_alpha to true, which in turn causes RenderForwardClustered::_geometry_instance_add_surface_with_material to not set the depth and shadow flags unless you also use depth_pre_pass.

While you are correct about 4.0, note that the bug report is for version 3.4.3 so you are looking in the wrong place :)

I could make a PR to re-enable depth and shadows when people use ALPHA_SCISSOR in their shader code. If necessary people could still turn it back off with the depth_draw_never or depth_test_disabled flags.

I'm not sure about this.
In GLES3 objects with alpha and alpha scissor should go down the opaque pipeline
https://github.com/godotengine/godot/blob/fd082ec39a2441b370d81de5895d24bc30a88a51/drivers/gles3/rasterizer_scene_gles3.cpp#L2281-L2283
https://github.com/godotengine/godot/blob/fd082ec39a2441b370d81de5895d24bc30a88a51/drivers/gles3/rasterizer_scene_gles3.cpp#L2326
In the MRP it is clear that the alpha-scissored mesh is going down the opaque pipeline (at least the prepass) as it is included in the SSAO.
Something else is going on here resulting in the material not getting drawn.

While you are correct about 4.0, note that the bug report is for version 3.4.3 so you are looking in the wrong place :)

True. But after noticing that this bug existed in 4.0 as well I decided to start there and then try to backport it once I have a working solution.


fix: Filter out null saved searches GRO-1525

After some exploration that I've documented in the Jira ticket, I'm left scratching my head but I can fix the problem by filtering out nulls. I think that's worth doing, right? I'm ccing the FX team here in case this rings any bells for them...
https://artsyproduct.atlassian.net/browse/GRO-1525
/cc @artsy/grow-devs @artsy/fx-devs

This is probably fine but if we have a staff account with a reliable repro, can we just log in to it and see what the issue is?
Like the problem here is that there's a null being returned in an array of otherwise normal alerts. I'd like to know how that's possible?

Thanks for kicking this discussion off!
tldr: I think we should add a mapping entry here in Metaphysics for "Textile Arts". That should work around the need for this explicit filter here.
I was able to isolate the problem by generating an access token in Gravity (essentially impersonating Isabelle's Artsy user) and reproducing the query using a local GraphQL client (Insomnia).
{
  me {
    email
    savedSearchesConnection(first: 10) {
      edges {
        node {
          labels {
            displayValue
          }
        }
      }
    }
  }
}

{
  "errors": [
    {
      "message": "Cannot return null for non-nullable field SearchCriteriaLabel.displayValue."
    }
  ]
}

Note that there is a partial result returned by Metaphysics but it looks like we error pretty hard even if one node in the list is not resolved. Is there an opportunity to degrade a bit more gracefully?
The SearchCriteria type is defined here in Gravity but these labels are added here in Metaphysics via stitching code (sorry).
We have a mapping of gene IDs to Medium Type here in Metaphysics which is intended to cover all of the options that would show up in the Medium artwork filter. I'm guessing that we're showing "Textile Arts" as a filter option either in Force or Eigen but because we're missing a mapping entry here, we're unable to fully resolve the filter labels via MP.

@dblandin — it's more than that; there's missing entries for:
Mixed Media
Architecture
Fashion Design and Wearable Art
Textile Arts
Posters
Books and Portfolios
Other

Which yes, obviously we'll expand the mapping but I'm not entirely sure how it's expected to keep this list in sync between our services.

@dzucconi As far as I known, we knowingly do not expose all medium types as filter options in collector-facing artwork grids.
This Notion page goes into some context.
I believe this mapping used to accurately describe which filter options were exposed to users. Seems to still be accurate on Force but I'm wondering if the logic in Eigen has changed (maybe via this PR?) to include more of those partner-facing mediums.
This comment in particular points to the known difference between option in the Medium facet on artwork grids and the full list of artwork medium types as chosen in CMS.

Actually, this might be due to the "Create alert" flow on artwork pages. I'm not sure if we disable or alter the alert criteria when the artwork's medium type is not one of the available filters.

Interesting, it seems like we should err on the side of inclusivity then though?

After some chatting we decided this was not a good enough solution and have transferred this ticket over to FX: https://artsyproduct.atlassian.net/browse/FX-4578

we knowingly do not expose all medium types as filter options in collector-facing artwork grids.
This Notion page goes into some context.

This one might be more illuminating  — more than you ever wanted to know about this mediums-vs-genes indirection:
https://www.notion.so/artsy/Medium-types-vs-medium-filters-39310c0278d64675b755e6db46fec363
Each ❌ in that doc corresponds to the ones highlighted by Damon above. Interestingly there is a little caveat about "Textile Arts" there.  I'll add these details to the new FX ticket.

😱


Deprecate this filter.

This filter was created to help users work around Elasticsearch 2.0-2.3 rejecting fields with dots in the name.
Elasticsearch 2.4 (I believe), and 5.0 now support dots in field names, so the original need for this filter has been resolved.
I propose deprecating and removing this filter.

I'm +1 on deprecating soon, and removing in 6.0.

Removing this seems resonable, i wonder though what is the upgrade path for production installations that are using these? We have hundreds, if not thousands, of dashboards that refer to de-dotted fields. There isn't an obvious upgrade path for dealing with the change over and as such we are currently still de-dotting even though elasticsearch supports the dotted fields.

There is still use in this filter for removing dots from fields that you don't to become sub fields. While Elasticsearch handles dots, it does so by transforming the field into objects. If you want to transform the dots into underscores, this filter is very useful (especially when you can't control the source data).


Service 403s should log with additional context and guide devs to success

Library or service name.
I'm primarily concerned with WebJobs extensions (Microsoft.Azure.WebJobs.Extensions.*). However, I think the more suitable place would be in the underlying service SDKs, with some more centralized standardization/enforcement in Azure.Identity or maybe Microsoft.Extensions.Azure.
Is your feature request related to a problem? Please describe.
Implicit use of DefaultAzureCredential in these libraries means that when developing locally, the developer's identity is used. We have repeatedly observed confusion among developers attempting to do so, and the SDKs should be guiding them toward success. The issue occurs because the developer may not actually have the role assignment they need, and there is no part of the experience that would tell them this, save for separately going to find documentation on it. However, the developer may still think they have the necessary permission, which is where this creates the most confusion. A simple example is someone with Owner role scoped to a storage account.
Here's a partial trace from that scenario in the context of Azure Functions:
[2021-08-06T17:53:21.207Z] An unhandled exception has occurred. Host is shutting down.
[2021-08-06T17:53:21.215Z] Azure.Storage.Blobs: This request is not authorized to perform this operation using this permission.
RequestId:edebec47-201e-0077-80eb-8aa449000000
Time:2021-08-06T17:53:20.7880023Z
[2021-08-06T17:53:21.220Z] Status: 403 (This request is not authorized to perform this operation using this permission.)
[2021-08-06T17:53:21.222Z] ErrorCode: AuthorizationPermissionMismatch
[2021-08-06T17:53:21.224Z]
[2021-08-06T17:53:21.226Z] Content:
[2021-08-06T17:53:21.229Z] <?xml version="1.0" encoding="utf-8"?><Error>AuthorizationPermissionMismatch<Message>This request is not authorized to perform this operation using this permission.
RequestId:edebec47-201e-0077-80eb-8aa449000000
Time:2021-08-06T17:53:20.7880023Z</Message></Error>
[2021-08-06T17:53:21.233Z]
[2021-08-06T17:53:21.235Z] Headers:
[2021-08-06T17:53:21.237Z] Server: Windows-Azure-Blob/1.0,Microsoft-HTTPAPI/2.0
[2021-08-06T17:53:21.241Z] x-ms-request-id: edebec47-201e-0077-80eb-8aa449000000
[2021-08-06T17:53:21.243Z] x-ms-client-request-id: f0b691cd-65d2-40a8-98fb-76aadc179fe1
[2021-08-06T17:53:21.245Z] x-ms-version: 2020-08-04
[2021-08-06T17:53:21.249Z] x-ms-error-code: AuthorizationPermissionMismatch
[2021-08-06T17:53:21.251Z] Date: Fri, 06 Aug 2021 17:53:20 GMT
[2021-08-06T17:53:21.253Z] Content-Length: 279
[2021-08-06T17:53:21.256Z] Content-Type: application/xml
[2021-08-06T17:53:21.258Z] .

The returned "AuthorizationPermissionMismatch" from the service helps only if you understand the requirements for the service. But someone with Owner might reasonably assume something else has gone wrong, as we've observed.
The feature request would be to identify these issues from the response and inform the user of the standard requirements for the operation. In the above, it would be great to also log:

The underlying source used by DefaultAzureCredential (and/or the OID of the principal) - note that this issue isn't limited to DefaultAzureCredential, though. That's just the common way to hit it. OID would be valid for all TokenCredential types.
The permission required by the operation. In this case Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read
The built-in roles which include this permission, such as Storage Blob Data Reader, Storage Blob Data Contributor, and Storage Blob Data Owner. Ideally, we focus on least privilege.
A link to relevant documentation

I believe the above would allow users to more quickly remediate this class of issue and move forward with whatever task was at hand.
CC @pakrym @fabiocav

Related https://github.com/Azure/azure-sdk-for-net/issues/22424

Adding to this, an indication of which resource was being accessed would also be necessary. In a situation where I'm connecting to multiple storage accounts, how do I know which one caused the error? Using the SDKs directly, I can figure this out largely from breakpoint debugging, but I'm dealing with indirect access in situations like the WebJobs SDKs. Concretely, the BlobTrigger for example references two storage connections, which could be configured to use different accounts.


Added spaceBetween prop to ActionButtonItem

Default is 15, but user can change that.

hey, can you update the readme file, so others now, this prop exists? thanks


[ClangImporter] Not all protocols adopted in ObjC come from ObjC.

So when sorting, don't just jump directly to the Clang decl and get its name, because there might not be a Clang decl; instead, use the objc attribute if there is one and the protocol's base name if not. We're not using ProtocolType::compareProtocols because we'd rather not depend on knowing for sure which Clang module a protocol lives in.
This wasn't caught until now because it required adopting a protocol in Objective-C that itself adopted (directly or indirectly) at least two protocols, at least one of which originally came from Swift.
rdar://problem/26232085

@swift-ci Please test macOS

@swift-ci Please smoke test Linux


[New] newline-after-imports: new option exactCount and docs update

Fixes #1901. Fixes #514.
Checklist

[x] option implementation
[x] tests
[x] docs update

added option named exactCount of type Boolean default false that will enforce strict following of the count option where the number of newline has to be equal to count.
Updated the docs as mentioned in the linked issue accordingly.

Coverage decreased (-2.08%) to 95.821% when pulling 3f05cdf671dcab3a466f0a1138ea9559c7f7b973 on anikethsaha:fixes-1913 into 13aa29c4d7a4c0fc86a1739d31c576c43150d4ce on benmosher:master.

This also fixes #514.

Looks like there's some test errors in eslint 2.

@anikethsaha Are you planning on merging this?

I would love this - any way I can help move it forward?

If someone wants to rebase this branch, fix the test errors, and post a link to the branch here (NOT a new PR, please!) then I can pull in the changes and we can get this merged.

I rebased, fixed conflicts, fixed eslint errors, and added a test using this in combination with the newer considerComments option. I ran npm test again and there's no issues with these specific files anymore (there's a few unrelated eslint warnings elsewhere which I didn't start fixing now). I don't know if there's more tests I could and should be running (I see your CI here runs a lot more tests than that). Anyway: https://github.com/reosarevok/eslint-plugin-import/tree/fixes-1913

alrighty, if the tests pass we can un-draft this and move forward

@reosarevok the tests are still failing in eslint 2, pretty consistently, about the autofix output. it would be ideal to figure out how to get them passing in eslint 2.

The travis failure is because they're on an outdated nvm, and npm 10 breaks on node 14; appveyor's WSL failures are expected. Once the rest of the appveyor tests pass, I'll land this.

There's a comment related bug with this; I've filed a new bug since this is already merged.


Document how to recover from Error: another operation (install/upgrade/rollback) is in progress

If the helm chart upgrade is interrupted the Error: another operation (install/upgrade/rollback) is in progress operation persists preventing further deployment. It should be possible to recover from this by executing a helm rollback command. I do not know how to execute this command
Cf- https://stackoverflow.com/questions/71599858/upgrade-failed-another-operation-install-upgrade-rollback-is-in-progress

In a local test deployment what worked for me was running:
kubectl get secret -A | grep jupyterhub
This returns a list like
dev              nebari-jupyterhub-sftp                                              Opaque                                2      8d
dev              nebari-jupyterhub-ssh                                               Opaque                                1      8d
dev              sh.helm.release.v1.jupyterhub-dev.v1                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v2                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v3                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v4                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v5                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v6                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v7                                helm.sh/release.v1                    1      1d

then find the the one with the greatest version (in this example sh.helm.release.v1.jupyterhub-dev.v7), then running:
kubectl delete secret sh.helm.release.v1.jupyterhub-dev.v7

This only addresses a specific case for jupyterhub (though those files do exist for each release), I was going to suggest the same as what you found in that stack overflow answer. In k9s you can inspect the helm releases and installed services by visiting out to :helm.
Its heavily advised to be careful with rolling back changes, since depending on the version you are moving towards you might end up losing resources specific to a range of versions (e.g a volume that has been integrated since a certain version)


Not working on Chrome?

I installed BetterDiscord on Chrome from the site but when I go to Discord I don't see any settings for BetterDiscord at all

If the emotes are showing then it works, the browser versions only support showing emotes for now (no settings or anything else).

Oh ok the emotes do work I didn't know settings didn't work yet for browser version


Code that doesn't understand

I am a novice swift developer, can you tell me how to understand the "" in "|> .backgroundColor .~ UIColor.white"

Hi there, |> is the pipe forward operator and .~ is the set operator. The definition for |> is here and .~ here.
|> forwards a value to a function, so using the example:
button |> \.backgroundColor .~ .white

We are forwarding the value button to the function returned from \.backgroundColor .~ .white.
The syntax is a little hard to read at first if you're unfamiliar with these concepts, this in particular refers to something called Lenses. If you're interested I would suggest these resources:
Talk on Lenses: https://www.youtube.com/watch?v=ofjehH9f-CU
PointFree: https://www.pointfree.co/


Currency and SIP Calculator Dark Mode missing

I want to work on this issue under JWOC

@TuhinBanerjee31 Go for it. Do it only for Currency converter. SIP calc dark mode is under processing.

Okay


dts: bindings: rename nxp,kinetis-ftm and nxp,kinetis-ftm-pwm compatibles

Rename "nxp,kinetis-ftm" and "nxp,kinetis-ftm-pwm" compatibles to "nxp,ftm" and "nxp,ftm-pwm", respectively, to remove the
device family from its name because this hardware block is used in multiple NXP devices from different families.
Also relocate "nxp,ftm" binding to timer bindings because NXP FlexTimer Module is a configurable timer peripheral and right now is wrongly placed under Arm bindings.

unrelated CI failures due to zephyr/include/generated/zephyr/syscalls/random.h:37: undefined reference to z_impl_sys_rand_get'`.. I'm looking at it

unrelated CI failures due to zephyr/include/generated/zephyr/syscalls/random.h:37: undefined reference to z_impl_sys_rand_get'.. I'm looking at it

rebased to fix CI issues :crossed_fingers:

rebased to clear CI issues

Tried restarting CI

Appears to be an issue with building the shield for BT? https://github.com/zephyrproject-rtos/zephyr/actions/runs/12289202979/job/34564981997?pr=82195#step:12:911

We should probably consider if any of these work?
https://github.com/zephyrproject-rtos/zephyr/blob/87b08cc5bb966eb83ddb491491ab5d844117dee1/samples/bluetooth/peripheral_ht/sample.yaml#L15-L21

Appears to be an issue with building the shield for BT? https://github.com/zephyrproject-rtos/zephyr/actions/runs/12289202979/job/34564981997?pr=82195#step:12:911
Seems to stem from: a4b9ef6

it's still the same issue as reported above, I will rebase after https://github.com/zephyrproject-rtos/zephyr/pull/82859

Appears to be an issue with building the shield for BT? zephyrproject-rtos/zephyr/actions/runs/12289202979/job/34564981997?pr=82195#step:12:911
Seems to stem from: a4b9ef6

it's still the same issue as reported above, I will rebase after #82859 is merged

PR merged. I've rebased this PR for you.

Cool :)

fixed the merge conflict


Update dependencies and apply recommendations based on updates

This pull request updates all dependencies, removes outdated dependencies, and applies recommendations based on the updated dependencies.

📝 Changed routes:

/

(view full size)

Commit e5a9e5f8be05d5afe6212f4dbbdbcf4d8ee5ebba (https://getkapco-fm3jt6adv-kap.vercel.app).


Use glk

Port ZVM to use Glk as its output system. Match Quixe for the general API.
Possibly develop a JS terminal Glk implementation for use as a terminal interpreter.

@erkyrath I'm starting to port ZVM to use Glk, and have a couple of questions.
How would you feel about renaming the init() function of Quixe to start()? My class system uses init for constructors. At the moment I'm overwriting the init function so it's not a big issue.
Should ZVM stop buffering text and let Glk handle that?

Sorry, I let this slip...
I don't want to rearrange the function names in the Quixe interface just for this. You could rename them at load time, e.g. say Quixe.originit = Quixe.init and go on from there.
Yes, Glk is enthusiastic about buffering output so the VM doesn't have to.

Yeah renaming at run time is easy.
The conversion has been surprisingly easy! The next thing to do is the status window functions, which I had previously just handed off to Parchment to do. I noticed from Bocfel that even something like keeping track of the cursor has to be done manually.

In the future I'd like to get better style support, but for now I think Glk support is pretty much complete.

Ok, cool.


Cannot use dynamic baseUrl endpoint

Describe the bug
A clear and concise description of what the bug is.
Almost Same as #355, but the solution is not working.
I want to use dynamic baseUrl which provides by the user, and tried to pass it through factory method but it did not work.
I don't want to have const url, and I want to get base url from shared preferences.
Can you please help me with this?
Thanks

as soon as I change It to const string, it works

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

You can specify a dummy base url and have a Dio interceptor (https://pub.dev/documentation/dio/latest/dio/Interceptor-class.html) to rewrite if for every request.

Can you please explain more?
How to add it ?
Thanks

import 'package:dio/dio.dart';

class URLInterceptor extends Interceptor {

  @override
  void onRequest(RequestOptions options, RequestInterceptorHandler handler) {
    handler.next(options.copyWith(baseUrl: 'whateveryouwant'));
  }
}

ApiClient create() {
  final dio = Dio(BaseOptions(contentType: 'application/json'));
  dio.interceptors.add(URLInterceptor());

  return ApiClient(dio);
}


Remove duplicate drafts for specialist publisher.

A bunch of these were created a while ago when we
restructured the database.  They need to go away
so that things don't show as "redrafted" when they
aren't really.
Before:
ContentItemFilter.new(scope: ContentItem.where(publishing_app: "specialist-publisher")).filter(state: "draft").count
=> 14912

ContentItemFilter.new(scope: ContentItem.where(publishing_app: "specialist-publisher")).filter(state: "published").count
=> 14843

During:
Deleting duplicate draft #222886 (423b74de-18b6-412b-878d-5f3511693a7b)
Deleting duplicate draft #214094 (dd47dae6-dd09-486d-bf1b-f256ac0cead2)
Deleting duplicate draft #220998 (ae1c9e54-a7d2-40bc-823c-a0dcbecd02ee)
Deleting duplicate draft #297432 (2a557115-00a9-44b9-b74e-d2be3e756a5b)
Deleting duplicate draft #219545 (0c180eb7-9b86-4eb2-9fe8-af4f05f961d6)
Deleting duplicate draft #225890 (2f573873-7db2-4243-bf02-d02c313518fd)
Deleting duplicate draft #220838 (da36c3b7-e448-42c5-9551-e73768526da3)

... many others ...

Deleting duplicate draft #226700 (6f683588-3a2c-48d6-ab88-c82d1172d020)
Deleting duplicate draft #223640 (81130353-a0f9-4bfa-87ac-634adc05b83d)
Deleting duplicate draft #216541 (8e3e642e-6589-47d8-a8b3-2bb939cc8286)
Deleting duplicate draft #224201 (4b5a301b-d200-4d7a-8c5e-dc91db218277)
Deleting duplicate draft #427050 (7738c361-e2bf-484d-96d9-bba68036e3b0)

After:
ContentItemFilter.new(scope: ContentItem.where(publishing_app: "specialist-publisher")).filter(state: "draft").count
=> 644

ContentItemFilter.new(scope: ContentItem.where(publishing_app: "specialist-publisher")).filter(state: "published").count
=> 14843

@benilovj @tuzz Could your team confirm that this is the right number of drafts to be left over?  (these numbers based on a bit of an old dataset)

Had a look in specialist-publisher after a data replication and we get these numbers:
SpecialistDocumentEdition.where(state: "draft").count
#=> 617

SpecialistDocumentEdition.where(state: "published").count
#=> 14788

So those numbers reported seem like the right ballpark. Your numbers are higher, too, which seems safer.

OK.  Once this is on integration I'll check again against specialist publisher.

Are there any other document types we should be checking? Although specialist-publisher is most visibly affected because it's using the publishing-api to show the state of all its content items, it seems likely that the duplicate draft issue exists for other content too, which might have undesirable effects further down the line.

@danielroseman Yeah that occurred to me too.  Perhaps we should do this one which is relatively well contained, and once everyone's happy with it adjust the rake task to run on everything.

Though that said, any brand new drafts will be caught by this, so requires a bit of careful thought.

@danielroseman I've restricted this run to the period around the migration and updated the output above.
Seems to have had much the same effect and was much quicker to run.


Document how this works with Vite

I can't quite grock how this interacts with the project bundler and guess others might also wonder.
A specific question is if the framework code is dynamically loaded how does it get bundled so is only loaded for the first hydrated component. Or is this somehting all bundler can support?
To be honest, right now I just care about vite_js (ie rollup) :)

I tested these 3 methods and they all work fine with Vite (and with the Eleventy Vite plugin)!
<!-- direct reference to node modules -->
<script type="module"<EMAIL_ADDRESS>
<!-- bare specifier -->
<script type="module">
import "@11ty/is-land";
</script>

<script type="module" src="./external-file.js"></script>
<!-- where external-file.js declares `import "@11ty/is-land";` -->

I would warn that this did not work in Vite (nor in Eleventy Vite):
<script type="module" src="@11ty/is-land"></script>


to add new templates

"it's complicated to add new templates. I'm searching for an easier way".        i want to add the new slide ,but i don't know how to do it  If you know how to do it, please tell me

Hey there!
You want to just add a new slide to your generated presentation? Not to create a new template?
If this really is just the case, open it with powerpoint and... add it?
On the top left there is a "add slide" button.
In case you want to create a new template, it's a bit hard and complicated to provide a step by step tutorial but here is what you basically need to do:

In PowerPoint, create a new powerpoint with a template. Then delete every slide. Then you need to check if your template has the following layout indicies which are defined in the app.py script:
layout_indices = [1, 7, 8]
1.1 You can check this by clicking new slide and you will see if the structure (title and content) of the powerpoint matches these indices.
Export the powerpoint without a slide (every slide deleted) and name it for example Design-8.pptx.
Add the option to the script to check if the number is greater than 8 instead of 7.

Hope this somehow works. - You need to understand how the code works to do this correctly I think.
Kind regards,
Timon Käch

Hello,
Thank you for sharing this code. I have a similar project, but in my project, it needs to first learn from previous PPTs and, after that, create a new PPT based on user prompts while maintaining the same template.
How can I solve this? Can you help me?
Regards

Hello
Sorry for the late reply. This is quite difficult to implement as I would first have to implement the logic to create new slides from the same template/style.
I don't plan to do this at the moment.
Thank you for your understanding and kind regards,
Timon Käch

Hello
Sorry for the late reply. This is quite difficult to implement as I would first have to implement the logic to create new slides from the same template/style.
I don't plan to do this at the moment.
Thank you for your understanding and kind regards, Timon Käch

Thank you for response. I am still trying the solution but it is difficult :(


Promscale fails to start with error: could not acquire schema version lease. is a migration in progress?

Hi,
Recently I updated my timescaledb+promscale packages from:
promscale_0.3.0_Linux_x86_64
postgresql_version: 12.6-1.pgdg100+1
timescaledb_version: 2.2.0~debian10
promscale_extension: 0.1.1

to
promscale_0.10.0_Linux_x86_64
postgresql_version: 12.10-1.pgdg100+1
timescaledb_version: 2.6.0~debian10
promscale_extension: 0.3.0

OS is Debian 10 and all packages are installed from apt repos except promscale_extension which is installed from source and promscale is downloaded as binary (Linux_x86_64)
Now trying to start promscale as before I get this error:
Feb 23 17:31:25 timescaledb promscale_0.10.0_Linux_x86_64[15964]: level=error ts=2022-02-23T16:31:25.705Z caller=runner.go:101 msg="aborting startup due to error" err="could not acquire schema version lease. is a migration in progress?"
And I see this long query stuck running on postgresql:

query | CALL _prom_catalog.execute_everywhere('create_prom_modifier', $ee$               +
      |     DO $$                                                                        +
      |         BEGIN                                                                    +
      |             CREATE ROLE prom_modifier;                                           +
      |         EXCEPTION WHEN duplicate_object THEN                                     +
      |             RAISE NOTICE 'role prom_modifier already exists, skipping create';   +
      |             RETURN;                                                              +
      |         END                                                                      +
      |     $$;                                                                          +
      | $ee$);                                                                           +
      |                                                                                +
      | CALL _prom_catalog.execute_everywhere('create_prom_admin', $ee$                  +
      |     DO $$                                                                        +
      |         BEGIN                                                                    +
      |             CREATE ROLE prom_admin;                                              +
      |         EXCEPTION WHEN duplicate_object THEN                                     +
      |             RAISE NOTICE 'role prom_admin already exists, skipping create';      +
      |             RETURN;                                                              +
      |         END                                                                      +
      |     $$;                                                                          +
      | $ee$);                                                                           +
      |                                                                                +
      | CALL _prom_catalog.execute_everywhere('create_prom_maintenance', $ee$            +
      |     DO $$                                                                        +
      |         BEGIN                                                                    +
      |             CREATE ROLE prom_maintenance;                                        +
      |         EXCEPTION WHEN duplicate_object THEN                                     +
      |             RAISE NOTICE 'role prom_maintenance already exists, skipping create';+
      |             RETURN;                                                              +
      |         END                                                                      +
      |     $$;                                                                          +
      | $ee$);                                                                           +
      |                                                                                +
      | CALL _prom_catalog.execute_everywhere('grant_prom_reader_prom_writer',$ee$       +
      |     DO $$                                                                        +
      |     BEGIN                                                                        +
      |         GRANT prom_rea

Tried even with version 0.9.0 and it throws the same error.
Can you tell how to solve this issue?
Thanks

I tried to stop/start this specific process and also the whole postgresql server, tried to use different promscale binary versions (e.g promscale_0.6.2_Linux_x64_64) and the executable seems to be stucked without listening to port 9201 and the same query can be shown on postgresql pg_stat_activity.
Is there any way to tell if this is a normal migration/upgrade process or if there is any issue?

I used promscale_0.6.2_Linux_x86_64 and let it run for a long time (more than 8 hours) and afterwards promscale showed this error:
Feb 24 05:39:20 timescaledb promscale_0.6.2_Linux_x86_64[16294]: level=error ts=2022-02-24T04:39:20.295Z caller=runner.go:50 msg="aborting startup due to error" err="migration error: Error while trying to migrate DB: Error encountered during migration: error executing migration script: name versions/dev/0.5.2-dev/1-downsampling.sql, err ERROR: deadlock detected (SQLSTATE 40P01)
How can I ensure that the migration finishes successfully?

Hey @enidvrenozaj just wanted to let you know we are looking into this issue, will try to get back to you as soon as possible.
Thanks!

Hi @antekresic thank you for your feedback.
Just want to update on the issue that after leaving the promscale binary running without any output for more than 8 hours now I can see metrics being pushed to promscale v0.6.2.
I wonder if I can go directly to version 0.10.0 or should I use some intermediary versions?

And after starting correctly version 0.6.2 I could just run version 0.10.0 without any issues and without waiting a long time.
I guess the issue was going from 0.3.0 to 0.6.x probably?

Yeah, I think there was some issue going from lower versions to 0.6 . I suggest moving to 0.10 definitely and I would be surprised if you had any issues migrating to it. Do let us know if the issues persist.

Yes indeed, seems to be ok until now. Will update you in case I encounter any issue.
Thank you


Update wake-word.md - training for snowboy

Since Kitt-AI have discontinued snowboy, there is a forked, free, offline training program available, so I updated the documentation to point to this.

Thanks!


GROOVY-5283 Add a collate method to List

I have often found a need for collating or partitioning a List into a List of sub-lists of a given size.
This question has been asked on StackOverflow a couple of times as well
ie:
[1,2,3,4,5].collate( 3 ) == [ [ 1, 2, 3 ], [ 4, 5 ] ]

This could be chained to generate a multi-dimensional list of lists, ie:
(1..9).collate( 3 ).collate( 2 ) == [ [ [1,2,3], [4,5,6] ],
                                      [ [7,8,9]          ] ]

Hope the pull request is ok...  I think I covered all bases with my tests

Thanks again for a great contribution ;-)


BUG: subscribe to our newsletter has two Email address inputs.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The subscribe to our newsletter has two input fields asking for the same input i.e. email address. This needs to be fixed.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

I want to work on this issue.
Can you please assign it to me?


[Apple Reminders] Weekdays options for recurring reminders

Extension
https://www.raycast.com/raycast/apple-reminders
Description
Sometimes I need to create a recurring reminders only for weekdays, but it's not currently possible on the Create Reminder command. When I need to do so, I use the Reminders app where it's possible, not only weekdays reoccurrences, but also set hourly, weekends and other options for recurring reminders.
Who will benefit from this feature?
Everyone
Anything else?
The current options

In green 🟢, the options I think it could be added to the extension. In blue 🔵, what already can be done in the extension.

Thanks for the feature request. Would you like to work on it? If yes, here's our guide on extension contributions so that you can open up a pull request. Feel free to contact me here or in the Slack community if you need further help.


Channel restriction

Hi ! This is my first issue and I'm not sure how github works. Sorry if I got it wrong. I suggest adding channel restriction for slash commands.

This is not a bot feature by itself, this has to be done through integration options of the channel.


Benchmark redb vs LMDB

Add a feature that makes ord use LMDB as its backend, and benchmark redb vs lmdb backend for indexing speed and space usage.

This is done, we ran the benchmarks, and redb and lmdb had nearly identical space-usage. lmdb was way faster, but that's probably because they don't fully fsync.

Also, I checked, and indexing isn't faster even if all database writes are commented out, indicating that database write speed isn't a bottleneck. We're probably bottlenecked on reading blocks from bitcoin core.


Table: Storybook fix for checkbox preselected row issue

Description

References
Fixes  #1983
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update

How Has This Been Tested?

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings

@prashanthr6383 I can still reproduce the issue by selecting couple of rows and changing a prop, if the selection gets reset during re-render then it is fine but that's not the case here so we have to find out the root cause of this issue.