feat: Asset endpoint profile commands

Cont. of  https://github.com/Azure/azure-edge-cli-extension/pull/51
https://github.com/Azure/azure-iot-ops-cli-extension/pull/72
SHINY NEW FEATURES:

asset create now checks if the asset endpoint profile exists (within the sub) and gives a warning if it doesn't!

Non blocking because it may still succeed! WOW!

asset and asset endpoint commands that would result in the asset being modified now have a does this cluster exist and is it online check! Warns if it doesn't!
Create:

Update:

Delete:

Non blocking because of race conditions that could make things succeed! WOW!

asset endpoints commands are mostly a copy paste of asset commands! So that means that endpoints also have the nifty cluster + custom location check! WOW!
Asset endpoint create has a nifty way to figure out what authentication mode you are using and what you are missing based on inputs! Less inputs! WOW!
asset endpoints have a sub command for transportation authentication - aka what certificates are associated with this endpoint. Different from user authentication. WOW!
Assets and asset endpoints are now under a folder called ADR and have a shared base class that handles common commands like show, delete, list, and cluster checks! WOW!

Future:

make the warnings actual errors with a flag to ignore errors
query gets old api assets too - it is fun to see what jank people did!
The following will get stuck (with no keyboard interrupt) because poller.result() forces the current thread to wait till the poller is done. Once we figure out what to do in general to avoid poller.result(), apply it to these commands too:

asset's subpoint add and remove
asset endpoint profile certificate add and remove

WOW!

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact<EMAIL_ADDRESS>with any additional questions or comments.
Thank you for contributing to Azure IoT Operations tooling!
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Intent for Production

[ ] It is expected that pull requests made to default or core branches such as dev or main are of production grade. Corollary to this, any merged contributions to these branches may be deployed in a public release at any given time. By checking this box, you agree and commit to the expected production quality of code.

Basic expectations

[ ] If introducing new functionality or modified behavior, are they backed by unit and/or integration tests?
[ ] In the same context as above are command names and their parameter definitions accurate? Do help docs have sufficient content?
[ ] Have all the relevant unit and integration tests pass? i.e. pytest <project root> -vv. Please provide evidence in the form of a screenshot showing a succesful run of tests locally OR a link to a test pipeline that has been run against the change-set.
[ ] Have linter checks passed using the .pylintrc and .flake8 rules? Look at the CI scripts for example usage.
[ ] Have extraneous print or debug statements, commented out code-blocks or code-statements (if any) been removed from the surface area of changes?
[ ] Have you made an entry in HISTORY.rst which concisely explains your user-facing feature or change?

Azure IoT Operations CLI maintainers reserve the right to enforce any of the outlined expectations.
A PR is considered ready for review when all basic expectations have been met (or do not apply).

@digimaun I smoke tested all commands under asset at this point(including asset endpoint), everything working as expected


Delete unnecessary spaces

Delete unnecessary spaces: When copying from the web page, there is an unnecessary space after the code.
Fix indent: Indentation is misaligned.

@changeworld : Thanks for your contribution! The author, @craigshoemaker, has been notified to review your proposed change.

Thanks again, @changeworld!
#sign-off

@changeworld - Thank you for your submission. We are not able to accept these kinds of changes (formatting and spacing changes) in the repo at this time.


Error on installation in Ubuntu

The error is fllowing one:
/usr/bin/ld: cannot find -loflops_test
collect2:error:ld returned 1 exit status
make[2]: *** [Makefile:587:oflops] Error 1
make[2]: Leaving directory '/home/smallbian/oflops'
make[1]: *** [Makefile:657:all-recursive] Error 1
make[1]: Leaving directory '/home/smallbian/oflops'
make: *** [Makefile:443:all] Error 2
Thanks

use low version of Ubuntn can fix this problem


Add BarbicanSpecCore struct

This version of the struct (called "core") is meant to be used via the OpenStackControlplane. It is the same as BarbicanSpec only it is missing the containerImages from the nested API, Backup, Scheduler, and Volume specs.
The Default() function for webhooks has been split accordingly.
Jira: OSPRH-4835

/lgtm


Cannot GET /

Describe the bug
Stuck there... Cannot GET /
Been trying to fix the error for 1000000 tokens! Nothing works!

Screen Recording / Screenshot
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

Appreciate the feedback! At time, the AI model is unable to solve programming challenges and manual intervention is required. Did you receive any other error message in the console?


Col_widths and colsVisibility

I've not noticed this before so I'm not sure if this is new since 0.5.33 or if I've just never used both these features in combination.
Column widths appear to apply to the visible columns, not to the actual columns position.  Eg if I have a 2 column table with:
col_widths: ["10px","100px"]
eg an ID and a description when both are visible the column widths are 10px for column 0 (the ID) and 100px for column 1 the description.
When hiding column 0 the width of the description becomes 10px
eg open http://koalyptus.github.io/TableFilter/columns-visibility.html
and run this code
tf.destroy();
   var tfConfig = {
        base_path: 'tablefilter/',
        paging: true,
        state: { types: ['cookie'] },
        alternate_rows: true,
        rows_counter: true,
        btn_reset: true,
        btn_reset_text: 'Clear',
        status_bar: true,
		col_widths: ["50px","100px","200px","50px","100px","300px"],
        col_1: 'select',
        col_2: 'select',
        col_types: [
            'number', 'string', 'string',
            'formatted-number', 'formatted-number', 'string'
        ],

        /* columns visibility and sort extension */
        extensions: [{
              name: 'colsVisibility',
              at_start: [3, 5],
              text: 'Columns: ',
              enable_tick_all: true
          }, {
              name: 'sort'
        }]
    };
    var tf = new TableFilter('demo', tfConfig);
    tf.init();

(this is the existing config copied from the page with col_widths parameters added).
As you hide columns on the left of the table the columns move left and adopt the width of the column previously occupying that space rather than keeping their own width.
We're on v 0.5.33 and it appears on the live examples as well (v0.5.40)
Sorry for finding these "opportunities for improvement" ;-)

Tx for pointing this out, after a quick investigation seems to be a unexpected behaviour, there is always room for improvement 😄

@cjohnsonuk should now be fixed starting from v0.5.42


Contact Edit fails: 'Could not find contact with id 3'

View and Delete work as expected.

Could not find contact with id @ContactId.
 is the error message. That extra . looks like a problem but removing it changes nothing.
Did I break something after download?
Kal

I just tested and it worked fine. Is this clicked "edit" from the grid? With logging turned on, do you see any generated errors or messages?

