x/build/cmd/relui: macOS installer should add GOBIN to PATH

We currently provide installers for Go for Windows (an .msi file) and macOS (a .pkg file).
Both installers add $GOROOT/bin to PATH. This lets users run commands like go build without having to edit PATH themselves.
However, users still need to edit PATH in order to run binaries installed with go install or go get. This introduces unnecessary confusion for new developers. To avoid this, both installers should add $GOBIN to PATH as well.
(Note that neither GOBIN nor GOPATH are likely to be set when an installer runs. If they are set, we should respect them; the goal is just to ensure that the directory where go install writes binaries is added to PATH).

I think this is a good idea as it will lead to a noticeable improvement to the user experience for new users, and we should do this, unless we are able to discover a reason why doing so could be harmful or dangerous.
Given the installers already own the decision of where to place the Go installation and make it available (via an added entry to PATH or a platform-equivalent), and by not setting a GOPATH, they are implicitly relying on the default GOPATH value that go uses (which is $HOME/go or platform-equivalent), I think also adding GOBIN to PATH is an appropriate and in-scope task for an installer.
I'll think more about it, but I can't think of concerns with doing so.
I'll tentatively mark this for consideration for 1.15, since it seems like a minor and safe change to me (and the change doesn't need to be done in the main Go tree). It's an opportunity to use an upcoming beta release to try it out and get user feedback. That said, we are in the release freeze for 1.15, so if people think this decision needs more time or input, we can move this for 1.16 cycle.
/cc @golang/osp-team

This issue is currently labeled as early-in-cycle for Go 1.16.
That time is now, so this is a friendly ping so the issue is looked at again.

@jayconrod Friendly ping on this. Does it sound good to you to move this issue to NeedsFix for 1.16 milestone?
I'll also /cc @stevetraut who's been working on improving the installation experience, I think this change can be beneficial.

Sure, it sounds like we're in agreement this is a good idea.
Does anyone on  the release team have bandwidth to fix this for 1.16? I'm not familiar with the installers, and I'm not sure if I'll have bandwidth to look at this before the freeze.

Yes, I can take this.

It seems this has already been done for Windows 3 years ago. See issue #23025 and CL 104115.
Going to look into the current state of the macOS installer next.

I've made progress on the side of the macOS installer, but ran into some usability questions that we'll need to agree on answers to. I'll provide more detail and follow up on this during the 1.17 cycle.

While talking about this briefly with @toothrot, he suggested a possible idea for the cmd/go command to consider printing a prompt after go install example.com/cmd@latest if it detects that the installed cmd isn't in already PATH. If false positives can be eliminated (i.e., some users may intentionally choose not add GOPATH/bin to PATH), this could be similar to some other helpful messages cmd/go prints in some situations.

This that this 2020 issue is stalled on determining the right solution, I think it would be highly valuable and appreciated if go install example.com/cmd@latest checked whether the location where the cmd is installed is in the path, and displayed a message to the user about this.
Suggest that any such user facing message include a link to https://go.dev/doc/install where a more detailed explanation can be always be kept up to date.
—
If such a fix is going to still take some time, can we update the docs:

Update https://go.dev/doc/install (for macOS) to explicitly mention adding $HOME/go/bin to $PATH manually (for example by documenting adding export PATH="$PATH:$(go env GOPATH)/bin" to ~/.bash_profile). Advanced users will know what they want to do (instead). Everyone else will be helped.
Update https://go.dev/doc/manage-install (for macOS) to remove $HOME/go/bin from $PATH

This is a good idea to avoid having to set up the environment variables manually.
Ref: https://discussions.apple.com/thread/250911992?sortBy=best


Added defaultPrevented flag to the Event interface

Support for feature defaultPrevented attribute on the Event interface was added as requested in issue https://github.com/tmpvar/jsdom/issues/989
This feature is supported by DOM living standard and can be referenced here. https://dom.spec.whatwg.org/#interface-event
Also added an event default for click on input elements of type checkbox.
Tests were added. Please code review and merge. Thank you.

Reviewed! Please rebase and make updates. Excited to have this.

Rebase has been performed and the updates have been made. Please review and merge. Thank you.

Thanks!! Merged with slight tweaks as 7901be1bc19e6a1b4e9e5b20f0fdd021b86a8c54, and also a quick follow-up at https://github.com/tmpvar/jsdom/commit/23ffcacc710e1ba06ab1e30bb505e6338becb568. Released as 4.3.0.
Really appreciate your contributions!!


Challenge_02

This is the second challenge

Please open "Second_Try" file, that is better than first file


step 7 profile pic is not shown

In step 7 you are asked to copy-paste the code for receiving the Profile-pic-URL. After that, you are supposed to see a profile pic next to the username when you sign in. I can only see the user name, but no picture is being shown.
am I doing something wrong or is something not working?
I did everything that's stated in the tutorial:

Go back to the file public/scripts/main.js.
Find the functions getProfilePicUrl and getUserName.
Replace both functions with the following code.

Code:
// Returns the signed-in user's profile pic URL.
function getProfilePicUrl() {

  console.log(firebase.auth().currentUser.photoURL || '/images/profile_placeholder.png');
  return firebase.auth().currentUser.photoURL || '/images/profile_placeholder.png';
![bug](https://user-images.githubusercontent.com/62097031/97025780-d2085980-1558-11eb-8c7e-60ca7c3d84f2.jpg)
![bug](https://user-images.githubusercontent.com/62097031/97025795-d6cd0d80-1558-11eb-9ae7-494bacece60e.jpg)
![bug1](https://user-images.githubusercontent.com/62097031/97025883-f3694580-1558-11eb-8d03-2edbaded4adc.jpg)

}

// Returns the signed-in user's display name.
function getUserName() {
  return firebase.auth().currentUser.displayName;
}

okay everybody, after trying around for a while, I didn't change anything, but  just continued with the next steps.
After some time it just worked! - maybe it just needed a while :)
thanks anyways


changed testnet amm converter addresses

Changed addresses of SOV/RBTC, XUSD/RBTC, FISH/RBTC, BNBS/RBTC, ETHS/RBTC & MOC/RBTC AMM pool converter addresses.
QA:

deposit to AMM pools (Yield Farm)
withdraw from AMM pools
make swaps using these pools
open trade positions
add margin to position
close position

Not able make any deposits

Even after few minutes of loading the parameters are still buffering.
Deposit function is not working. Not able to do any deposi

ts


Remove date macro on version for reproducible builds

cf https://reproducible-builds.org/

Thanks for the info!


[BUG] Release 4.1.1 is not published to NuGet so issues #199 & #205 are not fixed

Describe the bug
Release 4.1.1 from Feb 2022 hasn't been published to NuGet, so issues #199  and #205 , although “fixed” are not fixed.
Expected behavior
Release 4.1.1 should be on NuGet.
Thankyou :-)

Any update for when we can expect 4.1.1 release? I love the enhancement in #205 and would like to use it.

Reviving this issue, hopefully this change will still be included in the library at some point. This would hugely improve testability.

ta!

2 year? really?


Some copy tweaks to the statistic type descriptions

Copy tweaks from @Nadiahuq and @spencerball.

Closing this as I, err, already did it here: https://github.com/racedisparityaudit/ethnicity-facts-and-figures-publisher/blob/master/scripts/data_migrations/2018-11-05_tweak_type_of_statistic.sql (but forgot to run the migration)


StateStore - Storing Value as byte[] - (cosmos state component)

Prior there was an issue  with inconsistent use of json/byte[] for the cosmos component.
State is now stored as byte[] on all operations, using cosmos (see test below).
But using bytes in stores catered for json is not "optimal".
In the Cosmos case this affects;
Being able to query my collection (json expected)
Using change feed (json expected)
Is this a concern for the SDK or on component level ?
To my understanding the component checks the value, if its byte[].
      [Fact]
       public async Task SavingStateAsync()
       {
           await client.SaveStateAsync("localcosmos", "storage-test-1", new TestEventRecord("hello there"));
           await client.ExecuteStateTransactionAsync("localcosmos", new[] {
               new StateTransactionRequest("storage-test-2", JsonSerializer.SerializeToUtf8Bytes(new TestEvent("hello there")), StateOperationType.Upsert) });
       }

Thanks @perokvist for opening this.
There's unfortunately nothing the SDK can do about this right now because this behavior is part of the cosmos component. There's nothing other than the choice of protocol that an SDK can do to influence how this works. I'm going to move this to components-contrib.
I've also opened dapr/dapr#2892 to discuss whether this should be enabled in a centralized way.


Add timing panel

Added a timing panel to go along with the rest to provide numerical values if needed. Helps a lot with calibration.

It's not perfect though as slide chain notes will throw the average way off on slide-heavy charts due to them being registered at around -16~20ms.
Side note: I'm not well versed in C++ beyond classes during a semester a few years ago, so the code might not be as clean as it could be

Rejected because it dosent follow the code style (e.g. using _t in the added struct) and lack of proper formatting from lack of running make fmt.
The early/late judgements(for cool at least) are >= -0.01 and >= 0.01, though this is fundamentally wrong for my own usage of it which is using the actual judgement line to judge whether its early or late.
The average offset is a good addition however it dosent need its own window and would be better as an addition to the main score window.

Also generally don't add comments to other peoples comments, especially comments describing blatantly obvious things


problem with useSSL and usePASV

fixed reference to useSSL and usePASV fields that are now just ssl and pasv on Client/Config.php

+1

Thanks!


Automate forecast submissions on Open Stack server

This needs to be working by Thursday May 20.

[ ] Copy model scripts over
[ ] Set up chron job(s)
[ ] Test submission works

Double check the submission time is afternoon-ish for North America.

WIP notes:
Log into server w/ ssh -i ~/.ssh/id_rsa<EMAIL_ADDRESS>Copy files and data for model runs over to server: git clone https://github.com/genophenoenvo/neon-datasets.git
Need to install all R and Python packages
R: readr, dplyr, udunits2, plantecophys, tidyr, aws.s3
Python: pandas, datetime, pickle, glob, os, sklearn


[UWP][Accessibility] Keyboard behavior in expanded choice sets

Platform

UWP

Details
From Inclusive and Accessible Design Spec Review Report:
Using Input.ChoiceSet.Expanded.Label.json:

Keyboard accessibility, Tab and shift Tab key should be used to move between group of radio button not with in group of radio button.
When using tab key or shift tab key, focus should go to the selected radio button irrespective of its position in group.

See guidelines and example from  WCAG’s Wai-aria from https://www.w3.org/TR/wai-aria-practices/examples/radio/radio-1/radio-1.html
Using Input.ChoiceSet.Expanded.MultiSelect.Label.json

Keyboard accessibility: Up and down arrow keys should move focus within group of checkbox.

See example and guideline from WCAG W3C link https://www.w3.org/TR/wai-aria-practices/examples/checkbox/checkbox-1/checkbox-1.html

I don't think that WCAG rules apply in UWP. We should be following platform accessibility guidelines, which should already be implemented in XAML.


feat: enable advanced slippage

Description
Enable advanced (user selectable) slippage.
Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A
Risk
TODO
Testing
Engineering
Operations
Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #5179   👈

This comment was auto-generated by Graphite.


Update ElasticSearch version

Current version may present a security vulnerability

Our python-env image contains the Python elasticsearch module only and no Java stuff at all (no Log4j, etc.), so thankfully it was not affected by the Log4j vulnerability.  However, it is indeed a good idea to match the version of Python module to that of the Elasticsearch v7.16.1 (Java) Docker image being used at OpenDRR/opendrr-api.  That was completed with the merge of

#4

and the release of v1.1.0 of the python-env image.


Commits are not shown after migration

hi everyone,
A migration was made from jira Cloud to cloud and the github plugin for jira has been reinstalled, but the old commits do not appear, can that information be recovered or make it appear?
Thanks in advance

After you installed the plugin, did you add the Github organization back into the app?  After that happens, a backfill will run to get all historical data from Github :)

