Feature/python3 support

Enabled Python3 support for badgecheck thus far.  This includes 'requiring' a fork/branch of pydux that is not currently merge into their master.  I plan to keep an eye on this and update setup.py and requiremetns.txt as appropriate when the time comes.
tox tests pass.

Approving merge into feature/python3-support branch for mergeing


plus-one dependency tracking does not handle custom rules

The plus-one reduced classpath is implemented using an aspect that propagates along deps and exports. This doesn't work with custom rules that declare a custom attribute and call java_common.compile directly.

We can work around this by exporting the custom dependencies. This is not ideal for all cases though.

One potential solution is to expose a provider (maybe PlusOneDeps itself) so that custom rules can report their direct dependencies.

@jdai8 I'm not sure I fully follow your idea. Any chance you can make a small POC PR to demonstrate what you have in mind?

Consider a custom rule my_java_rule with a custom_dep attribute:
def my_java_rule_impl(ctx):
  ...
  java_info = java_common.compile(
    source_files = ctx.attrs.srcs,
    deps = [ctx.attr.custom_dep[JavaInfo]],
  )

  return [java_info]

my_java_rule(
  name = "foo",
  ...
  custom_dep = "//:second_order_dep",
)

scala_library(
  name = "bar",
  srcs = ...,
  deps = [
    ":foo",
  ]
)

If we use the plus-one mode, I'd expect second_order_dep to be on the classpath for bar, but it's not.


cmd/gc: unexplained allocation for convT2I

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go version devel +2bf7034 Mon Apr 25 16:18:10 2016 +0000 darwin/amd64

What operating system and processor architecture are you using (go env)?

darwin/amd64

What did you do?

