有关/apollo/cyber/conf/cyber.pb.conf的run_mode_conf字段的问题。

Describe the bug
cyber.pb.conf当中的run_mode_conf可以被设置成MODE_SIMULATION或者MODE_REALITY，该配置在Apollo里多次被检测，例如
/apollo/modules/perception/onboard/transform_wrapper/transform_wrapper.cc的QueryTrans函数中就会检测运行模式，如果是REALITY模式下就会要求点云frame数据的时间戳和系统时间相近或者一致，否做就报错transform模块不存在。
E0419 06:10:56.087642 368229 transform_wrapper.cc:279] [mainboard]Can not find transform.<PHONE_NUMBER>.494726419 frame_id: world child_frame_id: novatel Error info: Lookup would require extrapolation into the past.  Requested time<PHONE_NUMBER>494726400 but the earliest data is at time<PHONE_NUMBER>580000000, when looking up transform from frame [novatel] to frame [world]:timeout
I0419 06:10:56.087679 368229 transform_wrapper.cc:106] [mainboard]ERROR: query earlier timestamp than transform cache
E0419 06:10:56.087687 368229 lidar_detection_component.cc:166] [mainboard]Failed to get pose at time: 1.51381e+09

因此我尝试将该字段修改成MODE_SIMULATION，然后奇怪的事情发生了，我用cyber_recorder播放测试数据，然后cyber_moniter里没有任何channel数据。
另外有个额外问题，即便当我把字段改回成MODE_REALITY之后，cyber_moniter可以看到channel数据，但是dreamview还是没有任何显示。这很奇怪。
To Reproduce
Steps to reproduce the behavior:

修改/apollo/cyber/conf/cyber.pb.conf的run_mode_conf字段为MODE_SIMULATION
尝试播放数据cyber_recorder play -l -f ./sensor_rgb.record
查看cyber_moniter
cyber_moniter里没有channel数据

Expected behavior
理论上/apollo/cyber/conf/cyber.pb.conf不应该影响cyber数据交互
Desktop (please complete the following information):

OS: docker环境
Version: Apollo8.0

蹲后续😮😮😮😮😮

MODE_SIMULATION for simulation or user can control step by step, I can't confirm if this feature is fully enabled at the moment.
For the other question, cyber_moniter can see data but dreamview not. I don't know if we need to restart dreamview to make the configuration take effect, we can check the code and feedback then

MODE_SIMULATION for simulation or user can control step by step, I can't confirm if this feature is fully enabled at the moment.
For the other question, cyber_moniter can see data but dreamview not. I don't know if we need to restart dreamview to make the configuration take effect, we can check the code and feedback then

Thank you for your reply. In this situation, if I use MODE_REALITY, transform_wrapper will check the time stamp from point cloud frame code, then report that "Can not find transform.". Is there any workaround to avoid this error?

Honestly, I will confirm this feature and I will give you feedback before next Wednesday

Honestly, I will confirm this feature and I will give you feedback before next Wednesday

Same question. Cyber_monitor can not see any data when the run_mode is set to be MODE_SIMULATION.However, I can see data by using cyber_channel echo /apollo/canbus/chassis outside of the apollo docker

Honestly, I will confirm this feature and I will give you feedback before next Wednesday

Same question. Cyber_monitor can not see any data when the run_mode is set to be MODE_SIMULATION.However, I can see data by using cyber_channel echo /apollo/canbus/chassis outside of the apollo docker

run_mode_conf {
run_mode: MODE_SIMULATION
clock_mode: MODE_MOCK
}


Failure to return --match *

works correctly in push pull  but...
Fails to return correct matches when attempting to list/stat files of a given type.
command:
drive list gdrive/.../folder --match VOB
returns:
"/../--matches" cannot be found remotely
"/../VOB" cannot be found remotely
/.../all_files_in_folder
list still works, but does not match.

Hello @mitote thanks for reporting this and welcome to drive!
So Go's command line parser accepts options first before arguments therefore to make your command work, please pass in the arguments with "--" before the arguments like this:
- drive list gdrive/.../folder --match VOB
+ drive list --match VOB gdrive/.../folder

Hi @odeke-em and thanks for supporting this awesome program.
I should have waited a little to report the bug.
I have tried every combination of syntax I could think of without success including the above syntax.
Attempted Syntax:
drive list gdrive/.../folder --match VOB
drive list gdrive/.../folder -match VOB
drive list gdrive/.../folder match VOB
 variations with quotation marks
All return
"/../--matches" cannot be found remotely
"/../VOB" cannot be found remotely
...
Attempted Syntax:
drive list  --match VOB gdrive/.../folder
...all previous variations with this syntax and more
All return
no drive context found; run drive initor go into one of the directories (sub directories) that you performeddrive init
Definitely already initialized and functioning correctly.
I will attempt the following:

Updating to go-1.5.1
Testing on another machine (when I can get to it) and/or OS
shake my fists at the screen

I've written a work around in the mean time but if it helps I'll keep this thread up to date on my problem.

Please go into gdrive and repeat the syntax with what I had suggested, that's what the issue is.
See drive works in contexts, that is if you run a directory either it is a sub directory or the main directory that you ran drive init in and has a .gd directory.

So simple yet far down on my list of things to try.
I will re-evaluate my approach.
Yes this works.  Many Thanks.

No worries, am glad I could be of help and thanks for checking out drive plus for the patience.


New version: Ryujinx.Ryujinx.Ava version 1.1.1100

Pull request has been created with Komac v1.11.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Exception during executable launch operation System.InvalidOperationException: No process is associated with this object.

@wingetbot waivers Add Validation-Executable-Error

@rakleed why do you submit regular ryujinx zip into Avalonia package?

@soredake thanks for pointing it out, I'll fix it.


change file extension for VS Code notebooks

The current file extension, .dotnet-interactive, is a placeholder. We should come up with something more concise.

Here are some suggestions

.dib - dotnet interactive book

.dibs - dotnet interactive book scripts

.dsx - dotnet scripts

mls - multi

dni - dotnet interactive

.inet - interact

.dsx
.dni
.mls

dibs
dsx
dib
"Hey can you share that .dibs file ?"
" Do you have that dibs file"?

I think my favorite is

.dni

What about:

.icsn
.innb (interactive .net notebook, pronounced "inn-bee".

It will show my age, but a "dib" once referred to a "device independent bitmap".

I’ve got dibs on this one.

I liked the idea of having NB for notebook in it.

dnnb : has no real results if I google for it.

Most of the suggestions so far have common files that exist with that extensions. That's not necessarily a show stopper.

No real results in terms of an existing file extension that is :)

@glennc  and @BillWagner  I like both your suggestions. .NET Interactive isn't purely for notebooks so, we were trying to leave out of the name. But, I really like both your suggestions

dnnb  : dotnet notebooks
.innb (interactive .net notebook, pronounced "inn-bee".
cc @jonsequitur  thoughts

I think the "nb" suffix helps make the association to notebooks so even though these files are also usable as automation scripts, that might be less important.

oh my it's gotta be .dnb, dni, dib, any of those.

Yep, was thinking .dnb too. Three letters is best and dnb is fun anyways because

Thanks @jongalloway  and @shanselman I kind of like dnb  because it could be dotnet books or dotnet notebooks.
Low-key  I am still rooting for . dib

with all due respect I don't like the .dni option. I can't not think of "DNI" - 'do not resuscitate'. my favorite was dib but now I think I like dnb better. I mean, I was a d'n'b dj for a moment.
but not dni.

@bradygaster good point about .dni.  I also immediately think about D&I as well.
Looking at the options so far these three seem to resonate

.dib- dotnet interactive book
Pros: Catchy and simple.  Identifies it as .NET being interactive and can also be used in notebooks.
Cons: used to be device independent bitmap. Seems like it hasn't been used for a while.
.dnb - dotnet notebooks
Pros: Simplicity. It immediately resonates with a ecosystem the exist without mimicking it.
Cons: DNB file is a Microsoft Windows DNS Binary DNS Database.
.dnnb - dotnet notebooks
Pros: Not in use. Simple and resonates with an existing ecosystem.

I like .dib and .dnb
But looking at the pros and cons @LadyNaggaga has listed .dib is the best choice since device independent bitmap hasn't been used in awhile

I'd vote for dib first and dnb second.
I'm a bit of the fan of the "interactive book" because it does a better job of explaining what the document is for than notebook. The term "notebook", popularized by Jupyter (and MATLAB before that) is a child of the academic origins of these technologies -- but is super easy to conflate with others thing, like a OneNote notebook, for newbies to the ecosystem. It also obfuscates the best parts of these technologies: the interactivity portion.
I like that dib highlights how the document works (it's interactive!) instead of just what it is (it's a a notebook!).
Also, TBH, from my experience whether or not "nb" exists in the file extension won't really affect whether people colloquially refer to it as a notebook or not. That depends more on how it functions (does it have code cells, does it have outputs, does it have the concept of a "run cell") than what's in the file extension. So you can get away with not having nb in the extension but still using notebook in the marketing to indicate what it's all about it.
Anyhoooo, I'll stop rambling now but you can tell which one I am passionate about. :P

💯  @captainsafia

My top two choices are .dib and .dnb, in that order.
I agree that it's nice to keep "interactive" as part of the extension name so that this isn't thought of as just a notebook solution, and so that the transition from .dotnet-interactive -> new-extension-name is smooth. But .dnb is a really close and nice second choice.
I also can't help but think of all of the demo fun you could have when saying it's time to open your dib file 😄

I agree -- .dib or .dnb sounds best to me 👍

I really like dib. It's catchy, rolls off your tongue, and represents the product well.
I dislike dni. I think the acronym could conflict with other things as well (dotnet interop, dotnet installer, etc.) even though I know we're choosing a file extension not am acronym per se.

I also like .dib but wonder if the fact that Windows has a default icon for it would confuse people. Maybe not a big deal once people change their file association to VS Code?

My vote is for .dib or .dnb as well! Those two sound the best to me overall :)

My vote is for .dib or .dnb as well! Those two sound the best to me overall  - though, I'm slightly leaning towards .dib more ;)

.dib wins.
The latest version of the extension supports this.


lbry.tv marked as external site

The Issue
Steps to reproduce

Find a description with a lbry.tv hyperlink
Click the link

Expected behavior
You should navigate to the lbry.tv link
Actual behavior
You'll get a warning that lbry.tv is an external site
System Configuration

Browser version: Microsoft Edge (Chromium) Version <IP_ADDRESS> (Official build) dev (64-bit)
Operating system: Windows 10 x64

Screenshots

Fixed with #2605


Problem reading progx_charge sensor

You Inverter
Details about your Inverter: Sunsynk 8kw running SW ver (M <IP_ADDRESS> / S  <IP_ADDRESS> / C E.4.2.4)
Describe the issue/bug and what you expect
I've configured the 'system_mode' profile in the Sunsynk Inverter Add-on (dev) on Home Assistant.
Most everything seems to work nicely. But for some reason the progX_charge sensors are coming up with unknown value.
I suspect that it will also have issues trying to write settings (I have not tried this).
See below screenshots where the ProgX Charge sensors have unknown/no values
https://tinypic.host/i/RzRuA
https://tinypic.host/i/RzT9i
Am I perhaps specifying the sensors wrong? They look to be correct according to definitions.py
Is there perhaps anything I can do to make them work? Or should I rather remove them for now?
My Config
PORT: ""
DEVICE: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
DRIVER: umodbus
SUNSYNK_ID: "xxxxxxxxx"
SENSOR_PREFIX: ss
SENSORS:
  - essential_power
  - non_essential_power
  - aux_power
  - battery_soc
  - battery_power
  - battery_voltage
  - battery_current
  - battery_temperature
  - grid_power
  - grid_frequency
  - grid_voltage
  - grid_current
  - grid_ct_power
  - grid_ld_power
  - grid_l2_power
  - grid_connected_status
  - inverter_power
  - inverter_frequency
  - inverter_voltage
  - pv1_power
  - pv1_voltage
  - pv1_current
  - pv2_power
  - pv2_voltage
  - pv2_current
  - load_power
  - load_l1_power
  - load_l2_power
  - day_active_power
  - day_battery_charge
  - day_battery_discharge
  - day_grid_export
  - day_grid_import
  - day_load_power
  - day_pv_energy
  - day_reactive_power
  - month_grid_power
  - month_load_power
  - month_pv_power
  - total_active_power
  - total_battery_charge
  - total_battery_discharge
  - total_grid_export
  - total_grid_import
  - total_load_power
  - total_pv_power
  - year_grid_export
  - year_load_power
  - year_pv_power
  - control_mode
  - priority_mode
  - prog1_time
  - prog2_time
  - prog3_time
  - prog4_time
  - prog5_time
  - prog6_time
  - prog1_power
  - prog2_power
  - prog3_power
  - prog4_power
  - prog5_power
  - prog6_power
  - prog1_capacity
  - prog2_capacity
  - prog3_capacity
  - prog4_capacity
  - prog5_capacity
  - prog6_capacity
  - prog1_charge
  - prog2_charge
  - prog3_charge
  - prog4_charge
  - prog5_charge
  - prog6_charge
  - prog1_voltage
  - prog2_voltage
  - prog3_voltage
  - prog4_voltage
  - prog5_voltage
  - prog6_voltage
READ_SENSORS_BATCH_SIZE: 60
NUMBER_ENTITY_MODE: auto
PROFILES:
  - system_mode
  - system_mode_voltages
MODBUS_SERVER_ID: 1
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_USERNAME: *
MQTT_PASSWORD: *
DEBUG: 0

Logs (if applicable)
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2022-12-15 15:49:05,503 INFO    Loading HASS OS configuration
2022-12-15 15:49:05,522 DEBUG   could not patch umodbus: numpy not found
2022-12-15 15:49:05,529 INFO    ############################################################
2022-12-15 15:49:05,529 INFO      Sensor deprecated: day_active_power -> day_active_energy
2022-12-15 15:49:05,529 INFO    ############################################################
2022-12-15 15:49:05,530 INFO    ############################################################
2022-12-15 15:49:05,530 INFO        Sensor deprecated: day_load_power -> day_load_energy
2022-12-15 15:49:05,530 INFO    ############################################################
2022-12-15 15:49:05,531 INFO    ############################################################
2022-12-15 15:49:05,531 INFO    Sensor deprecated: day_reactive_power -> day_reactive_energy
2022-12-15 15:49:05,531 INFO    ############################################################
2022-12-15 15:49:05,531 INFO    ############################################################
2022-12-15 15:49:05,532 INFO      Sensor deprecated: month_grid_power -> month_grid_energy
2022-12-15 15:49:05,532 INFO    ############################################################
2022-12-15 15:49:05,532 INFO    ############################################################
2022-12-15 15:49:05,532 INFO      Sensor deprecated: month_load_power -> month_load_energy
2022-12-15 15:49:05,533 INFO    ############################################################
2022-12-15 15:49:05,533 INFO    ############################################################
2022-12-15 15:49:05,533 INFO        Sensor deprecated: month_pv_power -> month_pv_energy
2022-12-15 15:49:05,533 INFO    ############################################################
2022-12-15 15:49:05,534 INFO    ############################################################
2022-12-15 15:49:05,534 INFO    Sensor deprecated: total_active_power -> total_active_energy
2022-12-15 15:49:05,534 INFO    ############################################################
2022-12-15 15:49:05,535 INFO    ############################################################
2022-12-15 15:49:05,535 INFO      Sensor deprecated: total_load_power -> total_load_energy
2022-12-15 15:49:05,535 INFO    ############################################################
2022-12-15 15:49:05,535 INFO    ############################################################
2022-12-15 15:49:05,536 INFO        Sensor deprecated: total_pv_power -> total_pv_energy
2022-12-15 15:49:05,536 INFO    ############################################################
2022-12-15 15:49:05,536 INFO    ############################################################
2022-12-15 15:49:05,536 INFO       Sensor deprecated: year_load_power -> year_load_energy
2022-12-15 15:49:05,537 INFO    ############################################################
2022-12-15 15:49:05,537 INFO    ############################################################
2022-12-15 15:49:05,537 INFO         Sensor deprecated: year_pv_power -> year_pv_energy
2022-12-15 15:49:05,537 INFO    ############################################################
2022-12-15 15:49:05,539 INFO    Added hidden sensor battery_low_capacity as other sensors depend on it
2022-12-15 15:49:05,539 INFO    Added hidden sensor battery_low_voltage as other sensors depend on it
2022-12-15 15:49:05,539 INFO    Added hidden sensor battery_float_voltage as other sensors depend on it
2022-12-15 15:49:05,540 INFO    Filter *step used for aux_power, battery_current, battery_power, control_mode, day_reactive_power, essential_power, grid_ct_power, grid_current, grid_frequency, grid_l2_power, grid_ld_power, grid_power, inverter_frequency, inverter_power, load_l1_power, load_l2_power, load_power, non_essential_power, pv1_current, pv1_power, pv2_current, pv2_power
2022-12-15 15:49:05,540 INFO    Filter *last used for battery_soc, day_active_power, day_battery_charge, day_battery_discharge, day_grid_export, day_grid_import, day_load_power, day_pv_energy, grid_connected_status, month_grid_power, month_load_power, month_pv_power, total_active_power, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_load_power, total_pv_power, year_grid_export, year_load_power, year_pv_power
2022-12-15 15:49:05,540 INFO    Filter *avg used for battery_temperature, battery_voltage, grid_voltage, inverter_voltage, pv1_voltage, pv2_voltage
2022-12-15 15:49:05,540 INFO    Filter *round_robin used for priority_mode, prog1_capacity, prog1_charge, prog1_power, prog1_time, prog1_voltage, prog2_capacity, prog2_charge, prog2_power, prog2_time, prog2_voltage, prog3_capacity, prog3_charge, prog3_power, prog3_time, prog3_voltage, prog4_capacity, prog4_charge, prog4_power, prog4_time, prog4_voltage, prog5_capacity, prog5_charge, prog5_power, prog5_time, prog5_voltage, prog6_capacity, prog6_charge, prog6_power, prog6_time, prog6_voltage, prog6_voltage, prog6_voltage, prog6_voltage
2022-12-15 15:49:05,560 INFO    Reading startup sensors prog1_time, prog3_time, serial, prog6_time, battery_low_voltage, rated_power, prog4_time, prog5_time, battery_low_capacity, prog2_time, battery_float_voltage
2022-12-15 15:49:05,872 INFO    ############################################################
2022-12-15 15:49:05,873 INFO                Inverter serial number 'xxxxxxxx'
2022-12-15 15:49:05,873 INFO    ############################################################
2022-12-15 15:49:05,884 INFO    MQTT: Connecting to hass@core-mosquitto:1883
2022-12-15 15:49:05,906 INFO    MQTT: Connection successful

Just to note.
The progX_charge setting does write the correct values to the inverter when changing them, and it seems to remember the settings. Maybe the problem is just that initial value before actually setting it?

I suspect this is related to #72 your original prog_charge registers likely contained something else
@ASomerN no idea what inverter you have, but also completely different to this issu, so best to open your own with more info

Could be related to #72 yes.
It is strange that it would not read the original values (not sure what they were or how to check)
But I can set/change the values perfectly, and it reads the values that were manually set fine after that.

Some unrecognised bits in the register must have been set. Writing the new value changed them to a known state.
Unfortunately there is no way to check that now, except to see if something changed in the settings on the inverter…

Thanks @kellerza
I'll close this issue then.
I've left a comment on a closed PR, which I'm not sure was the best and most visible idea https://github.com/kellerza/sunsynk/pull/57#issuecomment-1354280980
How best to I raise this issue/question?
I'm willing to give the changes a stab if I can get some direction.

Hi @jabezz I've replied to your comment in that PR - since it's about adding new R/W sensors, can you create a new issue for it?

Some unrecognised bits in the register must have been set. Writing the new value changed them to a known state.
Unfortunately there is no way to check that now, except to see if something changed in the settings on the inverter…

Fully agree with this. I have replied in #78 with a similar response.
@jabezz if you can up the verbosity level in the logs so that we can get an idea of what the values of the ProgX..Charge sensors are being set to by the inverter, we might be able to figure out what bits are being set.

I believe @jabezz original issue has been resolved. Let's close this one in favour of other more specific issues

Hi,
I had only started using these sensors when they became available in the inverter add-on (not dev add-on).
I applied debug five to the non-dev addon and it crashed.
I've started the dev add-on with the same settings as the non-dev and this was logged:
2023-01-09 17:32:59,278 INFO    Loading HASS OS configuration
2023-01-09 17:32:59,280 INFO    PROFILES were deprecated. Please remove this configuration.
2023-01-09 17:32:59,347 INFO    ############################################################
2023-01-09 17:32:59,348 INFO        Sensor deprecated: total_pv_power -> total_pv_energy
2023-01-09 17:32:59,349 INFO    ############################################################
2023-01-09 17:32:59,349 DEBUG   last unit:kWh, id:total_pv_power
2023-01-09 17:32:59,350 DEBUG   last unit:kWh, id:total_battery_charge
2023-01-09 17:32:59,351 DEBUG   last unit:kWh, id:total_battery_discharge
2023-01-09 17:32:59,352 DEBUG   last unit:kWh, id:total_grid_export
2023-01-09 17:32:59,353 DEBUG   last unit:kWh, id:total_grid_import
2023-01-09 17:32:59,353 DEBUG   last unit:%, id:battery_soc
2023-01-09 17:32:59,354 DEBUG   step unit:W, id:grid_power
2023-01-09 17:32:59,355 DEBUG   step unit:W, id:pv1_power
2023-01-09 17:32:59,355 DEBUG   step unit:W, id:pv2_power
2023-01-09 17:32:59,356 DEBUG   step unit:W, id:battery_power
2023-01-09 17:32:59,357 DEBUG   step unit:W, id:load_power
2023-01-09 17:32:59,357 DEBUG   step unit:Hz, id:grid_frequency
2023-01-09 17:32:59,358 DEBUG   step unit:, id:control_mode
2023-01-09 17:32:59,359 INFO    Added hidden sensor battery_low_capacity as other sensors depend on it
2023-01-09 17:32:59,360 INFO    Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power
2023-01-09 17:32:59,360 INFO    Filter *step used for battery_power, control_mode, grid_frequency, grid_power, load_power, pv1_power, pv2_power
2023-01-09 17:32:59,361 INFO    Filter *round_robin used for priority_mode, prog1_capacity, prog1_charge, prog1_power, prog1_time, prog2_capacity, prog2_charge, prog2_power, prog2_time, prog3_capacity, prog3_charge, prog3_power, prog3_time, prog4_capacity, prog4_charge, prog4_power, prog4_time, prog5_capacity, prog5_charge, prog5_power, prog5_time, prog6_capacity, prog6_charge, prog6_charge, prog6_power, prog6_time
2023-01-09 17:32:59,362 DEBUG   Using selector: EpollSelector
2023-01-09 17:32:59,364 DEBUG   Connecting.
2023-01-09 17:32:59,387 DEBUG   Client connected to modbus server
2023-01-09 17:32:59,387 INFO    Protocol made connection.
2023-01-09 17:32:59,389 INFO    Connected to /dev/ttyUSB0
2023-01-09 17:32:59,389 INFO    Reading startup sensors serial, prog4_time, prog6_time, rated_power, prog1_time, prog5_time, battery_low_capacity, prog2_time, prog3_time
2023-01-09 17:32:59,394 DEBUG   send: 0x1 0x3 0x0 0x3 0x0 0x5 0x75 0xc9
2023-01-09 17:32:59,396 DEBUG   Adding transaction 1
2023-01-09 17:32:59,438 DEBUG   recv: 0x1
2023-01-09 17:32:59,438 DEBUG   Frame - [b'\x01'] not ready
2023-01-09 17:32:59,439 DEBUG   recv: 0x3 0xa
2023-01-09 17:32:59,440 DEBUG   Frame - [b'\x03\n'] not ready
2023-01-09 17:32:59,441 DEBUG   recv: 0x32
2023-01-09 17:32:59,442 DEBUG   Frame - [b'2'] not ready
2023-01-09 17:32:59,443 DEBUG   recv: 0x32 0x30
2023-01-09 17:32:59,444 DEBUG   Frame - [b'20'] not ready
2023-01-09 17:32:59,444 DEBUG   recv: 0x34
2023-01-09 17:32:59,445 DEBUG   Frame - [b'4'] not ready
2023-01-09 17:32:59,446 DEBUG   recv: 0x31 0x39
2023-01-09 17:32:59,447 DEBUG   Frame - [b'19'] not ready
2023-01-09 17:32:59,448 DEBUG   recv: 0x34 0x30
2023-01-09 17:32:59,448 DEBUG   Frame - [b'40'] not ready
2023-01-09 17:32:59,449 DEBUG   recv: 0x37
2023-01-09 17:32:59,450 DEBUG   Frame - [b'7'] not ready
2023-01-09 17:32:59,451 DEBUG   recv: 0x30 0x3e
2023-01-09 17:32:59,452 DEBUG   Frame - [b'0>'] not ready
2023-01-09 17:32:59,452 DEBUG   recv: 0xa
2023-01-09 17:32:59,453 DEBUG   Getting Frame - 0x3 0xa 0x32 0x32 0x30 0x34 0x31 0x39 0x34 0x30 0x37 0x30
2023-01-09 17:32:59,453 DEBUG   Factory Response[ReadHoldingRegistersResponse: 3]
2023-01-09 17:32:59,453 DEBUG   Frame advanced, resetting header!!
2023-01-09 17:32:59,454 DEBUG   Getting transaction 1
2023-01-09 17:32:59,455 DEBUG   Request registers: [3, 4, 5, 6, 7] glen=5. Response [12850, 12340, 12601, 13360, 14128] len=5. regs={3: 12850, 4: 12340, 5: 12601, 6: 13360, 7: 14128}
2023-01-09 17:32:59,456 DEBUG   send: 0x1 0x3 0x0 0x10 0x0 0x2 0xc5 0xce
2023-01-09 17:32:59,457 DEBUG   Adding transaction 1
2023-01-09 17:32:59,497 DEBUG   recv: 0x1
2023-01-09 17:32:59,498 DEBUG   Frame - [b'\x01'] not ready
2023-01-09 17:32:59,498 DEBUG   recv: 0x3
2023-01-09 17:32:59,499 DEBUG   Frame - [b'\x03'] not ready
2023-01-09 17:32:59,499 DEBUG   recv: 0x4
2023-01-09 17:32:59,500 DEBUG   Frame - [b'\x04'] not ready
2023-01-09 17:32:59,500 DEBUG   recv: 0x38
2023-01-09 17:32:59,501 DEBUG   Frame - [b'8'] not ready
2023-01-09 17:32:59,501 DEBUG   recv: 0x80
2023-01-09 17:32:59,502 DEBUG   Frame - [b'\x80'] not ready
2023-01-09 17:32:59,502 DEBUG   recv: 0x0
2023-01-09 17:32:59,503 DEBUG   Frame - [b'\x00'] not ready
2023-01-09 17:32:59,504 DEBUG   recv: 0x1
2023-01-09 17:32:59,504 DEBUG   Frame - [b'\x01'] not ready
2023-01-09 17:32:59,505 DEBUG   recv: 0x37
2023-01-09 17:32:59,505 DEBUG   Frame - [b'7'] not ready
2023-01-09 17:32:59,506 DEBUG   recv: 0x7b
2023-01-09 17:32:59,506 DEBUG   Getting Frame - 0x3 0x4 0x38 0x80 0x0 0x1
2023-01-09 17:32:59,506 DEBUG   Factory Response[ReadHoldingRegistersResponse: 3]
2023-01-09 17:32:59,507 DEBUG   Frame advanced, resetting header!!
2023-01-09 17:32:59,507 DEBUG   Getting transaction 1
2023-01-09 17:32:59,509 DEBUG   Request registers: [16, 17] glen=2. Response [14464, 1] len=2. regs={16: 14464, 17: 1}
2023-01-09 17:32:59,509 DEBUG   send: 0x1 0x3 0x0 0xdb 0x0 0x1 0xf4 0x31
2023-01-09 17:32:59,510 DEBUG   Adding transaction 1
2023-01-09 17:32:59,548 DEBUG   recv: 0x1
2023-01-09 17:32:59,548 DEBUG   Frame - [b'\x01'] not ready
2023-01-09 17:32:59,549 DEBUG   recv: 0x3
2023-01-09 17:32:59,550 DEBUG   Frame - [b'\x03'] not ready
2023-01-09 17:32:59,551 DEBUG   recv: 0x2 0x0
2023-01-09 17:32:59,552 DEBUG   Frame - [b'\x02\x00'] not ready
2023-01-09 17:32:59,553 DEBUG   recv: 0xf
2023-01-09 17:32:59,553 DEBUG   Frame - [b'\x0f'] not ready
2023-01-09 17:32:59,554 DEBUG   recv: 0xf8 0x40
2023-01-09 17:32:59,555 DEBUG   Not a valid unit id - 1, ignoring!!
2023-01-09 17:32:59,555 DEBUG   Resetting frame - Current Frame in buffer - 0x1 0x3 0x2 0x0 0xf 0xf8 0x40
2023-01-09 17:33:09,408 ERROR   Timeout reading:
2023-01-09 17:33:09,408 INFO    ############################################################
2023-01-09 17:33:09,409 INFO    No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc
2023-01-09 17:33:09,409 INFO    ############################################################
2023-01-09 17:33:09,409 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically.

@ASomerN from the logs you could not connect to the inverter. Most likely you still had the non-dev addon running.
Only one app can access the USB port at a time.
The only way to get 2x to connect is to use the mbusd addon to connect to the USB port and then you connect via tcp://ip:502 to mbusd from the addons

Hi,
I updated to the latest version and turned off the non-dev version. restarted the PI and then started dev with the config and it works.
Everything is working correctly on the latest dev version. The options are not flicking on/off. Updating each sensor is reflected right away on the inverter and in HA.
Looks to be resolved on the dev add-on.


how to handle static files (e.g., images)?

Hi @EstherPlomp, any thoughts on how to handle static files like images in this repo?
I often keep them in a separate cloud storage and then automatically download them into the repo (but not commit them) in order to keep the repository size small. however, this is a bit more complicated and perhaps a but unnecessary here since we are likely not including many large images anyways. let me know which way you would prefer to handle static files. thanks!

I think it might be nicer to include them in the repo and try to avoid too many images?
I don't have a lot of experience with doing it otherwise actually - but happy to also give that a try if you were planning to put images everywhere :)


Suppress deployment log generated by Azure CLI

Azure CLI will print the content of deployment manifest during deployment. There's feedback that we shouldn't print that, so remove the logs.

Hi @shyama1208 could you help review this pull request? Thank you!


96boards Poplar OE board support

Hi folks,
This pull request adds Poplar OE recipes for l-loader-poplar, ATF, U-Boot, and Linux. Currently this code is being pulled from Linaro GitHub but once various parts get upstreamed we should be able to switch to upstream repos.
This has been tested with rpb-console-image, and the resulting binaries once flashed onto the board, boot correctly and mount the rootfs.
Build artifacts are: -
fastboot.bin (contains mbr, l-loader, atf & u-boot): Once this is flashed board will boot into U-Boot on next reboot. mbr is being generated in l-loader-poplar repo via a script similar to hikey).
boot-poplar.img: fat boot image containing kernel, dtb and extlinux.conf
rpb-console-image-poplar.ext4 (rootfs)
Installation
Copy build artifacts onto a USB stick, and then hold USB boot button and turn on board. Board will boot into U-Boot from fastboot on USB stick.
Flashing
At U-boot prompt:
fatload usb 0:1 0x08000000 fastboot.bin
mmc write 0x08000000 0 0x780
fatload usb 0:1 0x08000000 boot-poplar.img
mmc write 0x08000000 0x2000 0x40000
fatload usb 0:1 0x08000000 rpb-console-image-poplar.ext4
mmc write 0x08000000 0x46800 <size of image in bytes divided by 512>
Reboot board. See boot log below
===
Bootrom start
Boot Media: eMMC
Decrypt auxiliary code ...OK
lsadc voltage min: 000000FF, max: 000000FF, aver: 000000FF, index: 00000000
Entry boot auxiliary code
Auxiliary code - v1.00
DDR code - V1.1.2 20160205
Build: Mar 24 2016 - 17:09:44
Reg Version:  v134
Reg Time:     2016/03/18 09:44:55
Reg Name:     hi3798cv2dmb_hi3798cv200_ddr3_2gbyte_8bitx4_4layers.reg
Boot auxiliary code success
Bootrom success
LOADER:  Switched to aarch64 mode
LOADER:  Entering ARM TRUSTED FIRMWARE
LOADER:  CPU0 executes at 0x000ce000
INFO:    BL1: 0xe1000 - 0xe7000 [size = 24576]
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v1.3(debug):dc20ebf
NOTICE:  BL1: Built : 19:38:45, Jun  6 2017
INFO:    BL1: RAM 0xe1000 - 0xe7000
INFO:    BL1: cortex_a53: errata workaround for 855873 was applied
INFO:    BL1: Loading BL2
INFO:    Loading image id=1 at address 0xe9000
INFO:    Image id=1 loaded at address 0xe9000, size = 0x5008
NOTICE:  BL1: Booting BL2
INFO:    Entry point address = 0xe9000
INFO:    SPSR = 0x3c5
NOTICE:  BL2: v1.3(debug):dc20ebf
NOTICE:  BL2: Built : 19:38:45, Jun  6 2017
INFO:    BL2: Loading BL31
INFO:    Loading image id=3 at address 0x129000
INFO:    Image id=3 loaded at address 0x129000, size = 0x8020
INFO:    BL2: Loading BL33
INFO:    Loading image id=5 at address 0x37000000
INFO:    Image id=5 loaded at address 0x37000000, size = 0x56867
NOTICE:  BL1: Booting BL31
INFO:    Entry point address = 0x129000
INFO:    SPSR = 0x3cd
INFO:    Boot BL33 from 0x37000000 for 354407 Bytes
NOTICE:  BL31: v1.3(debug):dc20ebf
NOTICE:  BL31: Built : 19:38:45, Jun  6 2017
INFO:    ARM GICv2 driver initialized
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: errata workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x37000000
INFO:    SPSR = 0x3c9
U-Boot 2017.05 (Jun 06 2017 - 19:18:00 +0200)poplar
Model: HiSilicon Poplar Development Board
BOARD: Hisilicon HI3798cv200 Poplar
DRAM:  1024 MiB
MMC:   Hisilicon DWMMC: 0
In:    serial@8b00000
Out:   serial@8b00000
Err:   serial@8b00000
Net:   Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
scanning usb for ethernet devices... 0 Ethernet Device(s) found
USB device 0: unknown device
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:2...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
240 bytes read in 4 ms (58.6 KiB/s)
1:      Reference-Platform-Build-X11
Retrieving file: /extlinux/../Image
reading /extlinux/../Image
15798784 bytes read in 1393 ms (10.8 MiB/s)
append: root=/dev/mmcblk0p3 rootfstype=ext4 rootwait rw append mem=1G earlycon console=ttyAMA0 console=
Retrieving file: /extlinux/../hi3798cv200-poplar.dtb
reading /extlinux/../hi3798cv200-poplar.dtb
9197 bytes read in 7 ms (1.3 MiB/s)
Flattened Device Tree blob at 32200000
Booting using the fdt blob at 0x32200000
Loading Device Tree to<PHONE_NUMBER>123000, end<PHONE_NUMBER>1283ec ... OK
Starting kernel ...
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.11.2-g035bdfc-dirty (oe-user@oe-host) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02-rc3~dev) ) #1 SMP PREEMPT Tue Jun 6 19:26:14 CEST 2017
[    0.000000] Boot CPU: AArch64 Processor [410fd034]
[    0.000000] Memory limited to 1024MB
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 16 MiB at 0x000000003f000000
[    0.000000] earlycon: pl11 at MMIO 0x00000000f8b00000 (options '115200n8')
[    0.000000] bootconsole [pl11] enabled
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000003fffffff]
[    0.000000] NUMA: Adding memblock [0x0 - 0x128fff] on node 0
[    0.000000] NUMA: Adding memblock [0x132000 - 0x3fffffff] on node 0
[    0.000000] NUMA: Initmem setup node 0 [mem 0x00000000-0x3fffffff]
[    0.000000] NUMA: NODE_DATA [mem 0x3efe6200-0x3efe7cff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000000000-0x000000003fffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000000128fff]
[    0.000000]   node   0: [mem 0x0000000000132000-0x000000003fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003fffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.0 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] percpu: Embedded 23 pages/cpu @ffff80003ef87000 s56856 r8192 d29160 u94208
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: enabling workaround for ARM erratum 845719
[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 258039
[    0.000000] Policy zone: DMA
[    0.000000] Kernel command line: root=/dev/mmcblk0p3 rootfstype=ext4 rootwait rw append mem=1G earlycon console=ttyAMA0 console=
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Memory: 999392K/1048540K available (9084K kernel code, 1028K rwdata, 4160K rodata, 1088K init, 407K bss, 32764K reserved, 16384K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     modules : 0xffff000000000000 - 0xffff000008000000   (   128 MB)
[    0.000000]     vmalloc : 0xffff000008000000 - 0xffff7dffbfff0000   (129022 GB)
[    0.000000]       .text : 0xffff000008080000 - 0xffff000008960000   (  9088 KB)
[    0.000000]     .rodata : 0xffff000008960000 - 0xffff000008d80000   (  4224 KB)
[    0.000000]       .init : 0xffff000008d80000 - 0xffff000008e90000   (  1088 KB)
[    0.000000]       .data : 0xffff000008e90000 - 0xffff000008f91200   (  1029 KB)
[    0.000000]        .bss : 0xffff000008f91200 - 0xffff000008ff6eac   (   408 KB)
[    0.000000]     fixed   : 0xffff7dfffe7fd000 - 0xffff7dfffec00000   (  4108 KB)
[    0.000000]     PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000   (    16 MB)
[    0.000000]     vmemmap : 0xffff7e0000000000 - 0xffff800000000000   (  2048 GB maximum)
[    0.000000]               0xffff7e0000000000 - 0xffff7e0001000000   (    16 MB actual)
[    0.000000]     memory  : 0xffff800000000000 - 0xffff800040000000   (  1024 MB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 64.
[    0.000000]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[    0.000000] NR_IRQS:64 nr_irqs:64 0
[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns:<PHONE_NUMBER>92 ns
[    0.000003] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every<PHONE_NUMBER>097ns
[    0.008248] Console: colour dummy device 80x25
[    0.012768] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.023150] pid_max: default: 32768 minimum: 301
[    0.027858] Security Framework initialized
[    0.032158] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.039944] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[    0.047150] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.053928] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.077185] ASID allocator initialised with 65536 entries
[    0.090858] EFI services will not be available.
[    0.111460] smp: Bringing up secondary CPUs ...
[    0.148127] Detected VIPT I-cache on CPU1
[    0.148159] CPU1: Booted secondary processor [410fd034]
[    0.180148] Detected VIPT I-cache on CPU2
[    0.180165] CPU2: Booted secondary processor [410fd034]
[    0.212183] Detected VIPT I-cache on CPU3
[    0.212198] CPU3: Booted secondary processor [410fd034]
[    0.212228] smp: Brought up 1 node, 4 CPUs
[    0.244345] SMP: Total of 4 processors activated.
[    0.249099] CPU features: detected feature: 32-bit EL0 Support
[    0.255019] CPU: All CPU(s) started at EL2
[    0.259167] alternatives: patching kernel code
[    0.264209] devtmpfs: initialized
[    0.268787] DMI not present or invalid.
[    0.272767] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>100000 ns
[    0.282648] futex hash table entries: 1024 (order: 5, 131072 bytes)
[    0.289335] pinctrl core: initialized pinctrl subsystem
[    0.295347] NET: Registered protocol family 16
[    0.303893] cpuidle: using governor menu
[    0.308111] vdso: 2 pages (1 code @ ffff000008967000, 1 data @ ffff000008e95000)
[    0.315598] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.323121] DMA: preallocated 256 KiB pool for atomic allocations
[    0.329508] Serial: AMBA PL011 UART driver
[    0.334668] f8b00000.serial: ttyAMA0 at MMIO 0xf8b00000 (irq = 5, base_baud = 0) is a PL011 rev2
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.11.2-g035bdfc-dirty (oe-user@oe-host) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02-rc3~dev) ) #1 SMP PREEMPT Tue Jun 6 19:26:14 CEST 2017
[    0.000000] Boot CPU: AArch64 Processor [410fd034]
[    0.000000] Memory limited to 1024MB
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 16 MiB at 0x000000003f000000
[    0.000000] earlycon: pl11 at MMIO 0x00000000f8b00000 (options '115200n8')
[    0.000000] bootconsole [pl11] enabled
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000003fffffff]
[    0.000000] NUMA: Adding memblock [0x0 - 0x128fff] on node 0
[    0.000000] NUMA: Adding memblock [0x132000 - 0x3fffffff] on node 0
[    0.000000] NUMA: Initmem setup node 0 [mem 0x00000000-0x3fffffff]
[    0.000000] NUMA: NODE_DATA [mem 0x3efe6200-0x3efe7cff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000000000-0x000000003fffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000000128fff]
[    0.000000]   node   0: [mem 0x0000000000132000-0x000000003fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003fffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.0 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] percpu: Embedded 23 pages/cpu @ffff80003ef87000 s56856 r8192 d29160 u94208
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: enabling workaround for ARM erratum 845719
[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 258039
[    0.000000] Policy zone: DMA
[    0.000000] Kernel command line: root=/dev/mmcblk0p3 rootfstype=ext4 rootwait rw append mem=1G earlycon console=ttyAMA0 console=
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Memory: 999392K/1048540K available (9084K kernel code, 1028K rwdata, 4160K rodata, 1088K init, 407K bss, 32764K reserved, 16384K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     modules : 0xffff000000000000 - 0xffff000008000000   (   128 MB)
[    0.000000]     vmalloc : 0xffff000008000000 - 0xffff7dffbfff0000   (129022 GB)
[    0.000000]       .text : 0xffff000008080000 - 0xffff000008960000   (  9088 KB)
[    0.000000]     .rodata : 0xffff000008960000 - 0xffff000008d80000   (  4224 KB)
[    0.000000]       .init : 0xffff000008d80000 - 0xffff000008e90000   (  1088 KB)
[    0.000000]       .data : 0xffff000008e90000 - 0xffff000008f91200   (  1029 KB)
[    0.000000]        .bss : 0xffff000008f91200 - 0xffff000008ff6eac   (   408 KB)
[    0.000000]     fixed   : 0xffff7dfffe7fd000 - 0xffff7dfffec00000   (  4108 KB)
[    0.000000]     PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000   (    16 MB)
[    0.000000]     vmemmap : 0xffff7e0000000000 - 0xffff800000000000   (  2048 GB maximum)
[    0.000000]               0xffff7e0000000000 - 0xffff7e0001000000   (    16 MB actual)
[    0.000000]     memory  : 0xffff800000000000 - 0xffff800040000000   (  1024 MB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 64.
[    0.000000]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[    0.000000] NR_IRQS:64 nr_irqs:64 0
[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns:<PHONE_NUMBER>92 ns
[    0.000003] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every<PHONE_NUMBER>097ns
[    0.008248] Console: colour dummy device 80x25
[    0.012768] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.023150] pid_max: default: 32768 minimum: 301
[    0.027858] Security Framework initialized
[    0.032158] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.039944] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[    0.047150] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.053928] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.077185] ASID allocator initialised with 65536 entries
[    0.090858] EFI services will not be available.
[    0.111460] smp: Bringing up secondary CPUs ...
[    0.148127] Detected VIPT I-cache on CPU1
[    0.148159] CPU1: Booted secondary processor [410fd034]
[    0.180148] Detected VIPT I-cache on CPU2
[    0.180165] CPU2: Booted secondary processor [410fd034]
[    0.212183] Detected VIPT I-cache on CPU3
[    0.212198] CPU3: Booted secondary processor [410fd034]
[    0.212228] smp: Brought up 1 node, 4 CPUs
[    0.244345] SMP: Total of 4 processors activated.
[    0.249099] CPU features: detected feature: 32-bit EL0 Support
[    0.255019] CPU: All CPU(s) started at EL2
[    0.259167] alternatives: patching kernel code
[    0.264209] devtmpfs: initialized
[    0.268787] DMI not present or invalid.
[    0.272767] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>100000 ns
[    0.282648] futex hash table entries: 1024 (order: 5, 131072 bytes)
[    0.289335] pinctrl core: initialized pinctrl subsystem
[    0.295347] NET: Registered protocol family 16
[    0.303893] cpuidle: using governor menu
[    0.308111] vdso: 2 pages (1 code @ ffff000008967000, 1 data @ ffff000008e95000)
[    0.315598] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.323121] DMA: preallocated 256 KiB pool for atomic allocations
[    0.329508] Serial: AMBA PL011 UART driver
[    0.334668] f8b00000.serial: ttyAMA0 at MMIO 0xf8b00000 (irq = 5, base_baud = 0) is a PL011 rev2
[    0.887859] console [ttyAMA0] enabled
[    0.887859] console [ttyAMA0] enabled
[    0.895470] f8b02000.serial: ttyAMA2 at MMIO 0xf8b02000 (irq = 6, base_baud = 0) is a PL011 rev2
[    0.895470] f8b02000.serial: ttyAMA2 at MMIO 0xf8b02000 (irq = 6, base_baud = 0) is a PL011 rev2
[    0.913509] OF: amba_device_add() failed (-19) for /soc@f0000000/spi@8b1a000
[    0.913509] OF: amba_device_add() failed (-19) for /soc@f0000000/spi@8b1a000
[    0.928176] OF: amba_device_add() failed (-19) for /soc@f0000000/gpio@8004000
[    0.928176] OF: amba_device_add() failed (-19) for /soc@f0000000/gpio@8004000
[    0.949030] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.949030] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.962343] ACPI: Interpreter disabled.
[    0.962343] ACPI: Interpreter disabled.
[    0.970435] vgaarb: loaded
[    0.970435] vgaarb: loaded
[    0.976571] SCSI subsystem initialized
[    0.976571] SCSI subsystem initialized
[    0.984393] usbcore: registered new interface driver usbfs
[    0.984393] usbcore: registered new interface driver usbfs
[    0.995464] usbcore: registered new interface driver hub
[    0.995464] usbcore: registered new interface driver hub
[    1.006191] usbcore: registered new device driver usb
[    1.006191] usbcore: registered new device driver usb
[    1.016522] media: Linux media interface: v0.10
[    1.016522] media: Linux media interface: v0.10
[    1.025683] Linux video capture interface: v2.00
[    1.025683] Linux video capture interface: v2.00
[    1.035003] pps_core: LinuxPPS API ver. 1 registered
[    1.035003] pps_core: LinuxPPS API ver. 1 registered
[    1.044971] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    1.044971] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    1.063339] PTP clock support registered
[    1.063339] PTP clock support registered
[    1.071309] dmi: Firmware registration failed.
[    1.071309] dmi: Firmware registration failed.
[    1.080318] Advanced Linux Sound Architecture Driver Initialized.
[    1.080318] Advanced Linux Sound Architecture Driver Initialized.
[    1.093053] clocksource: Switched to clocksource arch_sys_counter
[    1.093053] clocksource: Switched to clocksource arch_sys_counter
[    1.105390] VFS: Disk quotas dquot_6.6.0
[    1.105390] VFS: Disk quotas dquot_6.6.0
[    1.113300] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.113300] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.127243] pnp: PnP ACPI: disabled
[    1.127243] pnp: PnP ACPI: disabled
[    1.137860] NET: Registered protocol family 2
[    1.137860] NET: Registered protocol family 2
[    1.146910] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    1.146910] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    1.161135] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[    1.161135] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[    1.174334] TCP: Hash tables configured (established 8192 bind 8192)
[    1.174334] TCP: Hash tables configured (established 8192 bind 8192)
[    1.187174] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    1.187174] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    1.199082] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    1.199082] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    1.211935] NET: Registered protocol family 1
[    1.211935] NET: Registered protocol family 1
[    1.220881] RPC: Registered named UNIX socket transport module.
[    1.220881] RPC: Registered named UNIX socket transport module.
[    1.232774] RPC: Registered udp transport module.
[    1.232774] RPC: Registered udp transport module.
[    1.242227] RPC: Registered tcp transport module.
[    1.242227] RPC: Registered tcp transport module.
[    1.251672] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.251672] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.265071] kvm [1]: 8-bit VMID
[    1.265071] kvm [1]: 8-bit VMID
[    1.271374] kvm [1]: IDMAP page: 3094d000
[    1.271374] kvm [1]: IDMAP page: 3094d000
[    1.279425] kvm [1]: HYP VA range:<PHONE_NUMBER>00:ffffffffffff
[    1.279425] kvm [1]: HYP VA range:<PHONE_NUMBER>00:ffffffffffff
[    1.291254] kvm [1]: Hyp mode initialized successfully
[    1.291254] kvm [1]: Hyp mode initialized successfully
[    1.301597] kvm [1]: virtual timer IRQ3
[    1.301597] kvm [1]: virtual timer IRQ3
[    1.310556] audit: initializing netlink subsys (disabled)
[    1.310556] audit: initializing netlink subsys (disabled)
[    1.321483] audit: type=2000 audit(1.184:1): state=initialized audit_enabled=0 res=1
[    1.321483] audit: type=2000 audit(1.184:1): state=initialized audit_enabled=0 res=1
[    1.321642] workingset: timestamp_bits=44 max_order=18 bucket_order=0
[    1.321642] workingset: timestamp_bits=44 max_order=18 bucket_order=0
[    1.325702] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.325702] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.326039] NFS: Registering the id_resolver key type
[    1.326039] NFS: Registering the id_resolver key type
[    1.326055] Key type id_resolver registered
[    1.326055] Key type id_resolver registered
[    1.326056] Key type id_legacy registered
[    1.326056] Key type id_legacy registered
[    1.326062] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.326062] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.326176] 9p: Installing v9fs 9p2000 file system support
[    1.326176] 9p: Installing v9fs 9p2000 file system support
[    1.337786] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    1.337786] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    1.337790] io scheduler noop registered
[    1.337790] io scheduler noop registered
[    1.337907] io scheduler cfq registered (default)
[    1.337907] io scheduler cfq registered (default)
[    1.337909] io scheduler mq-deadline registered
[    1.337909] io scheduler mq-deadline registered
[    1.351332] pl061_gpio f8b21000.gpio: PL061 GPIO chip @0x00000000f8b21000 registered
[    1.351332] pl061_gpio f8b21000.gpio: PL061 GPIO chip @0x00000000f8b21000 registered
[    1.351544] pl061_gpio f8b22000.gpio: PL061 GPIO chip @0x00000000f8b22000 registered
[    1.351544] pl061_gpio f8b22000.gpio: PL061 GPIO chip @0x00000000f8b22000 registered
[    1.351751] pl061_gpio f8b23000.gpio: PL061 GPIO chip @0x00000000f8b23000 registered
[    1.351751] pl061_gpio f8b23000.gpio: PL061 GPIO chip @0x00000000f8b23000 registered
[    1.351942] pl061_gpio f8b24000.gpio: PL061 GPIO chip @0x00000000f8b24000 registered
[    1.351942] pl061_gpio f8b24000.gpio: PL061 GPIO chip @0x00000000f8b24000 registered
[    1.352143] pl061_gpio f8b26000.gpio: PL061 GPIO chip @0x00000000f8b26000 registered
[    1.352143] pl061_gpio f8b26000.gpio: PL061 GPIO chip @0x00000000f8b26000 registered
[    1.352340] pl061_gpio f8b2a000.gpio: PL061 GPIO chip @0x00000000f8b2a000 registered
[    1.352340] pl061_gpio f8b2a000.gpio: PL061 GPIO chip @0x00000000f8b2a000 registered
[    1.354291] xenfs: not registering filesystem on non-xen platform
[    1.354291] xenfs: not registering filesystem on non-xen platform
[    1.356245] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.356245] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.357100] SuperH (H)SCI(F) driver initialized
[    1.357100] SuperH (H)SCI(F) driver initialized
[    1.357263] msm_serial: driver initialized
[    1.357263] msm_serial: driver initialized
[    1.361784] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    1.361784] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    1.365411] loop: module loaded
[    1.365411] loop: module loaded
[    1.365778] hisi_sas: driver version v1.6
[    1.365778] hisi_sas: driver version v1.6
[    1.366801] libphy: Fixed MDIO Bus: probed
[    1.366801] libphy: Fixed MDIO Bus: probed
[    1.367009] tun: Universal TUN/TAP device driver, 1.6
[    1.367009] tun: Universal TUN/TAP device driver, 1.6
[    1.429155] libphy: hix5hd2_mii_bus: probed
[    1.429155] libphy: hix5hd2_mii_bus: probed
[    1.429443] (unnamed net_device) (uninitialized): using random MAC address d2:86:1b:81:29:6f
[    1.429443] (unnamed net_device) (uninitialized): using random MAC address d2:86:1b:81:29:6f
[    1.436432] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.436432] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.436433] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.436433] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.436465] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[    1.436465] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[    1.436466] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.436466] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.436489] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    1.436489] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    1.436490] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.436490] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.436512] sky2: driver version 1.30
[    1.436512] sky2: driver version 1.30
[    1.436789] VFIO - User Level meta-driver version: 0.3
[    1.436789] VFIO - User Level meta-driver version: 0.3
[    1.437409] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.437409] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.437411] ehci-pci: EHCI PCI platform driver
[    1.437411] ehci-pci: EHCI PCI platform driver
[    1.437434] ehci-platform: EHCI generic platform driver
[    1.437434] ehci-platform: EHCI generic platform driver
[    1.437473] ehci-exynos: EHCI EXYNOS driver
[    1.437473] ehci-exynos: EHCI EXYNOS driver
[    1.437508] ehci-msm: Qualcomm On-Chip EHCI Host Controller
[    1.437508] ehci-msm: Qualcomm On-Chip EHCI Host Controller
[    1.437540] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.437540] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.437569] ohci-pci: OHCI PCI platform driver
[    1.437569] ohci-pci: OHCI PCI platform driver
[    1.437594] ohci-platform: OHCI generic platform driver
[    1.437594] ohci-platform: OHCI generic platform driver
[    1.437626] ohci-exynos: OHCI EXYNOS driver
[    1.437626] ohci-exynos: OHCI EXYNOS driver
[    1.437789] usbcore: registered new interface driver usb-storage
[    1.437789] usbcore: registered new interface driver usb-storage
[    1.438413] i2c /dev entries driver
[    1.438413] i2c /dev entries driver
[    1.439377] lirc_dev: IR Remote Control driver registered, major 240
[    1.439377] lirc_dev: IR Remote Control driver registered, major 240
[    1.439379] IR NEC protocol handler initialized
[    1.439379] IR NEC protocol handler initialized
[    1.439381] IR RC5(x/sz) protocol handler initialized
[    1.439381] IR RC5(x/sz) protocol handler initialized
[    1.439382] IR RC6 protocol handler initialized
[    1.439382] IR RC6 protocol handler initialized
[    1.439384] IR JVC protocol handler initialized
[    1.439384] IR JVC protocol handler initialized
[    1.439385] IR Sony protocol handler initialized
[    1.439385] IR Sony protocol handler initialized
[    1.439387] IR SANYO protocol handler initialized
[    1.439387] IR SANYO protocol handler initialized
[    1.439388] IR Sharp protocol handler initialized
[    1.439388] IR Sharp protocol handler initialized
[    1.439390] IR MCE Keyboard/mouse protocol handler initialized
[    1.439390] IR MCE Keyboard/mouse protocol handler initialized
[    1.439391] IR LIRC bridge handler initialized
[    1.439391] IR LIRC bridge handler initialized
[    1.439393] IR XMP protocol handler initialized
[    1.439393] IR XMP protocol handler initialized
[    1.439436] hix5hd2-ir f8001000.ir: no power-reg
[    1.439436] hix5hd2-ir f8001000.ir: no power-reg
[    1.439505] rc rc0: hix5hd2-ir as /devices/virtual/rc/rc0
[    1.439505] rc rc0: hix5hd2-ir as /devices/virtual/rc/rc0
[    1.439853] input: MCE IR Keyboard/Mouse (hix5hd2-ir) as /devices/virtual/input/input1
[    1.439853] input: MCE IR Keyboard/Mouse (hix5hd2-ir) as /devices/virtual/input/input1
[    1.440012] rc rc0: lirc_dev: driver ir-lirc-codec (hix5hd2-ir) registered at minor = 0
[    1.440012] rc rc0: lirc_dev: driver ir-lirc-codec (hix5hd2-ir) registered at minor = 0
[    1.440017] Registered IR keymap rc-empty
[    1.440017] Registered IR keymap rc-empty
[    1.440084] input: hix5hd2-ir as /devices/virtual/rc/rc0/input0
[    1.440084] input: hix5hd2-ir as /devices/virtual/rc/rc0/input0
[    1.440774] sdhci: Secure Digital Host Controller Interface driver
[    1.440774] sdhci: Secure Digital Host Controller Interface driver
[    1.440776] sdhci: Copyright(c) Pierre Ossman
[    1.440776] sdhci: Copyright(c) Pierre Ossman
[    1.440876] Synopsys Designware Multimedia Card Interface Driver
[    1.440876] Synopsys Designware Multimedia Card Interface Driver
[    1.440958] dw_mmc f9830000.mmc: fifo-depth property not found, using value of FIFOTH register as default
[    1.440958] dw_mmc f9830000.mmc: fifo-depth property not found, using value of FIFOTH register as default
[    1.441042] dw_mmc f9830000.mmc: IDMAC supports 32-bit address mode.
[    1.441042] dw_mmc f9830000.mmc: IDMAC supports 32-bit address mode.
[    1.441184] dw_mmc f9830000.mmc: Using internal DMA controller.
[    1.441184] dw_mmc f9830000.mmc: Using internal DMA controller.
[    1.441190] dw_mmc f9830000.mmc: Version ID is 270a
[    1.441190] dw_mmc f9830000.mmc: Version ID is 270a
[    1.441225] dw_mmc f9830000.mmc: DW MMC controller at irq 10,32 bit host data width,64 deep fifo
[    1.441225] dw_mmc f9830000.mmc: DW MMC controller at irq 10,32 bit host data width,64 deep fifo
[    1.457105] mmc_host mmc0: Bus speed (slot 0) = 25000000Hz (slot req 400000Hz, actual 390625HZ div = 32)
[    1.457105] mmc_host mmc0: Bus speed (slot 0) = 25000000Hz (slot req 400000Hz, actual 390625HZ div = 32)
[    1.489350] dw_mmc f9830000.mmc: 1 slots initialized
[    1.489350] dw_mmc f9830000.mmc: 1 slots initialized
[    1.489631] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.489631] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.500971] ledtrig-cpu: registered to indicate activity on CPUs
[    1.500971] ledtrig-cpu: registered to indicate activity on CPUs
[    1.501430] usbcore: registered new interface driver usbhid
[    1.501430] usbcore: registered new interface driver usbhid
[    1.501432] usbhid: USB HID core driver
[    1.501432] usbhid: USB HID core driver
[    1.502363] NET: Registered protocol family 17
[    1.502363] NET: Registered protocol family 17
[    1.502414] 9pnet: Installing 9P2000 support
[    1.502414] 9pnet: Installing 9P2000 support
[    1.502455] Key type dns_resolver registered
[    1.502455] Key type dns_resolver registered
[    1.502864] registered taskstats version 1
[    1.502864] registered taskstats version 1
[    1.504627] hctosys: unable to open rtc device (rtc0)
[    1.504627] hctosys: unable to open rtc device (rtc0)
[    1.504710] ALSA device list:
[    1.504710] ALSA device list:
[    1.504711]   No soundcards found.
[    1.504711]   No soundcards found.
[    1.776256] mmc_host mmc0: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0)
[    1.776256] mmc_host mmc0: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0)
[    1.818749] mmc0: new MMC card at address 0001
[    1.818749] mmc0: new MMC card at address 0001
[    1.819020] mmcblk0: mmc0:0001 8WPD3R 7.28 GiB
[    1.819020] mmcblk0: mmc0:0001 8WPD3R 7.28 GiB
[    1.819119] mmcblk0boot0: mmc0:0001 8WPD3R partition 1 4.00 MiB
[    1.819119] mmcblk0boot0: mmc0:0001 8WPD3R partition 1 4.00 MiB
[    1.819207] mmcblk0boot1: mmc0:0001 8WPD3R partition 2 4.00 MiB
[    1.819207] mmcblk0boot1: mmc0:0001 8WPD3R partition 2 4.00 MiB
[    1.838213]  mmcblk0: p1 p2 p3
[    1.838213]  mmcblk0: p1 p2 p3
[    2.346302] uart-pl011 f8b00000.serial: no DMA platform data
[    2.346302] uart-pl011 f8b00000.serial: no DMA platform data
[    2.584911] random: fast init done
[    2.584911] random: fast init done
[    2.685615] EXT4-fs (mmcblk0p3): recovery complete
[    2.685615] EXT4-fs (mmcblk0p3): recovery complete
[    2.697027] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[    2.697027] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[    2.713313] VFS: Mounted root (ext4 filesystem) on device 179:3.
[    2.713313] VFS: Mounted root (ext4 filesystem) on device 179:3.
[    2.727058] devtmpfs: mounted
[    2.727058] devtmpfs: mounted
[    2.733443] Freeing unused kernel memory: 1088K
[    2.733443] Freeing unused kernel memory: 1088K
[    4.489767] systemd[1]: System time before build time, advancing clock.
[    4.489767] systemd[1]: System time before build time, advancing clock.
[    4.790746] NET: Registered protocol family 10
[    4.790746] NET: Registered protocol family 10
[    4.800194] Segment Routing with IPv6
[    4.800194] Segment Routing with IPv6
[    4.904533] systemd[1]: systemd 232 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD )
[    4.904533] systemd[1]: systemd 232 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD )
[    4.940995] systemd[1]: Detected architecture arm64.
[    4.940995] systemd[1]: Detected architecture arm64.
Welcome to Reference-Platform-Build-X11 2.4+linaro!
[    4.966761] systemd[1]: Set hostname to .
[    4.966761] systemd[1]: Set hostname to .
[    5.816970] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    5.816970] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[    5.845285] systemd[1]: Listening on Journal Socket.
[    5.845285] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[    5.869278] systemd[1]: Listening on Network Service Netlink Socket.
[    5.869278] systemd[1]: Listening on Network Service Netlink Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[    5.897104] systemd[1]: Reached target Swap.
[    5.897104] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[    5.917183] systemd[1]: Listening on udev Control Socket.
[    5.917183] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    5.941213] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    5.941213] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[    5.973167] systemd[1]: Listening on Journal Socket (/dev/log).
[    5.973167] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Listening on Syslog Socket.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Created slice System Slice.
[  OK  ] Reached target Slices.
Starting Load Kernel Modules...
Mounting Huge Pages File System...
Mounting POSIX Message Queue File System...
[  OK  ] Created slice system-getty.slice.
Starting Create list of required st��…ce nodes for the current kernel...
[    6.206103] fuse init (API version 7.26)
[    6.206103] fuse init (API version 7.26)
[  OK  ] Created slice system-serial\x2dgetty.slice.
Mounting Debug File System...
Starting Remount Root and Kernel File Systems...
[    6.263163] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[    6.263163] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
Starting Journal Service...
Mounting Temporary Directory...
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Temporary Directory.
[  OK  ] Started Journal Service.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Create list of required sta��…vice nodes for the current kernel.
[  OK  ] Started Remount Root and Kernel File Systems.
Starting udev Coldplug all Devices...
Starting Create Static Device Nodes in /dev...
Starting Apply Kernel Variables...
Mounting FUSE Control File System...
Mounting Configuration File System...
Starting Flush Journal to Persistent Storage...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Configuration File System.
[    6.618667] systemd-journald[1228]: Received request to flush runtime journal from PID 1
[    6.618667] systemd-journald[1228]: Received request to flush runtime journal from PID 1
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
Mounting /var/volatile...
[  OK  ] Mounted /var/volatile.
[  OK  ] Started udev Coldplug all Devices.
Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems.
Starting Create Volatile Files and Directories...
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown...
Starting Network Time Synchronization...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Found device /dev/ttyAMA0.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started dnf-automatic-download timer.
[  OK  ] Started dnf makecache timer.
[  OK  ] Started dnf-automatic-install timer.
[  OK  ] Listening on RPCbind Server Activation Socket.
Starting sshd.socket.
[  OK  ] Started dnf-automatic-notifyonly timer.
[  OK  ] Reached target Timers.
Starting Docker Socket for the API.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on Docker Socket for the API.
[  OK  ] Listening on sshd.socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Reached target Containers.
[  OK  ] Started Kernel Logging Service.
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
Starting Network Manager...
Starting Network Service...
[  OK  ] Started System Logging Service.
Starting Login Service...
[  OK  ] Started Network Service.
[  OK  ] Started Login Service.
[  OK  ] Started Network Manager.
Starting Network Manager Script Dispatcher Service...
[  OK  ] Reached target Network.
Starting Docker Application Container Engine...
Starting DNS forwarder and DHCP server...
Starting Network Name Resolution...
Starting Permit User Sessions...
Starting Berkeley Internet Name Domain (DNS)...
[  OK  ] Started DNS forwarder and DHCP server.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyAMA0.
[  OK  ] Started Network Name Resolution.
[  OK  ] Started Network Manager Script Dispatcher Service.
Starting Hostname Service...
[  OK  ] Started Hostname Service.
[   14.292387] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   14.292387] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   14.306243] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   14.306243] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Starting Authorization Manager...
[   15.333428] hisi-gmac f9841000.ethernet eth0: Link is Down
[   15.333428] hisi-gmac f9841000.ethernet eth0: Link is Down
[   16.357452] hisi-gmac f9841000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   16.357452] hisi-gmac f9841000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   16.374487] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   16.374487] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Reference-Platform-Build-X11 2.4+linaro poplar ttyAMA0
poplar login: [   25.271050] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   25.271050] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   25.307847] Bridge firewalling registered
[   25.307847] Bridge firewalling registered
[   25.379657] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
[   25.379657] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
[   25.568530] ip_tables: (C) 2000-2006 Netfilter Core Team
[   25.568530] ip_tables: (C) 2000-2006 Netfilter Core Team
[   25.584575] audit: type=1325 audit(1496778812.774:2): table=filter family=2 entries=0
[   25.584575] audit: type=1325 audit(1496778812.774:2): table=filter family=2 entries=0
[   25.600394] audit: type=1300 audit(1496778812.774:2): arch=c00000b7 syscall=273 success=yes exit=0 a0=0 a1=419348 a2=0 a3=0 items=0 ppid=34 pid=2148 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=)
[   25.600394] audit: type=1300 audit(1496778812.774:2): arch=c00000b7 syscall=273 success=yes exit=0 a0=0 a1=419348 a2=0 a3=0 items=0 ppid=34 pid=2148 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=)
[   25.651806] audit: type=1327 audit(1496778812.774:2): proctitle=2F7362696E2F6D6F6470726F6265002D71002D2D0069707461626C655F66696C746572
[   25.651806] audit: type=1327 audit(1496778812.774:2): proctitle=2F7362696E2F6D6F6470726F6265002D71002D2D0069707461626C655F66696C746572
[   25.700488] audit: type=1325 audit(1496778812.890:3): table=nat family=2 entries=0
[   25.700488] audit: type=1325 audit(1496778812.890:3): table=nat family=2 entries=0
[   25.715807] audit: type=1300 audit(1496778812.890:3): arch=c00000b7 syscall=273 success=yes exit=0 a0=1 a1=419348 a2=0 a3=1 items=0 ppid=34 pid=2156 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=)
[   25.715807] audit: type=1300 audit(1496778812.890:3): arch=c00000b7 syscall=273 success=yes exit=0 a0=1 a1=419348 a2=0 a3=1 items=0 ppid=34 pid=2156 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=)
[   25.767263] audit: type=1327 audit(1496778812.890:3): proctitle=2F7362696E2F6D6F6470726F6265002D71002D2D0069707461626C655F6E6174
[   25.767263] audit: type=1327 audit(1496778812.890:3): proctitle=2F7362696E2F6D6F6470726F6265002D71002D2D0069707461626C655F6E6174
[   25.866452] audit: type=1325 audit(1496778813.058:4): table=nat family=2 entries=5
[   25.866452] audit: type=1325 audit(1496778813.058:4): table=nat family=2 entries=5
[   25.881742] audit: type=1300 audit(1496778813.058:4): arch=c00000b7 syscall=208 success=yes exit=0 a0=4 a1=0 a2=40 a3=191d5720 items=0 ppid=2030 pid=2177 auid=4294967295 uid=0 gid=0 euid=0 suid=0 f)
[   25.881742] audit: type=1300 audit(1496778813.058:4): arch=c00000b7 syscall=208 success=yes exit=0 a0=4 a1=0 a2=40 a3=191d5720 items=0 ppid=2030 pid=2177 auid=4294967295 uid=0 gid=0 euid=0 suid=0 f)
[   25.936490] audit: type=1327 audit(1496778813.058:4): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4E00444F434B4552
[   25.936490] audit: type=1327 audit(1496778813.058:4): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4E00444F434B4552
[   25.963313] audit: type=1325 audit(1496778813.058:5): table=filter family=2 entries=4
[   25.963313] audit: type=1325 audit(1496778813.058:5): table=filter family=2 entries=4
[   26.223611] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
[   26.223611] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Reference-Platform-Build-X11 2.4+linaro poplar ttyAMA0
poplar login:
Reference-Platform-Build-X11 2.4+linaro poplar ttyAMA0
poplar login: linaro
[  201.331018] kauditd_printk_skb: 38 callbacks suppressed
[  201.331018] kauditd_printk_skb: 38 callbacks suppressed
[  201.341747] audit: type=1006 audit(1496778988.524:18): pid=2252 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=1 res=1
[  201.341747] audit: type=1006 audit(1496778988.524:18): pid=2252 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=1 res=1
poplar:~$
poplar:~$

Just pushed v2 with Nico's comments fixed.

Just pushed a v3 addressing all the review feedback so far :)

LGTM. @koenkooi any comments?

I'm still not fond of using MACHINE_ESSENTIAL_EXTRA_RDEPENDS for bootloaders, but that can be fixed later.


Update Python to 3.11-slim

Hey, I enjoyed this repo. Very useful! 👏🏾👏🏾👏🏾👏🏾
I built locally a docker image with python 3.11 so easily that I decided to open this pull request.
Thanks!

Looks great! Thanks so much for the contribution!
I originally omitted Python 3.11 because it was unstable when this project started, but now that it's officially released I'm happy to include it in the automatic builds.
To be more on top of core Python version updates going forward, I've also added Python's release update RSS feed to my personal task tracker. :D


create postgresdb v11

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

@ciaranca @timja - Do we need to get this PR merged https://github.com/hmcts/cnp-module-postgres/pull/49 before I merge this PR ?

@ciaranca @timja - Do we need to get this PR merged - hmcts/cnp-module-postgres#49 before I can merge my PR ?

no, they are unrelated

I've got some changes to apply in this tf branch soon for private endpoints is it possible to hold off on this for a couple of days?

I've got some changes to apply in this tf branch soon for private endpoints is it possible to hold off on this for a couple of days?

sure .. after whitelisting postgrest_tf in terraform-infra-approvals strangely I see whitelisting errors in the PR build but this time  around referring use-user-account-for-delegating-access which I don't see inside cnp-module-postgres https://build.platform.hmcts.net/blue/organizations/jenkins/HMCTS_CNP%2Fcnp-plum-recipes-service/detail/PR-245/6/pipeline

@timja @avi-hmcts So I think the best way to progress with this work is to rebase the tf branch with the latest master and then Avinash could continue his work on testing the changes with plum.


lazy require servers

Does not work. eg pairs() doesn't work anymore.

Was it necessary to close the PR? Comes across a little dismissive.
I'm sure I'll be able to work on the PR some more so it does work.

I'm sorry, I meant no offense! Feel free to reopen/recreate if you find something :)
I've just spent 30 mins trying various approaches, but none of them checked all the boxes. I don't want to introduce unstable/confusing behavior for such a minor performance gain.

No worries, just opened #175


State.java:27: design State interface

The puzzle 32-b32bc0c2 from #32 has to be resolved:
https://github.com/eo-cqrs/cmig/blob/8d1946dee42e847762438f4f56608f81f3ab8d2e/src/main/java/io/github/eocqrs/cmig/State.java#L27-L27
The puzzle was created by @rultor on 11-Aug-23.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd thank you for reporting this. I'll assign someone to take care of it soon.

@0pdd thank you for reporting this. I'll assign someone to take care of it soon.

I see you're talking to me, but I can't reply since I'm not a chat bot.

@l3r8yJ this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-08-21T10:29:21.394172.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@l3r8yJ Don't forget to close this ticket before the deadline (2023-08-21T10:29:21). You are past the first half of the allowed period.

The puzzle 32-b32bc0c2 has disappeared from the source code, that's why I closed this issue.

@0pdd 2 puzzles #49, #50 are still not solved.

@l3r8yJ thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.

@0pdd the puzzle #49 is still not solved; solved: #50.


Propagate config attribute

Otherwise it is impossible to specify allowUnfree = true or permittedInsecurePackages.

Could you rebase your branch?


bug: transfer-data-plane - Initiate Transfer Process Fails

Bug Report
Initiate Transfer Process API /management/v2/transferprocesses fails.
Describe the Bug
While initiating transfer, an access token using a private key is generated to initiate the dataflow.
Private key alias (against which private key is stored in Vault) is provided via config edc.transfer.proxy.token.signer.privatekey.alias which is not mandatory and has default value null.
When above config is not provided to connector, it tries to resolve a vault secret with null value and hence it fails.
Code which causes issue: TransferDataPlaneCoreExtension.java
private Supplier<PrivateKey> getPrivateKeySupplier(ServiceExtensionContext context, String privKeyAlias) {
        return () -> privateKeyResolver.resolvePrivateKey(privKeyAlias)
                .orElse(f -> {
                    context.getMonitor().warning(f.getFailureDetail());
                    return null;
                });
    }

Since privKeyAlias was not provided, privateKeyResolver.resolvePrivateKey(privKeyAlias) throws NullPointerException.
Expected Behavior
When privateKeyAlias is not provided, it should use a default private key. Since it is not mandatory.
Observed Behavior
Stack Trace during transfer process
DEBUG 2024-01-30T06:35:53.621882064 TransferProcess: ID b7c8d6b6-1b43-4a32-b748-381e17dfe7ee. Initiate data flow
java.lang.NullPointerException: Cannot invoke "String.length()" because "<parameter1>" is null
        at java.base/java.net.URLEncoder.encode(Unknown Source)
        at org.eclipse.edc.vault.hashicorp.HashicorpVaultClient.getSecretUrl(HashicorpVaultClient.java:186)
        at org.eclipse.edc.vault.hashicorp.HashicorpVaultClient.getSecretValue(HashicorpVaultClient.java:65)
        at org.eclipse.edc.vault.hashicorp.HashicorpVault.resolveSecret(HashicorpVault.java:41)
        at org.eclipse.edc.spi.security.VaultPrivateKeyResolver.resolveInternal(VaultPrivateKeyResolver.java:42)
        at org.eclipse.edc.spi.security.AbstractPrivateKeyResolver.resolvePrivateKey(AbstractPrivateKeyResolver.java:41)
        at org.eclipse.edc.connector.transfer.dataplane.TransferDataPlaneCoreExtension.lambda$getPrivateKeySupplier$3(TransferDataPlaneCoreExtension.java:132)
        at org.eclipse.edc.token.JwtGenerationService.generate(JwtGenerationService.java:45)
        at org.eclipse.edc.connector.transfer.dataplane.proxy.ConsumerPullDataPlaneProxyResolver.lambda$generateAccessToken$4(ConsumerPullDataPlaneProxyResolver.java:89)
        at org.eclipse.edc.spi.result.AbstractResult.compose(AbstractResult.java:169)
        at org.eclipse.edc.connector.transfer.dataplane.proxy.ConsumerPullDataPlaneProxyResolver.generateAccessToken(ConsumerPullDataPlaneProxyResolver.java:86)
        at org.eclipse.edc.connector.transfer.dataplane.proxy.ConsumerPullDataPlaneProxyResolver.lambda$toDataAddress$2(ConsumerPullDataPlaneProxyResolver.java:66)
        at org.eclipse.edc.spi.result.AbstractResult.compose(AbstractResult.java:169)
        at org.eclipse.edc.connector.transfer.dataplane.proxy.ConsumerPullDataPlaneProxyResolver.toDataAddress(ConsumerPullDataPlaneProxyResolver.java:66)
        at org.eclipse.edc.connector.transfer.dataplane.flow.ConsumerPullTransferDataFlowController.lambda$initiateFlow$1(ConsumerPullTransferDataFlowController.java:63)
        at java.base/java.util.Optional.map(Unknown Source)
        at org.eclipse.edc.connector.transfer.dataplane.flow.ConsumerPullTransferDataFlowController.initiateFlow(ConsumerPullTransferDataFlowController.java:63)
        at org.eclipse.edc.connector.transfer.flow.DataFlowManagerImpl.lambda$initiate$0(DataFlowManagerImpl.java:59)
        at java.base/java.util.Optional.map(Unknown Source)
        at org.eclipse.edc.connector.transfer.flow.DataFlowManagerImpl.chooseControllerAndApply(DataFlowManagerImpl.java:86)
        at org.eclipse.edc.connector.transfer.flow.DataFlowManagerImpl.initiate(DataFlowManagerImpl.java:59)
        at org.eclipse.edc.connector.transfer.process.TransferProcessManagerImpl.lambda$processStarting$14(TransferProcessManagerImpl.java:310)
        at org.eclipse.edc.statemachine.retry.StatusResultRetryProcess.process(StatusResultRetryProcess.java:48)
        at org.eclipse.edc.statemachine.retry.RetryProcess.execute(RetryProcess.java:71)
        at org.eclipse.edc.connector.transfer.process.TransferProcessManagerImpl.processStarting(TransferProcessManagerImpl.java:315)
        at org.eclipse.edc.spi.telemetry.Telemetry.lambda$contextPropagationMiddleware$0(Telemetry.java:73)
        at org.eclipse.edc.statemachine.ProcessorImpl.lambda$process$1(ProcessorImpl.java:55)
        at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
        at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(Unknown Source)
        at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
        at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
        at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown Source)
        at java.base/java.util.stream.ReduceOps$5.evaluateSequential(Unknown Source)
        at java.base/java.util.stream.ReduceOps$5.evaluateSequential(Unknown Source)
        at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
        at java.base/java.util.stream.ReferencePipeline.count(Unknown Source)
        at org.eclipse.edc.statemachine.ProcessorImpl.process(ProcessorImpl.java:62)
        at java.base/java.util.stream.ReferencePipeline$5$1.accept(Unknown Source)
        at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(Unknown Source)
        at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
        at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
        at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown Source)
        at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
        at java.base/java.util.stream.LongPipeline.reduce(Unknown Source)
        at java.base/java.util.stream.LongPipeline.sum(Unknown Source)
        at org.eclipse.edc.statemachine.StateMachineManager.performLogic(StateMachineManager.java:110)
        at org.eclipse.edc.statemachine.StateMachineManager.lambda$loop$2(StateMachineManager.java:101)
        at io.micrometer.core.instrument.composite.CompositeTimer.record(CompositeTimer.java:141)
        at io.micrometer.core.instrument.Timer.lambda$wrap$0(Timer.java:193)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)
SEVERE 2024-01-30T06:42:39.013773565 TransferProcess: ID b7c8d6b6-1b43-4a32-b748-381e17dfe7ee. Fatal error while Initiate data flow. Error details: Unable to process transfer b7c8d6b6-1b43-4a32-b748-381e17dfe7ee. Data flow controller throws an exception: Cannot invoke "String.length()" because "<parameter1>" is null
WARNING 2024-01-30T06:42:39.014937674 Unable to process transfer b7c8d6b6-1b43-4a32-b748-381e17dfe7ee. Data flow controller throws an exception: Cannot invoke "String.length()" because "<parameter1>" is null
DEBUG 2024-01-30T06:42:39.052486906 [TransferProcessManagerImpl] TransferProcess b7c8d6b6-1b43-4a32-b748-381e17dfe7ee is now in state TERMINATING
DEBUG 2024-01-30T06:42:39.060849516 TransferProcess: ID b7c8d6b6-1b43-4a32-b748-381e17dfe7ee. Terminate data flow

Steps to Reproduce
Steps to reproduce the behavior:

Initiate a transfer process.
Check Transfer Process State which is TERMINATED
Check connector logs.

Context Information

Used version: EDC v0.5.0
OS: Windows

Detailed Description
Possible Implementation

I think the behavior here should be that, when there's no private key the (consumer pull) transfer should not happen, likely providing a better error message. The problem is here:
https://github.com/eclipse-edc/Connector/blob/98b5e8ac71935545a7cc98c3782b879b2545a0d4/core/common/token-core/src/main/java/org/eclipse/edc/token/JwtGenerationService.java#L45
when the returned privateKey is null, this token generation service should return a failed Result so the error will be propagated up to the data flow controller.
In addition, maybe we could ensure that the ConsumerPullTransferDataFlowController is not registered when the setting is missing.

I agree, previously we generated key pair on the fly if missing if i remember correctly. Since it's not there anymore we should make the config mandatory or not registering ConsumerPullTransferDataFlowController if the key it's not there

Hi @ndr-brt , is there any workaround for this.

Without using config edc.transfer.proxy.token.signer.privatekey.alias
If this config edc.transfer.proxy.token.signer.privatekey.alias needs to be defined, what value should be used against this alias in vault.

Without using config edc.transfer.proxy.token.signer.privatekey.alias

If that config is not set, the connector won't be able to provide "consumer pull" transfers, because for those there's the need to sign the token

If this config edc.transfer.proxy.token.signer.privatekey.alias needs to be defined, what value should be used against this alias in vault.

the alias should be the key with which the private key has been stored in the vault


fix: add data types passed to constructor to instance properties

Fixes #11064

@LeeLenaleee done

@kurkle @LeeLenaleee @etimberg Review please 🙏

Will take a look as soon as I am home again where I have access to my normal PC, should be either tonight or monday evening

Old way:

This MR:

This should still not be the way, because it still sugest a bubble data point, it suggest a floating bar which are all wrong

@LeeLenaleee It is because now you can change chart type on the fly without type errors.
The old way was that myChart.data is ChartData<'line'>, and it limits data mutation to another chart type.
In this PR myChart.data is ChartData<ChartType>, so now you can push new datasets with different types, and you can set new chart type without type errors.
You can't change generics on the fly. For example:
myChart = new Chart('ctx', { type: 'line' }) // Chart<'line'>

In old way here will type error:
myChart.type = 'bar'

And it can't change generic type to Chart<'bar'>. That's how TypeScript works. So we should make data property (and some others too) universal.
Anyway, in real world it not a problem, because to do something with union type you should check it before:
var dpPoint = myChart.data.datasets[0].data[0]

dpPoint.r // type error, cause `r` doesn't exist in `number | [number, number] | ...`

if ('r' in dpPoint) {
  dpPoint.r // no errors, if it is not a BubbleDataPoint then this code just never runs
}

Even if chart type is line dpPoint should have number | Point type

in old way it is number and it also incorrect behavior, because it just gets type from constructor
number | Point it is a union, and again you should check type of the variable first

And I still don't agree with that, if my editor shows me the type could be of type BubblePoint I excpect it to be possible of it being that type. Also I should not need to check if it it available each time in my eyes.
Still I stand by that I rather have the old behaviour as this new one where you can change the type.
So unless @etimberg and @kurkle are fine with this I am against it

@LeeLenaleee What are we able to do with JS, we should be able to do with TypeScript without type errors. In the old way, it is not like that.

@LeeLenaleee What are we able to do with JS, we should be able to do with TypeScript without type errors. In the old way, it is not like that.

You can, just add @ts-ignore. :)
But for real, I disagrer in that js allows using amything anywhere and that is precicely not what typescript is for.

@LeeLenaleee @kurkle Ok, just for clear
const chart4 = new Chart('chart', {
  data: {
    labels: ['1', '2', '3'],
    datasets: [{
      type: 'bar',
      data: [1, 2, 3]
    }]
  }
});

chart4.data.datasets.push({
  type: 'line',
  data: [{ x: 1, y: 2}]
});

Do you think this example should work without type errors?

Would it be too much to ask for new Chart<'line'|'bar'>(...) in that case?

If I have to choose between that example and chart.js infering the correctly used types used at the time of chart initilisation I would choose the correct data types for your data array that are infered from initialization. But I am repeating myself so unless there is a way for both ways to co-exist I am against this and it should get reverted to what it was in my eyes

Perhaps this is an indication that a future chart.js version should require the data-type for each dataset and dispense with the overall chart type.


Book Management System

This is a code in C++ for book management.
@AryanBarsaiyan kindly assign me this issue.

Okk


Can't get colors to work

There's no way i can get colored output from gulp.
Here is the gulp task:
gulp.task('phpunit', function() {
  var options = {colors: 'true'};
  gulp.src('phpunit.xml')
  .pipe(phpunit('phpunit', options))
  .on('error', function(){});
});

When issuing the phpunit command, the output is coloured properly as specified in the phpunit.xml file. Any idea?

Same here. I have run the task with debug, and here's the output:
$ gulp test
[20:53:46] Using gulpfile ~/tmp/yo-test/gulpfile.js
[20:53:46] Starting 'test'...
[20:53:46] Finished 'test' after 5.9 ms
[20:53:46]

       *** Debug Cmd: ./vendor/bin/phpunit --colors --debug -c "/Users/lianoglj/tmp/yo-test/phpunit.xml" ***

PHPUnit 4.7.7 by Sebastian Bergmann and contributors.

Starting test 'TDDKatas\StringCalculatorTest::testFail'.
F

Time: 96 ms, Memory: 4.00Mb

There was 1 failure:

1) TDDKatas\StringCalculatorTest::testFail
Nothing but fails in here.

/Users/lianoglj/tmp/yo-test/tests/StringCalculatorTest.php:12

FAILURES!
Tests: 1, Assertions: 0, Failures: 1.
[20:53:46] { [Error: Command failed: /bin/sh -c ./vendor/bin/phpunit --colors --debug -c "/Users/lianoglj/tmp/yo-test/phpunit.xml"
]
  killed: false,
  code: 1,
  signal: null,
  cmd: '/bin/sh -c ./vendor/bin/phpunit --colors --debug -c "/Users/lianoglj/tmp/yo-test/phpunit.xml"' }
Command failed: /bin/sh -c ./vendor/bin/phpunit --colors --debug -c "/Users/lianoglj/tmp/yo-test/phpunit.xml"

That that is quite thorough ;)
As per my last note, a sample app would be most helpful.

Please see details in #25. Let me know if you need any more.


hide batch add if integrated H feature off

Images

On
Off

Why though? It can be used with mangadex

hmm didnt know that. toggle if delegated source off then?

It would still work for E-Hentai

if both is off then

In the same line of thought the "sync library" option from the overflow menu in the library could be removed when not applicable.

In the same line of thought the "sync library" option from the overflow menu in the library could be removed when not applicable.

yea was thinking to hide that too few days ago (before reading this)

In the same line of thought the "sync library" option from the overflow menu in the library could be removed when not applicable.

yea was thinking to hide that too few days ago (before reading this)

Are you also working on this?


Added capacity(), reserve(), and shrink_to_fit().

Let me know if there are any issues.
Thanks.

Already added to dynamic_bitset


Disabling line numbers when user uses relativenumber

If I use relativenumber, I can't use set nonumber directly to disable line numbers.
I must set line number to normal number and then disable it:
set number
set nonumber

Huh. I've never actually seen relativenumber before. Helpful!
I'll add support next to the regular number. I need to touch that again anyway to properly restore state when toggling vimroom off.

Can you pull the latest master branch and let me know if that fixes the issue for you? Thanks!

Nice work! Thank you.


Contract print form missing fields

2 fields are missing in print form and must be added:

contract_number
nhs_signed_date

1. If contract_request in statuses 'PENDING_NHS_SIGN' - generate printout form.
`set nhs_signed_date=now()::date`
2. If contract_request's status was changed either to  'NHS_SIGNED' or 'SIGNED',
printout form could be taken through Get Contract request details

No idea what to do here, @svetavedmed says it's half a duplicate or something


Add-* vs New-*

I wonder if this is something that was just not thought about (i doubt it :) ), or if there is a specific reason that there are no "New-*" commands.
To me it feels odd to use these as "Add", because many of them are really creating new resources.
e.g. New-VSTeamGitRepository vs Add-VSTeamGitRepository
New-VSTeam vs Add-VSTeam
New-VSTeamProject vs Add-VSTeamProject
It just feels more "the powershell way" by using New-* instead of Add-* for many things.
Add- for me would be something like:
Add-VSTeamGroupMember
Just a thought, thanks for the consideration and keep up the good work 👍

If you review the PowerShell Verb guidelines Add is paired with Remove. Delete is not an approved verb. So after I New something how do I delete it? Given the approved Verbs Add and Remove were selected. https://docs.microsoft.com/en-us/powershell/developer/cmdlet/approved-verbs-for-windows-powershell-commands

You can always add your own alias for the functions if you like.

Thanks for the explanation, and I'll go with the alias.
However I'd also like to submit some statistics from my system:
(Fairly standard, more or less just AzureRM PS installed):
New/Remove pairs: 421
Add/Remove pairs: 152
Or just for AzureRM modules:
New/Remove pairs: 282
Add/Remove pairs: 75
So while technically the guide does state "Add/Remove" pairs, it is used far more for New/Remove pairs, even by Microsoft itself... ;)

Thanks for the data. The guidelines should be updated to reflect your findings.

Maybe in a future release that has a lot of breaking changes I might swap them.

Cool.
Yes, I‘ll open an issue with the ps docs team.