> Rebase and merge on GitHub will always update the committer information and create new commit SHAs
115 karma · joined May 24, 2016
> Rebase and merge on GitHub will always update the committer information and create new commit SHAs
It's kind of like if you had a shell script to launch programs, and it used to move the mouse to press icons, but now you've deprecated that and will only run programs directly.
© 2020 Wyze Labs, Inc
Amazon, Alexa, Echo Spot and all related logos are trademarks of Amazon.com, Inc. or its affiliates.
Google, Inc., Google, Google Home, Google Home Mini, G logo, The Google Assistant built-in, and related marks and logos are trademarks of Google, Inc. All rights reserved.
But nothing says that any given device, say a Zigbee light controller (on/off) from manufacturer X, MUST implement the standard on/off cluster for that. They could have their own manufacturer-specific profile+cluster for controlling the light, where a payload of 0x11 turns it on, 0x22 turns it off, and 0xF7 toggles the light. Or maybe you send the ASCII string "on".
Suppose that HA has implemented the functionality needed to interact with the standard on/off cluster. That functionality would work with devices that implement the standard cluster, but not with manufacturer X's device that needs the string "on". But then, HA could be updated to recognize such devices and implement the required functionality.
Assuming you're familiar with HTTP: just because two services both consume and produce JSON, doesn't mean the message bodies are interchangeable.
At the RF protocol level, yes they should be. Speaking as someone who works at a company with a few Zigbee-certified products, I can say that there are a LOT of "optional" features in the Zigbee specification, and even implementations of mandatory features can have differences that lead to incompatibility.
Manufacturer-specific profiles are also a big thing. So just be aware that manufacturer A's Zigbee "hub"/coordinator may or may not be inherently compatible with manufacturer B's sensors. But I would imagine that open-source systems like HomeAssistant deal with that.
And inversely, PyPI normalizes the package name (the name you give to `pip install`) to use hyphens instead of underscores. https://www.python.org/dev/peps/pep-0503/#normalized-names
> exmaple.com was explicitly reserved for scenarios like this
class MyObject:
def doThing(self, value: str) -> None:
# whatever
pass
obj = MyObject()
obj.doThing("value!")
MyObject.doThing(obj, "a different value!")
The only difference is that doThing is namespaced to the MyObject class.Virtualization core: Drop recompiler, i.e. running VMs now needs a CPU supporting hardware virtualization
I think the "Availability" note means how long they plan to support it and/or sell it.
(Only took me about twenty minutes of assorted searches to find it too...)