Cutter produces incorrect very low resolution result from 2d mercator map

I created a 2d mercator map of San Francisco using the tutorial data.  I used cutter and manually created the polygon by outlining the high resolution area of north east SF.  I specified a region level of 18 and left the other settings at their default values.  When I register this portable map in the GEE server and then view it everything looks correct.  See image 1-ResultOfSfCut.png.
I then created a 2d mercator map of the Orlando theme park area using imagery from the USGS Earth Explorer site.  I used cutter and manually created the polygon by outlining a rectangular area that included Disney's Magic Kingdom and Epcot.  I specified a region level of 18 and left the other settings at their default values.  See image 2-CreatingOrlandoCut.png.  When I register this portable map in the GEE server and then view it the polygon contains very low resolution imagery.  See image 3-ResultIsLowRes.png.

One difference that might be worth noting is the Orlando imagery contains a mosaic.  If you look at image 2-CreatingOrlandoCut.png, the lighter green area outside of the polygon is from a single imagery resource created as a mosaic from nine images.

@tst-blaird Just a guess, can you check your "Advanced Settings" and make sure the polygon level goes up to 18 as well? Also, try specify a zoom level for world also, like 8 or 10.

@tst-ccamp I checked the advanced settings and the polygon level defaulted to 18.  I generated a new cutfile after expanding the advanced settings section and the result was the same.
I then specified a world level of 8 and generated a new cutfile.  The polygon was still low resolution but it appeared the tiles outside the polygon region were one level better resolution.  There were four squares in the world region for every one square in the polygon region.  Screenshot:


Use model name or table name for validator caching

This simple change allows one AjvValidator instance to be shared across multiple models.
See #549 for further discussions.

Coverage remained the same at 95.814% when pulling 76c76c1b51ec97a3fbd4e8dc6975893df3629dab on lehni:fix/shared-validator into 8f9dba02c4b8168f6255f72a99428dbb2f1a0525 on Vincit:master.

Looks good to me. Thanks!


Don't use port 5000 as an option

OS X Yosemite uses port 5000 for AirPlay streaming.
Running Rails on port 5000 will add noise to the backtrace such as:
HTTP parse error, malformed request ():
ENV:
{"rack.version"=>[1, 1], "rack.errors"=>#<IO:<STDERR>>,
"rack.multithread"=>true, "rack.multiprocess"=>false,
"rack.run_once"=>false, "SCRIPT_NAME"=>"", "CONTENT_TYPE"=>"text/plain",
"QUERY_STRING"=>"txtAirPlay&txtRAOP", "SERVER_PROTOCOL"=>"HTTP/1.1",
"SERVER_SOFTWARE"=>"2.11.2", "GATEWAY_INTERFACE"=>"CGI/1.2",
"REQUEST_METHOD"=>"GET", "REQUEST_PATH"=>"/info",
"REQUEST_URI"=>"/info?txtAirPlay&txtRAOP"}

http://stackoverflow.com/questions/31194909/http-parse-errors-coming-from-airplay

This might not be necessary after https://github.com/thoughtbot/suspenders/pull/611

This seems like a good idea in the mean time.

This seems like a good idea in the mean time.

Indeed. Thank you!


the task is multi-choice or free-response question? And how to evaluate on the val split?

Hi,
Excellent work and thank you for making the resources publicly available.
While conducting evaluation experiments on your dataset, I encountered some issues.
In the published paper, you stated:

Evaluation. We use answer prediction accuracy as the metric and evaluate model performance on answering different types of questions. The answer vocabulary consists of 42
possible answers (22 objects, 12 counting choices, 6 location types, and yes/no) to different types of questions in the dataset. For training, we use one single model to handle all
questions without training separated models for each type. So the accuracy with random choice is 1/42≈2.4%. Additionally, all models are trained on our AVQA dataset using
the same features for a fair comparison.

It seems that the task is muti-choice questions, right?  Could you provide a list of the 42 possible answers?
Any additional details regarding how to perform the evaluation would be helpful. Thank you.
@DTaoo @ayameyao

It seems that you get to 42 answers when you read the json files of all three sets (train, val and test) and compute the set of all answers (field anser). That gets me to a set of size 42. I hope those are the 42 possible answers mentioned in the paper.


Unknown msg: xxxxxxxxxxxxxxxxx  in HA log since 0.4.1.

