Moving pie chart location (legend overlaps chart)

Is there a way to control the location of the actual chart within the actual PieChartView? My view spans across the whole view controller's UIView, but is always centered. The rendering rect is private for the PieChartView so I can't access it, any ideas of how I can solve the issue (could involve legend as well). I added a picture for reference.
Thanks!

I just played with the ChartsDemo pie chart, similar case. I guess you have to modify some code and re-build it so you can use.
however, I think this is not a good way, but actually you can choose write your own chart legend, like putting it in a scroll view, or some tricks
@danielgindi I found another bug is, in charts demo, if you drag the slider, the pie chart radius trend is: decreasing --> increasing

Hi royhema
I want to use pieBarChar but there's no documentation on how to use it , and I tried to translate demo project as I don't know Objective-C but a lot of errors are showing , can you just show me how to get and put hard coded values just as an example , so I get an idea on how to work with dynamic numbers . Thanks very much.
And sorry for the off-topic question.

@dushiarlind it's twoo hard to answer your question, as your question is not clear. you have to understand you just needs to create pie chart data set with your values, and create pie chart data and feed it to pie chart view. Objc is one of the most easiest code to read and understand, you just have to get the idea. take a look at - (void)setDataCount:(int)count range:(double)range in pieChartViewController,
PieChartDataSet *dataSet = [[PieChartDataSet alloc] initWithYVals:yVals1 label:@"Election Results"];
_chartView.data = data;
is how you create it and feed it to chart view.
But do remember, first configure your chart view, and then set the data, not the revsered way.

@liuxuan30  Sorry for not clearing things up.
I've put a uiview in my storyboard , set class to PieChartView and created an IBOutlet .
Now I need this pie to show me 3 slices with different numbers which will come to me from json object.
Let's say I parsed the numbers and stored them in 3 variables. Now I want to put them in the pieChart.
How do I do that .
So I've got  myPieChart  and  variables   let slice1 , let slice2 and let slice3  which containt 3 different numbers.

as I said, you have to understand you just needs to create pie chart data set with your values, and create pie chart data and feed it to pie chart view. You should look at the ChartsDemo first.
Please avoid your further questions on this thread. It's distracting. I do not suggest you open a new one for the same question, as the answer is obvious and already in the code, I merely say what the code say.

@royherma Were you able to figure out moving the location of the PieChart or did you create a custom Scroll view for the legend like @liuxuan30 suggested?

I created a custom scroll view legend from scratch.
On Wed, Mar 2, 2016 at 11:14 AM, Kelo Akalamudo<EMAIL_ADDRESS>wrote:

@royherma https://github.com/royherma Were you able to figure out
moving the location of the PieChart or did you create a custom Scroll view
for the legend like @liuxuan30 https://github.com/liuxuan30 suggested?
—
Reply to this email directly or view it on GitHub
https://github.com/danielgindi/ios-charts/issues/707#issuecomment-191379848
.

If you want complete control, you can now set the legend to drawInside, to avoid affecting the Pie's position. And then use custom offsets to move the pie around.


Ramda.pluck: function cannot be called on any member of intersection type

Meta

flow-bin 0.60.1
flow-typed 2.2.3
ramda 0.25.0 (with type def 656f69c1c8/ramda_v0.x.x/flow_>=v0.49.x)

Problem
The following code
function pluckIds<V, T: Array<{ [key: string]: V }>>(items: T) {
  return R.pluck('id', items)
}

causes some hard-to-understand errors:
  8:   return R.pluck('id', items)
              ^^^^^^^^^^^^^^^^^^^^ call of method `pluck`. Function cannot be called on any member of intersection type
  8:   return R.pluck('id', items)
              ^^^^^^^ intersection
  Member 1:
                               v
  819:   declare function pluck<
  820:     V,
  821:     K: string | number,
  ...:
  826:   ): Array<V>;
         ----------^ function type. See lib: flow-typed/npm/ramda_v0.x.x.js:819
  Error:
    8:   return R.pluck('id', items)
                              ^^^^^ array type. Has some incompatible type argument with
  822:     T: Array<Array<V> | { [key: string]: V }>
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ array type. See lib: flow-typed/npm/ramda_v0.x.x.js:822
    Type argument `T` is incompatible:
      822:     T: Array<Array<V> | { [key: string]: V }>
                        ^^^^^^^^ array type. This type is incompatible with. See lib: flow-typed/npm/ramda_v0.x.x.js:822
        7: function pluckIds<V, T: Array<{ [key: string]: V }>>(items: T) {
                                         ^^^^^^^^^^^^^^^^^^^^ object type

Isn't Array<{ [key: string]: V }> a narrower type of Array<Array<V> | { [key: string]: V }>? Why wouldn't it pass type checking?

Oops, seems to be related to covariance / contravariance.
Ref: https://github.com/facebook/flow/issues/4258


Washington County USPS Address Point Update

Benefit
Update USPS data
Acceptance
Washington Co addresses submitted to the USPS system

Benefit
Update USPS data
Acceptance
Washington Co addresses submitted to the USPS system

This morning when I checked the County Project's link, it shows that the service is currently unavailable. I am not sure if it's a temporary service downtime, the tool is no longer available, or if there is a new tool somewhere else. Just leaving my observation here for your information.

@mhchou I submitted points for Washington last week. What link were you checking out?

Sorry, Zach. I was talking with Greg on the USPS's County Project. https://postalpro.usps.com/address-quality/county-project
And it seems to work now! Disregard my previous comment.

No worries @mhchou, I'm new to the USPS stuff and wasn't sure if I was missing something. We'll see what the USPS has to say.

Waiting for response from USPS

Sprint 5

[ ] Triage feedback and contact person in Tennessee

Dinged USPS, now waiting for a response.

USPS is updating their addresses.


Indeterminate values

At certain values of l, m, s and theta, SpinWeightedSphericalHarmonicY returns 0^0, an indeterminate value.
Eg. l = 2, m = -2, s = -2, theta = pi

This should be straightforward to fix, by appropriately taking the limit theta->pi of
Sin[\[Theta]/2]^(2 l - 2 r - s + m)] Cos[\[Theta]/2]^(2 r + s - m)

given the constraints on the integers l, r, s, and m. This could be added as another definition in certain cases.
We may also need to do similar for the theta->0 limit.


Surveyor license # not appearing in monument submission

My Profile

Monument submission header

This appears properly in the header on each page, including the review.


feat: port Analysis.Convolution

Ah, I wasn't paying attention and also started on this. Only got as far as the second theorem, though:
--- Mathlib/Analysis/Convolution.lean
+++ Mathlib/Analysis/Convolution.lean
@@ -123,13 +123,17 @@ variable [AddGroup G] [TopologicalSpace G]
 theorem convolution_integrand_bound_right_of_le_of_subset {C : ℝ} (hC : ∀ i, ‖g i‖ ≤ C) {x t : G}
     {s u : Set G} (hx : x ∈ s) (hu : -tsupport g + s ⊆ u) :
     ‖L (f t) (g (x - t))‖ ≤ u.indicator (fun t => ‖L‖ * ‖f t‖ * C) t := by
-  refine' le_indicator (fun t ht => _) (fun t ht => _) t
+  -- Porting note: added `suffices`
+  suffices (fun t => ‖(L (f t)) (g (x - t))‖) ≤ indicator u (fun t ↦ ‖L‖ * ‖f t‖ * C) by
+    apply this t
+  refine' le_indicator (fun t _ => _) (fun t ht => _)
   · refine' (L.le_op_norm₂ _ _).trans _
-    apply mul_le_mul_of_nonneg_left (hC _) (mul_nonneg (norm_nonneg _) (norm_nonneg _))
+    apply mul_le_mul_of_nonneg_left (hC _) (mul_nonneg (norm_nonneg L) (norm_nonneg _))
   · have : x - t ∉ support g := by
       refine' mt (fun hxt => _) ht
       apply hu
-      refine' ⟨_, _, set.neg_mem_neg.mpr (subset_closure hxt), hx, _⟩
+      refine' ⟨_, _, Set.neg_mem_neg.mpr (subset_closure hxt), hx, _⟩
+      simp only
       rw [neg_sub, sub_add_cancel]
     rw [nmem_support.mp this, (L _).map_zero, norm_zero]
 #align convolution_integrand_bound_right_of_le_of_subset convolution_integrand_bound_right_of_le_of_subset
@@ -137,8 +141,8 @@ theorem convolution_integrand_bound_right_of_le_of_subset {C : ℝ} (hC : ∀ i,
 theorem HasCompactSupport.convolution_integrand_bound_right_of_subset (hcg : HasCompactSupport g)
     (hg : Continuous g) {x t : G} {s u : Set G} (hx : x ∈ s) (hu : -tsupport g + s ⊆ u) :
     ‖L (f t) (g (x - t))‖ ≤ u.indicator (fun t => ‖L‖ * ‖f t‖ * ⨆ i, ‖g i‖) t := by
-  apply convolution_integrand_bound_right_of_le_of_subset _ (fun i => _) hx hu
-  exact le_ciSup (hg.norm.bdd_above_range_of_has_compact_support hcg.norm) _
+  refine convolution_integrand_bound_right_of_le_of_subset _ (fun i => ?_) hx hu
+  exact le_ciSup (hg.norm.bddAbove_range_of_hasCompactSupport hcg.norm) _
 #align has_compact_support.convolution_integrand_bound_right_of_subset HasCompactSupport.convolution_integrand_bound_right_of_subset

 theorem HasCompactSupport.convolution_integrand_bound_right (hcg : HasCompactSupport g)

@Ruben-VandeVelde After a few merge conflicts, I started pushing to github & opening a PR right after running start_port.sh.

This file is incredibly slow since MeasureTheory.Measure is overloaded with Measure, that alone probably adds multiple minutes of compile time in this file.

What should we do? Introduce local notation "Measure" := MeasureTheory.Measure? Something else? Ask core devs to add a namespace to _root_.Measure? (is it an option?)

I started https://leanprover.zulipchat.com/#narrow/stream/287929-mathlib4/topic/Measure.20is.20overloaded/near/366584965

local notation "Measure" => MeasureTheory.Measure would be nice, but it doesn't work. It still considers _root_.Measure. I think as a workaround I'll just search-and-replace Measure to MeasureTheory.Measure (with a porting note).

bors r+


Add 'bias', 'obfuscate' and 'tidy'

Another small batch of allowed verbs that we have ended up using since adopting this CI check! Following in the footsteps of #130 and #131 :)

@faern can you please fix the commit message? (See the failing CI.)

@mristin

@faern can you please fix the commit message? (See the failing CI.)

I already have... Please check the commits tab. I dunno why the CI did not re-run

I recommited the same thing and force pushed, just to trigger the CI. Should be fine now?

Oh, lol. It was complaining about the length of the github PR title? :joy: My god. I have been so confused about that before.
Why do you enforce that to be so short? I guess that's a more ideological question. The only reason I want to limit the length of git commit messages is so they display nicely when rendered as a tree in my terminal. For the github PR title and description none of those limitations apply.

Why do you enforce that to be so short?

I think I couldn't really separate the two in the code as far as I can remember. I'm open to changing that behavior -- please feel free to open a new issue!

But we are using this CI action and only limit git commit messages, not github PR content. It just works? :shrug: :joy:
https://github.com/mullvad/mullvadvpn-app/blob/main/.github/workflows/git-commit-message-style.yml#L25-L35

However, that is completely unrelated to this PR. Feel free to merge the extra verbs :)

But we are using this CI action and only limit git commit messages, not github PR content. It just works? 🤷 😂 https://github.com/mullvad/mullvadvpn-app/blob/main/.github/workflows/git-commit-message-style.yml#L25-L35

I think the event is crucial -- if you run it against pull request, the body will be the pull request description. I'm not really sure anymore, though.


Added Audio Steganography

Description
Here, you can see two different scripts 1. endcoder.py and 2. decoder.py. First, talking about the encoder.py. This script is used to hide the data in the audio by the LSB algorithm. The first user is requested to enter the file name and then the secret message after that script will generate an encoded audio file. Second, decoder.py is used to decode the msg from the encoded audio file. In this script, the user is requested to enter the name of the audio file and the script will automatically decode the secret msg in it. Here, I attached one sample audio file iphone.mp3.
Fixes: #790

Hello sir, I am getting an error in the Lint code base. It says (please find attachment),

As per my understanding, There is an error with setparams and writeframes but when I am running my code in my system. I am not getting any errors. Please can you help me out?

Hello sir, How can I link this PR to issue-790?
(By mistake, I closed this PR but I reopened it in a minute. So, sorry for that and looking forward to getting merged).
Thank you

Hello sir, How can I link this PR to issue-790?
(By mistake, I closed this PR but I reopened it in a minute. So, sorry for that and looking forward to getting merged).
Thank you

I have done that

I am not able to test the script locally, @antrikshmisri @santushtisharma10 can you confirm the working of the script?

@MayankkumarTank Did you update the changes suggested by @santushtisharma10?

@MayankkumarTank will you update the PR?

Sorry sir for no input from my side.
Due to health issue, i am not able to work. I was in complete bed rest. I will update it soon.
Once again sorry and Thank you.

Sorry sir for no input from my side.
Due to health issue, i am not able to work. I was in complete bed rest. I will update it soon.
Once again sorry and Thank you.

oh okay, You should have informed me in the first place. Take your time, 3-4 days or till you feel better.

@MayankkumarTank are you in the state of completing this issue? If no, then I can assign it to someone else.

PR closed and issue unassigned due to participant's health


Fix typo

Codecov Report

Merging #36 (0d0ac4f) into master (2dc2192) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #36   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            2         2
=========================================
  Hits             2         2

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 2dc2192...0d0ac4f. Read the comment docs.


Projection support

Hi, I'd like to know if someone could add projection support to this plugin, if not I'll eventually make a pull request to add it in the next month. Thank you.

It exists.


Development to Master

This is a bit of a beast. Includes all of the additional QA tabs work, and also the shinyapps.io additions. There's a number of other smaller tweaks that are in here too.

@sarahmwong - latest version should be deploying to shinyapps.io now


REFRESH HATE

Improve the refresh rate of the app. Be instant. pls.

there currently working on this. it a pinned issue.

Merging with #4180


Support fine grained authorization for API developers

Description:
In the current implementation, users under the "Creator" role can modify APIs which has been created by other users who has the same "Creator" role. This can cause some problems in an environment where API developers needs to operate independently. Providing user level (fine grained) authentication for API creation and publishing would be a really useful feature
Suggested Labels:
feature, 2.1.0
Suggested Assignees:
nuwan
Affected Product Version:
2.1.0
OS, DB, other environment details and versions:
Ubuntu 16.04
Steps to reproduce:

Create 2 users in the API Manager called "user1" and "user2" and assign them the "creator" role
Now create an API by logging into publisher with "user1" account.
Log into API publisher with "user2" account. Now you can see the API create by "user1" and edit the API.

Related Issues:

Hi @chanakaudaya ,
This has been addressed from the API Visibility control in publisher level from 2.1.0 WUM and 2.2.0 release


Supporting older Bravia KDL models with wake on lan

This pull request aims at integrating older Sony KDL models that cannot be turned ON via REST API (see Issue #14). The configuration of the plugin now provides an additional field wakeOnLan that, if set to true,  allow the plugin to use wake_on_lan to turn ON the television.
This pull request also provides a fix for older models that do not correctly show the name of the CEC devices (e.g. Playstation 4) connected to the television by showing the label instead of the title when the former is available.
Tested with BRAVIA KDL-48W605.
Summary of Changes:

Add wake_on_lan dependency to plugin
Change README with wakeOnLan field
Use label instead of title (when defined) to name a CEC input in order to show the correct connected device name (e.g. Playstation 4)
Minor refactoring and extraction of removeEntries method in accessory.js

Thanks for pull request. WOL function is now added in version 3.0

How do you handle the lack of PSK support with older models in setting up?

@ronvandeven
In a future release i will add ip controll over token instead with psk

@ronvandeven
added new function for older models without PSK support! Install the latest beta and remove PSK parameter from config.json. Follow the instructions in your LOG.

@seydx
After basically scrubbing my entire homebridge installation, I’m now running the latest beta. I’ve managed to authenticate with my older Sony TV, with 4 digit pin code in the local json file, but it will not show up in the home app.

@ronvandeven
Can u post your log pls

@SeydX
Woonkamer TV = Older Sony, non-android, succesfully authenticated with PIN in the local json file, doesn't show in the home app.Not sure if I should have used WOL
Slaapkamer TV = Android Sony, was working with V2, is showing in the home app also under V3
Config.json sample:
"platforms": [
{
"platform": "BraviaOSPlatform",
"tvs": [
{
"name": "Woonkamer TV",
"ip": "<IP_ADDRESS>",
"mac": "XX:XX:XX:XX:XX:XX",
"port": 80,
"cecInputs": true,
"wol": true
},
{
"name": "Slaapkamer TV",
"ip": "<IP_ADDRESS>",
"port": 80,
"psk": "XXXXXXXXXX",
"cecInputs": true
}
],
"interval": 10
}
]
### LOG output
[2019-4-14 20:18:20] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-14 20:18:20] ---
[2019-4-14 20:18:20] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-14 20:18:20] Loaded plugin: homebridge-bravia-tvos
[2019-4-14 20:18:20] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-14 20:18:20] Loading 1 platforms...
[2019-4-14 20:18:20] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-14 20:18:20] [BraviaOSPlatform] **************************************************************
[2019-4-14 20:18:20] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-14 20:18:20] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-14 20:18:20] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-14 20:18:20] [BraviaOSPlatform] **************************************************************
[2019-4-14 20:18:20] [BraviaOSPlatform] start success...
[2019-4-14 20:18:20] Loading 0 accessories...
[2019-4-14 20:18:20] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-14 20:18:21] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-14 20:18:21] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-14 20:18:21] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-14 20:18:21] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-14 20:18:21] Homebridge is running on port XXXXX.
[2019-4-14 20:18:21] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-14 20:18:21] [BraviaOSPlatform] [INFO] Slaapkamer TV: CEC detected, checking TV state before fetching inputs...
[2019-4-14 20:18:21] [BraviaOSPlatform] [WARN] Slaapkamer TV: TV not on! Turning on the TV...
[2019-4-14 20:18:21] [BraviaOSPlatform] [INFO] Slaapkamer TV: TV switched ON!
[2019-4-14 20:18:21] [BraviaOSPlatform] [INFO] Slaapkamer TV: Wait 7s before fetching inputs..
[2019-4-14 20:18:21] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-4-14 20:18:26] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!
[2019-4-14 20:18:26] [BraviaOSPlatform] [INFO] Woonkamer TV: CEC detected, checking TV state before fetching inputs...
[2019-4-14 20:18:26] [BraviaOSPlatform] [WARN] Woonkamer TV: Can not check TV state, because WOL is on!
[2019-4-14 20:18:26] [BraviaOSPlatform] [INFO] Woonkamer TV: Turning on TV (WOL)
[2019-4-14 20:18:26] [BraviaOSPlatform] [INFO] Woonkamer TV: TV switched ON!
[2019-4-14 20:18:26] [BraviaOSPlatform] [INFO] Woonkamer TV: Wait 7s before fetching inputs..
[2019-4-14 20:18:28] [BraviaOSPlatform] [INFO] Slaapkamer TV: New Inputs fetched. Turning off TV again.
[2019-4-14 20:18:29] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-14 20:18:29] Slaapkamer TV is running on port 32845.
[2019-4-14 20:18:29] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX

@ronvandeven
You need to add the second tv manually to Apple Home

@seydx
I’ve added the second tv manually to the home app. It is the first one the old sony model that doesn’t show up in the app.

@ronvandeven
You have also added the bridge to HomeKit?
The first one (Woonkamer) is associated to the bridge, only the tv‘s after the first one are separate accessories like Slaapkamer TV

@seydx
Yes the bridge was added as well, no TV showed up, then added the second tv manually. Second Tv is in the app and works.

@ronvandeven
can u restart homebridge and post the log again pls

@SeydX
[2019-4-14 21:34:28] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-14 21:34:28] ---
[2019-4-14 21:34:28] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-14 21:34:28] Loaded plugin: homebridge-bravia-tvos
[2019-4-14 21:34:29] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-14 21:34:29] Loading 1 platforms...
[2019-4-14 21:34:29] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-14 21:34:29] [BraviaOSPlatform] **************************************************************
[2019-4-14 21:34:29] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-14 21:34:29] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-14 21:34:29] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-14 21:34:29] [BraviaOSPlatform] **************************************************************
[2019-4-14 21:34:29] [BraviaOSPlatform] start success...
[2019-4-14 21:34:29] Loading 0 accessories...
[2019-4-14 21:34:29] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-14 21:34:29] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-14 21:34:29] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-14 21:34:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-14 21:34:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-14 21:34:29] Homebridge is running on port XXXXX.
[2019-4-14 21:34:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-14 21:34:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: CEC detected, checking TV state before fetching inputs...
[2019-4-14 21:34:30] [BraviaOSPlatform] [WARN] Slaapkamer TV: TV not on! Turning on the TV...
[2019-4-14 21:34:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: TV switched ON!
[2019-4-14 21:34:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Wait 7s before fetching inputs..
[2019-4-14 21:34:30] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-4-14 21:34:34] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!
[2019-4-14 21:34:34] [BraviaOSPlatform] [INFO] Woonkamer TV: CEC detected, checking TV state before fetching inputs...
[2019-4-14 21:34:34] [BraviaOSPlatform] [WARN] Woonkamer TV: Can not check TV state, because WOL is on!
[2019-4-14 21:34:34] [BraviaOSPlatform] [INFO] Woonkamer TV: Turning on TV (WOL)
[2019-4-14 21:34:35] [BraviaOSPlatform] [INFO] Woonkamer TV: TV switched ON!
[2019-4-14 21:34:35] [BraviaOSPlatform] [INFO] Woonkamer TV: Wait 7s before fetching inputs..
[2019-4-14 21:34:37] [BraviaOSPlatform] [INFO] Slaapkamer TV: New Inputs fetched. Turning off TV again.
[2019-4-14 21:34:38] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-14 21:34:38] Slaapkamer TV is running on port 36783.
[2019-4-14 21:34:38] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX

@ronvandeven
can you check the folder where your config.json is if there is a file called "Woonkammer TV.json"

The plugin tries to add the Woonkammer TV to HomeKit but it doesnt register as a platform, will check this

@ronvandeven
after this line

[2019-4-14 21:34:35] [BraviaOSPlatform] [INFO] Woonkamer TV: Wait 7s before fetching inputs..

Is there something else from "Woonkamer TV" ?

@SeydX
I've removed the CEC, it makes the log a bit more transparant it seems. The process for the woonkamertv stops after authentication, as you will see in the last line. No registration of external accessory
Yes I have Woonkamer TV.json file in the folder next to config.json. It has the Pin and cookie in the json.
[2019-4-14 22:28:28] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-14 22:28:28] ---
[2019-4-14 22:28:29] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-14 22:28:29] Loaded plugin: homebridge-bravia-tvos
[2019-4-14 22:28:29] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-14 22:28:29] Loading 1 platforms...
[2019-4-14 22:28:29] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-14 22:28:29] [BraviaOSPlatform] **************************************************************
[2019-4-14 22:28:29] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-14 22:28:29] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-14 22:28:29] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-14 22:28:29] [BraviaOSPlatform] **************************************************************
[2019-4-14 22:28:29] [BraviaOSPlatform] start success...
[2019-4-14 22:28:29] Loading 0 accessories...
[2019-4-14 22:28:29] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-14 22:28:29] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-14 22:28:29] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-14 22:28:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-14 22:28:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-14 22:28:29] Homebridge is running on port XXXXX.
[2019-4-14 22:28:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-14 22:28:30] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-4-14 22:28:30] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-14 22:28:31] Slaapkamer TV is running on port 35635.
[2019-4-14 22:28:31] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
[2019-4-14 22:28:34] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!

@ronvandeven
can u remove only slaapkammer and try again pls

@ronvandeven
pushed a new update. Can u reinstall and try again with two TVs pls. It will help me to debug more

@SeydX
I've downloaded the new update after removing the older plugin, but it seems now to nest in 2 locations. I don't seem to able to deinstall both only the one in my node v11 folder.
[2019-4-15 22:26:41] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-15 22:26:42] ---
[2019-4-15 22:26:42] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-bravia-tvos' since we already loaded the same plugin from '/home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos'.
[2019-4-15 22:26:42] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-15 22:26:42] Loaded plugin: homebridge-bravia-tvos
[2019-4-15 22:26:42] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-15 22:26:42] ---
[2019-4-15 22:26:42] Loaded plugin: homebridge-config-ui-x
[2019-4-15 22:26:42] Registering platform 'homebridge-config-ui-x.config'
[2019-4-15 22:26:42] ---
[2019-4-15 22:26:42] Loading 1 platforms...
[2019-4-15 22:26:42] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-15 22:26:42] [BraviaOSPlatform] **************************************************************
[2019-4-15 22:26:42] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-15 22:26:42] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-15 22:26:42] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-15 22:26:42] [BraviaOSPlatform] **************************************************************
[2019-4-15 22:26:42] [BraviaOSPlatform] start success...
[2019-4-15 22:26:42] Loading 0 accessories...
[2019-4-15 22:26:43] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-15 22:26:43] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-15 22:26:43] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-15 22:26:43] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-15 22:26:43] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-15 22:26:43] Homebridge is running on port xxxxx.
[2019-4-15 22:26:43] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-15 22:26:43] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-4-15 22:26:44] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-15 22:26:44] Slaapkamer TV is running on port 42499.
[2019-4-15 22:26:44] Please add [Slaapkamer TV] manually in Home app. Setup Code: xxx-xx-xxx
[2019-4-15 22:26:48] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!

@SeydX
I've updated the installation, but it seems no change in behavior.
[2019-4-16 20:00:06] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-16 20:00:07] ---
[2019-4-16 20:00:07] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-16 20:00:07] Loaded plugin: homebridge-bravia-tvos
[2019-4-16 20:00:07] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-16 20:00:07] ---
[2019-4-16 20:00:07] Loaded plugin: homebridge-config-ui-x
[2019-4-16 20:00:07] Registering platform 'homebridge-config-ui-x.config'
[2019-4-16 20:00:07] ---
[2019-4-16 20:00:07] Loading 1 platforms...
[2019-4-16 20:00:07] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-16 20:00:07] [BraviaOSPlatform] **************************************************************
[2019-4-16 20:00:07] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-16 20:00:07] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-16 20:00:07] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-16 20:00:07] [BraviaOSPlatform] **************************************************************
[2019-4-16 20:00:07] [BraviaOSPlatform] start success...
[2019-4-16 20:00:07] Loading 0 accessories...
[2019-4-16 20:00:07] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-16 20:00:08] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-16 20:00:08] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-16 20:00:08] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-16 20:00:08] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-16 20:00:08] Homebridge is running on port XXXXX.
[2019-4-16 20:00:08] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-16 20:00:08] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-4-16 20:00:09] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-16 20:00:09] Slaapkamer TV is running on port XXXXX.
[2019-4-16 20:00:09] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
[2019-4-16 20:00:13] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!
[2019-4-16 20:02:03] [BraviaOSPlatform] [INFO] Slaapkamer TV: Hi!
[2019-4-16 20:02:08] [BraviaOSPlatform] [INFO] Slaapkamer TV: Turn on
[2019-4-16 20:02:10] [BraviaOSPlatform] [INFO] Slaapkamer TV: Turn off

@ronvandeven
pushed new update with more debugging funcationality... pls update and post the output here
thx

@SeydX
The log is a least different, shows some errors
[2019-4-17 09:10:46] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-17 09:10:46] ---
[2019-4-17 09:10:46] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-17 09:10:46] Loaded plugin: homebridge-bravia-tvos
[2019-4-17 09:10:47] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-17 09:10:47] ---
[2019-4-17 09:10:47] Loaded plugin: homebridge-config-ui-x
[2019-4-17 09:10:47] Registering platform 'homebridge-config-ui-x.config'
[2019-4-17 09:10:47] ---
[2019-4-17 09:10:47] Loading 1 platforms...
[2019-4-17 09:10:47] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-17 09:10:47] [BraviaOSPlatform] **************************************************************
[2019-4-17 09:10:47] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-17 09:10:47] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-17 09:10:47] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-17 09:10:47] [BraviaOSPlatform] **************************************************************
[2019-4-17 09:10:47] [BraviaOSPlatform] start success...
[2019-4-17 09:10:47] Loading 0 accessories...
[2019-4-17 09:10:47] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-17 09:10:48] Homebridge is running on port XXXXX.
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Handling inputs...
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching External Inputs...
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: External Inputs fetched!
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching inputs finished!
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Collecting...
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Looking for removable inputs...
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Stop looking for removable inputs!
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Refreshing input list...
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Finished refreshing!
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Inputs Finished!
[2019-4-17 09:10:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Resolving inputs...
[2019-4-17 09:10:49] [BraviaOSPlatform] [INFO] Slaapkamer TV: Linking inputs...
[2019-4-17 09:10:49] [BraviaOSPlatform] [INFO] Slaapkamer TV: ADD: true
[2019-4-17 09:10:49] [BraviaOSPlatform] [INFO] Slaapkamer TV: EXTERNAL: 1
[2019-4-17 09:10:49] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-17 09:10:49] Slaapkamer TV is running on port 45233.
[2019-4-17 09:10:49] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
(node:20602) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'status' of undefined
at Bravia.checkAuthentication (/home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos/lib/Bravia.js:320:23)
at processTicksAndRejections (internal/process/task_queues.js:86:5)
(node:20602) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:20602) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@ronvandeven
Pushed a new update, can you reinstall and try again pls

@SeydX another step closer it feels
[2019-4-17 10:41:15] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-17 10:41:15] ---
[2019-4-17 10:41:16] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-17 10:41:16] Loaded plugin: homebridge-bravia-tvos
[2019-4-17 10:41:16] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-17 10:41:16] ---
[2019-4-17 10:41:16] Loaded plugin: homebridge-config-ui-x
[2019-4-17 10:41:16] Registering platform 'homebridge-config-ui-x.config'
[2019-4-17 10:41:16] ---
[2019-4-17 10:41:16] Loading 1 platforms...
[2019-4-17 10:41:16] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-17 10:41:16] [BraviaOSPlatform] **************************************************************
[2019-4-17 10:41:16] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-17 10:41:16] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-17 10:41:16] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-17 10:41:16] [BraviaOSPlatform] **************************************************************
[2019-4-17 10:41:16] [BraviaOSPlatform] start success...
[2019-4-17 10:41:16] Loading 0 accessories...
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-17 10:41:17] Homebridge is running on port XXXXX.
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Handling inputs...
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching External Inputs...
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: External Inputs fetched!
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching inputs finished!
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Collecting...
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Looking for removable inputs...
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Stop looking for removable inputs!
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Refreshing input list...
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Finished refreshing!
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Inputs Finished!
[2019-4-17 10:41:17] [BraviaOSPlatform] [INFO] Slaapkamer TV: Resolving inputs...
[2019-4-17 10:41:18] [BraviaOSPlatform] [INFO] Slaapkamer TV: Linking inputs...
[2019-4-17 10:41:18] [BraviaOSPlatform] [INFO] Slaapkamer TV: ADD: true
[2019-4-17 10:41:18] [BraviaOSPlatform] [INFO] Slaapkamer TV: EXTERNAL: 1
[2019-4-17 10:41:18] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-17 10:41:18] Slaapkamer TV is running on port 44067.
[2019-4-17 10:41:18] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
[2019-4-17 10:41:22] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!
[2019-4-17 10:41:22] [BraviaOSPlatform] [INFO] Woonkamer TV: Handling inputs...
[2019-4-17 10:41:22] [BraviaOSPlatform] [INFO] Woonkamer TV: Fetching External Inputs...

@ronvandeven
Pushed new update, can u try again pls

@SeydX pulled the update in, but no significant changes,
here are the latest logs
[2019-4-17 21:43:47] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-17 21:43:47] ---
[2019-4-17 21:43:47] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-17 21:43:47] Loaded plugin: homebridge-bravia-tvos
[2019-4-17 21:43:47] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-17 21:43:47] ---
[2019-4-17 21:43:47] Loaded plugin: homebridge-config-ui-x
[2019-4-17 21:43:47] Registering platform 'homebridge-config-ui-x.config'
[2019-4-17 21:43:47] ---
[2019-4-17 21:43:47] Loading 1 platforms...
[2019-4-17 21:43:47] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-17 21:43:47] [BraviaOSPlatform] **************************************************************
[2019-4-17 21:43:47] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-17 21:43:47] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-17 21:43:47] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-17 21:43:47] [BraviaOSPlatform] **************************************************************
[2019-4-17 21:43:47] [BraviaOSPlatform] start success...
[2019-4-17 21:43:47] Loading 0 accessories...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-17 21:43:48] Homebridge is running on port XXXXX.
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Handling inputs...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching External Inputs...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Recived External Inputs!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: External Inputs fetched!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching inputs finished!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Collecting...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Looking for removable inputs...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Stop looking for removable inputs!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Refreshing input list...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Finished refreshing!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Inputs Finished!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Resolving inputs...
[2019-4-17 21:43:49] [BraviaOSPlatform] [INFO] Slaapkamer TV: Linking inputs...
[2019-4-17 21:43:49] [BraviaOSPlatform] [INFO] Slaapkamer TV: ADD: true
[2019-4-17 21:43:49] [BraviaOSPlatform] [INFO] Slaapkamer TV: EXTERNAL: 1
[2019-4-17 21:43:49] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-17 21:43:49] Slaapkamer TV is running on port XXXXX.
[2019-4-17 21:43:49] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
[2019-4-17 21:43:53] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!
[2019-4-17 21:43:53] [BraviaOSPlatform] [INFO] Woonkamer TV: Handling inputs...
[2019-4-17 21:43:53] [BraviaOSPlatform] [INFO] Woonkamer TV: Fetching External Inputs...
[2019-4-18 17:57:25] [BraviaOSPlatform] [WARN] Slaapkamer TV: TV currently offline, trying to connect (this can take up to 5 minutes) ...
[2019-4-18 17:57:38] [BraviaOSPlatform] [INFO] Slaapkamer TV: Connection established!

@ronvandeven
Are u using different bravia plugin for Woonkammer TV? It seems, the plugin can not fetch the inputs from Woonkammer TV, if you are using a different plugin, it can disturb the request from this plugin.

No no other plugins on my homebridge server.
But maybe a remote control app on my iPad could interfere?

@SeydX I've checked already had deregistered the iOS app from the TV before and also removed the TV from within the iOS remote control app.
But, it seems after a while additional error details were displayed in the logs
[2019-4-17 21:43:47] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-17 21:43:47] ---
[2019-4-17 21:43:47] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-17 21:43:47] Loaded plugin: homebridge-bravia-tvos
[2019-4-17 21:43:47] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-17 21:43:47] ---
[2019-4-17 21:43:47] Loaded plugin: homebridge-config-ui-x
[2019-4-17 21:43:47] Registering platform 'homebridge-config-ui-x.config'
[2019-4-17 21:43:47] ---
[2019-4-17 21:43:47] Loading 1 platforms...
[2019-4-17 21:43:47] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-17 21:43:47] [BraviaOSPlatform] **************************************************************
[2019-4-17 21:43:47] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-17 21:43:47] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-17 21:43:47] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-17 21:43:47] [BraviaOSPlatform] **************************************************************
[2019-4-17 21:43:47] [BraviaOSPlatform] start success...
[2019-4-17 21:43:47] Loading 0 accessories...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-17 21:43:48] Homebridge is running on port XXXXX.
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Handling inputs...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching External Inputs...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Recived External Inputs!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: External Inputs fetched!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching inputs finished!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Collecting...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Looking for removable inputs...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Stop looking for removable inputs!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Refreshing input list...
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Finished refreshing!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Inputs Finished!
[2019-4-17 21:43:48] [BraviaOSPlatform] [INFO] Slaapkamer TV: Resolving inputs...
[2019-4-17 21:43:49] [BraviaOSPlatform] [INFO] Slaapkamer TV: Linking inputs...
[2019-4-17 21:43:49] [BraviaOSPlatform] [INFO] Slaapkamer TV: ADD: true
[2019-4-17 21:43:49] [BraviaOSPlatform] [INFO] Slaapkamer TV: EXTERNAL: 1
[2019-4-17 21:43:49] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-17 21:43:49] Slaapkamer TV is running on port XXXXX
[2019-4-17 21:43:49] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
[2019-4-17 21:43:53] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!
[2019-4-17 21:43:53] [BraviaOSPlatform] [INFO] Woonkamer TV: Handling inputs...
[2019-4-17 21:43:53] [BraviaOSPlatform] [INFO] Woonkamer TV: Fetching External Inputs...
[2019-4-18 17:57:25] [BraviaOSPlatform] [WARN] Slaapkamer TV: TV currently offline, trying to connect (this can take up to 5 minutes) ...
[2019-4-18 17:57:38] [BraviaOSPlatform] [INFO] Slaapkamer TV: Connection established!
[2019-4-18 22:03:45] [BraviaOSPlatform] [WARN] Slaapkamer TV: TV currently offline, trying to connect (this can take up to 5 minutes) ...
[2019-4-18 22:06:36] [BraviaOSPlatform] [INFO] Slaapkamer TV: Connection established!
(node:6913) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON
at JSON.stringify ()
at axios.then.catch.err (/home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos/lib/Bravia.js:592:85)
at processTicksAndRejections (internal/process/task_queues.js:86:5)
(node:6913) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:6913) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@ronvandeven
Pushed a new update!

