text:
inconsistent row size

Hello,
I'm trying to use roast in order to project alignments of 30ish plant species.
I get the error 'inconsistent row size' and afterwards that the corresponding multiz command has failed.
An example:
multiz M=1  /tmp/_MZ_6588_left.maf22 /tmp/_MZ_6588_right.maf22 0 /tmp/_MZ_6588_U1 /tmp/_MZ_6588_U2 >> /tmp/_MZ_6588_MZ22
multiz.v11.2: line 5803179 of /tmp/_MZ_6588_right.maf22: inconsistent row size
roast.v3: command 'multiz M=1  /tmp/_MZ_6588_left.maf22 /tmp/_MZ_6588_right.maf22 0 /tmp/_MZ_6588_U1 /tmp/_MZ_6588_U2 >> 254 /tmp/_MZ_6588_MZ22' failed
This happens for different versions of alignments (containing different species). The weird thing is this error of inconsistency can show up but the roast continues.
Would you be kind to lead me in any kind of direction as to how to troubleshoot this?
For context, I made the alignment using a pipeline that uses the last aligner, and the roast is using toast2.maf files.
Thank you!

(I'm pasting here a separate email where this was reported. I assume this is from the same person, but the messages have some differences so for the sake of completeness I'm copying that email here.)
I was wondering if you are able to help me solve an error message I encountered using multiz.
I am aligning multiple avian genomes to a reference genome (L. tetrix) to create a .maf file. I have used LASTZ to align all query genomes to the reference genome, and am now using roast to generate the multiple species alignment file. However, my pipeline gets stuck at an error saying that there is an inconsistent row size. This is the end of the log file:
multiz M=1  /tmp/_MZ_2339053_left.maf8 /tmp/_MZ_2339053_right.maf8 0 /tmp/_MZ_2339053_U1 /tmp/_MZ_2339053_U2 >> /tmp/_MZ_2339053_MZ8
multiz.v11.2: line 117256 of /tmp/_MZ_2339053_right.maf8: inconsistent row size
roast.v3: command 'multiz M=1  /tmp/_MZ_2339053_left.maf8 /tmp/_MZ_2339053_right.maf8 0 /tmp/_MZ_2339053_U1 /tmp/_MZ_2339053_U2 >> /tmp/_MZ_2339053_MZ8' failed
I am using the msa_pipeline to generate the roast.maf file, so see their documentation for the exact software used in the pipeline to get to the roast call.
You can check out the /_MZ_2339053_right.maf8 file here if you like: https://wetransfer.com/downloads/08f544bf991576876fa85909bc8dedfb20221111084513/a7d63d8cf143bd636073d57ab9930cca20221111084529/376830
With the limited details I’ve provided you with I realize this is not a reproducible example, but at this stage I am wondering if you could explain to me what this error message of inconsistent row size means, so I can try to identify the problem in my data myself?
Many thanks in advance,

ruttix wrote:

For context, I made the alignment using a pipeline that uses the last aligner, and the roast is using toast2.maf files.

To make sure I understand you, you used the pairwise aligner at gitlab.com/mcfrith/last ? multiz is more commonly used with lastz. I don't know yet whether this is relevant to the issue. But I don't want to try to figure out if last is the issue if you aren't in fact using it.

The emailer whose name I have not revealed wrote:

You can check out the /_MZ_2339053_right.maf8 file here if you like:
https://wetransfer.com/downloads/08...

Thanks. I followed the link and it wants me to sign in. Not sure yet if I can view that for free or not. Will check on that later.

multiz.v11.2: line 5803179 of /tmp/_MZ_6588_right.maf22: inconsistent row size
OR
multiz.v11.2: line 117256 of /tmp/_MZ_2339053_right.maf8: inconsistent row size

The most likely cause is that the output file from one process was truncated. And then when it was used downstream a sanity check triggered.
What the error message specifically means is that two nucleotide strings (including letters and hyphens) in the same alignment block don't have the same length. Looking at "the simple example" of MAF at http://genome.ucsc.edu/FAQ/FAQformat#format5 , the nucleotide strings in a block all have the same length.
The line number given in the error message would be the number of the line where the error was detected. If it's a file on disk, you should be able to look at that line and the lines preceding it in the same alignment block, and see the problem. My best guess is that this will be the last line in the file, because the file was truncated.
If it isn't the last line, you should notice the difference in lengths. This would indicate some problem with whatever created the file.
That's my best guess. Feel free to post followups.

The emailer whose name I have not revealed wrote:

I am using the msa_pipeline ...

Thanks (very much!) for including that. At this point I've only briefly glanced at it. But that will be helpful is the root of the problem is something other than file truncation.

Thanks a lot Bob for your help, I'm the person from the email and thought it would be easier to respond on here.
Your explanation of the error message makes sense in theory and that's also how I interpreted it. Maybe I understand it wrong, but I think that would mean that the alignments from the different species (both target/reference and query ones) do not have the same length. However, this is the case for most of my alignment blocks and those don't show any errors.
In case you cannot open the wetransfer file, I copied the important information below (i.e. the last few code blocks of the file that contain the error). Here are the last three alignment blocks from my .maf file, for which the error code happens at line 8 in this case. I just added these line numers for ease of referencing to them on here, they're not in the original file. I also shortened the sequences by replacing the rest with ***.
1 score=53327.0
2 Lyrurustetrix.ScEsiA3_19038;HRSCAF=23783 37999201 688 + 109349036 AAAAAAGTG***
3 Chrysolophuspictus.KZ861216.1             2082782 663 -   2160913 AAAAAAGTG***

4 a score=94939.0
5 s Lyrurustetrix.ScEsiA3_19038;HRSCAF=23783 37999966 1151 + 109349036 TTTTTTTTTTCCCCT***
6 s Chrysolophuspictus.JRFT01062866.1               2 1167 +      2082 TTTTTTTTTTCCCCTC***

7 a score=1575323.0
8 s Lyrurustetrix.ScEsiA3_19038;HRSCAF=23783 38001117 19335 + 109349036 AGGTG***
9 s Chrysolophuspictus.KZ861216.1             2084670 19381 -   2160913 AGGTATG***

