Vue 2 removes former event listeners

I'm currently trying VueJS 2 and noticed a change when using it on existing DOM
Indeed everytime VueJS is initialised it will do something on existing DOM and will remove events previously binded outside of VueJS.
// We bind an event
document.querySelector('#demo').addEventListener('click', function () {
    alert("i'm a button")
})

// and it's lost when Vue is binded
new Vue({
    el: '#vuejs'
})

JSFiddle
This same example works fine with VueJS1. I don't have enough understanding of Vue core to understand what changed between the two version of the compiler.js that would explain this change.

Is there a reason why you can't use Vue events instead?

    <button id="demo" @click="var1 += 'a'">Bouton</button>

    {{ var1 }}

new Vue({
  el: '#vuejs',
  data: {
    var1: 'Hello world'
  }
})

Vue works under the assumption that you do not manipulate dom yourself.

Vue 2 retrieves and removes in-dom templates, compiles them to render functions, and render virtual dom back into real dom,
while Vue 1 doesn't remove in-dom templates.

 My use case is pretty specific since I use VueJS on a website using Turbolinks (that reloads the entire body every time a link is pressed) and bind a lots of events everywhere.

Such usage was never documented, and it's obviously a hack, so it wouldn't
be a surprise for most people.
On Fri, Sep 2, 2016, 16:17 Grafikart<EMAIL_ADDRESS>wrote:

That's a pretty stupid use case I know :)
Since it worked before it could be misleading for people migrating to v2.
My use case is pretty specific since I use VueJS on a website using
Turbolinks (that reloads the entire body every time a link is pressed) and
bind a lots of events everywhere.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue/issues/3587#issuecomment-244312649, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFTLl0SHGGk7LPlXEsVD5hbQEpeNaTXBks5ql9u3gaJpZM4JzdEX
.

Thanks ! I'll VueJS all my code :)

what if you're in the process of trying to migrate to vue, but you have some legacy parts in jquery
trying to move to vue now means an all or nothing approach
this bit me trying out my first vue component amongst my legacy components
so what you're saying is that I have to move all of them to vuejs and there is no way to intermingle?

Lucky there is a work around. For anyone else who finds this an easy way to get around it is to attach your listeners when vue mounts your element.
    mounted: function () {
      addHandlers(this.$el);
    },

Vue has created $el in the shadow dom but handlers still work if you do it after mounted.

@oppianmatt Could you share a clearer example, I can't tell from the api documentation how best to go about this

I got this to work by moving the script tag for my pre-existing DOM scripts to be AFTER the vuejs app code.

@squarenomad in your case why aren't you just using @click for the vue handling of a click?
This post was more for legacy js scripts for people who are migrating to vue but with a big codebase of libraries.
But yeah as @sroberson pointed out, attaching your handlers after vuejs has created it's shadow dom works. Whether that's just putting your script tags after (but then your code has to run synchronous), or by attaching your handlers in mounted.
Vue takes over the dom so handlers set before vue has taken over are going to be lost (or strange effects). Also can't really modify the dom elements that vue owns

The same thing with select2, if i use Vue.js in a page with Select2 it disables select2 events. How to reenable them?

The wonderful VueJS guide has an example how to wrap an existing js module, and the example they use is select2! https://vuejs.org/v2/examples/select2.html
It uses the very same technique in here by attaching to $el in the mounted stage.

Hello world example is always simple, but the real world is cruel. I cannot init select2 by using vue.js.  Select2 is inited by 3rd party framework.

I met the same problem.
I added an onsubmit listener into form before the form was bound to Vue.
But the onsubmit listener got lost.
Any solutions?

i met the same problem, when migrating from jQuery (i am undestand your pain :D).  As a temporary solution, you may mount Vue.js into small containers, until all your page will be rewritten on Vue.

met the same problem, when migrating from jQuery

Funny, I face the use case migrating kinda from Vue to somethinig. In fact, from Vue to Vue with jQuery on top.
The use case is:

Vue is on legacy code side, bundled and minified. No access to the source Vue code.
There are several ViewModels managed by Vue on the page. There are non-Vue parts of the DOM still.
The issue comes to life when I want to add a new listener within the DOM, which is managed by legacy Vue code. The listener gets erased by Vue.

To fix this I use the workaround here.
I assign non-Vue event listener after some timeout assuming that Vue has finished repacing its part of the DOM by the time timeout is ended. This way the listener is landed onto the DOM already rendered by Vue.
setTimeout(function () {
    document.querySelector('#test-button').addEventListener('click', function(e) {
        console.log('Click event worked');
    });;
}, 3000);

I know this is coarse. It especially could be coarse on slower devices and networks. So the timeout value should be tested on the real device before implementing this in production. But so far nothing better comes to mind for this use case.

I'm not integrating a legacy system - or upgrading from v1 to v2, but my use case is just a simple example in Codepen. I'm working through some exercises to explain Vue / in which I first show how we would complete the example with plain JS - and then with Vue to talk about the differences - and they can't coexist without following some rules. Example. Where you can't have your standard event listeners described before the new Vue instance. So, I'm showing these people how to do these super simple solutions and everything just does not work with no explanation. I didn't see a 'gotcha' section in the docks / but I'll help make one. I guess it makes sense that anything in the el/Vue context is going to get blown out and replaced - so, no event bound elements should exist in there. Is there a spot in the docs that talks about it?
There are no warnings or errors for so many simple cases I'm running into. Another example, is that you might set up an instance, and then create some components for that instance, but you have to register your components before you create a new instance. Which makes sense if you break it down - but feels a little unexpected and has no error: example

I'm new to Vue.js and I stumbled upon this issue in a project where we want to migrate from jquery to Vue incrementally. After a week of try and error I finally found this issue on Github. So I put the Vue code above the old jquery code and finally everything works. :tada:
This behavior should be definitely in the docs, maybe somewhere at the beginning.

So much effort is spent by various frameworks to implement and to use virtual DOM but in modern browsers it makes the very little speed difference while adding the pain to maintain the second-party components compatibility.
Maybe a good idea would be to have the configuration setting to turn off virtual DOM usage by the framework completely (it could be "on" by default, of course). Such as disabling of interpolation, which is very useful to avoid the conflicts with server-side Jinja2 templates, it is already possible.

I arrived here because event listeners added through Optimize would disappear
First I fixed it by adding v-on attributes but then changing to another page or reloading would make the event fail (as code is now added after Vue has loaded)
My final solution was to add both v-on and addEventListener. The event will not be fired twice as, if one listener exists, the other one doesn't

in my case, using webpack, sb-admin-2, and vuejs. I had to defer the loading of the scripts for sb-admin-2 for it to work properly(sidebar expand/collapse)
in my app.js/main.js where I instantiate the main VueJs app, I use require inside the mounted()
`import '../Common/main';
import Vue from 'vue';
new Vue({
el: '#wrapper',
mixins: mixinArray,
mounted() {
require('startbootstrap-sb-admin-2/vendor/bootstrap/js/bootstrap.bundle');
require('startbootstrap-sb-admin-2/vendor/jquery-easing/jquery.easing');
require('startbootstrap-sb-admin-2/js/sb-admin-2');
},
methods: {
}
});`
Hope this helps as I was on the same pain with the others, pulled some hair from  here and there,
just trying to migrate a jquery based app to vuejs.  >,,<


Add linting to CI for typescript and vue

We can enforce the formatting for vue.js and typescript in GitHub CI.

we are already utilizing yarn lint in there, so i guess we can close this


Update free-courses-pt_BR.md

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s)
For resources
Description
Adding free Angular 9 course by Cod3r
Why is this valuable (or not)?
Cod3r cares about its future and offers the best courses in the main technologies with excellence. Our teachers and methods will give you the basis and the foundations for you to learn the whys and walk the paths of success.
How do we know it's really free?
It's on YouTube.
For book lists, is it a book? For course lists, is it a course? etc.
It's a course.
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

For youtube, we prefer "playlist" links and the name of the producer/creator.


chattoapp.h and  chattoAdditions.h class in not call in my swift

hi sir,
Please help me out with this issue i am not able to remove this

What is your installation method?

@NaiyerAghaz Are you trying to compile this code in ChattoApp or in your own project?

I am also facing the same issue. I am trying to compile in my own project. If I run ChattoApp it is working. But if I copy all the code from ChattoApp to my app it is shwoing above error.


[keyvault] Evaluate timeout tests

The KV SDKs have a number of tests like this:
https://github.com/Azure/azure-sdk-for-js/blob/5be4e93e75027487b523faadb16e3d72788f9176/sdk/keyvault/keyvault-secrets/test/public/list.spec.ts#L164-L176
These tests seem to be intended to make sure the SDK honors the request timeout passed through OperationRequestOptions  I have a few issues with these tests:

They're very flaky and cause a lot of unnecessary nightly test failures (seriously, the vast majority of Key Vault pipeline failures are due to these tests, absent any persistent issue)
They don't work in playback mode since the response comes back too fast, limiting their value
Key Vault doesn't seem like the right place for these tests since, ultimately, they're testing functionality in Core
Other SDKs don't test this functionality

Questions:

Is there adequate test coverage elsewhere (e.g. in Core) of the timeout functionality?
If so, can we drop the timeout tests in Key Vault? If not, can we improve our test coverage in Core so that Key Vault doesn't need to test this anymore?

List of issues relating to these tests:

https://github.com/Azure/azure-sdk-for-js/issues/26229
https://github.com/Azure/azure-sdk-for-js/issues/26644
https://github.com/Azure/azure-sdk-for-js/issues/26157
https://github.com/Azure/azure-sdk-for-js/issues/25853
https://github.com/Azure/azure-sdk-for-js/issues/26182
https://github.com/Azure/azure-sdk-for-js/issues/23997
https://github.com/Azure/azure-sdk-for-js/issues/24755
https://github.com/Azure/azure-sdk-for-js/issues/23580


Newline in Content-Type meta tag breaks the page