don't know if it is related to the new 0.4.1 version or not.
But since I updated from 0.4.0 to 0.4.1, I sometimes get Unknown msg in my logs:
Logger: /usr/local/lib/python3.10/site-packages/pyduofern/duofern.py
Source: /usr/local/lib/python3.10/site-packages/pyduofern/duofern.py:709
First occurred: 07:58:13 (7 occurrences)
Last logged: 09:26:41
Unknown msg: 0000407f0e6f12340181000000000000000000000000
Unknown msg: 6f123401810000000000000000000000000000000000
Unknown msg:<PHONE_NUMBER>00407f0e6f123401810000000000000000
Unknown msg: 00407f0e6f1234018100000000000000000000000000
Unknown msg:<PHONE_NUMBER>004100120000407f0e6f12340181000000
I only have 1 Rademacher RolloTron Standard DuoFern 1400 (HA entity: cover.407f0e) and 1 Rademacher Sonnensensor 9478. (not recognized by pyduofern)
Maybe the solar sensor internal battery is recharged again with rescent sunny days and the threshold is reached for sun on/off. Although the Unknown message also occurs on non sunny days or at night.
Is there a decryption tool somewhere to decode the duofern's msg's ?
Is above a bug, it looks like the message contains the same codes, but is shifted left or right.
Below a full debug log of duofern :
2023-02-23 11:21:12.405 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.406 INFO (SyncWorker_6) [custom_components.duofern.cover] updating state
2023-02-23 11:21:12.407 INFO (SyncWorker_6) [custom_components.duofern.cover] 407f0e state is now 100
2023-02-23 11:21:12.417 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.418 INFO (SyncWorker_4) [custom_components.duofern.cover] updating state
2023-02-23 11:21:12.418 INFO (SyncWorker_4) [custom_components.duofern.cover] 407f0e state is now 100
2023-02-23 11:21:12.419 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.420 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.420 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.420 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.421 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 4 msgs left in queue
2023-02-23 11:21:12.423 INFO (SyncWorker_1) [custom_components.duofern.cover] updating state
2023-02-23 11:21:12.424 INFO (SyncWorker_1) [custom_components.duofern.cover] 407f0e state is now 100
2023-02-23 11:21:12.447 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 4 msgs left in queue
2023-02-23 11:21:12.498 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 3 msgs left in queue
2023-02-23 11:21:12.526 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 2 msgs left in queue
2023-02-23 11:21:12.577 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 1 msgs left in queue
2023-02-23 11:21:12.606 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 0 msgs left in queue
2023-02-23 11:21:12.686 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] detected unknown device, ID=7f0e6f
2023-02-23 11:21:12.687 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: ff0f210000640000004100120000407f0e6f12340181
2023-02-23 11:21:12.958 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.959 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.960 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.960 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.960 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.961 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.965 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.965 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.967 INFO (SyncWorker_5) [custom_components.duofern.cover] updating state
2023-02-23 11:21:12.967 INFO (SyncWorker_5) [custom_components.duofern.cover] 407f0e state is now 100
2023-02-23 11:21:12.969 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.969 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.969 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.970 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.970 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:12.971 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 0 msgs left in queue
2023-02-23 11:21:12.977 INFO (SyncWorker_2) [custom_components.duofern.cover] updating state
2023-02-23 11:21:12.977 INFO (SyncWorker_2) [custom_components.duofern.cover] 407f0e state is now 100
2023-02-23 11:21:12.990 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 0 msgs left in queue
2023-02-23 11:21:13.198 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.200 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.201 INFO (SyncWorker_0) [custom_components.duofern.cover] updating state
2023-02-23 11:21:13.201 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-02-23 11:21:13.203 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.205 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.205 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.205 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.206 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.206 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.206 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.206 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.207 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.207 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.207 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.208 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 0 msgs left in queue
2023-02-23 11:21:13.208 INFO (SyncWorker_3) [custom_components.duofern.cover] updating state
2023-02-23 11:21:13.209 INFO (SyncWorker_3) [custom_components.duofern.cover] 407f0e state is now 100
2023-02-23 11:21:13.230 INFO (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 0 msgs left in queue
2023-02-23 11:21:13.422 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.423 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.424 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.424 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
2023-02-23 11:21:13.425 INFO (Thread-3) [custom_components.duofern] scheduling update for 407f0e
If I only filter on the unkown message:
Search "Unknown msg" (60 hits in 1 file of 1 searched)
new 63 (60 hits)
Line    22217: 	Line    23990: 2023-02-23 11:21:12.687 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: ff0f210000640000004100120000407f0e6f12340181
Line    25803: 	Line    27588: 2023-02-23 11:24:42.552 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>4100120000407f0e6f1234018100000000
Line   205536: 	Line   208587: 2023-02-23 13:53:45.676 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>407f0e6f12340181000000000000000000
Line   212012: 	Line   215098: 2023-02-23 13:59:30.420 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>120000407f0e6f12340181000000000000
Line   250777: 	Line   254056: 2023-02-23 14:30:20.864 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>00407f0e6f123401810000000000000000
Line   288354: 	Line   291763: 2023-02-23 14:55:57.766 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 7f0e6f12340181000000000000000000000000000000
Line   312402: 	Line   315905: 2023-02-23 15:15:56.542 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 7f0e6f12340181000000000000000000000000000000
Line   380013: 	Line   383753: 2023-02-23 16:08:29.812 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>00407f0e6f123401810000000000000000
Line   396353: 	Line   400168: 2023-02-23 16:20:12.255 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 6f123401810000000000000000000000000000000000
Line   400290: 	Line   404132: 2023-02-23 16:23:28.351 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>00407f0e6f123401810000000000000000
Line   472959: 	Line   477140: 2023-02-23 17:17:12.224 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 00407f0e6f1234018100000000000000000000000000
Line   539697: 	Line   544155: 2023-02-23 18:07:41.150 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 407f0e6f123401810000000000000000000000000000
Line   544789: 	Line   549285: 2023-02-23 18:11:01.053 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>000000000000000000000000000000407f
Line   551546: 	Line   556064: 2023-02-23 18:16:42.647 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0000407f0e6f12340181000000000000000000000000
Line   572894: 	Line   577526: 2023-02-23 18:35:31.217 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>7f0e6f1234018100000000000000000000
Line   597698: 	Line   602481: 2023-02-23 18:56:32.299 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 120000407f0e6f123401810000000000000000000000
Line   617949: 	Line   622847: 2023-02-23 19:11:03.618 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000407f0e
Line   668547: 	Line   673702: 2023-02-23 19:47:59.965 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: ff0f210000640000004164120000407f0e6f12340181
Line   741537: 	Line   747058: 2023-02-23 20:42:50.570 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 00407f0e6f1234018100000000000000000000000000
Line   754345: 	Line   759929: 2023-02-23 20:53:16.585 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>000000000000000000000000000000407f
Line   765536: 	Line   771173: 2023-02-23 21:01:46.208 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000407f0e
Line   774254: 	Line   779960: 2023-02-23 21:08:06.520 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 00407f0e6f1234018100000000000000000000000000
Line   777714: 	Line   783436: 2023-02-23 21:10:28.162 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>4164120000407f0e6f1234018100000000
Line   822699: 	Line   828660: 2023-02-23 21:48:39.402 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000407f0e6f1234018100000000000000
Line   823214: 	Line   829179: 2023-02-23 21:49:05.262 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0000407f0e6f12340181000000000000000000000000
Line   868784: 	Line   875007: 2023-02-23 22:28:43.961 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0000407f0e6f12340181000000000000000000000000
Line   906585: 	Line   912958: 2023-02-23 22:58:44.815 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0000407f0e6f12340181000000000000000000000000
Line   971526: 	Line   978214: 2023-02-23 23:56:05.042 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0e6f1234018100000000000000000000000000000000
Line   971527: 	Line   978215: 2023-02-23 23:56:05.202 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 6f123401810000000000000000000000000000000000
Line 1071688: 	Line 1078728: 2023-02-24 01:10:38.450 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 6f123401810000000000000000000000000000000000
Line 1093935: 	Line 1101043: 2023-02-24 01:25:34.478 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 6f123401810000000000000000000000000000000000
Line 1229081: 	Line 1236694: 2023-02-24 03:17:18.047 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>004164120000407f0e6f12340181000000
Line 1229636: 	Line 1237250: 2023-02-24 03:17:34.535 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0000407f0e6f12340181000000000000000000000000
Line 1257736: 	Line 1265435: 2023-02-24 03:38:47.995 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 7f0e6f12340181000000000000000000000000000000
Line 1258424: 	Line 1266127: 2023-02-24 03:39:20.172 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000000040
Line 1311063: 	Line 1318942: 2023-02-24 04:21:33.308 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0e6f1234018100000000000000000000000000000000
Line 1320379: 	Line 1328293: 2023-02-24 04:30:09.024 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>004164120000407f0e6f12340181000000
Line 1321147: 	Line 1329062: 2023-02-24 04:30:21.994 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0f210000640000004164120000407f0e6f1234018100
Line 1324399: 	Line 1332329: 2023-02-24 04:34:05.005 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0e6f1234018100000000000000000000000000000000
Line 1330739: 	Line 1338686: 2023-02-24 04:38:22.704 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0000407f0e6f12340181000000000000000000000000
Line 1334851: 	Line 1342813: 2023-02-24 04:41:26.231 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000407f0e6f1234018100000000000000
Line 1360026: 	Line 1368107: 2023-02-24 05:01:06.650 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000000040
Line 1431662: 	Line 1440047: 2023-02-24 06:02:06.565 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>000000000000000000000000000000407f
Line 1433195: 	Line 1441587: 2023-02-24 06:03:04.361 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000000040
Line 1444401: 	Line 1452848: 2023-02-24 06:11:36.097 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: ff0f210000640000004164120000407f0e6f12340181
Line 1493500: 	Line 1502279: 2023-02-24 06:57:06.730 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>000000000000000000000000000000407f
Line 1518625: 	Line 1527533: 2023-02-24 07:17:22.107 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 6f123401810000000000000000000000000000000000
Line 1536908: 	Line 1545936: 2023-02-24 07:33:07.038 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>00407f0e6f123401810000000000000000
Line 1628187: 	Line 1637540: 2023-02-24 08:41:41.514 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 0e6f1234018100000000000000000000000000000000
Line 1629171: 	Line 1638530: 2023-02-24 08:43:05.569 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000000040
Line 1639431: 	Line 1648836: 2023-02-24 08:53:51.686 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000407f0e
Line 1670228: 	Line 1679725: 2023-02-24 09:19:10.415 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000000040
Line 1703343: 	Line 1712941: 2023-02-24 09:48:37.663 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000407f0e
Line 1722573: 	Line 1732307: 2023-02-24 10:05:05.916 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>00407f0e6f123401810000000000000000
Line 1729434: 	Line 1739185: 2023-02-24 10:10:35.899 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000000000000000000000000000407f0e
Line 1741038: 	Line 1750824: 2023-02-24 10:19:09.586 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>120000407f0e6f12340181000000000000
Line 1749330: 	Line 1759158: 2023-02-24 10:25:08.319 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>120000407f0e6f12340181000000000000
Line 1798782: 	Line 1808783: 2023-02-24 11:04:53.109 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>00004100120000407f0e6f123401810000
Line 1803597: 	Line 1813608: 2023-02-24 11:08:35.800 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg:<PHONE_NUMBER>0000407f0e6f1234018100000000000000
Line 1805403: 	Line 1815424: 2023-02-24 11:10:25.811 WARNING (Thread-3) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern.py] Unknown msg: 407f0e6f123401810000000000000000000000000000
Originally posted by @8OND007 in https://github.com/gluap/pyduofern-hacs/issues/26#issuecomment-1430974080

FYI, I reverted back to the previous version 0.4.0 and did not had any of these "Unknown msg" again the last 24h.
So the last 0.4.1 must cause this somehow.

I think this is related to the auto-polling of device state. I'm looking into it.

