"unhanded error event" after running for 2 hrs

I ran my homebridge for approx. 2 hr then I get this message.  Does anyone have any idea what is causing it? Is it a plugin I have installed? If so can you tell me which so I can move the issue to that page. Thanks for the help!
events.js:141
throw er; // Unhandled 'error' event
^
Error: connect TIME-OUT {has Ip address}
at Object.exports._errnoException (util.js:874:11)
at exports._exceptionWithHostPort (util.js:897:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1063:14)

I have recently run home bridge in debug mode and am almost positive it is an issue with the demo-platform. I am going to keep this issue open incase it is actually an issue with homebridge. After we get it resolved whether it is Homebridge or the plugins faults I will close the issue

By that do you mean the wemo-platform (auto-correct) - can you send me the debug logs in an issue in https://github.com/rudders/homebridge-platform-wemo please.

Having the exact same issue. Running on a Rasp Pi. Any thoughts on what this is?

@vincentanthony - are you using homebridge-platform-wemo?

No, just nest and harmony hub at the moment.

try running env DEBUG=* homebridge and post some of the error log that leads up to the error - that should help identify the module that isn't handling this http.request error.

I'm having this error too. Sometimes it happens after a couple of days, others after a couple of hours:
Using homebridge-platform-wemo.
Here are some of the logs:
Tue, 29 Dec 2015 02:48:41 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
Tue, 29 Dec 2015 02:48:41 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
Tue, 29 Dec 2015 02:48:41 GMT EventedHTTPServer [fe80::1489:e5d7:c839:86a9] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
Tue, 29 Dec 2015 02:49:45 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221445K1300262, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:49:45 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:49:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:49:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221448K1300E1C, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:49:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221439K13003D3, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:49:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120017B, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:49:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:51:45 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221445K1300262, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:51:45 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:51:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:51:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221448K1300E1C, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:51:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221439K13003D3, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:51:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120017B, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:51:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:53:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221445K1300262, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:53:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:53:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:53:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221448K1300E1C, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:53:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221439K13003D3, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:53:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120017B, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:53:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:basicevent:1
Tue, 29 Dec 2015 02:53:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:basicevent:1
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNREFUSED <IP_ADDRESS>:49153
    at Object.exports._errnoException (util.js:837:11)
    at exports._exceptionWithHostPort (util.js:860:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1060:14)
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>

Sun, 03 Jan 2016 08:18:36 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
Sun, 03 Jan 2016 08:18:36 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
Sun, 03 Jan 2016 08:18:36 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
Sun, 03 Jan 2016 08:18:36 GMT EventedHTTPServer [2601:646:8b00:fb19:a2:ab9f:2031:4cde] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
Sun, 03 Jan 2016 08:18:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:18:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:18:43 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221445K1300262, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:18:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:18:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:18:43 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221448K1300E1C, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:18:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:18:44 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:18:45 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120017B, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:18:45 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120017B, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:18:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221439K13003D3, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:20:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:20:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:20:43 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221445K1300262, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:20:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:20:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:20:43 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221448K1300E1C, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:20:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:20:44 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:20:45 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120017B, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:20:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221439K13003D3, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:20:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120017B, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:22:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:22:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:22:43 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221445K1300262, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:22:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:22:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:22:43 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221448K1300E1C, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:22:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:22:44 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:22:45 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120017B, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:22:46 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221439K13003D3, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:22:46 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120017B, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:24:43 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221448K1300E1C, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:24:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:24:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:24:43 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221445K1300262, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:24:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:insight:1
Sun, 03 Jan 2016 08:24:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221504K12000B8, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:24:43 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K1200172, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:24:44 GMT wemo-client Renewing subscription - Device: uuid:Insight-1_0-221506K120013A, Service: urn:Belkin:service:basicevent:1
Sun, 03 Jan 2016 08:24:47 GMT wemo-client Renewing subscription - Device: uuid:Lightswitch-1_0-221439K13003D3, Service: urn:Belkin:service:basicevent:1
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: connect ETIMEDOUT <IP_ADDRESS>:49153
    at Object.exports._errnoException (util.js:837:11)
    at exports._exceptionWithHostPort (util.js:860:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1060:14)
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>

@devbobo found where the issue was. It was an issue of the Wemo-client dependency for the plugin. it has now been fixed. I have been running homebridge for the past 5 hrs and haven't had the error yet. You need to replace the contents the client.js with https://raw.githubusercontent.com/timonreinhard/wemo-client/master/client.js
You will find the client.js at homebridge-platfprm-wemo/node_modules/wemoclient/master/client.js
Tell me if that worked for you. The fix should be pushed to the nam site soon just the Wemo-Client npm has to be updated for the homebridge-platform-wemo npm to be updated for the fix. If that makes any since. So essentially the fix should be mainstream as soon as the Wemo-client NPM page gets updated then enabling @rudders to update the homebridge-platform-wemo plugin.
@benmazin

Please update to<EMAIL_ADDRESS>which will pull the latests wemo-client form a private fork. This will get us out of trouble till wemo-client is updated,

@benmazin ^^

Thanks for the update, I've upgraded to 0.6.1, I'll see how it behave over the next few days.

Even running<EMAIL_ADDRESS>I received the error after. It took 1h50m to appear.
I've attached the full debug logs from starting Homebridge to the error.
homebridge.err.txt
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: connect ETIMEDOUT <IP_ADDRESS>:49153
    at Object.exports._errnoException (util.js:837:11)
    at exports._exceptionWithHostPort (util.js:860:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1060:14)

I'm running:
Raspbian 4.9.2-10
└──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

@bemazin Try downloading @devbobo fork of the platform-wemo and delete @rudders plugin. Let us know how that works. The way I described how I got it working worked for me. I haven't updated to @rudders newest version of the platform-wemo plugin. I just have been using a manually edited client.js

@benmazin - please make sure you do an pm install -g home bridge-platform-wemo so you pull through the wemo-client from my repo ( dependency that should come through with<EMAIL_ADDRESS>)

Could you could also run env DEBUG=* homebridge and share with us the log just before it crashes so we can be sure it's in this plugin.