Yes, it is clicked ‘edit’ from the grid.
I just grabbed a fresh clone from the site and did the migration step which linked it to the existing database. It works as expected.
I did a comparison of the two versions and some of the code has changed. Also, yesterday I updated all the Nugget links to the latest which I have not done with the today clone. In any case, seems to work now.
Thanks for your help,
Kal
From: Jeremy Likness<EMAIL_ADDRESS>Sent: Thursday, June 18, 2020 1:02 PM
To: JeremyLikness/BlazorWasmEFCoreExample<EMAIL_ADDRESS>Cc: Loren Kallevig<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [JeremyLikness/BlazorWasmEFCoreExample] Contact Edit fails: 'Could not find contact with id 3' (#7)
I just tested and it worked fine. Is this clicked "edit" from the grid? With logging turned on, do you see any generated errors or messages?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/JeremyLikness/BlazorWasmEFCoreExample/issues/7#issuecomment-646277298, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEHDK2MQP334C4WDD43SQHLRXJXDXANCNFSM4OCDG3UQ.

Glad you were able to sort it out. Thanks!


Use ssl instead of encryption pin

Socket connection should be protected by SSL
https://github.com/ale8193/shamir-fido/blob/24d7b3d9fad6e8e129ba758fe73758da218b6f43/src/socket/SocketServer.js#L17

For simplicity we can use a random pin (changed in every new connection) with the size of 256 bits to ensure a strong security of the communication channel


Avoid using magic number indexes in the node system

There are tons of fragile index values like 0, 1, 2, etc. used to reference inputs and outputs (amongst other things?) between nodes and node internals. This is extremely fragile, makes it hard to refactor, provides a difficult developer experience, lacks self-documenting clarity, and is hard to debug.
One potential solution could be using enums. But thinking through some alternative ways to achieve this could also be good.

Hey Keavon,
I'd be interested in contributing to this. Any chance we can chat about this issue?
Thanks

Hi @Kakapio, I don't think this issue is likely to be an easily-solved one that's easy for newcomers to jump on. But I'd encourage you to ask me on Discord for some advice about which issues you can get started with based on your background and I can direct you to some issues that are easier to begin with. Thanks!


ci: add releaserc preset and if statement

I wanted to add the preset that Parker and I talked about in a thread on #proj-gratibot so that the conventional-releaser actions would follow similar behavior to that of Sparky. Also, I wanted to add an if statement on the prod-apply job so that it wouldn't ask to deploy to the prod environemnt if there were no new releases made.

Example workflow of a push that includes changes is seen here
Example workflow of a push that doesn't include changes is seen here.

lgtm


Recovery options -> RestartService. Seconds.

I want my service to be restarted in 5 seconds after crash. I can configure it with SC utility, but how can I specify it with Topshelf?

Have you checked out the service recovery section?

Have you checked out the service recovery section?

Yes. There are only minutes.

set it to zero, that's what I do


Update zerossl-bot.sh

Issue with arguments caused some to issue with wrong CA

You sure this is good? Since I run from master, I get the following error with a DNS authentication hook (sensitive information removed):
technitium-dns_manager_server-1  | [2023-08-31T17:07:46Z DEBUG dns_manager_server::routes::dns_manager] CMD: cd "/tmp/.tmpAvP58B" && "zerossl-bot" "--zerossl-api-key=<zerossl_api_key>" "certonly" "--csr=csr.txt" "--config-dir=/var/certbot/config" "--logs-dir=/var/certbot/logs" "--work-dir=/var/certbot/work" "--manual" "--agree-tos" "--email=<email>" "-n" "--manual-public-ip-logging-ok" "--preferred-challenges=dns" "--manual-auth-hook=/usr/local/bin/dns-manager-server -z ion.ooo -t <api key> --email \'<email>\' --dns-endpoint \'http://technitium:5380/\' authentication-hook"
technitium-dns_manager_server-1  | [2023-08-31T17:07:49Z DEBUG dns_manager_server::routes::dns_manager] CMD stdout: certonly --csr=csr.txt --config-dir=/var/certbot/config --logs-dir=/var/certbot/logs --work-dir=/var/certbot/work --manual --agree-tos --email=<email> -n --manual-public-ip-logging-ok --preferred-challenges=dns --manual-auth-hook=/usr/local/bin/dns-manager-server -z ion.ooo -t <api key> --email '<email>' --dns-endpoint 'http://technitium:5380/' authentication-hook --eab-kid KIAEht_UuI9dasZUJJQAOw --eab-hmac-key <key> --server https://acme.zerossl.com/v2/DV90
technitium-dns_manager_server-1  |      stderr: usage:
technitium-dns_manager_server-1  |       certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...
technitium-dns_manager_server-1  |
technitium-dns_manager_server-1  |     Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
technitium-dns_manager_server-1  |     it will attempt to use a webserver both for obtaining and installing the
technitium-dns_manager_server-1  |     certificate.
technitium-dns_manager_server-1  |     certbot: error: unrecognized arguments: -z ion.ooo <api key> --dns-endpoint 'http://technitium:5380/' authentication-hook
technitium-dns_manager_server-1  |

I believe https://github.com/zerossl/zerossl-bot/pull/25 is the right way to do it. Why is it reverted?

@peterwilli you provided the wrong ARGs. The goal for this PR and my issue https://github.com/zerossl/zerossl-bot/issues/33 was to use the ${CERTBOT_ARGS[@]} instead of ARGS for certbot.
Make sure your zerossl-bot.sh has in the last line
certbot ${CERTBOT_ARGS[@]}

Make sure your zerossl-bot.sh has in the last line

Thanks for replying so soon! I used bash <(curl -s https://zerossl.com/get-zerosslbot.sh), which pulls from master (so all the merged PR's should've been in there). I still got the error message above.
Also, running curl https://raw.githubusercontent.com/zerossl/zerossl-bot/master/zerossl-bot.sh shows the last line you mentioned.


[BUG Datetimefeatures inconsistent formats / day_of_year not working

Some fixes to my first PR which contained a few inconsistencies and a bug
https://github.com/alan-turing-institute/sktime/issues/3189
https://github.com/alan-turing-institute/sktime/issues/3188

Hi I added two more tests and resolved the inplace use

@danbartl, if you don´t see this today, I´ll merge based on that the fit is already outside functions in pre-PR situation, to have the fix in the release. I would then open an issue on this so we track it. Will check back in a few hours.

Opened an issue here https://github.com/alan-turing-institute/sktime/issues/3237 so this can be addressed separately.
Merging so the fix is in the release.


build_log: make sure to carry the old uid and gid

see #1302 as a normal workflow you do things like "ninja all && sudo
ninja install" for the case that the install target executes a build
target then ninja_log will be writte ntwo which will result in its
permissions to be root / root, which is a problem since you cannot
execute the workflow from above again.

Okay its resolved, i saw that the problem is also in deps_log, so i added the same there!

How portable is this? (What about Windows?)

I have 2 patches that are making them portable, i just can compile them, but cannot run them (dont have a windows maschine arround ... ) I hope i can get tomorrow a running windows maschine and run it on there ...

I made it now work on windows (took a while to dive into theire api). Works now on windows and linux!
Any other comments? Or can it proceed ?

Is there anything blocking this PR to get accepted?
We have seen this issue several times in the process of getting our project moved from autotools+make to meson+ninja

This is replaced with #1588, i cannot update this one here anymore


Nucleus Datastore used as queue handler (blocking connections) are not destroyed properly

When a Nucleus Datastore uses the blocking command BRPOP (BLPOP), the client cannot be destroyed properly.

Fixed in 0.9.6


Feature request: Configure paths for storing parts of ngrx when separateDirectory is true

It's a great generator. Saves me whole bunch of time of writing those manually, I even hooked up an npm command in order not to install it globally. I have one feature request though. Would it be possible to configure paths via package.json where the files should be added. For example my structure requires to put actions, effects in ./app/shared/effects, ./app/shared/actions etc.
Regards

I will try to add this feature soon. Thanks!

Done! You can now add this:
 "ngrxGen": {
    "seperateDirectory": "true",
    "basePath": "./src/app/shared"
  }

Note that the path should be relative to your root package.json.

Thank you very much

Adding this configuration to the package.json gives an error saying:
res = path.slice(lastSlash + 1, i);  RangeError: Maximum call stack size exceeded


msleep will not wake with certain goroutines/channels setup

It is possible to cause an endless loop using two coroutines communicating over two channels, preventing msleep from wakeup in the main coroutine.
I found it while trying to add these coroutines to tests/signals, to create some other activity when receiving signals, and i get the same endless loop, breaking the send/receive signals loop in the main coroutine.
For example code, see: https://github.com/nirs/libmill/commit/ecefe4f1908629d66ea3cce043f33f9cc4e02dfb

Adding gotrace(1) in start of main, we see:
FAIL: tests/sched
=================

==> 00:11:03.585608 {0}      <1>=chmake(0) at tests/sched.c:40
==> 00:11:03.585668 {0}      <2>=chmake(0) at tests/sched.c:41
==> 00:11:03.585684 {0}      {1}=go() at tests/sched.c:43
==> 00:11:03.585694 {1}      chr(<1>) at tests/sched.c:32
==> 00:11:03.585709 {0}      {2}=go() at tests/sched.c:44
==> 00:11:03.585718 {2}      chr(<2>) at tests/sched.c:32
==> 00:11:03.585729 {0}      chs(<1>) at tests/sched.c:46
==> 00:11:03.585739 {1}      chs(<2>) at tests/sched.c:33
==> 00:11:03.585751 {2}      chs(<1>) at tests/sched.c:33
==> 00:11:03.585760 {1}      chr(<1>) at tests/sched.c:32
==> 00:11:03.585769 {2}      chr(<2>) at tests/sched.c:32
==> 00:11:03.585778 {1}      chs(<2>) at tests/sched.c:33
==> 00:11:03.585787 {2}      chs(<1>) at tests/sched.c:33
==> 00:11:03.585795 {1}      chr(<1>) at tests/sched.c:32
==> 00:11:03.585804 {2}      chr(<2>) at tests/sched.c:32
==> 00:11:03.585813 {1}      chs(<2>) at tests/sched.c:33
==> 00:11:03.585821 {2}      chs(<1>) at tests/sched.c:33
==> 00:11:03.585830 {1}      chr(<1>) at tests/sched.c:32
==> 00:11:03.585839 {2}      chr(<2>) at tests/sched.c:32
...

And if we run this in gdb, we see this goredump:
^CProgram received signal SIGINT, Interrupt.
0x000000305fae66b0 in __write_nocancel () at ../sysdeps/unix/syscall-template.S:81
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
(gdb) p goredump()

COROUTINE  state                                      current                                  created
------------------------------------------------------------------------------------------------------------------------
{0}        msleep()                                   tests/sched.c:50                         <main>
{1}        ready                                      tests/sched.c:32                         tests/sched.c:43
{2}        RUNNING                                    ---                                      tests/sched.c:44

CHANNEL  msgs/max    senders/receivers                          refs  done  created
------------------------------------------------------------------------------------------------------------------------
<1>      0/0                                                    1     no    tests/sched.c:40
<2>      0/0                                                    1     no    tests/sched.c:41

Reproduced. The problem is that poller is called only if the process would be idle otherwise. In this case, the process always has some stuff to process and poller (which handles deadlines) is never even invoked.

This the problem of behaviour under 100% cpu load. Originally, libmill didn't process file descriptor events or timeouts under such conditions. Now it checks once in a while.
Fixed.


Segmentation fault after update to ver 1.44

Issue Type: Bug
After update to ver 1.44 the remote server fails to start with the following error log.
/.vscode-server-insiders/bin/fc14315c37f3017af937270532ae2adfbdb6b45f/server.sh: line 12: 53557 Segmentation fault      "$ROOT/node" ${INSPECT:-} "$ROOT/out/vs/server/main.js" "$@"
> <<< End of server log
> c64395281831##32##

Steps to reproduce:

Let the vs code insiders auto update to ver 1.44
Connect to remote server using the remote-ssh extension
This only seems to affect some random machines since i am able to connect to other remote servers with the same vs code version

VS Code version: Code - Insiders 1.44.0-insider (fc14315c37f3017af937270532ae2adfbdb6b45f, 2020-03-25T10:51:12.912Z)
OS version: Darwin x64 19.3.0
Fetching remote diagnostics for 'SSH' failed: The VS Code Server failed to start

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
2, 3, 3

Memory (System)
16.00GB (1.87GB free)

Process Argv

Screen Reader
no

VM
0%

Fetching remote diagnostics for 'SSH' failed: The VS Code Server failed to start
Extensions: none

Can you try running the command "Kill VS Code Server on Host" so the the remote server will get reinstalled, then try connecting again and check whether you still see it?

@roblourens Yep that fixed it. I suspect this is due to a corrupt download/install on the home directory in the remote end.It didnt have enough disk space so vs code complained in the beginning of an earlier install. So i cleared up some space and the install went through. Tried remote connect and kept hitting this issue. once the "Kill vs code server on host" was issued to the remote host it fixed itself.
Apologies for the false negative and thanks for your help. I am going to close this.
[15:45:17.952] Remote extension host environment: {"SSH_AUTH_SOCK":"/run/user/868382/vscode-ssh-auth-sock-850045900"}
[15:45:17.966] ------

[15:45:18.018] [Forwarding server 51423] Got connection 1
[15:45:18.019] [Forwarding server 51423] Got connection 2
[15:45:20.264] "Update SSH_AUTH_SOCK" terminal command done


webgui

perfectly worked for me,just needed WEBGUI command line during rebbot i forgot to check
and how to increase uploading speed,basically i will be using for seeding,so is there any restriction already made in config or its set to full max?
just had one more query in my mind can i set my own plugins here?
i need file manager and check update plugins too
ur version has good plugins but missing some :)

Not sure what you mean in terms of WEBGUI command line?
There is no restriction, but you may want to optimise your rtorrent config. See this guide on the rtorrent project with regards to performance tuning - https://github.com/rakshasa/rtorrent/wiki/Performance-Tuning
Yes you can install additional plugins. Just follow the instructions that the plugin authors provide.
Just note that if you rerun rtinst main script, you will need to reinstall any additional plugins, and will lose any config changes, so if you do make significant changes to the configuration of rtorrent and/or rutorrent, make sure you backup those config files, so you can easily reapply them if needed.
Any additional programs you want to install, should not impact the installation in any way. You can add in things like Plex or OpenVPN, without any conflict.

hello u have solved my previous isssues,i m very very thankful to you
i have searched a lot on Github and google as well but i didnt get satisfactory plugin to upload files to file hostings,i need plugin of filemanager which could upload file on file hosting sites,i tried this one but its older one and has got no support as such :)
please i need guideance from your expertise,please also it will be good if u help me guiding

steps to install that plugin which has file manager support with uploading filehosting :)
as i have install your script so i m asking for plugin from here :)