FYI, I again switched from 0.4.0 to the latest versions 0.5.1 and now 0.5.2 and did not notice this "Unknown msg" anymore in the HA log. I do notice now the Duofern stick requesting status updates every 5 minutes now and the Covers sending it multiple times  :
2023-03-15 09:03:34.881 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:03:34.903 INFO (Thread-2) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 0 msgs left in queue
2023-03-15 09:03:35.107 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.108 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.108 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.108 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.109 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.111 INFO (SyncWorker_3) [custom_components.duofern.cover] updating state
2023-03-15 09:03:35.111 INFO (SyncWorker_3) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:03:35.112 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.115 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.116 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.116 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.116 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.119 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.119 INFO (SyncWorker_1) [custom_components.duofern.cover] updating state
2023-03-15 09:03:35.119 INFO (SyncWorker_1) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:03:35.120 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:35.120 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:03:49.882 INFO (SyncWorker_0) [custom_components.duofern.cover] updating state
2023-03-15 09:03:49.883 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:04:04.881 INFO (SyncWorker_0) [custom_components.duofern.cover] updating state
2023-03-15 09:04:04.882 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:04:19.883 INFO (SyncWorker_6) [custom_components.duofern.cover] updating state
2023-03-15 09:04:19.883 INFO (SyncWorker_6) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:04:34.883 INFO (SyncWorker_0) [custom_components.duofern.cover] updating state
2023-03-15 09:04:34.883 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:04:49.883 INFO (SyncWorker_9) [custom_components.duofern.cover] updating state
2023-03-15 09:04:49.884 INFO (SyncWorker_9) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:05:04.894 INFO (SyncWorker_5) [custom_components.duofern.cover] updating state
2023-03-15 09:05:04.894 INFO (SyncWorker_5) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:05:19.886 INFO (SyncWorker_3) [custom_components.duofern.cover] updating state
2023-03-15 09:05:19.887 INFO (SyncWorker_3) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:05:34.887 INFO (SyncWorker_2) [custom_components.duofern.cover] updating state
2023-03-15 09:05:34.887 INFO (SyncWorker_2) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:05:49.888 INFO (SyncWorker_1) [custom_components.duofern.cover] updating state
2023-03-15 09:05:49.889 INFO (SyncWorker_1) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:06:04.890 INFO (SyncWorker_3) [custom_components.duofern.cover] updating state
2023-03-15 09:06:04.890 INFO (SyncWorker_3) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:06:19.893 INFO (SyncWorker_2) [custom_components.duofern.cover] updating state
2023-03-15 09:06:19.893 INFO (SyncWorker_2) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:06:34.893 INFO (SyncWorker_7) [custom_components.duofern.cover] updating state
2023-03-15 09:06:34.894 INFO (SyncWorker_7) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:06:49.894 INFO (SyncWorker_4) [custom_components.duofern.cover] updating state
2023-03-15 09:06:49.894 INFO (SyncWorker_4) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:07:04.895 INFO (SyncWorker_6) [custom_components.duofern.cover] updating state
2023-03-15 09:07:04.895 INFO (SyncWorker_6) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:07:19.896 INFO (SyncWorker_0) [custom_components.duofern.cover] updating state
2023-03-15 09:07:19.897 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:07:34.897 INFO (SyncWorker_0) [custom_components.duofern.cover] updating state
2023-03-15 09:07:34.898 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:07:49.899 INFO (SyncWorker_9) [custom_components.duofern.cover] updating state
2023-03-15 09:07:49.899 INFO (SyncWorker_9) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:08:04.903 INFO (SyncWorker_4) [custom_components.duofern.cover] updating state
2023-03-15 09:08:04.904 INFO (SyncWorker_4) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:08:19.904 INFO (SyncWorker_3) [custom_components.duofern.cover] updating state
2023-03-15 09:08:19.904 INFO (SyncWorker_3) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:08:34.904 INFO (SyncWorker_5) [custom_components.duofern.cover] updating state
2023-03-15 09:08:34.904 INFO (SyncWorker_5) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:08:34.910 INFO (Thread-2) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 0 msgs left in queue
2023-03-15 09:08:35.136 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.138 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.139 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.139 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.139 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.140 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.140 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.140 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.141 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.141 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.144 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.144 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.145 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:08:35.160 INFO (SyncWorker_6) [custom_components.duofern.cover] updating state
2023-03-15 09:08:35.161 INFO (SyncWorker_6) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:08:49.904 INFO (SyncWorker_5) [custom_components.duofern.cover] updating state
2023-03-15 09:08:49.904 INFO (SyncWorker_5) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:09:04.905 INFO (SyncWorker_1) [custom_components.duofern.cover] updating state
2023-03-15 09:09:04.905 INFO (SyncWorker_1) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:09:19.925 INFO (SyncWorker_3) [custom_components.duofern.cover] updating state
2023-03-15 09:09:19.926 INFO (SyncWorker_3) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:09:34.919 INFO (SyncWorker_3) [custom_components.duofern.cover] updating state
2023-03-15 09:09:34.919 INFO (SyncWorker_3) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:09:49.916 INFO (SyncWorker_0) [custom_components.duofern.cover] updating state
2023-03-15 09:09:49.916 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:10:04.919 INFO (SyncWorker_9) [custom_components.duofern.cover] updating state
2023-03-15 09:10:04.920 INFO (SyncWorker_9) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:10:19.921 INFO (SyncWorker_0) [custom_components.duofern.cover] updating state
2023-03-15 09:10:19.921 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:10:34.920 INFO (SyncWorker_0) [custom_components.duofern.cover] updating state
2023-03-15 09:10:34.920 INFO (SyncWorker_0) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:10:49.911 INFO (SyncWorker_7) [custom_components.duofern.cover] updating state
2023-03-15 09:10:49.912 INFO (SyncWorker_7) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:11:04.925 INFO (SyncWorker_6) [custom_components.duofern.cover] updating state
2023-03-15 09:11:04.925 INFO (SyncWorker_6) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:11:19.915 INFO (SyncWorker_1) [custom_components.duofern.cover] updating state
2023-03-15 09:11:19.915 INFO (SyncWorker_1) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:11:34.924 INFO (SyncWorker_4) [custom_components.duofern.cover] updating state
2023-03-15 09:11:34.925 INFO (SyncWorker_4) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:11:49.932 INFO (SyncWorker_2) [custom_components.duofern.cover] updating state
2023-03-15 09:11:49.932 INFO (SyncWorker_2) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:12:04.924 INFO (SyncWorker_5) [custom_components.duofern.cover] updating state
2023-03-15 09:12:04.925 INFO (SyncWorker_5) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:12:19.917 INFO (SyncWorker_3) [custom_components.duofern.cover] updating state
2023-03-15 09:12:19.917 INFO (SyncWorker_3) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:12:34.918 INFO (SyncWorker_8) [custom_components.duofern.cover] updating state
2023-03-15 09:12:34.918 INFO (SyncWorker_8) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:12:49.920 INFO (SyncWorker_6) [custom_components.duofern.cover] updating state
2023-03-15 09:12:49.921 INFO (SyncWorker_6) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:13:04.920 INFO (SyncWorker_1) [custom_components.duofern.cover] updating state
2023-03-15 09:13:04.920 INFO (SyncWorker_1) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:13:19.923 INFO (SyncWorker_6) [custom_components.duofern.cover] updating state
2023-03-15 09:13:19.923 INFO (SyncWorker_6) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:13:34.932 INFO (SyncWorker_1) [custom_components.duofern.cover] updating state
2023-03-15 09:13:34.932 INFO (SyncWorker_1) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:13:34.974 INFO (Thread-2) [/usr/local/lib/python3.10/site-packages/pyduofern/duofern_stick.py] sending 0DFF0F400000000000000000000000000000407f0e01 from write queue, 0 msgs left in queue
2023-03-15 09:13:35.181 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.183 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.184 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.188 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.188 INFO (SyncWorker_9) [custom_components.duofern.cover] updating state
2023-03-15 09:13:35.188 INFO (SyncWorker_9) [custom_components.duofern.cover] 407f0e state is now 100
2023-03-15 09:13:35.191 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.191 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.191 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.193 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.193 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.193 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.194 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.194 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.194 INFO (Thread-2) [custom_components.duofern] Updatecallback for 407f0e
2023-03-15 09:13:35.198 INFO (SyncWorker_5) [custom_components.duofern.cover] updating state
2023-03-15 09:13:35.199 INFO (SyncWorker_5) [custom_components.duofern.cover] 407f0e state is now 100
Don't know why the Cover does not send its status once.
It would be indeed great if we could disable the auto update or at least fill in a custom time interval. I don't need a status update every 5 minutes.
My experience with status update with v.0.4.0 was also good. Only update if the cover moves.
The only time I would like an auto update is when HA reboots and the cover position is unkown. Afterwards if HA sends the cover to another posiiton or I steer the cover locally on the panel it always sends an update by itself. So no need for auto update status request by the Duofern stick.
I did not found my Sun Sensor with the newest versions. Maybe my Duofern stick is too far away from the Sun Sensor. Duofern isn't a mesh network I guess like Z-wave or Zigbee.
I also don't see the new UI to add/pair new devices.
I tried to disable/enable the Duofern integration (0.5.1) to see if that triggers the new UI on the Devices page in HA but it did not.
The new toggle butoon works.
Changing the manual mode, I did not see it on the panel.
You can close this specific ticket.

