How to install

Hello!
This is exactly what I'm looking for but I have no idea on how to install it :(
I'm currently running hass.io image and already performed the command git clone but I don't know about the next step.
Is it possible to install it as an addon?
Thanks!

I'm afraid this project doesn't really work with current Unifi firmware if I remember correctly (last time I've checked the LED state gets overwritten regularly by the setting configured in the Unifi controller).
This project was done more as proof of concept instead of something reliable for anyone to use, so this has to be installed manually via docker / docker-compose.
Thank you for your interest though.

however, if you wanna try (and have docker and docker-compose installed already) the full installation steps should be:
git clone --recurse-submodules https://github.com/patagonaa/homeassistant-unifi-led.git
cd homeassistant-unifi-led
cp src/HomeAssistantUnifiLed/config.example.json src/HomeAssistantUnifiLed/config.json

then edit src/HomeAssistantUnifiLed/config.json to add your MQTT server and access points (with SSH credentials).
then start the app using
docker-compose up -d --build

and things should be up and running (logs can be checked via docker-compose logs -f)

Issue with current firmware (#2) is fixed now btw

Hi @patagonaa
Thank you very much for your quick reply :)
I will try to install it
Thanks!


How about use in iOS swift project?

Will only work for @objc annotated objects as this uses the objc runtime.


mask_rcnn_x101_32x4d_fpn_gn_ws_2x.py？

RuntimeError: invalid hash value (expected "6adc888e", got "414e04feac04cb88d56b1444e63af0a21fecf7585f407bfe72f5015505b7847c")

Thanks for your report and we will check it.

#629

#629
It  still wrong!

https://github.com/open-mmlab/mmcv/pull/67

open-mmlab/mmcv#67

It is still wrong!

open-mmlab/mmcv#67

It is still wrong!

How do you modify your mmcv? I just successfully run it.

open-mmlab/mmcv#67

It is still wrong!

How do you modify your mmcv? I just successfully run it.

I use faster_rcnn_r50_fpn_gn_ws_1x.py now

open-mmlab/mmcv#67

It is still wrong!

How do you modify your mmcv? I just successfully run it.

I use faster_rcnn_r50_fpn_gn_ws_1x.py now

How do you modified your mmcv? Why do you say it is still wrong? Could you tell me so that I can fix it.

open-mmlab/mmcv#67

It is still wrong!

How do you modify your mmcv? I just successfully run it.

I use faster_rcnn_r50_fpn_gn_ws_1x.py now

How do you modified your mmcv? Why do you say it is still wrong? Could you tell me so that I can fix it.

You mennt I must modify mmcv?

open-mmlab/mmcv#67

It is still wrong!

How do you modify your mmcv? I just successfully run it.

I use faster_rcnn_r50_fpn_gn_ws_1x.py now

How do you modified your mmcv? Why do you say it is still wrong? Could you tell me so that I can fix it.

You meant I must modify mmcv? How and where?

I use faster_rcnn_r50_fpn_gn_ws_1x.py now

Also ,you only modify resnetx101,no  resnet 50.

You can follow the modification in https://github.com/open-mmlab/mmcv/pull/67.
Just replace 6adc888e to 34ac1a9e at this line.
https://github.com/open-mmlab/mmcv/blob/c728193f8d1dc62537c54b29748d9ba595184d40/mmcv/runner/checkpoint.py#L25

#629
It  still wrong!

You just mentioned resnetx101 error earlier. Now I have fix them. Please have a check https://github.com/open-mmlab/mmcv/pull/67


Workbox documentation: bgsync - Let users know how the sync process works

Right now on this page: https://developers.google.com/web/tools/workbox/modules/workbox-background-sync it explains how to use the background sync helper from Workbox, but it tells the user to press the "Sync" button on the Chrome Dev Tools in order to force a sync and test if background sync is working.
This works but it's very confusing as the developer never really knows when the sync automatically happens if you don't press the button. I assumed the browser synced as soon as the user regained connection, but it turns out (after exhaustive searching and finding this issue: https://github.com/GoogleChrome/workbox/issues/1249 and this blog post: https://golb.hplar.ch/2018/06/background-sync.html) that the browser first tries to sync after 5 minutes, then it does a second try after 15 minutes, and a third try (when ???) until it fails. It would be very helpful to have this information explained on the workbox documentation.

Hey @andrralv
The behavior you're describing is called exponential backoff
While it's not mentioned in the documentation page you linked to, it is mentioned in Jake's post about background-sync.
 It's in a different repo and here's the file you need to edit: workbox-background-sync

It's never really explained because I think it's assumed that people know it.. I couldn't find a place that explains it on the internet other than this wikipedia page
I think it would be enough to at least mention that the delay is an exponential backoff, and if you feel like adding more info that would be cool
I personally know exponential backoff from telegram and other apps that try to reconnect when I lose internet connectivity

I've added info about this to the Workbox v4 docs in https://github.com/google/WebFundamentals/commit/2e6915b571bd8390cc3c59b148036a77b502887e
Thanks for bringing it to our attention!


Catch and sanitize errors thrown in TW SCA request

Related to https://github.com/opencollective/opencollective-api/pull/4211#discussion_r457941590

@Betree I refactored fundTransfer to use requestDataAndThrowParsedError. It was my original intent, I just forgot to remove the development version from fundTransfer at the time.


Updated python format

Append close marker to the end of last line instead of creating
new empty line.

Thank you very much for this :)


Error when returns a big array

Report
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: InvalidProtocolBufferException: While parsing a protocol message, the input ended unexpectedly
in the middle of a field. This could either mean that the input
has been truncated or that an embedded message misreported its
own length.

Note that the buffer containing the message has 67544120 bytes, but
CodedBufferReader was allowed to parse only 67108864 bytes.

#0      CodedBufferReader._throwTruncatedMessageError (package:protobuf/src/protobuf/coded_buffer_reader.dart:34:7)
#1      CodedBufferReader._withLimit (package:protobuf/src/protobuf/coded_buffer_reader.dart:57:7)
#2      _readPackableToList (package:protobuf/src/protobuf/coded_buffer.dart:241:11)
#3      _readPackable (package:protobuf/src/protobuf/coded_buffer.dart:205:3)
#4      _mergeFromCodedBufferReader (package:protobuf/src/protobuf/coded_buffer.dart:140:9)
#5      GeneratedMessage.mergeFromBuffer (package:protobuf/src/protobuf/generated_message.dart:192:5)
#6      new ReadResponse.fromBuffer (package:xxx/messages/xxx.pb.dart:89:130)
#7      _HomeSimpleState.build.<anonymous closure> (package:xxx/main.dart:235:64)
<asynchronous suspension>

This error is caused when the function returns a big array, and it's OK if the array size is small.
Is there any way to change the limit of CodedBufferReader?
System Information
rustc --version
rustc 1.72.0 (5680fa18f 2023-08-23)

protoc --version
libprotoc 24.2

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.13.3, on Microsoft Windows [version 10.0.22621.2283])
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.7.3)
[√] Android Studio (version 2022.3)
[√] VS Code (version 1.82.1)
[√] Connected device (3 available)

I found a post sayes CodedBufferReader constructor takes an optional sizeLimit argument.
Could I do this via rust-in-flutter config?
Thank you.

Will inspect this soon, thanks for the report :)

May I ask you if you're using one of the fields of the protobuf message as binary, with a large size?

@temeddix
My proto like:
message ReadResponse {
  repeated float output_numbers = 1;
  string output_string = 2;
}

output_numbers  is an array of f32 type of rust, and it can be very big.
When the length of output_numbers is 16886016, it will cause the error I posted.
After I made a small slice :
output_numbers = rrr[0..16000000].to_vec()

It works.
This slice didn't work:
output_numbers = rrr[0..16880000].to_vec()

I decided to modify my logic and use a simple array to solve this issue.

I think version 4.0.0 can help you with this issue:
https://github.com/cunarist/rust-in-flutter/pull/149
https://github.com/cunarist/rust-in-flutter/discussions/151


Projects show up as 'Paused' after Docker restart or system reboot

Describe the bug
A clear and concise description of what the bug is.
This has happened a handful of times; it is by no means a "consistent" issue, nor at all reproducible. I'm not sure if it is a DDEV issue or a Docker issue. But on several occasions, I will be working along, and all of a sudden I start getting errors. It may be a 504 Gateway error as I try to ddev launch, or it may be a mass of red error message following a DDEV command; the common factor seems to be, I will do a ddev list, and it shows on the project in question, in yellow letters, paused and db: running
Again, I'm not sure if this is DDEV or Docker, I'm not sure what causes it. Sometimes I can simply ddev start the project again, and all is well. Sometimes I have to ddev poweroff and then ddev start.

Usually "paused" means that the host computer has been rebooted, or docker has been restarted. You can also explicitly do ddev pause.
Essentially, ddev's docker containers don't automatically restart, although you can tell them to restart with the experimental (v1.16+) ddev config global --auto-restart-containers but your mileage may vary with that. It's not the default for a reason.

Yeah, these are things I'd thought of, but none apply. Hasn't rebooted, docker hasn't (that I'm aware) restarted, I haven't paused anything.  I do a DDEV LIST and see it is paused. From what you're saying, I'm guessing this is a docker issue.

It could be that a container has died. If it's one specific container that is making it do this, you can examine that container.
When you get an error of some kind, stop and do a ddev list. Figure out which project it is. Then look at the containers, docker ps -a | grep <project> You'll find one or more of those stopped. You can docker logs <containername> to get some insight into why it might have stopped. It could be an error.
As with all situations of this type, please check your docker file space (if on macOS or Windows Hyper-V backend) and check your memory allocated to docker.

No, that's the thing, it isn't one container over and over, it may be this one this time, and then that one another time, and then this one over here a different time. Like I say, nothing reproducible about it.

I'll do a ddev logs -s <service> next time it happens, and share the outcome with you.

Thanks - Please share as a gist (gist.github.com), rather than pasting directly here.  You should also do a docker ps -a

Will do. Thank you.

Closing this for now. Looking forward to figuring out what is happening in your specific case. Feel free to follow up here or anywhere else.


IGV WEB - Dropdown menu is not visible

Hi team.
I have installed this application on my ubuntu 18.04 laptop machine and building was successful.
But when I try navigate 'Genomes', the end of dropdown menu is not visible on my web browser as shown below.
I'm using firefox as my browser and screen resolution is 1360 x 768 (16:9).
Does IGV webapp require certain resolution or minimum size of screen? (My screen size is 15.6 inches)
Thanks

I see the entire dropdown, what do you mean "the end is not shown"?
On Tue, Oct 20, 2020 at 1:25 AM Thomas Sunghoon Heo <
<EMAIL_ADDRESS>wrote:

Hi team.
I have installed this application on my ubuntu 18.04 laptop machine and
building was successful.
But when I try navigate 'Genomes', the end of dropdown menu is not visible
on my web browser as shown below.
I'm using firefox as my browser and screen resolution is 1360 x 768 (16:9).
Does IGV webapp require certain resolution or minimum size of screen? (My
screen size is 15.6 inches)
Thanks
[image: igv_genome_scrolls]
https://user-images.githubusercontent.com/12674567/96560345-26ad9980-12f9-11eb-9d62-474f4f38852e.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/igvteam/igv-webapp/issues/179, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHD2HEG26NEYZRRCUVSEULSLVCOTANCNFSM4SX2YZKA
.

There should be a scrollbar on the web browser itself,  but I don't see it (on the right).   I'll see if we can reproduce this here.

Yes we can reproduce this.    We will work on a solution.   In the meantime you can get around this by editing "genomes.json" in the "dist/resources" directory.     Remove any genome entries that are not of interest.   Judging from your screen removing 4 or 5 should be enough.

@jrobinso
Thanks for you fast reply.
I have changed genomes.json file in dist/resources directory and restart http-server, but the 'Genomes' drop down menu did not change.
I have re-cloned this repository and changed contents of resorces/genomes.json file in cloned directory and then built this application and no changed applied.
To test if my machine has problem, I have moved onto new windows laptop with WSL2.
Again, I have cloned this repo, changed contents of resources/genomes.json under cloned repo and then build the app.
The change not but if I change the resources/genomes.json under dist directory, nothing happens.
I have tried to launch application both dist or cloned igv-webapp directory with command as in README file.
Is there any solution about this or am I doing something wrong?
Thanks in advance.

If you rebuild the app then genomes.json will get copied from /resources to /dist/resources,  so to be safe change in in both locations.   Also clear you browser cache.    If you use developer tools look for the "genomes.json" request in the network tab and verify it is getting it from where you are expecting it, and look at the response.   Everything is configurable here,  but it should be getting it from the location I specified.

Ahh, hold on, there might be a problem here in the latest code.   It seems to be getting it from amazon irrespective of local settings.    I'm looking at it now.

Actually, false alarm, it works as expected.  I see 2 loads of genomes.json, 1 from igv-webapp and one from igv.js.   The igv.js load is for internal use and does not affect the menu.   After removing all genomes except "hg38" from genomes.json this is what I see.

Depending on how and from where you start your webserver,  it might pickup dist/resources/genomes.json or resources/genomes.json,  to be safe edit both.   Otherwise you'll need to look in the network tab to see what's going on.  You will see 2 loads of a file called "genomes.json",  1 from an amazon host and 1 from you local system.  Ignore the amazon load, it is not relevant,  you can verify the path to the local one and also the response.

Hi @jrobinso
Thanks for reply!
I tried to change both location file but now worked but after clearing cache worked.
I think we can close this thread.
Thanks!

Ahh, good. I should have mentioned clearing the cache, for some reason browsers often don't detect changes to .js and .json files.


Use non-minified CSS when running docs locally

For easier debugging. Just like we already do for the JS.
CC: @XhmikosR

I guess it makes sense, yeah. :shipit:


Display arrow for multiple select

the main changes were made in src/scss/selectize.scss
other came from npm run build
on line 333 .#{$selectize}-control.single .#{$selectize}-input { and .single did not allow to apply styles for multiple select
wrapped to apply styles for arrow for all selects

old

new

It was never previously displayed for multi select?

hub


Fix the Header

I wish to fix the Header Column.
Please assign this issue to me under gssoc extnd and Hacktoberfest.

The issue is already fixed by someone else


Update packages with security issues

Maintenance. Updates some packages to clear out security issues.
Remove some codeowners

Thanks @harrismd! I'll have one more tomorrow to publish the new version.


user lacks privilege or object not found: FORTUNES

Followed "Deploying to Pivotal Web Services (or other Cloud Foundry environments)"
2016-03-07T06:18:54.000+00:00 [APP] OUT ...]
2016-03-07T06:18:54.000+00:00 [APP] OUT 2016-03-07 06:18:54.275 INFO 16 --- [ main] org.hibernate.Version : HHH000412: Hibernate Core {4.3.11.Final}
2016-03-07T06:18:55.000+00:00 [APP] OUT 2016-03-07 06:18:55.663 INFO 16 --- [ main] o.h.h.i.ast.ASTQueryTranslatorFactory : HHH000397: Using ASTQueryTranslatorFactory
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.112 INFO 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : HHH000227: Running hbm2ddl schema export
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.117 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : user lacks privilege or object not found: HIBERNATE_SEQUENCE in statement [drop sequence hibernate_sequence]
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.119 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : HHH000388: Unsuccessful: insert into fortunes (id, text) values (1001, 'You learn from your mistakes... You will learn a lot today.')
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.120 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : user lacks privilege or object not found: FORTUNES
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.121 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : user lacks privilege or object not found: FORTUNES
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.121 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : HHH000388: Unsuccessful: insert into fortunes (id, text) values (1008, 'The man or woman you desire feels the same about you.')
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.122 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : HHH000388: Unsuccessful: insert into fortunes (id, text) values (1013, 'You will become great if you believe in yourself.')
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.122 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : user lacks privilege or object not found: FORTUNES
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.125 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : HHH000388: Unsuccessful: insert into fortunes (id, text) values (1023, 'Love can last a lifetime, if you want it to.')
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.125 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : user lacks privilege or object not found: FORTUNES
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.128 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : HHH000388: Unsuccessful: insert into fortunes (id, text) values (1035, 'You will travel to many exotic places in your lifetime.')
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.128 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : user lacks privilege or object not found: FORTUNES
2016-03-07T06:18:56.000+00:00 [APP] OUT 2016-03-07 06:18:56.129 ERROR 16 --- [ main] org.hibernate.tool.hbm2ddl.SchemaExport : HHH000388: Unsuccessful: insert into fortunes (id, text) values (1040, 'LIFE CONSIST NOT IN HOLDING GOOD CARDS, BUT IN PLAYING THOSE YOU HOLD WELL.')

@renzrollon What relational database service are you binding to the "fortune server" app? Is it the Pivotal MySQL service on Pivotal Cloud Foundry, or something different? If it is Pivotal MySQL, what version of that product are you using?

Sorry for the issue. Fixed it already, I forgot to uncomment #cf cs elephantsql turtle fortunes-db in create_services.sh


Improve clarity of line and branch coverage format.

Put percentage first and then covered and total counts in brackets afterwards. Percentage is most critical at a quick glance.

Put line and brnach coverage on separate lines.

Before
Coverage report generated for (1/10), (10/10), (2/10), (3/10), (4/10), (5/10), (6/10), (7/10), (8/10), (9/10) to /Users/me/Development/cntral/coverage. 8534 / 16083 LOC (53.06%) covered. 2225 / 4749 branches (46.85%) covered.

After
Now it shows in a clean format, including covered branches, total branches and percent of covered branches. Something like this:
Coverage report generated for (1/10), (10/10), (2/10), (3/10), (4/10), (5/10), (6/10), (7/10), (8/10), (9/10) to /Users/me/Development/cntral/coverage.
Line Coverage: 53.06% (8534 / 16083)
Branch Coverage: 46.85% (2225 / 4749)

When branch coverage is not enabled it simply omits that line, so it appears like this:
Coverage report generated for (1/10), (10/10), (2/10), (3/10), (4/10), (5/10), (6/10), (7/10), (8/10), (9/10) to /Users/me/Development/cntral/coverage.
Line Coverage: 53.06% (8534 / 16083)

I like this new format indeed. So let me merge this.

For info, GitLab CI uses a regexp to extract the coverage percentage from simplecov output, and the above change breaks the previous regexp (as here) but once one knows that, it is fairly easy to fix.
No complaint about the change, just in case others are bitten by this :smile:

@noproblemwiththat Thanks for posting this and I appreciate you saying no complaint. :) I figured it would break something but I think it's worth it for the sake of clarity. Cheers.


Implemenent Lightup IOperationWrapper

Hello,
We'd need IOperationWrapper to be a real wrapper for IOperation interface.
https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/StyleCop.Analyzers/StyleCop.Analyzers/Lightup/IOperationWrapper.cs
Would you accept PR with this change?
It would:

Remove current IOperationWrapper interface
Generate IOperationWrapper struct with code generator
Update existing code generation to avoid duplicated implementations of Type and WrappedOperation members.
Update existing code generation to respect Base attribute from OperationInterfaces.xml

@pavel-mikula-sonarsource is this still valid after https://github.com/DotNetAnalyzers/StyleCopAnalyzers/commit/9b5db190f53bc6e8689b4df433684d92868fb6b0 ?

Doesn't seem so


Gone... What happened to it?

what is it supposed to do? standard vim?

Similar to control d but goes up.

I have it mapped to html unescape. I'm going to change that to ,he and ,hu and remove this mapping in a second


signal: add uv_signal_start_one_shot method

It behaves as uv_signal_start but it resets the signal handler as soon
as the signal is received.
Refs: https://github.com/libuv/libuv/issues/1104

It's still a WIP (tests, documentation, ...)  but wanted to know if something like this is what you had in mind @bnoordhuis ?

Finished unix implementation and tests added.
Windows implementation and docs still missing

I skimmed through the libuv and node issues but I can't figure out why this would need to be in libuv itself. Why can't the application call uv_signal_stop in the callback instead?

@saghul I think the reason is that we need a way to disarm the signal handler from the signal handler itself. Disarming it from the callback would not work in cases as the one described here: https://github.com/libuv/libuv/issues/1104#issuecomment-257269377 because the main thread doesn't get notified until the loop moves forward (until we exit the while loop in the example linked above)

@santigimeno Note that I meant doing it in C++, not in the JavaScript side of things.  I wasn't clear enough, sorry!

@saghul yes, I was referring to the C++ side too. From what I understand, if the main thread is in a tight loop, we don't get notified of the signal in the callback (for this we need that the loop advances), so any other subsequent signal that arrives will also be handled in the signal handler and that's what we try to avoid.

What I was thinking is to stop the handle in C++ before dispatching the callback to the JS side. Wouldn't that work?

I had a quick IRC chat with @santigimeno.  I get it now.  :+1: on the approach.  Will bikeshed on names later :-)

Speaking of name bikeshedding... any reason to use "one shot" over "once"?

One shot, one opportunity?

I think the sugested name comes from how SA_RESETHAND was previously called SA_ONESHOT http://man7.org/linux/man-pages/man2/rt_sigaction.2.html

One-shot is the traditional name for it, yes.

Added windows implementation though I'm not too sure about its correctness.  Let's see what the CI says: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/204/

PR updated incorporating the suggested changes and fixes in the uv__signal_first_handle logic.

Could someone review the Windows part too? Thanks!
/cc @saghul @bzoz @piscisaureus

Minor bikeshed (I had to) I prefer uv_signal_start_oneshot

I can do that and also add the corresponding documentation.

Added documentation and renamed to uv_signal_start_oneshot

Addressed all comments. Thanks!

I'll try to merge this tomorrow if nobody objects

Landed in https://github.com/libuv/libuv/commit/45616f542da523b3d87a8d379bb116ffc3a97845. Thanks everyone for the reviews.


Initialize textMaskInputElement on demand

This resolves issue #334

@PerfectPixel with this change, is it still possible to initialize the component with a value that it should mask? Say I want to initialize the component with<PHONE_NUMBER> and want to see<PHONE_NUMBER> in the input field. Will that work?

This changes only the time of initialization, not the behaviour. So if you pass in a value, the mask will initialize and mask the value. However, the one odd edge-case where a value is passed in but the input field does not exist yet remains.

Thanks @PerfectPixel!

These changes have been published as<EMAIL_ADDRESS>


Added enum for the EventNames in PlaidLink plus support the 'account' data in the PlaidLinkResponse

I was doing some debugging and created an enum for the Plaid Link event names, figured I'd contribute it back.
I also added the 'account' support in PlaidLinkResponse

I'm good with it as is, if you need it. I'd like to come back and add PlaidLinkExitResponse and PlaidLinkEventResponse to handle the metadata there specifically, as well as more associated enums.

I've got OnExitMetadata, OnSuccessMetadata and OnEventMetadata in the https://github.com/viceroypenguin/Going.Plaid.NET/tree/PlaidLink-Metadata branch.


Checkbox component

Create the vscode-checkbox component.
https://github.com/microsoft/vscode-webview-ui-toolkit/blob/main/src/checkbox/README.md

Hi I take this one but can't assign myself apparently

Thanks, @akurtaliqi, I've assigned you. 🙏

Thank you @estruyf :)

Hi @estruyf
I'm facing one issue compouding CSS styles, for example stacking
the enable style on the checkbox here  :

It does not seem to work :/ do you have any idea why ?
(I've tried different ways....)

Issue resolved :)

BTW Am I already supposed to handle all styles & possibilites ?

Initially we look for feature parity with the one from the UI toolkit.


Update tvmc_command_line_driver.py, modify the sentence, remove the duplicate "as"

modify the sentence, remove the duplicate "as"

Hi @lhutton1, I am so glad to contribute to the project. I am now learning about this project, and how to use it in my project. Is there any place to discuss questions?

Hi @PatricYan, thanks for the contribution. Yes, the best place to ask questions would be in the discuss forum: https://discuss.tvm.apache.org/


Update DG, UG

Codecov Report

Merging #299 (2bd0f3d) into master (40fb583) will decrease coverage by 0.11%.
The diff coverage is 40.00%.

@@             Coverage Diff              @@
##             master     #299      +/-   ##
============================================
- Coverage     84.37%   84.25%   -0.12%
- Complexity     1629     1668      +39
============================================
  Files           142      143       +1
  Lines          4256     4376     +120
  Branches        536      553      +17
============================================
+ Hits           3591     3687      +96
- Misses          548      566      +18
- Partials        117      123       +6

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/chopchop/model/Model.java
100.00% <ø> (ø)
1.00 <0.00> (ø)

src/main/java/chopchop/model/ModelManager.java
68.88% <0.00%> (-2.81%)
48.00 <0.00> (+12.00)
:arrow_down:

src/main/java/chopchop/ui/StatsBox.java
61.11% <ø> (ø)
4.00 <0.00> (ø)

...hop/logic/commands/StatsIngredientUsedCommand.java
94.44% <100.00%> (ø)
7.00 <0.00> (ø)

...hopchop/logic/commands/StatsRecipeMadeCommand.java
87.50% <100.00%> (ø)
16.00 <0.00> (ø)

src/main/java/chopchop/model/UsageList.java
84.26% <100.00%> (ø)
29.00 <0.00> (ø)

src/main/java/chopchop/model/EntryBook.java
90.90% <0.00%> (-1.10%)
17.00% <0.00%> (+5.00%)
:arrow_down:

.../main/java/chopchop/model/util/SampleDataUtil.java
100.00% <0.00%> (ø)
12.00% <0.00%> (+5.00%)

...ava/chopchop/logic/commands/MakeRecipeCommand.java
100.00% <0.00%> (ø)
17.00% <0.00%> (+3.00%)

...pchop/commons/util/BulkEditableObservableList.java
65.38% <0.00%> (ø)
8.00% <0.00%> (?%)

... and 3 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 40fb583...2bd0f3d. Read the comment docs.

Will need to update use cases and other parts but should be ok to merge first so there are less conflicts


Error when attempting to do logs on TTY service

Before this PR, attempting to do logs on service with TTY was undefined behavior and caused ~*~*~weird errors~*~*~. This doesn't fix that, but disallows the undefined behavior until we do.

Mirror of change docker/docker#31674

I think you should catch this at a higher level (REST API, gRPC, or CLI)

The corresponding change in Docker does (it's caught at the daemon level). This catch, lower in the stack, is to avoid the undefined behavior that results. Those are the two best places to catch this error. The only place I could also catch this that would make sense would maybe be in the GRPC call for logs.

LGTM


Use snake_case for namespace names

This PR refactors namespace names to use snake_case. This allows us to use the following without any name collisions.
using namespace mata;
using namespace mata::nfa;
Nfa this_is_nfa_class; // <-- compiler will know that it is a class, not namespace name.
Nfa nfa; // <-- compiler will know it is a variable name, so that
nfa::concatenate(nfa, this_is_nfa_class); // <-- compiler can distinguish between nfa::... and concatenate(nfa, ...).

There will be no longer a need to reference Nfa class as Nfa::Nfa, we can simply use Nfa.
I advise the reviewers to review the code commit by commit so that each type of change is easily recognizable. f399c1e07ade20857ebcecefbbdd545716e762d4 only refactors all namespace names to snake_case.
We agreed on these changes, but I ask the assigned reviewers to primarily express in their review whether they agree with the snake_case naming convention for namespace names or not. The review of the changes themselves is optional.

I am fine with that. So the current name convention is

snake case: namespaces, methods, functions
camel case: types

?

Basically, yeah. UpperCamelCase (== PascalCase) is what we use for types, type aliases, classes (and structs), enum classes.

(This force-push only resolves merge conflicts.)


How restart the Tombstone node？

Question

How restart the Tombstone tikv node？
Before asking a question, make sure you have:

Searched existing Stack Overflow questions.
yes
Googled your question.
yes
Searched open and closed GitHub issues
yes
Read the documentation:

TiKV Readme
TiKV Doc
TiKV-Ctl Doc
TiDB & TiKV Stack Doc

reference 👍 https://github.com/pingcap/tidb/issues/5344


Please elaborate on how you plan to run unsigned code without patching signature checks, I'm really interested in seeing this miracle in action.
(PS: devmode is unrelated to firmlaunching)

devmode is not needed,any other CFW who patch sig check can be used to update sysNAND

And rxtools supports the widest version range.


The values configured when the resource is created will not take effect if the default value is also configured

Describe the bug

The values configured when the resource is created will not take effect if the default value is also configured
Steps to reproduce

Add a resource definition and set some default values in the rule template.

Create a resource that matches the rule set above, and modify a field with default value.

Check the deployment configuration.

Result

The values configured when the resource was created did not take effect.

Expected behavior

User-configured values have a higher priority than the default.

Environment

Walrus version: main 9e14c25ece772fbb582b0be93a0fdb5e486fd53e
UI version: dev-e15ef2e

Additional context
Add any other context about the problem here.

Environment

Walrus version: v0.4.0-rc1  a3e5c0343d3e831ca30e4fd76a160212bc5bba7f
UI version: dev-6b82ce8

Issue 2: If configure default value in match rule template and UI schema as well, the default value in UI schema doesn't work too.

Parameter priority：User Input > UI Schema > Template

Environment

Walrus version: 4465aa8deb63ff1ceb270b6cbc1c5ae2852d8242
UI version: dev-7b0f2a2

Test Result: pass


another tutorials update aug 21 afternoon

Hi Saraneh, I merged your other request but this one remains because of an unresolved conflict. Are you able to take a look?

Hi Amber, this push is outdated so dont worry about it. I closed it. Thank you!


bigchainDB vagrant tutorial failed provisioning

BigchainDB version: 1.4.0 dev
Operating System: ubuntu/xenial64 (virtualbox, 20180122.0.0)
Deployment Type: vagrant

Description
I have tried this official bigchainDB tutorial, running with vagrant
https://docs.bigchaindb.com/projects/server/en/v1.3.0/appendices/run-with-vagrant.html
What I Did
Every time I hit the command vagrant up, it came out with this error below :
==> config-node: Running provisioner: hosts...
==> bdb-node-01: Updating hosts on: bdb-node-01
==> config-node: Configuring cache buckets...
==> config-node: Running provisioner: shell...
    config-node: Running: inline script
    config-node: Operation Sytem: ubuntu
    config-node: Version: 16.04
    config-node: Dependencies already installed:[ ansible ]
==> config-node: Configuring cache buckets...
==> config-node: Running provisioner: shell...
    config-node: Running: inline script
    config-node:
    config-node: PLAY [all] *********************************************************************
    config-node:
    config-node: TASK [Gathering Facts] *********************************************************
    config-node: fatal: [bdb-node-01]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Permission denied (publickey).\r\n", "unreachable": true}
    config-node:    to retry, use: --limit @/bigchaindb/configuration/bdb-deploy.retry
    config-node:
    config-node: PLAY RECAP *********************************************************************
    config-node: bdb-node-01                : ok=0    changed=0    unreachable=1    failed=0
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Thanks for posting your config file, and I have found the problem, so the issue was with ubuntu/xenial64, conventionally all the vagrant images have username/password set to vagrant/vagrant but that got changed, you can see the discussion here: https://bugs.launchpad.net/cloud-images/+bug/1569237
To cater for this scenario, in our Vagrant file we were handling the ubuntu user for the ubuntu/xenial64 image. We also mentioned in our file L30, L31.
But, this has been fixed in the latest ubuntu/xenial64 images >= v20180112.0.0`.
I will push a fix for this. Thanks for filing this issue. Good catch.

Thank you for the update.
I just tested and came out with no error.
vagrant@bdb-node-01:~$ ps -ef | grep bigchaindb
root     20972     1  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     20976 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     20986 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     20987 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     20988 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     20989 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     20991 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     20994 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     20995 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21025 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21026 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21027 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21028 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21030 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21033 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21035 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21040 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21041 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21042 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21043 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21044 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21050 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21054 20972  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21060 21050  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21066 21050  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21068 21050  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21069 21050  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start
root     21070 21050  0 06:09 ?        00:00:00 /usr/bin/python3 /usr/local/bin/bigchaindb start


espeak-ng-data make build  fails

LocalAI version:
Docker v1.23.0-cublas-cuda11
Environment, CPU architecture, OS, and Version:
Linux hostname 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64 GNU/Linux
NVIDIA-SMI 470.182.03   Driver Version: 470.182.03   CUDA Version: 11.4
Describe the bug
Unable to build the docker image ( even older version tried until 1.18 )
Here are last few lines of the issue:

cd build && cp -rf CMakeFiles/llama.dir/llama.cpp.o ../llama.cpp/llama.o
cd build && cp -rf examples/CMakeFiles/common.dir/common.cpp.o ../llama.cpp/common.o
cd build && cp -rf examples/CMakeFiles/common.dir/grammar-parser.cpp.o ../llama.cpp/grammar-parser.o
g++ -I./llama.cpp -I. -I./llama.cpp/examples -I./examples -O3 -DNDEBUG -std=c++11 -fPIC -Wall -Wextra -Wpedantic -Wcast-qual -Wno-unused-function -pthread -I./llama.cpp -I./llama.cpp/examples binding.cpp -o binding.o -c
binding.cpp: In function 'int llama_predict(void*, void*, char*, bool)':
binding.cpp:533:42: warning: cast from type 'const char*' to type 'char*' casts away qualifiers [-Wcast-qual]
  533 |             if (!tokenCallback(state_pr, (char*)token_str)) {
      |                                          ^~~~~~~~~~~~~~~~
binding.cpp:591:1: warning: label 'end' defined but not used [-Wunused-label]
  591 | end:
      | ^~~
binding.cpp: In function 'void llama_binding_free_model(void*)':
binding.cpp:613:5: warning: possible problem detected in invocation of 'operator delete' [-Wdelete-incomplete]
  613 |     delete ctx->model;
      |     ^~~~~~~~~~~~~~~~~
binding.cpp:613:17: warning: invalid use of incomplete type 'struct llama_model'
  613 |     delete ctx->model;
      |            ~~~~~^~~~~
In file included from ./llama.cpp/examples/common.h:5,
                 from binding.cpp:1:
./llama.cpp/llama.h:66:12: note: forward declaration of 'struct llama_model'
   66 |     struct llama_model;
      |            ^~~~~~~~~~~
binding.cpp:613:5: note: neither the destructor nor the class-specific 'operator delete' will be called, even if they are declared when the class is defined
  613 |     delete ctx->model;
      |     ^~~~~~~~~~~~~~~~~
cd build && cp -rf CMakeFiles/ggml.dir/k_quants.c.o ../llama.cpp/k_quants.o
ar src libbinding.a llama.cpp/ggml.o llama.cpp/k_quants.o  llama.cpp/common.o llama.cpp/grammar-parser.o llama.cpp/llama.o binding.o
make[1]: Leaving directory '/build/go-llama'
CGO_LDFLAGS="" C_INCLUDE_PATH=/build/go-llama LIBRARY_PATH=/build/go-llama \
go build -ldflags "-X "github.com/go-skynet/LocalAI/internal.Version=v1.23.0-15-gd603a9c" -X "github.com/go-skynet/LocalAI/internal.Commit=d603a9cbb5910eb69cd0bb7458ab40dcbdcf88cd"" -tags "stablediffusion tts" -o backend-assets/grpc/llama ./cmd/grpc/llama/
# github.com/go-skynet/go-llama.cpp
binding.cpp: In function 'void llama_binding_free_model(void*)':
binding.cpp:613:5: warning: possible problem detected in invocation of 'operator delete' [-Wdelete-incomplete]
  613 |     delete ctx->model;
      |     ^~~~~~~~~~~~~~~~~
binding.cpp:613:17: warning: invalid use of incomplete type 'struct llama_model'
  613 |     delete ctx->model;
      |            ~~~~~^~~~~
In file included from go-llama/llama.cpp/examples/common.h:5,
                 from binding.cpp:1:
go-llama/llama.cpp/llama.h:66:12: note: forward declaration of 'struct llama_model'
   66 |     struct llama_model;
      |            ^~~~~~~~~~~
binding.cpp:613:5: note: neither the destructor nor the class-specific 'operator delete' will be called, even if they are declared when the class is defined
  613 |     delete ctx->model;
      |     ^~~~~~~~~~~~~~~~~
# github.com/go-skynet/LocalAI/pkg/grpc/llm/llama
pkg/grpc/llm/llama/llama.go:32:9: undefined: llama.WithRopeFreqBase
pkg/grpc/llm/llama/llama.go:33:9: undefined: llama.WithRopeFreqScale
pkg/grpc/llm/llama/llama.go:82:24: cannot use opts.Temperature (variable of type float32) as float64 value in argument to llama.SetTemperature
pkg/grpc/llm/llama/llama.go:83:17: cannot use opts.TopP (variable of type float32) as float64 value in argument to llama.SetTopP
pkg/grpc/llm/llama/llama.go:88:25: cannot use ropeFreqBase (variable of type float32) as float64 value in argument to llama.SetRopeFreqBase
pkg/grpc/llm/llama/llama.go:89:26: cannot use ropeFreqScale (variable of type float32) as float64 value in argument to llama.SetRopeFreqScale
pkg/grpc/llm/llama/llama.go:90:32: cannot use opts.NegativePromptScale (variable of type float32) as float64 value in argument to llama.SetNegativePromptScale
pkg/grpc/llm/llama/llama.go:112:64: cannot use opts.MirostatETA (variable of type float32) as float64 value in argument to llama.SetMirostatETA
pkg/grpc/llm/llama/llama.go:116:64: cannot use opts.MirostatTAU (variable of type float32) as float64 value in argument to llama.SetMirostatTAU
pkg/grpc/llm/llama/llama.go:126:60: cannot use opts.PresencePenalty (variable of type float32) as float64 value in argument to llama.SetPenalty
pkg/grpc/llm/llama/llama.go:126:60: too many errors
make: *** [Makefile:350: backend-assets/grpc/llama] Error 1
ERROR: Service 'api' failed to build: The command '/bin/sh -c ESPEAK_DATA=/build/lib/Linux-$(uname -m)/piper_phonemize/lib/espeak-ng-data make build' returned a non-zero code: 2

To Reproduce
Change image to image: quay.io/go-skynet/local-ai:v1.23.0-cublas-cuda11 then  docker-compose up -d

run make clean after git pull. You are probably using old code checkouts

That was the issue, it works now thanks!


first day of week

Hi,
would it be possible to set by config which day should be displayed as first day of week e.g. Monday instead of Sunday?
Thanks

Looking in calendar_monthly.js right now, but no luck :(

Yes, that would be very much appreciated. I am in Europe and seeing Sunday in the first column confuses me every time as I expect Monday there. Without having that customization option the module is kinda useless for me. Also unfortunately there is no other comparable module, so I am stuck.
Thanks a lot!

Same same... Is there a workaround ?


URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).
HTTP URLs that Could Not Be Fixed
These URLs were unable to be fixed. Please review them to see if they can be manually resolved.

[ ] http://xslthl.sf.net (301) with 4 occurrences could not be migrated:
(https result AnnotatedConnectException).
[ ] http://exslt.org/common (404) with 1 occurrences could not be migrated:
(https result SSLHandshakeException).

Fixed URLs
Fixed But Review Recommended
These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended.

[ ] http://waffle.io/spring-cloud/spring-cloud-dataflow-server-kubernetes (301) with 2 occurrences migrated to:
https://waffle.io/spring-cloud/spring-cloud-dataflow-server-kubernetes (https result ReadTimeoutException).
[ ] http://<IP_ADDRESS>:8080 (ConnectTimeoutException) with 1 occurrences migrated to:
https://<IP_ADDRESS>:8080 (https result ConnectTimeoutException).
[ ] http://<IP_ADDRESS> (ConnectTimeoutException) with 4 occurrences migrated to:
https://<IP_ADDRESS> (https result ConnectTimeoutException).
[ ] http://<IP_ADDRESS>:31991 (ConnectTimeoutException) with 2 occurrences migrated to:
https://<IP_ADDRESS>:31991 (https result ConnectTimeoutException).
[ ] http://<IP_ADDRESS>:32123 (ConnectTimeoutException) with 1 occurrences migrated to:
https://<IP_ADDRESS>:32123 (https result ConnectTimeoutException).

Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

[ ] http://cloud.spring.io/spring-cloud-dataflow/ with 1 occurrences migrated to:
https://cloud.spring.io/spring-cloud-dataflow/ (https result 200).
[ ] http://cloud.spring.io/spring-cloud-skipper/ with 2 occurrences migrated to:
https://cloud.spring.io/spring-cloud-skipper/ (https result 200).
[ ] http://docs.spring.io/spring-boot/docs/current/reference/html/howto-logging.html with 1 occurrences migrated to:
https://docs.spring.io/spring-boot/docs/current/reference/html/howto-logging.html (https result 200).
[ ] http://docs.spring.io/spring-cloud-dataflow-server-kubernetes/docs/current-SNAPSHOT/reference/htmlsingle/ with 1 occurrences migrated to:
https://docs.spring.io/spring-cloud-dataflow-server-kubernetes/docs/current-SNAPSHOT/reference/htmlsingle/ (https result 200).
[ ] http://docs.spring.io/spring-cloud-dataflow/docs/ with 4 occurrences migrated to:
https://docs.spring.io/spring-cloud-dataflow/docs/ (https result 200).
[ ] http://docs.spring.io/spring-cloud-dataflow/docs/2.0.0.BUILD-SNAPSHOT/reference/htmlsingle/ with 1 occurrences migrated to:
https://docs.spring.io/spring-cloud-dataflow/docs/2.0.0.BUILD-SNAPSHOT/reference/htmlsingle/ (https result 200).
[ ] http://github.com/ with 1 occurrences migrated to:
https://github.com/ (https result 200).
[ ] http://stackoverflow.com with 1 occurrences migrated to:
https://stackoverflow.com (https result 200).
[ ] http://stackoverflow.com/tags/spring-cloud-dataflow with 2 occurrences migrated to:
https://stackoverflow.com/tags/spring-cloud-dataflow (https result 200).
[ ] http://bit.ly/Celsius-SR3-stream-applications-kafka-10-docker with 1 occurrences migrated to:
https://bit.ly/Celsius-SR3-stream-applications-kafka-10-docker (https result 301).
[ ] http://bit.ly/Celsius-SR3-stream-applications-rabbit-docker with 1 occurrences migrated to:
https://bit.ly/Celsius-SR3-stream-applications-rabbit-docker (https result 301).
[ ] http://kubernetes.io/docs/user-guide/configmap/ with 1 occurrences migrated to:
https://kubernetes.io/docs/user-guide/configmap/ (https result 301).
[ ] http://kubernetes.io/docs/user-guide/prereqs/ with 1 occurrences migrated to:
https://kubernetes.io/docs/user-guide/prereqs/ (https result 301).
[ ] http://kubernetes.io/docs/user-guide/secrets/ with 1 occurrences migrated to:
https://kubernetes.io/docs/user-guide/secrets/ (https result 301).
[ ] http://repo.spring.io/ with 1 occurrences migrated to:
https://repo.spring.io/ (https result 302).

Ignored
These URLs were intentionally ignored.

http://docbook.org/ns/docbook with 4 occurrences
http://docbook.sourceforge.net/xmlns/l10n/1.0 with 2 occurrences
http://localhost:8761/eureka/ with 1 occurrences
http://localhost:8888 with 1 occurrences
http://www.w3.org/1999/XSL/Format with 2 occurrences
http://www.w3.org/1999/XSL/Transform with 6 occurrences
http://www.w3.org/1999/xlink with 1 occurrences

merged with mods in da4378921


5 title element

when i view the title element
then i find concise, descriptive title

Added descriptive title


NameLayer fixes

Why does this include undoing https://github.com/CivClassic/NameLayer/commit/1a25dbf42b784aa3f38462ef979ae3e42c5c7d60 to readd the Mercury dependency?

Also I'm fine with merging this, but think we might want to diverge entirely for the 1.14 branch then instead of merging it later on

Mercury APIs are present within the following files:-

command/commands/*
gui/AdminFunctionsGUI
gui/InvitationGUI
gui/MainGroupGUI
group/AutoAcceptHandler
group/Blacklist
group/Group
listeners/MercuryMessageListener
misc/Mercury
permission/GroupPermission
GroupManager
NameLayerPlugin

It felt like too big of a change to make, to remove all this based off of Teal removing just the dependency. I felt it better to re-add it, if only so that it'll compile, then deciding where to go from there if it became an issue.
As for this pull request, it doesn't have anything to do with the 1.14 update, but just to fix some glaring issues with what's currently running on the server :)

I thought I already did all the work to remove mercury. Why are you starting from a branch before that effort? it was in with the 1.12 updates or 1.13 start, I forget which.

Because there's a problem that needs to be imminently fixed on Civclassics and this is the master branch for the Civclassics fork? If there's a 1.12 version out there in the ether that has already fixed these things... that's great... but why hasn't that been reflected here... and more important, why isn't that being used on the server then? I can remove all the Mercury stuff if it's really that important, but I'd really, really like the fix the whole one player being able to lag the entire server with one command/gui click because the server is waiting for the database to delete an entry from the database.

Idk why civclassic does what it does.
On Thu, Jan 9, 2020, 19:38 Alexander<EMAIL_ADDRESS>wrote:

Because there's a problem that needs to be imminently fixed on Civclassics
and this is the master branch for the Civclassics fork? If there's a 1.12
version out there in the ether that has already fixed these things...
that's great... but why hasn't that been reflected here... and more
important, why isn't that being used on the server then? I can remove all
the Mercury stuff if it's really that important, but I'd really, really
like the fix the whole one player being able to lag the entire server with
one command/gui click because the server is waiting for the database to
delete an entry from the database.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/CivClassic/NameLayer/pull/11?email_source=notifications&email_token=AADD5DWWSKPES3X7ODYD24TQ467RZA5CNFSM4KESKSG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEISI5TI#issuecomment-572821197,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADD5DRSBNR7GZIPS6URSYDQ467RZANCNFSM4KESKSGQ
.

So what should be the next move?

Probably contribute the fixes as a patch (without re-adding mercury), once to master (and let Maxopoly deal with the compile problems) -- and second as a patch to civ14 branch, which iirc includes the full mercury removal (and should be 1.12 ... if the civmodcore api calls are still compatible with the 1.12 civmodcore)
Or yeah, just contribute this same effort (which seems great, btw) as a patch that does not re-add the mercury deps, to master, and don't worry about the build problem that you would experience locally.

Oke, I'll work on removing Mercury

Done and tested, everything seems in working order

huh, ok. My comments were meant to encourage you not to worry about removing those code lines since they were already removed in the pending civ14 branch, but hey! looks good. Enjoy, @Maxopoly :)

Idk why civclassic does what it does.

Me neither tbh

Staged and will be deployed with next restart


lit-html, lit-element and redux : _stateChanged ignore template attributes update

Also I came to this specific use-case where a LitElement updates one of its attributes from a redux state property and an attribute in a lit-html template (the template returned from the render method).
Here's the reproduction
I tried to simplify as much as I could.
Simply put, the main view (person-view) html is embedding another custom element (person-card) and set one of its attributes using the "dot notation" (.personId="${this._personId}").
When the state changes (clicking the button) the main view updates its property _personId. Naturally I was expecting the view to update the html attribute of person-card as well so when person-card _stateChanged method is called its property personId value is coherent to the application global state.
I found that was natural because person-card is one leaf of the tree which is the application and should rely on its parents' state.
I think this behavior is caused from the methods _stateChanged called in an asynchronous way or technically not awaiting upper elements dom full update (I can't really tell as my understand of how the core libraries work is limited).
As for now I am trying to find a workaround but If you think this case deserves special attention I'd be gladly waiting for an update.
Love you Polymer Team !

Just a quick addition, this is the workaround I found and I think this is the syntax some lit-element showcases are using.
However in my project I really need to do the treatment in the _stateChanged method because the computed property is coherent to the element and is used subsequently in other elements' methods.
What I mean is that the property is not used for rendering purpose only. So I maintain the state of this issue.

It looks like lit-element will rerender the template of the view asynchronously, so it turns out the personId gets updated in the child component after the _stateChanged method has been called. In your example the parent already has the correct state, but this state hasn't been propagated to the child yet.
I'm not sure what the best approach is to solve the issue (add a synchronous variant of _invalidate to LitElement?), but in any case this looks more like an issue for Polymer/lit-element than lit-html. Could you open a ticket there?

@bgotink Ok I will, thanks for your answer.


Fix get token error

Fix bug when get token error occures. This bug is due to a type conflict and do application to crash.
Upgrade gradle tools and google service versions

Thank you, I'll check and test it asap. 😃


issue #65 side menu to access app features

#65
-modified the side menu to look like mockups
-UI tests for all elements

Overall excellent job! I am happy and impressed with the changes 🥇
@Amanda-Kolopa I noticed I asked @zohalmir to test when on the side menu and upon clicking on the Schedule button does it take you to map_fragment view. I am not sure if this is necessary as the Calendar test already takes this into consideration. If we were to run this test "as a whole" then we have redundancy. What do you say?

@zohalmir I spoke with Amanda, she has agreed it is not needed. You can remove the test where it clicks on "Schedule" then goes back. It is redundant and no longer needed. Please remove it and I will then merge this request 😄


Provide docker-compose.yml with customized config for Postgres

New cardano-db-sync release <IP_ADDRESS> requires some postgres configuration changes. Details below:
From: https://github.com/input-output-hk/cardano-db-sync/blob/<IP_ADDRESS>-rc2/doc/migrations.md

stage 4: introduces all the other indexes. By default these are the indexes that were created by previous db-sync versions. This stage is executed when db-sync has reached 30mins before the tip of the chain. It is advised to increase the maintenance_work_mem from Postgres config to 0.5GB - 1GB to speed this process (default is 64MB). Also use the default (2) or higher max_parallel_maintenance_workers. These files can be modified or extended by users.

Inside cardano-db-sync repo in scripts directory I created:
mkdir docker
cd docker
touch change-postgres-config.sh

cardano-db-sync/scripts/docker/change-postgres-config.sh script.
Content of the startup.sh script:
#!/bin/bash
sed -i 's/^ *# *maintenance_work_mem *= *[^ ]*/maintenance_work_mem = 1GB #/' /var/lib/postgresql/data/postgresql.conf
sed -i 's/^ *# *max_parallel_maintenance_workers *= *[^ ]*/max_parallel_maintenance_workers = 4 #/' /var/lib/postgresql/data/postgresql.conf

Then added to docker-compose.yml line:
- ${PWD}/postgresdocker/:/docker-entrypoint-initdb.d to volumes:
    image: postgres:11.5-alpine
    environment:
      - POSTGRES_LOGGING=true
      - POSTGRES_DB_FILE=/run/secrets/postgres_db
      - POSTGRES_PASSWORD_FILE=/run/secrets/postgres_password
      - POSTGRES_USER_FILE=/run/secrets/postgres_user
    secrets:
      - postgres_password
      - postgres_user
      - postgres_db
    ports:
      - ${POSTGRES_PORT:-5432}:5432
    volumes:
      - postgres:/var/lib/postgresql/data
      - ${PWD}/scripts/docker:/docker-entrypoint-initdb.d
    restart: on-failure

Looks like script was executed:
docker compose logs postgres
cardano-db-sync-postgres-1  | The files belonging to this database system will be owned by user "postgres".
cardano-db-sync-postgres-1  | This user must also own the server process.
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | The database cluster will be initialized with locale "en_US.utf8".
cardano-db-sync-postgres-1  | The default database encoding has accordingly been set to "UTF8".
cardano-db-sync-postgres-1  | The default text search configuration will be set to "english".
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | Data page checksums are disabled.
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
cardano-db-sync-postgres-1  | creating subdirectories ... ok
cardano-db-sync-postgres-1  | selecting default max_connections ... 100
cardano-db-sync-postgres-1  | selecting default shared_buffers ... 128MB
cardano-db-sync-postgres-1  | selecting default timezone ... UTC
cardano-db-sync-postgres-1  | selecting dynamic shared memory implementation ... posix
cardano-db-sync-postgres-1  | creating configuration files ... ok
cardano-db-sync-postgres-1  | running bootstrap script ... ok
cardano-db-sync-postgres-1  | sh: locale: not found
cardano-db-sync-postgres-1  | 2022-11-29 16:54:07.854 UTC [29] WARNING:  no usable system locales were found
cardano-db-sync-postgres-1  | performing post-bootstrap initialization ... ok
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | WARNING: enabling "trust" authentication for local connections
cardano-db-sync-postgres-1  | You can change this by editing pg_hba.conf or using the option -A, or
cardano-db-sync-postgres-1  | --auth-local and --auth-host, the next time you run initdb.
cardano-db-sync-postgres-1  | syncing data to disk ... ok
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | Success. You can now start the database server using:
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | waiting for server to start....2022-11-29 16:54:08.326 UTC [33] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.366 UTC [34] LOG:  database system was shut down at 2022-11-29 16:54:08 UTC
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.375 UTC [33] LOG:  database system is ready to accept connections
cardano-db-sync-postgres-1  |  done
cardano-db-sync-postgres-1  | server started
cardano-db-sync-postgres-1  | CREATE DATABASE
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/change-postgres-config.sh
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | waiting for server to shut down....2022-11-29 16:54:08.680 UTC [33] LOG:  received fast shutdown request
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.687 UTC [33] LOG:  aborting any active transactions
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.688 UTC [33] LOG:  background worker "logical replication launcher" (PID 40) exited with exit code 1
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.688 UTC [35] LOG:  shutting down
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.733 UTC [33] LOG:  database system is shut down
cardano-db-sync-postgres-1  |  done
cardano-db-sync-postgres-1  | server stopped
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | PostgreSQL init process complete; ready for start up.
cardano-db-sync-postgres-1  |
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.795 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.795 UTC [1] LOG:  listening on IPv6 address "::", port 5432
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.809 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.842 UTC [48] LOG:  database system was shut down at 2022-11-29 16:54:08 UTC
cardano-db-sync-postgres-1  | 2022-11-29 16:54:08.852 UTC [1] LOG:  database system is ready to accept connections

Checking postgres container:
docker ps
CONTAINER ID   IMAGE                             COMMAND                  CREATED          STATUS                             PORTS                                       NAMES
dd90ca482af6   postgres:11.5-alpine              "docker-entrypoint.s…"   43 seconds ago   Up 42 seconds (healthy)            <IP_ADDRESS>:5432->5432/tcp, :::5432->5432/tcp   cardano-db-sync-postgres-1
7a18b4159127   inputoutput/cardano-node:1.35.4   "entrypoint"             43 seconds ago   Up 42 seconds (health: starting)                                               cardano-db-sync-cardano-node-1

checking postgres config  file:
docker exec -it dd90ca482af6 bash
bash-5.0# cat /var/lib/postgresql/data/postgresql.conf | grep maint
maintenance_work_mem = 1GB # min 1MB
#autovacuum_work_mem = -1		# min 1MB, or -1 to use maintenance_work_mem
max_parallel_maintenance_workers = 4 # taken from max_parallel_workers
bash-5.0#


XGBoost Evaluator Proposal

Draft pull request for the XGBoost Evaluator issue, located here.

Is my assumption correct that we will need:
examples/xgboost_pipeline
tfx_addons/xgboost_evaluator

Is my assumption correct that we will need?
examples/xgboost_pipeline
tfx_addons/xgboost_evaluator

@cent5 @kindalime

Yes! Also I think we may want to move examples/sklearn_penguins/data/ up one level to share it between the example pipelines, instead of duplicating the data.

That sounds about right, yes.

open


test inventory object refresh removal

mmm I missed nuage

i feel like the ovirt failure on this is all lies
https://github.com/ManageIQ/manageiq-cross_repo-tests/pull/91

@d-m-u looks like just nuage failing which is expected


How to deal with multiple texture updates per bgfx::frame()?

I have a LUT which sits in texture memory and is accessed in the shader.
I'd like to execute this shader multiple times on different inputs, with different LUTs, outputting to different framebuffers.
I implemented this using the Views mechanism: one view per render to one of the framebuffers using a unique LUT.
However, it seems that textures are only updated once per bgfx::frame(), and not between rendering different Views. Is there a reason why I can't update textures between views? If so, how would you deal with such a situation? It seems a waste to make 10 different textures that will be used as LUT, such that I can use one texture per view; or wouldn't you agree that this is a waste?

For completeness, my situation looks like this:
for (int view = 0; view < 10; ++view) {
    bgfx::setViewMode(view, bgfx::ViewMode::Sequential);

    const bgfx::Memory *lut_mem = bgfx::alloc(lut[view].size() * sizeof(float));
    std::memcpy(lut_mem->data, lut[view].data(), lut[view].size() * sizeof(float));
    bgfx::updateTexture2D(m_texture_lut, 0, 0, 0, 0, lut[view].size(), 1, lut_mem); // << UPDATE HERE

    bgfx::setTexture(0, m_uni_input, m_texture_input);
    bgfx::setTexture(1, m_uni_lut, m_texture_lut);

    bgfx::setViewFrameBuffer(view, dst[view]->target_framebuffer());
    bgfx::setViewClear(view, BGFX_CLEAR_COLOR | BGFX_CLEAR_DEPTH, 0xff3366ff);
    bgfx::setViewRect(view, 0, 0, dst[view]->width(), dst[view]->height());
    bgfx::setState(BGFX_STATE_WRITE_RGB | BGFX_STATE_WRITE_A);
    bgfx::setVertexBuffer(0, m_vertex_buffer);
    bgfx::setIndexBuffer(m_index_buffer);

    bgfx::submit(view, my_shader);
}
bgfx::frame();

The loop updates (updateTexture2D) the same texture m_texture_lut multiple times: once for each submit(). But they are all rendered within the same bgfx::frame() and are ALL rendered with one shared LUT, instead of every render with its own LUT.

Okay, I found the whole TextureUpdateBatch mechanism in the source; and how a texture batch update command is put in the command buffer as soon as the update buffer gets full.
I didn't find a way to manually encode a CommandBuffer::UpdateTexture, which would be hard to get it into the right position as the order of the Views is determined even later...
So I guess I see two options here:

use multiple textures.
use bgfx::frame() for every render and fix #1936 in order for Vulkan to work properly.

Suggestions, thoughts, or ideas?

Yes, multiple textures, or texture array, or texture atlas... All data must be available at frame.


up_squared: zbus: hello_world: sample output mangling fails regex verification

The hello_world test requires orderly console output to verify the proper operation of the program via RegEx. The bug mangles the output of two output lines in total, making RegEx not recognize the required lines and timing out the test.
part of the log:
DEBUG   - DEVICE: I: Sensor sample started raw reading, version 0.1-2!
DEBUG   - DEVICE: I: Channel list:
DEBUG   - DEVICE: I: 0 - Channel acc_data_chan:
DEBUG   - DEVICE: I:       Message size: 12
DEBUG   - DEVICE: I:       Observers:
DEBUG   - DEVICE: I:       - foo_lis
DEBUG   - DEVICE: I:       - bar_sub
DEBUG   - DEVICE: I: 1 - Channel simple_chan:
DEBUG   - DEVICE: I:       Message size: 4
DEBUG   - DEVICE: I:       Observers:
DEBUG   - DEVICE: I: 2 - Channel version_chan:
DEBUG   - DEVICE: I:       Message size: 4
DEBUG   - DEVICE: I:       Observers:
DEBUG   - DEVICE: I: Observers list:
DEBUG   - DEVICE: I: 0 - Subscriber bar_sub
DEBUG   - DEVICE: I: 1 - Listener foo_lis
DEBUG   - DEVICE: I: From listener -> Acc x=1, y=1, z=1
DEBUG   - DEVICE: I: From subscriber -> Acc x=1, y=1, z=1
DEBUG   - DEVICE: I: From listener -> Acc x=2, y=2, z=2
DEBUG   - DEVICE: II::  FPruobm  as uvbaslcirdi bvearl u-e>  tAoc ca  xc=h2a,n nye=l2 ,w izt=h2
DEBUG   - DEVICE: validator successfully.
DEBUG   - DEVICE: I: Pub an invalid value to a channel with validator successfully.

This line is corrupted:
DEBUG   - DEVICE: II::  FPruobm  as uvbaslcirdi bvearl u-e>  tAoc ca  xc=h2a,n nye=l2 ,w izt=h2

And it should looks like:
DEBUG   - DEVICE: I: Pub a valid value to a channel with validator successfully."

To Reproduce
Steps to reproduce the behavior:

Connect at least one UP Squared board to your controller and map it

Run the CHRE test
<path/to>/zephyrproject/zephyr$ ./scripts/twister --device-testing --hardware-map <path/to>/<up2.map> -T samples/subsys/zbus/hello_world/ -vv

The test should fail.

Expected behavior
The test should pass.
Impact
Currently, annoyance and lack of clear test output. However, name mangling while using RegEx to verify program operation can lead to further test failures and thus useless tests.
Logs and console output
DEBUG   - DEVICE: >>Media Present......
DEBUG   - DEVICE: Downloading NBP file...
DEBUG   - DEVICE:
DEBUG   - DEVICE: Succeed to download NBP file.
DEBUG   - DEVICE: *** Zephyr EFI Loader ***
DEBUG   - DEVICE: RSDP found at 0x79c34000
DEBUG   - DEVICE: Zeroing 4824560 bytes of memory at 0x108000
DEBUG   - DEVICE: Copying 32768 data bytes to 0x1000 from image offset
DEBUG   - DEVICE: Copying 32768 data bytes to 0x100000 from image offset 32768
DEBUG   - DEVICE: Copying 2110184 data bytes to 0x5a1e00 from image offset 65536
DEBUG   - DEVICE: Jumping to Entry Point: 0x1137 (48 31 c0 48 31 d2 48)
DEBUG   - DEVICE: I: Sensor sample started raw reading, version 0.1-2!
DEBUG   - DEVICE: I: Channel list:
DEBUG   - DEVICE: I: 0 - Channel acc_data_chan:
DEBUG   - DEVICE: I:       Message size: 12
DEBUG   - DEVICE: I:       Observers:
DEBUG   - DEVICE: I:       - foo_lis
DEBUG   - DEVICE: I:       - bar_sub
DEBUG   - DEVICE: I: 1 - Channel simple_chan:
DEBUG   - DEVICE: I:       Message size: 4
DEBUG   - DEVICE: I:       Observers:
DEBUG   - DEVICE: I: 2 - Channel version_chan:
DEBUG   - DEVICE: I:       Message size: 4
DEBUG   - DEVICE: I:       Observers:
DEBUG   - DEVICE: I: Observers list:
DEBUG   - DEVICE: I: 0 - Subscriber bar_sub
DEBUG   - DEVICE: I: 1 - Listener foo_lis
DEBUG   - DEVICE: I: From listener -> Acc x=1, y=1, z=1
DEBUG   - DEVICE: I: From subscriber -> Acc x=1, y=1, z=1
DEBUG   - DEVICE: I: From listener -> Acc x=2, y=2, z=2
DEBUG   - DEVICE: II::  FPruobm  as uvbaslcirdi bvearl u-e>  tAoc ca  xc=h2a,n nye=l2 ,w izt=h2
DEBUG   - DEVICE: validator successfully.
DEBUG   - DEVICE: I: Pub an invalid value to a channel with validator successfully.
DEBUG   - Timed out while monitoring serial output on up_squared
DEBUG   - run status: up_squared/samples/subsys/zbus/hello_world/sample.zbus.hello_world error
INFO    - 2/2 up_squared                samples/subsys/zbus/hello_world/sample.zbus.hello_world  ERROR No Console Output(Timeout) (device 63.291s)

Environment:

OS: Ubuntu for the controller
Toolchain: Zephyr SDK 15.0
The current Zephyr version used

Additional context
Multiline RegEx used in the test in question:
regex:
        - "I: Sensor sample started raw reading, version 0.1-2!"
        - "I: Channel list:"
        - "I: 0 - Channel acc_data_chan:"
        - "I:       Message size: 12"
        - "I:       Observers:"
        - "I:       - foo_lis"
        - "I:       - bar_sub"
        - "I: 1 - Channel simple_chan:"
        - "I: 2 - Channel version_chan:"
        - "I:       Message size: 4"
        - "I: Observers list:"
        - "I: 0 - Subscriber bar_sub"
        - "I: 1 - Listener foo_lis"
        - "I: From subscriber -> Acc x=1, y=1, z=1"
        - "I: From listener -> Acc x=1, y=1, z=1"
        - "I: From subscriber -> Acc x=2, y=2, z=2"
        - "I: From listener -> Acc x=2, y=2, z=2"
        - "I: Pub a valid value to a channel with validator successfully."
        - "I: Pub an invalid value to a channel with validator successfully."

The problem is similar to this issue:
https://github.com/zephyrproject-rtos/zephyr/issues/54861
https://github.com/zephyrproject-rtos/zephyr/issues/55076

The template text needs to be changed to something useful. Please change the content in each section with details.

@nashif > The template text needs to be changed to something useful. Please change the content in each section with details.
Sorry, I was in the middle of typing when I accidentally posted an issue

According to my investigation, this test passed after changing CONFIG_SMP parameter in
<paht/to>/zephyr/boards/x86/up_squared/up_squared_defconfig
from CONFIG_SMP=y to CONFIG_SMP=n.
Moreover, test <path/to>/tests/kernel/smp has a parameter platform_allow: qemu_x86_64. This can mean, that the up2 board doesn't support smp.

This is likely a shared stack variable going across cores where the cache coherence isn't kept. Just a guess though.

Any update ?

Any update ?

@SzymonRichert
Does the up2 board support SMP? Because based on the  @gbarkadiusz comment, the test passed when SMP was disabled.

@rodrigopex  yes, this board supports SMP.

This might be more related to how logging works and on SMP its possible to get mangled logs if the log backend doesn't deal with concurrency in a log immediate mode. Or similarly with SMP and printk. There's a Kconfig option to serialize printk calls I believe. Or route printk through logging.
In the end this looks like a race on the output stream where the messages are not being serialized properly in some way. That seems to be likely the case for #54861 as well.

The isssue still exists

@KamilxPaszkiet, Would you happen to have a solution idea? I could not figure out a way to solve that. Changing the regex to fit the case is not the way to go. The SMP support for the architecture is out of ZBus's scope. I cannot even run the code. There is no simulator for that.

@nashif maybe you can help?

@rodrigopex I have the board and can reproduce the issue. I don't have a concrete fix proposal however.
Do I understand correctly that the issue is multiple CPU cores trying to produce output to the console at the same time? In that case this doesn't sound board-specific, rather SMP specific. Most likely the logging subsystem (and printk implementation) should somehow create critical regions over each high-level logging call, so that while the call is entered (typically mapping to one line of output) no other place in the tree can also try to output something at the same time.
As far as I can see, this is at least not an issue with the UART driver - the interface between UART console and the UART driver, or log_backend_uart.c and the UART driver, is on a per-character basis, so the (seemingly) missing locking would need to be done in some layer above the UART driver. @nordic-krch any thoughts here?

@jhedberg, I see. Based on that, we can say that it is not a zbus issue, right? I imagine it is a more general "big" issue related to SMP and log/print.

@jhedberg, I see. Based on that, we can say that it is not a zbus issue, right? I imagine it is a more general "big" issue related to SMP and log/print.

Yes, that's what it looks like to me. Would be good to get some comment from the logging subsystem maintainer.

Btw, looks like there are other bug reports as well with the same likely root cause: #54861

When minimal logging is used, then any log is converted to printk which polls out characters one by one so it can be interrupted by any other thread and output can be interleaved. There are two options: change to use deferred mode (CONFIG_LOG_MODE_DEFERRED=y) or use immediate mode with clean output (interrupts are locked for each message processing): CONFIG_LOG_MODE_IMMEDIATE=y CONFIG_LOG_IMMEDIATE_CLEAN_OUTPUT=y

@nordic-krch thanks. I can confirm that with the following patch (which causes deferred mode to be used) the output is normal again:
--- a/samples/subsys/zbus/hello_world/prj.conf
+++ b/samples/subsys/zbus/hello_world/prj.conf
@@ -1,5 +1,4 @@
 CONFIG_LOG=y
-CONFIG_LOG_MODE_MINIMAL=y
 CONFIG_BOOT_BANNER=n
 CONFIG_MAIN_THREAD_PRIORITY=5
 CONFIG_ZBUS=y

@KamilxPaszkiet in the future when you have these "output fails regex verification", as the first thing please check what log mode is used. It seems both this issue as well as #54861 are both caused by the samples setting CONFIG_LOG_MODE_MINIMAL=y. I just confirmed that the output is normal (not garbled) if I remove the setting and let the default (LOG_MODE_DEFERRED) be used instead. Same goes for LOG_MODE_IMMEDIATE - it's expected that the output is garbled if that's not combined with LOG_IMMEDIATE_CLEAN_OUTPUT.
Now, I'm wondering what's the right course of action here: do we want to forbid any application from using LOG_MODE_MINIMAL? It has its uses, so that seems a bit harsh. Maybe you should simply filter out any tests from your test matrix that enable LOG_MODE_MINIMAL (or LOG_MODE_IMMEDIATE without LOG_IMMEDIATE_CLEAN_OUTPUT).
Either way, neither of these two issues is specific to up_squared, rather they could happen on any SMP platform.

@nordic-krch would it perhaps make sense to add depends on !SMP to LOG_MODE_MINIMAL?

@nordic-krch would it perhaps make sense to add depends on !SMP to LOG_MODE_MINIMAL?

Hmm, I took a look at the implementation, and it seems it's just mapping to printk(). And actually even if it wasn't possible to enable it for SMP systems there's still any direct printk() calls themselves that apps might do. I wonder if it'd then make sense to consider adding (behind a new Kconfig option) some locking to printk itself, to prevent garbled output.

Strange but there is already PRINTK_SYNC (https://github.com/zephyrproject-rtos/zephyr/blob/ecb2df0444f10bd21dbdd1220cbe353655cab5cc/lib/os/Kconfig#L37)  default to y for SMP but not when log is used.
default y if SMP && MP_MAX_NUM_CPUS > 1 && !(EFI_CONSOLE && LOG)

@nordic-krch that seems to come from commit e696de1f316e85dc2209f7ff5e6a6518e54eb9ed
I'm not so sure it's a valid change though, since typically what you get on x86 systems is that EFI console is used during early boot and the overridden by UART console later, so there locking will still be needed.

@enjiamai any comments on the above?

After reading https://github.com/zephyrproject-rtos/zephyr/issues/45929#issuecomment-1141159022 it sounds like maybe we should remove default y from X86_EFI_CONSOLE:
https://github.com/zephyrproject-rtos/zephyr/blob/f89c5ddd1aaf0e4a5b6fd0a1397c5a72f1cba388/arch/x86/Kconfig#L471-L475
@andyross @dcpleung @tbursztyka @finikorg FYI

Created a fix proposal: https://github.com/zephyrproject-rtos/zephyr/pull/65739


Ignite 481

https://issues.apache.org/jira/browse/IGNITE-481 Closed as won't fix, closing PR as well


Fabric 1.19.2 support

look at title

What about it

Srry not completed

Ok, so I don't know how I misunderstood this then, but sorry. I won't be adding support for 1.19, cos library I use doesn't have features I need in those versions. Again, sorry for miscommunication on my part, and thank you for sending the issue. Thread closed.