@SeydX it seems woonkamer TV is no longer gets authenticated and other node:.... errors
[2019-4-22 14:42:40] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-22 14:42:40] ---
[2019-4-22 14:42:40] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-22 14:42:40] Loaded plugin: homebridge-bravia-tvos
[2019-4-22 14:42:41] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-22 14:42:41] ---
[2019-4-22 14:42:41] Loaded plugin: homebridge-config-ui-x
[2019-4-22 14:42:41] Registering platform 'homebridge-config-ui-x.config'
[2019-4-22 14:42:41] ---
[2019-4-22 14:42:41] Loading 1 platforms...
[2019-4-22 14:42:41] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-22 14:42:41] [BraviaOSPlatform] **************************************************************
[2019-4-22 14:42:41] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-22 14:42:41] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-22 14:42:41] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-22 14:42:41] [BraviaOSPlatform] **************************************************************
[2019-4-22 14:42:41] [BraviaOSPlatform] start success...
[2019-4-22 14:42:41] Loading 0 accessories...
[2019-4-22 14:42:41] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-22 14:42:41] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-22 14:42:41] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-22 14:42:42] Homebridge is running on port XXXXX.
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Handling inputs...
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching External Inputs...
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Recived External Inputs!
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: External Inputs fetched!
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching inputs finished!
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Collecting...
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Looking for removable inputs...
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Stop looking for removable inputs!
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Refreshing input list...
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Finished refreshing!
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Inputs Finished!
[2019-4-22 14:42:42] [BraviaOSPlatform] [INFO] Slaapkamer TV: Resolving inputs...
[2019-4-22 14:42:43] [BraviaOSPlatform] [INFO] Slaapkamer TV: Linking inputs...
[2019-4-22 14:42:43] [BraviaOSPlatform] [INFO] Slaapkamer TV: ADD: true
[2019-4-22 14:42:43] [BraviaOSPlatform] [INFO] Slaapkamer TV: EXTERNAL: 1
[2019-4-22 14:42:43] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-22 14:42:43] Slaapkamer TV is running on port XXXXX.
[2019-4-22 14:42:43] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
(node:1812) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON
at JSON.stringify ()
at Bravia.checkAuthentication (/home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos/lib/Bravia.js:346:32)
at processTicksAndRejections (internal/process/task_queues.js:86:5)
(node:1812) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:1812) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@ronvandeven
pushed a new update, can u try again pls

@SeydX
Less errors, but still no fix.
[2019-4-28 17:32:28] Loaded config.json with 0 accessories and 1 platforms.
[2019-4-28 17:32:28] ---
[2019-4-28 17:32:28] Plugin /home/pi/.config/versions/node/v11.14.0/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-4-28 17:32:28] Loaded plugin: homebridge-bravia-tvos
[2019-4-28 17:32:29] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-4-28 17:32:29] ---
[2019-4-28 17:32:29] Loaded plugin: homebridge-config-ui-x
[2019-4-28 17:32:29] Registering platform 'homebridge-config-ui-x.config'
[2019-4-28 17:32:29] ---
[2019-4-28 17:32:29] Loading 1 platforms...
[2019-4-28 17:32:29] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-4-28 17:32:29] [BraviaOSPlatform] **************************************************************
[2019-4-28 17:32:29] [BraviaOSPlatform] BraviaOSPlatform v3.0.0 by SeydX
[2019-4-28 17:32:29] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-4-28 17:32:29] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-4-28 17:32:29] [BraviaOSPlatform] **************************************************************
[2019-4-28 17:32:29] [BraviaOSPlatform] start success...
[2019-4-28 17:32:29] Loading 0 accessories...
[2019-4-28 17:32:29] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-4-28 17:32:29] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-4-28 17:32:29] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-4-28 17:32:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-4-28 17:32:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-4-28 17:32:29] Homebridge is running on port XXXXX.
[2019-4-28 17:32:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-4-28 17:32:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Handling inputs...
[2019-4-28 17:32:29] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching External Inputs...
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Recived External Inputs!
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: External Inputs fetched!
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Fetching inputs finished!
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Collecting...
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Looking for removable inputs...
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Stop looking for removable inputs!
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Refreshing input list...
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Finished refreshing!
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Inputs Finished!
[2019-4-28 17:32:30] [BraviaOSPlatform] [INFO] Slaapkamer TV: Resolving inputs...
[2019-4-28 17:32:31] [BraviaOSPlatform] [INFO] Slaapkamer TV: Linking inputs...
[2019-4-28 17:32:31] [BraviaOSPlatform] [INFO] Slaapkamer TV: ADD: true
[2019-4-28 17:32:31] [BraviaOSPlatform] [INFO] Slaapkamer TV: EXTERNAL: 1
[2019-4-28 17:32:31] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-4-28 17:32:31] Slaapkamer TV is running on port XXXXX.
[2019-4-28 17:32:31] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
[2019-4-28 17:32:34] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!
[2019-4-28 17:32:34] [BraviaOSPlatform] [INFO] Woonkamer TV: Handling inputs...
[2019-4-28 17:32:34] [BraviaOSPlatform] [INFO] Woonkamer TV: Fetching External Inputs...
[2019-4-28 17:40:19] [BraviaOSPlatform] [WARN] Slaapkamer TV: TV currently offline, trying to connect (this can take up to 5 minutes) ...
[2019-4-28 17:40:36] [BraviaOSPlatform] [INFO] Slaapkamer TV: Connection established!

@ronvandeven
pushed a new update (v3.0.3) can u try again pls

Hi @SeydX
I'm running your latest build, the log got a little smaller.
Unfortunately still not working. Here is the log:
[2019-5-1 22:17:32] Loaded config.json with 0 accessories and 1 platforms.
[2019-5-1 22:17:32] ---
[2019-5-1 22:17:32] Plugin /usr/local/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-5-1 22:17:32] Loaded plugin: homebridge-bravia-tvos
[2019-5-1 22:17:33] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-5-1 22:17:33] ---
[2019-5-1 22:17:33] Loaded plugin: homebridge-config-ui-x
[2019-5-1 22:17:33] Registering platform 'homebridge-config-ui-x.config'
[2019-5-1 22:17:33] ---
[2019-5-1 22:17:33] Loading 1 platforms...
[2019-5-1 22:17:33] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-5-1 22:17:33] [BraviaOSPlatform] **************************************************************
[2019-5-1 22:17:33] [BraviaOSPlatform] BraviaOSPlatform v3.0.6 by SeydX
[2019-5-1 22:17:33] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-5-1 22:17:33] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-5-1 22:17:33] [BraviaOSPlatform] **************************************************************
[2019-5-1 22:17:33] [BraviaOSPlatform] start success...
[2019-5-1 22:17:33] Loading 0 accessories...
[2019-5-1 22:17:33] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-5-1 22:17:33] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-5-1 22:17:33] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-5-1 22:17:33] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-5-1 22:17:33] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-5-1 22:17:33] Homebridge is running on port XXXXX.
[2019-5-1 22:17:33] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-5-1 22:17:34] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-5-1 22:17:34] [BraviaOSPlatform] [INFO] Slaapkamer TV: Inputs Finished!
[2019-5-1 22:17:34] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-5-1 22:17:34] Slaapkamer TV is running on port XXXXX.
[2019-5-1 22:17:34] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
[2019-5-1 22:17:38] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!

@ronvandeven
please start Homebridge in Debug mode with
homebridge -D
or via systemd
DEBUG=BraviaPlatform,BraviaPlatformApi
and can u try Woonkammer without wol pls? (wol=false)

@SeydX
Situation 1:
WOL set to false , TV off, Debug on
[2019-5-4 10:33:00] Loaded config.json with 0 accessories and 1 platforms.
[2019-5-4 10:33:00] ---
[2019-5-4 10:33:00] Plugin /usr/local/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-5-4 10:33:00] Loaded plugin: homebridge-bravia-tvos
[2019-5-4 10:33:00] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-5-4 10:33:00] ---
[2019-5-4 10:33:00] Loaded plugin: homebridge-config-ui-x
[2019-5-4 10:33:00] Registering platform 'homebridge-config-ui-x.config'
[2019-5-4 10:33:00] ---
[2019-5-4 10:33:01] Loading 1 platforms...
[2019-5-4 10:33:01] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-5-4 10:33:01] [BraviaOSPlatform] **************************************************************
[2019-5-4 10:33:01] [BraviaOSPlatform] BraviaOSPlatform v3.0.6 by SeydX
[2019-5-4 10:33:01] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-5-4 10:33:01] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-5-4 10:33:01] [BraviaOSPlatform] **************************************************************
[2019-5-4 10:33:01] [BraviaOSPlatform] start success...
[2019-5-4 10:33:01] Loading 0 accessories...
[2019-5-4 10:33:01] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-5-4 10:33:01] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-5-4 10:33:01] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-5-4 10:33:01] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-5-4 10:33:01] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-5-4 10:33:01] Homebridge is running on port XXXXX.
[2019-5-4 10:33:01] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-5-4 10:33:02] [BraviaOSPlatform] [INFO] Slaapkamer TV: Inputs Finished!
[2019-5-4 10:33:02] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-5-4 10:33:02] Slaapkamer TV is running on port XXXXX.
[2019-5-4 10:33:02] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
[2019-5-4 10:33:05] [BraviaOSPlatform] [ERROR] Error: connect EHOSTUNREACH <IP_ADDRESS>:80
[2019-5-4 10:33:05] [BraviaOSPlatform] [ERROR] Error: connect EHOSTUNREACH <IP_ADDRESS>:80
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1088:14)
Situation 2:
TV on, WOL set to False, Debug On
[2019-5-4 10:36:19] Loaded config.json with 0 accessories and 1 platforms.
[2019-5-4 10:36:19] ---
[2019-5-4 10:36:19] Plugin /usr/local/lib/node_modules/homebridge-bravia-tvos requires Node version of ^8.9.1 which does not satisfy the current Node version of v11.14.0. You may need to upgrade your installation of Node.
[2019-5-4 10:36:19] Loaded plugin: homebridge-bravia-tvos
[2019-5-4 10:36:20] Registering platform 'homebridge-bravia-tvos.BraviaOSPlatform'
[2019-5-4 10:36:20] ---
[2019-5-4 10:36:20] Loaded plugin: homebridge-config-ui-x
[2019-5-4 10:36:20] Registering platform 'homebridge-config-ui-x.config'
[2019-5-4 10:36:20] ---
[2019-5-4 10:36:20] Loading 1 platforms...
[2019-5-4 10:36:20] [BraviaOSPlatform] Initializing BraviaOSPlatform platform...
[2019-5-4 10:36:20] [BraviaOSPlatform] **************************************************************
[2019-5-4 10:36:20] [BraviaOSPlatform] BraviaOSPlatform v3.0.6 by SeydX
[2019-5-4 10:36:20] [BraviaOSPlatform] GitHub: https://github.com/SeydX/homebridge-bravia-tvos
[2019-5-4 10:36:20] [BraviaOSPlatform] Email<EMAIL_ADDRESS>[2019-5-4 10:36:20] [BraviaOSPlatform] **************************************************************
[2019-5-4 10:36:20] [BraviaOSPlatform] start success...
[2019-5-4 10:36:20] Loading 0 accessories...
[2019-5-4 10:36:20] [BraviaOSPlatform] [INFO] Adding new accessory: Woonkamer TV
[2019-5-4 10:36:20] [BraviaOSPlatform] [INFO] Woonkamer TV: Initalizing Bravia API with IP Control
[2019-5-4 10:36:20] [BraviaOSPlatform] [INFO] Woonkamer TV: Cheking authentication...
[2019-5-4 10:36:20] [BraviaOSPlatform] [INFO] Slaapkamer TV: Initalizing Bravia API with PSK
[2019-5-4 10:36:20] [BraviaOSPlatform] [INFO] Slaapkamer TV: Cheking authentication...
[2019-5-4 10:36:20] Homebridge is running on port XXXXX.
[2019-5-4 10:36:20] [BraviaOSPlatform] [INFO] Slaapkamer TV: Authenticated!
[2019-5-4 10:36:21] [BraviaOSPlatform] [INFO] Woonkamer TV: Woonkamer TV.json refreshed with new cookie!
[2019-5-4 10:36:21] [BraviaOSPlatform] [INFO] Slaapkamer TV: Inputs Finished!
[2019-5-4 10:36:21] [BraviaOSPlatform] [INFO] Registring external accessory: Slaapkamer TV
[2019-5-4 10:36:21] Slaapkamer TV is running on port XXXXX.
[2019-5-4 10:36:21] Please add [Slaapkamer TV] manually in Home app. Setup Code: XXX-XX-XXX
[2019-5-4 10:36:25] [BraviaOSPlatform] [INFO] Woonkamer TV: Authenticated!
Situation 3
TV on, WOL set to true, Debug on
Same log as Situation 2


Display framebuffer allocation

Problem
Most drivers do not provide a framebuffer but the display interface seems to assume a framebuffer is used. (Example drawing a horizontal line 64 pixels might require 64 bytes of buffer).
This is probably why cfb allocates it's own framebuffer. However this is a problem as the buffer can not be used for other things like drawing a line or add a logo next to the rendered text. Having separate buffers is not a option as most(?) drivers requires blocks of 8x8 pixels or larger for write(). It is also a waste of memory to have multiple framebuffers if not needed.
Solution (suggestion)

cfb should at least try to get the framebuffer from the driver before calling k_malloc.
Perhaps have something like CONFIG_DISPLAY_DRIVER_FRAMEBUFFER that requires the drivers to allocate a framebuffer at compile time?

A problem with suggested solution is that it is not clear what buffer size, pitch etc display_get_framebuffer(const struct device *dev) will return. If for example this buffer would be passed to display_write(), then what would the struct display_buffer_descriptor *desc argument be?

Most drivers do not provide a framebuffer but the display interface seems to assume a framebuffer is used. (Example drawing a horizontal line 64 pixels might require 64 bytes of buffer).

No, that depends on the pixel format, and you can draw a line with very small buffer sufficient for minimum addressable unit that a display controller supports, for example 3 bytes for one RGB_888 pixel, a buffer multiple of 3 makes it faster to draw a line but is not required.

This is probably why cfb allocates it's own framebuffer. However this is a problem as the buffer can not be used for other things like drawing a line or add a logo next to the rendered text. Having separate buffers is not a option as most(?) drivers do not support write of individual pixels.. It is also a waste of memory to have multiple framebuffers if not needed.

CFB was designed before display controller driver API, it can be changed to use smaller buffer to render the characters. It is not designed to render graphic primitives, there was no need, although this can also be changed too.

Solution (suggestion)
* cfb should at least try to get the framebuffer from the driver before calling k_malloc.

Not really sure what do you mean by "framebuffer form the driver", rather cfb can be optimized to use smaller buffers.

* Perhaps have something like `CONFIG_DISPLAY_DRIVER_FRAMEBUFFER` that requires the drivers to allocate a framebuffer at compile time?

That also does not make sense.
I do not see what the concrete enhancement should be, it rather question round.


operator camel-k (1.11.0)

Signed-off-by: Andrea Cosentino<EMAIL_ADDRESS>Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description of the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

Could this be merged? Thanks.

/test 4.12-deploy-operator-on-openshift

| /test 4.11-deploy-operator-on-openshift
-- | --

/test 4.11-deploy-operator-on-openshift

/merge possible


idea: support yo-yo

idea: support yo-yo
yo-yo comes in weighing about 10KB less than virtual-dom, and is equally flexible. In the examples it seems mostly focused on creating self-contained elements, but I don't see why it wouldn't be possible to use it as a virtual-app backend - which I've found to work very well for managing complexity.
changes
Though yo-yo and virtual-dom seem mostly compatible, there are a couple of changes that should be made:

[ ] change app.h from hyperscript to hyperx - the biggest and most controversial change, this could potentially warrant creating a different package instead
[ ] loosen up virtual-raf to accept different diffing methods (e.g. yo.update(old, new)

It might be worth revisiting #3; as apparently hyperscript no longer is the lowest common denominator - hyperx appears to be closer. I quite like the idea of having a super flexible framework that only overlays a certain pattern on top of components of a choosing - I think it could definitely work for virtual-app without introducing too much scope creep.
wrapping up
And that's about it I think. We're already returning a DOM node that can be appended, so that was a very good change in hindsight. Let me know what you think! :sparkles:
see also

https://www.npmjs.com/package/yo-yo
https://www.npmjs.com/package/virtual-raf
https://www.npmjs.com/package/bel
https://www.npmjs.com/package/morphdom

Don't mean to derail this, totally OK to open separate thread, but curious if you had considered snabbdom instead of virtual-dom ? It is supposedly more performant and offers more hooks and support for things like animations... Thoughts?

Very interesting - just 200 lines of code is pretty cool! It looks like they're using a slightly different syntax than virtual-dom though. I'm starting to think that perhaps the only reasonable approach to dealing with different libraries is to have a html-as-template-literal syntax that can then be translated down to whatever engine, perhaps using compile time transforms to make it fast. Also not sure I dig the whole react / android-esque event system.

Actually now that im looking more at yoyo, its really exciting, and way more in line w/ my modular npm approach than snabddom.  Happen to be a max ogden fan as well so that doesnt hurt.  I'm noticing that a huge component of yoyo is bel and found this: https://github.com/shama/bel/wiki#elements-on-npmjscom  – npm-ability of components is basically what im looking for here so thats a positive sign.  i'll keep an eye out here as virtual-app leveraging this could be the sweet spot im looking for, and if so i may be able to get my team to contribute to the project. thanks for fielding all my questions!

:+1: I'm going to experiment with bel & yo-yo today / this week.
Getting hyperxify or a new transform working with bel/yo-yo is the only main concern I have: https://github.com/shama/bel/issues/7

I have a transform almost ready for shama/bel#7 and the early perf and file size results look really promising.
But currently without a transform, I get very similar perf results creating trees with virtual-dom and yo-yo but the difference is, yo-yo has already created an element in that time where virtual-dom would still need to render to actual elements.
In the meantime, one could use hyperxify now by doing:
var createElement = require('bel').createElement
var hyperx = require('hyperx')
var yo = hyperx(createElement)

Then hyperxify will recognize the require to hyperx and replace it with calls directly to createElement. You get a little perf boost and support older browsers.

@shama rad! i'll watch for that transform & use the method you describe for now.

I'm leaning toward not integrating yo-yo with virtual-app, mostly because I made this tiny state module send-action, and a usage example with it and yo-yo seems easier to reason about than virtual-app's basic example:
var yo = require('yo-yo')
var sendAction = require('send-action')

/*
* Create send function.
*/
var send = sendAction({
  onaction: onaction,
  onchange: onchange,
  state: { value: 'ok' }
})

/*
* Set up the action handler to modify state based on the actions triggered
*/
function onaction (action, state) {
  if (action.type === 'example') {
    return { value: action.value }
  }
}

/*
* Subscribe to changes to the store to render the app
*/
function onchange (action, state, oldState) {
  yo.update(document.getElementById('app'), render(state))
}

/*
* Render the html of the app with yo-yo
*/
function render (state) {
  return yo`<div id="app">${state.value}</div>`
}

/*
* Attach the html to the dom
*/
document.body.appendChild(render(send.state()))

/*
* Send an action to the store
*/
send({ type: 'example', value: 'cool' })

Yeah, I quite like it. If we add a lil RAF as a separate thing we're back where we started. Neat, thanks!


You must have the Azure Functions Core Tools installed to debug your local functions although it's installed globally

Hi,
In this closed issue #1750, it's stated that we have to install core-tools package globally. Actually, it was working before but after I just change between branches, this error occurred again:

Since we use v3 version of the tools, I installed it with npm i -g azure-functions-core-tools@3 --unsafe-perm true but it still occurs. If I launch code from terminal it works no problem, but although my json files configured, debug mode is not working at all. I tried those below but unfortunately I still can't launch in debug mode;

Reinstalling the package
Closing and reopening vscode
Checking out my launch file configurations

I know it's a simple issue but all suggestions are welcomed 😅. Thanks in advance!

Does the problem reoccur when you completely close out and restart VS Code? If the command works in the terminal, I'm wondering if the path just hasn't been picked up yet by the VS Code terminal

Does the problem reoccur when you completely close out and restart VS Code? If the command works in the terminal, I'm wondering if the path just hasn't been picked up yet by the VS Code terminal

Thanks for the reply! The command to start "func start" works out well in the terminal but debugger still does not responding at all. I tried completely shutting down and restarting either vscode and my device. But still not working :(

Hello again, I literally changed nothing since I opened this issue. But today, it just wanted to work and now, fortunately my debugger works well. Thanks for the help Matthew! I can only guess, since I configured json files right, it just needed some days-time to run 😄


Create "PelotonMain" object

There is no single object that encapsulates the different objects in the system. Both @malin1993ml and @sid1607 have the problem that they need to maintain stateful objects that are used in different parts of the system but there is no single location to put them. The TrafficCop object is really just a bunch of static methods, so it's not really the right place.
I propose that  create a new class called PelotonMain that is responsible for instantiating the different parts of the system and connecting them together (e.g., thread pools, optimizer, traffic cop, executors). We can make this a singleton object that can be retrieved by any part of the system that needs it (need to think about this, it might be a bad idea).

From my experience, for the following components, we should have the orders below:

epoch manager -> gc manager
epoch manager -> log manager -> transaction worker threads / networking threads

Currently their initialization order depends on whose GetInstance() method gets called first... I have to manually call the GetInstance() to enforce the order in our micro-benchmarks...
For the implementation, I think it's good to have a class that is in charged of all the initialization logic. May be each component (e.g. epoch_manager, gc_manager, thread_pool) should have a uniform interface of  Init(...) and Start(...), where Init() initializes the parameters of the component and Start() spawns threads of that component. The centralized init logic can call Init() and Start() of different components to enforce the order.


How can I compile it?

I spent 2 hours now trying to compile the solution...
How can I get it running?
ANT always fails with missing dependencies..
Thanks.

Hello Kim,
Sorry to hear that ... I will look into that.
You can use the realise in the meantime:
https://github.com/pknoe3lh/WordClockGenerator/releases

Moved to Maven!
Now it should be no problem I hope!
greetings
Patrick

Please add the release links into the README.md file. I spent an hour trying to run this both on Linux and Windows. No luck. I was just about to report an issue, then I found this! :)

Done!


fix(ui): bump dependencies

Description
See title
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Also curious why core is needed in auth but not firestore and database? Is it not transitive?

Does this need bumping to 10.0.1? https://github.com/firebase/flutterfire/blob/50794a8cd41e20071bd82cdee15133a1849e9f4e/packages/flutterfire_ui/pubspec.yaml#L22

and this to 4.0.1? https://github.com/firebase/flutterfire/blob/50794a8cd41e20071bd82cdee15133a1849e9f4e/packages/flutterfire_ui/pubspec.yaml#L22


Inconsistent unit test result

What steps did you take and what happened:
Unit tests under pkg/image deliver inconsistent result
What did you expect to happen:
Unit tests should be consistent
Anything else you would like to add:
My initial reaction is probably improper mock or race conditions. This occurred on CircleCI on 2b8d1eabc96070954a3fad5c482973fffefd2506 as part of #1179.
Failed on first run, but without anything being changed, it passed on second run.

@wilsonehusin yes, the CI is flaky.  The workaround is to kick off the entire job after a failure.  We will need to address this issue and possibly re-write the CI jobs.

Investigation

seems like it was surfaced here (line 178) https://github.com/vmware-tanzu/sonobuoy/blob/7419e1d901b5c57ab23dbf971a80a5203a9dbeda/pkg/image/manifest_test.go#L170-L179

inspecting the value of imageTagPairs, turns out not all registries were overwritten (I've sorted the output here to show the first section where the paths were not replaced vs the second section where they were properly replaced)

example output
{docker.io/gluster/glusterdynamic-provisioner:v1.0 docker.io/gluster/glusterdynamic-provisioner:v1.0}
{gcr.io/authenticated-image-pulling/alpine:3.7 gcr.io/authenticated-image-pulling/alpine:3.7}
{gcr.io/k8s-authenticated-test/agnhost:2.6 gcr.io/k8s-authenticated-test/agnhost:2.6}
{gcr.io/google-containers/startup-script:v1 gcr.io/google-containers/startup-script:v1}
{invalid.com/invalid/alpine:3.1 invalid.com/invalid/alpine:3.1}
{gcr.io/authenticated-image-pulling/windows-nanoserver:v1 gcr.io/authenticated-image-pulling/windows-nanoserver:v1}
{quay.io/kubernetes_incubator/nfs-provisioner:v2.2.2 quay.io/kubernetes_incubator/nfs-provisioner:v2.2.2}

{gcr.io/kubernetes-e2e-test-images/apparmor-loader:1.0 my-custom/registry/apparmor-loader:1.0}
{gcr.io/kubernetes-e2e-test-images/cuda-vector-add:1.0 my-custom/registry/cuda-vector-add:1.0}
{k8s.gcr.io/pause:3.1 my-custom/registry/pause:3.1}
{gcr.io/kubernetes-e2e-test-images/test-webserver:1.0 my-custom/registry/test-webserver:1.0}
{k8s.gcr.io/etcd:3.4.3 my-custom/registry/etcd:3.4.3}
{docker.io/library/httpd:2.4.38-alpine my-custom/registry/httpd:2.4.38-alpine}
{docker.io/library/httpd:2.4.39-alpine my-custom/registry/httpd:2.4.39-alpine}
{gcr.io/kubernetes-e2e-test-images/nonroot:1.0 my-custom/registry/nonroot:1.0}
{gcr.io/kubernetes-e2e-test-images/resource-consumer-controller:1.0 my-custom/registry/resource-consumer-controller:1.0}
{gcr.io/kubernetes-e2e-test-images/metadata-concealment:1.2 my-custom/registry/metadata-concealment:1.2}
{gcr.io/kubernetes-e2e-test-images/nonewprivs:1.0 my-custom/registry/nonewprivs:1.0}
{k8s.gcr.io/prometheus-dummy-exporter:v0.1.0 my-custom/registry/prometheus-dummy-exporter:v0.1.0}
{gcr.io/kubernetes-e2e-test-images/volume/nfs:1.0 my-custom/registry/volume/nfs:1.0}
{gcr.io/kubernetes-e2e-test-images/cuda-vector-add:2.0 my-custom/registry/cuda-vector-add:2.0}
{gcr.io/kubernetes-e2e-test-images/dnsutils:1.1 my-custom/registry/dnsutils:1.1}
{gcr.io/kubernetes-e2e-test-images/ipc-utils:1.0 my-custom/registry/ipc-utils:1.0}
{docker.io/library/nginx:1.14-alpine my-custom/registry/nginx:1.14-alpine}
{k8s.gcr.io/sd-dummy-exporter:v0.2.0 my-custom/registry/sd-dummy-exporter:v0.2.0}
{gcr.io/kubernetes-e2e-test-images/volume/iscsi:2.0 my-custom/registry/volume/iscsi:2.0}
{gcr.io/kubernetes-e2e-test-images/sample-apiserver:1.10 my-custom/registry/sample-apiserver:1.10}
{gcr.io/kubernetes-e2e-test-images/mounttest:1.0 my-custom/registry/mounttest:1.0}
{docker.io/library/perl:5.26 my-custom/registry/perl:5.26}
{docker.io/library/redis:5.0.5-alpine my-custom/registry/redis:5.0.5-alpine}
{gcr.io/kubernetes-e2e-test-images/regression-issue-74839-amd64:1.0 my-custom/registry/regression-issue-74839-amd64:1.0}
{gcr.io/kubernetes-e2e-test-images/resource-consumer:1.5 my-custom/registry/resource-consumer:1.5}
{gcr.io/kubernetes-e2e-test-images/volume/gluster:1.0 my-custom/registry/volume/gluster:1.0}
{gcr.io/kubernetes-e2e-test-images/agnhost:2.8 my-custom/registry/agnhost:2.8}
{docker.io/library/busybox:1.29 my-custom/registry/busybox:1.29}
{gcr.io/kubernetes-e2e-test-images/echoserver:2.2 my-custom/registry/echoserver:2.2}
{gcr.io/kubernetes-e2e-test-images/jessie-dnsutils:1.0 my-custom/registry/jessie-dnsutils:1.0}
{gcr.io/kubernetes-e2e-test-images/nautilus:1.0 my-custom/registry/nautilus:1.0}
{docker.io/library/nginx:1.15-alpine my-custom/registry/nginx:1.15-alpine}
{gcr.io/kubernetes-e2e-test-images/kitten:1.0 my-custom/registry/kitten:1.0}
{gcr.io/kubernetes-e2e-test-images/mounttest-user:1.0 my-custom/registry/mounttest-user:1.0}
{k8s.gcr.io/prometheus-to-sd:v0.5.0 my-custom/registry/prometheus-to-sd:v0.5.0}
{gcr.io/kubernetes-e2e-test-images/volume/rbd:1.0.1 my-custom/registry/volume/rbd:1.0.1}

seems like this might be origin of drift, where only some of the registries were modified (lines 127-130) https://github.com/vmware-tanzu/sonobuoy/blob/7419e1d901b5c57ab23dbf971a80a5203a9dbeda/pkg/image/manifest_test.go#L121-L146
fortunately (unfortunately?) the test above writes to a config file in /tmp (Mac might have a different directory due to TempFile implementation, I'm on Linux) which was not deleted at the end of test run. here's an example value which I found on my computer:
buildImageRegistry: ""
dockerGluster: docker.io/gluster
dockerLibraryRegistry: my-custom/registry
e2eRegistry: my-custom/registry
e2eVolumeRegistry: ""
gcRegistry: my-custom/registry
googleContainerRegistry: gcr.io/google-containers
promoterE2eRegistry: ""
quayIncubator: quay.io/kubernetes_incubator
sampleRegistry: my-custom/registry
sigStorageRegistry: ""

while I'm tempted to straight up modify the code above to add the rest of registries, I've found the following lines as well:
https://github.com/vmware-tanzu/sonobuoy/blob/7419e1d901b5c57ab23dbf971a80a5203a9dbeda/pkg/image/manifest.go#L302-L316

Proposal solution
I think it is correct for invalidRegistry, gcAuthenticatedRegistry, and privateRegistry to remain as is, for they are used to validate image pulling behavior. Therefore, I think they should remain untouched.
With that being said, imageTagPairs in our test will always have some of its members to not be prefixed with my-custom/registry.
I think we should only assert the values where we specifically modify the registries, i.e. choosing one/any/all of e2eRegistry, dockerLibraryRegistry, or gcRegistry deterministically.

@vladimirvivien do you have thoughts on the solution?

@wilsonehusin you know how I feel about this part of the code.  For now, any fix that would make things better is welcome.  By the way thanks for looking into this with such insight.


dcp-925 large dataset crashes graph validation

optimise handling of big datasets:

batch commit to neo4j
no need to maintain entities in a dict with uuids as keys. It is a waste of memory and costs a lot during entry and extraction. A simple list is enough.

Adding informative logging messages every 1000 records. This could be deleted when the problem is solved.
This improves generating the nodes list and loading to neo.
The edges generation is still not scaling well. It starts fast, but there is degradation after a few thousand edges. Running locally is impractical due to this. Installation on dev is required to check whether the current optimisations are enough at this point.
dcp-925
ebi-ait/dcp-ingest-central#925

@aaclan-ebi please also review this PR. It's already merged, but I would like your opinion.

Looks like these changes are now in dev and prod. Once @ESapenaVentura's changes are deployed in prod, we should test the performance of graph validation for large submissions.


Split "Installation" docs up into "Pip/Local" and "Docker" sections

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2246
Originally created by @DouweM on 2020-08-12 16:05:12

View 2 previous comments from the original issue on GitLab


Install issue

First, great project and good job.  I had a small issue with the dependencies.  Is the CLI supposed to download all the dependencies?
Here's how to repeat my issue:
Here's my steps:

reactql new
cd .\reactql-app
npm start
...
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: webpack-dev-server --colors
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'webpack-dev-server --colors'.
...

then did a npm install and it fixed the issue.

npm install

Thanks for reporting, @RuairiSpain.
Yes, the reactql tool is supposed to install all NPM packages for you. It does this with yarn (if it's installed) or falls back to npm if not available (which should theoretically be on all platforms that Node.js was installed on, unless you installed from source/binaries manually.)
Please provide answers to the following:

What OS are you using?
What's the output from...
reactql version?
npm -v
node -v

Hi @leebenson , here's more info.   I've got both yarn and npm installed.  It's likely the script used yarn for the packages and I used blindly did what the getting started guide told me.  I used "npm start"  and probably should have done yarn start.
Windows 10
Error was caused by "npm start", see more details at end of post
reactql 2.2.0
npm -v 3.10.9
node -v 7.9.0
yarn 0.21.3
PS C:....\reactql-app> npm start

<EMAIL_ADDRESS>start C:...\reactql-app
webpack-dev-server --colors

'webpack-dev-server' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Windows_NT 10.0.15063
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\ruair\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v7.9.0
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: webpack-dev-server --colors
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'webpack-dev-server --colors'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the reactql-app package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     webpack-dev-server --colors
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs reactql-app
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls reactql-app
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\ruair\Documents\GitHub\reactql\reactql-app\npm-debug.log

Thanks for the info @RuairiSpain. It's very strange that Yarn/NPM isn't being invoked after installing- I tested on my local Windows 10 machine with both yarn and NPM installed, and couldn't replicate the issue.
I'll keep this issue open and do more testing. In the meantime, if anyone else is running into problems with Windows, manually doing the npm install step seems to fix it.

Updating to the latest version of my npm and global packages did it for me.

After further testing, I haven't been able to replicate this issue on my local Windows machine, so hopefully it was a one-off. I'll close this for now - but if anyone else runs into the same problem, will investigate further.


Build using Docker failed

Build of current master fails with
#15 63.85 sh: 1: cannot open html: No such file
#15 63.85 sh: 2: Syntax error: redirection unexpected

in
 => ERROR [run 5/6] RUN /opt/ort/bin/import_proxy_certs.sh &&     if [ -n "$CRT_FILES" ]; then       /opt/ort/bi
 => CANCELED [build 4/4] RUN --mount=type=cache,target=/tmp/.gradle/     export GRADLE_USER_HOME=/tmp/.gradle/ &

Looks more like a temporary network hiccup... and our CI builds for the Docker image seem to still succeed.

thx about the hint
it was indeed only a problem with my network


Enhancements to support IL-DCP (new & improved)

Update to 0.16.0-SNAPSHOT
Fix Jackson security (see security alerts)
Add unit tests for all IL-DCP classes
Improve Javadoc in various classes
Remove deprecated InterledgerPacketMapper.
Fixes #144
Fixes #145

Signed-off-by: sappenin<EMAIL_ADDRESS>

Codecov Report

Merging #183 into master will decrease coverage by 0.17%.
The diff coverage is 64.51%.

@@             Coverage Diff              @@
##             master     #183      +/-   ##
============================================
- Coverage     70.86%   70.69%   -0.18%
- Complexity      331      360      +29
============================================
  Files            99      111      +12
  Lines          1596     1723     +127
  Branches        155      157       +2
============================================
+ Hits           1131     1218      +87
- Misses          396      434      +38
- Partials         69       71       +2

Impacted Files
Coverage Δ
Complexity Δ

...n/codecs/AsnInterledgerFulfillPacketDataCodec.java
100% <ø> (ø)
3 <0> (ø)
:arrow_down:

...org/interledger/core/InterledgerFulfillPacket.java
50% <ø> (ø)
1 <0> (ø)
:arrow_down:

...org/interledger/core/InterledgerPreparePacket.java
100% <ø> (ø)
2 <0> (ø)
:arrow_down:

...n/codecs/AsnInterledgerPreparePacketDataCodec.java
100% <ø> (ø)
3 <0> (ø)
:arrow_down:

.../main/java/org/interledger/ildcp/IldcpRequest.java
0% <0%> (ø)
0 <0> (?)

...rc/main/java/org/interledger/ildcp/IldcpUtils.java
0% <0%> (ø)
0 <0> (?)

...g/interledger/ildcp/IldcpResponsePacketMapper.java
0% <0%> (ø)
0 <0> (?)

...dcp/asn/codecs/AsnIldcpRequestPacketDataCodec.java
100% <100%> (ø)
3 <3> (?)

.../asn/framework/InterledgerCodecContextFactory.java
91.66% <100%> (ø)
1 <0> (ø)
:arrow_down:

...r/ildcp/asn/codecs/AsnIldcpRequestPacketCodec.java
100% <100%> (ø)
1 <1> (?)

... and 20 more

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 2703db0...1c625c0. Read the comment docs.

@adrianhopebailie @sublimator This one is ready for review now.


full api documentation

namely, all the options. Docs for custom flavors/suffixes/suffixGroups/formats are all missing too.

https://erosson.github.io/swarm-numberformat/
npm run push-doc


Feature request emulator support

When do you guys think you could work that in specifically support for yuzu

Never. It is not up to us to implement the missing parts of Yuzu for Skyline to run.
This is designated with consoles in mind, and emulation is just not far enough yet for it to work, so you'll have to be patient.
Some work is being done on Ryujinx to run it though.

No yeah I realized like two minutes after I sent this sorry for that lol

@ZombiePelican007 any progress on this front will likely be happening in the yuzu repo's issue instead: https://github.com/yuzu-emu/yuzu/issues/6076


Remove unnecessary information from TYPY3 section (docs)

The Problem/Issue/Bug:
That page is too convoluted already. Information that is not specific to a framework should not be unnecessarily repeated there.
How this PR Solves The Problem:
This removes information unspecific to TYPO3 from that section.
As a drive-by change it beautifies the big bold block for legacy TYPO3
installation.

Thanks so much for maintaining this important stuff! I moved that one sentence and rebased.
I did change your ddev config --... to just ddev config since it's good for people to learn that ddev will autodetect almost everything almost always.