Running Under Docker Requires resetting proxy with http_proxy=""

Its late, and I wanted to make sure to get this logged in case I forgot.  I haven't seen this with anything else I've Dockerized, but recently Dockerizing a bot of mine I ran into a unique issue:
ERROR -- : Failed to open TCP connection to : (getaddrinfo: Name or service not known) (Faraday::ConnectionFailed)
An hour or so of sleuthing through slack-ruby-bot, slack-ruby-client, faraday and finally ruby (2.3)'s own net/http library led me to an interesting realization; it was using an HTTP proxy.  The problem was, the HTTP proxy specified by Docker was unrecognizable by Ruby's net libraries and consequently failed to determine its hostname... which unexpectedly didn't error out, but just returned nil for the entire proxy address.  :tada:
Ultimately, I temporarily got around this by including http_proxy="" in my command to start my bot.  This was Docker CE 17.06.1 on a Mac.  I'm uncertain as to if it affects any other platforms.
I'll try to track down where this would properly go; but figured that if nothing else - dropping a line in this project's README would help someone out if they stumbled upon this later.
I admit, my Docker knowledge is not very advanced and I may be mis-interpreting something - but again; wanted this searchable somewhere in case anyone else ran into it.  Feel free to close, I won't feel bad.

What's the proxy value specified?

Oh hai!  docker.for.mac.localhost:63074 is the value that Docker sets.
$ export | grep proxy
=> declare -x http_proxy="docker.for.mac.localhost:63074"
=> declare -x no_proxy="localhost, 127/8, localhost, 127/8"

I suspect that the port changes depending on environmental factors.  If it wasn't clear in my Issue; I am literally passing an empty value in to override the declare'd value.
$ http_proxy="" SLACK_API_TOKEN=super-secret bundle exec ruby ./cookiebot.rb
I'll get a chance to test if this happens on Docker in Linux either tonight or tomorrow night.

What's the configuration in the bot? Are you setting proxy or websocket_proxy in code?

Nope.  That was the weirdest part and what ultimately threw me for a gigantic loop.  net/http was automatically picking up the environment variable that Docker had set for http_proxy and going "Oh, let me use that proxy.".  In debugging, I reduced the bot down to:
#!/usr/bin/env ruby

require "slack-ruby-bot"

class CookieBot < SlackRubyBot::Bot; end

CookieBot.run

It's actually documented, https://docs.ruby-lang.org/en/2.0.0/Net/HTTP.html#class-Net::HTTP-label-Proxies.
I wouldn't assume that the problem is parsing and debug it. If it's a full proxy it should work, so I would try figuring out whether it's an SSL proxy, whether it supports websockets, etc., then potentially prefixing it with http:// or https:// to see if that helps. I am shooting in the dark though :)

Hehe, I was actually caught off guard because the proxy environment variable was set by Docker without my knowledge or intervention - hence having to track down what ERROR -- : Failed to open TCP connection to : (getaddrinfo: Name or service not known) (Faraday::ConnectionFailed) actually meant.
Ultimately, in tracing it down I found out that the specific value that Docker was setting it to resulted in net/http not being able to determine a hostname from the value and instead of throwing an error, it passes nil back up the call-stack which causes the "Name or service not known" (obviously, a hostname of nil won't resolve).
I guess, the crux of it is that I had no idea an http_proxy was being set in the brand new default environment and thus had no reason to suspect it was the cause of the issues.  The error message that bubbles up the chain ends up being rather uninformative as to what's going wrong (an invalid http_proxy value was set in the environment; but the error message from Faraday simply says "name or service not known").
As soon as I unset that environment variable, everything was happy days.  Its solved for me, but I was generally hoping this Issue might save someone else from having to figure out "Why doesn't this work on Docker for Mac?".  :)
I guess; 3 possible outcomes:

Update the README to include a note about this behavior (maybe if someone else could validate it happens for them as well?)
Add a guard clause to suggest possible reasons for Faraday::ConnectionFailed exceptions (I'd be happy to open a PR, but it might not be for a bit)
Close this issue and let Google serve as the next person's guide

(btw, thanks for being so responsive.  I love your library and have gotten a great deal of use out of it over the last 6 months or so)

I think we should update the README around proxy configuration saying that the default is not nil, but the value of ENV['http_proxy'] and link to the documentation for net/http. Care to do that?

Sounds like a plan!

Hey @phantomdata, I'm running into this same problem. I'm trying to get a bot dockerized and deployed to kubernetes. The image starts fine but I'm seeing the same 00:43:01 web.1  | E, [2017-12-28T00:43:01.545282 #16] ERROR -- : Failed to open TCP connection to slack.com:443 (getaddrinfo: Name or service not known) (Faraday::ConnectionFailed)
Did you ever get this resolved? I'm pretty new to docker and have a pretty basic docker file at the moment.
FROM ruby:2.3-onbuild
ENV LC_ALL C.UTF-8
ENV LANG en_US.UTF-8
ENV LANGUAGE en_US.UTF-8
CMD ["bash", "-l", "-c", "/usr/src/app/script/start.sh"]

I might be running into an issue with my cluster configuration actually... Might be unrelated.

:wave:  @jasonwc That's exactly what I did to get mine up and running (http_proxy="" bundle exec ...).  Did your cluster configuration end up having something to do with it?  If that container is able to run standard Unix network utilities (eg: ping) and can get out successfully; I'd start tracking down the value of that http_proxy variable in your program.  Maybe Foreman or another lib (dot-env perhaps?) is getting in the way somehow.
Let us know what you find out.  I'll probably update that README over the next few days, so if there's another reason for that Faraday::ConnectionFailed to confusingly popup; I'd love to see it added.
Thanks for reminding me about this issue, heh.  It had totally slipped my mind to update the README.

@dblock I've got a PR awaiting review for this over at https://github.com/slack-ruby/slack-ruby-bot/pull/174.  Happy New Year!  :)

Thanks for the docs @phantomdata, updated in https://github.com/slack-ruby/slack-ruby-bot/commit/c9ed35549c263cc82eb60a1fe8ec9632af980096.

Thanks @phantomdata and @dblock!
It turned out that I was running into an issue with my Kubernetes cluster. I basically did what you had suggested @phantomdata and tried to ping Google and Slack and wasn't able to get out. I then realized that my kube-dns pods were in a CrashLoopBackOff cycle and that was causing my networking issues. I'll make sure to verify that the http_proxy issue isn't present in Linux once I get my cluster sorted, but as I was debugging I wasn't seeing anything in the env that suggested that it was setting it.
Regardless, this issue was helpful in giving me a few things to try so thanks for the README update! This library has been super helpful for our internal slackbot and I'm hoping to find a chance to contribute back soon. I've been tooling around on a blog post about combining this library, docker, and kubernetes to make a sweet sweet bot cluster for interfacing with a lot of different services.

I came across this issue when investigating a similar error in a library that uses net/http so I wanted to leave a breadcrumb for others.
This error:
ERROR -- : Failed to open TCP connection to : (getaddrinfo: Name or service not known)
Is caused by http_proxy missing the http:// prefix. http_proxy="docker.for.mac.localhost:63074" in this case is not a valid proxy uri.


The models do not match activity any more.

Keras.version = 2.2.4
Tensorflow.version = 1.11.0
PyTorch = 1.0.0a0+ff608a9
I tried running the example and the activity does not match. Any ideas?

I find the same problem

That's a shame, I guess things don't stay the same and an update is needed.
I added a note in the README to warn users of this.


Fix typo in metrics page PersistenVolume -> PersistentVolume

Description
Fix typo
Issue
N/A

/hold
PR is modifying the auto generated page directly.

Previously @windsonsea  mentioned PR in K8s upstream to solve this problem

https://github.com/kubernetes/website/pull/47827

Maybe we do need to open this PR again?

PR https://github.com/kubernetes/kubernetes/pull/117540 is also dealing with this issue.


Fix "Server" heading spelling

This fixes the spelling of "Server" within the level 1 heading.
This will close issue #475.

Thank you!


Client-side Kubernetes Auth solution for AAD-enabled AKS clusters

Hey, I just made a Pull Request!
Need
The following PR addresses this user/integrator story:
As a Backstage integrator I want a client-side kubernetes auth solution for AKS clusters so that I can surface the status of AKS-deployed services in Backstage without granting high-powered privileges to a service account. This solution resolves #13685. See issue for more information.
Solution:
This is being done by:

Creation of a new Auth Provider and ApiRef built from the oauth2 implementation using the 6dae42f8-4368-4678-94ff-3960e28e3630/user.read scope.
Creation of a new KubernetesAuthProvider called AksKubernetesAuthProvider which consumes the above OAuthApi to get an access token and appends it to the kubernetes-backend request in a field like auth.microsoftaks
Creation of a new KubernetesAuthTranslator called AksKubernetesrAuthTranslator which receives the token from the auth.microsoftaks field in the request body and uses it as a service account token in requests to k8s

:heavy_check_mark: Checklist

[X] A changeset describing the change and affected packages. (more info)
[X] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[X] All your commits have a Signed-off-by line in the message. (more info)

It might not be necessary but it could be a good idea to raise this as 2 PRs, one to add the auth backend to Backstage and one to add the auth provider to the k8s plugin. I'll leave it up to you to decide though

It might not be necessary but it could be a good idea to raise this as 2 PRs, one to add the auth backend to Backstage and one to add the auth provider to the k8s plugin. I'll leave it up to you to decide though

Its definitely doable but the auth backend only works in the context of the k8s plugin, you wont be able to use this new provider for sign in with its current implementation as it was only made to access kubernetes resources in an AKS cluster. I figured it would be less confusing if we coupled it all together so reviewers can have the full picture.

@Rugvip @agentbellnorm Removing stale tag.

@Rugvip I have opened #16323, which enhances the microsoft auth provider to support some of the simplifying changes you've advocated for here. I'm hoping we can agree on that implementation first and then rebase this PR (in a much simpler form) to leverage those enhancements.

Closing PR. New solution will be provided making use of a single auth provider as suggested in the comments.


Telescope Picker Complains about opts = nil

Enjoying my emoji bookmarks 💯 🚀
Also when I try to use the telescope picker, I see:
E5108: Error executing lua ...scope.nvim/lua/telescope/previewers/buffer_previewer.lua:41: attempt to index local 'opts' (a nil value)
stack traceback:
...scope.nvim/lua/telescope/previewers/buffer_previewer.lua:41: in function 'qflist_previewer'
...y/bookmarks.nvim/lua/telescope/_extensions/bookmarks.lua:68: in function 'list'
[string ":lua"]:1: in main chunk
Maybe there is something wrong with my mapping, or I am failing to pass in default opts somewhere? I'm in lazyvim btw, and fairly new to the plugin setup style
https://www.lazyvim.org/extras/util/project
Notably, telescope opts is set to nil (?), but I'm not seeing this issue with other plugins. Let me know if I should send this to Telescope or Lazyvim..
Thanks 🤝

-- Overriding editor.lua for better grep with telescope, fzf
local Util = require("lazyvim.util")

return {

  {
    "nvim-telescope/telescope.nvim",
    config = function()
      local actions = require("telescope.actions")
      require("telescope").setup({
      defaults = {
        mappings = {
          i = {
            ["<esc>"] = actions.close,
            ["<c-j>"] = actions.move_selection_next,
            ["<c-k>"] = actions.move_selection_previous,
          },
        },
      },
      })
    end,
    dependencies = {
...
      {
        "tomasky/bookmarks.nvim",
        config = function()
          require("bookmarks").setup({
            -- sign_priority = 8,  --set bookmark sign priority to cover other sign
            save_file = vim.fn.expand("$HOME/.bookmarks"), -- bookmarks save file path
            keywords = {
              -- You can just copy these from emoji keyboard in browser (since it's using same font)
              ["@t"] = "🔥", -- mark annotation startswith @t ,signs this icon as `Todo`
              ["@w"] = "⚠ ", -- mark annotation startswith @w ,signs this icon as `Warn`
              ["@f"] = "⛏ ", -- mark annotation startswith @f ,signs this icon as `Fix`
              ["@n"] = "🧠", -- mark annotation startswith @n ,signs this icon as `Note`
            },
            on_attach = function(bufnr)
              local keymap = vim.keymap.set
              local bm = require("bookmarks")
              keymap("n", "<leader>mm", bm.bookmark_toggle, { desc = "# Toggle Emoji Bookmark" })
              keymap("n", "<leader>mi", bm.bookmark_ann, { desc = "# Change annotation" })
              keymap("n", "<leader>mc", bm.bookmark_clean, { desc = "# Clean all marks in buffer" })
              keymap("n", "<leader>mn", bm.bookmark_next, { desc = "# Jump to next mark in buffer" })
              keymap("n", "<leader>mp", bm.bookmark_prev, { desc = "# Jump to prev mark in buffer" })
              keymap("n", "<leader>mq", bm.bookmark_list, { desc = "# Show marked file list in quickfix window" })
              require("telescope").load_extension("bookmarks")
              keymap(
                "n",
                "<leader>ml",
                [[:lua require("telescope").extensions.bookmarks.list()<cr>]],
                { desc = "# Telescope bookmarks list" }
              )
            end,
          })
        end,
      },
    },
...

I ran into this issue as well. Try this

            { desc = "# Telescope bookmarks list" }

This line should be

            { desc = "# Telescope bookmarks list", buffer = true }

Interesting!
The error goes away, but also a picker does not appear (no messages)..
I'm assuming we want a command to work on its own regardless of the mapping options.

Interesting! The error goes away, but also a picker does not appear (no messages).

Sorry, that wasn't a complete fix. I've made a PR to fix the telescope extension here: https://github.com/tomasky/bookmarks.nvim/pull/17

Sorry, that wasn't a complete fix. I've made a PR to fix the telescope extension here: #17

It works well only on the first screen, if you go over the bookmarks and bring up the telescope again, nothing works

Sorry, that wasn't a complete fix. I've made a PR to fix the telescope extension here: #17

It works well only on the first screen, if you go over the bookmarks and bring up the telescope again, nothing works

I've had issues with bookmarks disappearing. Unsure if it's related to your issue or if yours and mine are entirely new ones. I suggest opening a separate PR with more details on your issue

Thanks @cybermelons @Komar0ff for your help. Agree it sounds like a new issue 🙌


Enhancement: "Accept Card" from 'Saw'

There's no visual feedback when one of the Sawbones' med packs is selected to show that it's been added - any chance of a glow around the card if it's already in your hand?

Good point. Thanks.
I'll add this asap.


Fix cmake 3.6.2 URL

Updated the URL to cmake 3.6.2 as the previous URL was returning a 404 error code

N/A

…this won't actually merge yet because the Linux smoke test is broken. :-/

@swift-ci Please smoke test and merge

Ahh my bad, I believe I missed the revision number, 3.5.2 works, from memory.

... but good to know more recent versions of cmake still work. Thanks :)

Yeah, I noticed you used 3.5.2 elsewhere after I made the change. But it works fine with 3.6.2 :)


10/13/2020 Publish

Docs Build status updates of commit 6372364:
:clock10: Full build: the average full build time is 270 min(s) 40 sec(s), this is based on the last 908 build(s) for this repository.

Docs Build status updates of commit 6372364:
:clock10: Full build: the average full build time is 272 min(s) 32 sec(s), this is based on the last 909 build(s) for this repository.

Docs Build status updates of commit 6372364:
:clock10: Full build: the average full build time is 272 min(s) 32 sec(s), this is based on the last 909 build(s) for this repository.

Docs Build status updates of commit 6372364:
:clock10: Full build: the average full build time is 272 min(s) 32 sec(s), this is based on the last 909 build(s) for this repository.

Docs Build status updates of commit 6372364:
:clock10: Full build: the average full build time is 272 min(s) 32 sec(s), this is based on the last 909 build(s) for this repository.

Docs Build status updates of commit 6372364:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/ai-formrecognizer-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/ai-metricsadvisor-readme-pre.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/communication-chat-readme-pre.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/identity-readme-pre.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/messaging-eventgrid-readme-pre.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/sdk-template-readme-pre.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/search-documents-readme-pre.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/security-keyvault-administration-readme-pre.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

.openpublishing.redirection.json
:warning:Warning

Details

:warning:Warning

Details

docs-ref-autogen/com.azure.ai.formrecognizer.FormRecognizerAsyncClient.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.FormRecognizerClient.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.FormRecognizerClientBuilder.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.FormRecognizerServiceVersion.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FieldBoundingBox.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FieldData.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FieldValue.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FieldValueType.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormContentType.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormElement.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormField.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormLine.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormPage.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormPageRange.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormRecognizerError.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormRecognizerErrorInformation.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormRecognizerException.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormRecognizerOperationResult.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormTable.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormTableCell.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.FormWord.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.LengthUnit.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.Point.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.RecognizeContentOptions.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.RecognizeCustomFormsOptions.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.RecognizeReceiptsOptions.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.RecognizedForm.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.models.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.FormTrainingAsyncClient.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.FormTrainingClient.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.FormTrainingClientBuilder.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.models.AccountProperties.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.models.CopyAuthorization.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.models.CustomFormModel.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.models.CustomFormModelField.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.models.CustomFormModelInfo.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.models.CustomFormModelStatus.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.models.CustomFormSubmodel.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.models.TrainingDocumentInfo.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.azure.ai.formrecognizer.training.models.TrainingFileFilter.yml
:white_check_mark:Succeeded
View (azure-java-stable)

This comment lists only the first 50 files in the pull request.

docs-ref-services/ai-formrecognizer-readme.md

Line 199: [Warning-InvalidBookmark] Invalid link: 'below'. The file docs-ref-services/ai-formrecognizer-readme.md doesn't contain a bookmark named 'Examples'.
Line 199: [Warning-InvalidBookmark] Invalid link: 'below'. The file docs-ref-services/ai-formrecognizer-readme.md doesn't contain a bookmark named 'Examples'.
Line 199: [Warning-InvalidBookmark] Invalid link: 'below'. The file docs-ref-services/ai-formrecognizer-readme.md doesn't contain a bookmark named 'Examples'.

docs-ref-services/ai-metricsadvisor-readme-pre.md

Line 349: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-gb/azure/cognitive-services/metrics-advisor/glossary' contains locale code 'en-gb'. For localizability, remove 'en-gb' from links to most Microsoft sites.
Line 349: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-gb/azure/cognitive-services/metrics-advisor/glossary' contains locale code 'en-gb'. For localizability, remove 'en-gb' from links to most Microsoft sites.
Line 349: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-gb/azure/cognitive-services/metrics-advisor/glossary' contains locale code 'en-gb'. For localizability, remove 'en-gb' from links to most Microsoft sites.

docs-ref-services/communication-chat-readme-pre.md

Line 80: [Warning-InvalidBookmark] Invalid link: 'Chat Thread Operations'. The file docs-ref-services/communication-chat-readme-pre.md doesn't contain a bookmark named 'thread-operations'.
Line 80: [Warning-InvalidBookmark] Invalid link: 'Chat Thread Operations'. The file docs-ref-services/communication-chat-readme-pre.md doesn't contain a bookmark named 'thread-operations'.
Line 80: [Warning-InvalidBookmark] Invalid link: 'Chat Thread Operations'. The file docs-ref-services/communication-chat-readme-pre.md doesn't contain a bookmark named 'thread-operations'.
Line 81: [Warning-InvalidBookmark] Invalid link: 'Chat Message Operations'. The file docs-ref-services/communication-chat-readme-pre.md doesn't contain a bookmark named 'message-operations'.
Line 81: [Warning-InvalidBookmark] Invalid link: 'Chat Message Operations'. The file docs-ref-services/communication-chat-readme-pre.md doesn't contain a bookmark named 'message-operations'.
Line 81: [Warning-InvalidBookmark] Invalid link: 'Chat Message Operations'. The file docs-ref-services/communication-chat-readme-pre.md doesn't contain a bookmark named 'message-operations'.
Line 82: [Warning-InvalidBookmark] Invalid link: 'Chat Thread Member Operations'. The file docs-ref-services/communication-chat-readme-pre.md doesn't contain a bookmark named 'thread-member-operations'.
Line 82: [Warning-InvalidBookmark] Invalid link: 'Chat Thread Member Operations'. The file docs-ref-services/communication-chat-readme-pre.md doesn't contain a bookmark named 'thread-member-operations'.
Line 82: [Warning-InvalidBookmark] Invalid link: 'Chat Thread Member Operations'. The file docs-ref-services/communication-chat-readme-pre.md doesn't contain a bookmark named 'thread-member-operations'.

docs-ref-services/identity-readme-pre.md

Line 298: [Warning-InvalidBookmark] Invalid link: 'chaining credentials'. The file docs-ref-services/identity-readme-pre.md doesn't contain a bookmark named 'chaining-credentials'.
Line 298: [Warning-InvalidBookmark] Invalid link: 'chaining credentials'. The file docs-ref-services/identity-readme-pre.md doesn't contain a bookmark named 'chaining-credentials'.
Line 298: [Warning-InvalidBookmark] Invalid link: 'chaining credentials'. The file docs-ref-services/identity-readme-pre.md doesn't contain a bookmark named 'chaining-credentials'.

docs-ref-services/messaging-eventgrid-readme-pre.md

Line 293: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=330212' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 293: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=330212' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 293: [Warning-insecure-link] Link 'http://go.microsoft.com/fwlink/?LinkId=330212' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

docs-ref-services/sdk-template-readme-pre.md

Line 56: [Warning-InvalidBookmark] Invalid link: 'Introduction'. The file docs-ref-services/sdk-template-readme-pre.md doesn't contain a bookmark named 'introduction'.
Line 56: [Warning-InvalidBookmark] Invalid link: 'Introduction'. The file docs-ref-services/sdk-template-readme-pre.md doesn't contain a bookmark named 'introduction'.
Line 56: [Warning-InvalidBookmark] Invalid link: 'Introduction'. The file docs-ref-services/sdk-template-readme-pre.md doesn't contain a bookmark named 'introduction'.

docs-ref-services/search-documents-readme-pre.md

Line 341: [Warning-InvalidBookmark] Invalid link: 'SearchIndexClient'. The file docs-ref-services/search-documents-readme-pre.md doesn't contain a bookmark named 'Create-a-SearchIndexClient'.
Line 341: [Warning-InvalidBookmark] Invalid link: 'SearchIndexClient'. The file docs-ref-services/search-documents-readme-pre.md doesn't contain a bookmark named 'Create-a-SearchIndexClient'.
Line 341: [Warning-InvalidBookmark] Invalid link: 'SearchIndexClient'. The file docs-ref-services/search-documents-readme-pre.md doesn't contain a bookmark named 'Create-a-SearchIndexClient'.
Line 444: [Warning-InvalidBookmark] Invalid link: 'SearchAsyncClient'. The file docs-ref-services/search-documents-readme-pre.md doesn't contain a bookmark named 'Create-a-SearchClient'.
Line 444: [Warning-InvalidBookmark] Invalid link: 'SearchAsyncClient'. The file docs-ref-services/search-documents-readme-pre.md doesn't contain a bookmark named 'Create-a-SearchClient'.
Line 444: [Warning-InvalidBookmark] Invalid link: 'SearchAsyncClient'. The file docs-ref-services/search-documents-readme-pre.md doesn't contain a bookmark named 'Create-a-SearchClient'.

docs-ref-services/security-keyvault-administration-readme-pre.md

Line 42: [Warning-InvalidBookmark] Invalid link: 'KeyVaultAccessControlClient'. The file docs-ref-services/security-keyvault-administration-readme-pre.md doesn't contain a bookmark named 'create-access-control-client'.
Line 42: [Warning-InvalidBookmark] Invalid link: 'KeyVaultBackupClient'. The file docs-ref-services/security-keyvault-administration-readme-pre.md doesn't contain a bookmark named 'create-backup-client'.
Line 42: [Warning-InvalidBookmark] Invalid link: 'KeyVaultAccessControlClient'. The file docs-ref-services/security-keyvault-administration-readme-pre.md doesn't contain a bookmark named 'create-access-control-client'.
Line 42: [Warning-InvalidBookmark] Invalid link: 'KeyVaultBackupClient'. The file docs-ref-services/security-keyvault-administration-readme-pre.md doesn't contain a bookmark named 'create-backup-client'.
Line 42: [Warning-InvalidBookmark] Invalid link: 'KeyVaultAccessControlClient'. The file docs-ref-services/security-keyvault-administration-readme-pre.md doesn't contain a bookmark named 'create-access-control-client'.
Line 42: [Warning-InvalidBookmark] Invalid link: 'KeyVaultBackupClient'. The file docs-ref-services/security-keyvault-administration-readme-pre.md doesn't contain a bookmark named 'create-backup-client'.

.openpublishing.redirection.json

[Warning-DifferentFileExtensionExistsForSourcePath] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-autogen/com.microsoft.azure.management.monitor.md'. However, file with different extension W:\f5jq-s\docs-ref-autogen/com.microsoft.azure.management.monitor.yml already exists in the Git repo in conflict with the redirection rule.  Docs will ignore the file W:\f5jq-s\docs-ref-autogen/com.microsoft.azure.management.monitor.yml and populate with the redirection rule instead. To resolve this warning, please remove the file W:\f5jq-s\docs-ref-autogen/com.microsoft.azure.management.monitor.yml from git repository
[Warning-DifferentFileExtensionExistsForSourcePath] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-autogen/com.microsoft.azure.sdk.iot.deps.ws.md'. However, file with different extension W:\f5jq-s\docs-ref-autogen/com.microsoft.azure.sdk.iot.deps.ws.yml already exists in the Git repo in conflict with the redirection rule.  Docs will ignore the file W:\f5jq-s\docs-ref-autogen/com.microsoft.azure.sdk.iot.deps.ws.yml and populate with the redirection rule instead. To resolve this warning, please remove the file W:\f5jq-s\docs-ref-autogen/com.microsoft.azure.sdk.iot.deps.ws.yml from git repository
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-azure-tools.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-add-certificate-ca-store.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-azure-authenticate.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-azure-concepts.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-azure-containers-samples.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-azure-get-started.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-azure-release-notes.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-azure-security-samples.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-azure-sql-database-samples.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-azure-virtual-machine-samples.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-azure-web-apps-samples.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-configure-webapp-sources.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-manage-sql-elastic-pools.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-manage-storage-accounts.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-manage-virtual-machines.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-manage-virtual-networks.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-manage-vm-scalesets.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/java-sdk-virtual-machines-in-parallel.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-RedirectionFileAlreadyExists] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/index.yml'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning-DifferentFileExtensionExistsForSourcePath] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'legacy/docs-ref-autogen/com.microsoft.azure.management.batch.implementation.md'. However, file with different extension W:\f5jq-s\legacy/docs-ref-autogen/com.microsoft.azure.management.batch.implementation.yml already exists in the Git repo in conflict with the redirection rule.  Docs will ignore the file W:\f5jq-s\legacy/docs-ref-autogen/com.microsoft.azure.management.batch.implementation.yml and populate with the redirection rule instead. To resolve this warning, please remove the file W:\f5jq-s\legacy/docs-ref-autogen/com.microsoft.azure.management.batch.implementation.yml from git repository
[Warning-DifferentFileExtensionExistsForSourcePath] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.implementation.md'. However, file with different extension W:\f5jq-s\legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.implementation.yml already exists in the Git repo in conflict with the redirection rule.  Docs will ignore the file W:\f5jq-s\legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.implementation.yml and populate with the redirection rule instead. To resolve this warning, please remove the file W:\f5jq-s\legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.implementation.yml from git repository
[Warning-DifferentFileExtensionExistsForSourcePath] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.md'. However, file with different extension W:\f5jq-s\legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.yml already exists in the Git repo in conflict with the redirection rule.  Docs will ignore the file W:\f5jq-s\legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.yml and populate with the redirection rule instead. To resolve this warning, please remove the file W:\f5jq-s\legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.yml from git repository

[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "docs-ref-autogen/com.microsoft.azure.sdk.iot.deps.ws.yml, docs-ref-autogen/com.microsoft.azure.sdk.iot.deps.ws.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "docs-ref-autogen/com.microsoft.azure.sdk.iot.deps.ws.yml, docs-ref-autogen/com.microsoft.azure.sdk.iot.deps.ws.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "docs-ref-autogen/com.microsoft.azure.management.monitor.yml, docs-ref-autogen/com.microsoft.azure.management.monitor.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "docs-ref-autogen/com.microsoft.azure.management.monitor.yml, docs-ref-autogen/com.microsoft.azure.management.monitor.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/ServiceBus.yml, docs-ref-services/servicebus.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/ServiceBus.yml, docs-ref-services/servicebus.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/IoT.yml, docs-ref-services/iot.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/IoT.yml, docs-ref-services/iot.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/EventGrid.yml, docs-ref-services/eventgrid.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/EventGrid.yml, docs-ref-services/eventgrid.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/Storage.yml, docs-ref-services/storage.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/Storage.yml, docs-ref-services/storage.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/CosmosDB.yml, docs-ref-services/cosmosdb.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/CosmosDB.yml, docs-ref-services/cosmosdb.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/HDInsight.yml, docs-ref-services/hdinsight.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "preview/docs-ref-autogen/overview/HDInsight.yml, docs-ref-services/hdinsight.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.yml, legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.yml, legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "legacy/docs-ref-autogen/com.microsoft.azure.management.batch.implementation.yml, legacy/docs-ref-autogen/com.microsoft.azure.management.batch.implementation.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "legacy/docs-ref-autogen/com.microsoft.azure.management.batch.implementation.yml, legacy/docs-ref-autogen/com.microsoft.azure.management.batch.implementation.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.implementation.yml, legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.implementation.md".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.implementation.yml, legacy/docs-ref-autogen/com.microsoft.azure.management.monitor.implementation.md".

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Add timing output for rustdoc and crate total

Closes #298
New output format:
     Parsing <crate> ... (current)
      Parsed [   S.SSSs] (current)
     Parsing <crate> ... (baseline)
      Parsed [   S.SSSs] (baseline)
    Checking <crate> ...
     Checked [   S.SSSs] ...
    Finished [   S.SSSs] <crate>

Thanks again! 🚀


OpenTherm gateway: unhandled error

Home Assistant release with the issue: 0.89.2 with pyotgw 0.4b2
Last working Home Assistant release (if known): n/a
Operating environment (Hass.io/Docker/Windows/etc.): Linux / venv / python 3.7.2
Component/platform: opentherm gateway
Description of problem:
Error shown in log, component failed to work further - reported values stayed as for the moment of error (so I can see boiler working non-stop even tho it's off since at least 12h)
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
not relevant, socket to nodemcu with espeasy as serial server
Traceback (if applicable):
Unhandled error in exception handler
context: {'message': 'Task exception was never retrieved', 'exception': RecursionError('maximum recursion depth exceeded while calling a Python object'), 'future': <Task finished coro=<protocol._watchdog() done, defined at /srv/homeassistant/lib/python3.7/site-packages/pyotgw/protocol.py:120> exception=RecursionError('maximum recursion depth exceeded while calling a Python object')>}
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 1643, in call_exception_handler
    self._exception_handler(self, context)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/core.py", line 110, in async_loop_exception_handler
    "Error doing job: %s", context['message'], **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1412, in error
    self._log(ERROR, msg, args, **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1519, in _log
    self.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1529, in handle
    self.callHandlers(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1591, in callHandlers
    hdlr.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 905, in handle
    self.emit(record)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 168, in emit
    _figure_out_source(record, stack, self.hass))
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 98, in __init__
    traceback.format_exception(*record.exc_info))
  File "/usr/local/lib/python3.7/traceback.py", line 121, in format_exception
    type(value), value, tb, limit=limit).format(chain=chain))
  File "/usr/local/lib/python3.7/traceback.py", line 497, in __init__
    _seen=_seen)
  File "/usr/local/lib/python3.7/traceback.py", line 497, in __init__
    _seen=_seen)
  File "/usr/local/lib/python3.7/traceback.py", line 497, in __init__
    _seen=_seen)
  [Previous line repeated 486 more times]
  File "/usr/local/lib/python3.7/traceback.py", line 473, in __init__
    _seen.add(id(exc_value))