What steps will reproduce the problem?

Make a new webpage with the following meta tag:
<meta http-equiv="Content-Type" content="text/html;

charset=UTF-8">
2. Upload the file to your server with the standard mod_pagepeed
configuration loaded.
3. Open the website in the Chrome browser
What is the expected output?
You should see the webpage you've just created.
What do you see instead?
This webpage is not available
ERR_CONTENT_DECODING_FAILED
What version of the product are you using (please check X-Mod-Pagespeed
header)?
X-Mod-Pagespeed: <IP_ADDRESS>-4448
On what operating system?
Redhat 5
Which version of Apache?
Apache version 2.2.3-91
Please provide any additional information below, especially a URL or an
HTML file that exhibits the problem.
Here's a demo page - http://www.allesamerika.sbi1b.sitesell.com/cultuur-amerika.html

Out of curiosity, how do you manage to get newlines embedded in the
meta-tag string?
On Thu, May 14, 2015 at 5:06 PM, Sachin Sebastian<EMAIL_ADDRESS>wrote:

What steps will reproduce the problem?

Make a new webpage with the following meta tag:
<meta http-equiv="Content-Type" content="text/html;

charset=UTF-8">
2. Upload the file to your server with the standard mod_pagepeed
configuration loaded.
3. Open the website in the Chrome browser
What is the expected output?
You should see the webpage you've just created.
What do you see instead?
This webpage is not available
ERR_CONTENT_DECODING_FAILED
What version of the product are you using (please check X-Mod-Pagespeed
header)?
X-Mod-Pagespeed: <IP_ADDRESS>-4448
On what operating system?
Redhat 5
Which version of Apache?
Apache version 2.2.3-91
Please provide any additional information below, especially a URL or an
HTML file that exhibits the problem.
Here's a demo page -
http://www.allesamerika.sbi1b.sitesell.com/cultuur-amerika.html
—
Reply to this email directly or view it on GitHub
https://github.com/pagespeed/mod_pagespeed/issues/1083.

Because I was curious, I checked the spec.  It is not valid HTML to embed
newlines in quoted attribute values, at least by my interpretation of
http://www.w3.org/TR/html-markup/syntax.html#syntax-attribute-value :4.5.
Text and character data
Text in element contents
http://www.w3.org/TR/html-markup/syntax.html#contents (including in
comments http://www.w3.org/TR/html-markup/syntax.html#syntax-comments)
and attribute values
http://www.w3.org/TR/html-markup/syntax.html#syntax-attribute-value must
http://www.w3.org/TR/html-markup/terminology.html#must-requirement consist
of Unicode characters, with the following restrictions:

must
http://www.w3.org/TR/html-markup/terminology.html#must-requirement not
contain U+0000 characters
must
http://www.w3.org/TR/html-markup/terminology.html#must-requirement not
contain permanently undefined Unicode characters
must
http://www.w3.org/TR/html-markup/terminology.html#must-requirement not
contain control characters other than space characters     [I BELIEVE
THIS INVALIDATES NEWLINES]

However I agree that the bug is valid, and we should not generate an
invalid HTTP attribute just because we were given an invalid HTML attribute.
-Josh
On Thu, May 14, 2015 at 6:24 PM, Joshua Marantz<EMAIL_ADDRESS>wrote:

Out of curiosity, how do you manage to get newlines embedded in the
meta-tag string?
On Thu, May 14, 2015 at 5:06 PM, Sachin Sebastian <
<EMAIL_ADDRESS>wrote:

What steps will reproduce the problem?

Make a new webpage with the following meta tag:
<meta http-equiv="Content-Type" content="text/html;

charset=UTF-8">
2. Upload the file to your server with the standard mod_pagepeed
configuration loaded.
3. Open the website in the Chrome browser
What is the expected output?
You should see the webpage you've just created.
What do you see instead?
This webpage is not available
ERR_CONTENT_DECODING_FAILED
What version of the product are you using (please check X-Mod-Pagespeed
header)?
X-Mod-Pagespeed: <IP_ADDRESS>-4448
On what operating system?
Redhat 5
Which version of Apache?
Apache version 2.2.3-91
Please provide any additional information below, especially a URL or an
HTML file that exhibits the problem.
Here's a demo page -
http://www.allesamerika.sbi1b.sitesell.com/cultuur-amerika.html
—
Reply to this email directly or view it on GitHub
https://github.com/pagespeed/mod_pagespeed/issues/1083.

@jmarantz It does look like newline is invalid. That site is one of my client site, so I don't know how that newline came up there in the first place. I was assuming it could be one of the html editors doing it.
For now I've disabled 'convert_meta_tags' filter, and that fixed the issue.

I tried to reproduce this on master, but no luck.
Perhaps there has been a fix for this specific example, or it was fixed as a side-effect of an unrelated change. Tracing the code, it parses the mimetype/character set as declared within the attribute.
Looking closer, I could figure out the following example would still break, this still reproduces the problem on master for me:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;

charset=UT

F-8">
</head>
<body>
foo
</body>
</html>

For completeness, sample response headers resulting from similar html input:
2015/10/27 19:30:20 [debug] 103935#0: *2 HTTP/1.1 200 OK
Server: nginx/1.9.6
Content-Type: text/html; charset=zwa

hili
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
Date: Tue, 27 Oct 2015 18:30:20 GMT
X-Page-Speed: <IP_ADDRESS>-7430
Cache-Control: max-age=0, no-cache


Suggestion

one thing I'm thinking is wouldn't it be a better idea to make an exokernel and have the wasm VM be a library os kinda like ExOS https://github.com/gwoplock/ExOS/issues

even if you do that still means that the kernel is going to be quite large
at least in comparison to an exokernel and as we all know
big kernels are bad because they're more likely to crash
and if they crash you have to restart the whole computer also
sense the VM would be a library instead of the kernel itself
you could implement some of the more advanced wasm features
like a garbage collector or a dom, which would allow programs in general
to be smaller now I know wasm doesn't (currently) support either of those
but it will and having those in the kernel itself would make your kernel
huge maybe even the size of a monolith like Linux which again would be bad

when I initially made this issue I had no idea what I was talking about
so here's a new idea instead of having nebulet run on an exokernel have it be an exokernel
I know you can optimize the heck out of system calls since there now just function calls
but you could also have a library running on nebulet to add that functionality

What is the different between nebulet being an exokernel and nebulet being a monolithic kernel?

this is something cool that doesn't really contribute to the conversation
https://www.nexedi.com/news/NXD.Blog.WebLinux


24 | Automatically infer max and infernal cape from WiseOldMan

Let's get this rebased onto dev and then we can merge it in after #46.

Closing this in favor of the new PR into dev.


librealsense+realsense_ros Jetson Orin nano

Required Info
Nvidia Jetson Orin nano

Camera Model
{ D435 }

Firmware Version
<IP_ADDRESS>

Operating System & Version
Jetpack 5 (Ubuntu 20.04)  Jetson Linux 35.3.1

Kernel Version (Linux Only)
(5.1)

Platform
NVIDIA Jetson Orin Nano

SDK Version
{ 2.54.1 }

Issue Description
I am trying to get librealsense working with realsense_ros so that I can display a pointcloud in rviz...
I am following the instructions provided here...
https://github.com/IntelRealSense/realsense-ros/tree/ros1-legacy
realsense ros was installed using the method outlined in step 2 of the above instructions
To install realsense sdk I used two different methods from this guide
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md
1: When using the apt-get method
michael@ubuntu:~/catkin_ws$ roslaunch realsense2_camera rs_camera.launch
... logging to /home/michael/.ros/log/c18c36e2-1cfa-11ee-a3e2-c76eb876b7b1/roslaunch-ubuntu-77199.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://<IP_ADDRESS>:39847/
SUMMARY
PARAMETERS