@rudders I've upgraded to the latest version as you described:
└─┬<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ ├─┬<EMAIL_ADDRESS>  │ │ └─┬<EMAIL_ADDRESS>  │ │   └──<EMAIL_ADDRESS>  │ └─┬<EMAIL_ADDRESS>  │   └──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
I also upgraded Homebridge to the latest:
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    ├──<EMAIL_ADDRESS>(git://github.com/KhaosT/node-curve25519.git#922eae612bb379fa84e8deb29f80c53d57c8be7b)
    ├──<EMAIL_ADDRESS>(git://github.com/KhaosT/ed25519.git#6356bc9e6e4643d56020293c14920ac12bcaa1ac)
    ├──<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>(git://github.com/KhaosT/node-srp.git#7feff53254897a0b1b9f0667ad17a8beb78acbb9)

But I'm still receive the error "events.js:141". Homebrige is crashing and throwing this error extremely frequently.
I've attached some of the DEBUG logs
Debug Log.txt
Any help is appreciate.
Thanks
Ben

Thats a different error mate - that looks like a second instance of home bridge trying to be started and they're clashing in listening on that port.
Homebridge is running on port 51827.
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE :::51827
    at Object.exports._errnoException (util.js:837:11)
    at exports._exceptionWithHostPort (util.js:860:20)

thanks for the help, I'm in the process of looking the for instance and cleaning it up.

@benmazin I am going to close the issue because the original problem was fixed and this was improperly placed. Feel free to create a separate issue if you need to but make sure you share your debug log or at least the last couple of lines including the error.

Thanks @AppleTechy and @rudders for your help.
I was playing with using forever to keep homebridge running due to the crashes constant, looks like I had it setup running on a different port and hadn't stopped it from auto starting at boot.
I'm back up hopefully no more crashes.

@benmazin No problem thats the beauty of open source is everyone helps each other. Good Luck!

No worries

Anyone experiencing ETIMEDOUT errors and that use the homebridge-platform-wemo plugin might like to test my forked version of the plugin discussed here https://github.com/rudders/homebridge-platform-wemo/issues/21#issuecomment-171392046 - please update that issue with your findings.


renderBox of type Null instead of RenderBox in getNodeWidgetSize.

@alexst07
import 'package:flutter/material.dart';
import 'package:node_editor/node_editor.dart';

import 'nodes.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  final NodeEditorController controller = NodeEditorController();
  final FocusNode _focusNode = FocusNode();
  final FocusNode _focusNode2 = FocusNode();
  TextEditingController _controller = TextEditingController();
  @override
  void initState() {
    controller.addSelectListener((Connection conn) {
      debugPrint("ON SELECT inNode: ${conn.inNode}, inPort: ${conn.inPort}");
    });

    controller.addNode(
      componentNode('node_1_1'),
      NodePosition.afterLast,
    );
    controller.addNode(
      componentNode('node_1_2'),
      NodePosition.afterLast,
    );
    controller.addNode(
      componentNode('node_1_3'),
      NodePosition.afterLast,
    );
    controller.addNode(
      receiverNode('node_2_1', _focusNode2, _controller),
      NodePosition.afterLast,
    );
    controller.addNode(
      binaryNode('node_3_1'),
      NodePosition.afterLast,
    );
    controller.addNode(
      sinkNode('node_4_1'),
      NodePosition.afterLast,
    );
    super.initState();
  }
  void _addNewNode() {
    controller.addNode(
      componentNode('new_node'),
      NodePosition.afterLast,
    );
  }
  @override
  void dispose() {
    _focusNode.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        title: Text(widget.title),
        actions: [
          IconButton(
              onPressed: () {
                debugPrint('controller.toMap(): ${controller.toJson()}');
              },
              icon: Icon(Icons.abc))
        ],
      ),
      body: NodeEditor(
        focusNode: _focusNode,
        controller: controller,
        background: const GridBackground(
          backgroundColor: Color(0xfdfffd),
          lineColor: Color.fromARGB(255, 255, 255, 255),
          strokeWidth: 1,
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _addNewNode,
        child: Icon(Icons.add),
      ),
    );
  }
}

I am getting the following error when the button is pressed and this was the stack when the button was pressed
Connecting to VM Service at ws://<IP_ADDRESS>:64992/QngPEayh25k=/ws
flutter: Set stackPos
════════ Exception caught by widgets library ═══════════════════════════════════
The following _TypeError was thrown building LayoutBuilder:
type 'Null' is not a subtype of type 'RenderBox' in type cast
The relevant error-causing widget was:
NodeEditor NodeEditor:file:///Users/samyashah21/Downloads/alexst07%20flutter_node_editor%20master%20examples-advanced/lib/main.dart:101:16
When the exception was thrown, this was the stack:
#0      NodesManager.getNodeWidgetSize (package:node_editor/src/nodes.dart:243:48)
#1      NodeEditorController.getMaxScreenSize (package:node_editor/src/controller.dart:77:32)
#2      _NodeEditorState.build.. (package:node_editor/src/custom_painter.dart:88:53)
#3      _LayoutBuilderElement._layout.layoutCallback (package:flutter/src/widgets/layout_builder.dart:116:77)
#4      BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2835:19)
#5      _LayoutBuilderElement._layout (package:flutter/src/widgets/layout_builder.dart:150:12)
#6      RenderObject.invokeLayoutCallback. (package:flutter/src/rendering/object.dart:2657:59)
#7      PipelineOwner._enableMutationsToDirtySubtrees (package:flutter/src/rendering/object.dart:1071:15)
#8      RenderObject.invokeLayoutCallback (package:flutter/src/rendering/object.dart:2657:14)
#9      RenderConstrainedLayoutBuilder.rebuildIfNecessary (package:flutter/src/widgets/layout_builder.dart:225:7)
#10     _RenderLayoutBuilder.performLayout (package:flutter/src/widgets/layout_builder.dart:308:5)
#11     RenderObject._layoutWithoutResize (package:flutter/src/rendering/object.dart:2385:7)
#12     PipelineOwner.flushLayout (package:flutter/src/rendering/object.dart:1025:18)
#13     PipelineOwner.flushLayout (package:flutter/src/rendering/object.dart:1038:15)
#14     RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:591:23)
#15     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:986:13)
#16     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:457:5)
#17     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1325:15)
#18     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1255:9)
#19     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:1113:5)
#20     _invoke (dart:ui/hooks.dart:312:13)
#21     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:383:5)
#22     _drawFrame (dart:ui/hooks.dart:283:31)
════════════════════════════════════════════════════════════════════════════════

Figured out the issue, it was because the RenderBox was being accessed before it was initialised.

Hey @ShaSam2104,
Thanks for the solution, could you please create an example with this code you posted here? As this example to demonstrate the bug was made by you, I believe it would be more fair and appropriate for you to create the example and commit.

yess i will make changes in the example and commit it


Add configMap defaultMode to helm chart values file

Please describe the missing/desired functionality:
Provide a mechanism to override defaulMode value using values.yaml
|volumes:|
||- name: config
||configMap:|
||name: {{ include "zeebe-cluster.fullname" . }}|
||{color:#FF0000}defaultMode: 0744{color}|
What problem would the feature solve?
After deployment containers cant read configMap because they are running as non-root
What effort would be required without the feature?
Since we're running containers as non-root, after each deploy we have to change this value manually in yaml.
Why do you need this feature?
Because it's inconvenient to change this value after each deployment
How would not implementing the feature impact you?
We need to change yaml file manually after each helm upgrade or install.
Support
https://jira.camunda.com/browse/SUPPORT-12967

Same issue here: https://jira.camunda.com/browse/SUPPORT-13290

What @jonathanlukas and the customer proposed is not working for another partner on open shift. They get the same initial error and tried to fix with the mentioned defaultMode, but get:
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(StatefulSet.spec.template.spec.containers[0].volumeMounts[0]): unknown field "defaultMode" in io.k8s.api.core.v1.VolumeMount
This aligns with kubectl explain StatefulSet --recursive=true | grep volumeMounts -A10 -B1 which gives no occurence of this attribute...

Hey @McAlm it is part of the volumnes spec

https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/#volume-v1-core

OpenShift converts the value from octal to integer representation. But setting 0755 works to get Zeebe started.

Hey folks, @falko @McAlm @jonathanlukas with #277 we solved this issue (hopefully) we made the defaultMode for configMaps for all services configurable. Example for Zeebe would be: zeebe.configMap.defaultMode=0755
I will create an release now so you can try it out and tell it our customers.


Auth solution

@GermanoRenner
It's up to you now!

Yeah! I'm doing.

@GermanoRenner
Sorry, but I need to get this issue.
I need for a project I've started.
I opened a PR #60 for treating of this.


[WIP] fix race condition due to pruning in results watcher

Changes
Fixes: #514
/kind bug
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you review them:

[ ] Has Docs included if any changes are user facing
[ ] Has Tests included if any functionality added or changed
[x] Tested your changes locally (if this is a code change)
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user-facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[x] Release notes contain the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

hi @gabemontero @adambkaplan with finalizers, at least locally, I've been able to fix the race condition. There's a small caveat with finalizer. Bcs we add finalizer for the PR to not get pruned until the streaming/sending of logs is done. Finalizer along with the PipelineRun object is stored as well.
While that might not be a deal breaker (I'm not sure though), but I find it simpler to utilize this field from LogStatus to simply hold on to pruning until we find isStored: true.

hi @gabemontero @adambkaplan with finalizers, at least locally, I've been able to fix the race condition. There's a small caveat with finalizer. Bcs we add finalizer for the PR to not get pruned until the streaming/sending of logs is done. Finalizer along with the PipelineRun object is stored as well. While that might not be a deal breaker (I'm not sure though), but I find it simpler to utilize this field from LogStatus to simply hold on to pruning until we find isStored: true.

for me at least I like using IsStored() instead as well @ramessesii2 @adambkaplan @ramessesii2 @sayan-biswas  assuming the watcher reconciler that handles pruning can watch for that and requeue if it is not yet stored
I believe that is the case based on what I recall from the fix for handling cancelled pipeline/task runs
putting metadata i.e. in the object we are storing seems more fragile to me in hindsight
what do you all think?
perhaps as part of breaking out the mem leak fix from this one, either create a separate PR or a separate commit in this PR so we can compare IsStored vs. finalizer

FYI : #713 uses Logs API to address race condition


LND not ready yet ... waiting another 60 seconds. If this takes too long (more then 10min total) --> CTRL+c and report Problem

I have used both the raspiblitz-2018-10-20.img.gz card image and have also built my own using these instructions. The bitcoin side is working fine, but I continually get stuck at:
LND not ready yet ... waiting another 60 seconds.
If this takes too long (more then 10min total) --> CTRL+c and report Problem

If I do CTRL+c and then "sudo systemctl status lnd" I get:
● lnd.service - LND Lightning Daemon
   Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2018-12-04 14:37:23 GMT; 13s ago
  Process: 4802 ExecStart=/usr/local/bin/lnd --externalip=${PUBLICIP} (code=exited, status=1/FAILURE)
 Main PID: 4802 (code=exited, status=1/FAILURE)

Dec 04 14:37:23 RaspiBlitz systemd[1]: lnd.service: Unit entered failed state.
Dec 04 14:37:23 RaspiBlitz systemd[1]: lnd.service: Failed with result 'exit-code'.

I'm not sure why lnd won't run. Any suggestions? I'm using as Raspberry Pi 2 which I think should work fine since I had a lightning node setup working fine previously under the RaspiBolt project.

LND has problems starting up - is exiting. It would be helpful to check the logfiles:
sudo journalctl -u lnd -b --no-pager -n20

Here is the output of sudo journalctl -u lnd -b --no-pager -n20
admin@RaspiBlitz:~ sudo journalctl -u lnd -b --no-pager -n20
-- Logs begin at Tue 2018-12-04 14:14:42 GMT, end at Wed 2018-12-05 14:28:53 GMT. --
Dec 05 14:26:46 RaspiBlitz systemd[1]: Stopped LND Lightning Daemon.
Dec 05 14:26:46 RaspiBlitz systemd[1]: lnd.service: Ignoring invalid environment assignment '<body bgcolor=white>': /run/publicip
Dec 05 14:26:46 RaspiBlitz systemd[1]: Started LND Lightning Daemon.
Dec 05 14:26:46 RaspiBlitz systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Dec 05 14:26:46 RaspiBlitz systemd[1]: lnd.service: Unit entered failed state.
Dec 05 14:26:46 RaspiBlitz systemd[1]: lnd.service: Failed with result 'exit-code'.
Dec 05 14:27:46 RaspiBlitz systemd[1]: lnd.service: Service hold-off time over, scheduling restart.
Dec 05 14:27:46 RaspiBlitz systemd[1]: Stopped LND Lightning Daemon.
Dec 05 14:27:46 RaspiBlitz systemd[1]: lnd.service: Ignoring invalid environment assignment '<body bgcolor=white>': /run/publicip
Dec 05 14:27:46 RaspiBlitz systemd[1]: Started LND Lightning Daemon.
Dec 05 14:27:47 RaspiBlitz systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Dec 05 14:27:47 RaspiBlitz systemd[1]: lnd.service: Unit entered failed state.
Dec 05 14:27:47 RaspiBlitz systemd[1]: lnd.service: Failed with result 'exit-code'.
Dec 05 14:28:47 RaspiBlitz systemd[1]: lnd.service: Service hold-off time over, scheduling restart.
Dec 05 14:28:47 RaspiBlitz systemd[1]: Stopped LND Lightning Daemon.
Dec 05 14:28:47 RaspiBlitz systemd[1]: lnd.service: Ignoring invalid environment assignment '<body bgcolor=white>': /run/publicip
Dec 05 14:28:47 RaspiBlitz systemd[1]: Started LND Lightning Daemon.
Dec 05 14:28:47 RaspiBlitz systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Dec 05 14:28:47 RaspiBlitz systemd[1]: lnd.service: Unit entered failed state.
Dec 05 14:28:47 RaspiBlitz systemd[1]: lnd.service: Failed with result 'exit-code'.

I don't know what changed, but I ssh'd into my pi today and it greeted me with the option to setup a wallet. I went through the process of creating a wallet, but still seems like lnd isn't running. Now whenever I reboot it, it asks me to put in my password to unlock the wallet, but no matter what I put in for the password (correct or not) it returns:
[lncli] rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:10009: connect: connection refused"
I ctrl+c and check if lnd is running, but it isn't:
admin@RaspiBlitz:~ $ sudo systemctl status lnd
● lnd.service - LND Lightning Daemon
   Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2018-12-10 12:16:14 GMT; 35s ago
  Process: 5719 ExecStart=/usr/local/bin/lnd --externalip=${PUBLICIP} (code=exited, status=1/FAILURE)
 Main PID: 5719 (code=exited, status=1/FAILURE)

Dec 10 12:16:14 RaspiBlitz systemd[1]: lnd.service: Failed with result 'exit-code'.

I do sudo journalctl -u lnd -b --no-pager -n20 again, but still returns the same as before:
admin@RaspiBlitz:~ $ sudo journalctl -u lnd -b --no-pager -n20
-- Logs begin at Mon 2018-12-10 07:49:27 GMT, end at Mon 2018-12-10 12:17:24 GMT. --
Dec 10 12:15:13 RaspiBlitz systemd[1]: Stopped LND Lightning Daemon.
Dec 10 12:15:13 RaspiBlitz systemd[1]: lnd.service: Ignoring invalid environment assignment '<body bgcolor=white>': /run/publicip
Dec 10 12:15:13 RaspiBlitz systemd[1]: Started LND Lightning Daemon.
Dec 10 12:15:14 RaspiBlitz systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 12:15:14 RaspiBlitz systemd[1]: lnd.service: Unit entered failed state.
Dec 10 12:15:14 RaspiBlitz systemd[1]: lnd.service: Failed with result 'exit-code'.
Dec 10 12:16:14 RaspiBlitz systemd[1]: lnd.service: Service hold-off time over, scheduling restart.
Dec 10 12:16:14 RaspiBlitz systemd[1]: Stopped LND Lightning Daemon.
Dec 10 12:16:14 RaspiBlitz systemd[1]: lnd.service: Ignoring invalid environment assignment '<body bgcolor=white>': /run/publicip
Dec 10 12:16:14 RaspiBlitz systemd[1]: Started LND Lightning Daemon.
Dec 10 12:16:14 RaspiBlitz systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 12:16:14 RaspiBlitz systemd[1]: lnd.service: Unit entered failed state.
Dec 10 12:16:14 RaspiBlitz systemd[1]: lnd.service: Failed with result 'exit-code'.
Dec 10 12:17:14 RaspiBlitz systemd[1]: lnd.service: Service hold-off time over, scheduling restart.
Dec 10 12:17:14 RaspiBlitz systemd[1]: Stopped LND Lightning Daemon.
Dec 10 12:17:14 RaspiBlitz systemd[1]: lnd.service: Ignoring invalid environment assignment '<body bgcolor=white>': /run/publicip
Dec 10 12:17:14 RaspiBlitz systemd[1]: Started LND Lightning Daemon.
Dec 10 12:17:15 RaspiBlitz systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 12:17:15 RaspiBlitz systemd[1]: lnd.service: Unit entered failed state.
Dec 10 12:17:15 RaspiBlitz systemd[1]: lnd.service: Failed with result 'exit-code'.

Anyone have any suggestions on what to do to get lnd running?


[Android] Fix immersive full screen mode doesn't recover.

Immersive Fullscreen mode doesn´t recover after changing the volume on
the device.
Refer https://github.com/fujunwei/crosswalk-cordova-android/commit/c9e30e77cf71da2d189faecd861c29c04a1548f6
to fix this issue.
BUG=XWALK-3651, XWALK-2367
(cherry picked from commit 69175e025253dc0ad4537b896444aee60e8f41d8)

@rakuco Please merge this patch to crosswalk-13, thanks.

Is it necessary to backport to previous branch?

If the bug also affects Crosswalk 12, yes.

It affects crosswalk 10 ~ 14, even before Crosswalk 10. Should all of the affected branch be backported? Thanks.

No, we do not work on any branch prior to crosswalk-12 anymore.


don't pin gradle dependency versions

fixes #78

Worked for me after getting this error when trying to make it work with react-native-fcm:
:app:dexDebug
Unknown source file : UNEXPECTED TOP-LEVEL EXCEPTION:
Unknown source file : com.android.dex.DexException: Multiple dex files define Lcom/google/android/gms/measurement/AppMeasurementContentProvider;
Unknown source file :  	at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
Unknown source file :  	at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
Unknown source file :  	at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
Unknown source file :  	at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
Unknown source file :  	at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
Unknown source file :  	at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:502)
Unknown source file :  	at com.android.dx.command.dexer.Main.runMonoDex(Main.java:334)
Unknown source file :  	at com.android.dx.command.dexer.Main.run(Main.java:277)
Unknown source file :  	at com.android.dx.command.dexer.Main.main(Main.java:245)
Unknown source file :  	at com.android.dx.command.Main.main(Main.java:106)

Fixes #78

@rebeccahughes Hi, can we get a new package with this?

rndi 0.9.5 published

@GantMan thanks for that


Example written in C (stanc-lite?)

As a demonstration it might be useful to have a program written in C which uses the interface. Maybe put it in examples/c? (https://github.com/protobuf-c/protobuf-c)

There's not yet any C library supporting protobuf version 3


Add TabPanel component

Migrate the TabPanel component we currently have in a number of our apps to this library. This is the component that wraps tab children and allows only one of them to be visible at a time.

For the story, create a couple of tab panels and expose a value to show that you can hide one and make another visible etc.

For the tests, similar thing, create couple of components parented in to tab panel and check they are visible/invisible based on the current value.

Repos to update:

NGD
VPM
MM
IAM
Cloud licensing


✨ Automatically register standardized values that are not yet in instance

Fixes https://github.com/laminlabs/lamindb/issues/2071

Now automatically creating records from_source if standardized values are not yet in the instance
Limits output of standardized and unsaved values to max 10 values in line with other print limits
Fixes an intendation issue of the warning output

Hmm, auto-saving doesn’t look right to me, .standardize is meant to be a non-write operation, similar to .validate and .inspect.
The user pattern is expected to be:
standardized_names = bt.Gene.standardize(names)
records = bt.Gene.from_values(standardized_names)
ln.save(records)

I wouldn’t make un-explicit save calls in low-level API. I think it’s OK in Curator because that’s a high-level class. For standardize I don’t think we should do it.


Avoid returning errors where possible

https://github.com/rust-fuzz/arbitrary/commit/1d2f65360f634968b5525f4d6430a88a376277f0

Next breaking release that we make, I think we can remove the fallibility from
the Arbitrary trait and all the Unstructured methods.

This wasn't addressed in the discussion about 1.0 https://github.com/rust-fuzz/arbitrary/issues/62 .
Is this still something we want to do? Are you open for a PR implementing it?

I don't think it is worth addressing at this time, because we just cut 1.0 and I don't think it is worth cutting a 2.0 just for this change.
Really unfortunate that this slipped through the cracks though :(


scaleFactor calculation for gradient could cause divide by zero error…

This should fix:
https://github.com/tmroyal/Chart.HeatMap/issues/2
If the range of heatmap data isn't sufficiently large you can get divide by zero errors. Looks like maybe should be adding one here instead of subtracting.
Not sure what version of Charts.js you were basing this off off, so I didn't rebuild the whole project, just changed the main source file.

I fixed this issue by using a conditional statement before it calculates the scaleFactor for 'gradient' colorInterpolation. Since I was not having any issue if the datalength is equal to zero, I just used the conditional statement for datalength 1 or 2. I tried to use your fix but I was not getting the exact color gradient, so here it looks like in my code:
var colorFunction, scaleFactor;
var dataLength = max-min;
var base = min;
if (dataLength === 1 || dataLength === 2){
      colorInterpolation = 'palette';
}
if (colorInterpolation === 'gradient'){
  colorFunction = getGradientColor;
  scaleFactor = (colors.length-1)/(dataLength -1);
} else {
  colorFunction = getIndexedColor;
  scaleFactor = (colors.length)/(dataLength+1);
}


Update dependencies

The package with updated dependencies is now published as 1.0.2.
@matthiasn Sorry for the delay.
@t1ooo Thank you for contributing!


Alexa, set thermostat temperature

Home Assistant release with the issue:
0.74.2
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
Alexa
Description of problem:
Alexa report an (audio) error message when setting a thermostat temperature. The temperature is setted but Alexa report a problem.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:
It seems in v3 Smart Home api, Alexa expect a "context" answer for such an event. I've changed the smart_home.py code to add this context and this solve the issue, see https://community.home-assistant.io/t/alexa-home-assistant-cloud-climate-support/61826/5

I too have testes this and it appears to work, implemented slightly differently as below in the following functions:
`async def async_api_set_target_temp(hass, config, request, context, entity):
"""Process a set target temperature request."""
min_temp = entity.attributes.get(climate.ATTR_MIN_TEMP)
max_temp = entity.attributes.get(climate.ATTR_MAX_TEMP)
unit = hass.config.units.temperature_unit
data = {
    ATTR_ENTITY_ID: entity.entity_id
}
payload = request[API_PAYLOAD]
if 'targetSetpoint' in payload:
    requestType = 'targetSetpoint'
    temp = temperature_from_object(hass, payload['targetSetpoint'])
    if temp < min_temp or temp > max_temp:
        return api_error_temp_range(
            hass, request, temp, min_temp, max_temp)
    data[ATTR_TEMPERATURE] = temp
if 'lowerSetpoint' in payload:
    requestType = 'lowerSetpoint'
    temp_low = temperature_from_object(hass, payload['lowerSetpoint'])
    if temp_low < min_temp or temp_low > max_temp:
        return api_error_temp_range(
            hass, request, temp_low, min_temp, max_temp)
    data[climate.ATTR_TARGET_TEMP_LOW] = temp_low
if 'upperSetpoint' in payload:
    requestType = 'lowerSetpoint'
    temp_high = temperature_from_object(hass, payload['upperSetpoint'])
    if temp_high < min_temp or temp_high > max_temp:
        return api_error_temp_range(
            hass, request, temp_high, min_temp, max_temp)
    data[climate.ATTR_TARGET_TEMP_HIGH] = temp_high

await hass.services.async_call(
    entity.domain, climate.SERVICE_SET_TEMPERATURE, data, blocking=False,
    context=context)

context={
    'properties': [
            { "namespace": "Alexa.ThermostatController",
              "name": requestType,
              "value":
                { "value": temp,
                  "scale": API_TEMP_UNITS[unit]
                }
            }
          ]
        }
return api_message(request, context = context)

@HANDLERS.register(('Alexa.ThermostatController', 'AdjustTargetTemperature'))
@extract_entity
async def async_api_adjust_target_temp(hass, config, request, context, entity):
"""Process an adjust target temperature request."""
min_temp = entity.attributes.get(climate.ATTR_MIN_TEMP)
max_temp = entity.attributes.get(climate.ATTR_MAX_TEMP)
unit = hass.config.units.temperature_unit
temp_delta = temperature_from_object(
    hass, request[API_PAYLOAD]['targetSetpointDelta'], interval=True)
target_temp = float(entity.attributes.get(ATTR_TEMPERATURE)) + temp_delta

if target_temp < min_temp or target_temp > max_temp:
    return api_error_temp_range(
        hass, request, target_temp, min_temp, max_temp)

data = {
    ATTR_ENTITY_ID: entity.entity_id,
    ATTR_TEMPERATURE: target_temp,
}

await hass.services.async_call(
    entity.domain, climate.SERVICE_SET_TEMPERATURE, data, blocking=False,
    context=context)

context={
    'properties': [
            { "namespace": "Alexa.ThermostatController",
              "name": "targetSetpoint",
              "value":
                { "value": target_temp,
                  "scale": API_TEMP_UNITS[unit]
                }
            }
          ]
        }
return api_message(request, context = context)

@HANDLERS.register(('Alexa.ThermostatController', 'SetThermostatMode'))
@extract_entity
async def async_api_set_thermostat_mode(hass, config, request, context,
entity):
"""Process a set thermostat mode request."""
mode = request[API_PAYLOAD]['thermostatMode']
mode = mode if isinstance(mode, str) else mode['value']
operation_list = entity.attributes.get(climate.ATTR_OPERATION_LIST)
ha_mode = next(
(k for k, v in API_THERMOSTAT_MODES.items() if v == mode),
None
)
if ha_mode not in operation_list:
msg = 'The requested thermostat mode {} is not supported'.format(mode)
return api_error(
request,
namespace='Alexa.ThermostatController',
error_type='UNSUPPORTED_THERMOSTAT_MODE',
error_message=msg
)
data = {
    ATTR_ENTITY_ID: entity.entity_id,
    climate.ATTR_OPERATION_MODE: ha_mode,
}

await hass.services.async_call(
    entity.domain, climate.SERVICE_SET_OPERATION_MODE, data,
    blocking=False, context=context)

context={
    'properties': [
            { "namespace": "Alexa.ThermostatController",
              "name": "thermostatMode",
              "value":
                {
                  "value": mode,
                }
            }
          ]
        }
return api_message(request, context = context)`

Duplicate of: https://github.com/home-assistant/home-assistant/issues/15580
PR to address this is linked to that bug - #15580


Actors not moving in synchronous mode

I use two clients, one for data collection, the other for spawning actors (spawn_npc.py). The first runs in synchronous mode to make sure no data is lost. But I have the problem that all actors from the second client do not move when I see them through the cameras of the first client. When running an asynchronous script (e.g. manual_control.py) all of the spawned pedestrians can be seen moving. Does anyone know how to solve this issue? Thanks a lot in advance!
(CARLA version 0.9.6 running on Ubuntu 18.04)

I have the same issue on Ubuntu 16.04 using CARLA 0.9.8. I used in Python world.tick() but my actors are not moving when I set autopilot(True). Maybe a problem with the TrafficManager module?

I got it :)
There is a "hidden" function "set_synchronous_mode" for the TrafficManager that is not documented in the Python API. I got it with the following code working.
tm = client.get_trafficmanager()     TrafficManager.set_synchronous_mode(tm, True)

@Schuck84 where should I add these two lines of codes? In spawn_npc.py or synchronous_mode.py? I tried to add in both of them but it doesn't work for me.

I ended up using the spawn_npc.py file as a thread in the other client I was using to make it work. This issue might also help you, as it is somewhat related: https://github.com/carla-simulator/scenario_runner/issues/495


Update CODEOWNERS

Adding myself as a code owner so I can stay on top of issues and PRs filed.

No changes needing a change description found.

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs

just waiting for resolution of dicussion on the same PR for typespec, I don't think this is necsssary and will not necessarly achieve the expected result anwway


Add support for boost mode

Hi Cyr-ius,
Can you add support for the boost mode for the Heatzy Pilote v2 ?
You can switch boost mode on by setting derog_mode to 2 and derog_time to 30min, or 60 min, or what you want.
You can't find it in the heatzy api documentation, but there is blog post about it (in french, sorry) :
https://heatzy.com/blog/communaute-siri-boost
I made a fork a month ago with boost mode :
https://github.com/ellmout/hass-heatzy/tree/feature-boost-mode
but your code change a lot since.
Thx

The boost mode is based on a timer of 30 or 60 min, it would rather be a service that allows people to choose the duration

I have Wiser thermostat and you can set the boost mode like this :

Please test 5.9.7-beta0
Boost services and vacations services
Boost preset

Setting boost mode is ok !
But when i switch back to eco, it stays on boost mode !
In the app, it stays on boost mode too.
Thx!

Fix into 5.9.7-beta1


Is there umd compatible version  [ mobx.umd.js ]?

<EMAIL_ADDRESS>

I'm assuming you are looking for a umd bundle of the mobx-wiretap?  I'll try to include in the next release which should be in a couple of days.

Hey @PawelGIX, I did not realize that the bundle that already available in mobx-wiretap is, in fact, a UMD bundle. Did you experience any issues using it?


[Todo] remove one deprecated section of CUE basic

Location: https://kubevela.io/docs/platform-engineers/cue/basic
https://kubevela.io/zh/docs/platform-engineers/cue/basic#导入-kubernetes-包
Apply to: Both zh and en docs in v1.1 and NEXT
Confirmed with @leejanee

You can  still keep this section in v1.1 , and it's deprecated in Next and v1.2

/assign

/assign

/assign


New app: Best Picture Picker

Description
Built an app that will cycle through all Academy Award Best Picture Nominees and display the name of the movie, the imdb rating, the year it was nominated, and the movie poster art. Uses an API under the hood which I already have built for another web application I designed.
Copilot

copilot:all

I have read the CLA Document and I hereby sign the CLA

recheck


AttributeError: 'list' object has no attribute 'readlines'

Hello,
Your script works fine if I pipe my list of dates into it, but I'm facing an error when using the --file argument.
$ ./gfs.py daily=3 --file /tmp/list
Traceback (most recent call last):
  File ".../gfs.py", line 504, in <module>
    main()
  File ".../gfs.py", line 478, in main
    dates = set(line.strip() for line in args.file.readlines())
                                         ^^^^^^^^^^^^^^^^^^^
AttributeError: 'list' object has no attribute 'readlines'

Might be caused by use of nargs=1 in the argument's declaration
https://github.com/shello/gfs.py/blob/02b9a1e1a632fa1069182a741ae983aa2ded7450/gfs.py#L458-L459
From the docs https://docs.python.org/3/library/argparse.html#nargs

Note that nargs=1 produces a list of one item. This is different from the default, in which the item is produced by itself.

Hey @dregad, thanks for reporting that issue. You're entirely correct that the nargs=1 option shouldn't be there and is the root cause of this problem. I've pushed a commit to fix it.
% python3 gfs.py daily=3 </tmp/test_gfspy
2017-05-21T22:00:00
2017-05-20T20:00:00
2017-05-14T19:00:00
% python3 gfs.py -f /tmp/test_gfspy daily=3
2017-05-14T19:00:00
2017-05-20T20:00:00
2017-05-21T22:00:00


[Mobile] Expired Pokemon on Notification list wont go away until Page Refresh

Expired Pokemon on Notification list wont go away until Page Refresh

that seems like a feature... if you chose to be notified about it, you probably want to see how much time it has, even if it expired in order to maybe determine if that is a nest for a certain spawn.

thought so (and I like the idea but maybe control it with a checkbox??), but it doesn't say expired in any case... I've crosschecked the desktop and mobile version and sometimes the pokemon is still there and sometimes is not..also that's not the way it works on the desktop version (expired). maybe keep the same behavior on both ???


[Merged by Bors] - perf (Subalgebra.Basic): de-prioritize Subalgebra.module'

This can send TC search off on a wild goose chase. Discussion on Zulip

Thanks :tada:
bors merge

Here are the benchmark results for commit a192f92. There were significant changes against commit c532ace:
  Benchmark                                                           Metric         Change
  =========================================================================================
+ ~Mathlib.CategoryTheory.Limits.FilteredColimitCommutesFiniteLimit   instructions   -20.4%

This file doesn't import the changed file at all (or any other algebraic files)! Why does it keep showing up in benchmark results, once more after this.

That is noisy for reasons I have yet to figure out.


As an author, posts I create can link to images.

I'm not sure if this is any image or just images that users have uploaded. If it's any image, that can be done with markdown at the moment

Their stories are too vague... I think the markdown is a good interpretation of it. If Josh wants to argue about it.. We can argue with Hindle. I'll reassign to you and call it done.

For submission: verified, assuming through markdown is ok. (PS, I thought it would just make a link to an image, it actually brings the image into the post. Very nice :+1: )


bump @octokit/rest from 18.5.6 to 18.6.7

Dependabot opened a PR where some types now are string | undefined so we just need to update the code to support the new types.
Should be a pretty simple job. PR exists here: #6374
Happy hacking!

@benjdlambert I guess we have to do yarn add string.

@benjdlambert But the branch of #6374 is deleted how I can cherry-pick the commit. It saying fatal: bad revision '4349a88'.

@iamrajiv the branch is restored, you should be able to fetch the branch now and either carry on working on that branch, or cherry pick the commit onto your own fork.

As PR #6494 got closed due to incomplete implementation I'd like to take this one on me to do another run 😄


Add option to always open bottom dock with result

Added an option to always open bottom dock with the result of the command, regardless of bottom dock visibility.

CI failure is unrelated to code changed.

Thanks! I'll push a new update tonight


Update 4 Digit Number Combinations.py

Removed repeated code and added PEP8 styling.

Thank you @ytho . I've updated the code using your suggestion. Appended the strings to the list, if the user needs to access it.


Mimmick game features

Please add a Double Time button or Nightcore button, some songs are only fun to listen in nightcore mode because they're really slow paced.
It would also be really cool if you could figure out a way for the application to read the highest difficulty songs and have a button where it plays the clicking noise from the circles in game.
Talking about this hit sound : https://www.youtube.com/watch?v=HgUCxmzMjNk
example here : https://imgur.com/a/ScGQ6zF
I'm a retired player so I plan on using this software since I can't physically play anymore, its really nice software being able to listen to the music without having to launch into the game itself and scroll through the menus constantly. But these 2 features would be really nice to have because it just sounds wrong sometimes not being able to listen to some songs with out the hit circle sounds.
edit : also just came up with another idea, please have an option where we can click on a "copy to clipboard" option so if we wanna look up the song on Spotify or youtube it saves us the trouble of having to keep looking at the name.

Yeah, I tried to implement something like this earlier. Wasn't able to achieve it in satisfying manner, so decided against it. I'll look at it again in free time, but can't promise I implement it. osu.Music mostly works directly with osu database which is faster and easier than manually work with beatmap files. And for me to achieve this funcionality I have to work with beatmap files.

So doing a nightcore feature wouldn't be possible? NightCore or DT feature? It is just the game speeding up at 1.5x speed. So it should be possible.

Sorry for the confusion. I was talking about the hit sound feature. As for DT/NC: used audio library doesn't support playback speed change out of the box, but I should be able to implement it myself.

Sweet, I also did have a couple other requests I just thought of.
https://imgur.com/a/9logUzs can you add a beatmap preview window? So we can see what version of a song is? Since there's like 20 different versions of certain beatmaps now. Would be nice.
https://imgur.com/a/rfY3ihb also this one is a must, when hovering over the osu,music app its annoying I cant pause it without having to open it up or alt tabbing into the program. Can you please add a small play button like what windows media player does?
Many thanks!


Updating golang/x/net to version 0.24.0

Updating the golang/x/net version to 0.24.0 as per OSD-23081 JIRA

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

Project coverage is 54.94%. Comparing base (62570a8) to head (16cd588).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #172   +/-   ##
=======================================
  Coverage   54.94%   54.94%
=======================================
  Files           7        7
  Lines         637      637
=======================================
  Hits          350      350
  Misses        277      277
  Partials       10       10

/retest

/lgtm

/lgtm


Remove emit-metrics flag in e2e tests base library

Fix https://github.com/knative/test-infra/issues/1568
Remove emit-metrics as the relevant job has been deprecated.
/cc @adrcunha
/cc @chaodaiG

Nice!
/lgtm
/approve


A couple minor fixes and WHITESPACE!!!

What exactly did you do to the whitespace? I can't tell.

I fixed indentation and removed trailing whitespace.

How did you fix indentation? And I don't know why there would be whitespace, as Atom automatically removes it. Odd.

Vim is a magical thing

mixed-indentation

:retab
fixed.

trailing whitespace

:%s/\s\+$
fixed. Atom looking so great now?

u r meen

Oh well, not my fault you're unworthy of a good editor.
On Tue, Sep 13, 2016, 07:48 Erik Boesen<EMAIL_ADDRESS>wrote:

u r meen
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ErikBoesen/FRCNewTab/pull/16#issuecomment-246656363,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGcMgKfxgCTEcWD5ceOFiv_RZZvxl_gRks5qpo2ggaJpZM4J2ee_
.

1-800-SO-RUDE


Expound on example.

I think it would be really helpful to have a second more advanced example.
I had gone down a (albeit stupid) rabbithole modifying the repo to allow for callbacks before I realized you intended for a user to supply their own command handler.
I'm also deathly lost when it comes to get apps working.

Yeah, I think I could provide an example command handler.
What are you trying to do with apps? They're pretty much like all the other commands.
In theory, it could be possible to provide the list of apps and icons just like command handler as an argument, but for the library's use case it doesn't matter.
Harmony doesn't use the TCP API for apps though, it uses IR, so if you're trying that, it won't work.

The apps have alluded me in their use. I was just trying to get full functionality out of the API and I wasn't able to figure them out.
If they are IR only then it makes sense why I couldn't figure them out, they're probably useless to me.
Well the example command handler would still be helpful to others for sure! This tool is great and I'm going to try and spread it around because you seem to have done the best job in doing this out of anything else I've seen. Keep up the good work!


Add project on codeclimate

added lint tool, I want resolver #4

Coverage remained the same at 71.25% when pulling a8c01b4d056fce7746a58ac27c26cf713abfb533 on codeclimate into c9b57f95e621355d63a136514066895f9a4e0f55 on master.


fnm doesn't work when navigating to the directory with .fnmrc, .nvmrc or .node-version

Hi, I just installed fnm and trying to make it work, would appreciate if you can help me to fix the issue.

fnm v1.8.0
fish v2.4.0

Hi @liubko, can you share your fish version and OS?

macOS Sierra v10.12.1
fish v2.4.0

This happened to me when I had Fisherman NVM installed prior to installing fnm. Both plugins have defined nvm.fish and node.fish functions which might be causing conflicts.

@josalmi Thanks for sharing this.

I'm having the same problem with Fish 2.6.0, fnm 1.8.2, macOS 10.12.6, and I don't believe I ever installed Fisherman NVM.

@wesbaker Ping 😉

The only other Fish item I have installed is https://github.com/rafaelrinaldi/pure. Not sure if that helps...?

@will-stone These days I am on verman, but wesbasker may be able to help you out when he gets a chance to see this.

Ah, thanks @JorgeBucaran I'll give verman a go. Is that considered the successor to fnm? (I'm a proper fish newbie, having only installed it this morning after getting frustrated with how slow zsh is)

@will-stone Not really, after fnm's source grew too big for my taste I decided to make simpler tool, so verman was born. Mostly to version node and go, but there's ruby support too.

So I wiped my fish installation completely. Started again, installed Fisherman, installed fnm, but same issue. Please also note, that where a folder contains a node-version file, not even the fnm file works.

@will-stone I think I have a solution. I’ll post it once I get to my desk.

@will-stone mind trying the fix in #53? You should just need to change the code in ~/.config/fisherman/fnm/functions/__fnm_run_bin_as.fish

that looks to have fixed it 👍


Cant get integration working

Hi,
I have configured the webhook URL and the base URL, created channel and sent a test, it was not received in the channel. Tested multiple combinations of base URL and channel name:
Our GitLab URL is: https://gitlab.com/example.com/projectslug
So I have tried:
Base: https://gitlab.com/
Ch: example.com-projectSlug
Base: https://gitlab.com/example.com
Ch: projectSlug
Thanks

This might have something to do with case sensitivity. Pls try to name the channel in all lower case.
Also, I found that the newest version from this repository is not yet in the Marketplace. I triggered a new release, but this depends on an approval from Rocketchat to actually get there. It might be worth to look out for this coming release, and try with this version again.

@jschirrmacher sorry my bad, we had it lowercase everything I just wrote the example camel case. The problem was, that the hook url was like: example.com//api/apps/...  notice the double slash after .com maybe we have rocket chat miss-configured since it was generated with that double slash, usually that's no problem for routing in most apps so I did not give it too much thought.


Allow setting of ContentType

Allow multipart builders to set the content type if passed in, otherwise ... use the default.

Cool thing.


Cube.is_compatible requires cell_methods to have the same order

On this line:  https://github.com/SciTools/iris/blob/b2ce2a34e2eef7e3d6203c77ada7ed4ce89e3145/lib/iris/cube.py#L918 cell methods is compared in a way which seems like it cares about the order of the cell methods. It may be more appropriate to check equality in a way which ignores order (perhaps by comparing sets).

@stephenworsley The iris.coords.CellMethod is not very rich in functionality, even through it's been around for a while.
This certainly seems like a reasonable approach to take to make the equality more robust i.e., independent of order - which shouldn't make a difference.

While you’re in there, I have a question about this method at #2992.  Perhaps the docstring can be improved for clarification?

In general, I believe cell methods are not commutable, e.g. taking the mean over time of a standard deviation over area vs. a standard deviation over area of a mean over time. Hence, the order of cell methods is important.

@rhattersley Thanks, that's good to know.


claws-mail: Change download URL

The update commit for claws-mail was missing the new url and file hash for the installer

I appreciate it Ash!
It almost feels wrong to push your changes, I would have just made an issue but I thought I could just change the url & hash and save someone else the effort :p


Knowledge Build-up 'landscape-setup'

Description
Before we can build good landscaper-components for existing Gardener components, we need to have a good understanding of the currently used 'landscape-setup'.

We learned as much as possible, so now we can close this issue.


anchor-contrib: Add testutils

This should be a separate package-- we don't want chai to be added to user bundles


test new command query tx-mempool

depends on: https://github.com/input-output-hk/cardano-node/issues/4459

The query tx-mempool looks like a useful command that should be added to clusterlib and used from there.

The query tx-mempool looks like a useful command that should be added to clusterlib and used from there.

updated


Add Backward Compatibility to PyQt4 and <=PyQt5.6

I've already create two separated branches for the PyQt4 version and the PyQt5.6 version. The 5.6 is the one with greatest performance since QWebView is still faster than QWebEngineView.
Create two branches in the main repository so I can open a PR. One branch from 8baec2 and another from c44a01

Thanks for your effort, new branch added.


Advanced options showing if Approve Transaction unchecks "Execute transaction" checkbox

Description
When the last owner has to sign the tx and decides to NOT execute it the "Advanced options" are being shown and there is a warning message "This transaction will most likely fail."
Steps to reproduce
In a 2/x safe

Create a transaction that will be awaiting one other confirmation
With another Safe owner click to confirm the transaction
In the "Approve Transaction" modal uncheck the "Execute transaction" checkbox

Expected result

The "Advanced options" shall not be displayed
The warning should not show

Screenshots

Probably makes sense to add this into the refactor of the approval modals, no?

I think it has to be tackled earlier.


Add option to disable EME expiration events

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
2.5.0
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app?
Both recreate the issue, yes.
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
EDGE 18.18362 on Windows 10 and also XBOX
What are the manifest and license server URIs?
Asset is encrypted with PlayReady.
What did you do?
Start playback of a dash manifest encrypted with playready.
What did you expect to happen?
Playback played back without interruption
What actually happened?
Video playback struggles, every few frames the video appears to get stuck and no dropped frames are reported.
I have been digging into an issue where XBOX is having an issue where it "stutters". The shaka player is being used on XBOX and the content is encrypted with PlayReady. Upon diagnosing this issue I eventually discovered there is an expirationTimer running every second. When I add a rudimentary timer around the call to session.expired I see this call taking around 1000 milliseconds consistently. This expirationTimer appears to be a no-op for dash manifests and it would be nice to have a way to disable this timer as it is impacting video playback on XBOX. This ticket may make more since as a feature request. As far as I can tell there is no way to disable the timer and the cost of checking the expiration seems expensive with the playready cdm on EDGE.
https://github.com/google/shaka-player/blob/v2.4.x/lib/media/drm_engine.js#L1708

This was with playready 3.0 and different keys on video and audio.

That function isn't a no-op, it is used to update the expiration of EME sessions.  This is used to update metadata for offline content and to fire an event for the app when the expiration changes.  Unfortunately there is no way for us to get an event when the expiration changes, so we need to poll.  Expiration is important for apps so they can show UI or change streams when approaching the expiration time.
But since this is an app event, we could add a configuration value to disable this timer.  This will be a low-priority enhancement, but we'd be happy to review a PR.

I'm very surprised that it takes a full second.  Can you tell us how many sessions are being updated in your case?  (The length of this.activeSessions_)
If the callback through player to the DASH parser is a no-op, the only thing taking up time should be the loop over sessions and asking the browser to give us the expiration time.  If the loop only has a small number of iterations, it could be that asking for the expiration time is surprisingly expensive on XBox.  If we know those details, it could help us build a more efficient solution for that platform.

If I recall correctly there were 3 sessions. The application which I use shaka for uses a separate key for audio, SD video, and HD video. I was also very surprised when I saw it taking so long. The issue was also noticeable on windows desktop with EDGE. To resolve the issue I have commented out the expirationTimer for the time being.
https://github.com/google/shaka-player/blob/master/lib/media/drm_engine.js#L109
The assets I am provided come from an external source. That source is starting to test new changes they are making to their assets and this issue was spotted. The old assets and the new assets they have provided me with both use 3 sessions. The old assets work fine and make the call in a reasonable time similar to chrome where it is around 0ms and not a noticeable synchronous interruption. With the new assets the time for that call on EDGE (or XBOX) jumped significantly.

That is really interesting.  I would be very interested to know what the expiration values are.  For example, (this is pure speculation, and I know nothing about PlayReady), perhaps the old assets have a "never expire" policy of some kind, in which case expiration would be NaN.  If the new assets now expire at a specific time, there may be an async call to another process to get the expiration time from the CDM, which could be very slow on XBox.
Again, pure speculation.  Can you instrument the expiration times for the old and new assets to give us one more data point?  I may be able to contact someone at Microsoft to chase down an answer if we have enough information.

Collected some real data today versus the rough estimates I provided when making this ticket in haste.
The new content I referenced above has 2 active sessions and an expiration for each. The previous content had 1 active session and also an expiration. The expiration time is 5 hours for both sessions. One of the sessions is for audio and one is for video.
On both the old and new content it is taking the call to expiration 50-100ms. When there are 2 active sessions this blocking for 50-100ms gets more noticeable as it happens twice.
Another interesting tidbit is that if I continually restart playback without refreshing the overall page the call to expiration takes longer and longer. This can be recreated on the shaka demo page.
This is the timing code I quickly threw into the compiled source:
var startTime = new Date().getTime();
var b=a.oldExpiration,c=a.session.expiration;
console.log("EXPIRATION: " + c);
console.log("TOOK: " + ((new Date()).getTime() - startTime));

I pulled this data on a windows desktop with the most recent EDGE browser but similar behavior is seen on XBOX.

#2456 has brought up another need for this option.  Some policies on Tizen 5 report the wrong expiration time.

If anyone is interested to contribute a PR for this, please let us know!


Testing Buefy Snackbars

I am not finding any meaning full documentation regarding how to test buefy snackbar

What do you mean? You don't need to test other libraries, you need to concentrate on your own logic and behaviour. Provide a piece of code you want to test


How to use multiple ExtrudeGeometry holes

const g1 = new THREE.ExtrudeGeometry(boxShape1, extrudeSettings)
const g2= new THREE.ExtrudeGeometry(boxShape2, extrudeSettings)
const g3 = new THREE.ExtrudeGeometry(boxShape3, extrudeSettings)

  const csgEvaluator = new Evaluator();
  const brush1 = new Brush(geometry);
  const brush2 = new Brush(g1);
  const result = csgEvaluator.evaluate(brush1, brush2, SUBTRACTION);
  newGeometry = result.geometry;
  const brush= new Brush(newGeometry);
  const brush3 = new Brush(g2);
const result2= csgEvaluator.evaluate(brush1, brush3, SUBTRACTION);

I can't do that。Something's wrong with him。

// basic pieces
const cylinder1 = new Brush( new THREE.CylinderGeometry( 0.5, 0.5, 6, 45 ), blueMaterial );
cylinder1.updateMatrixWorld();

const cylinder2 = new Brush( new THREE.CylinderGeometry( 0.5, 0.5, 6, 45 ), blueMaterial );
cylinder2.rotation.x = Math.PI / 2;
cylinder2.updateMatrixWorld();

const cylinder3 = new Brush( new THREE.CylinderGeometry( 0.5, 0.5, 6, 45 ), blueMaterial );
cylinder3.rotation.z = Math.PI / 2;
cylinder3.updateMatrixWorld();

const sphere = new Brush( new THREE.SphereGeometry( 1, 50, 50 ), greenMaterial );
sphere.updateMatrixWorld();

const box = new Brush( new THREE.BoxGeometry( 1.5, 1.5, 1.5 ), redMaterial );
box.updateMatrixWorld();

// processing
const evaluator = new Evaluator();
let result;
result = evaluator.evaluate( cylinder1, cylinder2, ADDITION );
result = evaluator.evaluate( result, cylinder3, ADDITION );
result = evaluator.evaluate( sphere, result, SUBTRACTION );
result = evaluator.evaluate( box, result, INTERSECTION );

i know!can't read geometry,load brush?

 const brush= new Brush(newGeometry);
 const brush3 = new Brush(g2);
 const result2= csgEvaluator.evaluate(brush1, brush3, SUBTRACTION);

You are using brush1 again in the second evluation.

i know!can't read geometry,load brush?

I'm not sure what you mean by this.


Suggested minor edits

Hello,
I had some issues running the pipeline via the provided commands on an Ubuntu 20 VM. So, I went ahead and forked/fixed the problems I was having. I'm happy to put in a pull request, but I'm not sure if I've handled the changes in the way that you would prefer. That includes converting python2 scripts to 3 using 2to3 (plus some other minor edits), making a new folder for bash scripts (from slightly modified sbatch scripts), and deleting headers from some of the design files that were causing errors.
Let me know if you still want the pull request, and I'll put one in.
-Lucas

Lucas
Have you seen the latest pipeline?
Everything was converted I believe... there is a new paper look for
"Testcross" first author Miller.   Would be very bad if we have a deprecated link from your paper not directing to the newest code. Would also be bad if we still have v2 floating about
Lauren

From: J. Lucas Boatwright @.>
Sent: Sunday, June 27, 2021 2:44 PM
To: McIntyre-Lab/BayesASE @.>
Cc: Subscribed @.***>
Subject: [McIntyre-Lab/BayesASE] Suggested minor edits (#1)
[External Email]
Hello,
I had some issues running the pipeline via the provided commands on an Ubuntu 20 VM. So, I went ahead and forked/fixed the problems I was having. I'm happy to put in a pull request, but I'm not sure if I've handled the changes in the way that you would prefer. That includes converting python2 scripts to 3 using 2to3 (plus some other minor edits), making a new folder for bash scripts (from slightly modified sbatch scripts), and deleting headers from some of the design files that were causing errors.
Let me know if you still want the pull request, and I'll put one in.
-Lucas
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_McIntyre-2DLab_BayesASE_issues_1&d=DwMCaQ&c=sJ6xIWYx-zLMB3EPkvcnVg&r=lnVATt_LlDyOygd8jM84Jw&m=HZvH8brj892Ht9pz2k0P32MwYUZIi9mPV7eFPOf9lu0&s=kXwpqk6vV_Zf4n4DRmUL0djZTTEO2eVauwCRQSf1nlI&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AE43DBOOK4SF5M47MGN6AV3TU5WR3ANCNFSM47MU6ELA&d=DwMCaQ&c=sJ6xIWYx-zLMB3EPkvcnVg&r=lnVATt_LlDyOygd8jM84Jw&m=HZvH8brj892Ht9pz2k0P32MwYUZIi9mPV7eFPOf9lu0&s=gPuBWjrgXycqyqPFlEsvldaQFfzmHnyPnHWEPAwgwUE&e=.

Hi Lauren!
I hope you're doing well. Yes, I saw this newly published pipeline and was excited about the changes you all made. I'm actually helping Doug/Pam write something on robust homoeolog-specific expression and suggested that we use this newer pipeline. I think all of the main code looks fine, I was just having minor trouble with the demo steps and thought I'd mention it. It may alternatively be an issue with my setup, but I thought I would check to make sure. Either way, I have it working on my system now. The available setup options (conda, Nextflow, etc) made getting everything running very easy.
Thanks for the quick reply.


Fragment being SubComponent of Activity example.

2 Fragment classes, its Component classes, layouts

New branch if possible

opening new pull request


Adding raw public key provisioning

Fix the issue:#1328
Signed-off-by: Xiangfei Ma<EMAIL_ADDRESS>

Yes, these changes would have to go in after the Q4 release. And I think it would help to split it up into smaller pull requests once we digest the overall design. In particular the changes to cryptlib are effectively standalone and testable and would make a good standalone pull request.

Yes, these changes would have to go in after the Q4 2022 release.

I second that. This change is too big. Hard to review in limited time. And we need fix other planned items.
@xiangfeima, any concern if we push to after the Q4 2022 release.

I will update new PR for spdm-emu once this one is considered to be good to merge.

Usually, what we do is to create a PR for spdm-emu as well, as draft.
It will fail the CI as expected, but allow people to review the code and feedback.
Then once libspdm merge, we create a new PR to sync libspdm. Once it is merged, the CI will pass.

Sorry for late, I left office for few days.

any concern if we push to after the Q4 2022 release.

It's okay to me. I understand we need more time to review this big change.

Usually, what we do is to create a PR for spdm-emu as well, as draft.
It will fail the CI as expected, but allow people to review the code and feedback.
Then once libspdm merge, we create a new PR to sync libspdm. Once it is merged, the CI will pass.

I will do this.


[newrelic-logging] Made fluent-bit.conf and parsers.conf ConfigMap configurable from values.yaml file

Is this a new chart
No
What this PR does / why we need it:
The changes in this PR provide users the ability to customize the fluent-bit.conf and parsers.conf files using the values.yaml file.  Previously, this was statically set in the configmap.yaml file.  This will provide much better flexibility for custom fluent-bit configurations.
Which issue this PR fixes
N/A
Special notes for your reviewer:
This closely mimics the fluent-bit helm chart
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [mychartname])

Hi @bpschmitt , is it still working in progress?

@tejunior yes, still testing some changes.

I've made a mess, so closing this PR and opening a fresh one :)


tests for QualityScoreDistribution

thanks to @dekling
fixed #408

Back to @akiezun to patch this branch before I review.

i'll wait for #636  to be merged and rebase on it

back to @droazen then

Back to @akiezun -- one comment, then good to merge.


mat-select ngModelChange/selectionChange triggers twice on selecting option with undefined value

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Triggering/emitting only once.
What is the current behavior?
If you select an option without a value propery (thus making it undefined) ngModelChange/selectionChange triggers twice.
What are the steps to reproduce?
https://stackblitz.com/angular/bnolvjbmlro
What is the use-case or motivation for changing an existing behavior?
Inconsistent behavior
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular CLI: 6.1.2
Node: 8.9.1
OS: win32 x64
Angular: 6.1.2
Material: 6.4.5
Is there anything else we should know?
No

Closing as a duplicate of https://github.com/angular/material2/issues/10675.


[11.x] Fix integrity constraint violation on failed_jobs_uuid_unique

Fixes #53230
Listeners are bound each time Artisan::call('queue:work') is called. That results in:

Job output being duplicated
If DatabaseUuidFailedJobProvider is used, then an integrity constraint violation is thrown due to multiple calls to logFailedJob().

Rather than using the global events system where event listeners cannot be unset, this PR uses SplObserver / SplSubject (Observer Design pattern). That allows the observer (event listeners) to be reset/cleared, every time queue:work runs.

I wonder if this would be more easily solved with just a static variable in the WorkCommand class?

That's what I did first! I'm happy to have another look at that.


Rewrite README update script in Python and remove from pre-commit

.update-readme-help.sh benefits from being rewritten in Python because:

The syntax for sed -i with no extension differs between Linux and macOS, and thus the current shell script is not portable.
The Python script is more efficient, as it only needs to pass over the file once, where as the shell script processes the file twice.

Running .update-readme-help.sh via pre-commit is problematic, as it requires duct to be installed in the current Python environment, yet no provision is made for this.  Unless you can come up with a simple, clean way to install duct in editable mode in some virtualenv, I think it's better to just leave this out of pre-commit.

Ah thank you, it was clunky and driving me crazy :)


add reverse geocoding to get portal address from lat/lng

A quick look found a couple of options

google: https://developers.google.com/maps/documentation/geocoding/#ReverseGeocoding
(this seems to work without an API key too)

map quest: http://developer.mapquest.com/web/products/open/geocoding-service

we could also use the regular geocoding service from either of these as the search option too - I think we directly hit openstreetmap at the moment?

Is there more work to be done on this issue?


Importing constants not working

In the README's "Actions" example:
import { LOAD, SAVE } from 'redux-storage';

Importing the constants in this way doesn't work as they are exposed as properties of the default export object, rather than as named exports.
I've gotten around this with something like:
import storage from 'redux-storage';
const { LOAD, SAVE } = storage;

We could either:

Update the README example, or
Change the way the constants are exported

What do you think?

Thank you for reporting this!
It broke with switching from babel@5 to babel@6 (more details) :cry:
But I've been able to:

fix this bug
updated the README to encourage import * as storage from 'redux-storage' for full imports
but also keep the old behaviour import storage from 'redux-storage'

A new version (v1.3.4) is already published to npm :rocket:

Awesome :tada:
Thanks for providing such a comprehensive solution!


Feat: Add ScrollToTop button

Describe the feature
I want to add scroll to top button in resource page
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@MuraliDharan7 assigned


[types] switch from 256 bit -> 128 bit addresses

[types] switch from 256 bit -> 128 bit addresses

Change address length to 16 bytes

Add 32 byte AuthenticationKey type + logic for deriving an address from the last 16 bytes of an authentication key

Change all Move code/tests to expect 16 byte addresses instead of 32. The biggest change here is that any script that may create an account (mint, create_account, P2P payment) now take both an address parameter and an "auth_key_prefix" parameter. If no account exists at address, one will be created at auth_key_prefix | address. In the future, we can consider adding separate scripts for minting/paying to a pre-existing account, but this seems like the least disruptive way forward for now.

The CLI client interprets now 32 byte values as authentication keys and 16 byte values as account addresses
The vast majority of the code changes here are updating tests and client code that conflates account addresses and authentication keys. The meat of this change is in account_address.rs and libra_account.move (create_account procedure).

Motivation
See https://github.com/libra/libra/issues/2764.
Have you read the Contributing Guidelines on pull requests?
Yes

#2774  will fix the test here.

:umbrella: The latest upstream changes (presumably 5ada39a94d36faabb41dc3a346b8f55ae0a9638e) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 85c5d2d1d8d596061f38a548d8fa9cc57462b360) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably aff42939a73bc04c6f3e1ce648a9e21e037f0bca) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably a2bbf6d8bcdc650634b8ac99231ae1ce639fce0a) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably f014b4ffd2052bf1241d56a2646dffa27208831c) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably bf22198145009538c76194cf579da05f5e3dc3ec) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 5ae7350067d5e351409e4ff8cc36541fc642a370) made this pull request unmergeable. Please resolve the merge conflicts.

 Many thanks.