As described on UCSC (http://genome.ucsc.edu/FAQ/FAQformat#format5), the third column refers to the length of the aligning region in the source sequence (which I think is the one that the error message refers to as being different in length, in block 1 688 and 663, in blcok 2 1151 and 1167 and in block 3 19335 and 19381). As you can see, these lengths are different for all three alignment blocks, not just the last one with the error.
So long story short, I'm still not sure what the error really refers to and therefore am not sure where to start with solving the problem. Do you have a better idea after seeing this example?
Some additional info: I tried leaving out species Chrysolophus pictus but when I do this, error messages from alignments of other species show up.
I'm currently trying to align with minimap2 rather than lastz to see if it makes a difference in the roast call. Will keep you updated!
Thanks again,
Rebecca

rshuhuachen posted:

As described on UCSC (http://genome.ucsc.edu/FAQ/FAQformat#format5), the third column refers to the length of the aligning region in the source sequence ...

Right, but that's the length of the aligning region, not the length of the alignment text. The text (usually) includes some hyphens. While I don't see anything in the MAF spec that requires text to have the same length for all components in a block, the block doesn't make sense as a multiple alignment if some text has a different length.
I'll create a free wetransfer account this morning and see if I can access the example you linked.

Ruttix posted:

I'm not sure what do you mean by difference in length - the alignments are indeed not all the same in length. What does roast check triggering this?

See the reply to rshuhuachen I posted about ten minutes ago.

I am indeed using the last aligner, and not lastz ...

That should be fine. I haven't used last much myself, other than a few small test cases several years back. Martin Frith is top notch and I expect last is as well.

@rshuhuachen I've downloaded your example, _MZ_2339053_right.maf8. It does appear to have been truncated. Below is what I see at the end of the file. The final line abruptly stops at CATAAT and there isn't even a newline character after it.
Multiz reported the problem being at line 117256 which is one off from where I'm seeing the problem. I can't explain that. It's possible multiz starts counting from zero; it's hard to tell looking through the source code.
So now the question is what caused the file to be truncated. Usually this is some sort of system issue. Possibly a process moving the file from one disk to another was terminated, or such process wasn't finished (e.g. stalled) before a downstream process started reading the file. Or perhaps the process creating the file in the first place was terminated for some reason.
I don't know exactly what created _MZ_2339053_right.maf8. I think your best bet is to find that command line, rerun it, and see if the new result has more than 117257 lines.
117251 a score=94939.0
117252 s Lyrurustetrix.ScEsiA3_19038;HRSCAF=23783 37999966 1151 + 109349036 TTTTTT***
117253 s Chrysolophuspictus.JRFT01062866.1               2 1167 +      2082 TTTTTT***
117254
117255 a score=1575323.0
117256 s Lyrurustetrix.ScEsiA3_19038;HRSCAF=23783 38001117 19335 + 109349036 AGGTGC***CATAAT***(another ≈17K characters here)
117257 s Chrysolophuspictus.KZ861216.1             2084670 19381 -   2160913 AGGTAT***CATAAT

Thanks @rsharris, I was just about to post something similar. Indeed the lengths including the hyphens/mismatches are not the same for the alignment block that throws the error.
If your suspicion is that maybe it's a system issue rather than a problem with the sequences, potentially it has to do with the storage space required in the /tmp/ directory? I will play around with this and let you know! Thanks a lot for all your help

@rshuhuachen

... potentially it has to do with the storage space required in the /tmp/ directory?

Yeah, that'd be a good thing to check. IIRC the default size of /tmp on most linux systems is pretty small by bioinformatics standards.

authors: Ruttix rsharris rshuhuachen

repo: multiz/multiz


text:
支持异体字关联检索

比如搜索「闲适」，那么将匹配「闲」和「适」的所有异体字组合，结果为： [閑閒闲𫔮间間][适適𨓈]

能提供一个词典用于测试吗？

https://forum.freemdict.com/

source: gharchive/issue

authors: asgsdbrseg mumu-lhl

repo: mumu-lhl/Ciyue

license: MIT

license_type: permissive

license_source: github-api


text:
how to get grott working for a beginner ?

hello muppet3000
i have the following question  , i am trying to understand what to do / prepare so i can use the grott application .
this weekend i was trying to get it done the following way.
i am running home assistant OS on a thin client which is working fine. to run grott i have picked up another thin client and installed debian 12 on it and the docker desktop
then i get lost in the things i think i need to do .  run grott and mqtt on this debian docker is already a problem
i think i am doing it wrong , can you help me out and make a manual or something so i can make it happen ?
what is the best home assisant installation needed to use grott ?(i need hacs and addons so i think  the OS is the only one )
is it possible to run all of the needed software on 1 thin client or do i need a more powerfull PC
and if so  , how ?
i was happy with the integration you have made and with my 2 hours intervall it worked perfect , never a problem untill now.
So i realy want to go to your "new" growatt solution but i do not understand how to start
hoping you find some time to explaine it , thinking there are more people who would like it this way but also do not understand how to realize it .
thanks

Hi @annbuw - If you've already got HA running using HA OS I'd really recommend using the @egguy home-assistant add-on - this one: https://github.com/egguy/grott-home-assistant-add-on.
It will run Grott for you and you can just point your Inverter directly at that for the data to be published.
It will also run MQTT for you as well.
I'm going to update my documentation to point to that as an example.
The extra thing to do is when you're installing that add-on is to tweak the options show on this image: https://github.com/muppet3000/homeassistant-grott/issues/16#issuecomment-1623172859
You need to enable "Enable Grott MQTT" option and to disable the "Home Assistant plugin" option. After that my integration should then be able to be installed and make use of the data being pushed into MQTT from grott.
If you have any problems let me know, I'd love to get some feedback from a 'beginner' (bonus points for screengrabs) so that I can update the documentation.

hello i have installed everything like you told me
now i have to change te ip adres in the dataloggers
what ip adres do i put in it and do i have to use a port
is it my home assistant adress with 8123 port ?

If you're running the Grott Home Assistant Add On then it'll be the IP address of your Home Assistant instance on port 5279 (which is the default for your data logger anyway)

thanks , so alone the ip adress is enough
i will try it tomorrow when the sun shines again !!

Hi muppet, didnt want to open a new ticket for this reason. Iam a little confused, iam a newbie too.
Following setup:

HA on HA OS
Mosquitto broker
installed the egguy grott add on, named "Grott edge - Home Assistant native MQTT integration"
-- Enable grott MQTT | disable ha plugin
installed your HA Grott
Set interval on my Shine Stick to 1 minute and set the ip from my ha without ending :8123 (default port in the config is 5279)
-- Stick is online

But i didnt get data in HA, Growatt Server didnt get data as well.
Log from Grott edge (egguy):

Log from mosquitto:

what am i missing?

muppet3000
it seems to work , YES , i have 4 inverters and the MOD 5000TL3-X is not giving the right values .
i read about change something in grott .ini but when i look in it there is nothing in this file , it is empty. what to do about it?
the other 3 are older 1fase inverters and they are giving the normal values.
in the phone app the inverters are green normal so i think the data is also going to the server , so that should work too.
do i need to delete the old integration , if yes , i believe i loose al the histery data ? correct ?
is there a way to keep that , ?
thank you sofar

do i need to delete the old integration , if yes , i believe i loose al the histery data ? correct ? is there a way to keep that , ?

https://gist.github.com/langestefan/acbf7e42b15b302e9aacc08663039e57#1-im-replacing-my-solar-inverter-energy-meter--how-can-i-retain-my-energy-dashboard-data
I didnt know if its work, i let my old integration installed for the data. ;-)

hello muppet3000
any idea how i should fix the wrong data from the mod inverter ?

In the grott.ini file you need to set the invtype variable.
The default grott.ini file looks like this: https://github.com/johanmeijer/grott/blob/master/examples/grott.ini
You need to set the correct one for your system, the possible values are: default,sph,spf,max, tl3 so I think you need to use the tl3 one.

Just wondering, if I disable the Home assistant plugin in mqtt and enable the grott mqtt, will I then break the zigbee2mqtt addon?

Just wondering, if I disable the Home assistant plugin in mqtt and enable the grott mqtt, will I then break the zigbee2mqtt addon?

I'm unsure what you mean. MQTT is a message broker it is a service in it's own right. In the example you've given both Zigbee and Grott can publish to the same MQTT system and not interfere with each other. If you stop Grott it will have no affect on Zigbee and vice versa.
The question you've asked though seems a little backwards: "If I disable the home assistant plugin in mqtt" - There is no home assistant plugin for MQTT, so I'm not sure what you're asking here. Are you saying there is an add-on you're running in home-assistant called MQTT? If so - don't stop it, that's what Zigbee and Grott are publishing to.
Does that make more sense?

Hi @muppet3000 . I dont know why, but even with the configurations that you mention my Grott integration doesn't work.
Did you know why? Look:

I have the MQTT working:

How did you get the data showing in the MQTT area of Home Assistant? I'm not sure what's pushing that into there.
Also, leave the ID in the "device information" on your first image you posted as a "+" and see what happens.

Well, i have the Grott HA Addon

Then i have the MQTT integration that "Auto create" the devices inside HA, based on the MQTT packets received by the MQTT Addon.

Example:

I don't know if that's what you wanted to know.
Ps: I've already tried leaving it with just + but it didn't have any effect either.

I have the same issue as beped above

Hi, if you want the addon to only work with grott HACS, check enable grott MQTT and disable HA integration The MQTT devices should be marked as disabled, and grott HACS is going to receive the message.

I already did that, it didn't work either, you can see from the screenshot I sent above.

There was an update today from the Grott Addon, after the update it worked.

Thanks for the assist @egguy - Are you ok if I drop you an email to collaborate more? I think between us we can make all of this a lot easier to use?

My MQTT is full of entities and are updated when home assistant plugin in enabled in the ini however, I only have 8 entities per datalogger in Grott. Any ideas?

My MQTT is full of entities and are updated when home assistant plugin in enabled in the ini however, I only have 8 entities per datalogger in Grott. Any ideas?

Disable the ha_plugin in the ini
Configure MQTT broker in Home Assistant - https://github.com/muppet3000/homeassistant-grott/blob/main/docs/setup/homeassistant-mqtt-broker.md
Install the integration that you've logged this bug in: https://github.com/muppet3000/homeassistant-grott

After that you should have all the stats showing under the grott integration in Home Assistant.

Sorry muppet I should have been a bit more clear.
When I disable the ha_plugin the Grott integration (that I logged this bug in) only shows 8 entities per datalogger where if I enable the ha_plugin and check MQTT there are many entities from the datalogger.
I have setup everything like you mentioned above.

Hi, if you want the addon to only work with grott HACS, check enable grott MQTT and disable HA integration The MQTT devices should be marked as disabled, and grott HACS is going to receive the message.

Have you read this comment from @egguy : https://github.com/muppet3000/homeassistant-grott/issues/44#issuecomment-1748798817
check enable grott MQTT and disable HA integration The MQTT devices should be marked as disabled, and grott HACS is going to receive the message.
I think you've got things in a weird mixed up state currently. You're nearly there though.

hello muppet3000
i still have now reading from the mod-5000 inverter
i have tried a few things but nothing changed in the data
the only thing that is in my grott.ini is
[Generic]
inverterid = REHBCF???? (inverter serial number)
invtype = tl3
i have 4 inverters but the other 3 are fine so i did not name them in the ini file.
must there be more in the ini file for it to work ?
everything is furter okay
thanks

You don't need to list the inverter IDs in the ini file as far as I know.
Can you please share the logs from Grott so we can see what's happening with the data from the inverter?

2023-10-10 08:00:38.541 DEBUG (MainThread) [custom_components.grott.sensor] Received message: energy/growatt
2023-10-10 08:00:38.541 DEBUG (MainThread) [custom_components.grott.sensor] Payload: {'device': 'REHBCF908X', 'time': '2037-08-20T22:36:52', 'buffered': 'no', 'values': {'datalogserial': 'XGD6CJD2RN', 'pvserial': 'REHBCF908X', 'pvstatus': 0, 'pvpowerin': 0, 'pv1voltage': 2295, 'pv1current': 0, 'pv1watt': 0, 'pv2voltage': 2295, 'pv2current': 0, 'pv2watt': 0, 'pvpowerout': 0, 'pvfrequentie': 0, 'pvgridvoltage': 0, 'pvgridcurrent': 0, 'pvgridpower': 0, 'pvgridvoltage2': 0, 'pvgridcurrent2': 0, 'pvgridpower2': 0, 'pvgridvoltage3': 0, 'pvgridcurrent3': 0, 'pvgridpower3': 5002, 'totworktime': 0, 'pvenergytoday': 4040, 'pvenergytotal': 263262168, 'epvtotal': 0, 'epv1today': 24352, 'epv1total': 11694350, 'epv2today': 0, 'epv2total': 15788, 'pvtemperature': 323, 'pvipmtemperature': 0, 'battery1soc': 0}}
2023-10-10 08:00:38.541 DEBUG (MainThread) [custom_components.grott.sensor] Configured to look for device: + (+ means all)
2023-10-10 08:00:38.541 DEBUG (MainThread) [custom_components.grott.sensor] Configured to include calculated values: False
2023-10-10 08:00:38.541 INFO (MainThread) [custom_components.grott.sensor] PROCESSING UPDATES
2023-10-10 08:00:38.541 INFO (MainThread) [custom_components.grott.sensor] 32 sensors for processing
2023-10-10 08:00:38.542 DEBUG (MainThread) [custom_components.grott.sensor] raw_mqtt_sensors - matched on REHBCF908X
2023-10-10 08:00:38.542 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV Serial, unique id: grott_rehbcf908x_mqtt_001
2023-10-10 08:00:38.542 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Datalog Serial, unique id: grott_rehbcf908x_mqtt_002
2023-10-10 08:00:38.542 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV Status, unique id: grott_rehbcf908x_mqtt_003
2023-10-10 08:00:38.542 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV-All Power, unique id: grott_rehbcf908x_mqtt_004
2023-10-10 08:00:38.542 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Voltage, unique id: grott_rehbcf908x_mqtt_005
2023-10-10 08:00:38.543 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Current, unique id: grott_rehbcf908x_mqtt_006
2023-10-10 08:00:38.543 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Power, unique id: grott_rehbcf908x_mqtt_007
2023-10-10 08:00:38.543 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Voltage, unique id: grott_rehbcf908x_mqtt_008
2023-10-10 08:00:38.543 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Current, unique id: grott_rehbcf908x_mqtt_009
2023-10-10 08:00:38.543 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Power, unique id: grott_rehbcf908x_mqtt_010
2023-10-10 08:00:38.543 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Output Power, unique id: grott_rehbcf908x_mqtt_011
2023-10-10 08:00:38.544 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Grid Frequency, unique id: grott_rehbcf908x_mqtt_012
2023-10-10 08:00:38.544 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Single/First Phase), unique id: grott_rehbcf908x_mqtt_013
2023-10-10 08:00:38.544 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Single/First Phase), unique id: grott_rehbcf908x_mqtt_014
2023-10-10 08:00:38.544 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Single/First Phase), unique id: grott_rehbcf908x_mqtt_015
2023-10-10 08:00:38.544 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Second Phase), unique id: grott_rehbcf908x_mqtt_016
2023-10-10 08:00:38.544 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Second Phase), unique id: grott_rehbcf908x_mqtt_017
2023-10-10 08:00:38.545 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Second Phase), unique id: grott_rehbcf908x_mqtt_018
2023-10-10 08:00:38.545 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Third Phase), unique id: grott_rehbcf908x_mqtt_019
2023-10-10 08:00:38.545 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Third Phase), unique id: grott_rehbcf908x_mqtt_020
2023-10-10 08:00:38.545 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Third Phase), unique id: grott_rehbcf908x_mqtt_021
2023-10-10 08:00:38.545 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Time Since Commissioned, unique id: grott_rehbcf908x_mqtt_022
2023-10-10 08:00:38.545 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Power Generation - Today (pvenergytoday), unique id: grott_rehbcf908x_mqtt_024
2023-10-10 08:00:38.546 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Power Generation - Total (pvenergytotal), unique id: grott_rehbcf908x_mqtt_071
2023-10-10 08:00:38.546 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Energy - Today, unique id: grott_rehbcf908x_mqtt_026
2023-10-10 08:00:38.546 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Energy - Total, unique id: grott_rehbcf908x_mqtt_027
2023-10-10 08:00:38.549 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Energy - Today, unique id: grott_rehbcf908x_mqtt_028
2023-10-10 08:00:38.549 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Energy - Total, unique id: grott_rehbcf908x_mqtt_029
2023-10-10 08:00:38.549 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV-All Energy - Total, unique id: grott_rehbcf908x_mqtt_030
2023-10-10 08:00:38.549 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Temperature, unique id: grott_rehbcf908x_mqtt_031
2023-10-10 08:00:38.550 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X IPM Temperature, unique id: grott_rehbcf908x_mqtt_032
2023-10-10 08:00:38.550 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Last data update, unique id: grott_rehbcf908x_mqtt_099
2023-10-10 08:02:18.432 DEBUG (MainThread) [custom_components.grott.sensor] Received message: energy/growatt
2023-10-10 08:02:18.432 DEBUG (MainThread) [custom_components.grott.sensor] Payload: {'device': 'REHBCF908X', 'time': '2037-08-08T19:20:24', 'buffered': 'no', 'values': {'datalogserial': 'XGD6CJD2RN', 'pvserial': 'REHBCF908X', 'pvstatus': 0, 'pvpowerin': 0, 'pv1voltage': 3296, 'pv1current': 0, 'pv1watt': 0, 'pv2voltage': 2400, 'pv2current': 0, 'pv2watt': 0, 'pvpowerout': 0, 'pvfrequentie': 0, 'pvgridvoltage': 0, 'pvgridcurrent': 0, 'pvgridpower': 0, 'pvgridvoltage2': 0, 'pvgridcurrent2': 0, 'pvgridpower2': 0, 'pvgridvoltage3': 0, 'pvgridcurrent3': 0, 'pvgridpower3': 5001, 'totworktime': 0, 'pvenergytoday': 4040, 'pvenergytotal': 263327707, 'epvtotal': 39, 'epv1today': 24352, 'epv1total': 11694350, 'epv2today': 21, 'epv2total': 15788, 'pvtemperature': 370, 'pvipmtemperature': 0, 'battery1soc': 0}}
2023-10-10 08:02:18.432 DEBUG (MainThread) [custom_components.grott.sensor] Configured to look for device: + (+ means all)
2023-10-10 08:02:18.432 DEBUG (MainThread) [custom_components.grott.sensor] Configured to include calculated values: False
2023-10-10 08:02:18.433 INFO (MainThread) [custom_components.grott.sensor] PROCESSING UPDATES
2023-10-10 08:02:18.433 INFO (MainThread) [custom_components.grott.sensor] 32 sensors for processing
2023-10-10 08:02:18.433 DEBUG (MainThread) [custom_components.grott.sensor] raw_mqtt_sensors - matched on REHBCF908X
2023-10-10 08:02:18.433 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV Serial, unique id: grott_rehbcf908x_mqtt_001
2023-10-10 08:02:18.434 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Datalog Serial, unique id: grott_rehbcf908x_mqtt_002
2023-10-10 08:02:18.434 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV Status, unique id: grott_rehbcf908x_mqtt_003
2023-10-10 08:02:18.434 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV-All Power, unique id: grott_rehbcf908x_mqtt_004
2023-10-10 08:02:18.434 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Voltage, unique id: grott_rehbcf908x_mqtt_005
2023-10-10 08:02:18.435 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Current, unique id: grott_rehbcf908x_mqtt_006
2023-10-10 08:02:18.435 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Power, unique id: grott_rehbcf908x_mqtt_007
2023-10-10 08:02:18.435 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Voltage, unique id: grott_rehbcf908x_mqtt_008
2023-10-10 08:02:18.436 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Current, unique id: grott_rehbcf908x_mqtt_009
2023-10-10 08:02:18.436 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Power, unique id: grott_rehbcf908x_mqtt_010
2023-10-10 08:02:18.436 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Output Power, unique id: grott_rehbcf908x_mqtt_011
2023-10-10 08:02:18.437 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Grid Frequency, unique id: grott_rehbcf908x_mqtt_012
2023-10-10 08:02:18.437 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Single/First Phase), unique id: grott_rehbcf908x_mqtt_013
2023-10-10 08:02:18.440 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Single/First Phase), unique id: grott_rehbcf908x_mqtt_014
2023-10-10 08:02:18.440 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Single/First Phase), unique id: grott_rehbcf908x_mqtt_015
2023-10-10 08:02:18.440 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Second Phase), unique id: grott_rehbcf908x_mqtt_016
2023-10-10 08:02:18.441 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Second Phase), unique id: grott_rehbcf908x_mqtt_017
2023-10-10 08:02:18.441 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Second Phase), unique id: grott_rehbcf908x_mqtt_018
2023-10-10 08:02:18.441 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Third Phase), unique id: grott_rehbcf908x_mqtt_019
2023-10-10 08:02:18.441 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Third Phase), unique id: grott_rehbcf908x_mqtt_020
2023-10-10 08:02:18.442 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Third Phase), unique id: grott_rehbcf908x_mqtt_021
2023-10-10 08:02:18.442 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Time Since Commissioned, unique id: grott_rehbcf908x_mqtt_022
2023-10-10 08:02:18.443 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Power Generation - Today (pvenergytoday), unique id: grott_rehbcf908x_mqtt_024
2023-10-10 08:02:18.443 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Power Generation - Total (pvenergytotal), unique id: grott_rehbcf908x_mqtt_071
2023-10-10 08:02:18.443 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Energy - Today, unique id: grott_rehbcf908x_mqtt_026
2023-10-10 08:02:18.444 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Energy - Total, unique id: grott_rehbcf908x_mqtt_027
2023-10-10 08:02:18.444 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Energy - Today, unique id: grott_rehbcf908x_mqtt_028
2023-10-10 08:02:18.444 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Energy - Total, unique id: grott_rehbcf908x_mqtt_029
2023-10-10 08:02:18.445 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV-All Energy - Total, unique id: grott_rehbcf908x_mqtt_030
2023-10-10 08:02:18.447 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Temperature, unique id: grott_rehbcf908x_mqtt_031
2023-10-10 08:02:18.448 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X IPM Temperature, unique id: grott_rehbcf908x_mqtt_032
2023-10-10 08:02:18.448 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Last data update, unique id: grott_rehbcf908x_mqtt_099
2023-10-10 08:04:06.017 DEBUG (MainThread) [custom_components.grott.sensor] Received message: energy/growatt
2023-10-10 08:04:06.017 DEBUG (MainThread) [custom_components.grott.sensor] Payload: {'device': 'REHBCF908X', 'time': '2037-08-20T22:36:39', 'buffered': 'no', 'values': {'datalogserial': 'XGD6CJD2RN', 'pvserial': 'REHBCF908X', 'pvstatus': 0, 'pvpowerin': 0, 'pv1voltage': 3406, 'pv1current': 0, 'pv1watt': 0, 'pv2voltage': 2433, 'pv2current': 0, 'pv2watt': 0, 'pvpowerout': 0, 'pvfrequentie': 0, 'pvgridvoltage': 0, 'pvgridcurrent': 0, 'pvgridpower': 0, 'pvgridvoltage2': 0, 'pvgridcurrent2': 0, 'pvgridpower2': 0, 'pvgridvoltage3': 0, 'pvgridcurrent3': 0, 'pvgridpower3': 4998, 'totworktime': 0, 'pvenergytoday': 4040, 'pvenergytotal': 263786460, 'epvtotal': 0, 'epv1today': 24352, 'epv1total': 11694350, 'epv2today': 0, 'epv2total': 15788, 'pvtemperature': 394, 'pvipmtemperature': 0, 'battery1soc': 0}}
2023-10-10 08:04:06.017 DEBUG (MainThread) [custom_components.grott.sensor] Configured to look for device: + (+ means all)
2023-10-10 08:04:06.018 DEBUG (MainThread) [custom_components.grott.sensor] Configured to include calculated values: False
2023-10-10 08:04:06.018 INFO (MainThread) [custom_components.grott.sensor] PROCESSING UPDATES
2023-10-10 08:04:06.018 INFO (MainThread) [custom_components.grott.sensor] 32 sensors for processing
2023-10-10 08:04:06.018 DEBUG (MainThread) [custom_components.grott.sensor] raw_mqtt_sensors - matched on REHBCF908X
2023-10-10 08:04:06.018 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV Serial, unique id: grott_rehbcf908x_mqtt_001
2023-10-10 08:04:06.019 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Datalog Serial, unique id: grott_rehbcf908x_mqtt_002
2023-10-10 08:04:06.019 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV Status, unique id: grott_rehbcf908x_mqtt_003
2023-10-10 08:04:06.019 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV-All Power, unique id: grott_rehbcf908x_mqtt_004
2023-10-10 08:04:06.019 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Voltage, unique id: grott_rehbcf908x_mqtt_005
2023-10-10 08:04:06.020 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Current, unique id: grott_rehbcf908x_mqtt_006
2023-10-10 08:04:06.020 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Power, unique id: grott_rehbcf908x_mqtt_007
2023-10-10 08:04:06.020 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Voltage, unique id: grott_rehbcf908x_mqtt_008
2023-10-10 08:04:06.021 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Current, unique id: grott_rehbcf908x_mqtt_009
2023-10-10 08:04:06.021 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Power, unique id: grott_rehbcf908x_mqtt_010
2023-10-10 08:04:06.021 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Output Power, unique id: grott_rehbcf908x_mqtt_011
2023-10-10 08:04:06.022 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Grid Frequency, unique id: grott_rehbcf908x_mqtt_012
2023-10-10 08:04:06.022 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Single/First Phase), unique id: grott_rehbcf908x_mqtt_013
2023-10-10 08:04:06.025 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Single/First Phase), unique id: grott_rehbcf908x_mqtt_014
2023-10-10 08:04:06.025 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Single/First Phase), unique id: grott_rehbcf908x_mqtt_015
2023-10-10 08:04:06.025 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Second Phase), unique id: grott_rehbcf908x_mqtt_016
2023-10-10 08:04:06.026 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Second Phase), unique id: grott_rehbcf908x_mqtt_017
2023-10-10 08:04:06.026 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Second Phase), unique id: grott_rehbcf908x_mqtt_018
2023-10-10 08:04:06.026 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Third Phase), unique id: grott_rehbcf908x_mqtt_019
2023-10-10 08:04:06.026 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Third Phase), unique id: grott_rehbcf908x_mqtt_020
2023-10-10 08:04:06.027 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Third Phase), unique id: grott_rehbcf908x_mqtt_021
2023-10-10 08:04:06.027 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Time Since Commissioned, unique id: grott_rehbcf908x_mqtt_022
2023-10-10 08:04:06.028 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Power Generation - Today (pvenergytoday), unique id: grott_rehbcf908x_mqtt_024
2023-10-10 08:04:06.028 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Power Generation - Total (pvenergytotal), unique id: grott_rehbcf908x_mqtt_071
2023-10-10 08:04:06.028 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Energy - Today, unique id: grott_rehbcf908x_mqtt_026
2023-10-10 08:04:06.029 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Energy - Total, unique id: grott_rehbcf908x_mqtt_027
2023-10-10 08:04:06.029 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Energy - Today, unique id: grott_rehbcf908x_mqtt_028
2023-10-10 08:04:06.029 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Energy - Total, unique id: grott_rehbcf908x_mqtt_029
2023-10-10 08:04:06.032 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV-All Energy - Total, unique id: grott_rehbcf908x_mqtt_030
2023-10-10 08:04:06.033 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Temperature, unique id: grott_rehbcf908x_mqtt_031
2023-10-10 08:04:06.033 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X IPM Temperature, unique id: grott_rehbcf908x_mqtt_032
2023-10-10 08:04:06.033 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Last data update, unique id: grott_rehbcf908x_mqtt_099

