the idf.py monitor baudrate setting in sdkconfig has no effect or is ignored (IDFGH-7120)

Environment

Development Kit:      [ESP32-Wrover-Kit|ESP32-DevKitC|ESP32-PICO-Kit|ESP32-LyraT|ESP32-LyraTD-MSC|none]
Kit version (for WroverKit/PicoKit/DevKitC): [v1|v2|v3|v4]
Module or chip used:  [ESP32-WROOM-32|ESP32-WROOM-32D|ESP32-WROOM-32U|ESP32-WROVER|ESP32-WROVER-I|ESP32-WROVER-B|ESP32-WROVER-IB|ESP32-SOLO-1|ESP32-PICO-D4|ESP32]
IDF version : v4.4-c29343eb94d2f2ca17b3a5b38c82452e556147f2
Build System:         idf.py
OS: Linux
Using an IDE?: Yes (VSCODE IDF PLUGIN]
Power Supply:      external 3.3V

Problem Description
setting the idf.py monitor baudrate in sdkconfig has to effect. All entries still cause the serial output to be at 115200. So even if I choose 921600bps, the output remains at 115200. If I use an external monitor that I set to 115200, I can see the output normally. But when launching the idf.py monitor, since it expects 921600, all I get is junk. There is absolutely nothing in my code that is modifying the baudrate or touching the uart in any way. I only use ESP_LOG and printf functions. I never set any environment variables that would change the baudrate. MONITORBAUD is not set. It seems the chip doesn't respect this sdkconfig entry and ignores it.

I'm setting CONFIG_ESPTOOLPY_MONITOR_BAUD to 921600. But this is not having an effect. When I open any serial console @115200, it works fine. When I do so with @921600, I see jibberish. So when idf.py tries to open the monitor @921600, I see jibberish. I don't understand why setting CONFIG_ESPTOOLPY_MONITOR_BAUD is being ignored by the esp chip/app/uart (while idf.py monitor correctly opens in 921600).
However, CONFIG_ESP_CONSOLE_UART_BAUDRATE is set to 115200 in my sdkconfig, even though I never set it anywhere in menuconfig. In menuconfig, under "serial flasher config->idf.py monitor baud rate" I'm choosing "921600". Thus the variable CONFIG_ESPTOOLPY_MONITOR_BAUD is correctly being set to 921600, but when I inspect the sdkconfig file itself, I realize CONFIG_ESP_CONSOLE_UART_BAUDRATE is set to 115200, even though I never chose this. Could this be the source of the problem? I'm going to test it right now.

@dobairoland
I just realized, CONFIG_ESP_CONSOLE_UART_BAUDRATE is automatically being set to 115200 in the sdkconfig file everytime I flash the application. Even if I delete it or comment it out, once I hit the flash button, the file gets instantly modified and it reappears. So i have no way to test things with this option off. Is there a logical reason for this?

I don't understand why setting CONFIG_ESPTOOLPY_MONITOR_BAUD is being ignored by the esp chip/app/uart

Because changing the monitor baud rate doesn't imply or change the console baud rate.

So I think the solution for your problem is to set the monitor baud rate to follow the console baud rate; and change the desired baud rate for the console only.
This is the default behavior for ESP-IDF v5.0. You will not have to set it there.

First, you have to set custom UART. Then it will appear. If you don't enable it then custom baud-rate is hidden in the menu (if you set it manually then it will ignore it).

@dobairoland
I tried that... that only affects CONFIG_ESPTOOLPY_MONITOR_BAUD. It doesn't change CONFIG_ESP_CONSOLE_UART_BAUDRATE. What I need is a way to persistently change CONFIG_ESP_CONSOLE_UART_BAUDRATE. What exactly is changing it back to 115200 on every flash?

CONFIG_ESP_CONSOLE_UART_CUSTOM=y
CONFIG_ESP_CONSOLE_UART_BAUDRATE=921600

What exactly is changing it back to 115200 on every flash?

... is what I mentioned earlier. If you don't set custom UART then reconfiguration will ignore the baud-rate change.

@dobairoland that gives an error. the build system doesn't accept when I define it manually. it just overwrites both lines

there must be some other option that has to be set first to allow CONFIG_ESP_CONSOLE_UART_CUSTOM to be set to "y".

@dobairoland
can you please tell me the exact path from the top of menuconfig do I have to navigate to reach the option that allows me to set this from menuconfig? because doing so directly in the sdkconfig file.... just to have it throw errors in the menuconfig window, then overwrite stuff, then allow it strangely to work, is ofcourse not a systematic solution.

"Component config" -> "ESP system settings" -> "Channel for console output (Default: UART0)"

only then do submenu options appear that let you keep or change the uart number, its pins, and also set its output baudrate.

Yes, that is what I was trying to tell you. I'm sorry if it wasn't clear enough.


Add Microsoft FeatureManagement Documentation

There's a Mircosoft FeatureManagement provider but it doesn't have documentation. Without docs, it's difficult for new users to learn how the provider works. A readme should be created under /src/OpenFeature.Contrib.Providers.FeatureManagement that explains how the add the dependency to the project, how to use it in openfeature, and any limitations or gotchas that a user may encounter. Once the docs have been updated, this provider can be added to the OpenFeature ecosystem page.

Hi @ericpattison, would you be willing to write this doc?

At first glance its not clear if the provider wraps the Feature management for access through the OpenFeature SDK API or does it operate in the reverse, enable access to OpenFeature backends through FeatureManagment IConfiguration - it looks more like the  former, but it feels like the latter would be more desirable since its a native .NET feature. This is where documentation is required to at the very least provide an overview of what exactly this does.

@beeme1mr I'll set aside some time to work on the documentation.
@theperm I can understand the confusion. This implementation is to allow FeatureManagement to be a provider to OpenFeature.
I agree that a configuration source/provider for FeatureManagement to fetch information from OpenFeature would be great, but I'm personally not sure if this repo would be the best place for that (maintainers, please feel free to correct me if you disagree).
There are some challenges that would have to be addressed in order to safely provide that configuration source though, for example configuration providers are synchronous IO only, and are typically only loaded once and held in memory unless you can signal a reload mechanism.
All that said, I wouldn't mind finding time to put that together.

Ok i see... I'm not sure that approach would be popular but I'm new to OpenFeature so still mulling it over in this respect. I guess if using Azure App configuration it would provide a live configuration, but to use OpenFeature on top of FM/appsettings.cs doesnt feel the way i would want to develop a dotnet app. Using dotnet FeatureManagement as an abstraction to openfeature feels more natural since its native .net but it would also open up easy access to all the OpenFeature provider backends into the .net FeatureManagment through a single provider using IFeatureDefinitionProvider. This i think would be a better proposition. This would reduce the amount of custom providers people would have to create in .Net for all the feature flag backends out there. Food for thought.


How should I contribute Locale Information Constants needed in winnls module

I need to refer to some of the Locale Information Constants which are not currently in the crate, and might as well commit them for others to use.
What file should I commit these to?

They're defined in um\WinNls.h so the equivalent Rust bindings would go into um::winnls

I have the same issue and was about to post the following until I saw this. Including here just so you have a little more info on locale constants that would be useful...
Hello. I have a crate (num-format) that interacts with the Windows API and
winapi has been super helpful! Thank you.
That said, winapi seems to be missing a few constants that I need for my
crate; so I'm currently using bindgen and a build.rs file to pull in
the values I need that winapi doesn't currently support.
Would it be possible to add to winapi the constants listed in the links below?
That way I can drop my dependency on bindgen, which is a bit of a pain on Windows,
as you're probably aware, because of it's dependency on Clang.
It'd be great if you could include all the constants listed in the links below, but
in case that's too much I've included underneath each link the ones I'm currently
using that are not yet available in winapi.
Locale name constants

LOCALE_NAME_SYSTEM_DEFAULT

Locale information constants

LOCALE_SDECIMAL
LOCALE_SGROUPING
LOCALE_SNAME
LOCALE_SNAN
LOCALE_SNEGATIVESIGN
LOCALE_SNEGINFINITY
LOCALE_SPOSINFINITY
LOCALE_SPOSITIVESIGN
LOCALE_STHOUSAND


Return proper errors for exec failure

This is only to help debugging the exec errors because they correct
error message is not being returned or is being hidden from the client.
ref: #17473
Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

LGTM


Fix double extension with directories

when inputting a directory to waifu2x the output images would have 2 file extensions, for example "picture.png" -> "picture.png.png". On line 646 changing
path_t output_filename2 = filename + PATHSTR('.') + format;
to
path_t output_filename2 = filename_noext + PATHSTR('.') + format;
fixes the glitch

The duplicated extension issue has been already resolved in the latest code. This change is not needed. Thanks anyway.


Define core APIs and views for cards

Objective
Prepare card model and component for when we'll extract features as discoverable extension components.
Steps and guidelines
See #94, #96, #98 for detailled issues.
Card model (aka DataCard)

Distinguish, in the code, properties essential to a card from properties belonging to features
A card model shouldn't know anything about its parents or feature extensions

Remove any reference to parents
Move any method using a reference to a parent higher in the hierarchy
Distinguish methods essential to the card from methods belonging to features

If a method uses more than data accessible from self, or settable to self, move it to the associated component

Of course, if you move methods, fix all callers.
Card component
The card component manages a card model and its features. It provide an API to card views and parent components. It knows nothing about persistence, has no reference to its parents, and preferably doesn't fiddle with subcomponents of its children.

Remove any reference to parents. If the component needs to communicate with its parents, use answer() and/or return values from API called by a parent. If it needs info from its parent, use method calls/callbacks or parameters on its contructor, or return value of comp.answer().
Distinguish, in the code, methods and properties essential to card management from those belonging to features.
Move any database querying to the card model.
Try to handle components for features "anonymously", that is, in a generic way (see also view).

Card view

Separate the core views of a card from the rendering of features
Since we are now handling features as "anonymous" components, we should approach their views in a generic way. For each feature, define and handle views 'header', 'cover', 'badge', 'action' and a default view (for full card display).

Working on this.

#138, #126


PS frontend will crash the UE project if max bitrate is set lower than min bitrate

**UE Version: **
5.2
**Frontend Version: **
5.2
Problem component
Frontend
Description
Pixel Streaming frontend will crash UE project if max bitrate is set lower than min bitrate. Repro rate 100%. Steps to repro:

Start a PS-enabled UE project with local arguments
Run the SS
Connect to localhost
Open frontend settings and enter a max bit rate value that is lower than the min bit rate
Restart the stream
Observe the crash error as the project underneath PS dies

Note that signalling server doesn't actually die, so the application can be restarted and it will run normally.
Expected behavior
Frontend should able to handle this scenario whether the user changes it in the configuration menu, or adds the parameters to the URL or send the message directly.
Screenshots

Platform (please complete the following information):

Windows 10 Pro
Chrome

This is an application side issue that will be addressed there.


[Showcase Submission]

https://gist.github.com/camjocotem/cc3f9baecd324026931ae9544e1aaf62
Remove promoted tweets from your twitter feed! :D

Thanks! Just added this to the "Code Samples" category!


412 enhancement add a login modal to select pod provider

This PR:
Resolves #412
1.  Replaces basic text field for one with autocomplete (a dropdown appears with recommended options) in the OidcLoginComponent.
2. Adds SUGGESTED_OIDC_OPTIONS constant; a set of recommended pod servers.
Screenshots:

Future Steps/PRs Needed to Finish This Work:

The SUGGESTED_OIDC_OPTIONS has placeholder options in it, for now, that should be replaced.

The UI for the component was based on the design of Pod Pro's design. The one I made ended up being more heavy-duty than theirs because I was using MUI's Auto Complete component, which is more bulky by default. We could slim it down if needed. I started on a version that looked more like theirs, here was the result:

Pod Pro's Design:

My Attempt at a similar design:

The code I used to achieve that (not part of this PR):
<Autocomplete
        // ...
        PaperComponent={({ children }) => (
          <Box
            sx={{
              bgcolor: 'black',
              opacity: '0.8',
              fontSize: '12px',
              width: 'max-content',
              transform: 'translateX(15%) translateY(8px)'
            }}
          >
            {children}
          </Box>
        )}
        // ...
      />

