nmea_topic_driver is not publishing anything

Hi!
I created a rosbag that contains NMEA messages (nmea_msgs/Sentence), and I would like to generate sensor_msgs/NavSatFix messages.
I am working on simulating time, so I run:
rosparam set use_sim_time true

Then, I play the rosbag thats contains the NMEA messages
rosbag play --clock nmea_gps.bag

Then, I start the nmea_topic_driver to generate publish sensor_msgs/NavSatFix on /fix topic:
rosrun nmea_navsat_driver nmea_topic_driver

Finally, when I check with rostopic if there are message on /fix topic
rostopic echo /fix

WARNING: no messages received and simulated time is active.
Is /clock being published?

Any, idea of what is going on?
I check if nmea_topic_driver was subscribed to the NMEA messages properly, and it looks fine:
rostopic info /nmea_sentence
Type: nmea_msgs/Sentence

Publishers:
 * /play_1516740862743383627 (http://MS-7A15:46035/)

Subscribers:
 * /nmea_topic_driver (http://MS-7A15:46775/)

I also checked if the NMEA messages were right, and they look fine too:
rostopic echo /nmea_sentence

header:
  seq: 0
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 488000000
  frame_id: "GPS-RTK"
sentence: "$GPRMC,152545.80,A,3301.9913392,S,06053.0775644,W,0.12,0.00,261217,0.0,E,D*3F\r\n"
---
header:
  seq: 1
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 488000000
  frame_id: "GPS-RTK"
sentence: "$GPGGA,152545.80,3301.9913392,S,06053.0775644,W,5,09,1.0,52.356,M,17.442,M,0.2,*72\r\
  \n"
---
header:
  seq: 2
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 488000000
  frame_id: "GPS-RTK"
sentence: "$GPGSA,A,3,02,12,24,25,29,,,,,,,,12.0,1.7,11.8,1*29\r\n"
---
header:
  seq: 3
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 488000000
  frame_id: "GPS-RTK"
sentence: "$GLGSA,A,3,75,76,86,87,,,,,,,,,43.1,15.6,40.1,2*03\r\n"
---
header:
  seq: 4
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 488000000
  frame_id: "GPS-RTK"
sentence: "$GPGSV,2,1,05,02,52,107,35,12,61,145,38,24,49,007,37,25,48,217,36,1*6A\r\n"
---
header:
  seq: 5
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 488000000
  frame_id: "GPS-RTK"
sentence: "$GPGSV,2,2,05,29,47,283,41,,,,,,,,,,,,,1*55\r\n"
---
header:
  seq: 6
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 488000000
  frame_id: "GPS-RTK"
sentence: "$GLGSV,1,1,04,75,42,053,37,76,75,160,36,86,72,178,39,87,41,315,35,1*7F\r\n"
---
header:
  seq: 7
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 488000000
  frame_id: "GPS-RTK"
sentence: "$GPGST,152545.80,0.090,,,,0.081,0.061,0.194*78\r\n"
---
header:
  seq: 8
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 488000000
  frame_id: "GPS-RTK"
sentence: "$GPVTG,0.00,T,0.00,M,0.12,N,0.06,K,A*26\r\n"
---

The output of rosnode info /nmea_topic_driver is:
rosnode info /nmea_topic_driver

Node [/nmea_topic_driver]
Publications:
 * /fix [sensor_msgs/NavSatFix]
 * /rosout [rosgraph_msgs/Log]
 * /time_reference [sensor_msgs/TimeReference]
 * /vel [geometry_msgs/TwistStamped]

Subscriptions:
 * /clock [rosgraph_msgs/Clock]
 * /nmea_sentence [nmea_msgs/Sentence]

Services:
 * /nmea_topic_driver/get_loggers
 * /nmea_topic_driver/set_logger_level

contacting node http://MS-7A15:34339/ ...
Pid: 28973
Connections:
 * topic: /rosout
    * to: /rosout
    * direction: outbound
    * transport: TCPROS
 * topic: /nmea_sentence
    * to: /play_1516817666576416404 (http://MS-7A15:38155/)
    * direction: inbound
    * transport: TCPROS
 * topic: /clock
    * to: /play_1516817666576416404 (http://MS-7A15:38155/)
    * direction: inbound
    * transport: TCPROS

Thanks in advance

Can you share your bag so I can try to replicate the problem?

Thanks for the answer. The issue was solved when we removed the CR (Carriage Return) and the LF (Line Feed) control characters from the nmea sentences.

I have same problem. What are CR and LF?

You have to delete them from the nmea sentences. These characters are invisible, so you have to remove them from the nmea sentences. They are located at the end of each nmea sentence.

I encountered the same problem and resolved with the same way.
However, I'm wondering why nmea_navsat_driver does not accept a sentence with CR and LF.
The format guidline let us put them in the end:
https://en.wikipedia.org/wiki/NMEA_0183


Update for dart keyword.

Add some keyword.
The document of dart keyword in website.

Thank you for making this PR @CaiJingLong!
To make the build pass, you have to install Prism's dependencies with npm ci and then run npx gulp.

Thank you for contributing!


Flutter application can't run on windows

Every time I try to run a flutter application (even  hello world) on Windows, I get the following error:
[  +91 ms] Launching lib\main.dart on Windows in debug mode...
[ +153 ms] Building Windows application...
[ +126 ms] **********************************************************************
[        ] ** Visual Studio 2019 Developer Command Prompt v16.1.3
[   +1 ms] ** Copyright (c) 2019 Microsoft Corporation
[   +1 ms] **********************************************************************
[ +915 ms] [vcvarsall.bat] Environment initialized for: 'x64'
[  +47 ms] Microsoft (R) Build Engine version 16.1.76+g14b0a930a7 for .NET Framework
[        ] Copyright (C) Microsoft Corporation. All rights reserved.
[        ] MSBUILD : error MSB1009: Project file does not exist.
[        ] Switch: Runner.sln
[   +5 ms] Building Windows application... (completed in 1.1s)
[   +2 ms] "flutter run" took 8,549ms.
[        ] "flutter run" took 8,549ms.
Build process failed

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      buildWindows (package:flutter_tools/src/windows/build_windows.dart:83:5)
<asynchronous suspension>
#2      WindowsDevice.startApp (package:flutter_tools/src/windows/windows_device.dart:85:13)
<asynchronous suspension>
#3      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:371:54)
<asynchronous suspension>
#4      HotRunner.run (package:flutter_tools/src/run_hot.dart:247:39)
<asynchronous suspension>
#5      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:476:37)
<asynchronous suspension>
#6      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:477:18)
<asynchronous suspension>
#7      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:383:33)
<asynchronous suspension>
#8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:154:29)
<asynchronous suspension>
#9      _rootRun (dart:async/zone.dart:1124:13)
#10     _CustomZone.run (dart:async/zone.dart:1021:19)
#11     _runZoned (dart:async/zone.dart:1516:10)
#12     runZoned (dart:async/zone.dart:1463:12)
#13     AppContext.run (package:flutter_tools/src/base/context.dart:153:18)
<asynchronous suspension>
#14     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:375:20)
#15     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
<asynchronous suspension>
#16     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:396:21)
<asynchronous suspension>
#17     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:154:29)
<asynchronous suspension>
#18     _rootRun (dart:async/zone.dart:1124:13)
#19     _CustomZone.run (dart:async/zone.dart:1021:19)
#20     _runZoned (dart:async/zone.dart:1516:10)
#21     runZoned (dart:async/zone.dart:1463:12)
#22     AppContext.run (package:flutter_tools/src/base/context.dart:153:18)
<asynchronous suspension>
#23     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:356:19)
<asynchronous suspension>
#24     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:112:25)
#25     new Future.sync (dart:async/future.dart:224:31)
#26     CommandRunner.run (package:args/command_runner.dart:112:14)
#27     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:242:18)
#28     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:22)
<asynchronous suspension>
#29     _rootRun (dart:async/zone.dart:1124:13)
#30     _CustomZone.run (dart:async/zone.dart:1021:19)
#31     _runZoned (dart:async/zone.dart:1516:10)
#32     runZoned (dart:async/zone.dart:1500:12)
#33     run.<anonymous closure> (package:flutter_tools/runner.dart:60:18)
<asynchronous suspension>
#34     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:154:29)
<asynchronous suspension>
#35     _rootRun (dart:async/zone.dart:1124:13)
#36     _CustomZone.run (dart:async/zone.dart:1021:19)
#37     _runZoned (dart:async/zone.dart:1516:10)
#38     runZoned (dart:async/zone.dart:1463:12)
#39     AppContext.run (package:flutter_tools/src/base/context.dart:153:18)
<asynchronous suspension>
#40     runInContext (package:flutter_tools/src/context_runner.dart:57:24)
<asynchronous suspension>
#41     run (package:flutter_tools/runner.dart:51:10)
#42     main (package:flutter_tools/executable.dart:63:9)
<asynchronous suspension>
#43     main (file:///C:/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#44     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:303:32)
#45     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

Flutter doctor output:
[√] Flutter (Channel master, v1.8.2-pre.56, on Microsoft Windows [Version 10.0.17134.829], locale en-US)
    • Flutter version 1.8.2-pre.56 at C:\flutter
    • Framework revision 90326b6184 (5 hours ago), 2019-07-12 09:46:48 +0530
    • Engine revision d1dcd18486
    • Dart version 2.5.0 (build 2.5.0-dev.1.0 24725a8559)

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.1.6)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.1.29102.190

[√] Android Studio (version 3.4)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 36.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

same bug on IOS since v1.7.8+hotfix.3 when I use Android simulator

MSBUILD : error MSB1009: Project file does not exist.

The project you are trying to run hasn't been correctly set up to run on Windows. Where did you get the windows directory that you are using to add Windows support to the project?

the windows directory get generated automatically, when I run the flutter run command

windows directory contains only one file named Generated.props

A project as created by flutter create doesn't support running on Windows, you currently need to set it up manually. See flutter.dev/desktop, especially https://github.com/flutter/flutter/wiki/Desktop-shells#using-the-shells
Closing as a duplicate of #35271

@stuartmorgan I just ran into the same issue with latest master. Do we still have to setup the project manually?

I just ran into the same issue with latest master. Do we still have to setup the project manually?

Yes

https://github.com/flutter/flutter/wiki/Desktop-shells#create is the current link.


FYI: AGPL licensing

This is a nice library, and fast too (I ran my own benchmarks as well) :) Sadly I cannot use it for work due to its AGPL license.
You probably know that AGPL requires modified code to be shared with the public and remain under the AGPL license. Also any code linked to the GPL/AGPL code (either dynamically or statically) is considered a combined work and the entire combination must be licensed under GPL/AGPL. So the code I write for work would also have to be open sourced as GPL/AGPL.
Sadly my employer won't want to share the rest of our codebase that might use this library.

Hello 👋
What license do you think is best suited here? I'll have a look on my side too :)

I like the MIT license since it works for open source and proprietary software and is written in clear language.

I'll take a look at this tomorrow then :)

Wow thanks man!

No worries


Add More Examples

What does this PR do?
Adds more examples, specifically:

Customize item list based on device
Customize buttonText

Codecov Report

Merging #13 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #13   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines          66     66
=====================================
  Hits           66     66

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 76a4e66...3bda2c9. Read the comment docs.

Pull Request Test Coverage Report for Build 34

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.078%

Totals

Change from base Build 33:
0.0%

Covered Lines:
66

Relevant Lines:
66

💛  - Coveralls


Fix gitlab failing if protos doesn't need to run

Right now GitLab will fail if we didn't update anything that makes the protos job run, for example adding meeting notes or adjusting settings.json.
This is because the preview:protos job needs the protos job. To make the preview:protos job conditional on whether the protos job ran, we should use a when condition in the GitLab CI/CD configuration. This setting can prevent the preview:protos job from failing if the protos job did not produce new artifacts, such as when the only changes are in files like .eslint or settings.json.

Hey, sorry: I fixed this yesterday in https://github.com/Couchers-org/couchers/pull/5039 but didn't mention on slack! Sorry for the wasted effort!

Fixed in #5039


Use without internet connection

Hello! Great work, thank you! I wonder if there is a way to use these apps without an internet connection? Thank you

Hi @shionSo, unfortunately, this isn't possible. Log decryption requires a keychain that is provided by DJI servers. Only the keychains are exchanged — your logs remain on your device.


Is there a way to remove the cudaMalloc overhead in benchmark?

Request description
When I run the benchmark for matmul on CUDA, iree reports unreasonably bad performance. According to Nsight System, it seems like although iree has pretty good kernel performance, however, since it includes the cudaMalloc overhead, so it reports really bad perf.

IREE result:
---------------------------------------------------------------------------------------------------
Benchmark                                         Time             CPU   Iterations UserCounters...

What component(s) does this issue relate to?
Other
Additional context
No response

What are you running specifically for "the benchmark for matmul on CUDA"? A profile/trace (or larger screenshot from nsight) would help qualify what you are measuring.
One thing you can try is running with --device_allocator=caching. That caches allocations between runs, which is useful for static workloads during benchmarking.

What are you running specifically for "the benchmark for matmul on CUDA"?

I'm trying to measure the bare matmul performance of iree. So I wrote a pytorch model which only contains nn.Linear and export it to tosa dialect using torch-mlir. And then use this command to compile
./iree-build/tools/iree-compile --iree-hal-target-backends=cuda --iree-hal-cuda-llvm-target-arch=sm_86 -o linear linear.mlir

And this command to profile the performance.
./iree-build/tools/iree-benchmark-module --module=linear.vmfb \
    --iree-hal-target-backends=cuda --device=cuda://0 \
    --function=forward \
    --device_allocator=caching \
    --input=1x64x768xf16=-1 --benchmark_repetitions=10

However, adding --device_allocator=caching would still produce the similar result.
---------------------------------------------------------------------------------------------------
Benchmark                                         Time             CPU   Iterations UserCounters...
---------------------------------------------------------------------------------------------------
BM_forward/process_time/real_time              1.02 ms         1.14 ms          662 items_per_second=978.87/s
BM_forward/process_time/real_time             0.847 ms        0.911 ms          662 items_per_second=1.18089k/s
BM_forward/process_time/real_time             0.795 ms        0.856 ms          662 items_per_second=1.25826k/s
BM_forward/process_time/real_time             0.686 ms        0.761 ms          662 items_per_second=1.4585k/s
BM_forward/process_time/real_time             0.429 ms        0.469 ms          662 items_per_second=2.33169k/s
BM_forward/process_time/real_time             0.215 ms        0.252 ms          662 items_per_second=4.66178k/s
BM_forward/process_time/real_time             0.584 ms        0.628 ms          662 items_per_second=1.71309k/s
BM_forward/process_time/real_time             0.938 ms         1.04 ms          662 items_per_second=1.06586k/s
BM_forward/process_time/real_time             0.517 ms        0.570 ms          662 items_per_second=1.93588k/s
BM_forward/process_time/real_time             0.473 ms        0.521 ms          662 items_per_second=2.11314k/s
BM_forward/process_time/real_time_mean        0.650 ms        0.715 ms           10 items_per_second=1.8698k/s
BM_forward/process_time/real_time_median      0.635 ms        0.694 ms           10 items_per_second=1.5858k/s
BM_forward/process_time/real_time_stddev      0.253 ms        0.277 ms           10 items_per_second=1.08292k/s
BM_forward/process_time/real_time_cv          38.83 %         38.70 %            10 items_per_second=57.92%

Since it will still has a lot of cuMemAlloc.

While the kernel time is at about an average of ~0.0041 ms.

Although a little bit launch overhead is accepted, the overhead of iree benchmark is quite large. Comparing to pytorch, it only has about 0.031ms launch overhead with a average kernel perf of ~0.0046ms

Can I remove the cudaMalloc completely? or at least exclude it from the perf report so that I can get the more accurate kernel performance.

@benvanik something seems off here. I wouldn't expect such a simple example to be doing intermediate allocs, and if it isn't, then it seems like we might be benchmarking result allocs. If this were being invoked in something like pytorch, we would be using the calling convention for pre-allocated result buffers. I expect that since benchmark-module is not doing that, the allocation is happening "inside" and being measured. Am I thinking about this right? Is there a way with benchmark-module to have it pass a tied result buffer slab to simulate how this would be done in a real integration?

Thanks for the help!
FYI This zip contains the original mlir file and the nsys report of pytorch and iree.
linear_64_768_768.zip

iree-benchmark-module precisely matches the behavior of iree-run-module - there's no special behavior there (and won't be) - so best to think of how your program runs and what it requires and whether it's through iree-run-module or iree-benchmark-module just as a difference in whether we run it once and print out results or run it many times and print out statistics.
Thus, if your program allocates result buffers before returning iree-benchmark-module will benchmark those allocations - this is what allows it to be a useful benchmarking tool for what you'd expect if you ran it outside of benchmarking. There won't be any additional allocations in iree-benchmark-module than when it would normally run as it's exactly the same.
If you want to avoid the result allocations you can pass in buffers - but this is orthogonal to benchmarking - if you define your program to take in output buffers and modify the IR to use them then both iree-run-module and iree-benchmark-module (and whatever you'd use to run the program from your application) will have identical behavior and require you to pass the output buffers in.
Now all that said, unless you are running one-shot you're going to want the caching allocator and you're going to want it everywhere (benchmarking and not). So if you pass --device_allocator=caching to iree-benchmark-module (and you should) then you also want to pass it to iree-run-module and do the same thing (configure the caching allocator) in your hosting application. That's because we behave consistently across all surfaces and don't have special behavior based on how something is run.
As for how to use output buffers you have two choices: the easy way to hack into IR and the better way that you change your frontend for. To hack the IR, for any result you want to store into a provided buffer you add one !hal.buffer (or !hal.buffer_view) function argument with the iree.abi.output attribute specifying which result it is the storage for. So:
util.func @foo(%arg0: tensor<?x8x8x3xf32>, %ret0: !hal.buffer {iree.abi.output = 0 : index}, %ret1: !hal.buffer {iree.abi.output = 1 : index}) ->
    (tensor<?x8x8x3xf32>, tensor<?x8x8x3xf32>) {

Note that you must still return the results - only when using this what's returned is just a reference to the storage with its final shape instead of an allocation of a device buffer - otherwise it's the same.
When calling you can then allocate one buffer per result yourself, or ideally one large buffer and use iree_hal_buffer_subspan to slice it up and pass it in. In the tools you can use the & prefix to indicate that an input is passed by-reference:
$ iree-run-module (or iree-benchmark-module) --input=1x8x8x3xf32=100 --input=&1x8x8x3xf32 --input=&1x8x8x3xf32

You can also initialize the inputs if doing in-place updates by giving them values.
The best way to do it, though, is to set up the ABI from the frontend using the hal.tensor.import/hal.tensor.export ops instead of the attributes. This lets you group multiple results in the same buffers.

Thanks Ben, I was being imprecise when I was saying "make benchmark-module" do this. What I was actually asking was how to do the output buffer thing in the program and then benchmark that.
I've got it on my list to add this properly to the torch frontend as I need it for some serving cases (and the previous times I've done this it has been ad-hoc).
But as you say, it should still be possible to get approximately what is being asked for with the caching allocator, and I'm wondering if there is a problem here or more things to try.

Thanks for the really detailed explanation. If I understand correctly, simply using the aforementioned compile command would not move the result allocation to a pre allocated buffer. Is this possible to reuse such conversion as a WAR? If not(a naive question), how to lower the exported TOSA dialect to the iree dialect so that I can modify the result buffer behavior and then compile it to vmfb file? Thanks!

Yeah, the pipelines defaulting to generate programs with all results allocated internally is a bias from a long time back -- and it is a lot easier to write with fewer sharp edges. For a lot of big workloads/graphs, the impact is much less than if trying to do a single kernel launch with tight constraints. The tools should work for that, but it isn't the dominant case that folks are generally working on.
The TOSA input pipeline is mostly just taking the defaults, so it should convert func.func to the internal util.func and preserve those ABI attributes. You can just hack it directly.
For example, I changed the func line to this:
  func.func @forward(%arg0: tensor<1x64x768xf16>, %arg1: !hal.buffer {iree.abi.output = 0 : index}) -> tensor<1x64x768xf16> {

Then ran this:
iree-compile --iree-hal-target-backends=llvm-cpu iree_linear_64_768_768.mlir -o /dev/null --mlir-print-ir-after-all --mlir-elide-elementsattrs-if-larger=100 2>&1 | less

And paged down to WrapEntryPointsPass to see how that got converted. There you see this:
  util.func public @forward(%arg0: !hal.buffer_view, %arg1: !hal.buffer) -> !hal.buffer_view attributes {iree.abi.stub, iree.reflection = {iree.abi.declaration = "sync func @forward(%input0: tensor<1x64x768xf16>, %input1: !hal.buffer {iree.abi.output = 0 : index}) -> (%output0: tensor<1x64x768xf16>)"}} {
    %0 = hal.tensor.import %arg0 "input0" : !hal.buffer_view -> tensor<1x64x768xf16>
    %1 = util.call @_forward(%0, %arg1) : (tensor<1x64x768xf16>, !hal.buffer) -> tensor<1x64x768xf16>
    %2 = hal.tensor.export %1 "output0" into(%arg1 : !hal.buffer) : tensor<1x64x768xf16> -> !hal.buffer_view
    util.return %2 : !hal.buffer_view
  }
  util.func private @_forward(%arg0: tensor<1x64x768xf16>, %arg1: !hal.buffer {iree.abi.output = 0 : index}) -> tensor<1x64x768xf16> {
    %cst = arith.constant 0.000000e+00 : f16
    %cst_0 = arith.constant dense_resource<__elided__> : tensor<768x768xf16>
    %0 = tensor.empty() : tensor<768x768xf16>
    %transposed = linalg.transpose ins(%cst_0 : tensor<768x768xf16>) outs(%0 : tensor<768x768xf16>) permutation = [1, 0]
    %expanded = tensor.expand_shape %transposed [[0, 1], [2]] : tensor<768x768xf16> into tensor<1x768x768xf16>
    %1 = tensor.empty() : tensor<1x64x768xf16>
    %2 = linalg.fill ins(%cst : f16) outs(%1 : tensor<1x64x768xf16>) -> tensor<1x64x768xf16>
    %3 = linalg.batch_matmul ins(%arg0, %expanded : tensor<1x64x768xf16>, tensor<1x768x768xf16>) outs(%2 : tensor<1x64x768xf16>) -> tensor<1x64x768xf16>
    util.return %3 : tensor<1x64x768xf16>
  }

Note the hal.tensor.export into the provided buffer. This is the default behavior Ben was describing.
I haven't actually tried running it, but this looks like the compiled form I would expect. I still think you should be able to get a result that is doing approximately the same work as the Torch version using allocator settings (which is how Torch amortizes its allocations).

While not needed in this case, if you want to hack on internal dialect forms (vs TOSA/frontend), you can use --compile-to. Can help when poking on things that aren't exposed to all frontends. Example:
iree-compile --iree-hal-target-backends=llvm-cpu iree_linear_64_768_768.mlir --compile-to=input --mlir-elide-elementsattrs-if-larger=100

Great! Thanks for the example! I'll try it myself. Really appreciate the help.
As for this issue, I'll leave it open for further discussion on what can iree do for the output buffer benchmarking. Feel free to close it.

Let us know your findings. There's too much tribal knowledge on this, and we should at least close the issues with some docs or a sample. But would like to document something that we know works :)

Let us know your findings.

Sure👌

Note that providing output storage is largely incompatible with dynamic shapes, conditional execution, or proper async (which is why we don't do it by default). We do support using less storage (so if you pass in a buffer that could hold tensor<4096xf32> but only produce a tensor<4xf32> we'll just store that and return the buffer view with the shape 4xf32). In async mode the disadvantage is that you preallocate and wire the memory before you begin running instead of letting it be allocated on-demand (possibly reusing input buffers that are dead after being consumed). Basically, output args are a special case that only works in certain situations - those may be always for certain users (static shapes only, already existing persistent storage, synchronous execution or their own scheduling) but not something that's a safe or usable default.

Sorry for the late reply, took some time on physically fix the down server. Using the provided steps, I can observe that there is no such cudaMalloc overhead. That is,

Add the output buffer as function argument
Run with --device_allocator=caching --input=1x64x768xf16=-1 --input="&1x64x768xf16"

The modification to the mlir file is so simple that I simply wrote a python script which only modify the function args. And it works pretty fine. So I'm comfortable with this approach.
And the perf result basically reflex the real kernel performance.
---------------------------------------------------------------------------------------------------
Benchmark                                         Time             CPU   Iterations UserCounters...

Nice!
Not related to the issue you were having, but if trying to benchmark for real, you should generate real inputs (from a random or other source with entropy). The tools take npy files for input and we usually generate them in python and pass them in.
The reason is that on a lot of modern hardware, moving repeating patterns of bits across memory fabrics can be a lot more efficient than moving "real" values. This can result in parts of the machine experiencing different power utilization and can throw performance measurements off. It's a good practice to always test with data of a similar distribution as the real thing.

which seems to be introduced by the benchmark itself

By default the compiler uses a synchronous ABI, which puts the sync "inside" the workload. The reason is historical but suffice to say that it is a lot harder to screw up and the convention held.
There is an alternative ABI ("coarse-fences") which externalizes the synchronization handles so they are passed in to the function and allows the caller to do arbitrary synchronization. That is used for any high performance integrations, but it is harder to use. The tooling will detect it and do the right thing, but I think it will still do a wait inside the benchmark loop to ensure the pipeline completed.
When coming from torch, the compiler builds both ABIs and makes the async one available with a special function name suffix. But we haven't done that work on other input pipelines. There is a generic way to do it, but as Ben says, it isn't compatible with this abi.output thing you are doing right now.
If you can get what you need without getting into the exciting world of async benchmarking, I'd recommend not going down this rabbit hole until you need to since there are things that don't quite connect up on all of the paths. We use these modes for production cases, but the simpler stuff is easier to iterate on.

Thanks for the explanation on all of my questions.

The reason is that on a lot of modern hardware, moving repeating patterns of bits across memory fabrics can be a lot more efficient than moving "real" values.

Though this mechanism is straight-forward, but it surprises me that this feature happens in the real-world case.
As for the benchmark part, I see the burden here for async benchmarking. Actually, as for now, I'm satisfied for the currently status. So I'll take the advice not to dwell on this case.
Also, thanks again for the detailed answers to these questions! 🚀

You want to run way more than a single dispatch at a time - otherwise you are indeed just measuring cold start time and synchronization. For example, our dispatch benchmarks have a batch size argument that lets the benchmarking tool specify how many to run at a time and averages the number between them. You could just dispatch the same thing N times and pass --batch_size=N to have the tool do the math for you.
But key thing it to not try to benchmark single dispatches.


Add support for telescope theme

It would be nice to also support the use of telescope themes

i second this 👍

Hi, I'm not entirely sure what telescope-undo does not support. Can you give me an example? To my knowledge, all config options are respected.

Hello!
Below is the screenshot of what we meant. Take for example the extension file browser below has the theme set to "ivy". The Ui appears like that.
But if you set the theme of Undo to "ivy". It will still look like the default theme.
Telescope File-Browser theme set to "ivy"

Telescope Undo theme set to "ivy"

TIL about the literal theme key, thanks! I've added support for that, hope it works for you 👍🏻


Publish to crates.io

The old crates published by @GGist are now quite out-of-date.
It would be nice to upgrade the #21 dependency before publishing, however I don't think that it is critical.
I do need to research how to publish a package from a virtual workspace. I guess it will be no problem.
https://github.com/torrust/torrust-tracker/blob/develop/.github/workflows/publish_crate.yml
Overall It would be nice to get some alpha releases soon for testing.

👋 @GGist we will need some cooperation from you if we wish to continue using the same package names on crates.io .


MTCAP3: wrong gateway_id reported by concentratord to mqtt-forwarder

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

What happened?
Using MTCAP3 gateway and the latest concentratord/mqtt-forwarder chirpstack pre-compiled packages, the gateway_id reported by the concentratord (or read by the mqtt-forwarder) does not match the configured gateway_id inside concentratord.toml configuration file:

gateway_id="0000000000000000"

After starting concentratord/mqtt-forward processes, the following can be seen in the logs:

2023-12-13T13:41:21.293871+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Starting the concentrator
2023-12-13T13:41:23.807940+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Gateway ID retrieved, gateway_id: "0016c001f1388eb8"
2023-12-13T13:44:49.899489+00:00 mtcap3 chirpstack-mqtt-forwarder[1793]: Reading gateway id
2023-12-13T13:44:49.913138+00:00 mtcap3 chirpstack-mqtt-forwarder[1793]: Received gateway id, gateway_id: 0016c001f1388eb8
2023-12-13T13:44:49.914460+00:00 mtcap3 chirpstack-mqtt-forwarder[1793]: Received Gateway ID from backend, gateway_id: 0016c001f1388eb8

This does not occur on a MTCDT gateway.
What did you expect?
I would expect the reported gateway id by concentratord/mqtt-forwarder to matches the gateway id as defined in the concentratord.toml configuration file on the MTCAP3 gateway.
Steps to reproduce this issue
Steps:

On the MTCAP3, setup a mqtt-forwarder + concentratord.
Set the gateway_id parameter to whatever value in concentratord.toml configuration file
Restart the mqtt-forwarder / concentratord processes.
Inspect the logs, gateway id reported by concentratord / mqtt-forwarder will not match the one defined in concentratord.toml configuration file

Could you share your log output?

2023-12-13T13:41:54.072747+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Stopping the concentrator
2023-12-13T13:41:54.079098+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Updating concentrator configuration
2023-12-13T13:41:54.080469+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Starting Concentratord SX1302 (version: 4.3.4, docs: https://www.chirpstack.io/docs/chirpstack-concentratord/)
2023-12-13T13:41:54.081765+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Executing reset command, command: mts-io-sysfs, args: ["store", "lora/reset", "0"]
2023-12-13T13:41:54.219920+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Executing reset command, command: mts-io-sysfs, args: ["store", "lora/reset", "1"]
2023-12-13T13:41:54.361003+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Setting i2c device path, path: /dev/i2c-1
2023-12-13T13:41:54.361362+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Setting board configuration, lorawan_public: true, clock_source: 0, com_type: Spi, com_path: /dev/spidev1.0
2023-12-13T13:41:54.361648+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Setting up fine timestamp, enable: false
2023-12-13T13:41:54.361892+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Setting up concentrator channels
2023-12-13T13:41:54.362205+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring radio, radio: 0, enabled: true, center_freq: 902700000, type: SX1250
2023-12-13T13:41:54.362472+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring radio, radio: 1, enabled: true, center_freq: 903700000, type: SX1250
2023-12-13T13:41:54.362691+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Setting up concentrator channels
2023-12-13T13:41:54.362993+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring multi-SF LoRa channel, channel: 0, enabled: true, freq: 902300000, rf_chain: 0, if_freq: -400000
2023-12-13T13:41:54.363272+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring multi-SF LoRa channel, channel: 1, enabled: true, freq: 902500000, rf_chain: 0, if_freq: -200000
2023-12-13T13:41:54.363541+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring multi-SF LoRa channel, channel: 2, enabled: true, freq: 902700000, rf_chain: 0, if_freq: 0
2023-12-13T13:41:54.363795+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring multi-SF LoRa channel, channel: 3, enabled: true, freq: 902900000, rf_chain: 0, if_freq: 200000
2023-12-13T13:41:54.368515+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring multi-SF LoRa channel, channel: 4, enabled: true, freq: 903100000, rf_chain: 0, if_freq: 400000
2023-12-13T13:41:54.369768+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring multi-SF LoRa channel, channel: 5, enabled: true, freq: 903300000, rf_chain: 1, if_freq: -400000
2023-12-13T13:41:54.371004+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring multi-SF LoRa channel, channel: 6, enabled: true, freq: 903500000, rf_chain: 1, if_freq: -200000
2023-12-13T13:41:54.372219+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring multi-SF LoRa channel, channel: 7, enabled: true, freq: 903700000, rf_chain: 1, if_freq: 0
2023-12-13T13:41:54.373417+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring Std LoRa channel, enabled: true, freq: 903000000, rf_chain: 0, if_freq: 300000
2023-12-13T13:41:54.374594+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Configuring FSK channel, enabled: false, freq: 0, rf_chain: 0, if_freq: 0
2023-12-13T13:41:54.376791+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Starting the concentrator
2023-12-13T13:41:56.882896+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Gateway ID retrieved, gateway_id: "0016c001f1388eb8"
2023-12-13T13:41:56.884252+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Initializing JIT queue, capacity: 32
2023-12-13T13:41:56.885795+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Creating socket for publishing events, bind: ipc:///tmp/concentratord_event
2023-12-13T13:41:56.892755+00:00 mtcap3 chirpstack-concentratord-sx1302[1521]: Creating socket for receiving commands, bind: ipc:///tmp/concentratord_command
2023-12-13T13:44:29.661536+00:00 mtcap3 chirpstack-mqtt-forwarder[1744]: Starting ChirpStack MQTT Forwarder (version: 4.1.3, docs: https://www.chirpstack.io/)
2023-12-13T13:44:29.662329+00:00 mtcap3 chirpstack-mqtt-forwarder[1744]: Setting up ChirpStack Concentratord backend
2023-12-13T13:44:29.663187+00:00 mtcap3 chirpstack-mqtt-forwarder[1744]: Setting up ChirpStack Concentratord backend
2023-12-13T13:44:29.665181+00:00 mtcap3 chirpstack-mqtt-forwarder[1744]: Connecting to Concentratord event API, event_url: ipc:///tmp/concentratord_event
2023-12-13T13:44:29.667677+00:00 mtcap3 chirpstack-mqtt-forwarder[1744]: Connecting to Concentratord command API, command_url: ipc:///tmp/concentratord_command
2023-12-13T13:44:29.668930+00:00 mtcap3 chirpstack-mqtt-forwarder[1744]: Reading gateway id
2023-12-13T13:44:29.676716+00:00 mtcap3 chirpstack-mqtt-forwarder[1744]: Received gateway id, gateway_id: 0016c001f1388eb8
2023-12-13T13:44:29.677987+00:00 mtcap3 chirpstack-mqtt-forwarder[1744]: Received Gateway ID from backend, gateway_id: 0016c001f1388eb8
Your Environment

Component
Version

MQTT Forwarder
4.1.3

Concentratord
4.3.4

The SX1302 has the gateway-id baked in the chip, there is no gateway_id configuration option:
https://www.chirpstack.io/docs/chirpstack-concentratord/configuration.html#configuration-example-1

Unlike the -sx1301 binary, there is no option for configuring the gateway_id. The unique gateway ID is embedded in the SX1302 and read by the Concentratord daemon.

Oh, my bad. Good to know. Thank you!


Line chart with vertical line

Is it possible to have a line chart with a vertical line which shows a label?
Something like that:
http://www.fusioncharts.com/dev/assets/images/vertical_lines.png.pagespeed.ce.JPDT_Ecw2V.png

You can use a markLine to simulate it.

to have a vertical line I should specify 'indexValue: 0', right?
And anyway, how could I print a label?

markline not labelline
On Mon, Feb 29, 2016 at 8:50 PM, Gabriele Nosso<EMAIL_ADDRESS>wrote:

to have a vertical line I should specify 'indexValue: 0', right?
And anyway, how could I print a label?
—
Reply to this email directly or view it on GitHub
https://github.com/ecomfe/echarts/issues/2693#issuecomment-190196951.

I'm also looking same result from you please let me know how to draw line with veritcal lines with labes either xAxis top or bottom ?


pinkerton: Remove unused storage drivers

We currently only use AUFS, no need to compile the rest of the drivers.

LGTM


Wrong Type Hint for EntityManager

Hi!
If a custom EntityManager Decorator is used, AuditManager->createAuditReader() and AuditReader::__construct() throwing exceptions because of 'EntityManager' Type Hint:
Catchable Fatal Error: Argument 1 passed to SimpleThings\EntityAudit\AuditReader::__construct() must be an instance of Doctrine\ORM\EntityManager, instance of ACME\Bundle\SomeBundle\Doctrine\EntityManagerDecorator given
and
Catchable Fatal Error: Argument 1 passed to SimpleThings\EntityAudit\AuditManager::createAuditReader() must be an instance of Doctrine\ORM\EntityManager, instance of ACME\Bundle\SomeBundle\Doctrine\EntityManagerDecorator given
I think it would be better to use 'EntityManagerInterface' instead.
Thanks!

Sounds about right - would you mind creating a PR?

This can be closed now

thank you :)

:+1:


Expose Delaunay2D to GDScript

It seems Delaunay triangulation has already been implemented in Godot (here). It's currently only used for animation related purposes.
I propose exposing it to GDScript as to enable certain procedural generation algorithms.

I wrote delaunay triangulation for my own project in GDScript, and I know at least one other person did, too.

I wrote delaunay triangulation for my own project in GDScript, and I know at least one other person did, too.

It's about performance.

I believe this is suited to be a plugin (GDNative)

Isn't there a Geometry singleton already with a triangulate() function in it?

Isn't there a Geometry singleton already with a triangulate() function in it?

It's not Delaunay. Also it doesn't work very consistently. Also when it works it doesn't include all points.

@Zylann: Geometry.triangulate() only works for convex polygons, also most delaunay implementations can work with inner points unlike this.

Should it be made available in Geometry singleton as triangulate_polygon_delaunay alongside triangulate_polygon? Perhaps an enum could be created for different types of triangulation, or a simple boolean.

@Xrayez I think a triangulate_delaunay would suffice. I mean there's just two types of triangulation, an enum would just confuse people.


OSM image doubled on screen

Sorry for the repost, I have realised I put it in the wrong spot earlier.
when loading the OSM, the image is doubled on screen.

first thoughts are that it is similar to when a 31k signal is sent to a 15k monitor, however Naomi is set to 15k on dipswitches and the monitor chassis is 15k.

libnaomi doesn't currently support 15khz/interlaced modes, hence why you see a double image.

I've added simple 15khz support to libnaomi toolchain. It looks kinda ugly and I'm sure that with some finessing of registers it might look a bit better. However, it should at least work for your case now. Go ahead and give the latest menu a try.

I'm going to try to work on the ugliness tomorrow, by the way, if you want to hold off trying until later.

I got a much much better interlaced picture from some changes tonight, but I ran out of time before I could push them. So I'll have to wait until tomorrow to clean it up.

This should be fixed! 15khz mode is now fully supported in libnaomi and compiled into the default OSM. chunksin will have to compile against the newest release to get that in his fork, however. Closing since this is fixed in base!


easy share -- for my hackathon friends

@shortstuffsushi -- proof of concept, don't merge. useful for hackathons

Moving this to the Invite SDK.


⚠ GitLab Server has degraded performance

In db171fa, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 8148 ms

Resolved: GitLab Server performance has improved in e66071d.


[resolves #217] Remove test security domain from app server configuratio...

...n

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/144/
Test PASSed.


cdcon 2021: confirm fundraising goal for bgc & wwc

we are moving forward w/fundraising for these two orgs

we have added an optional donation option to our registration process


RW cluster keep failing due to Starrocks sink error

Describe the bug
We have setup a cluster with multiple compute nodes, every time we trying to start a starrocks sink, the compute nodes keep failling one by one. Our current RW version is 1.8.
And everytime this error  happen, the entir cluster keep failing other tasks will be affacted
Error message/log
2024-04-30T02:18:22.283474848Z ERROR risingwave_stream::task::stream_manager: actor exit with error actor_id=34285 error=Executor error: Sink error: Doris/Starrocks connect error: deadline has elapsed

Backtrace:

   0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/anyhow-1.0.75/src/error.rs:551:25

   1: <T as core::convert::Into<U>>::into

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/convert/mod.rs:757:9

   2: risingwave_connector::sink::doris_starrocks_connector::InserterInner::wait_handle::{{closure}}

             at ./risingwave/src/connector/src/sink/doris_starrocks_connector.rs:313:73

   3: risingwave_connector::sink::doris_starrocks_connector::InserterInner::finish::{{closure}}

             at ./risingwave/src/connector/src/sink/doris_starrocks_connector.rs:323:28

   4: risingwave_connector::sink::starrocks::StarrocksClient::finish::{{closure}}

             at ./risingwave/src/connector/src/sink/starrocks.rs:610:40

   5: <risingwave_connector::sink::starrocks::StarrocksSinkWriter as risingwave_connector::sink::writer::SinkWriter>::barrier::{{closure}}

             at ./risingwave/src/connector/src/sink/starrocks.rs:481:29

   6: <core::pin::Pin<P> as core::future::future::Future>::poll

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/future/future.rs:124:9

   7: <risingwave_connector::sink::writer::LogSinkerOf<W> as risingwave_connector::sink::LogSinker>::consume_log_and_sink::{{closure}}

             at ./risingwave/src/connector/src/sink/writer.rs:198:51

   8: <core::pin::Pin<P> as core::future::future::Future>::poll

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/future/future.rs:124:9

   9: <F as futures_core::future::TryFuture>::try_poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/future.rs:82:9

  10: <futures_util::future::try_future::try_flatten::TryFlatten<Fut,<Fut as futures_core::future::TryFuture>::Ok> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/future/try_future/try_flatten.rs:57:41

  11: <futures_util::future::try_future::TryFlatten<Fut1,Fut2> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/lib.rs:91:13

  12: <futures_util::future::try_future::AndThen<Fut1,Fut2,F> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/lib.rs:91:13

  13: risingwave_stream::executor::sink::SinkExecutor<F>::execute_consume_log::{{closure}}

             at ./risingwave/src/stream/src/executor/sink.rs:421:14

  14: <futures_util::stream::once::Once<Fut> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/once.rs:46:33

  15: <futures_util::future::future::IntoStream<F> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/lib.rs:102:13

  16: futures_util::stream::select_with_strategy::poll_side

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/select_with_strategy.rs:219:27

  17: futures_util::stream::select_with_strategy::poll_inner

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/select_with_strategy.rs:243:11

  18: <futures_util::stream::select_with_strategy::SelectWithStrategy<St1,St2,Clos,State> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/select_with_strategy.rs:270:17

  19: <futures_util::stream::select::Select<St1,St2> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/select.rs:115:9

  20: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:120:9

  21: <futures_util::stream::stream::flatten::Flatten<St,<St as futures_core::stream::Stream>::Item> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/stream/flatten.rs:50:44

  22: <futures_util::stream::stream::Flatten<St> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/lib.rs:102:13

  23: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:120:9

  24: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:120:9

  25: futures_util::stream::stream::StreamExt::poll_next_unpin

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/stream/mod.rs:1638:9

  26: <futures_util::stream::stream::next::Next<St> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/stream/next.rs:32:9

  27: <await_tree::future::Instrumented<F,_> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/await-tree-0.1.1/src/future.rs:124:23

  28: risingwave_stream::executor::wrapper::trace::instrument_await_tree::{{closure}}

             at ./risingwave/src/stream/src/executor/wrapper/trace.rs:115:10

  29: <futures_async_stream::try_stream::GenTryStream<G> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-async-stream-0.2.9/src/lib.rs:506:33

  30: risingwave_stream::executor::wrapper::schema_check::schema_check::{{closure}}

             at ./risingwave/src/stream/src/executor/wrapper/schema_check.rs:24:1

  31: <futures_async_stream::try_stream::GenTryStream<G> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-async-stream-0.2.9/src/lib.rs:506:33

  32: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:120:9

  33: futures_util::stream::stream::StreamExt::poll_next_unpin

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/stream/mod.rs:1638:9

  34: <futures_util::stream::stream::next::Next<St> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/stream/next.rs:32:9

  35: risingwave_stream::executor::wrapper::epoch_check::epoch_check::{{closure}}

             at ./risingwave/src/stream/src/executor/wrapper/epoch_check.rs:31:44

  36: <futures_async_stream::try_stream::GenTryStream<G> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-async-stream-0.2.9/src/lib.rs:506:33

  37: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:120:9

  38: <S as futures_core::stream::TryStream>::try_poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:196:9

  39: futures_util::stream::try_stream::TryStreamExt::try_poll_next_unpin

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/try_stream/mod.rs:1131:9

  40: <futures_util::stream::try_stream::try_next::TryNext<St> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/try_stream/try_next.rs:32:9

  41: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:347:31

  42: tokio::task::task_local::LocalKey<T>::scope_inner

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:217:19

  43: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:343:19

  44: risingwave_common::util::epoch::task_local::scope::{{closure}}

             at ./risingwave/src/common/src/util/epoch.rs:244:47

  45: risingwave_stream::executor::wrapper::epoch_provide::epoch_provide::{{closure}}

             at ./risingwave/src/stream/src/executor/wrapper/epoch_provide.rs:31:59

  46: <futures_async_stream::try_stream::GenTryStream<G> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-async-stream-0.2.9/src/lib.rs:506:33

  47: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:120:9

  48: futures_util::stream::stream::StreamExt::poll_next_unpin

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/stream/mod.rs:1638:9

  49: <futures_util::stream::stream::next::Next<St> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/stream/next.rs:32:9

  50: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tracing-0.1.40/src/instrument.rs:321:9

  51: risingwave_stream::executor::wrapper::trace::trace::{{closure}}

             at ./risingwave/src/stream/src/executor/wrapper/trace.rs:48:69

  52: <futures_async_stream::try_stream::GenTryStream<G> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-async-stream-0.2.9/src/lib.rs:506:33

  53: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:120:9

  54: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:120:9

  55: <risingwave_stream::executor::dispatch::DispatchExecutor as risingwave_stream::executor::StreamConsumer>::execute::{{closure}}

             at ./risingwave/src/stream/src/executor/dispatch.rs:382:9

  56: <futures_async_stream::try_stream::GenTryStream<G> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-async-stream-0.2.9/src/lib.rs:506:33

  57: <core::pin::Pin<P> as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:120:9

  58: <&mut S as futures_core::stream::Stream>::poll_next

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.30/src/stream.rs:104:9

  59: <tokio_stream::stream_ext::next::Next<St> as core::future::future::Future>::poll

             at ./root/.cargo/git/checkouts/tokio-968c02b7a1a41bea/fe39bb8/tokio-stream/src/stream_ext/next.rs:42:9

  60: <tokio_stream::stream_ext::try_next::TryNext<St> as core::future::future::Future>::poll

             at ./root/.cargo/git/checkouts/tokio-968c02b7a1a41bea/fe39bb8/tokio-stream/src/stream_ext/try_next.rs:43:9

  61: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tracing-0.1.40/src/instrument.rs:321:9

  62: <await_tree::future::Instrumented<F,_> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/await-tree-0.1.1/src/future.rs:124:23

  63: risingwave_stream::executor::actor::Actor<C>::run_consumer::{{closure}}

             at ./risingwave/src/stream/src/executor/actor.rs:206:18

  64: <tokio::future::maybe_done::MaybeDone<Fut> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/future/maybe_done.rs:68:48

  65: risingwave_stream::executor::actor::Actor<C>::run::{{closure}}::{{closure}}::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/macros/join.rs:126:24

  66: <tokio::future::poll_fn::PollFn<F> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/future/poll_fn.rs:58:9

  67: risingwave_stream::executor::actor::Actor<C>::run::{{closure}}::{{closure}}

             at ./risingwave/src/stream/src/executor/actor.rs:162:17

  68: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:347:31

  69: tokio::task::task_local::LocalKey<T>::scope_inner

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:217:19

  70: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:343:19

  71: risingwave_expr::expr_context::expr_context_scope::{{closure}}

             at ./risingwave/src/expr/core/src/expr_context.rs:35:65

  72: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:347:31

  73: tokio::task::task_local::LocalKey<T>::scope_inner

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:217:19

  74: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:343:19

  75: risingwave_stream::executor::actor::Actor<C>::run::{{closure}}

             at ./risingwave/src/stream/src/executor/actor.rs:170:10

  76: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/future/future/map.rs:55:37

  77: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/lib.rs:91:13

  78: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:347:31

  79: tokio::task::task_local::LocalKey<T>::scope_inner

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:217:19

  80: <tokio::task::task_local::TaskLocalFuture<T,F> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/task/task_local.rs:343:19

  81: await_tree::registry::TreeRoot::instrument::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/await-tree-0.1.1/src/registry.rs:51:45

  82: <futures_util::future::either::Either<A,B> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/future/either.rs:109:32

  83: core::ops::function::FnOnce::call_once

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/ops/function.rs:250:5

  84: tokio_metrics::task::instrument_poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-metrics-0.3.0/src/task.rs:2530:15

  85: <tokio_metrics::task::Instrumented<T> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-metrics-0.3.0/src/task.rs:2430:9

  86: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tracing-0.1.40/src/instrument.rs:321:9

  87: tokio::runtime::task::core::Core<T,S>::poll::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/core.rs:334:17

  88: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/loom/std/unsafe_cell.rs:16:9

  89: tokio::runtime::task::core::Core<T,S>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/core.rs:323:13

  90: tokio::runtime::task::harness::poll_future::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/harness.rs:485:19

  91: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/panic/unwind_safe.rs:272:9

  92: std::panicking::try::do_call

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panicking.rs:552:40

  93: std::panicking::try

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panicking.rs:516:19

  94: std::panic::catch_unwind

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panic.rs:142:14

  95: tokio::runtime::task::harness::poll_future

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/harness.rs:473:18

  96: tokio::runtime::task::harness::Harness<T,S>::poll_inner

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/harness.rs:208:27

  97: tokio::runtime::task::harness::Harness<T,S>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/harness.rs:153:15

  98: tokio::runtime::task::raw::RawTask::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/raw.rs:200:18

  99: tokio::runtime::task::LocalNotified<S>::run

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/mod.rs:400:9

 100: tokio::runtime::scheduler::multi_thread::worker::Context::run_task::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/scheduler/multi_thread/worker.rs:576:18

 101: tokio::runtime::coop::with_budget

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/coop.rs:107:5

 102: tokio::runtime::coop::budget

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/coop.rs:73:5

 103: tokio::runtime::scheduler::multi_thread::worker::Context::run_task

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/scheduler/multi_thread/worker.rs:575:9

 104: tokio::runtime::scheduler::multi_thread::worker::Context::run

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/scheduler/multi_thread/worker.rs:526:24

 105: tokio::runtime::scheduler::multi_thread::worker::run::{{closure}}::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/scheduler/multi_thread/worker.rs:491:21

 106: tokio::runtime::context::scoped::Scoped<T>::set

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/context/scoped.rs:40:9

 107: tokio::runtime::scheduler::multi_thread::worker::run::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/scheduler/multi_thread/worker.rs:486:9

 108: tokio::runtime::context::runtime::enter_runtime

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/context/runtime.rs:65:16

 109: tokio::runtime::scheduler::multi_thread::worker::run

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/scheduler/multi_thread/worker.rs:478:5

 110: tokio::runtime::scheduler::multi_thread::worker::Launch::launch::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/scheduler/multi_thread/worker.rs:447:45

 111: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/blocking/task.rs:42:21

 112: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tracing-0.1.40/src/instrument.rs:321:9

 113: tokio::runtime::task::core::Core<T,S>::poll::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/core.rs:334:17

 114: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/loom/std/unsafe_cell.rs:16:9

 115: tokio::runtime::task::core::Core<T,S>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/core.rs:323:13

 116: tokio::runtime::task::harness::poll_future::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/harness.rs:485:19

 117: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/panic/unwind_safe.rs:272:9

 118: std::panicking::try::do_call

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panicking.rs:552:40

 119: std::panicking::try

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panicking.rs:516:19

 120: std::panic::catch_unwind

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panic.rs:142:14

 121: tokio::runtime::task::harness::poll_future

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/harness.rs:473:18

 122: tokio::runtime::task::harness::Harness<T,S>::poll_inner

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/harness.rs:208:27

 123: tokio::runtime::task::harness::Harness<T,S>::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/harness.rs:153:15

 124: tokio::runtime::task::raw::RawTask::poll

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/raw.rs:200:18

 125: tokio::runtime::task::UnownedTask<S>::run

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/task/mod.rs:437:9

 126: tokio::runtime::blocking::pool::Task::run

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/blocking/pool.rs:159:9

 127: tokio::runtime::blocking::pool::Inner::run

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/blocking/pool.rs:513:17

 128: tokio::runtime::blocking::pool::Spawner::spawn_thread::{{closure}}

             at ./root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/blocking/pool.rs:471:13

 129: std::sys_common::backtrace::__rust_begin_short_backtrace

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/sys_common/backtrace.rs:155:18

 130: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/thread/mod.rs:529:17

 131: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/panic/unwind_safe.rs:272:9

 132: std::panicking::try::do_call

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panicking.rs:552:40

 133: std::panicking::try

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panicking.rs:516:19

 134: std::panic::catch_unwind

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panic.rs:142:14

 135: std::thread::Builder::spawn_unchecked_::{{closure}}

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/thread/mod.rs:528:30

 136: core::ops::function::FnOnce::call_once{{vtable.shim}}

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/ops/function.rs:250:5

 137: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/alloc/src/boxed.rs:2015:9

 138: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/alloc/src/boxed.rs:2015:9

 139: std::sys::unix::thread::Thread::new::thread_start

             at ./rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/sys/unix/thread.rs:108:17

 140: start_thread

             at ./nptl/pthread_create.c:442:8

 141: __GI___clone

             at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:100

To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
Helm charts
The version of RisingWave
1.8
Additional context
No response

same error happened

What is the version of sr and what are the specific sql statements?

RisingWave: 1.8

It may be caused by getting the internal host from the  SR  front end when accessing the SR back end.

It may be caused by getting the internal host from the SR front end when accessing the SR back end.

what's that mean? I'm not quit understand

It is indeed caused by accessing starrocks http port, can you please provide the specific host and port of sr's fe and cn nodes?

you mean this?
host:
fe: starrocks-fe-service.dp-prod
cn: starrocks-cn-service.dp-prod

you mean this?
host: fe: starrocks-fe-service.dp-prod cn: starrocks-cn-service.dp-prod

okk, thanks, can you test the connectivity between the rw cn node and the sr cn node direct network?

you mean this?
host: fe: starrocks-fe-service.dp-prod cn: starrocks-cn-service.dp-prod

okk, thanks, can you test the connectivity between the rw cn node and the sr cn node direct network?

connectivity is good, and actually the SR sink is fine in dev enviorment, only error in prod, maybe it's a local env problem, I will test it in prod later this weekend

I have tested this case in  dev/prod envs, still have this kind error, sames like writing to SR is too slow, can RW cn nodes keep failling

e0.log
e1.log
e2.log

e2.log
e1.log
e0.log

this can be resolved by add sink_decouple param


Redesigning home page UI

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to a problem. The current UI of the homepage might have several issues that are affecting user experience and engagement. Here are some possible problems:
Poor Visual Design: The design seems to be outdated, unappealing, or not aligned with modern web design standards, which can deter users from staying on the site.
Poor Content Layout: Important information might be buried or not highlighted properly, making it hard for users to find what they are looking for quickly.
By redesigning the homepage, I aim to address these problems, improving user satisfaction, engagement, and overall site performance.
Describe the solution you'd like.
Solution I'd like are
Modern Visual Design: Update the visual design to be clean, appealing, and aligned with current web design trends. Use a cohesive color scheme, high-quality images, and modern typography to create a professional and inviting look.
Clear Messaging: Feature a bold headline and subheadline that clearly communicate value proposition.
Describe alternatives you've considered.
By implementing these design and visual appeal elements, the redesigned homepage will provide a more engaging, intuitive, and aesthetically pleasing experience for our users, encouraging them to explore the site further and take action.
For example in domains , I can add some photos in all the respective domains instead of just simple anchor tag text.
I will be doing this with figma.
Add any other context or screenshots about the feature request here.
So take into consideration this issue and assign me this task, I would love to make its UI more appealing.

Thankyou @Kushal997-das

There is no figma file.
On Wed, 22 May, 2024, 11:17 pm Anuja Singh, @.***>
wrote:

I need old figma file in order to redesign Home Page, I had mailed you
regarding this matter, please check and reply.
—
Reply to this email directly, view it on GitHub
https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2125415085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOUDPZLETTE3KI6VI74R4EDZDTK3JAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGQYTKMBYGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Okkk...so I need to change the design of readme file using html codes pr
should I make a figma one?
On Thu, 23 May 2024, 07:33 Kushal Das, @.***> wrote:

There is no figma file.
On Wed, 22 May, 2024, 11:17 pm Anuja Singh, @.***>
wrote:

I need old figma file in order to redesign Home Page, I had mailed you
regarding this matter, please check and reply.
—
Reply to this email directly, view it on GitHub
<
https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2125415085>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AOUDPZLETTE3KI6VI74R4EDZDTK3JAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGQYTKMBYGU>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2126057810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5AS7PBP6E4J56EDAWTERFDZDVFALAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGA2TOOBRGA
.
You are receiving this because you were assigned.Message ID:
@.***>

What UI exactly you want to change?
On Thu, 23 May, 2024, 9:32 am Anuja Singh, @.***> wrote:

Okkk...so I need to change the design of readme file using html codes pr
should I make a figma one?
On Thu, 23 May 2024, 07:33 Kushal Das, @.***> wrote:

There is no figma file.
On Wed, 22 May, 2024, 11:17 pm Anuja Singh, @.***>
wrote:

I need old figma file in order to redesign Home Page, I had mailed you
regarding this matter, please check and reply.
—
Reply to this email directly, view it on GitHub
<

https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2125415085>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AOUDPZLETTE3KI6VI74R4EDZDTK3JAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGQYTKMBYGU>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2126057810>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A5AS7PBP6E4J56EDAWTERFDZDVFALAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGA2TOOBRGA>

.
You are receiving this because you were assigned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2126187873,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOUDPZOC77GVLWSNXMAPICTZDVS45AVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGE4DOOBXGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

I don't think anyone requirement need.
On Thu, 23 May, 2024, 9:34 am Kushal Das, @.***> wrote:

What UI exactly you want to change?
On Thu, 23 May, 2024, 9:32 am Anuja Singh, @.***>
wrote:

Okkk...so I need to change the design of readme file using html codes pr
should I make a figma one?
On Thu, 23 May 2024, 07:33 Kushal Das, @.***> wrote:

There is no figma file.
On Wed, 22 May, 2024, 11:17 pm Anuja Singh, @.***>
wrote:

I need old figma file in order to redesign Home Page, I had mailed
you
regarding this matter, please check and reply.
—
Reply to this email directly, view it on GitHub
<

https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2125415085>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AOUDPZLETTE3KI6VI74R4EDZDTK3JAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGQYTKMBYGU>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2126057810>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A5AS7PBP6E4J56EDAWTERFDZDVFALAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGA2TOOBRGA>

.
You are receiving this because you were assigned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2126187873,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOUDPZOC77GVLWSNXMAPICTZDVS45AVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGE4DOOBXGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

The picture in blue..does not seem too good and below that, I was thinking
to add images with the domain as marked in attachment and font as well
doesn't seem to be attractive.
On Thu, 23 May 2024, 09:35 Kushal Das, @.***> wrote:

What UI exactly you want to change?
On Thu, 23 May, 2024, 9:32 am Anuja Singh, @.***> wrote:

Okkk...so I need to change the design of readme file using html codes pr
should I make a figma one?
On Thu, 23 May 2024, 07:33 Kushal Das, @.***> wrote:

There is no figma file.
On Wed, 22 May, 2024, 11:17 pm Anuja Singh, @.***>
wrote:

I need old figma file in order to redesign Home Page, I had mailed
you
regarding this matter, please check and reply.
—
Reply to this email directly, view it on GitHub
<

https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2125415085>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AOUDPZLETTE3KI6VI74R4EDZDTK3JAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGQYTKMBYGU>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<

https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2126057810>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/A5AS7PBP6E4J56EDAWTERFDZDVFALAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGA2TOOBRGA>

.
You are receiving this because you were assigned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2126187873>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AOUDPZOC77GVLWSNXMAPICTZDVS45AVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGE4DOOBXGM>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Kushal997-das/Project-Guidance/issues/1067#issuecomment-2126189962,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5AS7PERG3J4W7SSMAMDCSTZDVTHVAVCNFSM6AAAAABIC6A6NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWGE4DSOJWGI
.
You are receiving this because you were assigned.Message ID:
@.***>

@Anuja1227 Ok go ahead


[Q] Sync settings without syncing extensions

I do not want to sync my extensions because I have a lot of them on my main machine, but I want something more lightweight for my VPS. I just want to sync the settings for vscode and the extensions I have already installed on the remote.

you can set "sync.syncExtensions": false in the settings.json (F1, search for open settings (json)


Does not work with forge.

I I tried to test your extension (e6ad605) with latest forge (29be1da7) UI and got a few exceptions like that:
*** Error executing callback cfg_denoiser_callback for /mnt/SSD/neuro/forge/extensions/sd-webui-detail-daemon/scripts/detail_daemon.py                         | 7/25 [00:04<00:11,  1.56it/s]
    Traceback (most recent call last):
      File "/mnt/SSD/neuro/forge/modules/script_callbacks.py", line 233, in cfg_denoiser_callback
        c.callback(params)
      File "/mnt/SSD/neuro/forge/extensions/sd-webui-detail-daemon/scripts/detail_daemon.py", line 154, in denoiser_callback
        params.sigma[1] *= 1 - self.schedule[idx] * -.1
        ~~~~~~~~~~~~^^^
    IndexError: index 1 is out of bounds for dimension 0 with size 1

Is it possible to make your extension compatible with forge?

Gotta look into it later. But for now if you set mode to "both" or maybe "cond" it might work.

Gotta look into it later. But for now if you set mode to "both" or maybe "cond" it might work.

Yes, I confirm that "cond" and "both" both work on Forge, for now only "uncond" generates that problem.

Just got fixed.. to a degree. Forge does not allow cond and uncond modes, but it's handled more gracefully now (i.e. it automatically switches to both and prints a warning to console instead of throwing an error).


Improve ion-img performance

Safari has troubles cancelling image requests with the img src changes. Manually handle image HTTP requests, rather than letting <img> attempt to handle this.

do you think we should fill a bug report in safari/webkit as well?

This is largely only a UIWebView problem, so I guess they kind of did fix it in WKWebView. The new way will not reuse the same img element, so it does a better job at aborting image requests.


Image under Power Tools Strategy

Hey Charu,
Could you please provide a custom drawn image For calculating Average power?

Hey Sheryl
I update that image.


Update DG

Codecov Report

Merging #98 (af9c3d3) into master (4060748) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #98   +/-   ##
=========================================
  Coverage     38.72%   38.72%
  Complexity      383      383
=========================================
  Files           123      123
  Lines          2270     2270
  Branches        251      251
=========================================
  Hits            879      879
  Misses         1348     1348
  Partials         43       43

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Compile fail when bind member function with new_usertype, and the param is const pointer.

Here is the code
#include "sol.hpp"

class A
{
public:
    A() {};
    ~A() {};
};

class B
{
public:
    B() {};
    ~B() {};
    void foo(const A* a) {};
}

int main(void)
{
    sol::state lua;
    lua.new_usertype<B>("B", "foo", &B::foo);
    return 0;
}

Compile fail, error:
stack_get.hpp:297:12: error: assigning to 'void *' from incompatible type 'const A *'
udata = detail::catch_cast(udata, basecast);

This is a bug in my implementation. Sorry about that: I've got a fix ready and will push it soon.
Thanks for checking this over for me.

Ok，did sol has email list or some discussion groups? Recently I intend to integrate sol into our project, although sol has tutorial and api manual, I still hope to have a way to consult some questions.

GH Issues > mailing lists/discussion groups

GIthub Issues is the place to put them. A mailing list I've found to be discouraging, alongside forums: they often have month-old topics in them and that makes people feel like they'll receive no support if they post there.
Github, on the other hand, shows latest commit information and can also display recent issues. Issues are also easily searchable as well, so it makes it easier for people to find out things.
I am considering getting a Gitter for the real-time chat aspect, but that might be overdoing it (especially since I won't be available 24/7 to basically run support).

Employ some Indians, maybe?

Fixed: https://github.com/ThePhD/sol2/releases/tag/v2.10.0


Emircado hexcolorfield - testing session build

Closes
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

closing because this was just for the testing session


Fix maintenance spelling

Updates a few references to maintenance that were misspelled as maintainence.  These variables are misspelled in Split.io as well, so those will need to be updated as part of this change.
Once this is merged to main, we should update the dev and staging feature flags, and after our next release, we should update the prod feature flags.

I've gone ahead and made the updates in Split.io for dev and staging environments, and also added this variable to the prod environment (without removing the old spelling so that it continues to work there).  After our next release, I'll clean up the prod feature flag.


Unsupported operator LRN

Hi. I'm attempting to convert the blvc_googlenet model, but found an unsupported operator. Do you mind fixing this? Thanks.
Model could be found here: https://github.com/onnx/models/tree/master/bvlc_googlenet
./tools/onnx2daq/onnx2daq bvlc_googlenet.onnx bvlc_googlenet.daq
I1211 16:30:49.410192 14595 OnnxConverter.cpp:193] Node
I1211 16:30:49.410250 14595 OnnxConverter.cpp:195] Start converting Conv
I1211 16:30:49.410262 14595 OnnxConverter.cpp:112] Vanilla conv
I1211 16:30:49.410290 14595 OnnxConverter.cpp:220] Converting Conv completed
I1211 16:30:49.410295 14595 OnnxConverter.cpp:193] Node
I1211 16:30:49.410297 14595 OnnxConverter.cpp:272] Start converting Relu
I1211 16:30:49.410301 14595 OnnxConverter.cpp:279] Converting Relu completed
I1211 16:30:49.410305 14595 OnnxConverter.cpp:193] Node
I1211 16:30:49.410307 14595 OnnxConverter.cpp:222] Start converting Pool
I1211 16:30:49.410315 14595 OnnxConverter.cpp:270] Converting Pool completed
I1211 16:30:49.410320 14595 OnnxConverter.cpp:193] Node
terminate called after throwing an instance of 'std::invalid_argument'
  what():  Unsupported operator LRN
