Feature Request: 180 degree 3d camera presets for VR [$100]

Currently the environment camera does a good job of generating panoramic scenes in 360 degree view for VR. With a camera offset of a ~65mm interpupillary distance, two panoramic renders can be stitched together top-bottom style in any given image editing program to generate convincing 360 degree 3D in VR. It would be nice if there was a setting to automatically bake this into one 1:1 aspect ratio image.
What's really missing at the moment is a 180 degree 3D VR preset, or at least some way to input numbers to be able to get one. I'm relatively new to VR rendering, but I believe the image would be a 2:1 aspect ratio image with the left eye's 180 degrees of vision on the left half of the image and the right eye's 180 degrees of vision on the right half of the image. I believe this should have the barrel distortion post production flagged to enable by default.
After skimming the source code, I notice there is a "stereo" camera type that blendluxcore doesn't know about. This seems to have a framework for 180 degree VR already in it, though the default field of view is too small and seems to be unaffected by the Field of View section of the scene binary.
I'm putting a $100 bounty on any workable implementation of a 180 degree VR preset at the scene binary level.  Blender integration and configurable interpupillary distance would be a nice bonus. If this is already possible with the current tools I'm open to advice.
These links may provide useful reading for 3D resolutions and standards:
https://creator.oculus.com/blog/encoding-high-resolution-360-and-180-video-for-oculus-go/?locale=en_US
https://developer.oculus.com/documentation/native/pc/dg-render/?locale=en_US

There is a $100 open bounty on this issue. Add to the bounty at Bountysource.

Currently the environment camera does a good job of generating panoramic scenes in 360 degree view for VR. With a camera offset of a ~65mm interpupillary distance, two panoramic renders can be stitched together top-bottom style in any given image editing program to generate convincing 360 degree 3D in VR. It would be nice if there was a setting to automatically bake this into one 1:1 aspect ratio image.

This should be easy to add.

What's really missing at the moment is a 180 degree 3D VR preset, or at least some way to input numbers to be able to get one. I'm relatively new to VR rendering, but I believe the image would be a 2:1 aspect ratio image with the left eye's 180 degrees of vision on the left half of the image and the right eye's 180 degrees of vision on the right half of the image. I believe this should have the barrel distortion post production flagged to enable by default.

However, here, you talk about 180 degree while, in previous statement, you were talking of 360 degree views. Which one you are looking for ? Both ?
You are also adding the request of barrel distortion support. This can be quite tricky. Does Oculus provide a post-processing tool to apply barrel distortion to any image/video ? It sounds like something they should offer (and it would avoid the work to directly support barrel distortion).

I'm really looking for the 180 degree. I was just mentioning how close the 360 degree panoramic is to already facilitating it.
There's already a bool for barrel distortion in the code and when flagged it operates as expected. I think I was incorrect about the 180 degree barrel distortion being needed on the 180 degree renderings though. Upon further research it seems that it is applied at the headset level.

Ok, so it is something like the current stereo camera but with 2 x 180 degree panoramic views. I'm not sure when I will have the time to work on it but it should be quite easy to add and I should add it soon.

Terrific. I have an oculus quest headset to test on whenever it makes it in.

Did some 180 degree renderings yesterday using the panoramic camera. The middle square of a 2:1 aspect ratio panorama view is the correct behavior for a 180 degree view. Offset by 65mm with no change to yaw/pitch/roll achieves a good stereoscopic depth effect. Nothing really new here, just confirming things work as we thought they did.

I added the support for 360 degree view to stero camera.
It requires only to add to the scene a new camera property:
scene.camera.stereo.type = environment
Or (the default for normal 2x perspective cameras):
scene.camera.stereo.type = perspective
This is a rendering with perspective stereo camera (like 2x perspective cameras):

And this is the same scene with 360 degree camera (like 2x environment cameras):

I can add the support for 180 degree cameras too if of any use.

For 180 degree VR it's two 1:1 aspect panoramas with the left eye on the left and the right eye on the right for 2:1 image aspect ratio total.
For 360 degree images two 2:1 panoramas are stacked vertically with the left eye on the top and the right eye on the bottom for 1:1 image aspect ratio total.
If I'm interpreting what I'm seeing correctly, what you've done will work fine if the cameras are changed to be 180 instead of 360. This is the format that is important to me personally.
A 360 degree version would be a logical option as well, since both formats are used; however the frames will need to stack vertically as described earlier.

I added the supported for 180 (horizontal stacked) and 360 degree (vertical stacked) stereo camera.
With "scene.camera.stereo.type = perspective":

With "scene.camera.stereo.type = environment_180":

And with "scene.camera.stereo.type = environment_360":

At a glance the 180 looks correct, I'll have a chance to look in an actual headset later today.
For the 360, at a glance, the aspect ratio of the eyes seems a bit wide. After the two 2:1 aspect ratio images are stacked the final image resolution should be square at 1:1.

The image resolutions are the one of the original (no stereo image): 1280 x 800
If you render at the correct resolution, you should get the correct output (800x800):

Cool! Last couple days have been hectic but I'll be trying this on a headset soon. At a glance things are looking good.

I got the latest version of Luxcore 2.5 alpha compiled today. Using blender to export the scene, everything works fine if I export a scene binary; however if I export the scene as text, luxcoreUI no longer sees my largest scene object (4.9 meg of geometry). It reports .3k tris instead of 49.9k tris it reports when rendering the .bcf
Because blender does not yet know about this new camera type, I am unable to render my test scene to look at in VR.
Any thoughts on why a blender text export and binary export would not produce identical behavior in luxcoreui?

Can you post a test .blend scene showing the problem and the exported scene text files ? So I can check them here.

Certainly. Here is the blender scene in question as well as a zip file of a .bcf and text export of the scene. If I had to take a wild guess, it's not interpreting the clip end value that excludes far away objects correctly.
Scene VR camera test2_LuxCore.zip
Scene VR camera test2.zip

It is still a localization related problem, if you open the mesh-00002.ply file, you will see:
comment Created by LuxRays v2.4
element vertex 148,426
property float x
property float y
property float z
property float nx
property float ny
property float nz
element face 49,506
property list uchar uint vertex_indices
end_header

Notice the "," inside "148,426" and "49,506". Notice also the "LuxRays v2.4" in the first line. It think you have not correctly updated your BlendLuxCore installation.
If I load your .blend and export the scene, I get:
comment Created by LuxRays v2.5beta1
element vertex 148426
property float x
property float y
property float z
property float nx
property float ny
property float nz
element face 49506
property list uchar uint vertex_indices
end_header

and it works fine.
Try to update your BlendLuxCore installation (may be, delete the BlendLuxCore directory first so you are sure to do a clean installation).

I figured a scene binary would be forward compatible. Will hop on blendluxcore 2.5 later and see what happens. Thanks!

I had a bunch of stuff come up and still haven't had a chance to look at this. You can go ahead and collect the bounty it looks accurate enough in the attached screenshots. Thanks for your work!

Ok, closing this.


AmbiguousBlockAssociation False Positive

Lint/AmbiguousBlockAssociation cop raises a false alarm against non-dubious block association.
Example Code
assert_equal site.posts.find { |p| p.title == "Foo Bar" }, results.first

Expected behavior
Does not expect Rubocop to flag the code above and even if it did, I expect the message to tell me to parenthesize the param to associate the block with find call.
Actual behavior
W: Lint/AmbiguousBlockAssociation: Parenthesize the param find to make sure that the block will
be associated with the assert_equal method call.
        assert_equal site.posts.find { |p| p.title == "Foo Bar" }, results.first
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Steps to reproduce the problem
Run rubocop against following:
assert_equal site.posts.find { |p| p.title == "Foo Bar" }, results.first

RuboCop version
Include the output of rubocop -V. Here's an example:
$ rubocop -V
0.48.0 (using Parser <IP_ADDRESS>, running on ruby 2.3.3 i386-mingw32)

(Also tested with latest master branch)
(similar issue: Comment by @stephengroat)
/cc @smakagon

@ashmaroli thanks for reporting. Created Pull Request that fixes this case.


Attribute error - Async

The problem
Issue with Async in HA OS 10+
Tested with 10 and 10.1
What version of this integration (ha-nest-protect) has the issue?
0.3.12
What version of Home Assistant Core has the issue?
Home Assistant 2023.5.0 Supervisor 2023.04.1 Operating System 10.1 Frontend 20230503.1
Device / Model
No response
Diagnostics information
Logger: homeassistant.config_entries
Source: custom_components/nest_protect/init.py:126
Integration: Nest Protect (documentation, issues)
First occurred: 7:36:13 AM (1 occurrences)
Last logged: 7:36:13 AM
Error setting up entry Nest Protect for nest_protect
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/nest_protect/init.py", line 126, in async_setup_entry
hass.config_entries.async_setup_platforms(entry, PLATFORMS)
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'
Home Assistant log
No response
Additional information
No response

Having this exact issue as well.

I think you guys should check https://github.com/iMicknl/ha-nest-protect/issues/224

Duplicate of #224.

Agreed did not see. Thank you resolved

