text:
Measure V2

Start with new cleaner architecture for measuring. DRY code and allow to switch power meters and light controllers easily without changing the measure logic
Todo:

[x] Switchable light controllers / power meters using some selection procedure / factories.
[x] Move sensitive configuration which should not be commited to .env file
[x] Implement Kasa powermeter
[x] Implement Tasmota powermeter
[x] Allow user to select light entity_id from a list
[x] Implement some error handling in the API responses
[x] Retry mechanism in hass power meter to wait for a recent measurement
[ ] Take multiple measurement and pick the average (see for example current kasa implementation).
[x] Automatic gzipping of CSV files
[x] Ask measure information so we can add this in model.json
[x] Format model.json
[ ] Validate power meter and light controller configurations

Thank you for your work. A few more notes about the readme:

On Windows you can't run "source measure/bin/activate".  Source does not exist here.
The requirements.txt is still missing

Unfortunately, measure.py cannot be executed correctly on my system either.

Thank you for your work. A few more notes about the readme:

On Windows you can't run "source measure/bin/activate".  Source does not exist here.

Thanks, will add a note that creating a virtual env is optional.

The requirements.txt is still missing

Yes still need to add it.

Unfortunately, measure.py cannot be executed correctly on my system either.

I had this kind of error before. I think it's because of python version. Will add a potential fix soon

I have added a commit which maybe solves your error. Could you try again?

Sorry, still not working for me:

Yes, it works now, thank you.
However, with your version I always get a blank line between records in the CSV. This was already the case with your V1. In my Tasmota version I had fixed this with newline='' when opening the CSV (see here). But I don't know why this happens apparently only with me.
Furthermore you take so far only one value. Therefore I receive with your version also still more noise than with mine. Maybe it makes sense either to take several values and calculate the average (like with my version) or later not only to interpolate, but also to smooth and remove outliers.

Yes, it works now, thank you.
However, with your version I always get a blank line between records in the CSV. This was already the case with your V1. In my Tasmota version I had fixed this with newline='' when opening the CSV (see here). But I don't know why this happens apparently only with me.

Ok thanks for noticing. Will incoorporate this in the code.

Furthermore you take so far only one value. Therefore I receive with your version also still more noise than with mine. Maybe it makes sense either to take several values and calculate the average (like with my version) or later not only to interpolate, but also to smooth and remove outliers.

It's already in the task list.

@stefangries Taking multiple samples is also implemented. You can set SAMPLE_COUNT=3 in .env file.
Also added the requirements.txt
Only thing left is implement a mechanism to check if measurements are recent enough.

First version of new script is finished. @CM000n @stefangries @smonesi @nepozs @OzGav, are any of you able to test the new tooling and give me feedback before I release this to public?
https://github.com/bramstroker/homeassistant-powercalc/tree/feature/measure_v2 here you can download or checkout the code. In utils/measure_v2 is a README.md which should you get up and running.

I tried the kasa implementation, it doesn't work (it keeps looping on sample 0 until it stops).
As usual, I'm not a python expert, but this does seem to fix (since it looked like the "default" time.time() was not accepted):
    return PowerMeasurementResult(float(power),time.time())

I appreciate the new feature of taking more samples, as I feel like this is the reason why most measurements didn't seem right (eg. the standby value sometimes was higher than a low brightness value). However, it still looks like either the hue bulb (LCT015) is doing something strange or my HS110 plug is highly unreliable, because for a long period of time the average measurement of the standby value was 0.49W (which seems correct) but a few hours later it was more like 0.34W:

In both cases, measurements can be as low as 0.15W or as high as 0.54W, it looks like at least 10 samples are needed to get a more sensible value.
Has anybody else noticed this behaviour? Should I stop using the HS110 for measurement since it is simply too unreliable?

@smonesi Yes I think in powermeter.py default value is set to current time when script is first loaded into memory. Will see if I can fix this. Passing in time.time() from Kasa meter is perfectly fine.
I think this accuracy issue is mostly existent in the low power regions <0.5. most powerplugs have problems measuring this accurately. Shelly plug can't even measure below 0.4 watt.
@nepozs was testing the same plug afaik. Did you experience the same issues with HS110?

Has anybody else noticed this behaviour? Should I stop using the HS110 for measurement since it is simply too unreliable?

I have the same problem with my tasmotas. So it can even happen that if you change a light regarding brightness from 1 to 2, that the power consumption according to the measurement decreases a bit instead of increasing. Apparently most WiFi plugs have this inaccuracy. If we can identify a plug that is more accurate, we should recommend it.

Apparently most WiFi plugs have this inaccuracy.
Actually I think this is normal. All of the bulbs I have measured start at value X and then go down a little as the brightness increases then will jump up at some value then go down a little as the brightness increases further and it keeps doing that through the whole brightness range.

@stefangries Could you work out a way to know the update time of the power sensor? Is this somehow exposed by tasmota endpoint? I did some google but couldn't found any references to /?m, not sure what kind of API this is.
If this is not possible time.time() is also fine, but than the feature to check for outdated measurements will not work.

Apparently most WiFi plugs have this inaccuracy. If we can identify a plug that is more accurate, we should recommend it.

Yes I also think this is normal behaviour. This is de way dimming works on LED lights, this is not 100% linear. @nepozs also created some graphs for it.

Latest commit fixes kasa 👍
I'm currently trying to do some manual measurement with a Fibaro FGWPF-102 Z-Wave Plug, trying to understand if it is more precise (or at least more "stable") than the HS110, I'll post some graph here.
Is anybody able to write a powermeter that connects to the Z-Wave JS server? I did try but got stuck immediately since I couldn't find any meaningful example.

Latest commit fixes kasa 👍

Great

Is anybody able to write a powermeter that connects to the Z-Wave JS server? I did try but got stuck immediately since I couldn't find any meaningful example.
Did you see this library: https://github.com/home-assistant-libs/zwave-js-server-python? You'll have to make sure to map the websocket port from the container to the host so you can access the websocket from outside home assistant.

Did you see this library: https://github.com/home-assistant-libs/zwave-js-server-python? You'll have to make sure to map the websocket port from the container to the host so you can access the websocket from outside home assistant.

Yes... but I still have no clue on how to interact with my Z-Wave Plug (ie. how to write actual code to ask for the power measure).
The result of my manual test shows that the Fibaro FGWPF-102 Z-Wave Plug only provides 1 decimal value but is much more stable compared to the HS110. I can provide some graph that shows this, if anybody is interested.

Yes... but I still have no clue on how to interact with my Z-Wave Plug (ie. how to write actual code to ask for the power measure).

I also don't have an exact clue yet. We will need to connect to the websocket and than listen for node value messages somehow. I think we need to connect to the client and than call listen, https://github.com/home-assistant-libs/zwave-js-server-python/blob/master/zwave_js_server/client.py#L218. This will listen for messages and than construct event objects which should be handled somehow. Will see if I can do some coding next week.

authors: OzGav bramstroker smonesi stefangries

repo: bramstroker/homeassistant-powercalc


text:
Exception thrown on AttributeError (bad values call?)

Processing stopped with the following:
processing photo 4561 of 6826: 4596249797
Traceback (most recent call last):
  File "org_photos.py", line 72, in <module>
    print('Skipping photo with insufficient metadata.')
  File "org_photos.py", line 60, in main
    primary_photo_id=photo_id,
AttributeError: 'unicode' object has no attribute 'values'

This is resolved with cee50b1.

source: gharchive/issue

repo: brandoconnor/flickr-album-per-camera

license_type: permissive

license_source: bigquery


text:
🛑 Dev Charite gateway-iop-connection is down