@bors-libra r=kchalkias

:pushpin: Commit 41c4e6f has been approved by kchalkias

:hourglass: Testing commit 41c4e6fd3b08826995887c248d0f1fcddd44fbce with merge 95ffa7240864df2c201950f41db78ca253503001...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: kchalkias
Pushing 95ffa7240864df2c201950f41db78ca253503001 to master...


Spanish translations

Hi, how can i help you to add spanish translations? i use this mod in my personal modpack and i want to have this mod in spanish if it's possible please. Thank you in advance.

Hi,
You can make a pull request with new translation file added (they are located in "common/src/main/resources/assets/seasonhud/lang") or here is the latest english version of the file and you can make the changes to it and send it back. You'll just replace the second part of each line with the spanish translation for it, then name the file the locale code for the translation. You can find that here under the "Locale Code > In-Game" heading.
en_us.json

I have done it locally and I have tried to upload the branch with the spanish translations file but I don't have permissions.  Thanks in advance.

If you wanna just upload it in a comment, I can grab that and include it next update

Here it is. Thank you.
es_es.json

Thank you! I'll include that in version 1.8.4, that should be out today


Is there any version of the js source code that has not been compressed and confusing, easy to read? Thank you.

Because I want to see the execution logic of js, but the source code is compressed and confusing, it is not conducive to reading and analysis, requesting to provide a js file that is not compressed and confused.

