Please confirm that these IPs won’t change for the specific region, or do we need to review these entries from time to time?

[Enter feedback here]
Please confirm that these IPs won’t change for the specific region, or do we need to review these entries from time to time?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 80d8f411-2e7f-abc4-3e62-8b467e2409e7
Version Independent ID: b4737b1d-b963-2ee4-aed0-558c80f02704
Content: Azure App Service Environment management addresses
Content Source: articles/app-service/environment/management-addresses.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

Any word on this?

The set of addresses can change over time.  There are two mechanisms to check if they have.  One is to check this doc now and then.  The second is to hit the API I noted to pull down the addresses.

Would be great if the example on get /subscriptions/<subscription ID>/resourceGroups/... was a bit more elaborate.
Can this information be returned as part of an existing ASE? Can this be an Azure-CLI command?
az resource show --ids /subscriptions/<sub>/resourceGroups/<rg>/providers/Microsoft.Web/hostingEnvironments/<name>/inboundnetworkdependenciesendpoints --api-version 2016-09-01
az resource: error: argument --ids: invalid ResourceId value: '/subscriptions//resourceGroups//providers/Microsoft.Web/hostingEnvironments//inboundnetworkdependenciesendpoints'

It looks like this issue has been addressed, so I am closing this. Thanks!


docs: changes to BUILD.md and CONTRIBUTING.md

Is your feature request related to a problem? Please describe.
Based on experience, recommended NodeJS to be used should be v16.13.1 and npm to v8.1.2 to progress smoothly in BUILD.md and CONTRIBUTING.md. Also, we've encountered problems with some codes in BUILD.md and CONTRIBUTING.md and found an alternative that will give an output of 'passed'.
Describe alternatives you've considered
for BUILD.md
NodeJS v16.13.1, npm v8.1.2 (we recommend using the Node Version Manager (nvm) if available for your OS)
•	nvm use 16.13.1
For example, you can run a ledger single status endpoint test via the REST API with this command:
•	npx tap --ts --timeout=600 packages/cactus-test-plugin-htlc-eth-besu/src/test/typescript/integration/plugin-htlc-eth-besu/get-single-status-endpoint.test.ts
for CONTRIBUTING.md
Integration test
•	npx tap --ts --timeout=600 packages/cactus-test-plugin-consortium-manual/src/test/typescript/integration/plugin-consortium-manual/get-consortium-jws-endpoint.test.ts
Unit test
•	npx jest packages/cactus-common/src/test/typescript/unit/objects/get-all-method-names.test.ts

Hello @petermetz . I created a new ticket for the suggestions of changes in documentation, can you assign me on this ticket? Thank you.

@ruzell22 Yup, assigning now. Thank you very much!


Storage S3 adapter broken with 3.15.3

Issue Summary
Storage S3 adapter looks like broken with the new release 3.15.3 where it was working under 3.14.0.
On start ghost return adapter S3 not able to found in folder content/adapters/storage
To Reproduce

Install the S3 adapter storage
Setup your config json prod
Start your ghost instance you will see the error

This is a bug to my pov because the same setup is working like a charm on 3.14
Both stack are deploy by the same ansible playbook roles etc..
Just ghost version change because my ansible role install the latest ghost version.
Technical details:

Ghost Version: 3.15.3
Node Version: 12
Browser/OS:ubuntu 18.04
Database: mysql

Staying at disposal if needed

👋 Hey @yakhatape , can you please specify which S3 storage adapter you are using in this case ?

Gonna close this as based on the information we have it seems like a problem with a specific storage adapter. Can reopen if more information is provided that shows this isn't true.


Add fileinfo extension

The test are still failing because a package on windows requires fileinfo, this was the reason for the ignore-platform-reqs I believe

Thanks!


gh-283: set up nox for developers and CI

Adds noxfile to support nox sessions for testing, docs, and linting/formatting.
Nox is now used to run everything in the CI.
Adds documentation about the new infrastructure in contributing guidelines.

Closes: #283

Blocked by #289

CI now running following #289

Ahh that was a pain, finally works and ready for a review!


Add "toward" and "away" options to point-at constraint

This would allow teams to point with whichever side of their robot is the side they need to use. Eg: you have an intake on the back of your robot but want to point at target with the intake while intaking.

Since arbitrary offsets don't work correctly with trajectory mirroring, we should just support "toward" and "away".

Superseded by #565


switch lightning-cloud to lightning SDK

Before submitting

[x] Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?

What does this PR do?
Discussed with @justusschock that SDK includes inside lightning_cloud and LitDAta also uses SDK, so it would be safer if litData uses single lightning_cloud codebase
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Looks like the authentication step is failing. Do we need to update the token? @Borda
                    "Authentication failed. Please run `lightning login`.")