One last idea I had was to make the component expand to be wider when selected, similar to This. This could keep the UI clean, while also accommodating potentially long URLs in the dropdown. I tried incorporating this myself but ended up giving up... I don't have much experience using MUI, but if someone else does, I imagine it wouldn't be too difficult.

Hey, @timbot1789! I made some changes based on your suggestions, let me know what you think...
I also added some comments to explain my thinking. I'm still learning and I wanna make sure that I'm following best practices and not breaking things! Don't hesitate to let me know if I need to make more changes.

Code itself looks good. However, it seems that we've left this linger too long and we have MERGE CONFLICTS. We'll need to resolve those, then we're good to merge.

I could help with the clean-up if needed, let me know here or on Discord @rioredwards

Code itself looks good. However, it seems that we've left this linger too long and we have MERGE CONFLICTS. We'll need to resolve those, then we're good to merge.

I could help with the clean-up if needed, let me know here or on Discord @rioredwards

Sounds good, I'll send you a message on Discord

@rioredwards you're good to merge this yourself once all the git checks have passed


Create Deferred type classes

I have wrapped my Deferreds in 2 functions:
'resolve' => GraphQLProxy::deferredMany(ReservationPlayer::class, 'reservation_id'), # $root to many: $building->floors
'resolve' => GraphQLProxy::deferredOne(Resource::class, 'resource_id'), # $root to one: $building->reception

It's the only 2 I've needed so far, but I can imagine many more kinds of Deferred loading.
It'd be very nice to create a Deferred class, and use it to store the queue and resolver. So instead of a Deferred object with a closure that returns a closure etc, it's just a single object that contains everything (for that specific field).
In my case, that would be
'resolve' => new CustomDeferredMany(ReservationPlayer::class, 'reservation_id'),
'resolve' => new CustomDeferredOne(Resource::class, 'resource_id'),

The default/provided would be the same as currently:
'resolve' => new CallbackDeferred(function() {
  // Return closures in closures
});

No need for static magic, or closures in closures. All the logic in a nice class. With some refactoring, it could be backward compatible by making Deferred a specific of the (new) DeferredInterface.
I don't understand PHP Promises, so I can't make a PR, but I still wanted to mention it. There are very few Deferred usages, so it might be doable... Or maybe I'm talking nonsense. Let me know.
(Deferred might have few usages, but calling a field's resolver might have many.)

But can't you already do the same using __invoke for such classes? A resolver is basically any callable, so you can wrap it as you want. Or am I missing something?

If __invoke is good enough for the graphql lib, that might be good enough for me. That depends on how callability is checked everywhere. You know that, I haven't checked.
I'm gonna try it. Be right back.

Yes. That works perfectly! Thanks.


expr is failing with multibyte chars

It causes https://github.com/coreutils/coreutils/blob/master/tests/misc/expr-multibyte.pl to fail
$ ./target/debug/coreutils expr length αbcdef
7

GNU:
$ expr length αbcdef
6

needs to have a different locale compiled like
sudo locale-gen fr_FR.UTF-8

Yeah, I am working on a fix :)

Actually, my patch was wrong, it should take in account the locale
$ LANG=C expr length αbcdef
7
$ LANG=fr_FR.UTF-8 expr length αbcdef
6

seems that we should use MB_CUR_MAX to see the number of bytes


Sync with android phone

This would be perfect if I could see and edit the same tasks on my phone.
A way to export this so that it can be imported into a todo.txt compatible app better still would be an app for this application.

This would be perfect if I could see and edit the same tasks on my phone.
I don't know how this could work but sounds good. :+1:

A way to export this so that it can be imported into a todo.txt compatible app better still would be an app for this application.
I am trying to export tasks data as a raw file. but the problem is that storage file is JSON format. So that anybody converts that for to any formatted file. (e.g: csv, pdf, image).

This seems to require some sort of infrastructure / service to back it. It
would take taskbook from a simple console app to another level.
Also could be related to #45
On Sat, Aug 11, 2018, 11:42 PM Joydip Roy<EMAIL_ADDRESS>wrote:

This would be perfect if I could see and edit the same tasks on my phone.
I don't know how this could work but sounds good. 👍
A way to export this so that it can be imported into a todo.txt compatible
app better still would be an app for this application.
I am trying to export tasks data as a raw file. but the problem is that
storage file is JSON format. So that anybody converts that for to any
formatted file. (e.g: csv, pdf, image).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/klauscfhq/taskbook/issues/78#issuecomment-412318353,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVkotgxU_1iKz0ZWar-s1glFXsv3bR_Pks5uP7IogaJpZM4V5S-J
.

--
K. Alex Mills