this log here under is with sun , the above is from starting up , i try also to get a picture from the HA from the same time
2023-10-10 10:09:10.782 DEBUG (MainThread) [custom_components.grott.sensor] Payload: {'device': 'REHBCF908X', 'time': '2023-10-10T10:06:07', 'buffered': 'no', 'values': {'datalogserial': 'XGD6CJD2RN', 'pvserial': 'REHBCF908X', 'pvstatus': 1, 'pvpowerin': 5481, 'pv1voltage': 3365, 'pv1current': 9, 'pv1watt': 3028, 'pv2voltage': 2394, 'pv2current': 7, 'pv2watt': 1675, 'pvpowerout': 0, 'pvfrequentie': 0, 'pvgridvoltage': 0, 'pvgridcurrent': 0, 'pvgridpower': 0, 'pvgridvoltage2': 0, 'pvgridcurrent2': 0, 'pvgridpower2': 0, 'pvgridvoltage3': 0, 'pvgridcurrent3': 0, 'pvgridpower3': 353833864, 'totworktime': 589824, 'pvenergytoday': 139137000, 'pvenergytotal': 266080253, 'epvtotal': 6, 'epv1today': 24358, 'epv1total': 11708328, 'epv2today': 4, 'epv2total': 15792, 'pvtemperature': 541, 'pvipmtemperature': 0, 'battery1soc': 0}}
2023-10-10 10:09:10.782 DEBUG (MainThread) [custom_components.grott.sensor] Configured to look for device: + (+ means all)
2023-10-10 10:09:10.782 DEBUG (MainThread) [custom_components.grott.sensor] Configured to include calculated values: False
2023-10-10 10:09:10.782 INFO (MainThread) [custom_components.grott.sensor] PROCESSING UPDATES
2023-10-10 10:09:10.782 INFO (MainThread) [custom_components.grott.sensor] 32 sensors for processing
2023-10-10 10:09:10.783 DEBUG (MainThread) [custom_components.grott.sensor] raw_mqtt_sensors - matched on REHBCF908X
2023-10-10 10:09:10.783 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV Serial, unique id: grott_rehbcf908x_mqtt_001
2023-10-10 10:09:10.783 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Datalog Serial, unique id: grott_rehbcf908x_mqtt_002
2023-10-10 10:09:10.783 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV Status, unique id: grott_rehbcf908x_mqtt_003
2023-10-10 10:09:10.784 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV-All Power, unique id: grott_rehbcf908x_mqtt_004
2023-10-10 10:09:10.784 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Voltage, unique id: grott_rehbcf908x_mqtt_005
2023-10-10 10:09:10.785 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Current, unique id: grott_rehbcf908x_mqtt_006
2023-10-10 10:09:10.785 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Power, unique id: grott_rehbcf908x_mqtt_007
2023-10-10 10:09:10.786 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Voltage, unique id: grott_rehbcf908x_mqtt_008
2023-10-10 10:09:10.786 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Current, unique id: grott_rehbcf908x_mqtt_009
2023-10-10 10:09:10.792 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Power, unique id: grott_rehbcf908x_mqtt_010
2023-10-10 10:09:10.792 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Output Power, unique id: grott_rehbcf908x_mqtt_011
2023-10-10 10:09:10.793 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Grid Frequency, unique id: grott_rehbcf908x_mqtt_012
2023-10-10 10:09:10.793 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Single/First Phase), unique id: grott_rehbcf908x_mqtt_013
2023-10-10 10:09:10.793 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Single/First Phase), unique id: grott_rehbcf908x_mqtt_014
2023-10-10 10:09:10.794 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Single/First Phase), unique id: grott_rehbcf908x_mqtt_015
2023-10-10 10:09:10.794 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Second Phase), unique id: grott_rehbcf908x_mqtt_016
2023-10-10 10:09:10.794 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Second Phase), unique id: grott_rehbcf908x_mqtt_017
2023-10-10 10:09:10.795 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Second Phase), unique id: grott_rehbcf908x_mqtt_018
2023-10-10 10:09:10.795 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Voltage (Third Phase), unique id: grott_rehbcf908x_mqtt_019
2023-10-10 10:09:10.795 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Current (Third Phase), unique id: grott_rehbcf908x_mqtt_020
2023-10-10 10:09:10.795 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Output Power (Third Phase), unique id: grott_rehbcf908x_mqtt_021
2023-10-10 10:09:10.796 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Time Since Commissioned, unique id: grott_rehbcf908x_mqtt_022
2023-10-10 10:09:10.799 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Power Generation - Today (pvenergytoday), unique id: grott_rehbcf908x_mqtt_024
2023-10-10 10:09:10.800 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Power Generation - Total (pvenergytotal), unique id: grott_rehbcf908x_mqtt_071
2023-10-10 10:09:10.801 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Energy - Today, unique id: grott_rehbcf908x_mqtt_026
2023-10-10 10:09:10.801 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV1 Energy - Total, unique id: grott_rehbcf908x_mqtt_027
2023-10-10 10:09:10.801 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Energy - Today, unique id: grott_rehbcf908x_mqtt_028
2023-10-10 10:09:10.802 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV2 Energy - Total, unique id: grott_rehbcf908x_mqtt_029
2023-10-10 10:09:10.802 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X PV-All Energy - Total, unique id: grott_rehbcf908x_mqtt_030
2023-10-10 10:09:10.803 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Inverter Temperature, unique id: grott_rehbcf908x_mqtt_031
2023-10-10 10:09:10.803 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X IPM Temperature, unique id: grott_rehbcf908x_mqtt_032
2023-10-10 10:09:10.803 DEBUG (MainThread) [custom_components.grott.sensor] Processing update for: REHBCF908X Last data update, unique id: grott_rehbcf908x_mqtt_099