/camera/realsense2_camera/accel_fps: -1
/camera/realsense2_camera/accel_frame_id: camera_accel_frame
/camera/realsense2_camera/accel_optical_frame_id: camera_accel_opti...
/camera/realsense2_camera/align_depth: False
/camera/realsense2_camera/aligned_depth_to_color_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye1_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye2_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_infra1_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_infra2_frame_id: camera_aligned_de...
/camera/realsense2_camera/allow_no_texture_points: False
/camera/realsense2_camera/base_frame_id: camera_link
/camera/realsense2_camera/calib_odom_file:
/camera/realsense2_camera/clip_distance: -2.0
/camera/realsense2_camera/color_fps: -1
/camera/realsense2_camera/color_frame_id: camera_color_frame
/camera/realsense2_camera/color_height: -1
/camera/realsense2_camera/color_optical_frame_id: camera_color_opti...
/camera/realsense2_camera/color_width: -1
/camera/realsense2_camera/confidence_fps: -1
/camera/realsense2_camera/confidence_height: -1
/camera/realsense2_camera/confidence_width: -1
/camera/realsense2_camera/depth_fps: -1
/camera/realsense2_camera/depth_frame_id: camera_depth_frame
/camera/realsense2_camera/depth_height: -1
/camera/realsense2_camera/depth_optical_frame_id: camera_depth_opti...
/camera/realsense2_camera/depth_width: -1
/camera/realsense2_camera/device_type:
/camera/realsense2_camera/enable_accel: False
/camera/realsense2_camera/enable_color: True
/camera/realsense2_camera/enable_confidence: True
/camera/realsense2_camera/enable_depth: True
/camera/realsense2_camera/enable_fisheye1: False
/camera/realsense2_camera/enable_fisheye2: False
/camera/realsense2_camera/enable_fisheye: False
/camera/realsense2_camera/enable_gyro: False
/camera/realsense2_camera/enable_infra1: False
/camera/realsense2_camera/enable_infra2: False
/camera/realsense2_camera/enable_infra: False
/camera/realsense2_camera/enable_pointcloud: False
/camera/realsense2_camera/enable_pose: False
/camera/realsense2_camera/enable_sync: False
/camera/realsense2_camera/filters:
/camera/realsense2_camera/fisheye1_frame_id: camera_fisheye1_f...
/camera/realsense2_camera/fisheye1_optical_frame_id: camera_fisheye1_o...
/camera/realsense2_camera/fisheye2_frame_id: camera_fisheye2_f...
/camera/realsense2_camera/fisheye2_optical_frame_id: camera_fisheye2_o...
/camera/realsense2_camera/fisheye_fps: -1
/camera/realsense2_camera/fisheye_frame_id: camera_fisheye_frame
/camera/realsense2_camera/fisheye_height: -1
/camera/realsense2_camera/fisheye_optical_frame_id: camera_fisheye_op...
/camera/realsense2_camera/fisheye_width: -1
/camera/realsense2_camera/gyro_fps: -1
/camera/realsense2_camera/gyro_frame_id: camera_gyro_frame
/camera/realsense2_camera/gyro_optical_frame_id: camera_gyro_optic...
/camera/realsense2_camera/imu_optical_frame_id: camera_imu_optica...
/camera/realsense2_camera/infra1_frame_id: camera_infra1_frame
/camera/realsense2_camera/infra1_optical_frame_id: camera_infra1_opt...
/camera/realsense2_camera/infra2_frame_id: camera_infra2_frame
/camera/realsense2_camera/infra2_optical_frame_id: camera_infra2_opt...
/camera/realsense2_camera/infra_fps: 30
/camera/realsense2_camera/infra_height: 480
/camera/realsense2_camera/infra_rgb: False
/camera/realsense2_camera/infra_width: 848
/camera/realsense2_camera/initial_reset: False
/camera/realsense2_camera/json_file_path:
/camera/realsense2_camera/linear_accel_cov: 0.01
/camera/realsense2_camera/odom_frame_id: camera_odom_frame
/camera/realsense2_camera/ordered_pc: False
/camera/realsense2_camera/pointcloud_texture_index: 0
/camera/realsense2_camera/pointcloud_texture_stream: RS2_STREAM_COLOR
/camera/realsense2_camera/pose_frame_id: camera_pose_frame
/camera/realsense2_camera/pose_optical_frame_id: camera_pose_optic...
/camera/realsense2_camera/publish_odom_tf: True
/camera/realsense2_camera/publish_tf: True
/camera/realsense2_camera/reconnect_timeout: 6.0
/camera/realsense2_camera/rosbag_filename:
/camera/realsense2_camera/serial_no:
/camera/realsense2_camera/stereo_module/exposure/1: 7500
/camera/realsense2_camera/stereo_module/exposure/2: 1
/camera/realsense2_camera/stereo_module/gain/1: 16
/camera/realsense2_camera/stereo_module/gain/2: 16
/camera/realsense2_camera/tf_publish_rate: 0.0
/camera/realsense2_camera/topic_odom_in: odom_in
/camera/realsense2_camera/unite_imu_method:
/camera/realsense2_camera/usb_port_id:
/camera/realsense2_camera/wait_for_device_timeout: -1.0
/rosdistro: noetic
/rosversion: 1.16.0

NODES
/camera/
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
ROS_MASTER_URI=http://<IP_ADDRESS>:11311/
process[camera/realsense2_camera_manager-1]: started with pid [77219]
process[camera/realsense2_camera-2]: started with pid [77220]
[ INFO] [1688767644.481799995]: Initializing nodelet with 6 worker threads.
[ INFO] [1688767646.182192671]: RealSense ROS v2.3.2
[ INFO] [1688767646.182439620]: Built with LibRealSense v2.50.0
[ INFO] [1688767646.182632616]: Running with LibRealSense v2.50.0
[ INFO] [1688767646.344277535]:
[ INFO] [1688767646.619063791]: Device with serial number<PHONE_NUMBER>92 was found.
[ INFO] [1688767646.619174962]: Device with physical ID 1-2.1-7 was found.
[ INFO] [1688767646.619202098]: Device with name Intel RealSense D435 was found.
[ INFO] [1688767646.621104056]: Device with port number 1-2.1 was found.
[ INFO] [1688767646.622154540]: Device USB type: 2.1
[ WARN] [1688767646.622346896]: Device<PHONE_NUMBER>92 is connected using a 2.1 port. Reduced performance is expected.
[ INFO] [1688767646.692568474]: getParameters...
[ INFO] [1688767647.917642833]: setupDevice...
[ INFO] [1688767647.918123099]: JSON file is not provided
[ INFO] [1688767647.918373696]: ROS Node Namespace: camera
[ INFO] [1688767647.918630661]: Device Name: Intel RealSense D435
[ INFO] [1688767647.918892202]: Device Serial No:<PHONE_NUMBER>92
[ INFO] [1688767647.919225456]: Device physical port: 1-2.1-7
[ INFO] [1688767647.919469973]: Device FW version: <IP_ADDRESS>
[ INFO] [1688767647.919725562]: Device Product ID: 0x0B07
[ INFO] [1688767647.920040641]: Enable PointCloud: Off
[ INFO] [1688767647.920271589]: Align Depth: Off
[ INFO] [1688767647.920513386]: Sync Mode: Off
[ INFO] [1688767647.920955859]: Device Sensors:
[ INFO] [1688767648.034201614]: Stereo Module was found.
[ INFO] [1688767648.065298068]: RGB Camera was found.
[ INFO] [1688767648.065461111]: (Confidence, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1688767648.069018269]: num_filters: 0
[ INFO] [1688767648.069092671]: Setting Dynamic reconfig parameters.
hwmon command 0x80( 5 0 0 0 ) failed (response -7= HW not ready)
hwmon command 0x80( 5 0 0 0 ) failed (response -7= HW not ready)
hwmon command 0x80( 5 0 0 0 ) failed (response -7= HW not ready)
hwmon command 0x80( 5 0 0 0 ) failed (response -7= HW not ready)
[ INFO] [1688767655.554418408]: Done Setting Dynamic reconfig parameters.
/opt/ros/noetic/lib/nodelet/nodelet: symbol lookup error: /home/michael/catkin_ws/devel/lib//librealsense2_camera.so: undefined symbol: _ZN2cv3MatC1Ev
[camera/realsense2_camera_manager-1] process has died [pid 77219, exit code 127, cmd /opt/ros/noetic/lib/nodelet/nodelet manager __name:=realsense2_camera_manager __log:=/home/michael/.ros/log/c18c36e2-1cfa-11ee-a3e2-c76eb876b7b1/camera-realsense2_camera_manager-1.log].
log file: /home/michael/.ros/log/c18c36e2-1cfa-11ee-a3e2-c76eb876b7b1/camera-realsense2_camera_manager-1*.log
[camera/realsense2_camera-2] process has finished cleanly
log file: /home/michael/.ros/log/c18c36e2-1cfa-11ee-a3e2-c76eb876b7b1/camera-realsense2_camera-2*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done
2: When using the RSUSB method
michael@ubuntu:~/librealsense$ realsense-viewer
bash: /usr/bin/realsense-viewer: No such file or directory
michael@ubuntu:~/catkin_ws$ roslaunch realsense2_camera rs_camera.launch
... logging to /home/michael/.ros/log/c18c36e2-1cfa-11ee-a3e2-c76eb876b7b1/roslaunch-ubuntu-67759.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://<IP_ADDRESS>:39381/
SUMMARY
PARAMETERS