So although something like this seems great to have I agree with @kalexmills that it does seem to change taskbook to something much more than just a simple cli app. There are ways you can actually do this now if you were willing to go through some setup. First you have to handle syncing. This can be done by editing your taskbook config to save the data into a directory you back up with something like dropbox or google drive. Then you have to sync that directory to your phone. Second you need to install a terminal app like Termux on your android phone and use that to setup taskbook there as well. This whole setup is not ideal but it does function as a workaround.
If you do decide to setup taskbook on your phone in Termux you will probably need to follow a fix mentioned in this npm issue (https://github.com/npm/npm/issues/19265) to be able to globally install things in npm.

Thank you for the reply and advice. Perhaps someone more adept at programming than I might consider creating an android app that would sync through Dropbox or Google Drive.

Hey, i created a fork of the taskbook project and started to continue development. I implemented a duedate functionality and the possibility to use google firestore to sync task across all devices. Maybe you want to have a look.
I also started to develop an app with flutter to use taskbook also on the way, but thats in an early phase.
https://github.com/perryrh0dan/taskline

Since this is a strongly Dev oriented project... It would not be easier instruct the user to save the local Taskbook file in a Git server (GitHub or GitLab for sure) and then build an app that just download the file from that repo and print it beautifully in a mobile screen?


Manytomanythrough fix and failling test for #1133

fix and failling test for https://github.com/balderdashy/waterline/issues/1133

Failing??

@weyert this test and fix require https://github.com/balderdashy/waterline-schema/pull/30

Alright @atiertant everything looks good in master and all tests are passing. I cherry picked these commits into the 0.10.x stable branch and went ahead and published 0.10.28 to npm.
Thanks again for all your hard work with this! The next thing we need to do is update the docs for through with a better explaination of where they stand as of now. Then I would like to look into @devinivy's issue with lifecycle callbacks on through tables.

Brilliant work!

Awesome stuff, congrats @atiertant :clap:


Documentation: pico_rgb_keypad, Readme.md, get_button_states

changed_buttons = current_buttons ^ last_buttons
...
pressed_buttons = current_buttons & changed

should read -

pressed_buttons = current_buttons & changed_buttons
...
released_buttons =  last_buttons & changed

should read -

released_buttons =  last_buttons & changed_buttons

Fix inbound. Good catch, thank you!


Module not found while using storybook

Bug Report
Description
Getting
Module not found: Error: [CaseSensitivePathsPlugin] `/Users/xxx/yyy/webapp/src/components/github/GithubModal.js` does not match the corresponding path on disk `Github`.
Details
I'm having some issues with specific paths while using storybook.
The React (v16) app works well, but the storybook throughs  Module not found: Error: [CaseSensitivePathsPlugin] on the path:

/Users/xxx/YYY/webapp/src/components/github/GithubModal.js

Two things to keep in mind:

when I copy paste the path to a browser's url the file is there.
In the path the YYY part has a dot in it, i.e aaa.bbb
The React app is working
Storybook works on other machines (High Sierra)

Versions

Webpack: 3.11.0
OSX El Capitan 10.11.6
React 16.3.1
Storybook/react: 3.4.4
case-sensitive-paths-webpack-plugin: 2.1.2 (from storybook's packages.json)

Hey there,
What is the exact import or require statement? Does it require github or Github? And does that match what is on the disk?
Some users have reported problems where a case has changed on one machine and supposedly committed, but Git didn't pick up on it, so on other machines the casing of the require statement and file on disk is inconsistent.

@bnbarak I'm still waiting on more information, I can't help you without knowing what is being required and whether or not the file reported in the console actually matches the file casing on disk.

Sorry for the delay. A week latter I updated libraries and it got solved.
Thank you!


Added security analytics dashboards.

Signed-off-by: AWSHurneyt<EMAIL_ADDRESS>Description
Added security analytics dashboards.
Issues Resolved
[List any issues this PR will resolve]
Check List

[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.

Closing in favor of https://github.com/opensearch-project/opensearch-dashboards-functional-test/pull/382


InteractiveAuto

Hi,
Im using the .net 8 Blazor Web App template with rendermode InteractiveAuto applied globally.
When running i get the error:   Microsoft.JSInterop.JSException: 'There are multiple .NET runtimes present, so a default dispatcher could not be resolved. Use DotNetObject to invoke .NET instance methods.
I tried the same Webapp template, the same rendermode but applied per page/component.
I made a page with a chart in the server project (rendermode = server) and one in the client project(rendermode = WebAssembly).
Both pages are giving the same error if i open the other first. So
open server side, than open client side => error
or
open client side, then open serverside => error
Microsoft.JSInterop.JSException
  HResult=0x80131500
  Message=There are multiple .NET runtimes present, so a default dispatcher could not be resolved. Use DotNetObject to invoke .NET instance methods.
Error: There are multiple .NET runtimes present, so a default dispatcher could not be resolved. Use DotNetObject to invoke .NET instance methods.
    at v (https://localhost:44307/_framework/blazor.web.js:1:2037)
    at e.invokeMethodAsync (https://localhost:44307/_framework/blazor.web.js:1:2428)
    at Object.lightweightChartsInvoke (https://localhost:44307/_content/LightweightCharts.Blazor/lightweight-charts.scripts.js:19:45)
    at https://localhost:44307/_framework/blazor.web.js:1:3244
    at new Promise (<anonymous>)
    at y.beginInvokeJSFromDotNet (https://localhost:44307/_framework/blazor.web.js:1:3201)
    at fn._invokeClientMethod (https://localhost:44307/_framework/blazor.web.js:1:62541)
    at fn._processIncomingData (https://localhost:44307/_framework/blazor.web.js:1:60016)
    at connection.onreceive (https://localhost:44307/_framework/blazor.web.js:1:53657)
    at i.onmessage (https://localhost:44307/_framework/blazor.web.js:1:81802)
  Source=System.Private.CoreLib
  StackTrace:
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at System.Runtime.CompilerServices.ValueTaskAwaiter`1.GetResult()
   at Microsoft.JSInterop.JSRuntime.<InvokeAsync>d__16`1.MoveNext()
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at System.Runtime.CompilerServices.ValueTaskAwaiter`1.GetResult()
   at LightweightCharts.Blazor.Charts.ChartComponent.<JavascriptInvokeAsync>d__53`1.MoveNext() in C:\Projects\GSL.CryptoHunter\LightweightCharts.Blazor\Charts\ChartComponent.cs:line 436
   at LightweightCharts.Blazor.Charts.ChartComponent.<Options>d__38.MoveNext() in C:\Projects\GSL.CryptoHunter\LightweightCharts.Blazor\Charts\ChartComponent.cs:line 287
   at BlazorApp1.Components.Pages.CandlestickSeries.<InitializeChartComponent>d__13.MoveNext() in C:\Projects\GSL.CryptoHunter\BlazorApp1\BlazorApp1\Components\Pages\CandlestickSeries.razor.cs:line 96

Regards,
Glenn

I posted the problem also in Microsoft's GitHub and it seems you need to adapt your library to support the new interactive auto mode. See https://github.com/dotnet/aspnetcore/issues/53330

this seems to be the line  (inside lightweight-charts.scripts.js) that goes wrong:
result.UniqueJavascriptId = await DotNet.invokeMethodAsync('LightweightCharts.Blazor', 'GenerateGuidForJavascript');

Hello,
Thanks for the fix,
I've changed that line that was using the DotNet member with a function from those linked by you.
Also, I've updated the sources and build a new package for the latest version 4.1.2 (this fix is included).


Support us territories

This PR updates United States specific queries so the results include US territories.

This change is

statistics/queries/us_census_tracts_asn_histogram.sql, line 306 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
This should be left as asn to match the field name in the output path template. It can be changed in the above parts of the query for clarity, as long as it is renamed to asn in the last step.

will change

statistics/queries/us_census_tracts_histogram.sql, line 55 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
I don't fully understand this part (probably because I'm missing something about the underlying data). I thought we had added this filter to deal with rows not having a Subdivision1ISOCode nor a Region -- doesn't this change mean they will be included again?
This comment also applies to other queries in this PR.

The change is ok because we've added a CASE statement when selecting CountryCode - Subdivision1ISOCode, so no null or empty values should be in the result set. I've run the tracts query as a test. There is still one tract where the resulting ISO code is "US-" but I think this is likely an annotation error, not an issue with the query.

statistics/queries/us_county_asn_histogram.sql, line 262 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Same as above re. ASNumber vs asn

ack

statistics/queries/us_state_territories_asn_histogram.sql, line 1 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Nit: this file has a mix of tabs and spaces.

Will correct.

statistics/queries/us_state_territories_asn_histogram.sql, line 274 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
ASNumber -> asn

ack

statistics/queries/us_state_territories_histogram.sql, line 1 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Nit: mixed tabs and spaces

ack

@robertodauria latest commit and comment addresses your comments. PTAL?

@robertodauria https://github.com/m-lab/stats-pipeline/pull/58/commits/e70cb7c9ecda9e662e530d75a364c82a52825398 adds paths to config.json and exporter queries for us_states. PTAL?

Thanks @robertodauria Latest commit corrects those misspellings.


add issue template

for effective co-operation we need issue templates

The existing issue template still have bugs(e.g. links, contribution guide). We should modify the issue template and have a contribution guide.

With more contributors in this community, while most of them are new to git, we need to introduce "How to make a good PR" in the issue template.
You can refer to (Git commits历史是如何做到如此清爽的？ - 知乎
https://www.zhihu.com/question/61283395)

See this https://github.com/stevemao/github-issue-templates


Trying to add a custom End-effector to an UR10e

Config

Ubuntu 22.04 Jammy
Ros HUMBLE
gazebo 11.10.2

Context
I've try last few days to put a customized End-effector (EE) to a UR10e (Visual + collision), so I can see it and work with it on gazebo and rviz (with moveit). However, I did not find lots of documentation on how to do it unfortunatly ...
What I did
I've add the EE corresponding .stl and .dae in /sr_description/meshes/ur_10e/collision/EE_v3_1.stl and /ur_description/meshes/ur10e/visual/EE_v3_1.dae.
Then, I edited the ur_macro.xacro as following :
<link name="${tf_prefix}tool0">
<xacro:get_visual_params name="tool0" type="visual_offset"/>
  <visual>
    <origin xyz="0 0 ${visual_params}" rpy="0 0 0"/>
    <geometry>
      <xacro:get_mesh name="tool0" type="visual"/>
    </geometry>
  </visual>
  <collision>
    <origin xyz="0 0 ${visual_params}" rpy="0 0 0"/>
    <geometry>
      <xacro:get_mesh name="tool0" type="collision"/>
    </geometry>
  </collision>
</link>

And also add in the visual_parameters.yaml file :
tool0:
      visual:
        mesh:
          package: sr_description
          path: meshes/ur10e/visual/EE_v3_1.dae
      collision:
        mesh:
          package: sr_description
          path: meshes/ur10e/collision/EE_v3_1.stl
      visual_offset: 0.0

(with the correct indentation so that the .xml file is well parsed)
After colcon building the project, I can now run the following command :
ros2 launch sr_simulation_gazebo sr_sim_moveit.launch.py

(Note that this is sr_ ... and not ur_... but this is just a copy / colly from ur_simulation_gazebo and ur_description github with a different name)
Bug
Gazebo is launching (slower than usual but still okay), however rviz is crashing or I need to wait several minutes to let it load. If I do so, I get a warn in motion planning : "Requested initial scene failed" as shown  below

Furthermore, I have the following bash :
ros2 launch sr_simulation_gazebo sr_sim_moveit.launch.py
[INFO] [launch]: All log files can be found below /home/luca/.ros/log/2024-10-29-10-35-46-452416-luca-TravelMate-TCO-123339
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [robot_state_publisher-1]: process started with pid [123347]
[INFO] [spawner-2]: process started with pid [123349]
[INFO] [spawner-3]: process started with pid [123351]
[INFO] [gzserver-4]: process started with pid [123353]
[INFO] [gzclient-5]: process started with pid [123355]
[INFO] [spawn_entity.py-6]: process started with pid [123358]
[INFO] [move_group-7]: process started with pid [123360]
[INFO] [rviz2-8]: process started with pid [123362]
[INFO] [servo_node_main-9]: process started with pid [123364]
[robot_state_publisher-1] [INFO] [1730194547.7216amazing13363] [robot_state_publisher]: got segment SR_table
[robot_state_publisher-1] [INFO] [1730194547.721688954] [robot_state_publisher]: got segment base
[robot_state_publisher-1] [INFO] [1730194547.721695454] [robot_state_publisher]: got segment base_link
[robot_state_publisher-1] [INFO] [1730194547.721699141] [robot_state_publisher]: got segment base_link_inertia
[robot_state_publisher-1] [INFO] [1730194547.721702850] [robot_state_publisher]: got segment flange
[robot_state_publisher-1] [INFO] [1730194547.721706217] [robot_state_publisher]: got segment forearm_link
[robot_state_publisher-1] [INFO] [1730194547.721709518] [robot_state_publisher]: got segment ft_frame
[robot_state_publisher-1] [INFO] [1730194547.721712849] [robot_state_publisher]: got segment shoulder_link
[robot_state_publisher-1] [INFO] [1730194547.721716519] [robot_state_publisher]: got segment tool0
[robot_state_publisher-1] [INFO] [1730194547.721719971] [robot_state_publisher]: got segment upper_arm_link
[robot_state_publisher-1] [INFO] [1730194547.721723312] [robot_state_publisher]: got segment world
[robot_state_publisher-1] [INFO] [1730194547.721726576] [robot_state_publisher]: got segment wrist_1_link
[robot_state_publisher-1] [INFO] [1730194547.721730127] [robot_state_publisher]: got segment wrist_2_link
[robot_state_publisher-1] [INFO] [1730194547.721733492] [robot_state_publisher]: got segment wrist_3_link
[rviz2-8] Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
[move_group-7] [WARN] [1730194547.755276763] [move_group.move_group]: Falling back to using the the move_group node namespace (deprecated behavior).
[move_group-7] [INFO] [1730194547.757609740] [moveit_rdf_loader.rdf_loader]: Loaded robot model in 0 seconds
[move_group-7] [INFO] [1730194547.757653381] [moveit_robot_model.robot_model]: Loading robot model 'ur'...
[move_group-7] [INFO] [1730194547.757665770] [moveit_robot_model.robot_model]: No root/virtual joint specified in SRDF. Assuming fixed joint
[servo_node_main-9] [WARN] [1730194547.757591813] [moveit_servo.servo_node]: Intra-process communication is disabled, consider enabling it by adding:
[servo_node_main-9] extra_arguments=[{'use_intra_process_comms' : True}]
[servo_node_main-9] to the Servo composable node in the launch file
[servo_node_main-9] [INFO] [1730194547.761875754] [moveit_rdf_loader.rdf_loader]: Loaded robot model in 0.00275101 seconds
[servo_node_main-9] [INFO] [1730194547.761920638] [moveit_robot_model.robot_model]: Loading robot model 'ur'...
[servo_node_main-9] [INFO] [1730194547.761932022] [moveit_robot_model.robot_model]: No root/virtual joint specified in SRDF. Assuming fixed joint
[rviz2-8] [INFO] [1730194548.108427204] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-8] [INFO] [1730194548.108556058] [rviz2]: OpenGl version: 4.6 (GLSL 4.6)
[rviz2-8] [INFO] [1730194548.132266617] [rviz2]: Stereo is NOT SUPPORTED
[spawner-3] [INFO] [1730194548.145574164] [spawner_joint_trajectory_controller]: waiting for service /controller_manager/list_controllers to become available...
[spawner-2] [INFO] [1730194548.147533200] [spawner_joint_state_broadcaster]: waiting for service /controller_manager/list_controllers to become available...
[rviz2-8] Warning: class_loader.impl: SEVERE WARNING!!! A namespace collision has occurred with plugin factory for class rviz_default_plugins::displays::InteractiveMarkerDisplay. New factory will OVERWRITE existing one. This situation occurs when libraries containing plugins are directly linked against an executable (the one running right now generating this message). Please separate plugins out into their own library or just don't link against the library and use either class_loader::ClassLoader/MultiLibraryClassLoader to open.
[rviz2-8]          at line 253 in /opt/ros/humble/include/class_loader/class_loader/class_loader_core.hpp
[spawn_entity.py-6] [INFO] [1730194548.307289372] [spawn_ur]: Spawn Entity started
[spawn_entity.py-6] [INFO] [1730194548.307800110] [spawn_ur]: Loading entity published on topic robot_description
[spawn_entity.py-6] /opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/qos.py:307: UserWarning: DurabilityPolicy.RMW_QOS_POLICY_DURABILITY_TRANSIENT_LOCAL is deprecated. Use DurabilityPolicy.TRANSIENT_LOCAL instead.
[spawn_entity.py-6]   warnings.warn(
[spawn_entity.py-6] [INFO] [1730194548.310045632] [spawn_ur]: Waiting for entity xml on robot_description
[spawn_entity.py-6] [INFO] [1730194548.312578253] [spawn_ur]: Waiting for service /spawn_entity, timeout = 30
[spawn_entity.py-6] [INFO] [1730194548.313029943] [spawn_ur]: Waiting for service /spawn_entity
[spawn_entity.py-6] [INFO] [1730194548.819332852] [spawn_ur]: Calling service /spawn_entity
[spawn_entity.py-6] [INFO] [1730194549.106829915] [spawn_ur]: Spawn status: SpawnEntity: Successfully spawned entity [ur]
[INFO] [spawn_entity.py-6]: process has finished cleanly [pid 123358]
[rviz2-8] [ERROR] [1730194551.245528699] [moveit_ros_visualization.motion_planning_frame]: Action server: /recognize_objects not available
[rviz2-8] [INFO] [1730194551.261844658] [moveit_ros_visualization.motion_planning_frame]: MoveGroup namespace changed: / -> . Reloading params.
[rviz2-8] [INFO] [1730194551.328723521] [moveit_rdf_loader.rdf_loader]: Loaded robot model in 0.00276092 seconds
[rviz2-8] [INFO] [1730194551.328772456] [moveit_robot_model.robot_model]: Loading robot model 'ur'...
[rviz2-8] [INFO] [1730194551.328783005] [moveit_robot_model.robot_model]: No root/virtual joint specified in SRDF. Assuming fixed joint
[servo_node_main-9] [WARN] [1730194551.738973241] [moveit_ros.robot_model_loader]: No kinematics plugins defined. Fill and load kinematics.yaml!
[gzserver-4] [INFO] [1730194552.250358931] [gazebo_ros2_control]: Loading gazebo_ros2_control plugin
[gzserver-4] [INFO] [1730194552.254035454] [gazebo_ros2_control]: Starting gazebo_ros2_control plugin in namespace: /
[gzserver-4] [INFO] [1730194552.254276157] [gazebo_ros2_control]: Starting gazebo_ros2_control plugin in ros 2 node: gazebo_ros2_control
[gzserver-4] [INFO] [1730194552.256491122] [gazebo_ros2_control]: connected to service!! robot_state_publisher
[gzserver-4] [INFO] [1730194552.259642518] [gazebo_ros2_control]: Received urdf from param server, parsing...
[gzserver-4] [INFO] [1730194552.259739614] [gazebo_ros2_control]: Loading parameter files /home/luca/ros2_ws/smart_robot/install/sr_simulation_gazebo/share/sr_simulation_gazebo/config/ur_controllers.yaml
[gzserver-4] [INFO] [1730194552.272964931] [gazebo_ros2_control]: Loading joint: shoulder_pan_joint
[gzserver-4] [INFO] [1730194552.273043536] [gazebo_ros2_control]: 	State:
[gzserver-4] [INFO] [1730194552.273062122] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273081096] [gazebo_ros2_control]: 		 found initial value: 0.000000
[gzserver-4] [INFO] [1730194552.273108146] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273123073] [gazebo_ros2_control]: 		 effort
[gzserver-4] [INFO] [1730194552.273136511] [gazebo_ros2_control]: 	Command:
[gzserver-4] [INFO] [1730194552.273148914] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273204960] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273223406] [gazebo_ros2_control]: Loading joint: shoulder_lift_joint
[gzserver-4] [INFO] [1730194552.273236933] [gazebo_ros2_control]: 	State:
[gzserver-4] [INFO] [1730194552.273249348] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273261902] [gazebo_ros2_control]: 		 found initial value: -1.570000
[gzserver-4] [INFO] [1730194552.273276766] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273289427] [gazebo_ros2_control]: 		 effort
[gzserver-4] [INFO] [1730194552.273301670] [gazebo_ros2_control]: 	Command:
[gzserver-4] [INFO] [1730194552.273314241] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273339879] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273356080] [gazebo_ros2_control]: Loading joint: elbow_joint
[gzserver-4] [INFO] [1730194552.273369216] [gazebo_ros2_control]: 	State:
[gzserver-4] [INFO] [1730194552.273381641] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273393188] [gazebo_ros2_control]: 		 found initial value: 0.000000
[gzserver-4] [INFO] [1730194552.273407155] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273420175] [gazebo_ros2_control]: 		 effort
[gzserver-4] [INFO] [1730194552.273433114] [gazebo_ros2_control]: 	Command:
[gzserver-4] [INFO] [1730194552.273445376] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273467066] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273483151] [gazebo_ros2_control]: Loading joint: wrist_1_joint
[gzserver-4] [INFO] [1730194552.273497347] [gazebo_ros2_control]: 	State:
[gzserver-4] [INFO] [1730194552.273509450] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273521458] [gazebo_ros2_control]: 		 found initial value: -1.570000
[gzserver-4] [INFO] [1730194552.273535553] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273547416] [gazebo_ros2_control]: 		 effort
[gzserver-4] [INFO] [1730194552.273559242] [gazebo_ros2_control]: 	Command:
[gzserver-4] [INFO] [1730194552.273571099] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273591643] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273607620] [gazebo_ros2_control]: Loading joint: wrist_2_joint
[gzserver-4] [INFO] [1730194552.273620476] [gazebo_ros2_control]: 	State:
[gzserver-4] [INFO] [1730194552.273632278] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273643509] [gazebo_ros2_control]: 		 found initial value: 0.000000
[gzserver-4] [INFO] [1730194552.273656559] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273668466] [gazebo_ros2_control]: 		 effort
[gzserver-4] [INFO] [1730194552.273680344] [gazebo_ros2_control]: 	Command:
[gzserver-4] [INFO] [1730194552.273692370] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273712071] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273727943] [gazebo_ros2_control]: Loading joint: wrist_3_joint
[gzserver-4] [INFO] [1730194552.273741031] [gazebo_ros2_control]: 	State:
[gzserver-4] [INFO] [1730194552.273753225] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273764183] [gazebo_ros2_control]: 		 found initial value: 0.000000
[gzserver-4] [INFO] [1730194552.273777558] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273831368] [gazebo_ros2_control]: 		 effort
[gzserver-4] [INFO] [1730194552.273847198] [gazebo_ros2_control]: 	Command:
[gzserver-4] [INFO] [1730194552.273859223] [gazebo_ros2_control]: 		 position
[gzserver-4] [INFO] [1730194552.273878985] [gazebo_ros2_control]: 		 velocity
[gzserver-4] [INFO] [1730194552.273955740] [resource_manager]: Initialize hardware 'ur'
[gzserver-4] [INFO] [1730194552.274132475] [resource_manager]: Successful initialization of hardware 'ur'
[gzserver-4] [INFO] [1730194552.274245475] [resource_manager]: 'configure' hardware 'ur'
[gzserver-4] [INFO] [1730194552.274259058] [resource_manager]: Successful 'configure' of hardware 'ur'
[gzserver-4] [INFO] [1730194552.274270915] [resource_manager]: 'activate' hardware 'ur'
[gzserver-4] [INFO] [1730194552.274279055] [resource_manager]: Successful 'activate' of hardware 'ur'
[gzserver-4] [INFO] [1730194552.274388654] [gazebo_ros2_control]: Loading controller_manager
[gzserver-4] [WARN] [1730194552.290203221] [gazebo_ros2_control]:  Desired controller update period (0.01 s) is slower than the gazebo simulation period (0.001 s).
[gzserver-4] [INFO] [1730194552.290471478] [gazebo_ros2_control]: Loaded gazebo_ros2_control.
[gzserver-4] [INFO] [1730194552.403618870] [controller_manager]: Loading controller 'joint_trajectory_controller'
[gzserver-4] [WARN] [1730194552.434430101] [joint_trajectory_controller]: [Deprecated]: "allow_nonzero_velocity_at_trajectory_end" is set to true. The default behavior will change to false.
[spawner-3] [INFO] [1730194552.444970410] [spawner_joint_trajectory_controller]: Loaded joint_trajectory_controller
[gzserver-4] [INFO] [1730194552.445901389] [controller_manager]: Configuring controller 'joint_trajectory_controller'
[gzserver-4] [INFO] [1730194552.446291106] [joint_trajectory_controller]: No specific joint names are used for command interfaces. Using 'joints' parameter.
[gzserver-4] [INFO] [1730194552.446323649] [joint_trajectory_controller]: Command interfaces are [position] and state interfaces are [position velocity].
[gzserver-4] [INFO] [1730194552.446360174] [joint_trajectory_controller]: Using 'splines' interpolation method.
[gzserver-4] [INFO] [1730194552.447271266] [joint_trajectory_controller]: Controller state will be published at 100.00 Hz.
[gzserver-4] [INFO] [1730194552.456018822] [joint_trajectory_controller]: Action status changes will be monitored at 20.00 Hz.
[gzserver-4] [INFO] [1730194552.464301009] [controller_manager]: Loading controller 'joint_state_broadcaster'
[spawner-2] [INFO] [1730194552.475020453] [spawner_joint_state_broadcaster]: Loaded joint_state_broadcaster
[gzserver-4] [INFO] [1730194552.475785316] [controller_manager]: Configuring controller 'joint_state_broadcaster'
[gzserver-4] [INFO] [1730194552.475963916] [joint_state_broadcaster]: 'joints' or 'interfaces' parameter is empty. All available state interfaces will be published
[spawner-3] [INFO] [1730194552.505662022] [spawner_joint_trajectory_controller]: Configured and activated joint_trajectory_controller
[spawner-2] [INFO] [1730194552.525479497] [spawner_joint_state_broadcaster]: Configured and activated joint_state_broadcaster
[INFO] [spawner-3]: process has finished cleanly [pid 123351]
[INFO] [spawner-2]: process has finished cleanly [pid 123349]
[move_group-7] [INFO] [1730194558.147019472] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Publishing maintained planning scene on 'monitored_planning_scene'
[move_group-7] [INFO] [1730194558.147189472] [moveit.ros_planning_interface.moveit_cpp]: Listening to 'joint_states' for joint states
[move_group-7] [INFO] [1730194558.147601364] [moveit_ros.current_state_monitor]: Listening to joint states on topic 'joint_states'
[move_group-7] [INFO] [1730194558.148015015] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Listening to '/attached_collision_object' for attached collision objects
[move_group-7] [INFO] [1730194558.148039175] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Starting planning scene monitor
[move_group-7] [INFO] [1730194558.148961968] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Listening to '/planning_scene'
[move_group-7] [INFO] [1730194558.148981904] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Starting world geometry update monitor for collision objects, attached objects, octomap updates.
[move_group-7] [INFO] [1730194558.149348762] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Listening to 'collision_object'
[move_group-7] [INFO] [1730194558.149736975] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Listening to 'planning_scene_world' for planning scene world geometry
[move_group-7] [WARN] [1730194558.150008698] [moveit.ros.occupancy_map_monitor.middleware_handle]: Resolution not specified for Octomap. Assuming resolution = 0.1 instead
[move_group-7] [ERROR] [1730194558.150024281] [moveit.ros.occupancy_map_monitor.middleware_handle]: No 3D sensor plugin(s) defined for octomap updates
[servo_node_main-9] [INFO] [1730194562.711839576] [moveit_ros.current_state_monitor]: Listening to joint states on topic '/joint_states'
[servo_node_main-9] [INFO] [1730194562.715833060] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Listening to '/attached_collision_object' for attached collision objects
[servo_node_main-9] [INFO] [1730194562.715887303] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Starting planning scene monitor
[servo_node_main-9] [INFO] [1730194562.716771804] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Listening to '/planning_scene'
[servo_node_main-9] [INFO] [1730194562.717799657] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Publishing maintained planning scene on '/servo_node/publish_planning_scene'
[rviz2-8] [INFO] [1730194565.034156259] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Starting planning scene monitor
[rviz2-8] [INFO] [1730194565.035502426] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Listening to '/monitored_planning_scene'
[servo_node_main-9] [INFO] [1730194567.719169342] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Failed to call service get_planning_scene, have you launched move_group or called psm.providePlanningSceneService()?
[servo_node_main-9] [WARN] [1730194567.739397649] [moveit_servo.servo_calcs]: No kinematics solver instantiated for group 'ur_manipulator'. Will use inverse Jacobian for servo calculations instead.
[servo_node_main-9] [WARN] [1730194567.739483289] [moveit_servo.collision_check]: Collision check rate is low, increase it in yaml file if CPU allows

If someone have a good tutorial on how adding a customized EE in ROS2, and ideally to an UR robot, would be very appreciated ! Thanks !

I find the culprit. The problem was that my End effector STL was huge (180 Mo), making everything crash ahah.
By reducing number of meshes (on MeshLab), it worked well.
However Im still searching a way to properly desable collision between 2 links .
<diseable_collision link1="" link2=""/> don t change anything.
I will close this subject.


Istiod keeps restarting due to readiness failed with statuscode 503

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
My istiod pods keep restarting.
I have installed 1.17.2 and one or two of istiod pods out of 3 pods keep restarting.
It looks initializing itself well with the following logs.

istiod bootup logs
2024-03-22T08:15:31.529191Z	info	FLAG: --caCertFile=""
2024-03-22T08:15:31.529248Z	info	FLAG: --clusterAliases="[]"
2024-03-22T08:15:31.529251Z	info	FLAG: --clusterID="Kubernetes"
2024-03-22T08:15:31.529254Z	info	FLAG: --clusterRegistriesNamespace="elb-system"
2024-03-22T08:15:31.529256Z	info	FLAG: --configDir=""
2024-03-22T08:15:31.529259Z	info	FLAG: --ctrlz_address="localhost"
2024-03-22T08:15:31.529262Z	info	FLAG: --ctrlz_port="9876"
2024-03-22T08:15:31.529264Z	info	FLAG: --domain="cluster.local"
2024-03-22T08:15:31.529267Z	info	FLAG: --grpcAddr=":15010"
2024-03-22T08:15:31.529271Z	info	FLAG: --help="false"
2024-03-22T08:15:31.529273Z	info	FLAG: --httpAddr=":8080"
2024-03-22T08:15:31.529275Z	info	FLAG: --httpsAddr=":15017"
2024-03-22T08:15:31.529279Z	info	FLAG: --keepaliveInterval="30s"
2024-03-22T08:15:31.529288Z	info	FLAG: --keepaliveMaxServerConnectionAge="30m0s"
2024-03-22T08:15:31.529291Z	info	FLAG: --keepaliveTimeout="10s"
2024-03-22T08:15:31.529293Z	info	FLAG: --kubeconfig=""
2024-03-22T08:15:31.529297Z	info	FLAG: --kubernetesApiBurst="160"
2024-03-22T08:15:31.529304Z	info	FLAG: --kubernetesApiQPS="80"
2024-03-22T08:15:31.529307Z	info	FLAG: --log_as_json="false"
2024-03-22T08:15:31.529309Z	info	FLAG: --log_caller=""
2024-03-22T08:15:31.529312Z	info	FLAG: --log_output_level="default:debug"
2024-03-22T08:15:31.529314Z	info	FLAG: --log_rotate=""
2024-03-22T08:15:31.529316Z	info	FLAG: --log_rotate_max_age="30"
2024-03-22T08:15:31.529319Z	info	FLAG: --log_rotate_max_backups="1000"
2024-03-22T08:15:31.529322Z	info	FLAG: --log_rotate_max_size="104857600"
2024-03-22T08:15:31.529325Z	info	FLAG: --log_stacktrace_level="default:none"
2024-03-22T08:15:31.529355Z	info	FLAG: --log_target="[stdout]"
2024-03-22T08:15:31.529363Z	info	FLAG: --meshConfig="./etc/istio/config/mesh"
2024-03-22T08:15:31.529366Z	info	FLAG: --monitoringAddr=":15014"
2024-03-22T08:15:31.529368Z	info	FLAG: --namespace="elb-system"
2024-03-22T08:15:31.529371Z	info	FLAG: --networksConfig="./etc/istio/config/meshNetworks"
2024-03-22T08:15:31.529374Z	info	FLAG: --profile="true"
2024-03-22T08:15:31.529380Z	info	FLAG: --registries="[Kubernetes]"
2024-03-22T08:15:31.529386Z	info	FLAG: --secureGRPCAddr=":15012"
2024-03-22T08:15:31.529389Z	info	FLAG: --shutdownDuration="10s"
2024-03-22T08:15:31.529395Z	info	FLAG: --tls-cipher-suites="[]"
2024-03-22T08:15:31.529397Z	info	FLAG: --tlsCertFile=""
2024-03-22T08:15:31.529399Z	info	FLAG: --tlsKeyFile=""
2024-03-22T08:15:31.529403Z	info	FLAG: --vklog="0"
2024-03-22T08:15:31.545929Z	info	initializing Istiod admin server
2024-03-22T08:15:31.549259Z	info	klog	Config not found: /var/run/secrets/remote/config
2024-03-22T08:15:31.549341Z	info	starting HTTP service at <IP_ADDRESS>:8080
2024-03-22T08:15:31.588512Z	info	initializing mesh configuration ./etc/istio/config/mesh
2024-03-22T08:15:31.604078Z	info	controllers	starting	controller=configmap istio-elb
2024-03-22T08:15:31.604457Z	info	Loaded MeshNetworks config from Kubernetes API server.
2024-03-22T08:15:31.604480Z	info	mesh networks configuration updated to: {

}
2024-03-22T08:15:31.608509Z	info	Loaded MeshConfig config from Kubernetes API server.
2024-03-22T08:15:31.609222Z	info	mesh configuration updated to: {
    "proxyListenPort": 15001,
    "connectTimeout": "10s",
    "protocolDetectionTimeout": "0s",
    "ingressClass": "istio",
    "ingressService": "istio-ingressgateway",
    "ingressControllerMode": "STRICT",
    "enableTracing": true,
    "accessLogFormat": "[%START_TIME%] \\\"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%\\\" %RESPONSE_CODE% %RESPONSE_FLAGS% %RESPONSE_CODE_DETAILS% %CONNECTION_TERMINATION_DETAILS% \"%UPSTREAM_TRANSPORT_FAILURE_REASON%\\\" %BYTES_RECEIVED% %BYTES_SENT% %DURATION% [%REQUEST_DURATION% %REQUEST_TX_DURATION% %RESPONSE_DURATION% %RESPONSE_TX_DURATION%] %RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% \\\"%REQ(X-FORWARDED-FOR)%\\\" \\\"%REQ(USER-AGENT)%\\\" \\\"%REQ(X-REQUEST-ID)%\\\" \\\"%REQ(:AUTHORITY)%\\\" \\\"%UPSTREAM_HOST%\\\" %UPSTREAM_CLUSTER% %UPSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_REMOTE_ADDRESS% %REQUESTED_SERVER_NAME% %ROUTE_NAME%\\n",
    "defaultConfig": {
        "configPath": "./etc/istio/proxy",
        "binaryPath": "/usr/local/bin/envoy",
        "serviceCluster": "istio-proxy",
        "drainDuration": "45s",
        "discoveryAddress": "istiod-elb.elb-system.svc:15012",
        "proxyAdminPort": 15000,
        "controlPlaneAuthPolicy": "MUTUAL_TLS",
        "statNameLength": 189,
        "concurrency": 2,
        "tracing": {
            "zipkin": {
                "address": "zipkin.elb-system:9411"
            }
        },
        "statusPort": 15020,
        "terminationDrainDuration": "5s"
    },
    "outboundTrafficPolicy": {
        "mode": "ALLOW_ANY"
    },
    "enableAutoMtls": true,
    "trustDomain": "cluster.local",
    "defaultServiceExportTo": [
        "*"
    ],
    "defaultVirtualServiceExportTo": [
        "*"
    ],
    "defaultDestinationRuleExportTo": [
        "*"
    ],
    "rootNamespace": "elb-system",
    "localityLbSetting": {
        "enabled": true
    },
    "dnsRefreshRate": "60s",
    "enablePrometheusMerge": true,
    "extensionProviders": [
        {
            "name": "prometheus",
            "prometheus": {

            }
        },
        {
            "name": "stackdriver",
            "stackdriver": {

            }
        },
        {
            "name": "envoy",
            "envoyFileAccessLog": {
                "path": "/dev/stdout"
            }
        }
    ],
    "defaultProviders": {

    },
    "discoverySelectors": [
        {
            "matchLabels": {
                "istio-discovery": "elb-services"
            }
        }
    ]
}
2024-03-22T08:15:31.620899Z	info	initializing mesh networks from mesh config watcher
2024-03-22T08:15:31.621121Z	info	mesh configuration: {
    "proxyListenPort": 15001,
    "connectTimeout": "10s",
    "protocolDetectionTimeout": "0s",
    "ingressClass": "istio",
    "ingressService": "istio-ingressgateway",
    "ingressControllerMode": "STRICT",
    "enableTracing": true,
    "accessLogFormat": "[%START_TIME%] \\\"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%\\\" %RESPONSE_CODE% %RESPONSE_FLAGS% %RESPONSE_CODE_DETAILS% %CONNECTION_TERMINATION_DETAILS% \"%UPSTREAM_TRANSPORT_FAILURE_REASON%\\\" %BYTES_RECEIVED% %BYTES_SENT% %DURATION% [%REQUEST_DURATION% %REQUEST_TX_DURATION% %RESPONSE_DURATION% %RESPONSE_TX_DURATION%] %RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% \\\"%REQ(X-FORWARDED-FOR)%\\\" \\\"%REQ(USER-AGENT)%\\\" \\\"%REQ(X-REQUEST-ID)%\\\" \\\"%REQ(:AUTHORITY)%\\\" \\\"%UPSTREAM_HOST%\\\" %UPSTREAM_CLUSTER% %UPSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_REMOTE_ADDRESS% %REQUESTED_SERVER_NAME% %ROUTE_NAME%\\n",
    "defaultConfig": {
        "configPath": "./etc/istio/proxy",
        "binaryPath": "/usr/local/bin/envoy",
        "serviceCluster": "istio-proxy",
        "drainDuration": "45s",
        "discoveryAddress": "istiod-elb.elb-system.svc:15012",
        "proxyAdminPort": 15000,
        "controlPlaneAuthPolicy": "MUTUAL_TLS",
        "statNameLength": 189,
        "concurrency": 2,
        "tracing": {
            "zipkin": {
                "address": "zipkin.elb-system:9411"
            }
        },
        "statusPort": 15020,
        "terminationDrainDuration": "5s"
    },
    "outboundTrafficPolicy": {
        "mode": "ALLOW_ANY"
    },
    "enableAutoMtls": true,
    "trustDomain": "cluster.local",
    "defaultServiceExportTo": [
        "*"
    ],
    "defaultVirtualServiceExportTo": [
        "*"
    ],
    "defaultDestinationRuleExportTo": [
        "*"
    ],
    "rootNamespace": "elb-system",
    "localityLbSetting": {
        "enabled": true
    },
    "dnsRefreshRate": "60s",
    "enablePrometheusMerge": true,
    "extensionProviders": [
        {
            "name": "prometheus",
            "prometheus": {

            }
        },
        {
            "name": "stackdriver",
            "stackdriver": {

            }
        },
        {
            "name": "envoy",
            "envoyFileAccessLog": {
                "path": "/dev/stdout"
            }
        }
    ],
    "defaultProviders": {

    },
    "discoverySelectors": [
        {
            "matchLabels": {
                "istio-discovery": "elb-services"
            }
        }
    ]
}
2024-03-22T08:15:31.621136Z	info	version: 1.17.2-3e857775086a061d12ee445f32a0b35ea17c8488-Clean
2024-03-22T08:15:31.621407Z	info	flags: {
   "ServerOptions": {
      "HTTPAddr": ":8080",
      "HTTPSAddr": ":15017",
      "GRPCAddr": ":15010",
      "MonitoringAddr": ":15014",
      "EnableProfiling": true,
      "TLSOptions": {
         "CaCertFile": "",
         "CertFile": "",
         "KeyFile": "",
         "TLSCipherSuites": null,
         "CipherSuits": null
      },
      "SecureGRPCAddr": ":15012"
   },
   "InjectionOptions": {
      "InjectionDirectory": "./var/lib/istio/inject"
   },
   "PodName": "istiod-elb-67dfb7579-zgdzv",
   "Namespace": "elb-system",
   "Revision": "elb",
   "MeshConfigFile": "./etc/istio/config/mesh",
   "NetworksConfigFile": "./etc/istio/config/meshNetworks",
   "RegistryOptions": {
      "FileDir": "",
      "Registries": [
         "Kubernetes"
      ],
      "KubeOptions": {
         "SystemNamespace": "",
         "MeshServiceController": null,
         "DomainSuffix": "cluster.local",
         "ClusterID": "Kubernetes",
         "ClusterAliases": {},
         "Metrics": null,
         "XDSUpdater": null,
         "NetworksWatcher": null,
         "MeshWatcher": null,
         "EndpointMode": 1,
         "KubernetesAPIQPS": 80,
         "KubernetesAPIBurst": 160,
         "SyncTimeout": 0,
         "DiscoveryNamespacesFilter": null
      },
      "ClusterRegistriesNamespace": "elb-system",
      "KubeConfig": "",
      "DistributionCacheRetention":<PHONE_NUMBER>0,
      "DistributionTrackingEnabled": false
   },
   "CtrlZOptions": {
      "Port": 9876,
      "Address": "localhost"
   },
   "KeepaliveOptions": {
      "Time":<PHONE_NUMBER>0,
      "Timeout":<PHONE_NUMBER>0,
      "MaxServerConnectionAge":<PHONE_NUMBER>000,
      "MaxServerConnectionAgeGrace":<PHONE_NUMBER>0
   },
   "ShutdownDuration":<PHONE_NUMBER>0,
   "JwtRule": ""
}
2024-03-22T08:15:31.621423Z	info	initializing mesh handlers
2024-03-22T08:15:31.621500Z	info	model	reloading network gateways
2024-03-22T08:15:31.621516Z	info	creating CA and initializing public key
2024-03-22T08:15:31.621536Z	info	Using istiod file format for signing ca files
2024-03-22T08:15:31.621554Z	info	Use self-signed certificate as the CA certificate
2024-03-22T08:15:31.664091Z	info	pkica	Load signing key and cert from existing secret elb-system/istio-ca-secret
2024-03-22T08:15:31.665401Z	info	pkica	Using existing public key: -----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

