Exception processing Microsoft.Resources schema 2019-07-01

[C:\github\azure-resource-manager-schemas\generator] executing: autorest-beta.cmd --azureresourceschema --output-folder=C:\Users\antmarti\AppData\Local\Temp\bfbwmkowy8a --tag=all-api-versions --api-version=2019-07-01 --title=none C:\Users\antmarti\AppData\Local\Temp\schm_azspc\specification\resources\resource-manager\readme.md
AutoRest code generation utility [version: 3.0.6122; node: v10.15.3, max-memory: 8192 gb]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      'C:\github\azure-resource-manager-schemas\generator\node_modules\@autorest\core\dist' (3.0.6139)
   Loading local AutoRest extension '@autorest/azureresourceschema' (C:\github\azure-resource-manager-schemas\generator\node_modules\@autorest\azureresourceschema)
FATAL: Error parsing swagger file. Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.IList`1[System.String]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'components.schemas.schemas:5056.required.0', line 1, position 394954.
FATAL: AutoRest.Core.Logging.CodeGenerationException: Error parsing swagger file. Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.IList`1[System.String]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'components.schemas.schemas:5056.required.0', line 1, position 394954.
   at AutoRest.Modeler.SwaggerParser.Parse(String swaggerDocument) in /home/vsts/work/1/s/autorest.common/src/SwaggerParser.cs:line 56
   at AutoRest.Modeler.ModelerPlugin.<ProcessInternal>d__1.MoveNext() in /home/vsts/work/1/s/autorest.common/src/Program.cs:line 41
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at NewPlugin.<Process>d__20.MoveNext() in /home/vsts/work/1/s/autorest.common/src/common/Plugins/NewPlugin.cs:line 164
  Error: Plugin imodeler2 reported failure.

For reasons I cannot explain, this problem goes away by removing these two sections from the swagger spec:
lines 4617-4620
lines 4646-4650
However worth noting these same sections exist in the previous swagger spec (2019-05-10), so the problem doesn't seem to be specific to these sections.

Before I find time to look into this, can you install the latest autorest-beta (npm install -g autorest-beta ) and add --version:3.0.61779 to the command line?
G

Before I find time to look into this, can you install the latest autorest-beta (npm install -g autorest-beta ) and add --version:3.0.61779 to the command line?
G

Thanks @fearthecowboy - yes I see the same behavior with autorest core version 3.0.6179 (logs below). Note autorest-beta is at version 3.0.6149 - I couldn't find a way to upgrade this.
 Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.IList`1[System.String]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'components.schemas.schemas:5056.required.0', line 1, position 423477.
FATAL: AutoRest.Core.Logging.CodeGenerationException: Error parsing swagger file. Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.IList`1[System.String]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'components.schemas.schemas:5056.required.0', line 1, position 423477.
   at AutoRest.Modeler.SwaggerParser.Parse(String swaggerDocument) in /home/vsts/work/1/s/autorest.common/src/SwaggerParser.cs:line 56
   at AutoRest.Modeler.ModelerPlugin.<ProcessInternal>d__1.MoveNext() in /home/vsts/work/1/s/autorest.common/src/Program.cs:line 41
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at NewPlugin.<Process>d__20.MoveNext() in /home/vsts/work/1/s/autorest.common/src/common/Plugins/NewPlugin.cs:line 164
C:\Users\antmarti\.autorest\@autorest_core<EMAIL_ADDRESS>- FAILURE {}
Process() cancelled due to exception : Plugin imodeler2 reported failure. / Error: Plugin imodeler2 reported failure.
    at C:\Users\antmarti\.autorest\@autorest_core@3.0.6179\node_modules\@autorest\core\dist\lib\pipeline\plugins\external.js:26:19
  Error: Plugin imodeler2 reported failure.
[66.69 s] Shutting Down.
[66.7 s] Exiting.

The cause is that following required section is converted to object, instead of string array. So deserialization failed at imodeler2, as it's expecting IList<string>.
managedapplications.json#L1427-L1432 is converted to:
        "required": {
          "0": "name",
          "1": "publisher",
          "2": "product",
          "3": "version"
        },

managedapplications.json#L1510-L1512 is converted to:
"required": { "0": "name" },

After removing the above required sections from swagger, it succeeded. Not sure at which node the model is wrong.

Thanks for narrowing down the issue @leni-msft. As an experiment I replaced "name" with "name2" in both places, and the issue went away.
@fearthecowboy, is there any special-case handling for a "name" property in the "required" array that might explain why the array is being converted into an object?

I debugged thru this, I've narrowed down where I think the fundemental problem is, but I think I have a faster fix for you.
add --pass-thru:subset-reducer onto your command line. I don't think you need what it does, and I'm pretty sure it's getting in your way.

@fearthecowboy Thanks! I've got no idea what that does, but will give it a go! Do you think this is something we can enable for schema generation across all resources in the specs repo (e.g. adding it to the params list here)?

I think so; subset reduction is used to reduce complexity it models when generating code, but I don't think that matters at all for your scenario.
Try out a few and see if it makes any significant problems

The issue is gone with new parameters. So close this issue.
AutoRest code generation utility [cli version: 3.0.6187; node: v13.9.0, max-memory: 8192 gb]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      '/home/leni/.autorest/@autorest_core@3.0.6306/node_modules/@autorest/core/dist' (3.0.6306)
   Loading AutoRest extension '@autorest/azureresourceschema' (~3.0.45->3.0.79)


feat: Spotlight integration with hydration-overlay

Feature Addition: Spotlight Integration in Hydration-Overlay
This pull request introduces an integration of Spotlight into the hydration-overlay module.
Key Highlights:

Addressed all necessary conditions outlined in the discussion here.
Note: Current integration and tests may not function as expected due to pending integration support in Spotlight. The implementation is primed for action once the necessary changes are merged.

Next Steps:

Track the progress of Hydration-overlay integration in Spotlight here.
Upon completion of Spotlight integration, a simple version update for the Spotlight package in this repository is all that's needed.

Hi @samijaber, we are done here.
we published a new version in spotlight to support hydration-overlay.
Added a test case also for nextjs app.
Please review.
Thanks.
btw, I found a issue while setting up webpack in nextjs with hydation-overlay but that will not hamper anything here.
I'll open it seperately.

Hi @samijaber just bumping here for this PR.
Thanks.

Hi @samijaber  just nudging for this feature.
Can you please review this PR.
Thanks

Hi @samijaber just bunping here as a reminder for this PR.
Thanks


Website Release: New site content and languages

29-04-22 - Changelog:

More Indonesian content added
Dependencies for website updated
Intial fund 8 Catalyst TV episodes added to website
New filipino language added to site with intial translations

During the review, if I found any typos, I click the Viewed check box and then just write a comment? Does the creator then need to revise & re-commit?

Youll have to patch the main branch with another pull request merging into main for it to up this PR

if Eveything checks out, im going to push this in to the release build @markibanez @andrecahyadi
like this if your okay or add a comment if you still want to make changes


Draw (temporal) Props Images

Create an image from each prop and prop-state. Every image has independent and measures (256x256px).
Need to draw:

[x] Draw Heal Plant (Grow01 - Grow02)
[x] Draw Explosive Plant (Grow01 - Grow02 - Throwed)
[x] Draw Breakeable Rock (Destroyed)
[x] Draw Barrel (Destroyed)

EXPECTED RESULTS:
Props images -
All the props images in placeHolders
plantHeal.png
plantHealG01.png
plantHealG02.png
plantExplosive.png
plantExplosiveG01.png
plantExplosiveG02.png
plantExplosiveBall.png
barrel.png
barrelDestroyed.png
rock.png
rockDestroyed.png

Uploaded Plants and barrel in commit https://github.com/RyuuSukeChan/ProjectDungeon/commit/38fe44f289442ba856d1b82a2270fd59dbe14912

Uploaded Rock and mark in commit https://github.com/RyuuSukeChan/ProjectDungeon/commit/f2e41ada60e1abbfb5754927fd7b0917cc132d65


Quiet private CLI switch & piping to drop use of chronic

Adds --quiet to the private-cli, letting us reduce the use of chronic. This is a step towards removing our use of chronic for silencing stdout/stderr on successfull steps of our workflows when run locally (needed since it seems snakemake will not do this for us).
This is followed up with piping noisy tools' stdout or stderr to a file as part of the snakemake command.
We can now drop the use of chronic which proved troublesome due to Perl dependency issues in conda.
Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)
[ ] This change requires a documentation update
[ ] This is a documentation update

Action Checklist

[x] Work on a single issue/concept (if there are multiple separate issues to address, please use a separate pull request for each)
[ ] Fork the pyani-plus repository under your own account (please allow write access for repository maintainers)
[x] Set up an appropriate development environment (please see CONTRIBUTING.md for this repository)
[x] Create a new branch with a short, descriptive name
[x] Work on this branch

[x] style guidelines have been followed (please see CONTRIBUTING.md for this repository)
[ ] new code is commented, especially in hard-to-understand areas
[x] corresponding changes to documentation have been made
[x] tests for the change have been added that demonstrate the fix or feature works

[x] Test locally with pytest-plus -v non-passing code will not be merged
[x] Rebase against origin/master
[x] Check changes with linting/formatting tools before submission (please see CONTRIBUTING.md for this repository)
[x] Commit branch
[x] Submit pull request, describing the content and intent of the pull request
[x] Request a code review
[x] Continue the discussion at Pull requests section in the pyan-plus repository

This is perhaps slightly less functional than using chronic, as in the event of a failure some of the potentially useful information will be in the log file from a snakemake job, rather than on screen in the terminal.
However, it avoids using chronic which proved non-trivial to get installed and working.


Fix broken_intra_doc_links lint warning

Running cargo test shows a warning which conveniently includes the fix as well:
warning: lint `broken_intra_doc_links` has been renamed to `rustdoc::broken_intra_doc_links`
  --> /home/dsaxton/git-repos/rust-bitcoin/src/lib.rs:60:9
   |
60 | #![deny(broken_intra_doc_links)]
   |         ^^^^^^^^^^^^^^^^^^^^^^ help: use the new name: `rustdoc::broken_intra_doc_links`
   |
   = note: `#[warn(renamed_and_removed_lints)]` on by default

warning: 1 warning emitted

Thanks for trying this, the build warning also annoys me. Your change doesn't work as CI shows, here is an alternate solution I came up with: https://github.com/rust-bitcoin/rust-bitcoin/pull/1059

Ah, got confused about MSRVs, @tcharding solution is great


Figure out how Go packaging works