/camera/realsense2_camera/accel_fps: -1
/camera/realsense2_camera/accel_frame_id: camera_accel_frame
/camera/realsense2_camera/accel_optical_frame_id: camera_accel_opti...
/camera/realsense2_camera/align_depth: False
/camera/realsense2_camera/aligned_depth_to_color_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye1_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye2_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_infra1_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_infra2_frame_id: camera_aligned_de...
/camera/realsense2_camera/allow_no_texture_points: False
/camera/realsense2_camera/base_frame_id: camera_link
/camera/realsense2_camera/calib_odom_file:
/camera/realsense2_camera/clip_distance: -2.0
/camera/realsense2_camera/color_fps: -1
/camera/realsense2_camera/color_frame_id: camera_color_frame
/camera/realsense2_camera/color_height: -1
/camera/realsense2_camera/color_optical_frame_id: camera_color_opti...
/camera/realsense2_camera/color_width: -1
/camera/realsense2_camera/confidence_fps: -1
/camera/realsense2_camera/confidence_height: -1
/camera/realsense2_camera/confidence_width: -1
/camera/realsense2_camera/depth_fps: -1
/camera/realsense2_camera/depth_frame_id: camera_depth_frame
/camera/realsense2_camera/depth_height: -1
/camera/realsense2_camera/depth_optical_frame_id: camera_depth_opti...
/camera/realsense2_camera/depth_width: -1
/camera/realsense2_camera/device_type:
/camera/realsense2_camera/enable_accel: False
/camera/realsense2_camera/enable_color: True
/camera/realsense2_camera/enable_confidence: True
/camera/realsense2_camera/enable_depth: True
/camera/realsense2_camera/enable_fisheye1: False
/camera/realsense2_camera/enable_fisheye2: False
/camera/realsense2_camera/enable_fisheye: False
/camera/realsense2_camera/enable_gyro: False
/camera/realsense2_camera/enable_infra1: False
/camera/realsense2_camera/enable_infra2: False
/camera/realsense2_camera/enable_infra: False
/camera/realsense2_camera/enable_pointcloud: False
/camera/realsense2_camera/enable_pose: False
/camera/realsense2_camera/enable_sync: False
/camera/realsense2_camera/filters:
/camera/realsense2_camera/fisheye1_frame_id: camera_fisheye1_f...
/camera/realsense2_camera/fisheye1_optical_frame_id: camera_fisheye1_o...
/camera/realsense2_camera/fisheye2_frame_id: camera_fisheye2_f...
/camera/realsense2_camera/fisheye2_optical_frame_id: camera_fisheye2_o...
/camera/realsense2_camera/fisheye_fps: -1
/camera/realsense2_camera/fisheye_frame_id: camera_fisheye_frame
/camera/realsense2_camera/fisheye_height: -1
/camera/realsense2_camera/fisheye_optical_frame_id: camera_fisheye_op...
/camera/realsense2_camera/fisheye_width: -1
/camera/realsense2_camera/gyro_fps: -1
/camera/realsense2_camera/gyro_frame_id: camera_gyro_frame
/camera/realsense2_camera/gyro_optical_frame_id: camera_gyro_optic...
/camera/realsense2_camera/imu_optical_frame_id: camera_imu_optica...
/camera/realsense2_camera/infra1_frame_id: camera_infra1_frame
/camera/realsense2_camera/infra1_optical_frame_id: camera_infra1_opt...
/camera/realsense2_camera/infra2_frame_id: camera_infra2_frame
/camera/realsense2_camera/infra2_optical_frame_id: camera_infra2_opt...
/camera/realsense2_camera/infra_fps: 30
/camera/realsense2_camera/infra_height: 480
/camera/realsense2_camera/infra_rgb: False
/camera/realsense2_camera/infra_width: 848
/camera/realsense2_camera/initial_reset: False
/camera/realsense2_camera/json_file_path:
/camera/realsense2_camera/linear_accel_cov: 0.01
/camera/realsense2_camera/odom_frame_id: camera_odom_frame
/camera/realsense2_camera/ordered_pc: False
/camera/realsense2_camera/pointcloud_texture_index: 0
/camera/realsense2_camera/pointcloud_texture_stream: RS2_STREAM_COLOR
/camera/realsense2_camera/pose_frame_id: camera_pose_frame
/camera/realsense2_camera/pose_optical_frame_id: camera_pose_optic...
/camera/realsense2_camera/publish_odom_tf: True
/camera/realsense2_camera/publish_tf: True
/camera/realsense2_camera/reconnect_timeout: 6.0
/camera/realsense2_camera/rosbag_filename:
/camera/realsense2_camera/serial_no:
/camera/realsense2_camera/stereo_module/exposure/1: 7500
/camera/realsense2_camera/stereo_module/exposure/2: 1
/camera/realsense2_camera/stereo_module/gain/1: 16
/camera/realsense2_camera/stereo_module/gain/2: 16
/camera/realsense2_camera/tf_publish_rate: 0.0
/camera/realsense2_camera/topic_odom_in: odom_in
/camera/realsense2_camera/unite_imu_method:
/camera/realsense2_camera/usb_port_id:
/camera/realsense2_camera/wait_for_device_timeout: -1.0
/rosdistro: noetic
/rosversion: 1.16.0

NODES
/camera/
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
ROS_MASTER_URI=http://<IP_ADDRESS>:11311/
process[camera/realsense2_camera_manager-1]: started with pid [67778]
process[camera/realsense2_camera-2]: started with pid [67779]
[ INFO] [1688766544.064357565]: Initializing nodelet with 6 worker threads.
[ INFO] [1688766544.292863953]: RealSense ROS v2.3.2
[ INFO] [1688766544.292977909]: Built with LibRealSense v2.50.0
[ INFO] [1688766544.293018966]: Running with LibRealSense v2.50.0
[ INFO] [1688766544.381246764]:
[ INFO] [1688766544.666438056]: Device with serial number<PHONE_NUMBER>92 was found.
[ INFO] [1688766544.667950802]: Device with physical ID 1-2.1-7 was found.
[ INFO] [1688766544.668289756]: Device with name Intel RealSense D435 was found.
[ INFO] [1688766544.670970662]: Device with port number 1-2.1 was found.
[ INFO] [1688766544.671796605]: Device USB type: 2.1
[ WARN] [1688766544.672153447]: Device<PHONE_NUMBER>92 is connected using a 2.1 port. Reduced performance is expected.
[ INFO] [1688766544.848428526]: getParameters...
[ INFO] [1688766546.021033316]: setupDevice...
[ INFO] [1688766546.021326220]: JSON file is not provided
[ INFO] [1688766546.021528882]: ROS Node Namespace: camera
[ INFO] [1688766546.021731287]: Device Name: Intel RealSense D435
[ INFO] [1688766546.021903900]: Device Serial No:<PHONE_NUMBER>92
[ INFO] [1688766546.022082209]: Device physical port: 1-2.1-7
[ INFO] [1688766546.022268070]: Device FW version: <IP_ADDRESS>
[ INFO] [1688766546.022455180]: Device Product ID: 0x0B07
[ INFO] [1688766546.022794805]: Enable PointCloud: Off
[ INFO] [1688766546.022983738]: Align Depth: Off
[ INFO] [1688766546.023158591]: Sync Mode: Off
[ INFO] [1688766546.023425031]: Device Sensors:
[ INFO] [1688766546.098159107]: Stereo Module was found.
[ INFO] [1688766546.143228487]: RGB Camera was found.
[ INFO] [1688766546.143381931]: (Confidence, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1688766546.143445677]: num_filters: 0
[ INFO] [1688766546.143479246]: Setting Dynamic reconfig parameters.
hwmon command 0x80( 5 0 0 0 ) failed (response -7= HW not ready)
hwmon command 0x80( 5 0 0 0 ) failed (response -7= HW not ready)
hwmon command 0x80( 5 0 0 0 ) failed (response -7= HW not ready)
hwmon command 0x80( 5 0 0 0 ) failed (response -7= HW not ready)
[ INFO] [1688766552.828000424]: Done Setting Dynamic reconfig parameters.
/opt/ros/noetic/lib/nodelet/nodelet: symbol lookup error: /home/michael/catkin_ws/devel/lib//librealsense2_camera.so: undefined symbol: _ZN2cv3MatC1Ev
[camera/realsense2_camera_manager-1] process has died [pid 67778, exit code 127, cmd /opt/ros/noetic/lib/nodelet/nodelet manager __name:=realsense2_camera_manager __log:=/home/michael/.ros/log/c18c36e2-1cfa-11ee-a3e2-c76eb876b7b1/camera-realsense2_camera_manager-1.log].
log file: /home/michael/.ros/log/c18c36e2-1cfa-11ee-a3e2-c76eb876b7b1/camera-realsense2_camera_manager-1*.log
[camera/realsense2_camera-2] process has finished cleanly
log file: /home/michael/.ros/log/c18c36e2-1cfa-11ee-a3e2-c76eb876b7b1/camera-realsense2_camera-2*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done

Hi @MichaelKerley  Versions 2.50.0 of the librealsense SDK and 2.3.2 of the ROS wrapper are the correct pairing.
It appears that you are experiencing the same error message when installing librealsense with either apt-get or an RSUSB source code build.
/opt/ros/noetic/lib/nodelet/nodelet: symbol lookup error: /home/michael/catkin_ws/devel/lib//librealsense2_camera.so: undefined symbol: _ZN2cv3MatC1Ev
Ideally, there should only be one type of librealsense installation on the same computer (either package or source code, but not both).
If the ROS wrapper was installed from source code with Step 2, then let's first try removing the librealsense package build so that only the source code build of the SDK remains.  Inputting the command below into the Ubuntu terminal should uninstall all RealSense related packages.
dpkg -l | grep "realsense" | cut -d " " -f 3 | xargs sudo dpkg --purge
If uninstalling the package version of librealsense does not make a difference, a RealSense ROS user at https://github.com/IntelRealSense/realsense-ros/issues/2467#issuecomment-1268417031 shares the method for how they resolved their own undefined symbol: _ZN2cv3MatC1Ev error.  They were using a Jetson AGX Orin in their particular case.

This issues is occured because you are download ddynamic_reconfigure multiple time
make this command
roscd ddynamic_reconfigure
and if it in the any workspace delete it and rebuild the workspace
and then check and remove it from main ROS distribute
sudo apt remove ros-distro-ddynamic_reconfigure
and reinstall ddynamic_reconfigure

I managed to get realsense viewer working after doing
dpkg -l | grep "realsense" | cut -d " " -f 3 | xargs sudo dpkg --purge
However now when building realsense ros I get
michael@ubuntu:~/catkin_ws$ catkin_make -DCATKIN_ENABLE_TESTING=False -DCMAKE_BUILD_TYPE=Release
Base path: /home/michael/catkin_ws
Source space: /home/michael/catkin_ws/src
Build space: /home/michael/catkin_ws/build
Devel space: /home/michael/catkin_ws/devel
Install space: /home/michael/catkin_ws/install

Running command: "make cmake_check_build_system" in "/home/michael/catkin_ws/build"

Running command: "make -j6 -l6" in "/home/michael/catkin_ws/build"