Hi Michel
The plugin was reinstalled in the final instance, and the new commits that are made are seen in the issues but other issues that had commits in the source instance do not appear, and it is required to retrieve that information.

Good morning Michel, I would appreciate if you can help us with this problem or if in fact that history of previous commits cannot be recovered, thank you very much for the answer

Hi @Juni0rs. Could we please get a screenshot of the config page so we can see the status of backfilling for the connected org/s?


Create a placeholder image for mentors who don't supply photos

Do we need it?
For the mentors bar.

This got done over the last couple of weekends. If there's no image defined in frontmatter then the template uses the default image.
The image for "anonymous sponsor" is:
https://s3-ap-southeast-2.amazonaws.com/2016govhackmentors/secret-squirrel.jpg

That works well for sponsors, but I had in mind a more "silhouette of person" placeholder for mentors. Reopening and assigning to myself as a lower priority.


fix: add storage prefix in connection

Description:
Commit Message
fix: add storage prefix in connection

see the guidelines for commit messages.
Changelog Entry
version: <log entry>

Checklist:

[ ] I have performed a self-review of my own code
[ ] I have documented my code in accordance with the documentation guidelines
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have run the unit tests
[ ] I only have one commit (if not, squash them into one commit).
[ ] I have a descriptive commit message that adheres to the commit message guidelines

Please review the CONTRIBUTING.md file for detailed contributing guidelines.

Codecov Report

Merging #436 (fca8a3d) into main (dbbc307) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #436      +/-   ##
============================================
+ Coverage     66.93%   66.98%   +0.05%
  Complexity      551      551
============================================
  Files           191      191
  Lines         17298    17328      +30
  Branches        352      352
============================================
+ Hits          11578    11608      +30
  Misses         5541     5541
  Partials        179      179

Flag
Coverage Δ

rust
64.84% <100.00%> (+0.07%)
:arrow_up:

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

Impacted Files
Coverage Δ

contracts/cosmwasm-vm/cw-common/src/lib.rs
100.00% <100.00%> (ø)

contracts/cosmwasm-vm/cw-ibc-core/src/contract.rs
50.79% <100.00%> (ø)

...-vm/cw-ibc-core/src/ics03_connection/connection.rs
82.66% <100.00%> (+0.23%)
:arrow_up:

...asm-vm/cw-ibc-core/src/ics03_connection/handler.rs
89.35% <100.00%> (+0.01%)
:arrow_up:

.../cw-ibc-core/src/ics04_channel/handler/open_try.rs
89.47% <100.00%> (ø)


Clean Installation failed Hassbian / Clean Raspbian

At first, my english is not realy good, but i hope you can understand me,
Home Assistant release with the issue:

0.101.1
Last working Home Assistant release (if known):
New clean Installation on a Raspberry Pi 3b+
Operating environment (Hass.io/Docker/Windows/etc.):

Hardware: Raspberry Pi 3b+
I try to use Hassbian and a clean (fresh downloaded and installed) Raspbian Buster
Integration:

Notching
Description of problem:
I try to install Home Assistant on a Raspberry Pi 3b+.
I followed the manual on https://www.home-assistant.io/docs/installation/hassbian/installation/ step by step. After the first start of hass, the installation generates some Error messages. See below.
After some failed trys, i try to install homeassistant on a clean raspbian butcher on this manual (Commands Copy + Paste): https://www.home-assistant.io/docs/installation/raspberry-pi/
It crashs with the same Problem. (See below)
It looks like the script can't or don't install the hass_frontend.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
default / first installation

