Feat minify messages

In Order To make our chat-views more useful we try to minify/collapse messages or their respective content so that the view is not cluttered with cascading and duplicate entries
This PR changes the following in the chat-view (aka open connection view)
Any message that has been proposed/claimed/rejected/retracted will be minified in the chat view (see screenshot below

)
The referenced-content of a message will be collapsible/expandable now, the references have the following inital collapsed State:

forwards -> not collapsed by default
proposes -> not collapsed by default
claims -> not collapsed by default
accepts -> collapsed by default
proposeToCancel -> collapsed by default
rejects -> collapsed by default
retracts -> collapsed by default

If a message containing references is going to be collapsed (e.g if the message was rejected) the contained references of the message are also all collapsed -> this will ensure that upon displaying (click on the collapsed message) the message we will not get bombarded with the whole content right away

It's better now but still inconsistent and hard to follow. Consider a proposal.
It starts with a message (M) that message gets hidden when it s proposed by proposal P.
When P gets accepted by A, though, P gets different buttons, but keeps its title.
I think the transition M -> P is good, but P -> A is inconsistent with that and not as good.
How about this:
as P gets accepted by A, P is hidden (just as M was earlier), saying 'Message was accepted. Click to expand', and A starts expanded - same for propose to cancel and accept.
good:

not so good:

I find this confusing because the state of the agreement protocol here is already 'agreed', but the prominent interaction element says 'proposes'. Confusingly, the button says 'propose to cancel'.
Wording
I find the titles confusing.


[R] Refer to the Arrow C++ compute engine as Acero

Once ARROW-16632 and ARROW-16626 are complete, we should update some of the text in the R cookbook to refer to the Arrow C++ compute engine using its new name, Acero. We should try to be quite explicit about the fact that the {arrow} R package converts {dplyr} code into an Acero ExecPlan.

can you expand upon where

We should try to be quite explicit about the fact that the {arrow} R package converts {dplyr} code into an Acero ExecPlan.

would fit, in terms of where in the cookbook it'd be relevant to mention this?

Yes, I think it would be valuable to add some content about this to the Manipulating Data - Tables R cookbook entry. It would be great if that cookbook entry could explain what happens under the hood when the user calls dplyr verbs on an Arrow table/recordbatch/dataset and then calls collect() or compute(): an Acero ExecPlan is constructed and executed.

OK, make sense, we could mention that briefly in the intro and then link to some docs where it's explained in more detail.


"Glitchless" Mode Request

Simply, A mode that disables logic/coloring for glitch obtainable items. I.e., reducing the tracker to Bright Green/Yellow/Red/Grey. This would be ideal for users such as myself, that perform runs without using glitches.

This can be closed out, as it was added in a recent update


Cannot debug with F10 or F11 in Python 2.7 debugger, the program will be hanged without any response.

Steps to Reproduce
1.Create python application in vs
2.Typing code:

3.Make suew "Use legacy debugger in tool->Options->Python->Debugging" was unchecked
4.Press F10 or F11 to debub all the time in the program
Expected behavior
Debug and output successfully
Additional context and screenshots
It will be hanged during debug

Repro step
debugger.zip
Test Environment:

Thanks. I can reproduce. Here is the code. This is using ptvsd 4.3.2.
log.txt
from math import cos, radians

# Create a string with spaces proportional to a cosine of x in degrees
def make_dot_string(x):
    rad = radians(x)                             # cos works with radians
    numspaces = int(20 * cos(radians(x)) + 20)   # scale to 0-40 spaces
    st = ' ' * numspaces + 'o'                   # place 'o' after the spaces
    return st

def main():
    for i in range(0, 1800, 12):
        s = make_dot_string(i)
        print(s)

main()


Application with Opencv library fails on release mode builds.

Describe the bug
Installed opencv library using vcpkg. Installation and integration was successful and a test application builds successfully on debug mode. During release build, it fails with the message 'opencv_aruco340.dll was not found'. The project configuration is same for both modes, hence it is not related to the IDE project settings.
Environment

OS: Windows
Compiler: Visual C++ 2019

To Reproduce
Steps to reproduce the behavior:

vcpkg install opencv3[ffmpeg]:x64-windows

Build a test application release mode.

are you up to date with vcpkg? the 340 dll extension looks very suspicious on that end