Good to see I'm not the only one looking for a bit of control on the 5 minutes auto update feature.
Have a look at https://github.com/gluap/pyduofern-hacs/issues/26 for this.
For HA start: simply create an automation (if you don't have one yet) with

trigger: HA start
action: use the update device status service from duoFern to request a full status update once (in the past I used the cover.stop_cover service for this) *

depending on the duoFern version installed the name and need for specifying an entity_id as target for the service call varies


[AVM Module Issue]:

Check for previous/existing GitHub issues

[x] I have checked for previous/existing GitHub issues

Issue Type?
Bug
Module Name
avm/res/search/search-service
(Optional) Module Version
0.7.0
Description
I copy-pasted the sample code to try Default and deploying keys to azure key vault with version 0.7.0 and the key vault object parameter is automatically flagged as not permitted. I went into the module and I see it's declare so I don't know exactly where the issue is. I just wanted to raise it for awareness or to be corrected if I missed something.

My code:
param location string = resourceGroup().location

param kvName string

param envName string = 'dev'

param aiSeachName string = 'ai-search-${uniqueString(resourceGroup().id)}-${envName}}'

@allowed([
  'free'
  'disabled'
  'standard'
])
@description('Configuration for semantic search, dependent on region and SKU')
param semanticSearchConfig string = 'free'

resource kv 'Microsoft.KeyVault/vaults@2024-04-01-preview' existing ={
  name: kvName
}

module searchService 'br/public:avm/res/search/search-service:0.7.0' = {
  name: 'searchServiceDeployment'
  params: {
    // Required parameters
    name: aiSeachName
    // Non-required parameters
    authOptions: {
      aadOrApiKey: {
        aadAuthFailureMode: 'http401WithBearerChallenge'
      }
    }
    disableLocalAuth: false
    location: location
    semanticSearch: semanticSearchConfig
    // issue gets flagged here
    secretsExportConfiguration: {
      keyVaultResourceId: kv.id
      primaryAdminKeyName: 'Primary-Admin-Key'
      secondaryAdminKeyName: 'Secondary-Admin-Key'
    }
  }
}

(Optional) Correlation Id
No response

Link with the sample I used: https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/search/search-service#example-2-deploying-with-a-key-vault-reference-to-save-secrets

@jolerasioo Could you please test with the version 0.7.1 or newer? I think the 0.7.0 didn't support secretsExportConfiguration.


CASSANDRA-19688 SAI support for BETWEEN operator

Patch by Arun Ganesh; reviewed by TBD for CASSANDRA-19688

Committed as https://github.com/apache/cassandra/commit/bddaa4409fc4cb83394c2963a1028bcfb9dce733


[@hmscore/react-native-hms-push] Downlink Messages are always sent to silent channel

"@hmscore/react-native-hms-push": "^6.3.0-304",
"react-native": "0.63.4",

When I sent Downlink Message from my server to the device it is sent to the automatically created channel "Advertisements" and it has Gentle notifications enabled by default (a message is displayed only in the notification panel, and has no sound).
Here is the code:
fetch(
    `https://push-api.cloud.huawei.com/v1/${appId}/messages:send`,
    {
      method: 'POST',
      headers: {
        'Content-Type': 'application/json',
        Accept: 'application/json',
        Authorization: `${tokenType} ${accessToken}`,
      },
      body: JSON.stringify({
        message: {
          android: {
            notification: {
              title: 'Title',
              notify_summary: 'Summary',
              body: 'Body',
              click_action: { type: 3 },
              default_sound: true,
              importance: 'NORMAL',
            },
          },
          token: [token],
        },
      }),
    }

I tried to send it to that another channel (huawei-hms-rn-push-channel), got its id huawei-hms-rn-push-channel-id-4 and added channel_id property to the request but the messages wasn't sent to that channel. So specifying channel id doesn't work as well.
Silent mode on the device is not enabled.
How to send notifications that are not silent?

Could you kindly help us with some information to locate this issue?

A push requestid and token which the value of the importance field is NORMAL.
Push logs on devices side: You can obtain it by selecting File Management (APP) > Search push.log/NC.log > Deep Search.

Hi @Xuejiao-Shi, here is the data you asked for, thanks:
Push requestId:
165605476452135269037701

Push token:
IQAAAACy0tu7AACL3-_D7wkob1WwQ9JW4m_SsI1p48P7y1RIuu13kP1OY2TxHLHCbUdVERr08AtnltfETc4NDlCrW-jg7V-4vN2TSx3ErV3zMzBdew

Latest push logs after sending downlink message:
2022-06-24-11:11:49 -> PushLog110002306 [ReceiverDispatcher-231]enter AlarmTools:setExactAlarm(intent:Intent { act=com.huawei.android.push.intent.HEARTBEAT_RSP_TIMEOUT pkg=android } interval:10000ms
2022-06-24-11:11:49 -> PushLog110002306 [ReceiverDispatcher-231]setExactAlarm expectTriggerTime:1656054719013
2022-06-24-11:11:49 -> PushLog110002306 [ReceiverDispatcher-231]process cmdid to send to pushSrv:46, subCmdId:FF
2022-06-24-11:11:49 -> PushLog110002306 [ReceiverDispatcher-231]send msg to remote srv success
2022-06-24-11:11:49 -> PushLog110002306 [SocketRead_10:47:46-254]process cmdid to receive from pushSrv:47, subCmdId:FF
2022-06-24-11:11:49 -> PushLog110002306 [SocketRead_10:47:46-254]enter AlarmTools:setExactAlarm(intent:Intent { act=com.huawei.push.alarm.HEARTBEAT pkg=android } interval:180000ms
2022-06-24-11:11:49 -> PushLog110002306 [SocketRead_10:47:46-254]setExactAlarm expectTriggerTime:1656054889328
2022-06-24-11:11:49 -> PushLog110002306 [ReceiverDispatcher-231]process push message cmdid from pushSrv:47, subCmdId:FF
2022-06-24-11:12:48 -> PushLog110002306 [SocketRead_10:47:46-254]process cmdid to receive from pushSrv:44, subCmdId:FF
2022-06-24-11:12:48 -> PushLog110002306 [ReceiverDispatcher-231]process push message cmdid from pushSrv:44, subCmdId:FF
2022-06-24-11:12:48 -> PushLog110002306 [ReceiverDispatcher-231]msgType: 2 [0:PassBy msg, 1:System notification, 2:normal notification, 3:HCM PassBy msg]
2022-06-24-11:12:48 -> PushLog110002306 [ReceiverDispatcher-231]receive a push msg,ctrl state:0, isDawn:false
2022-06-24-11:12:48 -> PushLog110002306 [ReceiverDispatcher-231]send selfshow msg to NC to display, pkgName:com.myapp,msgID:013731D76C0B9930,haStorageId:-1,userId:0,subjectId:
2022-06-24-11:12:48 -> PushLog110002306 [ReceiverDispatcher-231]AiClose Switch is off
2022-06-24-11:12:48 -> PushLog110002306 [ReceiverDispatcher-231]process cmdid to send to pushSrv:45, subCmdId:FF
2022-06-24-11:12:48 -> PushLog110002306 [ReceiverDispatcher-231]send msg to remote srv success
2022-06-24-11:12:48 -> PushLog110002306 [ReceiverDispatcher-231]handleMessageResponse the response msg is :45,msgId:013731D76C0B9930,displayPkgName:com.myapp,flag:00

Can you provide the push.log and NC.log log files on devices side? You can obtain it by selecting File Management (APP) > Search push.log/NC.log > Deep Search.

hi @yaroslavnikiforov you can send it to<EMAIL_ADDRESS>thanks

Can I confirm that your app is going to release in China? Looks like you've set the Data Processing Location to China. If Data Processing Location is set to China and the app does not apply for self-categorization rights, the importance field does not take effect. As a result, the messages are intelligently classified as marketing notifications.
If your app users are not primarily in China, you are advised to set the data processing location based on the location of your users: https://developer.huawei.com/consumer/en/doc/development/HMSCore-Guides/android-config-agc-0000001050170137#section3380135485

Sorry, as the self-categorized rights document is currently only available in Chinese, you can try to translate the content of that page.
How to avoid classifying messages as marketing notifications in this case?
--For applications release in China, need to apply for self-classification rights to avoid this.

I don't have 'self-classification' on the corresponding page in AppGallery Connect.

Sorry@yaroslavnikiforov, confirm with the product team that your account belongs to overseas, Therefore, the portal for applying for self-categorized rights button is not displayed on the AGC. You can refer to this document to send the application to Huawei Push operation team by email. We are very sorry that it brings you inconvinience and have reported this issue to the corresponding product team.


Kourend Library Plugin: Add config option to hide duplicate books

Added a config in the Kourend Library setting to hide book you already have in your inventory.
Since you can't have any duplicate books in your inventory.

I would like for the plugin to keep a EnumSet<Book> that updates on ItemContainerChanged, so the overlay doesn't have to iterate the whole inventory multiple times a frame

I've addressed the problem., but something came to my attention, the merged pull request also contain this problem. When shall I pick this up and how?

I didn't worry about that because that was running at most once per frame. If you want to make it use the enumset, you can just add a commit to this pr, and smash everything else together.

I didn't worry about that because that was running at most once per frame. If you want to make it use the enumset, you can just add a commit to this pr, and smash everything else together.

By smash everything together, you mean squash all commits into one?

yes, combine the commits, except for the one changing the merged pr

yes, combine the commits, except for the one changing the merged pr

I didn't worry about that because that was running at most once per frame. If you want to make it use the enumset, you can just add a commit to this pr, and smash everything else together.

Done

yes, combine the commits, except for the one changing the merged pr

Done


Volume definition needs to done better

Improve the way volume definition is done, size is not common to everything it's only in pvc.

There is a bit more issues with how are volumes done currently.
I think that top level "persistentVolume" should be based on PersistentVolumeClaim and not on Volume.

This is how I think handling persistent storage should look like.
full example
name: database
containers:
# pod spec
- image: mariadb:10
  volumeMounts:
  - name: vol1
    mountPath: /var/lib/mysql
volumes:
  - name: vol1
    persistentVolumeClaim:
       claimName: vol1

persistentVolumes:
# PersitentVolumeClaimSpec
- name: vol1
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 8Gi

with shortcuts
name: database
containers:
- image: mariadb:10
  volumeMounts:
  - name: vol1
    mountPath: /var/lib/mysql

persistentVolumes:
- name: vol1
  size: 8Gi # shortcut for specifying 'requst.storage'

If there is no matching volume for volumeMount, volume is created automatically with the same name and the same name is also used to attach volume to 'persistentVolumeClaim`

taking this up!


Dependencies alerts

In some alerts you want that more than one conditions will happen to issue an alert.
So the flow will be like the following,
Query -> Alert -> Check N query -> Alert \ cancel the alert
What do you think?

Could you give a more concrete example of what you are trying to accomplish?
I think this can be solved using join but I am not sure.

For example, we I monitored CPU spike, I want to check the memory before I send the alert, if the memory is acting as expected, then I dont want to send the alert.

Would this work?
var cpu = stream.from('cpu')...
var mem = stream.from('mem')...

cpu.join(mem)
        .as('cpu', 'mem')
    .alert()
        .crit(lamda: "cpu.value" > 80 AND "mem.value" > 95)
         ....

This can be a good starting, if I take it further, I can think on a case that if I have CPU spike i'd want to see the last 5min avg cpu.
So it's also depends on time and not only on value and measurement.
Does this also supported, right?

Instead of thinking of action/reaction for alerting let's first define the criteria for the alert. For example lets choose something relatively complex.

CPU -- There must be a spike in cpu over the last minute above 80% and the last 5 minutes of CPU must be over 70%
Memory -- The last 5 minutes of memory usage must be above 80%

Ok now that we have our criteria we just need to figure out how to get those three data points into a single point so we can define our alert criteria.
Starting backwards here is our alerting criteria:
.alert()
    .crit(lambda: "cpu1min.mean" > 80 AND "cpu5min.mean" > 70 AND "mem5min.mean" > 80)

Ok so now we just need to define each of our fields and join on them. Since join uses time as the join index, we need to make sure that each stream is emitting a value at the same time. This is where the windowing functionality comes in.
var cpu1min = stream.from('cpu')
    .window()
        .period(1m)
        .every(1m)
        // align the window so that can we can ensure proper joining.
        .align()
    .mapReduce(influxql.mean('value'))

var cpu5min = stream.from('cpu')
    .window()
        .period(5m)
        //Note we still emit the value every minute so that we can join properly.
        .every(1m)
        .align()
    .mapReduce(influxql.mean('value'))

var mem5min = stream.from('mem')
    .window()
        .period(5m)
        //Note we still emit the value every minute so that we can join properly.
        .every(1m)
        .align()
    .mapReduce(influxql.mean('value'))

With that we have defined the three streams of fields we need. Now let's join them.
cpu1min.join(cpu5min, mem5min)
      .as('cpu1min', 'cpu5min', 'mem5min')
     // Now we have a stream of data with a value every minute that contains the cpu mean for the past 1 and 5 minutes as well as the mean memory usage for the past 5 minutes.

Putting it all together:
var cpu1min = stream.from('cpu')
    .window()
        .period(1m)
        .every(1m)
        // align the window so that can we can again ensure proper joining.
        .align()
    .mapReduce(influxql.mean('value'))

var cpu5min = stream.from('cpu')
    .window()
        .period(5m)
       //Note we still emit the value every minute so that we can join properly.
        .every(1m)
        .align()
    .mapReduce(influxql.mean('value'))

var mem5min = stream.from('mem')
    .window()
        .period(5m)
       //Note we still emit the value every minute so that we can join properly.
        .every(1m)
        .align()
    .mapReduce(influxql.mean('value'))

cpu1min.join(cpu5min, mem5min)
      .as('cpu1min', 'cpu5min', 'mem5min')
   .alert()
    .crit(lambda: "cpu1min.mean" > 80 AND "cpu5min.mean" > 70 AND "mem5min.mean" > 80)

@nathanielc Thanks for the described explanation, much appreciated!


Auchan - The message "Bucuresti is not a city in Romania" and others like this is displayed on scrapers.peviitor.ro for all the jobs

ENVIRONMENT: production
URL: https://scrapers.peviitor.ro/
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:
1.Open the URL in the browser
2.Run scraper for "Auchan" Company
3.Check the location for all the jobs
EXPECTED RESULTS:
Jobs should have a city as a location
ACTUAL RESULTS:
The message "Bucuresti is not a city in Romania" and others like this is displayed on scrapers.peviitor.ro for all the jobs
On the company's website https://cariere.auchan.ro/auchan/jobs/, the location of the jobs is specified as being exactly the city from the message displayed on the scrapers.peviitor.ro
For ex.:
"Timișoara is not a city in Romania", the location is Timisoara;
"București is not a city in Romania", the location is Bucuresti
"Iași is not a city in Romania", the location is Iasi
and so on

Fixed

The scraper was retested and new bugs were found.
1. The message "Ilfov is not a city in Romania" is displayed on https://scrapers.peviitor.ro/src/auchan/ for this jobs

Inspector Calitate Depozit Logistic Stefanestii de Jos
Specialist Exploatare

For this Job "Inspector Calitate Depozit Logistic Stefanestii de Jos"  the location on the Company's website is  Platforma logistica Stefanestii de Jos
https://cariere.auchan.ro/auchan/jobs/job-inspector-calitate-depozit-logistic-stefanestii-de-jos/
For this Job "Specialist Exploatare"  the location on the Company's website is Platforma Logistica https://cariere.auchan.ro/auchan/jobs/job-specialist-exploatare/

2. On the https://peviitor.ro/rezultate?q=auchan, this job " Asistent Vanzari JYSK Constanta Auchan Sud" appears belongs to the JYSK company,  which is located inside the Auchan store

That job is no longer available

Regression testing:
On the https://scrapers.peviitor.ro/src/auchan/ the changes required to fix the bug did not introduce new problems and didn't affect other functionality.


Adding svelte preprocessors to rollup config?

I've tried to follow other examples in the issues here, but haven't been able to figure it out.
I have a custom rollup config already, but I'm trying to add a markdown library (https://mdsvex.com/) to my app (I also tried with https://github.com/AlexxNB/svelte-preprocess-markdown but had the same issue).
The problem is in both their examples they add the function directly to the svelte rollup plugin, which doesn't seem possible - and not possible to have multiple.
I've tried adding it to a preprocessor script, but it's not clear where I add the extensions. I ended on below - nothing breaks but it's not rendering as expected, so I assume it's not being loaded?  (I tried using it in the replace, but that seems to be a different set of options)
const { mdsvex } = require('mdsvex')

function setSveltePreprocessOptions(options) {
  return {
    typescript: {
      extensions: [
        '.svelte',
        '.svx'
      ],
      plugins: [
        mdsvex({extensions: ['.svelte', '.svx']})
      ]
    }
  };
}

module.exports = setSveltePreprocessOptions;

I added a hopefully easier way to do the configurations. There's an example in the docs now.

I'll close this for now, reopen if the problem still exist or open a new after you tried the update :-)


No more versions?

This is not an issue report, just a question.
Are you planning to continue delivering new releases? It seems to be stopped at 2.9.3, with much work done related to 2.9.4 but without a formal release.
Do we need to use 2.9.3 as it's stable, or just jump into 2.9.4?
Thank you.

There are also deprecation warnings in modern sass versions:
Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div(100% * $count, $perpage) or calc(100% * $count / $perpage)

Came to check on those deprecation warnings and I see they have been noted.

What are you waiting for merge this:
https://github.com/ganlanyuan/tiny-slider/pull/704


bzr source plugin can introduce non-determinism

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:53
Summary
When staging the bzr checkout at Source.stage() time, we are not making any effort to ensure that the staged files have deterministic file attributes.
As far as I can see, similar to issue #527 and more similar to #543, the checkout will result in file permissions which depend on the user's umask.

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:53
marked this issue as related to #527

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:53
marked this issue as related to #540

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:53
marked this issue as related to #541

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:53
marked this issue as related to #542

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:53
marked this issue as related to #543

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:57
marked this issue as related to #545

In GitLab by [Gitlab user @toscalix] on Aug 6, 2018, 09:51
assigned to [Gitlab user @valentindavid]

In GitLab by [Gitlab user @valentindavid] on Aug 6, 2018, 10:42
marked this issue as related to #555

In GitLab by [Gitlab user @valentindavid] on Aug 6, 2018, 17:09
mentioned in commit 4d142206bdba11bcef52e54c8c2ea4e1ad525d03

In GitLab by [Gitlab user @valentindavid] on Aug 7, 2018, 17:33
mentioned in commit 4d49d8c0a2ad3e94f44080bfe55cc853dd22198e

In GitLab by [Gitlab user @valentindavid] on Aug 9, 2018, 15:18
mentioned in commit 298fa0483ec407e0cc54c216eefcbeaf328d7f0a

In GitLab by [Gitlab user @valentindavid] on Aug 10, 2018, 09:53
mentioned in commit c5362746c10efc734fe65d5978d8c1ad47b3f0d9

In GitLab by [Gitlab user @valentindavid] on Aug 10, 2018, 11:08
mentioned in commit 9daa8eace89f750a227e38b59137e6861c256dd1

In GitLab by [Gitlab user @valentindavid] on Aug 10, 2018, 14:50
mentioned in commit 8757117c2fe3abd89e9682909587657125e6a10d

In GitLab by [Gitlab user @valentindavid] on Aug 10, 2018, 15:22
mentioned in commit 1b9c9277e92f57d4ec2bf510eaf00d45bf33ee12

In GitLab by [Gitlab user @valentindavid] on Aug 12, 2018, 06:54
mentioned in commit 322cab58e255916da10e0a59ae91e92f50898504

In GitLab by [Gitlab user @valentindavid] on Aug 12, 2018, 06:57
mentioned in commit 465909ddc6d39822f7669d554f3033e497b6f762

In GitLab by [Gitlab user @tristanvb] on Aug 12, 2018, 07:59
closed via merge request !616

In GitLab by [Gitlab user @valentindavid] on Aug 12, 2018, 07:59
closed via commit 322cab58e255916da10e0a59ae91e92f50898504

In GitLab by [Gitlab user @tristanvb] on Aug 12, 2018, 07:59
mentioned in commit c1fdebb3137891305bea7db8b4f1ad9f0b1e2043


feat: universal tensor type

Introduces the type Tensor can take any kind of tensor (for now this means np and torch).
The former tensor type is renamed to NdArray.
As far as the proto is concerned, Tensor does not exist; it is only a shorthand that will cast the input either to NdArray or to TorchTensor.
closes #782

I kept the type as NdArray in the tests since the tests are not about that.
To properly test the (de)serialization of this new type I instead added a dedicated test for that


Remove wp-locales from git

Fixes

N/A -- Just fixing this so it doesn't show up in every PR or whenever you run pnpm dev.
Won't be necessary again after #580 is merged.
Description

Updates wp-locales.json with the newest information.
Testing Instructions

Run pnpm i18n:get-translations and verify there are no staged changes.
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[N/A] I added or updated tests for the changes I made (if applicable).
[N/A] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

#580 is merged, so perhaps it's better to delete the file in this PR? It must've gotten accidentally committed despite the .gitignore, probably during someone's merge.

I'm merging because I really want this on my current PR and you're probably deep in a code flow. Thanks @sarayourfriend!


entire disk as filesystem?

Hi,
When running a separate journal, and you take a whole disk as OSD, why bother creating GPT and partition?
You could just format the entire blockdevice with XFS without partitions.
Is there a downside to this approach?

ceph-disk is doing that we don't have any control on this.


Undefined token

No sure what's going on

Can you provide minimal reproduction?

@glebbash same problem from me.
This is related to decorator metadata.
NestJS check for metadata design:paramtype
Fireorm check form metadata design:type
If change to design:type application start

Interesting, will check, I supposed I the issue is related to reflector-metadata lib then I tried to downgrade but didn't worked, will check that, thanks!

@Ivanrenes related to https://github.com/rbuckton/reflect-metadata/issues/160?

I've seen issues upgrading to latest reflect-metadata as well.

If change to design:type application start

@mrbatista can you provide more info on this so I could add it to the lib.

@Ivanrenes related to https://github.com/rbuckton/reflect-metadata/issues/160?

Ye

I've seen issues upgrading to latest reflect-metadata as well.

If change to design:type application start

@mrbatista can you provide more info on this so I could add it to the lib.

I'm trying to understand the problem:
Package @nest/common has moved reflect-metadata to peerDependecies https://github.com/nestjs/nest/blob/ddc1265735bdec0f2e1dc4ac19d98304692b841a/packages/common/package.json#L28 and allow 0.1.0 and 0.2.0 dependency.
My dependencies tree is correct:

fireorm library has peerDependency to ^0.1.13 https://github.com/wovalle/fireorm/blob/7305cbbe7c32f12d9e932abf3ed5c79f06891373/package.json#L78 which forces you to stay on version 0.1.*
nest check at this line for metadata design:type.
FireormService has different metadata (line 36):

Interesting, will check, I supposed I the issue is related to reflector-metadata lib then I tried to downgrade but didn't work, will check that, thanks!

@Ivanrenes any news?

Hello, i have the same issue.
Could anyone find a way to solve it?

I managed to fix it in a sample projest. The issue is in<EMAIL_ADDRESS>Doing this should fix the issue:
npm i<EMAIL_ADDRESS>

Seems like this PR is the cause of the issue: https://github.com/nestjs/nest/commit/f242efafcdc7dedfabc9a8da6418c0f2f685dbb9

@glebbash absolutely, that's the issue

PR was reverted, now npm i @nestjs/common@latest will work too.

Closing this now. Thanks everyone for reporting and helping to find the issue. 💪


feature flag enabled in prod1 and 2

https://harness.atlassian.net/browse/CDS-63662
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ x] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/CDS-63662

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Error: Path must be a string. Received undefined

Windows 7x64
Node 6.1.0
Npm 3.10.9
electron-packager v8.3.0
I only get the above error when running a packaged app and only with electron-prebuilt versions below 1.22
I know how to debug a non-packaged app using phpstorm, but I am not sure how to debug a packaged app.
I am not sure of the exact relationship between electron and electron-prebuilt but as I understand it electron is a stand-in replacement for electron-prebuilt and looking at the release dates both electron and electron-prebuilt releases 1.22 happened on the same day and in the release notes chrome was updated to  51.0.2704.84. This might the case with electron-prebuilt as well and may be the source of the problem
Any help in tracking this down would be appreciated.

Thanks for filing an issue! In order to help you with your problem, we're going to need more information about it. In particular:

Console output when you run electron-packager with the environment variable DEBUG=electron-packager. Please include the stack trace of the error.

What command line arguments are you passing? Alternatively, if you are using the API, what
parameters are you passing to the packager() function?

Please provide either a failing minimal testcase (with code) or detailed steps to reproduce your
problem. Using electron-quick-start is a good starting point.

package.json script args

"build-win": "electron-packager . musicwrapper --debug=electron-packager --platform=win32 --arch=ia32 --version=1.2.2 --overwrite --out ./build/win",

If --version=1.0.2 with corresponding electron-prebuilt it works.  Using the above --version=1.2.2 it does not.
Compile command npm run-script build-win
I do not get the above error when running it in debug mode. the app runs as expected.
Here is the console output

λ 2016-12-03T18:24:14.388Z - info: Logger initialized. Writing info/warnings/errors to stdout. Writing all logs to "C:\Users\Daniel\AppData\Roaming\google-music-electron\verbose.log"
2016-12-03T18:24:14.426Z - info: App ready. Opening Google Music window nodeIntegration=false, webSecurity=true, height=698, icon=F:\Development\GitHub\delebash\Electron\google-music-electron-master\build\win\musicwrapper-win32-ia32\resources\app\lib\assets/icon-32.png, preload=F:\Development\GitHub\delebash\Electron\google-music-electron-master\build\win\musicwrapper-win32-ia32\resources\app\lib/browser.js, skip-taskbar=undefined, width=1024, x=109, y=null, http_parser=2.7.0, node=6.1.0, v8=5.1.281.59, uv=1.9.0, zlib=1.2.8, ares=1.10.1-DEV, modules=48, openssl=1.0.2h, electron=1.2.2, atom-shell=1.2.2, chrome=51.0.2704.84, version=2.13.0

Link to project
https://github.com/delebash/tunein-music-wrapper.git

A few additional questions:

You must be getting the error as a popup, since it's not in your console output. Is this correct? If so, can you copy/paste all of the stack trace from it (or screenshot the popup, but that's not ideal).
Can you pinpoint exactly which version of Electron (by which I mean electron-prebuilt) where it starts to fail for you? For example, does 1.2.1 work?

electron-prebuilt releases jump from 1.0.2 to 1.2.2 nothing in-beween
https://github.com/electron-userland/electron-prebuilt/releases?after=v1.2.3

I see if I can get a stack trace.
Thanks

A few things to help you debug:

The stacktrace is in your screenshot. Windows appears to cut it off horizontally (note the ... near the end of three of the lines), try making the error popup wider before screenshotting it, so you can see exactly which file is being referenced.
You can optionally set --version=1.2.1 or whatever (valid) Electron version you want in the package.json script args. There are versions between 1.0.2 and 1.2.2 (see Electron releases), but I don't recall why there weren't electron-prebuilt releases made for them.
--debug=electron-packager is not a valid flag for Electron Packager. You have to run SET DEBUG=electron-packager in Windows before running  npm run-script build-win.

Thanks for the info on how to use the DEBUG setting.
I can't resize the popup
I will get back to you on the exact version # of electron that it fails on.  My confusion was about the difference between electron-prebuilt and electron. I will just use electron instead of electron-prebuilt and let you know.
I am not trying to get you to debug my app, it is just that the app runs fine if I just run it via electron .  verses compiled. I am happy to track down the error myself but I am just not familiar with debugging a compiled exe.  My code is in phpstorm so I guess I would install VS, move my code over there, compile it and attach to the running exe.  I will research this some more.
I am ok with compiling it on a lower version that works.  I just thought there where security fixes that would make it better to compile it using the latest stable release.
Thanks for the help.
Here is the console output

<EMAIL_ADDRESS>build-win F:\Development\GitHub\delebash\Electron\google-music-electron-master
electron-packager . musicwrapper --debug=electron-packager --platform=win32 --arch=ia32 --version=1.2.2 --overwrite --out ./build/win

electron-packager Electron Packager 8.3.0 +0ms
electron-packager Node v6.1.0 +2ms
electron-packager Host Operating system: win32 (x64) +1ms
electron-packager Packager Options: {"_":[".","musicwrapper"],"all":false,"deref-symlinks":true,"download":{"strictSSL":true},"overwrite":true,"prune":
true,"debug":"electron-packager","platform":"win32","arch":"ia32","version":"1.2.2","out":"./build/win","dir":".","name":"musicwrapper","protocols":[]} +
1ms
electron-packager Target Platforms: win32 +0ms
electron-packager Target Architectures: ia32 +0ms
electron-packager Inferring app-version from version in F:\Development\GitHub\delebash\Electron\google-music-electron-master\package.json +11ms
electron-packager Application name: musicwrapper +1ms
electron-packager Target Electron version: 1.2.2 +0ms
electron-packager Ignored path regular expressions: [ '/node_modules/electron($|/)',
'/node_modules/electron-prebuilt($|/)',
'/node_modules/electron-packager($|/)',
'/\.git($|/)',
'/node_modules/\.bin($|/)',
'\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"strictSSL":true,"platform":"win32","arch":"ia32","version":"1.2.2"} +102ms
Packaging app for platform win32 ia32 using electron v1.2.2
electron-packager Creating C:\Users\Daniel\AppData\Local\Temp\electron-packager\win32-ia32-template +3ms
electron-packager Extracting C:\Users\Daniel.electron\electron-v1.2.2-win32-ia32.zip to C:\Users\Daniel\AppData\Local\Temp\electron-packager\win32-ia3
2-template +1ms
electron-packager Initializing app in C:\Users\Daniel\AppData\Local\Temp\electron-packager\win32-ia32\musicwrapper-win32-ia32 from C:\Users\Daniel\AppD
ata\Local\Temp\electron-packager\win32-ia32-template template +946ms
electron-packager Ignored paths based on the out param: [ 'F:\Development\GitHub\delebash\Electron\google-music-electron-master\build\win' ] +22
ms
electron-packager Running npm prune --production +4s
electron-packager Renaming electron.exe to musicwrapper.exe in C:\Users\Daniel\AppData\Local\Temp\electron-packager\win32-ia32\musicwrapper-win32-ia32
+6s
electron-packager Running rcedit with the options {"version-string":{},"file-version":"2.13.0","product-version":"2.13.0"} +3ms
electron-packager Moving C:\Users\Daniel\AppData\Local\Temp\electron-packager\win32-ia32\musicwrapper-win32-ia32 to build\win\musicwrapper-win32-ia32 +
263ms
Wrote new app to build\win\musicwrapper-win32-ia32

There is no difference between electron and electron-prebuilt, except for the name and that electron-prebuilt will no longer have Electron releases published to it at the end of this year.

Interestingly enough, I built your app on Linux and the error gets printed to the console, rather than a popup. Hope this helps:
A JavaScript error occurred in the main process
Uncaught Exception:
TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at basename (path.js:1355:5)
    at Command.parse (/tmp/tunein-music-wrapper/build/musicwrapper-linux-x64/resources/app/node_modules/commander/index.js:446:30)
    at Object.exports.parse (/tmp/tunein-music-wrapper/build/musicwrapper-linux-x64/resources/app/lib/cli-parser.js:46:11)
    at Object.<anonymous> (/tmp/tunein-music-wrapper/build/musicwrapper-linux-x64/resources/app/lib/google-music-electron.js:22:39)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:456:32)
    at tryModuleLoad (module.js:415:12)
    at Function.Module._load (module.js:407:3)

(At first glance it appears that you need to modify the CLI parser to not require at least one argument - I ran musicwrapper something and it ran fine.)


winafl-cmin.py issues

hey all,
I'm trying to use the winafl-cmin.py file for corpus distillation but I'm having troubles running it.
Here's the command I tried and the result:
python winafl-cmin.py -i "C:\Users\john\Desktop\results\seed_files" -o "C:\Users\john\Desktop\results\syncdir" -coverage_module shimgvw.dll -target_module PhotoViewerLoader.exe -nargs 2 -D "C:\users\john\Desktop\DynamoRIO-Windows-6.2.0-2\bin32\" -target_offset 0x1040 -t 10000 -- PhotoViewerLoader.exe @@
corpus minimization tool for WinAFL by<EMAIL_ADDRESS>Based on WinAFL by<EMAIL_ADDRESS>Based on AFL by<EMAIL_ADDRESS>usage: winafl-cmin.py [-h] -i dir -o dir [-n] [--working-dir dir] [-v]                       [-covtype {edge,bb}]                       [-call_convention {stdcall,fastcall,thiscall,ms64}]                       -coverage_module module -target_module module -nargs                       nargs -D dir                       (-target_method method | -target_offset rva offset)                       [-t msec] [-f file] [-C] [-e] [-w n]                       ...
winafl-cmin.py: error: one of the arguments -target_method -target_offset is required
Running WinAFL with the -target_offset is working fine so I can't really tell what I'm missing here. Any help would be appreciated!
Thanks,
doria90

Hey @doria90,
Could you try without the last '' in your -D argument? My guess is that
you're escaping the final double quote which messes up the command line
parsing.
Let me know!
Cheers
2017-07-30 1:16 GMT-07:00 doria90<EMAIL_ADDRESS>
hey all,
I'm trying to use the winafl-cmin.py file for corpus distillation but I'm
having troubles running it.
Here's the command I tried and the result:
python winafl-cmin.py -i "C:\Users\john\Desktop\results\seed_files" -o
"C:\Users\john\Desktop\results\syncdir" -coverage_module shimgvw.dll
-target_module PhotoViewerLoader.exe -nargs 2 -D "C:\users\john\Desktop
DynamoRIO-Windows-6.2.0-2\bin32" -target_offset 0x1040 -t 10000 --
PhotoViewerLoader.exe @@
corpus minimization tool for WinAFL by<EMAIL_ADDRESS>Based on
WinAFL by<EMAIL_ADDRESS>Based on AFL by<EMAIL_ADDRESS>usage: winafl-cmin.py [-h] -i dir -o dir [-n] [--working-dir dir] [-v]
[-covtype {edge,bb}] [-call_convention {stdcall,fastcall,thiscall,ms64}]
-coverage_module module -target_module module -nargs nargs -D dir
(-target_method method | -target_offset rva offset) [-t msec] [-f file]
[-C] [-e] [-w n] ...
winafl-cmin.py: error: one of the arguments -target_method -target_offset
is required
Running WinAFL with the -target_offset is working fine so I can't really
tell what I'm missing here. Any help would be appreciated!
Thanks,
doria90
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ivanfratric/winafl/issues/65, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABaHRTxPF_vC3GxjF6OQMRluLRUfGTCMks5sTDvKgaJpZM4Onkns
.

Yep. It works! silly me.. Thanks!!

Awesome! Feel free to close the issue then :-).
Cheers
2017-08-03 1:31 GMT-07:00 doria90<EMAIL_ADDRESS>
Yep. It works! silly me.. Thanks!!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ivanfratric/winafl/issues/65#issuecomment-319904275,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABaHRfpAURhqkeIgv6tPoUCuawWhER3Qks5sUYVNgaJpZM4Onkns
.


Updated JDK8-openj9 Problem List

All the links to issues that have perm excluded tests from openj9 were not updated in the JDK8-openj9 problem list. This PR intends to fix that

I will do the same for JDK13 on Monday

Also includes the JDK13-openj9 updates in the commit above


Add information about MiniTestPlugin to README

Before, there was no mention of the MiniTestPlugin in the readme (see confusion in #136).
At least for me, resetting the Capybara session between tests wasn't necessary; all it took was including the minitest plugin.
@matt-riemer any thoughts/comments?

Thanks @Mavvie for the contribution.  Whilst I feel like we should resolve the root problem, this is a sensible step to help others, so will merge.


doc: Update README about dependencies property

Explicitly state that the dependencies listed in the PluginSpec will be automatically installed in case they're missing.
This will happen only if a complete plugin name has been provided. (Relevant https://github.com/folke/lazy.nvim/commit/4bf771a6b255fd91b2e16a21da20d55f7f274f05)

Thank you for the suggesiton, but I don't think this is needed


User credential preferred

Even though Device Credential is an option on the GPO, the device credential gives error while auto-enrollment tasks running through the Task Scheduler. To avoid this error we need to choose the User Credential option from the dropdown to auto-enroll the device. The below line has been updated on the document.
5. Click Enable, and select User Credential from the dropdown Select Credential Type to Use, then click OK.

This PR closes the issue https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5543

GitHub pro tip (for future PRs):
if you include the text (example) "Closes #5543" at the end of the commit text (1-2 lines below the commit message/description), the referenced issue ticket will be closed automatically.
You can also use words like "Resolves" or "Fixes" if you prefer any of those instead of "Closes".
The important part is that the "Closes #...." message line is included in the initial PR commit.


issue about ofdm-transfer

Hello, I am using ofdm-transfer recently. The project is now read-only. I have encountered the same problem you left in the issue page. I would like to ask how is your current progress on this project and whether it can be successfully transmitted using bladerf? I'm using:
-bladerf （tx and rx)
-ubuntu 22.04

There are several versions of the program. There is one example of transmitting and receiving on the same machine using a bladeRF - I think that that is "ofdm_loopback05.grc" on -
https://github.com/righthalfplane/rfspace
uBuntu 22.04 was causing problems, but I think they are mostly cleared up - In the past, I had to destroy all copies of the SoapSDR stuff and gnuradio and install from source to get things going.
I shifted to uBuntu 23.10 and got things working there, but if you install CubicSDR it screws things up. When adding programs, remember to always start with -
sudo apt-get update
sudo apt-get upgrade
It does work on uBuntu with the bladeRF - Unfortunately, there is a huge list of things that can break it. Give it a try - If it does not work - post the output - perhaps, I can tell what is wrong.

hello,i mean the project is :https://github.com/glv2/ofdm-transfer
Do you remember? I saw your comment on the issue page and I had the same problem as you and wanted to know how you finally solved it.

Yes, Now I know which one you are talking about. I worked on that quite a while. He claimed that it worked, but I tried his exact setup and it did not work. It used a large number of frequencies, but the SDR's gain drops as the number of frequencies increases and the bandwidth decreases (I found this out latter). Another problem is the DC-OFFSET, I do not remember that there was any correction for that. There are many parameters here, It could be that his devices just happen to work ? His program uses several thousand frequencies, the example that worked (ofdm_loopback05.grc) only uses 12.

The problem page states that imprecise clocks can cause frequency offsets, If the offset between the center frequencies of the sender and the receiver is bigger than 1% of the OFDM signal  bandwidth, the receiver will probably not be able to decode the frames. So I used the same external clock source to clock both BladerFs, but I didn't receive any data at the receiver. Have you tried something similar before, or do you know what the problem is? Thanks for your answer!
Also I see you mentioned that you received the same five lines. What parameters are used, and what is the format of the file sent?


ts config alias does not work at all

I'm testing this lib, and find some problems.
I have a test folder with dependencies:

src/index.tsx: ["src/pages/page1/index.tsx"]
src/pages/page1/index.tsx: ["src/pages/page1/index.module.scss"]

But when I run yarn build which runs node scripts/build.js, madge listed dependencies of src/index.tsx as an empty array instead of including src/pages/page1/index.tsx
with extends in tsconfig:

without extends in tsconfig:

I installed madge globally, manually updated dependencies dependency-tree and detective-typescript, and seems it solves my task with tsconfig aliases

I had a similar issue and I managed to fix it by adding "baseUrl": "." to my tsconfig.json (despite this option being deprecated: https://www.typescriptlang.org/tsconfig#baseUrl)

I had a similar issue and I managed to fix it by adding "baseUrl": "." to my tsconfig.json (despite this option being deprecated: https://www.typescriptlang.org/tsconfig#baseUrl)

But there are already baseUrl : "src" in my config.

I installed madge globally, manually updated dependencies dependency-tree and detective-typescript, and seems it solves my task with tsconfig aliases

What are the respective versions did you update to manually?

Simply latest

I installed madge globally, manually updated dependencies dependency-tree and detective-typescript, and seems it solves my task with tsconfig aliases

What are the respective versions did you update to manually?

Simply latest

that's not work for me ... and adding "baseUrl": "."  to tsconfig.json work

I installed madge globally, manually updated dependencies dependency-tree and detective-typescript, and seems it solves my task with tsconfig aliases

What are the respective versions did you update to manually?

Simply latest

that's not work for me ... and adding "baseUrl": "."  to tsconfig.json work

Finally, i solved this problem with option  basedir. Cause I run madge cmd in another package dir of monorepo,  it work right

@huntye1 I always set this option)
Now it work from the box or need to update dependencies?

I think I'm running into the same issue, what did you set basedir to that solved it? Madge works with vue as well unless I run madge from outside the project's directory.


React Native support

Are there means of modifying (or plans to) this library in order to support RN environment along with Node.js one? I tried with a babel plugin rewrite-require to replace Node-tied dependencies (like fs, http etc) with their react native counterpart, but some things, notably cookies and the library used to make the request (Node request-promise vs RN fetch) don't really get along (at least in my hands 😅
Even simple suggestions/clues are greatly appreciated

@Brucbbro Did you manage to get this to work with React Native?

Hey @arminsal1 sadly i didn't get anything out of my attempts 😢


add get_fields method to Event

Thank you for your contribution! See morg's and my comments.
I also updated the  pull request title a bit, as it's not so common to have line numbers in commit titles.


provide guidance on rebuilding sound banks

need to rebuild sound banks if Wwise versions doesn't match the sample project.  remind the user that they may need to do this.

@NoelCross : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Add support for hierarchical menus

Newly the following hierarchical menu is supported:
var docSpec={
  elements: {
    item: {
      menu: [{
        caption: "Add attribute",
        menu: [
          {caption: "Add @name=\"something\"", ...},
          {caption: "Add @desc=\"something\"", ...}
        ]
      }, {
        caption: "Delete this <item>",
        action: Xonomy.deleteElement
      }, {
        caption: "New <item>",
        menu: [
         {caption: "New <item> before this", ...},
         {caption: "New <item> after this", ...}
        ]
     }],
    }
  }
};

New function Xonomy.internalMenu() is called from all the Xonomy.[element|attribute|inline]Menu handlers and performs all the common stuff. It accepts array of indices and transforms it to a hierarchical menu item lookup code and also distinguishes between menu and submenu div classes.
CSS stylesheet is updated to support hierarchical menus.

Something like this had been at the back of my mind for a long time. Thanks for doing it so I don't have to!


Use /bin/sh instead of bash for more portability

I did a cursory glance of the scripts, I didn't see any bashisms. Improves build on OpenBSD.

Thanks! Merged in.


Integrate graphql-serve with graphback

The graphql-serve package uses outdated version of the graphback packages. It needs to be ported to the newer versions of said packages.
Work In progress:

[x] Add serve and print schema commands
[x] Update Readme
[ ] Integrate gql serve with graphback-cli
[ ] Update docs
[ ] Add tests
[ ] Improve CLI
[ ] General code cleanup

I am working on this issue

Some of the work has been done in #830
I will continue to work on some of these in another PR

Package has been set to private true. Once we fix readme we can remove it in order to release it

This looks to be done, but feel free to reopen if I am wrong.


Add validation analysis

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.674%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
388

Relevant Lines:
392

💛  - Coveralls


No icon when I search for something

Hello,
Is it normal that I have no icon of applications that I search? In place of the icon, I have this:

(like an error for the icon)
Thank you!
Maxime

I have the same issue. It appeared after making the latest update (updating from 0.6 to 0.6.1).

Yep, same here on Windows 10.

i'm fixing this issue now

This issue has been resolved with v0.6.2
Please try it.

Thank you, it works !


switch.eh123456_smart_charging does not reflect smart charging state correctly

The problem
If I disable smart charging by manipulating switch.eh123456_smart_charging in HA (by toggling the switch in the lovelace UI), the charger correctly disables smart charging (LEDs go white), but the HA switch reverts (after 0-3 seconds or so) to on - thereby incorrectly reflecting the smart charging status of the charger.
Toggling the HA switch again (to off) does not affect the charger (it already indicates NOT smart charging - the LEDs are white).
Toggling the HA switch once more (to on) makes the charger change to smart charging (LEDs go blue) and the HA switch stays on.
It seems the problem only occurs when switching smart charging off from the HA UI.
Version of Easee integration having the issue?
easee-0.9.45
Version of Home Assistant Core having the issue?
core-2022.10.4
Anything in the logs that might be useful for us?
No response
Additional information

Issue raised twice by mistake. Closing this one


Isn't this setting "enabled" by default?

Isn't this setting "enabled" by default?
https://docs.microsoft.com/en-us/microsoftsearch/result-cluster#enable-result-clusters
Enable result clusters
The result cluster experience is turned off by default.
Follow these steps to turn on the experience at the organization level:
In the Microsoft 365 admin center, go to Verticals.
Select the All vertical, then enable Show connector results.
https://lynx.office.net/messagecenter/MC253495 commented This is on by default.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 57c18e36-9714-5e35-de06-2a252e743cbd
Version Independent ID: 6548815c-be43-a8f6-4fa8-ef0a059cc109
Content: Connectors result cluster
Content Source: MicrosoftSearch/result-cluster.md
Service: mssearch
GitHub Login: @Manusi
Microsoft Alias: manusi

Hi,
Thanks for your query.
The default Admin option for showing Connector Results in "All" tab for MSO and MSB is presently disabled. We will be changing the default option to "ON" by early next month and the same is communicated through the MC post.
If you would like to see the Connector results in "All" tab before that, you may enable this option via the Admin panel using the instructions shared here: https://docs.microsoft.com/en-us/microsoftsearch/result-cluster#enable-result-clusters
Thanks.

Thank you for your prompt reply. Now, I got it.  But if so, it would be grateful if you can change this article to the default option "on" by early next month, too.
FYI.. currently, this enable/disable option seems to be not working even I change this option thru the above metioned Admin panel, thought..
kind regards,

Thank you. We are working on the change and we will update here as soon as the default option is changed to "ON".
However, with the manual option change, the Connector results should show in All tab in MSO and MSB (with other conditions being met), could you please share your issue to this email id<EMAIL_ADDRESS>so we can help and take a look.
Thanks.

We will be closing this issue as the resolution was shared over email. Please feel free to reach out to us at<EMAIL_ADDRESS>for any queries.  Thanks.


Feature request to add Emonet model

Do you plan to add Emonet to the Facetorch repository?
If so, it would be great!!

Thank you for the suggestion. Unfortunately, Emonet's non-commercial license is incompatible with facetorch's MIT license. As such, we cannot integrate it.


HoistField Cleanups

I had spent a while a few weeks ago trying to clean up HoistFields and their docs, but then I didn’t get to complete that and I think the branch I openeed is probably pretty dead now in terms of being usable for merging. But that said, unless something has changed there is probably still some good cleanup I would like us to do.
I made two commits on that branch - https://github.com/exhi/hoist-react/commits/fieldCodeCleanups - I think they show pretty much what I was trying to accomplish in terms of docs / comments / code style.
Basically when I started really looking at those classes there were a bunch of inconsistencies with what was documented and how.
A bigger change I would like to consider was removing the delegateProps notion from HoistField, as this was rather opaque, made the propType-based docs incomplete, and wasn't being used consistently.

Let's go ahead and remove the delegate props and see how things work without it? It was just an experiment of mine and always intended to just be an implementation helper for authors of Hoist Fields themselves, and never something intended to be visible to Application.
Was mainly trying to DRY up things in the implementation.

As part of this, would also like to document / formalize the requirements and handling of record IDs. See discussion within #488, including potentially problematic code that currently generates missing IDs using the index of the raw data object within the records collection:
https://github.com/exhi/hoist-react/blob/0dc739d2ddeeff0ba5aa8235afd9ee07e57bb085/data/LocalStore.js#L114

Grabbing this ticket back as part of my ongong docs work.

I have a pretty major refactor here in progress that flattens out this whole hierarchy, and simplifies the documentation.  Also removes the much beloved delegateProps.

Closing this -- Anselm wrangled these changes into the product earlier this fall.
Created the following to capture the one somewhat unrelated item that was not dealt with here:
https://github.com/exhi/hoist-react/issues/844


Run tests against Python 3.11 and add trove classifier

released on 2022-10-24, see https://pythoninsider.blogspot.com/2022/10/python-3110-is-now-available.html

Thanks!


error CS0425 / Serialize() implementation

I get an error with the example code.
[MemoryPackable]
public partial class Person
{
    public int Age { get; set; }
    public string Name { get; set; }
}

Person.MemoryPackFormatter.g.cs(55,24,55,33): error CS0425: The constraints for type parameter 'TBufferWriter' of method 'Person.Serialize<TBufferWriter>(ref MemoryPackWriter<TBufferWriter>, scoped ref Person?)' must match the constraints for type parameter 'TBufferWriter' of interface method 'IMemoryPackable<Person>.Serialize<TBufferWriter>(ref MemoryPackWriter<TBufferWriter>, scoped ref Person?)'. Consider using an explicit interface implementation instead.

[global::MemoryPack.Internal.Preserve]
    static void IMemoryPackable<Person>.Serialize<TBufferWriter>(ref MemoryPackWriter<TBufferWriter> writer, scoped ref Person? value)
    {

        if (value == null)
        {
            writer.WriteNullObjectHeader();
            goto END;
        }

        writer.WriteUnmanagedWithObjectHeader(2, value.@Age);
        writer.WriteString(value.@Name);

    END:

        return;
    }

If I try to implement  IMemoryPackable<Person> directly TBufferWriter is constrained to IBufferWriter<byte> which doesn't happen in the autogenerated code.
public partial class Person : IMemoryPackable<Person>
{
    public int Age { get; set; }
    public string Name { get; set; }

    public static void Serialize<TBufferWriter>(ref MemoryPackWriter<TBufferWriter> writer, ref Person? value) where TBufferWriter : IBufferWriter<byte>
    {
        throw new NotImplementedException();
    }

    public static void Deserialize(ref MemoryPackReader reader, ref Person? value)
    {
        throw new NotImplementedException();
    }
}

which version(.NET / IDE / TargetFramework) do you use?

Microsoft Visual Studio Community 2022 (64-bit) - Preview
Version 17.5.0 Preview 1.0

https://github.com/espenrl/issue-repro/tree/main/memorypack-cs0425
This is a dotnet new maui template showing the error. I tested that the error doesn't occur with dotnet new console.

It seems bug of MAUI's compilation process.
For explicit implementations, constraint is inherited.
In fact, if you copy-paste the generated code, it will compile!
Yet, only in the case of Source Generator, I get a puzzling error.
The workaround is to create a net7 project where the generative types are placed and then referenced by the MAUI project.

I know MAUI ties into MSBuild, but I can't see how it would affect the compiler. I'll look into it when I have time. Thanks for your feedback.

only <TargetFrameworks>net7.0-windows10.0.19041.0</TargetFrameworks> fails.
I don't know the reason.

It works with the latest MAUI tooling, both with Visual Studio and dotnet build. Closing the issue.
Microsoft Visual Studio Community 2022 (64-bit) - Preview
Version 17.5.0 Preview 5.0
MAUI .NET7 SR3


Common: update READMEs markdown in according with CommonMark

Hey @oguzhanunlu, could you please also fix another READMEs, they're plural in ticket name.


added missing semicolon after calling exporter function

fixes issue reported in #3376

:+1:

:+1: