The "uninstalling flag" check in ServiceWorkerRegistration.update() should be moved to the Update algorithm

Currently the spec in section 3.2.5 step 3 says:
If registration's uninstalling flag is set, reject p with an "InvalidStateError" exception and abort these steps.

Therefore, if the script calls unregister() and update() sequentially, assuming the job queue is not empty, the Unregister algorithm runs after the initial call to update(), which is where we check the uninstalling flag.
It seems better to move this check to the Update algorithm instead so that we can check the latest value of the uninstalling flag no matter what the order of operations leading to this have been.
I'm modifying Gecko to implement this.

I also think it makes sense in the update algorithm.  This will also abort soft updates that are triggered on an uninstalling registration.

Added the guard in Update algorithm: 784f69a8fdd027b267abf8f0d80b5c40df137a7a. I didn't remove the corresponding steps in update() and Soft Update so they can abort the update requests before scheduling them. Do you think we better remove them?

I think it would be better to remove the additional checks in update() and Soft Update.
Consider:

Registration has its uninstalling flag set.
A new register job is pending in the queue.  This will clear the uninstalling flag when it runs.
update() is called

Leaving the checks in place will cause the update() call here to be racey.  If update() is called before the register job runs, then it will abort.  If its called after the register job is run then the update will be executed.
In contrast, if we remove the synchronous uninstalling flag checks, then we always get the same behavior.  The update job always execute because the register job clears the flag.

Agreed. Remove those additional checks: 23e6438ae3e2678b7030bc8d6d8778f1b05dc19d. Thanks!


Correctly autoindent single newline in Selection#insertText

Fixes #11473
/cc @kuychaco
@t9md I ran vmp specs against this change and they all pass

Good catch, @50Wliu, thanks. That conditional was getting gnarly so I split it out as well.


One dark theme for xCode

Hi,
I didn't find anything on Google relative to a version of the One Dark theme for xCode.
Is there such a theme available or even a close one?
Thanks !

You can use https://discuss.atom.io/ to start Atom related discussions or questions.

@JeanLebrument Do as @jerone suggests, as this theme is specifically created for Atom. You or someone else will have to create a port of this theme for Xcode.

Was this every made? :panda_face:

Was this ever made? :panda_face:

Try https://libraries.io/alcatraz/One Dark for Xcode

Check this one: xcode-one-dark

Also check out DarkSide theme https://github.com/onmyway133/DarkSide


Question on module structure

Thanks for writing this great library!
Sorry if I am missing something, but would be great if you could help explains where this import comes from?
https://github.com/thedirtyfew/dash-extensions/blob/bd7827b081f0164b1f6a4f05780edcd5e2cd196b/dash_extensions/_imports_.py#L10

That line imports the Python code which is auto generated during the Dash component build process. Take a look at the docs for more details,
https://dash.plotly.com/plugins


dont exit poll() when ime composing

related #1823
we have problem when composing korean because poll() method keep exit when korean first letter composing in IE11
IE11 make selection when korean letter is composing(we need several key type to make one letter)
I think this maybe solution
how about this?

Could you describe the problem that is occurring a bit more precisely?

ok sorry about my english
I'll show you with gif animation
below is right situation

when i type keyboard button "ㅇ"
we need poll() "ㅇ" and applyTextInput so editor should render "ㅇ"
then i type keyboard button "ㅏ"
we need poll() "아" and applyTextinput so editor should render "아"
then i type keyboard button "ㄴ"
we need poll() "안" and applyTextinput so editor should render "안"
so we can get complete one letter "안"
but IE 11 / window7 dont show first letter so when we want to input "안녕"
cm dont render "안" until "녕" composition start
show below

this because
poll: function() {
      var cm = this.cm, input = this.textarea, prevInput = this.prevInput;
      // Since this is called a *lot*, try to bail out as cheaply as
      // possible when it is clear that nothing happened. hasSelection
      // will be the case when there is a lot of text in the textarea,
      // in which case reading its value would be expensive.
      if (this.contextMenuPending || !cm.state.focused ||
          (hasSelection(input) && !prevInput) ||
          isReadOnly(cm) || cm.options.disableInput || cm.state.keySeq)
        return false;

(hasSelection(input) && !prevInput)
that condition cancel polling "ㅇ" -> "아" -> "안"
so we can't see "ㅇ" -> "아" -> "안"
i hope that this comment can help

That makes sense. Merged as 76582ee


flora: flora service connect failed on getting nlp result

Version: 7.29.0
Platform: all
Subsystem: component/flora

No detailed descriptions and reproduce steps. Closing.


gdal version mismatch?

Looks like the gdal swig binary is out of sync with newer python bindings?  I'm running this inside the non-gpu docker image.  I gather the GNM bits are relatively new, so it makes sense that they'd get hit.
root@f059367028e3:/DeepOSM# python ./bin/create_training_data.py
Traceback (most recent call last):
  File "./bin/create_training_data.py", line 6, in <module>
    from src.training_data import download_and_serialize
  File "/DeepOSM/src/training_data.py", line 10, in <module>
    from osgeo import gdal
  File "/usr/local/lib/python2.7/dist-packages/osgeo/gdal.py", line 86, in <module>
    from gdalconst import *
  File "/usr/local/lib/python2.7/dist-packages/osgeo/gdalconst.py", line 148, in <module>
    OF_GNM = _gdalconst.OF_GNM
AttributeError: 'module' object has no attribute 'OF_GNM'

Also, I've tried going straight to https://hub.docker.com/r/homme/gdal/ and I can't reproduce there.
I'm wondering if one of the apt-get installs brought along an out-of-date gdal binary?
Here are a few more files:
root@f059367028e3:/usr/local/lib/python2.7/dist-packages# ls -lha /usr/local/lib/libgdal*
-rw-r--r-- 1 root root 288M Oct 28 11:24 /usr/local/lib/libgdal.a
-rwxr-xr-x 1 root root 1.6K Oct 28 11:24 /usr/local/lib/libgdal.la
lrwxrwxrwx 1 root root   17 Oct 28 11:24 /usr/local/lib/libgdal.so -> libgdal.so.20.1.0
lrwxrwxrwx 1 root root   17 Oct 28 11:24 /usr/local/lib/libgdal.so.20 -> libgdal.so.20.1.0
-rwxr-xr-x 1 root root 116M Oct 28 11:24 /usr/local/lib/libgdal.so.20.1.0
root@f059367028e3:/usr/local/lib/python2.7/dist-packages# ls -lha *gdal*
-rw-r--r-- 1 root staff 128 Oct 28 10:15 gdal.py
-rw-r--r-- 1 root staff 244 Oct 28 11:25 gdal.pyc
-rw-r--r-- 1 root staff 143 Oct 28 10:15 gdalconst.py
-rw-r--r-- 1 root staff 274 Oct 28 11:25 gdalconst.pyc
-rw-r--r-- 1 root staff 147 Oct 28 10:15 gdalnumeric.py
-rw-r--r-- 1 root staff 279 Oct 28 11:25 gdalnumeric.pyc

Thanks for opening the issue, I get the same thing on my mac.
Are you able to do a PR to fix this?
On Mon, Feb 13, 2017 at 1:35 PM, Jesse Montrose<EMAIL_ADDRESS>wrote:

Looks like the gdal swig binary is out of sync with newer python bindings?
I'm running this inside the non-gpu docker image. I gather the GNM bits are
relatively new, so it makes sense that they'd get hit.
root@f059367028e3:/DeepOSM# python ./bin/create_training_data.py
Traceback (most recent call last):
File "./bin/create_training_data.py", line 6, in
from src.training_data import download_and_serialize
File "/DeepOSM/src/training_data.py", line 10, in
from osgeo import gdal
File "/usr/local/lib/python2.7/dist-packages/osgeo/gdal.py", line 86, in
from gdalconst import *
File "/usr/local/lib/python2.7/dist-packages/osgeo/gdalconst.py", line 148, in
OF_GNM = _gdalconst.OF_GNM
AttributeError: 'module' object has no attribute 'OF_GNM'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/trailbehind/DeepOSM/issues/74, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbzf9vWKHguYxl-XUzWPWm6r_ygLzZTks5rcMyigaJpZM4L_wHu
.

I don't know how to fix it yet, still finding my way around.
Any guidance?  I'm happy to poke around some more!

Fixed just now with dc89093

That fixed it, thanks! 👍


Faster behat tests

See https://github.com/sulu-io/sulu/pull/971

Build is erroring :/

I know .. firefox isn't playing well with URL based HTTP BASIC authentication

Ok, and what do we do about that now? :-)

Dunno, we can fix the behavior with a custom FF profile I think .. or we can use Chrome.


Bump golang.org/x/crypto

The addon isn't affected by CVE-2021-43565, but this bumps the
dependency anyway so that the project no longer gets flagged.
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

/retest
/lgtm

This is ready to merge, but an Owner has to merge it apparently.

/lgtm


'stream-deck@latest' is not in the npm registry.

$ npx stream-deck create
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/stream-deck - Not found
npm ERR! 404
npm ERR! 404 'stream-deck@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR!


Infinite loop

I have been testing v0.8.3 and I only receive the status and the rssi but not the message.
I have compiled the gateway with debug_info and this is what I get:
[I][EnigmaIOTGatewayMQTT.ino:174] processRxData(): 7725 Heap: 237524 Published MQTT from A0:20:A6:08:CD:88: {"per":0.000000e+00,"lostmessages":0,"totalmessages":1,"packetshour":11320.75}
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 7764 Heap: 237772 Publish MQTT. Esp-New/A0:20:A6:08:CD:88/data : [{"channel":38,"type":103,"name":"temperature","value":27.4},{"channel":38,"type":104,"name":"humidity","value":69},{"channel":38,"type":142,"name":"switch","value":0},{"channel":38,"type":115,"name":"pressure","value":0.9},{"channel":38,"type":142,"name":"switch","value":0},{"channel":39,"type":2,"name":"analog_input","value":42}]
[I][EnigmaIOTGateway.cpp:836] manageMessage(): 7780 Heap: 238048 Data OK
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 7819 Heap: 238412 Publish MQTT. Esp-New/A0:20:A6:08:CD:88/data : [{"channel":38,"type":103,"name":"temperature","value":27.4},{"channel":38,"type":104,"name":"humidity","value":69},{"channel":38,"type":142,"name":"switch","value":0},{"channel":38,"type":115,"name":"pressure","value":0.9},{"channel":38,"type":142,"name":"switch","value":0},{"channel":39,"type":2,"name":"analog_input","value":42}]
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 7863 Heap: 240256 Publish MQTT. Esp-New/A0:20:A6:08:CD:88/data : [{"channel":38,"type":103,"name":"temperature","value":27.4},{"channel":38,"type":104,"name":"humidity","value":69},{"channel":38,"type":142,"name":"switch","value":0},{"channel":38,"type":115,"name":"pressure","value":0.9},{"channel":38,"type":142,"name":"switch","value":0},{"channel":39,"type":2,"name":"analog_input","value":42}]
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 7902 Heap: 240256 Publish MQTT. Esp-New/A0:20:A6:08:CD:88/data : [{"channel":38,"type":103,"name":"temperature","value":27.4},{"channel":38,"type":104,"name":"humidity","value":69},{"channel":38,"type":142,"name":"switch","value":0},{"channel":38,"type":115,"name":"pressure","value":0.9},{"channel":38,"type":142,"name":"switch","value":0},{"channel":39,"type":2,"name":"analog_input","value":42}]
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 7940 Heap: 240256 Publish MQTT. Esp-New/A0:20:A6:08:CD:88/data : [{"channel":38,"type":103,"name":"temperature","value":27.4},{"channel":38,"type":104,"name":"humidity","value":69},{"channel":38,"type":142,"name":"switch","value":0},{"channel":38,"type":115,"name":"pressure","value":0.9},{"channel":38,"type":142,"name":"switch","value":0},{"channel":39,"type":2,"name":"analog_input","value":42}]
...infinite
I have tried with Wemos D1 mini
and with LOLIN32 (without mqtt_secure)
both with the same result.