The logs you have posted are from the Grott Integration in Home Assistant, not Grott itself, however they do contain the information that will be processed and displayed, specifically this section:
 {'device': 'REHBCF908X', 'time': '2023-10-10T10:06:07', 'buffered': 'no', 'values': {'datalogserial': 'XGD6CJD2RN', 'pvserial': 'REHBCF908X', 'pvstatus': 1, 'pvpowerin': 5481, 'pv1voltage': 3365, 'pv1current': 9, 'pv1watt': 3028, 'pv2voltage': 2394, 'pv2current': 7, 'pv2watt': 1675, 'pvpowerout': 0, 'pvfrequentie': 0, 'pvgridvoltage': 0, 'pvgridcurrent': 0, 'pvgridpower': 0, 'pvgridvoltage2': 0, 'pvgridcurrent2': 0, 'pvgridpower2': 0, 'pvgridvoltage3': 0, 'pvgridcurrent3': 0, 'pvgridpower3': 353833864, 'totworktime': 589824, 'pvenergytoday': 139137000, 'pvenergytotal': 266080253, 'epvtotal': 6, 'epv1today': 24358, 'epv1total': 11708328, 'epv2today': 4, 'epv2total': 15792, 'pvtemperature': 541, 'pvipmtemperature': 0, 'battery1soc': 0}}

You can see that these are the same values that are being displayed on the screenshots you shared.
e.g. pv1voltage: 3365 = PV1 Voltage: 339,5v (I assume there was a slight time lag between the screenshots and the log output)
Therefore if you believe some of the values are incorrect for this specific inverter you'd need to raise a bug in the https://github.com/johanmeijer/grott/issues area to see if the developer of Grott can assist in fixing them.
I'm sorry I can't be more help, please let me know if that assists your debug.

@muppet3000 , thanks everything is working fine now , i will close this issue

Great, thanks @annbuw

authors: Erlingnygard Fannboy1337 annbuw beped egguy julianjosias muppet3000


text:
Updating Reproducibility Rmd

Adding a few more tidbits here.
I knitted things by hand because make labs wouldn't work.
Rscript -e "remotes::install_github('muschellij2/jhur')"