Traceback Hassbian (if applicable): (output off /var/log/syslog)
Nov  1 14:34:27 hassbian systemd[1]: install_homeassistant.service: Succeeded.
Nov  1 14:34:29 hassbian hass[1626]: 2019-11-01 14:34:29 INFO (SyncWorker_1) [homeassistant.util.package] Attempting install of pyotp==2.3.0
Nov  1 14:34:33 hassbian hass[1626]: 2019-11-01 14:34:33 INFO (SyncWorker_0) [homeassistant.util.package] Attempting install of PyQRCode==1.2.1
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_6) [homeassistant.loader] Loaded group from homeassistant.components.group
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_5) [homeassistant.loader] Loaded script from homeassistant.components.script
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_1) [homeassistant.loader] Loaded automation from homeassistant.components.automation
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_4) [homeassistant.loader] Loaded default_config from homeassistant.components.default_config
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_0) [homeassistant.loader] Loaded tts from homeassistant.components.tts
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_1) [homeassistant.loader] Loaded homeassistant from homeassistant.components.homeassistant
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_10) [homeassistant.loader] Loaded device_automation from homeassistant.components.device_automation
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_4) [homeassistant.loader] Loaded persistent_notification from homeassistant.components.persistent_notification
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_1) [homeassistant.loader] Loaded http from homeassistant.components.http
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (MainThread) [homeassistant.setup] Setting up homeassistant
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant took 0.0 seconds.
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_3) [homeassistant.loader] Loaded webhook from homeassistant.components.webhook
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (MainThread) [homeassistant.setup] Setting up persistent_notification
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (MainThread) [homeassistant.setup] Setup of domain persistent_notification took 0.0 seconds.
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_11) [homeassistant.loader] Loaded cloud from homeassistant.components.cloud
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_7) [homeassistant.loader] Loaded config from homeassistant.components.config
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_12) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_2) [homeassistant.loader] Loaded api from homeassistant.components.api
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_14) [homeassistant.loader] Loaded auth from homeassistant.components.auth
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_0) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_4) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_1) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_5) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_3) [homeassistant.loader] Loaded history from homeassistant.components.history
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_11) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_8) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_13) [homeassistant.loader] Loaded map from homeassistant.components.map
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_9) [homeassistant.loader] Loaded mobile_app from homeassistant.components.mobile_app
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_15) [homeassistant.loader] Loaded person from homeassistant.components.person
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_0) [homeassistant.loader] Loaded ssdp from homeassistant.components.ssdp
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_10) [homeassistant.loader] Loaded sun from homeassistant.components.sun
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_16) [homeassistant.loader] Loaded system_health from homeassistant.components.system_health
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_5) [homeassistant.loader] Loaded updater from homeassistant.components.updater
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_3) [homeassistant.loader] Loaded zeroconf from homeassistant.components.zeroconf
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (MainThread) [homeassistant.bootstrap] Setting up {'system_log'}
Nov  1 14:34:37 hassbian hass[1626]: 2019-11-01 14:34:37 INFO (SyncWorker_19) [homeassistant.util.package] Attempting install of aiohttp_cors==0.7.0
Nov  1 14:34:46 hassbian hass[1626]: 2019-11-01 14:34:46 INFO (MainThread) [homeassistant.setup] Setting up http
Nov  1 14:34:46 hassbian hass[1626]: 2019-11-01 14:34:46 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
Nov  1 14:34:46 hassbian hass[1626]: 2019-11-01 14:34:46 INFO (MainThread) [homeassistant.setup] Setting up system_log
Nov  1 14:34:46 hassbian hass[1626]: 2019-11-01 14:34:46 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
Nov  1 14:34:46 hassbian hass[1626]: 2019-11-01 14:34:46 INFO (SyncWorker_13) [homeassistant.util.package] Attempting install of sqlalchemy==1.3.10
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 INFO (MainThread) [homeassistant.setup] Setting up recorder
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.5 seconds.
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 INFO (MainThread) [homeassistant.setup] Setting up group
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 INFO (MainThread) [homeassistant.setup] Setup of domain group took 0.0 seconds.
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 INFO (MainThread) [homeassistant.setup] Setting up lovelace
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 ERROR (MainThread) [homeassistant.setup] Error during setup of component lovelace
Nov  1 14:34:55 hassbian hass[1626]: Traceback (most recent call last):
Nov  1 14:34:55 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/setup.py", line 172, in _async_setup_component
Nov  1 14:34:55 hassbian hass[1626]:     hass, processed_config
Nov  1 14:34:55 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/lovelace/__init__.py", line 66, in async_setup
Nov  1 14:34:55 hassbian hass[1626]:     hass.components.frontend.async_register_built_in_panel(
Nov  1 14:34:55 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 421, in __getattr__
Nov  1 14:34:55 hassbian hass[1626]:     component: Optional[ModuleType] = integration.get_component()
Nov  1 14:34:55 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 223, in get_component
Nov  1 14:34:55 hassbian hass[1626]:     cache[self.domain] = importlib.import_module(self.pkg_path)
Nov  1 14:34:55 hassbian hass[1626]:   File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
Nov  1 14:34:55 hassbian hass[1626]:     return _bootstrap._gcd_import(name[level:], package, level)
Nov  1 14:34:55 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
Nov  1 14:34:55 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 983, in _find_and_load
Nov  1 14:34:55 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
Nov  1 14:34:55 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
Nov  1 14:34:55 hassbian hass[1626]:   File "<frozen importlib._bootstrap_external>", line 728, in exec_module
Nov  1 14:34:55 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
Nov  1 14:34:55 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/frontend/__init__.py", line 10, in <module>
Nov  1 14:34:55 hassbian hass[1626]:     import hass_frontend
Nov  1 14:34:55 hassbian hass[1626]: ModuleNotFoundError: No module named 'hass_frontend'
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 INFO (SyncWorker_15) [homeassistant.util.package] Attempting install of distro==1.4.0
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 INFO (MainThread) [homeassistant.setup] Setting up person
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 INFO (MainThread) [homeassistant.setup] Setting up sun
Nov  1 14:34:55 hassbian hass[1626]: 2019-11-01 14:34:55 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.2 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setting up webhook
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setting up auth
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setting up script
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.0 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setting up system_health
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.0 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setting up config
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 ERROR (MainThread) [homeassistant.setup] Error during setup of component history
Nov  1 14:34:56 hassbian hass[1626]: Traceback (most recent call last):
Nov  1 14:34:56 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/setup.py", line 172, in _async_setup_component
Nov  1 14:34:56 hassbian hass[1626]:     hass, processed_config
Nov  1 14:34:56 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/history/__init__.py", line 283, in async_setup
Nov  1 14:34:56 hassbian hass[1626]:     hass.components.frontend.async_register_built_in_panel(
Nov  1 14:34:56 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 421, in __getattr__
Nov  1 14:34:56 hassbian hass[1626]:     component: Optional[ModuleType] = integration.get_component()
Nov  1 14:34:56 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 223, in get_component
Nov  1 14:34:56 hassbian hass[1626]:     cache[self.domain] = importlib.import_module(self.pkg_path)
Nov  1 14:34:56 hassbian hass[1626]:   File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
Nov  1 14:34:56 hassbian hass[1626]:     return _bootstrap._gcd_import(name[level:], package, level)
Nov  1 14:34:56 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
Nov  1 14:34:56 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 983, in _find_and_load
Nov  1 14:34:56 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
Nov  1 14:34:56 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
Nov  1 14:34:56 hassbian hass[1626]:   File "<frozen importlib._bootstrap_external>", line 728, in exec_module
Nov  1 14:34:56 hassbian hass[1626]:   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
Nov  1 14:34:56 hassbian hass[1626]:   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/frontend/__init__.py", line 10, in <module>
Nov  1 14:34:56 hassbian hass[1626]:     import hass_frontend
Nov  1 14:34:56 hassbian hass[1626]: ModuleNotFoundError: No module named 'hass_frontend'
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setting up api
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setup of domain person took 0.4 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setting up device_automation
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.0 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setting up onboarding
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.0 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setting up automation
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 0.0 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.0 seconds.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of frontend. Setup failed for dependencies: lovelace
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 ERROR (MainThread) [homeassistant.setup] Setup failed for frontend: Could not set up all dependencies.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of logbook. Setup failed for dependencies: frontend
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 ERROR (MainThread) [homeassistant.setup] Setup failed for logbook: Could not set up all dependencies.
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of map. Setup failed for dependencies: frontend
Nov  1 14:34:56 hassbian hass[1626]: 2019-11-01 14:34:56 ERROR (MainThread) [homeassistant.setup] Setup failed for map: Could not set up all dependencies.
Nov  1 14:35:00 hassbian hass[1626]: 2019-11-01 14:35:00 INFO (MainThread) [homeassistant.setup] Setting up updater
Nov  1 14:35:00 hassbian hass[1626]: 2019-11-01 14:35:00 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.0 seconds.
Nov  1 14:35:00 hassbian hass[1626]: 2019-11-01 14:35:00 INFO (SyncWorker_18) [homeassistant.util.package] Attempting install of netdisco==2.6.0
Nov  1 14:35:00 hassbian hass[1626]: 2019-11-01 14:35:00 INFO (SyncWorker_11) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
Nov  1 14:35:00 hassbian hass[1626]: 2019-11-01 14:35:00 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
Nov  1 14:35:00 hassbian hass[1626]: 2019-11-01 14:35:00 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.0 seconds.
Nov  1 14:35:00 hassbian hass[1626]: 2019-11-01 14:35:00 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.updater
Nov  1 14:35:00 hassbian hass[1626]: 2019-11-01 14:35:00 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new binary_sensor.updater entity: binary_sensor.updater
Nov  1 14:35:06 hassbian hass[1626]: 2019-11-01 14:35:06 INFO (MainThread) [homeassistant.setup] Setting up ssdp
Nov  1 14:35:06 hassbian hass[1626]: 2019-11-01 14:35:06 INFO (MainThread) [homeassistant.setup] Setup of domain ssdp took 0.0 seconds.
Nov  1 14:35:06 hassbian hass[1626]: 2019-11-01 14:35:06 INFO (SyncWorker_8) [homeassistant.util.package] Attempting install of mutagen==1.42.0
Nov  1 14:35:11 hassbian hass[1626]: 2019-11-01 14:35:11 INFO (SyncWorker_6) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate
Nov  1 14:35:11 hassbian hass[1626]: 2019-11-01 14:35:11 INFO (SyncWorker_0) [homeassistant.util.package] Attempting install of hass-nabucasa==0.22
Nov  1 14:35:53 hassbian systemd[1]: session-c1.scope: Succeeded.
Nov  1 14:35:53 hassbian systemd[1]: session-c2.scope: Succeeded.
Nov  1 14:35:57 hassbian systemd[1]: Started Session c3 of user pi.
Nov  1 14:35:58 hassbian systemd[1]: Started Session c4 of user pi.
Nov  1 14:36:14 hassbian hass[1626]: 2019-11-01 14:36:14 INFO (MainThread) [homeassistant.setup] Setting up cloud
Nov  1 14:36:14 hassbian hass[1626]: 2019-11-01 14:36:14 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
Nov  1 14:36:14 hassbian hass[1626]: 2019-11-01 14:36:14 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 0.1 seconds.
Nov  1 14:36:14 hassbian hass[1626]: 2019-11-01 14:36:14 INFO (SyncWorker_11) [homeassistant.loader] Loaded esphome from homeassistant.components.esphome
Nov  1 14:36:14 hassbian hass[1626]: 2019-11-01 14:36:14 INFO (SyncWorker_3) [homeassistant.util.package] Attempting install of gTTS-token==1.1.3
Nov  1 14:36:14 hassbian hass[1626]: 2019-11-01 14:36:14 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.2 seconds.
Nov  1 14:36:20 hassbian hass[1626]: 2019-11-01 14:36:20 INFO (MainThread) [homeassistant.setup] Setting up tts
Nov  1 14:36:20 hassbian hass[1626]: 2019-11-01 14:36:20 INFO (SyncWorker_14) [homeassistant.components.tts] Create cache dir /home/homeassistant/.homeassistant/tts.
Nov  1 14:36:20 hassbian hass[1626]: 2019-11-01 14:36:20 INFO (SyncWorker_13) [homeassistant.util.package] Attempting install of aioesphomeapi==2.4.2
Nov  1 14:36:29 hassbian hass[1626]: 2019-11-01 14:36:29 INFO (SyncWorker_1) [homeassistant.util.package] Attempting install of PyNaCl==1.3.0
Nov  1 14:36:36 hassbian hass[1626]: 2019-11-01 14:36:36 ERROR (MainThread) [homeassistant.setup] Setup failed for mobile_app: Unable to import component
Nov  1 14:36:36 hassbian hass[1626]: 2019-11-01 14:36:36 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 16.1 seconds.
Nov  1 14:36:36 hassbian hass[1626]: 2019-11-01 14:36:36 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of default_config. Setup failed for dependencies: config, frontend, history, l$
Nov  1 14:36:36 hassbian hass[1626]: 2019-11-01 14:36:36 ERROR (MainThread) [homeassistant.setup] Setup failed for default_config: Could not set up all dependencies.
Nov  1 14:36:36 hassbian hass[1626]: 2019-11-01 14:36:36 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 127.23s
Nov  1 14:36:36 hassbian hass[1626]: 2019-11-01 14:36:36 INFO (MainThread) [homeassistant.core] Starting Home Assistant
Nov  1 14:36:36 hassbian hass[1626]: 2019-11-01 14:36:36 INFO (MainThread) [homeassistant.core] Timer:starting
Nov  1 14:36:36 hassbian hass[1626]: 2019-11-01 14:36:36 INFO (SyncWorker_0) [homeassistant.components.zeroconf] Starting Zeroconf broadcast

Traceback Raspbian(if applicable):
(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $ hass
Unable to find configuration. Creating default one in /home/homeassistant/.homeassistant
Config directory: /home/homeassistant/.homeassistant
2019-11-01 14:05:56 INFO (SyncWorker_0) [homeassistant.util.package] Attempting install of pyotp==2.3.0
2019-11-01 14:06:04 INFO (SyncWorker_1) [homeassistant.util.package] Attempting install of PyQRCode==1.2.1
2019-11-01 14:06:12 INFO (SyncWorker_3) [homeassistant.loader] Loaded automation from homeassistant.components.automation
2019-11-01 14:06:12 INFO (SyncWorker_3) [homeassistant.loader] Loaded tts from homeassistant.components.tts
2019-11-01 14:06:12 INFO (SyncWorker_4) [homeassistant.loader] Loaded script from homeassistant.components.script
2019-11-01 14:06:12 INFO (SyncWorker_4) [homeassistant.loader] Loaded group from homeassistant.components.group
2019-11-01 14:06:12 INFO (SyncWorker_12) [homeassistant.loader] Loaded default_config from homeassistant.components.default_config
2019-11-01 14:06:12 INFO (SyncWorker_1) [homeassistant.loader] Loaded homeassistant from homeassistant.components.homeassistant
2019-11-01 14:06:12 INFO (SyncWorker_14) [homeassistant.loader] Loaded persistent_notification from homeassistant.components.persistent_notification
2019-11-01 14:06:12 INFO (SyncWorker_7) [homeassistant.loader] Loaded device_automation from homeassistant.components.device_automation
2019-11-01 14:06:12 INFO (SyncWorker_8) [homeassistant.loader] Loaded http from homeassistant.components.http
2019-11-01 14:06:12 INFO (MainThread) [homeassistant.setup] Setting up homeassistant
2019-11-01 14:06:12 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant took 0.0 seconds.
2019-11-01 14:06:12 INFO (MainThread) [homeassistant.setup] Setting up persistent_notification
2019-11-01 14:06:12 INFO (MainThread) [homeassistant.setup] Setup of domain persistent_notification took 0.0 seconds.
2019-11-01 14:06:12 INFO (SyncWorker_3) [homeassistant.loader] Loaded webhook from homeassistant.components.webhook
2019-11-01 14:06:12 INFO (SyncWorker_10) [homeassistant.loader] Loaded cloud from homeassistant.components.cloud
2019-11-01 14:06:12 INFO (SyncWorker_4) [homeassistant.loader] Loaded config from homeassistant.components.config
2019-11-01 14:06:12 INFO (SyncWorker_2) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
2019-11-01 14:06:12 INFO (SyncWorker_15) [homeassistant.loader] Loaded api from homeassistant.components.api
2019-11-01 14:06:12 INFO (SyncWorker_0) [homeassistant.loader] Loaded auth from homeassistant.components.auth
2019-11-01 14:06:12 INFO (SyncWorker_5) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
2019-11-01 14:06:12 INFO (SyncWorker_14) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
2019-11-01 14:06:12 INFO (SyncWorker_8) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
2019-11-01 14:06:12 INFO (SyncWorker_9) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
2019-11-01 14:06:12 INFO (SyncWorker_6) [homeassistant.loader] Loaded history from homeassistant.components.history
2019-11-01 14:06:12 INFO (SyncWorker_10) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
2019-11-01 14:06:12 INFO (SyncWorker_11) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook
2019-11-01 14:06:12 INFO (SyncWorker_13) [homeassistant.loader] Loaded map from homeassistant.components.map
2019-11-01 14:06:12 INFO (SyncWorker_12) [homeassistant.loader] Loaded mobile_app from homeassistant.components.mobile_app
2019-11-01 14:06:12 INFO (SyncWorker_1) [homeassistant.loader] Loaded person from homeassistant.components.person
2019-11-01 14:06:12 INFO (SyncWorker_16) [homeassistant.loader] Loaded ssdp from homeassistant.components.ssdp
2019-11-01 14:06:12 INFO (SyncWorker_14) [homeassistant.loader] Loaded sun from homeassistant.components.sun
2019-11-01 14:06:12 INFO (SyncWorker_3) [homeassistant.loader] Loaded system_health from homeassistant.components.system_health
2019-11-01 14:06:12 INFO (SyncWorker_17) [homeassistant.loader] Loaded updater from homeassistant.components.updater
2019-11-01 14:06:12 INFO (SyncWorker_6) [homeassistant.loader] Loaded zeroconf from homeassistant.components.zeroconf
2019-11-01 14:06:12 INFO (MainThread) [homeassistant.bootstrap] Setting up {'system_log'}
2019-11-01 14:06:12 INFO (SyncWorker_4) [homeassistant.util.package] Attempting install of aiohttp_cors==0.7.0
2019-11-01 14:06:24 INFO (MainThread) [homeassistant.setup] Setting up http
2019-11-01 14:06:24 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
2019-11-01 14:06:24 INFO (MainThread) [homeassistant.setup] Setting up system_log
2019-11-01 14:06:24 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2019-11-01 14:06:24 INFO (SyncWorker_13) [homeassistant.util.package] Attempting install of sqlalchemy==1.3.10
2019-11-01 14:06:37 INFO (MainThread) [homeassistant.setup] Setting up recorder
2019-11-01 14:06:37 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.5 seconds.
2019-11-01 14:06:37 INFO (SyncWorker_1) [homeassistant.util.package] Attempting install of distro==1.4.0
2019-11-01 14:06:37 INFO (MainThread) [homeassistant.setup] Setting up sun
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.1 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up person
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2019-11-01 14:06:38 ERROR (MainThread) [homeassistant.setup] Error during setup of component lovelace
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/setup.py", line 172, in _async_setup_component
    hass, processed_config
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/lovelace/__init__.py", line 66, in async_setup
    hass.components.frontend.async_register_built_in_panel(
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 421, in __getattr__
    component: Optional[ModuleType] = integration.get_component()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 223, in get_component
    cache[self.domain] = importlib.import_module(self.pkg_path)
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/frontend/__init__.py", line 10, in <module>
    import hass_frontend
ModuleNotFoundError: No module named 'hass_frontend'
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up group
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain group took 0.0 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up config
2019-11-01 14:06:38 ERROR (MainThread) [homeassistant.setup] Error during setup of component config
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/setup.py", line 172, in _async_setup_component
    hass, processed_config
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/config/__init__.py", line 34, in async_setup
    hass.components.frontend.async_register_built_in_panel(
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 421, in __getattr__
    component: Optional[ModuleType] = integration.get_component()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 223, in get_component
    cache[self.domain] = importlib.import_module(self.pkg_path)
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/frontend/__init__.py", line 10, in <module>
    import hass_frontend
ModuleNotFoundError: No module named 'hass_frontend'
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up auth
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up script
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.0 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up webhook
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up system_health
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.0 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up history
2019-11-01 14:06:38 ERROR (MainThread) [homeassistant.setup] Error during setup of component history
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/setup.py", line 172, in _async_setup_component
    hass, processed_config
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/history/__init__.py", line 283, in async_setup
    hass.components.frontend.async_register_built_in_panel(
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 421, in __getattr__
    component: Optional[ModuleType] = integration.get_component()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 223, in get_component
    cache[self.domain] = importlib.import_module(self.pkg_path)
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/frontend/__init__.py", line 10, in <module>
    import hass_frontend
ModuleNotFoundError: No module named 'hass_frontend'
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up api
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain person took 0.2 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.0 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up device_automation
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.0 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setting up automation
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 0.0 seconds.
2019-11-01 14:06:38 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.0 seconds.
2019-11-01 14:06:38 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of frontend. Setup failed for dependencies: lovelace
2019-11-01 14:06:38 ERROR (MainThread) [homeassistant.setup] Setup failed for frontend: Could not set up all dependencies.
2019-11-01 14:06:38 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of map. Setup failed for dependencies: frontend
2019-11-01 14:06:38 ERROR (MainThread) [homeassistant.setup] Setup failed for map: Could not set up all dependencies.
2019-11-01 14:06:38 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of logbook. Setup failed for dependencies: frontend
2019-11-01 14:06:38 ERROR (MainThread) [homeassistant.setup] Setup failed for logbook: Could not set up all dependencies.
2019-11-01 14:06:45 INFO (MainThread) [homeassistant.setup] Setting up updater
2019-11-01 14:06:45 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.0 seconds.
2019-11-01 14:06:45 INFO (SyncWorker_18) [homeassistant.util.package] Attempting install of netdisco==2.6.0
2019-11-01 14:06:45 INFO (SyncWorker_10) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
2019-11-01 14:06:45 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
2019-11-01 14:06:45 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.0 seconds.
2019-11-01 14:06:45 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.updater
2019-11-01 14:06:45 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new binary_sensor.updater entity: binary_sensor.updater
2019-11-01 14:06:57 INFO (MainThread) [homeassistant.setup] Setting up ssdp
2019-11-01 14:06:57 INFO (MainThread) [homeassistant.setup] Setup of domain ssdp took 0.0 seconds.
2019-11-01 14:06:57 INFO (SyncWorker_19) [homeassistant.util.package] Attempting install of mutagen==1.42.0
2019-11-01 14:07:06 INFO (SyncWorker_5) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate
2019-11-01 14:07:06 INFO (SyncWorker_16) [homeassistant.util.package] Attempting install of hass-nabucasa==0.22
2019-11-01 14:08:20 INFO (MainThread) [homeassistant.setup] Setting up cloud
2019-11-01 14:08:20 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
2019-11-01 14:08:20 INFO (SyncWorker_6) [homeassistant.util.package] Attempting install of gTTS-token==1.1.3
2019-11-01 14:08:20 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 0.1 seconds.
2019-11-01 14:08:20 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.1 seconds.
2019-11-01 14:08:20 INFO (SyncWorker_11) [homeassistant.loader] Loaded esphome from homeassistant.components.esphome
2019-11-01 14:08:30 INFO (MainThread) [homeassistant.setup] Setting up tts
2019-11-01 14:08:30 INFO (SyncWorker_12) [homeassistant.components.tts] Create cache dir /home/homeassistant/.homeassistant/tts.
2019-11-01 14:08:30 INFO (SyncWorker_13) [homeassistant.util.package] Attempting install of PyNaCl==1.3.0
2019-11-01 14:08:39 ERROR (MainThread) [homeassistant.setup] Setup failed for mobile_app: Unable to import component
2019-11-01 14:08:39 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of default_config. Setup failed for dependencies: config, frontend, history, logbook, map, mobile_app
2019-11-01 14:08:39 INFO (SyncWorker_7) [homeassistant.util.package] Attempting install of aioesphomeapi==2.4.2
2019-11-01 14:08:39 ERROR (MainThread) [homeassistant.setup] Setup failed for default_config: Could not set up all dependencies.
2019-11-01 14:08:55 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 25.5 seconds.
2019-11-01 14:08:55 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 179.33s
2019-11-01 14:08:55 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2019-11-01 14:08:55 INFO (MainThread) [homeassistant.core] Timer:starting
2019-11-01 14:08:55 INFO (SyncWorker_8) [homeassistant.components.zeroconf] Starting Zeroconf broadcast

Additional information:
If i make a mistake, i don't know on which position. Does somebody had an idea or the same problem?
Thanks for helping.
(If this is the wrong place for this issue ticket, i'm sorry)

This is the bug/issue tracker for Home Assistant. Please use the forum for questions about installation, setup, configuration and usage. For Hassbian -> https://community.home-assistant.io/c/installation/hassbian
Also, Hassbian is discontinued.

Oh, i didn't get this information about hassbian. Thanks!
But i think, that there is a problem on install script that will be execute on the first start of Home Assistant. If i understand #28361 right, he has the same problem. (First post)

@fabaff
There is realy a small problem at script:
The current raspbian buster apt repository list don't contains a docker version.
With this information, the installation guide on
https://www.home-assistant.io/docs/installation/raspberry-pi/
can't work.
After i installed docker manually, everything works fine. I think, a small warning at start of this guide would be helpfull.


Don't hardcode Luigi v1.1.2

The new release of Luigi added a dependency on cached_property, which wasn't being found on the slave nodes.  This change installs Luigi on the slave nodes too, including all of Luigi's dependencies.

Fixes #96.


Update mdoc_2.13, sbt-mdoc to 2.2.19

Updates

org.scalameta:mdoc_2.13
org.scalameta:sbt-mdoc

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta" } ]

labels: library-update, semver-patch

Superseded by #535.


go.mod: Update hcsshim to v0.9.2

This tag brings in some bug fixes related to waiting for containers to terminate and
trying to kill an already terminated process, as well as tty support (exec -it) for
Windows Host Process Containers.

I forget the integration/client dance when updating deps every. single. time.


Ability to write to the console and/or log file

Would be useful for developers and users.
I don't know if System.Console.SetOut could be used to use the existing Console.Write and Console.WriteLine methods.

I believe we could polish what the logging API offers before exposing to the public. #1370 is bothering me so much and I'm too busy solving that one.
I think we should not mess with System.Console.SetOut as it should be shared across the process. Would be too toxic if SHVDN changes that, way more problematic than when some dev changes it to whatever they like for debugging.

Hello. As a student striving for academic excellence, I found the review about the best paper writing service to be incredibly informative. It provided a detailed analysis of various services, highlighting their strengths in terms of quality, reliability, and affordability. Knowing which services are reputable and deliver exceptional results is invaluable when seeking assistance with challenging assignments. This review has certainly guided my decision-making process, ensuring I choose services that uphold high standards and help me achieve my academic goals effectively.


Create a README for using the Helm Chart for WSO2 Open Banking Deployment Pattern 1

Description:
Add a README for the using the Helm Chart created to deploy WSO2 Open Banking Deployment pattern 1 on Kubernetes

Fixed with https://github.com/wso2/kubernetes-open-banking/pull/22


refactor(dropdown): remove rootScope from the service

All scopes shares the same $$phase string, so there is no need to inject $rootScope when you have a scope hanging around already.

Perhaps I am wrong? let me check

No, I am just stupid, fixed.

I think $rootScope's was supposedly the only reliable one though - I am not sure if that changed though.

It is just a variable, I don't think it was never non reliable.

Looking at https://github.com/angular/angular.js/blob/master/src/ng/rootScope.js#L1312-L1322 , this appears to confirm my memory that we should only check against $rootScope.$$phase ever.

That doesn't prove anything, that is just the logic to start / stop phases. What I mean is that there is $$phase object in the $rootScope and all children has access to it and it is the same object everywhere.
Check: http://plnkr.co/edit/Osh4PGOSOkPBkpRXF866?p=preview

I absolutely would not trust that - the other mention of $$phase is https://github.com/angular/angular.js/blob/master/src/ng/rootScope.js#L169, and $rootScope.$$phase is also used in $evalAsync. IMO this is an invalid change & risky.

As per discussion, closing as $$phase can be different if an isolate scope lies in between the inheritance chain.


bug: --id-only

Outputs: more lines interfering even though --id-only flag is passed!!
%%bash --out job_id
  bacalhau docker run --download \
    --id-only \
    --timeout 3600 \
    --wait-timeout-secs 3600 \
    --wait \
    --gpu 0 \
    --cpu 2 \
    --memory '1Gb' \
    ghcr.io/decenter-ai/compute:v1.6.2

!echo $job_id

539eca54-8499-4f77-903e-529e7b75ac9d
/bin/bash: line 2: Results: command not found
/bin/bash: line 3: /content/job-539eca54: Is a directory

Rel #2966

What is
%%bash --out job_id

?

this is run in jupyter nb, i got this from bacalhau docs.

bacalhau docker run --download \
>     --id-only \
>     --timeout 3600 \
>     --wait-timeout-secs 3600 \
>     --wait \
>     --gpu 0 \
>     --cpu 2 \
>     --memory '1Gb' \
>     ghcr.io/decenter-ai/compute:v1.6.2

9773ff15-dee7-41d3-b192-77f598088574

Fetching results of job '9773ff15-dee7-41d3-b192-77f598088574'...
Results for job '9773ff15-dee7-41d3-b192-77f598088574' have been written to...
/Users/hiro/job-9773ff15

Output exceeds the id

@wdbaruni ys that was the desired behaviour. Download results but only print job-id.

@wdbaruni see if we can have download results can be print to stderr instead of stdout . That way, console logging is not affected.Its also best if you can do that for all the debugging stuffs, as it would keep stdout clean , making it easy to automate without complex chaining of commands.

On an additional note : @ CoopHive- cli was the only reliable interface to run jobs via server in production as the rest api server is timing out without providing the jobId or significant trace info. Hence its very critical for us to get just the id on stdout and rest of the trace/error logs on stdout


portable/static ip supporting in bosh-softlayer-cpi

In this PR, bosh-softlayer-cpi could support SL portable ip setting in deployment. And also, the vlan information settings could be moved from the cloud_properties of resource_pool to network, the following is a snippet in deployment yaml:
networks:
- cloud_properties:
    PrimaryBackendNetworkComponent:
      NetworkVlan:
        Id: <%=private_vlan_id%>
    PrimaryNetworkComponent:
      NetworkVlan:
        Id: <%=public_vlan_id%>
  dns:
  - <%=director_pub_ip%>
  - <IP_ADDRESS>
  - <IP_ADDRESS>
  name: default
  type: dynamic

@maximilien  @mattcui
It is ready for your review, thanks!

Thanks @jianqiu I will complete review today. Best.

Looking good but incomplete. Remember, all public method or function needs to have a unit test.
Please address and I will review again. Thanks,
max

@maximilien @mattcui
Hi Max,
I had updated the PR to contain all your comments, could you please review it again? Thanks!

Ok cool. Cheers :+1:

congrats. docs update coming?
Sent from my iPhone

On Sep 13, 2016, at 6:53 AM, dr.max<EMAIL_ADDRESS>wrote:
Merged #153.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

/cc @jianqiu and @gu-bin please update bosh.io docs for @cppforlife

Updated bosh.io doc for manual network in commit https://github.com/cloudfoundry/docs-bosh/pull/158/commits/06c4d1ff910d1eff5c403f31c4ff48452bae908b


Attach existing frames from an error to a new error without wrapping

Errors are not always wrapped where the underlying cause is available via Unwrap -- this is common to avoid implementation detail leakages across API boundaries, to avoid callers depending on specific internal errors via errors.Is or errors.As.
However, this also loses any traces from the underlying errors, and traces aren't intended for APIs but debuggability. This is pretty common when Errorf is used with %v instead of %w. Ideally, we'd have some way to maintain the trace in these cases.
Example API to start the discussion:
if err := [...]; err != nil {
  return WithTrace(err).Errorf("foo: %v", err)
}

or
err := [...]
if errors.Is(err, fs.ErrNotExist) {
  return WithTrace(err).Wrap(errUserNotFound)
}

From an API perspective, we should avoid an API that takes 2 error arguments where one's used for the underlying trace, and the other is the returned error, as it's too easy to mixup the arguments.

If we do something like this, we'll may want to define a cross-repo interface contract for extracting trace information (similar to pkg/errors' interface{ Stacktrace() errors.StackTrace }) from an error without unwrapping it.


Automated cherry pick of #11569

Cherrypicking changes to build/mark-new-version from #11569,  #11124 and #11609
Have removed other doc changes.
This is another try at https://github.com/GoogleCloudPlatform/kubernetes/pull/11604

cc @zmerlynn @brendandburns @lavalamp

can you run this script on a copy of our docs and temporarily attach that in another commit, just so we can see what this does?

https://github.com/GoogleCloudPlatform/kubernetes/pull/11622 shows the result of running this script on our docs

I manually ran this on the docs, but I guess we still need to cherry pick if we make a 1.0.2?
I'll give this to @brendandburns, he can ask for a rebase if it looks like we want a 1.0.2.

The IS_VERSIONED tag prevents the unversioned warning munger from
reinstalling the warning.

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11619#issuecomment-125350565
.

If you'd like to get this in, you should soon, otherwise I'm calling dibs on mark-new-version.sh. :)

Rebasing

Rebased, PTAL.
Jenkins failed with error:
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from https://github.com/GoogleCloudPlatform/kubernetes

Restarting it.
@k8s-bot ok to test

LGTM, shippable is a flake, re-running.


feat: seda extension.

ok to test

ok to test

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/461/


Jazzy debian package release

I don't know if this falls under the scope of the PlanSys2 maintainers, but is there a known time that ROS 2 jazzy packages will be released to main: https://repo.ros2.org/status_page/ros_jazzy_default.html?q=plansys2 ?
The immediate symptom is that apt install ros2-jazzy-plansys2-core isn't working on the osrf/ros:jazzy-desktop-full docker image.

Ok, thanks. I have to check It. And yes, It is my responsability 😕


Show version on batch_scoring --version

Why was this merged with broken tests?

Looks like Jenkins config was broken.
Tests (all two) have passed locally.


Labels in Organ{A,C,S}MNIST

Hi,
do the labels in all three Organ{A,C,S}MNIST datasets correspond to the same organs? Thank you for sharing your work!

Yes. You can refer to the label info here.


Removing appveyor py2.7 check

For a few weeks, appveyor fails on python 2.7. I looked into it, and it was partly appveyor.yml, but also a mysterious failed unit-test in RK45 (test_stommel) that only appeared in py27.
Since it doesn't happen on any other platform or python version, and since we have now moved to python 3 as default for Parcels, I suggest that we suspend python2.7 support on Windows for now?

+1 for dropping Py27 for Windows.


[TIR] Improved error message if tir.Schedule passed to lower/build

Previously, if a TIR Schedule is passed to tvm.lower, the error message is returned ValueError: ('Expected input to be an IRModule, PrimFunc or Schedule, but got, ', <class 'tvm.tir.schedule.schedule.Schedule'>).  This can cause user confusion, as the expected class name in the error message does not differentiate between between a tvm.te.Schedule and a tvm.tir.Schedule.  Updated error message to explicitly state that this should be a te.Schedule.

@tvm-bot rerun

Thanks @Lunderberg!!


Allow to disable the main script

When using your own stub, e.g. in PsySH, the main script may be unnecessary

what is "main script" ?

Your application entry point which is the main setting.
The PHAR has another entry point which is the stub, which usually call the main script. But since in some cases the main script is registered as the stub, it doesn't make sense to include the main script in this case (although it has no effect, it's is only for a minor weight improvement)

so, if there is stub pointing to concrete file, main shall need to be empty, right?

yes or completely omitted.
There is a few cases where there is contradicting configurations ever since box2, I think it would be nice to provide some warnings about it to the user (see https://github.com/humbug/box/issues/123) but allowing the user to carry on

warning is nice, i would even crash and ask user to fix the config and decide what he want explicitly, instead of deciding for him (assuming that stub is used no main omitted or stub is default and main included)

I'm hesitating a bit between the two. Sometimes you want to tweak a bit the config to just test one setting and in those cases it's annoying to have to change more than one thing. For example you want to disable the signature for some reasons I don't feel like you should need to remove the private key path as well.
Since those decisions have always been made, it may be better to stay in line and just provide feedback of some kind about the config rather than bailing out hard. Another point is that it would make the Box2 -> Box3 migration easier


feat: add support for AsyncAPI 2.6

Description
This PR adds support for AsyncAPI 2.6.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.409%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4734

Relevant Lines:
4993

💛  - Coveralls

/rtm


[try-slang]: Polish the try-slang website

We need to polish the website, now the website just looks like a notebook without good layout and style.

https://github.com/shader-slang/slang-playground/pull/4


Add tooling to roll ASG with new AMI

Currently, the process for rolling a new AMI out to the autoscaling group is a bit manual. To avoid the situation in #78, we have to manually create a new EC2 instance with the appropriate settings (quite a few), and then attach it to the ASG once it's warmed up. Ideally we would have a script to take care of this for us.

This should be unneeded as long as we run the autoscaling group in a single availability zone, which I've set up now.


using spikes clips

Hi, Is it possible to use Ironclust in previously detected spikes?
Which should be the structure of the file with the spikes to do something like that?

it uses PC features for sorting (trFet_spk)  pope but I haven’t implemented an importing tool yet to extract features from spike clips. I think it should be easy and possible. Which format do you want to import from? Do you have an example file available to share?
-James

On Nov 11, 2019, at 10:01 AM, Fernando J. Chaure<EMAIL_ADDRESS>wrote:
Hi, Is it possible to use Ironclust in previously detected spikes?
Which should be the structure of the file with the spikes to do something like that?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'm testing a few things on single channels and for that cases I uses a matrix in a .mat. You can find an example file here. I know that the structure should be more complex for polytrodes, if you show me the easiest way to give spikes to ironclus I will do the conversion.

I added irc2 import-clip myfile.mat command. it will output firings.mda  file in the same directory where the .mat file is located. Please click on the link to learn how to parse the output.

Sorry I wasn't able to run the code, I though that I was doing something wrong. I tried a few things like adding a check in the line 116 of irc2 to don't enter the if when S0 already exist, etc;  but I couldn't fix the the real issue.


Suport for IPv6

Any chance we could get support for IPv6 in the config process? My ISP only provides IPv6 and I haven't been able to get the VPN to work yet.

We don't have that yet, but that's a really good question. For now: do the install, and then afterwards edit the config files as described in https://community.openvpn.net/openvpn/wiki/IPv6 @0-kaladin: this is something we will need to do

Change proto udp into proto udp6

Also take a look at this section about IPv6 routes.

This is mandatory, my ISP start to provide only IPv6

@nellsavedra if you think this is mandatory, just make a pull request yourself!
sorry if I am being quite rude, but there's no such thing as mandatory and priority around here.
this is mainly maintained with @0-kaladin and @redfast00 free time, and more recently by me, and I am also with a big lack of free time since I just changed job and country.
so if you think this is URGENT, well do it and make a pull request, otherwise, you will have to wait until we have time for that!
I am sorry.

Considering:  https://github.com/pivpn/pivpn/issues/619
@orazioedoardo @devZer0
Shall we disable IPv6 until we support setup for it?
actually, I don't think it will solve the issue as the connection probably falls back to IPv6 on the client side of things ...
As i don't have IPv6 can't really test this ... any comments?

i would disable ipv6 until people complain

i actually just disabled ipv6 on my windows machine and everything works as it should. I know this isn't the preferred option but it works for me.
My ISP is Comcast and the router hands out ipv6 by default but it will do ipv4 as a fallback.

That's the only doubt I have .. if disabling IPv6 on the server side will be enough to fix the issue ... but I expect that the client will eventually fall back to IPv6 if its enable on clientside thus bypassing the VPN and leaking the IPv6

I honestly think it client depended as my Asus router && Android phone do not have this issue and neither leak ipv6 DNS to my knowledge.
I have tested with all sorts dns leak testing sites. And seen 0 positive results in that area.

It's possible to enable ipv6 networking over VPN, correct? If that's the case then it wouldn't fallback as long as blocking outside dns still happened? Im not completely sure the commands to setup and test a dual stack config are or I would test them

Not 100% sure how OpenVPN handles it, but in WireGuard, if one does not enable IPv6 forwarding on the server, there are two possible issues if the client supports IPv6:

You force ::1 IPv6 route through the VPN on the client, then IPv6 connections simply hang.
You do not force IPv6 through VPN, then those will bypass the VPN, so inexperienced users will never know if they have a private connection up or not, being an in-acceptable case.
So either all clients need to disable IPv6 (and this is not always possible, e.g. in case or Android and other restrictive OS), or IPv6 forwarding/handling needs to be enabled on the server to have an acceptable situation.

As said not sure how this is/can be handled with OpenVPN. If there is a way to force IPv6 to IPv4 fallback silently without any hang, then this is probably the easiest solution for now.
Of course all this applies for DNS requests as well.

You only have to change one line in server.conf!
tcp to tcp6 or from upd to udp6!
In your client configurations, you just have to replace your IPv4 with your IPv6!
Also change udp -> udp6 / tcp -> tcp6
If i find some time i create a pull request ... one little pull request is done ... that fixed the stats ...
A IPv6 is simply longer than a IPv4 :-)

Is this explanation valid for openvpn or wireguard? If it is for openvpn, can you describe what I have to do in wireguard to enable the IPv6 support? Reason: I read that some hotels provide only IPv6 WLAN, then I assume the current configuration will not work?

tcp to tcp6 or from upd to udp6!

This is for OpenVPN, although don't ask me about the details 😉.
For WireGuard:

Assure that the server can connect to IPv6 hosts, e.g.: ping -6 dns9.quad9.net
Server-side, enable forwarding for IPv6 separately and assure that the server accepts IPv6 router advertisements even that it acts as router for the VPN itself (accept_ra=2):PostUp = sysctl net.ipv6.conf.eth0.accept_ra=2
PostUp = sysctl net.ipv6.conf.%i.forwarding=1 net.ipv6.conf.eth0.forwarding=1
PostUp = ip6tables -A FORWARD -i %i -j ACCEPT; ip6tables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = ip6tables -D FORWARD -i %i -j ACCEPT; ip6tables -t nat -D POSTROUTING -o eth0 -j MASQUERADE

Forwarding rules be applied via nftables (or bpfilter?) as well, depending on machine and kernel capabilities + available userspace firewall frontends.
Replace eth0 with the actual network interface for outgoing requests on the server.

Client-side force IPv6 requests to be done through the VPN as well separately:AllowedIPs = <IP_ADDRESS>/0, ::/0

Thanks for your fast answer!
Just to be sure to understand everything:

* Assure that the server can connect to IPv6 hosts, e.g.: `ping -6 dns9.quad9.net`

Ok I have tired this on my raspberry pi, result:
PING dns9.quad9.net(2620:fe::9) 56 data bytes 64 bytes from 2620:fe::9: icmp_seq=1 ttl=58 time=14.2 ms
I would assume this is ok because "2620:fe::9" looks like a IPv6 address.
This 4 lines has to be added to iptables (this is installed on raspbian) and modified according to my eth0 interface?:

* **Server-side**, enable forwarding for IPv6 separately and assure that the server accepts IPv6 router advertisements even that it acts as router for the VPN itself (`accept_ra=2`):

.....
Can you explain shortly what these 4 lines will do?

As far as I understand this was already added by pivpn during setup, I can see this in my client configuration details:

* **Client-side** force IPv6 requests to be done through the VPN as well separately:
  ```
  AllowedIPs = <IP_ADDRESS>/0, ::/0
  ```

This 4 lines has to be added to iptables (this is installed on raspbian) and modified according to my eth0 interface?

The 4 lines have to be added to your WireGuard server config /etc/wireguard/wg0.conf to the [Interface] block. So on startup via wg-quick service, iptables is called automatically to establish the forwarding rules.

As far as I understand this was already added by pivpn during setup, I can see this in my client configuration details:

Ah yes, I should have checked what PiVPN actually adds 😄.

@MichaIng Thanks again for your fast answer, fantastic support!
I have added the four lines to the wg0.conf file and tested with ipv6-test.com whether IPv6 support is detected using wireguard VPN on my smartphone. But it still shows IPv6 not supported.

  * Replace `eth0` with the actual network interface for outgoing requests on the server.

My RPi is connected with a ethernet cable and is using just ethernet connection, so I left eth0 in the four lines. Or is the "interface for outgoing requsts on the server" the wiregurard (wg0) interface?!?

I have added the four lines to the wg0.conf file and tested with ipv6-test.com whether IPv6 support is detected using wireguard VPN on my smartphone. But it still shows IPv6 not supported.

Do you have IPv6 connectivity on your cellular connection?

You are right I don't have IPv6 connectivity on my cellular connection. Sorry I missed that...

The 4 lines have to be added to your WireGuard server config /etc/wireguard/wg0.conf to the [Interface] block. So on startup via wg-quick service, iptables is called automatically to establish the forwarding rules.

Is it normal that after adding these four lines ifconfig shows me for eth0:
two inet6 fd00 and two inet6 200x addresses? (before adding just one fd00, fe80, 200x address)?

Which network interface(s) are those addresses attached to? ip a

Which network interface(s) are those addresses attached to? ip a

As far as I understand to eth0, here the output of ip a
XXXXXX@raspberrypi:~ $ ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

	link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
	inet xxx.xxx.xxx.xxx/8 scope host lo
		valid_lft forever preferred_lft forever
	inet6 ::1/128 scope host
	       valid_lft forever preferred_lft forever

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

	link/ether xx:xx:xx:xx:xx:xx brd xx:xx:xx:xx:xx:xx
	inet xxx.xxx.xxx.xxx/xx brd xxx.xxx.xxx.xxx scope global noprefixroute eth0
		valid_lft forever preferred_lft forever
	inet6 200x:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr 	noprefixroute
		valid_lft 7154sec preferred_lft 1216sec
	inet6 200x:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr
		valid_lft 7154sec preferred_lft 1216sec
	inet6 fd00::xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr
		valid_lft 7154sec preferred_lft 3554sec
	inet6 fd00::xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr noprefixroute
		valid_lft 7154sec preferred_lft 3554sec
	inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link
		valid_lft forever preferred_lft forever

3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
	link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff

4: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
	link/none
	inet xxx.xxx.xxx.xxx/24 scope global wg0
		valid_lft forever preferred_lft forever

Hmm, indeed the Unique Local Unicast (fd00::) and Global Unicast (200x::) addresses seem to be doubled somehow. Now sure if/how this is related to the WireGuard PostUp commands as those should only have an effect on how incoming requests are handled and forwarded. Those addresses should be assigned by the router. How do you do that, DHCPv6?
On the Pi check whether the rules have been applied successfully and whether WireGuard reported any errors:
sysctl net.ipv6.conf.eth0.accept_ra net.ipv6.conf.{eth0,wg0}.forwarding
journalctl -u wg-quick@wg0

Hmm, indeed the Unique Local Unicast (fd00::) and Global Unicast (200x::) addresses seem to be > doubled somehow. Now sure if/how this is related to the WireGuard PostUp commands as those > > should only have an effect on how incoming requests are handled and forwarded.

I have restarted the RPi and after that the double addresses are gone. Very curious :-/

Those addresses should be assigned by the router. How do you do that, DHCPv6?

I use a Fritzbox as a router and yes DHCPv6 is activated but at the moment only IPv6 DNS Server is assigned to the clients. There are two other options (assign DNS+IA_PD or assign DNS+IA_PD+IA_NA) but according to some threads in the Pihole forum the most common advise is there to use only the first option "assign DNS-Server".
Would you recommend one of the other options?

On the Pi check whether the rules have been applied successfully and whether WireGuard reported any errors:
sysctl net.ipv6.conf.eth0.accept_ra net.ipv6.conf.{eth0,wg0}.forwarding

Here the result:
net.ipv6.conf.eth0.accept_ra = 2
net.ipv6.conf.eth0.forwarding = 1
net.ipv6.conf.wg0.forwarding = 1

journalctl -u wg-quick@wg0

Here the result:
-- Logs begin at Sun 2020-06-14 23:01:17 CEST, end at Sun 2020-06-14 23:02:14 CEST. --
Jun 14 23:01:43 raspberrypi systemd[1]: Starting WireGuard via wg-quick(8) for wg0...

IA_PD+IA_NA should not be required indeed.
I was reading a bid further into it and get contrary info. In some cases an IPv6 subnet is used additionally for the tunnel network: https://stanislas.blog/2019/01/how-to-setup-vpn-server-wireguard-nat-ipv6/
This somehow makes sense as every adapter that wants to communicate via IPv6 requires an IPv6 address. However the last time I tested it I was able to ping IPv6 addresses without it and some guides also do not contain this while containing IPv6 tunnelling and forwarding rules: https://wiki.ubuntuusers.de/WireGuard/
In IPv6 many thanks are automated and I probably that additional two IPv6 addresses on the eth0 interface are due to forwarding IPv6 from the IPv4-only wg0 interface. Adding an IPv6 subnet to the WireGard network may compensate this or in your case enable IPv6 through the VPN at all.
Probably some network specialist needs to give clarification, probably I find some time do run tests here and verify that/how it works in my case without assigning IPv6 addresses to the WireGuard interfaces 🤔.

@MichaIng Many thanks for your effort! I'm not at all a network specialist but I can support with additional tests in my configuration if needed and if you want. When I look in your links and in this link from ubuntuusers: https://technofaq.org/posts/2017/10/how-to-setup-wireguard-vpn-on-your-debian-gnulinux-server-with-ipv6-support/ then I see there is a IPv6 address defined in the /etc/wireguard/wg0.conf interface section. In my config file is at the moment only a IPv4 address defined. But is this a random generated IPv6 address?!? :-/

The Ubuntu wiki does not use an IPv6 address but the other one does and yes this is the first thing I'd try as well.

But is this a random generated IPv6 address?!?

Not totally random, but it seems to be an own chosen one from the ULA (unique local address) range.
I found another source where they used a sub range from the one that the router assigned to the eth0 interface, in your case one from the fd00::XXX address with e.g. /72 mask (so a smaller range). However actually it should not matter as long as it does not collide with the other VPN host or clients IPv6 addresses, so choosing an own one should work fine.

Thanks to the previous comments and tips, with a little addition to the configs I have ipv6 fully working on the wg tunnel, also works with a cellular connection which is only ipv4.
Here are my working configs.
wg0.conf
`[Interface]
PrivateKey = hide
Address = <IP_ADDRESS>/24,fd42:42:42::1/64
ListenPort = 51899
PostUp = sysctl net.ipv6.conf.eth0.accept_ra=2
PostUp = sysctl net.ipv6.conf.%i.forwarding=1 net.ipv6.conf.eth0.forwarding=1
PostUp = ip6tables -A FORWARD -i %i -j ACCEPT; ip6tables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = ip6tables -D FORWARD -i %i -j ACCEPT; ip6tables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
[Peer]
PublicKey = hide
PresharedKey = hide
AllowedIPs = <IP_ADDRESS>/32, fd42:42:42::2/128
`
And the client config
`[Interface]
PrivateKey = client 1 private key
Address = <IP_ADDRESS>/24,fd42:42:42::2/64
DNS = <IP_ADDRESS>
[Peer]
PublicKey = server public key
Endpoint = :51899
AllowedIPs = <IP_ADDRESS>/0,::/0`
And the connection is up
wg show
`interface: wg0
public key: hide
private key: (hidden)
listening port: 51899
peer: hide
preshared key: (hidden)
endpoint: xxx.xxx.xxx.xxx:40869
allowed ips: <IP_ADDRESS>/32, fd42:42:42::2/128
latest handshake: 8 seconds ago
transfer: 335.25 KiB received, 1.40 MiB sent`
To add another peer simply increment the last digit in the ipv6 address as we do with ipv4
I do like the simplicity of using pivpn to add wireguard tunnels, with these few additions ipv6 is fully working too, well for me, anyone else find this a solution for them?

@btb23 use 3  ```
to signify

multi line

code blocks

use 1 `
to signify single line code

@btb23  thanks for sharing your solution. I have now find the time to try that on my pi. In my first trails I had no success.
Issues on my side after trying to transfer your solution into my configuration:

Not really a problem but confusing: ip a shows on eth0 two external IPv6 addresses.
wg show shows me also the configured IPv6 address but all IPv6 tests are not successful. (cellular connection with IPv4 and WiFi with IPv4/6)

Questions regarding your solution:

Is this address fd42:42:42::1/64 just random or according to the ULA defined in your router? I have tried both router ULA +1,2,3,4 for the clients and with a different ULA.
Why one time /64 and for the peers /128? (I tried with both /64 for all, /128 only for clients)
Have you activated port forwarding for IPv4 and IPv6 in your router?
Have also changed something at your clients? I assume that the configuration in the android /iOS app has to be updated or not?

is there any plans to add listening on IPv6 as a non-default?

@Dunrar I would do that but I'm unable to test as I do not have access to (multiple) IPv6 networks, don't know about @4s3ti. If someone is willing to make changes and test, why not? We could add support.

unfortunately I have no reliable way to test IPv6 =/

I would be able to run test. I could also open a related PR, but it could take a while until I find time, so would be great if someone else could do that,
A working config for WireGuard has been posted above: https://github.com/pivpn/pivpn/issues/259#issuecomment-699619034

I can't get this to work, but I'm fortunate enough to have true DualStack, so I atleast have IPv4 going for me. I don't even really understand why I can't use IPv6 through my IPv4 tunnel though. Do I really need two separate connections, one to my public IPv4 and one to my public IPv6 address, just to have support for both types? That's sounds kinda wasteful IMO but I guess that's just how it works. Hopefully PiVPN will sooner than later make this whole process as painless as possible since the world is heading to IPv6.

I don't even really understand why I can't use IPv6 through my IPv4 tunnel though. Do I really need two separate connections, one to my public IPv4 and one to my public IPv6 address, just to have support for both types?

The connection to the VPN server is not relevant for the connections passed through the VPN server. So you can without problems connect via IPv4 to the VPN server and then have an IPv6 connection to a remote host tunnelled through it.
If a client is in an environment with IPv6 support and has it not actively disabled, it likely has a GUA IPv6 address as well and will in most cases by default try to connect via IPv6 to hosts if an AAAA record is provided. In this case, you don't want to bypass your VPN ("IPv6 leak"), but want to have that IPv6 request tunnelled as well, and successful instead of hanging. The client VPN config needs to force all IPv6 requests through the tunnel (which is already the case with the default PiVPN client config, if I'm not mistaken) and the VPN server needs to support IPv6, have IPv6 forwarding and NATing enabled, which is covered by the sysctl and iptables6 commands provided above.

@MichaIng Okay good, I didn't really invest too much time because I couldn't even establish a connection to my public IPv6 address (port was open and firewall deactivated for the host) but if this can already work. I'll give it a try tomorrow.
Although I'd like to know this one as well:

Is this address fd42:42:42::1/64 just random or according to the ULA defined in your router? I have tried both router ULA +1,2,3,4 for the clients and with a random ULA.

That is the VPN internal IPv6 address, so any address (range) within the fd00::/8 block will work. Of course clients then need to be defined within the same subnet.
I read again through the old posts above, and indeed there seem to be cases where the dedicated/additional IPv6 addresses on the WireGuard network seem to be required. At least worth to test when it's not working without, adding that to server and client configs shouldn't be so hard. I'll also play around with it when I find time.

That is the VPN internal IPv6 address, so any address (range) within the fd00::/8 block will work.

I know that these are ULAs, but I didn't know that any device can just claim one (I though that only the DHCPv6 can). Anyway, I copied btb23's config exactly, but that didn't work for me (I couldn't even ping fd42:42:42::1). It's probably the iptables that are not configured correctly in my setup, but I honestly don't care. I chose PiVPN because I didn't want to deal with this, so let's hope the devs provide a automagical solution 😛

I didn't know that any device can just claim one (I though that only the DHCPv6 can).

Well, every device can apply itself any IP (or you can apply any IP to any device). If a DHCPv6 server is present, than the device can ask which ULA it shall apply and respect it, or keep looking for RAs to do SLAAC do something totally different. Not that it would make sense, but it's the devices which apply the IPs themselves and nothing external can strictly force them to do anything 😉.
In case of the VPN, there is no DHCP-ish server, but the client indeed must create the network interface, apply the IP and the routes everything themselves, which is practically done by the wg-quick command/service, respectively the WireGuard client, based on the config you gave them. Then it can try to establish the connection with the server and if IP and key matches to what the server has stored about that client, it is granted.
I cope you kept your private and public key info when applying btb23's configs 😉. To debug, check the WireGuard server logs and whether IP and routes have been applied as expected:
ip a s wg0
ip r l dev wg0
ip -6 r l dev wg0

@MichaIng Appreciate the support, but I don't think just helping me to pull this off is gonna amount to much. Instead you should make it work on your setup first, create a PR and hope to get enough input from the PiVPN community (including me) to get something going that works for everyone :)

Well it might help to answer the last open questions before creating the PR. But yes, often having a PR is a more productive basis for testing and discussion. I'll see if I find time, as currently I'm very busy with own projects.


Fix ExpressEntityEntries.publicIdentifier migration

This is a repeatable migration, so we should be sure we don't wipe out previous data.
See https://github.com/concrete5/concrete5/pull/7822#discussion_r441125632

Can you also reopen this against the 8.5.x branch?

Can you also open this against the 8.5.x branch?

Not very soon. I think you should be able to cherry pick this commit btw

Thanks, will do.


Availability of baseline model

Hi @bowenliu16!
The paper associated with this repository describes a baseline model with "2868 unique retrosynthetic reaction rules, defined by SMARTS strings." Is that baseline model available in this repository or elsewhere?
Thanks!

Hi @rmcgibbo!
The baseline that we adapted can be found here:
https://github.com/connorcoley/ochem_predict_nn


Select on tables do not return insertion order, rather PK (id) order

Hi, is there any way to select rows ordered by insertion order? After testing I found that the query select(table) returns the rows ordered by id.

In sqlite, the order of returned rows is undefined if you don't use an explicit ORDER BY clause. They just happen to be ordered by their rowid (or INTEGER PRIMARY KEY column) by default.

is there any way to select rows ordered by insertion order

Usually, that's what should happen if you have an auto-incrementing integer column. If you have a custom primary key that's also an int, you'd have to add another int column to track the insertion order.
You could use DateTimeColumn createdAt => dateTime().default(currentDateAndTime)() and then sort by that.

I have inserted the rows in this order (id:45, title: "Category1"), (id:44, title: "Category2"), ..., (id:40, title:"Category6") in a batch. However when I make a select 40, 41,... 46 is returned. I don't think this is a normal behavior.

Yes it is. From the sqlite3 documentation:

If a SELECT statement that returns more than one row does not have an ORDER BY clause, the order in which the rows are returned is undefined

So any order for the select is normal behavior if you don't set an explicit ORDER BY.
If sqlite3 preserved the insertion order, it would have to store additional data so one can argue that it shouldn't do that by default. If you want to sort by insertion order, you would have to add your own incrementing column in Dart. I'll close this issue since moor behaves as intended, but I can help you add that column if you want to.


[enhancement]:Reloading while going from one page to other

What's the style idea?
We need to improve  the way it is traversing pages when clicked the view profile which will seamlessly change the pages
Add screenshots
Add screenshots
Code of Conduct

[x] I agree to follow this project's Code of Conduct

Okay Thank you

i would like to resolve this issue

Yeah it redirects user to the portfolio link user has provided and we are opening it in a new tab.
whats the issue in it?

It can redirect seamlessly without loading the dom

We can't do that because it is an external link.

Okay okay


Deprecate a CommandOption parameter

Is your feature request related to a problem? Please describe.
It would be useful if there was a solution to allow us to mark a parameter as deprecated and to recommend using a replacement parameter. Given the below example that sets the resource group name:
[CommandOption("--resource-group-name")]
public string? ResourceGroupName { get; set; }

We would then wish to shorten this parameter to --resource-group whilst still supporting consumers to use the --resource-group-name parameter but instead with a warning or hint to use the recommended flag instead.
An example of other Cli tools that have done this in the past is Docker recommending to use --help instead of -h:

Describe the solution you'd like
I'd welcome a more elegant solution, but possibly allowing adding multiple attributes to a property, with a new "deprecated" parameter to pass in could be an option?
[CommandOption("--resource-group-name", isDeprecated = true)]
[CommandOption("--resource-group")]
public string? ResourceGroupName { get; set; }

This would then generate a message to suggest using the current CommandOption instead.
Describe alternatives you've considered
A couple of alternatives used at the moment can be found below.

Just append to the template after the first Long parameter name
[CommandOption("--resource-group|--resource-group-name")]
public string? ResourceGroupName { get; set; }

This will accept both parameters, and the help with show the primary long parameter by default. The only downside is there is no warning message to encourage usage of the new parameter

Add multiple properties and use a validator
[CommandOption("--resource-group-name")]
public string? ResourceGroupOld { get; set; }

[CommandOption("--resource-group")]
public string? ResourceGroupNew { get; set; }

public string? ResourceGroupName => this.ResourceGroupNew ?? this.ResourceGroupOld

public override ValidationResult Validate()
{
    if (!string.IsNullOrWhiteSpace(this.ResourceGroupOld))
    {
        AnsiConsole.MarkupLine("[red]--resource-group-name is deprecated, use --resource-group instead.[/]");
    }
    return base.Validate();
}

This approach does work as expected, but requires adding a bit of boilerplate code (it may even be able to be simplified?)

Additional context

Cool suggestion, I agree.

Why not use the ObsoleteAttribute here instead?


[WIP] Gene refinement

Support for Gene refinement
Partnered with https://github.com/artsy/eigen/pull/1960

          1 Warning

:warning:
The following files do not have tests: lib/components/artist/about.js, lib/components/artist/shows/large_list.js, lib/components/buttons/navigation_button.js, lib/containers/gene.js, lib/containers/home.js, lib/native_modules/refine_callback.js & lib/relay/config.js

  Generated by :no_entry_sign: danger

This also improves logging for the infinite scroll view, I've got a simpler version of the Relay logger in there now

MP PR is in 👍


RAWMOUSE: Sort usButtonFlags RI_MOUSE_* flags by value. Merge cells with same value.

@DJm00n : Thanks for your contribution! The author(s) have been notified to review your proposed change.