E               click.exceptions.ClickException: Authentication failed. Please run `lightning login`.
```"

Looks like the authentication step is failing. Do we need to update the token?

I don't see any auth token, so likely we need to update the testing mock


⚠ GitLab Server has degraded performance

In 8a32b64, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 16447 ms

Resolved: GitLab Server performance has improved in 1047d77.


Add definition for impact

Description
Added definition for categorisation impact.
Type of change
Please delete options that are not relevant.

[X] New document(s)/updating existing
[ ] Fixes
[ ] Styling
[ ] Bug fix (non-breaking change which fixes an issue)

hi @igurney-codat, I made some edits to this. should this still be in draft, or are you ready to convert this into a PR for review?
also, please consider the reasoning for updating the Portal / categorize-accounts page. It is no longer surfaced in the menu as it is legacy, and I will be asking shortly if we are ready to remove this entirely - are you confident we should be updating it?


Domain list is out of date when compared to the source.

Hi @ihmpavel, first of all, thanks for the library!
Secondly, there have been some additional domains added to the source list since the last release. Is it possible to create a new release with the latest version of the list, please? 🙂 🙏

Hi @craigcarlyle,
I have released new version 1.0.13 with updated list.


Fixed extra space if not found products in everything new section home page

Related issues

Fix the extra space appear if no any products in the Everything New section
closes #
Short description and why it's useful

make space class conditional so, issue has been fixed.
Screenshots of visual changes before/after (if there are any)

Before:

After:

Which environment this relates to
Check your case. In case of any doubts please read about Release Cycle

[X] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and currently important rules acceptance

[X] I read and followed contribution rules
[ ] I read the TypeScript Action Plan and adjusted my PR according to it
[ ] I read about Vue Storefront Modules and I am aware that every new feature should be a module

Thanks! Could You please just update the changelog?

Thanks! Could You please just update the changelog?

Okay,
But will you please tell me in which release I have to add change log?

@cnviradiya just in this PR, release 1.10rc1

Thanks @cnviradiya !


VS Code extension installation error: unable to verify the first certificate

Hi there, I tried installing rust-analyzer extension via remote SSH in vscode behind a corporate proxy. But it failed with such message:
ERROR [11/26/2021, 9:29:50 AM]: Bootstrap error [st [FetchError]: request to https://api.github.com/repos/rust-analyzer/rust-analyzer/releases/tags/2021-11-22 failed, reason: unable to verify the first certificate
	at ClientRequest.<anonymous> (/home/me/.vscode-server/extensions/matklad.rust-analyzer-0.2.826/out/main.js:39:48367)
	at ClientRequest.emit (events.js:315:20)
	at TLSSocket.socketErrorListener (_http_client.js:469:9)
	at TLSSocket.emit (events.js:315:20)
	at emitErrorNT (internal/streams/destroy.js:106:8)
	at emitErrorCloseNT (internal/streams/destroy.js:74:3)
	at processTicksAndRejections (internal/process/task_queues.js:80:21)] {
  type: 'system',
  errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
  code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
}

I have set http.proxyStrictSSL to false and http.proxy properly, and don't have problem with installing other extensions. My git and cargo both work fine from cmdline. Github API (the above url) is reachable as well. What could be the problem here? Thanks a lot in advance!

Does curl -LO https://api.github.com/repos/rust-analyzer/rust-analyzer/releases/tags/2021-11-22 work for you? Which distro are you using?

that's a good point. Thank you @lnicola
What I got is:
❯ curl -LO https://api.github.com/repos/rust-analyzer/rust-analyzer/releases/tags/2021-11-22
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

But if I provide the option --insecure, the curl command can succeed

my understanding is the vscode setting "http.proxyStrictSSL": false is for this purpose, isn't it?

Which distro are you using?
I'm using ubuntu 20.04

I think that might only apply to the network requests performed by Code. We download the server binary ourselves using node-fetch.

I think that might only apply to the network requests performed by Code. We download the server binary ourselves using node-fetch.

oh, interesting to know! Thanks for the info. Then it would be great to have an extension option to disable the ssl checking. Or, is it possible to bypass it by setting some env vars?

Yeah, it's something we should normally fix. We'd like to bundle the server binary with the extension, but we'll probably still need to keep the code for the nightly updates :disappointed:.

You can try setting NODE_TLS_REJECT_UNAUTHORIZED=0. You might need to add it to your .profile or somewhere.

You can try setting NODE_TLS_REJECT_UNAUTHORIZED=0. You might need to add it to your .profile or somewhere.

It worked like a charm. Many many thanks! I still hope this can be configurable anyway via this extension's settings.
p.s. for googlers who landed here, to solely set NODE_TLS_REJECT_UNAUTHORIZED=0 is not really sufficient for my case as I was facing this issue in the SSH remote mode. To make it work, I killed all the running code or vscode-server processes on the remote server, set this var via export NODE_TLS_REJECT_UNAUTHORIZED=0 (or inject this line to the .bashrc or .zshrc or .profile), then restarted vscode and installed this extension successfully. Now I can enjoy rust-analyzer :)
Thank you @lnicola for your kind help! I think you can consider closing this ticket if the abovementioned extension setting is not easy to implement very soon. This env var solution is acceptable for me.

i filed #10871, but it's pretty hard to test and probably not ready yet.

set this var via export NODE_TLS_REJECT_UNAUTHORIZED=0

Yeah, that only works locally. For SSH you need to edit one of the dotfiles, and for containers it's pretty easy.

I filed #10871, but it's pretty hard to test and probably not ready yet.

really awesome! I can test it by unsetting NODE_TLS_REJECT_UNAUTHORIZED from my side. Pls give me a ping when it get merged. But it would be great if there is a vsix file that I can try with

Yes, I will try it tomorrow or on Thursday. Thank you for the info!
from Dr. Lu Liu's mobile device
On Tue, 30 Nov 2021, 14:42 Laurențiu Nicola, @.***>
wrote:

@tumluliu https://github.com/tumluliu can you give "rust-analyzer.updates.channel":
"nightly" a try?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-analyzer/rust-analyzer/issues/10866#issuecomment-982648338,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL5ZEAZC6THRZ4EJHAGLPTUOTIF3ANCNFSM5I2A5XTA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@lnicola for some reason, it seems that I could not fetch the nightly build although have set the "rust-analyzer.updates.channel": "nightly" config for user, remote and workspace all. Error message was still given by 0.2.834 version:
INFO [12/1/2021, 10:13:33 PM]: PersistentState: {
  lastCheck: undefined,
  nightlyReleaseId: undefined,
  serverVersion: '0.2.834'
}
ERROR [12/1/2021, 10:14:39 PM]: [st [FetchError]: request to https://api.github.com/repos/rust-analyzer/rust-analyzer/releases/tags/nightly failed, reason: unable to verify the first certificate
	at ClientRequest.<anonymous> (/home/me/.vscode-server/extensions/matklad.rust-analyzer-0.2.834/out/main.js:39:48367)
	at ClientRequest.emit (events.js:315:20)
	at TLSSocket.socketErrorListener (_http_client.js:469:9)
	at TLSSocket.emit (events.js:315:20)
	at emitErrorNT (internal/streams/destroy.js:106:8)
	at emitErrorCloseNT (internal/streams/destroy.js:74:3)
	at processTicksAndRejections (internal/process/task_queues.js:80:21)] {
  type: 'system',
  errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
  code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
}

could you pls give me some hints how I can ensure the nightly build can be properly picked up? thanks!

Oh wait, you can't download the nightly build like that. Try getting it from the GitHub release page.

https://github.com/rust-analyzer/rust-analyzer/releases/tag/nightly
Get the vsix from here and install it using the "Install extension from VSIX" command.

@lnicola thanks for the hint! I tried with the vsix file you mentioned, but seems still no luck 🤔
ERROR [12/2/2021, 7:43:03 AM]: [st [FetchError]: request to https://api.github.com/repos/rust-analyzer/rust-analyzer/releases/tags/nightly failed, reason: unable to verify the first certificate
	at ClientRequest.<anonymous> (/home/me/.vscode-server/extensions/matklad.rust-analyzer-0.3.837/out/main.js:39:48367)
	at ClientRequest.emit (events.js:315:20)
	at TLSSocket.socketErrorListener (_http_client.js:469:9)
	at TLSSocket.emit (events.js:315:20)
	at emitErrorNT (internal/streams/destroy.js:106:8)
	at emitErrorCloseNT (internal/streams/destroy.js:74:3)
	at processTicksAndRejections (internal/process/task_queues.js:80:21)] {
  type: 'system',
  errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
  code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
}

anything I can check from my side?

@tumluliu can you try again using the latest nightly VSIX from GitHub?

@lnicola I just did it, but unfortunately still could not run through...
DEBUG [12/4/2021, 8:45:32 AM]: Issuing request for released artifacts metadata to https://api.github.com/repos/rust-analyzer/rust-analyzer/releases/tags/nightly
DEBUG [12/4/2021, 8:45:32 AM]: Fetching release metadata via proxy: http://x.x.x.x:yyyyy
ERROR [12/4/2021, 8:45:44 AM]: Bootstrap error [mt [FetchError]: request to https://api.github.com/repos/rust-analyzer/rust-analyzer/releases/tags/nightly failed, reason: unable to verify the first certificate
	at ClientRequest.<anonymous> (/home/me/.vscode-server/extensions/matklad.rust-analyzer-0.3.839/out/main.js:39:338604)
	at ClientRequest.emit (events.js:315:20)
	at TLSSocket.socketErrorListener (_http_client.js:469:9)
	at TLSSocket.emit (events.js:315:20)
	at emitErrorNT (internal/streams/destroy.js:106:8)
	at emitErrorCloseNT (internal/streams/destroy.js:74:3)
	at processTicksAndRejections (internal/process/task_queues.js:80:21)] {
  type: 'system',
  errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
  code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
}

I assume you did disable http.proxyStrictSSL, right? Oof.

yes, it's really disabled. Otherwise some other plugin would not be able to get installed. But this setting is only on "remote", not in "user" or "workspace". Could this be related?

I fixed one more issue in #10940, which should be included in today's release. But I'll probably have to figure out how to set up an HTTPS proxy to test it properly.

@tumluliu did you get a chance to get test the latest fix? It was included in the last two stable releases, see my comment above.

@lnicola sorry for the long delay! And thank you so much for your updates. I will try to test the latest version you mentioned. It's now a bit more complex for me though since I have updated my certificate to avoid such issue in general.
But still, I will find a time to try it. Once again, thank you for your efforts!

@tumluliu don't worry. The latest version doesn't download the server from GitHub (unless you switch to the nightly channel), so this shouldn't be a problem any more. So it's all right if you can't test it.


fresh vite project throws error

According to the documentation, I've created a project using:
npm init @vitejs/app vite-project -- --template vue
after running cd vite-project,npm install, npm run dev I get the following error:
><EMAIL_ADDRESS>dev
> vite

Pre-bundling dependencies:
  vue
(this will be run only when your dependencies or config have changed)
 > ../../../../package.json:2:0: error: Unexpected end of file
    2 │
      ╵ ^

 > ../../../package.json:2:0: error: Unexpected end of file
    2 │
      ╵ ^

 > ../../package.json:2:0: error: Unexpected end of file
    2 │
      ╵ ^

error when starting dev server:
Error: Build failed with 3 errors:
../../../../package.json:2:0: error: Unexpected end of file
../../../package.json:2:0: error: Unexpected end of file
../../package.json:2:0: error: Unexpected end of file
    at failureErrorWithLog (/Users/projects/vite-project/node_modules/esbuild/lib/main.js:1170:15)
    at buildResponseToResult (/Users/projects/vite-project/node_modules/esbuild/lib/main.js:906:32)
    at /Users/projects/vite-project/node_modules/esbuild/lib/main.js:1001:20
    at /Users/projects/vite-project/node_modules/esbuild/lib/main.js:553:9
    at handleIncomingPacket (/Users/projects/vite-project/node_modules/esbuild/lib/main.js:642:9)
    at Socket.readFromStdout (/Users/projects/vite-project/node_modules/esbuild/lib/main.js:520:7)
    at Socket.emit (node:events:378:20)
    at addChunk (node:internal/streams/readable:313:12)
    at readableAddChunk (node:internal/streams/readable:288:9)
    at Socket.Readable.push (node:internal/streams/readable:227:10)

I can not reproduce this issue. Please respect the issue template including system information.
If the issue remains, please create a reproduction in GitHub uploading the content of your generated vite-project. Thanks.


[orgmode] Pygments is highlighting html from org-html-format-code

At least from cpp and python code blocks, Pygments is highlighting html from org-html-format-code instead of the source code. For instance, the source code block

+BEGIN_SRC cpp ::exports code
int
c = 2;
for( int i = 0; i < 42; i++ ) {
c += i;
}
+END_SRC

is highlighted as

int c = 2;
for( int i = 0; i < 42; i++ ) {
    c += i;
}

I can fix it my removing org-html-format-code from org-html-src-block in init.el:

(let* ((lang (org-element-property :language src-block))
(code-info (org-export-unravel-code element))
(code (car code-info))
;;(code (org-html-format-code src-block info))
)

and I get the correct highlighting:

int c = 2;
for( int i = 0; i < 42; i++ ) {
    c += i;
}

But, I wonder if I'm missing some configuration setting? I'm using emacs <IP_ADDRESS> and org-mode 8.3.5.
Thanks

Can you try dropping the -g flag to pygments as mentioned here: https://github.com/getnikola/plugins/issues/162 ?

No, no luck there. The input to Pygments has already been converted to html, and Pygments is trying to highlight that.

What version of org-mode are you using?  I'm unable to reproduce this with 8.3.x or 9.0.  Please update to a relatively recent version of org-mode and feel free to re-open this if the problem persists.


How to disable auto completion pop up when dot is typed?

Related:

https://github.com/tomv564/LSP/issues/203 Spaces don't trigger autocompletion

I see the related code here:
File: sublime-text-3/Packages/LSP/plugin/completion.py
168:     def register_trigger_chars(self, session: Session) -> None:
169:         completion_triggers = self.view.settings().get('auto_complete_triggers', [])
170:         view_language = self._view_language(session.config.name)
171:         if view_language:
172:             for language in session.config.languages:
173:                 if language.id == view_language:
174:                     for scope in language.scopes:
175:                         # log(2, "registering", self.trigger_chars, "for", scope)
176:                         scope_trigger = next(
177:                             (trigger for trigger in completion_triggers if trigger.get('selector', None) == scope),
178:                             None
179:                         )
180:                         if scope_trigger:
181:                             scope_trigger['characters'] = "".join(self.trigger_chars)
182:                         else:
183:                             completion_triggers.append({
184:                                 'characters': "".join(self.trigger_chars),
185:                                 'selector': scope
186:                             })
187:

Is there something incorrect about the autocomplete behaviour, or is it a preference to not see it?

I as I set to commit auto-completion with the Enter key, it just became very annoying recently because most times I had to close it with Escape. It is preferable to press Ctrl+Space to open the auto-completion if I need it after a dot.

To avoid adding yet another setting to LSP, I wonder if we can make LSP respect your Sublime configuration here. Would it work if LSP only registered the trigger characters if you had nothing configured for a given scope?

What do you mean by scope? Is it this configuration?
  "default_clients":
  {
    "pyls":
    {
      "command": ["pyls"],
      "scopes": ["source.python"],
      "syntaxes": ["Packages/Python/Python.sublime-syntax"],
      "languageId": "python"
    },

I did not configure the "scopes": ["source.python"] on my user settings.

Sorry, that was super unclear.
So I think LSP is aggressive in modifying the user's Sublime auto_complete_triggers:
    "auto_complete_triggers": [ {"selector": "text.html", "characters": "<"} ],

My proposal is to disable the registering of additional auto complete triggers in LSP if you add { "selector": "source.python", "characters": "" }
What do you think?

If I can add { "selector": "source.python", "characters": "" } into the LSP settings, for the pyls plugin, then it is fine. I would not like to add it to my main/global Preferences.sublime-settings because I would overwrite all packages settings for this setting.

@evandrocoan syntax-specific settings may be an alternative?

I do not like that neither. They are also global (per language) settings configuration.
What is the problem with adding a LSP setting to the LSP.sublime-settings?

I understand you think it's LSP's problem and that's why the setting should live there. I don't want to add new settings to LSP for every single exception, so my offer is to respect the user's Sublime configuration.

I just managed to add the setting. I just cannot believe how hard it was.
Now I understand why you do not want to add new settings. It is incredibly hard. Any change involves a lot of refactoring by changing several function calls signatures.
I managed to get out with less by adding it in some place I did not liked to add it, but involved 0 refactoring.
Ideally, I would add this setting for each language the language server provides, but to avoid any refactoring to the internal settings building I added it globally to all languages a language server provides.
Why it is not difficult to add new settings? It is because language servers are insane to satisfy?

The code registering trigger characters if you had already specified some for source.python has been removed in master. If more users find the workaround unacceptable then we can revisit the current behaviour.


Option to include vs exclude borders of the selection ?

Hi,
When I select a neighbourdhood, it looks like the selection tool doesn't include the outside boundary
Ex:

I would love to be able to activate a parameter for the selection tool to make these roads part of the visualisation (in levels of red, just like residential streets, to be able to visualize that when I add modal filters my residential streets are getting pinkish/white, while my main roads are getting darker levels of red)
ltn_Neudorf.zip
For exemple here, I'd like to get Avenue du Rhin, Rue du Landsberg, Avenue Aristide Briand and Avenue Jean Jaurès part of the equation (which isn't easy with the current selection tool). I only managed to get a part of "Avenue Jean Jaurès" in the mix (the east->west direction)

Absolutely unhelpful comment but it's really cool to see someone (who's a compelty stranger to me) work with LTN on the neighborhood where I grew up and spent nearly 10+ years of my life. :heart: (ok to be honest, I lived 1.5km to the south-west)

This now works with the new "Include perim roads" option. #67 tracks some problems with finding perimeter roads


Switch to new CodeMirror-based editor

This replaces the Ace editor with a new CodeMirror-based editor, being built as a separate component here: https://github.com/chordbook/editor

@edwinzap @jrmora This diff shows an example of using the new editor, if you want to try it out. Specifically these lines in Editor.js


ZEPPELIN-1607. Refactor Livy Interpreter to adapt scope mode

What is this PR for?
ZEPPELIN-1606 will make scoped mode as the default interpreter mode of livy. This PR is to refactor livy interpreter to adapt the scoped mode. Besides, it also fix several bugs of livy interpreter.  like ZEPPELIN-1516. Besides that I also enable livy integration test in travis to make sure the refactoring correct.
What type of PR is it?
[Refactoring]
Todos

Move session creation to open()
Other refactoring in livy interpreter, especially LivyHelper.java

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-1607

How should this be tested?
Travis is also enabled for livy integration test.
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@felixcheung @prabhjyotsingh @Leemoonsoo  Please help review.

Looks good to me

@Leemoonsoo @bzz @felixcheung Finally I got the livy integration test passed (failed test is flaky test, not related to this PR). I have to run livy integration test separately. Because the travis docker container has 3 gb memory limitation, the maven build process will be killed if I put livy integration test with others. Several other livy PR depends on this PR, so I hope get this PR merge first and plan to do the improvement of .travis.yml in a following PR.

LGTM and merge to master if there're no more comment.


IGraphicsHost Desgin?

What should IGraphicsHost have control over and expose?
Currently in OpenGL it handles the window and the window contains a timer. We are currently not using the timer since we have BeginFrame() and EndFrame().

@yufeih Why did you remove the Window Handle from IGraphicsHost in develop branch? :smiley:

IGraphicsHost should be platform independent. Window handle is specific to WIN32 app model.


update telemetry subcommand parser

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

Comparison is base (45d8578) 83.63% compared to head (fc66ac5) 83.63%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #443   +/-   ##
=======================================
  Coverage   83.63%   83.63%
=======================================
  Files         211      211
  Lines       12363    12363
=======================================
  Hits        10340    10340
  Misses       1654     1654
  Partials      369      369

Flag
Coverage Δ

unittests
83.63% <ø> (ø)

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

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


Installing app on device failed for platform "ios" with status code: 14.

I am trying to start an AIR application on the mobile device. Where can I find more information about the error codes? Would it be possible to make a more generic error description?
Preparing to install Adobe AIR application...
Installing Adobe AIR application...
Installing app on device failed for platform "ios" with status code: 14.

There are a couple of reasons listed in Adobe's official documentation: ADT installApp command.

If the specified device is not connected, ADT returns exit code 14: Device error (Android) or Invalid device specified (iOS).
If the specified package is already installed, ADT returns error code 14: Device error.

It's not the second one. VSCode always uninstalls the app before trying to install again.
Which platform are you on? On Windows, make sure to open iTunes. On any platform, make sure that you've unlocked the device and given permission for your computer to connect.

Thanks a lot for the hints. Do I need to explicitly name the device in a settings file or where/how can I specify the device?
Currently, I am on OS X High Sierra. iOS device is unlocked and has permission (I already used it with Flash Builder, which obviously I want to replace with VS Code 🥇).

This is the message box which appears.

Do I need to explicitly name the device in a settings file or where/how can I specify the device?

No, it should automatically detect your device. Just make sure that it's connected via USB and that no other iOS devices are also connected at the same time.

This is the message box which appears.

I think that this is a bug in VSCode, but it's normal when debugging fails.

@m-a-v Were you able to get an app installed on iOS?

Are you still seeing this error?

Installing app on device failed for platform "ios" with status code: 14.

I ask because the screenshot of the empty message box that you posted leads me to believe that installation might be completing successfully. That empty message box usually means that it's not connecting to the debugger after the app launches. Correct me if I'm wrong.
If your mobile device is on wifi, but your computer is not, you could try using the "connect" option for an "attach" request. This will attempt to connect to the debugger over USB instead of wifi.
{
	"type": "swf",
	"request": "attach",
	"name": "Attach SWF",
	"platform": "ios",
	"connect": true
}

After a long time I retry again to move our project to VS Code. The device was always attached with USB. The installation is certainly not successful. If I install the ipa using the adt tool I get an ApplicationVerificationFailed error, so I think this lead to the error 14 at the end.
Installation Error: ApplicationVerificationFailed.
The problem was that I made a typo in the application id.
BTW: Is there a way to store/cache the Adobe AIR code signing password?

BTW: Is there a way to store/cache the Adobe AIR code signing password?

Not at this time, but it's something that I want to add.

hello, was this resolved?


Ignoring device as it is offline

Describe The Bug:
In debug mode, the logs show my 3 devices are offline, but I can see and control them using the Honeywell Home App.
To Reproduce:
I just authenticated using the UI (and double checked that the config is in the file) and when home bridge starts it shows in the log the message in the title for each one of the 3 thermostats I have here.
Expected behavior:
Thermostats should be listed in the home Bridge device settings (and not ignored)
Logs:
6/6/2020, 12:04:31 PM] [HoneywellHome] [DEBUG] Getting devices for Lylebrooke...
[6/6/2020, 12:04:32 PM] [HoneywellHome] Found 3 devices at Lylebrooke.
[6/6/2020, 12:04:32 PM] [HoneywellHome] [DEBUG] Ignoring device named 1st as it is offline.
[6/6/2020, 12:04:32 PM] [HoneywellHome] [DEBUG] Ignoring device named 2nd as it is offline.
[6/6/2020, 12:04:32 PM] [HoneywellHome] [DEBUG] Ignoring device named 3rd as it is offline.

Homebridge Config:

{
            "name": "HoneywellHome",
            "credentials": {
                "consumerKey": "token",
                "refreshToken": "refresh_tokey",
                "notice": "Keep your tokens a secret!"
            },
            "options": {
                "ttl": 60,
                "debug": true
            },
            "platform": "HoneywellHome"
        }

Screenshots:
Not applicable
Environment:

Node.js Version: 12.18.0
NPM Version: 6.14.4
Homebridge Version: latest (1.1.0)
Homebridge Honeywell Home Version: latest (just installed)
Homebridge Config UI X Plugin Version: latest
Operating System: Raspbian

I am having the same problem.

if you have a fix for this, you can submit a pr. I have never experience this.

I do not. Can you help debugging? I used the UI to config and that’s what the log show me. Even with today’s update.

@roficas @gcollier  what is your thermostat models?

THE ROUND SMART THERMOSTAT

can you test the latest beta #186 ? and let me know what you see?
If you are willing to test, I can take the provisioning piece out

I'll test this weekend! I'm checking your changes as well... thanks!

I am going to close this since this will be in the next release. I have take the provisioning piece out for now.

I closed by mistake - sorry... reopening.
Do you want me to post the logs here? I'll do that later...

I closed by mistake - sorry... reopening.
Do you want me to post the logs here? I'll do that later...

yes full logs would be good!

They are similar to the last one and fail when trying to config the fist device:

[7/31/2020, 2:01:18 PM] Registering platform 'homebridge-honeywell-home.HoneywellHome'
[7/31/2020, 2:01:20 PM] [HoneywellHome] Initializing HoneywellHome platform...
[7/31/2020, 2:01:20 PM] [HoneywellHome] Finished initializing platform: HoneywellHome
[7/31/2020, 2:01:20 PM] [HoneywellHome] Config OK
[7/31/2020, 2:01:21 PM] [HoneywellHome] Executed didFinishLaunching callback
[7/31/2020, 2:01:21 PM] [HoneywellHome] Got access token: xxx
[7/31/2020, 2:01:21 PM] [HoneywellHome] New refresh token: xxx
[7/31/2020, 2:01:21 PM] [HoneywellHome] Homebridge config.json has been updated with new refresh token.
[7/31/2020, 2:01:22 PM] [HoneywellHome] # of Locations Found: 1.
[7/31/2020, 2:01:22 PM] [HoneywellHome] Getting devices for Lylebrooke...
[7/31/2020, 2:01:22 PM] [HoneywellHome] 1359757
[7/31/2020, 2:01:22 PM] [HoneywellHome] {
  locationID: 1359757,
  name: 'Lylebrooke',
  country: 'US',
  zipcode: '30080',
  devices: [
    {
      thermostatVersion: '<IP_ADDRESS>',
      scheduleStatus: 'Pause',
      allowedTimeIncrements: 15,
      settings: [Object],
      deviceClass: 'Thermostat',
      deviceType: 'Thermostat',
      deviceID: 'TCC-xxx’,
      userDefinedDeviceName: '1st',
      name: '1st',
      schedule: [Object],
      isAlive: true,
      isUpgrading: false,
      isProvisioned: false,
      macID: ‘xxx’,
      deviceSettings: {},
      service: [Object],
      deviceRegistrationDate: '2019-07-20T01:13:43.2266667',
      dataSyncStatus: 'UnKnown',
      units: 'Fahrenheit',
      indoorTemperature: 80,
      outdoorTemperature: 76,
      allowedModes: [Array],
      deadband: 0,
      hasDualSetpointStatus: false,
      minHeatSetpoint: 40,
      maxHeatSetpoint: 99,
      minCoolSetpoint: 40,
      maxCoolSetpoint: 99,
      changeableValues: [Object],
      operationStatus: [Object],
      smartAway: [Object],
      indoorHumidity: 49,
      indoorHumidityStatus: 'Measured',
      deviceModel: 'Round'
    },
    {
      thermostatVersion: '<IP_ADDRESS>',
      scheduleStatus: 'Pause',
      allowedTimeIncrements: 15,
      settings: [Object],
      deviceClass: 'Thermostat',
      deviceType: 'Thermostat',
      deviceID: 'TCC-xxx’,
      userDefinedDeviceName: '2nd',
      name: '2nd',
      schedule: [Object],
      isAlive: true,
      isUpgrading: false,
      isProvisioned: false,
      macID: ‘xxx’,
      deviceSettings: {},
      service: [Object],
      deviceRegistrationDate: '2020-06-04T12:46:19.35',
      dataSyncStatus: 'UnKnown',
      units: 'Fahrenheit',
      indoorTemperature: 79,
      outdoorTemperature: 76,
      allowedModes: [Array],
      deadband: 0,
      hasDualSetpointStatus: false,
      minHeatSetpoint: 40,
      maxHeatSetpoint: 99,
      minCoolSetpoint: 40,
      maxCoolSetpoint: 99,
      changeableValues: [Object],
      operationStatus: [Object],
      smartAway: [Object],
      indoorHumidity: 49,
      indoorHumidityStatus: 'Measured',
      deviceModel: 'Round'
    },
    {
      thermostatVersion: '<IP_ADDRESS>',
      scheduleStatus: 'Pause',
      allowedTimeIncrements: 15,
      settings: [Object],
      deviceClass: 'Thermostat',
      deviceType: 'Thermostat',
      deviceID: 'TCC-xxx’,
      userDefinedDeviceName: '3rd',
      name: '3rd',
      schedule: [Object],
      isAlive: true,
      isUpgrading: false,
      isProvisioned: false,
      macID: ‘xxx’,
      deviceSettings: {},
      service: [Object],
      deviceRegistrationDate: '2019-08-13T20:14:14.54',
      dataSyncStatus: 'UnKnown',
      units: 'Fahrenheit',
      indoorTemperature: 80,
      outdoorTemperature: 76,
      allowedModes: [Array],
      deadband: 0,
      hasDualSetpointStatus: false,
      minHeatSetpoint: 40,
      maxHeatSetpoint: 99,
      minCoolSetpoint: 40,
      maxCoolSetpoint: 99,
      changeableValues: [Object],
      operationStatus: [Object],
      smartAway: [Object],
      indoorHumidity: 65,
      indoorHumidityStatus: 'Measured',
      deviceModel: 'Round'
    }
  ],
  users: [
    {
      userID: xxx,
      username: ‘xxx’,
      firstname: 'Roger',
      lastname: ‘xxx’,
      created:<PHONE_NUMBER>,
      deleted: -62135596800,
      activated: true,
      connectedHomeAccountExists: true,
      locationRoleMapping: [Array],
      isOptOut: '',
      isCurrentUser: true
    },
    {
      userID: xxx,
      username: ‘xxx,
      firstname: 'Livia',
      lastname: ‘xxx’,
      created:<PHONE_NUMBER>,
      deleted: -62135596800,
      activated: true,
      connectedHomeAccountExists: true,
      locationRoleMapping: [Array],
      isOptOut: '',
      isCurrentUser: false
    }
  ],
  timeZoneId: 'Eastern',
  timeZone: 'Eastern Standard Time',
  ianaTimeZone: 'America/New_York',
  daylightSavingTimeEnabled: true,
  geoFences: [
    {
      geofenceEnabled: true,
      geoFenceID: 1367520,
      latitude: xx,
      longitude: -xx,
      radius: 1609.86633,
      geoOccupancy: [Object],
      geoFenceNotificationEnabled: false
    }
  ],
  geoFenceEnabled: true,
  predictiveAIREnabled: false,
  comfortLevel: 0,
  geoFenceNotificationEnabled: false,
  geoFenceNotificationTypeId: 13,
  configuration: {
    faceRecognition: {
      enabled: false,
      maxPersons: 2,
      maxEtas: 2,
      maxEtaPersons: 1,
      schedules: [Array]
    }
  }
}
[7/31/2020, 2:01:22 PM] [HoneywellHome] # of Thermostats Found at Lylebrooke: 3.
[7/31/2020, 2:01:22 PM] [HoneywellHome] {
  thermostatVersion: '<IP_ADDRESS>',
  scheduleStatus: 'Pause',
  allowedTimeIncrements: 15,
  settings: {
    homeSetPoints: { homeHeatSP: 70, homeCoolSP: 76, units: 'Fahrenheit' },
    awaySetPoints: {
      awayHeatSP: 68,
      awayCoolSP: 72,
      smartCoolSP: 80,
      smartHeatSP: 55,
      useAutoSmart: true,
      units: 'Fahrenheit'
    },
    hardwareSettings: { brightness: 3, volume: 10, maxBrightness: 10, maxVolume: 10 },
    fan: {
      allowedModes: [Array],
      changeableValues: [Object],
      fanRunning: false
    },
    temperatureMode: { feelsLike: true, air: true },
    specialMode: { autoChangeoverActive: true, emergencyHeatActive: false }
  },
  deviceClass: 'Thermostat',
  deviceType: 'Thermostat',
  deviceID: 'TCC-xxx’,
  userDefinedDeviceName: '1st',
  name: '1st',
  schedule: { scheduleType: 'Geofence' },
  isAlive: true,
  isUpgrading: false,
  isProvisioned: false,
  macID: ‘xxx’,
  deviceSettings: {},
  service: { mode: 'Up' },
  deviceRegistrationDate: '2019-07-20T01:13:43.2266667',
  dataSyncStatus: 'UnKnown',
  units: 'Fahrenheit',
  indoorTemperature: 80,
  outdoorTemperature: 76,
  allowedModes: [ 'Cool', 'Heat', 'Off' ],
  deadband: 0,
  hasDualSetpointStatus: false,
  minHeatSetpoint: 40,
  maxHeatSetpoint: 99,
  minCoolSetpoint: 40,
  maxCoolSetpoint: 99,
  changeableValues: {
    mode: 'Auto',
    autoChangeoverActive: true,
    emergencyHeatActive: false,
    heatSetpoint: 72,
    coolSetpoint: 80,
    heatCoolMode: 'Cool'
  },
  operationStatus: { mode: 'EquipmentOff' },
  smartAway: {
    active: false,
    timeOfDay: '00:00:00',
    durationInHours: 0,
    durationInDays: 0,
    lastUsedFormat: 'TimeOfDay',
    endsIn: '2000-01-01T00:00:00-05:00'
  },
  indoorHumidity: 49,
  indoorHumidityStatus: 'Measured',
  deviceModel: 'Round'
}
[7/31/2020, 2:01:22 PM] [HoneywellHome] TCC-2733987
[7/31/2020, 2:01:22 PM] [HoneywellHome] Allowed Fan Modes: Auto,On,Circulate
[7/31/2020, 2:01:22 PM] [HoneywellHome] Fan Mode: Auto
[7/31/2020, 2:01:22 PM] [HoneywellHome] Failed to refresh access token. device.groups is not iterable

Looks like the issue is at line 245:
for (const group of device.groups) {

I haven't looked at the API yet to understand what is a group and if this is required to later load the thermostats (line 255:
const accessory = (await this.axios.get(`${DeviceURL}/thermostats/${device.deviceID}/group/${group.id}/rooms`, {

Maybe there is a way around that or a reason for my config not having this group...

@roficas device.groups is required for T9 thermostats since they have rooms and groups. I will look into see if I can make two different versions of thermostats work with this. the two different versions are TCC and LCC. I have LCC.
I will work on this as soon as I can, but no promise that it will be quick.

@roficas I have released a new update. this includes an if statement to find TCC devices. Can you test it and post the outputs?

With this beta, it could go further. Here is the output with this release:
[8/1/2020, 11:10:35 AM] [HoneywellHome] Initializing HoneywellHome platform...
[8/1/2020, 11:10:35 AM] [HoneywellHome] Finished initializing platform: HoneywellHome
[8/1/2020, 11:10:35 AM] [HoneywellHome] Config OK
[8/1/2020, 11:10:36 AM] [HoneywellHome] Executed didFinishLaunching callback
[8/1/2020, 11:10:36 AM] [HoneywellHome] Got access token: xxx
[8/1/2020, 11:10:36 AM] [HoneywellHome] New refresh token: xxx
[8/1/2020, 11:10:36 AM] [HoneywellHome] Homebridge config.json has been updated with new refresh token.
[8/1/2020, 11:10:36 AM] [HoneywellHome] # of Locations Found: 1.
[8/1/2020, 11:10:36 AM] [HoneywellHome] Getting devices for Lylebrooke...
[8/1/2020, 11:10:36 AM] [HoneywellHome] 1359757
[8/1/2020, 11:10:36 AM] [HoneywellHome] {
  locationID: 1359757,
  name: 'Lylebrooke',
  country: 'US',
  zipcode: '30080',
  devices: [
    {
      thermostatVersion: '<IP_ADDRESS>',
      scheduleStatus: 'Pause',
      allowedTimeIncrements: 15,
      settings: [Object],
      deviceClass: 'Thermostat',
      deviceType: 'Thermostat',
      deviceID: 'TCC-xxx’,
      userDefinedDeviceName: '1st',
      name: '1st',
      schedule: [Object],
      isAlive: true,
      isUpgrading: false,
      isProvisioned: false,
      macID: ‘xxx’,
      deviceSettings: {},
      service: [Object],
      deviceRegistrationDate: '2019-07-20T01:13:43.2266667',
      dataSyncStatus: 'UnKnown',
      units: 'Fahrenheit',
      indoorTemperature: 80,
      outdoorTemperature: 84,
      allowedModes: [Array],
      deadband: 0,
      hasDualSetpointStatus: false,
      minHeatSetpoint: 40,
      maxHeatSetpoint: 99,
      minCoolSetpoint: 40,
      maxCoolSetpoint: 99,
      changeableValues: [Object],
      operationStatus: [Object],
      smartAway: [Object],
      indoorHumidity: 49,
      indoorHumidityStatus: 'Measured',
      deviceModel: 'Round'
    },
    {
      thermostatVersion: '<IP_ADDRESS>',
      scheduleStatus: 'Pause',
      allowedTimeIncrements: 15,
      settings: [Object],
      deviceClass: 'Thermostat',
      deviceType: 'Thermostat',
      deviceID: 'TCC-xxx’,
      userDefinedDeviceName: '2nd',
      name: '2nd',
      schedule: [Object],
      isAlive: true,
      isUpgrading: false,
      isProvisioned: false,
      macID: ‘xxx’,
      deviceSettings: {},
      service: [Object],
      deviceRegistrationDate: '2020-06-04T12:46:19.35',
      dataSyncStatus: 'UnKnown',
      units: 'Fahrenheit',
      indoorTemperature: 79,
      outdoorTemperature: 84,
      allowedModes: [Array],
      deadband: 0,
      hasDualSetpointStatus: false,
      minHeatSetpoint: 40,
      maxHeatSetpoint: 99,
      minCoolSetpoint: 40,
      maxCoolSetpoint: 99,
      changeableValues: [Object],
      operationStatus: [Object],
      smartAway: [Object],
      indoorHumidity: 49,
      indoorHumidityStatus: 'Measured',
      deviceModel: 'Round'
    },
    {
      thermostatVersion: '<IP_ADDRESS>',
      scheduleStatus: 'Pause',
      allowedTimeIncrements: 15,
      settings: [Object],
      deviceClass: 'Thermostat',
      deviceType: 'Thermostat',
      deviceID: 'TCC-xxx’,
      userDefinedDeviceName: '3rd',
      name: '3rd',
      schedule: [Object],
      isAlive: true,
      isUpgrading: false,
      isProvisioned: false,
      macID: ‘xxx’,
      deviceSettings: {},
      service: [Object],
      deviceRegistrationDate: '2019-08-13T20:14:14.54',
      dataSyncStatus: 'UnKnown',
      units: 'Fahrenheit',
      indoorTemperature: 80,
      outdoorTemperature: 84,
      allowedModes: [Array],
      deadband: 0,
      hasDualSetpointStatus: false,
      minHeatSetpoint: 40,
      maxHeatSetpoint: 99,
      minCoolSetpoint: 40,
      maxCoolSetpoint: 99,
      changeableValues: [Object],
      operationStatus: [Object],
      smartAway: [Object],
      indoorHumidity: 50,
      indoorHumidityStatus: 'Measured',
      deviceModel: 'Round'
    }
  ],
  users: [
    {
      userID: xxx,
      username: ‘xxx’,
      firstname: 'Roger',
      lastname: ‘xxx’,
      created:<PHONE_NUMBER>,
      deleted: -62135596800,
      activated: true,
      connectedHomeAccountExists: true,
      locationRoleMapping: [Array],
      isOptOut: '',
      isCurrentUser: true
    },
    {
      userID: xxx,
      username: ‘xxx’,
      firstname: 'Livia',
      lastname: ‘xxx’,
      created:<PHONE_NUMBER>,
      deleted: -62135596800,
      activated: true,
      connectedHomeAccountExists: true,
      locationRoleMapping: [Array],
      isOptOut: '',
      isCurrentUser: false
    }
  ],
  timeZoneId: 'Eastern',
  timeZone: 'Eastern Standard Time',
  ianaTimeZone: 'America/New_York',
  daylightSavingTimeEnabled: true,
  geoFences: [
    {
      geofenceEnabled: true,
      geoFenceID: 1367520,
      latitude: xxx,
      longitude: -xxx,
      radius: 1609.86633,
      geoOccupancy: [Object],
      geoFenceNotificationEnabled: false
    }
  ],
  geoFenceEnabled: true,
  predictiveAIREnabled: false,
  comfortLevel: 0,
  geoFenceNotificationEnabled: false,
  geoFenceNotificationTypeId: 13,
  configuration: {
    faceRecognition: {
      enabled: false,
      maxPersons: 2,
      maxEtas: 2,
      maxEtaPersons: 1,
      schedules: [Array]
    }
  }
}
[8/1/2020, 11:10:36 AM] [HoneywellHome] # of Thermostats Found at Lylebrooke: 3.
[8/1/2020, 11:10:36 AM] [HoneywellHome] {
  thermostatVersion: '<IP_ADDRESS>',
  scheduleStatus: 'Pause',
  allowedTimeIncrements: 15,
  settings: {
    homeSetPoints: { homeHeatSP: 70, homeCoolSP: 76, units: 'Fahrenheit' },
    awaySetPoints: {
      awayHeatSP: 68,
      awayCoolSP: 72,
      smartCoolSP: 80,
      smartHeatSP: 55,
      useAutoSmart: true,
      units: 'Fahrenheit'
    },
    hardwareSettings: { brightness: 3, volume: 10, maxBrightness: 10, maxVolume: 10 },
    fan: {
      allowedModes: [Array],
      changeableValues: [Object],
      fanRunning: false
    },
    temperatureMode: { feelsLike: true, air: true },
    specialMode: { autoChangeoverActive: true, emergencyHeatActive: false }
  },
  deviceClass: 'Thermostat',
  deviceType: 'Thermostat',
  deviceID: 'TCC-xxx’,
  userDefinedDeviceName: '1st',
  name: '1st',
  schedule: { scheduleType: 'Geofence' },
  isAlive: true,
  isUpgrading: false,
  isProvisioned: false,
  macID: ‘xxx’,
  deviceSettings: {},
  service: { mode: 'Up' },
  deviceRegistrationDate: '2019-07-20T01:13:43.2266667',
  dataSyncStatus: 'UnKnown',
  units: 'Fahrenheit',
  indoorTemperature: 80,
  outdoorTemperature: 84,
  allowedModes: [ 'Cool', 'Heat', 'Off' ],
  deadband: 0,
  hasDualSetpointStatus: false,
  minHeatSetpoint: 40,
  maxHeatSetpoint: 99,
  minCoolSetpoint: 40,
  maxCoolSetpoint: 99,
  changeableValues: {
    mode: 'Auto',
    autoChangeoverActive: true,
    emergencyHeatActive: false,
    heatSetpoint: 72,
    coolSetpoint: 80,
    heatCoolMode: 'Cool'
  },
  operationStatus: { mode: 'EquipmentOff' },
  smartAway: {
    active: false,
    timeOfDay: '00:00:00',
    durationInHours: 0,
    durationInDays: 0,
    lastUsedFormat: 'TimeOfDay',
    endsIn: '2000-01-01T00:00:00-05:00'
  },
  indoorHumidity: 49,
  indoorHumidityStatus: 'Measured',
  deviceModel: 'Round'
}
[8/1/2020, 11:10:36 AM] [HoneywellHome] TCC-xxx
[8/1/2020, 11:10:36 AM] [HoneywellHome] Allowed Fan Modes: Auto,On,Circulate
[8/1/2020, 11:10:36 AM] [HoneywellHome] Fan Mode: Auto
[8/1/2020, 11:10:36 AM] [HoneywellHome] Ignoring device named 1st - TCC-xxx, Alive Status: true
[8/1/2020, 11:10:36 AM] [HoneywellHome] {
  thermostatVersion: '<IP_ADDRESS>',
  scheduleStatus: 'Pause',
  allowedTimeIncrements: 15,
  settings: {
    homeSetPoints: { homeHeatSP: 70, homeCoolSP: 78, units: 'Fahrenheit' },
    awaySetPoints: {
      awayHeatSP: 62,
      awayCoolSP: 85,
      smartCoolSP: 80,
      smartHeatSP: 55,
      useAutoSmart: true,
      units: 'Fahrenheit'
    },
    hardwareSettings: { brightness: 2, volume: 5, maxBrightness: 10, maxVolume: 10 },
    fan: {
      allowedModes: [Array],
      changeableValues: [Object],
      fanRunning: false
    },
    temperatureMode: { feelsLike: true, air: true },
    specialMode: { autoChangeoverActive: true, emergencyHeatActive: false }
  },
  deviceClass: 'Thermostat',
  deviceType: 'Thermostat',
  deviceID: 'TCC-xxx’,
  userDefinedDeviceName: '2nd',
  name: '2nd',
  schedule: { scheduleType: 'Geofence' },
  isAlive: true,
  isUpgrading: false,
  isProvisioned: false,
  macID: ‘xxx’,
  deviceSettings: {},
  service: { mode: 'Up' },
  deviceRegistrationDate: '2020-06-04T12:46:19.35',
  dataSyncStatus: 'UnKnown',
  units: 'Fahrenheit',
  indoorTemperature: 79,
  outdoorTemperature: 84,
  allowedModes: [ 'Cool', 'Heat', 'Off' ],
  deadband: 0,
  hasDualSetpointStatus: false,
  minHeatSetpoint: 40,
  maxHeatSetpoint: 99,
  minCoolSetpoint: 40,
  maxCoolSetpoint: 99,
  changeableValues: {
    mode: 'Auto',
    autoChangeoverActive: true,
    emergencyHeatActive: false,
    heatSetpoint: 72,
    coolSetpoint: 79,
    heatCoolMode: 'Cool'
  },
  operationStatus: { mode: 'EquipmentOff' },
  smartAway: {
    active: false,
    timeOfDay: '00:00:00',
    durationInHours: 1,
    durationInDays: 0,
    lastUsedFormat: 'DurationInHours',
    endsIn: '2020-01-03T13:08:00-05:00'
  },
  indoorHumidity: 49,
  indoorHumidityStatus: 'Measured',
  deviceModel: 'Round'
}
[8/1/2020, 11:10:36 AM] [HoneywellHome] TCC-xxx
[8/1/2020, 11:10:36 AM] [HoneywellHome] Allowed Fan Modes: Auto,On,Circulate
[8/1/2020, 11:10:36 AM] [HoneywellHome] Fan Mode: Auto
[8/1/2020, 11:10:36 AM] [HoneywellHome] Ignoring device named 2nd - TCC-xxx, Alive Status: true
[8/1/2020, 11:10:36 AM] [HoneywellHome] {
  thermostatVersion: '<IP_ADDRESS>',
  scheduleStatus: 'Pause',
  allowedTimeIncrements: 15,
  settings: {
    homeSetPoints: { homeHeatSP: 70, homeCoolSP: 78, units: 'Fahrenheit' },
    awaySetPoints: {
      awayHeatSP: 62,
      awayCoolSP: 85,
      smartCoolSP: 80,
      smartHeatSP: 55,
      useAutoSmart: true,
      units: 'Fahrenheit'
    },
    hardwareSettings: { brightness: 2, volume: 5, maxBrightness: 10, maxVolume: 10 },
    fan: {
      allowedModes: [Array],
      changeableValues: [Object],
      fanRunning: false
    },
    temperatureMode: { feelsLike: true, air: true },
    specialMode: { autoChangeoverActive: true, emergencyHeatActive: false }
  },
  deviceClass: 'Thermostat',
  deviceType: 'Thermostat',
  deviceID: 'TCC-xxx’,
  userDefinedDeviceName: '3rd',
  name: '3rd',
  schedule: { scheduleType: 'Geofence' },
  isAlive: true,
  isUpgrading: false,
  isProvisioned: false,
  macID: ‘xxx’,
  deviceSettings: {},
  service: { mode: 'Up' },
  deviceRegistrationDate: '2019-08-13T20:14:14.54',
  dataSyncStatus: 'UnKnown',
  units: 'Fahrenheit',
  indoorTemperature: 80,
  outdoorTemperature: 84,
  allowedModes: [ 'Cool', 'Heat', 'Off' ],
  deadband: 0,
  hasDualSetpointStatus: false,
  minHeatSetpoint: 40,
  maxHeatSetpoint: 99,
  minCoolSetpoint: 40,
  maxCoolSetpoint: 99,
  changeableValues: {
    mode: 'Auto',
    autoChangeoverActive: true,
    emergencyHeatActive: false,
    heatSetpoint: 73,
    coolSetpoint: 80,
    heatCoolMode: 'Cool'
  },
  operationStatus: { mode: 'EquipmentOff' },
  smartAway: {
    active: false,
    timeOfDay: '00:00:00',
    durationInHours: 2,
    durationInDays: 0,
    lastUsedFormat: 'TimeOfDay',
    endsIn: '2000-01-01T00:00:00-05:00'
  },
  indoorHumidity: 50,
  indoorHumidityStatus: 'Measured',
  deviceModel: 'Round'
}
[8/1/2020, 11:10:36 AM] [HoneywellHome] TCC-xxx
[8/1/2020, 11:10:36 AM] [HoneywellHome] Allowed Fan Modes: Auto,On,Circulate
[8/1/2020, 11:10:36 AM] [HoneywellHome] Fan Mode: Auto
[8/1/2020, 11:10:36 AM] [HoneywellHome] Ignoring device named 3rd - TCC-xxx, Alive Status: true

I am sorry, I used some old code that included device.isProvisioned, which would ignore your devices. New beta should work for you. @roficas, Can you test it and let me know?

It is much better now... The thermostats are listed in the device list and I could control the fan. But when I tried to change the temperature, it did not actually changed (I'm double checking every command using the Honeywell app).
Also, there is a 400 error when I open the device in HomeKit (seems to be a refresh status).
[8/3/2020, 8:46:23 AM] [HoneywellHome] Set TargetHeatingCoolingState: 3
[8/3/2020, 8:46:24 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 79, heatSetpoint: 72
[8/3/2020, 8:46:24 AM] [HoneywellHome] {"mode":"Auto","thermostatSetpointStatus":"TemporaryHold","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":72}
[8/3/2020, 8:46:24 AM] [HoneywellHome] Request failed with status code 400
[8/3/2020, 8:46:33 AM] [HoneywellHome] Set Target Fan State: 0
[8/3/2020, 8:46:33 AM] [HoneywellHome] TargetFanState' 0 'Active' 0
[8/3/2020, 8:46:33 AM] [HoneywellHome] Sending request to Honeywell API. Fan Mode: Circulate
[8/3/2020, 8:46:33 AM] [HoneywellHome] {"mode":"Circulate"}
[8/3/2020, 8:46:34 AM] [HoneywellHome] [ 'Auto', 'On', 'Circulate' ]
[8/3/2020, 8:46:34 AM] [HoneywellHome] { mode: 'Circulate' }
[8/3/2020, 8:46:34 AM] [HoneywellHome] Fetched update for 2nd from Honeywell API: {"mode":"Auto","autoChangeoverActive":true,"emergencyHeatActive":false,"heatSetpoint":72,"coolSetpoint":79,"heatCoolMode":"Cool"} and Fan: {"mode":"Circulate"}
[8/3/2020, 8:46:34 AM] [HoneywellHome] "Auto"
[8/3/2020, 8:46:34 AM] [HoneywellHome] {"mode":"Circulate"}
[8/3/2020, 8:46:58 AM] [HoneywellHome] Set Target Fan State: 1
[8/3/2020, 8:46:59 AM] [HoneywellHome] TargetFanState' 1 'Active' 0
[8/3/2020, 8:46:59 AM] [HoneywellHome] Sending request to Honeywell API. Fan Mode: Auto
[8/3/2020, 8:46:59 AM] [HoneywellHome] {"mode":"Auto"}
[8/3/2020, 8:47:00 AM] [HoneywellHome] [ 'Auto', 'On', 'Circulate' ]
[8/3/2020, 8:47:00 AM] [HoneywellHome] { mode: 'Auto' }
[8/3/2020, 8:47:00 AM] [HoneywellHome] Fetched update for 2nd from Honeywell API: {"mode":"Auto","autoChangeoverActive":true,"emergencyHeatActive":false,"heatSetpoint":72,"coolSetpoint":79,"heatCoolMode":"Cool"} and Fan: {"mode":"Auto"}
[8/3/2020, 8:47:00 AM] [HoneywellHome] "Auto"
[8/3/2020, 8:47:00 AM] [HoneywellHome] {"mode":"Auto"}
[8/3/2020, 8:47:04 AM] [HoneywellHome] Set TargetHeatingCoolingState: 3
[8/3/2020, 8:47:04 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 80, heatSetpoint: 72
[8/3/2020, 8:47:04 AM] [HoneywellHome] {"mode":"Auto","thermostatSetpointStatus":"TemporaryHold","autoChangeoverActive":true,"coolSetpoint":80,"heatSetpoint":72}
[8/3/2020, 8:47:05 AM] [HoneywellHome] Request failed with status code 400
[8/3/2020, 8:48:07 AM] [HoneywellHome] Set TargetHeatingCoolingState: 3
[8/3/2020, 8:48:07 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 80, heatSetpoint: 72
[8/3/2020, 8:48:07 AM] [HoneywellHome] {"mode":"Auto","thermostatSetpointStatus":"TemporaryHold","autoChangeoverActive":true,"coolSetpoint":80,"heatSetpoint":72}
[8/3/2020, 8:48:08 AM] [HoneywellHome] Request failed with status code 400
[8/3/2020, 8:48:11 AM] [HoneywellHome] Set TargetTemperature:': 24
[8/3/2020, 8:48:11 AM] [HoneywellHome] Set HeatingThresholdTemperature: 22
[8/3/2020, 8:48:11 AM] [HoneywellHome] Set CoolingThresholdTemperature: 26.1
[8/3/2020, 8:48:11 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 79, heatSetpoint: 72
[8/3/2020, 8:48:11 AM] [HoneywellHome] {"mode":"Auto","thermostatSetpointStatus":"TemporaryHold","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":72}
[8/3/2020, 8:48:12 AM] [HoneywellHome] Request failed with status code 400
[8/3/2020, 8:48:28 AM] [HoneywellHome] Set TargetHeatingCoolingState: 3
[8/3/2020, 8:48:28 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 79, heatSetpoint: 72
[8/3/2020, 8:48:28 AM] [HoneywellHome] {"mode":"Auto","thermostatSetpointStatus":"TemporaryHold","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":72}
[8/3/2020, 8:48:29 AM] [HoneywellHome] Request failed with status code 400
[8/3/2020, 8:48:46 AM] [HoneywellHome] Set TargetHeatingCoolingState: 3
[8/3/2020, 8:48:46 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 79, heatSetpoint: 72
[8/3/2020, 8:48:46 AM] [HoneywellHome] {"mode":"Auto","thermostatSetpointStatus":"TemporaryHold","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":72}
[8/3/2020, 8:48:47 AM] [HoneywellHome] Request failed with status code 400
[8/3/2020, 8:48:56 AM] [HoneywellHome] Set TargetTemperature:': 24.5
[8/3/2020, 8:48:56 AM] [HoneywellHome] Set HeatingThresholdTemperature: 22
[8/3/2020, 8:48:56 AM] [HoneywellHome] Set CoolingThresholdTemperature: 27.2
[8/3/2020, 8:48:57 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 81, heatSetpoint: 72
[8/3/2020, 8:48:57 AM] [HoneywellHome] {"mode":"Auto","thermostatSetpointStatus":"TemporaryHold","autoChangeoverActive":true,"coolSetpoint":81,"heatSetpoint":72}
[8/3/2020, 8:48:57 AM] [HoneywellHome] Request failed with status code 400
[8/3/2020, 8:49:08 AM] [HoneywellHome] Set TargetHeatingCoolingState: 3
[8/3/2020, 8:49:08 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 81, heatSetpoint: 72
[8/3/2020, 8:49:08 AM] [HoneywellHome] {"mode":"Auto","thermostatSetpointStatus":"TemporaryHold","autoChangeoverActive":true,"coolSetpoint":81,"heatSetpoint":72}
[8/3/2020, 8:49:09 AM] [HoneywellHome] Request failed with status code 400

I will have to look. it may be how I am sending the settings, that might make it harder....

{
            "name": "HoneywellHome",
            "credentials": {
                "consumerKey": "token",
                "refreshToken": "refresh_tokey",
                "notice": "Keep your tokens a secret!"
            },
            "options": {
                "ttl": 60,
                "debug": true
            },
            "platform": "HoneywellHome"
        }

Also just noticed that your ttl is set to 60, I would move that up or you will get rate limit errors from Honeywell's API.

@roficas I think I found what we need to send possibly.
 changeableValues: {
    mode: 'Auto',
    autoChangeoverActive: true,
    emergencyHeatActive: false,
    heatSetpoint: 72,
    coolSetpoint: 79,
    heatCoolMode: 'Cool'
  },

emergencyHeatActive: false, I could be wrong but I will look a little more, before I add this and have you test it on the beta.

@roficas okay. the latest beta should work for you. can you try it and let me know?
Beta Version: 6.1.1-beta.5

Hey, thanks for keep working on this :)
I'm installing the new beta and will reply with the outputs. Meanwhile, what would be a good number for ttl? Actually, my current config does not have any options configured anymore - I have removed the entire config a few tests before and I only have what was created by the plugin once linked to Honeywell...

Opening the thermostat:
[8/4/2020, 9:57:38 AM] [HoneywellHome] Set TargetHeatingCoolingState: 3
[8/4/2020, 9:57:38 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 79, heatSetpoint: 72
[8/4/2020, 9:57:38 AM] [HoneywellHome] {"mode":"Auto","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":72}
[8/4/2020, 9:57:39 AM] [HoneywellHome] Request failed with status code 400

Trying to set a new temperature (twice):
[8/4/2020, 9:57:50 AM] [HoneywellHome] Set TargetTemperature:': 24
[8/4/2020, 9:57:50 AM] [HoneywellHome] Set HeatingThresholdTemperature: 22
[8/4/2020, 9:57:50 AM] [HoneywellHome] Set CoolingThresholdTemperature: 26.1
[8/4/2020, 9:57:50 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 79, heatSetpoint: 72
[8/4/2020, 9:57:50 AM] [HoneywellHome] {"mode":"Auto","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":72}
[8/4/2020, 9:57:51 AM] [HoneywellHome] Request failed with status code 400
[8/4/2020, 9:57:54 AM] [HoneywellHome] Set TargetTemperature:': 24
[8/4/2020, 9:57:54 AM] [HoneywellHome] Set HeatingThresholdTemperature: 22
[8/4/2020, 9:57:54 AM] [HoneywellHome] Set CoolingThresholdTemperature: 25.6
[8/4/2020, 9:57:54 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 78, heatSetpoint: 72
[8/4/2020, 9:57:54 AM] [HoneywellHome] {"mode":"Auto","autoChangeoverActive":true,"coolSetpoint":78,"heatSetpoint":72}
[8/4/2020, 9:57:55 AM] [HoneywellHome] Request failed with status code 400

The config was like this:
{
            "name": "HoneywellHome",
            "credentials": {
                "consumerKey": "xxx",
                "consumerSecret": "xxx",
                "refreshToken": "xxx",
                "notice": "Keep your tokens a secret!"
            },
            "platform": "HoneywellHome"
        }

@roficas has any version ever worked?

AFAI remember, the previous oficial version worked when I removed the device.isProvisioned myself.

@roficas can you post more logs? in debug so I can see more?

after everything is initialized (same logs as before), I open the thermostat and this is the output (in debug mode):
[8/10/2020, 10:17:06 AM] [HoneywellHome] Set TargetHeatingCoolingState: 3
[8/10/2020, 10:17:06 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 79, heatSetpoint: 72
[8/10/2020, 10:17:06 AM] [HoneywellHome] {"mode":"Auto","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":72}
[8/10/2020, 10:17:07 AM] [HoneywellHome] Request failed with status code 400

Then I tried to set the max temperature and got this output:
[8/10/2020, 10:18:20 AM] [HoneywellHome] Set TargetTemperature:': 24
[8/10/2020, 10:18:20 AM] [HoneywellHome] Set HeatingThresholdTemperature: 22
[8/10/2020, 10:18:20 AM] [HoneywellHome] Set CoolingThresholdTemperature: 25.6
[8/10/2020, 10:18:20 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 78, heatSetpoint: 72
[8/10/2020, 10:18:20 AM] [HoneywellHome] {"mode":"Auto","autoChangeoverActive":true,"coolSetpoint":78,"heatSetpoint":72}
[8/10/2020, 10:18:21 AM] [HoneywellHome] Request failed with status code 400

I don't know if this is not an issue, but I'm using Fahrenheit and it showed Celsius first...

The same happens when setting the lower temperature:
[8/10/2020, 10:20:24 AM] [HoneywellHome] Set TargetTemperature:': 24.5
[8/10/2020, 10:20:24 AM] [HoneywellHome] Set HeatingThresholdTemperature: 23.3
[8/10/2020, 10:20:24 AM] [HoneywellHome] Set CoolingThresholdTemperature: 25.6
[8/10/2020, 10:20:25 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 78, heatSetpoint: 74
[8/10/2020, 10:20:25 AM] [HoneywellHome] {"mode":"Auto","autoChangeoverActive":true,"coolSetpoint":78,"heatSetpoint":74}
[8/10/2020, 10:20:25 AM] [HoneywellHome] Request failed with status code 400

I hope this helps...

This may be a little confusing, but I tried several times to set the temperature then change the cooling mode (auto, fan circulate, fan on) and I noticed that the fan mode always works but the temperature completely ignores what I had set before.
[8/10/2020, 10:24:25 AM] [HoneywellHome] Sending request to Honeywell API. Fan Mode: Circulate
[8/10/2020, 10:24:25 AM] [HoneywellHome] {"mode":"Circulate"}
[8/10/2020, 10:24:26 AM] [HoneywellHome] Set Active State: 1
[8/10/2020, 10:24:26 AM] [HoneywellHome] TargetFanState' 0 'Active' 1
[8/10/2020, 10:24:26 AM] [HoneywellHome] Sending request to Honeywell API. Fan Mode: On
[8/10/2020, 10:24:26 AM] [HoneywellHome] {"mode":"On"}
[8/10/2020, 10:24:27 AM] [HoneywellHome] [ 'Auto', 'On', 'Circulate' ]
[8/10/2020, 10:24:27 AM] [HoneywellHome] { mode: 'Circulate' }
[8/10/2020, 10:24:27 AM] [HoneywellHome] Fetched update for 2nd from Honeywell API: {"mode":"Auto","autoChangeoverActive":true,"emergencyHeatActive":false,"heatSetpoint":70,"coolSetpoint":79,"heatCoolMode":"Cool"} and Fan: {"mode":"Circulate"}
[8/10/2020, 10:24:27 AM] [HoneywellHome] "Auto"
[8/10/2020, 10:24:27 AM] [HoneywellHome] {"mode":"Circulate"}
[8/10/2020, 10:24:28 AM] [HoneywellHome] [ 'Auto', 'On', 'Circulate' ]
[8/10/2020, 10:24:28 AM] [HoneywellHome] { mode: 'On' }
[8/10/2020, 10:24:28 AM] [HoneywellHome] Fetched update for 2nd from Honeywell API: {"mode":"Auto","autoChangeoverActive":true,"emergencyHeatActive":false,"heatSetpoint":70,"coolSetpoint":79,"heatCoolMode":"Cool"} and Fan: {"mode":"On"}
[8/10/2020, 10:24:28 AM] [HoneywellHome] "Auto"
[8/10/2020, 10:24:28 AM] [HoneywellHome] {"mode":"On"}
[8/10/2020, 10:24:39 AM] [HoneywellHome] Set TargetHeatingCoolingState: 3
[8/10/2020, 10:24:39 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 79, heatSetpoint: 70
[8/10/2020, 10:24:39 AM] [HoneywellHome] {"mode":"Auto","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":70}
[8/10/2020, 10:24:40 AM] [HoneywellHome] Request failed with status code 400
[8/10/2020, 10:24:42 AM] [HoneywellHome] Set TargetTemperature:': 23
[8/10/2020, 10:24:42 AM] [HoneywellHome] Set HeatingThresholdTemperature: 21
[8/10/2020, 10:24:42 AM] [HoneywellHome] Set CoolingThresholdTemperature: 25
[8/10/2020, 10:24:42 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 77, heatSetpoint: 70
[8/10/2020, 10:24:42 AM] [HoneywellHome] {"mode":"Auto","autoChangeoverActive":true,"coolSetpoint":77,"heatSetpoint":70}
[8/10/2020, 10:24:43 AM] [HoneywellHome] Request failed with status code 400
[8/10/2020, 10:24:45 AM] [HoneywellHome] Set Active State: 0
[8/10/2020, 10:24:45 AM] [HoneywellHome] TargetFanState' 0 'Active' 0
[8/10/2020, 10:24:45 AM] [HoneywellHome] Sending request to Honeywell API. Fan Mode: Circulate
[8/10/2020, 10:24:45 AM] [HoneywellHome] {"mode":"Circulate"}
[8/10/2020, 10:24:47 AM] [HoneywellHome] [ 'Auto', 'On', 'Circulate' ]
[8/10/2020, 10:24:47 AM] [HoneywellHome] { mode: 'Circulate' }
[8/10/2020, 10:24:47 AM] [HoneywellHome] Fetched update for 2nd from Honeywell API: {"mode":"Auto","autoChangeoverActive":true,"emergencyHeatActive":false,"heatSetpoint":70,"coolSetpoint":79,"heatCoolMode":"Cool"} and Fan: {"mode":"Circulate"}
[8/10/2020, 10:24:47 AM] [HoneywellHome] "Auto"
[8/10/2020, 10:24:47 AM] [HoneywellHome] {"mode":"Circulate"}
[8/10/2020, 10:24:47 AM] [HoneywellHome] Set Active State: 1
[8/10/2020, 10:24:47 AM] [HoneywellHome] TargetFanState' 0 'Active' 1
[8/10/2020, 10:24:47 AM] [HoneywellHome] Sending request to Honeywell API. Fan Mode: On
[8/10/2020, 10:24:47 AM] [HoneywellHome] {"mode":"On"}
[8/10/2020, 10:24:49 AM] [HoneywellHome] [ 'Auto', 'On', 'Circulate' ]
[8/10/2020, 10:24:49 AM] [HoneywellHome] { mode: 'On' }
[8/10/2020, 10:24:49 AM] [HoneywellHome] Fetched update for 2nd from Honeywell API: {"mode":"Auto","autoChangeoverActive":true,"emergencyHeatActive":false,"heatSetpoint":70,"coolSetpoint":79,"heatCoolMode":"Cool"} and Fan: {"mode":"On"}
[8/10/2020, 10:24:49 AM] [HoneywellHome] "Auto"
[8/10/2020, 10:24:49 AM] [HoneywellHome] {"mode":"On"}
[8/10/2020, 10:25:02 AM] [HoneywellHome] Set TargetHeatingCoolingState: 2
[8/10/2020, 10:25:02 AM] [HoneywellHome] Sending request to Honeywell API. mode: Cool, coolSetpoint: 79, heatSetpoint: 70
[8/10/2020, 10:25:02 AM] [HoneywellHome] {"mode":"Cool","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":70}
[8/10/2020, 10:25:04 AM] [HoneywellHome] [ 'Auto', 'On', 'Circulate' ]
[8/10/2020, 10:25:04 AM] [HoneywellHome] { mode: 'On' }
[8/10/2020, 10:25:04 AM] [HoneywellHome] Fetched update for 2nd from Honeywell API: {"mode":"Auto","autoChangeoverActive":true,"emergencyHeatActive":false,"heatSetpoint":70,"coolSetpoint":79,"heatCoolMode":"Cool"} and Fan: {"mode":"On"}
[8/10/2020, 10:25:04 AM] [HoneywellHome] "Auto"
[8/10/2020, 10:25:04 AM] [HoneywellHome] {"mode":"On"}
[8/10/2020, 10:25:04 AM] [HoneywellHome] Set TargetTemperature:': 25
[8/10/2020, 10:25:04 AM] [HoneywellHome] Sending request to Honeywell API. mode: Auto, coolSetpoint: 79, heatSetpoint: 70
[8/10/2020, 10:25:04 AM] [HoneywellHome] {"mode":"Auto","autoChangeoverActive":true,"coolSetpoint":79,"heatSetpoint":70}
[8/10/2020, 10:25:05 AM] [HoneywellHome] Request failed with status code 400
[8/10/2020, 10:25:08 AM] [HoneywellHome] Set Active State: 0
[8/10/2020, 10:25:08 AM] [HoneywellHome] TargetFanState' 0 'Active' 0
[8/10/2020, 10:25:08 AM] [HoneywellHome] Sending request to Honeywell API. Fan Mode: Circulate
[8/10/2020, 10:25:08 AM] [HoneywellHome] {"mode":"Circulate"}
[8/10/2020, 10:25:10 AM] [HoneywellHome] Set Target Fan State: 1
[8/10/2020, 10:25:10 AM] [HoneywellHome] TargetFanState' 1 'Active' 0
[8/10/2020, 10:25:10 AM] [HoneywellHome] Sending request to Honeywell API. Fan Mode: Auto
[8/10/2020, 10:25:10 AM] [HoneywellHome] {"mode":"Auto"}
[8/10/2020, 10:25:10 AM] [HoneywellHome] [ 'Auto', 'On', 'Circulate' ]
[8/10/2020, 10:25:10 AM] [HoneywellHome] { mode: 'Circulate' }
[8/10/2020, 10:25:10 AM] [HoneywellHome] Fetched update for 2nd from Honeywell API: {"mode":"Auto","autoChangeoverActive":true,"emergencyHeatActive":false,"heatSetpoint":70,"coolSetpoint":79,"heatCoolMode":"Cool"} and Fan: {"mode":"Circulate"}
[8/10/2020, 10:25:10 AM] [HoneywellHome] "Auto"
[8/10/2020, 10:25:10 AM] [HoneywellHome] {"mode":"Circulate"}
[8/10/2020, 10:25:11 AM] [HoneywellHome] [ 'Auto', 'On', 'Circulate' ]
[8/10/2020, 10:25:11 AM] [HoneywellHome] { mode: 'Auto' }
[8/10/2020, 10:25:11 AM] [HoneywellHome] Fetched update for 2nd from Honeywell API: {"mode":"Auto","autoChangeoverActive":true,"emergencyHeatActive":false,"heatSetpoint":70,"coolSetpoint":79,"heatCoolMode":"Cool"} and Fan: {"mode":"Auto"}
[8/10/2020, 10:25:11 AM] [HoneywellHome] "Auto"
[8/10/2020, 10:25:11 AM] [HoneywellHome] {"mode":"Auto"}

@roficas okay I will keep looking into this.

@roficas lets try 6.1.3-beta.8

I'm out of town so I'll be able to try only next week.
Thanks for keep working on this.

I'm out of town so I'll be able to try only next week.
Thanks for keep working on this.

Sounds good.

@roficas once you are able to try this, if you can post the output for the latest beta. Then if you can install and older version before I had the fans feature, when you said it was working. and also post that output. Both in debug mode.

I have release v6.2.0, which should support the TCC devices. Once you can test this release and confirm that it is working for you, let me know.


[BACKLOG-36168-latest-9-sep]

:white_check_mark: Build finished in 7m 2s
Build command:
mvn clean verify -B -e -Daudit -amd -pl plugins/repositories/core

:exclamation: No tests found!
:information_source:  This is an automatic message

Please revise the commit message so that the jira tag matches the jira ticket and there is an appropriate description of the changes.

Also please resolve the issues noted in the SonarQube analysis


all: Completely remove external block building tool, build blocks internally, sign transactions internally

Completely removes all references to b11r tool and builds the blocks internally.
Also all transaction types are now signed internally.

Btw, this gives almost a 2x speed-up on my laptop, running fill (until Shanghai):

d34385b2b150af8e802d9cbef9fe1cac165db1b1: ~17s
86d8a818a229e32e33bf388de89a12af891a34e6: ~9s


Failed to compile with zksolc, LLVM IR generator definition pass error

Could someone help me to resolve the issue. I install the zkSync foundry compiler and right now i can't run any Test!!!!!!!!

@Senya123 can you please post this to the foundry-zksync repo rather than here. As this repo is for hardhat plugins.
Please also provide more details in the issue so we can help debug. Like steps to reproduce and a link to the repo.
Thanks.


pull request for e2e test at 11/23/2016 03:56:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Maintenance: Update SDK/Golang Version

As part of periodic Steampipe maintenance all plugins should be upgraded to use SDK 1.8.2 as well as golang v1.17.

Done in #10


Change the base image from micro to minimal

The micro image does not have the necessary certificates to make requests to AWS API endpoints.

/lgtm


Allow models to execute on different warehouses

Resolves PECO-1182
Description
Allows models in a dbt project to run on different SQL warehouses.
The available warehouses are specified as named values in the dbt profile.
The configuration for a model can specify by name which warehouse it should run on.
Checklist

[x] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.

Out of curiosity, how did you validate?  Do you have tests that are uncommitted, or did you look at the logs of some existing tests?

I verified by modifying one of the integration tests and stepping through the code as well as adding some temporary print statements. I validated the open session parameters for a model that specifies a different warehouse than the one in the profile.

Stylistically looks good, and to the extent I can follow, the logic looks right.  Assuming we go this way, please add unit tests for the new logic, and at least 1 functional test that uses the compute definitions from the existing profiles.

Stylistically looks good, and to the extent I can follow, the logic looks right. Assuming we go this way, please add unit tests for the new logic, and at least 1 functional test that uses the compute definitions from the existing profiles.

Per discussion with dbt, we're going to try to finish migrating to their functional tests, so no new integration tests.

Definitely going to add tests if this is the implementation we decide to use.  That's why its a draft PR at this point


CSS Paint API

Spec: https://drafts.css-houdini.org/css-paint-api/
Chrome: https://www.chromestatus.com/features/5685444318593024
Edge: ?
FireFox:
WebKit: https://webkit.org/status/#specification-css-painting-api-level-1

+1

Here are some useful links:

https://github.com/GoogleChrome/houdini-samples
https://developers.google.com/web/updates/2016/05/houdini

Now available at https://caniuse.com/#feat=css-paint-api


[SPARK-46676][SS] dropDuplicatesWithinWatermark should not fail on canonicalization of the plan

What changes were proposed in this pull request?
This PR proposes to fix the bug on canonicalizing the plan which contains the physical node of dropDuplicatesWithinWatermark (StreamingDeduplicateWithinWatermarkExec).
Why are the changes needed?
Canonicalization of the plan will replace the expressions (including attributes) to remove out cosmetic, including name, "and metadata", which denotes the event time column marker.
StreamingDeduplicateWithinWatermarkExec assumes that the input attributes of child node contain the event time column, and it is determined at the initialization of the node instance. Once canonicalization is being triggered, child node will lose the notion of event time column from its attributes, and copy of StreamingDeduplicateWithinWatermarkExec will be performed which instantiating a new node of StreamingDeduplicateWithinWatermarkExec with new child node, which no longer has an event time column, hence instantiation will fail.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
New UT added.
Was this patch authored or co-authored using generative AI tooling?
No.

cc. @zsxwing @viirya @anishshri-db Please take a look.
Also cc. @cloud-fan Maybe this does not require streaming expertise, hence asking for a review.
Thanks in advance!

As the finder of the bug repro and a curious learner of Catalyst I'd really appreciate it if anyone can tell me

Where is this canonicalized spark plan constructed in this simple test case, or why do we even bother to create such a plan for spark physical plans??
Why without select (i.e. Project), the query runs successfully? It should still go through this canonicalization process right?
Thanks in advance!

There are some optimization rules being applied to the physical plan to reuse the shuffle/subquery in batch side across microbatches (they are unlikely changed between microbatches unless the batch source has updated). One example is ReuseExchangeAndSubquery.
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/reuse/ReuseExchangeAndSubquery.scala
This rule leverages canonicalized plan to compare with cached subtree (plan). It does not require the plan to be exactly same - as long as they are identical without cosmetic.

cc. @zsxwing @viirya @anishshri-db @cloud-fan Friendly reminder.

@anishshri-db Thanks for reviewing!
cc. @zsxwing @viirya @cloud-fan @HyukjinKwon Mind having a quick look given @anishshri-db reviewed this already? Thanks in advance!

GA failure is just a linter issue - Sphinx version.

If some attribute metadata streaming is not cosmetic, shall we keep them during canonicalization?

@cloud-fan Do you suggest retaining metadata selectively, or keep all metadata? For event time column metadata I guess it's unlikely to have a side effect, but I'm not sure about propagating all metadata.

Do you suggest retaining metadata selectively, or keep all metadata?

I mean the metadatas that are not cosmetic, and I think even time metadata is one of them.

@cloud-fan
Ah OK. Thanks for the suggestion. I can look into how to propagate event time metadata only. Will ping you again once I'm done with it.

@cloud-fan
It does not seem to be easy fix - I have a hard time debugging on this:
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/EventTimeWatermarkExec.scala
eventTime in the constructor does not seem to match with child.output via semanticEquals. Does canonicalization care about making child.output and attribute referring child.output in sync after canonicalization? Otherwise I expect the fix to be very involved and current fix of the PR sounds to me as reasonable workaround.

Yes, see https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/QueryPlan.scala#L606-L610

There are two kinds of expr IDs: 1) to reference attributes from children. 2) to indicate the output of the plan node.
After canonicalization, the output expr IDs for each plan node (if they have output columns, such as Project) will be normalized to 0, 1, 2, .... The reference expr IDs will be normalized to the ordinal of the matching column from children output columns.  So ideally they can match, as the ordinal 0 means the first output column, whose expr ID should also be 0. However, it's possible that an attribute is both a reference and a output, e.g. Project(a#1 AS aa#3, b#2). So it seems we can't find the event column on a canonicalized plan.

OK, looks like we have a case where propagating event time metadata on canonicalization won't help. Given that current fix could handle such case as well, shall we allow the current fix as it is?

@cloud-fan Mind having another look, please? The failure in GA is only from doc generation (sphinx version), which is a known one.

Thanks all for reviewing! Merging to master/3.5.


Wizard opening on Step 5

After creating a plan, if user selects Add plan button the wizard opens at step 5 with validation running and then shows validation success with no plan name.

Sounds like we've determined this is actually a pf4 modal bug that needs to get fixed upstream. @ibolton336 do you have a link to the issue you filed upstream so we can add it here?

I actually think the bug was fixed upstream. We just havent updated out version of PF4.

https://github.com/patternfly/patternfly-react/issues/1845


ODCode128Reader: use FNC1 to determine if GS1, remove assumeGS1 (#265)

Closes #265
Part-implements #214
For Code128, uses position of FNC1 to determine if GS1 (or AIM) barcode rather than assumeGS1 hint which is no longer used and is marked as deprecated in DecodeHints.
Also sets new symbologyIdentifier attribute added to "Result.h" (implemented for Code128 only for now).
Adds processing of optional  ".result.txt" files in "test/samples" that contain keyed Result attributes and values for additional validation.
Implementation of further symbology identifiers will follow in subsequent PRs (also checking of other Result attributes in ".result.txt" files).

Since you've been tuning your patch a few times (it seems): do you consider the current version final?
I'd merge it as is but would like to suggest to include only those metadata fields in future .result.txt files that are non-default (like you did for all of the new ones except the first 2).

Hi, thanks, removed the non-default fields as requested. Plus fixed some sp -> tab formatting.
Yes the previous force-pushes were me forgetting to add stuff (the ".result.txt" files - 2 goes) and remove stuff (the "convertFNC1" field from "ODCode128Reader.h"). In future will annotate any force-pushes and add comment indicating ready for review.
This PR is ready for review.

Awesome. Thanks as always.


UV's gone

Hi so I am trying to import my usd mesh from maya. The problem is when i load it into unity my mesh goes completely black. If i name my uv set map1 I am able to get textures if i import st. The problem then is that there seems to be padding along the uv seems...
I am completely stuck on what this could be. Anyone got a suggestion?

The only current option is to unwrld the verts along the seam in your source mod.
There is an open feature request to dynamically unwrld on load, which is a high priority for the next release.
Similarly we plan enable import of "st" by default in the future. The problem here is that Maya must not have exported a material with your mesh, if it had, the UV would have been imported automatically into Unity.
Sorry for the trouble!

Ow okey that sucks. any estimate on when that next release is? We are nearing production and would love to have the USD pipeline up for that.
Anyways, Thank you for the answer! :)

We have no ETA on the next release yet, but we are hoping for a faster turnaround than the previous release. We work publicly, so when the fix lands in dev, you could start experimenting with it. This would actually be super helpful to be sure we are fixing your problem correctly.
For a faster fix, you could modify the mesh importer and either (a) implement the real fix of unwelding verts or (b) take the easy route of just completely converting the mesh to triangle soup when the UV data is face varying. Note that changing the mesh topology may have knock-on effects, which is why we wanted to avoid it initially. If you end up doing (a), a pull request would be great ;)
Also, please keep in mind that this is a preview release(!), so building a real production on it will come with inevitable pain & speed bumps.
We very much appreciate filing bugs & issues, thanks!
cc @mfe @lucillecaillaud

This is actually a duplicate of #75, closing


Refresh control capability

This library has been excellent. Except there is no ability to add a refresh control to the scroll views. I would like to be able to refresh my feeds with the refresh control. Is there a way to do this?

@harrisonas18 I am glad you liked it.
I added tp_scrollViewDidLoad to TPProgressDelegate to obtain the overlayScrollView. So you can use it to add refreshController or whatever reason. I already added implementation to the Example project with UIRefreshControl but you can use other libraries such as MJRefresh or custom.
See updated TPProgressDelegate:
public protocol TPProgressDelegate{
    func tp_scrollView(_ scrollView: UIScrollView, didUpdate progress: CGFloat)

    //New method to get overlayScrollView
    func tp_scrollViewDidLoad(_ scrollView: UIScrollView)
}


Unable to load local js file into react componet

What i am trying to do:
adding vidyoConnector.js script to a react component in order to create a WebRTC instance with vidyo
What is happening:
instead of adding the particular vidyoConnector.js file it loads index.html file because of which i get an unexpected token < error in console.

i am using react-async-script-loader to load this vidyoConnector script.

Also tried to add the script using Weback addAssetPlugin but ended up breaking the Build.
What i am expecting :
Any best approach to load a library file into the component which has its dependency.
Note
The Vidyo library has been written in jquery and hence do not support the ES6 modular pattern hence please help me with any best approach to achieve the same.
Please find below the screenshot for above issue:

This is an issue tracker for issues with the react-boilerplate project itself. Questions about your specific project are better suited for StackOverflow, you'll likely get answers more quickly there! (you can use the react-boilerplate tag on SO)

thank you for the assistance


add 'indeterminate' value in haeder checkbox for selectable table ele…

…ments

[x] I have tested my component
[ ] I have updated the documentation or there is no documentation needed

Libraries that use the DS (need to merge first)

[ ] BCF Components
[ ] BIMData Components
[ ] Building maker

Repos that use the DS (and that I need to check after libraries have been merged)

[ ] Viewer
[ ] Platform
[ ] SDK
[ ] Marketplace
[ ] Documentation

:tada: This PR is included in version 2.1.0-rc.28 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix RBAC and CRDs in k8s template

Describe what this PR does and why we need it:
This PR fixes two issues with the K8s template:

it adds the jobstates resource to the asb-auth ClusterRole
it fixes the copy&paste error in the bundlebindings and bundleinstances CRDs

@pst There is one change that I'm aware needs to be made, removing jobstates. Once that is made we should be able to merge this.


Made Object.hashAll and Object.hashAllUnordered accept nullable lists

Fixes #48094

Review in https://dart-review.googlesource.com/c/sdk/+/226806

Closing as per review comments in https://dart-review.googlesource.com/c/sdk/+/226806


Adding support for bytea columns

Firstly, thank you for your brilliant work.
After using your package to access some of the functionality that the core laravel packages do not possess, I have discovered that even your package does not cater for Bytea columns.
As per this comment https://github.com/laravel/framework/issues/10847#issuecomment-512612353  (which I have tested locally) and is available in the fork https://github.com/Rocketseed-Development/laravel-postgresql-enhanced.
I propose adding the following function to PostgresEnhancedConnection.php
`
/**

Modify the bindValues function to cater for Bytea

@param \PDOStatement $statement
@param Array $bindings
@return void
*/
public function bindValues($statement, $bindings)
{
foreach ($bindings as $key => $value) {
$statement->bindValue(
is_string($key) ? $key : $key + 1,
$value,
is_int($value) || is_float($value) ?
PDO::PARAM_INT :
($value === null || ctype_print($value) ? PDO::PARAM_STR : PDO::PARAM_LOB)
);
}
}
`

My expressions package has a value type. Can you try whether using the value in binary mode will solve the problem`
new Value('....', binary: true)