In a8caed9, Dev Charite gateway-iop-connection (https://dev-ids.health-x.charite.de/health/4) was down:

HTTP code: 500
Response time: 164 ms

Resolved: Dev Charite gateway-iop-connection is back up in 493720d after 21 minutes.

repo: braunma/dataloft-endpoint-monitor

license: MIT

license_source: github-api


text:
Require the epsilon value (tolerance) to be specified explicitly, and remove the default

As @Andlon explains:

I'm not sure if it's actually wise to provide a default epsilon/tolerance - this is the very problem that Bruce Dawson discusses in the randomascii blog I know we've both spent some time reading. The problem with absolute differences is that there is really no sensible default - it depends entirely on the numbers you are comparing.

Note that I was referring explicitly to the absolute difference test for equality in that code, by the way. A default tolerance makes more sense for relative/ulp-based comparison.

Right! Thanks for the clarification.

What do you think a good default epsilon would be for ulps and relative?

Which epsilon do you mean, exactly? The absolute difference for comparing near-zero numbers that Bruce Dawson advocates in his blog, or the tolerance used for comparison with relative error or ULPs respectively?
IIRC, I think the defaults you've already been using in this crate have been fairly sane.

authors: Andlon brendanzab

repo: brendanzab/approx


text:
Scripted Installer - AUTO option for stamp location

Currently, I am creating a folder /data on the target machine and putting all stamp files and log files there.  Support the ability to override that with an option.  (This will not be supported in the prompt script.)

Already implemented.  Part of 1.0.

repo: brennanfee/linux-bootstraps


text:
Can not connect to cloudflare after upgrading to 5.0.1 version

The problem
After upgrading to latest add-on version, my ha installation can not connect to cloudflare anymore
What version of Cloudflared has the issue?
5.0.1
What was the last working version of Cloudflared?
5.0.0
What type of installation are you running?
Home Assistant Supervised
Add-on YAML Configuration
external_hostname: hassio.gpzoboli.net
additional_hosts: []
tunnel_token: {HIDDEN}

Anything in the logs that might be useful for us?
-----------------------------------------------------------
 Add-on: Cloudflared
 Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports
-----------------------------------------------------------
 Add-on version: 5.0.1
 You are running the latest version of this add-on.
 System: Armbian 23.8.1 bullseye  (armhf / qemuarm)
 Home Assistant Core: 2024.1.3
 Home Assistant Supervisor: 2023.12.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[21:08:11] INFO: Using Cloudflare Remote Management Tunnel
[21:08:11] INFO: All add-on configuration options except tunnel_token will be ignored.
[21:08:12] INFO: Connecting Cloudflare Tunnel...
2024-01-18T20:08:13Z INF Starting tunnel tunnelID=1b24ab33-97cd-4745-a742-4e5cd3c8d98b
2024-01-18T20:08:14Z INF Version 2024.1.2
2024-01-18T20:08:14Z INF GOOS: linux, GOVersion: go1.21.5, GoArch: arm
2024-01-18T20:08:14Z INF Settings: map[loglevel:info metrics:0.0.0.0:36500 no-autoupdate:true token:*****]
2024-01-18T20:08:14Z INF Generated Connector ID: 6a756953-c45a-41ad-908f-2fc4b5d8f0fe
2024-01-18T20:08:14Z INF Initial protocol quic
2024-01-18T20:08:15Z INF ICMP proxy will use 172.30.33.4 as source for IPv4
2024-01-18T20:08:15Z INF ICMP proxy will use :: as source for IPv6
2024-01-18T20:08:15Z INF Starting metrics server on [::]:36500/metrics
2024-01-18T20:08:15Z ERR Failed to serve quic connection error="INTERNAL_ERROR (local): write udp [::]:42617->198.41.200.193:7844: sendmsg: cannot allocate memory" connIndex=0 event=0 ip=198.41.200.193
2024-01-18T20:08:15Z ERR Serve tunnel error error="INTERNAL_ERROR (local): write udp [::]:42617->198.41.200.193:7844: sendmsg: cannot allocate memory" connIndex=0 event=0 ip=198.41.200.193
2024-01-18T20:08:15Z INF Retrying connection in up to 2s connIndex=0 event=0 ip=198.41.200.193
2024-01-18T20:08:15Z WRN Your version 2024.1.2 is outdated. We recommend upgrading it to 2024.1.3
2024-01-18T20:08:17Z INF Tunnel server stopped
2024-01-18T20:08:17Z ERR Initiating shutdown error="INTERNAL_ERROR (local): write udp [::]:42617->198.41.200.193:7844: sendmsg: cannot allocate memory"
2024-01-18T20:08:17Z INF Metrics server stopped
2024-01-18T20:08:17Z ERR icmp router terminated error="context canceled"
INTERNAL_ERROR (local): write udp [::]:42617->198.41.200.193:7844: sendmsg: cannot allocate memory
[21:08:17] WARNING: cloudflared crashed, halting add-on
[21:08:17] INFO: cloudflared stopped, restarting...

Steps to reproduce the issue
no problems before upgrading to 5.0.1 version
Additional information
No response

We just released a new version. Can you please update and check if this persists?

same error with 5.0.2 version too:

Add-on: Cloudflared
Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports
Add-on version: 5.0.2
You are running the latest version of this add-on.
System: Armbian 23.8.1 bullseye  (armhf / qemuarm)
Home Assistant Core: 2024.1.3
Home Assistant Supervisor: 2023.12.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
[22:33:13] INFO: Using Cloudflare Remote Management Tunnel
[22:33:13] INFO: All add-on configuration options except tunnel_token will be ignored.
[22:33:14] INFO: Connecting Cloudflare Tunnel...
2024-01-18T21:33:14Z INF Starting tunnel tunnelID=1b24ab33-97cd-4745-a742-4e5cd3c8d98b
2024-01-18T21:33:14Z INF Version 2024.1.3
2024-01-18T21:33:14Z INF GOOS: linux, GOVersion: go1.21.5, GoArch: arm
2024-01-18T21:33:14Z INF Settings: map[loglevel:info metrics:0.0.0.0:36500 no-autoupdate:true token:*****]
2024-01-18T21:33:14Z INF Generated Connector ID: d76e515c-211d-4af5-8798-93556b1a036d
2024-01-18T21:33:14Z INF Initial protocol quic
2024-01-18T21:33:15Z INF ICMP proxy will use 172.30.33.4 as source for IPv4
2024-01-18T21:33:15Z INF ICMP proxy will use :: as source for IPv6
2024-01-18T21:33:15Z INF Starting metrics server on [::]:36500/metrics
2024-01-18T21:33:15Z ERR Failed to serve quic connection error="failed to accept QUIC stream: INTERNAL_ERROR (local): write udp [::]:46752->198.41.192.167:7844: sendmsg: cannot allocate memory" connIndex=0 event=0 ip=198.41.192.167
2024-01-18T21:33:15Z ERR Serve tunnel error error="failed to accept QUIC stream: INTERNAL_ERROR (local): write udp [::]:46752->198.41.192.167:7844: sendmsg: cannot allocate memory" connIndex=0 event=0 ip=198.41.192.167
2024-01-18T21:33:15Z INF Retrying connection in up to 2s connIndex=0 event=0 ip=198.41.192.167
2024-01-18T21:33:16Z INF Tunnel server stopped
2024-01-18T21:33:16Z ERR Initiating shutdown error="failed to accept QUIC stream: INTERNAL_ERROR (local): write udp [::]:46752->198.41.192.167:7844: sendmsg: cannot allocate memory"
2024-01-18T21:33:16Z INF Metrics server stopped
2024-01-18T21:33:16Z ERR icmp router terminated error="context canceled"
failed to accept QUIC stream: INTERNAL_ERROR (local): write udp [::]:46752->198.41.192.167:7844: sendmsg: cannot allocate memory
[22:33:17] WARNING: cloudflared crashed, halting add-on
[22:33:17] INFO: cloudflared stopped, restarting...

running kernel: Linux cubietruck 4.19.38-sunxi

Got it now, I am sorry to let you know that since Version 5.0.0., the support for armhf was dropped. So there is really nothing you can do but roll back to v4.2.12.

just for the record, with version 5.0.0 it works:

Add-on: Cloudflared
Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports
Add-on version: 5.0.0
There is an update available for this add-on!
Latest add-on version: 5.0.2
Please consider upgrading as soon as possible.
System: Armbian 23.8.1 bullseye  (armhf / qemuarm)
Home Assistant Core: 2024.1.3
Home Assistant Supervisor: 2023.12.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
[23:25:03] INFO: Using Cloudflare Remote Management Tunnel
[23:25:03] INFO: All add-on configuration options except tunnel_token will be ignored.
[23:25:04] INFO: Connecting Cloudflare Tunnel...
2024-01-18T22:25:04Z INF Starting tunnel tunnelID={HIDDEN}
2024-01-18T22:25:04Z INF Version 2023.10.0
2024-01-18T22:25:04Z INF GOOS: linux, GOVersion: go1.20.6, GoArch: arm
2024-01-18T22:25:04Z INF Settings: map[loglevel:info metrics:0.0.0.0:36500 no-autoupdate:true token:*****]
2024-01-18T22:25:04Z INF Generated Connector ID: {HIDDEN}
2024-01-18T22:25:04Z INF Initial protocol quic
2024-01-18T22:25:05Z INF ICMP proxy will use 172.30.33.4 as source for IPv4
2024-01-18T22:25:05Z INF ICMP proxy will use :: as source for IPv6
2024-01-18T22:25:05Z INF Starting metrics server on [::]:36500/metrics
2024/01/18 23:25:05 failed to sufficiently increase receive buffer size (was: 160 kiB, wanted: 2048 kiB, got: 320 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2024-01-18T22:25:05Z WRN Your version 2023.10.0 is outdated. We recommend upgrading it to 2024.1.3
2024-01-18T22:25:05Z INF Registered tunnel connection connIndex=0 connection={HIDDEN} event=0 ip=198.41.200.113 location=fco01 protocol=quic
2024-01-18T22:25:06Z INF Registered tunnel connection connIndex=1 connection={HIDDEN} event=0 ip=198.41.192.107 location=mxp02 protocol=quic
2024-01-18T22:25:06Z INF Updated to new configuration config="{"ingress":[{"hostname":"{HIDDEN}","service":"http://{HIDDEN}:8123"},{"service":"http_status:404"}],"warp-routing":{"enabled":false}}" version=1
2024-01-18T22:25:07Z INF Registered tunnel connection connIndex=2 connection={HIDDEN} event=0 ip=198.41.200.53 location=fco01 protocol=quic
2024-01-18T22:25:08Z INF Registered tunnel connection connIndex=3 connection={HIDDEN} event=0 ip=198.41.192.227 location=mxp03 protocol=quic

authors: brenner-tobias gpzoboli

repo: brenner-tobias/addon-cloudflared


text:
enh: try into_function on user code

https://docs.rs/mlua/latest/mlua/struct.Chunk.html#method.into_function
and here: https://github.com/khvzak/script-bench-rs/blob/main/benches/mlua.rs.t#L35-L44
this should be faster than .load()

This shows that using .call() is 50x faster:
use mlua::prelude::*;
use std::time::Instant;

fn main() -> LuaResult<()> {
    let lua = Lua::new();

    // Lua code
    let lua_code = r#"
    function process_data(x, y)
        return x * y
    end
    "#;
    lua.load(lua_code).exec()?;

    // Get a reference to the Lua function
    let lua_func: LuaFunction = lua.globals().get("process_data")?;

    // Benchmark using .call() on a pre-loaded function
    let start = Instant::now();
    for _ in 0..1_000_000 {
        let _: i32 = lua_func.call((2, 3))?;
    }
    let duration = start.elapsed();
    println!("Time elapsed using .call(): {:?}", duration);

    // Benchmark using .load() and .exec() on each loop iteration
    let start = Instant::now();
    for _ in 0..1_000_000 {
        let _: i32 = lua.load(&format!("return {} * {}", 2, 3)).eval()?;
    }
    let duration = start.elapsed();
    println!("Time elapsed using .load() and .eval(): {:?}", duration);

    Ok(())
}

can also use this which is just as fast:

    let raw_func: LuaFunction = lua
        .load(
            r#"
        x, y = ...
        return x * y
    "#,
        )
        .into_function()?;
    let start = Instant::now();
    let mut s: i32 = 0;
    for _ in 0..1_000_000 {
        let v: i32 = raw_func.call((2, 3))?;
        s += v;
    }
    let duration = start.elapsed();
    println!("Time elapsed using raw .call(): {:?} sum: {}", duration, s);

repo: brentp/pbr


text:
Error on run

I try:

npm i -D integrity-matters
node_modules/.bin/integrity-matters --help

And I get:
/home/sbrunner/workspace/tilecloud-chain/node_modules/update-notifier/index.js:36
                        throw new Error('pkg.name and pkg.version required');
                        ^

Error: pkg.name and pkg.version required
    at new UpdateNotifier (/home/sbrunner/workspace/tilecloud-chain/node_modules/update-notifier/index.js:36:10)
    at module.exports (/home/sbrunner/workspace/tilecloud-chain/node_modules/update-notifier/index.js:182:25)
    at exports.cliBasics (/home/sbrunner/workspace/tilecloud-chain/node_modules/command-line-basics/src/index.js:100:20)
    at Object.<anonymous> (/home/sbrunner/workspace/tilecloud-chain/node_modules/integrity-matters/bin/index.js:9:27)
    at Module._compile (node:internal/modules/cjs/loader:1356:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
    at Module.load (node:internal/modules/cjs/loader:1197:32)
    at Module._load (node:internal/modules/cjs/loader:1013:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
    at node:internal/main/run_main_module:28:49

Node.js v18.19.1

What did I wrong?

This tool requires you have a package.json file with name and version properties. You can run npm init to be assisted in creating the file.

Effectively thanks :-)


text:
running server

May i know how can i run the server ?

emm.. npm start?)

authors: DDroll abyshery


text:
flutter_stetho crashed after updating to version 0.3.0

Hey, i just updated the package to version 0.3.0.
Unfortunately, it crashes on build with the following exception:
Launching lib\main.dart on WAS LX1A in debug mode...
Initializing gradle...
Resolving dependencies...
Running Gradle task 'assembleDebug'...
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)

Compiler message:
file:///C:/Dev/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_stetho-0.3.0/lib/src/http_client_response.dart:4:7: Error: 'StethoHttpClientResponse' can't implement both 'Stream<List<int>>' and 'Stream<Uint8List>'
 - 'Stream' is from 'dart:async'.
 - 'List' is from 'dart:core'.
 - 'Uint8List' is from 'dart:typed_data'.
class StethoHttpClientResponse extends StreamView<List<int>>
      ^
Compiler failed on C:\Dev\petleo-flutter-app\lib\main.dart

FAILURE: Build failed with an exception.

* Where:
Script 'C:\Dev\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 652

* What went wrong:
Execution failed for task ':app:compileflutterBuildDebugArm64'.
> Process 'command 'C:\Dev\flutter\bin\flutter.bat'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 12s
Finished with error: Gradle task assembleDebug failed with exit code 1

Channel dev, v1.8.1, (I also tried beta 1.7)
Dart 2.5.0 (build 2.5.0-dev.0.0 b5aeaa6796)
Any ideas how to solve this problem?
Best
Junus

Oh boy -- you're right. Not sure what happened, I tested on Master but for some reason it looks like the engine did not upgrade properly when I switched to the dev / master channel.
Could you please try this version in your pubspec.yaml to see if it fixes the issue?
dependencies:
  flutter_stetho:
    git:
      url: git://github.com/brianegan/flutter_stetho.git
      ref: master-fixes

Hey Brian,
thanks for the fast response. It seems to work now. :-)
Best,
Junus

Awesome. I'll publish a new version 0.4.0 with that fix. Appreciate the feedback!

Still getting this error on 0.4.0
Compiler message:
file:///Users/nicepants/sdk/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_stetho-0.4.0/lib/src/http_client_response.dart:5:7: Error: 'StethoHttpClientResponse' can't implement both 'Stream<Uint8List>' and 'Stream<List<int>>'
 - 'Stream' is from 'dart:async'.
 - 'Uint8List' is from 'dart:typed_data'.
 - 'List' is from 'dart:core'.
class StethoHttpClientResponse extends StreamView<Uint8List>
      ^
file:///Users/nicepants/sdk/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_stetho-0.4.0/lib/src/http_client_request.dart:54:42: Error: The argument type 'HttpClientResponse' can't be assigned to the parameter type 'Stream<Uint8List>'.
 - 'HttpClientResponse' is from 'dart:_http'.
 - 'Stream' is from 'dart:async'.
 - 'Uint8List' is from 'dart:typed_data'.
Try changing the type of the parameter, or casting the argument to 'Stream<Uint8List>'.
      createResponseTransformer(id).bind(response),
                                         ^

Flutter 1.7.8+hotfix.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision b712a172f9 (10 days ago) • 2019-07-09 13:14:38 -0700
Engine • revision 54ad777fd2
Tools • Dart 2.4.0
Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.7.8+hotfix.3, on Mac OS X 10.14.5 18F132, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
[✓] iOS tools - develop for iOS devices
[✓] Android Studio (version 3.4)
[✓] VS Code (version 1.36.1)
[✓] Connected device (1 available)

Thanks! I'll fix the Changelog to note that.

authors: JunusErgin Mooibroek brianegan


text:
how can change icon color?

Can the color of this icon be changed?

sorry.pls del this.

license: mit


text:
not able to compile,  POM for com.yahoo.ycsb:core:jar:0.12.0-SNAPSHOT is missing

log.txt
Hi,
I am trying to do execute the ycsb with maven, but it is complaining the  POM for com.yahoo.ycsb:core:jar:0.12.0-SNAPSHOT is missing. Just wondering is there something that Ihave to configured?
Command executed on linus shell
mvn -pl com.yahoo.ycsb:mongodb-binding -am clean package
Error message
/applications/YCSB2/YCSB/mongodb (master)*$ mvn -pl com.yahoo.ycsb:mongodb-binding -am clean package
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building MongoDB Binding 0.12.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for com.yahoo.ycsb:core:jar:0.12.0-SNAPSHOT is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.995s
[INFO] Finished at: Thu Sep 08 14:40:25 CEST 2016
[INFO] Final Memory: 13M/481M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project mongodb-binding: Could not resolve dependencies for project com.yahoo.ycsb:mongodb-binding:jar:0.12.0-SNAPSHOT: Could not find artifact com.yahoo.ycsb:core:jar:0.12.0-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

@kennethlwk is this still an issue? I just pulled latest and ran the command you specified mvn -pl com.yahoo.ycsb:mongodb-binding -am clean package and it works.

Closing due to no update.

authors: kennethlwk risdenk

repo: brianfrankcooper/YCSB


text:
[core] print data integrity status is enabled

Users would benefit if they would know exactly that their
flags take an effect.

How do I pass field length via histogram file (hist.txt)?

source: gharchive/pull-request

authors: rashmi-mssaha sitano


text:
long parse fix

small bug fix that fixes record generation bug for insert_count > INT_MAX or record_count > INT_MAX

closing in favor of #1579

authors: busbey bushwhackr


text:
sp/2013/SharePoint/CopyTheContentsOfTheSharePointMediaHere.txt should contain SP2013 refference

Tried to check in this change but could not push my own branch. The first paragraph of sp/2013/SharePoint/CopyTheContentsOfTheSharePointMediaHere.txt says:
You can place the monolithic Public Update or Cumulative Update pack installers (e.g. ubersrv2010-kb2775353-fullfile-x64-glb.exe) in either the root or subfolders here and they will automatically be applied.
It should say:
You can place the monolithic Public Update or Cumulative Update pack installers (e.g. officeserversp2013-kb2880552-fullfile-x64-en-us.exe) in either the root or subfolders here and they will automatically be applied.

Pretty minor and TBH I'm surprised anyone noticed :) I'll update in next commit.

authors: brianlala jdnark

repo: brianlala/AutoSPInstaller


text:
Add support for AWS DynamoDB storage backend

Adds support for configuring Vault to use the DynamoDB storage engine.
Documentation for all of the backend-specific variables and their defaults have been added to the README. The defaults are based on the AWS KMS unseal backend defaults, allowing for
overriding of most of the defaults via environment variables.
Note: This PR also includes some changes to the AWS KMS template as well, as I ran into issues
with that template while testing a full deployment with my changes.
I was having issues with values not appearing in the generated configuration file due to the existing if var | bool checks.
If you would prefer to deal with those changes separately, I can back them out of this PR and submit them in a separate PR.

Thanks!

authors: brianshumate chris-dudley

repo: brianshumate/ansible-vault


text:
[Question] Why assembly attributes is not adding when use module

Hello.
I wrote AssemblyAttribute MyAttribute:
[AttributeUsage(AttributeTargets.Assembly)]
public class MyAttribute : Attribute
{
}

I have some code in AssemblyInfo.cs:
[assembly: ClassLibrary3.MyAttribute]
[assembly: Bridge.Module(Bridge.ModuleType.UMD, Name = "ClassLibrary3")]

ActualResult:
have 2 files ClassLibrary3.js and ClassLibrary3.meta.js
ClassLibrary3.js:
/**
 * @version 1.0.0.0
 * @copyright Copyright ©  2019
 * @compiler Bridge.NET 17.6.0
 */
Bridge.assembly("ClassLibrary3", function ($asm, globals) {
    "use strict";

    (function (root, factory) {
        if (typeof define === 'function' && define.amd) {
            define("ClassLibrary3", factory);
        } else if (typeof module === 'object' && module.exports) {
            module.exports = factory();
        } else {
            root.ClassLibrary3 = factory();
        }
    }(this, function () {
        var ClassLibrary3 = { };
        Bridge.define("ClassLibrary3.App", {
            $metadata : function () { return {"att":1048577,"a":2,"m":[{"a":2,"isSynthetic":true,"n":".ctor","t":1,"sn":"ctor"},{"a":2,"n":"Main","is":true,"t":8,"sn":"Main","rt":System.Void}]}; },
            $scope: ClassLibrary3,
            main: function Main () { }
        });

        Bridge.define("ClassLibrary3.MyAttribute", {
            inherits: [System.Attribute],
            $metadata : function () { return {"att":1048577,"a":2,"m":[{"a":2,"isSynthetic":true,"n":".ctor","t":1,"sn":"ctor"}]}; },
            $scope: ClassLibrary3
        });
        return ClassLibrary3;
    }));

});

//# sourceMappingURL=data:application/json;base64,ewogICJ2ZXJzaW9uIjogMywKICAiZmlsZSI6ICJDbGFzc0xpYnJhcnkzLmpzIiwKICAic291cmNlUm9vdCI6ICIiLAogICJzb3VyY2VzIjogW10sCiAgIm5hbWVzIjogW10sCiAgIm1hcHBpbmdzIjogIiIsCiAgInNvdXJjZXNDb250ZW50IjogW10KfQo=

ClassLibrary3.meta.js:
Bridge.assembly("ClassLibrary3", function ($asm, globals) {
    "use strict";

    (function (root, factory) {
        if (typeof define === 'function' && define.amd) {
            define("ClassLibrary3", factory);
        } else if (typeof module === 'object' && module.exports) {
            module.exports = factory();
        } else {
            root.ClassLibrary3 = factory();
        }
    }(this, function () {
        var ClassLibrary3 = { };

        $asm.attr= [new ClassLibrary3.ClassLibrary3.MyAttribute()];
        return ClassLibrary3;
    }));

});

As you can see, my attribute usage is in ClassLibrary3.meta.js and if i try to load both files thrue define i will catch an exception, that "module already defined".
Maybe $asm.attr= should generate in ClassLibrary3.js when i use module?

Ah, it seems i found answer:
"reflection": {
  "target": "Inline"
},

This was actually not supposed to be required, so @vladsch went ahead and fixed the issue. The fix should be available next Bridge version (see attached milestone). Thanks for the report!

authors: colderlord fabriciomurta

repo: bridgedotnet/Bridge


text:
Feature/3449 three liner examples

Changes proposed in this Pull Request:

Add Threeliner examples, playground & docs.

I don't know what feedback you are looking for through this draft pull request, if any. I encourage you to communicate that in the PR description.
In the meantime, I recommend adding a simple toolbar menu to the "ThreeLiner with Custom Content" as a frequently seen use case. I also encourage you to write "ThreeLiner" in Title Case.

Hey @huayunh this was supposed to be a real PR, not a draft!  My mistake - will update based on your comments.

🚀


text:
Comparison with tRPC

hey, just stumbled on this repo and this looks great, just curious on what differs from trpc ? couldn't find anything in the doc site and this looks close feature-wise

RPC endpoints are just telefunctions.
Drastically simpler design (no routing, no middlewares, no query/mutation distinction, no batching, no error formating, no data transformers, etc.). The idea is here is that you think in terms of functions instead of thinking in terms of RPC endpoints.
Inversion of Control. This is an important shift in thinking leading to a fundamentally improved separation of concerns.
TypeScript just works. No need to do anything for full TypeScript support.
Custom arguments type saftey (shield()) instead of using zod (zod is nice but 90% of it unnecessary in the context of RPC).
Simpler React integration. (No React Query nor any Telefunc React component. It uses Async Hooks under the hood which makes using Telefunc super easy in the context of SSR.)
Support for other UI frameworks: Vue, Angular, etc.
Support for other ecosystems such as Vite
Support for edge computing such as Cloudfare Workers (which will play a crucial role in the upcoming RPC "revolution").

Also Telefunc's vision is fundamentally different than tRPC's one. Telefunc is ambitious.
That said, tRPC has support for bi-directional communication which is not a priority for Telefunc for now. With Telefunc you have to use a separate tool for bi-directional communication. Other than that I'm not aware of any tRPC advantage over Telefunc but I'm happy to be shown wrong.

Closing, hope this shed some light.

Heya! Creator of tRPC here. Excited that there are more projects popping up in this space! I will have a proper play with telefunc someday soon and get back properly - only skimmed the docs so far and got this issue linked to me.
Got some questions on your points here below.

Drastically simpler design (no routing, no middlewares, no query/mutation distinction, no batching, no error formating, no data transformers, etc.).

Could you expand on why these are good things?

[..] The idea is here is that you think in terms of functions instead of thinking in terms of RPC endpoints.

If you don't have data transformers, you can't really properly think about things as functions as you won't be able to return things like Date/Map/Sets and just use them.

Inversion of Control. This is an important shift in thinking leading to a fundamentally improved separation of concerns.

I don't think I follow this - what is the difference in inversion of control here? In tRPC we also have a context object which is passed into all resolvers.

TypeScript just works. No need to do anything for full TypeScript support.

What do you mean you need to do with tRPC that you don't need to in telefunc?

Custom arguments type saftey (shield()) instead of using zod (zod is nice but 90% of it unnecessary in the context of RPC).

In tRPC you can do this as well.

Simpler React integration. (No React Query nor any Telefunc React component. It uses Async Hooks under the hood which makes using Telefunc super easy in the context of SSR.)

Do you provide any hooks to easily fetch the data? In the next example, I see the following which seems quite verbose? Easy-to-use hooks are essential for a good DX.
https://github.com/vikejs/telefunc/blob/25e01c7942d50efa002cc1a498b501c64217e7c0/examples/next/pages/index.tsx#L7-L20

Support for other UI frameworks: Vue, Angular, etc.

@trpc/server + @trpc/client are completely framework agnostic as well. In what way is telefunc different in this regard?

Support for other ecosystems such as Vite

What do you mean here? tRPC should work fine with Vite afaik as it doesn't require any compilation.

Support for edge computing such as Cloudfare Workers (which will play a crucial role in the upcoming RPC "revolution").

Possible with tRPC as well, I saw someone doing a repo of this the other day.

Also Telefunc's vision is fundamentally different than tRPC's one. Telefunc is ambitious.

My goals with tRPC are quite ambitious as well and it already does a looot whilst being quite composable, so why you're insinuating that tRPC is unambitious  😅

That said, tRPC has support for bi-directional communication which is not a priority for Telefunc for now. With Telefunc you have to use a separate tool for bi-directional communication. Other than that I'm not aware of any tRPC advantage over Telefunc but I'm happy to be shown wrong.

You already mentioned a few advantages with tRPC: "no routing, no middlewares, no query/mutation distinction, no batching, no error formating, no data transformers". I could add to that list, but I'm not here for that.
I'm excited to try Telefunc out!

Updated the list, I hope it's more accurate now.

Possible with tRPC as well, I saw someone doing a repo of this the other day.

Mind sharing? The main problem here is that Next.js doesn't support Cloudflare Workers.

Do you provide any hooks to easily fetch the data

Yes it's work in progress. It's actually the only piece missing for Telefunc's release.

You already mentioned a few advantages with tRPC: "no routing, no middlewares, no query/mutation distinction, no batching, no error formating, no data transformers". I could add to that list, but I'm not here for that.

No please do. I'm not adding these to tRPC advantages because I think these are design flaws and not features. Happy to be shown wrong though.

Updated the list, I hope it's more accurate now.

You didn't address most of my points & your list is still lacking a bit of nuance. Would you mind going through my points again and respond with your thoughts on each?
On my phone now, will respond with why all of those things you consider flaws are actually benefits.

@brillout would be interesting with an update here adressing @KATT’s points.

What points specifically? IIUC https://telefunc.com/tour#inversion-of-control and my replies here covers everything.

https://telefunc.com/tour#inversion-of-control

👆404 on that URL.
As my 5¢ input. I'm personally using Zodios. Would be nice to see a comparison table with Zodios and TRPC. I'm not convinced why I should choose Telefunc over Zodios becase the latter operates with Zod schemas that are reusable and give me TS types for free! With Telefunc it's another DSL only to validate APIs.

👆404 on that URL.

Yea, I removed that. I may re-add this section somewhere in the docs (some users like these kind of theoretical explanation).

why I should choose Telefunc

Because it's fundamentally simpler.

With Telefunc it's another DSL

It isn't because the goal of shield() is to be internal (it's automatically generated). I may remove the docs for shield() to make it clear that it's something you'll ideally/almost never use.

Thank you, I'll have to give it another look then 👍

This is quite an old post, but thought I'd leave my thoughts here for anyone else who's comparing trpc with telefunc. I use trpc for most of my projects, and just saw telefunc and thought it was really interesting. Reminded me of next.js server actions, being able to write server code directly in the frontend code. This was what made telefunc most interesting to me.
However, my biggest use case for trpc so far has been the integration with react query. Having all my server functions automatically wrapped with react-query hooks for queries & mutations is extremely useful (I usually work on more dynamic fully client-side rendered projects, so react-query is especially useful for me). This also means I can invalidate queries after mutations happen to update the UI, and I don't even need to worry about managing query keys since I can directly call the invalidation function using their react query utils.
Overall, I'd say it boils down to your use case. I initially was excited about the possibility of using telefunc until I realized that it doesn't work well with client-side projects that heavily utilize react-query to manage data loading. trpc is perfect for this use case, and with specific frameworks like Next.js (which already have server actions) you may not even need something like this. But overall, these libraries cover different use cases and you need to see what will work best for your project.

@kirankunigiri Neat comparison, thank you! FYI Vike users can use Telefunc with vike-react-query, although it would be better to have a TanStack Query integration that works across frameworks.

authors: KATT astahmer brillout ivan-kleshnin kirankunigiri redbar0n

repo: brillout/telefunc


text:
PrintSVEvidence Error: inputs are not sorted

Hi, I'm trying to replicate some steps in the workflow of gatk-sv. In the step MatrixQC, I have encountered the following bug, which I have no idea how to fix.
`Using GATK jar /media/atlantis/data_4tb/Exec/sv_workflow/gatk_sv_snakemake/.snakemake/conda/019f9e2664948e9d7669ca9498b81e93/share/gatk4-4.2.6.1-1/gatk-package-4.2.6.1-local.jar
Running:
java -Dsamjdk.use_async_io_read_samtools=false -Dsamjdk.use_async_io_write_samtools=true -Dsamjdk.use_async_io_write_tribble=false -Dsamjdk.compression_level=2 -Xmx10G -jar /media/atlantis/data_4tb/Exec/sv_workflow/gatk_sv_snakemake/.snakemake/conda/019f9e2664948e9d7669ca9498b81e93/share/gatk4-4.2.6.1-1/gatk-package-4.2.6.1-local.jar PrintSVEvidence --sequence-dictionary resource/Homo_sapiens_assembly38.dict --evidence-file /media/atlantis/data_4tb/Exec/results/GatherBatchEvidence/MergeEvidence/VN_01.pe.txt.gz -L /media/atlantis/data_4tb/Exec/results/EvidenceQC/MatrixQC/regions.pe.bed -O /media/atlantis/data_4tb/Exec/results/EvidenceQC/MatrixQC/local.pe.txt.gz
17:42:28.106 INFO  NativeLibraryLoader - Loading libgkl_compression.so from jar:file:/media/atlantis/data_4tb/Exec/sv_workflow/gatk_sv_snakemake/.snakemake/conda/019f9e2664948e9d7669ca9498b81e93/share/gatk4-4.2.6.1-1/gatk-package-4.2.6.1-local.jar!/com/intel/gkl/native/libgkl_compression.so
17:42:31.040 INFO  PrintSVEvidence - ------------------------------------------------------------
17:42:31.041 INFO  PrintSVEvidence - The Genome Analysis Toolkit (GATK) v4.2.6.1
17:42:31.041 INFO  PrintSVEvidence - For support and documentation go to https://software.broadinstitute.org/gatk/
17:42:31.041 INFO  PrintSVEvidence - Executing as atlantis@atlantis on Linux v5.15.0-43-generic amd64
17:42:31.041 INFO  PrintSVEvidence - Java runtime: OpenJDK 64-Bit Server VM v11.0.13+7-b1751.21
17:42:31.041 INFO  PrintSVEvidence - Start Date/Time: August 3, 2022 at 5:42:28 PM ICT
17:42:31.041 INFO  PrintSVEvidence - ------------------------------------------------------------
17:42:31.041 INFO  PrintSVEvidence - ------------------------------------------------------------
17:42:31.042 INFO  PrintSVEvidence - HTSJDK Version: 2.24.1
17:42:31.042 INFO  PrintSVEvidence - Picard Version: 2.27.1
17:42:31.042 INFO  PrintSVEvidence - Built for Spark Version: 2.4.5
17:42:31.042 INFO  PrintSVEvidence - HTSJDK Defaults.COMPRESSION_LEVEL : 2
17:42:31.043 INFO  PrintSVEvidence - HTSJDK Defaults.USE_ASYNC_IO_READ_FOR_SAMTOOLS : false
17:42:31.043 INFO  PrintSVEvidence - HTSJDK Defaults.USE_ASYNC_IO_WRITE_FOR_SAMTOOLS : true
17:42:31.043 INFO  PrintSVEvidence - HTSJDK Defaults.USE_ASYNC_IO_WRITE_FOR_TRIBBLE : false
17:42:31.043 INFO  PrintSVEvidence - Deflater: IntelDeflater
17:42:31.043 INFO  PrintSVEvidence - Inflater: IntelInflater
17:42:31.043 INFO  PrintSVEvidence - GCS max retries/reopens: 20
17:42:31.043 INFO  PrintSVEvidence - Requester pays: disabled
17:42:31.043 WARN  PrintSVEvidence -
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Warning: PrintSVEvidence is an EXPERIMENTAL tool and should not be used for production
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
17:42:31.043 INFO  PrintSVEvidence - Initializing engine
17:42:31.226 INFO  FeatureManager - Using codec DiscordantPairEvidenceCodec to read file file:///media/atlantis/data_4tb/Exec/results/GatherBatchEvidence/MergeEvidence/VN_01.pe.txt.gz
17:42:31.295 INFO  FeatureManager - Using codec BEDCodec to read file file:///media/atlantis/data_4tb/Exec/results/EvidenceQC/MatrixQC/regions.pe.bed
17:42:31.299 INFO  IntervalArgumentCollection - Processing 24000000 bp from intervals
17:42:31.300 WARN  IndexUtils - Feature file "file:///media/atlantis/data_4tb/Exec/results/GatherBatchEvidence/MergeEvidence/VN_01.pe.txt.gz" appears to contain no sequence dictionary. Attempting to retrieve a sequence dictionary from the associated index file
17:42:31.361 WARN  IntelInflater - Zero Bytes Written : 0
17:42:31.362 WARN  IndexUtils - Index file /media/atlantis/data_4tb/Exec/results/GatherBatchEvidence/MergeEvidence/VN_01.pe.txt.gz.tbi is out of date (index older than input file). Use IndexFeatureFile to make a new index.
17:42:31.367 INFO  PrintSVEvidence - Done initializing engine
17:42:31.370 INFO  ProgressMeter - Starting traversal
17:42:31.371 INFO  ProgressMeter -        Current Locus  Elapsed Minutes    Features Processed  Features/Minute
17:42:31.420 INFO  PrintSVEvidence - Shutting down engine
[August 3, 2022 at 5:42:31 PM ICT] org.broadinstitute.hellbender.tools.sv.PrintSVEvidence done. Elapsed time: 0.06 minutes.
Runtime.totalMemory()=627048448

A USER ERROR has occurred: inputs are not sorted at chr1:248437396

Set the system property GATK_STACKTRACE_ON_USER_EXCEPTION (--java-options '-DGATK_STACKTRACE_ON_USER_EXCEPTION=true') to print the stack trace.`
I have sorted and indexed the input pe file with these commands:
sort -k1,1V -k2,2n  $pe_file | bgzip -c > $pe_final_file
tabix -f -s1 -b2 -e2 $pe_final_file