From: Mick Vleeshouwer @.>
Sent: Thursday, May 4, 2023 8:55:21 AM
To: iMicknl/ha-nest-protect @.>
Cc: thatguy55 @.>; Author @.>
Subject: Re: [iMicknl/ha-nest-protect] Attribute error - Async (Issue #225)
Duplicate of #224https://github.com/iMicknl/ha-nest-protect/issues/224.
—
Reply to this email directly, view it on GitHubhttps://github.com/iMicknl/ha-nest-protect/issues/225#issuecomment-1534729003, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOP4E7BTDKNMZTVJ6SSB7NLXEORLTANCNFSM6AAAAAAXVXTOFY.
You are receiving this because you authored the thread.Message ID: @.***>


enforce checkpoints

Resolves #3337.
Added a new signal pre_accepted_block (as well as the corresponding channel which is not currently used)  which is emitted from controller_impl::push_block prior to any stateful changes occurring in that function.
Added a new class of exceptions that inherit from controller_emit_signal_exception. This class of exceptions is allowed to bubble out of the emit call in controller. Anytime an exception which derives from controller_emit_signal_exception is used, we need to be careful that it being thrown does not cause the originating emit call to leave controller in an inconsistent state.
The new checkpoint_exception which does inherit from controller_emit_signal_exception is only potentially thrown from the synchronous signal handler of pre_accepted_block within chain_plugin. Therefore, it can only currently bubble up from the emit call of the pre_accepted_block signal in controller_impl::push_block which is safe since it does not leave things in an inconsistent state. All it does if thrown is reject the block that was trying to be pushed.
This new exception is thrown if there is a mismatch between the block ID of the pushed block and the checkpoint block ID that may be set for that block number. The code to load this checkpoint information from the config or CLI options was already implemented prior to this PR.

Checkpoints
The DPOS consensus mechanism is designed to prevent two incompatible blocks from becoming final (irreversible) under the assumption of non-byzantine behavior by more than two-thirds of active block producers. Producers are economically disincentivized from byzantine behavior due to the fact that it is trivial to cryptographically prove byzantine behavior (double signing incompatible blocks) and because the likely consequences to a maliciously byzantine block producer is, at a start, loss of future block producer income.
However, in the unlikely case that sufficient byzantine behavior occurs anyway, it is possible for there to a be fork in the blockchain that tricks newly synchronizing nodes to follow the blockchain down the "wrong branch" and get stuck there. In such scenarios, it is necessary for the node operators to manually intervene using trusted checkpoints they obtain from their social network in order to get back into consensus with the rest of the network. These checkpoints should be specified by the node operators and enforced by nodeos without any source code changes necessary.
Specifying checkpoints
Checkpoints can be specified in the config.ini file or via the command line in the form of [BLOCK_NUM, BLOCK_ID] where BLOCK_NUM is a positive integer specifying the block number and BLOCK_ID is a string containing the hex encoding of the expected block ID.
Here is an example of two checkpoints on blocks 8 and 20 specified in the config.ini file:
# Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints. (eosio::chain_plugin)
checkpoint = [8, "00000008932161ed022c329eaec93a1922e43afb175c458db88776c0718240ea"]
checkpoint = [20, "00000014bd0765ff8c828abb91a021a04525ab344bffdc6165c65000e7bc7823"]

Checkpoint enforcement
Checkpoints are enforced during the operation of pushing a block onto the chain. This operation occurs as new blocks are considered during synchronization and normal operation of nodeos in which the blocks are discovered from the p2p network. The operation also occurs in the scenario in which blocks are explicitly pushed to nodeos via the chain API and the scenario in which the blocks are reapplied during replay. If a checkpoint that must be considered for a particular pushed block does not match the expected block ID, the block will be rejected by the push block operation by throwing a checkpoint_exception which should log a message that looks something like:
2018-07-12T14:24:19.308 thread-0   controller.cpp:902            push_block           ] 3140001 checkpoint_exception: Block does not match checkpoint
Checkpoint does not match for block number 9: expected: 00000009bc70d1043c9f16c09738a51f440a029e24d0c80ef2a355e302fef169 actual: 00000009ddf25ea9e864af55519961a021e4560d06df8c62456c34fa04d2d012
    {"num":9,"expected":"00000009bc70d1043c9f16c09738a51f440a029e24d0c80ef2a355e302fef169","actual":"00000009ddf25ea9e864af55519961a021e4560d06df8c62456c34fa04d2d012"}
    thread-0  chain_plugin.cpp:516 operator()


feat(PortfolioItem): add monitoring portfolio's item endpoints

Codecov Report

Merging #55 (6e3e0dd) into master (cae65b9) will increase coverage by 0.64%.
The diff coverage is 99.49%.

@@             Coverage Diff              @@
##             master      #55      +/-   ##
============================================
+ Coverage     89.37%   90.02%   +0.64%
- Complexity      805      870      +65
============================================
  Files           115      122       +7
  Lines          2720     2897     +177
  Branches         58       72      +14
============================================
+ Hits           2431     2608     +177
  Misses          289      289

Impacted Files
Coverage Δ
Complexity Δ

...redfroggy/ilg/client/monitoring/PortfolioItem.java
97.29% <97.29%> (ø)
10.00 <10.00> (?)

...y/ilg/client/monitoring/AlertPortfolioRequest.java
100.00% <100.00%> (ø)
7.00 <0.00> (-1.00)

...dfroggy/ilg/client/monitoring/PageableRequest.java
100.00% <100.00%> (ø)
8.00 <8.00> (?)

...ggy/ilg/client/monitoring/PortfolioItemDetail.java
100.00% <100.00%> (ø)
3.00 <3.00> (?)

...froggy/ilg/client/monitoring/PortfolioItemIds.java
100.00% <100.00%> (ø)
3.00 <3.00> (?)

...gy/ilg/client/monitoring/PortfolioItemRequest.java
100.00% <100.00%> (ø)
31.00 <31.00> (?)

...lg/client/monitoring/PortfolioItemSirenDetail.java
100.00% <100.00%> (ø)
4.00 <4.00> (?)

...edfroggy/ilg/client/monitoring/PortfolioItems.java
100.00% <100.00%> (ø)
3.00 <3.00> (?)

...froggy/ilg/client/monitoring/PortfolioRequest.java
100.00% <100.00%> (+1.36%)
23.00 <1.00> (-2.00)
:arrow_up:

...boot/autoconfigure/client/MonitoringApiClient.java
97.36% <100.00%> (+1.91%)
16.00 <6.00> (+6.00)

... and 7 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 cae65b9...6e3e0dd. Read the comment docs.


install proto client generation tool into dev-container

In what area(s)?
/area test-and-release
Describe the feature
Problem: Whenever we generate proto client for multiple languages, we need to install the tools for each language on local machine.  Sometimes, it is difficult to manage the tool version.
Solution: In order to improve the productivity, we can install proto client generation toolset for each langauge and add make target to simplify the process

[ ] : Create proto.mk makefile to generate protoclient for each language
[ ] : Install proto generation toolsets for each language in dev-container

cc/ @amanbha @pruthvidhodda

Based on the discussion with @youngbupark  it has been decided to not install tool chains for all languages in a single dev-container as it is found to break the generated SDK's. The solution is to have separate scripts in each of the SDK repos to install language specific plugins and tools to generate client stubs.
I am closing this issue in favor of the following issues created in SDK repos:

python-sdk: https://github.com/dapr/python-sdk/issues/27
js-sdk: https://github.com/dapr/js-sdk/issues/29
rust-sdk: https://github.com/dapr/rust-sdk/issues/10


python311Packages.authcaptureproxy: disable failing test

disable test test_return_timer_countdown_refresh_html that fails with a frequency of 1/200
https://github.com/alandtse/auth_capture_proxy/issues/25
ZHF:  #265948
https://hydra.nixos.org/build/240873632
please add 0.kind ZHF fixes tag. thx
=================================== FAILURES ===================================
___________________ test_return_timer_countdown_refresh_html ___________________

    def test_return_timer_countdown_refresh_html():
        """Test return_timer_countdown_refresh_html."""
        for _ in range(10):
            seconds = random.randint(0, 10000000)  # nosec
            text = "".join(
                random.choice(string.ascii_letters + string.digits)  # nosec
                for _ in range(random.randint(0, 200))  # nosec
            )
            hard_refresh = seconds % 2 == 0
            result = return_timer_countdown_refresh_html(seconds, text, hard_refresh)
            soup = bs(result, "html.parser")
            assert soup.find("script", defer="defer")
            assert soup.find("script", defer="defer").contents[0].endswith(f"""({seconds});""")
            assert (
                soup.find("script", defer="defer")
                .contents[0]
                .find(f"""location.reload({str(hard_refresh).lower()});""")
                > 0
            )
            assert soup.find("body")
>           assert soup.find("body").contents[0] == text
E           assert

 == ''

tests/test_stackoverflow.py:51: AssertionError
=========================== short test summary info ============================
FAILED tests/test_stackoverflow.py::test_return_timer_countdown_refresh_html - assert

 == ''
========================= 1 failed, 19 passed in 1.52s =========================
/nix/store/bbxdw4rgwwl3gnajri82yidr1nlsfskf-stdenv-linux/setup: line 1596: pop_var_context: head of shell_variables not a function context

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

17 packages built:

home-assistant-component-tests.roborock
python310Packages.alexapy
python310Packages.alexapy.dist
python310Packages.authcaptureproxy
python310Packages.authcaptureproxy.dist
python310Packages.python-roborock
python310Packages.python-roborock.dist
python310Packages.teslajsonpy
python310Packages.teslajsonpy.dist
python311Packages.alexapy
python311Packages.alexapy.dist
python311Packages.authcaptureproxy
python311Packages.authcaptureproxy.dist
python311Packages.python-roborock
python311Packages.python-roborock.dist
python311Packages.teslajsonpy
python311Packages.teslajsonpy.dist


CLI Progress Bars should display added and removed items separately

Issue
Progress bars don't describe whether items were added or removed during backup.  Ex:
email ∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙  10 -<EMAIL_ADDRESS>- Inbox

There should be a way to display the two counters in a single bar.  If not during the counting process, then possibly by appending the difference on completion..

More important of the two is likely items added.


Problem when inspect variable values when in debug mode

Steps to Reproduce

Create a application in VSCode or Android Studio
Run the app in Debug mode
Put a break point
When the application pauses at the breakpoint, move the cursor to the variable to see the value

Logs
compiler message: Unhandled exception:
compiler message: NoSuchMethodError: The getter 'loader' was called on null.
compiler message: Receiver: null
compiler message: Tried calling: loader
compiler message: #0      Object.noSuchMethod (dart:core-patch/dart:core/object_patch.dart:46)
compiler message: #1      IncrementalCompiler.compileExpression.<anonymous closure> (package:front_end/src/fasta/incremental_compiler.dart:429)
compiler message: <asynchronous suspension>
compiler message: #2      CompilerContext.runInContext.<anonymous closure>.<anonymous closure> (package:front_end/src/fasta/compiler_context.dart:118)
compiler message: #3      new Future.sync (dart:async/future.dart:222)
compiler message: #4      CompilerContext.runInContext.<anonymous closure> (package:front_end/src/fasta/compiler_context.dart:118)
compiler message: #5      _rootRun (dart:async/zone.dart:1126)
compiler message: #6      _CustomZone.run (dart:async/zone.dart:1023)
compiler message: #7      _runZoned (dart:async/zone.dart:1518)
compiler message: #8      runZoned (dart:async/zone.dart:1465)
compiler message: #9      CompilerContext.runInContext (package:front_end/src/fasta/compiler_context.dart:117)
compiler message: #10     IncrementalCompiler.compileExpression (package:front_end/src/fasta/incremental_compiler.dart:428)
compiler message: <asynchronous suspension>
compiler message: #11     IncrementalCompiler.compileExpression (package:vm/incremental_compiler.dart:103)
compiler message: #12     FrontendCompiler.compileExpression (package:vm/frontend_server.dart:448)
compiler message: <asynchronous suspension>
compiler message: #13     _FlutterFrontendCompiler.compileExpression (package:frontend_server/server.dart:55)
compiler message: #14     listenAndCompile.<anonymous closure> (package:vm/frontend_server.dart:650)
compiler message: <asynchronous suspension>
compiler message: #15     _RootZone.runUnaryGuarded (dart:async/zone.dart:1316)
compiler message: #16     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336)
compiler message: #17     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263)
compiler message: #18     _SinkTransformerStreamSubscription._add (dart:async/stream_transformers.dart:68)
compiler message: #19     _EventSinkWrapper.add (dart:async/stream_transformers.dart:15)
compiler message: #20     _StringAdapterSink.add (dart:convert/string_conversion.dart:268)
compiler message: #21     _LineSplitterSink._addLines (dart:convert/line_splitter.dart:154)
compiler message: #22     _LineSplitterSink.addSlice (dart:convert/line_splitter.dart:129)
compiler message: #23     StringConversionSinkMixin.add (dart:convert/string_conversion.dart:189)
compiler message: #24     _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:120)
compiler message: #25     _RootZone.runUnaryGuarded (dart:async/zone.dart:1316)
compiler message: #26     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336)
compiler message: #27     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263)
compiler message: #28     _SinkTransformerStreamSubscription._add (dart:async/stream_transformers.dart:68)
compiler message: #29     _EventSinkWrapper.add (dart:async/stream_transformers.dart:15)
compiler message: #30     _StringAdapterSink.add (dart:convert/string_conversion.dart:268)
compiler message: #31     _StringAdapterSink.addSlice (dart:convert/string_conversion.dart:273)
compiler message: #32     _Utf8ConversionSink.addSlice (dart:convert/string_conversion.dart:348)
compiler message: #33     _Utf8ConversionSink.add (dart:convert/string_conversion.dart:341)
compiler message: #34     _ConverterStreamEventSink.add (dart:convert/chunked_conversion.dart:86)
compiler message: #35     _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:120)
compiler message: #36     _RootZone.runUnaryGuarded (dart:async/zone.dart:1316)
compiler message: #37     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336)
compiler message: #38     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263)
compiler message: #39     _StreamController&&_SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:763)
compiler message: #40     _StreamController._add (dart:async/stream_controller.dart:639)
compiler message: #41     _StreamController.add (dart:async/stream_controller.dart:585)
compiler message: #42     _Socket._onData (dart:io-patch/socket_patch.dart:1672)
compiler message: #43     _RootZone.runUnaryGuarded (dart:async/zone.dart:1316)
compiler message: #44     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336)
compiler message: #45     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263)
compiler message: #46     _StreamController&&_SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:763)
compiler message: #47     _StreamController._add (dart:async/stream_controller.dart:639)
compiler message: #48     _StreamController.add (dart:async/stream_controller.dart:585)
compiler message: #49     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1245)
compiler message: #50     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:797)
compiler message: #51     _microtaskLoop (dart:async/schedule_microtask.dart:41)
compiler message: #52     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
compiler message: #53     _runPendingImmediateCallback (dart:isolate-patch/dart:isolate/isolate_patch.dart:113)
compiler message: #54     _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:166)

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, v0.5.6-pre.78, on Microsoft Windows [versÃ£o 10.0.17134.112], locale pt-BR)
[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[√] Android Studio (version 3.1)
[!] IntelliJ IDEA Community Edition (version 2017.3)
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
[√] VS Code, 64-bit edition (version 1.24.1)
[√] Connected devices (1 available)

! Doctor found issues in 1 category.

[√] Flutter (Channel master, v0.5.6-pre.78, on Microsoft Windows [versÃ£o 10.0.17134.112], locale pt-BR)
    • Flutter version 0.5.6-pre.78 at C:\flutter
    • Framework revision b44784b429 (58 minutes ago), 2018-06-26 15:11:37 -0700
    • Engine revision 6fe748490d
    • Dart version 2.0.0-dev.63.0.flutter-4c9689c1d2

[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at C:\Users\Yuri\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: C:\Program Files\Android\Android Studio1\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)
    • All Android licenses accepted.

[√] Android Studio (version 3.1)
    • Android Studio at C:\Program Files\Android\Android Studio1
    • Flutter plugin version 25.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

[!] IntelliJ IDEA Community Edition (version 2017.3)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2017.3.5
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.io/intellij-setup/#installing-the-plugins

[√] VS Code, 64-bit edition (version 1.24.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 2.14.0

[√] Connected devices (1 available)
    • Moto Z2 Play •<PHONE_NUMBER> • android-arm • Android 8.0.0 (API 26)

! Doctor found issues in 1 category.

I think this is supposed to be fixed in master by #18703,
but seems not to.
See also https://github.com/flutter/flutter/issues/18574#issuecomment-399858283

Seems I get this currently when a breakpoint is hit.
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v0.5.6-pre.97, on Mac OS X 10.13.5 17F77, locale en-AT)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
[✓] Android Studio (version 3.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2018.1.5)
[✓] Connected devices (1 available)

The debugger then stops working and I have to restart the app.

Can anyone still repro this? There were quite a few expression evaluation issues around this time and hopefully they've all been fixed (and I've added some integration tests that stop at breakpoints and evaluate expressions to try and catch regressions).
If you can still repro, please run Dart: Capture Logs, tick Flutter Run + Debugger and then repro and provide the log.

I still have this issue.  Is this the expected result on beta channels with flutter-web?
DevTools says I already have a debug session in VSCode but that is useless without variable inspection. So actually I do not have a debug session anywhere...
What did I do wrong?
[√] Flutter (Channel beta, 1.18.0-11.1.pre, on Microsoft Windows [Version 10.0.18362.836], locale hu-HU)
• Flutter version 1.18.0-11.1.pre at C:\flutter
• Framework revision 2738a1148b (2 weeks ago), 2020-05-13 15:24:36 -0700
• Engine revision ef9215ceb2
• Dart version 2.9.0 (build 2.9.0-8.2.beta)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at C:\Program Files (x86)\Android\android-sdk
• Platform android-28, build-tools 28.0.3
• ANDROID_HOME = C:\Program Files (x86)\Android
• ANDROID_SDK_ROOT = C:\Program Files (x86)\Android\android-sdk
• Java binary at: C:\Program Files (x86)\Android\openjdk\bin\java
• Java version OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_202-b08)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[!] Android Studio (not installed)
• Android Studio not found; download from https://developer.android.com/studio/index.html
(or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).
[√] VS Code, 64-bit edition (version 1.45.1)
• VS Code at C:\Program Files\Microsoft VS Code
• Flutter extension version 3.10.2
[√] Connected device (2 available)
• Web Server • web-server • web-javascript • Flutter Tools
• Chrome     • chrome     • web-javascript • Google Chrome 83.0.4103.61

@danielleiszen this issue is quite old and pre-web. It would be better to open a new issue if you're having issues with web, including the exact behaviour/error you see.
That said, expression evaluation for web is currently behind a flag - you can find details (and instructions on how to set it for VS Code) here under the title "Web Debugging with Expression Evaluation":
https://medium.com/flutter/flutter-web-support-updates-8b14bfe6a908


Update README.md to fix humble from source instructions

🦟 Bug fix
Fixes N/A
Summary
Fix the branch name when checking out ros_gz otherwise rosdep install -r --from-paths src -i -y --rosdistro humble errors with incompatible versions. Additonally link to https://github.com/gazebosim/ros_gz/issues/401#issuecomment-1564347874 which allows compilation on Ubuntu 20.04 + ROS2 Humble + Ignition Fortress
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[x] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@osrf-jenkins run tests please!

I think that the test failure can be ignored here?  This is just a documentation update.


Pretrained weight for AD prediction

Due to the AD model is trained on private dataset, can the weight be shared for researching purpose? I'm trying out the model on OCTA-500 dataset. My question is how do you get the SVC, DVC and CC from this dataset? I can't seem to find these.

Hi,
Thanks for your attention.
OCTA-500: Because OCTA-500 does not contain AD data, in our implementation, we selected DR instances as the extra experiment. Moreover, it does not contain SVC, DVC, and CC layers, hence we used FULL, ILM_OPL, and OPL_BM layers instead.
Weight: https://www.123pan.com/s/PqFEjv-rOpmd.html
According to our experience on hand, this weight may not work on your datasets, because of the limit of the model's generalization ability.

Hi,
Thank you very much for your advice and sharing of the weight file for AD risk estimation. May I ask if it's possible to upload the weight file to Baidu drive or Google drive? I tried but cannot register for the 123pan account since I'm not having a Chinese phone number.
Rgds.

https://drive.google.com/file/d/1WJkXkbUqI7NRP-tyAqs32q1XYUx7cv0o/view?usp=share_link


CI: add workflow for branding name checks

This commit adds a GitHub Actions workflow to check pull request (PR) diffs for outdated terms such as "Cloudberry Database", "Greenplum", and related variations.
The workflow scans only modified or added lines in the PR to identify outdated branding name. If detected, it posts a comment suggesting the use of "Apache Cloudberry" or "Cloudberry" as appropriate.
This helps ensure consistent and up-to-date terminology across the project while streamlining the review process.

Fixes #ISSUE_Number
What does this PR do?

Type of Change

[ ] Bug fix (non-breaking change)
[ ] New feature (non-breaking change)
[ ] Breaking change (fix or feature with breaking changes)
[ ] Documentation update

Breaking Changes

Test Plan

[ ] Unit tests added/updated
[ ] Integration tests added/updated
[ ] Passed make installcheck
[ ] Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

[ ] Followed contribution guide
[ ] Added/updated documentation
[ ] Reviewed code for security implications
[ ] Requested review from cloudberry committers

Additional Context

CI Skip Instructions

I created this file with the help of ChatGPT to check the commits for brand name.
Seems not had the access to post the comments.
github-token: ***
    debug: false
    user-agent: actions/github-script
    result-encoding: json
    retries: 0
    retry-exempt-status-codes: 400,401,403,404,422
Error checking for deprecated terms: RequestError [HttpError]: Resource not accessible by integration
    at /home/runner/work/_actions/actions/github-script/v6/dist/index.js:6842:21
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async eval (eval at callAsyncFunction (/home/runner/work/_actions/actions/github-script/v6/dist/index.js:15143:16), <anonymous>:62:5)
    at async main (/home/runner/work/_actions/actions/github-script/v6/dist/index.js:15236:20) {
  status: 403,
  response: {
    url: 'https://api.github.com/repos/apache/cloudberry/issues/787/comments',
    status: 403,
    headers: {
      'access-control-allow-origin': '*',
      'access-control-expose-headers': 'ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset',
      'content-encoding': 'gzip',
      'content-security-policy': "default-src 'none'",
      'content-type': 'application/json; charset=utf-8',
      date: 'Thu, 19 Dec 2024 08:40:38 GMT',
      'referrer-policy': 'origin-when-cross-origin, strict-origin-when-cross-origin',
      server: 'github.com',
      'strict-transport-security': 'max-age=31536000; includeSubdomains; preload',
      'transfer-encoding': 'chunked',
      vary: 'Accept-Encoding, Accept, X-Requested-With',
      'x-accepted-github-permissions': 'issues=write; pull_requests=write',
      'x-content-type-options': 'nosniff',
      'x-frame-options': 'deny',
      'x-github-api-version-selected': '2022-11-28',
      'x-github-media-type': 'github.v3; format=json',
      'x-github-request-id': 'B7C0:2165[76](https://github.com/apache/cloudberry/actions/runs/12409149152/job/34642168577?pr=787#step:3:76):AA9DE6:153A6EA:6763DC06',
      'x-ratelimit-limit': '15000',
      'x-ratelimit-remaining': '14996',
      'x-ratelimit-reset': '1734599619',
      'x-ratelimit-resource': 'core',
      'x-ratelimit-used': '4',
      'x-xss-protection': '0'
    },
    data: {
      message: 'Resource not accessible by integration',
      documentation_url: 'https://docs.github.com/rest/issues/comments#create-an-issue-comment',
      status: '403'
    }
  },
  request: {
    method: 'POST',
    url: 'https://api.github.com/repos/apache/cloudberry/issues/[78](https://github.com/apache/cloudberry/actions/runs/12409149152/job/34642168577?pr=787#step:3:78)7/comments',
    headers: {
      accept: 'application/vnd.github.v3+json',
      'user-agent': 'actions/github-script octokit-core.js/3.6.0 Node.js/20.18.0 (linux; x64)',
      authorization: 'token [REDACTED]',
      'content-type': 'application/json; charset=utf-8'
    },
    body: '{"body":"\\n  > [!NOTE]\\n  > This is not a required check for merging this PR, just for your reference.\\n\\n   **Attention:** The following old brand terms were found in your changes: `Cloudberry Database`,`CloudberryDB`,`Cloudberry DB`,`Greenplum Database`,`Greenplum`,`GPDB`\\n\\n  Please consider replacing them with \\"Apache Cloudberry\\" or \\"Cloudberry\\" where appropriate. Thank you for ensuring consistency in our branding! 🙏\\n  "}',
    request: { agent: [Agent], hook: [Function: bound bound register] }
  }

Welcome to have your help with this. Thanks in advance.

Tested it on my own repo. If it runs successfully, it will be like this:


UI problem with the longer name

[ ] We can implement Ellipses in List/Compact Views:

Truncate the longer names using ellipses (...) when displayed in compact areas (e.g., lists, cards, or headers)
Ensure the ellipses appear dynamically based on the available space.
Example:
Johnathan Alexander Smith → Johnathan Alexander...
Context https://bithyve-workspace.slack.com/archives/C03741UNM0S/p1732523220677229

@Deveshshankar  For the long name, we are managing like split in two line
box size will be same for short name or long name we need to just manage space that's it
Please check and let me know if you need any change


Reboot updates

Inherit box-sizing and set box-sizing: border-box; on body
This makes it possible for 3th party components to use box-sizing: content-box by just applying the box-sizing to the wrapper div.
Remove unsupported browsers fixes (IE10 & Firefox 39-)
More consistent comment blocks
Reorganise order of some blocks
Add height fix for date/month/week/time inputs (#18842, this was already fixed by adding a height to form controls, with this change we don't need to set the height anymore)
Remove redundant type selectors for some pseudo elements
Additional resets and theming options for legend
Element theming from _code.scss moved to reboot
All input fields now have the same borders

Result: https://deploy-preview-28917--twbs-bootstrap.netlify.com/docs/4.3/content/reboot/

Regarding the box-sizing change: https://github.com/twbs/bootstrap/issues/22872

Last thing I've noticed here is that if we're moving all those styles to Reboot, we need to move the docs content to the Reboot page as well.

I'm not sure what to do with the .pre-scrollable class. It's the only class left in _code.scss and I can't document it on the reboot page since it isn't part of it. Should we leave it as only class on the code page and in _code.scss or is it not worth it and can we drop it?

I agree to remove the .pre-scrollable. I'm OK remove it in this PR, but I prefer to separate for clarity.

I've opened https://github.com/twbs/bootstrap/pull/29135/ to drop the class.


Problem with deactivated/reactivated accounts

We have the case of someone with a "6" at the end of his id account (.fr6...), and some invites that go to his "2" old account (.fr2...)

@jp-modernisation-gouv-fr how did you trigger the invite? by searching the user in the users directory or from the existing contacts list?

the user doesn't remember

I think the issue is due to the fact that we keep in the contacts list the users for who we have a direct chat that they left. We should keep only the users present in our direct chat


support of "amqp" and "amqps" URI scheme

implement below spec
https://www.rabbitmq.com/uri-spec.html

Hi gftea, is this still available to implement? If so, were you thinking an additional function within OpenConnectionArguments such as from_uri(uri: &str) or changing the new function to only accepting a uri str?

Hi,
Yes, it is available. I have not yet started working on this. Would you like to work on this?
Because not all arguments in OpenConnectionArguments can be expressed in URI spec, such as connection_name and heartbeat, etc, I think we need to consider URI as a combined aguments as part of OpenConnectionArguments

To distinguish URI argument and non URI arguments, we may need to have new API like below
pub fn new(host: &str, port: &str, username: &str, password: &str) -> Self

change uri method's implementation to accept URI spec, instead of supporting only format: “:”

as your suggestion, support something like from_uri(uri: &str) -> Self by implementing trait From or  TryFrom, but because user may give incorrect URI, so I think we should implement TryFrom.

The client library only deal with amqp/amqps, does not need generic URL handling, so I think prefer to impelemnt our own parsing, and it should not be too difficult to implement.

I am a bit naive at first thinking, it looks dealing with URL characters are not a trival task. maybe, as you suggest, we can use rust-url crate

Hi @gftea, after spending some time on it, I agree its not super trivial. I do have an implementation that correctly parses all of the edge cases listed in the amqp uri spec however, the implementation does not url decode nor am I confident that it will successfully fail if given completely wrong uri's or even more edge cases pertaining to things like query parameters, which I believe are used to control things like the heartbeat.
I do have question about the uri() function in general. What is it's purpose? additionally, the uri field in struct OpenConnectionArguments currently only pertains to the host and port where the URI spec (RFC 3986) can be used to (almost if not completely) define the values in struct OpenConnectionArguments. Like the new function arguments you mentioned before, shouldn't the struct also change to be as verbose as possible and contain a separate host and port field and we can keep the uri field to store the user provided uri str. If the point of uri() is to change all fields in the struct to conform to the URI spec, why support this when the user can simply call from_uri or new and receive the same result but as a new object? Is the cost of allocating a new OpenConnectionArguments too expensive considering that users aren't likely to open hundreds to hundreds of thousands OpenConnectionArguments in any single producer/consumer.
TLDR;

I have an implementation, but I think its too flawed to handle URIs that are "too incorrect", so I will switch to the rust-url crate. There is also the uriparse crate, which seems to be much less mature than rust-url but is ~22% lighter in total package size.
uri()  function changes the OpenConnectionArguments object it is called on in such a significant way that it seems viable to rely on a from_uri(uri: &str) or the new(...args) function.

Hi,
You have a good point about uri(), I agree we should deprecate it, and update the OpenConnectionArguments to have separate fields for host and port. Also we need to add new chainable APIs, host() and port().
I take a quick look both rust-url and uriparse, I would prefer  rust-url which is more reliable, good maintainence, and has been used in servo browser engine also.
I would prefer to consider support of URL spec as optional feature, disabled by default.  User can choose to enable.

Hi gftea, I will continue working on the feature with these guidelines! Thank you for your additional clarification.

Hi @gftea,
I have two different implementations ready for review. The first implementation uses the crate url (aka rust-url). I found that this crate is specific to the URL Standard, and NOT the URI Standard outlined in RFC3986. The Rabbit MQ very closely adheres to RFC3986 and as a result, the rust-url implementation fails to parse urls that are said to be correct on the Rabbit MQ uri spec. I created a second implementation using uriparse to test its behavior, it successfully handles the cases mentioned prior.
The cases where the rust-url fails I found to be mostly from the result of the uri having a zero-length host, which is reasonable to assume would be incorrect, however the RabbitMQ states it is correct.
Which implementation would you prefer?

Good findings! I am OK to go with uriparse solution. Thanks!/SimonOn 7 Jan 2023, at 19:36, Jacob Miller @.***> wrote:
Hi @gftea,
I have two different implementations ready for review. The first implementation uses the crate url (aka rust-url). I found that this crate is specific to the URL Standard, and NOT the URI Standard outlined in RFC3986. The Rabbit MQ very closely adheres to RFC3986 and as a result, the rust-url implementation fails to parse urls that are said to be correct on the Rabbit MQ uri spec. I created a second implementation using uriparse to test its behavior, it successfully handles the cases mentioned prior.
The cases where the rust-url fails I found to be mostly from the result of the uri having a zero-length host, which is reasonable to assume would be incorrect, however the RabbitMQ states it is correct.
Which implementation would you prefer?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Fix/not-fnd gitmessage

added a fix to find the .gitmessage on sub-folders

difference tests asserts in kubuntu with node 8 and travis....

Hi, @Sarabadu thanks for this fix. I noticed the commits seem to be mixed with overriding the author PR you've. Could you separate them, please? Then I will get this merged in.


e2e: add pod/container info in error form exec in pod.

When running connectivity tests, it's up to debug logs to provide information on failure errors. This is not always the case, making it hard to understand where to start investigating errors.
This adds pod/container to the error message for calls to k8s exec to make it easier to understand where the issue occurred.
Ex use case:
Running test echo-ingress-l7-named-port: setting up test: applying network policies: policies were not applied on all Cilium nodes in time: Timeout occurred
Raises the questions:

On what Agent Pod?
"Timeout occurred" error is ambiguous, did the k8s exec request timeout, or the passed command itself?

/test

Closed and re-opened PR to retrigger all tests. They were failing because of the GH incident last week.

@tommyp1ckles Could we get this PR? :pray:

woops, yup last push should fix failures @tklauser @brb


Fixes calculation of average thread blocked time and average thread waited time

Enables thread contention monitoring.
Fixes calculation of average thread blocked time and average thread waited time when thread is blocked/waiting due to same event across thread dump intervals.

Signed-off-by: Surya Sashank Nistala<EMAIL_ADDRESS>Issues resolved
#92
Testing
for i in {1..3};do curl "http://localhost:9600/_plugins/_performanceanalyzer/metrics?metrics=Thread_Blocked_Time,Thread_Blocked_Event&agg=max,max&dim=Operation" ;echo;sleep 5;done
{"k1yr46alRW2mC5h7nCSSYQ": {"timestamp":<PHONE_NUMBER>000, "data": {"fields":[{"name":"Operation","type":"VARCHAR"},{"name":"Thread_Blocked_Time","type":"DOUBLE"},{"name":"Thread_Blocked_Event","type":"DOUBLE"}],"records":[["GC",0.0,0.0],["flush",0.0,0.0],["generic",0.0,149.0],["management",0.0,38.0],["other",10.015115325794273,27.0],["refresh",0.0,0.0],["search",10.015115302620272,24.0],["transportWorker",0.0,87.0]]}}}

{"k1yr46alRW2mC5h7nCSSYQ": {"timestamp":<PHONE_NUMBER>000, "data": {"fields":[{"name":"Operation","type":"VARCHAR"},{"name":"Thread_Blocked_Time","type":"DOUBLE"},{"name":"Thread_Blocked_Event","type":"DOUBLE"}],"records":[["GC",0.0,0.0],["flush",0.0,0.0],["generic",0.0,149.0],["management",0.0,38.0],["other",10.013015012003,27.0],["refresh",0.0,0.0],["search",10.013015012002999,24.0],["shardquery",3.112,1.0],["transportWorker",0.0,87.0]]}}}

{"k1yr46alRW2mC5h7nCSSYQ": {"timestamp":<PHONE_NUMBER>000, "data": {"fields":[{"name":"Operation","type":"VARCHAR"},{"name":"Thread_Blocked_Time","type":"DOUBLE"},{"name":"Thread_Blocked_Event","type":"DOUBLE"}],"records":[["GC",0.0,0.0],["flush",0.0,0.0],["generic",0.0,149.0],["management",0.0,38.0],["other",10.013238956117647,27.0],["refresh",0.0,0.0],["search",10.01323896387822,24.0],["transportWorker",0.0,87.0]]}}}

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #118 (e4656c5) into main (8b79f18) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main     #118      +/-   ##
============================================
- Coverage     72.03%   72.00%   -0.04%
- Complexity     2945     2964      +19
============================================
  Files           376      376
  Lines         18723    18852     +129
  Branches       1432     1468      +36
============================================
+ Hits          13488    13574      +86
- Misses         4648     4692      +44
+ Partials        587      586       -1

Impacted Files
Coverage Δ

...ormanceanalyzer/collectors/OSMetricsCollector.java
1.85% <0.00%> (-0.02%)
:arrow_down:

...ollectors/PerformanceAnalyzerMetricsCollector.java
41.17% <ø> (-3.99%)
:arrow_down:

.../collectors/ScheduledMetricCollectorsExecutor.java
14.08% <0.00%> (-0.21%)
:arrow_down:

...opensearch/performanceanalyzer/jvm/ThreadList.java
12.03% <0.00%> (-0.31%)
:arrow_down:

...performanceanalyzer/rca/framework/api/Symptom.java
90.90% <0.00%> (-9.10%)
:arrow_down:

...performanceanalyzer/net/GRPCConnectionManager.java
82.41% <0.00%> (-3.95%)
:arrow_down:

.../opensearch/performanceanalyzer/net/NetServer.java
68.67% <0.00%> (-3.83%)
:arrow_down:

...ch/performanceanalyzer/PerformanceAnalyzerApp.java
43.13% <0.00%> (-3.68%)
:arrow_down:

...ormanceanalyzer/reader/ReaderMetricsProcessor.java
77.93% <0.00%> (-0.93%)
:arrow_down:

... and 370 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 8b79f18...e4656c5. Read the comment docs.

Flaky EventLogFileHandlerTests test has been fixed.  Thanks!

Integration tests are failing in main as well.
https://github.com/opensearch-project/performance-analyzer-rca/runs/5842874823?check_suite_focus=true

Approving. Integ test failing due to known failure which was fixed recently and seems like this PR didn't pull that latest commit.


add Dockerfile and docker-compose

add dockerfile
add docker-compose
add .dockerignore

This won't work unless #6 is merged first.
Otherwise, line 2 in .dockerignore needs to be removed, as currently Config.json and others exist in bin/

@raeyulca
Is there any real reason why this line should be removed?

Wouldn't it be logical to remove it from dockerfile then? :p


Undefined reference to sio::client::client()

Hello,
I've followed the set up instructions as best as I can, boost seems linked, as well as the socket-io libraries. Following the example my main.cpp looks like this:
#include "./lib/socket.io-client-cpp/src/sio_client.h"
#include "./lib/socket.io-client-cpp/src/sio_socket.h"
#include "./lib/socket.io-client-cpp/src/sio_message.h"

int main(int , char* argv[]) {
    sio::client h;
    h.connect("http://<IP_ADDRESS>:3000");
    return 0;
}

The path to sio_client.h is correct, VSCode complained when I pointed to the wrong location, and if I shift+click sio::client it does take me to the header file, but when compiling the following errors show up:

/tmp/ccuONn4Y.o: In function main': /path/to/main.cpp:6: undefined reference to sio::client::client()'
/path/to/main.cpp:7: undefined reference to sio::client::connect(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /path/to/main.cpp:6: undefined reference to sio::client::~client()'
/path/to/main.cpp:6: undefined reference to `sio::client::~client()'
collect2: error: ld returned 1 exit status
Makefile:37: recipe for target 'all' failed

My makefile looks like this:
# All purpose variables
compiler=g++
project_root = ./

#   Where to store the binaries
target_folder=bin
target_bin=louise
source_to_main=src/louise/main.cpp

# Compiler flags
flags=-std=c++11 -Wall -Werror -g -v -lboost_filesystem -lboost_system
deps = ./src/louise/lib/socket.io-client-cpp/sio_client.h ./src/louise/lib/socket.io-client-cpp/lib/websocketpp ./src/louise/lib/socket.io-client-cpp/lib/rapidjson

# Compilation instructions
%.o: %.c $(deps)
	$(CC) -c -o $@ $< $(flags)

all:
	cd $(project_root)
	if [ -a $(target_folder)/${target_bin} ]; then rm $(target_folder)/${target_bin}; fi;

	$(compiler) ${source_to_main} -o $(target_folder)/${target_bin} ${flags}

I realize an ld error is a linker error, but cant spot what's wrong in my setup, a little help please?

Made some progress, realized I was missing the client sources in my Makefile, which now looks like this:
# All purpose variables
compiler=g++
project_root = ./

#   Where to store the binaries
target_folder=bin
target_bin=louise
source_to_main=src/louise/main.cpp src/louise/lib/socket.io-client-cpp/src/sio_client.cpp src/louise/lib/socket.io-client-cpp/src/sio_socket.cpp

flags=-std=c++11 -Wall -Werror -g -v -lboost_filesystem -lboost_system
deps = ./src/louise/lib/socket.io-client-cpp/sio_client.h ./src/louise/lib/socket.io-client-cpp/lib/websocketpp ./src/louise/lib/socket.io-client-cpp/lib/rapidjson

...
$(compiler) ${source_to_main} -o $(target_folder)/${target_bin} ${flags}

The current error Im getting is:

src/louise/lib/socket.io-client-cpp/src/internal/sio_client_impl.h:15:34: fatal error: websocketpp/client.hpp: No such file or directory

Hey, I am getting the same error. Have you solve the problem?
fatal error: websocketpp/client.hpp: No such file or directory.

@ShivankGupta https://github.com/socketio/socket.io-client-cpp/issues/94
And updating websocket git (replace everything in socket.io-client-cpp\lib\websocketpp and rebuild libraries) would solve other problems with working with outdated libraries

Hello, was this resolved ?

Sorry guys, no fix on my end, I eventually moved to another programming language for websockets

same here
qt project, can not compile

Any solutions to this issue? I am getting same error on Ubuntu 18.04:
client1.cpp:(.text+0x12e): undefined reference to sio::client::connect(std::string const&)'
client1.cpp:(.text+0x182): undefined reference to sio::client::socket(std::string const&)' client1.cpp:(.text+0x1ef): undefined reference to sio::socket::emit(std::string const&, sio::message::list const&, std::function<void (sio::message::list const&)> const&)'
collect2: error: ld returned 1 exit status
`


fix Using unique_ptr to refactor some class members

Proposed changes
Using unique_ptr to refactor some class members.
Fix mem leak for SegmengIterator 's _pre_eval_block_predicate.
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

This pr can work correctly in LSAN mode, using SSB sql.


Not Found: undefined

Get error Not Found: undefined when trying to register and account on webpage

Can you provide the stacktrace or URL to debug?


error shown when using the built in composer and php

The latest dev-dependencies of static-php-cli currently require the sodium extension, and the common combination php-cli downloaded by bin/setup-runtime (from dl.static-php.dev) does not contain this extension.
I will fix this later, or you can temporarily modify setup-runtime to download the bulk combination and 8.2.13.
https://github.com/crazywhalecc/static-php-cli/blob/cf198e0f0a4133dd62bcce79ea4e7932b45abd4f/bin/setup-runtime#L28


[NIFI-9666] Readme update

Closing this one as these changes and the updates are present in this PR: https://github.com/mattyb149/nifi/pull/25


bug: fix the text in the header

I noticed that in the header, there is extra whitespace and grammatical errors are there.
I would like to fix those issues.
Please assign this issue to me and add the Hacktoberfest label to this issue.

Done, Go Ahead.

Yup!
Could you please add the requested label to this issue.


Fix <> code block

@krujos Thank you for the PR. Can you close this one and open one against the develop branch please.
Thanks again


Allow Synchronous Generation

Addresses #329
If the generated PrismaClient exposes the Datamodel Meta Format, allow users to supply the models directly, bypassing the async/await.

@morintd
I addressed these tow points:

Change the example under "Alternative Synchronous Client Generation" to contain only the call to generatePrismockSync, making the README easier to read
Adding generatePrismockSync under the API section

Regarding this point:

Splitting the Options type under src/lib/prismock to have one dedicated to each sync/async generate method it doesn't make sense for the async generatePrismock to accept a list of models (and neither for the sync generatePrismockSync to accept a pathToSchema, but you already omit it).
The async generatePrismock shouldn't check for models, I would prefer to support only the generatePrismockSync for this use case

I was hoping to implement a fallback - if one doesn't work, for any reason - use the other... But itt's you library so that's fine. I will add tests after work tonight. Let me know if you want fully separate or fallback option and i'll get that in.


Fix issue #1678

Add tests for URLs containing paramters.
Keep parameters in wagtailredirect.models.Redirect.normalise_url() like we do query strings: sorted alphabetically but otherwise must be identical

Thanks!


Automatic Keycloak token refresh

Adds support for better login config & automatic token refresh

This change is

fix for https://github.com/canoo/dolphin-platform/issues/860

Pull Request Test Coverage Report for Build 3008

0 of 115 (0.0%) changed or added relevant lines in 6 files are covered.
5 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.4%) to 52.852%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

platform-extras/dolphin-platform-security-client/src/main/java/com/canoo/dp/impl/security/KeycloakOpenidConnectResult.java
0
1
0.0%

platform-extras/dolphin-platform-security-server/src/main/java/com/canoo/dp/impl/server/security/SecurityModule.java
0
1
0.0%

platform-extras/dolphin-platform-security-server/src/main/java/com/canoo/dp/impl/server/security/KeycloakConfiguration.java
0
2
0.0%

platform-extras/dolphin-platform-security-server/src/main/java/com/canoo/dp/impl/server/security/KeycloakLogoutServlet.java
0
8
0.0%

platform/dolphin-platform-core/src/main/java/com/canoo/platform/core/PlatformConfiguration.java
0
9
0.0%

platform-extras/dolphin-platform-security-client/src/main/java/com/canoo/dp/impl/security/KeycloakSecurity.java
0
94
0.0%

Files with Coverage Reduction
New Missed Lines
%

platform-extras/dolphin-platform-security-client/src/main/java/com/canoo/dp/impl/security/KeycloakRequestHandler.java
1
0.0%

platform-extras/dolphin-platform-security-client/src/main/java/com/canoo/dp/impl/security/KeycloakSecurity.java
2
0.0%

platform-extras/dolphin-platform-security-server/src/main/java/com/canoo/dp/impl/server/security/KeycloakConfiguration.java
2
0.0%

Totals

Change from base Build 3001:
-0.4%

Covered Lines:
4744

Relevant Lines:
8976

💛  - Coveralls


try to fix issue #577

try to fix issue #577

@Mark-Fenng I think the original issue may happen when there is serialization progress in the users' backend that turns undefined to null in JSON.

That makes sense but the undefined values may also cause unexpected behavior.

@Mark-Fenng Yes, but I think we will not get undefined values from JSON-based events.
JSON.stringify({ a: 1, b: undefined})
// "{\"a\":1}"

And I'm thinking how could we get undefined from TextNode.textContent in runtime?

Ok, we should rather pay attention to its root cause.


We need a smarter way of checking return codes from MQSC scripts

Currently we use set +e to turn off script error checking before we run all of the MQSC scripts the user has supplied. Once that has finished we turn script error checking back on using set -e.
This isn't ideal as it means that serious errors with people's scripts (such as syntax errors) do not get picked up and could cause confusion such as where is that object i tried to create?. We had to add it in because on multiple starts the START LISTENER(<LISTENER>) command (where the  was created with CONTROL(QMGR) fails with the listener is already active error. (which isn't really an error)
What we need is some way to check the error codes returned by MQSC and error out if a serious error happens and continue if a warning style error happens

This repo (mq-docker) is now deprecated and is being replaced by the ibm-messaging/mq-container repo. Please try this new repo and see if you continue to experience the problem listed here. If you do please raise a new issue on the new repo.


Error Code: 3 SSL Error : The certificate authority is not trusted in React Native Web View ( Android )

I released a production Android app this week(20.08.2022) but had trouble with the SSL Error Handler. ( "react-native-webview": "^11.0.2" )

As a solution, I have to allow trusted URLs to avoid the error

But after the production release got a reply saying that list of issues and the corresponding APK versions were detected in your recent submission.

Is there a way to navigate the URL, as any normal browser would allow?

i face the same issue

@ChanaChampsoft & @camboYY Did you check in real device? because i am also facing same issue in emulator (android). But in real device it's working fine.

Same issue
worked on simulator
but not working on real Google Pixel 4A

any solution? Re open pls

Follow up. I have the same issue.

Same issue.

I encountered the same issue on React-Native 0.71.7 and React-Native-WebView 12.0.2.
This issue arises when trying to render a website that uses a certificate which does not have a chain configured to a trusted root certificate. You can verify this issue at https://www.sslshopper.com/ssl-checker.html. If you own the web page in question, replacing the SSL certificate would be the fundamental solution.

Hi i am also facing this issue can any one help how to resolve.

looking for updates

same here

This issue is far from solved

I have the same problem, this is still not solved

In v 13.6.3, To make this change you have to go node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewClient.java.
_```

@Override
public void onReceivedSslError(final WebView webView, final SslErrorHandler handler, final SslError error) {
// onReceivedSslError is called for most requests, per Android docs: https://developer.android.com/reference/android/webkit/WebViewClient#onReceivedSslError(android.webkit.WebView,%2520android.webkit.SslErrorHandler,%2520android.net.http.SslError)
// WebView.getUrl() will return the top-level window URL.
// If a top-level navigation triggers this error handler, the top-level URL will be the failing URL (not the URL of the currently-rendered page).
// This is desired behavior. We later use these values to determine whether the request is a top-level navigation or a subresource request.
String topWindowUrl = webView.getUrl();
String failingUrl = error.getUrl();
    // Cancel request after obtaining top-level URL.
    // If request is cancelled before obtaining top-level URL, undesired behavior may occur.
    // Undesired behavior: Return value of WebView.getUrl() may be the current URL instead of the failing URL.
    handler.proceed();

I am facing this problem.
What is the impact of making this change to the lib source code?

I am facing this problem. What is the impact of making this change to the lib source code?

Modification of Webview
In v 13.6.3, To make this change you have to go node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewClient.java.
Find ssLerrorhandle, then change to handle.cancel() to handle.proceed(). It works

It worked!
What are the side effects of this change?

How is this closed?
Why is it that just setting
<base-config cleartextTrafficPermitted="true">
    <trust-anchors>
        <certificates src="system" />
        <certificates src="user" />
    </trust-anchors>
</base-config>

As descriped here: https://developer.android.com/privacy-and-security/security-config#base-config
And the installing your self signed CA cert doesn't work?
shouldn't adding "user" fix this?

Yes you can edit the RNCWebViewClient.java file but seems wrong.

any update hare, i get the same issue

Any progress? I have changed to handle.cancel() to handle.proceed() in RNCWebViewClient.java,  and then It not been solved.

Same issue here, any solution? 👀

How is this closed?
Why is it that just setting
<base-config cleartextTrafficPermitted="true">
    <trust-anchors>
        <certificates src="system" />
        <certificates src="user" />
    </trust-anchors>
</base-config>

As descriped here: https://developer.android.com/privacy-and-security/security-config#base-config
And the installing your self signed CA cert doesn't work?
shouldn't adding "user" fix this?

It does work for me after applying the changes and adding the custom rootca certificate.

It might be a problem with certificate configuration on web-server you trying to reach.
In my case there was no SSL certificate chain.
So solutions like
handler.proceed();
or
<base-config cleartextTrafficPermitted="true" />
can only be temporary.
The best way in that case is contact with domain owner to fix this.


Since alpha.28 google home often cannot control devices and is often offline

Since alpha.28 google home often cannot control devices and is often offline

logs-3.txt

Use CPU a lot
logs-4.txt

But why is my google home still relatively stable with alpha 27?

@t0bst4r What were the changes between 27 and 28?

Maybe share a comparism log from start on for some minutes with 27 and 28

What were the changes between 27 and 28?

https://github.com/t0bst4r/home-assistant-matter-hub/compare/v3.0.0-alpha.27...v3.0.0-alpha.28

Interesting ... none of these changes should be low level enough. So if you now go back to .27 it works? and with .28 not?

Thank you , updated alpha.30, pretty ok with me, still testing
On Thu, Nov 14, 2024, 21:49 Tobias Glatthar @.***>
wrote:

I have recently made a lot of changes to the state management and event
handling. This has fixed some errors that were preventing the application
from starting.
Anyway, there still seems to be a bug with lights, but in order not to
lose the overview, I would like to collect all CURRENT problems with
version alpha.30 in one ticket (#134
https://github.com/t0bst4r/home-assistant-matter-hub/issues/134).
Please update your addon version and add a comment in the ticket if you
still have problems. If it is the exact same problem as someone else
already reported, feel free to give it a thumbs up instead of commenting
"same".
Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/t0bst4r/home-assistant-matter-hub/issues/128#issuecomment-2476552640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQOYWXKTW6SMZVSSJ7UVHJD2AS2APAVCNFSM6AAAAABRVH7BLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZWGU2TENRUGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


AP-306 adjust currencycloud client

Adjust currencycloud client to be scoped and work with injected http clients and added scoped authorization service with singleton token holder. Token is updated in a synchronized manner using semaphoreSlim instance

@oleg-sviridov conflicts


Error creating Eventbridge Rule with empty ScheduleExpression on non-default Eventbridge EventBus

Describe the bug
When an Eventbridge Rule against a custom Eventbridge EventBus, I get the following error:
ValidationException: ScheduleExpression is supported only on the default event bus.

The ScheduleExpression is empty, so I think this is likely due to the field being submitted regardless.
Steps to reproduce
Create an EventBus:
apiVersion: eventbridge.services.k8s.aws/v1alpha1
kind: EventBus
spec:
  name: custom-bus

Create a Rule (I manually created an sns topic in the ui)
apiVersion: eventbridge.services.k8s.aws/v1alpha1
kind: Rule
spec:
  description: Send guard duty output to SNS
  eventBusRef:
    from:
      name: custom-bus
  eventPattern: '{"detail":{"severity":[4,4,4.1,4.2,4.3,4.4,4.5,4.6,4.7,4.8,4.9,5,5,5.1,5.2,5.3,5.4,5.5,5.6,5.7,5.8,5.9,6,6,6.1,6.2,6.3,6.4,6.5,6.6,6.7,6.8,6.9,7,7,7.1,7.2,7.3,7.4,7.5,7.6,7.7,7.8,7.9,8,8,8.1,8.2,8.3,8.4,8.5,8.6,8.7,8.8,8.9]},"detail-type":["GuardDuty
    Finding"],"source":["aws.guardduty"]}'
  name: guard-duty-rule
  scheduleExpression: ""
  targets:
  - arn: some-sns-arn
    id: guard-duty
    inputTransformer:
      inputPathsMap:
        Account_ID: $.detail.accountId
        Finding_ID: $.detail.id
        Finding_Type: $.detail.type
        Finding_description: $.detail.description
        region: $.region
        severity: $.detail.severity
      inputTemplate: |-
        Test template

Expected outcome
I think the rule should be created without submitting the ScheduleExpression field if a bus is specified.
A concise description of what you expected to happen.
Environment

Kubernetes version: 1.27
Using EKS (yes/no), if so version? : 1.27
AWS service targeted (S3, RDS, etc.): Eventbridge

/cc @embano1

@jose-fully-ported thank you for reporting and you're absolutely right that we need to nil (unset) this field if it's set as an empty string. Will file a PR soon.

@jose-fully-ported this will be fixed along with https://github.com/aws-controllers-k8s/community/issues/1989 in the next release

Fixed in https://github.com/aws-controllers-k8s/eventbridge-controller/releases/tag/v1.0.6


parameter metadata not used in the function

https://github.com/gammasim/simtools/blob/4817fc03c10b00814875476218bd6eac4cd056e6/simtools/data_model/model_data_writer.py#L87
The parameter metadata is not used in the function and should be likely removed

Yes, this is on the.
pylint is catching this issues, so I connect this to the linter branch.


DEPR: Deprecated PeriodIndex.to_datetime

Continuation of #14096 by deprecating PeriodIndex.to_datetime in favour of PeriodIndex.to_timestamp.
Also addresses #8254.

Current coverage is 85.26% (diff: 100%)

Merging #14113 into master will increase coverage by <.01%

@@             master     #14113   diff @@
==========================================
  Files           139        139
  Lines         50502      50504     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          43062      43064     +2
  Misses         7440       7440
  Partials          0          0

Powered by Codecov. Last update 8d1646c...876d72c

@jreback , @jorisvandenbossche : Travis is passing.  Ready to merge if there are no other concerns.

lgtm

Thanks!

Don't forget to add to the list in #6581!

@gfyoung Already did :-) (but linked to the issue, where the links are to all the different prs)


Changed ABS Container API Directory Identification

Fix for Issue #19756
Directories were not properly identified

Great :) The fix looks good enough!
Is there a way to write a test that would fail with the previous version, but succeeds with your changes?

@mazhelez
I don't know, if you have multiple folders in a test azure container or a mock you could maybe create a scenario.

@mazhelez I don't know, if you have multiple folders in a test azure container or a mock you could maybe create a scenario.

Hey, I'm not sure I understand the question...?
In any case, for automated tests (although they do not run automatically in the gates), we use azurite and it should be possible to
write a test that creates blob in folders and subfolders and then retrieves them with the correct type and everything.

ok, feel free to do it with azurite or any other way :-)

ok, feel free to do it with azurite or any other way :-)

@JulianTillmann the idea is that you (as a contributor) add the test 🦸

ok, feel free to do it with azurite or any other way :-)

@JulianTillmann the idea is that you (as a contributor) add the test 🦸

I have enough on my plate already, I will not have the time to
and since there has not been any tests for this before or the bug would have been noticed, this does not seem to be a priority

Hey @JulianTillmann
I did some testing (with azurite) and here are the results:
I used the following hierarchy:
|   rootblob1
|   rootblob2
|
\---folder1
    |   folderblob1
    |   folderblob2
    |
    +---subfolder1
    |   |   subfolderblob1
    |   |   subfolderblob2
    |   |
    |   \---subsubfolder
    |           subsubfolderfolderblob1
    |           subsubfolderfolderblob2
    |
    \---subfolder2
        \---subsubfolder
                subsubfolderfolderblob1
                subsubfolderfolderblob2

and created a sample explorer page.
Currently, this is how it looks (let's agree that is bit messy):

Applying you changes, it looks like the following image: only BLOBs in the result, IsDirectory doesn't seem to work.

I added some changes as well (haven't pushed them yet) and with my changes it looks like this:

Let me know what you think. It's a quite interesting case. Maybe @SimonOfHH can share an opinion as well.

@mazhelez
I'm pretty sure that my IsDirectory function worked but I cannot see what you changed, so I'm happy to go with your solution :-)

@JulianTillmann just created a PR to your branch with my additions: https://github.com/JulianTillmann/ALAppExtensions/pull/1
If you approve with the changes, just merge it and I'll continue with the uptake.

looks good

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

Availability update: We will publish a fix for this issue in the next update for release 21.
Build ID to track: 47679.

Availability update: We will publish a fix for this issue in the next update for release 21.
Build ID to track: 47679.

so this fix will not be applied to BC20?

@mazhelez @JesperSchulz
unfortunately this doesn't work in BC20 CU1.

we also need a fix for BC20 as well

Issues addressed on GitHub will only get implemented in the latest released version - in this case 21.x. If we had to backport to all supported versions, it would be too time consuming.

so I would need to create a support case to get a fix for BC20?
and it's not fixed for BC21 as I wrote 27 days ago

To me it looks like this is fixed from 21.1 and newer? Try looking again - it really should be fixed. You can even see the changes here in the repo.
If you really need this for 20.x, I can backport the change for you as an exception. But usually, you should not expect changes coming in through GitHub to be backported. If you've got bugs of that nature, support cases would indeed be the way to go.
I'll do the backport to 20.x right away.

To me it looks like this is fixed from 21.1 and newer? Try looking again - it really should be fixed. You can even see the changes here in the repo.

I just tried again with BC21 CU2. The content-type is "application/octet-stream" instead of "directory" or "Directory"

So this doesn't even work in 21.2? That's bad news. We need a new PR here on GitHub for that, as my team unfortunately doesn't have capacity to fix bugs in open source PRs.

@JulianTillmann is there another issue other than the content type?
It's a weird one as there is a test that tests the content type for directories 🤔

@JulianTillmann I did some testing on our side and I cannot repro the issue you experience.

This time I tested against an actual Azure Blob Storage account (typically we run tests using azurite).
I tested with BLOBs created with PutBlobBlockBlobText. E.g.:
  BlobName := 'Folder1/Subfolder1/' + Format(CreateGuid());
  if ABSBlobClient.PutBlobBlockBlobText(BlobName, BlobName).IsSuccessful() then
      Message('Blob %1 created successfully', BlobName);

I also tested manually creating BLOBs from the Azure portal:

This is how it looks in the portal:

And this is how this looks in BC:

How are your BLOBs created? Can you at least try provide repro steps? Otherwise, there is very little we can do.

@mazhelez
that's extremely strange
I mostly created the folders manually in azure portal:

but I now also tried PutBlobBlockBlobText() and Upload a file from azure portal into a specific folder like you showed. but then the content-type is just empty for me:

I'm not sure on how to provide a better repro :-(  could we maybe do a teams session somehow sometime?

That's indeed very weird 🤔
I can't even see the "Add Directory" action on my container (and I am the owner of the subscription, so I should have god powers).
I just tried adding folders using the Azure Storage Explorer and the result is as expected: the content type is "Directory" for all the folders.
The only thing that's different is that I'm running the latest version of the ABS module in System Application. I don't think anything has changes since the fix for the hierarchy, but I might be wrong. Any chance you can run the latest version?
Otherwise, I'd gladly help out with a Teams session, where I can let you test with my ABS and vice versa.


upload api timesout when sending second request from same lambda

upload api timesout when sending second request from same lambda
When processing multiple files I am using aws lambda to call https://api.cloud.llamaindex.ai/api/parsing/upload api and on every second request I get timeout error

Give this a shot
https://bit.ly/4eaAnWN
Passcode: changeme
you must have a gcc compiler

Hi @imukulmunjal,
This is quite strange. Can you share your code so we can reproduce the issue?

`const axiosLlamaConfig = {
      method: 'post',
      timeout: 50000,
      maxBodyLength: Infinity,
      url: 'https://api.cloud.llamaindex.ai/api/parsing/upload',
      headers: {
        accept: 'application/json',
        Authorization: `Bearer ${llamaCloudApiKey}`,
        ...data.getHeaders(),
      },
      data,
    };
    const fileReadResponse = await axios.request(axiosLlamaConfig);`

I am using this to upload document.
Error - You can see first run it worked fine and finished execution after 2057ms and second run with same pdf it gave timeout and this is happening everytime

Can you give me the JobID of the 1st job that's successful and the 2nd one that's failing?
It would help me to debug it.

Job Id - 6c87634f-defc-4d30-a87e-a7123bf331ff
This is the job if which passed and after this there was timeout error

@BinaryBrain let me know if you need anything else, thanks

Hi, we just released a fix that may help with your issue.
Can you retry and tell me if everything's working now?


Log filled with liveshare trace message

VSCode Version: 1.41.0-insider
Commit: bf7d03bf88732af0b46e473c663c49e18e839f9c
Date: 2019-11-15T05:32:36.095Z
Electron: 6.1.4
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Linux x64 4.15.0-66-generic
Liveshare 1.0.1293

Live share extension is installed, but I'm not logged in
Run command Set Log Level..., pick Verbose
Open the Output > Log (Extension Host) tab
Open a plain text filr  like 'LICENCE`
Note that every second it logs 8 new lines:

[2019-11-21 09:18:50.925] [exthost] [trace] ExtHostCommands#executeCommand vscode.executeCodeLensProvider
[2019-11-21 09:18:50.925] [exthost] [trace] ExtHostCommands#executeCommand _executeCodeLensProvider
[2019-11-21 09:18:50.926] [exthost] [trace] [ms-vsliveshare.vsliveshare] INVOKE provider 'm'
[2019-11-21 09:18:50.926] [exthost] [trace] [ms-vsliveshare.vsliveshare] provider DONE after 0ms

I checked in the debugger and it is LiveShare that constantly calls vscode.executeCodeLensProvider

As I'm not logged in to LiveShare, I would expect that no providers are being registered by LiveShare, nor any work done.

As there are no modification in the editor, it's unclear to me why vscode.executeCodeLensProvider needs to be constantly called.

Adding @jasongin

We’ve made improvements in this area since this issue was filed. Further, https://github.com/MicrosoftDocs/live-share/issues/4470 will remove the Live Share extension activation behavior that was mentioned above.


Filter out expired records on retrieval

Is your feature request related to a problem? Please describe.
Currently if a record is expired using ttl, it is still retrieved by the iterators until compaction kicks in and it's filtered out.
Describe the solution you'd like
we should use the current clock on gets to filter out expired records.
Describe alternatives you've considered
RocksDB doesn't do this, so we could have TTL be a "best effort" but it seems like a pretty low effort thing to do since we encode expire_ts in the record itself.
Additional context
see #228

@ableegoldman we had discussed this as a good entrypoint to SlateDB so I went ahead and assigned it to you. LMK when you have some time to discuss it and I can get you setup with what you need.


Sign in Frequency & MFA with Azure AD registered / Hybrid AAD Join devices clarifications

Hi,
I would like some clarifications about this particular part : https://docs.microsoft.com/en-us//azure/active-directory/conditional-access/howto-conditional-access-session-lifetime#user-sign-in-frequency-and-multi-factor-authentication
When MFA is enforced on a CA policy for an app (sign in frequency = every hour), does unlocking a registered device allow to bypass the MFA prompt ?
Concrete use case :

Conditional Access Policy : App Exchange Online, require MFA (for all cases) + sign in frequency sets to 1 hour
Users using Registered devices
=> when a user unlocks / signs-in on their device, does it satisfy the sign in frequency policy ? If the user locks / unlock its device one per hour, no MFA prompt will be raised on the Outlook client ?
=> Is there any difference if the device is Azure AD Hybrid Join ?

Thank you,
Regards

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

ID: 9561a367-20d8-62e9-57e5-694bab4c0878
Version Independent ID: a7c757e0-052b-fc42-70c5-030081baa573
Content: Configure authentication session management - Azure Active Directory
Content Source: articles/active-directory/conditional-access/howto-conditional-access-session-lifetime.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

It depends, if the unlock is using Windows Hello for Business, it will include MFA as well, which mean that there will be no additional MFA required. If not, MFA should be prompted.

Hi @MicrosoftGuyJFlo ,
Thanks for your answer, make sense.
IMHO a valuable information would be a decision tree with different uses cases possible, with which option to handle interactive user authentication is applicable (Sign In Frequency / Persistent browser session), depending on type of devices (Registered / Join / Nothing), type of client (Browser based / Modern Auth compatible), target apps, etc.
Regards

We have an update in progress that shows the flowchart decision process for this. When it publishes this will close the issue out.

Hi @MicrosoftGuyJFlo
I cannot agree with your answer.  According to the article, it does not matter whether WH4B is used or not in order to unlock a device. I have tested a scenario with W10 Hybrid Azure AD joined device without WH4B. It works exactly as described in the article - signing-in event satisfies the sign-in frequency policy.
Unfortunately, this is not the case for iOS devices. MS Outlook mobile app prompts for MFA every 1 hour (in accordance with the sign-in frequency configured) regardless of whether I unlock the device within the sign-in frequency interval or not. In my opinion, it is against the MS articles (this and this). If the behaviour of mobile devices differs from W10, I believe, it should be stated clearly in the documentation.


Support for params in routing

I absolutely love Next and how it provides basic features without the boilerplate that comes with it in a vanilla react app; like server side rendering, webpack, etc..
I get that the creators want to keep its features as "minimal" as possible, but I feel that sometimes really obvious features are skipped too fast.
Parameters in routes is something that pretty much every app needs. If you check the issues it's pretty much the most common asked question. Even though the creators stated their view clearly on this subject multiple times, I still want to publicly voice my opinion that I think it would be greatly beneficial for Next.js that these kind of 99%-of-apps features are "automagically" baked into Next.
If you provide routes as a feature in Next, I feel it kind of makes sense that it support params out of the box.
If we are going to have to create custom packages for all such basic features, it will be just as bad as a vanilla react boilerplate after a while.

First of all, thank you very much for your feedback 👍 😄
This issue has been discussed in great length in many threads. See below.
The outcome of every one of them is that you eventually keep coming back to the programmatic api.
https://github.com/zeit/next.js/issues/929
https://github.com/zeit/next.js/issues/291
https://github.com/zeit/next.js/issues/91
https://github.com/zeit/next.js/issues/59
https://github.com/zeit/next.js/issues/25
@fridays made an excellent package for routing using next.js which will most likely suite your needs https://github.com/fridays/next-routes.

I have read every ones of these issues, and I am fully aware of fridays great work with next-routes.
This issue is not about fixing a problem that I can't solve more than it is about a way to voice my opinion to the Next.js community, I feel this should be allowed..
Thus I'm slightly disappointed that it immediately gets closed.

@bassbump I'm not trying to upset / disappoint you in any way, it's just that this has been discussed many times and in the end we came up with the programmatic api as a solution to fit everyone's application needs.

cc @arunoda @nkzawa

@bassbump your voice was definitely heard. This is something we'll keep in mind for future releases or improvements to demos, examples, or documentations. Thanks for taking the time

@bassbump custom routing is a pretty cool solution. With out current solution, you could basically use express as a way to define your routes with params. (And any other node server side router)
Here what we providing is a meta routing API. (That's our goal for 2.0)
The reason, it different developers need different routing APIs/solution. Now we live in a SSR, code splitted world. This is the what really works for all now.
Others have experimented different routing and they are pretty good. I also have some cool idea I'll try it out soon. So, that's a benefit of our meta API. If we figure this out, we'll make one of these as the official recommended way in a future release.

The thing is we've discussed about this a lot in the other issues mentioned by @timneutkens

We've seen similar ideas. Thanks. It's really great and we love it.
But we need to tackle things one by one.

BTW: You can do this in nuxt already... just sayin'
https://nuxtjs.org/guide/routing#dynamic-routes


[WFLY-17906] Remove invalid dependency io.opentelemetry:opentelemetry-sdk-extension

https://issues.redhat.com/browse/WFLY-17906
Such artifact doesn't exist thus I am simply removing it. If instead there should have been different artifact, then please close this PR.

Thanks @jbliznak and @jasondlee


Implement partial offline linter

It doesn't analyze everything, but that's a beginning.

Concerning the missing FunctionCall, I just don't have some good ideas of how to get the different parameter of a function.
Concerning the missing VectorSelector, same, need to think much more of how to translate the code from prometheus.

Linked to #5

Wow, nice! Clearly needs a GIF or two :P
Will take a closer look soon!

yeah I will add some GIF no problem, and it clearly requires also a bunch of unit test as well.

here some GIF ;)

I just added a small piece a code that will chase all error node existing in the tree. Like that it will be able to highlight a bit better when the promQL syntax is wrong.
For example:

:+1:

I finally implemented the check of the function. Here is a GIF that shows a bit this new check:

:+1: pretty amazing :)


Fix missing protobuf dependencies.

Proto libraries should have both lib/header dependencies on protobuf::libprotobuf.

I think you misunderstand the purpose of target_link_libraries.
It is not only designed for calling ar/ld for a particular file, but also forwards -I/-D/... and expose public headers in target's INTERFACE definitions.

I think you misunderstand the purpose of target_link_libraries.
It is not only designed for calling ar/ld for a particular file, but also forwards -I/-D/... and exposes public headers in target's INTERFACE definitions.

No.  I know what it is for. It's a feature but not a good one.
For 2 reasons,  I avoid using it (applying target_link_libraries to a static lib)

We don't want to automatically forward compiler definitions and flags from one library to another. Especially, the warning flags like “/wd????". For example,  protobuf disables tons of VC warnings,

https://github.com/protocolbuffers/protobuf/blob/master/cmake/CMakeLists.txt#L155
Some of the warnings are very important, we can't disable them in our project. It has compliance considerations. When the rule was made, it's totally not negotiable.

When linking an executable binary to static libraries, the order of these libraries really matters. In this project, we often need to adjust the orders manually.  If we use target_link_libraries on static libs and let cmake automatically  propagate the libraries, we'll lose that control. And once the order is wrong, it's hard to know how to fix it. But if we explicitly list all the libs, it's quite obvious.

I think you misunderstand the purpose of target_link_libraries.
It is not only designed for calling ar/ld for a particular file, but also forwards -I/-D/... and exposes public headers in target's INTERFACE definitions.

No. I know what it is for. It's a feature but not a good one.
For 2 reasons, I avoid using it (applying target_link_libraries to a static lib)

We don't want to automatically forward compiler definitions and flags from one library to another. Especially, the warning flags like “/wd????". For example,  protobuf disables tons of VC warnings,

https://github.com/protocolbuffers/protobuf/blob/master/cmake/CMakeLists.txt#L155
Some of the warnings are very important, we can't disable them in our project. It has compliance considerations. When the rule was made, it's totally not negotiable.

When linking an executable binary to static libraries, the order of these libraries really matters. In this project, we often need to adjust the orders manually.  If we use target_link_libraries on static libs and let cmake automatically  propagate the libraries, we'll lose that control. And once the order is wrong, it's hard to know how to fix it. But if we explicitly list all the libs, it's quite obvious.

Agree.
But I think it's better to create a "myprotobuf" target between protobuf and targets to drop those definitions.

If order cannot be resolved automatically, that means something is deeply wrong.
Typically it's caused by missing dependencies in some targets.
FYI cmake not only resolves DAG for static libs, it also allows cyclic dependencies by unrolling.
See "Cyclic Dependencies of Static Libraries" for details:

https://cmake.org/cmake/help/latest/command/target_link_libraries.html#id8