I have recompiled version 0.8.3 with dEBUG_LEVEL DBG
In Esp32, this is the output:
[D][EnigmaIOTGateway.cpp:703] addInputMsgQueue(): 91226 Heap: 237536 Message 0x01 added from B4:E6:2D:44:A0:E9. Size: 1
[D][EnigmaIOTGateway.h:186] front(): 91237 Heap: 237536 Read element. ReadIdx: 0. WriteIdx: 1. Size: 1
[D][EnigmaIOTGateway.cpp:727] getInputMsgQueue(): 91246 Heap: 239244 EnigmaIOT message got from queue. Size: 1
[D][EnigmaIOTGateway.h:168] pop(): 91256 Heap: 239244 Remove element. Buffer was not empty
[D][EnigmaIOTGateway.h:169] pop(): 91264 Heap: 239244 Before -- > ReadIdx: 0. WriteIdx: 1. Size: 1
[D][EnigmaIOTGateway.h:177] pop(): 91273 Heap: 237536 After -- > ReadIdx: 1. WriteIdx: 1. Size: 0
[D][EnigmaIOTGateway.cpp:751] popInputMsgQueue(): 91281 Heap: 239244 EnigmaIOT message pop. Size 0
[D][EnigmaIOTGateway.cpp:835] handle(): 91290 Heap: 239244 EnigmaIOT input message from queue. MsgType: 0x01
[I][EnigmaIOTGateway.cpp:845] manageMessage(): 91300 Heap: 239244 Reveived message. Origin MAC: B4:E6:2D:44:A0:E9
[I][EnigmaIOTGateway.cpp:919] manageMessage(): 91310 Heap: 239244  <------- ENCRYPTED DATA
[D][GwOutput_mqtt.cpp:458] addMQTTqueue(): 91318 Heap: 238364 1 MQTT messages queued Len:175 Esp-New/B4:E6:2D:44:A0:E9/data [{"channel":8,"type":103,"name":"temperature","value":85},{"channel":9,"type":103,"name":"temperature","value":93.1},{"channel":10,"type":103,"name":"temperature","value":85}]
[I][GwOutput_mqtt.cpp:506] outputDataSend(): 91344 Heap: 238364 MQTT queued Esp-New/B4:E6:2D:44:A0:E9/data. Length 175
[I][EnigmaIOTGatewayMQTT.ino:163] processRxData(): 91354 Heap: 238444 Published data message from B4:E6:2D:44:A0:E9, length 175: [{"channel":8,"type":103,"name":"temperature","value":85},{"channel":9,"type":103,"name":"temperature","value":93.1},{"channel":10,"type":103,"name":"temperature","value":85}]
[D][GwOutput_mqtt.cpp:458] addMQTTqueue(): 91381 Heap: 237928 2 MQTT messages queued Len:75 Esp-New/B4:E6:2D:44:A0:E9/status {"per":0.000000e+00,"lostmessages":0,"totalmessages":1,"packetshour":55.12}
[I][GwOutput_mqtt.cpp:506] outputDataSend(): 91398 Heap: 237928 MQTT queued Esp-New/B4:E6:2D:44:A0:E9/status. Length 75
[I][EnigmaIOTGatewayMQTT.ino:175] processRxData(): 91409 Heap: 238004 Published MQTT from B4:E6:2D:44:A0:E9: {"per":0.000000e+00,"lostmessages":0,"totalmessages":1,"packetshour":55.12}
[I][EnigmaIOTGateway.cpp:932] manageMessage(): 91425 Heap: 238528 Data OK
[D][GwOutput_mqtt.cpp:465] getMQTTqueue(): 91432 Heap: 238528 MQTT message got from queue
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 91439 Heap: 238528 Publish MQTT. Esp-New/B4:E6:2D:44:A0:E9/data : [{"channel":8,"type":103,"name":"temperature","value":85},{"channel":9,"type":103,"name":"temperature","value":93.1},{"channel":10,"type":103,"name":"temperature","value":85}]
[D][EnigmaIOTGateway.cpp:781] handle(): 91464 Heap: 238528 EnigmaIOTGatewayClass::flashrx
[D][GwOutput_mqtt.cpp:465] getMQTTqueue(): 91472 Heap: 238528 MQTT message got from queue
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 91480 Heap: 238528 Publish MQTT. Esp-New/B4:E6:2D:44:A0:E9/data : [{"channel":8,"type":103,"name":"temperature","value":85},{"channel":9,"type":103,"name":"temperature","value":93.1},{"channel":10,"type":103,"name":"temperature","value":85}]
[D][GwOutput_mqtt.cpp:465] getMQTTqueue(): 91505 Heap: 238528 MQTT message got from queue
In mosquitto I receive nothing, only this:
pi@RaspiZero:~ $ mosquitto_sub -t Esp-New/#
1
1
{"reason":4}
{"rssi":-67,"channel":6}
1
{"reason":4}
{"rssi":-76,"channel":6}

Hello, looking at log data I cannot conclude any error. Indeed there is no warning or error message.
Output from mosquitto_sub command does not correspond to that log because {reason:4} indicates node key revocation. I recommend to add -v option to see mqtt topic.