I will need to set up packaging/versioning so we can have a proper release process.
Along with this will be allowing people who download this to install it to their computer so they aren't having to use go run .
Also the packaging will allow people to import this into their own go projects.
Can we package this in a way where we can use this library in other languages?

https://pkg.go.dev/about#adding-a-package


Inform Pipeline Columns of Currency Awareness

Add the ability to instantiate pipeline Columns with a currency_aware flag, indicating whether or not it makes sense to call .fx/convert the column's values to another currency. For example, OHLC data is currency-aware, but Volume is not.

Coverage decreased (-0.6%) to 87.625% when pulling 73468f34d1e0746dfeff88cb261ff250f7ed8899 on nicer-fx-errors into 009af2116f603fd22969dfa7217c1502f54ef871 on master.

@ssanderson This is good to go unless you had anything else?


Single GPU Training

How can I train the model on a Single GPU machine? Thanks

If you run main.py on a machine with a single GPU it will train using only that one GPU. If you plan on training on ImageNet-size images (3x224x224) you will also need to reduce the batch size to 128, 64, or even 32, since you won't be able to fit a batch size of 2048 into a single GPU.
When using such a small batch size, it also might make sense to replace LARS by SGD.


updated the values of functions such as zeta, psi, etc.

Since the temperature q[-1] keeps changing, ChemicalNetwork.py needs to update the values of functions zeta, psi, etc., otherwise the subsequent calculation will always call these functions with the original value of q[-1], which will potentially lead to negative temperature q[-1].

Hi @Xsmos , thanks for diving into this, and my apologies for the massive delay in getting back to you.
It has been awhile since I looked at this corner of the code, but it looks like it's setup in such a way that these coefficients are updated at a higher level. For example, in ares.simulations.GasParcel, there's a routine called update_rate_coefficients that calls the routine which resets these attributes (SourceIndependentCoefficients, which sets, e.g., Beta, alpha, etc.).  It does look like they are changing with time in tests. This setup of course requires care for users who are trying to use the ChemicalNetwork directly, so perhaps there are better ways of alerting the user to that possibility or re-organizing things in a more failsafe way. I'd be curious to hear your thoughts about that if that's the boat you're in.
This might also get at a deeper point about how the calculations are done. The fact that the coefficients are updated at a "higher level" than in ChemicalNetwork is a reflection of there being two different kinds of timesteps. There's a "global" timestep, which controls how often we update the radiation background and things like the photoionization and photoheating rate coefficients (k_ion, k_heat, etc), but then the ODE solver is operating on timescales smaller than that, over which k_ion, k_heat etc are assumed to not change very much. The reason for that is that it would be computationally expensive to recompute anything having to do with the radiation field so frequently. The coefficients you've identified are actually not that expensive to compute and so in principle could be updated within each global step, but the code currently lumps them in with the coefficients involving the radiation field. To deal with rapidly evolving quantities in a scheme like this, one can change what is the biggest fractional change that is allowed in any quantity in a single timestep. That's the parameter epsilon_dt, set to 0.05 by default.
I'm definitely open to discussion on this -- at the moment I'm waffling on which approach is most correct. If you have concrete examples / parameter choices that make it clear, let me know! I'd also be curious to know if reducing the value of epsilon_dt helps. Anyways, thanks again, and sorry for the delay.


Erroneous BridgeEvent events created by backwards compatibility layer.

asterisk-java cleverly creates BridgeEvent events out of BridgeEnterEvent events when the count of channels in a bridge reaches two. The only trouble with this is that not all channels that enter a bridge are actually being bridged together. Example:
1.SIP/a calls SIP/b
2.SIP/b parks call
SIP/a enters parking bridge
3.SIP/c calls SIP/b
4.SIP/b parks call
SIP/c enters parking bridge
asterisk-java recognizes that a bridge has two channels now
asterisk-java generates a BridgeEvent indicating that SIP/a and SIP/c are connected to one another
Parking uses what is known as a holding bridge -- a system for keeping channels in the bridging architecture, but while they are in these bridges they don't really communicate with each other in any way and it's not accurate to connect them.
Trivial fix is to add a conditional check on the bridge technology to make sure the bridge isn't a holding bridge before doing doing the whole backwards compatibility thing.

relevant block of code starts at
main/java/org/asteriskjava/manager/internal/backwardsCompatibility/bridge/BridgeState.java:47

Would you be able to push a patch?

I will attempt to do so within the next few hours.

Alright, I made a pull request. Let me know if you need anything else.

thanks


[Vue3 + XState] Write blog post on kit

Acceptance criteria:

[x] Blog post draft is written about the kit and any interesting architectural tidbits related to it
[x] Someone has been tagged and asked for review of the post

Completed and sent to content team, now live on blog.


Improved tests

Codecov Report

Merging #14 (44688a0) into main (7a7df8a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #14   +/-   ##
=======================================
  Coverage   98.87%   98.87%
=======================================
  Files          30       30
  Lines         266      266
=======================================
  Hits          263      263
  Misses          3        3

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


Adding |> <| support (For Elm especially)

|> or <| in Elm is ugly
Love the triangles with Fira Code !

I've started on the glyphs. What do you think?

I love it ! :D

Here's the other... I fixed the spacing to be more "optically" centered vs "numerically" centered.

Love it too ! Very good job !

Closed by 2464f9f94100d1fb86718f529d3aa2bb20b0e1fd
Used wrong issue #.


[Release] sdk/resourcemanager/recoveryservices/armrecoveryservices/2.0.0

https://github.com/Azure/sdk-release-request/issues/5130

The breaking changes are introduced and approved in this PR.

/azp run go - armrecoveryservices - ci

The breaking changes are introduced and approved in this PR.

@JeffreyRichter , please approve this major version release by adding label of Approved Major Version, thanks.


is_image() function not working with URL params appended to an image src

Expected behavior
Image class method is_image() should return true when is called for supported file extensions.
https://github.com/timber/timber/blob/384f130c7b5dc34363b8bea60eff8b50503b6f9f/lib/Image.php#L535
Actual behavior
When the attachement SRC includes URLs parameters, is_image() method returns false.
Example :
https://cdn-name.imgix.net/2021/04/photo-1434871619871-1f315a50efba-scaled.jpeg?auto=format&fit=scale&h=1361&ixlib=php-3.3.0&w=2048&wpsize=2048x2048&s=fd1fd431490df94d4d338e1b1729f3fa
This is happening because WP internal method wp_check_filetype() does not support URL params. A 6 years old ticket is still open about this specific issue :
https://core.trac.wordpress.org/ticket/30377
Possible fix and patch :
Strip URL params in PathHelper methods, check out my commit here :
https://github.com/thetoine/timber/commit/97390e202853ed783c0cc9508cc7eb4899ee83e9
What version of WordPress, PHP and Timber are you using?
WP 5.7.1
Timber 1.18.2
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
WP.org

Salut @thetoine,
This issue has been fixed in https://github.com/timber/timber/pull/2730. Unfortunately, we're probably not going to backport this change to Timber 1.x.
Timber 2.x is almost out and we're putting all our efforts to make it happen ASAP.

Bonjour @nlemoine, thanks for the update!


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.1 to before v5.16.11",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=470502de5bdb1ed0def643a4458593a40b8f6b66",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=18b57afacdc8dc1fa0d1a3c3a15a1d5a599159fa"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "470502de5bdb1ed0def643a4458593a40b8f6b66",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "18b57afacdc8dc1fa0d1a3c3a15a1d5a599159fa",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net_sched: add __rcu annotation to netdev->qdisc\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.16.11 by commit 18b57afacdc8dc1fa0d1a3c3a15a1d5a599159fa, it was introduced in version v5.1 by commit 470502de5bdb1ed0def643a4458593a40b8f6b66. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000553


Add messages to all uses of common-utils assert

Addresses https://github.com/microsoft/FluidFramework/issues/4439, i.e. adds a message to every use of assert that relies on the browser-friendly version from the common-utils package.
I tried making useful messages, but would appreciate feedback!
Other changes:
Along the way, I also noticed a couple uses of the common-utils assert in test code:

packages/drivers/odsp-driver/src/test/rateLimiter.spec.ts (switched this one to use typical { strict as assert })
packages/loader/driver-utils/src/test/blobAggregation.spec.ts  (switches this one as well)

Also fixed one comment typo in mergetree

My one feedback. Please do smaller PRs in the future. this could easily have been done per packager, or per layer

i'm going to commit this and fast follow with a short code implementing, that I'm currenting prototyping. I'll likely checkin a pr to move short codes before the automation. current prototype takes less than 10 sec to run


Added reference from Array.shuffle to GDScript.randomize.

Closes  #28689

Thanks! But this duplicates https://github.com/godotengine/godot/pull/28699. You should discuss with them which one of your respective PRs should be kept open.

Sorry, I should have posted a comment there that I was going to do this.  The other one was there first, so I'll close this.


everything-json does not report the allocated memory to the GC

everything-json does not report the allocated memory to the GC which means that the GC is not aware when large amounts of memory have been allocated by what appears to be small in JavaScript JSON objects.
Although there is no leak, this means that the GC won't aggressively try to free those objects and can run out of memory.
In particular, the amount of memory reported during a next build operation can be off by a very significant amount if using lots of JSON parsing.

Fixed by #111


gradle-vaadin-plugin stuck at vaadinRun?

This is my build.gradle script:
buildscript {
  repositories {
    maven {
      url "https://plugins.gradle.org/m2/"
    }
  }
  dependencies {
    classpath "fi.jasoft.plugin:gradle-vaadin-plugin:0.11.4"
  }
}

apply plugin: "fi.jasoft.plugin.vaadin"

Hi,
What do you mean "stuck"?
The vaadinRun task is a long running task that will remain running serving the web application until it is terminated by the user.


Remove bundled loader from notebooks webview

Fixes #121245
Instead of including our custom loader for all notebooks, it makes more sense that each notebook implementation can bring along their own loader if one is needed
This results in the notebooks loading a bit faster by default and also lets us avoid some of the weird CSP issues we were seeing while trying to include our loader on the web
@DonJayamanne  We'll need confirmation that Jupyter has a workaround in place for this before this can be merged

@mjbvz if I'm not mistaken, the solution here is for us to include require.js isn't that right.

@DonJayamanne Yes, you will need to include require.js (I believe as a preload). One benefit though is that you now can make sure the version of require used in VS Code Jupyter notebooks matches the version used in other notebook implementations

We're currently swamped. I'll let you know sometime this week.
Hope that works.
I too would like to get this into vscode, it's a very good change, getting rid of the archaic amd..

Superseded by #124864
Once python is shipping their own loader, will follow up by removing our loader entirely


chansrv: change chansrv log path to ${XDG_DATA_HOME}/xrdp

like Xorg's logfile is written to ${XDG_DATA_HOME}/xorg/Xorg.n.log.
If XDG_DATA_HOME is not defined, the log path will be
${HOME}/.local/share/xrdp.

I like Xorg's log path in user directory so I imitated it. What do you think of?

If XDG_DATA_HOME is not defined, the log path will be
${HOME}/.local/share/xrdp.

And if that doesn't exist?

${XDG_DATA_HOME}/xrdp/ or ${HOME}/.local/share/xrdp will be created if the directory doesn't exists.
If HOME environment variable is not defined, print error and exit (chansrv.c:1518).

If no objections, I'll merge this after a week.


Add link to Gravatar provider repository

As discussed here #1794 I created my own repo with Gravatar provider.
Could you add the link, please? Maybe it will be useful to someone else too

@ottaviano
Can you resolve conflicts, please?

@localheinz done 👍

Thanks!


Add Jaeger logo

Right now, the Jaeger template for OpenShift is using Go's gopher. Ideally, we'd like to use Jaeger's own logo: https://github.com/jaegertracing/artwork
Ref: https://github.com/jaegertracing/jaeger-openshift/pull/92

@rhamilto, would this be something that would get merged if I send a PR? If so, are there instructions somewhere on how to do it?

@jpkrohling.  PRs welcome!  See https://github.com/openshift/openshift-logos-icon#contributing

Created #22

The next release will be 4.0.  I've opened a PR to make use of the v1.7.0 release including the Jaeger icon in the new console.
In addition to the icon, the console also has an optional color image replacement of the icon.  See https://github.com/openshift/console/blob/master/frontend/public/components/catalog-item-icon.tsx#L7-L176.  If you have a color image, you can either open a PR to console or you can supply me with the image and I'll take care of it for you.  Usage wise, nothing changes.  You'll still update the templates to include icon-jaeger, but instead of the monochrome font icon, you'll get the color image.  :)

That's nice! At this moment, we have only the EPS version here:
https://github.com/jaegertracing/artwork/blob/master/EPS/Jaeger_Logo_Final_PANTONE.eps
And the PNG:
https://github.com/jaegertracing/artwork/blob/master/PNG/Jaeger_Logo_Final_PANTONE.png
A PR is on its way, providing a SVG:
https://github.com/jaegertracing/artwork/pull/4
https://github.com/jaegertracing/artwork/blob/16507f99bf1199994852e19b2600d0b726bb2d3b/SVG/Jaeger_Logo_Final_PANTONE.svg

https://github.com/jaegertracing/artwork/blob/16507f99bf1199994852e19b2600d0b726bb2d3b/SVG/Jaeger_Logo_Final_PANTONE.svg

I recommend trimming the extra canvas surrounding the image in the SVG to maximize the size of the image on the page.  For example, https://github.com/openshift/console/blob/master/frontend/public/imgs/logos/3scale.svg

Something like this? https://github.com/jaegertracing/artwork/blob/b8d9b68b98e5652718af77be880052744cdd1ee6/SVG/Jaeger_Logo_Final_PANTONE.svg

Perfect!


Cannot find last release 4.0.0

Describe the bug
Hi
On github I can see the last release is 4.0.0, however on maven central or repository I can only find 4.0.0-alpha (https://central.sonatype.com/artifact/io.bkbn/kompendium-core/versions) - is it expected?
(btw a comment on the doc: it is very clear and well written. However on https://bkbn.gitbook.io/kompendium/#notarizing-a-ktor-application I would expect to be able to open the openapi.json at the end.
However this did not work, from the examples I understood that I needed ktor ContentNegotiation plugin also. You could argue that examples are there for this actually, however if there are prerequisites it could be worth explaining them).

This project is honestly in an unmaintained state.  I no longer work w/ Ktor or Kotlin, and on the whole, don't have the time to fix issues for the project.
I've debated making it a public archive project, but, have left it as is for now

The sonatype connection randomly breaking really took the remaining wind out of my sails, because sonatype is such a pain to debug, and it's left the project in a weird state b/c the documentation is all ready for 4.0, but 4.0 can't be released until the sonatype issue is figured out


Moving pushMiddlewareToGroup to boot method in service provider

Hello,
with the newer laravel versions, using pushMiddlewareToGroup in register method is not supported anymore :
https://github.com/laravel/framework/issues/36604
this PR moves the pushMiddlewareToGroup calls to boot() method of the service provider.
thanks !

Thanks for the fix! I've included it in the v6.5.2 release.


win32 not available when using webpack 5 and path-browserify polyfill

https://github.com/APIDevTools/json-schema-ref-parser/blob/26d824b4b230f4ce2471f73401a4b6f7c7c67ac2/lib/util/convert-path-to-posix.ts#L10
win32 is not supported withe the path-browserify polyfill.  This currently causes a null failure.
Cannot read properties of null (reading 'sep')
at convertPathToPosix (convert-path-to-posix.js:12:1)

Fixed in v11.2.2


Allows an external NavigatorKey in the DialogService

It was a bad idea, since it makes more sense to directly configure it via GetX


Breaking changes in ba7a70a

Downloaded b394ccf to replace my existing a70313e installation has caused trouble, every entity is now duplicated with the suffix _2 at the end of the entity ID, and every automation and dashboard is now broken.
Not sure what exactly caused this, but after looking at the commits I'm pretty sure there's an breaking change in ba7a70a.
This is exactly why we need tagged releases so that we don't need to download untested experimental code... (ref. #38)
For anyone reading this, stay away from ba7a70a as well as the newer versions bef18eb and b394ccf until this issue has been resolved.
EDIT:
Rollback to a70313e seems to fix this issue, except some manual work to cleaning up the mess after the newer versions.
Rollback also has to be done manually, as the ability isn't available in HACS yet (see #41).

Do you have multiple fans?

No, just one.

How is this one resolved?
Why is the IDs duplicated, and why not revert? Bug not fixed!

Just because I have 1 fan, everyone else in the world should delete and rename 25 entities each, is that a good solution?
If there's a good reason to not revert, then that's perfectly fine, but I'm sure there's a way to make old IDs continue work, while using new IDs for new fans.

No, most people have only 1 fan. Including me. I had no issues, but I suspected having more fans could be your issue, as that’s a scenario I can’t test (easily).
As I had no problems with this version, I believe that’s the case for most people. If it happens to be a problem, just remove and add the fan again. It should take you less than 15 seconds.
The cause of this is most likely a fix that makes sure it doesn’t matter if you use upper or lowercase mac address. This might have created a new device with a new identifier in your case. It shouldn’t have, but that’s the only explanation I can see.


Removed addOnBlur property, and remove option when removing item

So addOnBlur property was not doing what is defined, it was used on a conditional to set clearValidation onBlur, it was losing classes as it can be seen when there is an error, the field was losing the validation classes.
Instead of "deselecting" the option remove it because it remains after removeItem, and affects when it has been created, deleted and created again as it does not enter a conditional (line 2303) and createItemCallback will not fire.

i'm not entirely sure that's how it should be. createcallback is only expected to fire the first time the item is created, after that, it's only unselected
might not be ideal, but still i don't see how i could merge this without breaking change.

Yeah I thought that too, just checking, and with the property addOnBlur what do you think?.

unless i'm missing something, addonblur is doing what it should be doing
the validation thing is required, see demo.html for examples

if you have a proposal to make:

make sure your pr doesn't break these demos
provide a demo of what's not working and how your pr solves it


iOS 9 minimum SDK?

Hello!
How can I still use Branch with iOS SDK 8 or do I have to update my entire SDK to use Branch? :smile:

Did you get it figured out? And for my info, how did you figure it out?


Problem in spawning multiple drones in Gazebo

I am not able to launch multi-uav-mavros-sitl with the latest firmware.
Here are the commands I am using:
cd catkin_ws/src/Firmware
git submodule update --init --recursive
make px4_sitl_default
make px4_sitl_default sitl_gazebo
source Tools/setup_gazebo.bash $(pwd) $(pwd)/build/px4_sitl_default
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$(pwd):$(pwd)/Tools/sitl_gazebo
roslaunch px4 multi_uav_mavros_sitl.launch
There is no error that shows up, but gazebo doesn't show 3 drones . It shows nothing. Neither are the drones connected over udp.
If I try to launch single_vehicle_spawn launch file , even that doesn't get launched.

Same issue. Have been trying to fix it for over a month. It was working on ubuntu 16 Ros kinetic few months back. @devs please fix this.

@k2shah can you please look into this and get this resolved. Similar sort of issues happened before, as I remember you and @bkueng were able to resolve this in the past.

hi @pravardhanreddy
I'm not able to set aside time to handle this at the current moment.
if you don't need the current firmware I mention here https://github.com/PX4/Firmware/issues/10430 that you can clone our labs fork https://github.com/StanfordMSL/Firmware/tree/multi-quad
last i checked it was working on 16/kinetic and 18/lunar
I will look into this as soon as some other tasks of mine have been resolved.

I had worked on the same script 2 months back and it was working properly. I don't have a backup of that PX4 firmware. Need ti find a solution to this asap.

if you clone our fork of the px4 repo at the multi-quad branch it should roll back the changes made to the udp port changes that were made

@k2shah what arguments should i use for make?

you should just be able to pull that branch form our fork and make as normal (after the git update)
git submodule update --init --recursive make px4_sitl_default make px4_sitl_default sitl_gazebo

I get the following error
Makefile:422: *** "px4_sitl_default cannot be the first argument. Use 'make help|list_config_targets' to get a list of all possible [configuration] targets.".  Stop.

it might just be make siti_default

hmm i don't remember the exact make line, check the simulation documentation the makes you need to run should be there

Ok so there is some progress. I used the following commands for make
make posix_sitl_default
make posix_sitl_deafult sitl_gazebo
First I tested for snigle vehicle simulation
roslaunch px4 mavros_posix_sitl.launch
The drone got spawned in gazebo with its motors spinning slowly for some reason, all the mavros topics were also listed under
rostopic list
but they are not publishing anything, when i do
rostopoic echo /mavros/imu/data
i get the following warning
WARNING: no messages received and simulated time is active. Is /clock being published?
I checked /clock it was publishing.
Seems like mavros is not able to connect to the drone.
I am testing on Ubuntu 18.04/melodic

same issue with multi vehicle
All the three vehicles are spawned, also with their motors spinning slowly (don't know why that is happening).
All the mavros topics are also listed under their respective namespaces but they are not publishing any data.

are you on 18? can you try a machine with 16 on it? I can try to clone and build when i have access to a linux machine

i am working on ubuntu16. I am also facing the same issue with https://github.com/StanfordMSL/Firmware/tree/multi-quad , motors are spinning slowly on in multi_uav launch. Also these drones are not getting connected over udp to QGC. Same is the the case for mavros_posix_sitl.launch.

Can you pipe the output of the launch file to a txt and send that to me/post it here

in the latest px4/Firmware repo, the only problem is with multi-uav launch. px4_sitl is not getting connected to simulator. Neither it is getting connected to QGC.
While roslaunch mavros_posix_sitl.launch works absolutely perfect and i am also able to control the drone using rosrun px4 mavros_offboard_posctl_test.py

That makes sense because the port were changed from udp to tcp. There's probably some gazebo <=> px4 port miss match happening

'source Tools/setup_gazebo.bash $(pwd) $(pwd)/build_posix_sitl_default
source Tools/setup_gazebo.bash $(pwd) $(pwd)/build/px4_sitl_default
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$(pwd)
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$(pwd)/Tools/sitl_gazebo
roslaunch px4 multi_uav_mavros_sitl.launch'
these are the set of commands
and the output is
started roslaunch server http://dharna-Latitude-E6420:41105/
SUMMARY
CLEAR PARAMETERS

/uav1/mavros/
/uav2/mavros/

PARAMETERS

/rosdistro: kinetic
/rosversion: 1.12.14
/uav1/mavros/cmd/use_comp_id_system_control: False
/uav1/mavros/conn/heartbeat_rate: 1.0
/uav1/mavros/conn/system_time_rate: 1.0
/uav1/mavros/conn/timeout: 10.0
/uav1/mavros/conn/timesync_rate: 10.0
/uav1/mavros/distance_sensor/hrlv_ez4_pub/field_of_view: 0.0
/uav1/mavros/distance_sensor/hrlv_ez4_pub/frame_id: hrlv_ez4_sonar
/uav1/mavros/distance_sensor/hrlv_ez4_pub/id: 0
/uav1/mavros/distance_sensor/hrlv_ez4_pub/orientation: PITCH_270
/uav1/mavros/distance_sensor/hrlv_ez4_pub/send_tf: True
/uav1/mavros/distance_sensor/hrlv_ez4_pub/sensor_position/x: 0.0
/uav1/mavros/distance_sensor/hrlv_ez4_pub/sensor_position/y: 0.0
/uav1/mavros/distance_sensor/hrlv_ez4_pub/sensor_position/z: -0.1
/uav1/mavros/distance_sensor/laser_1_sub/id: 3
/uav1/mavros/distance_sensor/laser_1_sub/orientation: PITCH_270
/uav1/mavros/distance_sensor/laser_1_sub/subscriber: True
/uav1/mavros/distance_sensor/lidarlite_pub/field_of_view: 0.0
/uav1/mavros/distance_sensor/lidarlite_pub/frame_id: lidarlite_laser
/uav1/mavros/distance_sensor/lidarlite_pub/id: 1
/uav1/mavros/distance_sensor/lidarlite_pub/orientation: PITCH_270
/uav1/mavros/distance_sensor/lidarlite_pub/send_tf: True
/uav1/mavros/distance_sensor/lidarlite_pub/sensor_position/x: 0.0
/uav1/mavros/distance_sensor/lidarlite_pub/sensor_position/y: 0.0
/uav1/mavros/distance_sensor/lidarlite_pub/sensor_position/z: -0.1
/uav1/mavros/distance_sensor/sonar_1_sub/id: 2
/uav1/mavros/distance_sensor/sonar_1_sub/orientation: PITCH_270
/uav1/mavros/distance_sensor/sonar_1_sub/subscriber: True
/uav1/mavros/fake_gps/eph: 2.0
/uav1/mavros/fake_gps/epv: 2.0
/uav1/mavros/fake_gps/fix_type: 3
/uav1/mavros/fake_gps/geo_origin/alt: 408.0
/uav1/mavros/fake_gps/geo_origin/lat: 47.3667
/uav1/mavros/fake_gps/geo_origin/lon: 8.55
/uav1/mavros/fake_gps/gps_rate: 5.0
/uav1/mavros/fake_gps/mocap_transform: True
/uav1/mavros/fake_gps/satellites_visible: 5
/uav1/mavros/fake_gps/tf/child_frame_id: fix
/uav1/mavros/fake_gps/tf/frame_id: map
/uav1/mavros/fake_gps/tf/listen: False
/uav1/mavros/fake_gps/tf/rate_limit: 10.0
/uav1/mavros/fake_gps/tf/send: False
/uav1/mavros/fake_gps/use_mocap: True
/uav1/mavros/fake_gps/use_vision: False
/uav1/mavros/fcu_protocol: v2.0
/uav1/mavros/fcu_url<EMAIL_ADDRESS>/uav1/mavros/gcs_url:
/uav1/mavros/global_position/child_frame_id: base_link
/uav1/mavros/global_position/frame_id: map
/uav1/mavros/global_position/gps_uere: 1.0
/uav1/mavros/global_position/rot_covariance: 99999.0
/uav1/mavros/global_position/tf/child_frame_id: base_link
/uav1/mavros/global_position/tf/frame_id: map
/uav1/mavros/global_position/tf/global_frame_id: earth
/uav1/mavros/global_position/tf/send: False
/uav1/mavros/global_position/use_relative_alt: True
/uav1/mavros/image/frame_id: px4flow
/uav1/mavros/imu/angular_velocity_stdev: 0.000349065850399
/uav1/mavros/imu/frame_id: base_link
/uav1/mavros/imu/linear_acceleration_stdev: 0.0003
/uav1/mavros/imu/magnetic_stdev: 0.0
/uav1/mavros/imu/orientation_stdev: 1.0
/uav1/mavros/local_position/frame_id: map
/uav1/mavros/local_position/tf/child_frame_id: base_link
/uav1/mavros/local_position/tf/frame_id: map
/uav1/mavros/local_position/tf/send: False
/uav1/mavros/local_position/tf/send_fcu: False
/uav1/mavros/mission/pull_after_gcs: True
/uav1/mavros/mocap/use_pose: True
/uav1/mavros/mocap/use_tf: False
/uav1/mavros/odometry/in/child_frame_id: base_link
/uav1/mavros/odometry/in/frame_id: odom
/uav1/mavros/odometry/in/frame_tf/body_frame_orientation: flu
/uav1/mavros/odometry/in/frame_tf/local_frame: local_origin_ned
/uav1/mavros/odometry/out/frame_tf/body_frame_orientation: frd
/uav1/mavros/odometry/out/frame_tf/local_frame: vision_ned
/uav1/mavros/plugin_blacklist: ['safety_area', '...
/uav1/mavros/plugin_whitelist: []
/uav1/mavros/px4flow/frame_id: px4flow
/uav1/mavros/px4flow/ranger_fov: 0.118682389136
/uav1/mavros/px4flow/ranger_max_range: 5.0
/uav1/mavros/px4flow/ranger_min_range: 0.3
/uav1/mavros/safety_area/p1/x: 1.0
/uav1/mavros/safety_area/p1/y: 1.0
/uav1/mavros/safety_area/p1/z: 1.0
/uav1/mavros/safety_area/p2/x: -1.0
/uav1/mavros/safety_area/p2/y: -1.0
/uav1/mavros/safety_area/p2/z: -1.0
/uav1/mavros/setpoint_accel/send_force: False
/uav1/mavros/setpoint_attitude/reverse_thrust: False
/uav1/mavros/setpoint_attitude/tf/child_frame_id: target_attitude
/uav1/mavros/setpoint_attitude/tf/frame_id: map
/uav1/mavros/setpoint_attitude/tf/listen: False
/uav1/mavros/setpoint_attitude/tf/rate_limit: 50.0
/uav1/mavros/setpoint_attitude/use_quaternion: False
/uav1/mavros/setpoint_position/mav_frame: LOCAL_NED
/uav1/mavros/setpoint_position/tf/child_frame_id: target_position
/uav1/mavros/setpoint_position/tf/frame_id: map
/uav1/mavros/setpoint_position/tf/listen: False
/uav1/mavros/setpoint_position/tf/rate_limit: 50.0
/uav1/mavros/setpoint_raw/thrust_scaling: 0.0
/uav1/mavros/setpoint_velocity/mav_frame: LOCAL_NED
/uav1/mavros/startup_px4_usb_quirk: True
/uav1/mavros/sys/disable_diag: False
/uav1/mavros/sys/min_voltage: 10.0
/uav1/mavros/target_component_id: 1
/uav1/mavros/target_system_id: 1
/uav1/mavros/tdr_radio/low_rssi: 40
/uav1/mavros/time/time_ref_source: fcu
/uav1/mavros/time/timesync_avg_alpha: 0.6
/uav1/mavros/time/timesync_mode: MAVLINK
/uav1/mavros/vibration/frame_id: base_link
/uav1/mavros/vision_pose/tf/child_frame_id: vision_estimate
/uav1/mavros/vision_pose/tf/frame_id: map
/uav1/mavros/vision_pose/tf/listen: False
/uav1/mavros/vision_pose/tf/rate_limit: 10.0
/uav1/mavros/vision_speed/listen_twist: True
/uav1/mavros/vision_speed/twist_cov: True
/uav1/rotors_description: <?xml version="1....
/uav2/mavros/cmd/use_comp_id_system_control: False
/uav2/mavros/conn/heartbeat_rate: 1.0
/uav2/mavros/conn/system_time_rate: 1.0
/uav2/mavros/conn/timeout: 10.0
/uav2/mavros/conn/timesync_rate: 10.0
/uav2/mavros/distance_sensor/hrlv_ez4_pub/field_of_view: 0.0
/uav2/mavros/distance_sensor/hrlv_ez4_pub/frame_id: hrlv_ez4_sonar
/uav2/mavros/distance_sensor/hrlv_ez4_pub/id: 0
/uav2/mavros/distance_sensor/hrlv_ez4_pub/orientation: PITCH_270
/uav2/mavros/distance_sensor/hrlv_ez4_pub/send_tf: True
/uav2/mavros/distance_sensor/hrlv_ez4_pub/sensor_position/x: 0.0
/uav2/mavros/distance_sensor/hrlv_ez4_pub/sensor_position/y: 0.0
/uav2/mavros/distance_sensor/hrlv_ez4_pub/sensor_position/z: -0.1
/uav2/mavros/distance_sensor/laser_1_sub/id: 3
/uav2/mavros/distance_sensor/laser_1_sub/orientation: PITCH_270
/uav2/mavros/distance_sensor/laser_1_sub/subscriber: True
/uav2/mavros/distance_sensor/lidarlite_pub/field_of_view: 0.0
/uav2/mavros/distance_sensor/lidarlite_pub/frame_id: lidarlite_laser
/uav2/mavros/distance_sensor/lidarlite_pub/id: 1
/uav2/mavros/distance_sensor/lidarlite_pub/orientation: PITCH_270
/uav2/mavros/distance_sensor/lidarlite_pub/send_tf: True
/uav2/mavros/distance_sensor/lidarlite_pub/sensor_position/x: 0.0
/uav2/mavros/distance_sensor/lidarlite_pub/sensor_position/y: 0.0
/uav2/mavros/distance_sensor/lidarlite_pub/sensor_position/z: -0.1
/uav2/mavros/distance_sensor/sonar_1_sub/id: 2
/uav2/mavros/distance_sensor/sonar_1_sub/orientation: PITCH_270
/uav2/mavros/distance_sensor/sonar_1_sub/subscriber: True
/uav2/mavros/fake_gps/eph: 2.0
/uav2/mavros/fake_gps/epv: 2.0
/uav2/mavros/fake_gps/fix_type: 3
/uav2/mavros/fake_gps/geo_origin/alt: 408.0
/uav2/mavros/fake_gps/geo_origin/lat: 47.3667
/uav2/mavros/fake_gps/geo_origin/lon: 8.55
/uav2/mavros/fake_gps/gps_rate: 5.0
/uav2/mavros/fake_gps/mocap_transform: True
/uav2/mavros/fake_gps/satellites_visible: 5
/uav2/mavros/fake_gps/tf/child_frame_id: fix
/uav2/mavros/fake_gps/tf/frame_id: map
/uav2/mavros/fake_gps/tf/listen: False
/uav2/mavros/fake_gps/tf/rate_limit: 10.0
/uav2/mavros/fake_gps/tf/send: False
/uav2/mavros/fake_gps/use_mocap: True
/uav2/mavros/fake_gps/use_vision: False
/uav2/mavros/fcu_protocol: v2.0
/uav2/mavros/fcu_url<EMAIL_ADDRESS>/uav2/mavros/gcs_url:
/uav2/mavros/global_position/child_frame_id: base_link
/uav2/mavros/global_position/frame_id: map
/uav2/mavros/global_position/gps_uere: 1.0
/uav2/mavros/global_position/rot_covariance: 99999.0
/uav2/mavros/global_position/tf/child_frame_id: base_link
/uav2/mavros/global_position/tf/frame_id: map
/uav2/mavros/global_position/tf/global_frame_id: earth
/uav2/mavros/global_position/tf/send: False
/uav2/mavros/global_position/use_relative_alt: True
/uav2/mavros/image/frame_id: px4flow
/uav2/mavros/imu/angular_velocity_stdev: 0.000349065850399
/uav2/mavros/imu/frame_id: base_link
/uav2/mavros/imu/linear_acceleration_stdev: 0.0003
/uav2/mavros/imu/magnetic_stdev: 0.0
/uav2/mavros/imu/orientation_stdev: 1.0
/uav2/mavros/local_position/frame_id: map
/uav2/mavros/local_position/tf/child_frame_id: base_link
/uav2/mavros/local_position/tf/frame_id: map
/uav2/mavros/local_position/tf/send: False
/uav2/mavros/local_position/tf/send_fcu: False
/uav2/mavros/mission/pull_after_gcs: True
/uav2/mavros/mocap/use_pose: True
/uav2/mavros/mocap/use_tf: False
/uav2/mavros/odometry/in/child_frame_id: base_link
/uav2/mavros/odometry/in/frame_id: odom
/uav2/mavros/odometry/in/frame_tf/body_frame_orientation: flu
/uav2/mavros/odometry/in/frame_tf/local_frame: local_origin_ned
/uav2/mavros/odometry/out/frame_tf/body_frame_orientation: frd
/uav2/mavros/odometry/out/frame_tf/local_frame: vision_ned
/uav2/mavros/plugin_blacklist: ['safety_area', '...
/uav2/mavros/plugin_whitelist: []
/uav2/mavros/px4flow/frame_id: px4flow
/uav2/mavros/px4flow/ranger_fov: 0.118682389136
/uav2/mavros/px4flow/ranger_max_range: 5.0
/uav2/mavros/px4flow/ranger_min_range: 0.3
/uav2/mavros/safety_area/p1/x: 1.0
/uav2/mavros/safety_area/p1/y: 1.0
/uav2/mavros/safety_area/p1/z: 1.0
/uav2/mavros/safety_area/p2/x: -1.0
/uav2/mavros/safety_area/p2/y: -1.0
/uav2/mavros/safety_area/p2/z: -1.0
/uav2/mavros/setpoint_accel/send_force: False
/uav2/mavros/setpoint_attitude/reverse_thrust: False
/uav2/mavros/setpoint_attitude/tf/child_frame_id: target_attitude
/uav2/mavros/setpoint_attitude/tf/frame_id: map
/uav2/mavros/setpoint_attitude/tf/listen: False
/uav2/mavros/setpoint_attitude/tf/rate_limit: 50.0
/uav2/mavros/setpoint_attitude/use_quaternion: False
/uav2/mavros/setpoint_position/mav_frame: LOCAL_NED
/uav2/mavros/setpoint_position/tf/child_frame_id: target_position
/uav2/mavros/setpoint_position/tf/frame_id: map
/uav2/mavros/setpoint_position/tf/listen: False
/uav2/mavros/setpoint_position/tf/rate_limit: 50.0
/uav2/mavros/setpoint_raw/thrust_scaling: 0.0
/uav2/mavros/setpoint_velocity/mav_frame: LOCAL_NED
/uav2/mavros/startup_px4_usb_quirk: True
/uav2/mavros/sys/disable_diag: False
/uav2/mavros/sys/min_voltage: 10.0
/uav2/mavros/target_component_id: 1
/uav2/mavros/target_system_id: 2
/uav2/mavros/tdr_radio/low_rssi: 40
/uav2/mavros/time/time_ref_source: fcu
/uav2/mavros/time/timesync_avg_alpha: 0.6
/uav2/mavros/time/timesync_mode: MAVLINK
/uav2/mavros/vibration/frame_id: base_link
/uav2/mavros/vision_pose/tf/child_frame_id: vision_estimate
/uav2/mavros/vision_pose/tf/frame_id: map
/uav2/mavros/vision_pose/tf/listen: False
/uav2/mavros/vision_pose/tf/rate_limit: 10.0
/uav2/mavros/vision_speed/listen_twist: True
/uav2/mavros/vision_speed/twist_cov: True
/uav2/rotors_description: <?xml version="1....
/use_sim_time: True

NODES
/uav1/
iris_1_spawn (gazebo_ros/spawn_model)
mavros (mavros/mavros_node)
sitl_1 (px4/px4)
/uav2/
iris_2_spawn (gazebo_ros/spawn_model)
mavros (mavros/mavros_node)
sitl_2 (px4/px4)
/
gazebo (gazebo_ros/gzserver)
gazebo_gui (gazebo_ros/gzclient)
auto-starting new master
process[master]: started with pid [8007]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to c31b841a-3288-11e9-8209-2477030c6464
process[rosout-1]: started with pid [8020]
started core service [/rosout]
process[gazebo-2]: started with pid [8046]
process[gazebo_gui-3]: started with pid [8051]
process[uav1/sitl_1-4]: started with pid [8120]
INFO  [Unknown] Creating symlink /home/dharna/catkin_ws/src/swarm/ROMFS/px4fmu_common -> /home/dharna/.ros/etc

| ___ \ \ \ / /   /   |
| |/ /  \ V /   / /| |
|  __/   /   \  / /| |
| |     / /^\ \ ___  |
_|     /   /     |_/
px4 starting.
INFO  [Unknown] Calling startup script: bash etc/init.d-posix/rcS 1
1061 WARNING: setRealtimeSched failed (not run as root?)
process[uav1/iris_1_spawn-5]: started with pid [8130]
process[uav1/mavros-6]: started with pid [8132]
[ INFO] [1550389860.314789502]: FCU URL: udp://:14541@localhost:14558
[ INFO] [1550389860.318867758]: udp0: Bind address: <IP_ADDRESS>:14541
[ INFO] [1550389860.319117469]: udp0: Remote address: <IP_ADDRESS>:14558
[ INFO] [1550389860.319338769]: GCS bridge disabled
[ INFO] [1550389860.399793056]: Plugin 3dr_radio loaded
[ INFO] [1550389860.403510661]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1550389860.409261684]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[ INFO] [1550389860.415035599]: Plugin 3dr_radio initialized
[ INFO] [1550389860.415353997]: Plugin actuator_control loaded
[ INFO] [1550389860.431431558]: Plugin actuator_control initialized
[ INFO] [1550389860.438984893]: Plugin adsb loaded
[ INFO] [1550389860.442818725]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1550389860.448500549]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[ INFO] [1550389860.461288757]: Plugin adsb initialized
[ INFO] [1550389860.461752063]: Plugin altitude loaded
[ INFO] [1550389860.467336322]: Plugin altitude initialized
[ INFO] [1550389860.467884193]: Plugin cam_imu_sync loaded
[ INFO] [1550389860.470489438]: Plugin cam_imu_sync initialized
[ INFO] [1550389860.470910997]: Plugin command loaded
[ INFO] [1550389860.502763344]: Plugin command initialized
[ INFO] [1550389860.503143205]: Plugin companion_process_status loaded
process[uav2/sitl_2-7]: started with pid [8305]
process[uav2/iris_2_spawn-8]: started with pid [8308]
INFO  [Unknown] Creating symlink /home/dharna/catkin_ws/src/swarm/ROMFS/px4fmu_common -> /home/dharna/.ros/etc
67 WARNING: setRealtimeSched failed (not run as root?)
process[uav2/mavros-9]: started with pid [8317]
[ INFO] [1550389860.548908683]: Plugin companion_process_status initialized
[ INFO] [1550389860.549544812]: Plugin debug_value loaded

| ___ \ \ \ / /   /   |
| |/ /  \ V /   / /| |
|  __/   /   \  / /| |
| |     / /^\ \ ___  |
_|     /   /     |_/
px4 starting.
INFO  [Unknown] Calling startup script: bash etc/init.d-posix/rcS 2
[ INFO] [1550389860.579316872]: Plugin debug_value initialized
[ INFO] [1550389860.579535748]: Plugin distance_sensor blacklisted
[ INFO] [1550389860.579901943]: Plugin fake_gps loaded
INFO  [dataman] Unknown restart, data manager file './dataman' size is 11405132 bytes
INFO  [simulator] Waiting for initial data on UDP port 14561. Please start the flight simulator to proceed..
[ INFO] [1550389860.696384317]: Plugin fake_gps initialized
[ INFO] [1550389860.696689844]: Plugin ftp loaded

MAV_SYS_ID: curr: 1 -> new: 2
[ INFO] [1550389860.769643547]: Plugin ftp initialized
[ INFO] [1550389860.770027429]: Plugin global_position loaded
INFO  [dataman] Unknown restart, data manager file './dataman' size is 11405132 bytes
INFO  [simulator] Waiting for initial data on UDP port 14562. Please start the flight simulator to proceed..
[ INFO] [1550389860.947531075]: Plugin global_position initialized
[ INFO] [1550389860.947759045]: Plugin gps_rtk loaded
[ INFO] [1550389860.964348934]: Plugin gps_rtk initialized
[ INFO] [1550389860.964798352]: Plugin hil loaded
[ INFO] [1550389861.075730897]: Plugin hil initialized
[ INFO] [1550389861.076273155]: Plugin home_position loaded
[ INFO] [1550389861.090836251]: FCU URL: udp://:14542@localhost:14559
[ INFO] [1550389861.094848120]: udp0: Bind address: <IP_ADDRESS>:14542
[ INFO] [1550389861.095048616]: udp0: Remote address: <IP_ADDRESS>:14559
[ INFO] [1550389861.095229647]: GCS bridge disabled
[ INFO] [1550389861.118014535]: Plugin home_position initialized
[ INFO] [1550389861.118441224]: Plugin imu loaded
[ INFO] [1550389861.166815149]: Plugin imu initialized
[ INFO] [1550389861.167247332]: Plugin local_position loaded
[ INFO] [1550389861.172618968]: Plugin 3dr_radio loaded
[ INFO] [1550389861.185669978]: Plugin 3dr_radio initialized
[ INFO] [1550389861.185884741]: Plugin actuator_control loaded
[ INFO] [1550389861.217428536]: Plugin actuator_control initialized
[ INFO] [1550389861.224770533]: Plugin adsb loaded
[ INFO] [1550389861.227142012]: Plugin local_position initialized
[ INFO] [1550389861.227536616]: Plugin log_transfer loaded
[ INFO] [1550389861.250207298]: Plugin adsb initialized
[ INFO] [1550389861.250483752]: Plugin altitude loaded
[ INFO] [1550389861.266300690]: Plugin altitude initialized
[ INFO] [1550389861.266677794]: Plugin cam_imu_sync loaded
[ INFO] [1550389861.266874179]: Plugin log_transfer initialized
[ INFO] [1550389861.267164280]: Plugin manual_control loaded
[ INFO] [1550389861.272174722]: Plugin cam_imu_sync initialized
[ INFO] [1550389861.272465020]: Plugin command loaded
[ INFO] [1550389861.324106338]: Plugin manual_control initialized
[ INFO] [1550389861.324364405]: Plugin mocap_pose_estimate loaded
[ INFO] [1550389861.357109242]: Plugin command initialized
[ INFO] [1550389861.357391029]: Plugin companion_process_status loaded
[ INFO] [1550389861.397112647]: Plugin companion_process_status initialized
[ INFO] [1550389861.397375461]: Plugin debug_value loaded
[ INFO] [1550389861.409347131]: Plugin mocap_pose_estimate initialized
[ INFO] [1550389861.409721697]: Plugin obstacle_distance loaded
[ INFO] [1550389861.428897588]: Plugin obstacle_distance initialized
[ INFO] [1550389861.429199439]: Plugin odom loaded
SpawnModel script started
[ INFO] [1550389861.460216024]: Plugin debug_value initialized
[ INFO] [1550389861.460310443]: Plugin distance_sensor blacklisted
[ INFO] [1550389861.460661650]: Plugin fake_gps loaded
[ INFO] [1550389861.515349364]: Plugin odom initialized
[ INFO] [1550389861.515647575]: Plugin param loaded
[ INFO] [1550389861.562624827]: Plugin param initialized
[ INFO] [1550389861.562876494]: Plugin px4flow loaded
[ INFO] [1550389861.633844317]: Plugin fake_gps initialized
[ INFO] [1550389861.634286275]: Plugin ftp loaded
[ INFO] [1550389861.645669722]: Plugin px4flow initialized
[ INFO] [1550389861.645747705]: Plugin rangefinder blacklisted
[ INFO] [1550389861.646004824]: Plugin rc_io loaded
[ INFO] [1550389861.683507406]: Plugin rc_io initialized
[ INFO] [1550389861.683591964]: Plugin safety_area blacklisted
[ INFO] [1550389861.683879235]: Plugin setpoint_accel loaded
[ INFO] [1550389861.694090091]: Plugin ftp initialized
[ INFO] [1550389861.694384473]: Plugin global_position loaded
[INFO] [1550389861.725809, 0.000000]: Loading model XML from ros parameter
[ INFO] [1550389861.741422096]: Plugin setpoint_accel initialized
[ INFO] [1550389861.742191285]: Plugin setpoint_attitude loaded
[INFO] [1550389861.752450, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
[ INFO] [1550389861.840405855]: Plugin setpoint_attitude initialized
[ INFO] [1550389861.840715527]: Plugin setpoint_position loaded
[ INFO] [1550389861.863877606]: Plugin global_position initialized
[ INFO] [1550389861.864152291]: Plugin gps_rtk loaded
[ INFO] [1550389861.885756473]: Plugin gps_rtk initialized
[ INFO] [1550389861.886059045]: Plugin hil loaded
[ INFO] [1550389861.960818540]: Plugin setpoint_position initialized
[ INFO] [1550389861.961167729]: Plugin setpoint_raw loaded
SpawnModel script started
[ INFO] [1550389861.994307609]: Plugin hil initialized
[ INFO] [1550389861.994672861]: Plugin home_position loaded
[ INFO] [1550389862.022441147]: Plugin home_position initialized
[ INFO] [1550389862.022735386]: Plugin imu loaded
[ INFO] [1550389862.044204282]: Plugin setpoint_raw initialized
[ INFO] [1550389862.044539006]: Plugin setpoint_velocity loaded
[INFO] [1550389862.084287, 0.000000]: Loading model XML from ros parameter
[INFO] [1550389862.097126, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
[ INFO] [1550389862.101488396]: Plugin setpoint_velocity initialized
[ INFO] [1550389862.101673555]: Plugin imu initialized
[ INFO] [1550389862.101865457]: Plugin sys_status loaded
[ INFO] [1550389862.101943264]: Plugin local_position loaded
[ INFO] [1550389862.164474317]: Plugin local_position initialized
[ INFO] [1550389862.164691395]: Plugin log_transfer loaded
[ INFO] [1550389862.188456503]: Plugin log_transfer initialized
[ INFO] [1550389862.188815850]: Plugin manual_control loaded
[ INFO] [1550389862.197879986]: Plugin sys_status initialized
[ INFO] [1550389862.198147405]: Plugin sys_time loaded
[ INFO] [1550389862.217941310]: Plugin manual_control initialized
[ INFO] [1550389862.218261081]: Plugin mocap_pose_estimate loaded
[ INFO] [1550389862.287074009]: TM: Timesync mode: MAVLINK
[ INFO] [1550389862.290693995]: Plugin mocap_pose_estimate initialized
[ INFO] [1550389862.290933877]: Plugin obstacle_distance loaded
[ INFO] [1550389862.299423680]: Plugin sys_time initialized
[ INFO] [1550389862.299630224]: Plugin trajectory loaded
[ INFO] [1550389862.320469336]: Plugin obstacle_distance initialized
[ INFO] [1550389862.320882256]: Plugin odom loaded
[INFO] [1550389862.370731, 0.000000]: Calling service /gazebo/spawn_urdf_model
[ INFO] [1550389862.382071580]: Plugin trajectory initialized
[ INFO] [1550389862.382526527]: Plugin vfr_hud loaded
[ INFO] [1550389862.391453163]: Plugin vfr_hud initialized
[ INFO] [1550389862.391543271]: Plugin vibration blacklisted
[ INFO] [1550389862.391788525]: Plugin vision_pose_estimate loaded
[INFO] [1550389862.409694, 0.000000]: Calling service /gazebo/spawn_urdf_model
[ INFO] [1550389862.433322104, 0.002000000]: Plugin odom initialized
[ INFO] [1550389862.433664429, 0.002000000]: Plugin param loaded
[ INFO] [1550389862.458906958, 0.002000000]: Plugin param initialized
[ INFO] [1550389862.459156308, 0.002000000]: Plugin px4flow loaded
[ INFO] [1550389862.517060660, 0.002000000]: Plugin vision_pose_estimate initialized
[ INFO] [1550389862.517351737, 0.002000000]: Plugin vision_speed_estimate loaded
[ INFO] [1550389862.554934634, 0.002000000]: Plugin px4flow initialized
[ INFO] [1550389862.555003542, 0.002000000]: Plugin rangefinder blacklisted
[ INFO] [1550389862.555224811, 0.002000000]: Plugin rc_io loaded
[ INFO] [1550389862.572227056, 0.002000000]: Plugin vision_speed_estimate initialized
[ INFO] [1550389862.572536652, 0.002000000]: Plugin waypoint loaded
[ INFO] [1550389862.578566288, 0.002000000]: Plugin rc_io initialized
[ INFO] [1550389862.578806705, 0.002000000]: Plugin safety_area blacklisted
[ INFO] [1550389862.579162141, 0.002000000]: Plugin setpoint_accel loaded
[ INFO] [1550389862.608808124, 0.002000000]: Plugin setpoint_accel initialized
[ INFO] [1550389862.609102320, 0.002000000]: Plugin setpoint_attitude loaded
[ INFO] [1550389862.615642949, 0.002000000]: Plugin waypoint initialized
[ INFO] [1550389862.616028108, 0.002000000]: Plugin wind_estimation loaded
[ INFO] [1550389862.621722916, 0.002000000]: Plugin wind_estimation initialized
[ INFO] [1550389862.621820599, 0.002000000]: Autostarting mavlink via USB on PX4
[ INFO] [1550389862.621934716, 0.002000000]: Built-in SIMD instructions: SSE, SSE2
[ INFO] [1550389862.622004356, 0.002000000]: Built-in MAVLink package version: 2019.1.12
[ INFO] [1550389862.622067347, 0.002000000]: Known MAVLink dialects: common ardupilotmega ASLUAV autoquad icarous matrixpilot paparazzi slugs standard uAvionix ualberta
[ INFO] [1550389862.622138578, 0.002000000]: MAVROS started. MY ID 1.240, TARGET ID 1.1
[ INFO] [1550389862.663132821, 0.002000000]: Plugin setpoint_attitude initialized
[ INFO] [1550389862.663553716, 0.002000000]: Plugin setpoint_position loaded
[ INFO] [1550389862.707893759, 0.002000000]: Plugin setpoint_position initialized
[ INFO] [1550389862.708246518, 0.002000000]: Plugin setpoint_raw loaded
[ INFO] [1550389862.738470856, 0.002000000]: Plugin setpoint_raw initialized
[ INFO] [1550389862.738770896, 0.002000000]: Plugin setpoint_velocity loaded
[ INFO] [1550389862.758456200, 0.002000000]: Plugin setpoint_velocity initialized
[ INFO] [1550389862.758794302, 0.002000000]: Plugin sys_status loaded
[ INFO] [1550389862.792082267, 0.002000000]: Plugin sys_status initialized
[ INFO] [1550389862.792388718, 0.002000000]: Plugin sys_time loaded
[INFO] [1550389862.810306, 0.006000]: Spawn status: SpawnModel: Successfully spawned entity
[ INFO] [1550389862.832254214, 0.028000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1550389862.835910493, 0.030000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1550389862.854774197, 0.046000000]: TM: Timesync mode: MAVLINK
[ INFO] [1550389862.886027833, 0.076000000]: Plugin sys_time initialized
[ INFO] [1550389862.886279885, 0.076000000]: Plugin trajectory loaded
[ INFO] [1550389862.989636803, 0.166000000]: Plugin trajectory initialized
[ INFO] [1550389862.989974770, 0.166000000]: Plugin vfr_hud loaded
[ INFO] [1550389862.994598504, 0.172000000]: Plugin vfr_hud initialized
[ INFO] [1550389862.994684776, 0.172000000]: Plugin vibration blacklisted
[ INFO] [1550389862.994910035, 0.172000000]: Plugin vision_pose_estimate loaded
[uav1/iris_1_spawn-5] process has finished cleanly
log file: /home/dharna/.ros/log/c31b841a-3288-11e9-8209-2477030c6464/uav1-iris_1_spawn-5*.log
[ INFO] [1550389863.147705844, 0.182000000]: Plugin vision_pose_estimate initialized
[ INFO] [1550389863.148091253, 0.182000000]: Plugin vision_speed_estimate loaded
[ INFO] [1550389863.176535334, 0.182000000]: Plugin vision_speed_estimate initialized
[ INFO] [1550389863.176960349, 0.182000000]: Plugin waypoint loaded
[ INFO] [1550389863.197110139, 0.182000000]: Plugin waypoint initialized
[ INFO] [1550389863.197406433, 0.182000000]: Plugin wind_estimation loaded
[ INFO] [1550389863.199601794, 0.182000000]: Plugin wind_estimation initialized
[ INFO] [1550389863.199950168, 0.182000000]: Autostarting mavlink via USB on PX4
[ INFO] [1550389863.200173915, 0.182000000]: Built-in SIMD instructions: SSE, SSE2
[ INFO] [1550389863.200355683, 0.182000000]: Built-in MAVLink package version: 2019.1.12
[ INFO] [1550389863.200512045, 0.182000000]: Known MAVLink dialects: common ardupilotmega ASLUAV autoquad icarous matrixpilot paparazzi slugs standard uAvionix ualberta
[ INFO] [1550389863.200660093, 0.182000000]: MAVROS started. MY ID 1.240, TARGET ID 2.1
[INFO] [1550389863.280613, 0.182000]: Spawn status: SpawnModel: Successfully spawned entity
[ INFO] [1550389863.351270329, 0.234000000]: Physics dynamic reconfigure ready.
[ INFO] [1550389863.356624835, 0.244000000]: Physics dynamic reconfigure ready.
[uav2/iris_2_spawn-8] process has finished cleanly
log file: /home/dharna/.ros/log/c31b841a-3288-11e9-8209-2477030c6464/uav2-iris_2_spawn-8*.log

I've done a fresh setup of Ros and Firmware, tree/multiuav one ...and the drones are up and properly connected to gazebo as well as QGC.
The only error I am getting now is that sensors fail ,Timeout

ERROR [sensors] Accel #0 fail:  STALE!
ERROR [sensors] Sensor Accel #0 failed. Reconfiguring sensor priorities.
WARN  [sensors] Remaining sensors after failover event 0: Accel #0 priority: 1
WARN  [sensors] Remaining sensors after failover event 0: Accel #1 priority: 1

The problem is solved after  git submodule update --init --recursive
Thank you @k2shah .Kindly update here about the latest firmware port updates

@DharnaNar is this resolved then and I can close the issue?

Related: https://github.com/PX4/Firmware/pull/11479

Temporarily this issue is resolved, but the ports issue for multi uav is not yet resolved for the latest firmware.

ports issue for?

Spawning multiple UAVs and connecting them over tcp or udp

It is still not working on Ubuntu 18.04/melodic. With the px4/firmware master, gazebo tries to open up but is stuck there nothing is shown, not even an empty world. The problem seems to be with single_vehicle_spawn.launch. With the StanfordMSL/Firmware/tree/multi-quad, the quads are spawning properly but are not publishing anything on the mavros topics. All the topics are listed when i do rostopic list but no data seems to be published on them (checked using rostopic echo).

Connecting multiuavs px4_sitl over udp to QGC and Gazebo simulator in the latest firmware

Connecting multiuavs px4_sitl over udp to QGC and Gazebo simulator in the latest firmware

StanfordMSL/Firmware/tree/multi-quad , quads are spawning and publishing on Ros topics on Ubuntu 16 and I am able to control these individually from py scripts

I found there is a port issue in the master version because of the mavlink_tcp_port.
I change and pull request at #11479  with PX4/sitl_gazebo.
It is working on Ubuntu 18.04/gazebo 7

https://github.com/PX4/Firmware/pull/11479 and https://github.com/PX4/Firmware/pull/11498 have been merged, this should work now. Please re-open if you still have issues, thanks.


[usecase] Add usecase for WebGl Video Texture

Impacted tests(approved): new 1, update 0, delete 0
Unit test platform: Crosswalk for Android 15.43.354.0
Unit test result summary: pass 0, fail 1, block 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-4183

I don't think this has addressed the issue https://crosswalk-project.org/jira/browse/XWALK-4143.
Close it as-is.


x/playground: 1.16 not available

What version of Go are you using (go version)?
go1.15.8
Does this issue reproduce with the latest release?
No.
What operating system and processor architecture are you using (go env)?
Not relevant (documentation issue)
What did you do?
Click "Run" on the filepath.Walk example on golang.org
https://golang.org/pkg/path/filepath/#Walk
What did you expect to see?
The output
What did you see instead?
A build error
prog.go:5:2: package io/fs is not in GOROOT (/usr/local/go-faketime/src/io/fs)

Conclusion
The system running golang.org's documentation examples should run the examples using the same version of go for which the examples were written.

This could also be interpreted as a breaking change.
https://github.com/golang/go/commit/7bb721b9384bdd196befeaed593b185f7f2a5589#diff-d2cc84019d3937e8eb23359f2f22350975e20f0d7ad70c4d8fae7800c7123409L353-R354
- type WalkFunc func(path string, info os.FileInfo, err error) error
+ type WalkFunc func(path string, info fs.FileInfo, err error) error

Thanks for reporting.
CC @golang/release.

@dmitshur can you help merge it? thanks

Is a language truly backward compatible if its documented examples are not?
I created this issue after spending a lot of time googling for Go 1.15 documentation to find a WalkFunc signature that worked with the version of Go I was using. I never found it. I've been working with go for 8 years and I've never needed to do this before. I had to go to the 1.15 source code to find the correct syntax.
I believe @dreamerjackson's approach (reverting the docs) is correct.
De-aliasing existing method signatures (WalkFunc) and examples (Walk) in a way that causes them to not work in older versions of the language should be considered a breaking change.
Is backward compatibility not the primary reason for aliases to exist?
Should the privilege of backward compatibility not extend to documented examples?
Reverting all instances of fs.FileInfo to os.FileInfo in all examples would require a few more changes. See https://github.com/golang/go/commit/7bb721b9384bdd196befeaed593b185f7f2a5589

https://golang.org/pkg/os/#example_FileMode
https://golang.org/pkg/net/http/#example_FileServer_dotFileHiding
https://golang.org/pkg/errors/#example_As
https://golang.org/pkg/errors/#example_Is

pkg.go.dev has docs for past versions of the stdlib: https://pkg.go.dev/path/filepath?tab=versions
redirecting golang.org/pkg is #44356

By the definitions used by the Go project, this is not a breaking change, because the code that worked with 1.15 continues to work fine with Go 1.16.  The problem here is that code that works with Go 1.16 does not work with Go 1.15.  And, of course, that is always true for every new release: code that works with the new release does not work with the old release.
I don't agree that we should change the Go 1.16 docs to work with Go 1.15.  If you are using Go 1.15, use the Go 1.15 docs.
But for documentation and code that is maintained outside of the Go release process, then I agree that that documentation should continue to work with Go 1.15 as long as 1.15 is supported.

The Playground Dockerfile needs an update to work with Go 1.16, due to assumptions it makes about GOPATH behavior for old tour snippets. This prevented the playground from updating with this release, and is why the newer demo code doesn't work.
I'll take a look.

Fixed and deployed.

Confirmed, tyvm!


Configuring Multiple Providers

Hi,
Is there a way to configure multiple providers? We need to send from one of multiple SMTP server and or Sendgrid within the same application. Can you configure this at point of sending instead of at startup?
Thanks

Hi,
I had same problem. and found solution for this.
You could use Sender property from FluentEmail to specify which type of SMTP you want to use.

Just following up on this some years after to say that you can register multiple instances of fluent email & multiple senders if you avoid the helper methods (such as AddFluentEmail) and instead register everything yourself.
As an example, I registered the following services...
builder.Services.AddSingleton<ITemplateRenderer, ReplaceRenderer>(sp => new ReplaceRenderer());
builder.Services.AddKeyedSingleton<ISender>("mailgun",
  (sp, k) => new MailgunSender("{my sender}", "{my key}"));
builder.Services.AddKeyedSingleton<IFluentEmail>("mailgun",
  (sp, k) => new Email(sp.GetService<ITemplateRenderer>(), sp.GetKeyedService<ISender>(k), "{my email}"));

That all worked as expected, such that I can now request the "mailgun" instance of IFluentEmail. Clearly you could also register various other versions of the same thing.
Hope this helps someone!


Inserting raw text for .token.parameter causes difficulties theming Typescript

Motivation
In Typescript I want to theme parameter names and their types separately, but sometimes this is not possible at all due to raw text that cannot be tracked by CSS rules.
Description
When a type for a parameter is not a builtin or styled otherwise, this happens when styling .token.parameter:

The generated HTML just inserts the parameter and the type as plain text:

As you can see, the strings are written raw to the output without wrapping them at all. I can't even use :first-child to track the parameter name.

This one will be quite difficult to solve because we have to find a way to match a TypeScript type expression.
Also, when doing this correctly, we also have to match recursive type definitions. E.g.
function foo(a: T, b: (x: { [key: string]: any, value: T }, y: any = null) => T, ...c: T[]) {}


Jeff Schaller: Watch teqhow.com

Jeff Schaller requests the watch of the watch_keyword teqhow\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

teqhow\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Not registered with the bower package registry

Nowhere to be found with bower. :crying_cat_face:

I'll take care of that later tonight ;)

Awesome! :+1:

Should be all set now!


Updating Data with new features

Adding new features in Data class:

[ ] Storaging features_names in new field
[ ] Storaging features_types in new field
[ ] Storaging categorical_features in separetly new field or getting it with function from features_types
[ ] Loading data from .npy format with new classmethod InputData.from_npy(...)
[ ] Loading data from .arff format with new classmethod InputData.from_arff(...)
[ ] ~Loading data with OpenML API by dataset id or name with new classmethod InputData.from_openml(...)~

Добавил бы from_df()

https://github.com/aimclub/FEDOT/issues/511 перекликается с этим


Unknown platform error under FreeBSD

buildhost /tmp/cargo # python -B src/etc/install-deps.py
Traceback (most recent call last):
  File "src/etc/install-deps.py", line 33, in <module>
    raise "Unknown platform"
TypeError: exceptions must be old-style classes or derived from BaseException, not str
zsh: exit 1     python -B src/etc/install-deps.py

Are you serious? Isn't python supposed to be cross platform? FreeBSD is far more advanced than most Linuxes these days...

Right now Cargo is built Cargo, so what this badly-worded error message is saying is that there is no official snapshot of Cargo for FreeBSD.
Seems like a message we could improve though!

Message is fixed. It would be nice to rename this bugreport or to forward it somewhere to have official FreeBSD snaphost one day.

I don't think it's resolved issue. Under my system step "python -B src/etc/install-deps.py" isn't even required to build Cargo without more than one known issue with missing RPATH info in cargo binary #2198. I hacked LD_LIBRARY_PATH problem with wrapper and there's no more issues under FreeBSD.
Read - FreeBSD is already supported and works just fine. Thanks.

Also, for those who use FreeBSD:
Definition of Rust 1.5.0 for Sofin:
https://github.com/VerKnowSys/sofin-definitions/blob/stable/definitions/rust.def
Binary build:
http://software.verknowsys.com/binary/FreeBSD-11.0-amd64/Rust-1.5.0.txz
Definition includes function "install_cargo" that automatically installs cargo (not available in FreeBSD ports definition yet). Both hacks required to build are also included (line: 19 and wrapper: lines 28-31)

@dmilith although FreeBSD may have a snapshot it's not officially supported in the sense that we provide a guarantee that it will continue to work. I'd be fine taking patches to the snapshot download script, but we won't necessarily actively seek them out.


Use UriRegexRewrite to implement full path rewrite in Gateway API

Please provide a description of this PR:
Now that UriRegexRewrite is supported in HTTPRewrite https://github.com/istio/istio/pull/45398, the previous hack https://github.com/istio/istio/pull/42605 used to support full path rewrite from Gateway API is no longer needed.

Hi @wujiaqi. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@wujiaqi: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wujiaqi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

integ-ambient_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wujiaqi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

integ-ambient_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-ambient

integ-pilot_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wujiaqi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

integ-ambient_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-ambient

integ-pilot_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot

integ-cni_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wujiaqi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

integ-ambient_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-ambient

integ-pilot_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot

integ-cni_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-cni

integ-pilot-multicluster_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wujiaqi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

integ-ambient_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-ambient

integ-pilot_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot

integ-cni_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-cni

integ-pilot-multicluster_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest-required

@wujiaqi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot

integ-cni_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-cni

integ-pilot-multicluster_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote-mc

integ-ambient_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wujiaqi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot

integ-cni_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-cni

integ-pilot-multicluster_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote-mc

integ-ambient_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wujiaqi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot

integ-cni_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-cni

integ-pilot-multicluster_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-multicluster

integ-ambient_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wujiaqi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-istiodremote-mc

integ-pilot_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot

integ-cni_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-cni

integ-pilot-multicluster_istio
636b35bba0e77ddf689d0cd39337c674eaffa348
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


ITensors.MPS/ITensors.MPO graph interface layer

Move the ITensors.MPS/ITensors.MPO graph interface layer from https://github.com/ITensor/ITensorTDVP.jl/pull/43 into this package, once that PR is merged.
An interesting question that hits on some limitations of Julia's subtyping system is that it would be nice for ITensors.MPS/ITensors.MPO to work in the functions defined in these packages, once they adhere to the AbstractDataGraph interface. However, it is awkward to try to make them subtypes of AbstractDataGraph.
It's possible to do that without making ITensors.jl depend on the full DataGraphs.jl package by making an interface package DataGraphsCore.jl in the spirit of StaticArraysCore.jl but that seems a bit overkill. The alternative is to use traits implemented with the SimpleTraits.jl package, and define traits such as IsITensorNetwork or IsDataGraph which are then overloaded for ITensors.MPS/ITensors.MPO, but that also seems a bit overkill as well since then we would need to define all of the functions we currently define through abstract type dispatch with AbstractITensorNetwork or AbstractDataGraph with traits instead.
In the end, it may not matter so much since I think the ITensorNetworks.TreeTensorNetwork type will supersede the ITensors.MPS/ITensors.MPO types but be superior in a variety of ways, so we can just keep some simple interfacing functionality and have conversions from ITensors.MPS/ITensors.MPO to ITensorNetworks.TreeTensorNetwork.

Yeah this is where I wish Julia dispatch worked more along the lines of "check if a certain set of methods are defined for this type, if so it is a DataGraph" which I think is more how the new concepts system works in C++20.
By the IsDataGraph idea, do you mean something like:
const IsDataGraph = Union{DataGraph,MPS,MPO}

? Then later removing this once MPS and MPO are defined as a kind of graph?

We could do it through a union type since we have a finite number of types in mind, but the more general solution is defining them as traits from SimpleTraits.jl since that is more extensible (it would allow someone else to opt-in with their own tensor network or data graph type, without hard-coding it in a union type or with subtyping).
This may be overkill for this case anyway, mostly just bringing up the issue and summarizing the different potential solutions. Eventually I would imagine just deprecating ITensors.MPS and ITensors.MPO, but of course we want to make sure they continue to exist and have the same functionality they have now going into the future so that user code still works. But the general plan may be to just add new functionality for ITensorNetworks.TreeTensorNetwork. Depending on how things develop, ITensorTDVP.jl/ITensorSolvers.jl may be the right time to rip off the band-aid and move fulling to ITensorNetworks.TreeTensorNetwork once the functionality catches up to ITensors.AbstractMPS.

An interesting perspective is that ITensors.AbstractMPS can be views as an implicitly defined graph, as in the graph layout is implicitly defined as a path graph by the type. The interface layer in the file src/tree_patch.jl in Lander's PR just makes that explicit. This is similar to SpecialGraphs.PathGraph.
So we could imagine in the future people devising implicitly defined graphs (i.e. the edges and vertices are implied by the type but not explicitly stored). A concrete example of that is Vector{ITensor}, which implicitly defines a graph by the connectivity of the indices of the ITensors. So it may be nice to make Vector{ITensor} act like a DataGraph through a IsDataGraph trait and the edges are determined on the fly by commoninds, which would be impossible with subtyping. This may be very inefficient since it would be doing O(length(tn)^2) calls to hascommoninds, but it could be nice for making functionality like prime(::Vector{ITensor}) and more sophisticated versions that only prime the link indices "just work" using ITensorNetworks.jl functionality.


Multiple headers

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   93.17%   93.17%
=======================================
  Files          12       12
  Lines         806      806
=======================================
  Hits          751      751
  Misses         55       55

Impacted Files
Coverage Δ

crates/sipmsg/src/header.rs
87.23% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Allow stakers to collateralize their stake, via Ramp DeFi

suggestion from a community member @middlechildpabk to Bruce:
"I have two projects in mind that bring unique value, that I believe would help aid in the long term support and success of these marketplaces.
First is Ramp DeFi, their main focus is to provide a solution to the issues staking has already caused. (I.e. locked capital, staking rewards in native project tokens create sell pressure, etc.) They’re providing a way to collateralize investors’ locked tokens and unlock liquidity.
This way, it can incentivize investors to be more patient and have more confidence leaving their tokens to stake, whether that’s traditional APY staking platforms, or my thinking, something like in the data marketplace, staking on data sets.
the question in my mind for the data marketplace was, how do we create more confidence and patience in people staking OCEAN on data sets without them rushing to dump to take profits, leaving the market very volatile, resulting in more FUD. If OCEAN stakers could lock up their tokens, and then collateralize those tokens through Ramp (rStake), they could unlock that staked liquidity for further opportunities, while still keeping their staked positions and earning marketplace rewards."
Note by Trent: this could be very useful. People could do this independently of Ocean of course. But we could make it easy by having it integrated in Ocean Market. I'd hold off considering further until we ship Better IDOs (v4), as there may be unforeseen interactions.

Closing because redundant:

We have a general thread of activities for DeFi integrations. This fits there. And there are already projects on collateralizing, eg Injective
We have roadmap plans to make staking safer and more attractive to LPs


duplicate definitions with "go to definition" when using CommonJS require

Issue Type: Bug
When using the "go to definition" command on a javascript function imported with require, multiple identical definitions are shown which results in a 'peek' instead of jumping to the definition in the other file.
I disabled all extensions and created two minimal javascript files which demonstrate this. See image below:

When I select the second definition, nothing changes. The filename and function that are displayed are identical. Here's a screenshot anyway:

Code from screencap:
index.js
const importedFoo = require('./fooFile');

importedFoo.foo(4);

fooFile.js
exports.foo = function (x) {
    return x + 5;
}

VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (12 x 3498)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.90GB (8.07GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Should already be fixed in VS Code insiders (which includes TypeScript 3.9)