I have also checked the pe file at the position, where the error occurs.
chr1    248437267       +       chr6    124582055       +       VN_01_00_0005
chr1    248437395       +       chr1    248654316       +       VN_01_00_0007
chr1    248437395       +       chrY    56836874        -       VN_01_00_0007
chr1    248437415       +       chr2    149572447       -       VN_01_00_0001

Hi @giacuong171,
This bug was fixed here on May 6 after the 4.2.6.1 release. Can you try compiling gatk from source or using a recent nightly build?

Hi @mwalker174 ,
Thank you for the quick reply. I will try to use the nightly build.

repo: broadinstitute/gatk-sv


text:
Add option for logfile

With the LorixOne Gateway, I have problem to start the gateway as a deamon and to pipe the stout and sterr to a file. START-STOP-DEAMON has a problem with that. I think I have no other options...
The Gateway run with a yocto linux 2.1.2.

What problem does start-stop-daemon have? Did you for example see this https://stackoverflow.com/questions/8251933/how-can-i-log-the-stdout-of-a-process-started-by-start-stop-daemon?
Also note that it might not be a good idea to persist logs on the gateway. I'm not sure about the LorixOne, but usually these devices do not have a lot of storage and the kind memory might not be suitable for lots of writes.

authors: brocaar minggi

repo: brocaar/lora-gateway-bridge


text:
DoorBird Chime

Has anyone else had issues with the DoorBird Chime not working in this setup? Does it need to be setup as a separate HTTP call?

Works fine for me.  There’s really no configuration to add DoorBird Chime into this setup, it hangs off the DoorBird app as an accessory as it did before.  No change.

On 26 Jul 2020, at 21:09, jbk1988 notifications@github.com wrote:
Has anyone else had issues with the DoorBird Chime not working in this setup? Does it need to be setup as a separate HTTP call?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/brownad/homebridge-doorbird/issues/75, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUK4CZ7YYOU76M6UVMR5S3R5SEQZANCNFSM4PIENFSA.

Likewise - I have several Chime devices. The Chimes are configured to speak with the Doorbird. There's no interaction model for them with this plugin. I'd validate that the chimes are working correctly with Doorbird, independent of this plugin.

authors: brownad hjdhjd jbk1988

repo: brownad/homebridge-doorbird


text:
Cleanup

