Subject, from, to and others API's encoding problem

As I mention in comment https://github.com/swoosh/swoosh/issues/489#issuecomment-657914196, I have a problem with subject, from, to and other API function encoding. When I type anything with Russian - it's turns in gibberish.
I have a template for my mail which works fine and Russian words encoded correctly. But subject and from is not.

Here is downloaded email source link. Unfortunately github doesn't support uploads with eml extension.
Here is my code in umbrella Phoenix app for building this email:
config/config.exs
config :proling_web, ProlingWeb.Mailer,
  adapter: Swoosh.Adapters.Gmail,
  access_token: {:system, "GMAIL_API_ACCESS_TOKEN"}

apps/proling_web/mix.exs
  defp deps do
    [
      {:phoenix, "~> 1.5"},
      {:phoenix_pubsub, "~> 2.0"},
      {:phoenix_ecto, "~> 4.0"},
      {:gettext, "~> 0.11"},
      {:proling, in_umbrella: true},
      {:plug_cowboy, "~> 2.3"},
      {:absinthe, "~> 1.5"},
      {:absinthe_plug, "~> 1.5"},
      {:absinthe_phoenix, "~> 2.0"},
      {:poison, "~> 2.1"},
      {:dataloader, "~> 1.0"},
      {:pow, "~> 1.0.20"},
      {:mail, "~> 0.2"},
      {:phoenix_swoosh, "~> 0.2.0"}
    ]
  end

apps/proling_web/lib/proling_web/mailer.ex
defmodule ProlingWeb.Mailer do
  use Pow.Phoenix.Mailer
  use Swoosh.Mailer, otp_app: :proling_web

  import Swoosh.Email

  require Logger

  @impl true
  def cast(%{user: user, subject: subject, text: text, html: html}) do
    new()
    |> to({"", user.email})
    |> from({"ProLing"<EMAIL_ADDRESS>    |> subject(subject)
    |> html_body(html)
    |> text_body(text)
  end

  @impl true
  def process(email) do
    email
    |> deliver()
    |> log_warnings()
  end

  defp log_warnings({:error, reason}) do
    Logger.warn("Mailer backend failed with: #{inspect(reason)}")
  end

  defp log_warnings({:ok, response}), do: {:ok, response}
end

apps/proling_web/lib/proling_web/emails/request_confirmation.ex
defmodule ProlingWeb.RequestConfirmation do
  use Phoenix.Swoosh, view: ProlingWeb.EmailView, layout: {ProlingWeb.LayoutView, :email}

  def request_confirmation(user) do
    new()
    |> from({"Переводческая компания ProLing"<EMAIL_ADDRESS>    |> to({"", user.email})
    |> reply_to({"Переводческая компания ProLing"<EMAIL_ADDRESS>    |> subject("Ваша заявка получена")
    |> render_body("request_confirmation.html", %{})
  end
end

And I'm using API right now within iex:
ProlingWeb.RequestConfirmation.request_confirmation(%{email<EMAIL_ADDRESS>|> ProlingWeb.Mailer.deliver

I'm not sharing templates because they're set properly and there is no problem with body. But if it would be helpful I can share it too.
Let me know how I can help to resolve this issue please.

I've moved to Swoosh.Adapters.SMTP and it works properly with subject, from and to encoding. I think would be more reliable and simple to stick with it.

Hey Vadim,
I'm glad you have found a reliable workaround. However, I'm just curious about if you were testing it on CMD or Powershell on Windows? I did some testing locally and it seems that the shell could be causing the problem. I'm pretty certain that I've tested Chinese with Swoosh before but not with Gmail Adapter, and I've always been using Docker.
If you could show me what you see when using IEx while building the email, it would be of great help.
This is what I see if I use iex.bat -S mix instead of running it in Docker.

If this was not the cause, my hunch is that Mail is not encoding non-ASCII headers properly.

Hi Po! I've not tested this at Windows or Powershell, I've done it with OS X and Hyper terminal which supports various enconding. I think this problem related to this issue, because Mail supports set of certain encodings. That's why Gmail adapter works so with Russian characters. Also I can't see any reason to use it instead of SMTP because of handling renew of access tokens. But ofcourse, I can be wrong :)

That's most likely it. Thanks for tracking it down. Too bad mail has basically been abandoned now.


indexer: temp remove objects partial index

Description
temp. remove them b/c the indices building takes long and to unblock testnet and mainnet release
Test plan
ci

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:
[ ] REST API:

no need any more


ENH Enhances and refactors sum kernel

I noticed that our sum reduction kernel was awkwardly written. The enhancement to size1 > 1 was done wrong. Each work group consumes shared memory equal to work_group_size * size1 but that is unjustified and will even cause shared memory overflow when size1 is too big.
The root cause it that there's a loop on n_rows when size1 > 1, but it was only necessary to repeatedly apply the same kernel to the other rows. That enables a better allocation of shared memory (constant w.r.t size1) and also reads much better overall since it doesn't require to abstract the operator anymore.

Merged latest fixes and applied suggestions

Will merge when pipeline succeeds


Able to select locked actor in the world

Hi, reporting, if I locked an actor, I'm  still able to click select in the  world view. It should not

Fixed in DM.
Newer version supports other editor modes.


Azure AAD auth provider is using AAD group's displayName instead of unique objectId for auth

Currently guard updates AAD token of the user with display name of AAD groups the user belongs to. Several AAD groups in an organization can have the same display name. This can cause group claim based auth using Guard webhook to be unreliable.
Code here: https://github.com/appscode/guard/blob/master/auth/providers/azure/graph/graph.go#L212
Fix: Update Guard to use AAD group's unique id/object id objectId (which is guaranteed to be unique) instead of display name which might not be unique.
E.g. here: https://msdn.microsoft.com/en-us/library/azure/ad/graph/api/groups-operations
cc: @tamalsaha

Fixed in https://github.com/appscode/guard/releases/tag/0.1.4


Include WebsiteContent.file url in metadata written to the backend (github)

The serializers used for writing content to files in github should insert the file url into the metadata for any WebsiteContent objects that have uploaded files, using the field name as specified in the site config.
The management command for syncing from github back to the database should also properly handle the file url in the metadata.

Is this necessary for linked images, like the ones in the testimonials in ocw-www?

Yes, this should have been closed by merging https://github.com/mitodl/ocw-studio/pull/333, entered the wrong issue # in the description.


Unsafe legacy lifecycles warring for Pickers

I have gone through these following points

[]   Check latest documentation: https://docs.nativebase.io/
[]   Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[]   Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[]   Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[]   For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[]   For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description
Adding picker component to any page throws following warning:

Warning: Unsafe legacy lifecycles will not be called for components using new component APIs.
%s uses %s but also contains the following legacy lifecycles:%s%s%s
The above lifecycles should be removed. Learn more about this warning here:
https://fb.me/react-async-component-lifecycle-hooks, Styled(PickerNB), getDerivedStateFromProps(), ,
UNSAFE_componentWillReceiveProps,

node, npm, react-native, react and native-base version, expo version if used, xcode version
native-base: 2.13.5,
expo: 34.0.4
,
Steps to reproduce
Just add Picker to the page.
Is the bug present in both iOS and Android or in any one of them?
Only on IOS

same here, IOS only

same issue as well:
native-base: 2.13.5
expo: 32.0.0
The picker still seems to work as normal, I just get the warning every time I navigate to that screen.

I have also noticed this with the version of react-native-keyboard-aware-scroll-view v0.8 which is being bundled with the latest version of native-base which is using react deprecated lifecycle method componentWillReceiveProps can you please update to use library to latest v0.9.1 which resolves this issue.

Same here (same as OP).

Same

same. We hope someone will submit a PR for this warning.

Can we try it with the latest version 2.13.7 and see if the issue still persists?

@sankhadeeproy007 Still having the issue with 2.13.7
package-lock.json:

in-app screenshot:

warning from terminal:
[09:52:54] Warning: Unsafe legacy lifecycles will not be called for components using new component APIs.

%s uses %s but also contains the following legacy lifecycles:%s%s%s

The above lifecycles should be removed. Learn more about this warning here:
https://fb.me/react-async-component-lifecycle-hooks, Styled(PickerNB), getDerivedStateFromProps(), ,
  UNSAFE_componentWillReceiveProps,

Exact same problem for me, any updates?

Fixed in 2.13.8


Require 1 confirmation when opening channels

We would like to support 0-conf, but rust-lightning immediately closes the channel because of this snippet1.
The gist of it is:

rust-lightning marks the channel as ready as soon as the fund transaction appears in the mempool.

It then sees that the funding transaction has 0 confirmations. It interprets this as the transaction being unconfirmed due to a chain reorg, so it closes the channel for safety reasons.

We could also modify rust-lightning, but that is slightly riskier.

I can confirm this behavior with my setup, let's get this in :)
Note: I overcame my problem of the taker not being able to connect with the maker by restarting nigiri :)

This does not make sense to me...

It doesn't make sense to me either 😭 I think it's a bug.

bors r+


added several examples

https://github.com/MicrosoftDocs/windows-powershell-docs/issues/300

Dear @JohanFreelancer9,
kindly do the copy editor review for this PR.
Dear @e0i, for your information
Thank you

Docs Build status updates of commit 8dd638d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docset/windows/hyper-v/New-VM.md
:warning:Warning

Details

docset/mdop/appvclient/set-appvclientmode.md
:warning:Warning

Details

docset/mdop/appvclient/remove-appvclientconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvclient/set-appvclientconfiguration.md
:warning:Warning

Details

docset/mdop/agpm/unlock-controlledgpo.md
:warning:Warning

Details

docset/windows/appvclient/Start-AppvVirtualProcess.md
:warning:Warning

Details

docset/windows/appvclient/Set-AppvClientPackage.md
:warning:Warning

Details

docset/mdop/appvsequencer/expand-appvsequencerpackage.md
:warning:Warning

Details

docset/windows/appvclient/Add-AppvClientPackage.md
:warning:Warning

Details

docset/mdop/appvclient/add-appvclientpackage.md
:warning:Warning

Details

docset/windows/appvclient/Remove-AppvClientPackage.md
:warning:Warning

Details

docset/windows/appvclient/Stop-AppvClientConnectionGroup.md
:warning:Warning

Details

docset/windows/appvsequencer/Expand-AppvSequencerPackage.md
:warning:Warning

Details

docset/windows/appvclient/Mount-AppvClientConnectionGroup.md
:warning:Warning

Details

docset/mdop/appvserver/publish-appvserverpackage.md
:warning:Warning

Details

docset/mdop/appvclient/get-appvvirtualprocess.md
:warning:Warning

Details

docset/windows/appvclient/Set-AppvClientMode.md
:warning:Warning

Details

docset/windows/appvclient/Set-AppvClientConfiguration.md
:warning:Warning

Details

docset/mdop/appvclient/get-appvpublishingserver.md
:warning:Warning

Details

docset/mdop/appvclient/sync-appvpublishingserver.md
:warning:Warning

Details

docset/mdop/appvserver/remove-appvserverconnectiongrouppackage.md
:warning:Warning

Details

docset/windows/appvclient/Remove-AppvClientConnectionGroup.md
:warning:Warning

Details

docset/mdop/appvclient/mount-appvclientpackage.md
:warning:Warning

Details

docset/mdop/appvserver/get-appvserverpackage.md
:warning:Warning

Details

docset/mdop/appvclient/stop-appvclientconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvserver/add-appvserverconnectiongrouppackage.md
:warning:Warning

Details

docset/mdop/appvserver/get-appvserverconnectiongroup.md
:warning:Warning

Details

docset/windows/appvclient/Get-AppvVirtualProcess.md
:warning:Warning

Details

docset/mdop/appvserver/update-appvserverconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvserver/set-appvserverconnectiongrouppackage.md
:warning:Warning

Details

docset/mdop/mbam/disable-mbamwebapplication.md
:warning:Warning

Details

docset/mdop/appvserver/set-appvserverpackage.md
:warning:Warning

Details

docset/mdop/appvserver/remove-appvserverpackage.md
:warning:Warning

Details

docset/windows/appvclient/Set-AppvPublishingServer.md
:warning:Warning

Details

docset/mdop/appvserver/set-appvserverconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvsequencer/update-appvsequencerpackage.md
:warning:Warning

Details

docset/mdop/appvserver/unpublish-appvserverpackage.md
:warning:Warning

Details

docset/mdop/mbam/disable-mbamcmintegration.md
:warning:Warning

Details

docset/mdop/appvclient/set-appvpublishingserver.md
:warning:Warning

Details

docset/mdop/appvserver/get-appvserverpackagedeploymentconfiguration.md
:warning:Warning

Details

docset/mdop/mbam/enable-mbamdatabase.md
:warning:Warning

Details

docset/mdop/mbam/get-mbamcmintegration.md
:warning:Warning

Details

docset/mdop/mbam/enable-mbamcmintegration.md
:warning:Warning

Details

docset/mdop/mbam/enable-mbamreport.md
:warning:Warning

Details

docset/mdop/mbam/get-mbamreport.md
:warning:Warning

Details

docset/mdop/appvsequencer/new-appvsequencerpackage.md
:warning:Warning

Details

docset/mdop/mbam/disable-mbamreport.md
:warning:Warning

Details

docset/mdop/mbam/test-mbamwebapplication.md
:warning:Warning

Details

docset/mdop/mbam/test-mbamcmintegration.md
:warning:Warning

Details

docset/mdop/medv/export-medvconfiguration.md
:warning:Warning

Details

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

docset/windows/hyper-v/New-VM.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/set-appvclientmode.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/remove-appvclientconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/set-appvclientconfiguration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/agpm/unlock-controlledgpo.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvclient/Start-AppvVirtualProcess.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvclient/Set-AppvClientPackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvsequencer/expand-appvsequencerpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Add-AppvClientPackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/add-appvclientpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Remove-AppvClientPackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvclient/Stop-AppvClientConnectionGroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvsequencer/Expand-AppvSequencerPackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvclient/Mount-AppvClientConnectionGroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvserver/publish-appvserverpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/get-appvvirtualprocess.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Set-AppvClientMode.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvclient/Set-AppvClientConfiguration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/get-appvpublishingserver.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/sync-appvpublishingserver.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/remove-appvserverconnectiongrouppackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Remove-AppvClientConnectionGroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/mount-appvclientpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/get-appvserverpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/stop-appvclientconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/add-appvserverconnectiongrouppackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/get-appvserverconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Get-AppvVirtualProcess.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvserver/update-appvserverconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/set-appvserverconnectiongrouppackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/mbam/disable-mbamwebapplication.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvserver/set-appvserverpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/remove-appvserverpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Set-AppvPublishingServer.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvserver/set-appvserverconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvsequencer/update-appvsequencerpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/unpublish-appvserverpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/mbam/disable-mbamcmintegration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/set-appvpublishingserver.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/get-appvserverpackagedeploymentconfiguration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/mbam/enable-mbamdatabase.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/mbam/get-mbamcmintegration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/mbam/enable-mbamcmintegration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/mbam/enable-mbamreport.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/mbam/get-mbamreport.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvsequencer/new-appvsequencerpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/mbam/disable-mbamreport.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/mbam/test-mbamwebapplication.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-file-not-found] Invalid file link: 'index.md'.

docset/mdop/mbam/test-mbamcmintegration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/medv/export-medvconfiguration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

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

Docs Build status updates of commit fd6f02a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/New-VM.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a856df5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/New-VM.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@dariomws @get-itips @tseward
Peer review needed for this PR. Thanks.

Docs Build status updates of commit c6bb3ab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/New-VM.md
:white_check_mark:Succeeded

docset/winserver2012-ps/hyper-v/New-VM.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

hello, added for WS2012 and WS2012 R2
Thank you

Docs Build status updates of commit 6e9e73e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/New-VM.md
:white_check_mark:Succeeded

docset/winserver2012-ps/hyper-v/New-VM.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/hyper-v/New-VM.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 4336618:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/New-VM.md
:white_check_mark:Succeeded

docset/winserver2012-ps/hyper-v/New-VM.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/hyper-v/New-VM.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 397ccd3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/New-VM.md
:white_check_mark:Succeeded
View (win10-ps)

docset/winserver2012-ps/hyper-v/New-VM.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/hyper-v/New-VM.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

For more details, please refer to the build report.
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.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


User mailboxes

Forking discussion from #4. From https://github.com/osuosl-cookbooks/proj-seagl/issues/4#issuecomment-1413089833:

For context, here are our [email needs], as far as I understand them:

We ideally would have individual @seagl.org mailboxes for folks, though we could possibly work around the lack of this with some alias forwarding + rules in folks' personal inboxes
We need some kind of sharing mechanism for certain email addresses (think<EMAIL_ADDRESS><EMAIL_ADDRESS>etc.) where multiple people will want to respond to emails as they come in
We need people to be able to send from @seagl.org mailing addresses, including the above shared addresses
We have pretty standard mailing list needs, though we'd ideally like to be able to administer lists ourselves

What support does OSUOSL offer here? Looking at https://osuosl.org/services/hosting/details/#e-mail it seems like it may make the most sense to run our own mail systems and use OSUOSL's relays for virus and spam protection? Though ideally we would like to avoid running our own stuff as much as possible, if there's something else not mentioned on that page.

We have been working on getting a more centralized mailbox hosted solution going, but it's not quite ready yet for projects. Do you have an idea of when you would like this ready?

We probably want it ASAP since we're currently getting billed by Google for Work and this is a big blocker for moving off it. That being said maybe we could spin up our own mail servers on OpenStack (@altsalt I know had a solution in mind) and we can coordinate moving data into OSUOSL's solution whenever that's ready?

Yes, I've had my eyes on Mailu for a while now, but less stuff that we are running that isn't conference-event specific, the better.

@ramereth any objections to us just spinning up Mailu on an OpenStack VM?

@strugee nope not at all, Given our current queue, I'm not sure when we'll get to this going on our end. Do you need anything from us to do that?

No problem, we'll work on setting this up. I don't think we need anything special though I'll let you know if we do.


NavController.loadPage does not handle promise rejection

Note: for support questions, please use one of these channels:
https://forum.ionicframework.com/
http://ionicworldwide.herokuapp.com/
Short description of the problem:
When you have an error in a second level page it does not propagate to the top level and it is not showed in the console
What behavior are you expecting?
Show errors in the console for all pages
Steps to reproduce:

Create a start project ionic start test --v2 --ts
Create a Page4
Add an error in Page4. Like undefined error.
4.Do this.nav.push(Page4); in Page1
Error will not be showed

This on Page1
goToPage4() {
    this.nav.push(Page4).then(
      response => {
        console.log('Response ' + response);
      },
      error => {
        console.log('Error: ' + error);
      }
    ).catch(exception => {
      console.log('Exception ' + exception);
    });;
  }

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
https://forum.ionicframework.com/t/ionic-2-error-not-showing-in-nav-push-somepage/49418/7
Which Ionic Version? 1.x or 2.x
2..0.0-beta.4
Plunker that shows an example of your issue
http://plnkr.co/edit/OBQjWnCgVkf7Z7mXezBs
Here it works but if you do it on a real project it does not.
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.1.1
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.1
Ionic CLI Version: 2.0.0-beta.17
Ionic App Lib Version: 2.0.0-beta.8
ios-deploy version: 1.7.0
ios-sim version: 4.1.1
OS: Mac OS X El Capitan
Node Version: v5.10.1
Xcode version: Xcode 7.3 Build version 7D175

+1, this is extremely annoying. I spent hours today trying to figure out why calls to this.nav.push() were dropping off a cliff.

@layton-glympse @lricoy Are you by chance also using Mac OS X? I guess that it's something platform-specific because all reports are coming from Mac OS X. I opened a new issue (#6433) to track all of them.

@iignatov yes

When this issue was opened, I was able to reproduce the OP's problem under Chromium on Debian (which led me to suspect loadPage), so I don't think it was OS specific. I use past tense because potentially things changed in Ionic beta 6.
If you look at the area around line 1412 in this commit diff, you should see a call to compileInHost that has been replaced by a call to DynamicComponentLoader's loadNextToLocation. They both return Promises, and it still looks to me like this loadPage function does not properly propagate errors to its caller, but perhaps this has become moot.
When I was troubleshooting the problem in this Ionic forum thread, template parse errors indirectly triggered by calls to NavController would not be delivered back to app code, and this loadPage call to compileInHost looked to be the culprit. It gets a Promise back, and only calls then on it. No error handler, no returning the promise back to its caller. I think that's where the errors get swallowed.
While the main purpose of this commit may indeed have been completely different, the call that I traced was removed by it and replaced by different code, and the symptoms appear to have also changed.

An update: using the original testbed (a deliberate error in a page's constructor that is being loaded via NavController.push) with Ionic beta 6, the error is in fact properly propagated back to callers and displays in the error console as expected.

@rapropos Ahh you were right ahead of me, i was fixing to report that i could not repro this issue with beta.6. Funny enough though, even with beta.4 i cant seem to repro this issue, i get an undefined error (which is expected) when trying to push the page. Im on the latest chrome canary.

@rapropos Would you mind trying again with the original plunker and seeing if you can repro the issue?

@jgw96 apologies but I cannot downgrade my testbed project, apparently because the Ionic starter templates are a moving target. I get zillions of es6-shim errors and some other problems with SCSS when manually downgrading ionic-angular and angular2 in package.json. Does not look easily fixable.

@rapropos Actually, you can use this plunker: http://plnkr.co/edit/OBQjWnCgVkf7Z7mXezBs to test with

@jgw96 sorry, but as OP noted, the event timing model used by plunker blows the problem away. I don't think anybody would ever have been able to reproduce it there.

Sorry, i meant you could pull that down and test it on a device haha (: Should have been more clear. I am gonna go ahead and close this issue, as i cant seem to repro it beta.6. If anyone has this issue with beta.6 feel free to comment and i will reopen. Thanks for using Ionic everyone!

It seems to be resolved - the OP confirmed that it's fixed in beta.6:

I see it fixed with the new version beta 6 and angular beta 15

@jgw96 I'm seeing silent fails of nav.push in beta6 still when there are template syntax errors (https://github.com/driftyco/ionic/issues/6433, https://github.com/driftyco/ionic/issues/6259, and https://github.com/driftyco/ionic/issues/6253)

@wli Alright, doing a quick test now.

I'm also hanging out on slack in #ionic-v2 if you need to chat

@wli Hey, sure you can message me on slack, im @justin . So i just did a little test with one of my apps  with nightly (wasnt the latest nightly, but one that was released right after beta.6). I intentionally put an error in the template, tried to push it, and it seemed that the error bubbled up fine in the promise. Would you mind trying with nightly? Im fixing to do another test with Beta.6.

@wli So i just did another test with beta.6. Same setup as my message above and the error bubbled up nicely. Could you put up a simple test app on Github that uses beta.6 and seems to have this issue?

@iignatov Are you still having this issue with beta.6 or is it working fine for you?

@jgw96 I can't reproduce this on Windows and all reports are coming from Mac users, so I guess that it might be platform-specific, i.e. Mac OS X or Safari/WebKit.
On the other hand after reading some comments it seems that the behavior that I'm observing on Windows (with Chrome) is more likely a feature of v8/Blink, but I'm still not absolutely sure about this because I got the same behavior with Firefox too.
I think that @rapropos is maybe on to something, I'll take a closer look at the code again tomorrow.

Are you still having this issue with beta.6 or is it working fine for you?

@jgw96 I'm actually not able to reproduce the issue on Windows at all - both locally and in plunker the errors are shown in the console as expected (in issue #6433 I just collected the feedback from the forum).

@iignatov I am testing on OSX El Capitan with Chrome canary and it works fine for me in my test app, our ionic-conference-app and in plunker.

Update: Works fine for me in Firefox on osx too

@wli Are you testing with chrome?

Yep, testing with Chrome. I've been trying to repro in a clean env but can't get it to trigger. May have to leave this for another day.

@wli Hmm really weird. If your able to repro it please tell me, id love to know! Im gonna leave this issue closed for now.

Sounds good, I'll reopen if I can ever figure out the repro conditions. It's definitely triggering under some set of circumstances for beta6 (I've been on beta6 ever since it was released, and triggered it earlier today in our app - unfortunately I attempted some workarounds instead of snapshotting the state).
I suspect it's related to calling the onPageWillEnter and onPageDidEnter hooks, but like I said, I haven't been able to reproduce in a clean environment.

For future reference / in case it helps with this debugging, this is what I had to do to upgrade from beta4 to beta6 successfully on Apr 20:

The template it was used is pretty simple, just some uses of {{ _question.text }} and other properties.

I can confirm that promise rejection is working for me now with beta.6 on mac El Captain/ Chrome Canary as well.
I will try to test later what @wli and @layton-glympse reported about template errors failing silently but it might be another issue all together.

I created two plunker demos for testing the problem and a possible fix (however I'm not absolutely sure if the problem would be reproducible in Plunker):

Original beta.6 code

Patched beta.6 code

Could anyone experiencing such issues run the demos in Safari and share the results here?
Note that at least in Chrome/Firefox the plunker has to be stopped and re-run after a click on each button.

@iignatov Both plunkrs work as expected (logging errors) for me on Safari but as you said, I can't confirm that this solves the issue of running outside of plunkr. I will try to reproduce it locally tonight.


DBus API change to switch to discrete resolution lists

This builds on top of #392
Changes from a dpi min/max to a discrete list of "here are the resolutions we support". This makes it easier for clients to do the right thing.

Not sure why, but you need to rebase this one too.

This broke piper. Is an update for it being worked on?

I guess the breakage was.. intentional, considering @bentiss' comment :) I just opened https://github.com/libratbag/piper/pull/186.


Create a simple JIT wrapper for regular Python functions

Changes included in this PR

Adds a jit_wrapper decorator that is both easier to use and also much faster than objmode (doesn't require compilation during runtime). This interface fits the common UDF case for calling regular Python especially well.
Testing strategy

Added unit test and also tested the AI "the pile" data processing example (will be added in a separate PR).
User facing changes

Checklist

[ ] Pipelines passed before requesting review. To run CI you must include [run CI] in your commit message.
[x] I am familiar with the Contributing Guide
[x] I have installed + ran pre-commit hooks.

@ehsantn Can you provide me some context on this change? Was this directly requested or has this been a known TODO for some time?

This came out of my work on AI examples and seeing the issues of objmode (interface, performance, reliability). This will have more feedback and iterations soon probably.

I haven't seen activity on the objmode side but will monitor.


imporove release workflow ( installing plugins is now easier than before)

Unity

Created .unitypackage

Added unity project for the above
Included flatbuffers.dll

Godot

Multi-platform support

UnrealEngine

Included flatbuffer .h/.lib in UnrealEngine

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8cac813) 30.29% compared to head (7c2cd12) 30.29%.
Report is 1 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #89   +/-   ##
=======================================
  Coverage   30.29%   30.29%
=======================================
  Files          99       99
  Lines        2862     2862
  Branches      388      388
=======================================
  Hits          867      867
  Misses       1940     1940
  Partials       55       55

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Pre devnet-4 interop testing

Description
Teku should be ready to participate in devnet-4 now. We can run local testnets to ensure a smooth devnet4 launch.
Need to check with other EL/CL teams to know if they have versions ready for devnet 4.

Status of testing being shared here: https://hackmd.io/@lucassaldanha/BkWWUBqk1x


Allow stream message json data to not be prefetched during stream reading.

When reading a stream (or all) you may not be interested in the JsonData payload of every single message. As there is currently no limit on the size of the JsonData payload in the core (limitation is store specific), this PR allows the user to disable prefetching of that JsonData
The key changes are:

IReadOnlyStreamStore.ReadAllForwards(), .ReadAllBackwards(), .ReadStreamForwards(), .ReadStreamBackwards() all have an additional, optional parameter prefetchJsonData = true.
StreamMessage.JsonData {get;} property has been replaced with a method Task<string> StreamMessage.GetJsonData(). When prefetch is turned off this will result will result in a call to the server.
InMemoryStreamStore simulates the async nature using a task offload if prefetching is turned off.
Prefetching is enabled by default.

Note there is a condition where the message may be deleted between handling a StreamMessage instance and calling the GetJsonData(). The implementation here is to return a null when that occurs.
This is a breaking change.

Note: I'd like to separately support reads that allow server side of filtering by StreamMessage.Type or StreamId prefix.

I should add, one of the other drivers of this was the HTTP API where we want to be able to GET streams with links to individual message json data (as opposed to embedding it).


fix: [UIE-8007] - DBaaS display host in summary details

Description 📝
Fix the display of host in DBaaS summary details
Changes  🔄
List any change relevant to the reviewer.

Remove MongoDB related code as it is no longer supported
Correctly show primary host in details

Target release date 🗓
11/12/24
Preview 📷

Before
After

How to test 🧪
Prerequisites

Managed Databases Beta capability
dbaasV2 feature flag

Reproduction steps

Navigate to database summary details page

Verification steps

Host is displayed

As an Author I have considered 🤔
Check all that apply

[x] 👀 Doing a self review
[x] ❔ Our contribution guidelines
[x] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[x] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[x] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

@corya-akamai looks like the the database details page is broken when tried to access the database is in provisioning state.

Strange. I'm able to render GA and beta summary.

Interesting I'm able to reproduce page crash when navigating to details page.
https://github.com/user-attachments/assets/e97dc350-4b0f-496b-a4e9-58a155101272

@cpathipa You are running into a Vite caching issue. Try clearing the Vite cache and your browser cache.
rm -r packages/manager/node_modules/.vite

Thanks @bnussman thats cache issue.


Error importing component OpenPim

Hi,
I imported the OpenPim components with the following command:
java -jar pim-components.car studio-deploy <DIRECTORY WHERE Talend IS INSTALLED>
but i get an error when restarting Talend.

Hi @borisdagnon,
Can you please clarify what Talend version you are using? If you are using Talend 8 please make sure that you are using java version 11 (this is quite old version) instead of something else because Talend requires java 11.
Thanks,
Slava Pedak

Hi,
I'm using the version <IP_ADDRESS>11109_1610 of Talend.
And i specified the version 11 of Java in the config.

Thanks.

Hi @borisdagnon,
But what jdk are you using to start Talend? You should take a look into TOS_DI-win-x86_64.ini file.
You can specify the java version there like
-vm
C:\Program Files\Java\jdk-<IP_ADDRESS>\bin
-vmargs
-Xms512m
-Xmx1536m
...
Thanks,
Slava Pedak

Hi @openpim
That's how it looks like now.

Sorry,
This is what i'm having now.

Hi,
The path C:\Program Files\Java\jdk-<IP_ADDRESS>\bin is just an example, this is path I have at my computer. You should provide your real path there.
Thanks,
Slava Pedak


Callback-stop-criterion

New callbacks with stop criterions for function, gradient, lmo count and primal value stop criterions

Codecov Report

Merging #305 (b25ecf5) into breaking-02 (575f6b0) will decrease coverage by 0.73%.
The diff coverage is 54.83%.

@@               Coverage Diff               @@
##           breaking-02     #305      +/-   ##
===============================================
- Coverage        83.87%   83.13%   -0.74%
===============================================
  Files               16       17       +1
  Lines             1885     1880       -5
===============================================
- Hits              1581     1563      -18
- Misses             304      317      +13

Impacted Files
Coverage Δ

src/stop_criterion.jl
0.00% <0.00%> (ø)

src/tracking.jl
68.29% <87.50%> (-0.28%)
:arrow_down:

src/fw_algorithms.jl
82.35% <100.00%> (+0.06%)
:arrow_up:

src/oracles.jl
86.45% <0.00%> (-0.80%)
:arrow_down:

src/types.jl
84.69% <0.00%> (-0.36%)
:arrow_down:

src/utils.jl
84.96% <0.00%> (-0.23%)
:arrow_down:

src/linesearch.jl
82.39% <0.00%> (-0.13%)
:arrow_down:

src/active_set.jl
93.33% <0.00%> (-0.11%)
:arrow_down:

src/polytope_oracles.jl
92.22% <0.00%> (-0.09%)
:arrow_down:

src/norm_oracles.jl
95.53% <0.00%> (-0.08%)
:arrow_down:

... and 1 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 575f6b0...b25ecf5. Read the comment docs.

There are errors now due to former usage of the callback (check in the docs examples, examples and tests).
This will be due to callbacks not returning a boolean value


Yosys aborts with exception in peephole optimizers pass

Yosys aborts with a vector::_M_range_check exception in the peephole optimizers pass (PEEPOPT pass). This happens with the verilog code below, which I have reduced as much as possible into an MCVE.
module top(y, clk, wire1);
   output wire [1:0] y;
   input wire        clk;
   input wire [1:0]  wire1;
   reg [1:0]         reg1 = 0;
   reg [1:0]         reg2 = 0;
   always @(posedge clk) begin
      reg1 <= wire1 == 1;
   end
   always @(posedge clk) begin
      reg2 <= 1 >> reg1[1:1];
   end
   assign y = reg2;
endmodule

Steps to reproduce the issue
Yosys version that this was tested with: Yosys 0.8+411 (git sha1 70d0f389, clang 8.0.0 -fPIC -Os), which is the current master.
The following command was used to synthesise the design:
yosys -p 'read -formal rtl.v; synth; write_verilog rtl_yosys.v'

Expected behavior
Synthesis without any exceptions.
=== top ===

   Number of wires:                  4
   Number of wire bits:              8
   Number of public wires:           4
   Number of public wire bits:       8
   Number of memories:               0
   Number of memory bits:            0
   Number of processes:              0
   Number of cells:                  1
     $_ORNOT_                        1

2.27. Executing CHECK pass (checking for obvious problems).
checking module top..
found and reported 0 problems.

3. Executing Verilog backend.
Dumping module `\top'.

Actual behavior
Yosys aborts with a vector::_M_range_check exception.
2.7. Executing WREDUCE pass (reducing word size of cells).
Removed top 1 bits (of 2) from port B of cell top.$eq$rtl.v:7$2 ($eq).
Removed cell top.$eq$rtl.v:7$2 ($eq).
Removed top 30 bits (of 32) from port A of cell top.$shr$rtl.v:10$4 ($shr).

2.8. Executing PEEPOPT pass (run peephole optimizers).
terminate called after throwing an instance of 'std::out_of_range'
  what():  vector::_M_range_check: __n (which is<PHONE_NUMBER>3709551615) >= this->size() (which is 0)
zsh: abort (core dumped)  yosys -p 'read -formal rtl.v; synth; write_verilog rtl_yosys.v'

Fixed in b37c31e.

Thank you for the quick fix!


[HUDI-763] Add hoodie.table.base.file.format option to hoodie.properties file

What is the purpose of the pull request
In order to support multiple storage formats, store hoodie.table.base.file.format to hoodie.properties.

hoodie.table.base.file.format: default PARQUET

Brief change log

Store hoodie.table.base.file.format to hoodie.properties.

Verify this pull request
This pull request is a minal rework.
Committer checklist

[X] Has a corresponding JIRA in PR title & commit

[X] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@lamber-ken trying to understand why this should be needed.. can't we distinguish based on the input format for ORC, where we can create HoodieOrcInputFormat ..

@lamber-ken trying to understand why this should be needed.. can't we distinguish based on the input format for ORC, where we can create HoodieOrcInputFormat ..

+1

hi @vinothchandar @pratyakshsharma, thanks very much for reviewing this.
The base file format for each hudi dataset can't be changed across writes, so we need to store this option to hoodie.properties.

Fair enough.. Hypothetically, we could support a world where base files across partitions are in different formats.. So given its not a real problem today.. we can deal with it down the line?
btw there are also things like index.type which should go there today and are not.. IIRC there is a ticket for that as well.. main challenge there is how would we apply this change to the hoodie.properties file.. (dont think overwriting will be atomic...) also does this change also fix older tables automatically.. If we can flesh those out, that may be good. wdyt

Codecov Report

Merging #1512 into master will increase coverage by 0.06%.
The diff coverage is 100.00%.

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

Hi @vinothchandar, apologies for the delay.

different partitions use different formats

I know hive support that feature, it's easy for hive. If we want to support different partitions use different format, we alos need to store these partition file format infomation to hoodie.properties file as shown bellow, these are required when read / write.
At present, I can't think of a better way, correct me if I'm wrong or do you have any good ideas?
// hoodie.properties
hoodie.table.name=hudi_mor_table
hoodie.archivelog.folder=archived
hoodie.table.type=COPY_ON_WRITE
hoodie.timeline.layout.version=0

hoodie.table.base.file.format.partition.2020.01.08=ORC
hoodie.table.base.file.format.partition.2020.01.09=PARQUET
hoodie.table.base.file.format.partition.2020.01.10=PARQUET
hoodie.table.base.file.format.partition.2020.01.11=ORC
hoodie.table.base.file.format.partition.2020.01.12=ORC

// sync to hive, need to set fileformat
ALTER TABLE day_table PARTITION (dt='20200805') SET FILEFORMAT rcfile;

store things like index.type ..

I found a jira about it, "Persist the HoodieIndex type in the hoodie.properties file" [1],
It seems to be another topic : )
[1] https://issues.apache.org/jira/browse/HUDI-37

@lamber-ken : Storing per-partition specific metadata in hoodie.properties wont work as we are not versioning hoodie.properties. There is no atomicity guarantees across different cloud storages   for writers.
I think supporting different file formats within a table is not a priority but if we have to do, then we can instead store in .hoodie_partition_metadata first time we create it per partition. Hudi Hive Sync needs to then read this for each new partition getting added to hive to register the correct input format for that partition. I am not sure how Spark, Presto and Impala would work in this case. We need to evaluate before venturing out to supporting this.
Coming back to the original objective of this PR, since hoodie.properties is effectively write-once, we can use it to store default file format of the hoodie table. As part of HoodieTableMetaClient.initTableType alone, we should set the file format of table once. TO support existing tables,  we can keep the default storage layout as "PARQUET" and if the setting is not present in hoodie.properties (for already created tables), we should use "PARQUET" as default.

All review comments are addressed and fixed, thanks you all.

Just 1 suggestion. LGTM otherwise . thanks @lamber-ken

@prashantwason @bvaradar IIUC some of this PR overlaps with the changes you are making as well. can you both clarify so we can close or revive this as needed..

yes @vinothchandar , this overlaps with PR-1687 which got merged. PR-1687 exposes setting base-file format through deltastreamer and spark data-source writer.
@lamber-ken : Can you check current master branch and see if you still need any other functionality?


Cannot open file from explorer under admin mode

Issue Type: Bug
When VSCode is running under admin mode, nothing happens when either right-clicking on the icon on taskbar then creating a new window, or right-clicking on a file in explorer then selecting "Open with Visual Studio Code"
VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T13:12:49.994Z)
OS version: Windows_NT x64 10.0.18363

As far as I am aware this behavior is by design - you can only have one window when running in admin mode. Having said that, there seems to be a regression as I tend to remember that when trying to open a second window when running in admin mode there was an error dialog. You can still hear the "error sound" but the dialog does not appear.

/duplicate https://github.com/microsoft/vscode/issues/6560

@lszomoru yeah good finding, let's track that particular issue here: https://github.com/microsoft/vscode/issues/104493


⚠ Bofrost.es has degraded performance

In e6dab7b, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1617 ms

Resolved: Bofrost.es performance has improved in 868771f after 17 minutes.


API docs HTML is broken

Eg. API Docs link on https://github.com/apple/turicreate/blob/master/userguide/recommender/introduction.md#recommender-systems

Thanks for pointing that out @anushkmittal!
Looks like we have quite a few links that ended up 404ing. I'm guessing some of these pages have changed URLs over time and the content hasn't been updated. The full list of 404s is:
https://machinelearning.wustl.edu/mlpapers/paper_files/icml2003_ZhangJYH03.pdf
https://apple.github.io/turicreate/docs/userguide/object_detector/introduction.md
https://apple.github.io/turicreate/docs/userguide/sgraph/sfraph.md
https://apple.github.io/turicreate/docs/generated/turicreate.show.html
https://apple.github.io/turicreate/docs/api/generated/turicreate.load_sgraph.html
https://apple.github.io/turicreate/docs/api/generated/turicreate.recommender.MatrixFactorizationModel.html
https://apple.github.io/turicreate/docs/api/generated/turicreate.recommender.FactorizationModel.html
https://apple.github.io/turicreate/docs/turicreate.toolkits.recommender.html
https://apple.github.io/turicreate/docs/userguide/image_classifier/linear-regression.md
https://apple.github.io/turicreate/docs/userguide/image_classifier/logistic-regression.md
https://apple.github.io/turicreate/docs/api/turicreate.toolkits.text_analytics.html and\n[SArray](https://apple.github.io/turicreate/docs/api/generated/turicreate.SArray.html
http://www.aaai.org/Papers/KDD/1996/KDD96-037
https://apple.github.io/turicreate/docs/api/generated/turicreate.linear_regression.LinearRegression.list_fields.html
https://apple.github.io/turicreate/docs/api/generated/turicreate.linear_regression.LinearRegression.get.html
https://apple.github.io/turicreate/docs/userguide/supervised_learning/logistic-regression.md
https://apple.github.io/turicreate/docs/userguide/supervised_learning/svm.md
https://apple.github.io/turicreate/docs/userguide/supervised_learning/boosted_trees_classifier.md
https://apple.github.io/turicreate/docs/userguide/supervised_learning/random_forest_classifier.md
https://apple.github.io/turicreate/docs/userguide/supervised_learning/decision_tree_classifier.md
https://apple.github.io/turicreate/docs/userguide/deployment/linear-regression.md
https://apple.github.io/turicreate/docs/userguide/supervised_learning/boosted_trees_regression.md

And there are also some 301s/302s:
https://labrosa.ee.columbia.edu/millionsong
https://www.naftaliharris.com/blog/visualizing-dbscan-clustering
https://stats.idre.ucla.edu

Oh, and the above is for the user guide. The API docs have these 404s as well:
http://www.ics.uci.edu/~smyth/courses/cs277/papers/intro-rec-sys-handbook.pdf
http://statweb.stanford.edu/~tibs/ElemStatLearn
http://www.aaai.org/Papers/KDD/1996/KDD96-037
https://www.cis.upenn.edu/~treebank/tokenization.html
https://www.kaggle.com/wiki/LogarithmicLoss

And these 301s/302s:
http://amstat.tandfonline.com/action/cookieAbsent
https://dl.acm.org/citation.cfm?id=279236
http://epubs.siam.org/action/cookieAbsent
http://proceedings.mlr.press/v37/neyshabur15.html
https://dl.acm.org/citation.cfm?id=1015332
http://www.research.att.com/people/Volinsky_Christopher_T/custom_index.html?utm_source=twitterfeed&utm_medium=twitter
https://www.microsoft.com/en-us/research/publication/stochastic-gradient-tricks/?from=http://research.microsoft.com/apps/pubs/default.aspx?id=192769
https://www.csie.ntu.edu.tw/~b97053/paper/Rendle2010FM.pdf
http://www.jstor.org/stable/2346178
https://en.wikipedia.org/wiki/Svm
https://www.naftaliharris.com/blog/visualizing-dbscan-clustering
https://publikationen.bibliothek.kit.edu/1000007159/4541
https://academic.oup.com/imajna/article-abstract/8/1/141/802460


VSCode hangs when opening python file

Issue Type: Bug

open vscode
open python file, eg tasks.py
vscode becomes unresponsive
try disabling python extension and observe same behavior

VS Code version: Code 1.26.0 (4e9361845dc28659923a300945f84731393e210d, 2018-08-13T16:25:59.521Z)
OS version: Linux x64 4.15.0-30-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz (4 x 3101)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarewebgl: enabledwebgl2: enabled

Load (avg)
3, 2, 1

Memory (System)
15.37GB (9.79GB free)

Process Argv
/usr/share/code/code --unity-launch

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

arm
dan
0.2.0

gitlens
eam
8.5.4

plantuml
jeb
2.8.5

rainbow-csv
mec
0.4.2

atom-keybindings
ms-
3.0.4

cpptools
ms-
0.17.7

vscode-docker
Pet
0.1.0

gitconfig
sid
1.0.1

code-spell-checker
str
1.6.10

alphabetical-sorter
ue
2.0.1

Same issue is happening with other plugins.  I'm having the issue with the PowerShell plugin. I have found that:

Exit the application  (Task Manager on Windows)
Open with a new work space so you are not point to old file that locked up the applications
Disable your plugin
Reload the application
Reopen the file, change 1 character and save.
Ensable your plugin
Reload the application

Was there a new plug-in caching mechanic in the new version?

@sandy081: looks like pasting this line causes a crash
    cmd = "git-clang-format --style=\"{{BasedOnStyle: Google, ColumnLimit: 100, IndentWidth: 2, " \           "AlignConsecutiveAssignments: true}}\" {COMMIT_SHA} -- ./**/*.proto > {OUTPUT}".format(

It hangs for me (same version of vscode) around this position in that string (if entered manually):
cmd = "git-clang-format --style=\"{{BasedOnStyle: Google, ColumnLimit: 100, In
I'm wondering if the {{ escape is not parsed, so the contents left of the : characters are being processed as format specifiers?
https://docs.python.org/3/library/string.html#formatstrings

Sample from #56338:
record = {
    "headers": {k: str(v) for k, v in self.request.META.items() if k.startswith('HTTP_')}
}

File https://github.com/MagicStack/MagicPython/issues/150 against MagicPython.


Unable to run cspell due to stale files somewhere

I've long been using cspell as a plugin for VSCode and it works well--thanks! Today I installed the command-line version (npm install -g cspell) and then tried this:
$ cspell --help
-bash: /Users/msorens/code/git/proj-ui/node_modules/cspell/dist/app.js: No such file or directory

I have tried sitting in different directories, but always the same error.  That path reference is to an old git repo I have not even used for months. What is telling it to try to look there...?

User error! I had a long forgotten alias buried in my env that was causing the issue.


Documentation layout is broken when using empty JSDoc tags.

Using empty JSDoc tags may break the layout of the rendered documentation.
See the attached images for further information.
Kind regards, Lord Saumagen.

Have you tried using the JSON output option? What does it look like? I wonder if this is a theme issue or a parsing issue.


reicast generator : removed unused file, corrected some unhandled beh…

…aviours

@digitalLumberjack Now it's done according to your suggestions :)

Thanks pal


Increase 8250 serial ports for SR/ES

To adapt to more devices, increase the number of 8250 serial ports instead of explicitly specifying console.
Refer to #148

Thanks, @ownia!
For others' reference, @ownia and I found an issue that we can't get acs linux console output on a system that is using more than 4 8250 UARTs. Therefore, we made this change so that we can still collect the logs from this kind of system.
Of course, the other reason is to align with most linux distributions to make SR ACS have capability to support more than 4 UARTs.

Thanks @ownia  and @sunnywang-arm  for the PR


Capture and process signals such as system interrupts

Support recieving and handling ctrl + c and exiting application.

Do we need to clean up any unfinished data before exiting the application, such as abort multipart upload?

Do we need to clean up any unfinished data before exiting the application, such as abort multipart upload?

No, while we receive a Ctrl+C, we should exit as soon as possible.


Page load blank on stock Galaxy S3 samsung Android browser

Hi there,
I'm not sure why but I get a blank page on the stock browser of the S3.
Can reproduce by downloading Genymotion motion and use the S3 image and open up the browser and access the site. Demo is working on Chrome browser downloaded through the app store.
Thanks
Andrew

Interesting, thanks for notifying me. Is that on master or on v3.0.0?

It's on master, figured it out it looks like Promise is not supported on that browser. Added promise polyfill and it is working now. Created a pull request.

Not merging anything into master anymore, as stated in the README, but I'd appreciate if you could check the v3.0.0 branch and, if relevant, send a PR against that! Thanks so much for digging into this!

Oh missed that readme this seems to be fine in the v3 branch. Closing.

:+1: awesome, thanks for checking!


Remove IO specific core based thread pool

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #18117 into master will increase coverage by 4.79%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #18117      +/-   ##
==========================================
+ Coverage   15.08%   19.88%   +4.79%
==========================================
  Files          48       53       +5
  Lines        1246     1368     +122
  Branches      192      213      +21
==========================================
+ Hits          188      272      +84
- Misses       1044     1082      +38
  Partials       14       14

Impacted Files
Coverage Δ

composer/packages/tracing/src/ToolBar.tsx
71.05% <0%> (ø)

composer/packages/tracing/src/TraceList.tsx
94.44% <0%> (ø)

composer/packages/tracing/src/DetailView.tsx
79.31% <0%> (ø)

composer/packages/tracing/src/TraceLogs.tsx
70.83% <0%> (ø)

composer/packages/tracing/src/index.ts
0% <0%> (ø)

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 6c98604...a1e29ca. Read the comment docs.


PWM

All the functionality has been tested on the oscilloscope and can be viewed in the func_test folder. There are extensive comments.

This was moved to the pay-optical repo.


Eclipse Java Indent Size Is Wrong

The Google Java Style states:

Each time a new block or block-like construct is opened, the indent increases by two spaces.

but the indentation size in eclipse-java-google-style.xml is set to 4.

Do you have a sample Java snippet that is being miss-indented? When I run the formatter in Eclipse I see it indenting by two characters as expected.

See https://github.com/google/styleguide/blob/9c6b371f419b1dd33c338846e3e7c1ce7304baff/eclipse-java-google-style.xml#L99 The indentation size is 4. Shouldn't it be 2?

That setting is not used.

This option is used only if the tab char is set to MIXED.

Source: https://help.eclipse.org/kepler/topic/org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENTATION_SIZE

That setting is not used.

This option is used only if the tab char is set to MIXED.

Source: https://help.eclipse.org/kepler/topic/org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENTATION_SIZE

So indentation size is then 2 by default in Eclipse, or is there a different place in eclipse-java-google-style.xml where it is set?

I believe it's the org.eclipse.jdt.core.formatter.tabulation.size setting.


Python 3.12 compat issues

Tests against Python 3.12.0rc1 which is due to be released in October are currently failing. See:
https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667
/home/runner/work/GAM/GAM/src/gam/gdata/service.py:1094: SyntaxWarning: invalid escape sequence '\?'
  m = re.compile('[\?\&]gsessionid=(\w*)').search(location)
/home/runner/work/GAM/GAM/src/gam/gdata/service.py:1342: SyntaxWarning: invalid escape sequence '\?'
  m = re.compile('[\?\&]gsessionid=(\w*)').search(location)
/home/runner/work/GAM/GAM/src/gam/gdata/service.py:1440: SyntaxWarning: invalid escape sequence '\?'
  m = re.compile('[\?\&]gsessionid=(\w*)').search(location)
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/Python_RSAKey.py:188: SyntaxWarning: invalid escape sequence '\Z'
  xmltools.getReqAttribute(element, "xmlns", "http://trevp.net/rsa\Z")
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:137: SyntaxWarning: invalid escape sequence '\Z'
  nsRegEx = "http://trevp.net/cryptoID\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:138: SyntaxWarning: invalid escape sequence '\.'
  cryptoIDRegEx = "([a-km-z3-9]{5}\.){3}[a-km-z3-9]{5}\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[39](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:40): SyntaxWarning: invalid escape sequence '\Z'
  urlRegEx = "http(s)?://.{1,100}\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[40](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:41): SyntaxWarning: invalid escape sequence '\Z'
  sha1Base64RegEx = "[A-Za-z0-9+/]{27}=\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[41](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:42): SyntaxWarning: invalid escape sequence '\Z'
  base64RegEx = "[A-Za-z0-9+/]+={0,4}\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[42](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:43): SyntaxWarning: invalid escape sequence '\Z'
  certsListRegEx = "(0)?(1)?(2)?(3)?(4)?(5)?(6)?(7)?(8)?(9)?\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[43](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:44): SyntaxWarning: invalid escape sequence '\Z'
  keyRegEx = "[A-Z]\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[44](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:45): SyntaxWarning: invalid escape sequence '\Z'
  keysListRegEx = "(A)?(B)?(C)?(D)?(E)?(F)?(G)?(H)?(I)?(J)?(K)?(L)?(M)?(N)?(O)?(P)?(Q)?(R)?(S)?(T)?(U)?(V)?(W)?(X)?(Y)?(Z)?\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[45](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:46): SyntaxWarning: invalid escape sequence '\d'
  dateTimeRegEx = "\d\d\d\d-\d\d-\d\dT\d\d:\d\d:\d\dZ\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[46](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:47): SyntaxWarning: invalid escape sequence '\Z'
  shortStringRegEx = ".{1,100}\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[47](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:48): SyntaxWarning: invalid escape sequence '\Z'
  exprRegEx = "[a-zA-Z0-9 ,()]{1,200}\Z"
/home/runner/work/GAM/GAM/src/gam/gdata/tlslite/utils/xmltools.py:1[48](https://github.com/GAM-team/GAM/actions/runs/5890842881/job/15976761667#step:36:49): SyntaxWarning: invalid escape sequence '\Z'
  notAfterDeltaRegEx = "0|([1-9][0-9]{0,8})\Z" #A number from 0 to (1 billion)-1

we need to either cleanup these regex expressions or cleanup the files they are in.
@taers232c FYI - I recall removing the "tlslite" directory" from gdata a looong time ago because it wasn't really used by GAM at all. Do you know if it's actually being used here?
It looks like the first 3 warnings against gdata/service.py just need the backslashes removed, I don't think it's necessary for those to be escaped and Python 3.12 is much more picky about this sort of thing.

closing as 3.12 is now supported / default Python for GAM binaries.


docker-compose build fails on fresh install

Hi,
I just cloned this repository to my computer and installed docker and ran the line 'docker-compose build' and it threw the following error. I am using a Mac if that's relevant.
I am keen to set up a docker image that can run MNE-Python, so Im available to help debug this issue, but I am new to docker, so any direction is appreciated.
git:(main) docker-compose build
Building scheduler
[+] Building 171.6s (12/12) FINISHED
 => [internal] load build definition from Dockerfile                                                                    0.0s
 => => transferring dockerfile: 813B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/continuumio/miniconda3:4.8.2                                                 9.7s
 => [1/7] FROM docker.io/continuumio/miniconda3:4.8.2@sha256:456e3196bf3ffb13fee7c9216db4b18b5e6f4d37090b31df3e030992  30.7s
 => => resolve docker.io/continuumio/miniconda3:4.8.2@sha256:456e3196bf3ffb13fee7c9216db4b18b5e6f4d37090b31df3e0309926  0.0s
 => => sha256:456e3196bf3ffb13fee7c9216db4b18b5e6f4d37090b31df3e0309926e98cfe2 953B / 953B                              0.0s
 => => sha256:b4adc22212f1c4628a1922a5669640e86734d0da3c26a0c35cb034e388c033ae 3.19kB / 3.19kB                          0.0s
 => => sha256:68ced04f60ab5c7a5f1d0b0b4e7572c5a4c8cce44866513d30d9df1a15277d6b 27.09MB / 27.09MB                       15.3s
 => => sha256:9c388eb6d33c40662539172f0d9a357287bd1cd171692ca5c08db2886bc527c3 80.22MB / 80.22MB                       25.1s
 => => sha256:96cf53b3a9dd496f4c91ab86eeadca2c8a31210c2e5c2a82badbb0dcf8c8f76b 50.36MB / 50.36MB                       20.6s
 => => extracting sha256:68ced04f60ab5c7a5f1d0b0b4e7572c5a4c8cce44866513d30d9df1a15277d6b                               0.9s
 => => extracting sha256:9c388eb6d33c40662539172f0d9a357287bd1cd171692ca5c08db2886bc527c3                               3.3s
 => => extracting sha256:96cf53b3a9dd496f4c91ab86eeadca2c8a31210c2e5c2a82badbb0dcf8c8f76b                               1.9s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 871B                                                                                0.0s
 => [2/7] RUN conda install --yes     -c conda-forge     python==3.8     python-blosc     cytoolz     dask==2021.4.0  108.1s
 => [3/7] RUN pip install s3fs                                                                                10.1s
 => [4/7] RUN pip install mne                                                                                9.4s
 => [5/7] RUN pip install bokeh                                                                                0.6s
 => [6/7] COPY prepare.sh /usr/bin/prepare.sh                                                                           0.0s
 => [7/7] RUN mkdir /opt/app                                                                                1.2s
 => exporting to image                                                                                1.7s
 => => exporting layers                                                                                1.7s
 => => writing image sha256:305f452ab8147df10a30a91fa8d2a687fd912af928604533c6edb2055c7d7286                            0.0s
 => => naming to docker.io/mnetools/mne-python                                                                          0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
Building worker
[+] Building 1.1s (12/12) FINISHED
 => [internal] load build definition from Dockerfile                                                                    0.0s
 => => transferring dockerfile: 37B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/continuumio/miniconda3:4.8.2                                                 1.0s
 => [1/7] FROM docker.io/continuumio/miniconda3:4.8.2@sha256:456e3196bf3ffb13fee7c9216db4b18b5e6f4d37090b31df3e0309926  0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 32B                                                                                0.0s
 => CACHED [2/7] RUN conda install --yes     -c conda-forge     python==3.8     python-blosc     cytoolz     dask==202  0.0s
 => CACHED [3/7] RUN pip install s3fs                                                                                0.0s
 => CACHED [4/7] RUN pip install mne                                                                                0.0s
 => CACHED [5/7] RUN pip install bokeh                                                                                0.0s
 => CACHED [6/7] COPY prepare.sh /usr/bin/prepare.sh                                                                    0.0s
 => CACHED [7/7] RUN mkdir /opt/app                                                                                0.0s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:305f452ab8147df10a30a91fa8d2a687fd912af928604533c6edb2055c7d7286                            0.0s
 => => naming to docker.io/mnetools/mne-python                                                                          0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
Building base-notebook
[+] Building 0.0s (1/1) FINISHED
 => ERROR [internal] load git source github.com/jupyter/docker-stacks.git#master:base-notebook                          0.0s
------
 > [internal] load git source github.com/jupyter/docker-stacks.git#master:base-notebook:
------
failed to solve with frontend dockerfile.v0: failed to read dockerfile: failed to load cache key: subdir not supported yet
ERROR: Service 'base-notebook' failed to build : Build failed

The notebook causing the build to fail can now be viewed in the CI build at https://github.com/mne-tools/mne-docker/runs/2836721778

Closed with #5


tests(apps): test for apps:info, apps:destroy, and apps:transfer

Current coverage is 26.98% (diff: 100%)

Merging #233 into master will increase coverage by 0.85%

@@             master       #233   diff @@
==========================================
  Files            56         56
  Lines          3861       3861
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1009       1042    +33
+ Misses         2719       2671    -48
- Partials        133        148    +15

Powered by Codecov. Last update a330059...4f78440

Had some crazy conflicts which weren't worth trying to cleanly merge. Closing this PR in favor of a cleaner one.


Tutorial on how to create a package from scratch

Is there any tutorial on how to create a package from scratch, for example with a product registration related to suppliers
with the following fields:
Product Table
id int (11)
suppliers_id int (11)
product varchar (255)
price float (11.2)
total float (11.2)
Supplier Table
id int (11)
supplier varchar (255)

Hi,
If you are talking about creating a Laravel package there are a lot of useful step by step tutorials on the web.
Once you know how to create a Laravel package, to create a structure in Enso (routes, views, controllers, tables, forms etc) take the laravel-enso/permissionmanager as an example, look at the permission groups part (it's simpler) and replicate everything there.

Thanks for the answer. In case when I talk about a package, it's for Enso!
I will study laravel-enso / permissionmanager as indicated.


Add local analytics

Message Counts
User engagement
Common Questions
Failed answers
Anonymized (?)

@zafarali Do you still need help here?

Hey! it would be great if you could make a small initial contribution!
Some clarifications:

By "local" solutions I meant that it doesn't work to bot analytics platforms. It's more for you to download and analyze layer.
Ideally the solution should be lightweight (json read/write files or a very small self-hosted database that is compatible with heroku or openshift)


auto create png fallback images from svg

grunt svg2png

https://github.com/dbushell/grunt-svg2png/issues/29

won't fix ... inline imaging is not part of the default setup anymore


HADOOP-18238.Fix reentrancy check in SFTPFileSystem.close()

Description of PR
Fix reentrancy check in SFTPFileSystem.close()

JIRA: HADOOP-18238

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 48s

trunk passed

+1 :green_heart:
compile
26m 30s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
20m 22s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 13s

trunk passed

+1 :green_heart:
mvnsite
1m 40s

trunk passed

+1 :green_heart:
javadoc
1m 15s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 50s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 40s

trunk passed

+1 :green_heart:
shadedclient
21m 51s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 58s

the patch passed

+1 :green_heart:
compile
22m  3s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
22m  3s

the patch passed

+1 :green_heart:
compile
19m 50s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
19m 51s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  7s

the patch passed

+1 :green_heart:
mvnsite
1m 36s

the patch passed

+1 :green_heart:
javadoc
1m  6s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 51s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 37s

the patch passed

+1 :green_heart:
shadedclient
21m 45s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m 47s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m  3s

The patch does not generate ASF License warnings.

209m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4330/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4330

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux a8bd76dcdbcf 4.15.0-169-generic #177-Ubuntu SMP Thu Feb 3 10:50:38 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a65cfadc7da379b731592a8d8b4bbf0796df0590

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4330/1/testReport/

Max. process+thread count
2424 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4330/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Split metrics into data metrics and server metrics

[RaftMetrics][] encapsulates a range of information about the internal states of
a Raft node, including the server state (e.g., Leader, Follower), and
data-related states such as the last log index and the last applied log index.
Applications interested in monitoring these details can subscribe to
[RaftMetrics][] to receive updates when these metrics change, with
Raft::metrics().
However, some metrics, like last_log_index, are frequently updated, while
others, such as current_term and state, change less often.
For applications solely concerned with server state transitions (like switching
from Leader to Follower), being notified of changes to last_log_index can
result in unnecessary wake-ups.
To optimize this, it would be beneficial to add two subsets of the metrics:

Metrics that are not data-related, such as current_term, vote, and state.
Metrics that are data-related, including last_log_index and last_applied.

By segregating these metrics, applications can subscribe to the relevant subset
and reduce the overhead of processing frequent updates that are not pertinent to
their needs.
TODO:

[ ] add Raft::data_metrics() to return a watch::Receiver<RaftDataMetrics>
that contains only metrics about log, state machine and snapshot.

[ ] add Raft::server_metrics() to return a
watch::Receiver<RaftServerMetrics> that contains only server related
metrics, such as vote, leader, id, running_state, membership

BTW, I was about to suggest the same :-).

Hi, may I claim this assignment? I'd like to have some try

Hi, may I claim this assignment? I'd like to have some try

Sure. Thank you!
Please keep current API and data types and just add new APIs. :)

Please keep current API and data types and just add new APIs. :)
get it~