Mqtt cover modifications

Description:
Making command topic optional so a tilt-only cover doesn't show up/down controls
Adding ability to set up/down position including ability to template the value
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#2729
**also has modifications for polymer project - PR not ready yet
Example entry for configuration.yaml (if applicable):
cover:
  - platform: mqtt,
    name: test,
    state_topic: 'state-topic',
    command_topic: 'command-topic',
    set_position_topic: 'position-topic',
    set_position_template: '{{100-62}}',
    payload_open: 'OPEN',
    payload_close: 'CLOSE',
    payload_stop: 'STOP'

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Hey @balloob. Sorry for the direct tag. Anyway this can make it into 0.46? Would be clutch to have it out in the next release cycle. Me and @cribbstechnologies worked through the bugs/my typos and I'm good to share my project soon.

Will it be possible to set the position with a customized json payload, e.g. like:
set_position_template: '{"covers": [1,2],"position" : value.position}'
where "value.position" gets substituted with the target position and then the complete json object is sent by mqtt?

I think I reverted it. Let me know if I didn't do it right.
On Wed, May 31, 2017 at 11:19 AM, Adam Mills<EMAIL_ADDRESS>wrote:

@armills approved this pull request.
LGTM, except the polymer submodule update needs to be removed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/7841#pullrequestreview-41262917,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABjyfUX-fCr8LZxR7wiY6ie6aMdLI1m0ks5r_YUXgaJpZM4Nq626
.

@armills if you approve, you can merge it too in the future 👍
Sorry, didn't make 0.46 as I am not really paying attention to notifications anymore (too many).

No worries! I'm trying out a new 12v stepper right now since I have the extra time.  Should be a good video once I have everything ready. Thanks much for everyone's work getting the MQTT tilt component integrated!

Untill it gets into the released version, will it then be enough to copy the modified cover/mqtt.py file into the custom component library?

Will cherry-pick it for 0.46.1

Can anyone guide me in the right direction setting this mqtt cover up.
My cover supports different positions between 0-100 percent - the  topic is given, but the payload is a json object, where the parameter is part of, e.g.:
{"covers": [1,2],"position" : 50}
How is this done, using the latest template feature?


NetDevPack and total refactoring

NetDevPack installed, saving hundreds of repetitive line codes.

NetDevPack installed, saving hundreds of repetitive line codes.


I got an error when i npm install in nodegit on windows10,please help me !

nodegit is 0.21.2

I don't know why, but it tries to compile instead of downloading a prebuilt binary for Windows 10 x32 for me. This is so disturbing. 😩

I was having problems getting Nodegit to build from source as well with Windows 10, particularly with gyp errors. This is what worked for me, let me know if it solves things for you.
Steps

Install latest Python 2. Make sure you set the env variable. With Windows 10, I went to Settings -> About -> System Info -> Advanced system settings -> Environment Variables... -> Clicked New... for System variables -> and added PYTHON as the variable, and C:\Python27\python.exe for the path (where I installed Python). Your path will be wherever you installed Python on your system.
Go to nodejs/node-gyp and scroll down to the Installation section of the README. Install with npm:
$ npm install -g node-gyp
Go to the Windows Section and do Option 1. You'll need to open PowerShell (like I did) or CMD.exe (run as Administrator). Install Microsoft's windows-build-tools using npm install --global --production windows-build-tools.

Immediately after these steps were completed, I ran npm install again in the nodegit directory. It completed successfully with no node-gyp errors. Hope this helps!

I am seeing prebuilt download disabled in your logs
Do you have the environment variable BUILD_ONLY set? That would cause this.


Add parallel_tests support.

I like the idea and the PR - it just shouldn't be necessary to not be able to use the existing :cmd and :cmd_additional_args options.
Here are my issues with this:
1. the need to handle option quoting in parallel_tests
I opened an issue here:
https://github.com/grosser/parallel_tests/issues/402
A PR would probably help there. I could merge this as is, but improving parallel_tests is a much better option
2. the :cmd, :cmd_additional_args options and passing parameters to :run_all should be better documented in the README - you have a very good use case to demonstrate this
3. guard-rspec should be flexible enough to handle any command
Just like it does for spring, guard-rspec, etc. I don't think parallel_rspec should be an exception if we can avoid it. This is especially because I don't want to break this when I get to processing output later (upcoming streaming formatters).
Otherwise, it's a very, very nice PR.