[  0%] Built target std_msgs_generate_messages_nodejs
[  0%] Built target sensor_msgs_generate_messages_nodejs
[  0%] Built target _realsense2_camera_generate_messages_check_deps_Metadata
[  0%] Built target sensor_msgs_generate_messages_lisp
[  0%] Built target _realsense2_camera_generate_messages_check_deps_DeviceInfo
[  0%] Built target _realsense2_camera_generate_messages_check_deps_IMUInfo
[  0%] Built target _realsense2_camera_generate_messages_check_deps_Extrinsics
[  0%] Built target std_msgs_generate_messages_lisp
[  0%] Built target sensor_msgs_generate_messages_eus
[  0%] Built target std_msgs_generate_messages_eus
[  0%] Built target sensor_msgs_generate_messages_cpp
[  0%] Built target std_msgs_generate_messages_cpp
[  0%] Built target std_msgs_generate_messages_py
[  0%] Built target sensor_msgs_generate_messages_py
[  0%] Built target _catkin_empty_exported_target
[  0%] Built target tf_generate_messages_nodejs
[  0%] Built target diagnostic_msgs_generate_messages_nodejs
[  0%] Built target diagnostic_msgs_generate_messages_eus
[  0%] Built target diagnostic_msgs_generate_messages_cpp
[  0%] Built target dynamic_reconfigure_gencfg
[  0%] Built target dynamic_reconfigure_generate_messages_cpp
[  0%] Built target tf2_msgs_generate_messages_nodejs
[  0%] Built target dynamic_reconfigure_generate_messages_lisp
[  0%] Built target tf2_msgs_generate_messages_cpp
[  0%] Built target tf2_msgs_generate_messages_lisp
[  0%] Built target actionlib_generate_messages_py
[  0%] Built target diagnostic_msgs_generate_messages_lisp
[  0%] Built target rosgraph_msgs_generate_messages_nodejs
[  0%] Built target actionlib_generate_messages_cpp
[  0%] Built target actionlib_msgs_generate_messages_py
[  0%] Built target roscpp_generate_messages_py
[  0%] Built target roscpp_generate_messages_eus
[  0%] Built target nav_msgs_generate_messages_cpp
[  0%] Built target dynamic_reconfigure_generate_messages_py
[  0%] Built target nav_msgs_generate_messages_eus
[  0%] Built target geometry_msgs_generate_messages_eus
[  0%] Built target actionlib_msgs_generate_messages_eus
[  0%] Built target roscpp_generate_messages_cpp
[  0%] Built target nav_msgs_generate_messages_lisp
[  0%] Built target geometry_msgs_generate_messages_py
[  0%] Built target tf2_msgs_generate_messages_eus
[  0%] Built target roscpp_generate_messages_lisp
[  0%] Built target actionlib_generate_messages_lisp
[  0%] Built target geometry_msgs_generate_messages_cpp
[  0%] Built target geometry_msgs_generate_messages_nodejs
[  0%] Built target dynamic_reconfigure_generate_messages_eus
[  0%] Built target std_srvs_generate_messages_cpp
[  0%] Built target rosgraph_msgs_generate_messages_lisp
[  0%] Built target tf_generate_messages_eus
[  0%] Built target rosgraph_msgs_generate_messages_eus
[  0%] Built target std_srvs_generate_messages_py
[  0%] Built target roscpp_generate_messages_nodejs
[  0%] Built target geometry_msgs_generate_messages_lisp
[  0%] Built target tf_generate_messages_py
[  0%] Built target tf_generate_messages_cpp
[  0%] Built target actionlib_msgs_generate_messages_nodejs
[  0%] Built target actionlib_msgs_generate_messages_cpp
[  0%] Built target actionlib_msgs_generate_messages_lisp
[  0%] Built target rosgraph_msgs_generate_messages_cpp
[  0%] Built target diagnostic_msgs_generate_messages_py
[  0%] Built target actionlib_generate_messages_eus
[  0%] Built target rosgraph_msgs_generate_messages_py
[  0%] Built target bond_generate_messages_lisp
[  0%] Built target nav_msgs_generate_messages_nodejs
[  0%] Built target dynamic_reconfigure_generate_messages_nodejs
[  0%] Built target bond_generate_messages_eus
[  0%] Built target tf2_msgs_generate_messages_py
[  0%] Built target std_srvs_generate_messages_lisp
[  0%] Built target std_srvs_generate_messages_eus
[  0%] Built target bond_generate_messages_cpp
[  0%] Built target nodelet_generate_messages_cpp
[  0%] Built target nodelet_generate_messages_lisp
[  0%] Built target nodelet_generate_messages_nodejs
[  0%] Built target actionlib_generate_messages_nodejs
[  0%] Built target nodelet_generate_messages_eus
[  0%] Built target std_srvs_generate_messages_nodejs
[  0%] Built target bond_generate_messages_nodejs
[  0%] Built target tf_generate_messages_lisp
[  0%] Built target nav_msgs_generate_messages_py
[  0%] Built target bond_generate_messages_py
[  0%] Built target nodelet_generate_messages_py
[ 14%] Built target realsense2_camera_generate_messages_lisp
[ 29%] Built target realsense2_camera_generate_messages_nodejs
[ 70%] Built target realsense2_camera_generate_messages_py
[ 70%] Built target realsense2_camera_generate_messages_eus
[ 85%] Built target realsense2_camera_generate_messages_cpp
[ 85%] Built target realsense2_camera_generate_messages
[ 96%] Building CXX object realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/base_realsense_node.cpp.o
[ 96%] Building CXX object realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/t265_realsense_node.cpp.o
[ 96%] Building CXX object realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/realsense_node_factory.cpp.o
In file included from /usr/include/boost/range/iterator_range_core.hpp:38,
from /usr/include/boost/lexical_cast.hpp:30,
from /opt/ros/noetic/include/ros/transport_hints.h:34,
from /opt/ros/noetic/include/ros/subscribe_options.h:33,
from /opt/ros/noetic/include/ros/node_handle.h:42,
from /opt/ros/noetic/include/ros/ros.h:45,
from /opt/ros/noetic/include/image_transport/publisher.h:38,
from /opt/ros/noetic/include/image_transport/image_transport.h:38,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/../include/../include/realsense_node_factory.h:8,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/../include/base_realsense_node.h:6,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/base_realsense_node.cpp:1:
/usr/include/boost/range/functions.hpp:18:10: fatal error: boost/range/begin.hpp: No such file or directory
18 | #include <boost/range/begin.hpp>
|          ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/boost/range/iterator_range_core.hpp:38,
from /usr/include/boost/lexical_cast.hpp:30,
from /opt/ros/noetic/include/ros/transport_hints.h:34,
from /opt/ros/noetic/include/ros/subscribe_options.h:33,
from /opt/ros/noetic/include/ros/node_handle.h:42,
from /opt/ros/noetic/include/ros/ros.h:45,
from /opt/ros/noetic/include/image_transport/publisher.h:38,
from /opt/ros/noetic/include/image_transport/image_transport.h:38,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/../include/realsense_node_factory.h:8,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/realsense_node_factory.cpp:4:
/usr/include/boost/range/functions.hpp:18:10: fatal error: boost/range/begin.hpp: No such file or directory
18 | #include <boost/range/begin.hpp>
|          ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
compilation terminated.
In file included from /usr/include/boost/range/iterator_range_core.hpp:38,
from /usr/include/boost/lexical_cast.hpp:30,
from /opt/ros/noetic/include/ros/transport_hints.h:34,
from /opt/ros/noetic/include/ros/subscribe_options.h:33,
from /opt/ros/noetic/include/ros/node_handle.h:42,
from /opt/ros/noetic/include/ros/ros.h:45,
from /opt/ros/noetic/include/image_transport/publisher.h:38,
from /opt/ros/noetic/include/image_transport/image_transport.h:38,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/include/../include/realsense_node_factory.h:8,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/include/base_realsense_node.h:6,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/../include/t265_realsense_node.h:3,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/t265_realsense_node.cpp:1:
/usr/include/boost/range/functions.hpp:18:10: fatal error: boost/range/begin.hpp: No such file or directory
18 | #include <boost/range/begin.hpp>
|          ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/build.make:76: realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/base_realsense_node.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/build.make:89: realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/t265_realsense_node.cpp.o] Error 1
make[2]: *** [realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/build.make:63: realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/realsense_node_factory.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1547: realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
Invoking "make -j6 -l6" failed

I managed to get realsense viewer working after doing
dpkg -l | grep "realsense" | cut -d " " -f 3 | xargs sudo dpkg --purge
However now when building realsense ros I get
michael@ubuntu:~/catkin_ws$ catkin_make -DCATKIN_ENABLE_TESTING=False -DCMAKE_BUILD_TYPE=Release
Base path: /home/michael/catkin_ws
Source space: /home/michael/catkin_ws/src
Build space: /home/michael/catkin_ws/build
Devel space: /home/michael/catkin_ws/devel
Install space: /home/michael/catkin_ws/install
Running command: "make cmake_check_build_system" in "/home/michael/catkin_ws/build"
Running command: "make -j6 -l6" in "/home/michael/catkin_ws/build"
[ 0%] Built target std_msgs_generate_messages_nodejs
[ 0%] Built target sensor_msgs_generate_messages_nodejs
[ 0%] Built target _realsense2_camera_generate_messages_check_deps_Metadata
[ 0%] Built target sensor_msgs_generate_messages_lisp
[ 0%] Built target _realsense2_camera_generate_messages_check_deps_DeviceInfo
[ 0%] Built target _realsense2_camera_generate_messages_check_deps_IMUInfo
[ 0%] Built target _realsense2_camera_generate_messages_check_deps_Extrinsics
[ 0%] Built target std_msgs_generate_messages_lisp
[ 0%] Built target sensor_msgs_generate_messages_eus
[ 0%] Built target std_msgs_generate_messages_eus
[ 0%] Built target sensor_msgs_generate_messages_cpp
[ 0%] Built target std_msgs_generate_messages_cpp
[ 0%] Built target std_msgs_generate_messages_py
[ 0%] Built target sensor_msgs_generate_messages_py
[ 0%] Built target _catkin_empty_exported_target
[ 0%] Built target tf_generate_messages_nodejs
[ 0%] Built target diagnostic_msgs_generate_messages_nodejs
[ 0%] Built target diagnostic_msgs_generate_messages_eus
[ 0%] Built target diagnostic_msgs_generate_messages_cpp
[ 0%] Built target dynamic_reconfigure_gencfg
[ 0%] Built target dynamic_reconfigure_generate_messages_cpp
[ 0%] Built target tf2_msgs_generate_messages_nodejs
[ 0%] Built target dynamic_reconfigure_generate_messages_lisp
[ 0%] Built target tf2_msgs_generate_messages_cpp
[ 0%] Built target tf2_msgs_generate_messages_lisp
[ 0%] Built target actionlib_generate_messages_py
[ 0%] Built target diagnostic_msgs_generate_messages_lisp
[ 0%] Built target rosgraph_msgs_generate_messages_nodejs
[ 0%] Built target actionlib_generate_messages_cpp
[ 0%] Built target actionlib_msgs_generate_messages_py
[ 0%] Built target roscpp_generate_messages_py
[ 0%] Built target roscpp_generate_messages_eus
[ 0%] Built target nav_msgs_generate_messages_cpp
[ 0%] Built target dynamic_reconfigure_generate_messages_py
[ 0%] Built target nav_msgs_generate_messages_eus
[ 0%] Built target geometry_msgs_generate_messages_eus
[ 0%] Built target actionlib_msgs_generate_messages_eus
[ 0%] Built target roscpp_generate_messages_cpp
[ 0%] Built target nav_msgs_generate_messages_lisp
[ 0%] Built target geometry_msgs_generate_messages_py
[ 0%] Built target tf2_msgs_generate_messages_eus
[ 0%] Built target roscpp_generate_messages_lisp
[ 0%] Built target actionlib_generate_messages_lisp
[ 0%] Built target geometry_msgs_generate_messages_cpp
[ 0%] Built target geometry_msgs_generate_messages_nodejs
[ 0%] Built target dynamic_reconfigure_generate_messages_eus
[ 0%] Built target std_srvs_generate_messages_cpp
[ 0%] Built target rosgraph_msgs_generate_messages_lisp
[ 0%] Built target tf_generate_messages_eus
[ 0%] Built target rosgraph_msgs_generate_messages_eus
[ 0%] Built target std_srvs_generate_messages_py
[ 0%] Built target roscpp_generate_messages_nodejs
[ 0%] Built target geometry_msgs_generate_messages_lisp
[ 0%] Built target tf_generate_messages_py
[ 0%] Built target tf_generate_messages_cpp
[ 0%] Built target actionlib_msgs_generate_messages_nodejs
[ 0%] Built target actionlib_msgs_generate_messages_cpp
[ 0%] Built target actionlib_msgs_generate_messages_lisp
[ 0%] Built target rosgraph_msgs_generate_messages_cpp
[ 0%] Built target diagnostic_msgs_generate_messages_py
[ 0%] Built target actionlib_generate_messages_eus
[ 0%] Built target rosgraph_msgs_generate_messages_py
[ 0%] Built target bond_generate_messages_lisp
[ 0%] Built target nav_msgs_generate_messages_nodejs
[ 0%] Built target dynamic_reconfigure_generate_messages_nodejs
[ 0%] Built target bond_generate_messages_eus
[ 0%] Built target tf2_msgs_generate_messages_py
[ 0%] Built target std_srvs_generate_messages_lisp
[ 0%] Built target std_srvs_generate_messages_eus
[ 0%] Built target bond_generate_messages_cpp
[ 0%] Built target nodelet_generate_messages_cpp
[ 0%] Built target nodelet_generate_messages_lisp
[ 0%] Built target nodelet_generate_messages_nodejs
[ 0%] Built target actionlib_generate_messages_nodejs
[ 0%] Built target nodelet_generate_messages_eus
[ 0%] Built target std_srvs_generate_messages_nodejs
[ 0%] Built target bond_generate_messages_nodejs
[ 0%] Built target tf_generate_messages_lisp
[ 0%] Built target nav_msgs_generate_messages_py
[ 0%] Built target bond_generate_messages_py
[ 0%] Built target nodelet_generate_messages_py
[ 14%] Built target realsense2_camera_generate_messages_lisp
[ 29%] Built target realsense2_camera_generate_messages_nodejs
[ 70%] Built target realsense2_camera_generate_messages_py
[ 70%] Built target realsense2_camera_generate_messages_eus
[ 85%] Built target realsense2_camera_generate_messages_cpp
[ 85%] Built target realsense2_camera_generate_messages
[ 96%] Building CXX object realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/base_realsense_node.cpp.o
[ 96%] Building CXX object realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/t265_realsense_node.cpp.o
[ 96%] Building CXX object realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/realsense_node_factory.cpp.o
In file included from /usr/include/boost/range/iterator_range_core.hpp:38,
from /usr/include/boost/lexical_cast.hpp:30,
from /opt/ros/noetic/include/ros/transport_hints.h:34,
from /opt/ros/noetic/include/ros/subscribe_options.h:33,
from /opt/ros/noetic/include/ros/node_handle.h:42,
from /opt/ros/noetic/include/ros/ros.h:45,
from /opt/ros/noetic/include/image_transport/publisher.h:38,
from /opt/ros/noetic/include/image_transport/image_transport.h:38,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/../include/../include/realsense_node_factory.h:8,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/../include/base_realsense_node.h:6,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/base_realsense_node.cpp:1:
/usr/include/boost/range/functions.hpp:18:10: fatal error: boost/range/begin.hpp: No such file or directory
18 | #include <boost/range/begin.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/boost/range/iterator_range_core.hpp:38,
from /usr/include/boost/lexical_cast.hpp:30,
from /opt/ros/noetic/include/ros/transport_hints.h:34,
from /opt/ros/noetic/include/ros/subscribe_options.h:33,
from /opt/ros/noetic/include/ros/node_handle.h:42,
from /opt/ros/noetic/include/ros/ros.h:45,
from /opt/ros/noetic/include/image_transport/publisher.h:38,
from /opt/ros/noetic/include/image_transport/image_transport.h:38,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/../include/realsense_node_factory.h:8,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/realsense_node_factory.cpp:4:
/usr/include/boost/range/functions.hpp:18:10: fatal error: boost/range/begin.hpp: No such file or directory
18 | #include <boost/range/begin.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
compilation terminated.
In file included from /usr/include/boost/range/iterator_range_core.hpp:38,
from /usr/include/boost/lexical_cast.hpp:30,
from /opt/ros/noetic/include/ros/transport_hints.h:34,
from /opt/ros/noetic/include/ros/subscribe_options.h:33,
from /opt/ros/noetic/include/ros/node_handle.h:42,
from /opt/ros/noetic/include/ros/ros.h:45,
from /opt/ros/noetic/include/image_transport/publisher.h:38,
from /opt/ros/noetic/include/image_transport/image_transport.h:38,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/include/../include/realsense_node_factory.h:8,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/include/base_realsense_node.h:6,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/../include/t265_realsense_node.h:3,
from /home/michael/catkin_ws/src/realsense-ros/realsense2_camera/src/t265_realsense_node.cpp:1:
/usr/include/boost/range/functions.hpp:18:10: fatal error: boost/range/begin.hpp: No such file or directory
18 | #include <boost/range/begin.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/build.make:76: realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/base_realsense_node.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/build.make:89: realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/t265_realsense_node.cpp.o] Error 1
make[2]: *** [realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/build.make:63: realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/realsense_node_factory.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1547: realsense-ros/realsense2_camera/CMakeFiles/realsense2_camera.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
Invoking "make -j6 -l6" failed

The problems in the wrapper build seem to begin with this error:
/usr/include/boost/range/functions.hpp:18:10: fatal error: boost/range/begin.hpp: No such file or directory
Boost was removed from the current latest librealsense SDK version 2.54.1.  Which librealsense version do you currently have installed, please?  If it is 2.54.1 then I can see how the removal of Boost as a dependency in this SDK version might cause the No such file or directory error.  As you are using ROS Noetic and wrapper 2.3.2, the librealsense version must not be newer than 2.51.1.

I am also facing a same error and my versions are:
2.50.0 of the librealsense SDK and 2.3.2 of the ROS wrapper
have you found any solid fix for this.
I am also running on jetson device with ubuntu 20.04
please help @MartyG-RealSense

Hi @fitzzzzzzzzz  The ROS1 wrapper (2.3.2) has not been updated since last year as development of it has ceased.  So the error would likely have been caused by something outside of the ROS wrapper as changes have not been made to the wrapper recently.
What method did you use to install librealsense and the ROS wrapper on your Jetson, please?

Hi @MartyG-RealSense , thank you so much for your quick response.
just a quick question, I am trying to reinstall again from the inputs you have shared above.
I am running this patch script from /scripts/patch-realsense-ubuntu-L4T.sh and I edited few lines like added 35.3.1 L4T version and jetpack as 5.1.1
I am getting a whole lot of errors, do you have any suggestion for that ?
i want to build the librealsense with cuda for ros1 for further use, please help.

If you are able to build librealsense from source code with CMake then using the RSUSB backend installation method avoids the need to use an edited patch script, as RSUSB bypasses the kernel and so it is not necessary to apply a kernel patch script when using RSUSB = true.
RSUSB is enabled by adding the flag -DFORCE_RSUSB_BACKEND=TRUE to the CMake build instruction.
If RSUSB does not work then it is also possible to use librealsense without applying a kernel patch, though the SDK will not provide hardware metadata information.
To enable CUDA support for Jetson in librealsense, you also need to include the flag -DBUILD_WITH_CUDA=TRUE
When CUDA support is enabled in librealsense, it is also automatically applied to the ROS wrapper.

thanks a lot, its working for me. @MartyG-RealSense

That's great to hear, @fitzzzzzzzzz - thanks very much for the update!

@MichaelKerley  As the creator of this issue, do you require further assistance with it please?  Thanks!

@MartyG-RealSense  I have one question though, what is the latest realsense ros-wrapper for jetpack 5.1. I want to use it with ros1 not with ros 2.
could you please help me out, becoz I am facing again above issue  again

JetPack 5.0.2 is supported by librealsense 2.54.1 but not JetPack 5.1.  A couple of RealSense users have tried editing the L4T kernel patch script to add 5.1 support themselves but it didn't work out.
So for 5.1 users I would recommend either not applying the kernel patch or build librealsense from source code with CMake with the -DFORCE_DSUSB_BACKEND=TRUE flag included in the CMake build instruction in order to bypass the kernel.
As you are using ROS1 and so librealsense 2.51.1 is the newest version that should be used with the ROS1 wrapper, not applying a kernel patch or using an RSUSB = true build of librealsense will work best for you if you have to use JetPack 5.1.

You could try Ubuntu 18.04 and JetPack 4.6.

okay thats the last option i hoped to try :(

any comment from repo owner??????

not yet

Case closed due to no further comments received.


Does training stop at some point on it's own or do I need to stop it after a checkpoint?

Should I just wait for it to complete or will it just run forever?

I read somewhere else that you need to stop it yourself.


toc strips newline from end of file

Traditionally, text files should end with a newline char.
The toc command strips the trailing newline from a README which has one.
I think that toc should either not change the presence or absence of a trailing newline, or if it does want to take an opinion on this issue, it should add one rather than remove one.

Sorry, this bug belongs on https://github.com/jonschlinkert/marked-toc not here.
I can't get markdown-toc to edit my README inline from the cli, so I can't retest if this bug also belongs here.

I can't get markdown-toc to edit my README inline from the cli, so I can't retest if this bug also belongs here.

I have now tested this (see #37), and markdown-toc has the same bug.
Please could you reopen?

Sorry I don't think i meant to close this one. my mistake.

Thanks!

thank you! sorry it took so long. Once I get behind (from a cold) it seems like it takes forever to catch back up!


Autoname aws secrets

Codecov Report

Merging #286 (6dd85a4) into develop (3558266) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #286   +/-   ##
========================================
  Coverage    33.08%   33.09%
========================================
  Files           49       49
  Lines         4803     4802    -1
========================================
  Hits          1589     1589
+ Misses        3063     3062    -1
  Partials       151      151

Flag
Coverage Δ

unittests
33.09% <ø> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/provider/pulumi/aws/aws.go
53.40% <ø> (+0.19%)
:arrow_up:

Continue to review full report at Codecov.

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


Fix remaining nightly failures.

Codecov Report

Merging #128 into master will decrease coverage by 0.01%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master     #128      +/-   ##
==========================================
- Coverage      89%   88.98%   -0.02%
==========================================
  Files          33       33
  Lines        3374     3377       +3
  Branches      556      558       +2
==========================================
+ Hits         3003     3005       +2
- Misses        262      263       +1
  Partials      109      109

Impacted Files
Coverage Δ

adanet/core/summary.py
93.38% <100%> (+0.01%)
:arrow_up:

adanet/tf_compat/__init__.py
77.31% <100%> (+0.19%)
:arrow_up:

adanet/core/estimator_distributed_test_runner.py
72.02% <40%> (-0.51%)
:arrow_down:

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 97a3c1f...5021681. Read the comment docs.


[Build System: CMake] Add back the missing install_name_dir for the standard library.

@swift-ci please smoke test


WIP Have a single point of reference for the .Net Core SDK version

PR Summary
Remove the hard-coded SDK version in the appeyor.yml file and parse the global.json file instead so that the only place referencing the .Net Core SDK version is global.json.
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an x between the square brackets. Please mark anything not applicable to this PR NA.

[x] PR has a meaningful title

[x] Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[ ] NA User facing documentation needed
[x] Change is not breaking
[ ] NA Make sure you've added a new test if existing tests do not effectively test the code changed
[ ] This PR is ready to merge and is not work in progress

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready

Well, it turns out that there seems to be a bug in Convert-FromJson in WMF4 that prevents if from working:
ConvertFrom-Json : Invalid object passed in, ':' or '}' expected. (1): {
At line:2 char:46
+ $globalDotJson = Get-Content .\global.json | ConvertFrom-Json
+                                              ~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [ConvertFrom-Json], ArgumentException
    + FullyQualifiedErrorId : System.ArgumentException,Microsoft.PowerShell.Commands.ConvertFromJsonCommand


Privacy policy not displayed correctly on old devices (EXPOSUREAPP-7268)

Please make sure that all App Information sub screens are working as before + on Android 6 have right formatting
Ticket
https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-7268
close https://github.com/corona-warn-app/cwa-app-android/issues/3166

This PR causes some longer URLs not to be completely displayed any more.
On Android 8, using 2.25.0 and selecting App Information > Data Privacy then URLs are fully visible. See especially the URLs in Section 7:

With this PR, the URLs still work as hyperlinks however they are truncated when displayed:

This PR causes some longer URLs not to be completely displayed any more.
On Android 8, using 2.25.0 and selecting App Information > Data Privacy, then URLs are fully visible. See especially the URLs in Section 7:

With this PR, the URLs still work as hyperlinks however they are truncated when displayed:

(Same problem on Android 6 and 12.)

@MikeMcC399  it is not truncated, you just need to scroll to the right. I will try to make content fit in the screen width.

@mtwalli

it is not truncated, you just need to scroll to the right.

You are right. Since there is no scroll-bar shown, I didn't think of trying to scroll to the right.

I will try to make content fit in the screen width.

Thank you!
I noticed two other unwanted side-effects of this change on Android 8:

When the privacy document is shown during onboarding, it displays as literal HTML text instead of being interpreted as HTML.
Links in the Terms of Use (App Information > Terms of Use) are no longer clickable.

Looks like using WebView comes with other issues ,despite text should be in HTML format , it appears to have some formatting issues. Closing this PR in favour of https://github.com/corona-warn-app/cwa-app-android/pull/5502


Update test-infra: keep only test-infra/scripts

Previous PR vendored unnecessary files from test-infra, update Gopkg.toml and clean up unneeded files
Link previous PR: https://github.com/knative/pkg/pull/175

/cc @adrcunha

Yay!
/approve
/lgtm


having issues compiling project

Hey,
i am just running your project for fun,but its giving me these errors..
ld: warning: directory not found for option
'-L/Users//Library/Developer/Xcode/DerivedData/Run-cltmfnuiujcqgwavllkejcboptgz/Build/Products/Debug-iphoneos/FrameAccessor'
ld: warning: directory not found for option
'-L/Users//Library/Developer/Xcode/DerivedData/Run-cltmfnuiujcqgwavllkejcboptgz/Build/Products/Debug-iphoneos/GoogleToolboxForMac'
ld: warning: directory not found for option
'-L/Users//Library/Developer/Xcode/DerivedData/Run-cltmfnuiujcqgwavllkejcboptgz/Build/Products/Debug-iphoneos/MKFoundationKit'
ld: warning: directory not found for option
'-L/Users//Library/Developer/Xcode/DerivedData/Run-cltmfnuiujcqgwavllkejcboptgz/Build/Products/Debug-iphoneos/UICountingLabel'
ld: library not found for -lFrameAccessor
clang: error: linker command failed with exit code 1 (use -v to see invocation)
also what if I want to run this project without these pods..

First, make sure the the pods are not missing. Secondly, you have to open the .xcworkspace(white) rather than . xcodeproj(blue). You might have to install the pods. Otherwise it will give you pod related issues.

Thanks for your interest in running my project. :)

hey,  yeah its a pretty cool project, I'm mostly interesting in the heart rate/workout area.
I am trying to create an iwatch app with a heart rate monitor. Your code has helped a lot!
thanks


Updated readme: UI & content

Updated readme: UI & content

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

@fulmicoton Almost good, can you check if there is no blunder in it?

@maximkpa @fmassot  Please, Can we have a screenshot of the search UI with the browser frame around the screenshot seems to be cut off though it's not.
Something like this with transparent background

@evanxg852000 good point, we can definitely improve this.

we plan to make a small video / gif, so we might skip the browser frame part.


Invoices: Discount has not effect on the invoice amount

Description
Neither the global discount on invoice level nor the specific discounts on salescontract position level have any effect on the calculated invoice amount. The amount is indepenantely calculatet with the full product price.
Reproduction

Create a new contract
Create a new invoice for the contract
Add two arbitrary positions to the contract (unit: h, product: 1 working hour in-house)
Set discount = 0.25 ...
a) ... on invoice level and check the resulting invoice amount
b) ... for one of the added salescontract positions and check the resulting invoice amount

Close issue due to an error while testing. The only problem here was that I tried to set the dicount to 0.25 instead of 25 (for 25 %)


Hrc are flushed sometimes for the subrtees in need.

Hrc files are great, but for big clouds their creation makes the conversion very slow, because all of them are recreated at each flush. I have a cloud with about 3 million bin files and 300k hrc files, and their creation takes about half of the time.
With this patch:

the hierarchy is not persisted at every flush, but more and more rarely, proceeding with the conversion
the subtrees that are not modified since the last flush do not update their hierarchy.

It seems to work for me.

Thanks for pointing out this issue. The PR is no longer compatible with the current branch but I'm going to use it as a reference for an up to date implementation.
I'd still like to flush the hierarchy at every flush, if possible. Hopefully it's fast enough if only modified hrc files are written.

Pushed something now: https://github.com/potree/PotreeConverter/commit/8ecacc95db44348a340e8e0dfd20979d91cbaf20 (experimental)
hrc files are only written to disk if they contain at least one new node.
After converting ~200m points, I get something like this:
´´´
hrcTotal: 16,659; hrcFlushed: 488
writing hierarchy: 0.018s
´´´
Previously 16.659 hrc files would have been written at that point and now it's just 488.
Test is still running. Previously, flushing took 70s after 3 billion points.

After converting 13 billion points with flush after every 50 million points:
INDEXING: 13,549,000,000 points processed; 13,549,000,000 points written; 41,322 seconds passed
INDEXING: 13,550,000,000 points processed; 13,550,000,000 points written; 41,323.7 seconds passed
FLUSHING: flush nodes: 42.498s
hrcTotal: 1,145,911; hrcFlushed: 4,345
writing hierarchy: 3.148s
46.683s

Hierarchy write duration for the last few flushes at >13b points ranged between ~1.5s to 6s.
Writing nodes took 30s to 50s.
Hierarchy write duration at <1b ranged between 0.01s to 1s
Writing nodes took 20s to 40s.
So flush performance still decreases but not that bad anymore.


Updated Sidebar with "MUX + MongoDB"

Description
The side navbar of the Mux and MongoDB sample app currently displays the name as "MUX+ Postgres," which is inaccurate. The correct representation should be "MUX + MongoDB." So I have updated the sidebar to accurately reflect the technologies used in the app.
Fixes #1402
Type of Change

[ x ] This change requires a documentation update.

Checklist:

[ x ] My code follows the style guidelines of this project.
[ x ] I have performed a self-review of my own code.
[ x ] I have made corresponding changes to the documentation.

Preview:

refering: - https://github.com/keploy/keploy/issues/1402


Blockchain

It's getting a file storing it in ipfs and returns a hash
Giving the hash to the analyze endpoint retrieves the file from ipfs and parses the image but not storing the hash in the blockchain ..it is not using smart contracts !!

It is storing the hash in the Blockchain through smart contracts. Check the Upload.js file in the components directory.
this.state.patient.methods.saveFile(this.state.fname, this.state.fhash, today).send({ from: this.state.account })
        .once('receipt', (receipt) => {
            console.log(receipt);
          this.setState({ loading: false })
        })


added my data

Good job @HarshJa1n
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in ClueLess Website.

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


Recover all translogs during relocation handoff for remote-backed indexes

Signed-off-by: Ashish Singh<EMAIL_ADDRESS>
Description
As discussed in #6214, during relocation certain documents indexed on the older primary were not seen on the new primary upon search. This was happening as recoverFromTranslog was recovering upto last known global checkpoint while it should be done upto Long.Max for cases where remote translog store is enabled.
https://github.com/opensearch-project/OpenSearch/blob/49d9a90b52d5451e0eda95ce03dfb94dd505a905/server/src/main/java/org/opensearch/index/shard/IndexShard.java#L4314-L4317
When remote translog is enabled, then remote store acts as the source of truth for storing translogs. During relocation we reset engine to writeable engine. When this happens, we initialise the RemoteFsTranslog which downloads all the translogs from remote store. The fix is to replay all the translogs here.
Issues Resolved
This fixes #6214.
Check List

[ ] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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.

Created manual PR - https://github.com/opensearch-project/OpenSearch/pull/6318


Webpack

Heya, I get this issue that webpack could not be started so it can't start the chat resource.
Any idea why this may be happening?

A workaround I found that works for this is to use a different chat resource that doesn't utilize webpack and yarn. However I'd still like the ability to use both webpack and yarn.

This issue seems to be happening with all the resources that need Yarn, really not sure what may be causing it.

Can confirm this issue does not occur on Spritsail's image


Antigen: PCR and Rapid test home screen cards (EXPOSUREAPP-6019, EXPOSUREAPP-6020, EXPOSUREAPP-6021)

PCR and Rapid test cards for Home Screen.

How to test:

test menu
"Home cards"
check all possible test cards for PCR and Rapid tests

Special note to testers:
Kindly check all these screens with different font size. Thank you 🚀

@AlexanderAlferov
Hi Alexander, from the screenshots of your OP, in case of positive test, the explaining text states 'no prove for a Virus'. Does the string pointer still need to be adapted here?

@AlexanderAlferov
Hi Alexander, from the screenshots of your OP, in case of positive test, the explaining text states 'no prove for a Virus'. Does the string pointer still need to be adapted here?

@vaubaehn hello. Great catch! Thank you ❤

PCR and Rapid test cards for Home Screen.

How to test:
1. test menu

2. "Home cards"

3. check all possible test cards for PCR and Rapid tests

Special note to testers:
Kindly check all these screens with different font size. Thank you 🚀

Both screenshots read "[Virus] wurde bei Ihnen NICHT nachgewiesen.", which seems strange after a positive test, no ;-)?

PCR and Rapid test cards for Home Screen.

How to test:
1. test menu

2. "Home cards"

3. check all possible test cards for PCR and Rapid tests

Special note to testers:
Kindly check all these screens with different font size. Thank you 🚀

Both screenshots read "[Virus] wurde bei Ihnen NICHT nachgewiesen.", which seems strange after a positive test, no ;-)?