vcpkg   version: 2021-05-05-9f849c4c43e50d1b16186ae76681c27b0c1be9d9`

@seccpur ,Thanks for posting this issue, please use git pull update vcpkg to the latest and try again.

and can you share cmake cache and logs of the build of your application? i fear it is finding another opencv installation

Here's some relevant files related to debug built:
CMakeError.log
cmake_check_cache.zip

don't you have a file called CMakeCache.txt?

This the CMakeCache.txt file. CMakeCache.txt

not of opencv, but of your application.
also, since it’s opencv3, the line you called in vcpkg is ./vcpkg install opencv3[ffmpeg]
without the 3, it would install opencv4, or either you are overlaying opencv

My bad, its typos in this thread, as you can clearly see opencv3 is definitely in the  CMakeCache.txt file.

so? is it working now?

Same.  It's not working in debug mode.

I am not sure how. Both are free from any run time error. Thanks for the support.


Docs: no cycle, split code examples so file separation is obvious

Making it more obvious that the code examples are individual files.

Coverage remained the same at 97.802% when pulling d27aeaf996799e5edcf99cd2002924d1fef92569 on alex-page:master into cf5573b5784a8b19c1a7c3e4003005dfaadc4375 on benmosher:master.

Coverage remained the same at 97.802% when pulling d27aeaf996799e5edcf99cd2002924d1fef92569 on alex-page:master into cf5573b5784a8b19c1a7c3e4003005dfaadc4375 on benmosher:master.


Refer to modelcard creator app from doc

Related to discussion in slack (internal link)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Change offset to 2 characters instead of 1

Hello, why?

This fixes https://github.com/kovetskiy/mark/issues/42. There's detailed comments on that ticket, but I'll summarize here:
I pulled down the repo so I could repro locally and characterize. I made 2 test files, one with only the necessary front matter, and another that duplicated the attachment in the front matter multiple times.
test1.md
test2.md

test1.md results:
>

# Test File

test2.md results:
tachment: images/1.png -->

# Test File

It's not 1:1 for lines of front matter to characters left in the markdown, but it's close.
I instrumented by inserting fmt.Printf("MD: %s", markdown) into main.go at line 165.
I believe the issue is that we must adjust the offset for 2 characters to account for both characters of the line feed.

Thanks for the explanation, your patience, and your willingness to contribute to the project.
I've finally got my hands on this ticket. I checked your test1/test markdown files and found why you need +2 there. This is because you used \r\n as new line breaks. It will definitely work for these files but will not work for 99% of other files created on Linux/macOS since on Unix we don't use \r for breaking lines.
More about new line format difference: https://en.wikipedia.org/wiki/Newline?oldformat=true
What I'd suggest is to rollback the current change and make ExtractData expect newline break to be \n but in the processFile in main.go drop all the \r\n breaks and replace them with \n.
It would be great to have a test for this, but a comment on top of string replacement would work for me too.

Changing offset to +2 also can lead to a panic if a file uses \n instead of \r\n.
For example, you can take your test2.md and convert it to unix line breaking standard:
sed -i $'s/\r$//' test2.md

running mark against it will  result in panic:
panic: runtime error: slice bounds out of range [1020:1002]

goroutine 1 [running]:
github.com/kovetskiy/mark/pkg/mark.ExtractMeta(0xc000328000, 0x3ea, 0x3eb, 0x3ea, 0x3eb, 0x0, 0x0, 0x3c, 0x10)

Ahhh, I see!  I'll pick this up on my next loop. I thought it was because there were 2 characters in \n. Honestly I may just fix my file. It's curious it's coming in with those line breaks considering I'm authoring in VSCode/Windows.

It looks like you've solved your issue by just using \n instead of \r\n. Feel free to re-open the issue!


Issue from website page Write Your First Flutter App

From URL: https://flutter.io/get-started/codelab/index.md

Can you elaborate on what the issue is, please?

@mit-mit That link is a 404.

Where did you find it? The actual page is https://flutter.io/get-started/codelab/.
The .md file is the source code of the page.

@mit-mit This issue is the result of what happens when someone clicks the "File Issue" link on that page and then hits "Submit new issue" without typing anything...
Source of the link:
<a href="https://github.com/flutter/flutter/issues/new?title=Issue from website page Write Your First Flutter App&body=From URL: https://flutter.io/get-started/codelab/index.md&labels=dev: docs - website" class="btn btn-sm">

@Herohtar, thanks, yup that is likely what happened. But as no actual issue has been mentioned, I'm going to close this.


docfix, reverse switch outputs

Can one of the admins verify this patch?

just learned that github edit feature creates new branch on official repo, closing this to make branch on my own cloned version and make PR from there


Cookie consent slightly broken

have to scroll to reach button on FF and Brave on real Android devices
no black background on old mobile Safari

On real Android device, multiple browsers:
![2020-11-10 10 18 42](https://user-images.githubusercontent.com/160299/98661343-3dff0600-233e-11eb-975b-4f5863407478.png =400x)
The page can be dragged around to get to the Got it! button.


Port to godot 4.0

Fixes: Merging gd4 to master
Fixes: https://github.com/Geequlim/ECMAScript/issues/139
Fix compile error for godot 4.0
Fix reference object constructor
Improve RefCounted binding
Rename ECMAScript to JavaScript for godot 4
Fix compile error with non-editor build
Implement JavaScriptCallable for Signal & slot
Implement script workflow
Godot call javascript is working
[FIX] Failsafe env["TOOLS"] variable getter
[FIX] Fixed missing comma
[FIX] Adds GDNative to GDExtension migration changes
[FIX] Adds missing get_global_name method
Updated JavaScript modules for Godot 4.0 branch
The commits address various issues, such as non-existent files, editor targets, module usage, and compilation errors. The messages also show an effort to align the project's GitHub actions with the main Godot repository and tackle platform-specific problems. Some commits address challenges related to advanced Linux builds and temporarily disable the "-werror" flag due to issues with QuickJS.

Waiting for the build to pass.


Update from upstream

This PR will update HTAN DCA to be level with Sage-Bionetworks/data_curator main branch.

FYI @elv-sb we may need to update the names of our secrets variables in HTAN DCA?

it looks like they have changed

ed in this update from the Sage-Bionetworks/data_curator:main


Clicking a method invocation take the user to the method declaration

As already discussed here: https://github.com/atom/symbols-view/issues/18
Would be nice to have that.
Sometimes you just want to click a method instead of navigating and then executing the shortcut.

see #2

Looks like I totally missed your commit etc... :relieved:


新增maven wrapper

maven版本3.5.0
https://github.com/alibaba/dubbo/issues/553

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

参考，#719


Import: fix most of #671

This gets started on #671. Okay, I actually wound up doing all of 1-4. Here's how it looks now:

I tested with a simple script and I can now "play" an animation by giving its name. It successfully round-trips with the exporter too.

Unique name were picked for each animation and stored in animation.track_name. It works just like picking names for other Blender stuff works, by appending .001, then .002, etc. until a name is free. The names are only unique within the current glTF file. There might be tracks already in the .blend that they collide with though.
Morph weights were spun out into their own file (did one object with both morph weight and TRS animations ever work? I think you need two actions...). I also redid it to use foreach_set like in #253 since it was actually easier, so there should be a nice performance boost.
Bones don't find their action by its name anymore, they look in a cache at gltf.arma_cache. This simplifies things a lot. This should get rid of the problems with grabbing old actions or animations having the same name, and I checked that #518 didn't regress.
Stashing was also simplified. Every time an action gets created, a note is pushed onto a work list at gltf.needs_stash and then it's all executed at the end. This got rid of a lot of repeated code too.
And restoring is now done by walking down from the root and and looking for strips with the right name and loading the action from those.
Hopefully you can tell me how it looks and if deleted anything I shouldn't have :)

Thanks for the PR. I will review it this week. Target is to merge it soon, to get it in 2.81 (we are now in a stabilization step, no more new features are allowed. But this PR can go, because this is "Improve and stabilize" step now)
PS: Don't hesitate to assign yourself the ticket when working on a feature, it will avoid someone else start working on same subject in same time


Chef 16: backport the post-bundle-install support

This is necessary to build against current omnibus-software and should hopefully be more reliable and is more flexible in terms of being able
to pull git gems into the appbundle.

red tests seem to be predominantly just dockerhub issues.


ImportError: cannot import name 'SIGPIPE' from 'signal'

D:\uro>uro
Traceback (most recent call last):
File "C:\Users\umara\AppData\Local\Programs\Python\Python38\Scripts\uro-script.py", line 33, in
sys.exit(load_entry_point('uro==0.0.2', 'console_scripts', 'uro')())
File "C:\Users\umara\AppData\Local\Programs\Python\Python38\Scripts\uro-script.py", line 25, in importlib_load_entry_point
return next(matches).load()
File "C:\Users\umara\AppData\Local\Programs\Python\Python38\lib\importlib\metadata.py", line 77, in load
module = import_module(match.group('module'))
File "C:\Users\umara\AppData\Local\Programs\Python\Python38\lib\importlib_init_.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "", line 259, in load_module
File "C:\Users\umara\AppData\Local\Programs\Python\Python38\lib\site-packages\uro-0.0.2-py3.8.egg\uro\uro.py", line 4, in
ImportError: cannot import name 'SIGPIPE' from 'signal' (C:\Users\umara\AppData\Local\Programs\Python\Python38\lib\signal.py)

You are using an older version of uro. This issue has been fixed, update your installation.

Issue still exists!

It should be fix now, please reinstall.


gofabric8 start on windows should try to use hyper-v for minikube & minishift - installing it if necessary

giving a nice error message if we can find Hyper-V is not installed and how to install it would be a nice step until we figure out how to install it automatically

we use hyper-v right now - though there's no attempt to install it yet


New ProtoData and annotated Builder methods

In this PR we update the version of ProtoData to 0.8.6.
Also, we apply the new capabilities of ProtoData to annotate build() and buildPartial() methods with @Validated and @NonValidated respectively.

@armiol, PTAL.
Please note that most of the changes are just the updates of config, not actual code repository changes.

@armiol, PTAL.

@dmdashenkov please update the PR description with the new version. I will be reviewing the PR itself tomorrow.


Thank you

Kindly continue this project till the end . . till it becomes one of the most famous tools in the world

I am working on something else right now, but I'll continue developing it as soon as possible and release a new version. Thanks !!!


[WIP] skrooge2: init at 2.4.0

Motivation for this change
The available skrooge package relies on KDE4. I would like to introduce the new version which relies on Qt5 and Kf5.
Things done

[ ] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

The package itself compiles fine, but running the application gets the following message:
##WARNING:This application can not run correctly because the SQLCipher version of the system (3.13.0) is not aligned with the SQLCipher version embedded in Qt (<IP_ADDRESS>). You should rebuild Qt with the option -system-sqlite.

Could anyone let me know how to handle this?
cc @bbenoist @qknight @ttuegel

@jokogr you might want to check how other applications depending on KDE5 are built, e.g. https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/misc/yakuake/3.0.nix
I imagine it could help.

@FRidh I do believe this issue is more related to Qt5 than KDE5.
Skrooge v2.4.0 relies still in Qt 5.5, because it requires QtWebKit. From the error message I think a new version of sqlite (3.13.0) has appeared and qt55 has not been rebuilt since then, right?
sqlite exists in propagatedBuildInputs of qt55.qtbase and Qt is indeed built against sqlite (from the same file the -system-sqlite flag can be seen).
Is there any reason qt55 is not built against the latest version of sqlite?
P.S. @FRidh Skrooge is indeed part of KDE Extragear, so I guess I could write a more KDE-oriented version (as in using kdeWrapper), let me know if I should do so.

I've noticed that QtWebKit is now available for Qt 5.6 and 5.7, so I swapped qt55.callPackage for the more generic qt5.callPackage.
Skrooge still does not work with Qt 5.7, but it compiles now fine with Qt 5.6. The error message remains, though.
@abbradar since you are also a new maintainer for Qt, do you have any idea why this is happening?
Thanks in advance

https://github.com/NixOS/nixpkgs/commit/3367c211c684c7399609de9f1605ca8a7037bcee fixes this problem for me.

The update of sqlcipher fixed the problem for me, too. Skrooge is now being built and running fine for me. Many thanks to @abbradar for his work.


A few fixes.

cleanup(): fixed package files matching.
checkIso(): switched to the EN-US page for downloading Windows 10 ISO.

Thanks for your contribution.


Migrate IssueStatusEventCell to AttributedStringCell

See #864 for how-to
Requires adding custom drawing for rounded background colors on labels. See:

https://stackoverflow.com/questions/21857408/how-to-set-nsstrings-background-cornerradius-on-ios7
https://stackoverflow.com/questions/16362407/nsattributedstring-background-color-and-rounded-corners

Actually hold on this, these also have icons.

NSTextAttachment @rnystrom? Allows images in attributed text!
Sent with GitHawk

I've always wanted to learn how to use those! Here's an excuse.


Pipeline streaming

Currently, a pipeline is not run until some data has been committed into the input repo.  However, in theory the pipeline can run as soon as any data has been written to the input repo, even before the commit is finished.  The obvious downside is that the pipeline can waste work if the input commit ends up being cancelled.
This can significantly speed up multi-pipeline applications where commits might be large.  Imagine three repos A, B, and C connected by two pipelines A->B and B->C.  Without this feature, B->C won't run until A->B finishes.  With this feature, A->B and B->C can run concurrently where the data sort of "flows" through the pipelines.

One can however argue that, if you care about having a pipeline run as soon as some data comes in, you can just split the input data into many small commits, as opposed to one single large commit.
However, creating many small commits can be unwieldy in many situations.  Sometimes you really just want your data to sit in one single commit, so it's easier to reason about your data.
One alternative solution is to introduce something like a "commit set", which is basically a large commit that composes of many small commits.  Users would use "commit sets" like they use commits today; and commits become more like a unit of streaming data.

At this point we've got a much better understanding of our current semantics and where they break down. I think there's some performance improvements we can make on when we process datums in jobs, but I don't think it's very likely we'll want to process things off of commit boundaries, it would be very difficult with how our code currently works, and it seems like for every case where it improves performance there's another case where it worsens it by processing data that isn't ready to be processed, is going to change, and thus is going to need to be reprocessed.
For those finding this issue, the recommended way to do this is to use granular commits that allow for granular processing and deferred processing to prevent the deleterious performance effects of lots of small commits.


update styles for non-selectable, select date format optins

Description
Update color to #D3DEE3 for non-selectable options in general
Update font-weight specifically for Date Input Format option
Fixes #1635
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

manual

Checklist:

[x] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@rishabhsaxena In the deploy preview, I can see that the font weight has changed for the Date Input Format header, but not for the Date Output Format header. Can you please change the font-weight for both headers?

@mohanarpit Yeah actually I didn't completely get the expected change I suppose, should I hard code the styles for both date format options (input/output) or for the non-selectable options (font-weight and background color)

@mohanarpit Yeah actually I didn't completely get the expected change I suppose, should I hard code the styles for both date format options (input/output) or for the non-selectable options (font-weight and background color)

Yes please. Those are essentially headings and we should differentiate them from the rest of the options.


Possible Shaftesbury / Weymouth error

If I search for Sarah Voss born Dorset in Dorset in FreeCEN2, household in 1841 says place=Shaftesbury but when you open it, civil parish is Weymouth - is that really right? Although the search on FreeCEN1 has Shaftesbury when you Show Household, it says Weymouth on the index result placing the emphasis on Weymouth which is more helpful.

Hi Denise,
Your answer is in the details for the Piece number HO107295.
Look at the National Archives at this link
Piece: HO107/295/16 Place: Shaftesbury -Dorset Enumeration District: 4
Civil Parish: Weymouth Ecclesiastical Parish: Melcombe Regis
Folio: 16 Page: 25
Address: Melcombe Regis East Street
http://discovery.nationalarchives.gov.uk/details/r/C3761028
Then look at the Stats page at this link or in FC2 under manage Pieces.
These are what the PARMS file pick up from the NA
Details for all the Parishs in this PIECE number are below.
https://www.freecen.org.uk/coverage-DOR.html#1841
This is what it says for the 1841 Census.
The Place is Shaftesbury and the Ed names are all those in the Comprising
column below.
These Parishes match up with the NA Page.
In this instance ED 4 is Weymouth,
You will see that is the name at the top left hand corner of the image.
I can send you a copy should you need it.
1841
PiecePlaceComprising
HO107/295 Shaftesbury  Shaston Borough , Holy Trinity S James, Alcester ,
St Peter , Sherborne Town , Sherborne , Overcoombe , Pinford , Wareham ,
Holy Trinity , Stoborough , Middlesbere , Redge , Lady S Mary Within , Lady
S Mary Out , Worgrete , Wargate , St Martin Within , St
It is rather like a jigsaw puzzle. Get all the details together and it
should then all join up.
Hope that helps
Brenda
On Tue, 24 Apr 2018 at 11:33, DeniseColbert<EMAIL_ADDRESS>wrote:

If I search for Sarah Voss born Dorset in Dorset in FreeCEN2, household in
1841 says place=Shaftesbury but when you open it, civil parish is Weymouth

is that really right? Although the search on FreeCEN1 has Shaftesbury
when you Show Household, it says Weymouth on the index result placing the
emphasis on Weymouth which is more helpful.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FreeUKGen/FreeCENMigration/issues/462, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ANC91teMji9FcPl2TvODICz9jenSRMa5ks5trv-DgaJpZM4Thaud
.

@DeniseColbert I don't think there is any action here on our part. However, we can use this as an example in documentation in order to help clarify places/locations over time (maps will help with this).


Bug fix, hidef enrichment term class (for if want to compare to a hidef output file)

It looks good. Merged to dev. Will merge to main after other fixes in hierarchyeval are done.


migrate create and drop schema to QueryProcessor

No issue to close
Description
extracts QueryProcessor from #183 (there it called QueryTransform)
changes create schema and drop schema queries to use new QueryProcessor
Client output
no changes to output

Coverage decreased (-0.1%) to 90.056% when pulling 6b15b1d73296a4418713bffd31fc45b482d83e5d on implement-plan-for-create-drop-schema into d6b2a19e8a8ea3b63a2573cd156e340827fe41d2 on master.


Source map validation warning/errors when using UglifyJsPlugin

The examples I've used are collected into a project for debugging purposes here: https://github.com/OliverJAsh/webpack-uglifyjs-source-map-issue

Given:
// package.json
{
  "private": true,
  "dependencies": {
    "webpack": "^3.6.0"
  }
}

// webpack.config.js
const webpack = require('webpack');

module.exports = {
    devtool: 'source-map',
    entry: {
        main: ['./test.js'],
    },
    output: {
        path: `${__dirname}/target`,
        filename: 'main.js',
    },
    plugins: [
        new webpack.optimize.UglifyJsPlugin({
            sourceMap: true,
        }),
    ],
};

// test.js
import foo from './foo';

foo.bar();

const x = 1;
const y = x + 1;
console.log(y);

// foo.js
module.exports = {
    bar: function () {},
};

When I run webpack and use https://sourcemaps.io/ to validate the source map, I get 83 warnings:

If I switch from using the default import to importing the whole module:
// test.js
import * as foo from './foo';

foo.bar();

const x = 1;
const y = x + 1;
console.log(y);

… and then I validate the source map, I get 1 error and 81 warnings:

If I remove UglifyJsPlugin altogether, the source map has no warnings or errors.
This could be the validator reporting false positives, although I believe I am also seeing issues resolving stack traces against the source map, so I have reason to believe these are not false positives.

@webpack-bot move to webpack-contrib/uglifyjs-webpack-plugin

Hey @webpack-bot still asleep?


Can you add a zooming-in editor for Python Tasks on the workflow page

就像shell节点一样，来个放大的python编辑器

After 1.3.0 is released, it will be added


Updates to Vagrant Ansible role

This updates the Vagrant Ansible role to:

Add a verbose option to Ansible for debugging purposes.
Update the IBM TPM task to specify the new software TPM scripts directory after the directory moved.
Fix formatting issues in Vagrantfile.

@lukehinds I just realized #34 is open that addresses part of what's in this PR. I'll leave it to you on how you want to reconcile the two.


Update validation regex for azurerm_managed_disk

Fixes #129

thanks for your contribution to Cloud Adoption Framework @sbgillett!


Cannot run eval on pretrained models, instructions unclear

Hello,
I am attempting to recreate steps that are documented in order to test this model.
Running the following command that is specified in the documentation:
D:\Projects\SportAnalytics\src\learnable-triangulation-pytorch> python train.py --eval --eval_dataset val --config experiments/human36m/eval/human36m_vol_softmax.yaml --logdir ./logs

Returns the following error:
args: Namespace(config='experiments/human36m/eval/human36m_vol_softmax.yaml', eval=True, eval_dataset='val', local_rank=None, logdir='./logs', seed=42)
Number of available GPUs: 1
Loading pretrained weights from: ./data/pretrained/human36m/pose_resnet_4.5_pixels_human36m.pth
Reiniting final layer filters: module.final_layer.weight
Reiniting final layer biases: module.final_layer.bias
Successfully loaded pretrained weights for backbone
Successfully loaded pretrained weights for whole model
Loading data...
Traceback (most recent call last):
  File "train.py", line 483, in <module>
    main(args)
  File "train.py", line 444, in main
    train_dataloader, val_dataloader, train_sampler = setup_dataloaders(config, distributed_train=is_distributed)
  File "train.py", line 117, in setup_dataloaders
    train_dataloader, val_dataloader, train_sampler = setup_human36m_dataloaders(config, is_train, distributed_train)
  File "train.py", line 65, in setup_human36m_dataloaders
    crop=config.dataset.train.crop if hasattr(config.dataset.train, "crop") else True,
  File "D:\src\learnable-triangulation-pytorch\mvn\datasets\human36m.py", line 70, in __init__
    self.labels = np.load(labels_path, allow_pickle=True).item()
  File "D:\Envs\Pose\lib\site-packages\numpy\lib\npyio.py", line 417, in load
    fid = stack.enter_context(open(os_fspath(file), "rb"))
FileNotFoundError: [Errno 2] No such file or directory: './data/human36m/extra/human36m-multiview-labels-GTbboxes.npy'

This seems odd as I am unable to find the specified file within the shared files on Google Drive to be able to run the model evaluation.
If You have any solutions to this problem please let me know.

Hi, have a look at these instructions. Follow them carefully and you will get that file.

Thank You very much for response @shrubb
I am closing this issue and if I will fail at the verbose instructions I will re-open it or message in it being closed.

@shrubb I have noticed that I am only after testing inference on the pretrained model that was uploaded into Google Drive at this point. But it seems that Your training system is complicated and there is no documentation about how to properly perform inference over media input albeit photos or videos.
Could You provide instructions on how to use the model?
My attempts at loading in the pretrained weights with the following code:
import torch
from mvn.models.triangulation import VolumetricTriangulationNet
from mvn.utils import cfg

config = cfg.load_config("./experiments/human36m/eval/human36m_vol_softmax.yaml")

model = VolumetricTriangulationNet(config)
model.load_state_dict(torch.load("./data/pretrained/human36m/human36m_vol_softmax_10-08-2019/checkpoints/0040/weights.pth"))
model.eval()

Result in the following Error being thrown:
python .\inference.py
Loading pretrained weights from: ./data/pretrained/human36m/pose_resnet_4.5_pixels_human36m.pth
Reiniting final layer filters: module.final_layer.weight
Reiniting final layer biases: module.final_layer.bias
Successfully loaded pretrained weights for backbone
Traceback (most recent call last):
  File ".\inference.py", line 9, in <module>
    model.load_state_dict(torch.load("D:/Projects/SportAnalytics/src/learnable-triangulation-pytorch/data/pretrained/human36m/human36m_vol_softmax_10-08-2019/checkpoints/0040/weights.pth"))
  File "D:\Envs\SportAnalytics\lib\site-packages\torch\nn\modules\module.py", line 1045, in load_state_dict
    self.__class__.__name__, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for VolumetricTriangulationNet:
        Missing key(s) in state_dict: "backbone.conv1.weight", [...]

I have spent a good couple of days trying to figure out how Your code works and if there is a built in way of performing inference on any media file but I can't seem to wrap my head around that @shrubb I would really appreciate if You could support me.

Hi, have you managed to run validation on Human3.6M? I mean the command from the original post, python train.py --eval --eval_dataset val ...
If yes, then check how train.py loads the model (I personally don't know this, never worked with that piece of code) and then do the same in your script. You can check it by, for example, running with python -m pdb instead of python.

@shrubb
I have made an account to access the dataset some time ago but I have not received any information.
So my attempts at validation are currently blocked.
In the meantime I would like to try and run inference on images / video, both monocular and with multiple camera inputs to see the pretrained model in action and to try and export the 3D information out of it.


Tests for throwing URLRequestConvertible

Issue Link :link:
Unit tests for #241
Goals :soccer:
Ensure the library correctly supports throwing URLRequestConvertible requests
Implementation Details :construction:
I've started fixing #241 but then noticed that a fix is already present on master. I already added the tests at that point, so hope these are useful still.

Added corresponding tests for ImageDownloader, UIButton and UIImageView extensions
Minor code refactoring in ImageDownloader to make it easier to understand and make it safer - preventing variable shadowing that can confuse the reader.

Testing Details :mag:
The PR mainly contains new tests for pre-existing functionality, and the minor refactoring in ImageDownloader is covered by existing tests which pass.
There are couple of failing tests which seem to be failing on master too.

Thank you for putting this together! 🍻
I just pushed both sets of changes into master as ba64b1bf and 529ea5b3 while maintaining your attribution. I made a few minor tweaks to the project organization and such. These changes will go out shortly in AFI 4.0.0.
Thanks again!


Create add and remove helper for dom events

Closes issue #22

This PR also removes extra file from example that isn't used in anywere.


I need to add image along with title.

let slices = [ CarnivalWheelSlice.init(title: "Get 10 Unipay Ponits",spinImage:UIImage(named: "jackpot_icon.png")!),
CarnivalWheelSlice.init(title: "Get 10% Off",spinImage:UIImage(named: "jackpot_icon.png")!),
CarnivalWheelSlice.init(title: "Better Luck",spinImage:UIImage(named: "jackpot_icon.png")!),
CarnivalWheelSlice.init(title: "Spin Again",spinImage:UIImage(named: "jackpot_icon.png")!),
CarnivalWheelSlice.init(title: "Get 5 Unipay Points",spinImage:UIImage(named: "jackpot_icon.png")!),
CarnivalWheelSlice.init(title: "Get 5% Off",spinImage:UIImage(named: "jackpot_icon.png")!)]

Hello, please take a look at https://github.com/tapptitude/TTFortuneWheel-iOS/issues/2


Trello now requires a Power-Up?

It seems you can't create an API Key unless you first create a powerup, which needs a site to communicate with. Going to trello.com/app-key will say you need to create a new Power Up. Is this the case with everyone else?

I'm sure that it works, I'm just pointing out that's a bit of work to hookup your Trello to VSCode.
To everyone wanting to do the same, as long as you have some basic .html you can put somewhere for your iframe connector, even if it is an empty page with:

Put that page URL in the iframe connector URL, and you basically got your trello powerup. Then there'll be a https://trello.com/power-ups//edit/api-key, and you can use the API key there to put into this extension. It'll bring you to a page with a large token string, use that for the next popup it shows.
Issues so far:

Cannot click on an issue in WSL.

I've decided with all the hassle it's not really worth it to pursue Trello in VSCode until someone makes a Powerup that everyone can use and just add to their board.

I would love for this to be developed. But sadly I don't have the time or skill either.. :(


move warning to debug

the deploy resource and other internal chef resources trigger this.

this is largely a non-problem since people have been happily using
the deploy resource for years and nobody has showed up in any of our
bugtrackers due to mutating the default hash.  we simply don't need to
annoy people this badly over this.

@chef/client-core @chef/client-maintainers review plz

:+1:

Do we even need it at all? I thought the top-level issue is when you define a default in a LWRP, which is in the scope of the class definition and therefore it is shared between all instances of the class, which is a bad thing, but we now auto-freeze those so the actual problem is fixed. Or am I missing some important detail?

I'm a bit confused as well...

We removed the auto-freeze I thought, pending Chef 13?

I guess we did: https://github.com/chef/chef/pull/3744

But now I'm more confused about how the deploy resource even hits this case. Looking at https://github.com/chef/chef/blob/master/lib/chef/resource/deploy.rb and searching for "default", I don't see anything relevant.

@danielsdeleo looks like its coming from application_ruby not deploy resource directly.

Ok, so based on my understanding of the change history (and memory of a ML thread or bug report that I can't easily find right now):

User did actually report a bug where their LWRP behaved unexpectedly because of mutating defaults set via the LWRP DSL. IIRC this can result in non-error incorrect behavior (i.e., chef does something the user doesn't expect but there isn't necessarily an exception raised).
We tried to "fix" it by freezing defaults
That wasn't a good fix because it broke cases where users hadn't triggered the bad behavior and the messaging about why things broke was unclear and we didn't present a clear alternative.
We got rid of the auto-freeze but there's a warning (I'd say the warning text also could be improved but we'd have to make it longer and the infrastructure to do that well is in-progress but not here yet).

This correct?
My opinion is that a debug message isn't very useful as a response to the bug, we might as well just get rid of the log message and preferably try to find a different way to address it.

I would suggest dup'ing or Marshall.dump/load if we want to try to fix it.  The other solution is just education.  If this happened once its still not very common.

There's no perfect general solution since you can't Marshal IO objects and we can't know if dup is implemented correctly for custom types. We could extend Hash or Array with a module that overrides every mutating method to warn and then calls super. Or we could phase out default and make you write a real method in that case or modify the DSL to require a block or whatever.

Anyway, I'm just in favor of removing the error entirely, rather than dropping to debug. The debug message won't be anywhere near the actual error in time or in the log.

I still think freezing non-proc defaults is a good solution so :-1: on this. We should get people to fix their footgun code.

I think it's wrong that the DSL makes it easy to do the wrong thing and freeze makes it pretty much impossible to give clear error messages with good context, though I did prefer that to letting LWRPs silently have incorrect behavior.

It's definitely not a good solution, but it gives at least some warning that a footgun is being created.

It creates pretty massive spam right now though and the impact is a lot higher than the footgun risk and it is going to be mostly warning when there's absolutely no actually buggy code involved (it warns anytime when the defaults 'could' be mutated, not when the defaults actually are mutated).
Having Chef 13 freeze the defaults would be better, then you'd only get an error if someone really mutated the defaults without needing to change a lot of cookbook code when there's no bug involved, that means waiting until Chef 13 to do anything about this.

I agree on the warning spam, it's worse than the actual problem it's trying to warn you about. I just don't think a debug message does any good, so my preference is to delete lines 811-813 and the corresponding test.

Updated to just remove the warning.

:+1:

What is the rationale for removing this? That we are worried about warning-spam for community cookbooks so it would be non-actionable for most users? This is something we need to find a way to tell users to avoid The Bad Thing™ and just removing it without adding a better notification seems like a step backwards.

I initially advocated for the warning over freezing the attributes.  After introducing the freeze, we saw cookbook breakages that I felt were unfair to inflict on users with a minor release.
The problem with the warnings is that they are often non-actionable.  In addition to community cookbooks, often the warning simply reports that the problem is with #<Class:0x007f81fcc4aad8>.some_property, which might be easily findable in a small system, but is not in a large system even when the user authored most of the cookbooks.
One possibility is to move this to a "deprecation" so that it uses the new rollup feature.  If the caller is reported correctly, that would also help make them more actionable.
I thought about wrapping defaults in some class such as:
require 'forwardable'
class PropertyDefault
  def initialize(data)
    @data = data.freeze
  end

  Object.new.methods.each do |method|
    def_delegator :@data, method
  end

  def method_missing(method, *args, &block)
    @data.send(method, *args, &block)
  rescue RuntimeError => e
    if is_frozen_exception?(e)
      puts "WARNING: You are modifying a blah blah blah this is bad because helpful helpful helpful you should do this this and this"
      @data = @data.dup
      @data.send(method, *args, &block)
      @data.freeze
    else
      raise
    end
  end

  private

  def is_frozen_exception?(e)
    if e.to_s =~ /can't modify frozen/
      true
    else
      false
    end
  end
end

But that is likely to break more code than freezing would because #class will return PropertyDefault still.

For one, the warning is completely indiscriminate. For example, having a default value of a Hash is fine if you always use the resource in a way that sidesteps the bug:
some_lwrp "name" do
  # BAD:
  thing[:foo] = "bar"
  # TOTALLY FINE:
  thing :foo => "bar"
end

Secondly, I agree with the argument here that the cure is worse than the disease. This warning triggers far too often, to the point that it's a usability issue.
Thirdly, I don't think we've done enough work on improving the LWRP attribute/property DSL to warrant a blanket warning for this case. I would like us to design an improved DSL where the easiest thing to do is the right thing before we make everyone change all their LWRPs.
And finally, I think just changing the message from warning to debug makes it pretty much useless. The message will not occur anywhere close to where the bug is exposed, and debug is so verbose that your chances of seeing it and learning that it's the cause of your problem some 1000s of lines of output later are very low.
I do think we should do something to address the mutated-default bug, but we should not have so much collateral damage. Perhaps we could make a WarnOnHashMutation module, with code like:
def []=(*args)
  warn_about_mutations
  super
end

...and extend that into any Hash defaults we get passed (and similar for Array). Or really any other thing that gives you a warning or error with good locality to the actual problem.
Likewise, if we come up with a better property/attribute DSL that doesn't default to doing the wrong thing, then I think it would be fair to deprecate the old thing and encourage everyone to adopt the new thing. I don't know if that's method chaining or something else, but I think property :thing, default: lazy { {} } isn't good enough.

Saying "this really bug doesn't affect you if you happen to avoid it" doesn't mean there isn't a bug. The freezing semantics are currently the accepted RFC-level correct behavior, so warning people about a pending deprecation seems very reasonable. If we want to do something else that should go back through through the RFC process.

That's fine, but this warning as constituted affects everyone who has a LWRP with a Hash or Array default value, not just folks who would get bonked trying to modify a frozen value.

That's always the case with deprecation warnings though. We add them in the hope that either the original author notices or someone bothers them about it.

Also remember we just merged a change so that deprecation warnings are now shown in a de-dup'd summary at the end of the run, so it shouldn't spam output during the converge.

Marking this as 12.5.0 since we should either merge it or close it before shipping, probably up to @thommay at this point.

I agree with Lamont and Dan here; the cure is definitely worse than the disease. @lamont-granquist please go ahead and merge this, but please also spend some time on an RFC that would allow us to detect and warn about this class of problem when we actually encounter them.


HACS UI is not showing up (initial setup)

Version of HACS

0.13.2
Describe the bug
I have tried to install HACS on my HA setup (docker version 0.97.2) based on https://hacs.netlify.com/installation/
but the ui still not showing up on the Community tab no matter version i chose to install.
Screenshot:

Imgur
Debug log

2019-08-18 09:46:20 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-18 09:46:20 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds.
2019-08-18 09:46:20 INFO (MainThread) [homeassistant.setup] Setting up http
2019-08-18 09:46:20 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
2019-08-18 09:46:20 INFO (MainThread) [homeassistant.setup] Setting up system_log
2019-08-18 09:46:20 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2019-08-18 09:46:20 INFO (MainThread) [homeassistant.setup] Setting up recorder
2019-08-18 09:46:20 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.2 seconds.
2019-08-18 09:46:20 INFO (MainThread) [homeassistant.setup] Setting up updater
2019-08-18 09:46:21 INFO (SyncWorker_1) [homeassistant.loader] Loaded yr from homeassistant.components.yr
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up input_select
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up discovery
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain discovery took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up sun
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up met
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain met took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up input_number
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up wake_on_lan
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain wake_on_lan took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up input_text
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up hacs
2019-08-18 09:46:21 INFO (MainThread) [hacs]
-------------------------------------------------------------------
HACS (Home Assistant Community Store)

Version: 0.13.2
This is a custom integration
If you have any issues with this you need to open an issue here:
https://github.com/custom-components/hacs/issues
-------------------------------------------------------------------

2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up input_boolean
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up group
2019-08-18 09:46:21 INFO (SyncWorker_12) [homeassistant.loader] Loaded template from homeassistant.components.template
2019-08-18 09:46:21 INFO (SyncWorker_9) [homeassistant.loader] Loaded webostv from homeassistant.components.webostv
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up zone
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.8 seconds.
2019-08-18 09:46:21 INFO (SyncWorker_15) [homeassistant.loader] Loaded version from homeassistant.components.version
2019-08-18 09:46:21 INFO (SyncWorker_17) [homeassistant.loader] Loaded weather from homeassistant.components.weather
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up webhook
2019-08-18 09:46:21 INFO (SyncWorker_6) [homeassistant.loader] Loaded html5 from homeassistant.components.html5
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up mqtt
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain mqtt took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up config
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up api
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up conversation
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up auth
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds.
2019-08-18 09:46:21 INFO (SyncWorker_19) [homeassistant.loader] Loaded spotify from homeassistant.components.spotify
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up history
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up system_health
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.template
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.template
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.template
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.template
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.template
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.template
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up weather
2019-08-18 09:46:21 INFO (SyncWorker_4) [homeassistant.loader] Loaded scrape from homeassistant.components.scrape
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain weather took 0.0 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up notify
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.1 seconds.
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up media_player
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.components.weather] Setting up weather.met
2019-08-18 09:46:21 INFO (MainThread) [homeassistant.setup] Setting up cloud
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.4 seconds.
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2019-08-18 09:46:22 INFO (SyncWorker_1) [homeassistant.loader] Loaded uptime from homeassistant.components.uptime
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain input_select took 0.9 seconds.
2019-08-18 09:46:22 INFO (SyncWorker_12) [homeassistant.loader] Loaded configurator from homeassistant.components.configurator
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain input_number took 0.8 seconds.
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain input_text took 0.8 seconds.
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain input_boolean took 0.7 seconds.
2019-08-18 09:46:22 INFO (SyncWorker_2) [homeassistant.loader] Loaded pi_hole from homeassistant.components.pi_hole
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setting up configurator
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain configurator took 0.0 seconds.
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.1 seconds.
2019-08-18 09:46:22 INFO (SyncWorker_6) [homeassistant.loader] Loaded dnsip from homeassistant.components.dnsip
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.notify] Setting up notify.webostv
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.webostv
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.spotify
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setting up frontend
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 0.0 seconds.
2019-08-18 09:46:22 INFO (SyncWorker_4) [homeassistant.loader] Loaded snmp from homeassistant.components.snmp
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setting up logbook
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.0 seconds.
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setting up map
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.0 seconds.
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.notify] Setting up notify.html5
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.5 seconds.
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 0.7 seconds.
2019-08-18 09:46:22 INFO (SyncWorker_12) [homeassistant.loader] Loaded systemmonitor from homeassistant.components.systemmonitor
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.9 seconds.
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setup of domain group took 1.1 seconds.
2019-08-18 09:46:22 INFO (SyncWorker_17) [homeassistant.loader] Loaded darksky from homeassistant.components.darksky
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setting up automation
2019-08-18 09:46:22 INFO (SyncWorker_18) [homeassistant.loader] Loaded harmony from homeassistant.components.harmony
2019-08-18 09:46:22 INFO (SyncWorker_14) [homeassistant.loader] Loaded xiaomi_miio from homeassistant.components.xiaomi_miio
2019-08-18 09:46:22 INFO (SyncWorker_10) [homeassistant.loader] Loaded mikrotik from homeassistant.components.mikrotik
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.setup] Setting up light
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.mqtt
2019-08-18 09:46:22 INFO (MainThread) [homeassistant.components.light] Setting up light.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.setup] Setting up sensor
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.setup] Setting up remote
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.setup] Setting up switch
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.setup] Setting up device_tracker
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.uptime
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.template
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.pi_hole
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.dnsip
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.snmp
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.snmp
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.template
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.snmp
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.snmp
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.snmp
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.snmp
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.yr
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.template
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.version
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.systemmonitor
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.scrape
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.darksky
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.template
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.remote] Setting up remote.harmony
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.switch] Setting up switch.xiaomi_miio
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.switch] Setting up switch.xiaomi_miio
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.switch] Setting up switch.xiaomi_miio
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.switch] Setting up switch.xiaomi_miio
2019-08-18 09:46:23 INFO (MainThread) [homeassistant.components.switch] Setting up switch.mqtt
2019-08-18 09:46:24 INFO (MainThread) [homeassistant.components.harmony.remote] Loading Harmony Platform: Media Room at <IP_ADDRESS>:5222, startup activity: None
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.components.xiaomi_miio.switch] Initializing with host <IP_ADDRESS> (token 24867...)
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.components.xiaomi_miio.switch] Initializing with host <IP_ADDRESS> (token e33b7...)
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.components.xiaomi_miio.switch] chuangmi.plug.m1 1.2.4_16 MW300 detected
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.components.xiaomi_miio.switch] Initializing with host <IP_ADDRESS> (token 42142...)
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.components.xiaomi_miio.switch] chuangmi.plug.m1 1.2.4_17 MW300 detected
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.components.xiaomi_miio.switch] Initializing with host <IP_ADDRESS> (token 98c76...)
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.components.xiaomi_miio.switch] chuangmi.plug.m1 1.2.4_17 MW300 detected
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 2.7 seconds.
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.legacy
2019-08-18 09:46:25 INFO (MainThread) [homeassistant.setup] Setup of domain media_player took 3.7 seconds.
2019-08-18 09:46:25 INFO (SyncWorker_3) [homeassistant.components.mikrotik.device_tracker] Connected to Mikrotik 951G-2HnD with IP <IP_ADDRESS>
2019-08-18 09:46:25 INFO (SyncWorker_3) [homeassistant.components.mikrotik.device_tracker] Mikrotik <IP_ADDRESS>: Not a CAPSman controller. Trying local interfaces
2019-08-18 09:46:26 INFO (MainThread) [homeassistant.setup] Setup of domain light took 3.1 seconds.
2019-08-18 09:46:26 INFO (SyncWorker_3) [homeassistant.components.mikrotik.device_tracker] Start polling Mikrotik (<IP_ADDRESS>) router...
2019-08-18 09:46:26 INFO (MainThread) [hole] Response from *hole: 200
2019-08-18 09:46:26 INFO (MainThread) [homeassistant.setup] Setup of domain device_tracker took 3.1 seconds.
2019-08-18 09:46:26 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 3.4 seconds.
2019-08-18 09:46:27 INFO (MainThread) [homeassistant.setup] Setup of domain remote took 3.8 seconds.
2019-08-18 09:46:28 INFO (MainThread) [hacs.repository.integration.custom-components.hacs] Registration complete
2019-08-18 09:46:28 INFO (MainThread) [homeassistant.setup] Setup of domain hacs took 6.9 seconds.
2019-08-18 09:46:28 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.hacs
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.setup] Setup of domain switch took 8.3 seconds.
2019-08-18 09:46:31 INFO (SyncWorker_12) [homeassistant.loader] Loaded ffmpeg from homeassistant.components.ffmpeg
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.setup] Setting up camera
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.setup] Setting up ffmpeg
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.setup] Setup of domain ffmpeg took 0.1 seconds.
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.camera] Setting up camera.ffmpeg
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.camera] Setting up camera.ffmpeg
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.setup] Setup of domain camera took 0.1 seconds.
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 11.32s
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Powered Off
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Youtube started from Hub
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger WebOS turned off by API
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Play Steam Link
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger BIG TV started from Hub
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger WebOS turned on by harmony
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Baby Shark started from Hub
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Watch Youtube
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Netflix started from Hub
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger WebOS turned off by harmony
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Watch BIG TV
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Watch Baby Shark
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Steam Link started from Hub
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger WebOS turned on by API
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Watch Netflix
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Powered off from Hub
2019-08-18 09:46:31 WARNING (MainThread) [homeassistant.components.template.sensor] Could not render template IT Echo Dot Volume, the state is unknown.
2019-08-18 09:46:31 INFO (MainThread) [hacs] Loading known repositories
2019-08-18 09:46:31 INFO (MainThread) [homeassistant.core] Timer:starting
2019-08-18 09:46:33 WARNING (MainThread) [homeassistant.components.http.auth] api_password is going to deprecate. You need to use a bearer token to access /api/stream from <IP_ADDRESS>
2019-08-18 09:46:34 INFO (SyncWorker_0) [homeassistant.loader] Loaded life360 from homeassistant.components.life360
2019-08-18 09:46:34 INFO (SyncWorker_5) [homeassistant.loader] Loaded adguard from homeassistant.components.adguard
2019-08-18 09:46:34 INFO (SyncWorker_18) [homeassistant.loader] Loaded toon from homeassistant.components.toon
2019-08-18 09:46:34 INFO (SyncWorker_7) [homeassistant.loader] Loaded notion from homeassistant.components.notion
2019-08-18 09:46:34 INFO (SyncWorker_12) [homeassistant.loader] Loaded hangouts from homeassistant.components.hangouts
2019-08-18 09:46:34 INFO (SyncWorker_19) [homeassistant.loader] Loaded ios from homeassistant.components.ios
2019-08-18 09:46:34 INFO (SyncWorker_16) [homeassistant.loader] Loaded heos from homeassistant.components.heos
2019-08-18 09:46:34 INFO (SyncWorker_14) [homeassistant.loader] Loaded iqvia from homeassistant.components.iqvia
2019-08-18 09:46:34 INFO (SyncWorker_1) [homeassistant.loader] Loaded upnp from homeassistant.components.upnp
2019-08-18 09:46:34 INFO (SyncWorker_9) [homeassistant.loader] Loaded zwave from homeassistant.components.zwave
2019-08-18 09:46:34 INFO (SyncWorker_8) [homeassistant.loader] Loaded homematicip_cloud from homeassistant.components.homematicip_cloud
2019-08-18 09:46:34 INFO (SyncWorker_5) [homeassistant.loader] Loaded ps4 from homeassistant.components.ps4
2019-08-18 09:46:34 INFO (SyncWorker_18) [homeassistant.loader] Loaded zha from homeassistant.components.zha
2019-08-18 09:46:34 INFO (SyncWorker_7) [homeassistant.loader] Loaded esphome from homeassistant.components.esphome
2019-08-18 09:46:34 INFO (SyncWorker_12) [homeassistant.loader] Loaded gpslogger from homeassistant.components.gpslogger
2019-08-18 09:46:34 INFO (SyncWorker_19) [homeassistant.loader] Loaded ifttt from homeassistant.components.ifttt
2019-08-18 09:46:34 INFO (SyncWorker_16) [homeassistant.loader] Loaded axis from homeassistant.components.axis
2019-08-18 09:46:34 INFO (SyncWorker_14) [homeassistant.loader] Loaded ipma from homeassistant.components.ipma
2019-08-18 09:46:34 INFO (SyncWorker_1) [homeassistant.loader] Loaded sonos from homeassistant.components.sonos
2019-08-18 09:46:34 INFO (SyncWorker_9) [homeassistant.loader] Loaded vesync from homeassistant.components.vesync
2019-08-18 09:46:34 INFO (SyncWorker_8) [homeassistant.loader] Loaded logi_circle from homeassistant.components.logi_circle
2019-08-18 09:46:34 INFO (SyncWorker_5) [homeassistant.loader] Loaded tellduslive from homeassistant.components.tellduslive
2019-08-18 09:46:34 INFO (SyncWorker_18) [homeassistant.loader] Loaded mobile_app from homeassistant.components.mobile_app
2019-08-18 09:46:34 INFO (SyncWorker_7) [homeassistant.loader] Loaded smhi from homeassistant.components.smhi
2019-08-18 09:46:34 INFO (SyncWorker_12) [homeassistant.loader] Loaded ambiclimate from homeassistant.components.ambiclimate
2019-08-18 09:46:34 INFO (SyncWorker_19) [homeassistant.loader] Loaded daikin from homeassistant.components.daikin
2019-08-18 09:46:34 INFO (SyncWorker_16) [homeassistant.loader] Loaded locative from homeassistant.components.locative
2019-08-18 09:46:34 INFO (SyncWorker_14) [homeassistant.loader] Loaded somfy from homeassistant.components.somfy
2019-08-18 09:46:34 INFO (SyncWorker_1) [homeassistant.loader] Loaded tplink from homeassistant.components.tplink
2019-08-18 09:46:34 INFO (SyncWorker_9) [homeassistant.loader] Loaded smartthings from homeassistant.components.smartthings
2019-08-18 09:46:34 INFO (SyncWorker_8) [homeassistant.loader] Loaded tradfri from homeassistant.components.tradfri
2019-08-18 09:46:34 INFO (SyncWorker_5) [homeassistant.loader] Loaded openuv from homeassistant.components.openuv
2019-08-18 09:46:34 INFO (SyncWorker_18) [homeassistant.loader] Loaded emulated_roku from homeassistant.components.emulated_roku
2019-08-18 09:46:34 INFO (SyncWorker_7) [homeassistant.loader] Loaded mailgun from homeassistant.components.mailgun
2019-08-18 09:46:34 INFO (SyncWorker_2) [homeassistant.loader] Loaded simplisafe from homeassistant.components.simplisafe
2019-08-18 09:46:34 INFO (SyncWorker_19) [homeassistant.loader] Loaded nest from homeassistant.components.nest
2019-08-18 09:46:34 INFO (SyncWorker_16) [homeassistant.loader] Loaded rainmachine from homeassistant.components.rainmachine
2019-08-18 09:46:34 INFO (SyncWorker_14) [homeassistant.loader] Loaded wemo from homeassistant.components.wemo
2019-08-18 09:46:34 INFO (SyncWorker_10) [homeassistant.loader] Loaded wwlln from homeassistant.components.wwlln
2019-08-18 09:46:34 INFO (SyncWorker_9) [homeassistant.loader] Loaded luftdaten from homeassistant.components.luftdaten
2019-08-18 09:46:34 INFO (SyncWorker_8) [homeassistant.loader] Loaded velbus from homeassistant.components.velbus
2019-08-18 09:46:34 INFO (SyncWorker_15) [homeassistant.loader] Loaded homekit_controller from homeassistant.components.homekit_controller
2019-08-18 09:46:34 INFO (SyncWorker_18) [homeassistant.loader] Loaded ambient_station from homeassistant.components.ambient_station
2019-08-18 09:46:34 INFO (SyncWorker_7) [homeassistant.loader] Loaded unifi from homeassistant.components.unifi
2019-08-18 09:46:34 INFO (SyncWorker_2) [homeassistant.loader] Loaded hue from homeassistant.components.hue
2019-08-18 09:46:34 INFO (SyncWorker_19) [homeassistant.loader] Loaded plaato from homeassistant.components.plaato
2019-08-18 09:46:34 INFO (SyncWorker_16) [homeassistant.loader] Loaded twentemilieu from homeassistant.components.twentemilieu
2019-08-18 09:46:34 INFO (SyncWorker_14) [homeassistant.loader] Loaded twilio from homeassistant.components.twilio
2019-08-18 09:46:34 INFO (SyncWorker_10) [homeassistant.loader] Loaded geofency from homeassistant.components.geofency
2019-08-18 09:46:34 INFO (SyncWorker_9) [homeassistant.loader] Loaded owntracks from homeassistant.components.owntracks
2019-08-18 09:46:34 INFO (SyncWorker_8) [homeassistant.loader] Loaded cast from homeassistant.components.cast
2019-08-18 09:46:34 INFO (SyncWorker_15) [homeassistant.loader] Loaded deconz from homeassistant.components.deconz
2019-08-18 09:46:34 INFO (SyncWorker_18) [homeassistant.loader] Loaded lifx from homeassistant.components.lifx
2019-08-18 09:46:34 INFO (SyncWorker_13) [homeassistant.loader] Loaded dialogflow from homeassistant.components.dialogflow
2019-08-18 09:46:34 INFO (SyncWorker_2) [homeassistant.loader] Loaded point from homeassistant.components.point
2019-08-18 09:46:39 INFO (MainThread) [hacs.repository.integration.DSorlov.hasl-platform] Registration complete
2019-08-18 09:46:43 INFO (MainThread) [hacs.repository.integration.StyraHem.ShellyForHASS] Registration complete
2019-08-18 09:46:47 INFO (MainThread) [hacs.repository.integration.isabellaalstrom.sensor.krisinformation] Registration complete
2019-08-18 09:46:50 INFO (MainThread) [hacs.repository.integration.JurajNyiri.HomeAssistant-Tavos] Registration complete
2019-08-18 09:46:54 INFO (MainThread) [hacs.repository.integration.JurajNyiri.HomeAssistant-Atrea] Registration complete
2019-08-18 09:46:58 INFO (MainThread) [hacs.repository.integration.JurajNyiri.HomeAssistant-qBitTorrentAlternativeSpeed] Registration complete
2019-08-18 09:47:01 INFO (MainThread) [hacs.repository.integration.TimSoethout.goodwe-sems-home-assistant] Registration complete
2019-08-18 09:47:05 INFO (MainThread) [hacs.repository.integration.bramkragten.lyric] Registration complete
2019-08-18 09:47:09 INFO (MainThread) [hacs.repository.integration.bramkragten.mind] Registration complete
2019-08-18 09:47:13 INFO (MainThread) [hacs.repository.integration.bouwew.sems2mqtt] Registration complete
2019-08-18 09:47:17 INFO (MainThread) [hacs.repository.integration.akasma74.Hass-Custom-Alarm] Registration complete
2019-08-18 09:47:21 INFO (MainThread) [hacs.repository.integration.keatontaylor.alexa_media_player] Registration complete
2019-08-18 09:47:25 INFO (MainThread) [hacs.repository.integration.albertogeniola.meross-homeassistant] Registration complete
2019-08-18 09:47:30 INFO (MainThread) [hacs.repository.integration.mudape.iphonedetect] Registration complete
2019-08-18 09:47:33 INFO (MainThread) [hacs.repository.integration.bertbert72.HomeAssistant_VirginTivo] Registration complete
2019-08-18 09:47:37 INFO (MainThread) [hacs.repository.integration.nstrelow.ha_philips_android_tv] Registration complete
2019-08-18 09:47:41 INFO (MainThread) [hacs.repository.integration.rsnodgrass.hass-integrations] Registration complete
2019-08-18 09:47:45 INFO (MainThread) [hacs.repository.integration.Ceerbeerus.beerbolaget] Registration complete
2019-08-18 09:47:48 INFO (MainThread) [hacs.repository.integration.thomasloven.hass-browser_mod] Registration complete
2019-08-18 09:47:52 INFO (MainThread) [hacs.repository.integration.thomasloven.hass-lovelace_gen] Registration complete
2019-08-18 09:47:56 INFO (MainThread) [hacs.repository.integration.thomasloven.hass-favicon] Registration complete
2019-08-18 09:47:59 INFO (MainThread) [hacs.repository.integration.claytonjn.hass-circadian_lighting] Registration complete

...

Since it looks like it's working my guess is that you are using Traefik.
if so have, a look here https://github.com/custom-components/hacs/issues/87#issuecomment-502389153

That is!
I have to set traefik.frontend.headers.frameDeny=false in my traefik configuration
Now it's working fine


Add term simplification to Python bindings

This PR exposes the concrete term simplification routines already used by the booster to the Python bindings so that they can be called from Pyk. Specifically, it adds two free functions to the runtime module:
simplify_pattern(Pattern, Sort) -> Pattern
simplify_bool_pattern(Pattern) -> bool

These are exposed as free functions because they depend on the runtime library and so can't be automatically bound to the Pattern class as methods; I suggest Pyk probably wants to monkey-patch them into its Pattern class along with some kind of dynamic check for whether the runtime module has been loaded or not.
Previously, the C and Python bindings didn't share a great deal of code; the simplification routine is the first bit of non-trivial behaviour that they need to share. I have therefore started a reorganisation of the bindings code to extract as much functionality to a common library, which has the additional benefit of reducing the amount of memory-leak prone handling of C wrapper structures. To keep the diff in this PR reasonable I have not completed this migration, but this is future work that I will complete in a future PR.
A summary of the changes in this PR is as follows:

Build a common bindings library that the C and Python bindings link against.
Extract the minimal set of features from the existing C bindings that the Python bindings require to perform term simplification, and port the C bindings over to calling the extracted common features.
Add a test case to the Python bindings test suite that performs a few small simplifications of sort Int and Bool; these are really just smoke tests and Pyk should test the feature more thoroughly.

I have also tested the booster's integration tests with this change applied and there is no breakage to the C bindings.


grpcproxy: fix deadlock in watchbroadcast

Calling empty() in watchbroadcast methods was trying to
lock the rwmutex when it was already held.
Fixes #6937

lgtm

semaphore failure unrelated; merging


[Feature] Add numbers

I discovered this keyboard on f-droid and I've been using it. As far as I know it isn't posible to input numbers
I think it's obvious that inputting numbers should be vital and by looking at the code I have not found how to input them either

Ok, i didn't read all the README

it could be nice to put the extra numbers and characters in their own similar circle layout

Another circle make the board crowded and also 'number' are pretty evenly distributed, on the axis of frequency. no point to optimize it on 8vim style keypad.
pressing the left sector should take you to numberpad.

I actually meant to have numbers and perhaps other special symbols in their own circle , which will appear right after hitting the extra keys button which right now show them in a normal keyboard layout... we need a solid interface ;)


codimd: fix option configuration.saml.idpCert

Fixes the wrong capitalization of idPCert -> idpCert
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: codimd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: codimd
Partial log (click to expand)
copying path '/nix/store/7laim5vvzxf0c873504mghwxfwvj7apy-qtsensors-5.11.1-bin' from 'https://cache.nixos.org'...
copying path '/nix/store/7m88x1wmbac1xkjqy0xllqxx2p01bmci-qtwebchannel-5.11.1-bin' from 'https://cache.nixos.org'...
copying path '/nix/store/ycfqzy6sabjzngf357rx48ixdz2cr09l-qtlocation-5.11.1-bin' from 'https://cache.nixos.org'...
copying path '/nix/store/g688pxl866vzrxzp3ir473a75wiiv96m-qtwebkit-5.212-alpha-01-26-2018' from 'https://cache.nixos.org'...
copying path '/nix/store/jla9rijan0bf452pwgxqw29a2wavfw0l-phantomjs-2.1.1' from 'https://cache.nixos.org'...
copying path '/nix/store/rcmqqf1d799ampi5mcp47ah4rkxg32dm-node-js-url-2.3.0' from 'https://cache.nixos.org'...
copying path '/nix/store/za8l47pl8n9m01dpsifkglq6fddcrw2d-node-markdown-pdf-8.1.1' from 'https://cache.nixos.org'...
copying path '/nix/store/wf06y2v4w91jz08j7ipzg7x7nkb9pv50-codimd-env' from 'https://cache.nixos.org'...
copying path '/nix/store/1rx39c3k2kaz4zqjkxjb9yw54vvbzyia-codimd-1.2.0' from 'https://cache.nixos.org'...
/nix/store/1rx39c3k2kaz4zqjkxjb9yw54vvbzyia-codimd-1.2.0

Timed out, unknown build status on aarch64-linux (full log)
Attempted: codimd
Partial log (click to expand)
[ 71%] Building CXX object Source/WebCore/CMakeFiles/WebCore.dir/__/__/DerivedSources/WebCore/JSCSSStyleRule.cpp.o
building of '/nix/store/w2mi5hdppz7wn93gc066x6ddclfpdwxa-qtwebkit-5.212-alpha-01-26-2018.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/2pg7fy6xnklvpjkg28b3d3c41cdqj8x9-phantomjs-2.1.1.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/pvcrjh7kdc3kzaqb8ikvyn1w1xhi0dvc-node-js-url-2.3.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/21d5dpd5477imp7s9jqcv98gj9q7w2mn-node-markdown-pdf-8.1.1.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/k7d8sc8znscdjs67whyxqfvk2ymlb1ra-node-phantomjs-prebuilt-2.1.16.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/c2myb3s41d5hgnhm3idiivl67n2v3wq5-codemirror-hackmdio-05-07-2018.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/p3hyh0gmn1sfmfsl66076d7wmzm84vrz-codimd-env.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/6lqb5775z74yyri49119i9qnaf5pv6b6-codimd-1.2.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/6lqb5775z74yyri49119i9qnaf5pv6b6-codimd-1.2.0.drv' failed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: codimd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: codimd
Partial log (click to expand)
copying path '/nix/store/7laim5vvzxf0c873504mghwxfwvj7apy-qtsensors-5.11.1-bin' from 'https://nix-cache.s3.amazonaws.com'...
copying path '/nix/store/ycfqzy6sabjzngf357rx48ixdz2cr09l-qtlocation-5.11.1-bin' from 'https://nix-cache.s3.amazonaws.com'...
copying path '/nix/store/7m88x1wmbac1xkjqy0xllqxx2p01bmci-qtwebchannel-5.11.1-bin' from 'https://nix-cache.s3.amazonaws.com'...
copying path '/nix/store/g688pxl866vzrxzp3ir473a75wiiv96m-qtwebkit-5.212-alpha-01-26-2018' from 'https://nix-cache.s3.amazonaws.com'...
copying path '/nix/store/jla9rijan0bf452pwgxqw29a2wavfw0l-phantomjs-2.1.1' from 'https://nix-cache.s3.amazonaws.com'...
copying path '/nix/store/rcmqqf1d799ampi5mcp47ah4rkxg32dm-node-js-url-2.3.0' from 'https://nix-cache.s3.amazonaws.com'...
copying path '/nix/store/za8l47pl8n9m01dpsifkglq6fddcrw2d-node-markdown-pdf-8.1.1' from 'https://nix-cache.s3.amazonaws.com'...
copying path '/nix/store/wf06y2v4w91jz08j7ipzg7x7nkb9pv50-codimd-env' from 'https://nix-cache.s3.amazonaws.com'...
copying path '/nix/store/1rx39c3k2kaz4zqjkxjb9yw54vvbzyia-codimd-1.2.0' from 'https://nix-cache.s3.amazonaws.com'...
/nix/store/1rx39c3k2kaz4zqjkxjb9yw54vvbzyia-codimd-1.2.0

Timed out, unknown build status on aarch64-linux (full log)
Attempted: codimd
Partial log (click to expand)
[ 68%] Building CXX object Source/WebCore/CMakeFiles/WebCore.dir/__/__/DerivedSources/WebCore/JSMediaStream.cpp.o
building of '/nix/store/w2mi5hdppz7wn93gc066x6ddclfpdwxa-qtwebkit-5.212-alpha-01-26-2018.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/2pg7fy6xnklvpjkg28b3d3c41cdqj8x9-phantomjs-2.1.1.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/pvcrjh7kdc3kzaqb8ikvyn1w1xhi0dvc-node-js-url-2.3.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/21d5dpd5477imp7s9jqcv98gj9q7w2mn-node-markdown-pdf-8.1.1.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/k7d8sc8znscdjs67whyxqfvk2ymlb1ra-node-phantomjs-prebuilt-2.1.16.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/c2myb3s41d5hgnhm3idiivl67n2v3wq5-codemirror-hackmdio-05-07-2018.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/p3hyh0gmn1sfmfsl66076d7wmzm84vrz-codimd-env.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/6lqb5775z74yyri49119i9qnaf5pv6b6-codimd-1.2.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/6lqb5775z74yyri49119i9qnaf5pv6b6-codimd-1.2.0.drv' failed


busthead, decence (logical-conflict)

This pull request was generated by the 'mq' tool

/trunk merge


Storage based on LMDB database

I managed to create database adapter based on insanely fast key-value store - LMDB. I open sourced it under https://github.com/Nekromancer/SoundFingerprinting.LMDB
It would be great if you could take a look at code and provide any feedback about it.
And if you like it - maybe you could link that in your README? :)
PS. I hope you don't mind - i took some of your integration tests to test out storage.

If you took some of his tests then you need to carry over his copyright declaration in those tests.

Thanks @Nekromancer! Will take a look at this later. I don't me you taking the integration tests. Actually, since there are 3 storages now, I was thinking about releasing a separate DLL just for that.

Yes, that would be great :)

It's used by the SoundTools https://github.com/AddictedCS/soundfingerprinting.soundtools. It's an internal helper project, built to provide means for analyzing the audio content, fingerprints structure and so on. It's not used by the main framework.

Have you considered moving InMemoryStorage out of main library? That would get rid of protobuf dependency, which imho isn't nessesary

Hey @Nekromancer, I’ve reviewed the LMDB and here are my thoughts:

Please re-publish the LMDB under SoundFingerprinting.Extensions.LMDB name. SoundFingerprinting.* prefix is reserved under my NuGet identity name, thus the community expecting me as the author. All extensions written by contributors should be published under SoundFingerprinting.Extensions.* prefix.
Please, un-list all current SoundFingerprting.LMDB versions, to remove confusion with newly published SoundFingerprinting.Extensions.LMDB.
Consider starting with version 5.2.2.x similar to how other extensions are published. This will make the versioning look consistent, as all extensions are dependent on the core library which drives the version updates.
You can still upload new versions of LMDB just by updating the last minor version i.e. 5.2.2.x.
In terms of the performance, 50 tracks is not really a use case that I’ve found frequently used. Users normally have at least 500, 1000, thus it would be more interesting to find how the performance looks when this number increases: 50, 100, 500, 1000 will provide a better overview of the dynamics.
In case if your target audience is specifically those who need to monitor low number of tracks, you can specify it in the docs.
Internal modifier for TrackData will stay as it is right now. The whole concept of it getting internally modified was not the best choice I’ve made at a time. There will be changes in the interfaces in the upcoming 6.x version, which will not require any internal modifications.

Hey @AddictedCS , thanks for the review.
I will re-publish NuGet to meet these requirements.
As far as performance goes - right know i'm using this adapter with 3000 ads (so audio samples are usually very small) and 10-20% performance loss (comparing to InMemoryStorage) is still valid in this use case. It would be great it somebody could try this out on larger data set.


Laravel Pagination

Is it possible to Paginate Laravel Paginate feature with vue2-datatable ? my return view like following i would like to paginate this with this plugin ..
{
  "current_page": 1,
  "data": [
  {
    "id": 1,
    "bill": "62753",
    "type": 3,
    "amount": 58,
    "price": 107,
    "date": "2018-06-09",
    "stock": 0,
    "created_at": null,
    "updated_at": null
  },
  {
    "id": 2,
    "bill": "97246",
    "type": 5,
    "amount": 150,
    "price": 118,
    "date": "2018-05-28",
    "stock": 1,
    "created_at": null,
    "updated_at": null
  }],
  "first_page_url": "http://site.test/purchases/get/list?page=1",
  "from": 1,
  "last_page": 25,
  "last_page_url": "http://site.test/purchases/get/list?page=25",
  "next_page_url": "http://site.test/purchases/get/list?page=2",
  "path": "http://site.test/purchases/get/list",
  "per_page": 2,
  "prev_page_url": null,
  "to": 2,
  "total": 49
}

just write some convert function

query = { limit: 10, offset: 0, sort: '', order: '' } by default

@kenberkeley any suggestions ? or documentation for custom pagination urls for now total is working fine. its kinda server side pagination

according to the return view you provided, query.limit is per_page which is 2, query.offset is (current_page - 1) * per_page which is 0, total is 49

that's fine but what about processing with next previous pages ?

define next previous pages

And how I can filter data on server side?

that's your business logic, pal

@kenberkeley i'm confused about defining next previous pages can you show me documentation url or example here ?

@joeljerushan : that's fine but what about processing with next previous pages ?
so i was confused what is next previous pages

i was talking about "next_page_url": "http://site.test/purchases/get/list?page=2", server side processing to get next set of data and previous set of data.
Hope you understand

control everything on the front end might be better

https://github.com/OneWayTech/vue2-datatable/blob/master/examples/src/_mockData/index.js

i understood ! but what if we get large set of data :) that will take time to load json object right

so you got to make the pagination

https://github.com/OneWayTech/vue2-datatable/issues/129#issuecomment-397866757

Thank you :) link you posted helped me ;)

Hi,
It seems that I cannot get the vue2-datatable pagination links working properly.
I'm a vue newbie and literally stucked on this test project since weeks... I cannot understand if it depends on vue or laravel side.
I'm sending to the rest api call these parameters:
methods: {
    getIncarichi() {
        axios.get("api/incarico2", {
            params: {
                limit: this.query.limit,
                offset: this.query.offset,
                sort: this.query.sort,
                order: this.query.order,
            }
        })
            .then(response => {
                this.data = response.data.data;
                this.total = response.data.total;
            })
            .catch(error => {
                console.log(error);
            });
    }
},

But the paginator is always setting up the page 1 response.
This is laravel code
public function index2(Request $request)
{
    $data = $this->model->getModel()
        ->orderBy($request->sort, $request->order)
        ->paginate($request->limit);
    return response()->json($data);
}

Example:
Clicking on the links (page 2 in this case) is always returning page 1 results using server-side laravel LengthAwarePaginator

Here is the debug screenshot of $data object been builted

And the table isn't refreshed.
(Sorting and filtering are working correctly).
Could please someone point to the right direction?
Thank you,
Alex


tab key skips selectpicker inputs

Safari 6.1.1, Mac: using the tab key ignores (skips) all .selectpicker inputs.  Works fine in Firefox 27 and Chrome 32.  To test, try using the tab key in the bootstrap-select demo in Safari.

Same here. Still valid on Safari 8.0 on Mac Yosemite

Still an issue here

Still an issue on Safari (9.1). Also on Safari Tech Preview (9.1.1).

I had the same issue, and it seems you need to enable tab access in Safari as described here.

@jchernan But we can't rely on users having this enabled. Furthermore, tab works just fine in Safari for regular form fields.
Has anyone found a better workaround?

Released in v1.13.17!


[Doc] link for  TLS Authentication on Proxies is dead

Expected behavior
Show a page / Enabling TLS Authentication on Proxies
Actual behavior
404
Steps to reproduce
1、Open https://pulsar.apache.org/docs/zh-CN/security-authorization/
2、Click a link for  Enabling TLS Authentication on Proxies

@Anonymitaet Thank you for solving my problem

@Anonymitaet @wangyunpeng666 Have you solved the issue?

@Jennifer88huang not yet, I'll fix when I'm available.

@Jennifer88huang could you please help tag help-wanted?

@Anonymitaet We can add help-wanted tag. If the link affects user experience, and no contributors fix it within two days, we need to fix it promptly.

what is the target page for "Enabling TLS Authentication on Proxies"？ can you give the target link?

@wangyunpeng666  what is the target page for "Enabling TLS Authentication on Proxies"？ can you give the target link?

@wangyunpeng666 what is the target page for "Enabling TLS Authentication on Proxies"？ can you give the target link?
I am a technical writer and try to fix the doc issue.

https://pulsar.apache.org/docs/zh-CN/security-authorization/security-tls-authentication#on-proxies

@wangyunpeng666 what is the target page for "Enabling TLS Authentication on Proxies"？ can you give the target link?
I am a technical writer and try to fix the doc issue.

https://pulsar.apache.org/docs/zh-CN/security-authorization/security-tls-authentication#on-proxies

@belinda-wong The following image will help you to resolve the issue.

You need to update it as "see "Enable TLS Authentication on Proxies"". After you update, you can run website locally and verify the change.


docs(web-components): storybook edit and add docs floating modal

Adding richer documentation to Floating modal component
Description
Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots:
Before (If applicable):

After:

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation update
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

TEST


Share Text to Discord when in Reading Mode as well as Edit Mode

Is your feature request related to a problem? Please describe.
Not a problem.  It would be just as convenient to be able to share text when in reading mode as it is in edit mode.  Many times I have text prepared ahead of time and it would be nice to just be able to select it and share it, rather than put the note in edit mode, then highlight and share.
Describe the solution you'd like
Share text in reading mode just like I can when it is in edit mode.
Describe alternatives you've considered
Alternative is just another step, put the note in edit mode and then share the text.
Additional context
This is just a matter of convenience more than anything else, but it would certainly be helpful.

Excellent request. Last I'd looked, the editor was just more accessible within their API. But I'd love to add this feature so I'll revisit some potential solutions soon.

Thanks Kirk!
On Sun, Apr 28, 2024, 5:52 PM Kirk Wiebe @.***> wrote:

Excellent request. Last I'd looked, the editor was just more accessible
within their API. But I'd love to add this feature so I'll revisit some
potential solutions soon.
—
Reply to this email directly, view it on GitHub
https://github.com/phd20/obsidian-discord-share/issues/32#issuecomment-2081686474,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL3WPIZCDNCJRD367EIUURTY7V4S7AVCNFSM6AAAAABG5HPJ4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGY4DMNBXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>