Removed phantomjs and safe-buffer (part of https://github.com/brave/brave-browser/issues/5490)
Updated all dev dependencies
Tidy up with newest standard --fix
Naming convention for importing files (like ESM)
Only test latest LTS (v12)

Thanks @jimmywarting

authors: dcousens jimmywarting

repo: browserify/randombytes


text:
ERROR: unknown command line flag 'crash_on_fatal_log'

我拉下代码，brpc没有安装到公有目录，但是在braft的cmake里指定了brpc的目录，编译通过了，./run_client.sh 和 ./run_server.sh 都报错了 ERROR: unknown command line flag 'crash_on_fatal_log'

这个flag跟宏BRPC_WITH_GLOG互斥

authors: bolanbujing ipconfigme

repo: brpc/braft


text:
Added two more rand examples

I do not know if rand examples are still open for contribution.
But I have added two more basic examples:

"Generate random numbers within a range"
"Generate random numbers with normal distribution"

These seam to be relatively frequently asked on SO.

Everything is open for contribution! (Well, governed by what Brian decides in https://github.com/brson/rust-cookbook/issues/64#issuecomment-300650595.)
Thanks, these look great.

authors: budziq dtolnay

repo: brson/rust-cookbook


text:
Wemod Patcher does not work after wemod update 9.0.0.1

I used the patcher to put the reject method, after that the wemod executable stopped responding, meaning I can't open it anymore.

[!Warning]
Wrong Repository
Please use the forum cs.rin.ru for more information related to this subject

Here is only related with "GSE Generator", thanks!

authors: ArgonHakon brunolee-GIT

repo: brunolee-GIT/GSE-Generator


text:
Browserify support

Add support for http://browserify.org/.

Added UMD support (http://davidbcalhoun.com/2014/what-is-amd-commonjs-and-umd/) to support both AMD & CommonJS.

repo: brunschgi/terrificjs


text:
Improvements

renamed domain/erase to domain/overwrite. I'll add a canonical erase later, which will use overwrite itself.
changed all match patterns that are used as mar_err
added copy_from_slice instead of a manual copy loop

All looks great my friend, nice work as usual!

Feel free to add yourself to the authors in Cargo.toml if you'd like! You've done massive amounts of work friend :)

Thank you) but I don't think 1000 LOC is "massive amount". First of all, I have to extract most of the logic from the cli :)


text:
Two commits (can be cherrypicked): Custom Env vars for Perl in settings, and convert tilda to home in paths

Feature 1:
Add support for custom Perl environment variables
Introduced two new environment variables: perlEnv and perlEnvAdd.

perlEnv: This is a hash to fully override the system's environment for PerlNavigator.
perlEnvAdd: This is a hash to add or modify specific environment variables for PerlNavigator.

Feature 2:
Add support for expanding leading tildas in paths

if needed: variable to On/Off that.

NOTE: I tested this under MacOS (no Windows and I suspect it might be a different way of substituting Windows "home" or other relativeness).

This looks great, thanks for putting this together! I'll do some testing this weekend and merge it in. Some comments:
I don't think we'd need to disable the tilde expansion. Currently, tilde's simply don't work so having it on all the time is probably the best. Looks like they considered adding it in node, but decided against it: https://github.com/nodejs/node/issues/684
And people seem to recommend untildify, which has 14 million weekly downloads and does the same thing ( os.homedir ) https://github.com/sindresorhus/untildify/blob/a901e25ef782d93df1eba04ed48f56c79d157c74/index.js#L10
Although I greatly prefer your approach over bringing in a dependency for one line of code.
On Windows, the equivalent is probably %USERPROFILE% although far less used. We can probably just ignore it for now. I can test on Windows and Linux just to make sure nothing breaks, but I think it would be fine.
PerlEnv and PerlEnvAdd both make sense as well. I suspect Add is the more common case, where someone just needs to add or override a variable. Clearing out variables might have some unexpected effects, especially if someone's perl setup uses PERL5LIB or a PERLCRITIC profile. We can use the README to point people toward preferring PerlEnvAdd if needed.
Thanks!

PerlEnv and PerlEnvAdd both make sense as well. I suspect Add is the more common case, where someone just needs to add or override a variable. Clearing out variables might have some unexpected effects, especially if someone's perl setup uses PERL5LIB or a PERLCRITIC profile. We can use the README to point people toward preferring PerlEnvAdd if needed.

Good point. I reworked the idea of PerlEnv: two variables:

perlEnv: Hash. Pass environment variables to the perl executable. Skipped if undefined.
perlEnvAdd: Boolean. Add environment variables to the current environment, or totally replace (perlEnv related). The default is true.

More clean, and added by default, and perlEnvAdd can be used rarely.

Also: removed

Add expandLeadTildasInPaths Setting for Optional Tilda Expansion

commit at all, no need to on/off tildas' expansion.

... and removed Windows "placeholder" ~\\ which is actually not.

This is great, my apologies for the slow merge. Thanks again for putting this together!

authors: bscan nugged

repo: bscan/PerlNavigator


text:
labwc: fix wlroots slot (0.7.x uses wlroots 0.17)

The 0.7.x line of labwc uses wlroots 0.17, as can be seen here. Only labwc master is on 0.18 already.
This MR fixes this by using the 0/17 slot for the wlroots dependency.

And thanks for the PR.

repo: bsd-ac/wayland-desktop

license: ISC


text:
Add sample backup config

This adds sample backup configurations for 2 of 3 and 3 of 5. Instead of giving step by step instructions, this just shows examples and talks about what the reader needs to consider.

@mflaxman I would like some input before I mark it as ready for merging

+1 i was surprised that this info wasnt included in the guide already
why do you recommend having copies of core and specter on a usb drive stored with the wallets?

Less chances of having incompatible versions. Also, if your heirs have to
find copies of the software they may get malware instead.
It's still not simple, but anything to lessen the complexity will help
On Tue, 22 Dec 2020, 13:42 mmikeww, notifications@github.com wrote:

+1 i was surprised that this info wasnt included in the guide already
why do you recommend having copies of core and specter on a usb drive
stored with the wallets?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/btcguide/btcguide.github.io/pull/48#issuecomment-749351633,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAGF5EAQPGMF2KCNXOGGB3SWAWTNANCNFSM4ULUQVMA
.

@mflaxman this is ready for review

@mflaxman this is ready for review

The cobo vault requires that you set up a password, and the Coldcard requires that you set up a PIN. So both of those should be backed up somewhere as well

The cobo vault requires that you set up a password, and the Coldcard requires that you set up a PIN. So both of those should be backed up somewhere as well

Thanks. I realized this should be talked about as well.
Generally speaking, the seed, PIN/password of the device should be with the corresponding device. However, where do you suggest the seed, PIN/password for the device/s that stay with you (in your house, or on your person if you're traveling) are stored?

Thanks. I realized this should be talked about as well.
Generally speaking, the seed, PIN/password of the device should be with the corresponding device. However, where do you suggest the seed, PIN/password for the device/s that stay with you (in your house, or on your person if you're traveling) are stored?

I don't have a good recommendation. This other guide suggests to spread that information out with other seeds, but also recommends keeping a digital copy somewhere, such as in an encrypted file in the cloud, or I guess in a password manager. He calls it a "digital note":
https://github.com/DriftwoodPalace/guides/blob/master/hodl-guide/hodl-guide_50_storage.md

I don't have a good recommendation. This other guide suggests to spread that information out with other seeds, but also recommends keeping a digital copy somewhere, such as in an encrypted file in the cloud, or I guess in a password manager. He calls it a "digital note":
https://github.com/DriftwoodPalace/guides/blob/master/hodl-guide/hodl-guide_50_storage.md

authors: mmikeww ramontayag


text:
can't get it to run on Raspberry Pi 4 - all time rejected :(

Heya,
I have a raspberry pi 4 with 4 gb ram.
Now I just try to get iobroker running in my docker environment and it is always rejecting.
I run docker in swarm mode to be able to use stacks in portainer.
I also tryed the image buanet/iobroker:arm7hf without success.
Can anyone help?
version: '3.7'

volumes:
  iobroker_data:

networks:
 hostnet:
   external: true
   name: host

services:
  iobroker:
    restart: always
    image: buanet/iobroker:latest
    hostname: iobroker
    networks:
     hostnet: {}
    ports:
      - 8081:8081
    volumes:
      - iobroker_data:/opt/iobroker
    environment:
      TZ: Europe/Berlin
      LANG: de_DE.UTF-8
      LANGUAGE: de_DE:de
      LC_ALL: de_DE.UTF-8
      PACKAGES: nano
      SETGID: 1000
      SETUID: 1000

As compose Version 3.7 is not supported by portainer yet, you have to use version 2...
https://github.com/portainer/portainer/issues/3750
Regards,
André

3.7 is running fine with docker swarm on portainer!
it is jsut not working with docker compose!

Sorry, do not use swarm mode.

3.7 is running fine with docker swarm on portainer!

If that's true I can not help you with that.
Regards,
Ande

BTW

I run docker in swarm mode to be able to use stacks in portainer.

Thats not true. I use stacks with docker in normal mode...
Regards,
André

BTW

I run docker in swarm mode to be able to use stacks in portainer.

Thats not true. I use stacks with docker in normal mode...
Regards,
André

I mean to insert my stack files directly in portainer instead of through the shell, maybe there is an other solution, but don't know that.

This is one of my testing environments. A single host (virtual DSM with Docker) and the running portainer container:

It's possible to manage stacks using the webui. But stackfile/ compose file have to be v2...

that looks great, have to take a look at it! thank you <3
for now I just tryed to start it the legacy way :D
docker run -d --network host --name iobroker -v iobroker_data:/opt/iobroker buanet/iobroker -e "TZ=Europe/Berlin"
Unfurtunately the port 8081 isn't accessible if I use the host net right?
Have to use the hostnet because my harmony hub won't be find through node-red otherwise :/

When you use host as network the Docker daemon will open up the ports on the host automatically. So no need to publish...
Port should be accessible when container is started. If not, take a look at the container log...

When you use host as network the Docker daemon will open up the ports on the host automatically. So no need to publish...
Port should be accessible when container is started. If not, take a look at the container log...

mhhh tryed again and can't find anything in the logs that tells me that something is wrong! I can't access https://hostIP:8081 after changing to host network.

You sure that https://hostIP:8081 is correct? The standard is http://...
You sure the admin is bind to 0.0.0.0 or the ip of your host? You may check/ change this over commandline (https://www.iobroker.net/docu/index-98.htm?page_id=3971&lang=de#iobroker_set)
So far, the log looks ok, but it is not the whole log. If you want me to check the log, please post theo whole one

Regards,
André

1. You sure that `https://hostIP:8081` is correct? The standard is http://...

2. You sure the admin is bind to 0.0.0.0 or the ip of your host? You may check/ change this over commandline (https://www.iobroker.net/docu/index-98.htm?page_id=3971&lang=de#iobroker_set)

3. So far, the log looks ok, but it is not the whole log. If you want me to check the log, please post theo whole one

Regards,
André

hey andré, thank you for your response!

https is correct because I changed this setting inside the iobroker. I did this in a non host environment.

where can I setup this IP? Host got 10.0.9.7 f.e. and don't know where to put it in?

here is the whole log after starting with host network

root@octopi:~# cat /var/lib/docker/containers/22870358a7da09dda3d91e821b6db19ec10346c87a7bee0dcdb2490f8b08a9ca/22870358a7da09dda3d91e821b6db19ec10346c87a7bee0dcdb2490f8b08a9ca-json.log
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:14.159460433Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:14.161770771Z"}
{"log":"---------------     2020-10-19 13:42:14      ---------------\n","stream":"stdout","time":"2020-10-19T11:42:14.165961953Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:14.168175793Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:14.168235681Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:14.170654202Z"}
{"log":"-----       Welcome to your ioBroker-container!        -----\n","stream":"stdout","time":"2020-10-19T11:42:14.170756201Z"}
{"log":"-----          Startupscript is now running.           -----\n","stream":"stdout","time":"2020-10-19T11:42:14.170833774Z"}
{"log":"-----                Please be patient!                -----\n","stream":"stdout","time":"2020-10-19T11:42:14.170913088Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:14.173281906Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:14.17337759Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:14.175640855Z"}
{"log":"-----              Debugging information               -----\n","stream":"stdout","time":"2020-10-19T11:42:14.175746409Z"}
{"log":"-----                                                  -----\n","stream":"stdout","time":"2020-10-19T11:42:14.175819186Z"}
{"log":"-----                      System                      -----\n","stream":"stdout","time":"2020-10-19T11:42:14.176006961Z"}
{"log":"-----               arch:      armv7l                  -----\n","stream":"stdout","time":"2020-10-19T11:42:14.181732862Z"}
{"log":"-----                                                  -----\n","stream":"stdout","time":"2020-10-19T11:42:14.18186436Z"}
{"log":"-----                     Versions                     -----\n","stream":"stdout","time":"2020-10-19T11:42:14.181895453Z"}
{"log":"-----               image:     v5.0.0                  -----\n","stream":"stdout","time":"2020-10-19T11:42:14.184018775Z"}
{"log":"-----               node:      v12.19.0                -----\n","stream":"stdout","time":"2020-10-19T11:42:14.201407235Z"}
{"log":"-----               npm:       6.14.8                  -----\n","stream":"stdout","time":"2020-10-19T11:42:15.09241105Z"}
{"log":"-----                                                  -----\n","stream":"stdout","time":"2020-10-19T11:42:15.092491975Z"}
{"log":"-----                       ENV                        -----\n","stream":"stdout","time":"2020-10-19T11:42:15.09252366Z"}
{"log":"-----               SETGID:    1000                    -----\n","stream":"stdout","time":"2020-10-19T11:42:15.095091031Z"}
{"log":"-----               SETUID:    1000                    -----\n","stream":"stdout","time":"2020-10-19T11:42:15.096990153Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:15.099498673Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:15.099556061Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:15.101546311Z"}
{"log":"-----         Step 1 of 5: Preparing container         -----\n","stream":"stdout","time":"2020-10-19T11:42:15.10168018Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:15.1041902Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:15.104258458Z"}
{"log":"Nothing to do here.\n","stream":"stdout","time":"2020-10-19T11:42:15.11949893Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:15.119566374Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:15.121676437Z"}
{"log":"-----   Step 2 of 5: Detecting ioBroker installation   -----\n","stream":"stdout","time":"2020-10-19T11:42:15.121803694Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:15.123915757Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:15.12396759Z"}
{"log":"Existing installation of ioBroker detected in /opt/iobroker.\n","stream":"stdout","time":"2020-10-19T11:42:15.716519152Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:15.716869055Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:15.718996062Z"}
{"log":"-----   Step 3 of 5: Checking ioBroker installation    -----\n","stream":"stdout","time":"2020-10-19T11:42:15.719196596Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:15.7213069Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:15.721478027Z"}
{"log":"(Re)Setting folder permissions (This might take a while! Please be patient!)...\n","stream":"stdout","time":"2020-10-19T11:42:15.721589785Z"}
{"log":"Done.\n","stream":"stdout","time":"2020-10-19T11:42:16.908776415Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:16.908845192Z"}
{"log":"Fixing \"sudo-bug\" by replacing sudo in iobroker with gosu...\n","stream":"stdout","time":"2020-10-19T11:42:16.908899117Z"}
{"log":"Done.\n","stream":"stdout","time":"2020-10-19T11:42:16.923414618Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:16.923488506Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:21.565668228Z"}
{"log":"-----      Step 4 of 5: Applying special settings      -----\n","stream":"stdout","time":"2020-10-19T11:42:21.565828467Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:21.570814027Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:21.570996487Z"}
{"log":"Some adapters have special requirements/ settings which can be activated by the use of environment variables.\n","stream":"stdout","time":"2020-10-19T11:42:21.571291057Z"}
{"log":"For more information take a look at readme.md on Github!\n","stream":"stdout","time":"2020-10-19T11:42:21.571365778Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:21.571427074Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:21.619894543Z"}
{"log":"-----          Step 5 of 5: ioBroker startup           -----\n","stream":"stdout","time":"2020-10-19T11:42:21.620003986Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T11:42:21.624087373Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:21.624187353Z"}
{"log":"Starting ioBroker...\n","stream":"stdout","time":"2020-10-19T11:42:21.624233797Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T11:42:21.624280352Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.admin.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.631715015Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.info.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.635398111Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.web.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.640934737Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.history.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.645532303Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.cloud.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.648070434Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.mobile.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.649913667Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.alexa2.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.651838899Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.deconz.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.654806654Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.mqtt.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.656457279Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.nuki-extended.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.657770742Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.node-red.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.658830227Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.daswetter.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.660226801Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.dwd.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.66124036Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.pollenflug.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.662576212Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.feiertage.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.663760677Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.telegram.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.66605746Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.text2command.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.667564198Z"}
{"log":"host.768e6c99e034 check instance \"system.adapter.harmony.0\" for host \"768e6c99e034\"\n","stream":"stdout","time":"2020-10-19T11:42:23.669080695Z"}

Hi,
here you can find how to set ip binding and port for admin adapter: https://forum.iobroker.net/topic/11774/binding-der-ip-adresse-des-admin-adapters
BTW the following tells me, that you not started a "completly fresh installation of ioBroker":
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T16:26:22.958073491Z"}
{"log":"-----   Step 2 of 5: Detecting ioBroker installation   -----\n","stream":"stdout","time":"2020-10-19T16:26:22.958149472Z"}
{"log":"------------------------------------------------------------\n","stream":"stdout","time":"2020-10-19T16:26:22.960455528Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T16:26:22.960601676Z"}
{"log":"Existing installation of ioBroker detected in /opt/iobroker.\n","stream":"stdout","time":"2020-10-19T16:26:23.135341972Z"}
{"log":" \n","stream":"stdout","time":"2020-10-19T16:26:23.135517639Z"}

Other than that I have no idea what's going wrong. Log looks good so far. ioBroker is starting.
Did you check if port 8081 is listening?
https://www.thomas-krenn.com/de/wiki/Linux_Netzwerk_Analyse_mit_netstat
Regards,
André

Good evening :)
this was a complete fresh installation of your image on a raspberry pi that never got ioBroker installed before o_O
If I try to telnet on port 8081 it is not working. So no the server doesn't seem to listen on this port.
I will read through the post you gave me tomorrow, realy frustrating right now :/
Just want to start and can't waaaaaah 😂

-----                Please be patient!                -----, ------------------------------------------------------------,  , ------------------------------------------------------------, -----              Debugging information               -----, -----                                                  -----, -----                      System                      -----, -----               arch:      armv7l                  -----, -----                                                  -----, -----                     Versions                     -----, -----               image:     v5.1.0                  -----, -----               node:      v12.19.0                -----, -----               npm:       6.14.8                  -----, -----                                                  -----, -----                       ENV                        -----, -----               IOB_OBJECTSDB_PORT: 9011                    -----, -----               SETGID:    1000                    -----, -----               SETUID:    1000                    -----, -----               IOB_STATESDB_PORT: 9010                    -----, ------------------------------------------------------------,  , ------------------------------------------------------------, -----         Step 1 of 5: Preparing container         -----, ------------------------------------------------------------,  , Registering maintenance script as command., Done.,  , ------------------------------------------------------------, -----   Step 2 of 5: Detecting ioBroker installation   -----, ------------------------------------------------------------,  , Existing installation of ioBroker detected in /opt/iobroker.,  , ------------------------------------------------------------, -----   Step 3 of 5: Checking ioBroker installation    -----, ------------------------------------------------------------,  , (Re)Setting folder permissions (This might take a while! Please be patient!)..., Done.,  , Fixing "sudo-bug" by replacing sudo in iobroker with gosu..., Done.,  , /opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22,     throw new Error(Unknown objects type: ${config.objects.type});,     ^, , Error: Unknown objects type: ,     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22:11),     at Module._compile (internal/modules/cjs/loader.js:1015:30),     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10),     at Module.load (internal/modules/cjs/loader.js:879:32),     at Function.Module._load (internal/modules/cjs/loader.js:724:14),     at Module.require (internal/modules/cjs/loader.js:903:19),     at require (internal/modules/cjs/helpers.js:74:18),     at dbConnect (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2439:15),     at CLIObjects.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/cli/cliObjects.js:159:9),     at CLIObjects.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/cli/cliObjects.js:32:29), /opt/scripts/iobroker_startup.sh: line 197: [: !=: unary operator expected, ------------------------------------------------------------, -----      Step 4 of 5: Applying special settings      -----, ------------------------------------------------------------,  , Some adapters have special requirements/ settings which can be activated by the use of environment variables., For more information take a look at readme.md on Github!,  , /opt/scripts/iobroker_startup.sh: line 369: [: : unary operator expected, ENV IOB_OBJECTSDB_TYPE is set and value meets detected ioBroker installation. Nothing to do here., /opt/scripts/iobroker_startup.sh: line 379: [: : unary operator expected, ENV IOB_OBJECTSDB_HOST is set and value meets detected ioBroker installation. Nothing to do here., ENV IOB_OBJECTSDB_PORT is set and value meets detected ioBroker installation. Nothing to do here.,  , ENV IOB_STATESDB_TYPE is set and value meets detected ioBroker installation. Nothing to do here., /opt/scripts/iobroker_startup.sh: line 406: [: : unary operator expected, /opt/scripts/iobroker_startup.sh: line 416: [: : unary operator expected, ENV IOB_STATESDB_HOST is set and value meets detected ioBroker installation. Nothing to do here., ENV IOB_STATESDB_PORT is set and value meets detected ioBroker installation. Nothing to do here.,  , ------------------------------------------------------------, -----          Step 5 of 5: ioBroker startup           -----, ------------------------------------------------------------,  , Starting ioBroker...,  , /opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22,     throw new Error(Unknown objects type: ${config.objects.type});,     ^, , Error: Unknown objects type: ,     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22:11),     at Module._compile (internal/modules/cjs/loader.js:1015:30),     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10),     at Module.load (internal/modules/cjs/loader.js:879:32),     at Function.Module._load (internal/modules/cjs/loader.js:724:14),     at Module.require (internal/modules/cjs/loader.js:903:19),     at require (internal/modules/cjs/helpers.js:74:18),     at Object.init (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4140:19),     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:8:19),     at Module._compile (internal/modules/cjs/loader.js:1015:30),

Hey @buanet,
just want to tell you that nothing is working with the host net with your docker image right now.
Tested all kinds of combinations... tested the bind ip adresses inside the shell of the contaier but still no access from outside.
If I change it back to normal overlay bridge network it will work with the forwarded port.
May you take a look at it again?

Hey @buanet,
just want to tell you that nothing is working with the host net with your docker image right now.
Tested all kinds of combinations... tested the bind ip adresses inside the shell of the contaier but still no access from outside.
If I change it back to normal overlay bridge network it will work with the forwarded port.
May you take a look at it again?

Ok I found the "problem" maybe...
After editing the IOB_STATESDB_PORT to 9002 instead the default 9000 it shows a new error message:
------------------------------------------------------------

-----   Step 3 of 5: Checking ioBroker installation    -----

------------------------------------------------------------

(Re)Setting folder permissions (This might take a while! Please be patient!)...

Done.

Fixing "sudo-bug" by replacing sudo in iobroker with gosu...

Done.

Hostname in ioBroker does not match the hostname of this container.

Updating hostname to  iobroker...

Could not connect database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0.

Could not connect database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0.

The host for instance "system.adapter.admin.0" was changed from "35f25f5596c8" to "iobroker".

The host for instance "system.adapter.discovery.0" was changed from "35f25f5596c8" to "iobroker".

The host for instance "system.adapter.info.0" was changed from "35f25f5596c8" to "iobroker".

Done.

------------------------------------------------------------

-----      Step 4 of 5: Applying special settings      -----

------------------------------------------------------------

Some adapters have special requirements/ settings which can be activated by the use of environment variables.

For more information take a look at readme.md on Github!

Adminport set by ENV does not match port configured in ioBroker installation.

Setting Adminport to "8089"...

Could not connect database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0.

Could not connect database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0.

New port for "admin.0" is: 8089

Instance settings for "admin.0" are changed.

and this is with a fresh new installation. I guess the environment variable isn't passed through to the right place isn't it?
Port 9000 is used by portainer.

Ok I found the "problem" maybe...
After editing the IOB_STATESDB_PORT to 9002 instead the default 9000 it shows a new error message:
------------------------------------------------------------

-----   Step 3 of 5: Checking ioBroker installation    -----

------------------------------------------------------------

(Re)Setting folder permissions (This might take a while! Please be patient!)...

Done.

Fixing "sudo-bug" by replacing sudo in iobroker with gosu...

Done.

Hostname in ioBroker does not match the hostname of this container.

Updating hostname to  iobroker...

Could not connect database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0.

Could not connect database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0.

The host for instance "system.adapter.admin.0" was changed from "35f25f5596c8" to "iobroker".

The host for instance "system.adapter.discovery.0" was changed from "35f25f5596c8" to "iobroker".

The host for instance "system.adapter.info.0" was changed from "35f25f5596c8" to "iobroker".

Done.

------------------------------------------------------------

-----      Step 4 of 5: Applying special settings      -----

------------------------------------------------------------

Some adapters have special requirements/ settings which can be activated by the use of environment variables.

For more information take a look at readme.md on Github!

Adminport set by ENV does not match port configured in ioBroker installation.

Setting Adminport to "8089"...

Could not connect database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0.

Could not connect database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0.

New port for "admin.0" is: 8089

Instance settings for "admin.0" are changed.

and this is with a fresh new installation. I guess the environment variable isn't passed through to the right place isn't it?
Port 9000 is used by portainer.

A fresh install on RaspberryPi4 wont run:
the compose-file:
`version: '2'
services:
iobroker:
restart: always
image: buanet/iobroker:latest
container_name: iobroker
hostname: iobroker
ports:

"8081:8081"
environment:
IOB_STATESDB_PORT=9010
IOB_OBJECTSDB_PORT=9011
volumes:
/home/pi/.config/appdata/iobroker:/opt/iobroker`

The Log :
----- Please be patient! -----,
------------------------------------------------------------,
,
------------------------------------------------------------,
----- Debugging information -----,
----- -----,
----- System -----,
----- arch: armv7l -----,
----- -----,
----- Versions -----,
----- image: v5.1.0 -----,
----- node: v12.19.0 -----,
----- npm: 6.14.8 -----,
----- -----,
----- ENV -----,
----- IOB_OBJECTSDB_PORT: 9011 -----,
----- SETGID: 1000 -----,
----- SETUID: 1000 -----,
----- IOB_STATESDB_PORT: 9010 -----,
------------------------------------------------------------,
,
------------------------------------------------------------,
----- Step 1 of 5: Preparing container -----,
------------------------------------------------------------,
,
Registering maintenance script as command.,
Done.,
,
------------------------------------------------------------,
----- Step 2 of 5: Detecting ioBroker installation -----,
------------------------------------------------------------,
,
Existing installation of ioBroker detected in /opt/iobroker.,
,
------------------------------------------------------------,
----- Step 3 of 5: Checking ioBroker installation -----,
------------------------------------------------------------,
,
(Re)Setting folder permissions (This might take a while! Please be patient!)...,
Done.,
,
Fixing "sudo-bug" by replacing sudo in iobroker with gosu...,
Done.,
,
/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22,
throw new Error(Unknown objects type: ${config.objects.type});,
^,
,
Error: Unknown objects type: ,
at Object. (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22:11),
at Module._compile (internal/modules/cjs/loader.js:1015:30),
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10),
at Module.load (internal/modules/cjs/loader.js:879:32),
at Function.Module._load (internal/modules/cjs/loader.js:724:14),
at Module.require (internal/modules/cjs/loader.js:903:19),
at require (internal/modules/cjs/helpers.js:74:18),
at dbConnect (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2439:15),
at CLIObjects.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/cli/cliObjects.js:159:9),
at CLIObjects.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/cli/cliObjects.js:32:29),
/opt/scripts/iobroker_startup.sh: line 197: [: !=: unary operator expected,
------------------------------------------------------------,
----- Step 4 of 5: Applying special settings -----,
------------------------------------------------------------,
,
Some adapters have special requirements/ settings which can be activated by the use of environment variables.,
For more information take a look at readme.md on Github!,
,
/opt/scripts/iobroker_startup.sh: line 369: [: : unary operator expected,
ENV IOB_OBJECTSDB_TYPE is set and value meets detected ioBroker installation. Nothing to do here.,
/opt/scripts/iobroker_startup.sh: line 379: [: : unary operator expected,
ENV IOB_OBJECTSDB_HOST is set and value meets detected ioBroker installation. Nothing to do here.,
ENV IOB_OBJECTSDB_PORT is set and value meets detected ioBroker installation. Nothing to do here.,
,
ENV IOB_STATESDB_TYPE is set and value meets detected ioBroker installation. Nothing to do here.,
/opt/scripts/iobroker_startup.sh: line 406: [: : unary operator expected,
/opt/scripts/iobroker_startup.sh: line 416: [: : unary operator expected,
ENV IOB_STATESDB_HOST is set and value meets detected ioBroker installation. Nothing to do here.,
ENV IOB_STATESDB_PORT is set and value meets detected ioBroker installation. Nothing to do here.,
,
------------------------------------------------------------,
----- Step 5 of 5: ioBroker startup -----,
------------------------------------------------------------,
,
Starting ioBroker...,
,
/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22,
throw new Error(`Unknown objects type: ${config.objects.type}`);,
^,
,
Error: Unknown objects type: ,
at Object. (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22:11),
at Module._compile (internal/modules/cjs/loader.js:1015:30),
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10),
at Module.load (internal/modules/cjs/loader.js:879:32),
at Function.Module._load (internal/modules/cjs/loader.js:724:14),
at Module.require (internal/modules/cjs/loader.js:903:19),
at require (internal/modules/cjs/helpers.js:74:18),
at Object.init (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4140:19),
at Object. (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:8:19),
at Module._compile (internal/modules/cjs/loader.js:1015:30),`

you have to keep statesdb port on 9000.... right now anything else won't work. The env variable should ether be removed or fixed
try to get other services bind to other ports rather than trying to change the ports for ioBroker... same happened to me as I described earlier

A fresh install on RaspberryPi4 wont run:
the compose-file:
`version: '2'
services:
iobroker:
restart: always
image: buanet/iobroker:latest
container_name: iobroker
hostname: iobroker
ports:

"8081:8081"
environment:
IOB_STATESDB_PORT=9010
IOB_OBJECTSDB_PORT=9011
volumes:
/home/pi/.config/appdata/iobroker:/opt/iobroker`

The Log :
----- Please be patient! -----,
------------------------------------------------------------,
,
------------------------------------------------------------,
----- Debugging information -----,
----- -----,
----- System -----,
----- arch: armv7l -----,
----- -----,
----- Versions -----,
----- image: v5.1.0 -----,
----- node: v12.19.0 -----,
----- npm: 6.14.8 -----,
----- -----,
----- ENV -----,
----- IOB_OBJECTSDB_PORT: 9011 -----,
----- SETGID: 1000 -----,
----- SETUID: 1000 -----,
----- IOB_STATESDB_PORT: 9010 -----,
------------------------------------------------------------,
,
------------------------------------------------------------,
----- Step 1 of 5: Preparing container -----,
------------------------------------------------------------,
,
Registering maintenance script as command.,
Done.,
,
------------------------------------------------------------,
----- Step 2 of 5: Detecting ioBroker installation -----,
------------------------------------------------------------,
,
Existing installation of ioBroker detected in /opt/iobroker.,
,
------------------------------------------------------------,
----- Step 3 of 5: Checking ioBroker installation -----,
------------------------------------------------------------,
,
(Re)Setting folder permissions (This might take a while! Please be patient!)...,
Done.,
,
Fixing "sudo-bug" by replacing sudo in iobroker with gosu...,
Done.,
,
/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22,
throw new Error(Unknown objects type: ${config.objects.type});,
^,
,
Error: Unknown objects type: ,
at Object. (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22:11),
at Module._compile (internal/modules/cjs/loader.js:1015:30),
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10),
at Module.load (internal/modules/cjs/loader.js:879:32),
at Function.Module._load (internal/modules/cjs/loader.js:724:14),
at Module.require (internal/modules/cjs/loader.js:903:19),
at require (internal/modules/cjs/helpers.js:74:18),
at dbConnect (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2439:15),
at CLIObjects.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/cli/cliObjects.js:159:9),
at CLIObjects.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/cli/cliObjects.js:32:29),
/opt/scripts/iobroker_startup.sh: line 197: [: !=: unary operator expected,
------------------------------------------------------------,
----- Step 4 of 5: Applying special settings -----,
------------------------------------------------------------,
,
Some adapters have special requirements/ settings which can be activated by the use of environment variables.,
For more information take a look at readme.md on Github!,
,
/opt/scripts/iobroker_startup.sh: line 369: [: : unary operator expected,
ENV IOB_OBJECTSDB_TYPE is set and value meets detected ioBroker installation. Nothing to do here.,
/opt/scripts/iobroker_startup.sh: line 379: [: : unary operator expected,
ENV IOB_OBJECTSDB_HOST is set and value meets detected ioBroker installation. Nothing to do here.,
ENV IOB_OBJECTSDB_PORT is set and value meets detected ioBroker installation. Nothing to do here.,
,
ENV IOB_STATESDB_TYPE is set and value meets detected ioBroker installation. Nothing to do here.,
/opt/scripts/iobroker_startup.sh: line 406: [: : unary operator expected,
/opt/scripts/iobroker_startup.sh: line 416: [: : unary operator expected,
ENV IOB_STATESDB_HOST is set and value meets detected ioBroker installation. Nothing to do here.,
ENV IOB_STATESDB_PORT is set and value meets detected ioBroker installation. Nothing to do here.,
,
------------------------------------------------------------,
----- Step 5 of 5: ioBroker startup -----,
------------------------------------------------------------,
,
Starting ioBroker...,
,
/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22,
throw new Error(`Unknown objects type: ${config.objects.type}`);,
^,
,
Error: Unknown objects type: ,
at Object. (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects.js:22:11),
at Module._compile (internal/modules/cjs/loader.js:1015:30),
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10),
at Module.load (internal/modules/cjs/loader.js:879:32),
at Function.Module._load (internal/modules/cjs/loader.js:724:14),
at Module.require (internal/modules/cjs/loader.js:903:19),
at require (internal/modules/cjs/helpers.js:74:18),
at Object.init (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4140:19),
at Object. (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:8:19),
at Module._compile (internal/modules/cjs/loader.js:1015:30),`

you have to keep statesdb port on 9000.... right now anything else won't work. The env variable should ether be removed or fixed
try to get other services bind to other ports rather than trying to change the ports for ioBroker... same happened to me as I described earlier

Can confirm you found the problem. You have to change the port of your portainer.
you have to keep statesdb port on 9000.... right now anything else won't work. The env variable should ether be removed or fixed
The ENVs for objectsdb port and statesdb port are not for changing the ports inside your iobroker on a standalone master. This is to configure the database connection when connecting to an external db (like in multihost mode or when using redis).
As far as I know, changing the ports inside iobroker is generally not supported at the moment.
Maybe I can mark the ENVs as "advanced settings - you need to know what you're doing" in readme.md.
I see no need to fix or remove it.
As your problem seems to be solved please close this issue.
Regards,
André

Can confirm you found the problem. You have to change the port of your portainer.
you have to keep statesdb port on 9000.... right now anything else won't work. The env variable should ether be removed or fixed
The ENVs for objectsdb port and statesdb port are not for changing the ports inside your iobroker on a standalone master. This is to configure the database connection when connecting to an external db (like in multihost mode or when using redis).
As far as I know, changing the ports inside iobroker is generally not supported at the moment.
Maybe I can mark the ENVs as "advanced settings - you need to know what you're doing" in readme.md.
I see no need to fix or remove it.
As your problem seems to be solved please close this issue.
Regards,
André

As I see no more actions here for 2 weeks now, I'll close this issue. Please feel free to reopen it if needed.
Thank you.
Regards,
André

As I see no more actions here for 2 weeks now, I'll close this issue. Please feel free to reopen it if needed.
Thank you.
Regards,
André

authors: buanet ffdfson nicedevil007

repo: buanet/docker-iobroker


text:
chore(package): update eslint to version 4.19.1

Closes #114

Coverage remained the same at 93.382% when pulling 02e78131dc47bf9c483b5a5a75e6d30d2183ea4f on greenkeeper/eslint-4.19.1 into 93a600bc7aeacfe9326ff1246ee0753f7b97f77f on master.

Coverage remained the same at 93.382% when pulling 02e78131dc47bf9c483b5a5a75e6d30d2183ea4f on greenkeeper/eslint-4.19.1 into 93a600bc7aeacfe9326ff1246ee0753f7b97f77f on master.

authors: coveralls helio-frota

repo: bucharest-gold/fidelity


text:
Provide function to write RPC errors from HTTP middleware

Is your feature request related to a problem? Please describe.
Even though Connect handlers work with net/http middleware, it's often necessary to re-implement existing HTTP middleware as Connect interceptors so that clients get nicely-annotated errors. This is a little silly.
Describe the solution you'd like
It'd be nice for Connect to include a function that HTTP middleware can use to encode Connect errors. func WriteError(http.ResponseWriter, *http.Request, error) might work.
Describe alternatives you've considered
The status quo is okay, but forces users to jump through more hoops that we'd like.

I look forward to this feature coming soon

Released in v0.5.0!

authors: akshayjshah xdorro

repo: bufbuild/connect-go


text:
[PLAT-12536] iOS XcFramework E2E

Goal
setup and tests for the iOS XcFramework fixture.
Changeset
Configure the new fixture to use the XcFramework packages and add steps to buildkite to run the E2E tests. I've had to move one test to a separate file so that this can be excluded from the XcFramework E2E tests due to a strange issues with mangled strings.
Testing
Covered by CI

It's not necessary to duplicate all the code files within the new test fixture - the new Xcode project/worksapce can be modified to reference the same source code files.  Have a look at the structure we now have in the bugsnag-cocoa repository here:
https://github.com/bugsnag/bugsnag-cocoa/tree/next/features/fixtures/ios

authors: joshedney twometresteve

repo: bugsnag/bugsnag-cocoa-performance