@Diapolo , thanks for this catch! We already fixed that 🤖 Screenshot would be updated soon.

Found some issues when increasing the font size to the maximum (Samsung S20+)

Positive RAT (Without having warned others):

Positive RAT (also warned others)

Margin is missing between the first and second point (positive RAT, with and without having warned others)

Some cards should contain the date, I don't see any implementation of that.

Some cards should contain the date, I don't see any implementation of that.

Implementation would be added later when we will connect logic, model and these views. Right now logic and model is under development.

Text style (font color) looks different.


Use version in basepath

Maybe a bit nit-picking but I would like to use the version number as part of my basepath:
info:
  version: 0.9.1
  title: My API
host: localhost:5000
basepath: /api/0.9.1

Apparently I could edit both 0.9.1 instances of the api version, but I would like to just edit the version definition once and then reuse it in the basepath definition (I would never have different values for these two strings (unless of course I forget to edit both places))
Is this implemented? I thought I could use some kind of $ref but it seems I cannot.
Thanks!

You can't do that now, and I doubt you will be able to using this method. At best, we may allow templating in the basePath, but that's not exactly what you're looking for.

I think this issue should be addressed somehow, because I cannot think of a use-case where the info.version number would be different from the basepath version number (if I choose to include a version number in the basepath) and this invites the potential to have a misconfiguration if I forget to update one of the two values.
As I said before, not a show-stopper, but something in the "nice-to-have" category.