Webapp folder is front-end codebase

Have found it, thx so much!


Game art layout profiles

It would be helpful to be able to save different game art layouts as “layout profiles” or “custom mixes”.
After setting up a complex multilayer layout I found myself wanting to try something completely different.  I had to screenshot my current layout and reenter the settings from scratch to come back to it.
Another use case is saving tweaks of a similar layout for different systems. Since aspect ratios vary from system to system it may be necessary to adjust parameters. If you ever add a new game and want to scrape the art the user could just select a named profile instead of keeping track of all those small differences.

With the new art loading screen this is defiantly something I want to work on soon I want to try combine this enhancement and #58 together in a full rework of the layouts managment.


Fixes a Typo in Project Euler Problem 70

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #38776
Line 15 changed for a minor typo.

Please have a look at the updated markdown. I hope this fixes everything.

🎉 Congratulations on your first contribution to freeCodeCamp @daksh-goyal 🎉


Bundle products not displayed in cart

What is the location of your example repository?
No response
Which package or tool is having this issue?
Hydrogen
What version of that package or tool are you using?
2024.1.3
What version of Remix are you using?
No response
Steps to Reproduce

Create an ATC button:
function AddToCartButton({analytics, children, disabled, lines, onClick}) {
return (

{(fetcher) => (
<>

<button
type="submit"
onClick={onClick}
disabled={disabled ?? fetcher.state !== 'idle'}
className="text-[#161616] bg-[#f5f5f0] md:text-[#f5f5f0] md:bg-[#f5f5f0] text-md py-2 px-7 rounded-[4px] w-60 md:w-[360px] h-[60px] md:h-14 cursor-pointer hover:bg-white/80 md:hover:bg-white/80 transition duration-300 ease-in-out"
>
{children}

</>
)}

);
}