won't install which is required by this.
Downloading GitHub repo muschellij2/jhur@HEAD
Error: Failed to install 'jhur' from GitHub:
  missing value where TRUE/FALSE needed
Execution halted

Oops. Wrong repo.

source: gharchive/pull-request


text:
Space between scripts

As seen in the image below, there are spaces between scripts which makes powerline unusable if more than 1 script is used. A way to toggle/specify this would be nice (unless it's something to do with my setup).

@CousinMachu you can just not put in the ':' characters in your format definition.

Thanks

authors: CousinMachu neeasade

repo: muse/Captain

license: mit

license_source: bigquery


text:
guidelines sidebar search input

The true_search_input is too wide on large screens; the search button is being rendered outside the window

width: 100vw doesn't work with the max-width: 1296px from .container.grid-xl
see #125

the basic problem seems to be
.specsLayout {
  width: 100vw;
}

conflicts with general page layout of the MEI website which moves the nav-column outside of the viewport

do we really need to have the page wieder for the specs? then maybe we should use another defined _layout? Or we could move the specs navbar to a responsive menu like the new main menu

closed with #145

authors: bwbohl rettinghaus


text:
fixes #797

this will allow @tstamp2 on <metaMark>, and will disallow @tstamp2.ges and @tstamp2.real. The two latter might be useful, but this is clearly a bug and needs to be fixed as proposed. Adding the other two attributes should be done when there's a request for this.

Agreed to merge at this month's ODD Friday

repo: music-encoding/music-encoding


text:
Installation: ImportError: No module named 'ale_python_interface'

When I try to run the saved model as :
python demo_a3c_ale.py ../roms/breakout.bin trained_model/breakout_ff/80000000_finish.h5

I get an error :
ImportError: No module named 'ale_python_interface'

which is because python3.5 (which I am using now by default) does not have access to ALE.
So I installed ALE but at the ale_python_interface step, that is when we have to execute
pip install --user .

I instead execute
python3.5 -m pip install --user .

since we want python3.5 to get access to ALE. This results in a syntax error since the ALE's python code still has python2.7 syntax. How do we fix this issue?
Thanks!

pip3 install --user . is the right command.

authors: sahiliitm sherjilozair

repo: muupan/async-rl


text:
setCurrentPhotoIndex is ignored on second opening

I am doing:
[_photoBrowser setCurrentPhotoIndex:newPhotoInd];
UINavigationController *navPhotoBrowser = [[UINavigationController alloc] initWithRootViewController:_photoBrowser];
navPhotoBrowser.modalTransitionStyle = UIModalTransitionStyleCrossDissolve;

[self presentViewController:navPhotoBrowser animated:YES completion:NULL];

On the second time, it keeps the photoIndex position of the first time.
Is it possible to do this?
Or do I have to dispose and reinit photoBrowser every time?
Thanks
Werner

I'm confused that how do you open for the second time? if you just dismiss, and present again, without dealloc _photoBrowser, setCurrentPhotoIndex should work. Of course, you should keep the position index after the browser dismiss and call setCurrentPhotoIndex with the position index you kept.

Hi! Thanks for your support.
In viewDidLoad I init the photoBrowser like this:
_photoBrowser = [[MWPhotoBrowser alloc] initWithDelegate:self];

// Set options
_photoBrowser.displayActionButton = YES; // Show action button to allow sharing, copying, etc (defaults to YES)
_photoBrowser.displayNavArrows = NO; // Whether to display left and right nav arrows on toolbar (defaults to NO)
_photoBrowser.displaySelectionButtons = NO; // Whether selection buttons are shown on each image (defaults to NO)
_photoBrowser.zoomPhotosToFill = YES; // Images that almost fill the screen will be initially zoomed to fill (defaults to YES)
_photoBrowser.alwaysShowControls = NO; // Allows to control whether the bars and controls are always visible or whether they fade away to show the photo full (defaults to NO)
_photoBrowser.enableGrid = YES; // Whether to allow the viewing of all the photo thumbnails on a grid (defaults to YES)
_photoBrowser.startOnGrid = NO; // Whether to start on the grid of thumbnails instead of the first photo (defaults to NO)
_photoBrowser.autoPlayOnAppear = NO; // Auto-play first video

to switch to the new photo index I am doing:
[_photoBrowser setCurrentPhotoIndex:newPhotoInd];

UINavigationController *navPhotoBrowser = [[UINavigationController alloc]
initWithRootViewController:_photoBrowser];
navPhotoBrowser.modalTransitionStyle = UIModalTransitionStyleCrossDissolve;

[self presentViewController:navPhotoBrowser animated:YES completion:NULL];

This seems to work only the first time.
When I call it the second time, the new photo index is ignored.
If I open it and swipe to a different photo, this is shown no matter which photo index I set in the above call.
The workaround that seems to work is to reinit the photobrowser. Is this supposed to be done this way?
Regards
Werner

I'm experiencing the same issue. Also, solved it by re-initing the photo browser each time.

authors: jiangyancong orenk86 plenio

repo: mwaterfall/MWPhotoBrowser


text:
Remove Java Native Interface

There are 2 building failure cases in CI for BUILD=check-java, for example here which is caused by Java version.
We never use these Java code in mwcproject, to make our CI tests clean, it's better to remove these Java interface, same as this upstream (root) commit by jonasnick on Jan. 08, 2020.

It works as expected, Two BUILD=check-java tests has been removed. The remaining two tests failure will be fixed in another PR.


text:
Problems with CredSSP in parallel executions

I'm using Boxstarter to install some chocolatey packages at the same time in several machines (in parallel).
At the beginning I had problems when two Boxstarter processes tried to access the log File at the same time. I've solved that issue configuring a different log file for each process.
Now, I'm experiencing a different issue also related to concurrency. When I launch Install-BoxstarterPackage to a single computer, the CredSSP works. However, if I launch several parallel tasks to run in different computers, the CredSSP Authentication fails in most of them. In the attached file you can see the Log output.
Errorlog.txt
It seems there is a problem with the Function Enable-BoxstarterCredSSP.ps1, but I do not know how to fix it or how to avoid the execution of this fuction.
Anyone have any ideas how I can get around this problem?

Hmm. Thats not surprising. Boxstarter was not really written with concurrency in mind and when it changes credssp settings, it later reverts those changes which may stomp on other boxstarter prpcesses. One workaround would be to enable credssp on both ends if thats appropriate for your environment. Then boxstarter wont try to mess with them.

Thanks for your response. Testing the solution you proposed I've just realized which is the problem I'm experiencing and I think it is not related to the execution of Boxstarter in parallel.
It seems to be a bug in the way Boxstarter deal with the CredSSP client credentials when there are more than one DelegateComputer entry in the system before running Boxstarter.
The resulting problem is that delegateComputer entry added by Boxstarter at the end of its execution is not valid and the previous configuration stops working.
Before running Boxstarter the CresSSP client credentials were:
wsman/*.campus.es,wsman/*.unican.es
While Boxstarter is running:
wsman/sir096.unican.es,wsman/*.campus.es,wsman/*.unican.es
And after the execution of Boxstarter the CredSSP have change to:
wsman/*.campus.es,*.unican.es  (wsman/ in the second entry is missing)
The command Enable-WSManCredSSP seems to admit only a single DelegateComputer entry at a time. Thus, when a string is passed as a parameter to DelegateComputer, it is parsed as a single entry, and the wsman/ is only added at the begginig of the string.
Changing the Line 910 of Install-BoxstarterPackage.ps1 to:
foreach ($entryin$CredSSPStatus.PreviousCSSPTrustedHosts.Replace("wsman/","").Split(",")){ enable-wsmancredssp-roleclient-delegatecomputer$entry-force }
it works (at least in my server).
In CredSSP_Test.txt you can see the script I used to perform the tests

authors: fernanqv mwrock

repo: mwrock/boxstarter


text:
Better README

As the beginning of the year approaches, freshman will soon try to look at and contribute to CSH projects. It's a bit hard when there are no setup instructions, or links of where to download python, pip, or any other tools we use.
It would be a good idea to add to the README some setup and other useful information

[x] Setup information
[x] System Dependencies
[x] Python version, potentially as a badge
[x] Code standards (Less important if pylint is present)

@devinmatte Does the current READEME satisfy?

authors: devinmatte mxmeinhold

repo: mxmeinhold/csh-quotefault-bot


text:
[ISSUE #1000]✨Add RocketMQTokioRwLock and RocketMQTokioMutex for rocketmq crate🎨

Which Issue(s) This PR Fixes(Closes)

Fixes #1000
Brief Description

How Did You Test This Change?

Summary by CodeRabbit

New Features

Introduced a new module for asynchronous locking mechanisms: rocketmq_tokio_lock.
Added RocketMQTokioMutex for exclusive data access.
Added RocketMQTokioRwLock for concurrent read and write access, with timeout options.

These enhancements improve the library's capabilities for asynchronous programming, providing users with more efficient synchronization tools.

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

repo: mxsm/rocketmq-rust


text:
New eslint-plugin-react rules complain "error Do not use Array index in keys"

Updated eslint-plugin-react rules disallow use of array index as key.
Error: ~/react-boilerplate/app/components/List/index.js 13:31
error Do not use Array index in keys react/no-array-index-key
Disable "react/no-array-index-key" in package.json
See: https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/no-array-index-key.md
To reproduce:
confirm #1501 has been merged
checkout current dev branch
remove  "react/no-array-index-key" from package.json
npm test
Boilerplate 3.4+ dev branch (ad871d7a1b70cec5b365fdc30eb86ee7e189158f)
Node 7.4.0
npm 4.1.1
yarn 0.19.1
Mac OS 10.11.6
Chrome 55.0.2883.95 (64-bit))

It's a bad idea to use the array index since it doesn't uniquely identify your elements. In cases where the array is sorted or an element is added to the beginning of the array, the index will be changed even though the element representing that index may be the same. This results in unnecessary renders.

Good enough reason to enforce the rule. Do we want to keep it? I can send a PR.

Yes, please send a PR 👍

Close by #1521

authors: KarandikarMihir gihrig

repo: mxstbr/react-boilerplate


text:
Markdown编辑和预览能否左右分屏

如题， 编辑时上下分屏，这样不能实时看到编辑结果，要来回的上下滚屏才能预览，这样非常不方便，左右分屏的话就很好，希望采纳！

可以的。  @rockliuxn
官方好像是不支持，不过可以通过自己修改源码实现Markdown编辑左右分屏。
以下是我的个人实践，在 simditor-markdown.js 文件中添加如下代码：
SimditorMarkdown.prototype.command = function() {
var button, i, len, ref;
    $(".markdown-editor").css("display", "inline-block")
        .css("width", "50%")
        .css("height", "100%")
        .css("min-height", "500px")
        .css("float", "left");
    $(".simditor .markdown-editor textarea").css("min-height", "500px");

    $(".simditor-body").css("display", "inline-block")
        .css("width", "50%")
        .css("height", "100%")
        .css("min-height", "500px")
        .css("float", "right");

this.editor.blur();
......
} else {
this.textarea.val('');
this.editor.body.attr('contenteditable', 'true');
      $(".markdown-editor").removeAttr("style");
      $(".simditor-body").removeAttr("style");

}
下面是源码修改后的效果图：

authors: iamroma rockliuxn

repo: mycolorway/simditor-markdown


text:
ci: update unity test runner action version

Removes the hardcoded reference to the unity-test-runner action, since a new version with the required changes is available. Mentioned in #18

:tada: This PR is included in version 2.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: mygamedevtools/scene-loader


text:
Add data to cell object to store text break interval

Add data to cell object to store the data regarding the text break interval when the user is using text wrap option.

Hey Mr.Liang, may I know why this request hasn't been merged ?

Hey Mr.Liang, may I know why this request hasn't been merged ?

Is there something in the code that needs some change ?

repo: myliang/x-spreadsheet


text:
修改语言包，增加多个语言的支持，可以使用locale进行切换

将默认使用en的语言改为可以使用zh-CN，引入其他的语言包的支持，使用locale动态切换

按需加载语言包，不默认加载所有语言包，默认只加载英文的语言
https://github.com/myliang/x-spreadsheet/wiki/Internationalization

如果存在需要支持多个语言的动态切换，是否可以设置成自动加载呢？根据需求和切换自动切换语言是否会更好点？

authors: longmartin myliang


text:
🛑 waf.sexy is down

In c05c4d2, waf.sexy (https://www.waf.sexy) was down:

HTTP code: 0
Response time: 0 ms

Resolved: waf.sexy is back up in 2f68891.

repo: mymovielist/uptime


text:
Month is outputting incorrectly

The issue I've found is that the csv output shows the month as June instead of July. I've spoken to Danny and it sounds like the month is counted from 0 (the days etc are not so they are all fine).

fixed with 7227361b74172dadf2

authors: IgnasJarusevicius ShaneHudson

repo: myriadrf/lime-tools


text:
this is listed as open source or paid?

Hi Guys i want to use this as a small part of my client project, want to make sure if this is open source thankyou

The license will be changed to a free open source license in 2024 Spring.

Ok then i can use this in my project now right

Ok then i can use this in my project now right

Most probably no. The current license is CC BY NC 4.0, you can google what it's rules are.

I will be happy to see

authors: Maksbranding Zengyi-Qin ehartford mustakimweb rsxdalv

repo: myshell-ai/OpenVoice


text:
How to request ssl use the default trust store, rather than specify the CA?

Sorry if this documented, I haven't been able to find an answer.
Right now, the docs specify that the minimum required to use an SSL/TLS connection while validating the server's certificate is:
var connection = mysql.createConnection({
  host : 'localhost',
  ssl  : {
    ca : fs.readFileSync(__dirname + '/mysql-ca.crt')
  }
});

However, I believe that if the server's certs are signed by a CA that is also in the systems trust store, supplying the CA should not be necessary. See https://github.com/nodejs/node/issues/4175#issuecomment-243715727
Is there a way to be lazy and not re-specify the CA? Something like:
var connection = mysql.createConnection({
  host : 'localhost',
  ssl  : {}
});

... would be ideal.

It's not documented well, but it is the last example in the section https://github.com/mysqljs/mysql/blob/master/Readme.md#ssl-options

Hi @dougwilson thanks for your response. I'm not sure I understand. Are you suggesting I specify rejectUnauthorized: true?

Hi @menicosia I'm not sure what you mean. The last example has rejectUnauthorized: false. Are you seeing something different?

Here is the example I am referring to:
var connection = mysql.createConnection({
  host : 'localhost',
  ssl  : {
    rejectUnauthorized: false
  }
});

Oh, I just realized what that means. The double-negative is really throwing me off. Yea, I believe you can use an empty object like your OP: ssl: {} to just use the Node.js CA logic. Does that not work?

Afraid not. Neither ssl: {} nor ssl: {rejectUnauthorized: true} work. I delayed responding till I made sure I was using a recent version - I'm testing on node 8.6.0.

Interesting. In the meantime I tested against Azure which uses certs that are part of Node.js (they use public domain certs) and using {} worked fine. If you can hrlp me replicate the issue I can debug through where the issue is, or if you can PR a fix. If you want me to take a look, I'll need the following:

Version of this module
Version of MySQL server
Complete code you are trying to use
Complete instructions for how you have setup the SSL on the server (or a way for me to connect to a server you have setup).

Thanks!

For the error (which wasn't in the original email) the HANDSHAKE_SSL_ERROR is just the code. If you can provide the message property and stack trace that may help shed light on this as well.

I will also check on 8.6.0 as well, since I tested on 6.11.4 while you gater the additional information.

@dougwilson thank you much for being super responsive and testing against a known implementation like Azure.
This leads me to worry that perhaps the CA certs that are expected to be in my trust store... are not actually in my trust store. (My project is a PaaS that is supposed to take care of automate distribution of certs, Cloud Foundry.)
Please put this bug on hold while I escalate internally.

Also, I'm not sure if you know (but I just realized from your notes) that if the CA you need is not part of the static set built into Node.js directly, then unless you have manually compiled Node.js yourself with the compile time flag to have it use the OpenSSL system store, your CA is probably not visible to Node.js (if you are getting a bin built by a distro they may have it setup for you). There is also the environment variable NODE_EXTRA_CA_CERTS will look at to load in extra CAs as well.
If you suspect it is a CA issue, there is probably some Node.js API to get the list of all CAs your Node.js knows about and you can verify if it is indeed in the list or not.

Thanks, I've added this to our issue #152172167. I'll check back!

Awesome :) I'm happy to help figure out what the caude is if needed. I'll likely follow this up to allow just "ssl: true" as a shortcut as well.

Hi @KuSh I went to add ssl: true support, and come to my surprise: it does work! Unfortunately it does not work the same as ssl: {}, in that rejectUnauthorized defaults to false instead of true... since there are things documenting that it does indeed work, it is unlikely I can fix it without a major release, as it would break a lot of folks, as internal MySQL instances are very likely use to use certs from the public PKI.

I'm going to close this as the original OP has the answer from so long ago for how to use the default Node.js store.

authors: dougwilson menicosia

repo: mysqljs/mysql


text:
[RFC] more http methods should be available as instance functions

1.: What's the problem with the axios function?
When using sinon.js as mocking engine, you'll see after very short time that I works with functions exported in another module, but not with an exported function. This issue has been discussed here: https://github.com/sinonjs/sinon/issues/664
Now there are a lot of http methods such as "LINK" or "LOCK" that are not present as instance functions, so the axios function must be used. I'm pretty sure that I'll run in the next time into such issues, so I've thinked about a solution for this issue.
2.: Configurable API
The simplest solution to pass more http verbs to the arrays in the axios.js (https://github.com/mzabriskie/axios/blob/master/lib/axios.js#L110) is IMHO not a good solution since there are approaches for custom http verbs which cannot use instance methods.
3.: How it could look like
The axios.create function in order to provide custom http verbs that should be supported as instance function:
import axios from 'axios';
// ...

const instance = axios.create({
    // ...
    http_verbs: [
        { name: 'LOCK', with_data: false },
        { name: 'LINK', with_data: true }
    ]
});

Sorry, I have a lot of other things demanding my attention and haven't given this a close look yet.
I think that any valid HTTP verb should be supported natively. Additionally it would be nice to allow adding custom verbs as you suggest.

@mzabriskie ok - the PR #190 aims to implement this :)
I think that exactly this will be quite difficult: there are a lot of RFCs like the RFC-2518 for enhanced authoring actions and some more.
I'll rebase my PR on master and there are some things I'd like to do before talking about merging.
Could you please have a look at the way it is implemented?

repo: mzabriskie/axios


text:
Handling cancellation errors in interceptor

Hey,
I have an interceptor that handles general errors for me. It looks something like this:
axios.interceptors.response.use(function (response) {
  ...
}, function (error) {
  if (error instanceof axios.Cancel) {
    if (ENV.env === 'development') {
      console.log(error.message);
    }
  }

  if (error.response && error.response.status === 401) {
    // logout here
  }

  return Promise.reject(error);
});

The problem is that when I have requests that I have cancelled the error function gets called in the interceptor and I'm getting this in the log:
Uncaught (in promise) Cancel {message: "cancelled the call"}

Why is the error handler being called when the request is cancelled?
If it must be called ... how do I handle it correctly?

Thanks!

I found out the I just have to handle the rejection of a promise ... I thought I could just ignore it ...


text:
Redirect history?

Does this library provide one?

@mzabriskie  @nickuraltsev ?

There's no support for the complete history but there's a way to get the last url. See #799.

Why is there no complete history, at least for Node.js? Controlled isomorphism?

@rubennorte ^

We use follow-redirects internally to implement redirections and it doesn't provide it. In case anyone is interested in this, it should be implemented there and then adapted here.

authors: rubennorte stevenvachon


text:
BUG

Basic information

My operating system and version: WIN11
My mzmine version: Mzmine3.9.0

What happened
After I used mass detection function to identify the data of MS1 and MS2, and then after ADAP builder and ADAP resolve processing, I exported the data to GNPS format to check the data, and the error was reported as shown in the figure.

Hi, WuTianRens, the link does not work. Please follow the steps on how to create a bug report, we cannot help without a way to reproduce the problem and the log file.

Hi, WuTianRens, the link does not work. Please follow the steps on how to create a bug report, we cannot help without a way to reproduce the problem and the log file.

I upload again

Hello, I had the same problem.
The problem is due to the type of data. I recorded everything in centroided but on a random mass, I have thresholeded data. The problem comes from here but I don't know what to do. Especially as this mass is not in the features list.
This poses a problem for mass detection.

Hi,
please update to latest version and see if the problem still appears.
kind regards

Style have the problem with the latest version. (my data have been recorder in centroided and convert to .mzxml)

How does your mass detection step look like? Do you use "ANY" for spectrum type in the scan filter? If it is set to CENTROIDED all other types will be ignored.

Hi, please update to latest version and see if the problem still appears. kind regards

I`ll do so to see

I found this solution to get round this problem. I changed the type of scan for any and modified the mass detector algorithm. The metric value entered for the noise level will not correspond for the next stage of the workflow.
The problem is that I don't understand why I have centroided data when I open it in mzmine. This type of data does not come from our builder's machine (bruker).
Thanks to help us,
King regards,

Style have the problem with the latest version. (my data have been recorder in centroided and convert to .mzxml)

I have 18 data, but only 1 has this problem,  confused me a lot

I found this solution to get round this problem. I changed the type of scan for any and modified the mass detector algorithm. The metric value entered for the noise level will not correspond for the next stage of the workflow.
The problem is that I don't understand why I have centroided data when I open it in mzmine. This type of data does not come from our builder's machine (bruker) and appear only for ms2 scans. Thanks to help us, King regards,

l will try this way, appreciate a lot

I found this solution to get round this problem. I changed the type of scan for any and modified the mass detector algorithm. The metric value entered for the noise level will not correspond for the next stage of the workflow.
The problem is that I don't understand why I have centroided data when I open it in mzmine. This type of data does not come from our builder's machine (bruker) and appear only for ms2 scans. Thanks to help us, King regards,

It works.  I only changed the type of scan for Any. After the work flow , it could be export to GNPS format. Appreciate a lot!

authors: GautDem SteffenHeu WuTianRens ansgarkorf

repo: mzmine/mzmine


text:
Iroh-examples: Example how to sync a sqlite database

Use a sqlite database locally
Use the sqlite VFS for change tracking (or do brute force rehash)
Sync the sqlite database to other nodes
Have a "compute over data" thing that reads multiple sqlite dbs and updates an aggregated sqlite db.
https://www.sqlite.org/vfs.html

instead of VFS maybe just do selects on aggregate and update accordingly ?

iroh-node with sqlite has a table with sequential id's
when act on table iroh-node  notifies aggregate
iroh-node chrono aggregate select for last id compares with own and do a select on aggregate for fetch [new] range
if request is not in local (inbetween chrono sync) node selects on aggregate
aggregate need have trigger for id that changed [updated deleted] in separate table with ts-id, that iroh-node can select on and update its synced local since last ts-id range

besides syncing sqlites in iroh-band it could also index as mentioned elsewhere for gateway supernodes etc.

table with humanized key's containing tickets and / or addrs derp hash]type] fields

how about mix and match with DuckDB ? it has a sqlite extension a rust client and several imports
http://duckdb.org/docs/extensions/sqlite
http://duckdb.org/docs/extensions/inet


text:
I want use this plug in with FVM

this plug in is very well
but i can't use this plug in with FVM
FVM is flutter version manager
when FVM installed
flutter command line
When entering the platter command, you must put fvm at the beginning.
example
fvm flutter pub run build_runner build --delete-conflicting-outputs
so i want to add fvm options

Hi, any news on this?
Thankyou for this plugin. It's very useful!

authors: Origogi fatshady

repo: nEdAy/Flutter-Toolkit


text:
Market dev

Need to merge in changes from the change from Product to Market into the master branch

Manually merged changes for Market instead of Product into changes made for fixing AggressiveImpactListener

repo: nabicht/MarketPy


text:
Fix - anchor tag breaks into parts with partial styling

Proposed fix for https://github.com/nadar/quill-delta-parser/issues/59
this is  a breaking change as Link->wrapper is discarded

@nadar thanks for allowing the tests to run.
I will pay additional attention to docs/tags as you mentioned and try and fix the failing checks.
This proposed fix is one approach to tackle the issue, based on my limited knowledge of the quill-delta-parser. I'm curious if you maybe have a completely different approach in mind.

@bartgloudemans thanks for the work! I will take a closer look within the next 48hours.

I'm especially interested because this link+italic example is a dressed down version of the issue I'm actually having with a more complex custom listener. My custom listener acts instead of the link listener and adds a complex piece of html into the rendered html. And that complex html is much harder to break down than the simple "wrapperOpen", "wrapperMiddle" and "wrapperClose".

Would you like to share your custom listener?

@bartgloudemans thanks for the work, i really appreciate it. I will make some small changes in upgrade docs and release version 3.0 asap.

Version 3.0 is published. https://github.com/nadar/quill-delta-parser/releases/tag/3.0.0

authors: bartgloudemans nadar

repo: nadar/quill-delta-parser


text:
Update janino to 3.1.8

Updates org.codehaus.janino:janino from 3.1.6 to 3.1.8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.codehaus.janino", artifactId = "janino" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.codehaus.janino", artifactId = "janino" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #560.

repo: namely/chief-of-state


text:
RBAC support?

I set up RBAC support over at https://github.com/bittorrent/kubernetes-graphite-cluster/commit/ca441f7d4639bb3f74946d747aca6fc367b56985 along with a change to use EBS as our EFS volumes didn't have enough io.
Is there any interest in formatting the RBAC portions of that commit into a PR? If so, I would be happy to do so.

Hi @vmrob thanks for bringing this up.
A few questions/thoughts:

The PVC (Persistent volume claims) type is empty hence it's supposed to take the default storage type for the cluster. On the cluster I use on AWS it is an EBS volume not EFS. I wonder why your default is different but it might be a good idea to explicitly state the storage type.
The storage size is now an environment variable so this change is not needed.

I haven't dealt with K8s RBAC before so please explain
3. What are the benefits here?
4. I am pretty sure RBAC was added on 1.6 right? If so, what will happen to 1.5.X clusters?

closed by #23

authors: erez-rabih vmrob

repo: nanit/kubernetes-graphite-cluster


text:
Switch ERB to use keyword arguments

Detailed description
Positional arguments were deprecated in Ruby 3. Change is backwards-compatible to Ruby 2.3.
Related issues
Resolves #1547.

Thanks!
(Tested locally and proper CI is being set up once more as we speak, so PRs will get tested properly once again.)

repo: nanoc/nanoc


text:
Rename this repo/driver?

Brocade IP products have different operating systems:

NetIron - used on the MLXe product line. Older OS, with limited Netconf support. Only practical way of automating this is via CLI/screen-scraping.
NOS - used on the VDX product line (e.g. VDX 6740, 6940). More modern OS, includes REST & Netconf interfaces.
SLX-OS - used on the new SLX 9850, 9540, 9140, 9240 switches/routers. This is based upon NOS, with similar APIs, but more operational state info available via API.

It's not a perfect comparison, but roughly, NetIron is equivalent to legacy IOS from an automation point of view, whereas NOS/SLX-OS are more like IOS-XR. SLX-OS is the 'future' OS, but NetIron is going to be around for a few years yet.
PR #1 here is designed to work with SLX-OS & NOS, leveraging the pyswitchlib library that works with both operating systems. But it is not going to work for NetIron systems.
There is interest in developing a NetIron driver for MLXe systems. This would probably start as a fork of the IOS driver.
Should we rename this driver to something like napalm-nos or napalm-slxos, and then create a new driver napalm-netiron, for MLXe devices?
Probably good to figure it out now, before code gets merged and people start using it :)
Thoughts?

I think we should do something like napalm-brocade-nos or napalm-brocade-slos.
Personally, I think napalm-platform is going to get too as the number of drivers increases (i.e. I will see napalm-nos and not know what it is refers to).
I think it is worth it to have the driver name be pretty self-explanatory as to what it is.

Yeah, I also like the idea of napalm-<vendor>-<platform>, similar to what you're doing with netmiko.

Hi @LindsayHill - thanks for clarifying this. I was really wondering what platforms is this driver going to support. At some point I just assumed that all of them would be covered. Certainly, I was wrong.
Yes, napalm-<vendor>-<platform> makes sense to me too. Let's see if @dbarrosop agrees and then I think we can rename.
Cheers,
Mircea

No problem, we can rename to napalm-brocade-nos or napalm-brocade-slxos. @LindsayHill feel free to pick one and I will rename the repo.

Hmmm, now I guess I better decide which one makes most sense. NOS is much more widely deployed today, but SLX-OS is the 'new' OS and should see more deployment from now on. Will doublecheck with someone else internally to see if they'll be using the "SLX-OS" or "NOS" name more.

OK, I think we should go with napalm-brocade-slxos. This will also work for NOS-based platforms (VDX). In future we can have napalm-brocade-netiron if/when we develop a driver for MLXe devices (these run NetIron).

Not sure thoughts on this but adding "-" could be helpful too. Often have to explain that one only used an API and not SSH.

On Mar 6, 2017, at 6:57 PM, Lindsay Hill notifications@github.com wrote:
OK, I think we should go with napalm-brocade-slxos. This will also work for NOS-based platforms (VDX). In future we can have napalm-brocade-netiron if/when we develop a driver for MLXe devices (these run NetIron).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

To clarify, knowing eos uses eapi is helpful like eos-eapi, or cisco-nxos-nxapi, or cisco-ios-ssh , etc.

On Mar 6, 2017, at 6:57 PM, Lindsay Hill notifications@github.com wrote:
OK, I think we should go with napalm-brocade-slxos. This will also work for NOS-based platforms (VDX). In future we can have napalm-brocade-netiron if/when we develop a driver for MLXe devices (these run NetIron).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

So the name for this one would be napalm-brocade-slxos-api? :)

In this case I'm not in favor of adding -<api>, if only because the driver should retain some flexibility to implement things as needed - e.g. maybe it mainly uses the API, but needs to use SSH for one specific thing.
FWIW, SLXOS will be almost all API, while NetIron will be SSH-based.

I don't think the name should encode too much information TBH, that's what the documentation is for. I will go with napalm-brocade-slxos.

This is done, feel free to reopen or comment if there is still some debate around the name :)

I agree that we shouldn't encode the transport (api versus ssh) into the Package name.

authors: LindsayHill dbarrosop jedelman8 ktbyers mirceaulinic

repo: napalm-automation/napalm-brocade


text:
Easier way to make points with no face color

🚀 Feature
Minor improvement: I'm using napari to visualize results of a cell finding algorithm. Would like to use points layer to draw circles around detections. My instinct was to try something like this:
viewer.add_points(yx, edge_color='magenta', face_color=None)
But this throws an error. As far as I can tell, the way to accomplish this is to use the ring marker, but this doesn't seem the best way to outline circular objects if you also want to provide shape information. Thoughts?

Hey @henrypinkard ! I think this should be possible. The Points layer wraps the vispy MarkersVisual. The face_color can be set with a ColorArray object, which has a alpha argument. We can make it such that when the Points layer face_color is set to None, the face color alpha is set to 0.  I think, this will make the face of the marker transparent. What do you think?
With regards to the ring marker, can you expand on what you mean by "doesn't seem the best way to outline circular objects if you also want to provide shape information"? You can pass a size to change the radius (can either by a single value that gets broadcasted to all markers in the layer or an array with sizes for each point).
viewer.add_points(yx, edge_color='magenta', symbol='ring', size=size_array)

Yeah sounds great!
Should have been a bit more clear on the second point. I just meant that if you want to 1) circle an object, 2) see the pixels within the circle, and 3) have the radius of the circle represent the object size, it is hard to do with the ring because by expanding the size in order to accomplish (2), you mess up (3) because both the inner and outer diameter enlarge simultaneously

Got it, that makes sense. I have another issue I’m working on, but I can get to this next!

This would be great. I'd prefer we use the explicit string 'transparent' instead of the python variable None as we sometime use None to trigger a guess or a use another default setting - which is maybe not the best practice, but it would lead to ambiguity here

I'm 👎 on "transparent", as it's not a color in any common color "dialects". (e.g. XKCD colors, the most extensive named color collection I know of, includes "dark forest green" but not "transparent".) We could just use (0,) * 4, and maybe None. I think None is fine, it can be the "default" when the actual default is properly specified in the signature.

Passing face_color = [0]*4 works right now on Shapes and Points (though setting layer.face_color=[0]*4 fails on Points and we need to fix). Passing (0,)*4 also should have worked, but throws an error which is definitely a bug and should be fixed in #774. Any 4-tuple fails right now, but a list of length 4 works. We should add tests to catch that too, and standardize this across layers using our colors.
@jni I was commenting more around a string representation that can be used within out color list, so users can say make shapes with no face color from the GUI.

I think the fact that 'transparent' doesn't appear in a survey of RGB colors is actually a very good sign that it would be a good word for an RGBA color where A is 0 as no one will be confused by it. I think '(0,) * 4' would be strange for a name. I'm fine with the string 'None' though if that is preferable to transparent. I'd just really prefer to avoid doing anything with the actual python variable None though as I just worry that shuts off so many options for us and creates so much ambiguity. That's why I still like 'transparent'. We also might want to curate that list of vispy colors too as right now there are many more than needed and that drop down is hard to use.
An alternative idea which renders much of this discussion moot would be to move away from that drop down menu to a more traditional color swatch display or color picker tab. Qt actually provides a `QColorDialog' - see here

that I'm sure we could adapt and possibly combine with the context boxes @tlambert03 has recently implemented. Curious what @tlambert03 thinks of this discussion too.
If we knew that we were going to do something like this soon then we don't have to support either 'transparent' or None.

Feature added in in #782 .

In napari 0.4.17 (vispy 0.11.0) in a conda environment on MacOS 13.1 (M1 Max) I cannot set a point's face color to be transparent independent of the edge color. I used to be able to do this by setting the alpha value of the face color, but this no longer has any effect, so perhaps something has changed recently? I can change the point opacity, but this changes both the edge color and the face color, and I want to only make the face transparent, not the edge. I tried to dig through the link to #782, but I could not find anything useful (there's a lot there, so maybe I missed it).
The inability to draw points as circles is pretty annoying, because the points occlude the selected parts that I want to see. I would think drawing points as rings with transparent faces would be something that many people would consider a standard feature for a library like this, but maybe I'm too niche ;) Anyway, if I'm missing something, please set me straight here. Otherwise, I think this issue needs to be reopened.

authors: henrypinkard jni kevinyamauchi marcel-goldschen-ohm sofroniewn

repo: napari/napari


text:
[FEATURE] UI(Thread): Use MUI Alerts

Description
Currently, we're only using native browser alerts for notifications. It'd be a great improvement to use MUI alerts/dialogs to create a consistent UI.
Screenshots
No response
Additional information
No response

Indeed it would be a good improvement!

I would be happy to add the MUI alerts.

Sure go ahead!
Ps. Project is currently down for some hours, so you might face some issues for now.


text:
Problems with installing autorift through conda.

Hi,
I want to install autoRIFT standalone through conda following the manual on https://github.com/conda-forge/autorift-feedstock. However, I failed with an error as follows:
PackagesNotFoundError: The following packages are not available from current channels:

  - autorift

Current channels:

  - https://conda.anaconda.org/conda-forge/win-64
  - https://conda.anaconda.org/conda-forge/noarch
  - https://repo.anaconda.com/pkgs/main/win-64
  - https://repo.anaconda.com/pkgs/main/noarch
  - https://repo.anaconda.com/pkgs/r/win-64
  - https://repo.anaconda.com/pkgs/r/noarch
  - https://repo.anaconda.com/pkgs/msys2/win-64
  - https://repo.anaconda.com/pkgs/msys2/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org

and use the search bar at the top of the page.

Is it still available to install autoRIFT through conda? Thanks!

@Wrootf the conda-forge recipe explicitly skips windows builds so it is not available on windows.
I'd be happy to review a PR to that feedstock that adds windows support, but I don't expect to do it myself any time soon.

authors: Wrootf jhkennedy

repo: nasa-jpl/autoRIFT


text:
Cropland: Tigray Ethiopia 2020

Start year: 2020
Start month: February

[x] Labeling project created
[x] Labeling completed
[x] Data added to repository
[x] Model trained
[x] Map made
[ ] Expert check

The labels for validation/test for this have already been completed last year. The data associated with the labels has been exported too, but I think we should re-export them since there have been changes since the last time it was done. @ivanzvonkov do you agree?

Yes you can see the data that is already available here:
https://github.com/nasaharvest/crop-mask/blob/74913ceff6b4bc4c3fd88f0aa3a381043108ffc9/data/report.txt#L132
The csv files can be accessed by running the following inside a cloned repo
dvc pull data/datasets

The data has been updated according to various changes over the last year. One outstanding change is using data with nans instead of skipping it. This can be achieved by
First, deleting the csv from data/datasets
Then
dvc commit data/datasets
dvc push
git add .
git commit -m'Update data'
git push

This will run the data pipeline and automatically generated new csvs with missing data not skipped.

Model is trained, pending merge of #266

first map draft

something funky? does not capture entire Tigray state

Retrain model without ERA5 data. Middle artifacts present in above seem to be in line with ERA5 sized tiling - Dr. Kerner

Retrained 2020 model without ERA5 data. Changed testing and validation metrics here

@bhyeh is the new map ready for review? Does it have artifacts and/or missing data?

Here is a link for the latest map for 2020. Was having issues with missing predictions the last few tries - but all is well now!

Yes @hannah-rae, I can set it up for @bhyeh

@bhyeh, Corrective labeling for Tigray 2020](https://aasareansah.users.earthengine.app/view/corrective-labeling-tigray-feb-2020-2021). More resources can also be found here

Next step: @bhyeh to make updated Tigray 2020 map with model updated with corrective labels

authors: MsPixels bhyeh hannah-rae ivanzvonkov

repo: nasaharvest/crop-mask


text:
Tidy XML output

I recently switched to this Node package for its versatility and I'm loving it. However, one thing I was missing is an option to format the XML output when using js2xml(). Consider the following example.
1.) Input object:
var obj = {
  _comment: " Released under The MIT License ",
  snippet: {
    content: {
      _cdata: "console.log($1)"
    },
    tabTrigger: {
      _text: "log"
    },
    scope: {
      _text: "source.js"
    }
  }
};

2.) Output XML – convert.json2xml(obj, {compact: true}):
<!-- Released under The MIT License --><snippet><content><![CDATA[console.log($1)]]></content><tabTrigger>log</tabTrigger><scope>source.js</scope></snippet>

3.) Output XML – convert.json2xml(obj, {compact: false, spaces: 4}):
<!-- The MIT License -->
    <snippet>
        <content/>
        <tabTrigger/>
        <scope/></snippet>

The output in 2.) is technically valid, but I would prefer an option that produces tidy/beautified XML. Unless I did something wrong, adding the spaces: 4 options produces an undesired result, why is both _cdata and _text missing?
Expected result (also note the indentation):
<!-- The MIT License -->
<snippet>
    <content><![CDATA[console.log($1)]]></content>
    <tabTrigger>log</tabTrigger>
    <scope>source.js</scope>
</snippet>

Not sure whether this is a bug or a misunderstanding of mine.
PS: I also tried converting the object to JSON with pretty-print and then use json2xml() instead – the results are the same!

Yes this is a bug.
I fixed this in v0.9.4.
Let me know if it is not as per your expectation.

Thank you, works great!

authors: idleberg nashwaan

repo: nashwaan/xml-js


text:
Implement FileTest#grpowned? and Process#groups

The specs of  FileTest#grpowned? depend on Process#groups, so this combination makes more sense than one would guess at first glance.

I did just push a newer version, it turns out you can call getgroups(2) with an empty buffer to query the number of groups. This might fix the Mac OS issue (or it might just as well be something completely unrelated).

https://github.com/natalie-lang/natalie/actions/runs/6275680663/job/17043679620?pr=1233
I added some debug output to the Mac OS run:
id -G
20 0 12 61 79 80 81 98 264 399 701 33 100 204 250 395 398 400

Run /usr/bin/id -G
20 0 12 61 79 80 81 98 264 399 701 33 100 204 250 395 398 400

Run ruby -e 'p Process.groups'
[20, 0, 12, 61, 79, 80, 81, 98, 264, 399, 701, 33, 100, 204, 250, 395, 398, 400]

Run bin/natalie -e 'p Process.groups'
[20, 0, 12, 61, 79, 80, 81, 98, 264, 399, 701, 33, 100, 204, 250, 395]

This still feels like we pass in a max of 16 and therefor don't retrieve the last two values.

Next attempt: use getgrouplist(3) instead of getgroups(2). If that doesn't work, I'm tempted to just disable the tests on Mac.

I believe MRI is setting _DARWIN_C_SOURCE here.
With the following C program:
#include <stdio.h>
#include <unistd.h>

int main() {
  int ngroups;

  ngroups = getgroups(0, NULL);
  printf("num = %d\n", ngroups);

  return 0;
}

...I get 16 as the result:
→ clang -o wat wat.c && ./wat
num = 16

...but if I define that macro, I get:
clang -o wat -D_DARWIN_C_SOURCE wat.c && ./wat   2.6.10p210
num = 17

I guess I was so focused on Process.groups that I completely forgot to update FileTest#grpowned? to fetch the required size of the groups list too. I updated that one too, let's hope the sixth time is a charm

Yay!

repo: natalie-lang/natalie