At best, we may allow templating in the basePath

Using a versioned API is currently really tedious and prone to breaking, so this is definitely something I could see myself using in our APIs:
info:
  version: 0.9.1
  title: My API
host: localhost:5000
basepath: /api/{info.version}/

Or, for OAS 3:
info:
  version: 0.9.1
  title: My API
servers:
  - url: localhost:5000/api/{info.version}/

The server object supports variables, which you can use to insert the version inside the base path.

The last comment seems to have provided the answer for OAS 3, so I'm closing this as resolved.


launcher update (minor)

@tch1001 Please remember to add a description that describes what you're doing. We're talking professional software development here
@lightningsf-ci please test this

I read the code and there seems to be no big change.

Thanks for your contribution! However, these contributions are extremely minor. Could you please make a few more changes before sending us a pull request? Apologies for all inconveniences caused.


Update sloth to 0.3.0

Updates com.github.cornerman.sloth:sloth from c0c6ef0 to 0.3.0.
GitHub Release Notes
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.cornerman.sloth", artifactId = "sloth" } ]

labels: library-update

@mergifyio update


Issue templates

So GitHub is testing an early preview of multiple Issue templates. Basically, we can set up multiple templates for Bugs/Questions/Feature requests and so on - I think these are great. Then the user that want to create an issue would see something similar to the UI below:

What I proposed in this PR are just templates directly from GitHub - we might want to evaluate what we could use from these and what we want to add from our own Issue_template.md.

I am not a big fan. I discussed MessageKit's issue template a while back with @SD10, which they feel is not working like they'd want to.
In the original issue template I intentionally made the barrier for creating an issue as low as possible, and these "please fill out this form" will not make it easier, I am afraid.
That being said, do you feel like there is a specific area of improvement? Maybe we can take a look at how we can tackle that?

I think that the templates are still just templates, you don't necessarily have to stick fully to the template - it should help in forming your opinion or bug report. Anyway, I would still pursue the idea of multiple issue templates, but I don't really have time to finish it, so I'm gonna close it 😢


Update README.md

Made the README more accessible, structured and including usable code snippets.

Hey Samuel,
nice work! I tried to improve the readability of your README file to support correct extension-mime-type-mapping in the world :wink:

Thanks!


Custom CA certificate - Prepare initContainer not mounted with service bindings

SSL certificate of Container Image registry is signed by a custom CA. Image resource is created with spec.build.services pointing to a secret containing CA certificate. Service binding volume is mounted only on detect and build initContainers and not on the prepare initContainer.
Build fails with the error reported by prepare initContainer stating
Error verifying write access to "registry01.cnalabs.com/kpack-demo/spring-petclinic": creating push check transport for registry01.cnalabs.com failed: Get "https://registry01.cnalabs.com/v2/": x509: certificate signed by unknown authority

To inject certs into the prepare container you will need to use something like the cert injection webhook https://github.com/vmware-tanzu/cert-injection-webhook with the label kpack.io/build


refactors vader_sentiment.py, adds Vader to requirements.txt

Description

refactors vader_sentiment.py
adds Vader to requirements.txt

This was already done once and it got reverted. Please remember to pull before you push!!!

[x] Bug fix

Checklist:

[x] My code follows PEP8 style guide
[x] I have removed unnecessary print statements from my code
[x] I have made corresponding changes to the documentation if necessary
[x] My changes generate no errors
[x] No commented-out code
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

I like how you changed it to use a string rather than a list. Increases usability in my opinion. BuT wHeRe'S tHe LoOm ViDeO?!

All I can say is: It's good to be a manager!


Integrate livecheckables into formulae

Contributing to homebrew-xorg:
You can erase any parts of this template not applicable to your Pull Request.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

The brew livecheck command will be migrated from Homebrew/homebrew-livecheck into Homebrew/brew in the not-too-distant future and we will be removing the Formulary extension that enables the use of files in a Livecheckables folder in the process.
The reason for this is that livecheckables will be integrated into formulae as a livecheck block. The current livecheck block format in livecheckables is a half-step in between. Livecheck has supported livecheck blocks in formulae for some time (and favors it over a livecheckable file) but we haven't yet migrated livecheckables in homebrew-livecheck to homebrew-core formulae as we need to take care of some other things first. [We're currently bringing existing livecheckables (namely, the older ones) up to existing standards before the migration.]
With all this in mind, there's no reason not to integrate the livecheckables in this repository into their corresponding formulae. Doing this now will prevent them from breaking after the Homebrew/brew migration, so I thought I would take a moment to take care of this.
Besides that, I also modified the regex calls to always use parentheses, since that's what we've standardized on for technical reasons.
I've confirmed that all checks for this tap work exactly the same both before and after these changes. Anything that worked before continues to work and anything that was broken is still broken (in the same manner).

Thank you, Sam! Excellent contribution -- much appreciated!