My expressions package has a value type. Can you try whether using the value in binary mode will solve the problem`
new Value('....', binary: true)

Thank you for your reply.
I added your other package tpetry/laravel-query-expressions to my project and defined the Bytea field as explained.
Yes. The binary mode does seem to solve the problem with inserting into the table.
I'm currently running some more tests just to make sure that the stream can be converted back to an image

Awesome, so it works as expected.


Is this project still alive - ping?

HDFS on k8s is pretty interesting, but from the last commits it looks like this project has been abandoned - is that the case?

Based on having no activity for a year, and the fact that their helm repository is dead
$ helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com/
Error: repo "https://kubernetes-charts-incubator.storage.googleapis.com/" is no longer available; try "https://charts.helm.sh/incubator" instead

I would assume this project is dead.


Bounty: Implement DLEQ proofs for client-side mint signature validation

This is a bounty offered by the Nodesignal Podcast and the developer who provides this functionality will receive a 250,000 sats bounty. More Information about the bounty program can be found here:
https://nodesignal.space/spenden-bitcoin-bounties/
Bounty goals
The goal of this bounty is to implement discrete log equality (DLEQ) proofs in Cashu.
This will enable three concrete things:

It will be possible for user Alice to make sure that the token they received from the mint Bob was indeed signed by them and not by a man-in-the-middle.
Alice can be sure that Bob has indeed used a the private key for signing their token that it had used, say, the day before. Otherwise, Bob could secretly use a special private key for every single token they sign, undermining the privacy of the entire setup by collapsing the anonymity set to 1.
In combination with P2SH, this will enable secure offline token transfers from Alice to Carol without Carol having to redeem tokens immediately to be sure that the signatures haven't been forged by Alice.

Cryptography
To quote from the original gist of Ruben Somsen (note that Alice and Bob have been swapped below because in the notation of Cashu, Alice is the user and Bob is the mint):
The protocol also has one additional weakness that can be addressed. Bob can't be certain that C' was correctly generated and thus corresponds to a*B' . Alice can resolve this by also supplying a discrete log equality proof (DLEQ), showing that a in A = a*G is equal to a in C' = a*B'. This equality can be proven with a relatively simple Schnorr signature, as described below.
Step 1
These steps occur while Bob the mint returns the blinded signature C'
Bob:
 r = random nonce
R1 = r*G
R2 = r*B'
 e = hash(R1,R2,A,C')
 s = r + e*a
return e, s

Step 2
The wallet (Alice) validates DLEQ proofs once it receives the blinded signature:
Alice:
R1 = e*A - s*G
R2 = e*C'- s*B'
e == hash(R1,R2,A,C')

If true, a in A = a*G must be equal to a in C' = a*B'

Step 3
When a token is transferred from Alice to Carol, Carol executes the same steps as Alice in Step 2 to validate that the tokens from Alices are indeed signed by Bob.

There is a sign error in the verification, Step 2. (confirmed it with waxwing)
R1 = e*A - s*G = -r*G R2 = e*C'- s*B' = -r*B'
So the DLEQ proof would fail. To easily correct it, we can replace the sides in the subtractions.
`
Alice:
R1 = sG - eA
R2 = sB' - eC'
e == hash(R1,R2,A,C')
If true, a in A = aG must be equal to a in C' = aB'
`

Congratulations for the bounty @moonsettler!


Camera tilts globe up instead of down

The first middle mouse drag after clicking the home button tilts the globe up instead of down.
It seems like it might be dependent on the screen aspect ratio somehow?
It happens every time in a window like this (width > height):

But none of the time in a window like this:

I just started to run into this too, I swear we fixed it at some point, maybe it's a regression with the new zoom behavior?  CC @bagnell

@bagnell, any chance you can look at this sometime soon?  It's really annoying.

Also see #5733