'colcon build' failed (rmf_fleet_adapter_python)

Bug report
Required information:

Operating system and version: Ubuntu 20.04
OpenRMF installation type: From source
ROS distribution and version: Foxy
ROS installation type: From source

Description of the bug:

The rmf_fleet_adapter_python package fails to compile.
Followed the instructions from :
https://github.com/open-rmf/rmf
Steps to reproduce the bug:
cd ~/rmf_ws
source /opt/ros/foxy/setup.bash
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release

Screenshots:

Hi there,
I am able to reproduce this bug when building the RMF workspace with ROS 2 foxy also built from source. Will look into this.

Hi @KamalanathanN
I tried to reproduce on my side but couldn't, to recap, on Ubuntu 20.04:

Fresh clone of ROS2 Foxy, following the official guide
Build and source the workspace
Clone rmf
Build up to rmf_fleet_adapter_python, through colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release --packages-up-to rmf_fleet_adapter_python

I get a few warnings but the build is successful:
--- stderr: rmf_fleet_adapter_python
CMake Warning at /home/luca/demos_ws/install/pybind_ament/share/pybind11/cmake/pybind11Tools.cmake:17 (message):
  Set PYBIND11_PYTHON_VERSION to search for a specific version, not
  PYTHON_VERSION (which is an output).  Assuming that is what you meant to do
  and continuing anyway.
Call Stack (most recent call first):
  /home/luca/demos_ws/install/pybind_ament/share/pybind11/cmake/pybind11Common.cmake:195 (include)
  /home/luca/demos_ws/install/pybind_ament/share/pybind11/cmake/pybind11Config.cmake:249 (include)
  CMakeLists.txt:34 (find_package)

/home/luca/demos_ws/src/rmf/rmf_ros2/rmf_fleet_adapter_python/src/adapter.cpp: In function ‘void pybind11_init_rmf_adapter(pybind11::module_&)’:
/home/luca/demos_ws/src/rmf/rmf_ros2/rmf_fleet_adapter_python/src/adapter.cpp:176:39: warning: ‘rmf_fleet_adapter::agv::FleetUpdateHandle& rmf_fleet_adapter::agv::FleetUpdateHandle::accept_delivery_requests(rmf_fleet_adapter::agv::FleetUpdateHandle::AcceptDeliveryRequest)’ is deprecated: Use accept_task_requests() instead [-Wdeprecated-declarations]
  176 |              &agv::FleetUpdateHandle::accept_delivery_requests,
      |                                       ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/luca/demos_ws/install/rmf_fleet_adapter/include/rmf_fleet_adapter/agv/Adapter.hpp:20,
                 from /home/luca/demos_ws/src/rmf/rmf_ros2/rmf_fleet_adapter_python/src/adapter.cpp:11:
/home/luca/demos_ws/install/rmf_fleet_adapter/include/rmf_fleet_adapter/agv/FleetUpdateHandle.hpp:157:22: note: declared here
  157 |   FleetUpdateHandle& accept_delivery_requests(AcceptDeliveryRequest check);
      |                      ^~~~~~~~~~~~~~~~~~~~~~~~
---

Do you still have this issue? I wonder if pulling the latest sources could help?

@luca-della-vedova
well.... To reproduce the bug try building the entire rmf_ws.
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release

you ignored the only package(rmf_fleet_adapter_python) that didnt build 😅using --packages-up-to rmf_fleet_adapter_python
The rest of rmf repos were build perfectly for me without any warnings by using following command :
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release --packages-ignore rmf_fleet_adapter_python

you ignored the only package(rmf_fleet_adapter_python) that didnt build :sweat_smile: using --packages-up-to rmf_fleet_adapter_python

Just to clarify on this, the --packages-up-to xyz option does include building package xyz, so using that argument would not prevent @luca-della-vedova from seeing an error related to building that package.

One odd detail that sticks out to me, @KamalanathanN : In your description of the bug, you say that ROS2 was installed from source, but you also say that you use $ source /opt/ros/foxy/setup.bash before building your rmf_ws.
Does that mean that you used something like colcon build --install-prefix /opt/ros/foxy to build and install ROS2? If so, I would very much discourage that. /opt/ros/foxy is meant to be the installation folder for debian packages that you get from your package manager. Installing locally built packages to that folder could cause strange dependency issues that would be hard to diagnose.
What happens if you build your ros2 workspace with the default install prefix, as recommended by the ROS2 build instructions and then source that ROS2 workspace before building rmf_ws?

There is a discrepancy in the description of the bug where the user states they built their RMF workspace with foxy from source but end up sourcing /opt/ros/foxy/setup.bash before the build.
I should clarify how I reproduced the error: I didn't follow the "steps to reproduce the bug". Instead I set up a single workspace with foxy packages and RMF packages. I then built the workspace with colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release. I added the --symlink-install by virtue of following the ROS2 build instructions. This leads to the above mentioned error with rmf_fleet_adapter_python. However if I run colcon build without the --symlink-install there is no build error. If one sets up two workspaces 1) Foxy and 2) RMF,  where the first workspace is built with --symlink-install (following ROS2 building instructions) and the second is built after sourcing the first (and without --symlink-install, ie, following RMF build instructions), the error will not be encountered.
@KamalanathanN  I am not sure if you followed the same steps but could you clarify exactly how your workspace(s) are setup and the commands used to source/build?

One odd detail that sticks out to me, @KamalanathanN : In your description of the bug, you say that ROS2 was installed from source, but you also say that you use $ source /opt/ros/foxy/setup.bash before building your rmf_ws.
Does that mean that you used something like colcon build --install-prefix /opt/ros/foxy to build and install ROS2? If so, I would very much discourage that. /opt/ros/foxy is meant to be the installation folder for debian packages that you get from your package manager. Installing locally built packages to that folder could cause strange dependency issues that would be hard to diagnose.
What happens if you build your ros2 workspace with the default install prefix, as recommended by the ROS2 build instructions and then source that ROS2 workspace before building rmf_ws?

@mxgrey you're right i'm really sorry for the error in the description(i've edited it now) ... actually during my initial tests i used foxy installed from source... later i switched to Installing ROS 2 via Debian Packages which at the time of reporting the bug i completely forgot that i switched.😬🤦♂
@Yadunund , sorry for the confusion i'll clarify,

Foxy installed from Debian packages
RMF is setup as instructed in https://github.com/open-rmf/rmf
and the "steps to reproduce the bug" remains the same.
i still get the same error :(

CMake Error at /home/kamal/rmf_ws_v2/install/pybind_ament/share/pybind11/cmake/pybind11Tools.cmake:147 (add_library):
  Target "rmf_adapter" links to target
  "std_msgs::std_msgs__rosidl_generator_c" but the target was not found.
  Perhaps a find_package() call is missing for an IMPORTED target, or an
  ALIAS target is missing?
Call Stack (most recent call first):
  CMakeLists.txt:36 (pybind11_add_module)

CMake Generate step failed.  Build files cannot be regenerated correctly.
Traceback (most recent call last):
  File "setup.py", line 91, in <module>
    setup(
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 144, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.8/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "setup.py", line 51, in run
    self.build_extension(ext)
  File "setup.py", line 84, in build_extension
    subprocess.check_call(['cmake', ext.sourcedir] + cmake_args,
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '/home/kamal/rmf_ws_v2/src/rmf/rmf_ros2/rmf_fleet_adapter_python', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/home/kamal/rmf_ws_v2/build/rmf_fleet_adapter_python/build/lib.linux-x86_64-3.8/', '-DPYTHON_EXECUTABLE=/usr/bin/python3', '-DCMAKE_BUILD_TYPE=Release']' returned non-zero exit status 1.
---
Failed   <<< rmf_fleet_adapter_python [2.57s, exited with code 1]

Summary: 48 packages finished [13.7s]
  1 package failed: rmf_fleet_adapter_python
  1 package had stderr output: rmf_fleet_adapter_python

one more thing... im not sure if its related but when i  rosdep install --from-paths src --ignore-src --rosdistro foxy -yr
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
rmf_demos_panel: Cannot locate rosdep definition for [python3-flask-cors]
Continuing to install resolvable dependencies...
#All required rosdeps installed successfully

i have installed it manually python3-flask-cors is already the newest version (3.0.8-2).  but it still shows error 🙎♂

Hi @KamalanathanN
We are fixing the issue that @Yadunund found, can you check if this PR in rmf_ros2 helps?
It actually removed pybind_ament that seems to be the source of your issues.

one more thing... im not sure if its related but when i  rosdep install --from-paths src --ignore-src --rosdistro foxy -yr
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
rmf_demos_panel: Cannot locate rosdep definition for [python3-flask-cors]
Continuing to install resolvable dependencies...
#All required rosdeps installed successfully

i have installed it manually python3-flask-cors is already the newest version (3.0.8-2). but it still shows error pouting_man

If you installed it manually it should be ok, the key for python3-flask-cors was added recently to rosdistro very recently. The error should disappear if you run rosdep update and try the rosdep install command again.

@KamalanathanN Could you let us know if you're still experiencing this issue with the latest changes? If we don't hear back, we'll be closing this issue for lack of reproducibility.

@mxgrey sorry for the delay. The issue is resolved with latest changes.
Thanks to everyone involved and looking forward to explore more of RMF :)


cargo build error

Hi guys,
I am new to tch-rs, it looks fantastic. but I meet some problems when I write my first program using tch.
here is my enviroment:
os: arch linux x86_64 5.15.13
rust: 1.58.0-nightly
tch: 0.6.1
libtorch: libtorch-shared-with-deps-1.10.1+cpu.zip
i followed the documentation, downloaded the litorch and then unzip it, and add it to my .zshrc like this:
export LIBTORCH=/home/chien/Development/Cpp/libtorch
export LD_LIBRARY_PATH=${LIBTORCH}/lib:$LD_LIBRARY_PATH

and this is my cargo.toml:
[package]
name = "tch-demo"
version = "0.1.0"
edition = "2021"

[dependencies]
tch = "0.6.1"
anyhow = "1.0.52"

when i run cargo build, it turns out this error:
error: linking with `cc` failed: exit status: 1

  = note: /usr/bin/ld: /home/chien/Development/Rust/tch-demo/target/debug/deps/libtorch_sys-73e1c808b35185b8.rlib(torch_api.o): in function `c10::Device::validate()':
          /home/chien/Development/Cpp/libtorch/include/c10/core/Device.h:120: undefined reference to `c10::detail::torchInternalAssertFail(char const*, char const*, unsigned int, char
const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Cpp/libtorch/include/c10/core/Device.h:124: undefined reference to `c10::detail::torchInternalAssertFail(char const*, char const*, unsigned int, char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Rust/tch-demo/target/debug/deps/libtorch_sys-73e1c808b35185b8.rlib(torch_api.o): in function `caffe2::TypeMeta::fromScalarType(c10::ScalarType)':
          /home/chien/Development/Cpp/libtorch/include/c10/util/typeid.h:472: undefined reference to `c10::detail::torchInternalAssertFail(char const*, char const*, unsigned int, char
const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Rust/tch-demo/target/debug/deps/libtorch_sys-73e1c808b35185b8.rlib(torch_api.o): in function `c10::IValue::toComplexDouble() const':
          /home/chien/Development/Cpp/libtorch/include/ATen/core/ivalue_inl.h:141: undefined reference to `c10::detail::torchInternalAssertFail(char const*, char const*, unsigned int,
char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Rust/tch-demo/target/debug/deps/libtorch_sys-73e1c808b35185b8.rlib(torch_api.o): in function `c10::IValue::toIntList() const &':
          /home/chien/Development/Cpp/libtorch/include/ATen/core/ivalue_inl.h:1304: undefined reference to `c10::detail::torchInternalAssertFail(char const*, char const*, unsigned int, char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Rust/tch-demo/target/debug/deps/libtorch_sys-73e1c808b35185b8.rlib(torch_api.o):/home/chien/Development/Cpp/libtorch/include/ATen/core/ivalue_inl.h:1320: more undefined references to `c10::detail::torchInternalAssertFail(char const*, char const*, unsigned int, char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' follow
          /usr/bin/ld: /home/chien/Development/Rust/tch-demo/target/debug/deps/libtorch_sys-73e1c808b35185b8.rlib(torch_api.o): in function `torch::optim::Adam::Adam(std::vector<torch::optim::OptimizerParamGroup, std::allocator<torch::optim::OptimizerParamGroup> >, torch::optim::AdamOptions)':
          /home/chien/Development/Cpp/libtorch/include/torch/csrc/api/include/torch/optim/adam.h:54: undefined reference to `c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Cpp/libtorch/include/torch/csrc/api/include/torch/optim/adam.h:55: undefined reference to `c10::detail::torchCheckFail(char const*, char
const*, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Cpp/libtorch/include/torch/csrc/api/include/torch/optim/adam.h:57: undefined reference to `c10::detail::torchCheckFail(char const*, char
const*, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Cpp/libtorch/include/torch/csrc/api/include/torch/optim/adam.h:58: undefined reference to `c10::detail::torchCheckFail(char const*, char
const*, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Cpp/libtorch/include/torch/csrc/api/include/torch/optim/adam.h:59: undefined reference to `c10::detail::torchCheckFail(char const*, char
const*, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
          /usr/bin/ld: /home/chien/Development/Rust/tch-demo/target/debug/deps/libtorch_sys-73e1c808b35185b8.rlib(torch_api.o): in function `at_load_callback_with_device':
          /home/chien/.local/share/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/torch-sys-0.6.1/libtch/torch_api.cpp:329: undefined reference to `torch::jit::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, c10::optional<c10::Device>)'
          collect2: error: ld returned 1 exit status

  = help: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname)

error: could not compile `tch-demo` due to previous error

where did i go wrong? thanks you.

Not sure that it's actually the issue here but note that tch-rs is currently compatible with libtorch 1.10.0 and not 1.10.1 so you may want to change the version you use.

@chienguo Have you fixed the issue?

Sorry, I have already download the libtorch of 1.10.0+cpu, and changed the environment followed the documentation:
$ echo $LIBTORCH
/home/chien/Developments/Cpp/libtorch
$ echo $LD_LIBRARAY_PATH
/home/chien/Developments/Cpp/libtorch/lib

but when I run  cargo run --example basics, it still went run:
target/debug/examples/basics: error while loading shared libraries: libtorch_cpu.so: cannot open shared object file: No such file or directory

I finally figured it out. You may need the -cxx11-abi- version.

Sorry, just found that I made a typing mistake when I set $LD_LIBRARY_PATH. I have correct it, now everything works great. Thanks for your patience!

I finally figured it out. You may need the -cxx11-abi- version.

Got this working for me! Thanks a lot, mate!!


superagent 1.1.0 vs 3.8.2

Changing the superagent dependency is breaking our application (running on node 0.12), as the main version of this package was not changed. We are using inline-css, which depends on extract-css, href-content and at the end remote-content.
Please revert the superagent to 1.1.0 in the v1.x.x versions.

Node v0.12 reached end of life at the end of 2016 and is no longer supported. If you can't upgrade Node, my suggestion is to fix the version of this package to 1.0.1.

We cannot downgrade your package, as the dependency is in a package which is a dependency of an other package...
I am asking you to fix your versioning according to semver.
I know that node v0.12 is not supported, and our upgrade is ongoing, but until then we cannot deploy our app.

I would argue that I am not violating semver because there were no breaking changes in this module. Tests are passing for all currently supported versions of node.
This dependency is four levels deep so I would have to bump the major version for four modules to do what you are asking, all with no breaking code changes so that you can stay on a version of node that has not been supported in over a year. My apologies but I am not currently inclined to do that.
You can fork the modules and have npm pull from your repo and then you should be able to deploy.

You are right in that we are using an outdated node version.
For quick fix we use npm-shrinkwrap.json.
Thanks.


Fix a sidekiq scheduling matcher worker bug

You seemingly can't pass through keyword arguments via sidekiq, so let's go back to options hashes to achieve the same thing.
Context
https://sentry.io/organizations/dfe-teacher-services/issues/3754948935/?project=1765973&referrer=slack

 Change frequency of running duplicate matches script


How to export instrument methods in meta data?

Hi developer,
I want to know is ThermoRawFileParser able to export instrument methods of hundreds of raw files in batch mode?
I have more than 100+ raw files downloaded from pride database, each of them has different instrument methods, I want to export the detailed instrument methods from all these raw files, can we do it?
For example the instrument methods below from Xcalibur:

But the meta data exported by ThermoRawFileParser has no these information (see below):
Created by=[MS, MS:1000529, created_by, Orbitrap_Lumos]
Number of instruments=4
Description=
Instrument model=[MS, MS:1000494, Thermo Scientific instrument model, Orbitrap Fusion Lumos]
Instrument name=Orbitrap Fusion Lumos
Instrument serial number=[MS, MS:1000529, instrument serial number, FSN20113]
Software version=[NCIT, NCIT:C111093, Software Version, 2.1.1565.18]
Firmware version=
Units=None
Mass resolution=[MS, MS:1000011, mass resolution, 0.500]
Number of scans=19123
Scan range=1;19123
Scan start time=[MS, MS:1000016, scan start time, 0.00]
Time range=0.00;90.00
Mass range=100.0000;2000.0000

#Sample information
Sample name=
Sample id=27
Sample type=Unknown
Sample comment=
Sample vial=RG1
Sample volume=0
Sample injection volume=3.5
Sample row number=2
Sample dilution factor=1

Hi @01joy ,
ThermoRawFileParser does not support method extraction in metadata. You can extract methods in plain text and (only some information) to CSV and XML, using different tool - https://bitbucket.org/caetera/scanheadsman/src/netcore/. Hope it will help.
#75

Hi @caetera ,
Thank you very much, I have tried your recommended tool, the scanheadsman, it is a very fantastic tool, it can export the detailed info for each ms2 scan, that's what I want. Thank you very much.


feature request: try_rcu / some return value to the caller of rcu

Sometimes the closure passed to rcu()  needs to be observable to the caller.
e.g.
i = **as.load()
as.rcu(|i| if *i > 10 {  i }  else {*i + 1});
if i == **as.load() {
   Err("hit the limit")
} else {Ok(())}

But this is clearly racy as we are re-reading.
I would love to be able to do:
as.try_rcu(|i| if *i > 10 {     Err("hit the limit")  }  else { Ok(*i + 1)});

or some similar construct, where the computation within the closure is able to signal to the caller.
Would you like a patch?

Hello
To be honest, I kind of don't understand what you're trying to say/accomplish. Maybe you could sketch the signature of that try_rcu?
Does it help that the rcu returns the previous value or that the closure passed in is FnMut, therefore you can „export“ any notes outside, like
bool changed = false;
as.rcu(|i| if (*i > 10) { i } else { changed = true; *i + 1 });
if changed { ... }

Anyway, sometimes I feel like the rcu itself is already a bit too complicated bit of API, considering the lowlevelness of the whole thing… therefore I don't really enjoy the idea of adding something even more complex. Isn't it enough that anything like that can be quite easily built with compare_and_swap (with inspiration by looking at the source code of rcu)?

Hmm, now I see the purpose.
My little worry here is, if it works for Result<.., ..>, should it also work for Option and for futures, etc. Unfortunately, Try is not stable yet :-(.
So I have to wonder if:

Better let these things live outside.
Do just this one for Result
Depend on a nightly feature (I don't like this one here)
Introduce our own Try for Result and Option, and ControlFlow (under a feature gate to allow compiling on old  rusts).

None of them looks like the ideal solution, but I'm open to your views on what to do here.

I don't have a strong opinion on the details, other than it would just be nice to have the feature.
Result is more general than Option - Result<T, ()> can model an Option, but not vice versa, so my suggestion would be to either implement just Result until Try is stable, and then revisit after stabilisation.

OK, that's fair. That being said, I'm not 100% sure extanding that try_rcu for the future Try would be a semver-compatible change at that point. But we can leave it until then.
Would you send a PR?
(And sorry that my answer took so long, too many other things to attend to…)


Email notification when the endpoint status turns to 'up'

A notification email should also be sent when the endpoint status turns to 'up' so as the administrator acknowledges that the endpoint is back to normal

Implemented, will be included in the next minor release v3.3.6


[SPARK-49629][CORE] JsonProtocol should use 'Shuffle Push Read Metrics' and 'Merged Fetch Fallback Count' fields of shuffle read metrics

What changes were proposed in this pull request?
JsonProtocol should use 'Shuffle Push Read Metrics' and 'Merged Fetch Fallback Count' fields of shuffle read metrics
Why are the changes needed?
JsonProtocol writes 'Push Based Shuffle' and 'Merged Fetch Fallback Count' fields of shuffle read metrics at present, which is inconsistent with 'Shuffle Push Read Metrics' and 'Merged Fallback Count' fields of task metric from json. Therefore, JsonProtocol should use 'Shuffle Push Read Metrics' and 'Merged Fetch Fallback Count' fields of shuffle read metrics.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
JsonProtocolSuite.
Was this patch authored or co-authored using generative AI tooling?
No.

Circling back to this PR - agree with your comment @JoshRosen.
Are you proposing to hold this PR until JSONProtocol test coverage is better ?


Setting up a database service with underscores fails and gives no UI acknlowledgment

https://user-images.githubusercontent.com/42276144/135534441-263b4fce-0a2f-4645-aa09-d1efde3de70d.mov
As detailed in the above video, I can fill out the form and click Save.  The modal closes, but no Database Service is created because the API request returned 400 with the following error.  There is no modal or error popup detailing what went wrong with the request, it just fails silently.
Cannot deserialize value of type `java.net.URI` from String "my_sql_user:mysql_pass@localhost:3306/test": not a valid textual representation, problem: Illegal character in scheme name at index 2: my_sql_user:mysql_pass@localhost:3306/test
 at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 185] (through reference chain: org.openmetadata.catalog.api.services.CreateDatabaseService["jdbc"]->org.openmetadata.catalog.type.JdbcInfo["connectionUrl"])

Thanks for reporting the issue @juliarvalenti .
@darth-coder00 can you take a look at the UI part and I'll check the backend exception.

Thanks for reporting the issue @juliarvalenti . @darth-coder00 can you take a look at the UI part and I'll check the backend exception.

Sure, will take a look


pydeck: Correct PUBLISH.md typo

Background

Change List

Coverage decreased (-2.5%) to 80.855% when pulling f654ef7fc00c4672bfd9fcb3ed001b413352f8d8 on ajd/remove-version into 0a86e916a54558d1ebcdcceb2cfbfb46ceb0fd27 on master.


Incompatibility with Immersive Portals: Can't ping beyond certain distance

With both this mod and the mod Immersive Portals installed, pings do not work beyond roughly 29m; nothing visibly happens when pressing the ping button, and a "raycast too far" error is output to the log. Tested on 1.20.1 both with Fabric and with Quilt, and with a couple of different versions of Ping Wheel and of Immersive Portals. Attached is an example log file containing the error.
Apologies if this turns out to be an issue that needs fixed by Immersive Portals rather than Ping Wheel; I wasn't sure where this should be reported. 😓

Hey!
As you already suspected, this is caused by Immersive Portals.

Looking at Immersive Portals' source code, I found the message that was thrown.
As of now it is unclear if this can be resolved within Ping Wheel's code.
Using Mixins is a complicated topic and it might just be 100% Immersive Portals' fault.
Thank you for your report and I'm sorry for any inconveniences this might have caused.
Luken or I will give you feedback once we know more... or if we don't get any progress in this at all.

In further investigation we found out that this is caused by an internal limit of raytraces set by Immersive Portals. If we exceed the hardcoded limit of 512 meters it will hardlimit the raytrace to 30 meters (not 512, for whatever reason) and throw the mentioned error. FYI; We use a raytrace with a limit of 1024, which will always throw an error.
We plan to accommodate users by dynamically limiting the raytracing based on their client-side render distance. This will still throw errors when using render distances above 30ish chunks, but we will not fix issues specific to Immersive Portals as we don't understand the need to limit our raytrace further.

As promised, there is now a compatibility layer available with the new version, 1.5.0. We didn't implement it as a dynamic raytrace-limit as stated a week ago tho. This is because of several limitations and mainly because of compatibility issues with alternate renderers like Sodium.
The option is available as raycastDistance in /config/ping-wheel.json and has to be set to either 255 (1.18) or 511 (>1.18) to prevent issues with Immersive Portals.


chore: move @frp-ts/test-utils to dev dependencies

Hi, last build of<EMAIL_ADDRESS>has next peerDeps:
"peerDependencies": {
    "@types/react": ">=16.0.0",
    "react": ">=16.0.0",
    "tslib": "^2.3.1",
    "@frp-ts/test-utils": "1.0.0-beta.0"
  },

where @frp-ts/test-utils is a private, non publisable library.
So when I tired to install it i got next error:

I take a look for other packages and add changes to packages where NX add this libs as a peer.

Alternatively you can set updateBuildableProjectDepsInPackageJson to false in your executor's options


Using Whisper for Chinese ASR in iOS may occasionally output illegal UTF-8 strings.

Describe the bug
A clear and concise description of what the bug is.
I followed the document at https://github.com/microsoft/Olive/tree/main/examples/whisper using the following command to generate the Whisper model: python prepare_whisper_configs.py --model_name openai/whisper-tiny --no_audio_decoder --multilingual --enable_timestamps | olive run --config whisper_cpu_int8.json 2> /dev/null. Because using the CPUExecutionProvider on an iPhone causes the phone to overheat severely, I implemented the following strategy: I run an ORTSession every 2 seconds to get the transcribed text, and based on the timestamps in the returned text, I decide whether to discard the corresponding audio samples that have already been correctly transcribed. Most of the time, the text is output normally, but there are instances where the output of an illegal UTF8 string causes the onnxruntime-objc to crash.
crash stack https://github.com/microsoft/onnxruntime/issues/21026
To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Olive config
Add Olive configurations here.
Olive logs
Add logs here.
Other information

OS: iOS
Olive version: 0.7.0
ONNXRuntime package and version: onnxruntime-objc: 1.18.0

Additional context
Add any other context about the problem here.

Hello,
I have encountered a similar issue while trying to use Olive Whisper to transcribe in Tajik Language. The resulting model from Olive performs far worse than a basic ONNX model and suffers from severe hallucinations. The Olive model also occasionally produces illegal UTF-8 strings, as you have mentioned. I have been unable to find an explanation or a fix for this.


example returns pre-formatted string, not HTML

I'm trying out the following example of using the html plugin(0.7.3):
import { Elysia } from 'elysia'
import { html } from '@elysiajs/html'

new Elysia()
    .use(html())
    .get('/', () => (

                <title>Hello World</title>

Hello World

    ))
    .listen(3000)

The response header is content-type | text/plain;charset=utf-8, and the rendered HTML looks like the following:

The problem is solved when I switch back to 0.6.5.

Wrap your html code in backtick.
                                                   <title>Hello World</title>
Hello World

@arthurfiorette, I tried that one before switch back to 0.6.5, and it didn't work for me. my bun ver. is 1.0.0. Below is what I have in my package.json:
"dependencies": {
    "@editorjs/editorjs": "^2.28.0",
    "@editorjs/header": "^2.7.0",
    "@editorjs/image": "^2.8.1",
    "@editorjs/link": "^2.5.0",
    "@editorjs/list": "^1.8.0",
    "@elysiajs/html": "^0.6.5",
    "@elysiajs/static": "^0.6.0",
    "@kitajs/html": "^3.0.2",
    "@kitajs/ts-html-plugin": "^1.3.0",
    "@material-ui/core": "^4.12.4",
    "@t3-oss/env-core": "^0.7.0",
    "@types/markdown-it": "^13.0.1",
    "@types/react": "^18.2.28",
    "beth-stack": "^0.0.34",
    "elysia": "latest",
    "markdown-it": "^13.0.1",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "zod": "^3.22.4"
  },
  "devDependencies": {
    "bun-types": "latest",
    "typescript": "latest"
  },

So your problem was outdated bun?

No, bun update updates elysia. My bun ver. remains at 1.0.0.


@ not allowed in username in EX_ConnectionStrings__Email

Hello,
I'm having trouble setting up Exceptionless with SMTP.
I run following command and exceptionless doesn't start up at all.
docker run --rm -it -p 7000:80 `
-e EX_ConnectionStrings__Email=smtps://user@domain.com:password@smtp.server.com:25 `
-v esdata:/usr/share/elasticsearch/data `
exceptionless/exceptionless:latest

I suppose that the bit that is failing is the @ in my username. Is there another way of setting up the SMTP connection?
Thanks in advance!

You probably need to URL escape the @ sign with %40 like smtps://user%40domain.com:password@smtp.server.com:25

You probably need to URL escape the @ sign with %40 like smtps://user%40domain.com:password@smtp.server.com:25

Eric is correct, you need to escape it. Please let us know if you have any questions or feedback.

Eric is correct, you need to escape it. Please let us know if you have any questions or feedback.


QueryString method to parse query strings in the same way as forms

I realized the majority of the functionality between parsing form data and query strings was identical, and thought this may be useful to some other people!

Thanks for the contribution, Logan!
Form() should get the data from the query string if there is one - is that not happening for you?

Oops, my bad! I'm new to Go and didn't realize request.Form contained both the request body and query string together. False alarm

On May 27, 2015, at 1:29 AM, Matt Holt<EMAIL_ADDRESS>wrote:
Thanks for the contribution, Logan!
Form() should get the data from the query string if there is one - is that not happening for you?
—
Reply to this email directly or view it on GitHub.


Replace System.Resources.ReaderWriter

Part of #199.

:shipit:

Don't push until we grab newer CoreCLR bits since this uses a new package we don't have on our feed yet.

@BrennanConroy yup, aware of that :smile:

@BrennanConroy ok, let me know when you guys have that done.

BTW, we recently changed the feeds. This is where the component is located: https://www.myget.org/feed/dotnet-core/package/nuget/System.Resources.Reader

@KrzysztofCwalina we don't pull directly from those feeds in this build - we always take snapshots of CoreCLR as part of a separate process. However, isn't that the same feed as it always was, though?

Ya, thats the feed we've always used

We changed from dotnet-corefx to dotnet-core feed. I think the reson is that we ran out of space on the old feed ;-(

@KrzysztofCwalina ah ok I don't see us using the old feed anywhere. I'm pretty sure we always used the dotnet-core feed (not dotnet-corefx).


Zombie instance not terminated

Version

Karpenter Version: v0.21.1

Kubernetes Version: v1.23
Expected Behavior
Karpenter provisioned a node that never started (EC2 reachability check failed from the beginng). After 3 day, I manually terminated the node.
Node that doesn't join to the cluster after some timeout should be terminated automatically.
Side note -
I also noticed that CPU utilization of the cluster was low (more than expected impact) during this time, and improved significantly in the hour after it was terminated (also other provisioners which is weird). However, there was scaling down events during this time and I can't pinpoint the reason. Just mentioning here in case it make sense to find another bug (again, it was 3 days of low utilization that improved the hour after I manually terminated).
Actual Behavior
Manual monitoring and termination is needed
Steps to Reproduce the Problem
Get a node not to start due to some hardware issue (probably any issue, not just hardware)
Resource Specs and Logs
Karpenter just logged using drift detection that it couldn't identify the type (not relevant, I can add later)
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Closing in favor of #2021. @jonathan-innis FYI


Fix the association of code coverage results with source code

Description
Fix the association of code coverage results with source code.  You'll have seen how this was broken because we stopped getting the comment on PRs with coverage information.  My apologies for breaking this in the most recent change to centralized the CC runs.
Issues Resolved

Resolves https://github.com/opensearch-project/security/issues/2649

Testing
Inspecting CC report on this PR.
Check List

[ ] ~New functionality includes testing~
[ ] ~New functionality has been documented~
[X] Commits are signed per the DCO using --signoff

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

@RyanL1997 @DarshitChanpura Could I get a second review?


Update emu-t and emu-nt for line breaks

From tc39/ecma262#64
The ::after way did not work as expected in IE, because <emu-t> and <emu-nt> are inline element.
I modified these elements to inline-block, then browsers make new line at the border of blocks if it's overflowed.
This way needed resetting text-indent, because this style is inherited from parent and <emu-rhs> has text-indent: -25px;.

This looks good. Thank you so much @mysticatea!


Fixes for network soundness test

This PR introduces the changes to network_soundness.py test to make it work with Condor.

bors r+


Allow to use go:generate $GOPATH/bin/genny

This is frequently used go:generate prefix.

The GOPATH environment variable is defined to include any number of paths to "Go workspaces",
which are searched in order by the relevant go tools, so
$GOPATH/bin/genny

won't fly if the user has their GOPATH set to something like /home/doe/go:/foo/bar/go:/quux/xyzzy/go (on Unix; on Windows they would use the ; as the separator).
Please refer to the output of running go help gopath for more info.

@kostix Why do you think that $GOPATH=/home/doe/go:/foo/bar/go:/quux/xyzzy/go would broke genny? When you use // go:generate genny  is searches genny in the $PATH  environment variable. It may include any number of paths too. The first match will be applied.The same way as with the $GOPATH.
*ps Sorry for my poor English.


Laravel 11 install dep error

I get the following dep error trying to install Larabug on Laravel 11:
larabug/larabug[1.0, ..., 1.4.2, 2.0, ..., 2.0.1] require guzzlehttp/guzzle ~6.0 -> found guzzlehttp/guzzle[6.0.0, ..., 6.5.8] but these were not loaded, likely because it conflicts with another require.
    - larabug/larabug[2.1, ..., 2.1.1] require guzzlehttp/guzzle ^6.0.2 -> found guzzlehttp/guzzle[6.0.2, ..., 6.5.8] but these were not loaded, likely because it conflicts with another require.
    - larabug/larabug 2.1.2 requires illuminate/support 5.8.*|^6.0|^7.0 -> found illuminate/support[v5.8.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6] but these were not loaded, likely because it conflicts with another require.
    - larabug/larabug[2.2, ..., 2.3] require illuminate/support ^5.8|^6.0|^7.0|^8.0 -> found illuminate/support[v5.8.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
    - larabug/larabug[2.3.1, ..., 2.4.2] require illuminate/support ^5.5|^5.6|^5.7|^5.8|^6.0|^7.0|^8.0 -> found illuminate/support[v5.5.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
    - larabug/larabug[2.4.3, ..., 2.4.4] require illuminate/support ^6.0|^7.0|^8.0 -> found illuminate/support[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
    - larabug/larabug[2.5, ..., 2.5.3] require illuminate/support ^6.0 || ^7.0 || ^8.0 || ^9.0 -> found illuminate/support[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16] but these were not loaded, likely because it conflicts with another require.
    - larabug/larabug 3.0 requires illuminate/support ^6.0 || ^7.0 || ^8.0 || ^9.0 || ^10.0 -> found illuminate/support[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.8] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires larabug/larabug * -> satisfiable by larabug/larabug[1.0, ..., 1.4.2, 2.0, ..., 2.5.3, 3.0].

my composer req:
"require": {
        "php": "^8.2",
        "doctrine/dbal": "^4.0",
        "filament/filament": "^3.2",
        "firebase/php-jwt": "^6.10",
        "laravel/framework": "^11.0",
        "laravel/jetstream": "^5.0",
        "laravel/sanctum": "^4.0",
        "laravel/tinker": "^2.9",
        "livewire/livewire": "^3.0",
        "pdfgeneratorapi/php-client": "^4.0"
    },
    "require-dev": {
        "barryvdh/laravel-debugbar": "^3.12",
        "fakerphp/faker": "^1.23",
        "laravel-lang/common": "^6.1",
        "laravel/pint": "^1.13",
        "laravel/sail": "^1.26",
        "mockery/mockery": "^1.6",
        "nunomaduro/collision": "^8.0",
        "phpunit/phpunit": "^10.5",
        "spatie/laravel-ignition": "^2.4"
    },
    ```

This is expected currently, there is no release version with Laravel 11 yet.
Need to fix an other issue first.
But you can use the current master branch instead, this already has L11 support.

Are there any updates to support Laravel 11?

Are there any updates to support Laravel 11?

From my understanding Nathan already made a release with Laravel 11 support, only the tests are still broken.
https://github.com/LaraBug/LaraBug/releases/tag/3.1


Update landscape ad

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

:heavy_check_mark: Deploy preview for landscape ready!
:hammer: Explore the source changes: f325dbece4ab3b97a8879ce7821ddb626d49de15
:mag: Inspect the deploy logs: https://app.netlify.com/sites/landscape/deploys/5ff608cadc6311000812ffbe
:sunglasses: Browse the preview: https://deploy-preview-1948--landscape.netlify.app

:heavy_check_mark: Deploy preview for landscape ready!
:hammer: Explore the source changes: f325dbece4ab3b97a8879ce7821ddb626d49de15
:mag: Inspect the deploy logs: https://app.netlify.com/sites/landscape/deploys/5ff608cadc6311000812ffbe
:sunglasses: Browse the preview: https://deploy-preview-1948--landscape.netlify.app


Update to upstream v2.39.1

The dependency review action failed here and says it's not supported, so we should remove it from our tests.yml.

I tested this and it's working (see my update on https://hathitrust.atlassian.net/issues/TTO-203) but I'm not sure what the best thing to do is regarding deploying this.
I'm kind of inclined to discard what we have on the master branch here and just reset that to upstream master. Then, we can manage future updates by applying our patches in a branch against upstream tagged releases, and then just tagging that rather than merging it to any particular branch. Not really sure if there are some best practices/patterns out there for dealing with this kind of pattern. I've had to do this kind of thing (long-term fork with our patches) a couple times, and it's been frustrating both times -- as opposed to building debian or redhat packages or something, where there's a well-documented and widely-used pattern for applying local patches to an upstream release.

Going to tag this branch, close the PR, and manually set main to this.

It also looks like the upstream auth proxy now supports headers for additional claims: https://github.com/dexidp/dex/commit/366e53c1b690fea99e6a22da0ff4c87883128753
so we may be able to use that directly rather than needing to maintain a fork. I'll look into that in the future.


Allow Modifier type to be changed via annotation in a Kubernetes Ingress

What does this PR do?
This allows you to specify ReplacePathRegex rewrites using a Kubernetes Ingress backend. It works by creating an annotation (traefik.ingress.kubernetes.io/modifier-type: ReplacePathRegex) that overrides the default of ‘ReplacePath’.
Motivation
There was no way to specify these kinds of rewrite rules using Kubernetes Ingress backends. We needed this to preserve some compatibility between old clients and new APIs hosted in Kubernetes.
More

[x] Added/updated tests
[x] Added/updated documentation

Potentially solves Issue 2985.

Hello @alexquintero,
Thanks for your contribution!
Unfortunately, rewrite-target is not an annotation that can have its behavior switched, as it will cause other issues with compatability.
However, the need for matchers is indeed important, and I have created a PR (https://github.com/containous/traefik/pull/3481) that will enable all the matchers.
Once that PR is merged, we will close this one. Please take a look, and give feedback on that PR if you wish.

Closed in favor of  #3481


[funimation] Add new extractor

I messed up with the git while trying to squash. I have no idea where that Merge remote-tracking branch 'rg3/master' came from or why my commit got deleted.

This is finally ready, I hope.

Newly created funimation accounts does not seem to work at all. Can you provide account credentials for test?

With the current commit, I have used my new account with a FreePass. It worked with the one in the test. Most of the videos doesn't work with a free account as they are hosted with Hulu, but there are some that works, like the one in the test. But I spend an hour trying to find it, they are very rare. Funimation is very useless without a paid subscription.
My SubPass still works as intended. Here is an example:
python ~/Dev/youtube-dl/youtube_dl/__main__.py --username<EMAIL_ADDRESS>--password ytdltest http://www.funimation.com/shows/air/videos/official/breeze
[Funimation] http://www.funimation.com/login: Downloading webpage
[Funimation] breeze: Downloading webpage
[Funimation] breeze: Downloading m3u8 information
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 146
[download] Destination: Air - Breeze-AIRENG0001.mp4
[download]   0.0% of ~272.29MiB at 171.36KiB/s ETA 41:27

I also created a trial account. I can't give credentials for it as you can't use it without credit card information but it appears it works too:
python ~/Dev/youtube-dl/youtube_dl/__main__.py http://www.funimation.com/shows/noragami/videos/official/wish?watch=dub
[Funimation] http://www.funimation.com/login: Downloading webpage
[Funimation] wish: Downloading webpage
[Funimation] wish: Downloading m3u8 information
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 147
[download] Destination: Noragami - Wish-NRGENG6m9gJM0016.mp4
[download]   0.0% of ~1.23GiB at 94.58KiB/s ETA 04:36:38

Can you post the error you get?

Cherry-picked in ab4bdc913fafc71217c1196602525e0382c4eea3, thanks.


Add quaternion to dcm conversion to worldobject

Should take in quaternion with the scalar as the fourth component.
worldobject.quat2dcm(self, q)

Does this need to be in the object? Maybe converters and helper functions should be in a separate library.


Readme.md edit

Adding CNN model of summarization

Ah, got it. I thought all models which used fairseq are listed in this README.
Sorry for the confusion.


Setup Verilator lint and waivers

Setup Verilator lint and waivers
This adds Verilator lint support to our fusesoc core file. A waiver file
is created to waive all well-understood lint warnings. The UNOPTFLAT
warnings are not well understood at the moment, they are waived for now
and further discussion is expected to happen in a GH issue (referenced
in the waiver).
Run with
fusesoc --cores-root . run --target=lint lowrisc:ibex:ibex_core

The waiver file support requires edalize >= 0.1.5.

(Note: This is not yet ready for review, as I need to get the edalize changes upstream first.)

A new version of edalize has been released with the requested changes

Updated and ready for review.

Thanks @olofk for the edalize release!

Good catch Pirmin, thanks! Updated and merged.


Update AppEngine CloudSQL second generation sample

Update doc region tags for coming doc updates
Refactor query onto its own line with comment for clarity in code sample snippet
Add spec that can be run locally to verify working sample

Additional review of README:
-- Add allowed characters string, because the use of underscores in the placeholder can be misleading.
---- Ex from Console: "Use lowercase letters, numbers, or hyphens. Start with a letter".
-- I understand that Running Locally answers how to run it locally, but "bundle install" should be a step in the instruction set if not you can't run create_tables.rb.
-- You have two "in" on instruction #8

Done ~ ready for review @frankyn


Wi-Fi Direct API samples

Adding samples for Wi-Fi Direct APIs

Please squash the commits.

Vishal, use:
git rebase -i HEAD~4
Then choose pick, fixup, fixup and fixup respectively for each of the changes listed in the text editor that opens.


Can't build .net 6 projects with dependency on Microsoft.Azure.Cosmos on Linux

Hi,
We have a .net 6 project that takes dependency on the Microsoft.Azure.Cosmos nuget, and we build and run it on Linux. When we try to upgrade the version to any version above 3.28, we get runtime errors because our project also uses System.Drawing.Common version 4.7.0, but the Microsoft.Azure.Cosmos upgrade changes the System.Drawing.Common version to 6.0.0, which is only supported on Windows.
Is there any solution to this problem other than moving away from System.Drawing.Common?
Thanks,
Yael

Hi, the Microsoft.Azure.Cosmos nuget does not depend on Windows or Linux or any other platform. This is a NETStandard2.0 library/package, there is no platform specific dependencies: https://www.nuget.org/packages/Microsoft.Azure.Cosmos/#dependencies-body-tab

There is no System.Drawing.Common dependency.

Thanks @ealsur,
My understanding is that the System.Drawing.Common dependency comes from System.Configuration.ConfigurationManager:
It depends on System.Security.Permissions:

and the .net 6 version of that depends on System.Windows.Extensions:

I think that since the target framework of our project is .net 6, we get the .net 6 dependencies as opposed to the .netstandard2.0 dependencies.

@yaeldekel That is correct, but that does not depend on this library. This is Nuget dependency resolution. This is not something that can be "fixed" on this library, if System.Windows.Extensions has an issue on Linux that would be
What I can confirm though is that we have plenty of Linux users using versions that have System.Configuration.ConfigurationManager 6.0 and there are no build issues reported (otherwise the applications wouldn't run).
What is the exact build error you are getting? 6.0 versions of these packages are from .NET 6, it's weird that .NET being a cross-platform framework, cannot build on Linux.

@ealsur our perf runs do run on Linux. What .NET version are using?

@kirankumarkolli NET 6 https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos.Samples/Tools/Benchmark/CosmosBenchmark.csproj#L4

Closing due to inactivity, please reopen and share the complete build error.