Aborted (core dumped)

Hi :) Thanks for your issue. I will support it when I have time


Test task should stream test output

Right now test task creates an html report and simply prints out summary like
Test for github.com/fkorotkov/example finished, 5 completed, 1 failed

It's not very convenient to have only html report for environments like CI since I don't have an access to the report after CI build finishes. It will be nice to stream output of go test command to the console.

Good advice, I'll try to improve it.

Hello - I found this issue and the fix. What do you think about adding a DSL similar to what's on the normal gradle Test task?
https://docs.gradle.org/current/dsl/org.gradle.api.tasks.testing.logging.TestLogging.html
Adding info to get logs is somewhat nice, but also adds tons of spam, being able to configure the output only for the test task would be more useful on e.g., CI which runs lots of tests and would be highly overloaded by all the output of --info.

@anuraaga Thanks for your suggestion, that's great! I'll try to make it in next release.

I like goGradle and I am using it.
One question I have is that, is it possible to get the report with junit xml format from goGradle test? I have seen the HTML report. However, I may need the xml report for the Jenkins.
I have found a tool to transform the go test output to junit xml report, for example, https://github.com/jstemmer/go-junit-report. I feel it would be great if goGradle could generate the xml report.

Also https://github.com/tebeka/go2xunit/.  It seems difficult to use either of these tools right now since the output of 'go test -v' is being dumped to the console by gogradle rather than being available for other tasks to consume.
Agree that it would be nice if it were a built-in feature of gogradle to produce xunit style xml reports, as well as cobertura style xml coverage reports (see https://github.com/t-yuki/gocov-xml)

@blindpirate any updates on this? It would be much more convenient to have an option right in goTest task than enabling INFO logging level for the whole gradle build.

@blindpirate I created a pull request that fixes this issue, please take a look: https://github.com/gogradle/gogradle/pull/309


provide command line api

like Dependency Walker, I would like to have an command line interface to use "Dependencies".

it's in the roadmap 😄
In the meantime, you can use ClrPhTester.exe which implements some feature for testing.

Thanks! Now that this is available, I would like to easily see my missing dependencies. In the GUI we can see a quotation mark icon next to the missing ones, but in the command line, it would be really usefull to list ONLY the problematic ones.

Both -modules and chain returns the "search strategy" for each module (Apiset schema, Sxs entries, etc.) or NOT_FOUND when the dll  wasn't found.
E.g.
PS > .\Dependencies.exe -modules C:\WINDOWS\system32\twext.dll | Select-String NOT_FOUND

[NOT_FOUND] ext-ms-win-security-chambers-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-core-winrt-remote-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-shell-knownfolderext-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-winrt-storage-removable-l1-1-0.dll :
[NOT_FOUND] ext-ms-onecore-defaultdiscovery-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-winrt-storage-fileexplorer-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-security-capauthz-ext-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-com-suspendresiliency-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-appmodel-deployment-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-appmodel-deployment-l1-1-1.dll :
[NOT_FOUND] ext-ms-windowscore-deviceinfo-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-appmodel-viewscalefactor-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-appmodel-usercontext-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-ui-viewmanagement-l1-1-0.dll :
[NOT_FOUND] EMCLIENT.dll :
[NOT_FOUND] api-ms-win-coreui-secruntime-l1-1-0.dll :
[NOT_FOUND] ext-ms-onecore-orientation-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-rtcore-minuser-private-ext-l1-1-0.dll :
[NOT_FOUND] ext-ms-onecore-appchromeapi-l1-1-0.dll :
[NOT_FOUND] ext-ms-onecore-shellchromeapi-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-rtcore-minuser-input-l1-1-1.dll :
[NOT_FOUND] ext-ms-mf-pal-l2-1-0.dll :
[NOT_FOUND] ext-ms-win-wer-xbox-l1-1-0.dll :
[NOT_FOUND] ext-ms-win-audiocore-pal-l1-2-0.dll :
[NOT_FOUND] ext-ms-onecore-appmodel-emclient-l1-1-0.dll :
[NOT_FOUND] ext-ms-onecore-shellchromeapi-l1-1-1.dll :


Tooltips are cut of by the browser window

If the tooltip overlaps the left or right border of the screen window it will be cut off:

You can try it on profile 7 here: https://jantimon.github.io/cpuprofile-webpack-plugin/

Looks rather like this plugin is not maintained anymore.

@jantimon - there is a way in case you can find out which element falls towards right/left extremities then we can specify the tooltip direction.


Adding a brief explanation for Algorithms and concepts.

Is your feature request related to a problem? Please describe.
A brief explanation for programs using comments or a separate readme file or even reference links would be a great addition to this repo.
Describe the solution you'd like
The explanations could be added in any form suitable to the repo managers, like proper commenting, a common readme file for all, directory-wise readme files, or a separate one for each concept.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
I would also like to contribute to this repo some time in the near future as I've just begun my competitive programming journey.

Though example usage would be nice to have; I do not have the time to add examples for the scripts available in this repo.
I assume that most people using PyRival have already reached the limits of competitive programming in Python and would be familiar with most of the algorithms provided here.
However, we already have a docs section in the repo. Currently, this is quite limited and only documents the bootstrap function which happens to be somewhat nontrivial in its implementation.
Please feel free to open a PR to the repo if you would like to contribute.


chore: add java-shared-config as parent for consolidated version mana…

…gement
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕
If you write sample code, please follow the samples format.

From local testing, adding java-shared-config and keeping the profile that previously existed in google-auth-library-java continues to result in:
[ERROR] Failed to execute goal org.graalvm.buildtools:native-maven-plugin:0.9.28:test (test-native) on project google-auth-library-oauth2-http: Execution test-native of goal org.graalvm.buildtools:native-maven-plugin:0.9.28:test failed: Test configuration file wasn't found.

Update: The graalvm checks are passing but the ci/lint check is now failing with:
Error:  Failed to execute goal com.coveo:fmt-maven-plugin:2.13:check (default-cli) on project google-auth-library-credentials: Execution default-cli of goal com.coveo:fmt-maven-plugin:2.13:check failed: An API incompatibility was encountered while executing com.coveo:fmt-maven-plugin:2.13:check: java.lang.NoSuchMethodError: 'java.lang.String com.google.googlejavaformat.java.ImportOrderer.reorderImports(java.lang.String, com.google.googlejavaformat.java.JavaFormatterOptions$Style)'


JWT Istio handler configuration

See: #34

We also need Status update changes, see: https://github.com/kyma-project/api-gateway#additional-information
Have to apply status for APs and RAs: https://github.com/kyma-project/api-gateway/blob/d8d574c236d9f6422df710476508c195a4434aba/controllers/apirule_controller.go#L195-L202

I saw that we have a lot of checks for the JWT handler. I think it would make sense to have an abstraction for JWT Handlers and implement a component for each handler and pass that around instead of adding the if-checks. This way removing the support for a JWT handler would also be easier. What do you think?

Yes, this is a bit of unfortunate. Tbh we did it to avoid a lot of code duplication. @strekm did also raise this. I would vote to leave it like this for now and completely refactor it, once we implement a new handler. Or plan for it in for the future.

Looks good for me, only fix the comments from Tim.


Add <meta> tag for https://*.webxrexperiments.com Origin-Trial token

Without needing a user to enable the flags for Cardboard or Daydream modes, I would recommend enrolling in the WebVR Origin Trial for Chrome for Android.
Sign up here: https://docs.google.com/forms/d/1OTvEk-VfavyKkMxef0Tvs0RFycl9NNu1vdg3FrqJhX8/viewform?edit_requested=true

done.


Sweep: implement depcheck as a github action

Problem: We have instances where we install a frontend library with yarn, but then we don't actually end up using it in our code. We should try to keep our frontend package size as small as possible and keep only the essentials to make our builds run faster
Solution: Use depcheck to create a Github Action that validates that there are no frontend libraries in yarn.lock that really don't get used.
Branch Setup:
git checkout nextjs
git pull origin nextjs
git checkout -b depcheck-sweep-action

We currently don't have depcheck implemented. Your job is to implement it

sweep: We currently don't have depcheck implemented. Your job is to implement it