Create /cart route with switch statement to allow for CartForm.ACTIONS.LinesAdd:
switch (action) {
case CartForm.ACTIONS.LinesAdd:
result = await cart.addLines(inputs.lines);
break;
}

Call this route with the AddToCartButton component, making a post request with inputs={{lines}}. Lines is an array with an object containing the correct merchandiseId and quantity. The input also contains an analytics string, but that is not related to this.

Expected Behavior
After this submission, the correct product should show up in the cart. When retrieving the cart lines, you should get back a lines object with a nodes array containing an id (id for the cartLine) and other information about the merchandise inside that line of the cart.
Actual Behavior
When I retrieve the cart lines, I get back an empty array for each line that a bundle was supposed to be in. When I go to checkout the cart, the bundle shows up in checkout. I cannot see the bundle in cart as there is no id for the cart line or any other information about the merchandise, just the empty array in it's place. I cannot even allow the user to remove this empty cart item because there is no id to perform a cart.updateLines or cart.removeLines mutation on.

Verified that cart querying a bundle product in skeleton breaks. An example cart output from storefront api:

The empty {} in the lines.nodes array is suppose to be the bundle product
Visit the checkout url - the bundled product correctly shows up

{
  "data": {
    "cart": {
      "updatedAt": "2024-03-11T16:53:01Z",
      "id": "gid://shopify/Cart/c1-32841e24355614ab2e45235fb95e1c4a",
      "checkoutUrl": "https://checkout.hydrogen.shop/cart/c/c1-32841e24355614ab2e45235fb95e1c4a?key=380f08dcb2f046ae259ddc0ee83c8149",
      "totalQuantity": 2,
      "buyerIdentity": {
        "countryCode": "US",
        "customer": null,
        "email": null,
        "phone": null
      },
      "lines": {
        "nodes": [
          {},
          {
            "id": "gid://shopify/CartLine/36504483-1b37-4375-8cf7-dd4f4f4cb523?cart=c1-32841e24355614ab2e45235fb95e1c4a",
            "quantity": 1,
            "attributes": [],
            "cost": {
              "totalAmount": {
                "currencyCode": "USD",
                "amount": "600.0"
              },
              "amountPerQuantity": {
                "currencyCode": "USD",
                "amount": "600.0"
              },
              "compareAtAmountPerQuantity": {
                "currencyCode": "USD",
                "amount": "649.95"
              }
            },
            "merchandise": {
              "id": "gid://shopify/ProductVariant/41007289630776",
              "availableForSale": true,
              "compareAtPrice": {
                "currencyCode": "USD",
                "amount": "649.95"
              },
              "price": {
                "currencyCode": "USD",
                "amount": "600.0"
              },
              "requiresShipping": true,
              "title": "154cm / Nested / Carbon-fiber",
              "image": {
                "id": "gid://shopify/ProductImage/36705302544440",
                "url": "https://cdn.shopify.com/s/files/1/0551/4566/0472/products/Main.jpg?v=1655932274",
                "altText": null,
                "width": 3908,
                "height": 3908
              },
              "product": {
                "handle": "snowboard",
                "title": "The Hydrogen Snowboard",
                "id": "gid://shopify/Product/6730850828344"
              },
              "selectedOptions": [
                {
                  "name": "Size",
                  "value": "154cm"
                },
                {
                  "name": "Binding mount",
                  "value": "Nested"
                },
                {
                  "name": "Material",
                  "value": "Carbon-fiber"
                }
              ]
            }
          }
        ]
      },
      "cost": {
        "subtotalAmount": {
          "currencyCode": "USD",
          "amount": "1225.0"
        },
        "totalAmount": {
          "currencyCode": "USD",
          "amount": "1175.0"
        },
        "totalDutyAmount": null,
        "totalTaxAmount": null
      },
      "note": "",
      "attributes": [],
      "discountCodes": []
    }
  },
  "extensions": {
    "context": {
      "country": "US",
      "language": "EN"
    }
  }
}

Thank you for the help! Where should I have looked to find the proper implementation of the CartLineComponent?

We don't have a styling example for bundles but it should just be an array of CartLine.
Here is the API doc for ComponentizableCartLine:
https://shopify.dev/docs/api/storefront/2024-01/objects/ComponentizableCartLine

Thank you. My question is where did I miss this step in implementing bundle products? I could not find the information anywhere that would have led me to understanding I need a CartLineComponent in my CartApiQuery, as you showed me.

It's part of understanding how Graphql the query language works.

cart.cartLines returns a [BaseCartLine!]! object (Doc
BaseCartLine is an interface that is implemented by type CartLine and ComponentizableCartLine

Since BaseCartLine is an interface, this means that we can query for the types it implements. But CartLine and ComponentizableCartLine are consider different types, they must be queried separately with:
    lines(first: $numCartLines) {
      nodes {
        ...CartLineComponent
      }
      nodes {
        ...CartLine
      }
    }