RecursionError: maximum recursion depth exceeded while calling a Python object

Additional information:
pyotgw is from latest version which should have 'reconnection issue' fixed - 0.4b2
@mvn23

It could be fault of some connection issue with the gateway being unavailable, but right now even restarting whole HA cause it's being unavailable:
2019-03-15 14:50:37 ERROR (MainThread) [pyotgw.pyotgw] Could not connect to serial device on socket://192.168.x.x:xxxx. Will keep trying. Reported error was: Could not open port socket://192.168.x.x:xxxx: [Errno 113] No route to host

Did you have a lot of disconnect errors between HA start and this problem occuring?

Yes - sort of. Before the fix some ofthe disconnection happened to freeze HA totally. After the fix they seem to get receonnect and work properly, but still it's nodemcu serial server, so WiFi and possible connection dropouts.

Trying to reproduce it here by stressing the watchdog/reconnect logic, but so far without success. Any further details about the connection drops (frequency, duration) and/or a debug log could be helpful.

The thing is that when that error occured - probably the nodemcu otgw itself somehow hanged/lost connection. But what's worse, HA didn't success to start until that nodemcu got hard-restarted (power off/power on).
So basically when it occured, HA waited when startup until the restart - without that I've tried to restart HA itself and no successs.
(totally in meanwhile I wait for ethernet module for OTGW to arrive then I'll do tests over LAN, but it's still few weeks before delivery tho...)