This is the output of LOLIN32 with enigmaiot0.8.3 Gateway:
[I][GwOutput_mqtt.cpp:231] reconnect(): 4376 Heap: 242224 Attempting MQTT connection...
[D][GwOutput_mqtt.cpp:237] reconnect(): 4384 Heap: 242224 Clock set.
[D][GwOutput_mqtt.cpp:239] reconnect(): 4390 Heap: 242224 Connect to MQTT server: user Esp32, pass , topic Esp-New/gateway/status
[W][GwOutput_mqtt.cpp:242] reconnect(): 4489 Heap: 239812 MQTT connected
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 4489 Heap: 239812 Publish MQTT. Esp-New/gateway/status : 1
[D][EnigmaIOTGateway.h:142] push(): 94157 Heap: 237916 Add element. Buffer was not full
[D][EnigmaIOTGateway.h:143] push(): 94157 Heap: 237916 Before -- > ReadIdx: 0. WriteIdx: 0. Size: 0
[D][EnigmaIOTGateway.h:158] push(): 94163 Heap: 237916 After -- > ReadIdx: 0. WriteIdx: 1. Size: 1
[D][EnigmaIOTGateway.cpp:703] addInputMsgQueue(): 94172 Heap: 237916 Message 0xFF added from 2C:F4:32:4A:08:00. Size: 1
[D][EnigmaIOTGateway.h:186] front(): 94182 Heap: 237916 Read element. ReadIdx: 0. WriteIdx: 1. Size: 1
[D][EnigmaIOTGateway.cpp:727] getInputMsgQueue(): 94191 Heap: 239624 EnigmaIOT message got from queue. Size: 1
[D][EnigmaIOTGateway.h:168] pop(): 94201 Heap: 239624 Remove element. Buffer was not empty
[D][EnigmaIOTGateway.h:169] pop(): 94209 Heap: 239624 Before -- > ReadIdx: 0. WriteIdx: 1. Size: 1
[D][EnigmaIOTGateway.h:177] pop(): 94218 Heap: 239624 After -- > ReadIdx: 1. WriteIdx: 1. Size: 0
[D][EnigmaIOTGateway.cpp:751] popInputMsgQueue(): 94227 Heap: 239624 EnigmaIOT message pop. Size 0
[D][EnigmaIOTGateway.cpp:835] handle(): 94236 Heap: 239624 EnigmaIOT input message from queue. MsgType: 0xFF
[I][EnigmaIOTGateway.cpp:845] manageMessage(): 94245 Heap: 239624 Reveived message. Origin MAC: 2C:F4:32:4A:08:00
[I][EnigmaIOTGateway.cpp:863] manageMessage(): 94255 Heap: 239624  <------- CLIENT HELLO
[D][EnigmaIOTGateway.cpp:1374] processClientHello(): 94323 Heap: 239624 Node key: 78 B8 BB 26 73 6E EA 13 B1 D6 9F 74 62 E9 63 5D B7 43 9F 31 2F E9 33 01 A1 31 C5 B6 A8 6E 5B 4E
[I][EnigmaIOTGateway.cpp:1565] serverHello(): 94328 Heap: 239624  -------> SERVER_HELLO
[D][espnow_hal.cpp:103] send(): ESP-NOW message to 2C:F4:32:4A:08:00
[D][espnow_hal.cpp:114] send(): Peer added on channel 6. Result 0
[D][espnow_hal.cpp:125] send(): esp now send result = 0
[D][espnow_hal.cpp:128] send(): Peer deleted. Result 0
[I][EnigmaIOTGateway.cpp:1567] serverHello(): 94358 Heap: 239624 Server Hello message sent to 2C:F4:32:4A:08:00
[I][EnigmaIOTGateway.cpp:868] manageMessage(): 94367 Heap: 239624 Server Hello sent
[D][GwOutput_mqtt.cpp:458] addMQTTqueue(): 94375 Heap: 239452 1 MQTT messages queued Len:0 Esp-New/2C:F4:32:4A:08:00/hello
[I][GwOutput_mqtt.cpp:601] newNodeSend(): 94386 Heap: 239452 Published MQTT Esp-New/2C:F4:32:4A:08:00/hello
[D][EnigmaIOTGatewayMQTT.ino:207] newNodeConnected(): 94395 Heap: 239528 New node 2C:F4:32:4A:08:00 message sent
MAC Address: 2C:F4:32:4A:08:00
Last counter: 0
Key valid from: 34 ms ago
Key: Valid
Status: Registered. Wait for messages
[D][GwOutput_mqtt.cpp:465] getMQTTqueue(): 94417 Heap: 239528 MQTT message got from queue
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 94424 Heap: 239528 Publish MQTT. Esp-New/2C:F4:32:4A:08:00/hello :
[D][GwOutput_mqtt.cpp:403] loop(): 94435 Heap: 237572 MQTT published. Esp-New/2C:F4:32:4A:08:00/hello
[D][GwOutput_mqtt.cpp:486] popMQTTqueue(): 94443 Heap: 238036 MQTT message pop. Size 0
[D][EnigmaIOTGateway.cpp:781] handle(): 94451 Heap: 238036 EnigmaIOTGatewayClass::flashrx
[D][EnigmaIOTGateway.h:142] push(): 95050 Heap: 237916 Add element. Buffer was not full
[D][EnigmaIOTGateway.h:143] push(): 95050 Heap: 237916 Before -- > ReadIdx: 1. WriteIdx: 1. Size: 0
[D][EnigmaIOTGateway.h:158] push(): 95056 Heap: 237916 After -- > ReadIdx: 1. WriteIdx: 2. Size: 1
[D][EnigmaIOTGateway.cpp:703] addInputMsgQueue(): 95065 Heap: 237916 Message 0x01 added from 2C:F4:32:4A:08:00. Size: 1
[D][EnigmaIOTGateway.h:186] front(): 95075 Heap: 237916 Read element. ReadIdx: 1. WriteIdx: 2. Size: 1
[D][EnigmaIOTGateway.cpp:727] getInputMsgQueue(): 95085 Heap: 239624 EnigmaIOT message got from queue. Size: 1
[D][EnigmaIOTGateway.h:168] pop(): 95094 Heap: 239624 Remove element. Buffer was not empty
[D][EnigmaIOTGateway.h:169] pop(): 95102 Heap: 239624 Before -- > ReadIdx: 1. WriteIdx: 2. Size: 1
[D][EnigmaIOTGateway.h:177] pop(): 95111 Heap: 239624 After -- > ReadIdx: 2. WriteIdx: 2. Size: 0
[D][EnigmaIOTGateway.cpp:751] popInputMsgQueue(): 95120 Heap: 239624 EnigmaIOT message pop. Size 0
[D][EnigmaIOTGateway.cpp:835] handle(): 95129 Heap: 239624 EnigmaIOT input message from queue. MsgType: 0x01
[I][EnigmaIOTGateway.cpp:845] manageMessage(): 95138 Heap: 239624 Reveived message. Origin MAC: 2C:F4:32:4A:08:00
[I][EnigmaIOTGateway.cpp:919] manageMessage(): 95148 Heap: 239624  <------- ENCRYPTED DATA
[D][GwOutput_mqtt.cpp:458] addMQTTqueue(): 95157 Heap: 238640 1 MQTT messages queued Len:280 Esp-New/2C:F4:32:4A:08:00/data [{"channel":0,"type":2,"name":"analog_in","value":3},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
[I][GwOutput_mqtt.cpp:506] outputDataSend(): 95191 Heap: 238640 MQTT queued Esp-New/2C:F4:32:4A:08:00/data. Length 280
[I][EnigmaIOTGatewayMQTT.ino:163] processRxData(): 95202 Heap: 238716 Published data message from 2C:F4:32:4A:08:00, length 280: [{"channel":0,"type":2,"name":"analog_in","value":3},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
[D][GwOutput_mqtt.cpp:458] addMQTTqueue(): 95238 Heap: 238192 2 MQTT messages queued Len:77 Esp-New/2C:F4:32:4A:08:00/status {"per":0.000000e+00,"lostmessages":0,"totalmessages":1,"packetshour":4609.48}
[I][GwOutput_mqtt.cpp:506] outputDataSend(): 95255 Heap: 238192 MQTT queued Esp-New/2C:F4:32:4A:08:00/status. Length 77
[I][EnigmaIOTGatewayMQTT.ino:175] processRxData(): 95266 Heap: 238272 Published MQTT from 2C:F4:32:4A:08:00: {"per":0.000000e+00,"lostmessages":0,"totalmessages":1,"packetshour":4609.48}
[I][EnigmaIOTGateway.cpp:932] manageMessage(): 95282 Heap: 237084 Data OK
[D][GwOutput_mqtt.cpp:465] getMQTTqueue(): 95289 Heap: 238796 MQTT message got from queue
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 95297 Heap: 238796 Publish MQTT. Esp-New/2C:F4:32:4A:08:00/data : [{"channel":0,"type":2,"name":"analog_in","value":3},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
[D][EnigmaIOTGateway.cpp:781] handle(): 95330 Heap: 238796 EnigmaIOTGatewayClass::flashrx
[D][GwOutput_mqtt.cpp:465] getMQTTqueue(): 95338 Heap: 238796 MQTT message got from queue
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 95346 Heap: 238796 Publish MQTT. Esp-New/2C:F4:32:4A:08:00/data : [{"channel":0,"type":2,"name":"analog_in","value":3},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
[D][GwOutput_mqtt.cpp:465] getMQTTqueue(): 95380 Heap: 238796 MQTT message got from queue
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 95388 Heap: 238796 Publish MQTT. Esp-New/2C:F4:32:4A:08:00/data : [{"channel":0,"type":2,"name":"analog_in","value":3},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
[D][GwOutput_mqtt.cpp:465] getMQTTqueue(): 95422 Heap: 238796 MQTT message got from queue
** more the same
[I][GwOutput_mqtt.cpp:411] publishMQTT(): 96975 Heap: 238796 Publish MQTT. Esp-New/2C:F4:32:4A:08:00/data : [{"channel":0,"type":2,"name":"analog_in","value":3},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
[D][GwOutput_mqtt.cpp:465] getMQTTqueue(): 97008 Heap: 238796 MQTT message got from queue
[I][GwOutput_mqtt.cpp:411] publishMQTT(Guru Meditation Error: Core  0 panic'ed (Interrupt wdt timeout on CPU0)
Core 0 register dump:
PC      : 0x4008b570  PS      : 0x00060034  A0      : 0x8008a6ef  A1      : 0x3ffaefd0
A2      : 0x3ffb81f0  A3      : 0x3ffb5e70  A4      : 0x00000001  A5      : 0x00000001
A6      : 0x00060023  A7      : 0x00000000  A8      : 0x3ffb5e70  A9      : 0x3ffb5e70
A10     : 0x00000002  A11     : 0x00000002  A12     : 0x00000001  A13     : 0x00000001
A14     : 0x00060023  A15     : 0x00000000  SAR     : 0x00000004  EXCCAUSE: 0x00000005
EXCVADDR: 0x00000000  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xfffffffd
Backtrace: 0x4008b570:0x3ffaefd0 0x4008a6ec:0x3ffaeff0 0x40088987:0x3ffaf010 0x400e8a84:0x3ffaf050 0x400d9e42:0x3ffaf0b0 0x400d9f3a:0x3ffaf0f0 0x400d9fad:0x3ffaf240 0x400dc4a5:0x3ffaf260 0x401488fd:0x3ffaf280 0x401172cf:0x3ffaf2a0 0x401171b0:0x3ffaf2d0 0x4010243d:0x3ffaf300 0x4010273b:0x3ffaf400 0x40157969:0x3ffaf420 0x4008f616:0x3ffaf470 0x40088b81:0x3ffaf4b0
Core 1 register dump:
PC      : 0x4008903a  PS      : 0x00060034  A0      : 0x80089799  A1      : 0x3ffb1cc0
A2      : 0x3ffbf434  A3      : 0xb33fffff  A4      : 0x00060023  A5      : 0x003fffff
A6      : 0x3ffbe7d8  A7      : 0x00000001  A8      : 0x0000cdcd  A9      : 0x0000abab
A10     : 0x0000cdcd  A11     : 0x3ffb0060  A12     : 0x8008a377  A13     : 0x3ffbe760
A14     : 0x00000008  A15     : 0x00000001  SAR     : 0x00000020  EXCCAUSE: 0x00000005
EXCVADDR: 0x00000000  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xfffffff8
Backtrace: 0x4008903a:0x3ffb1cc0 0x40089796:0x3ffb1cf0 0x4008b40c:0x3ffb1d10 0x4008b3c2:0x4000bff0
Rebooting...
ets Jun  8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:9720
ho 0 tail 12 room 4
load:0x40080400,len:6352
entry 0x400806b8
[D][GwOutput_mqtt.cpp:114] loadConfig(): 133 Heap: 299424 Opening /mqtt.json file
[D][GwOutput_mqtt.cpp:118] loadConfig(): 133 Heap: 299168 /mqtt.json opened. 83 bytes
[D][GwOutput_mqtt.cpp:124] loadConfig(): 138 Heap: 298496 JSON file parsed
This the Mosquitto_sub output:
pi@RaspiZero:~ $ mosquitto_sub -t Esp-New/# -v
Esp-New/gateway/status 1
Esp-New/gateway/status 0
Esp-New/gateway/status 1
Esp-New/gateway/status 0
Esp-New/gateway/status 1
Esp-New/2C:F4:32:4A:08:00/hello (null)
Esp-New/gateway/status 1
** Next reboot of Node
Esp-New/2C:F4:32:4A:08:00/bye {"reason":4}
Esp-New/2C:F4:32:4A:08:00/hello (null)
Esp-New/2C:F4:32:4A:08:00/result/rssi {"rssi":-16,"channel":6}
Esp-New/gateway/status 1
Esp-New/2C:F4:32:4A:08:00/bye {"reason":4}
Esp-New/2C:F4:32:4A:08:00/hello (null)
Esp-New/2C:F4:32:4A:08:00/result/rssi {"rssi":-34,"channel":6}

I would say that you are sending messages too quick. As Debug is activated Serial buffer is overflowed and that's why esp32 crashes before sending first data. Try to slow down node messages and reduce debug level.

Esp32 Gateway debug_level WARN:
*WM: Connecting as wifi client...
*WM: Try to connect with saved credentials
*WM: Connection result:
*WM: 3
*WM: IP Address:
*WM: <IP_ADDRESS>
[W][GwOutput_mqtt.cpp:242] reconnect(): 5362 Heap: 231112 MQTT connected
Node: 0
MAC Address: 2C:F4:32:4A:08:00
Last counter: 0
Key valid from: 1 ms ago
Key: Valid
Status: Registered. Wait for messages
dhcps: send_offer>>udp_sendto result 0
dhcps: send_nak>>udp_sendto result 0
pi@RaspiZero:~ $ mosquitto_sub -t Esp-New/# -v
Esp-New/gateway/status 1
Esp-New/gateway/status 0
Esp-New/gateway/status 1
Esp-New/2C:F4:32:4A:08:00/bye {"reason":4}
Esp-New/2C:F4:32:4A:08:00/hello (null)
Esp-New/2C:F4:32:4A:08:00/result/rssi {"rssi":-15,"channel":6}
Esp-New/2C:F4:32:4A:08:00/status {"per":0.000000e+00,"lostmessages":0,"totalmessages":1,"packetshour":348.84}
Esp-New/2C:F4:32:4A:08:00/status {"per":0.000000e+00,"lostmessages":0,"totalmessages":2,"packetshour":242.34}
Esp-New/2C:F4:32:4A:08:00/status {"per":0.000000e+00,"lostmessages":0,"totalmessages":3,"packetshour":178.89}
Esp-New/2C:F4:32:4A:08:00/status {"per":0.000000e+00,"lostmessages":0,"totalmessages":4,"packetshour":177.18}
Esp-New/2C:F4:32:4A:08:00/status {"per":0.000000e+00,"lostmessages":0,"totalmessages":5,"packetshour":127.78}
Node don't have reset pin connected, each time I push reset button I only get status message.
I think there is someting wrong with my libraries, but I don't know what. I use fresh arduino IDE .zip with portable folder inside and only libraries you link in github..
If you can upload  .bin firmware of Gateway I will try it.

I've just released a new version. Please test it. Share your code if still not working. Please use code blocks to improve readability https://guides.github.com/features/mastering-markdown/

This time I have used a linux live distribution on usb to install Arduino IDE from scratch.
I have installed in .zip:

enigma IOT 0.9.0
ESPAsyncWiFiManager
Arduino Crypto Library
PubSubClient
CayennLPP
ArduinoJSON 6

when I have compiled arduino it has asked me for a library espasyntcp.h I have used https://github.com/me-no-dev/ESPAsyncTCP
The code used is the example # EnigmaIOTGatewayMQTT # from the enigmaIOT library in esp8266 (wemos D1 mini),
I have only modified (Linux is case-sensitive):

Comms_hal.h
#if defined (ARDUINO) && ARDUINO> = 100
#include "arduino.h" -> "Arduino.h"
GwOutput_generic.h
#if defined (ARDUINO) && ARDUINO> = 100
#include "arduino.h" -> "Arduino.h"

-Debug level: Info
The node is also a wemos d1 mini with the example of the library without a bridge between D0 and RST, it only restarts when I press the reset button.
The serial output of the Gateway:
_W [9565] 28976 free (reconnect:242) MQTT connected
I [9565] 28976 free (publishMQTT:411) Publish MQTT. Esp-New/gateway/status : 1
I [33657] 28976 free (manageMessage:851) Reveived message. Origin MAC: B4:E6:2D:45:7A:34
I [33658] 28976 free (manageMessage:869)  <------- CLIENT HELLO
I [34253] 28976 free (serverHello:1581)  -------> SERVER_HELLO
I [34254] 28760 free (serverHello:1583) Server Hello message sent to B4:E6:2D:45:7A:34
I [34256] 28760 free (manageMessage:874) Server Hello sent
I [34261] 28624 free (newNodeSend:601) Published MQTT Esp-New/B4:E6:2D:45:7A:34/hello
Node: 0
MAC Address: B4:E6:2D:45:7A:34
Last counter: 0
Key valid from: 12 ms ago
Key: Valid
Status: Registered. Wait for messages
I [34283] 28696 free (publishMQTT:411) Publish MQTT. Esp-New/B4:E6:2D:45:7A:34/hello :
I [34594] 28976 free (manageMessage:851) Reveived message. Origin MAC: B4:E6:2D:45:7A:34
I [34594] 28976 free (manageMessage:925)  <------- ENCRYPTED DATA
I [34597] 27944 free (processRxData:140) CayenneLPP message
I [34603] 27520 free (outputDataSend:506) MQTT queued Esp-New/B4:E6:2D:45:7A:34/data. Length 283
I [34610] 27592 free (processRxData:175) Published data message from B4:E6:2D:45:7A:34, length 283: [{"channel":0,"type":2,"name":"analog_in","value":3.02},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}], Encoding 0x81
I [34646] 27144 free (outputDataSend:506) MQTT queued Esp-New/B4:E6:2D:45:7A:34/status. Length 78
I [34654] 27216 free (processRxData:187) Published MQTT from B4:E6:2D:45:7A:34: {"per":0.000000e+00,"lostmessages":0,"totalmessages":1,"packetshour":10746.27}
I [34668] 28248 free (manageMessage:938) Data OK
I [34673] 28248 free (publishMQTT:411) Publish MQTT. Esp-New/B4:E6:2D:45:7A:34/data : [{"channel":0,"type":2,"name":"analog_in","value":3.02},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
I [34705] 28248 free (publishMQTT:411) Publish MQTT. Esp-New/B4:E6:2D:45:7A:34/data : [{"channel":0,"type":2,"name":"analog_in","value":3.02},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
I [34736] 28248 free (publishMQTT:411) Publish MQTT. Esp-New/B4:E6:2D:45:7A:34/data : [{"channel":0,"type":2,"name":"analog_in","value":3.02},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]__
loop, I only press node RST button one time
node rst button
I [934273] 25672 free (manageMessage:851) Reveived message. Origin MAC: B4:E6:2D:45:7A:34
I [934281] 25672 free (manageMessage:925)  <------- ENCRYPTED DATA
I [934287] 24640 free (processRxData:140) CayenneLPP message
I [934293] 24216 free (outputDataSend:506) MQTT queued Esp-New/B4:E6:2D:45:7A:34/data. Length 283
I [934301] 24288 free (processRxData:175) Published data message from B4:E6:2D:45:7A:34, length 283: [{"channel":0,"type":2,"name":"analog_in","value":3.02},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}], Encoding 0x81
I [934336] 24072 free (outputDataSend:506) MQTT queued Esp-New/B4:E6:2D:45:7A:34/status. Length 76
I [934344] 24144 free (processRxData:187) Published MQTT from B4:E6:2D:45:7A:34: {"per":0.000000e+00,"lostmessages":0,"totalmessages":6,"packetshour":475.82}
I [934358] 25176 free (manageMessage:938) Data OK
I [934364] 25176 free (publishMQTT:411) Publish MQTT. Esp-New/B4:E6:2D:45:7A:34/status : {"per":0.000000e+00,"lostmessages":0,"totalmessages":4,"packetshour":640.57}
I [934378] 24648 free (publishMQTT:411) Publish MQTT. Esp-New/B4:E6:2D:45:7A:34/data : [{"channel":0,"type":2,"name":"analog_in","value":3.02},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
I [934411] 25320 free (publishMQTT:411) Publish MQTT. Esp-New/B4:E6:2D:45:7A:34/data : [{"channel":0,"type":2,"name":"analog_in","value":3.02},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
I [934441] 25320 free (publishMQTT:411) Publish MQTT. Esp-New/B4:E6:2D:45:7A:34/data : [{"channel":0,"type":2,"name":"analog_in","value":3.02},{"channel":1,"type":103,"name":"temperature","value":20.3},{"channel":2,"type":0,"name":"digital_in","value":123},{"channel":3,"type":115,"name":"pressure","value":1007.2},{"channel":4,"type":117,"name":"current","value":2.43}]
mosquitto_sub -t Esp-Now / # -v:
Esp-New/gateway/status 1
node rst button
Esp-New/B4:E6:2D:45:7A:34/hello (null)
node rst button
_Esp-New/B4:E6:2D:45:7A:34/result/rssi {"rssi":-28,"channel":6}
node rst button
Esp-New/B4:E6:2D:45:7A:34/status {"per":0.000000e+00,"lostmessages":0,"totalmessages":1,"packetshour":233.24}
node rst button
Esp-New/B4:E6:2D:45:7A:34/status {"per":0.000000e+00,"lostmessages":0,"totalmessages":2,"packetshour":415.87}
When I press the reset button of the node I only receive the status message in mqtt, never the data message.

Well today I have tried node_msgpack and it works fine !!
Data received, and there is no infinite loop on the gateway output.
I am using the gateway that yesterday failed.

Still looks strange. I understand that you are using basic node example, aren't you?

@dgcasana  If you have more info feel free to share it here and reopen the issue

yes, I use enigmaiot_node example, without changes.


swiper.esm.js contains erroneous * characters

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 4.0.6.

Platform/Target and Browser Versions: macOS.

What you did
Trying to import this file throws Unexpected token errors
Expected Behavior
File imports without errors
Actual Behavior
In many places where multiply calculations are done in this file, there is a double ** instead of a single *

Which line causes this?

There are a few: 719, 722, 4360, 4411, 4414, 4513, 4516, 4520, 4523

You mean ** which is just Math.pow()? Did you actually transpile the file to ES5 using Babel or anything else?
The file is written in ES6.
Also see https://stackoverflow.com/questions/33284569/is-the-double-asterisk-a-valid-javascript-operator

Ah, got you. Yes I'm transpiling with babel, looks like this is ES7, so maybe I need some extra stuff in my .babelrc

Probably the 2017 preset if available. https://babeljs.io/docs/plugins/preset-es2017/

Or better the env preset.

http://idangero.us/swiper/get-started/

I could solve it by upgrading UglifyJS to 3


Not able to build on ros2 foxy

Problem Description
I tried building this package on ros2 foxy (on Ubuntu 20.04), but was not able to due to the following issue
I tried to install gz-cmake but was not able to find where it would be distributed.
@ahcorde would you be able to provide any hints?
$ colcon build
Starting >>> gz-msgs9
Starting >>> sdformat13
Starting >>> ros_gz_interfaces
Starting >>> px4_msgs
Starting >>> vehicle_gateway
--- stderr: sdformat13
CMake Error at CMakeLists.txt:21 (find_package):
  By not providing "Findgz-cmake3.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "gz-cmake3", but CMake did not find one.

  Could not find a package configuration file provided by "gz-cmake3" with
  any of the following names:

    gz-cmake3Config.cmake
    gz-cmake3-config.cmake

  Add the installation prefix of "gz-cmake3" to CMAKE_PREFIX_PATH or set
  "gz-cmake3_DIR" to a directory containing one of the above files.  If
  "gz-cmake3" provides a separate development package or SDK, be sure it has
  been installed.

---
Failed   <<< sdformat13 [0.46s, exited with code 1]
Aborted  <<< gz-msgs9 [0.49s]
Aborted  <<< qgroundcontrol [0.61s]
Aborted  <<< vehicle_gateway [0.66s]
Aborted  <<< ros_gz_interfaces [2.47s]
Aborted  <<< px4_msgs [2.90s]

Summary: 0 packages finished [3.15s]
  1 package failed: sdformat13
  5 packages aborted: gz-msgs9 px4_msgs qgroundcontrol ros_gz_interfaces vehicle_gateway
  3 packages had stderr output: gz-msgs9 qgroundcontrol sdformat13
  11 packages not processed

@codebot Thanks for the pointers
I will try with ROS Humble in that case.


OCM-5310 | feat: changed default platform type to aws-classic & aws-hosted-cp

JIRA
Changing default platform type  to aws-classic & aws-hosted-cp from  aws & hostedcluster

/lgtm

/lgtm


Make triggers reliable

Login prompt detection was unreliable, which was making the nextgen
CI flakey. Shake out those errors. Fixes #223.

Andy, was your problem that this fix hadn't made it to the v0.2-devel branch?


how to test called times?

per title, is there any way to test a method called times, like xx.toHaveBeenCalledOnce/twice, etc.
Thanks.

expect(spy.calls).to.have.lengthOf(3)?

it works for me , thank u.


Multiple Transition groups with same same items

when using multiple transition groups with the same items in each one the animation or addition / remove always get applied to the last transition group on the page

Could you provide a peace of code to reproduce that?
I’m a bit confused by what you mean by “same items”.

I created a minimal example to try and reproduce it... and I wasn't able to... but oddly enough I can't reproduce it in my codebase now either
https://stackblitz.com/edit/solidjs-templates-hhmuax?file=src%2FApp.tsx
originally, when clicking something in "top" it would show up in "bottom" and not leave "top".. but yeah I can't reproduce it.
sorry about that


Add support for CompressedImageData

This PR

Adds loader.newCompressedData equivalent to love.image.newCompressedData
Adds support for CompressedImageData in loader.newImage
Fixes #17

Note: in order to support both CompressedImageData and ImageData a check with love.image.isCompressed is needed.

Very good!


Use vector.reserve() instead of resize()

Based on the comments it seems like the intention was to call reserve(). While resize to 0 does not decrease capacity() (and therefore no memory is de-allocated), the constructor and destructor for each element is still called. Since the struct also contains a vector the overhead of constructing and destructing is compounded.

After looking at the commit history, it seems like the comment is very poorly phrased. It would be more clear if the comment stated something along the lines of "force a page fault now to avoid it during runtime"


Nest Cameras via Nest Integration no longer stream via Hass

I am on Version: 1.9.6. Go2rtc installed as add-on on HA supervised.
Problem occurred after updating Home Assistant to 2024.11
All nest cameras (i.e., Nest Doorbell and Outdoor Nest Cam) still streams fine via Nest integration, just not from go2rtc. They worked well prior to 2024.11.
Could this be related to changes in 2024.11 relating to camera streams?
https://www.home-assistant.io/blog/2024/11/06/release-202411/
This is my first post. Feel free to let me know if I missed relevant details that would help in troubleshooting/etc.

Source: nest can be used as an alternative.

Source: nest can be used as an alternative.

Thanks. I managed to get it to work with https://github.com/AlexxIT/go2rtc/issues/1440#issuecomment-2462766842.
I had to dig up the required secret keys and tokens from /config/.storage/core.config_entries.
One thing I learned from my testing: I tried removing Nest integration and to reconfigure it again with 2024.11. It simply wouldn't want to be configured and just ends with 'error'.
When I rolled-back to 2024.10, I was able to get Nest integration to work again. So it is more than likely the cause for the problems seen with streaming Hass. But as mentioned before, I am able to get it to work with https://github.com/AlexxIT/go2rtc/issues/1440#issuecomment-2462766842

Hi @edward3600
How did you add in the keys? I got them out of core.config_entries, but it's giving me error 400 or 404 depends (there was a weird 1// on 1 key)
Did you have to do anything else other than add them in to the g2r config ?

Hi @edward3600
How did you add in the keys? I got them out of core.config_entries, but it's giving me error 400 or 404 depends (there was a weird 1// on 1 key)
Did you have to do anything else other than add them in to the g2r config ?

Hi @peterguy04, yes I recall the weird 1// too and I just included it in the go2rtc config. I too struggled to get it to work initially and I also had to refer to the https://console.developers.google.com/apis/credentials and https://console.nest.google.com/device-access/ to double check some values.

@edward3600
Thanks for your reply, worked this time. not sure why it didn't last time.

I am looking for a fix for this too... I should have all the right values for the nest config in go2rtc... did you have to do anything special like quoting the tokens, or for characters like the // did you have to escape them?

I am looking for a fix for this too... I should have all the right values for the nest config in go2rtc... did you have to do anything special like quoting the tokens, or for characters like the // did you have to escape them?

No, nothing special, but let go2rtc create the link for you rather than doing them manually
Add the values in the add tab of go2rtc under the nest option
Device ID & Secret  -https://console.developers.google.com/apis/credentials
Project ID - https://console.nest.google.com/device-access/
Refresh token - /config/.storage/core.config_entries (search this file for "nest"  and get the token.
I think refresh token has a weird 1// before it,dont remove that.
Then click login and wait a few seconds, it will create a list of links, for each camera.  Copy and paste these into config as normal

@peterguy04 @eric10k93 What did you guys use for device id? Is this the HA entity id or something from Nest/Google directly? That's the one item I haven't been able to find in my config files or in either development console

@NodeJSmith
I believe you can get the device ID from the Google home app  from Camera > settings > device information
But tbh manually creating the URL never worked for me, using the nest option in the go2rtc webui populated the links for me and they worked great (didn't need device ID)


Lombok Installer Is Not Finding my STS 3.9.5 / Eclipse Photon Installation

I am running the lombok jar file, but it doesn't find my new STS installation, justr the old one taht already has lombok in it.

Can you tell us that the full path to your installation directory is, what platform you use, and the name of both the executable and the ini file,