Try this: https://github.com/nelu/rutorrent-thirdparty-plugins
I have not used myself so I can't comment on them beyond providing you the link.

sorry for been more spoon feed,but i couldnt figure it out how install this plugin to rutorrent,if u just mention me steps i will do that and comment back after successful installation :)

You download the plugin folder  and move it to /var/www/rutorrent/plugins.
To download the plugin use the command:
svn checkout https://github.com/nelu/rutorrent-thirdparty-plugins/trunk/filemanager
You can either do it in the rutorrent/plugins folder directly or somewhere else and move it there,
If there is anything additional beyond that to get it working properly I don't know as I have not used them myself.

thanks a lot a very very deep respect for you,u r seriously a heart winner

i had tried this but i got this log
"filemanager: Plugin will not work. Webserver user can't access external program (unzip)"
i have install directly to /var/www/rutorrent/plugins
when i start my Rtorrent i get above message
i tried changing permissions to 775 but still didnt work

Not sure. Never used it so, can't help any further, you will need to check with their support.


upgraded cjs transformer to babel-plugin-transform-cjs-system-wrapper

@jrauschenbusch thanks so much for this PR work! It's been amazing to see yourself and @asapach get involved in taking this on, it was really not expected.
@asapach do you have any feedback here at all?

LGTM

@guybedford You are welcome. The opportunity to participate to such an amazing project is thanks enough.

👍

@jrauschenbusch I've invited you to the collaborators team here. Let me know when you've joined and I will give you admin access to transfer the transformer across.

@guybedford I've joined the collaborators team. :-)

@jrauschenbusch ok you should be able to transfer the repo through now.

@jrauschenbusch this went out in the latest release. I just added a minor modification in https://github.com/systemjs/babel-plugin-transform-cjs-system-wrapper/commit/6a31c21bcc9b13c15b0f06e7bb9019299533daff.
Could you add me as an npm owner to publish the change? (npm owner add guybedford babel-plugin-transform-cjs-system-require && npm owner add guybedford babel-plugin-transform-cjs-system-wrapper).
Thanks!

@guybedford done!


Add Feedback for Cluster Registrations

Description
When using the sveltosctl register cluster command, no feedback is provided for successful operations or when the cluster is already registered. While error messages are displayed if something goes wrong, users receive no confirmation for success or pre-existing registrations. This can create confusion and lead to unnecessary manual verification.
For example, after running:
sveltosctl register cluster \
    --namespace=dev \
    --cluster=dev-01 \
    --kubeconfig=./dev-01.yml \
    --labels=environment=dev,name=dev-01

If the registration is successful or the cluster is already registered, the CLI remains silent.
Proposed Solution
Add simple, default feedback for successful and already-registered scenarios:
1. Success:
Cluster 'dev-01' successfully registered in namespace 'dev'.

2. Already Registered:
Cluster 'dev-01' is already registered in namespace 'dev'.

These messages improve user experience without requiring verbose mode.
Benefits

Clarity: Users get immediate confirmation of their actions.
Usability: Eliminates the need for manual checks post-command.
Consistency: Aligns with standard CLI behavior for feedback.

Same message will be printed in case cluster is successfully registered for the first time or updated.
sveltosctl register cluster --namespace=civo --cluster=cluster2 --kubeconfig=/Users/mgianluc/Downloads/civo-cluster2-kubeconfig  --labels=env=production
cluster cluster2 successfully registered/updated in namespace civo.


[My habit] User unable to mark habit as done from "My space" page, "My habits" tab.

Environment: macOS Monterey 12.4
Safari 15.5
Reproducible: always.
Build found: 28.07.2022
Preconditions

Be an Authorized User.
Open the "My space" page
Open the "My Habits" tab.

Steps to reproduce

Click on the "Mark as done" button.

Actual result
The "Wrong date. Should be 'LocalDate'" error message is displayed and the "Mark as done" button isn't clickable anymore.
Expected result
The system marks the habit as done on the current day only and it is replaced by a green button “Done”.
User story and test case links
E.g.: "User story #990
Test cases #3247, #3248, #3249, #3250.
Labels to be added
"Bug", "My habits", "pri: medium ", "severity:major", "Functional".

Duplication #4499


Static stylings are not applied with @kuma-ui/webpack-plugin v1.3.0

Hello,
I've encountered a static styling issue with @kuma-ui/webpack-plugin 1.3.0: static stylings are not applied.
Steps to Reproduce

Switch to branch main (now f5125562c8a2164c31346be981c1ec734245d583).
Run pnpm start

Result
At the branch main

Static styles (color and font size of the text "Hello World", padding of green boxes) are not applied.
At the tag<EMAIL_ADDRESS>(1cc40f4ed0005581e9392f34d8869b2ce5b47b32)

Static styles and dynamic styles are both applied.
Workaround
Downgrading to @kuma-ui/webpack-plugin version v1.2.7 or lower.
Best,

I have confirmed that this issue is resolved by #399.

@ygkn
Thank you for pointing that out. I have merged #399  into main and released it, so it should be working correctly now :)

I've updated Kuma UI and confirmed it works in my project. Thanks for the quick action!


macOS 13 runner / Xcode 14.3.1 UI Testing - Timed out while enabling automation mode

Description
Similar to #7621 that @erik-bershel looked at, on my macos-13 runner setting DEVELOPER_DIR to /Applications/Xcode_14.3.1.app/Contents/Developer I am getting a Timed out while enabling automation mode error:
	UI Tests-Runner (25570) encountered an error (The test runner failed to initialize for UI testing. If you believe this error represents a bug, please attach the result bundle at /Users/runner/work/Sparkle/Sparkle/build/Logs/Test/Test-UITests-2023.06.24_14-41-23-+0000.xcresult. (Underlying Error: Timed out while enabling automation mode.))
Test session results, code coverage, and logs:

This has happened twice so I don't think it's a coincidence. I have gotten macos-13 to run successfully using Xcode 15 however (at least once).
More details on the runner:
Current runner version: '2.305.0'
Operating System
  macOS
  13.4
  22F66
Runner Image
  Image: macos-13
  Version: 20230524.1
  Included Software: https://github.com/actions/runner-images/blob/macos-13/20230524.1/images/macos/macos-13-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/macos-13%2F20230524.1
Runner Image Provisioner
  <IP_ADDRESS>

Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[X] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
https://github.com/sparkle-project/Sparkle/actions/runs/5364813953/jobs/9733244971
Is it regression?
Yes, doesn't occur using macos-12 and Xcode 14.2
Expected behavior
UI tests should work with this combination (Xcode 14.3.1 and macOS 13)
Actual behavior
UI tests don't start.
Repro steps
Run macOS UI tests and have them fail

it looks like you ran on image from may because some updates got stuck on our side, should be fixed now and all the images were updated to the version which has the ui call fix enabled.

@mikhailkoliada how you solved this issue i am still facing this issue.


Update [azure-sdk-for-java<1.29.0] to fix RELEASE_7 WARNING

Tool information

Tool name: azure-sdk-for-java
Add or update? update
Desired version: <1.29.0 or latest
Approximate size:

Area for Triage:

Question, Bug, or Feature?:
Feature
Virtual environments affected

[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
I dont know if affected:
[ ] macOS 10.15
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Can this tool be installed during the build?
?
Are you willing to submit a PR?
No but it should be availibe here: https://github.com/Azure/azure-sdk-for-java
Here is the mentioned WARNING fix: https://github.com/Azure/azure-sdk-for-java/issues/1653#issuecomment-563928086

@sorryusernameisalreadytaken could you provide a bit more details, please? What pipelines are affected? I can't see preinstalled azure-sdk-for-java in Ubuntu readmes'
https://github.com/actions/virtual-environments/releases/tag/ubuntu18%2F20200217.1
https://github.com/actions/virtual-environments/releases/tag/ubuntu16%2F20200217.1

@sorryusernameisalreadytaken , Hello, as @miketimofeev mentioned, we don't pre-install any azure-sdk-for-java on our images.
But please let me know if we missed something


remove backend folder

We don't need the backend folder anymore.
Also move the frontend folder to top level

@PaulBredl  I removed backend folder but second point you mean, we don't need config assistant folder under frontend.

yes we dont need a frontend folder, can be just config-assistant

We do not want to merge now because of many merge conflicts this will create (see pull request)


Hard refresh schema metadata before checking it

@mambocab Review please, and thanks.

+1 on these changes in particular, but this whole test needs some attention, as discussed offline. @ptnapoleon did you file a bug somewhere for the points I brought up about the comments and the order of parts of the test?

Nope! Will do that though.


Using atob returns TypeError: Illegal invocation

When running code within the sval interpreter that uses window.atob or window.btoa (those are the ones I've experienced the issue with so far), I get a TypeError: Illegal invocation error.

Just fixed. Keep it open until next release.

@Siubaak thanks for the speedy implementation. When will the next release be?

@imolorhe 0.4.8 released. try it

Thanks, it works!

@Siubaak using 0.4.8, calling some window methods (including atob and btoa) directly (not through window.) throws the Illegal invocation error for me. Not sure if I could be doing something wrong - I'm using your library in a chrome extension content script.
Anyway, the following workaround works for me:
const bindings = [
  'fetch',
  'setInterval',
  'clearInterval',
  'setTimeout',
  'clearTimeout',
  'atob',
  'btoa'
]
  .map((method) => `window.${method} = window.${method}.bind(null);\n`).join('');

const createSval = (options?: SvalOptions) => {
  const interpreter = new Sval(options);
  interpreter.run(bindings);
  return interpreter;
};

Setting the this arg to null is counterintuitive, but it seems to fix the issue.
Also, not all methods are affected by the issue eg. localStorage appears to work correctly without the fix.

@Siubaak using 0.4.8, calling some window methods (including atob and btoa) directly (not through window.) throws the Illegal invocation error for me. Not sure if I could be doing something wrong - I'm using your library in a chrome extension content script.
Anyway, the following workaround works for me:
const bindings = [
  'fetch',
  'setInterval',
  'clearInterval',
  'setTimeout',
  'clearTimeout',
  'atob',
  'btoa'
]
  .map((method) => `window.${method} = window.${method}.bind(null);\n`).join('');

const createSval = (options?: SvalOptions) => {
  const interpreter = new Sval(options);
  interpreter.run(bindings);
  return interpreter;
};

Setting the this arg to null is counterintuitive, but it seems to fix the issue. Also, not all methods are affected by the issue eg. localStorage appears to work correctly without the fix.

It seems to be a bug. Please create an issue, thanks. Or, pr is welcomed, anytime. :D

any updates?


react-native run-android warning Ignoring InnerClasses attribute for an anonymous inner class

react-native -v
react-native-cli: 1.0.0
react-native: 0.35.0

DuangLink-MacBook-Pro:bizapp3 duanglink$ npm install react-native-wechat --save
<EMAIL_ADDRESS>/Users/duanglink/ReactNativeProjects/bizapp3
└─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

:app:preDexDebug
Unknown source file : warning: Ignoring InnerClasses attribute for an anonymous inner class
Unknown source file : (com.tencent.mm.sdk.openapi.WXApiImplV10$ActivityLifecycleCb$1) that doesn't come with an
Unknown source file : associated EnclosingMethod attribute. This class was probably produced by a
Unknown source file : compiler that did not target the modern .class file format. The recommended
Unknown source file : solution is to recompile the class from source, using an up-to-date compiler
Unknown source file : and without specifying any "-target" type options. The consequence of ignoring
Unknown source file : this warning is that reflective operations on this class will incorrectly
Unknown source file : indicate that it is not an inner class.
Unknown source file : warning: Ignoring InnerClasses attribute for an anonymous inner class
Unknown source file : (com.tencent.mm.sdk.openapi.WXApiImplV10$ActivityLifecycleCb$2) that doesn't come with an
Unknown source file : associated EnclosingMethod attribute. This class was probably produced by a
Unknown source file : compiler that did not target the modern .class file format. The recommended
Unknown source file : solution is to recompile the class from source, using an up-to-date compiler
Unknown source file : and without specifying any "-target" type options. The consequence of ignoring
Unknown source file : this warning is that reflective operations on this class will incorrectly
Unknown source file : indicate that it is not an inner class.
Unknown source file : warning: Ignoring InnerClasses attribute for an anonymous inner class
Unknown source file : (com.tencent.mm.sdk.b.b) that doesn't come with an
Unknown source file : associated EnclosingMethod attribute. This class was probably produced by a
Unknown source file : compiler that did not target the modern .class file format. The recommended
Unknown source file : solution is to recompile the class from source, using an up-to-date compiler
Unknown source file : and without specifying any "-target" type options. The consequence of ignoring
Unknown source file : this warning is that reflective operations on this class will incorrectly
Unknown source file : indicate that it is not an inner class.

Which tools do you use to generate the logs?

@yorkie when I run react-native run-android

Warnings is not error, thus it doesn't effect your app. And after researching the above logs, it seems to detect the WeChat SDK source problems.


Dynamically load postgres extensions

Summary of changes
If extension file is not found - request it from compute_ctl
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

Note: this PR does not contain all the extension features
In
https://github.com/neondatabase/neon/pull/4555
I plan to add:
- add more tests
  -- multiple extension.control files to download
  -- does CREATE EXTENSION actually call extension_server?
- Handle not just Shared Extensions but also other types of extensions
- libs/remote_storage/src/s3_bucket.rs // TODO: if bucket prefix is empty, folder is prefixed with a "/" I think. Is this desired?
- add env variable to github of EXT_REMOTE_STORAGE_S3_BUCKET
- add tests for extension downloading with real S3 storage

closed in favor of rebased version in https://github.com/neondatabase/neon/pull/4592


Standard Command line Args or Explanation of piping

It is confusing because in my experience most CLI interfaces use command line arguments rather than linux piping. So maybe some examples under the help flag would help
Or use standard Command line arguments, maybe a library like Command Line Args
Or an explanation of Linux piping in the documentation: [Linux Tutorial] (http://ryanstutorials.net/linuxtutorial/piping.php#introduction)

I wouldn't be against an optional file agument or a --file flag.
In terms of immediate need, would it be best just to give usage examples in README?


change edition to 2021

also removes author field as it is not displayed on crates.io anymore.

I did the same here but didn't send it as it doesn't use any 2021 specific feature or addition. A side effect is raising the MSRV. Is it a problem?

msrv is already 1.58, 2021 edition is 1.56.0

with color-eyre added, I want to transition all possible instances of format!("...{}...", thing) to format!("...{thing}...")

bors r+


Screenshots show all device form-factors. Should only show wide/narrow contextually

When creating PWA screenshots, you can define whether they are 'wide' or 'narrow'. The browser then contextually only shows the screenshots contextually relevant for your device. This library prompt shows ALL screenshots.
https://developer.mozilla.org/en-US/docs/Web/Manifest/screenshots#form_factor
https://developer.mozilla.org/en-US/docs/Web/Manifest/screenshots#platform

[ ] To investigate what rules Chrome et al use to show the right screenshot for form_factor (screen width?)
[ ] To investigate use of platform parameter as well:

Indeed, I have considered this as well. The gallery was initially created from the first versions and received no complaints, which is why I did not continue working on it.


Pretty output fails if before hook is run twice

Current behavior
If the base url is updated and is visited in a before hook, then the hook is run twice
support/e2e.ts
before(() => {
  Cypress.config('baseUrl', 'http://<IP_ADDRESS>:4000');

  cy.intercept('/waiting-page', {
    headers: { 'content-type': 'text/html' },
    statusCode: 200
  }).visit('/waiting-page');
});

result :
An error was thrown in your plugins file while executing the handler for the before:spec event.

The error we received was:

Error: Unexpected state in beforeSpecHandler: before-spec (this might be a bug, please report at https://github.com/badeball/cypress-cucumber-preprocessor)
    at createError (/home/kduret/workspace/cypress-cucumber-preprocessor/examples/webpack-ts/node_modules/.pnpm/@badeball+cypress-cucumber-preprocessor@18.0.5_pjwvil4ofno6sgsjgd5tdc3zby/node_modules/@badeball/cypress-cucumber-preprocessor/dist/helpers/error.js:9:12)
    at beforeSpecHandler (/home/kduret/workspace/cypress-cucumber-preprocessor/examples/webpack-ts/node_modules/.pnpm/@badeball+cypress-cucumber-preprocessor@18.0.5_pjwvil4ofno6sgsjgd5tdc3zby/node_modules/@badeball/cypress-cucumber-preprocessor/dist/plugin-event-handlers.js:189:43)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
 ELIFECYCLE  Command failed with exit code 1.

this seems related to https://github.com/cypress-io/cypress/issues/26300
Desired behavior
Waiting a fix on cypress, handle this case, handle this specific case in event handler
This has already been done for a similar issue : https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/lib/plugin-event-handlers.ts#L446-L450
Test code to reproduce
Issue is reproduced here : https://github.com/kduret/cypress-cucumber-preprocessor/tree/reproduce-twice-before/examples/webpack-ts
I run the test with : pnpm run cypress:run
Versions

Cypress version: 13.1.0
Preprocessor version: 18.0.5
Node version: v18.17.0

Checklist

[x] I've read the FAQ.
[x] I've read instructions for logging issues.
[x] I'm not using<EMAIL_ADDRESS>(package name has changed and it is no longer the most recent version, see #689).

What’s your reason for configuring this in the runtime?

Currently, cypress does not allow to bypass the health check of the baseUrl when it starts
But we need to start the app during the tests because we have specific cases where the webserver is not available :

fresh install of the app
upgrade of the app

I am aware of this : https://docs.cypress.io/guides/references/best-practices#Web-Servers
But it does not match our use cases

By health check, are you referring to the following warning? This isn't a warning you strictly need to pay attention to.

Indeed, I'm referring to this warning, but this is blocking when using cypress:run :
> @ cypress:run ~/cypress-cucumber-preprocessor/examples/webpack-ts
> cypress run --config-file cypress.config.ts --browser=chrome

Cypress could not verify that this server is running:

  > https://localhost:1311

We are verifying this server because it has been configured as your baseUrl.

Cypress automatically waits until your server is accessible before running tests.

We will try connecting to it 3 more times...
We will try connecting to it 2 more times...
We will try connecting to it 1 more time...

Cypress failed to verify that your server is running.

Please start this server and then run Cypress again.
 ELIFECYCLE  Command failed with exit code 1.

I've fixed this with v18.0.6.

Thanks ! ❤


🌸PR Coffee Details Screen Update

Created details screen
changes

Removed unused imports
Added Listener for Coffee Detail Button
Stopped using UUIDs in Data Models
Created Coffee Display Composable
Implemented custom ripple theme
Naviage back when icon is clicked in the coffee display composable
Added description and price rows
Code refactoring and polishing
Bug-fixes, and more fixes

looks good


withDependency mutations should be available to downstream consumers

When the DependencySet is mutated via Configuration.withDependency, these modifications should be visible to all consumers of that dependency set. This includes:

When the configuration is consumed as project dependency
When the configuration is consumed as a substituted project dependency in a composite build
When the dependencies are published to an ivy.xml file with the ivy-publish plugin
When the dependencies are published to a pom file using the maven-publish plugin

This story is closely related to #812 and #3238
This story should include documentation and release notes for withDependencies.

Test coverage added

@bigdaz What about this part?

This story should include documentation and release notes for withDependencies?


⚠ Bofrost.lu has degraded performance

In d0684ab, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1667 ms

Resolved: Bofrost.lu performance has improved in 000a378 after 17 minutes.


How can I use autopy.key

Python 3.5
linux mint
When I use "autopy.key.toggle("1",True,autopy.key.MOD_CONTROL)"
I get:
Traceback (most recent call last):
File "", line 1, in
AttributeError: module 'autopy.key' has no attribute 'MOD_CONTROL'
Then I try "autopy.key.toggle("a",True,autopy.key.Modifier.CONTROL)"
get:
Traceback (most recent call last):
File "", line 1, in
TypeError
When I use autopy.key.tap(autopy.key.Code.RETURN)
get:
Traceback (most recent call last):
File "", line 1, in
TypeError: Required argument ('modifiers') (pos 2) not found
I don't know how to use this function...
Maybe you can give me some example,thanks!

I get it!!!
autopy.key.tap(autopy.key.Code.RETURN,[])
autopy.key.tap('a', [autopy.key.Modifier.CONTROL])

I just ran into the same issue, I was expecting autopy.key.tap(autopy.key.Code.RETURN) to work but got
Traceback (most recent call last):
File "", line 1, in
TypeError: Required argument ('modifiers') (pos 2) not found
Thanks DTDwind for posting a working example. I think the docs need some updating.

@DTDwind @fl0under: where did you see this shown in the docs? It looks like it does include List[Modifier] in the signature, but maybe it would be helpful to post an example somewhere.


gateware.usb2: send ZLP when the descriptor length is a multiple of the maximum packet size.

Issue
When the descriptor length is equal to the max packet size (for example 64), and the host requests more (for example on windows the request length is 255 (0xff)), the ZLP is not correctly sent. The first 64 bytes are sent during the first IN request, and the next IN are not answered (no DATA) by the device. This causes the device to become unresponsive. See pic:

Fix
Send the ZLP. See pic:

Note: this may help for this issue as well: https://github.com/greatscottgadgets/luna/issues/163#issuecomment-1114444677. Without the need to LUNA_AVOID_BLOCKRAM

Merged, thank you!


Qdrant improve client

Opening this issue to catch the need to improve this extension, and start the thread around the improvements needed to move from the langchain4j-qdrant dependency to Quarkus client, based on comments in the initial PR

FYI @lburgazzoli @geoand @cescoffier


Tutorials on enabling DirectMode for VRGate HMD?

I've got the latest release of OSVR (v0.6-1197-g8796762), but could not find a way to enable DirectMode for VRGate HMD.
Here is my understanding of the process to support DirectMode:

Add vendor id (PNPID) to RenderManagerBase.cpp and wait for a binary release (DONE and MERGED, I suppose it should be contained in the g8796762 release)
Run EnableOSVRDirectMode.exe or EnableOSVRDirectModeAMD.exe to hide the registered display. Here is the output on my dev machine:

No VRGate in the list, is that means the VRGate PNPID is not included in this release?

Then I found this troubleshooting, and noticed there is a registry whitelist on NVIDIA cards to enable DirectMode for development, but unfortunately I couldn't find the CombinedWhitelist.reg file in anywhere from the installation directory of RenderManager 0.6.41.
I'm using NVIDIA GTX970 with driver 365.19,

whitelist_OSVR.zip
This is a file for the OSVR HDK from an older RenderManager installer.  You'll need to edit it to change SVR to the correct one for your HMD.  Know that nVidia has deprecated this whitelist feature and I don't know if it will still work on that version of the driver.  You will also need to reboot the machine after adding the entry.

Thanks for the solution, but unfortunately it's not working on this driver.
Is there anything else I can do?
A solution for both NVIDIA and AMD cards is better, cause we're cooperating with AMD and some of our contents will be running on AMD cards.

Currently, the solutions are vendor-specific.  You'll need to contact nVidia to get them to add your device to their driver white-list.  Be aware that they have stopped DirectMode support for non-HDCP-compliant HMDs on laptops and on systems with multi GPUs (and they are warning that we should support it on any display going forward).
AMD has a different approach to getting devices registered, so you should contact them as well.
On the plus side, there is an API upgrade working its way through Microsoft that should provide a vendor-independent solution.  We're tracking it and plan to release a new driver when it comes out.  At that point, the entire rendering chain should be open source, because it will be using public APIs and not vendors-specific ones.  I don't have an ETA for this, other than it was supposed to have been out last August.

In the meantime, you can add a frame of prediction to the client-side prediction interval and use the standard display mode.  Note that some displays have a frame less of latency when you drive them in portrait mode as opposed to landscape mode, so this may help as well.

It explains everything I need, thanks a lot!
I'll try the AMD approach first as we have LiquidVR available now.


Completion for build-level keys

sbt's shell provided completion only for keys that were relative to a
defined project, but didn't provide completion for keys that belong to
the build definition only.
This commit fixes this issue by defining a new kind of Parser (from
which completions are generated) which runs its input simultaneously on
distinct parsers. We now define a parser for project-level keys and
another parser for build-level keys. These two parsers are eventually
combined, and we get the completions of both parsers.
Fixes sbt/sbt#2460

Cool :)

LGTM

Notes plz

@eed3si9n I just added the notes.

Could you forward port this?

Started util side of FPORT https://github.com/sbt/util/pull/41


Using an App Service managed identity from an App Service multi-container app

Can you use an App Service managed identity from an App Service multi-container app. We are having difficulty getting that to work. See this internal question. Should it be possible?

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

ID: f57d3177-ce9e-ebfa-03a7-45beb8ca3212
Version Independent ID: a59df23d-f3ac-9809-61d3-5741e31f020a
Content: Managed identities - Azure App Service
Content Source: articles/app-service/overview-managed-identity.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@cataggar
Thanks for your feedback! We will investigate and update as appropriate.

@cataggar Thanks for reaching here! As its mentioned here, multi-container is currently in preview.
The following App Service platform features are not supported:
Authentication / Authorization
Managed Identities
CORS
Virtual network integration is not supported for Docker Compose scenarios
Docker Compose on Azure App Services currently has a limit of 4,000 characters at this time.
You can keep up to date by checking this documentation or on the App Service Team blog site.
Hope this helps.

@cataggar We will now proceed to close this thread. If there are further questions regarding this matter, please let us know. We will gladly continue the discussion.


ipv6 address cannot update correctly

Failed to update ipv6 address. I tried to update the ipv4 address and success but cannot update the ipv6 address with the same host and token.

I've noticed that it's just pulling out the wrong address and the notification says it didn't manage to update. I checked my dynv6 account and it now had my SLAAC address in the record that I had previously put in my private address.


Add temporary blending "fix" for BufferedContainer

"Regressed" from https://github.com/ppy/osu-framework/pull/3423, because blending is now handled correctly through multiple parents.
This is temporary because BufferedContainer blending is 100% messed up. It's incorrect because it's blending a pre-multiplied alpha texture as if it isn't pre-multiplied.
Over the last 3 days I've tried to get it to blend correctly, but it isn't an easy feat - premultiplying itself is theoretically very easy, but there's some weirdness going on inside the hierarchy of BufferedContainer that I need to investigate more.
For now, this restores the original behaviour prior to the PR mentioned above, in the hope that it'll be removed in a short while. This fixes the results screen.
Haven't written a test for this because there's really nothing of value to test here - it's completely incorrect.

Explanation of the OP.
The results screen is broken because it applies a subtractive blending at a parent level. Due to the previous fix, children of the BCs receive the subtractive mode and subtract from the BC's framebuffer.
This would be compounded if EffectBlending actually respected the parent's blending mode, but it only changes if you set Blending or EffectBlending on the BC itself. This is a bug:
https://github.com/ppy/osu-framework/blob/fb601acc4d8dcc2ff5b60584fe64e440ac9cb6f2/osu.Framework/Graphics/Containers/BufferedContainer.cs#L328-L334
If this were fixed, there would be another subtraction blend between the BC and the backbuffer, which I believe is what we want.
As an initial idea, I thought that we'll want BC to always pass a Mixture blending mode to its children (which is essentially what this PR achieves, assuming the blending is set on a parent), however that breaks additive blending.
My idea for BufferedContainer and Container is that they should be completely interchangeable with no visual differences, meaning since children in a Container additively blend between themselves, so should children of a BufferedContainer, if the blending is set from outside.
As for why BC blending is completely broken, here's a few examples (left: Container, the expected output, right: BufferedContainer)

blending mode / framebuffer background
mixture
additive

transparent black (default)

transparent white

transparent yellow

As you can see, it is impossible to achieve the same blending as Container, unless you set the background of the BC to 100% opaque yellow, at which point the background box itself may as well not exist. This is undesirable in pretty much all occasions for us - we never have a BC on a single-colour background like this.
With pre-multiplied blending we can achieve the following results:

mixture
additive

Here's a further example with a gradient:

blending mode / type
mixture
additive

current

pre-multiplied

As you can see, we can achieve perfect blending using pre-multiplied alpha, and best of all this doesn't break the API between Container and BufferedContainer - children are still drawn in additive blending, unlike what this PR practically does.
Code for this:
[BackgroundDependencyLoader]
private void load()
{
    Children = new Drawable[]
    {
        new Container
        {
            Anchor = Anchor.Centre,
            Origin = Anchor.Centre,
            Size = new Vector2(200),
            X = -100,
            Children = new Drawable[]
            {
                new Box
                {
                    RelativeSizeAxes = Axes.Both,
                    Colour = ColourInfo.GradientVertical(Color4.Yellow, Color4.Blue)
                },
                new Container
                {
                    RelativeSizeAxes = Axes.Both,
                    Blending = BlendingParameters.Additive,
                    Children = new Drawable[]
                    {
                        new Box
                        {
                            Anchor = Anchor.Centre,
                            Origin = Anchor.Centre,
                            RelativeSizeAxes = Axes.Both,
                            Size = new Vector2(0.5f, 1),
                            Colour = Color4.Cyan,
                            Alpha = 0.5f,
                        },
                        new Box
                        {
                            Anchor = Anchor.Centre,
                            Origin = Anchor.Centre,
                            RelativeSizeAxes = Axes.Both,
                            Size = new Vector2(0.25f, 1),
                            Colour = Color4.Magenta,
                            Alpha = 0.5f
                        }
                    }
                }
            }
        },
        new Container
        {
            Anchor = Anchor.Centre,
            Origin = Anchor.Centre,
            Size = new Vector2(200),
            X = 100,
            Children = new Drawable[]
            {
                new Box
                {
                    RelativeSizeAxes = Axes.Both,
                    Colour = ColourInfo.GradientVertical(Color4.Yellow, Color4.Blue)
                },
                new BufferedContainer
                {
                    RelativeSizeAxes = Axes.Both,
                    // Required if not doing the blending tricks below.
                    // BackgroundColour = Color4.Yellow.Opacity(0),
                    // Blending = BlendingParameters.Additive,

                    // // Disable the blending tricks if using the above.
                    // // Use premultiplied alpha to draw to the screen
                    EffectBlending = new BlendingParameters
                    {
                        Source = BlendingType.One,

                        // Additive
                        Destination = BlendingType.One,
                        // Mixture
                        // Destination = BlendingType.OneMinusSrcAlpha,
                    },
                    // Set non-premultiplied alpha for children
                    Blending = new BlendingParameters
                    {
                        Source = BlendingType.SrcAlpha,

                        // Additive
                        Destination = BlendingType.One,
                        // Mixture
                        // Destination = BlendingType.OneMinusSrcAlpha

                        // The defaults are incorrect here
                        SourceAlpha = BlendingType.One,
                        DestinationAlpha = BlendingType.OneMinusSrcAlpha
                    },
                    Children = new Drawable[]
                    {
                        new Box
                        {
                            Anchor = Anchor.Centre,
                            Origin = Anchor.Centre,
                            RelativeSizeAxes = Axes.Both,
                            Size = new Vector2(0.5f, 1),
                            Colour = Color4.Cyan,
                            Alpha = 0.5f,
                        },
                        new Box
                        {
                            Anchor = Anchor.Centre,
                            Origin = Anchor.Centre,
                            RelativeSizeAxes = Axes.Both,
                            Size = new Vector2(0.25f, 1),
                            Colour = Color4.Magenta,
                            Alpha = 0.5f,
                        }
                    }
                }
            }
        }
    };
}


[Bug]-[200]:The CRUD operation is failing in snowflake datasource

Description
[What happened]When there are 2 columns in the table and the user perform the crud operation then the insert, delete and update operations are failing
Steps to reproduce the behaviour:

Important Details

Version: [Cloud ]
OS: [MacOS]
Browser [ chrome]
Environment  release

@RakshaKShetty can we check if this is resolved in release environment?

@RakshaKShetty can we please check if this has been resolved?

Stats

Stat
Values

Reach
50

Effort (months)
0.5

@RakshaKShetty can you please check this once more as we have updated the templates to include the JSON forms

Closing this as haven't seen any activity recently, please reopen if this is still pending


Release notes for 1.4.0

Release time
2021-08-16
Components involved

ClickHouse

Check list
Enhancement

[x] Support migrate data
[x] Support for building Log engine tables
[x] Support display Track DDL
[x] Support the Track input box to obtain the focus display
[x] Supports Windows system construction
[x] Support track query execution thread
[x] Support data source query times to be displayed on the dashboard
[x] Add query link tracing visualization
[x] Support multiple query windows
 issues-12
[x] Supports obtaining the occupied space of columns throug… …
[x] Supports data source modification
[x] Support display table usage when the database is selected
[x] Support service nodes to display database disk usage
[x] Support service nodes to display disk usage
[x] Support Data construction of left tree menu issues-20
[x] Supports the monitoring of mutations operation

Optimize

[x] Support the mutation consumption duration
[x] Optimized README.md

UI

[x] Set the default maximized window

Bug

[x] Fix metadata selection library table causing data rendering errors

CI

[x] Add auto release version CI script

Released


cacheable inside() call with extents

This could be a good speed improvement for cases with tons of points and tons of polygons - instead of doing o(n) wrt the number of vertices in the polygon, you'd have a constant-time "is this in an extent" call first

Nah, use rbush.


Apply UI linting to all modules

Body
The following modules need to be included into the UI linting:

[x] cypress https://github.com/apache/streampipes/pull/891
[x] deployment https://github.com/apache/streampipes/pull/920
[x] projects https://github.com/apache/streampipes/pull/1012
[x] src/app/_enums https://github.com/apache/streampipes/pull/1020
[x] src/app/_guards https://github.com/apache/streampipes/pull/1020
[x] src/app/_models https://github.com/apache/streampipes/pull/1020
[x] src/app/add https://github.com/apache/streampipes/pull/1021
[x] src/app/apidocs https://github.com/apache/streampipes/pull/1021
[x] src/app/app-asset-monitoring https://github.com/apache/streampipes/pull/1021
[x] src/app/app-overview https://github.com/apache/streampipes/pull/1021
[x] src/app/assets https://github.com/apache/streampipes/pull/1021
[x] src/app/configuration https://github.com/apache/streampipes/pull/1037
[x] src/app/connect https://github.com/apache/streampipes/pull/1059
[ ] src/app/core
[ ] src/app/core-model
[ ] src/app/core-services
[ ] src/app/core-ui
[ ] src/app/CustomMaterial
[ ] src/app/dashboard
[ ] src/app/data-explorer
[ ] src/app/editor
[ ] src/app/files
[ ] src/app/info
[ ] src/app/login
[ ] src/app/notifications
[ ] src/app/NS
[x] src/app/pipeline-details https://github.com/apache/streampipes/pull/1064
[x] src/app/pipelines https://github.com/apache/streampipes/pull/1054
[x] src/app/profile https://github.com/apache/streampipes/pull/1055
[x] src/app/services https://github.com/apache/streampipes/pull/1056
[x] src/scss https://github.com/apache/streampipes/pull/1053

Please update ui/.eslintignore and ui/.prettierignore if a module is updated.
Furthermore check to corresponding module in the list above and paste a link to the PR (see #820).
Mentoring
As this ticket is marked as good first issue: one of @dominikriemer, @tenthe, @smlabt  or @bossenti is happy to provide help for getting started, just tag (one of) them if you want to start working on this issue and need some help.
StreamPipes Committer

[X] I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.

Hey, I'm new to contributing to open source and I'm interested in contributing to this issue. How can I get started with it?

Hi @aamirshaikh7,
welcome to StreamPipes, great to hear that you want to contribute 🎉
This issue depends on #876 and therefore it's preferable to have this PR merged before starting to work on this issue.
I expect this to happen in the upcoming days.
Nevertheless, I'll give a quick wrap up what to do:

Choose one of the UI models listed above and remove them from ui/.eslintignore and ui/.prettierignore locally
Run the UI commit hook like described in the README
Fix the detected issues automatically (see README) or by hand
create a PR with your changes

In case you already want to contribute, feel free to have a look on our other issues.
There are some more good first issues.
If you are interested in UI development, you could for example have a look in #793

Hi, @bossenti
I have few questions.
Do all models mentioned above needs to be removed from ui/.eslintignore and ui/.prettierignore?
Regarding the README, It is mentioned that "node and npm (bundled with node) installed.", meaning both Node and npm need to be installed? I have installed Node and npm via nvm. Will this work?
Thankyou.

Do all models mentioned above needs to be removed from ui/.eslintignore and ui/.prettierignore?

Not at once but in the end, yes. The idea is to remove them step by step. So in best case you only remove one module from both files, run the tools and check where things need to adapted.
You can provide one PR per module or group more modules in one but please ensure that PRs don't get to big.

Regarding the README, It is mentioned that "node and npm (bundled with node) installed.", meaning both Node and npm need to be installed? I have installed Node and npm via nvm. Will this work?

Shouldn't be a problem, afaik

I have removed Cypress model from .eslintignore and .prettierignore.
I'm using Node v19.3.0 and npm version 9.2.0
npm install --legacy-peer-deps
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Redundant dependency in your project.
npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated. Please see https://blog.angular.io/modern-css-in-angular-layouts-4a259dca9127

><EMAIL_ADDRESS>prepare
> cd ../ && husky install ./ui/.husky

husky - Git hooks installed

added 2289 packages, and audited 2290 packages in 7m

258 packages are looking for funding
  run `npm fund` for details

14 vulnerabilities (1 moderate, 13 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

npm run build
><EMAIL_ADDRESS>build
> node ./deployment/prebuild.js && set NODE_OPTIONS=--max-old-space-size=8192 && npm run build-libraries && ng build --configuration production

Pre-Build started.
No build config specified. Using default config for dev.
Active Angular Module: spPipelines
Active Angular Module: spConnect
Active Angular Module: spDashboard
Active Angular Module: spDataExplorer
Active Angular Module: spAppOverview
Active Angular Module: spAdd
Active Angular Module: spAssets
Active Angular Module: spFiles
Active Angular Module: spConfiguration
Moved: logo.png
Moved: sp-logo-navigation.png
Moved: favicon
Moved: theme file
Moved: webpack dev config
Pre-Build finished.

><EMAIL_ADDRESS>build-libraries
> npm run build-libs && npm run install-libs

><EMAIL_ADDRESS>build-libs
> ng build @streampipes/platform-services && ng build @streampipes/shared-ui

Node.js version v19.3.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production. For more information, please see https://nodejs.org/en/about/releases/.
Building Angular Package

------------------------------------------------------------------------------
Building entry point '@streampipes/platform-services'
------------------------------------------------------------------------------
✔ Compiling with Angular sources in Ivy partial compilation mode.
✔ Generating FESM2020
✔ Generating FESM2015
✔ Copying assets
ℹ Removing devDependencies section in package.json.
✔ Writing package manifest
✔ Built @streampipes/platform-services

------------------------------------------------------------------------------
Built Angular Package
 - from: D:\root\Code\Open source\streampipes\ui\projects\streampipes\platform-services
 - to:   D:\root\Code\Open source\streampipes\ui\dist\streampipes\platform-services
------------------------------------------------------------------------------

Build at: 2022-12-23T14:17:14.951Z - Time: 14062ms

Node.js version v19.3.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production. For more information, please see https://nodejs.org/en/about/releases/.
Building Angular Package

------------------------------------------------------------------------------
Building entry point '@streampipes/shared-ui'
------------------------------------------------------------------------------
✔ Compiling with Angular sources in Ivy partial compilation mode.
✔ Generating FESM2020
✔ Generating FESM2015
✔ Copying assets
✔ Writing package manifest
✔ Built @streampipes/shared-ui

------------------------------------------------------------------------------
Built Angular Package
 - from: D:\root\Code\Open source\streampipes\ui\projects\streampipes\shared-ui
 - to:   D:\root\Code\Open source\streampipes\ui\dist\streampipes\shared-ui
------------------------------------------------------------------------------

Build at: 2022-12-23T14:17:22.767Z - Time: 5848ms

><EMAIL_ADDRESS>install-libs
> npm install @streampipes/platform-services@file:./dist/streampipes/platform-services @streampipes/shared-ui@file:./dist/streampipes/shared-ui --no-save

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/rxjs
npm WARN   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/@angular-architects/module-federation
npm WARN<EMAIL_ADDRESS>from the root project
npm WARN   18 more (@angular/cdk, @angular/common, @angular/core, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/rxjs-for-await
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/@nrwl/tao
npm WARN
npm WARN Conflicting peer dependency<EMAIL_ADDRESS>npm WARN node_modules/rxjs
npm WARN   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/rxjs-for-await
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN     node_modules/@nrwl/tao

added 2 packages, removed 1 package, and audited 2292 packages in 14s

258 packages are looking for funding
  run `npm fund` for details

15 vulnerabilities (2 moderate, 13 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
Node.js version v19.3.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production. For more information, please see https://nodejs.org/en/about/releases/.
⠙ Generating browser application bundles (phase: setup)...Processing legacy "View Engine" libraries:
- @ngx-loading-bar/core [es2015/esm2015] (https://github.com/aitboudad/ngx-loading-bar.git)
- @auth0/angular-jwt [es2015/esm2015] (git+https://github.com/auth0/angular2-jwt)
- angular-plotly.js [es2015/esm2015] ()
- ngx-color-picker [es2015/esm2015] ()
- ngx-showdown [es2015/esm2015] (https://github.com/yisraelx/ngx-showdown.git)
- @circlon/angular-tree-component [es2015/esm2015] (https://github.com/CirclonGroup/angular-tree-component.git)
- @asymmetrik/ngx-leaflet [module/esm5] (https://github.com/Asymmetrik/ngx-leaflet.git)
- @ngx-loading-bar/http-client [es2015/esm2015] (https://github.com/aitboudad/ngx-loading-bar.git)
Encourage the library authors to publish an Ivy distribution.
✔ Browser application bundle generation complete.
✔ Copying assets complete.
✔ Index html generation complete.

Initial Chunk Files           | Names         |  Raw Size | Estimated Transfer Size
main.4de047acc166de96.js      | main          |   7.13 MB |                 1.39 MB
scripts.c43a350a022f7435.js   | scripts       |   4.13 MB |                 1.01 MB
polyfills.8c9bd5b96c65f0c3.js | polyfills     |   1.56 MB |               304.64 kB
styles.f37f3afe7ea647ab.css   | styles        | 500.39 kB |                56.69 kB
runtime.ce57a00b859f65f6.js   | runtime       |  18.28 kB |                 4.27 kB

                              | Initial Total |  13.33 MB |                 2.76 MB

Lazy Chunk Files              | Names         |  Raw Size | Estimated Transfer Size
918.23e0dc1248177c8f.js       | echarts       | 628.87 kB |               166.30 kB
971.db6f19931fcef8ad.js       | quill         | 209.60 kB |                42.15 kB

Build at: 2022-12-23T14:20:40.919Z - Hash: b8f17da653c3c71a - Time: 169766ms

Warning: D:\root\Code\Open<EMAIL_ADDRESS>depends on 'leaflet'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open<EMAIL_ADDRESS>depends on 'rfdc'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\ngx-quill\fesm2020\ngx-quill.mjs depends on 'quill'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\ngx-showdown\__ivy_ngcc__\fesm2015\ngx-showdown.js depends on 'showdown'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\react-redux\es\components\connectAdvanced.js depends on 'hoist-non-react-statics'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-client\es\specmap\helpers.js depends on 'traverse'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on '@babel/runtime-corejs3/regenerator'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on '@braintree/sanitize-url'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'base64-js'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'classnames'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'css.escape'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'dompurify'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'ieee754'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'immutable'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'js-file-download'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'prop-types'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'randexp'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'react-copy-to-clipboard'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'react-debounce-input'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'react-immutable-proptypes'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'redux-immutable'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'serialize-error'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'url-parse'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'xml-but-prettier'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\node_modules\swagger-ui\dist\swagger-ui-es-bundle-core.js depends on 'zenscroll'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\src\app\connect\components\adapter-configuration\schema-editor\event-schema\event-schema.component.ts depends on 'angular2-uuid'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\src\app\core-ui\image\services\BrushLabeling.service.ts depends on 'konva'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\src\app\core-ui\static-properties\static-code-input\static-code-input.component.ts depends on 'jshint'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\src\app\editor\services\pipeline-positioning.service.ts depends on 'dagre'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: D:\root\Code\Open source\streampipes\ui\src\app\pipelines\pipelines.component.ts depends on 'file-saver'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:6059:16:
      6059 │ .swagger-ui .cf{*zoom:1}
           ╵                 ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:7864:2:
      7864 │   *zoom: 1;
           ╵   ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:7908:2:
      7908 │   *display: inline;
           ╵   ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:7910:2:
      7910 │   *vertical-align: auto;
           ╵   ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:7911:2:
      7911 │   *zoom: 1;
           ╵   ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:8053:2:
      8053 │   *zoom: 1;
           ╵   ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:8150:2:
      8150 │   *display: inline;
           ╵   ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:8152:2:
      8152 │   *vertical-align: auto;
           ╵   ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:8153:2:
      8153 │   *zoom: 1;
           ╵   ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:14008:2:
      14008 │   *border-right-width: 2px;
            ╵   ^

Warning: ▲ [WARNING] Expected identifier but found "*" [css-syntax-error]

    styles.cb03237a769a8a20.css:14009:2:
      14009 │   *border-bottom-width: 2px;
            ╵   ^

I can see getting few warning messages while building the project, haven't come across any errors.

@smlabt can you help out here?
Frankly, I'm not really familiar with the UI stack 🤠

@bossenti yes, sure :) @aamirshaikh7 you have to use npm run format and npm run lint now to get the respective errors and warnings.

I encountered error while running npm run format. So, I followed the README and I ran npm run format:fix
After that both run format and run lint passed.
npm run format
><EMAIL_ADDRESS>format
> prettier --check .

Checking formatting...
All matched files use Prettier code style!

npm run lint
><EMAIL_ADDRESS>lint
> ng lint

Node.js version v19.3.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production. For more information, please see https://nodejs.org/en/about/releases/.

Linting "app"...

All files pass linting.

@bossenti @smlabt If you're satisfied with these results. Can I make PR for this module (Cypress) ? You can review it.

@aamirshaikh7 great, sounds good! Yes, please open a PR for this module.

@smlabt On committing the changes, I'm getting an error.
error: cannot spawn ui/.husky/pre-commit: No such file or directory

Unfortunately I do not have a windows machine to reproduce and debug this issue right now.  Then please try to run it from the project root.
 This will skip the pre-commit hook. I will than have a look into this later.

I'm running git commit from project root only, but still getting the same error.
I have used git commit with --no-verify. It worked.

Can I make PR for this module? @smlabt You can review it.

Yes, please open a PR for your changes :)

I have been performing UI linting and formatting for configuration module.
Upon performing linting, I came a warning and few errors.
Warning:
D:\root\Code\Open source\streampipes\ui\src\app\app-asset-monitoring\dialog\add-pipeline\add-pipeline-dialog.component.ts
  78:5  warning  Lifecycle interface 'OnInit' should be implemented for method 'ngOnInit'. (https://angular.io/styleguide#style-09-01)  @angular-eslint/use-lifecycle-interface

I fixed the above warning by implementing OnInit interface on AddPipelineDialogComponent.
export class AddPipelineDialogComponent implements OnInit
That fixed the warning.
Also I came across few errors which occurs in multiple files and I'll be listing them below:
D:\root\Code\Open source\streampipes\ui\src\app\configuration\consul-configs\consul-configs.component.html
  37:51  error  Expected `===` but received `==`  @angular-eslint/template/eqeqeq

For the above error, I have replaced "==" with "===", for all the respected files, and that fixed the error.
D:\root\Code\Open source\streampipes\ui\src\app\configuration\consul-configs-boolean\consul-configs-boolean.component.ts
  24:15  error  The selector should start with one of these prefixes: "sp" (https://angular.io/guide/styleguide#style-02-07)  @angular-eslint/component-selector

I'm not sure how to fix the above error. I have tried searching for the solution. I Couldn't find anything.
D:\root\Code\Open source\streampipes\ui\src\app\configuration\export\import-dialog\data-import-dialog.component.ts
  49:5  error  Lifecycle methods should not be empty  @angular-eslint/no-empty-lifecycle-method

Also, I'm not sure about the above error, I came across a solution which stated that we need to modify ".eslintrc.json" file to exclude the rule from the linter.

Your suggestions look just fine, I've applied the same ones in some cases already.
Regarding the last one, I've just deleted the OnInit() lifecycle from the code of the affected components in my last PR.
That should be fine if we don't use it.
Or are there any objections @tenthe @dominikriemer @smlabt?

Hello 👋 Any suggestions for the above? @tenthe @dominikriemer @smlabt

Hi @aamirxshaikh, your suggestions looks good to me too.
Regarding the last point, I agree with @bossenti. You can remove such empty methods.
In general, we should add implements when a component implements a lifecycle hook. If the method is empty, we can safely delete it.
@aamirxshaikh here is a link to Angular documentation that explains lifecycle hooks link
Does the answer help you or do you have any unanswered questions?
Thanks for your detailed descriptions 👌

I have been performing UI linting and formatting for the core module, and I have a few questions.
Upon performing linting, I came across a few errors.
Error:
authenticated: boolean = true;
streampipes\ui\src\app\core\components\base-navigation.component.ts
  28:5  error  Type boolean trivially inferred from a boolean literal, remove type annotation  @typescript-eslint/no-inferrable-types

For the above error, we need to remove either boolean or true. My question is, which one should we remove?
Error:
selector: 'iconbar', or streampipes or toolbar
streampipes\ui\src\app\core\components\iconbar\iconbar.component.ts
  30:15  error  The selector should be kebab-case (https://angular.io/guide/styleguide#style-05-02)  @angular-eslint/component-selector

For the above error, the selector should be in kebab-case, which means that it should use all lowercase letters and separate words with a hyphen. Also, we have to apply the sp prefix, and after, it would look like this: sp-icon-bar
The component would be like this:
@Component({
    selector: 'sp-icon-bar',
    templateUrl: './iconbar.component.html',
    styleUrls: ['./iconbar.component.scss'],
})

My question is: After applying kebab-case and sp prefix to the selector, shouldn't we also apply the kebab-case to templateUrl and styleUrls or is it not required?
like:
@Component({
    selector: 'sp-tool-bar',
    templateUrl: './tool-bar.component.html',
    styleUrls: ['./tool-bar.component.scss'],
})

Hi @aamirxshaikh,
for the first error please remove the boolean type annotation, so I think authenticated = true is fine.
For the second error I think we can use sp-iconbar, so we do not have to change any filenames.  I have looked up the toolbar and in most cases this is spelled without a hyphen.

Thanks for the suggestions, @smlabt.

We have completed the linting and formatting for our UI 🎉
Thanks a lot for everyone involved @aamirxshaikh @tenthe @smlabt @dominikriemer
Great team effort 🤩


FedX cannot handle large joins with > 65k intermediate result

In the concurrency facilities of FedX we make use of the Java Phaser.
This is limited to 65535 registered parties.
In case of large joins we were seeing errors that the the phaser has reached limits.
Example trace
Caused by: java.lang.IllegalStateException: Attempt to register more than 65535 parties for java.util.concurrent.Phaser@3ab90002[phase = 0 parties = 65535 arrived = 0]

	at java.base/java.util.concurrent.Phaser.doRegister(Phaser.java:429)

	at java.base/java.util.concurrent.Phaser.register(Phaser.java:581)

	at org.eclipse.rdf4j.federated.evaluation.join.ControlledWorkerLeftJoin.handleBindings(ControlledWorkerLeftJoin.java:61)

	at org.eclipse.rdf4j.federated.evaluation.join.JoinExecutorBase.performExecution(JoinExecutorBase.java:51)

@jeenbroekstra I have a fix for this locally and will prepare a PR. Should this go as a bugfix for 3.7.x targeted to the master branch?


How to setup wercker.yml for none Ruby boxes?

Hello guys! I'm developing node.js application and using node.js box. And would like to connect this step to push notification to slack. But got such error:

You need to use a box that installed ruby

oh, it was very easy: http://devcenter.wercker.com/docs/steps/install-packages.html
just define:
- install-packages:
        packages: ruby

Thank you for the valuable information :+1:
I add the information in README :)

FYI, this is NOT in the README, I had a hard time figuring it out for a node box


Config Sync issue

config.json is not usable after sync with config.yaml

fixed with [dev0.2.5] - 2023-12-14


[FEATURE REQUEST] Manage

Is your feature request related to a problem? Please describe.
I'm currently using OIIO to generate Big geotiffs (larger than 4GBytes).
I get difficulties to manage custom Tiif tags TIFFTAG_GEOTIEPOINTS, TIFFTAG_GEOPIXELSCALE)  which don't seem to be a part of exif tags.
Moreover, previous code which allowed to write geotiff files used the method GTIFSetFromProj4 from Geotiff lib.
This method allows to update tiff tags according Proj4 projection.
Do you know if there is an elegant way to write such Geotiffs files using OIIO ?
I tried to firstly write the tiff using OIIO then update the header using GeoTiff lib but It doesn't seem to work.
Any idea ?
Describe the solution you'd like
A perfect solution would be to allow OIIO to manage as well tiff as geotiff format (using libtiff and geotiff)

I'm not sure hot to do this now, those tags aren't among those that we know about. Somebody would need to add proper GeoTIFF support. I don't have the time to do it, but I would gladly accept a PR that implemented this.


Is there a way to clear the history of the store?

I've tried using the pinia methods: $dispatch, $reset, but the history is not cleared.
Is there a method that allows you to clear the history and start saving the states from that point onwards?

Very sorry for the late reply. Please update to the latest and use the resetStack method for now:
store.$reset()
store.resetStack()


Port to Java 17/Jakarta

Port to Java 17/Jakarta

https://github.com/swedenconnect/ca-engine/pull/43


add x-account-id header

Experimenting adding x-account-id header addressed in the newrelic-client-go issue. https://github.com/newrelic/newrelic-client-go/issues/697
Hopefully pave a way to address this terraform-provider-newrelic issue

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing and moving work to https://github.com/newrelic/newrelic-client-go/pull/854


Question about Table 4 in paper (2D-3D-S dataset)

Hi there,
I am curious about the results in Table 4.
First, which experiment is performed here? As I understand from Sec.5 (Experiments) it is semantic segmentation, i.e. for each point you predict a semantic label (one out of N classes, here N=13 for 2D-3D Stanford http://buildingparser.stanford.edu/images/3Dmodal.png while clutter was not evaluated).
Second, I am wondering how you compute the AP? For semantic segmentation, the mean Intersection-over-Union (IoU) is more common. In fact, the AP is often used when reporting instance segmentation scores. The scores from the other methods [2, 17, 28] in Table 4 are all referring to instance segmentation, not semantic segmentation (which brings me back to the first question).
Assuming you are not comparing your semantic segmentation results to the much harder task of instance segmentation, how do you perform instance segmentation? The paper does not give an information on this, while Fig. 6 shows qualitative results only for semantic segmentation task, not instance segmentation.

Thanks for the feedback. However, we want to keep the github issues for the implementation details only. But we are open to discuss your point via email or skype/phone in depth.

Thanks for your reply avodo.
Please feel free to contact me at<EMAIL_ADDRESS>


Enhancement/code prettify

UI enhancement for  story example code.

Add new component <Code />to place source code.
enable syntax highlight when switching stories.
set background color for code block

screen shot below


chore: bump dockerfile base image to ubuntu:22.04

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

fix: #213. chore: bump dockerfile base image to ubuntu:22.04

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 72.318%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
4611

Relevant Lines:
6376

💛  - Coveralls


Web share component doesn't load

On firefox/ubuntu, expected buttons to share an url and a file don't appear in the page.

This is the expected behaviour... You can see in the tabs notes: "Your browser must support web share."