2024-03-22T08:15:31.665441Z	info	rootcertrotator	Set up back off time 18m32s to start rotator.
2024-03-22T08:15:31.665465Z	info	initializing controllers
2024-03-22T08:15:31.665543Z	info	No certificates specified, skipping K8S DNS certificate controller
2024-03-22T08:15:31.665569Z	info	rootcertrotator	Jitter is enabled, wait 18m32s before starting root cert rotator.
2024-03-22T08:15:31.873632Z	warn	kube	Skipping CRD gateway.networking.k8s.io/v1alpha2/ReferenceGrant as it is not present	controller=crd-controller
2024-03-22T08:15:31.873707Z	warn	kube	Skipping CRD gateway.networking.k8s.io/v1alpha2/TCPRoute as it is not present	controller=crd-controller
2024-03-22T08:15:31.873713Z	warn	kube	Skipping CRD gateway.networking.k8s.io/v1alpha2/TLSRoute as it is not present	controller=crd-controller
2024-03-22T08:15:31.873718Z	warn	kube	Skipping CRD gateway.networking.k8s.io/v1beta1/GatewayClass as it is not present	controller=crd-controller
2024-03-22T08:15:31.873723Z	warn	kube	Skipping CRD gateway.networking.k8s.io/v1beta1/Gateway as it is not present	controller=crd-controller
2024-03-22T08:15:31.873728Z	warn	kube	Skipping CRD gateway.networking.k8s.io/v1beta1/HTTPRoute as it is not present	controller=crd-controller
2024-03-22T08:15:31.874191Z	info	Adding Kubernetes registry adapter
2024-03-22T08:15:31.874275Z	info	initializing Istiod DNS certificates host: istiod-elb.elb-system.svc, custom host:
2024-03-22T08:15:32.243364Z	info	Generating istiod-signed cert for [istiod-elb.elb-system.svc istiod.elb-system.svc istiod-remote.elb-system.svc istio-pilot.elb-system.svc]:
 -----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----