I just realized the following works (notice where the ' marks are):
rspec_options = {
  cmd: "bundle exec rspec",
  run_all: {
    cmd: "bundle exec parallel_rspec -o '",
    cmd_additional_args: "'"
  }
}
guard :rspec, rspec_options do
# (...)

So I'll add this as an example to the README and I'm closing this - let me know if I've missed something.
Thanks for bringing this up!


The published version of react-static-plugin-sass on npm is causing problems on projects using Node 16

When installing the plugin react-static-plugin-sass, I get the following error:
error: 'remove_cv_t' is not a member of 'std'; did you mean 'remove_cv'?

This can be traced back to the now deprecated node-sass package which is a dependency of the npm published version of the aforementioned plugin.
I see there was a PR (https://github.com/react-static/react-static/pull/1621) which would solve this issue had it been published to npm, I left the following comment on the PR as well:
@deiga @SleeplessByte I think you guys forgot to release a new version of this plugin. It is still on 7.3.0 (which was released a year ago on npm). I was trying to use react-static-plugin-sass on a project under Node 16 but it breaks due to a problem on the old version of node-sass that the published version of react-static-plugin-sass depends on.
Originally posted by @jeanlescure in https://github.com/react-static/react-static/issues/1621#issuecomment-888769289

I also see that the root version of react-static is ahead of the version in npm. It seems that even though the build passed on Travis CI and the changes have been promoted to master, there has been no publish of the packages.
Any project using Node 16, depending on SASS support, and looking to adopt react-static will meet the same error I described. Is there anything else that needs to happen before publishing?

I just noticed 7.6.0 is out so I think we can close this issue.


Moved partial shims to separate module that can be included at-will

Instead of completely removing the partial shims, this pull request moves them to a separate module. The functions this module defines can then be added to Object if a developer wants to use them.

Could you wait for one pull request to complete before jamming another.

Also can you rename the methods so they are not confused w/ spec'ed ones.

I wasn't sure of how to do a "you could also do it this way" pull request. I wasn't trying to "jam another" pull request. In reference to renaming, it's not adding them directly to Object, so if the developer wants to rename them, he/she is free to do so when she/he assigns them to Object.

In reference to renaming, it's not adding them directly to Object, so if the developer wants to rename them, he/she is free to do so when she/he assigns them to Object.

Oh I know they aren't added directly to Object which is awesome, but just the name itself suggests functionality to the user too, which is one reason to use beget instead of create and so on. After all these are the left over hacky bits of es5-shim.

@jdalton why do the names matter? It makes sense to name them after the ES5 versions because they are attemps at emulation the functionality as close as possible.

@jdalton can't we name the container sensibly? so rather then es5object we could call it incompleteShims

I chose es5object to sort of namespace it. It's coming from es5-shims and they are Object shims. If this is included with an AMD loader or in a CommonJS environment, that name doesn't even come into play.

If hey were cleaned up and renamed to fit their actions, as I suggested earlier, then I could see it being named es5util or es5tools. Some tools may or may not be functional depending on browser (for ex: addGetter/addSetter).

If hey were cleaned up and renamed to fit their actions

I'm willing to rename them. I'm no naming expert, so I'd need a bit of help :).
If @jdalton's pull request for #84 gets merged, I'm going to close this and open a new one with just the module to prevent merge conflicts.


Fix auth parameters for the service providers module

This fixes an issue where we get a 401 unauthorized error. The list
of parameters used for authentication should be the same
as the other federation modules.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

ok to test

LGTM


Fix linux build

Thanks for pushing. I will rebase on top of your branch

I try to get mdfviewer also to run


Manual merge

Codecov Report

Merging #279 (77061dc) into master (40e0fde) will increase coverage by 0.02%.
The diff coverage is 88.23%.

@@             Coverage Diff              @@
##             master     #279      +/-   ##
============================================
+ Coverage     90.92%   90.94%   +0.02%
- Complexity      433      434       +1
============================================
  Files            44       44
  Lines          1289     1292       +3
============================================
+ Hits           1172     1175       +3
  Misses          117      117

Impacted Files
Coverage Δ

...licy/Violation/Filter/BrowserBugsNoiseDetector.php
95.00% <75.00%> (-5.00%)
:arrow_down:

src/ContentSecurityPolicy/Violation/Report.php
88.88% <91.66%> (+1.58%)
:arrow_up:

src/ContentSecurityPolicy/Violation/Log/Logger.php
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Feature Request DRAGGING ghost items

Actually drag the items to use as ghosts, not click and item sticks to the mouse
Should still allow single left/right clicks to be used as Recipe/Usage when the mouse is over the items
Bonus points if the bookmarked items are also draggable

I'm not sure if allowing left/right click while still enabling dragging with mouse held down is a good idea


Smart quotes in titles, and mmark bodies

The smart quotes option, as far as I can tell, only applies to the bodies of content, which are processed using the default BlackFriday ".md" parser.
The mmark seems superior in so many ways, so I have taken to using it. As it is derived from BlackFriday, presumably it also has the options for smart quotes. Yet I think they're not being used by Hugo.
Further, even if I use the BlackFriday parser, or I/we extend Hugo to also pass smartquotes and other options to mmark, it seems that quotes in titles are not processed. Is this correct? I suppose there's no easy way to solve this, as the smart quotes are done by the markdown processor, and the titles aren't markdown?
Could you confirm the above is correct, or let me know where I can set the options in case I'm missing them.

Please take questions at http://discuss.gohugo.io/

Hi @adrianmsmith,
Pleaes do what @ bep said, and see also Issue #1970 and Pull Request #2118.
(In short: It is forthcoming, hopefully for 0.17.)

Oh cool, @ bep is already a step of me as always.  :wink:  See https://discuss.gohugo.io/t/smart-quotes-in-titles-and-mmark-bodies/3485


Allows private fields to be used as persistent attributes

Codecov Report

Merging #282 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #282      +/-   ##
=========================================
+ Coverage    86.9%   86.9%   +<.01%
=========================================
  Files          88      88
  Lines        5713    5714       +1
=========================================
+ Hits         4965    4966       +1
  Misses        748     748

Impacted Files
Coverage Δ

lib/src/db/managed/object.dart
92.5% <100%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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


⚠ Bofrost.be has degraded performance

In ad87534, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2010 ms

Resolved: Bofrost.be performance has improved in b779fde.


Opaque errors at times returned from the SDKs

We're usually directly forwarding errors that have been created by wit-bindgen from SDK APIs. This can lead to errors that are less than ideal and only offer the minimal amount of information to the user.
For example, calling key_value::Store::open when the spin.toml manifest does not contain a key_value_stores key for the component simply displays the following:
Handler returned an error: Error::AccessDenied

If the user is unfamiliar with the key_value feature, they have absolutely no idea that this error means that they do not have any allowed stores configured. Ideally we would show something like the following:
Handler returned an error: Error::AccessDenied

Note: Are you sure you've included a list of allowed key_value_stores in your spin.toml?
Make sure to add the `key_value_stores` key to your component and specify which key value stores you'd like to allow.

For example, `key_value_stores = ["default"]` allows the default key value store.

Unfortunately, each SDK would have to handle this themselves. The Rust SDK could do this by making the Display implementation more sophisticated than it currently is. However, to make it really nice where we have configurable "verbosity" of error reporting, we'd likely want a bespoke trait that extends std::error::Error and provides additional features.

Great idea @rylev - in the meantime I have added a callout box to the docs so that folks can find a resolution to this outside of the CLI's response.
https://github.com/fermyon/developer/pull/1278

Unfortunately, each SDK would have to handle this themselves

Is that really the case? Could we do this handling on the runtime side?

Could we do this handling on the runtime side?

We could log details, but we can't tell whether an error is exceptional or not so we'd end up logging sometimes when the error is already being properly handled by the guest.

As we make other breaking changes to interfaces we should also adopt something like wasi:io/error to help with this.

but we can't tell whether an error is exceptional or not so we'd end up logging sometimes when the error is already being properly handled by the guest.

I think the main question is if you'd rather have scenarios with no error details at all or sometimes have duplicated errors.

We could certainly add it at a non-default log level but I personally prefer to keep default logging as actionable as possible.


Fix/issue 6 bugs

Description
Various small bug fixes
How Has This Been Tested?
The se-sdk example tests have not been implemented yet so I manually tested it
Due Diligence
Several of the wc deps have been upgraded to the latest version (2.4 -> 2.7)
Notes
A bug was intentionally left unresolved.
The issue is caused by duplicate key names in an array.
Which is caused by a different issue with core.
Once the issue with core is resolved, this issue will be resolved as well once the dep is upgraded in se-sdk
As there will no longer be dup keys

Hey @JonathanConn could you please add a short list of the bugs that were fixed so we know exactly what to test/look at 🙏

ah lmao, the title led me to think there were 6 bugs fixed, thanks!


enable padding for softmax computation and fix up the existing kernels

This doesn't help us as is, but going forward, its a first step towards padding the vocab dimension to a sane value that actually allows for fast implementations.
I haven't updated any of the softmaxes yet to actually make use of the fact that they're padded. I think the only kernel that would benefit directly from it (more on a LOC perspective than in terms of speed, I think), would be softmax7, as we could get rid of some of the ifs once we know ldd is a multiple of UNROLL_FACTOR.

rebased on  most recent master

superseded  by #264


Merge from develop and bump version to 2.0.0dev21

Codecov Report

Merging #2060 into v2 will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##               v2    #2060   +/-   ##
=======================================
  Coverage   92.71%   92.71%
=======================================
  Files          58       58
  Lines       10702    10702
=======================================
  Hits         9922     9922
  Misses        780      780

Impacted Files
Coverage Δ

botocore/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


activeDebugConsole.append() does not work on Version: 1.29.0

Version: 1.29.0 (system setup)
Commit: 5f24c93878bd4bc645a4a17c620e2487b11005f9
Date: 2018-11-12T07:47:15.448Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
After updated to latest version 1.29.0, my plugin which prints output into DebugConsole using activeDebugConsole.append() function doesnot work anymore.

Probably a duplicate of https://github.com/Microsoft/vscode/issues/61986
@ccc159 can you please try to reproduce with latest vscode insiders https://code.visualstudio.com/insiders/

@isidorn Sorry for late reply.
I tried a simple test on the lastest vscode insiders:
If I want to print something into the debug console, I used to just print like this:

And it should appear in the debug console as it did in the older versions.

Thanks for the clarification. However with the introduction of multi debug consoles we have made the debug console read only while debugging is inactive.
So the debug console can only be appended to if there is an active debug session.
Can you also reproduce this if you are debugging? If yes than this is a bug
If no than this is the limitation of our current design.

Thanks for your answer. I see the reason. It is unfortunately not documented in the vscode reference.
I will switch to OutputChannel to print messages.

Created this issue to make it clearer https://github.com/Microsoft/vscode/issues/63489
Yeah using an OutputChannel makes more sense for your use case.
Thanks!


Change protection level of variables CompanyAddr  in Report 1309 "Standard Sales - Return Rcpt.", Report 6636 "Purchase - Return Shipment", Report 407 "Purchase - Credit Memo", Report 408 "Purchase - Receipt"

Hello, please, change these var to protected var:
1.Report 1309 "Standard Sales - Return Rcpt."
Current:
var
CompanyAddr: array[8] of Text[100];
Should be:
protected var
CompanyAddr: array[8] of Text[100];
2.Report 6636 "Purchase - Return Shipment"
Current:
var
CompanyAddr: array[8] of Text[100];
Should be:
protected var
CompanyAddr: array[8] of Text[100];
3.Report 407 "Purchase - Credit Memo"
Current:
var
CompanyAddr : array[8] of Text[100];
Should be:
protected var
CompanyAddr: array[8] of Text[100];
4.Report 408 "Purchase - Receipt"
Current:
var
CompanyAddr: array[8] of Text[100];
Should be:
protected var
CompanyAddr: array[8] of Text[100];

we had an issue https://github.com/microsoft/ALAppExtensions/issues/26118
I made a mistake to specifying in most lines ShipToAddr :(
I would be very grateful if you could add this in the nearest app, since the company I work for has been waiting for a number of modifications to the tasks for half a year now..... if it lasts for half a year I will be very uncomfortable

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 26910.


Render a child view after target instead of inside it

Is this currently possible? I want to ember-wormhole some <li> blocks into a <ul>.
Right now I can't get it to work because it is putting the <li> blocks into a div and breaking some css.

@djsegal This is not currently possible.

@lukemelia we can close this, I found a way around it.

In my case, I was building a sidebar with breadcrumbs at the top and an index list at the bottom. Because of the temporality of the problem, I was able to just add everything sequentially (i.e. add one bread crumb for each depth of a resource and then a link for all its children).
Because I resolved this issue, I can't think of a use case that would require rendering child views after targets

Thanks for the followup @djsegal


Create stu.txt

@ringpolice Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


solarize color theme better supported

This modification should make the colors match up more closely with those using a Solarized scheme.  See http://ethanschoonover.com/solarized for more details.
Before (note the colored background behind .vimrc and vim-7.4.tar.bz2)

After (note the 'clear' background)

UP
@seebi can we revert this? see #83


[NOJIRA]: avoid commit promotion type not supported by aws tools

Change Logs

rollback when metastore syncfails
change schemaDifference updateColumn structure to store previous/next type
glue sync to fail when unsupported schema evolution

#11599
fixes #11701
Impact
Risk level (write none, low medium or high below)
medium
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@parisni is this ready for review again?

Could you also file a JIRA?

Its ready for revues. Let me add the jira ticket

@yihua updated with a jira ticket. BTW I did not yet test this patch to confirm it works as expected.


Text Formatting

Hello, query, how could I use the options to format the text within the results of the calculated fields?
% {Color: red} network% or  network </ span> are the options I'm trying to use.
Thank you very much.
Greetings.
Diego

Could you perhaps rephrase the question, please?

Yakov, my query is, could you apply some type of format to the result of the calculated fields?
Example: http://www.redmine.org/projects/redmine/wiki/RedmineTextFormattingTextile
I hope I was clear.
Thank you very much.
Greetings.

Sorry, this plugin's functional was created only to calculate values. You could use Textile in text fields, but you should find another way to process text.

Please feel free to reopen this issue if you need help.


Make data references resolvable

[important edit] : Same as #1146 , could not delete issue
Data references: Source should be linkable to a base URL or and resolution service (identifiers.org) and a shorthand namespace, such that the accession number can be resolved.

This is something eLife is interested in. Currently we link all RRIDs to their SciCrunch url, but realise this is not ideal as not a PID.
We're beginning to look at identifiers.org and n2t.net for things used in experiments, but had not thought about them for Data references.
We should talk about this as a group?

Please refer to the product brief document and complete user stories. We have tracked this under "Reference verification".

about compact identifiers: see section "DOIs and Compact Identifiers" in "A data citation roadmap for scientific publishers"

Thanks @michael I have added it to the Product brief
eLife will investigate this further too


Loading Plugins

Hello!
(Sorry in advance if this isn't the right place for this)
I am using FMOD's new CoreAPI wrapper to create FMOD plugins for our game in Godot. It's working fine on the studio end, but Godot is unable to recognize the bank and is giving the following error:
core/variant/variant_utility.cpp:1092 - A requested output, dsp unit type or codec was not available.class godot::Ref __cdecl godot::FmodCache::add_bank(const class godot::String &,unsigned int)src\fmod_cache.cpp47
I asked in the FMOD forums, and they said I'd need to load the built plugin library at runtime, after initialization and before the bank using the plugin is called, "by retrieving the Core API system with Studio::System::getCoreSystem and calling System::loadPlugin 1 with the Core system to load the plugin from the specified path."
They also said they were uncertain if fmod-gdextension has a way of handling plugin loading already.
Does the extension have a way of handling plugin loading? If not, can I maybe get some insight on where to even begin with this? I'm still relatively new to programming and feel a bit in over my head here!
Thanks!!

This extension doesn't have a mechanism to load plugins yet.
It has been requested by several people, and we are currently working on a new update, so loading plugins should be part of the next release (should be in a few weeks).
If you create your own plugins for FMOD, you will have to build it as a dynamic library, put it in a specific directory of your Godot project and call a new method we will add to the FmodServer.

Ah, good to know! Thank you, I'll keep my eyes peeled for the update.

Any updates on this/a rough estimate on when we can expect to see this added? Sorry to be a pest, it's been a few weeks and this is critical to a project I'm working on so I'm just trying to keep tabs/possibly find a workaround!

Hi! I was looking at the new release and noticed I didn't see the plugin loading you mentioned anywhere. Am I missing something or will we have to wait a bit longer?


Submit on ctrl+enter

Implements #35

This looks like pressing Ctrl+Enter while reading a question (not edition) will toggle edition mode. Am I correct?

No, theses lines are in Edit and Answer which are the components shown when editing

OK. I have 2 comments:

Is it intentional to have the listener attached on document instead of the text area? This means the user can press ctrl+enter anywhere and it will submit the question/answer. That might be OK, I don't know.
It might be interesting to have this behavior in a separate component or HOC. I'm not asking you to do it. Just suggesting :).

Those are valid comments 👍 I will implements the changes