See attached typescript. I do not understand why line 28, the call to sort.Sort, is allocating. It is in a call to convT2I but a, a.r, and the slice a.r[i] points to are already on the heap.   (You can tell just by looking at the generated assembly and see what the 3rd arg to convT2I is.  If it is 0, then it allocates.  If it is a pointer to a stack temp, it doesn't.)
With -m, we get (among other reports):
tmp3.go:6: sortable(a) escapes to heap
tmp3.go:10: f2 sortable(a) does not escape

So I think this has something to do with the analysis.  Maybe because quickSort is recursive and escape analysis gives up?
@dr2chase

Was just looking at this, decided (in the process) that the explainer (-m -m) could use a bit more work (did not finger the call properly for the escape at line 28 -- it is to Sort).
And the short answer is "you passed the interface to Sort, and Sort was recorded as escUnknown, so it escaped".  The longer answer is "and Sort contains a call to quickSort which is recursive, and escape analysis punts on recursive functions, and thought I did work on a CL for not punting, it was very, very fragile and did not produce much benefit, so I let it get pretty stale".  I will try to revive that CL and see if it helps here at all -- if it does, that raises its priority, and if not, then not.

Did a bit more work and brought the recursive-function-nest-escape-analyzer forward, and that by itself was not enough.


First "swipe"-animation is missing in Tab Bar with react-swipeable-views

The issue is related to the Material UI Tab Bar with multiple Tabs and the react-swipeable-views.
The react-swipeable-views provides slide animation and a swipe gesture on touch screen devices. react-swipeable-views is already mentioned on the material-ui component library itself.
I hope that someone will be able to solve the below explained issue.
Current Behavior 😯
The first "swipe" animation when selecting another tab (mouse click on other tab name) is missing. All further animations will appear.
Expected Behavior 🤔
The user expects the "swipe" animation on all Tab switches.
Steps to Reproduce 🕹
The issue exists in the component library on the homepage as well. You can see it here: https://material-ui.com/components/tabs/#full-width
Steps:

Tab bar and swipeable views are loaded and one tab is selected initially
Select another tab (with mouse click)
BUG -> There is no "swipe"-animation.
From now on the animation will appear when you select other tabs

Context 🔦
I am facing exact the same issue on my project. But furthermore I am using React (obviously), TypeScript and NextJS for Server Side Rendering.
Your Environment 🌎

`npx @material-ui/envinfo`
    System:
    OS: macOS 11.1
  Binaries:
    Node: 14.3.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.11 - ~/Projects/Spozing/spozing/frontend-booking-agent/node_modules/.bin/npm
  Browsers:
    Chrome: 88.0.4324.96
    Edge: Not Found
    Firefox: 85.0
    Safari: 14.0.2
  npmPackages:
    @material-ui/core: ^4.11.3 => 4.11.3
    @material-ui/icons: ^4.11.2 => 4.11.2
    @material-ui/lab: ^4.0.0-alpha.57 => 4.0.0-alpha.57
    @material-ui/styles:  4.11.3
    @material-ui/system:  4.11.3
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react: ^17.0.0 => 17.0.0
    react: ^17.0.1 => 17.0.1
    react-dom: ^17.0.1 => 17.0.1
    typescript: ^4.1.3 => 4.1.3

Duplicate of #22351

You can pass initial tabs value props  value={0}


Remove Non-Normative JSON Schema Examples

Closes https://github.com/decentralized-identity/presentation-exchange/issues/312

Ultimate Problem
The spec's examples included non-normative json schema for the filter property
Solution

Remove formatMinimum and formatMaximum from the examples
Add text explaining JSON Schema extensions and calling out that Holders SHOULD gracefully handle additional/unknown keywords.

This is a SHOULD in the JSON Schema spec, so that's what I went with here

I will update https://github.com/decentralized-identity/presentation-exchange/pull/311 after merge


Cannot store numeric LocalStorage data

localStorage.setItem("patchTimestamp",<PHONE_NUMBER>);
console.log(localStorage.getItem("patchTimestamp")); // logs "null" on Android, "undefined" on iOS

Stringifying the number value before setting it works as expected.

This issue was actually related to storing numeric data, so renamed the issue and  updated the description.

A fix has been merged and will be available in Tabris 1.1.0.


setup cob4-7

added arms configuration
commented head and sensorring

this PR requires https://github.com/ipa320/cob_calibration_data/pull/142
@cagbal @ipa-rmb FYI

@ipa-rmb @ipa-bfb @cagbal
please review - it won't get merged otherwise
@ipa-jba @ipa-fez

I could not understand that Johannes mentioned a cob4-2 robot, but this is about cob4-7. Is this the robot which will stay with us?

you need to get to know your robots :wink:


Add a note about the 8A lower limit to the readme

Hi Thomas,
Thank you very much for the work you did here! I was able to reuse the research you did and the ESP configuration. (I adapted the HA part to my needs).
I noticed that the wallbox refuses to set a limit lower than 8A (and saw on the HA forums you encountered the same behaviour). I added a note to the readme about this, because at first I thought something wasn't working correctly.
Some more info: If I limit the current in my car to 6A (and put no restriction on the wallbox), charging works as expected so this is definitely an issue (or setting) on the wallbox. I attached a utp cable to it and was able to verify that the "limit" field in the local wallbox API dropped to 0 as soon as I set something lower than 8.

Thanks!

Thanks for testing that out with the car and wallbox. My car doesn't allow me to configure these items and I don't have a UTP cable attached to the wallbox so I couldn't figure out where the limit came from.


fixes twitter/twemoji/issues/284

See #284

Sorry, while the spec does include keywords like "revolver", the visual consensus around U+1F52B is the "water pistol" interpretation.

FWIW, Emojione provides both graphics. Due to a probable veto by Apple, Unicode will probably not RGI a solution for the dilemma unless proven popular. I suggest, like the Pirate Flag, you add two custom ZWJ sequences: 🔫💥 for a lethal weapon and 🔫💦 for a toy. (The base of an emoji sequence always comes first, i.e. goes on the left, the determiner comes second after the glue, i.e. on the right, otherwise the common orientation of affected emojis would suggest the reverse order 💥🔫 and 💦🔫 or visually better 💧🔫.) Provide both in the emoji picker on the website and hide the default 🔫 without a determiner, revisit the issue in two years time.

So, @n8downs ,
you are saying you are mantaing a implementation of the unicode standard, while breaking it?
Why should we use a non-standard font, when emojione has stated that they will support standard?
Please reconsider this, you are creating a serious precedent. Characters can't change meanings.

@ArmeF97, respectfully, I'm not sure that the standard is as cut and dry as you're making it out to be. Regarding visual representations, the spec says that "[w]hile the shape of the character can vary significantly, designers should maintain the same “core” shape, based on the shapes used mostly commonly in industry practice."
If you feel that EmojiOne's inclusion of both the lethal weapon and toy images in their set is the correct behavior, I'd encourage you to use their set over ours.
I think @Crissov's idea to create separate ZWJ sequences for the two interpretations is a good one, but I don't foresee Twemoji adding these custom sequences in the near future.

To be fair, the spec was changed after the fact, because of this very issue and vendors (who make up a major of the Unicode Consortium) wanting to sanction their actions.
Custom sequences are perfectly fine and Twitter has done it before. Why do you not consider doing it again?


Smali decompilation errors

JADX is by far the best tool that I found so far to analyze APK files.
I tried several others which dont work at all or give less useful results.
It is a high quality project. Thanks for your work.
However I have a problem.
Just the function which I'am interested in has in the body:
{
        // Method dump skipped, instructions count: 5131
        throw new UnsupportedOperationException("Method not decompiled:  .......");
}

5131 instructions skipped ?
First I would like to understand why this happens.
I can get the Smali code from APK Tool and it looks quite reasonable to me.
But reading Smali manually is cumbersome.
My second question is if anything can be done to fix this, so that this code can be decompiled to Java.
If it would be partly decompiled with some question maks or comments were problems occur would be better than having 5131 instructions skipped entirely.
And my last question is: If this is not possible is there any tool which I can feed with a Smali file and which gives me more human readable output ? All tools which I tried so far here on Github were useless to get this code decompiled.
Here is a link to the Smali file :
https://netcult.ch/elmue/Smali.txt
The function starts at text line 921. It ends at line 8495
It is entirely skipped
And here is the link to the APK file :
https://netcult.ch/elmue/Test.apk.zip
(I had to add a ".ZIP" to the filename otherwise the server will not allow to download the file)

谢谢您的来信，您的邮件已收到！

@Elmue
At first, you can change code comments level option to debug it will show method instructions in fallback mode and this method will be very long, so it will be very hard to understand (that's the reason why it is hidden).
Next you can change show inconsistent code option to true it will show java code for this method but be careful: this code is incorrect in some way because jadx failed to restore code structure at some point.
For your case: looks like method is very big and uses too much try/catch blocks, so it is hard to restore, sorry 😞
And as a final solution, you can enable generate methods cfg graphs option to dump methods CFG in .dot format and next view using any graphviz app.

OK. Thanks for your answer. I will try that.
But two things I don't understand:

because jadx failed to restore code structure at some point.
Why does it fail at all in restoring the code ?
Isn't it just following a rule to translate Smali into Java ?
What is the problem?

method is very big and uses too much try/catch blocks

What does "too much" mean?
If there are 1000 Smali try - catch blocks why can this not be translated into a Java code with 1000 try - catch blocks?
Did you set a limit there?
And why?
If there is a huge routine in Smali it is obvious that a huge routine in Java will come out.
But this should not be the problem of JADX.
It is my job then to understand this routine.
I could copy that to a text editor and remove all code does not interest me and focus and what I want to understand.
But I prefer to have a routine with 1000 try - catch blocks than having nothing.

Why does it fail at all in restoring the code ? Isn't this a straight foreward process to translate Smali into Java like what a compiler does? What is the problem?

@Elmue Nothing can be more far away from the truth than this statement. The main problem is that the compiler does not stop after translating Java code to DEX byte code, instead it starts to optimize the code that means it merges duplicate statements if it's complex analysis shows that this has no effect. It moves blocks around and so on so that back tracking which code blocks belong to which if-else or try-catch block (especially when they are nested) can get pretty complicated. Take for example the example I posted in #1262. It is pretty small but complicated to decompile. Now imaging such a problem when it comes to try-catch blocks nested in two or three levels into another.
Additionally DEX code of some apps is modified again after the compiler has finished by code obfuscators. And finally some apps contain DEX code that was never built from Java code. Kotlin and other languages that are directly translated to DEX byte code can generate code that is pretty hard to decompile.

@Elmue you can also check GDA decompiler (it works for your method, using some gotos through) also JEB can be useful (I didn't check it).
Anyway, I don't think jadx will be fixed for your case soon, also this is a known issue with try/catch, so I will close this issue.
@jpstotz thank you for detailed reply! I always struggle to explain why decompilation is hard, but you did it quite well.
I think I need to state that jadx can't decompile 100% of code in readme, so people will be warned.

Hello
This is already closed. I hope you still read it.

Take for example the example I posted in #1262.

OK. I understand the problem.
These 2 if block are impossible to restore into normal Java code.
But have absolutely no problem that incase a code cannot be respoved into the if - else structure that it is simply displayed with goto's inside. This is far better than an error message that 5000 instructions could not be decompiled at all.

simply displayed with goto's inside. This is far better than an error message

@Elmue sure. I plan to implement less verbose fallback option and also working on fixing incorrect CFG with gotos :+1:

And thank you for the hint to try GDA. It is lightnig fast and works very well.


[Release] sdk/resourcemanager/computeschedule/armcomputeschedule/0.1.0

https://github.com/Azure/sdk-release-request/issues/5495

@Mitse1n first release need to add pipeline first

/azp run prepare-pipelines

/azp run go - armcomputeschedule - ci

/check-enforcer override


As a CIF administrator, I'd like to see a metabase view of upcoming action items, so I know what needs my attention

Description:
A list of upcoming milestones/reports due etc

Widget Feature: similar to what was proposed for external users, we’d like to have this feature offered internally that will show at the side/top of screen what’s outstanding, and upcoming

Acceptance Criteria:
Given
When
Then
Development Checklist:

[ ] Checklist item
[ ] Checklist item
[ ] Checklist item
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

@dleard This could be the topic of the hands-on metabase training we were talking about today.
Building a view of reporting requirements, with conditional formatting, sorted by due date, something like that?

I think this can be 2 metabase views:

what's outstanding, in order of what is the most late
what is upcoming sorted by what due date is the closest

It needs to include everything: Quarterly, Annual, TEIMP, Milestones, and Project Summary reports

Hey team! Please add your planning poker estimate with Zenhub @andrea-williams @BCerki @dleard @sam-warren @JoshLarouche

Fantastic @Sepehr-Sobhani !


SeeZero

Geo’s new app is called SeeZero - the new IHD’s connect to this.
Can this integration be used to access the data from the new IHD’s?

SeeZero app screenshot very similar to geo home app

SeeZero device supplied by Geo

Not sure if I asked for the right thing…

That's what they say to any api requests. The original api was reverse engineered by monitoring system traffic, and someone would need to do the same for this


Dom types not usable in nodejs (Cannot find name 'HTMLElement')

In backend nodejs projects the DOM types (HTMLElement) are only accessible if included explicitly by e.g. "lib": ["ES2020", "dom"] in tsconfig. Building without the included dom types gives the following error:
node_modules/juice/juice.d.ts:27:36 - error TS2304: Cannot find name 'HTMLElement'.

27   export let heightElements: HTMLElement[];
                                      ~~~~~~~~~~~
node_modules/juice/juice.d.ts:29:39 - error TS2304: Cannot find name 'HTMLElement'.

29   export let nonVisualElements: HTMLElement[];
                                         ~~~~~~~~~~~
node_modules/juice/juice.d.ts:31:35 - error TS2304: Cannot find name 'HTMLElement'.

31   export let tableElements: HTMLElement[];
                                     ~~~~~~~~~~~
node_modules/juice/juice.d.ts:32:35 - error TS2304: Cannot find name 'HTMLElement'.

32   export let widthElements: HTMLElement[];

Including all of the dom types only for the HTMLElement type seems like a bad idea and introducing alot of bloat.
Is there any workaround or possibility for another usable type here?

@SMKH-PRO I added it in a global typing file afair.


Add react-dnd-touch-backend

Fixes #1363

Can we merge this in :) ?

Yep! @longlho I made some updates to the TouchBackend to get it in line with our current TypeScript settings. I'll look into wiring it into the documentation so we can test out out further

thanks a lot!

Hey, I really would like to test it out. But I can't figure out right now, how to import the TouchBackend now.
import TouchBackend from 'react-dnd-touch-backend';

will be now?
Thanks for all your great work

Hey question:
My current Code:
import { BackendFactory } from 'dnd-core';
import TouchBackend from 'react-dnd-touch-backend';

const Backend: BackendFactory = TouchBackend({
  enableMouseEvents: true
});

export default Backend;

This will not work anymore with 9.0.0 now and the mono-repo (which I think is excellent step)
What do I need to do, to make it work again with:
<DndProvider backend={Backend}>

Thanks for all your work.

Hey Marvin,
The DndProvider in 9.0 accepts a new 'options' prop.
<DndProvider backend={TouchBackend} options={{ enableMouseEvents: true }}>
On Thu, Jul 4, 2019 at 12:37 AM Marvin<EMAIL_ADDRESS>wrote:

Hey question:
My current Code:
import { BackendFactory } from 'dnd-core';
import TouchBackend from 'react-dnd-touch-backend';
const Backend: BackendFactory = TouchBackend({
enableMouseEvents: true
});
export default Backend;
This will not work anymore with 9.0.0 now and the mono-repo (which I think
is excellent step)
What do I need to do, to make it work again with:

Thanks for all your work.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/react-dnd/react-dnd/pull/1425?email_source=notifications&email_token=AAA3XCHGP3XL63SE65H7B2TP5WSDXA5CNFSM4H2UWRO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZGTBLQ#issuecomment-508375214,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA3XCFTMGNPFLIVWDUWCXDP5WSDXANCNFSM4H2UWROQ
.

Hi,
<DndProvider backend={TouchBackend({ delayTouchStart: 200 })}> was working for me on<EMAIL_ADDRESS>with<EMAIL_ADDRESS>But this syntax caused an error on<EMAIL_ADDRESS>with<EMAIL_ADDRESS>After changing over to use <DndProvider backend={TouchBackend} option=({ delayTouchStart: 200 })>, I no longer had the error.
Nevertheless, even with the new syntax to avoid the error, time drag and drop no longer works for me on my touch device.
For now I've reverted for now back to 8.03 / 0.8.3. Will try to upgrade again sometime. Thanks.

@leantide would you be willing to put up a quick codesandbox demonstrating a working example? The touch-backend is fairly new in this repository, and I'd like to get that to a reliable point

I can repro it on my end. I'll see if I can get this working tonight

Thanks for the report @leantide - this should be fixed in the next patch releaes

Thanks @darthtrevino. Using <DndProvider backend={TouchBackend} options={{ delayTouchStart: 200 }}> now works for me on react-dnd-touch-backend @ 9.0.2.
Just a suggestion. Given that there are two backends, maybe it would be beneficial in your docs to show an example of how a web app could support both a mouse ainterface and touch interface, for example, by using a component that would dynamically use the HTML backend or the touch backend based on the detection of a mouse using
window.matchMedia('(pointer: fine)')
and the detection of touch using
window.matchMedia('(pointer: coarse)')


Unable to override command (introduced in 9.6.0)

Laravel Version: 9.6.0-9.8.1
PHP Version: 8.1

Description:
It is currently impossible to override a command handler provided by a package by creating a new command in app/Console/Commands with the same signature.
For example, package laravel/vapor-core has "stub" command vapor:handle which only throws exception with a request to create a custom vapor:handle command to process the input. But creating custom command with the same signature does not have any effect. Running php artisan vapor:handle PayLoaD still executes the handler from the vapor-core package and ignores custom handler from app/Console/Commands (or any other package)
Steps To Reproduce:

Install vapor-core: composer require laravel/vapor-core
Create new command overriding default handler from vapor-core: php artisan make:command CustomHandler --command="vapor:handle {payload}"
Run command: php artisan vapor:handle PayLoaD

GitHub repository demonstrating the issue: https://github.com/vadimpronin/bug-report
Possible cause:
I was able to pinpoint the problem to the new method getDefaultName in src/Illuminate/Console/Command.php in this commit: https://github.com/laravel/framework/commit/628d39f02cdb78ecb3049db8ce75fca2b3d20ec0#diff-132f1c15b2ac9b4ff179e85239c0a55e0daead42be5a2095b0fe765d3bc9ebd0R95
Specifically when this method is deleted (thus the parent method is used instead) everything works fine.
The parent method returns null for the overriding command's class, while the new method returns string "vapor:handle" taken from command's signature. I didn't quite understand how it affects the behaviour of overriding

Thanks @vadimpronin. We're going to revert that commit.

We've reverted this. This will be in Tuesday's release. Thanks


Odd git error

When deploying to Heroku for the first time using bin/setup_heroku, I received this error:
remote: Verifying deploy... done.
fatal: protocol error: bad line length character: warn
error: error in sideband demultiplexer
To https://git.heroku.com/testing-huginn-2.git
 + 2724bc9...2e9d1c0 master -> master (forced update)
Running database migrations...
Running `rake db:migrate` attached to terminal... up, run.8552
Restarting...
Restarting dynos... done
Done!

Anyone seen fatal: protocol error: bad line length character: warn before?

Never seen one of these before, everything I found about it suggests that the server is mis-configured. To which region did you try to deploy to? I just tested it with 'europe' and had no problems.

Very odd.  I just clicked the Heroku button to test it from scratch.  I'll assume it's a one-time Heroku issue.  Thanks for testing!


Figures preview

Figures and table preview for the reader.

Codecov Report

Merging #576 into master will decrease coverage by 0.42%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #576      +/-   ##
==========================================
- Coverage   54.17%   53.75%   -0.43%
==========================================
  Files         211      211
  Lines        5170     5211      +41
==========================================
  Hits         2801     2801
- Misses       2369     2410      +41

Impacted Files
Coverage Δ

src/article/models/FigureModel.js
0% <ø> (ø)
:arrow_up:

src/reader/components/ReaderXrefComponent.js
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@michael i'm not sure that it was a good idea to render table and figures inside reader xref component. On the one hand i think it was a good idea to keep html rendering inside model, on the other hand rendering tables without component could be a bit tricky and messy. What do you think, should i move it to models?

I chose to render inside xref component because of positioning (may also change in future but was quickest for now).
However as you say we could move the rendering code into separate components. The ideal goal would be to use shared/FigPreviewComponent etc. that is then used in the reader but also in the writer when selecting the targets.
Btw, @oliver---- started a big code restructuring of Texture, so it's likely we produce conflicts with new changes while he's working on that.
@oliver---- is it ok to continue this work, or better wait for your first round to be finished?

@Integral in the meanwhile can you try out if it feels better if preview popups are shown on explicit click of xref, compared to mouseover as done currently? Also we need to jump to functionality, when you click on the fig preview / table preview etc element, it should take you to the object on the page.

Let use anchors for jumping? Do we need highlighting?
Regarding popup on click, how can we jump in this case? Do we need to
render button inside popup then? For jumping I mean.
On Thu, 21 Jun 2018, 13:55 Michael Aufreiter<EMAIL_ADDRESS>wrote:

@Integral https://github.com/Integral in the meanwhile can you try out
if it feels better if preview popups are shown on explicit click of xref,
compared to mouseover as done currently? Also we need to jump to
functionality, when you click on the fig preview / table preview etc
element, it should take you to the object on the page.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/substance/texture/pull/576#issuecomment-399061151,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALG-oqRLGRK17o2pI_Dl6qGvF18qALjks5t-3u5gaJpZM4UxzLW
.

@michael do we want to render [1,2] as to separated links inside brackets?

@michael i've tried to do it here very roughly. We should decide something here as making a links inside labels [1,2], figure 1,2 or [1 to 3] are very tricky...

Yes!
On Tue, Jun 26, 2018 at 11:24 AM Michael Aufreiter<EMAIL_ADDRESS>wrote:

Hey @Integral https://github.com/Integral I think we don't need
separate links for reach label. But what I'd like to try is this: Clicking
(remove hover!) just opens the popup and then clicking the entry takes you
to the destination. And we do that for all xrefs (fig,bibr,table) in the
same way. Can you try this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/substance/texture/pull/576#issuecomment-400242084,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALG-huHQb9Lo6g15gjvAZ4qjh0uTAPVks5uAf3SgaJpZM4UxzLW
.

@michael I did try this in #579. However there are couple of problems as well. First is that there must be a link inside bib ref. So I'm not sure that we can wrap anything outside the label into the link. The other thing that we need to detect clicks/escape key to close popup and we need kind of the trap thing for it.
Anyways check if you like it and I will continue.

Forget about closing the popups for now. We can fix that later. But we need bigger click targets. Like in the popup the whole figure preview should be clickable same for references. Maybe add some hover style. Just try to make it look nice. And for xref, we should render them as <a> tags or <button>> not as span.. that makes for a strange click behavior.
Please finish that and let's merge it. Then you can do footnotes.
Merci. :)

Looks good. Merging this iteration. Maybe take care of footnotes display next. Using the API.


Add st stts22h temprature sensor

This pull request add STTS22H Temperature basic driver to Zephyr framework.
However, there is a problem with the i2c_burst_read in stts22h_STdC implementation. When I use i2c_burst_read to read from the sensor for two bytes, (L_OUT, H_OUT), it doesn't work. But when I call it two times, each time read a single byte, it works good.
More details:
Default implementation is as follows (That doesn't work):
int32_t stts22h_temperature_raw_get(stmdev_ctx_t *ctx, int16_t *val)
{
  uint8_t buff[2];
  int32_t ret;

  ret = stts22h_read_reg(ctx, STTS22H_TEMP_L_OUT, buff, 2);
  *val = (int16_t)buff[1];
  *val = (*val * 256) + (int16_t)buff[0];

  return ret;
}

In the above implementation, buff[0] and buff[1] always have the same value. (Seems the address doesn't increment)
After changing it to the two single read, it works:
int32_t stts22h_temperature_raw_get(stmdev_ctx_t *ctx, int16_t *val)
{
  uint8_t buff[2];
  int32_t ret;

  ret = stts22h_read_reg(ctx, STTS22H_TEMP_L_OUT, &buff[0], 1);
  ret = stts22h_read_reg(ctx, STTS22H_TEMP_H_OUT, &buff[1], 1);
  printk("Sep  Buf: %02X - %02X\n", buff[0], buff[1]);
  *val = (int16_t)buff[1];
  *val = (*val * 256) + (int16_t)buff[0];

  return ret;
}

Hi @javad123javad, thank you for this work. Unfortunately, there is already another PR in this regard https://github.com/zephyrproject-rtos/zephyr/pull/68356 .

Hi @javad123javad, thank you for this work. Unfortunately, there is already another PR in this regard #68356 .

Thanks @ajarmouni-st
Thats great. I will close this PR

Hi @javad123javad would you be able to submit the last 2 commits from this PR in another one since #68356 is merged now?


refactor: big typing cleanup, move to using hatch and ruff

Sorry that was a mistake, will fix On Nov 18, 2022, at 12:07 PM, Ian Hunt-Isaak @.***> wrote:
@ianhi commented on this pull request.
In src/pymmcore_plus/_util.py:

"""Locate a Micro-Manager folder (for device adapters).

In order, this will look for:

An environment variable named MICROMANAGER_PATH

An installation in the pymmcore_plus package directory (this is the

  default install location when running python -m pymmcore_plus.install)

The default micromanager install location:

   - `C:/Program Files/` on windows

   - `/Applications` on mac

   - `/usr/local/lib` on linux

"""

Why remove the details?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>


Plaid is returning "Code 1606: account not found"

Hi, I am testing out this gem and it seems very nice but I have run into an issue.
Whenever I try to use the helper, Plaid returns "Code 1606: account not found. The account ID provided was not correct..".
The params array includes "account_id"=>"".
I was under the impression that the account_id was only important for when you are trying to integrate plaid with stripe - which I am not trying to do.
Thanks

Having this same issue. Help?

hey there, sorry you're having issues -- which version of the gem are you using?

Hi. Thanks for your work on this. I'm hitting the same issue when using Plaid's test bank credentials, using gem versions 1.0.0.beta and 1.0.0.beta.2.


[#448] fixed problem with help-block is overlaying header with link

problem where different bootstrap-style-classes for header and
help-block. Now both use md for desktop
(https://www.w3schools.com/bootstrap/bootstrap_grid_examples.asp)

Coverage remained the same at 66.619% when pulling cd6316b667c93286cf6f76201013804891022543 on yearSelectionInAccountDetails into 841073f18afaaf07f55f6170ea77375134182dc5 on master.

Thank you for contributing!


WIP: CNV-25878: Add CPU and memory hot-plug

📝 Description
Jira: https://issues.redhat.com/browse/CNV-25878
🎥 Demo

Closing this PR as a new design was released for 4.16.


Fix minor compiler warnings

This fixes the only 2 warnings when building the library with MSVC.

Nice! :+1:


🐛 [core-web] Using a name in initializeApp results in "No Firebase App '[DEFAULT]' has been created"

Bug report
For android, I can call initializeApp with an app name and have no issues:
    await Firebase.initializeApp(
      options: DefaultFirebaseOptions.currentPlatform,
      name: 'Viewo - Test Sunny',
    );

But on web, providing the name like this results in the error
[core/no-app] No Firebase App '[DEFAULT]' has been created - call Firebase.initializeApp()
main.dart.js:22050     at Object.c (http://localhost/main.dart.js:4676:3)
main.dart.js:22050     at a_D.vu (http://localhost/main.dart.js:43272:36)
main.dart.js:22050     at Jf.L (http://localhost/main.dart.js:72172:55)
main.dart.js:22050     at MK.bT (http://localhost/main.dart.js:65742:18)
main.dart.js:22050     at MK.kb (http://localhost/main.dart.js:65718:9)
main.dart.js:22050     at MK.rY (http://localhost/main.dart.js:65685:6)
main.dart.js:22050     at MK.zN (http://localhost/main.dart.js:65716:11)
main.dart.js:22050     at MK.h8 (http://localhost/main.dart.js:65715:6)
main.dart.js:22050     at mo.wD (http://localhost/main.dart.js:65597:3)
main.dart.js:22050     at mo.er (http://localhost/main.dart.js:65550:16)

It works when initializeApp is called with no name (or with a name of [DEFAULT])
    await Firebase.initializeApp(
      options: DefaultFirebaseOptions.currentPlatform,
      //name: 'Viewo - Test Sunny',
    );

This may have been the issue behind #9269 (notice the user specified an app name in their example) and #9256 (notice the maintainer who responds did not specify an app name in their working config).
Steps to reproduce
Steps to reproduce the behavior:

make a flutter web app with firebase
give a name
flutter run

Expected behavior
The initialized project will be used as the default in spite of not being named '[DEFAULT]' (this is what it does on android, and I believe what documentation suggests you do).
Sample project
Let me know if you need one, this should be simple enough to not be necessary...
Additional context
None?
Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.5, on macOS 11.6.8 20G730 darwin-x64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✗] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[!] Android Studio (not installed)
[✓] Connected device (1 available)
[✓] HTTP Host Availability

! Doctor found issues in 3 categories.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
- _fe_analyzer_shared 46.0.0 [meta]
- analyzer 4.6.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- args 2.3.1
- asn1lib 1.1.0
- async 2.8.2 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 2.3.0 [analyzer async convert crypto glob logging meta path]
- build_config 1.1.0 [checked_yaml json_annotation path pubspec_parse yaml]
- characters 1.2.0
- charcode 1.3.1
- checked_yaml 2.0.1 [json_annotation source_span yaml]
- cli_repl 0.2.2 [async js]
- clock 1.1.0
- codemirror 0.7.6+5.65.5
- collection 1.16.0
- convert 3.0.2 [typed_data]
- crypto 3.0.2 [typed_data]
- encrypt 5.0.1 [args asn1lib clock collection crypto pointycastle]
- fake_async 1.3.0 [clock collection]
- file 6.1.2 [meta path]
- firebase_auth_platform_interface 6.5.3 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 4.2.3 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.5.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 1.7.1 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_database_platform_interface 0.2.2+1 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_database_web 0.2.1+3 [firebase_core firebase_core_web firebase_database_platform_interface flutter flutter_web_plugins js]
- fixnum 1.0.1
- flutter_highlight 0.7.0 [flutter highlight]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- fluttering_phrases 0.3.2
- font_awesome_flutter 10.1.0 [flutter]
- glob 2.1.0 [async collection file path string_scanner]
- google_sign_in_android 6.0.1 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.4.0 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.2.0 [flutter quiver]
- google_sign_in_web 0.10.2 [flutter flutter_web_plugins google_sign_in_platform_interface js]
- highlight 0.7.0 [collection]
- html_unescape 2.0.0
- http_parser 4.0.1 [collection source_span string_scanner typed_data]
- intl 0.17.0 [clock path]
- js 0.6.4
- json_annotation 4.6.0 [meta]
- lints 1.0.1
- logging 1.0.2
- markdown 5.0.0 [args charcode meta]
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.4
- mdc_web 0.6.0 [js meta]
- meta 1.7.0
- mime 1.0.2
- node_interop 2.1.0 [js]
- package_config 2.1.0 [path]
- path 1.8.1
- plugin_platform_interface 2.1.2 [meta]
- pointycastle 3.6.1 [collection convert js]
- protobuf 2.1.0 [fixnum collection meta]
- pub_semver 2.1.1 [collection meta]
- pubspec_parse 1.2.0 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.1.0 [matcher]
- sass 1.54.4 [args async charcode cli_repl collection meta node_interop js package_config path source_maps source_span stack_trace stream_transform string_scanner term_glyph tuple watcher http]
- sass_builder 2.1.4 [build build_config path sass]
- shelf 1.3.2 [async collection http_parser path stack_trace stream_channel]
- shelf_static 1.1.1 [convert http_parser mime path shelf]
- sky_engine 0.0.99
- source_maps 0.10.10 [source_span]
- source_span 1.8.2 [collection path term_glyph]
- split 0.0.7 [js meta]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.0 [charcode source_span]
- term_glyph 1.2.0
- test_api 0.4.9 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- tuple 2.0.0 [quiver]
- typed_data 1.3.0 [collection]
- vector_math 2.1.2
- watcher 1.0.1 [async path]
- webview_flutter_android 2.8.14 [flutter webview_flutter_platform_interface]
- webview_flutter_platform_interface 1.9.1 [flutter meta plugin_platform_interface]
- webview_flutter_wkwebview 2.7.5 [flutter path webview_flutter_platform_interface]
- yaml 3.1.1 [collection source_span string_scanner]

Thanks for the report @MichaelRFairhurst.
I ran the official plugin example https://github.com/firebase/flutterfire/tree/master/packages/firebase_core/firebase_core/example on web which has name for the app and it compiled and built properly as shown in below video:
https://user-images.githubusercontent.com/67046386/186109008-e7ed039c-40c9-40c3-bc69-01b0d19135b5.mov
Can you try the same example and confirm whether you still get same error or not ?

Thanks for the fast response -- I will take a look tomorrow.
However I can already see one place that may be the issue with this
attempted reproduction: it does not call .instance, which is present in
the stack trace of one (and getInstance is the erring method in the
other).
On Tue, Aug 23, 2022, 1:23 AM darshankawar @.***> wrote:

Thanks for the report @MichaelRFairhurst
https://github.com/MichaelRFairhurst.
I ran the official plugin example
https://github.com/firebase/flutterfire/tree/master/packages/firebase_core/firebase_core/example
on web which has name for the app and it compiled and built properly as
shown in below video:
https://user-images.githubusercontent.com/67046386/186109008-e7ed039c-40c9-40c3-bc69-01b0d19135b5.mov
Can you try the same example and confirm whether you still get same error
or not ?
—
Reply to this email directly, view it on GitHub
https://github.com/firebase/flutterfire/issues/9400#issuecomment-1223727967,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMNM67DNMZRKHWIGZSRQJLV2SC7LANCNFSM57JXQ72Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

From the example app, all I had to do was initialize the secondary app (not the primary) and then hit "get default config."
On android it works fine:
I/flutter (27350): Initialized FirebaseApp(foo)
I/flutter (27350): Current options for app [DEFAULT]: {apiKey: AIzaSyCdRjCVZlhrq72RuEklEyyxYlBRCYhI2Sw, appId: 1:406099696497:android:0d4ed619c031c0ac3574d0, messagingSenderId:<PHONE_NUMBER>97, projectId: flutterfire-e2e-tests, authDomain: null, databaseURL: https://flutterfire-e2e-tests-default-rtdb.europe-west1.firebasedatabase.app, storageBucket: flutterfire-e2e-tests.appspot.com, measurementId: null, trackingId: null, deepLinkURLScheme: null, androidClientId: null, iosClientId: null, iosBundleId: null, appGroupId: null}
I/flutter (27350): Currently initialized apps: [FirebaseApp([DEFAULT]), FirebaseApp(foo)]

But on web it crashes:
Initialized FirebaseApp(foo)
══╡ EXCEPTION CAUGHT BY GESTURE
╞═════════════════════════════════════════════════
══════════════════
The following FirebaseException was thrown while
handling a gesture:
[core/no-app] No Firebase App '[DEFAULT]' has been
created - call Firebase.initializeApp()

When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_
runtime/errors.dart 251:49  throw_
packages/firebase_core_web/src/firebase_core_web.d
art 269:9                   app
packages/firebase_core/src/firebase.dart 53:41
app
packages/firebase_core_example/main.dart 49:38
options
packages/flutter/src/material/ink_well.dart
1005:21                           [_handleTap]
packages/flutter/src/gestures/recognizer.dart
198:24                          invokeCallback
packages/flutter/src/gestures/tap.dart 613:48
handleTapUp
packages/flutter/src/gestures/tap.dart 298:5
[_checkUp]
packages/flutter/src/gestures/tap.dart 232:7
handlePrimaryPointer
packages/flutter/src/gestures/recognizer.dart
563:9                           handleEvent
packages/flutter/src/gestures/pointer_router.dart
94:12                       [_dispatch]
packages/flutter/src/gestures/pointer_router.dart
139:9                       <fn>
dart-sdk/lib/_internal/js_dev_runtime/private/link
ed_hash_map.dart 21:13      forEach
packages/flutter/src/gestures/pointer_router.dart
137:17
[_dispatchEventToRoutes]
packages/flutter/src/gestures/pointer_router.dart
123:7                       route
packages/flutter/src/gestures/binding.dart 445:19
handleEvent
packages/flutter/src/gestures/binding.dart 425:14
dispatchEvent
packages/flutter/src/rendering/binding.dart 329:11
dispatchEvent
packages/flutter/src/gestures/binding.dart 380:7
[_handlePointerEventImmediately]
packages/flutter/src/gestures/binding.dart 344:5
handlePointerEvent
packages/flutter/src/gestures/binding.dart 302:7
[_flushPointerEventQueue]
packages/flutter/src/gestures/binding.dart 285:32
[_handlePointerDataPacket]
lib/_engine/engine/platform_dispatcher.dart
1105:13                           invoke1
lib/_engine/engine/platform_dispatcher.dart 185:5
invokeOnPointerDataPacket
lib/_engine/engine/pointer_binding.dart 130:39
[_onPointerData]
lib/_engine/engine/pointer_binding.dart 543:18
<fn>
lib/_engine/engine/pointer_binding.dart 496:21
<fn>
lib/_engine/engine/pointer_binding.dart 210:16
loggedHandler

Handler: "onTap"
Recognizer:
  TapGestureRecognizer#0a5a8
══════════════════════════════════════════════════
══════════════════════════════════════════════════
Currently initialized apps: [FirebaseApp(foo)]

#9330 appears to be the same issue. Their described fix:
They are using a name in their example config
    var app = await Firebase.initializeApp(
      name: "my-throwaway-project",
      ...

to rectify the issue you must ALWAYS call initializeApp() with empty parameters, then you must subsequently call initializeApp(..) with a secondary project parameters.

"calling initializeApp() with empty parameters", would mean not providing a name, so this fits with my theory.

Thanks for the update @MichaelRFairhurst. I tried few things to replicate it, but still unable to trigger the error you are reporting. One thing I noticed after revisiting this issue is that, looking at this specific screenshot, it shows:
name != null ? firebase_interop.app(name) : firebase_interop.app(),
whereas, in latest version of firebase_core_web,  it shows getApp() instead:
https://github.com/firebase/flutterfire/blob/da36b9861b7d635382705b4893eed85fd672125c/packages/firebase_core/firebase_core_web/lib/src/interop/core.dart#L57
If I try below code without passing any parameters in initializeApp():
void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();

  runApp(MyApp());
}

I get below correct Assertion failure:
Error: Assertion failed: file:///Users/dhs/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-1.7.1/lib/src/firebase_core_web.dart:207:11
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 266:49  throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 29:3    assertFailed

I also tried the code sample again mentioned here, but was unable to replicate the error.
Also, from the log you shared above, I see that below values are null:
 authDomain: null
 measurementId: null

Whereas, I see the correct values being fetched from firebase_options.dart file for web:
authDomain: 'triage-79c7c.firebaseapp.com,
measurementId: 'G-EWHQGRTW9Q',
Can you confirm if the firebase_options.dart file in your project has above values and they are being fetched properly ?
Also, if you are using firebase_core_web plugin, make sure it it on latest version.
I have below:

I'm not sure I described my repro well.
Are you saying that it doesn't fail for you if you follow these steps? https://drive.google.com/file/d/1LvSqSJEFPuqkdOs-F9pgti3e5H2dXzyo/view?usp=sharing

Thanks for the update @MichaelRFairhurst. I tried few things to replicate it, but still unable to trigger the error you are reporting. One thing I noticed after revisiting this issue is that, looking at this specific screenshot, it shows:
name != null ? firebase_interop.app(name) : firebase_interop.app(),
whereas, in latest version of firebase_core_web, it shows getApp() instead:
https://github.com/firebase/flutterfire/blob/da36b9861b7d635382705b4893eed85fd672125c/packages/firebase_core/firebase_core_web/lib/src/interop/core.dart#L57

I checked out da36b9861b7d635382705b4893eed85fd672125c of the example and it still failed for me.
The Flutter DevTools debugger and profiler on Chrome is available at: http://<IP_ADDRESS>:9100?uri=http://<IP_ADDRESS>:60847/o2Gk0Z7nAqc=
Initialized FirebaseApp(foo)
══╡ EXCEPTION CAUGHT BY GESTURE ╞═══════════════════════════════════════════════════════════════════
The following FirebaseException was thrown while handling a gesture:
[core/no-app] No Firebase App '[DEFAULT]' has been created - call Firebase.initializeApp()

When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 251:49  throw_
packages/firebase_core_web/src/firebase_core_web.dart 269:9                   app
packages/firebase_core/src/firebase.dart 53:41                                app
packages/firebase_core_example/main.dart 49:38                                options
packages/flutter/src/material/ink_well.dart 1005:21                           [_handleTap]
packages/flutter/src/gestures/recognizer.dart 198:24                          invokeCallback
packages/flutter/src/gestures/tap.dart 613:48                                 handleTapUp
packages/flutter/src/gestures/tap.dart 298:5                                  [_checkUp]
packages/flutter/src/gestures/tap.dart 232:7                                  handlePrimaryPointer
packages/flutter/src/gestures/recognizer.dart 563:9                           handleEvent
packages/flutter/src/gestures/pointer_router.dart 94:12                       [_dispatch]
packages/flutter/src/gestures/pointer_router.dart 139:9                       <fn>
dart-sdk/lib/_internal/js_dev_runtime/private/linked_hash_map.dart 21:13      forEach
packages/flutter/src/gestures/pointer_router.dart 137:17
[_dispatchEventToRoutes]
packages/flutter/src/gestures/pointer_router.dart 123:7                       route
packages/flutter/src/gestures/binding.dart 445:19                             handleEvent
packages/flutter/src/gestures/binding.dart 425:14                             dispatchEvent
packages/flutter/src/rendering/binding.dart 329:11                            dispatchEvent
packages/flutter/src/gestures/binding.dart 380:7
[_handlePointerEventImmediately]
packages/flutter/src/gestures/binding.dart 344:5                              handlePointerEvent
packages/flutter/src/gestures/binding.dart 302:7
[_flushPointerEventQueue]
packages/flutter/src/gestures/binding.dart 285:32
[_handlePointerDataPacket]
lib/_engine/engine/platform_dispatcher.dart 1105:13                           invoke1
lib/_engine/engine/platform_dispatcher.dart 185:5
invokeOnPointerDataPacket
lib/_engine/engine/pointer_binding.dart 130:39                                [_onPointerData]
lib/_engine/engine/pointer_binding.dart 543:18                                <fn>
lib/_engine/engine/pointer_binding.dart 496:21                                <fn>
lib/_engine/engine/pointer_binding.dart 210:16                                loggedHandler

Handler: "onTap"
Recognizer:
  TapGestureRecognizer#9aaa1
════════════════════════════════════════════════════════════════════════════════════════════════════
Application finished.

If I try below code without passing any parameters in initializeApp():
void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();

  runApp(MyApp());
}

I get below correct Assertion failure:
Error: Assertion failed: file:///Users/dhs/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-1.7.1/lib/src/firebase_core_web.dart:207:11
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 266:49  throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 29:3    assertFailed

Just to clarify/confirm, I'm not calling initializeApp() without parameters. I'm calling it like this:
   await Firebase.initializeApp(
      options: DefaultFirebaseOptions.currentPlatform,
      //name: 'does not work unless this is commented out',
    );

I also tried the code sample again mentioned here, but was unable to replicate the error.

I was able to reproduce it but I had to tweak the sample, from var db = FirebaseFirestore.instanceFor(app: app); to var db = FirebaseFirestore.instance;

Also, from the log you shared above, I see that below values are null:
 authDomain: null
 measurementId: null

That's the log from me running this on android, where it doesn't crash.

Whereas, I see the correct values being fetched from firebase_options.dart file for web:
authDomain: 'triage-79c7c.firebaseapp.com, measurementId: 'G-EWHQGRTW9Q',
Can you confirm if the firebase_options.dart file in your project has above values and they are being fetched properly ?

It failed running on the example app you linked, https://github.com/firebase/flutterfire/tree/master/packages/firebase_core/firebase_core/example at a commit from earlier today.

Also, if you are using firebase_core_web plugin, make sure it it on latest version.
I have below:

In terms of my app where I originally had the issue, before I recreated that issue in the example app, I did take the time to list my dependencies when I opened the ticket. That showed
- firebase_core_web 1.7.1

so I'm running the latest version. (do note, your constraint of 1.6.5 is behind by 2 months)

I altered the original minimal repro, and got it down to this:
import 'package:cloud_firestore/cloud_firestore.dart';
import 'package:firebase_core/firebase_core.dart';

void main() async {
  await Firebase.initializeApp(
    name: "my-throwaway-project",
    options: const FirebaseOptions(
      apiKey: "AIzaSyBXOxFf_iXaer4tX-sE8eRrh77VftTKZI0",
      appId: "1:980810897373:android:b1a4bcd50cd76712868834",
      messagingSenderId: "980810897311",
      projectId: "my-throwaway-project",
    ),
  );

  FirebaseFirestore.instance;
}

I also made a tiny flutter app that crashes right after rendering and uploaded it here:
https://github.com/MichaelRFairhurst/firebase_debug
Hopefully one of these things help out, thanks so much for following this rabbit hole of a sneaky reproduction.

Thanks for the update and patience. I do see the same error now running above code sample and it crashes at:
FirebaseFirestore.instance; but I am not sure what's the purpose of this line as a standalone usage.
It seems to return instanceFor:
static FirebaseFirestore get instance {
    return FirebaseFirestore.instanceFor(
      app: Firebase.app(),
    );
  }

Which in turn checks for:
if (_cachedInstances.containsKey(app.name)) {
      return _cachedInstances[app.name]!;
    }

 error log

dhs@Dhss-MacBook-Pro firebase_core_example % flutter run -d chrome
Running "flutter pub get" in firebase_core_example...            2,076ms
Launching lib/main.dart on Chrome in debug mode...
Waiting for connection from debug service on Chrome...             20.8s
This app is linked to the debug service: ws://<IP_ADDRESS>:50716/WYeYk5ZY4bw=/ws
Debug service listening on ws://<IP_ADDRESS>:50716/WYeYk5ZY4bw=/ws

Running with unsound null safety
For more information see https://dart.dev/null-safety/unsound-null-safety

🔥  To hot restart changes while running, press "r" or "R".
For a more detailed help message, press "h". To quit, press "q".

An Observatory debugger and profiler on Chrome is available at: http://<IP_ADDRESS>:50716/WYeYk5ZY4bw=
Flutter Web Bootstrap: Auto
Error: [core/no-app] No Firebase App '[DEFAULT]' has been created - call Firebase.initializeApp()
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 266:49  throw_
packages/firebase_core_web/src/firebase_core_web.dart 269:9                   app
packages/firebase_core/src/firebase.dart 53:41                                app
packages/cloud_firestore/src/firestore.dart 27:21                             get instance
packages/triage/main.dart 128:21                                              main
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 45:50            <fn>
dart-sdk/lib/async/zone.dart 1660:54                                          runUnary
dart-sdk/lib/async/future_impl.dart 147:18                                    handleValue
dart-sdk/lib/async/future_impl.dart 767:44                                    handleValueCallback
dart-sdk/lib/async/future_impl.dart 796:13                                    _propagateToListeners
dart-sdk/lib/async/future_impl.dart 567:5                                     [_completeWithValue]
dart-sdk/lib/async/future.dart 528:22                                         <fn>
dart-sdk/lib/async/zone.dart 1660:54                                          runUnary
dart-sdk/lib/async/future_impl.dart 147:18                                    handleValue
dart-sdk/lib/async/future_impl.dart 767:44                                    handleValueCallback
dart-sdk/lib/async/future_impl.dart 796:13                                    _propagateToListeners
dart-sdk/lib/async/future_impl.dart 567:5                                     [_completeWithValue]
dart-sdk/lib/async/future_impl.dart 640:7                                     callback
dart-sdk/lib/async/schedule_microtask.dart 40:11                              _microtaskLoop
dart-sdk/lib/async/schedule_microtask.dart 49:5                               _startMicrotaskLoop
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 166:15           <fn>

</details>

/cc @russellwheatley

Hey @MichaelRFairhurst, you're seeing this error because you're using initializing a non-default app and trying to use the default app to use a plugin (presumably). For example:
final app = await Firebase.initializeApp(
      options: DefaultFirebaseOptions.currentPlatform,
      name: 'Viewo - Test Sunny',
    );

// This will use the default app instance which will cause an error
final db = FirebaseFirestore.instance;
//This is using the app you created which will not throw an error.
final db2 = FirebaseFirestore.instanceFor(app: app);

The reason why android does not throw an error is because you probably have a  google-services.json file in your android/app directory which by default creates a default app instance.

Thanks @russellwheatley and @darshankawar both!
OK, very unintuitive to me (even the example app from the project that I used didn't have a google-services.json, but rather ./android/app/src/main/res/values/values.xml). Huge thanks your team taking on the hard problem of making firebase configuration and initialization cross platform -- I'm sure there are all kinds of considerations especially running native firebase code along with flutter firebase code.
I was getting ready to point to documentation encouraging a name in initializeApp....but ultimately, I cannot track down any docs or tutorials that include specifying a name. I may have just been autocompletion-happy.
some more thoughts..
It seems like initializing [DEFAULT] on android here is misleading. And this seems like a potential trap still. You can use android configs like google-service.json, have everything working, not realize that calling initializeApp() is doing nothing, then go to web and crash. I don't know how common this potential trap is, all I know is it got me.

OK. I authored #9436 to explore options of better errors/logging to make this clearer going forward.


configuration failed

Good morning, I recently integrated my Ferroli air conditioners, but I continue to have configuration errors. to make them operational again I have to delete them and reinsert them. However, I have noticed that even in the application I sometimes have to refresh to get them to connect. what could it depend on? I attach the error log.
home-assistant_midea_ac_2024-08-19T08-41-15.534Z.log

Hi.
Based on your logs you may be having some general network issues. Your Shelly devices were also reporting errors. This would also explain why the OEM app also has issues.
Otherwise your devices appears to be working fine, except for <IP_ADDRESS> which was causing most of the errors. Try setting the Maximum Connection Lifetime to 90 seconds for this device.

Closing as stale.


Update QueueConsumer to reflect the API

Description
Hello team,
Im currently working on making https://github.com/cloudflare/terraform-provider-cloudflare/pull/3833 possible. Ive noticed that there are fields missing from the QueueConsumer and QueueConsumerSettings. Ive proceeded to add them, and also took consumer_id for Name input, which Im not sure is proper at the moment, Ill update if needed.
Please write to me for any additional changes needed, Im first time commiter on this repo.
Has your change been tested?
Ive tested it with the TF provider resources Im writing for the queue consumers.
Types of changes
What sort of change does your code introduce/modify?

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] This change is using publicly documented in cloudflare/api-schemas
and relies on stable APIs.

these fields are not documented as publicly stable so i'm afraid we cannot merge this as is.

these fields are not documented as publicly stable so i'm afraid we cannot merge this as is.

Do you have a schedule/cycles for maturing the API? If not, do you have a personal estimate? Just to have as a compass.

attributes and endpoints are documented when the service team believes they have reached the maturity level where they can commit to a public contract. it's very team and product dependent.


feat(client): show error, warn, and info in FCC debug console

Checklist:

[X] I have read and followed the contribution guidelines.
[X] I have read and followed the how to open a pull request guide.
[X] My pull request targets the main branch of freeCodeCamp.
[X] I have tested these changes either locally on my machine, or GitPod.

Closes #48744

@a2937 Would you provide some instructions on how to test your fixes.

@a2937 Would you provide some instructions on how to test your fixes.

Manual testing:
Step One: Start up the local FreeCodeCamp client and server with MongoDB database running in the background,
Step Two: Navigate to the client on port 8000 in your preferred web browser.
Step Three: Open up the curriculum
Step Four: Navigate JavaScript Algorithms and Data Structures
Step Five: Open a random challenge
Step Six: Find the text box to type the code in
Step Seven: In the text box type console.log("Hello"); to have something to compare it to.  Notice in the output it says "Hello"
Step Eight: Type console.info("Hello"); into the text box. Notice it should say "Hello" in the output as well.
Step Nine: Type console.warn("Warning"); into the text box. Notice it should say "Warning" in the output.
Step Ten: Type console.error("Error"); into the text box. Notice it should say "Error" in the output.
As for automated testing, I would be happy to provide some. However I had difficulty finding unit tests for the proxy logger.

As for automated testing, I would be happy to provide some. However I had difficulty finding existing unit tests for the proxy logger.

I don't think it's needed, there are no steps that requires using them, and when there will be one, the step itself will act as the unit test

Understandable.

I wish we could DRY this out a bit, but it works as is!

I could create a new method in test-evaluator called "postLogs" that would take care of the biggest offender.


Remove some unnecessary lookups.

Thanks! It was not explicitly described that tinyobjloader want to support rather old C++03 compiler, so we need to replace auto.

So described C++03 is the minimal requirement: https://github.com/syoyo/tinyobjloader/commit/03f8ebcf7346558f783ddeca60e128e267e0c98c
(Also, I have removed -std=c++11 in unit test)


v1.64.0 YouTube Bug with Firefox 53.0.3 (32-bit)

I recently updated to v1.64.0 for Firefox 53.0.3 (32-bit), and now I'm unable to scrobble in Youtube. I've already reauthenticated last.fm numerous times, and I'm still unable to scrobble. Here's the log: https://pastebin.com/gRuUW6Vw

Yes, it's the same for me. I'll investigate this bug.
As a temporary workaround, you can disable these options:

Okay, I just tried your suggested workaround, and now I can scrobble. Thanks very much, and I look forward to the bug being fixed!

@DuckFlagellant I changed some settings of Youtube API key, and now the extension should work even with enabled options. Could you check this and tell if it works?

It's working now, thank you so much!


Feature Request: Allow Filtering Based on Diff

I want to be able to collapse actions that don't modify the state (their diff is null) and auto-expand actions that do modify the state (their diff is non-null). Basically, I'm hoping that predicate can receive, in its report parameter, the computed diff string or object or whatever it is.

While we're here I'd really also like to just log like this [ACTION_TITILE_HERE]: DIFF_CONTENT_HERE

I like this idea, we will consider it.

I would like this as well.

@AndersDJohnson Yes!


 When I try to add homebridge as an accessory, I get the below error
http://imgur.com/a/f8oRQ
I have attached the debug output from start-up to failing to pair.
Thanks!
pi@raspberrypi /var/homebridge $ DEBUG=* homebridge -I
*** WARNING *** The program 'nodejs' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs
*** WARNING *** The program 'nodejs' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister
[12/15/2016, 11:02:35 PM] Plugin /usr/lib/nodejs does not have a package name that begins with 'homebridge-'.
[12/15/2016, 11:02:35 PM] Loaded plugin: homebridge-bigAssFans
[12/15/2016, 11:02:35 PM] Registering platform 'homebridge-bigAssFans.BigAssFans'
[12/15/2016, 11:02:35 PM] Registering accessory 'homebridge-bigAssFan.BigAssFan'
[12/15/2016, 11:02:35 PM] ---
[12/15/2016, 11:02:35 PM] Loaded plugin: homebridge-camera-ffmpeg
[12/15/2016, 11:02:35 PM] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[12/15/2016, 11:02:35 PM] ---
[12/15/2016, 11:02:37 PM] Loaded plugin: homebridge-zway
[12/15/2016, 11:02:37 PM] Registering accessory 'homebridge-zway.ZWayServer'
[12/15/2016, 11:02:37 PM] Registering platform 'homebridge-zway.ZWayServer'
[12/15/2016, 11:02:37 PM] ---
[12/15/2016, 11:02:37 PM] Loaded config.json with 0 accessories and 3 platforms.
[12/15/2016, 11:02:37 PM] ---
[12/15/2016, 11:02:37 PM] Loading 3 platforms...
[12/15/2016, 11:02:37 PM] Initializing ZWayServer platform...
ZWayServer Fetching Z-Way devices... +0ms
[12/15/2016, 11:02:37 PM] [Office Fan] Initializing BigAssFans platform...
[12/15/2016, 11:02:37 PM] [Office Fan] Big Ass Fans Platform Init
[12/15/2016, 11:02:37 PM] Initializing Camera-ffmpeg platform...
[12/15/2016, 11:02:37 PM] Loading 0 accessories...
[12/15/2016, 11:02:37 PM] [Office Fan] Office Fan Configure Accessory e1ed28a2-418a-43a7-bd8d-011a4e5d4d8a
[12/15/2016, 11:02:37 PM] [Office Fan] DidFinishLaunching
EventedHTTPServer Server listening on port 36024 +0ms
[12/15/2016, 11:02:37 PM] Front Right is running on port 36024.
EventedHTTPServer Server listening on port 52937 +39ms
[12/15/2016, 11:02:38 PM] Front Right is running on port 52937.
EventedHTTPServer Server listening on port 48705 +24ms
[12/15/2016, 11:02:38 PM] Front Right is running on port 48705.
ZWayServer Authenticating... +735ms
ZWayServer Authenticated. Resubmitting original request... +124ms
ZWayServer Device ZWayVDev_zway_Remote_3-0-0-B skipped!  +84ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +1ms
ZWayServer Device ZWayVDev_zway_Remote_6-0-0-B skipped!  +24ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +0ms
ZWayServer Device ZWayVDev_zway_Remote_7-0-0-B skipped!  +3ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +0ms
ZWayServer Device ZWayVDev_zway_Remote_12-0-0-B skipped!  +2ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +5ms
ZWayServer Device ZWayVDev_zway_2-0-49-5 skipped!  +3ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +0ms
ZWayServer Device ZWayVDev_zway_2-1-49-1 skipped!  +3ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +0ms
ZWayServer Device ZWayVDev_zway_2-2-49-5 skipped!  +4ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +1ms
ZWayServer Device ZWayVDev_zway_3-0-48-1 skipped!  +1ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +1ms
ZWayServer Device ZWayVDev_zway_6-0-48-1 skipped!  +3ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +0ms
ZWayServer Device ZWayVDev_zway_6-0-113-7-3-A skipped!  +2ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +1ms
ZWayServer Device ZWayVDev_zway_6-0-113-7-8-A skipped!  +1ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +1ms
ZWayServer Device ZWayVDev_zway_7-0-48-1 skipped!  +1ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +1ms
ZWayServer Device ZWayVDev_zway_12-0-48-1 skipped!  +4ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +1ms
ZWayServer Device ZWayVDev_zway_12-0-113-7-8-A skipped!  +2ms
ZWayServer { permanently_hidden: true,
ZWayServer   Skip: false,
ZWayServer   Include: false,
ZWayServer   opt_in: undefined } +0ms
ZWayServer Got grouped device InfoWidget_5_Int consisting of devices: +3ms
ZWayServer InfoWidget_5_Int - text +1ms
ZWayServer WARN: Didn't find suitable device class! +1ms
ZWayServer Got grouped device BatteryPolling_8 consisting of devices: +0ms
ZWayServer BatteryPolling_8 - battery.Battery +1ms
ZWayServer WARN: Didn't find suitable device class! +0ms
ZWayServer Got grouped device ZWayVDev_zway_Remote_5-0-0-B consisting of devices: +0ms
ZWayServer ZWayVDev_zway_Remote_5-0-0-B - switchControl +1ms
ZWayServer WARN: Didn't find suitable device class! +0ms
ZWayServer Got grouped device ZWayVDev_2-0 consisting of devices: +1ms
ZWayServer ZWayVDev_zway_2-0-128 - battery.Battery +0ms
ZWayServer WARN: Didn't find suitable device class! +0ms
ZWayServer Got grouped device ZWayVDev_3-0 consisting of devices: +0ms
ZWayServer ZWayVDev_zway_3-0-49-1 - sensorMultilevel.Temperature +1ms
ZWayServer ZWayVDev_zway_3-0-49-3 - sensorMultilevel.Luminiscence +0ms
ZWayServer ZWayVDev_zway_3-0-49-5 - sensorMultilevel.Humidity +0ms
ZWayServer ZWayVDev_zway_3-0-49-27 - sensorMultilevel.Ultraviolet +1ms
ZWayServer ZWayVDev_zway_3-0-113-7-3-A - sensorBinary +0ms
ZWayServer ZWayVDev_zway_3-0-113-7-8-A - sensorBinary +1ms
ZWayServer ZWayVDev_zway_3-0-128 - battery.Battery +0ms
ZWayServer Got grouped device ZWayVDev_4-0 consisting of devices: +1ms
ZWayServer ZWayVDev_zway_4-0-37 - switchBinary +1ms
ZWayServer Got grouped device ZWayVDev_5-0 consisting of devices: +1ms
ZWayServer ZWayVDev_zway_5-0-48-1 - sensorBinary.General purpose +0ms
ZWayServer ZWayVDev_zway_5-0-113-6-Door-A - sensorBinary +1ms
ZWayServer ZWayVDev_zway_5-0-128 - battery.Battery +0ms
ZWayServer Got grouped device ZWayVDev_6-0 consisting of devices: +0ms
ZWayServer ZWayVDev_zway_6-0-49-1 - sensorMultilevel.Temperature +1ms
ZWayServer ZWayVDev_zway_6-0-49-3 - sensorMultilevel.Luminiscence +0ms
ZWayServer ZWayVDev_zway_6-0-49-5 - sensorMultilevel.Humidity +0ms
ZWayServer ZWayVDev_zway_6-0-49-27 - sensorMultilevel.Ultraviolet +0ms
ZWayServer ZWayVDev_zway_6-0-128 - battery.Battery +1ms
ZWayServer Got grouped device ZWayVDev_7-0 consisting of devices: +0ms
ZWayServer ZWayVDev_zway_7-0-49-3 - sensorMultilevel.Luminiscence +1ms
ZWayServer ZWayVDev_zway_7-0-49-5 - sensorMultilevel.Humidity +1ms
ZWayServer ZWayVDev_zway_7-0-49-27 - sensorMultilevel.Ultraviolet +3ms
ZWayServer ZWayVDev_zway_7-0-49-1 - sensorMultilevel.Temperature +1ms
ZWayServer ZWayVDev_zway_7-0-113-7-3-A - sensorBinary +0ms
ZWayServer ZWayVDev_zway_7-0-113-7-8-A - sensorBinary +1ms
ZWayServer ZWayVDev_zway_7-0-128 - battery.Battery +0ms
ZWayServer Got grouped device ZWayVDev_8-0 consisting of devices: +0ms
ZWayServer ZWayVDev_zway_8-0-37 - switchBinary +1ms
ZWayServer Got grouped device ZWayVDev_9-0 consisting of devices: +0ms
ZWayServer ZWayVDev_zway_9-0-37 - switchBinary +0ms
ZWayServer Got grouped device ZWayVDev_10-0 consisting of devices: +1ms
ZWayServer ZWayVDev_zway_10-0-37 - switchBinary +0ms
ZWayServer Got grouped device ZWayVDev_11-0 consisting of devices: +0ms
ZWayServer ZWayVDev_zway_11-0-37 - switchBinary +0ms
ZWayServer Got grouped device ZWayVDev_12-0 consisting of devices: +1ms
ZWayServer ZWayVDev_zway_12-0-49-1 - sensorMultilevel.Temperature +0ms
ZWayServer ZWayVDev_zway_12-0-49-3 - sensorMultilevel.Luminiscence +0ms
ZWayServer ZWayVDev_zway_12-0-49-5 - sensorMultilevel.Humidity +1ms
ZWayServer ZWayVDev_zway_12-0-49-27 - sensorMultilevel.Ultraviolet +0ms
ZWayServer ZWayVDev_zway_12-0-113-7-3-A - sensorBinary +0ms
ZWayServer ZWayVDev_zway_12-0-128 - battery.Battery +1ms
ZWayServer Got grouped device ZWayVDev_13-0 consisting of devices: +0ms
ZWayServer ZWayVDev_zway_13-0-37 - switchBinary +0ms
ZWayServer Got grouped device ZWayVDev_14-0 consisting of devices: +7ms
ZWayServer ZWayVDev_zway_14-0-37 - switchBinary +1ms
ZWayServer Got grouped device ZWayVDev_15-0 consisting of devices: +0ms
ZWayServer ZWayVDev_zway_15-0-37 - switchBinary +1ms
ZWayServer Got grouped device ZWayVDev_16-0 consisting of devices: +0ms
ZWayServer ZWayVDev_zway_16-0-37 - switchBinary +0ms
ZWayServer Got grouped device ZWayVDev_20-0 consisting of devices: +1ms
ZWayServer ZWayVDev_zway_20-0-37 - switchBinary +0ms
ZWayServer ZWayVDev_zway_20-0-38 - switchMultilevel +0ms
ZWayServer Got grouped device ZWayVDev_21-0 consisting of devices: +1ms
ZWayServer ZWayVDev_zway_21-0-37 - switchBinary +0ms
ZWayServer ZWayVDev_zway_21-0-38 - switchMultilevel +1ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Garage Temperature'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_3-0-49-1" +96ms
ZWayServer Configured Characteristic "Current Temperature" for vdev "ZWayVDev_zway_3-0-49-1" +4ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_3-0-128" +4ms
ZWayServer Found and configured Service "TemperatureSensor" for vdev "ZWayVDev_zway_3-0-49-1" with typeKey "sensorMultilevel.Temperature" +2ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_3-0-128" +4ms
ZWayServer Configured Characteristic "Battery Level" for vdev "ZWayVDev_zway_3-0-128" +4ms
ZWayServer Configured Characteristic "Charging State" for vdev "ZWayVDev_zway_3-0-128" +2ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_3-0-128" +1ms
ZWayServer Found and configured Service "BatteryService" for vdev "ZWayVDev_zway_3-0-128" with typeKey "battery.Battery" +1ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_3-0-49-5" +4ms
ZWayServer Configured Characteristic "Current Relative Humidity" for vdev "ZWayVDev_zway_3-0-49-5" +3ms
ZWayServer Found and configured Service "HumiditySensor" for vdev "ZWayVDev_zway_3-0-49-5" with typeKey "sensorMultilevel.Humidity" +1ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_3-0-49-3" +3ms
ZWayServer Configured Characteristic "Current Ambient Light Level" for vdev "ZWayVDev_zway_3-0-49-3" +2ms
ZWayServer Found and configured Service "LightSensor" for vdev "ZWayVDev_zway_3-0-49-3" with typeKey "sensorMultilevel.Luminiscence" +1ms
ZWayServer Loaded services for Garage Temperature +1ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Doorbell'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_4-0-37" +25ms
ZWayServer Configured Characteristic "On" for vdev "ZWayVDev_zway_4-0-37" +4ms
ZWayServer Found and configured Service "Switch" for vdev "ZWayVDev_zway_4-0-37" with typeKey "switchBinary" +1ms
ZWayServer Loaded services for Doorbell +1ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Aeon Labs General purpose (<IP_ADDRESS>)'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_5-0-48-1" +10ms
ZWayServer Configured Characteristic "Contact Sensor State" for vdev "ZWayVDev_zway_5-0-48-1" +3ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_5-0-128" +2ms
ZWayServer Adding Characteristic "Name" failed with message "Cannot add a Characteristic with the same UUID as another Characteristic in this Service: 00000023-0000-1000-8000-0026BB765291". This may be expected. +1ms
ZWayServer Found and configured Service "ContactSensor" for vdev "ZWayVDev_zway_5-0-48-1" with typeKey "sensorBinary.General purpose" +1ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_5-0-128" +1ms
ZWayServer Configured Characteristic "Battery Level" for vdev "ZWayVDev_zway_5-0-128" +1ms
ZWayServer Configured Characteristic "Charging State" for vdev "ZWayVDev_zway_5-0-128" +1ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_5-0-128" +1ms
ZWayServer Found and configured Service "BatteryService" for vdev "ZWayVDev_zway_5-0-128" with typeKey "battery.Battery" +1ms
ZWayServer Loaded services for Aeon Labs General purpose (<IP_ADDRESS>) +0ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Lounge Room Temperature'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_6-0-49-1" +9ms
ZWayServer Configured Characteristic "Current Temperature" for vdev "ZWayVDev_zway_6-0-49-1" +9ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_6-0-128" +2ms
ZWayServer Found and configured Service "TemperatureSensor" for vdev "ZWayVDev_zway_6-0-49-1" with typeKey "sensorMultilevel.Temperature" +1ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_6-0-128" +1ms
ZWayServer Configured Characteristic "Battery Level" for vdev "ZWayVDev_zway_6-0-128" +1ms
ZWayServer Configured Characteristic "Charging State" for vdev "ZWayVDev_zway_6-0-128" +1ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_6-0-128" +3ms
ZWayServer Found and configured Service "BatteryService" for vdev "ZWayVDev_zway_6-0-128" with typeKey "battery.Battery" +0ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_6-0-49-5" +2ms
ZWayServer Configured Characteristic "Current Relative Humidity" for vdev "ZWayVDev_zway_6-0-49-5" +1ms
ZWayServer Found and configured Service "HumiditySensor" for vdev "ZWayVDev_zway_6-0-49-5" with typeKey "sensorMultilevel.Humidity" +1ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_6-0-49-3" +2ms
ZWayServer Configured Characteristic "Current Ambient Light Level" for vdev "ZWayVDev_zway_6-0-49-3" +1ms
ZWayServer Found and configured Service "LightSensor" for vdev "ZWayVDev_zway_6-0-49-3" with typeKey "sensorMultilevel.Luminiscence" +0ms
ZWayServer Loaded services for Lounge Room Temperature +1ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Temperature'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_7-0-49-1" +7ms
ZWayServer Configured Characteristic "Current Temperature" for vdev "ZWayVDev_zway_7-0-49-1" +1ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_7-0-128" +1ms
ZWayServer Found and configured Service "TemperatureSensor" for vdev "ZWayVDev_zway_7-0-49-1" with typeKey "sensorMultilevel.Temperature" +1ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_7-0-128" +2ms
ZWayServer Configured Characteristic "Battery Level" for vdev "ZWayVDev_zway_7-0-128" +0ms
ZWayServer Configured Characteristic "Charging State" for vdev "ZWayVDev_zway_7-0-128" +1ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_7-0-128" +0ms
ZWayServer Found and configured Service "BatteryService" for vdev "ZWayVDev_zway_7-0-128" with typeKey "battery.Battery" +1ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_7-0-49-5" +1ms
ZWayServer Configured Characteristic "Current Relative Humidity" for vdev "ZWayVDev_zway_7-0-49-5" +1ms
ZWayServer Found and configured Service "HumiditySensor" for vdev "ZWayVDev_zway_7-0-49-5" with typeKey "sensorMultilevel.Humidity" +0ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_7-0-49-3" +2ms
ZWayServer Configured Characteristic "Current Ambient Light Level" for vdev "ZWayVDev_zway_7-0-49-3" +0ms
ZWayServer Found and configured Service "LightSensor" for vdev "ZWayVDev_zway_7-0-49-3" with typeKey "sensorMultilevel.Luminiscence" +1ms
ZWayServer Loaded services for Temperature +0ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Garage Light'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_8-0-37" +10ms
ZWayServer Configured Characteristic "On" for vdev "ZWayVDev_zway_8-0-37" +1ms
ZWayServer Found and configured Service "Switch" for vdev "ZWayVDev_zway_8-0-37" with typeKey "switchBinary" +1ms
ZWayServer Loaded services for Garage Light +0ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Attic Fan'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_9-0-37" +13ms
ZWayServer Configured Characteristic "On" for vdev "ZWayVDev_zway_9-0-37" +1ms
ZWayServer Found and configured Service "Switch" for vdev "ZWayVDev_zway_9-0-37" with typeKey "switchBinary" +3ms
ZWayServer Loaded services for Attic Fan +1ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Front Lights'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_10-0-37" +7ms
ZWayServer Configured Characteristic "On" for vdev "ZWayVDev_zway_10-0-37" +1ms
ZWayServer Found and configured Service "Switch" for vdev "ZWayVDev_zway_10-0-37" with typeKey "switchBinary" +0ms
ZWayServer Loaded services for Front Lights +1ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Lounge Room Lights'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_11-0-37" +6ms
ZWayServer Configured Characteristic "On" for vdev "ZWayVDev_zway_11-0-37" +1ms
ZWayServer Found and configured Service "Switch" for vdev "ZWayVDev_zway_11-0-37" with typeKey "switchBinary" +0ms
ZWayServer Loaded services for Lounge Room Lights +0ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Attic Temperature'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_12-0-49-1" +11ms
ZWayServer Configured Characteristic "Current Temperature" for vdev "ZWayVDev_zway_12-0-49-1" +1ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_12-0-128" +1ms
ZWayServer Found and configured Service "TemperatureSensor" for vdev "ZWayVDev_zway_12-0-49-1" with typeKey "sensorMultilevel.Temperature" +3ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_12-0-128" +2ms
ZWayServer Configured Characteristic "Battery Level" for vdev "ZWayVDev_zway_12-0-128" +0ms
ZWayServer Configured Characteristic "Charging State" for vdev "ZWayVDev_zway_12-0-128" +2ms
ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_12-0-128" +0ms
ZWayServer Found and configured Service "BatteryService" for vdev "ZWayVDev_zway_12-0-128" with typeKey "battery.Battery" +1ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_12-0-49-5" +1ms
ZWayServer Configured Characteristic "Current Relative Humidity" for vdev "ZWayVDev_zway_12-0-49-5" +1ms
ZWayServer Found and configured Service "HumiditySensor" for vdev "ZWayVDev_zway_12-0-49-5" with typeKey "sensorMultilevel.Humidity" +1ms
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_12-0-49-3" +1ms
ZWayServer Configured Characteristic "Current Ambient Light Level" for vdev "ZWayVDev_zway_12-0-49-3" +0ms
ZWayServer Found and configured Service "LightSensor" for vdev "ZWayVDev_zway_12-0-49-3" with typeKey "sensorMultilevel.Luminiscence" +4ms
ZWayServer Loaded services for Attic Temperature +1ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Laundry Room Fan'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_13-0-37" +9ms
ZWayServer Configured Characteristic "On" for vdev "ZWayVDev_zway_13-0-37" +0ms
ZWayServer Found and configured Service "Switch" for vdev "ZWayVDev_zway_13-0-37" with typeKey "switchBinary" +1ms
ZWayServer Loaded services for Laundry Room Fan +0ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Master Bedroom Outside Light'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_14-0-37" +7ms
ZWayServer Configured Characteristic "On" for vdev "ZWayVDev_zway_14-0-37" +0ms
ZWayServer Found and configured Service "Switch" for vdev "ZWayVDev_zway_14-0-37" with typeKey "switchBinary" +1ms
ZWayServer Loaded services for Master Bedroom Outside Light +0ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Bathroom Light and Fan'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_15-0-37" +6ms
ZWayServer Configured Characteristic "On" for vdev "ZWayVDev_zway_15-0-37" +1ms
ZWayServer Found and configured Service "Switch" for vdev "ZWayVDev_zway_15-0-37" with typeKey "switchBinary" +1ms
ZWayServer Loaded services for Bathroom Light and Fan +0ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Master Bathroom Light and Fan'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_16-0-37" +13ms
ZWayServer Configured Characteristic "On" for vdev "ZWayVDev_zway_16-0-37" +1ms
ZWayServer Found and configured Service "Switch" for vdev "ZWayVDev_zway_16-0-37" with typeKey "switchBinary" +1ms
ZWayServer Loaded services for Master Bathroom Light and Fan +0ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Blind (20.0)'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_20-0-38" +15ms
ZWayServer Configured Characteristic "Current Position" for vdev "ZWayVDev_zway_20-0-38" +10ms
ZWayServer Configured Characteristic "Target Position" for vdev "ZWayVDev_zway_20-0-38" +4ms
ZWayServer Configured Characteristic "Position State" for vdev "ZWayVDev_zway_20-0-38" +1ms
ZWayServer Configured Characteristic "Hold Position" for vdev "ZWayVDev_zway_20-0-38" +2ms
ZWayServer Found and configured Service "WindowCovering" for vdev "ZWayVDev_zway_20-0-38" with typeKey "switchMultilevel.blind" +1ms
ZWayServer Loaded services for Blind (20.0) +0ms
[12/15/2016, 11:02:38 PM] Initializing platform accessory 'Blind (21.0)'...
ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_21-0-38" +9ms
ZWayServer Configured Characteristic "Current Position" for vdev "ZWayVDev_zway_21-0-38" +2ms
ZWayServer Configured Characteristic "Target Position" for vdev "ZWayVDev_zway_21-0-38" +2ms
ZWayServer Configured Characteristic "Position State" for vdev "ZWayVDev_zway_21-0-38" +2ms
ZWayServer Configured Characteristic "Hold Position" for vdev "ZWayVDev_zway_21-0-38" +1ms
ZWayServer Found and configured Service "WindowCovering" for vdev "ZWayVDev_zway_21-0-38" with typeKey "switchMultilevel.blind" +1ms
ZWayServer Loaded services for Blind (21.0) +1ms
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘

EventedHTTPServer Server listening on port 51826 +1s
[12/15/2016, 11:02:39 PM] Homebridge is running on port 51826.
EventedHTTPServer [::ffff:<IP_ADDRESS>] New connection from client +40ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server listening on port 38865 +8ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] New connection from client +15ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server listening on port 55544 +2ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] New connection from client +4ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server listening on port 40194 +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] New connection from client +7ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server listening on port 34688 +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-verify +32ms
HAPServer [8F:67:A7:27:F4:0F] HAP Request: POST /pair-verify +2ms
HAPServer [8F:67:A7:27:F4:0F] Pair verify step 1/2 +14ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +95ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-verify +6ms
HAPServer [8F:67:A7:27:F4:0F] HAP Request: POST /pair-verify +1ms
HAPServer [8F:67:A7:27:F4:0F] Pair verify step 1/2 +2ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +32ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-verify +2ms
HAPServer [5A:4E:B1:DE:1C:D0] HAP Request: POST /pair-verify +0ms
HAPServer [5A:4E:B1:DE:1C:D0] Pair verify step 1/2 +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +22ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-verify +2ms
HAPServer [5A:4E:B1:DE:1C:D0] HAP Request: POST /pair-verify +0ms
HAPServer [5A:4E:B1:DE:1C:D0] Pair verify step 1/2 +2ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +27ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] Client connection closed +28ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] Client connection closed +13ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP connection was closed +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server was closed +2ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP connection was closed +5ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server was closed +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] Client connection closed +2ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP connection was closed +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server was closed +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] Client connection closed +10ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP connection was closed +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server was closed +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] New connection from client +556ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server listening on port 48813 +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-setup +5ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-setup +0ms
HAPServer [CC:22:3D:E3:CE:30] Pair step 1/5 +5ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +2s
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-setup +6s
HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-setup +1ms
HAPServer [CC:22:3D:E3:CE:30] Pair step 2/5 +4ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +2s
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-setup +120ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-setup +1ms
HAPServer [CC:22:3D:E3:CE:30] Pair step 3/5 +3ms
HAPServer [CC:22:3D:E3:CE:30] Pair step 4/5 +8ms
HAPServer [CC:22:3D:E3:CE:30] Pair step 5/5 +7ms
Accessory [Homebridge] Paired with client 0BB4FC56-E05E-4C8D-AF7D-09CDA5AA8C37 +11ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +11ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] Client connection closed +16ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP connection was closed +2ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server was closed +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] New connection from client +15ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server listening on port 43607 +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-verify +11ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify +0ms
HAPServer [CC:22:3D:E3:CE:30] Pair verify step 1/2 +2ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +25ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-verify +23ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify +0ms
HAPServer [CC:22:3D:E3:CE:30] Pair verify step 2/2 +4ms
HAPServer [CC:22:3D:E3:CE:30] Client 0BB4FC56-E05E-4C8D-AF7D-09CDA5AA8C37 verification complete +7ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +6ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /accessories +17ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: GET /accessories +0ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +50ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pairings +239ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pairings +0ms
HAPServer [CC:22:3D:E3:CE:30] Removing pairing info for client +4ms
Accessory [Homebridge] Unpairing with client 0BB4FC56-E05E-4C8D-AF7D-09CDA5AA8C37 +1ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished +8ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] Client connection closed +10ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP connection was closed +2ms
EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server was closed +0ms
ZWayServer Got 6 updates. +15s
ZWayServer Updated characteristic Current Relative Humidity on Garage Humidity +3ms
ZWayServer Got 4 updates. +2s

Based on the log it looks like zway plugin returned invalid value to one of the characteristics and that resulted HomeKit thinking the bridge is out of compliance.

Updating the plugin worked. Thanks for the analysis.


Update documentation for initial setup

Description
This patch series is focused on updating the documentation for the initial README and setup for the project. There may be a lot of moving parts here, but this description will be updated with what each commit is trying to achieve.

73c265a This doesn't seem necessary any more, as per internal Slack. These are changes to the documentation.

Reviewer Notes
n/a
Setup
n/a
Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References
n/a
Screenshots
n/a

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 73c265af2c11f408739c7650969d82c482e30e36

closing this PR since it doesn't follow the team's branch name convention. Learning! 🤦🏽


[FLINK-13591][web]: fix job list display when job name is too long

What is the purpose of the change
fix Job List in Flink web doesn't display right when the job name is very long
Brief change log
add max-width to the td of job name column table to 40%
Verifying this change

Submit a job with long name (more than 200 char)
Visit the overview page

The job name column is not more than 40% width of table
before

after fix

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

+1, thanks for fixing this


New model equation type @log

Codecov Report

Merging #15 into master will decrease coverage by 2.02%.
The diff coverage is 67.00%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
- Coverage   73.99%   71.97%   -2.03%
==========================================
  Files          14       14
  Lines        1046     1074      +28
==========================================
- Hits          774      773       -1
- Misses        272      301      +29

Impacted Files
Coverage Δ

src/model.jl
67.09% <40.00%> (-2.69%)
:arrow_down:

src/steadystate.jl
71.05% <71.08%> (-4.54%)
:arrow_down:

src/abstract.jl
71.42% <100.00%> (ø)

src/equation.jl
62.50% <100.00%> (ø)

src/misc.jl
15.38% <0.00%> (-1.29%)
:arrow_down:

Continue to review full report at Codecov.

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