2024-03-22T08:15:32.243443Z	info	Using istiod file format for signing ca files
2024-03-22T08:15:32.243458Z	info	No plugged-in cert at etc/cacerts/ca-key.pem; self-signed cert is used
2024-03-22T08:15:32.243935Z	info	x509 cert - Issuer: "O=cluster.local", Subject: "", SN: 1c238c01e7f58574e1ec2da63564b4f0, NotBefore: "2024-03-22T08:13:32Z", NotAfter: "2034-03-20T08:15:32Z"
2024-03-22T08:15:32.243947Z	info	Istiod certificates are reloaded
2024-03-22T08:15:32.244014Z	info	spiffe	Added 1 certs to trust domain cluster.local in peer cert verifier
2024-03-22T08:15:32.244024Z	info	initializing secure discovery service
2024-03-22T08:15:32.244083Z	info	initializing secure webhook server for istiod webhooks
2024-03-22T08:15:32.267635Z	info	initializing sidecar injector
2024-03-22T08:15:32.292441Z	debug	New inject configuration: sha256sum 7c03ea042b106097aef26d9341c1b94b0260b3335b161309e7ffeef5831f5c78
2024-03-22T08:15:32.292487Z	debug	Policy: enabled
2024-03-22T08:15:32.292494Z	debug	AlwaysInjectSelector: []
2024-03-22T08:15:32.292497Z	debug	NeverInjectSelector: []
2024-03-22T08:15:32.292669Z	debug	Templates: map[gateway:{{- $containers := list }}
{{- range $index, $container := .Spec.Containers }}{{ if not (eq $container.Name "istio-proxy") }}{{ $containers = append $containers $container.Name }}{{end}}{{- end}}
...
  {{- if eq (env "ENABLE_LEGACY_FSGROUP_INJECTION" "false") "true" }}
  securityContext:
    fsGroup: 1337
  {{- end }}
]
2024-03-22T08:15:32.295352Z	debug	Failed to decode proto: "unknown field \"enabled\" in v1alpha1.GlobalConfig".  Switching to fail-close.
2024-03-22T08:15:32.400717Z	info	validationController	validatingwebhookconfiguration istio-validator-elb-elb-system (failurePolicy=Fail, resourceVersion=210417189) is up-to-date. No change required.
2024-03-22T08:15:32.433858Z	info	controllers	starting	controller=configmap istio-sidecar-injector-elb
2024-03-22T08:15:32.434336Z	info	controllers	starting	controller=default revision
2024-03-22T08:15:32.434433Z	info	controllers	starting	controller=default revision
2024-03-22T08:15:32.434460Z	info	controllers	starting	controller=default revision
2024-03-22T08:15:32.466282Z	info	kube	controller "networking.istio.io/v1alpha3/EnvoyFilter" is syncing...	controller=crd-controller
2024-03-22T08:15:32.471675Z	debug	New inject configuration: sha256sum 7c03ea042b106097aef26d9341c1b94b0260b3335b161309e7ffeef5831f5c78
2024-03-22T08:15:32.471707Z	debug	Policy: enabled
2024-03-22T08:15:32.471712Z	debug	AlwaysInjectSelector: []
2024-03-22T08:15:32.471714Z	debug	NeverInjectSelector: []
2024-03-22T08:15:32.471850Z	debug	Templates: map[gateway:{{- $containers := list }}
{{- range $index, $container := .Spec.Containers }}{{ if not (eq $container.Name "istio-proxy") }}{{ $containers = append

...

  {{- end }}
]
2024-03-22T08:15:32.473243Z	debug	Failed to decode proto: "unknown field \"enabled\" in v1alpha1.GlobalConfig". Trying decode with AllowUnknownFields=true
2024-03-22T08:15:32.481385Z	info	ads	Push debounce stable[1] 71 for config Secret/n3r-platform-grafana/grafana-operator-real.v1 and 70 more configs: 100.729767ms since last change, 101.33547ms since last push, full=false
2024-03-22T08:15:32.481523Z	info	ads	XDS: Incremental Pushing:0 ConnectedEndpoints:0 Version:
2024-03-22T08:15:32.566445Z	info	kube	controller "networking.istio.io/v1alpha3/EnvoyFilter" is syncing...	controller=crd-controller
2024-03-22T08:15:32.667755Z	debug	Handle event add for configuration networking.istio.io/v1alpha3/VirtualService/elb-system/health-vs-gateway4
2024-03-22T08:15:32.667768Z	debug	Handle event add for configuration networking.istio.io/v1alpha3/Gateway/elb-ghtest-pri2/36208e4bcf3003fc329bf4148a06aeb9-gw
2024-03-22T08:15:32.667819Z	debug	Handle event add for configuration networking.istio.io/v1alpha3/DestinationRule/elb-system/adff-dr
2024-03-22T08:15:32.667840Z	debug	Handle event add for configuration networking.istio.io/v1alpha3/EnvoyFilter/elb-real-business-sync-api/accesslog-format-filter
2024-03-22T08:15:32.667821Z	debug	Handle event add for configuration
...
2024-03-22T08:15:32.669499Z	debug	Handle event add for configuration networking.istio.io/v1alpha3/EnvoyFilter/elb-system/gateway8-filter
2024-03-22T08:15:32.669510Z	debug	Handle event add for configuration networking.istio.io/v1alpha3/EnvoyFilter/elb-system/gateway1-filter
2024-03-22T08:15:32.669522Z	info	kube	Pilot K8S CRD controller synced in 367.619287ms	controller=crd-controller
2024-03-22T08:15:32.669572Z	debug	started queue f7spxmpr7g
2024-03-22T08:15:32.769997Z	info	ads	Push debounce stable[2] 236 for config EnvoyFilter/elb-seonghyun/backend-health-check-envoy-filter and 235 more configs: 100.38441ms since last change, 102.118997ms since last push, full=true
2024-03-22T08:15:32.798388Z	info	ads	XDS: Pushing:2024-03-22T08:15:32Z/1 Services:20 ConnectedEndpoints:0 Version:2024-03-22T08:15:32Z/1
2024-03-22T08:15:32.802997Z	info	Waiting for caches to be synced
2024-03-22T08:15:32.803050Z	debug	registry Kubernetes is syncing
2024-03-22T08:15:32.803023Z	info	kube	joining leader-election for istio-namespace-controller-election in elb-system on cluster Kubernetes
2024-03-22T08:15:32.803158Z	info	klog	attempting to acquire leader lease elb-system/istio-namespace-controller-election...
2024-03-22T08:15:32.803210Z	info	controllers	starting	controller=default revision
2024-03-22T08:15:32.805751Z	debug	registry Kubernetes is syncing
2024-03-22T08:15:32.809949Z	debug	registry Kubernetes is syncing
2024-03-22T08:15:32.818157Z	debug	registry Kubernetes is syncing
2024-03-22T08:15:32.834849Z	debug	registry Kubernetes is syncing
2024-03-22T08:15:32.838722Z	info	ads	Full push, new service elb-beta-business-sync-batch/istio-ingressgateway-beta-business-sync-batch.elb-beta-business-sync-batch.svc.cluster.local
2024-03-22T08:15:32.838784Z	info	ads	Full push, new service elb-goohyun-pri1/istio-ingressgateway-goohyun-pri1.elb-goohyun-pri1.svc.cluster.local
...
2024-03-22T08:15:32.840612Z	info	ads	Full push, new service elb-system/istio-ingressgateway-gateway1.elb-system.svc.cluster.local
2024-03-22T08:15:32.840676Z	info	ads	Full push, new service elb-beta-business-sync-api/istio-ingressgateway-beta-business-sync-api.elb-beta-business-sync-api.svc.cluster.local
2024-03-22T08:15:32.840703Z	info	kube	kube controller for Kubernetes synced after 539.009841ms
2024-03-22T08:15:32.840712Z	debug	started queue Kubernetes
2024-03-22T08:15:32.867179Z	info	All controller caches have been synced up in 64.182453ms
2024-03-22T08:15:32.867208Z	debug	Waiting for pushcontext to process inbound updates, inbound: 515, committed : 307
2024-03-22T08:15:32.869387Z	debug	Waiting for pushcontext to process inbound updates, inbound: 515, committed : 307
2024-03-22T08:15:32.873596Z	debug	Waiting for pushcontext to process inbound updates, inbound: 515, committed : 307
2024-03-22T08:15:32.881801Z	debug	Waiting for pushcontext to process inbound updates, inbound: 515, committed : 307
2024-03-22T08:15:32.898066Z	debug	Waiting for pushcontext to process inbound updates, inbound: 515, committed : 307
2024-03-22T08:15:32.930439Z	debug	Waiting for pushcontext to process inbound updates, inbound: 515, committed : 307
2024-03-22T08:15:32.944929Z	info	ads	Push debounce stable[3] 208 for reason service and 207 more reasons: 100.913443ms since last change, 108.497976ms since last push, full=true
2024-03-22T08:15:32.972178Z	warn	discovery is not ready: <nil>
2024-03-22T08:15:32.987922Z	info	ads	XDS: Pushing:2024-03-22T08:15:32Z/2 Services:60 ConnectedEndpoints:0 Version:2024-03-22T08:15:32Z/2
2024-03-22T08:15:32.995233Z	info	ads	All caches have been synced up in 1.471715265s, marking server ready
2024-03-22T08:15:32.995383Z	info	starting secure gRPC discovery service at <IP_ADDRESS>:15012
2024-03-22T08:15:32.995410Z	info	starting webhook service at <IP_ADDRESS>:15017
2024-03-22T08:15:32.995429Z	info	starting gRPC discovery service at <IP_ADDRESS>:15010
2024-03-22T08:15:33.382829Z	info	validationController	validatingwebhookconfiguration istio-validator-elb-elb-system (failurePolicy=Fail, resourceVersion=210417189) is up-to-date. No change required.
2024-03-22T08:15:34.962545Z	info	ads	Push debounce stable[4] 1 for config ServiceEntry/elb-system/istiod-elb.elb-system.svc.cluster.local: 100.271086ms since last change, 100.270946ms since last push, full=false
2024-03-22T08:15:34.962650Z	info	ads	XDS: Incremental Pushing:2024-03-22T08:15:32Z/2 ConnectedEndpoints:0 Version:2024-03-22T08:15:32Z/2
2024-03-22T08:15:47.153543Z	info	ads	ADS: new connection for node:istio-ingressgateway-seonghyun-8b86b9cb4-pd464.elb-seonghyun-1
2024-03-22T08:15:47.154481Z	info	ads	CDS: PUSH request for node:istio-ingressgateway-seonghyun-8b86b9cb4-pd464.elb-seonghyun resources:3 size:1.4kB cached:0/2
2024-03-22T08:15:47.154631Z	debug	buildGatewayListeners: gateways after merging: &{[{8080 HTTP }] ...
2024-03-22T08:15:47.154672Z	debug	buildGatewayListeners: marshaling listener "<IP_ADDRESS>_8080" with 1 filter chains
2024-03-22T08:15:47.155070Z	debug	attached HTTP filter with 5 http_filter options to listener "<IP_ADDRESS>_8080" filter chain 0
2024-03-22T08:15:47.156016Z	info	ads	LDS: PUSH request for node:istio-ingressgateway-seonghyun-8b86b9cb4-pd464.elb-seonghyun resources:1 size:3.8kB
2024-03-22T08:15:47.156104Z	debug	buildGatewayRoutes: gateways after merging: &{[{8080 HTTP }] ...}
2024-03-22T08:15:47.156976Z	info	ads	RDS: PUSH request for node:istio-ingressgateway-seonghyun-8b86b9cb4-pd464.elb-seonghyun resources:1 size:717B cached:0/0
2024-03-22T08:15:52.308729Z	info	ads	ADS: new connection for node:istio-ingressgateway-gateway4-54bc8dbf78-kgbjf.elb-system-2
2024-03-22T08:15:52.310229Z	info	ads	CDS: PUSH request for node:istio-ingressgateway-gateway4-54bc8dbf78-kgbjf.elb-system resources:10 size:12.7kB cached:0/9
2024-03-22T08:15:52.310505Z	info	ads	EDS: PUSH request for node:istio-ingressgateway-gateway4-54bc8dbf78-kgbjf.elb-system resources:9 size:2.5kB empty:0 cached:0/9
2024-03-22T08:15:52.310671Z	debug	buildGatewayListeners: gateways after merging: &{[{8443 HTTPS } {8080 HTTP }] map[{8080 HTTP }:0xc00520ba10 ...
2024-03-22T08:15:52.310824Z	debug	buildGatewayListeners: marshaling listener "<IP_ADDRESS>_8443" with 1 filter chains
2024-03-22T08:15:52.310908Z	debug	attached HTTP filter with 5 http_filter options to listener "<IP_ADDRESS>_8443" filter chain 0
2024-03-22T08:15:52.310918Z	debug	buildGatewayListeners: marshaling listener "<IP_ADDRESS>_8080" with 1 filter chains
2024-03-22T08:15:52.310949Z	debug	attached HTTP filter with 5 http_filter options to listener "<IP_ADDRESS>_8080" filter chain 0
2024-03-22T08:15:52.311706Z	info	ads	LDS: PUSH request for node:istio-ingressgateway-gateway4-54bc8dbf78-kgbjf.elb-system resources:2 size:12.3kB
2024-03-22T08:15:52.311858Z	debug	buildGatewayRoutes: gateways after merging: &{[{8443 HTTPS } {8080 HTTP }] map[{8080 HTTP }:0xc00520ba10 {8443 HTTPS }:0xc00520b9b0] map[] ...}
...
2024-03-22T08:15:52.312267Z	info	ads	RDS: PUSH request for node:istio-ingressgateway-gateway4-54bc8dbf78-kgbjf.elb-system resources:2 size:4.1kB cached:0/0
2024-03-22T08:15:52.322131Z	debug	cached authorization for user system:serviceaccount:elb-system:istio-ingressgateway-gateway4-service-account: <nil>
2024-03-22T08:15:52.322466Z	info	ads	SDS: PUSH request for node:istio-ingressgateway-gateway4-54bc8dbf78-kgbjf.elb-system resources:1 size:9.9kB cached:0/1
2024-03-22T08:16:25.291988Z	info	ads	ADS: new connection for node:istio-ingressgateway-gateway9-dc68bb966-8cttb.elb-system-3
2024-03-22T08:16:25.292584Z	info	ads	CDS: PUSH request for node:istio-ingressgateway-gateway9-dc68bb966-8cttb.elb-system resources:7 size:8.8kB cached:0/6
2024-03-22T08:16:25.292830Z	info	ads	EDS: PUSH request for node:istio-ingressgateway-gateway9-dc68bb966-8cttb.elb-system resources:6 size:1.8kB empty:0 cached:0/6
...
2024-03-22T08:16:25.293066Z	debug	buildGatewayListeners: marshaling listener "<IP_ADDRESS>_8443" with 1 filter chains
2024-03-22T08:16:25.293149Z	debug	attached HTTP filter with 5 http_filter options to listener "<IP_ADDRESS>_8443" filter chain 0
2024-03-22T08:16:25.293158Z	debug	buildGatewayListeners: marshaling listener "<IP_ADDRESS>_8080" with 1 filter chains
2024-03-22T08:16:25.293185Z	debug	attached HTTP filter with 5 http_filter options to listener "<IP_ADDRESS>_8080" filter chain 0
2024-03-22T08:16:25.293934Z	info	ads	LDS: PUSH request for node:istio-ingressgateway-gateway9-dc68bb966-8cttb.elb-system resources:2 size:12.3kB
2024-03-22T08:16:25.301446Z	debug	cached authorization for user system:serviceaccount:elb-system:istio-ingressgateway-gateway9-service-account: <nil>
2024-03-22T08:16:25.301645Z	info	ads	SDS: PUSH request for node:istio-ingressgateway-gateway9-dc68bb966-8cttb.elb-system resources:1 size:9.9kB cached:0/1
2024-03-22T08:16:25.301791Z	debug	buildGatewayRoutes: gateways after merging: &{[{8443 HTTPS } {8080 HTTP }] ...
}
2024-03-22T08:16:25.302061Z	debug	buildGatewayRoutes: gateways after merging: &{[{8443 HTTPS } {8080 HTTP }] map[{8080 HTTP }:0xc005d57e90 {8443 HTTPS }:0xc005d57e30] map[] map[] map[port:{number:443  protocol:"HTTPS"  name:"https"}...}
2024-03-22T08:16:25.302213Z	info	ads	RDS: PUSH request for node:istio-ingressgateway-gateway9-dc68bb966-8cttb.elb-system resources:2 size:3.5kB cached:0/0
2024-03-22T08:17:00.014120Z	info	ads	ADS: new connection for node:istio-ingressgateway-gateway8-67bb9f786-lv56j.elb-system-4
2024-03-22T08:17:00.015183Z	info	ads	CDS: PUSH request for node:istio-ingressgateway-gateway8-67bb9f786-lv56j.elb-system resources:16 size:20.1kB cached:0/15
2024-03-22T08:17:00.015816Z	info	ads	EDS: PUSH request for node:istio-ingressgateway-gateway8-67bb9f786-lv56j.elb-system resources:15 size:3.8kB empty:0 cached:0/15
2024-03-22T08:17:00.016289Z	debug	buildGatewayListeners: gateways after merging: &{[{8443 HTTPS } {8080 HTTP }] map[{8080 HTTP }:0xc0029195f0 {8443 HTTPS }:0xc002919590] ...}
2024-03-22T08:17:00.016391Z	debug	buildGatewayListeners: marshaling listener "<IP_ADDRESS>_8443" with 1 filter chains
2024-03-22T08:17:00.016497Z	debug	attached HTTP filter with 5 http_filter options to listener "<IP_ADDRESS>_8443" filter chain 0
2024-03-22T08:17:00.016508Z	debug	buildGatewayListeners: marshaling listener "<IP_ADDRESS>_8080" with 1 filter chains
2024-03-22T08:17:00.016538Z	debug	attached HTTP filter with 5 http_filter options to listener "<IP_ADDRESS>_8080" filter chain 0
2024-03-22T08:17:00.017245Z	info	ads	LDS: PUSH request for node:istio-ingressgateway-gateway8-67bb9f786-lv56j.elb-system resources:2 size:12.3kB
2024-03-22T08:17:00.025683Z	debug	cached authorization for user system:serviceaccount:elb-system:istio-ingressgateway-gateway8-service-account: <nil>
2024-03-22T08:17:00.025902Z	info	ads	SDS: PUSH request for node:istio-ingressgateway-gateway8-67bb9f786-lv56j.elb-system resources:1 size:9.9kB cached:0/1
2024-03-22T08:17:00.026152Z	debug	buildGatewayRoutes: gateways after merging: &{[{8443 HTTPS } {8080 HTTP }] map[{8080 HTTP }:...}
2024-03-22T08:17:00.026534Z	debug	buildGatewayRoutes: gateways after merging: &{[{8443 HTTPS } {8080 HTTP }] map[{8080 HTTP }:0xc0029195f0 ...}
2024-03-22T08:17:00.026727Z	info	ads	RDS: PUSH request for node:istio-ingressgateway-gateway8-67bb9f786-lv56j.elb-system resources:2 size:7.0kB cached:0/0

But after a few minutes, they are terminated with the following logs.

logs before termination
2024-03-22T08:20:43.292226Z	debug	Monitoring server terminated: <nil>
2024-03-22T08:20:43.292284Z	info	controllers	stopped	controller=default revision
2024-03-22T08:20:43.292320Z	info	controllers	stopped	controller=configmap istio-sidecar-injector-elb
2024-03-22T08:20:43.292323Z	info	controllers	stopped	controller=unregister_workloadentry
2024-03-22T08:20:43.292347Z	info	controllers	stopped	controller=ingress
2024-03-22T08:20:43.292400Z	info	leader election lock lost: istio-gateway-status-leader
2024-03-22T08:20:43.292383Z	info	leader election lock lost: istio-gateway-deployment-leader
2024-03-22T08:20:43.292440Z	info	leader election lock lost: istio-leader
2024-03-22T08:20:43.292410Z	info	rootcertrotator	Received stop signal, so stop the root cert rotator.
2024-03-22T08:20:43.292388Z	info	controllers	stopped	controller=multicluster secret
2024-03-22T08:20:43.292451Z	info	controllers	stopped	controller=configmap istio-elb
2024-03-22T08:20:43.292478Z	debug	closed queue fs5ftlwpr2
2024-03-22T08:20:43.292487Z	info	controllers	stopped	controller=healthcheck
2024-03-22T08:20:43.292456Z	debug	closed queue Kubernetes
2024-03-22T08:20:43.292521Z	info	kube	Controller terminated
2024-03-22T08:20:43.292207Z	debug	closed queue f7spxmpr7g
2024-03-22T08:20:43.292647Z	info	kube	controller terminated	controller=crd-controller
2024-03-22T08:20:43.292232Z	info	leader election lock lost: istio-namespace-controller-election
2024-03-22T08:20:43.292256Z	info	controllers	stopped	controller=default revision
2024-03-22T08:20:43.292234Z	info	controllers	stopped	controller=default revision
2024-03-22T08:20:43.292641Z	info	controllers	stopped	controller=webhook patcher

I confirmed a readiness probe was working well but suddenly it responded with a 503 status code and the pod was terminated.
Strangely, not all but partial istiod pods keep restarting.
I skipped some logs due to the content length limit.
If you need skipped information too, please let me know.
Version
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-07T21:20:10Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.10", GitCommit:"b8609d4dd75c5d6fba4a5eaa63a5507cb39a6e99", GitTreeState:"clean", BuildDate:"2023-10-18T11:33:36Z", GoVersion:"go1.20.10", Compiler:"gc", Platform:"linux/amd64"}

Additional Information
No response

It turns out that there were two different competing hpa configurations.


StringError("numeric field did not have utf-8 text") when it is working with command line

I am getting following error when i was able to extract it from command line. It was tar.gz file

I read your solution from https://users.rust-lang.org/t/solved-tar-rs-failed-to-iterate-over-archive-when-unpacking-tar/4442/6 thanks


Fix ios_makefile.inc for TFLite iOS demo app

It seems broken when merging change in b2db981a6731e978453862a73dab892bc674db68.
The file was formatted with an invalid way.
I don't know why it happened. Is it due to the .inc file extension name?

Can one of the admins verify this patch?


Run CI against new React release

Just validates that we don't have those new propType warnings. No other changes – can't use PureComponent since that would break anyone on React < 15.3... like me, for example, since I still haven't cleaned up all the unknown prop things in my app.

This is a trivial chore, so merging as-is


Does Pistache support '206/Partial Content' response?

Dear all,
Answering to GET request, my rest api may have to return potentially huge content. I wonder if I can use the code 206/Partial content to return several limited data (json formatted) instead of only one big flow. Does Pistache handle this code? If yes I suppose that I have to finish with the OK code...
Many thanks for any help.
Jacqueline

It is defined in https://github.com/oktal/pistache/blob/master/include/pistache/http_defs.h so it should work, but I've not personally tested it - so I'm not sure.
The response line should look something like:
`response.send(Http::Code::Partial_Content, my_response_string)


Add: WJLP-DT8

Channel Name
WJLP-DT8
Native Name (optional)
No response
Network (optional)
meTV Plus
Country
US
Subdivision (optional)
US-NY
City (optional)
New York City
Broadcast Area
s/US-NY
Languages
eng
Categories (optional)
network
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://www.metv.com/metvplus
Logo
https://cdnmetv.metv.com/2sP5J-1620921942-73-page-metvplus.png
Notes
No response

Already in database: https://iptv-org.github.io/?q=WJLP-DT8


Could not find dependency: 'react' relative to '/node_modules/react-transition-group/esm/CSSTransition.js'

When installing Uploader via a package manager, if the project does not have react (it shouldn't have to) then the following error is produced on require("uploader"):
Could not find dependency: 'react' relative to '/node_modules/react-transition-group/esm/CSSTransition.js'

Resolved in https://github.com/upload-js/uploader/releases/tag/v1.24.1


Live video stream

Hi,
Is it possible to stream live video to vrview? I would like to stream live mp4 to vrview on chrome. I can't use HLS and Safari. I have looked at the video example here, it uses partial-content to upload the video file.
Is it possible to start playing the video without uploading the entire file ?
Or is it possible to respond with chunked encoding or multi-part (stream video)?
Any hint on how to do so, is appreciated.
Best regards Shah

should be able to using the video tag as a view, and input the url for m3u8. I have tried it myself and does not appear to work.


Add levels increment alphaMinor and alphaMajor

It is frequent to go through alpha pre-releases to test a new minor or major version.
If I want to start the test campaign for the 2.0.0 version of my project currently in 1.4.2 I have to specify by hand the name of the new version with its alpha suffix, it's a pity.
The alphaMajor level solves this problem.

I feel like combining options like this is startin to get a bit unwieldy.  I wonder if instead we should have the option to take an absolute version  as an alternative to relative versions.
This would also help with workspaces where at one-off times crates get releases but you also want a synchronized version occasionally.

I feel like combining options like this is startin to get a bit unwieldy.

Do you see an easier way to publish a 1st alpha in a project without dev version (which is my case) ?
It is also possible to hide these advanced levels of help as long as it remains simple (those who want to dig deeper always have the reference).

I wonder if instead we should have the option to take an absolute version as an alternative to relative versions.

I'm not sure I understand. It's already possible to write a version by hand so I guess you're talking about something else, what do you mean by "an absolute version"?

Do you see an easier way to publish a 1st alpha in a project without dev version (which is my case) ?

What I'm proposing is that instead of
cargo publish alphaMinor

which I feel is complicating things and doesn't scale (would we also have an rcMinor or a  betaMinor?), I'm wondering if its better to instead do
cargo publish 1.1-alpha.1

We'd want to have a check to make sure the version is higher than the crates we are bumping but this gives the user control to do what they want at the cost of losing the convenience of the relative helpers (like minrr).

I agree with @epage that this case is already supported via absolute version.  I use absolute version bump frequently in my workflow.  It was reported in #188 and implemented in #191. It's more flexible and keep the complexity at a low level: imagine someone wants betaMinor or betaMajor.
Anyway, thanks for your patch @librelois


Best way of dealing with a disabled namespace sandbox (for users)?

As some of you might know, Debian 9 ships with the namespace sandbox (and it's enabled too) but it doesn't allow unprivileged users to create namespaces.
The muon application will error and tell the user to run it with the --no-sandbox flag.
However, there is an easy fix for this
echo 1 > /proc/sys/kernel/unprivileged_userns_clone

^Works until reboot, a more permanent fix is available in the source below.
https://superuser.com/questions/1094597/enable-user-namespaces-in-debian-kernel#1122977
I wonder how all application developers using Muon deal with this limitation.
My current strategy to deal with this issue is to bootstrap the application from a node environment (like in the muon-quick example iirc), running it, then checking for the --no-sandbox error and the applying the temporary fix if required.
If anyone know of a better solution, please let me know.

I found this repository installer https://github.com/brave/electron-installer-debian
Which isn't that different from the main repository. Compared with the original: https://github.com/unindented/electron-installer-debian/compare/master...brave:master
electron-builder-debian suggests that we might be able to hack a small tweak into the preinstall bash scripts.
{
  scripts: {
    'preinst': 'resources/preinst_script',
    'postinst': 'resources/postinst_script',
    'prerm': 'resources/prerm_script',
    'postrm': 'resources/postrm_script'
  }
}

tracking: https://github.com/brave/browser-laptop/issues/6902


Mondial relay API changes

Hello,
Since a few days, the examples are not working because Mondial Relay change some of its endpoints to https (the WSDL is not correctly updated yet).
To fix it : add client.setEndpoint(apiUrl); after soap.createClient
https://github.com/tilli-fr/mondial-relay-api/commit/2b5f2bd477dcfc42625ab710bcd197b4e57e6e06#diff-e727e4bdf3657fd1d798edcd6b099d6e092f8573cba266154583a746bba0f346R21

You saved my day

Thanks 🙏


Can't pass arguments to custom expect function

An expect callback will only receive the response as an argument. How is it possible to pass in custom arguments?
.expect(customFn(res, param1, param2))

Just use Function.prototype.bind - https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_objects/Function/bind or pass a function to .expect:
.expect(customFn.bind(param1, param2)) // is equivalent to
.expect(function(res) {
    customFn.call(this, param1, param2, res);
})


Figure out how to deal with the encrypted objects in ETCD database

Look into etcd is dangerous and it's difficult to decrypt the information inside it.


UTs improvement

TypeScript supported
UTs

Hi @stracker-phil may you review it once you spare some time?


[#1730] Fix NPE in generated from RNC

Fixes #1730
The faulty code with NPE was returning null instead of new CommentListImpl()
Fixing NPE even if this returned class has /TODO/ inside with nothing done on addComents method.

@lukasj : PR updated with wanted changes 😉


iOS call events issue

Hello,
we are not finding any solution for iOS call events. In android it works fine but for iOS we are not finding anything. Does anyone have a solution?

Hi may I know for ur android, side is the Event.actionCallAccept being triggered when you accept the incoming call?


Uncaught Error: Module did not self-register.

Click around in a *.yaml file (* being any yaml file)

Atom: 1.46.0 x64
Electron: 4.2.7
OS: "Arch Linux"
Thrown From: Atom Core
Stack Trace
Uncaught Error: Module did not self-register.
At ELECTRON_ASAR.js:160

Error: Module did not self-register.
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:160:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:722:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:169:18)
    at Module.load (internal/modules/cjs/loader.js:602:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:541:12)
    at Function.Module._load (internal/modules/cjs/loader.js:533:3)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:20:18)
    at customRequire (/usr/share/atom/resources/app/static/<embedded>:1:695133)
    at get_KeyboardLayoutManager (/usr/share/atom/resources/app/static/<embedded>:14:2778162)
    at get_manager (/usr/share/atom/resources/app/static/<embedded>:14:2778264)
    at Object.getCurrentKeyboardLayout (/usr/share/atom/resources/app/static/<embedded>:14:2778390)
    at e.keystrokeForKeyboardEvent (/usr/share/atom/resources/app/static/<embedded>:14:1081110)
    at KeymapManager.keystrokeForKeyboardEvent (/usr/share/atom/resources/app/static/<embedded>:11:1253631)
    at KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app/static/<embedded>:11:1251616)
    at WindowEventHandler.handleDocumentKeyEvent (/usr/share/atom/resources/app/static/<embedded>:11:284744)

Commands
     -0:54.2.0 core:save (input.hidden-input)
     -0:53.6.0 core:close (input.hidden-input)
     -0:05.7.0 core:save (input.hidden-input)

Non-Core Packages
atom-ide-ui 0.13.0
build-bazel 0.1.0
busy-signal 2.0.1
color-picker 2.3.0
declarations 1.1.3
formatter-gofmt 1.0.1
go-debug 1.7.0
go-plus 6.1.0
go-signature-statusbar 1.2.3
ide-golang 0.0.5
intentions 1.1.5
intentions-colorpicker 1.0.1
intentions-numbers 1.0.4
language-bazel 0.3.4
language-docker 1.1.8
language-hcl 0.4.0
language-systemd 0.1.1
language-terraform 0.9.3
linter 2.3.1
linter-eslint 8.5.5
linter-golinter 1.3.0
linter-phpmd 2.0.2
linter-python 3.1.2
linter-scss-lint 3.2.1
linter-terraform-syntax 1.4.1
linter-travis-lint 1.0.2
linter-ui-default 1.8.1
minimap 4.29.9
minimap-linter 2.2.1
terraform-fmt 0.3.0

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/20222. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Parity: XMLDTD.init()

Implement it to create an empty .DTDKind node, as it does on Darwin.

@swift-ci please test


Client won't connect to internet

Not quite sure what I'm doing wrong, so I would like to request some guidance.
Creating the hotspot seems to work fine. The device (Nexus 4) is able to connect to it but is unable to reach anything but the local network.
The command I'm using to run the hotspot is /usr/bin/create_ap wlp5s0 enp5s1 FreeInternet.
Some outputs as asked in other issues:
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 90:2b:34:d0:2f:11 brd ff:ff:ff:ff:ff:ff
3: enp5s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether a0:f3:c1:04:94:7e brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global enp5s1
       valid_lft forever preferred_lft forever
    inet6 2003:45:4779:4c00:a2f3:c1ff:fe04:947e/64 scope global mngtmpaddr dynamic
       valid_lft 14388sec preferred_lft 1788sec
    inet6 fe80::a2f3:c1ff:fe04:947e/64 scope link
       valid_lft forever preferred_lft forever
4: wlp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:0f:b5:88:49:bd brd ff:ff:ff:ff:ff:ff
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default
    link/sit <IP_ADDRESS> brd <IP_ADDRESS>
12: ap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0f:b5:88:49:be brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global ap0
       valid_lft forever preferred_lft forever
    inet6 fe80::20f:b5ff:fe88:49be/64 scope link
       valid_lft forever preferred_lft forever

ip route
default via <IP_ADDRESS> dev enp5s1  proto static
<IP_ADDRESS>/24 dev enp5s1  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/24 dev ap0  proto kernel  scope link  src <IP_ADDRESS>

iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     udp  --  anywhere             anywhere             udp dpt:bootps
ACCEPT     udp  --  anywhere             anywhere             udp dpt:domain
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:domain

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  anywhere             <IP_ADDRESS>/24
ACCEPT     all  --  <IP_ADDRESS>/24      anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
MASQUERADE  all  --  <IP_ADDRESS>/24      anywhere

Give me the output of the following commands:
cat /proc/sys/net/ipv4/ip_forward
ping -c3 <IP_ADDRESS>

The ping also run it on the client.

cat /proc/sys/net/ipv4/ip_forward
1

ping -c3 <IP_ADDRESS> on host
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=58 time=18.7 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=58 time=18.7 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=58 time=18.7 ms

--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 18.766/18.773/18.786/0.112 ms

ping -c3 <IP_ADDRESS> on client
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.

--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2004ms

The setup looks correct.
Do you have the same problem with other clients? What wifi adapter do you use?

I'm getting the same issue on a laptop.
The wireless adapter is a Qualcomm Atheros AR5212/AR5213.
It might be worth noting that letting the client connect to a proxy like squid pretty much solves the issue, which makes it only half the dealbreaker.

Checkout 4d654b7 and try again. Does it work?
If not, checkout back to master and try again with --no-virt.
Try to use another channel, channels 1, 6 and 11 are the best choices because they don't overlap with each-other.

4d654b76a1f686a70276206de059f7e8ba187f4a does not seem to change anything (the module is loaded). Neither does --no-virt.

Can you use wireshark on the client and the server to confirm that the packets are send from client to server and then server route them to ethernet? Also, check for the replies, if the IP is correct. If the TTL is not expired etc.
I can not think what probably is wrong. The only way to find out is by checking the packets.

Also, give me your dmesg and iw list

I found a solution to this issue.
When using systemd 219 you will have to set IPForward=yes in the respective configuration for an interface you're planning to share the connection from.
See https://bugs.freedesktop.org/show_bug.cgi?id=89509 for details.

Cool thanks. It's strange that I didn't find this problem before. Anyway, I just checked the code of systemd that enables the forwarding and I found that it just enables 2 kernel flags through procfs (create_ap enables only one).
So, can you please remove IPForward=yes, run create_ap and make sure that it doesn't work and then run the following:
echo 1 > /proc/sys/net/ipv4/conf/enp5s1/forwarding

Please let me know if this makes it to work or not.

Can confirm that echo 1 > /proc/sys/net/ipv4/conf/enp5s1/forwarding enabled the connection to work properly when IPForward is disabled.

Thanks! I will add this in create_ap tomorrow, I'm a bit busy now.

Fixed. Try it and let me know if you have any problems.
Thanks!