The thing is that when that error occured - probably the nodemcu otgw itself somehow hanged/lost connection. But what's worse, HA didn't success to start until that nodemcu got hard-restarted (power off/power on).

I see the same behavior indeed. If the gateway is unreachable when HA starts, HA's interface will not be loaded until the connection to the gateway is made. During this time, I do see other activity in the debug log so it's not completely blocked. It seems to be related to how the connecting routine is scheduled, looking into that now.

Great! I hope to help finding the bug and making component even better :-)

Seems fixed with #22121 and #22106.
Will test next release and reopen if still an issue.


Update docs with better walkthroughs

Improve our contribution guide, especially following the addition of the install support in config.json.

Initial review is good. I made some comments, happy for this to be merged. 👍


Create Rook

Create a classical rook piece with an colour parameter.
The piece should have the following properties-

Allowed moves
Starting position

Use the media folder for any images needed.

I have taken up this issue


Add join, virtual table and fetch propagation handling to LogicalPlanner

This removes all remaining Consumers and implements most of the
functionality in LogicalPlan-operators.
Things missing:

Join order optimization
Recursive/nested semi-join rewrite on
Early fetch in case of nested selects

The fetch planning in general needs a bit of tuning. There are a couple
of cases where the plans are now a bit worse. But it creates functional
plans. We can improve from here.

@matriv @mxm I think this is now good enough for a first review. There are still a couple of TODOs that I want to address before merging it. But an initial rough review would be nice.
Some things that I'd like to keep out of this PR and add later:

Join planner improvements (re-adding the ordering & the distribution planning)
Fetch propagation tuning

It's already big enough as it is.

Codecov Report

:exclamation: No coverage uploaded for pull request base (logical-planner@9820397). Click here to learn what that means.
The diff coverage is 92.72%.

@@                Coverage Diff                 @@
##             logical-planner    #6334   +/-   ##
==================================================
  Coverage                   ?   83.03%
  Complexity                 ?    12773
==================================================
  Files                      ?     1477
  Lines                      ?    47792
  Branches                   ?     5809
==================================================
  Hits                       ?    39685
  Misses                     ?     5394
  Partials                   ?     2713

Impacted Files
Coverage Δ
Complexity Δ

sql/src/main/java/io/crate/planner/Limits.java
100% <ø> (ø)
11 <0> (?)

.../planner/projection/builder/ProjectionBuilder.java
70.45% <ø> (ø)
12 <0> (?)

...in/java/io/crate/analyze/TableIdentsExtractor.java
0% <ø> (ø)
0 <0> (?)

...main/java/io/crate/analyze/relations/JoinPair.java
60% <ø> (ø)
19 <0> (?)

...te/planner/node/dql/TableFunctionCollectPhase.java
90% <ø> (ø)
5 <0> (?)

sql/src/main/java/io/crate/analyze/QuerySpec.java
91.26% <ø> (ø)
44 <0> (?)

.../io/crate/planner/node/dql/RoutedCollectPhase.java
86.25% <ø> (ø)
28 <0> (?)

...ain/java/io/crate/analyze/relations/JoinPairs.java
33.33% <ø> (ø)
8 <0> (?)

...va/io/crate/analyze/relations/RelationPrinter.java
100% <ø> (ø)
7 <0> (?)

.../main/java/io/crate/planner/ResultDescription.java
50% <ø> (ø)
3 <0> (?)

... and 36 more

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 9820397...8686745. Read the comment docs.

Regarding the missing features: So far it's the fetch-propagation and the join ordering + distribution planning.
There are either still TODO or tests that are marked as Ignored because of these things.
So we've to make sure all of these are removed in the PR against master.


Call host functions from WebAssembly

The way that wasm_bindgen in Rust can access functions that are defined externally, how does one allow the WASM to call dart functions?

When you're instantiating the module, you can fill any function imports with Dart functions:
var inst = (WasmModule(data).builder()
      ..addFunction('env', 'myFunction', (int x) {
        // Do stuff
      }))
    .build();

You can see an example here: https://github.com/dart-lang/wasm/blob/main/wasm/test/fn_import_test.dart
On the C side, you just declare the function, but don't give it a body (this would usually give you a linker error, but you can tell your compiler to treat it as a function to be filled in later).
void myFunction(int x);

That's brilliant. I'll try that out.
To save creating another issue for each question, I hope it is ok if I put them here. I'll edit the title accordingly.
As far as I know, this plugin uses Wasmer to run the code. Looking at the Wasmer docs, I found that it is possible to use the Singlepass, Cranelift or LLVM compiler in increasing order of runtime performance and compilation time. How can I configure this through the WASM plugin?
In my use case, I have a WASM file which acts as a package. I need to write a Rust program to interact with this package. For this, I plan to use Wasmer rust. I need to then compile the Rust program to WASM which will then run on the phone using this plugin. Is there any way I can import the contents of the package WASM file into rust to avoid having nested Wasmer runtimes?

As far as I know, this plugin uses Wasmer to run the code. Looking at the Wasmer docs, I found that it is possible to use the Singlepass, Cranelift or LLVM compiler in increasing order of runtime performance and compilation time. How can I configure this through the WASM plugin?

Right now we use cranelift and there's no way to configure it. You can check out wasm/bin/cargo.toml to see all the config options we're using. Why do you want to configure this?

In my use case, I have a WASM file which acts as a package. I need to write a Rust program to interact with this package. For this, I plan to use Wasmer rust. I need to then compile the Rust program to WASM which will then run on the phone using this plugin. Is there any way I can import the contents of the package WASM file into rust to avoid having nested Wasmer runtimes?

You mean import package:wasm into rust? I don't know of any way to import dart into rust, but I don't do much rust programming. I think you'd still end up with multiple wasm runtimes, one in an .so file, and one in wasm code.
What if you compile your rust program to wasm, without the wasmer runtime, and with api surface between your rust library and wasm module exposed as function imports and exports? Then you could just import the rust and wasm modules into dart using package:wasm, and wire up the function imports and exports through dart. That way you'd only have package:wasm's runtime.

I want to configure this because the LLVM compiler is supposed to be the highest performing compiler out of them. My use-case requires as much performance as possible. Is it even possible to have this as an option on mobile?
Would it work if I used Wasmer to compile the package wasm into a .so or .dylib or whatever and then import that into Rust and then compile the result into WASM?
That could be a possibility. I'll look into it.

I want to configure this because the LLVM compiler is supposed to be the highest performing compiler out of them. My use-case requires as much performance as possible. Is it even possible to have this as an option on mobile?

I think LLVM would greatly increase your app size, and make your startup time slower, and only give you a modest speed boost. It wouldn't be possible to use this on iOS. I'm not sure if it would be possible on Android (that's a question for the Wasmer folks).
Before you conclude that LLVM is what you want, you should try running a benchmark. Run your library in Wasmer using LLVM and cranelift, and see how fast it runs, and how big the Wasmer binary is. I suspect that cranelift is the best trade-off between binary size and speed, but if you have data that says otherwise I can make this option configurable.

Would it work if I used Wasmer to compile the package wasm into a .so or .dylib or whatever and then import that into Rust and then compile the result into WASM?

If you do that, you'll have 2 copies of Wasmer in your app, one in package:wasm's .so file, and one in your wasm module. Also I don't know if it's even possible. Maybe try asking on the Rust stack overflow page.

My app is not one that is to be used by a wide audience and is only for my own use so the app size and startup time are not particularly important. Due to the performance critical nature of the app, I'd happily accept a modest speed boost haha. But if it's not possible, then nothing can be done about that. I might create an issue on the wasmer repo regarding this.
Out of interest, why would LLVM not run on iOS?
I'll run some benchmarks once the full custom WASM code is written. In the meantime, would it be possible to provide an option between Singleness and Cranelift anyway? Any customisability is appreciated.
That sounds inefficient, I'll try formulate a better plan. Thank you though.

Regarding the customisability for the compiler and engine of wasmer, it'll just allow the dev to choose the best option for their needs

Out of interest, why would LLVM not run on iOS?

I think LLVM is going to be generating machine code at runtime, which is not allowed on iOS. But I might be wrong about that. Check with the wasmer team.
If your project is just for you, you might fine it easier and faster to use FFI to load your Rust library. You could still use package:wasm to load the wasm library if you want.

The project is just for me but I have 2 reasons for wanting to load my rust code through WASM:

This app will just be an interface to a physical device which only works with mobile. The rust code will contain the logic. I want to be able to load in different logic at any time.

It will make development a bit faster because I won't have to recompile the app each time but just recompile the WASM and upload it

It seems like it'll be necessary to have nested wasmer runtimes for now but I'll check it out with the wasmer team as you suggested.

I mentioned this before, but I'll elaborate: it's possible to load both your rust module and your wasm module using package:wasm, without needing nested wasm runtimes.

Compile both your modules to wasm
Load them both into Dart using package:wasm
When you want to call from the rust module into the wasm module, do so by exporting the function from the wasm module, and importing the function into the rust module. Then you can use Dart as the bridge:

// Load the wasm module.
var wasmInst = (WasmModule(wasmModuleData).builder()).build();
var myFunction = wasmInst.lookupFunction('myFunction');

// Load the rust module.
var rustInst = (WasmModule(rustModuleData).builder()
      ..addFunction('env', 'myFunction', myFunction))
    .build();

From the Rust library's perspective, the wasm module will just be an external library that it imports some functions from. The Rust library won't need to run a wasm runtime. I don't know how you declare function imports in Rust, but the C equivalent would be:
void myFunction(int x);

Unfortunately, that doesn't work for my use case.  But thank you very much anyway.

Making this configurable should be doable. It's just plumbing.


[Suggestion] Add an ability to jump and kick the door open

Additional context
It could be nice if it worked the same way as when slide kicking the door open but instead jump kicking the door

nah


Not going through all of my posts?

For some reason, the software keeps stopping once it's gone through 4,220 of my posts. I know that there are more untagged posts going further back than that, but the software is not looking through the other 6,000 posts for some reason.

I have the same problem, mine stops at 480 posts when I know I have over 8000.

I think this was fixed by 27d74be, please reopen if the issue persists.


style: 2 column video

We need 2 column styling option for videos:
Ref: https://www.mammotome.com/products/mammotome-confirm/

@krizel4, I double checked and we actually already support 2 column styling for videos. Just needs a (two columns) added to the Videos block. I just wasn't aware of that during the call - we will document the block in the docs. Thanks for reporting - I added the (two columns) option to the Mammotome confirm page already.


v0.0.4 fails to display panel on iPad iOS 12.4

v0.0.3 and all prior versions worked u til this new v0.0.4 release.
Now the panel never displays and I have no way to control volume on my apps had previously turned down.
Please add ability to Downgrade on BigBoss repo. I need to revert to 0.0.3 last known good and I can’t find the deb to do so.
EDIT: this may be a working link
Tweak is super awesome otherwise, a bit confusing to use, but the effects you can achieve are incredibly useful.

Downgrading is always available on my repo.
Debs are always available at https://github.com/brendonjkding/brendonjkding.github.io/tree/master/debs

I've been pretty happily using 0.37r or whatever the last version is, for several months now and just wanted to thank you for such a brilliant tweak!!
Most days I watch YouTube in a PiP while racing Real Racing 3 or tapping ads in the game, and your tweak is indispensable for this scenario depending on whether I want to focus more on the dialog of the YouTube video or the racing game, and I can adjust the levels in real-time as my YouTube playlist proceeds and sometimes a video was recorded unusually quiet, etc. 👏🏼👏🏼


Update validation.php

minor translation update for traditional chinese

Hello,
thanks but for chinese version, I call @overtrue ;)

no problem, waiting for his review ;)

Hi, @caouecs,  I was in mainland China, @whsyu is Taiwanese, so zh-TW his work should be more accurate. Thank you!  so, just merge it. :smile:
谢谢！@whsyu

Ok ;)


Why data volume reduction before calibration?

Hi,
I am creating a daughter of the CameraCalibrator class dedicated to the calibration of LST real data (in cta-lstchain). Looking at the implementation of CameraCalibrator I am a bit surprised to see that data volume reduction is performed in  _calibrate_dl0() before the charge calibration (in _calibrate_dl1). What is here meant for volume reduction? Because in general It seems to me that data reduction on calibrated data should be more precise. So, I would do the other way around: calibrate the dl0 and reduce the dl1 ...

You are right that a form of charge extraction and camera calibration is likely needed for the data volume reduction - to identify pixels which have signal. However, as I understand it, the data volume reduction will be done before ctapipe - the DL0 waveforms ctapipe will read will already have data volume reduction applied.
The data volume reduction is done online, and therefore may utilise a rough, fast charge extraction and camera calibration that is not perfect. Whereas for extracting the images - we require accurate charge extraction and calibration.
And its important to remember that the output of the data volume reduction step is waveforms (at least for the pixels containing signal). Ctapipe will then need to read these waveforms, and perform the "best" charge extraction and calibration (which may be slower than the methods used in the data volume reduction).

Data volume reduction in this context is to do with reducing the amount of waveform data stored to disk.
There is a cleaning step after charge extraction (tailcuts etc.) which one may consider is "reducing the data volume of images". But this is a different operation to what is referred to as data volume reduction.

Hi @watsonjj,
yes, I agree that most probably the gain reduction will be done at the event builder level, but, as you say, any type of reduction will  ask for a calibration (even if rough), so if we decide to introduce a waveform reduction in ctapipe at this level why should we put it before the calibration? Is there a specific reason? (how do you think to do the reduction here with uncalibrated data?)
I thinks the problem is also coming from some inconsistency with the present data model in ctapipe, if you look at the DL0 container it speaks of calibrated waveforms:
class DL0CameraContainer(Container):
    """
    Storage of data volume reduced dl0 data from a single telescope
    """
    trigger_time = Field(None, "Telescope trigger time, start of waveform "
                               "readout")
    trigger_type = Field(0o0, "camera trigger type")

    waveform = Field(None, (
        "numpy array containing data volume reduced "
        "p.e. samples"
        "(n_pixels, n_samples). Note this may be a masked array, "
        "if pixels or time slices are zero-suppressed"
    ))

This is different from what @kosack suggests in his data model document where the DL0 level contains both the waveform and the image in digital counts:

If we follow this proposal both the image and waveform reduction (if not yet done at event builder level) must be at DL1 level with calibrated data, which in turn is consistent with the present DL1 data model in ctapipe which foresees the gain selection at this level
class DL1CameraContainer(Container):
    """
    Storage of output of camera calibration e.g the final calibrated
    image in intensity units and the pulse time.
    """
    image = Field(
        None,
        "Numpy array of camera image, after waveform extraction."
        "Shape: (n_chan, n_pixel)"
    )
    pulse_time = Field(
        None,
        "Numpy array containing position of the pulse as determined by "
        "the extractor."
        "Shape: (n_chan, n_pixel, n_samples)"
    )
    #TODO: Remove when gain selection added?
    gain_channel = Field(
        None,
        "boolean numpy array of which gain channel was used for each pixel "
        "in the image "
    )

@karl, since we are in process to setup the DL0-DL1 production in cta-lstchain,  could we update the DL0 (DL1?) ctapipe container so as to use the most recent/valuable solution for the LST1 data?

Ctapipe will read DL0 waveforms. These are the waveforms saved to disk, and due to their large data volume, they need to be reduced smartly.
Currently as a prototype, ctapipe also reads R1 waveforms. R1 waveforms have the camera-specific calibration applied to them, but no data volume reduction. They are calibrated waveforms. The data volume reduction step in ctapipe can be used to test algorithms for the data volume reduction step. This transforms the R1 waveforms into DL0 waveforms.
DL0 waveforms are then processed by the Image extractors to get the single values per pixel which make up the DL1 image.
It doesn't make sense to do the data volume reduction after the DL1 step, because beyond the DL1 calibration you no longer have waveforms. The purpose of the data volume reduction is to reduce the size of waveforms so that they can be stored (and archived) on disk.

DL0 level contains both the waveform and the image in digital counts

Those are not really digital counts, but calibrated values (pedestals and gains applied) stored as integers (so losing some precision, but enough to do data volume reduction and basic Hillas parameterization) .  Right now we do not model this in ctapipe. Probably we should at some point, but I was waiting until the on-line camera calibration procedures are defined.

@kosack,
perfect, this is what I thought it should be (perhaps the unit DC is a bit misleading ). So, the charge calibration mentioned at the end of _calibrate_dl1() is a second step calibration?
def _calibrate_dl1(self, event, telid):
        waveforms = event.dl0.tel[telid].waveform
        if self._check_dl0_empty(waveforms):
            return
        n_samples = waveforms.shape[2]
        if n_samples == 1:
            # To handle ASTRI and dst
            # TODO: Improved handling of ASTRI and dst
            #   - dst with custom EventSource?
            #   - Read into dl1 container directly?
            #   - Don't do anything if dl1 container already filled
            #   - Update on SST review decision
            corrected_charge = waveforms[..., 0]
            pulse_time = np.zeros(waveforms.shape[0:2])
        else:
            # TODO: pass camera to ImageExtractor.__init__
            if self.image_extractor.requires_neighbors():
                camera = event.inst.subarray.tel[telid].camera
                self.image_extractor.neighbors = camera.neighbor_matrix_where
            charge, pulse_time = self.image_extractor(waveforms)

            # Apply integration correction
            # TODO: Remove integration correction
            correction = self._get_correction(event, telid)[:, None]
            corrected_charge = charge * correction

        event.dl1.tel[telid].image = corrected_charge
        event.dl1.tel[telid].pulse_time = pulse_time

        # TODO: Add charge calibration

I think you're not wrong, but perhaps we are also talking about different things: analyzing simulations in a similar way to real data means a few extra steps. The real sequence would be something like:

In the camera server:

apply basic calibration (to integer level) and output R1

In the ACADA data handling system:

read R1 and apply data volume reduction and store as DL0
calculate rough hillas parameters and send to realtime pipeline

in the offline pipeline (Cat-B or Cat-C):

read DL0 and either

un-apply basic calibration and apply better calibration
apply corrections to basic calibration

etc.

We need to simulate the first 2 steps for Monte-Carlo data.

Yes, the point is that we don't have ACADA now (but perhaps I miss something, is there an ACADA repository/code somewhere?), so with the prototype data we are using ctapipe also for doing steps 1 and 2 ... this is probably at the origin of the confusion.
I totally agree that we must test these two points with MC data, for that we need to have the MON container also when we read the MC data. Waiting  for discussion in  https://github.com/cta-observatory/ctapipe/issues/1041 to converge, could we  modify the DataContainer() in the MC readers with a EventAndMonDataContainer(), so that one can store the results of the calibration procedure also when performed with MC events?

I think that sequence looks fine, but perhaps we are also talking about different things: analyzing simulations in a similar way to real data means a few extra steps. The real sequence would be something like:

In the camera server:

apply basic calibration (to integer level) and output R1

In the ACADA data handling system:

read R1 and apply data volume reduction and store as DL0
calculate rough hillas parameters and send to realtime pipeline

in the offline pipeline (Cat-B or Cat-C):

read DL0 and either

un-apply basic calibration and apply better calibration
apply corrections to basic calibration

etc.

Hi @kosack
Am I understanding correctly?

R1 = integers
DL0 = integers

--> un-apply calibration on DL0 is not an exact reverse operation (some precision loss as data is stored in integers)

Yes both R1 and DL0 should store waveforms as 16-bit unsigned integers (with some metadata fields to tell the scale and shift to apply to make them floating point). E.g. waveform_value = WAVE_SCALE * (waveform_int - WAVE_SHIFT) . And that value is then in units of PE  or equivalent (at least roughly calibrated).

This is somewhat confusing since we have not yet finalized the R1 and DL0 interface definitions in CTAO - this is right now just a rough guess of what the final version will be, but it's reasonable I think, and useful to try out to see if there are problems.  Once there is an official interface control document, we will have to implement exactly the data model associated with it .

I think is discussion is settled with the data format document.


Missing usb-modeswitch in Slate AX/Flint builds

(reported by d@petebarnett)
Needed for few LTE dongles.
Note: revise buildconfig packages.

Added in latest release.


Swap pool interface

Closes: #XXX
Description

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

Merging #758 (b04a881) into main (bc65a83) will decrease coverage by 0.43%.
The diff coverage is 27.60%.

@@            Coverage Diff             @@
##             main     #758      +/-   ##
==========================================
- Coverage   18.73%   18.29%   -0.44%
==========================================
  Files         172      174       +2
  Lines       23908    23979      +71
==========================================
- Hits         4478     4386      -92
- Misses      18655    18810     +155
- Partials      775      783       +8

Impacted Files
Coverage Δ

osmomath/math.go
64.44% <0.00%> (-1.47%)
:arrow_down:

x/gamm/keeper/invariants.go
14.92% <0.00%> (ø)

x/gamm/pool-models/balancer/balancer_pool.go
66.36% <0.00%> (-0.91%)
:arrow_down:

x/gamm/pool-models/balancer/math.go
0.00% <0.00%> (ø)

x/gamm/types/pool.go
0.00% <0.00%> (ø)

x/gamm/types/pool_asset.go
0.00% <0.00%> (ø)

x/gamm/keeper/swap.go
71.71% <73.17%> (-6.27%)
:arrow_down:

x/gamm/keeper/pool_service.go
59.52% <73.33%> (-2.83%)
:arrow_down:

x/gamm/keeper/multihop.go
74.35% <81.81%> (-5.65%)
:arrow_down:

x/claim/keeper/hooks.go
26.92% <0.00%> (-2.25%)
:arrow_down:

... and 4 more

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 bc65a83...b04a881. Read the comment docs.

ideas incorporated into later work!


[GOV] Interpretability for HIVE-COTE V2 Classifier

Describe the issue
Hi Team,
Just wanted to check if there are any interpretability frameworks that are currently supported for HIVECOTE V2 Classifier like SHAP, LIME, etc? If not, does the team plan to integrate anything in the near future?
Suggest a potential alternative/fix
No response
Additional context
I am working on a time-series classification problem statement using HIVECOTE V2 and would really love to interpret the model predictions.
Also, how do you suggest interpreting the results in the current scenario?

hi, happy to hear you are using HC2. Short answer is that there are no formal mechanisms as yet, and our plans to include them are more medium term than short term. HC2 is a meta ensemble, so the first useful information is the weights for each of the four components
   stc_weight_ : float
        The weight for STC probabilities.
    drcif_weight_ : float
        The weight for DrCIF probabilities.
    arsenal_weight_ : float
        The weight for Arsenal probabilities.
    tde_weight_ : float
        The weight for TDE probabilities.

If one component is noticeably better on the train data (which is used to form these weights) then you an look more closely at the internal workings of that component. For example, the shapelets notebook shows how to recover the most discriminatory shapelets and we can find feature relevance graphs I think. Matthew is off this week but can no doubt give much better advise than me when he comes back. We would really like to hear what sort of thing you are thinking of in terms of interpretability.


Warn when Geo* entities are logged and the viewer wasn't compiled with the map_view feature

The map view is behind a map_view cargo feature on rerun-cli, which is enabled in release build but not in default build (aka when building from source). This leads to a footgun where people don't see a map when they expect one. We should warn the user when that happens, indicating that the map_view feature needs to be enabled.
The proposed mechanism for that is to have a store subscribers that reacts to some specific indicator components, and emit warnings as required.
Level 1: hard code GeoPoints and GeoLineStrings (subject to bitrot, eg when we introduce GeoPolygons
Level 2: use the information already contained in attribute.docs.view_types to populate the reflection structures, and use said structure to generate warnings for all kinds of view that might be missing.
.
.
.
Level ∞: "unsupported data, click here to download the Map view plugin"

We log a warning, but that's not good enough. We should show the error message in the space view with the problem:


[topcrash] Specify the major version to avoid old builds

Resolves #1675
Checklist

[x] Type annotations added to new functions
[x] Docs added to functions touched in main classes
[x] Dry-run produced the expected results
[ ] The to-be-announced tag added if this is worth announcing

Dry-run
The following bugs are missing a topcrash keyword:

BugSummarySeverityAdded Keywords

1802620

Crash in [@ android.app.ForegroundServiceStartNotAllowedException: at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel(ForegroundServiceStartNotAllowedException.java)]

S2

topcrash

1802046

"GeckoRuntime is shutting down" Crash in [@ java.lang.RuntimeException: at org.mozilla.geckoview.WebExtensionController$$ExternalSyntheticLambda14.onShutdown(R8$$SyntheticClass:5)]

S3

topcrash

1779558

Crash in [@ mozalloc_abort | abort | _iris_batch_flush]

S2

topcrash

1776917

[Fission] Fenix tab crashes when attempting to access an unsecure page with HTTPS-Only Mode enabled

S3

topcrash

1639157

Crash while collecting the nursery

S4

topcrash-startup


Update readme to be more concise / code-forward

@escamoteur Hey Thomas, I took a stab at making the readme a bit more concise / code-forward.
Could you look it over and let me know what you think?

Have I missed anything important?
Is anything wrong?
Do you think this is a good idea at all?

View readable
Cheers,

I just had a look at it. I like the idea to have a code example at the beginning but I'm not sure if it gets easier by making it that succinct. IMHO the original explains the concepts better in detail. We have to keep in mind that beginners too should be able to understand the usage.

Hm, my thought is that this would generally be better for beginners to understand because it's more code-forward, and uses some tables to really clearly explain the various APIs.
The original readme seems more like a blog post that might accompany the launch of the lib, but I really think README's work best when they get down to business and just show show how to use the lib and explain the API.

I personally had a quite hard time understanding all the API and the difference between watchX watch watchOnly etc based on the readme, and it wasn't until I found the doc page, and could just read the API's in a concise way, that I really understood the lib: https://pub.dev/documentation/get_it_mixin/latest/get_it_mixin/GetItMixin-mixin.html
Do you think this version can be augmented to be something you're happy with, or should we just scrap it?

just as an addition, have you read https://github.com/fluttercommunity/get_it/issues/246

Thanks

Hi Shawn, I have to apologize, I had only read the diff view of your changes which don't give a good impression of how it looks as a whole. I really like it. What do you think that we keep the original one as readme_extended and we add a link under the first example telling that if you like more information they can find a more prosa explanation here. We should also add a link to my talk https://youtu.be/YJ52kSfSMyM

Nice! I'll review your comments and make the updates, and yes I think it's a good idea to do the links to the extended readme, as well as your talk.
I hadn't seen that link yet, looks like a good read, I'll dig in later today :)

@escamoteur I implemented most of your changes, and also updated the readme to use the phrasing 'watch' instead of 'bind' in some cases.
Remaining TBD:

Add an example data class for the watchXOnly example (maybe Streams/Futures as well?)
Test whether we can registerHandler in initState, and clarify the rules if we can't

Please have another look when you get a chance: https://github.com/escamoteur/get_it_mixin/tree/update-readme

Hi @escamoteur and @esDotDev,
I must say I like the proposed README quite a lot, it is more concise and offers a quick way to have a glance on what get_it_mixin is all about. Beginners would benefit a lot of the smaller, more concrete examples as well.

@escamoteur Think we could finish this off soon?
Here is what is left to tweak:

Add an example data class for the watchXOnly example (maybe Streams/Futures as well?)
Test whether we can registerHandler in initState, and clarify the rules if we can't
Incorporate links to extended readme and video

Hi Shawn, sorry for me not reacting, I hope it will go better for the next time. What do you watn from me to do here? I already agreed that we go forward with your readme witha link to the old one for people who like a more detailed explanation

Hey! You mentioned "> I would add a snipped of the watched class type because watchOnly works differently", so I was hoping you could add that, as I'm not totally sure how it works.
Also, I was curious:

Can we call registerHandler in initState
Do you have URLs we can use for the old readme? Should we just make it like history.md or something?

Hi @escamoteur, I went ahead and added a link to the README_EXTENDED as well as your talk.
Think we are good to land this? Sorry for the looooong delay!


GH-4128: Fix Inconsistent determination of positional Argument when using context.Arguments versus context.Argument

…Arguments versus context.Argument

Thanks for the PR @EdLichtman. Could you please reply to this as per the instructions here: https://github.com/cake-build/cake/pull/4139#issuecomment-1496141739 ?

@augustoproiete I can do that, but it's not the complete changelist you have, and like I mentioned in Issue #4128 I haven't yet been able to run the tests. Would it be alright for me to perform the checks and get my change in without it? It looks like I haven't fully implemented the changes you implemented, so it's still an incomplete change.

@EdLichtman That's fine. I can merge your changes and mine on the same PR - or you can bring the missing changes I did to this MR, and we close mine

@microsoft-github-policy-service agree

@EdLichtman your changes have been merged, thanks for your contribution :+1:


Datastore.php / Windows Dev AppEngine produces CGI/FastCGI issue

I'm using AppEngine under Windows for development. I've tried to create data in Datastore.
Unfortunately CGI/FastCGI will gone every time I call the demo script
https://github.com/amygdala/appengine_php_datastore_example/blob/master/datastore_connect.php

I've found that this line is producing the issue.
$service_dataset->commit($dataset_id, $req, []);

After looking to the Datastore.php from this lib I've replaced return value by a simple return.
  /**
   * Commit a transaction, optionally creating, deleting or modifying some
   * entities. (datasets.commit)
   *
   * @param string $datasetId Identifies the dataset.
   * @param Google_CommitRequest $postBody
   * @param array $optParams Optional parameters.
   * @return Google_Service_Datastore_CommitResponse
   */
  public function commit($datasetId, Google_Service_Datastore_CommitRequest $postBody, $optParams = array())
  {
    $params = array('datasetId' => $datasetId, 'postBody' => $postBody);
    $params = array_merge($params, $optParams);
    return;
    return $this->call('commit', array($params), "Google_Service_Datastore_CommitResponse");
  }

The issue was gone. As expected without data in the Google Datastore.

This also happens when running the HelloAnalytics.php.

The google php api client is not part of app engine, you should probably file this issue over on it's github project.

This is a known issue: https://code.google.com/p/googleappengine/issues/detail?id=12287

I would be interested to know if this happens with the newer version of the library, if anybody has time to test it.

I used the latest version this Saturday.
On Nov 2, 2015 22:27, "Brent Shaffer"<EMAIL_ADDRESS>wrote:

I would be interested to know if this happens with the newer version of
the library, if anybody has time to test it.
—
Reply to this email directly or view it on GitHub
https://github.com/google/google-api-php-client/issues/640#issuecomment-153162470
.

@bshaffer I've used the new lib and the issue was gone. Currently I've an authentication problem to storage but this shouldn't depend to this lib. I have to make more tests.

Great news @mf01!
I updated the master branch to use HTTP Streams instead of cURL on App Engine (see #715). I believe this has done the trick. @Abbe98 can you also confirm?

On the current master I got the error that the autoload has moved to vendor/autoload.php(seams weird as I'm not using composer and no vendor/ exists)...

@Abbe98 composer is required in the new version, or you can download the release here and the vendor directory is included.

Okey will install the master-branch from Composer then...
On Nov 7, 2015 01:29, "Brent Shaffer"<EMAIL_ADDRESS>wrote:

@Abbe98 https://github.com/Abbe98 composer is required in the new
version, or you can download the release here
https://github.com/google/google-api-php-client/releases and the vendor
directory is included.
—
Reply to this email directly or view it on GitHub
https://github.com/google/google-api-php-client/issues/640#issuecomment-154585896
.

Getting Fatal error: Class 'Google_Auth_AssertionCredentials' not found from master-dev.
So the crash is fixed and the Hello Analytics API: PHP is outdated.

@bshaffer I have another problem during update to the new version including composer.
This line will produce the error.
$service_dataset->commit($dataset_id, $req, []);
This is the issue.

Notice: Object of class google\appengine\runtime\CurlLite could not be converted to int in [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\guzzlehttp\ringphp\src\Client\CurlHandler.php on line 109

Notice: Object of class google\appengine\runtime\CurlLite could not be converted to int in [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\guzzlehttp\ringphp\src\Client\CurlHandler.php on line 118

Fatal error: Uncaught exception 'google\appengine\runtime\CurlLiteOptionNotSupportedException' with message 'Option 20056 is not supported by this curl implementation.' in [path-to-gae]\appengine\runtime\CurlLite.php:487 Stack trace:
#0 [path-to-gae]\appengine\runtime\CurlLite.php(215): google\appengine\runtime\CurlLite->setOption(20056, NULL)
#1 [path-to-gae]\appengine\runtime\CurlLiteStub.php(1325): google\appengine\runtime\CurlLite->setOptionsArray(Array)
#2 [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\guzzlehttp\ringphp\src\Client\CurlHandler.php(130): curl_setopt_array(Object(google\appengine\runtime\CurlLite), Array)
#3 [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\guzzlehttp\rin in [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\guzzlehttp\guzzle\src\Exception\RequestException.php on line 51
Maybe I'm wrong or did forgotten something. But it's not working using Google App Engine (local) environment.

aha, this would be because the check $client->isAppEngine() does not return true for the dev appserver :anguished:
You can set the stream handler manually in the meantime.

I'm sorry. The issue is still there.
So I've forced true return.
    // set StreamHandler on AppEngine by default
    if (true || $this->isAppEngine()) {
      $options['handler'] = new StreamHandler();
    }

And I have a different message.
Warning: Missing argument 1 for Monolog\Handler\StreamHandler::__construct(), called in [path-to-project]\lib\google-api-php-client-2.0.0-RC1\src\Google\Client.php on line 1042 and defined in [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\monolog\monolog\src\Monolog\Handler\StreamHandler.php on line 42

Notice: Undefined variable: stream in [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\monolog\monolog\src\Monolog\Handler\StreamHandler.php on line 45

Notice: Undefined variable: stream in [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\monolog\monolog\src\Monolog\Handler\StreamHandler.php on line 47

Fatal error: Uncaught exception 'InvalidArgumentException' with message 'A stream must either be a resource or a string.' in [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\monolog\monolog\src\Monolog\Handler\StreamHandler.php:50 Stack trace:
#0 [path-to-project]\lib\google-api-php-client-2.0.0-RC1\src\Google\Client.php(1042): Monolog\Handler\StreamHandler->__construct()
#1 [path-to-project]\lib\google-api-php-client-2.0.0-RC1\src\Google\Client.php(1027): Google_Client->createDefaultHttpClient()
#2 [path-to-project]\lib\google-api-php-client-2.0.0-RC1\src\Google\Service\Resource.php(190): Google_Client->getHttpClient()
#3 [path-to-project]\lib\google-api-php-client-2.0.0-RC1\vendor\monolog\monolog\src\Monolog\Handler\StreamHandler.php on line 50

Have you tried adding a php.ini to your root that includes:
extension = "php_curl.dll"
I had a similar problem with gitkit + app engine php local and this solved the problem.

Is this still an issue?
Also is everyone aware of the google/cloud library has Datastore package?


Fix prefixes of metric units of measurement

According to NIST (and WolframAlpha, and Wikipedia)
http://www.nist.gov/pml/wmd/metric/prefixes.cfm

Add demonyms

YAHOO! :muscle:


Change test organization for shared tests.

Description

Change test organization for shared tests. These tests are now organized under the corerp directory.
Separate cloud/non-cloud tests
Organize the corerp tests as per https://github.com/radius-project/design-notes/pull/35. There will be more PRs that will follow to re-org the other tests.

Type of change

This pull request adds or changes features of Radius and has an approved issue (#6588 ).

Fixes: Fixes part of https://github.com/radius-project/radius/issues/6588. This is a part of a multi-PR fix

long-running test is failed because it cannot get the secret to log in azure. it is expected.