Reporter Instant App Beta reqiurements

Eligibility of webmap

[ ] At least one editable layer must be present.

Load map using the Configuration

[ ]  Use the selected webmap and load the map
[ ]   Get the configured layers list
[ ]   Map Accessibility – (Alt + text access).
[ ]   Support legend (Configuration turn on/off)

Layer list

[ ] Show all/Configured editable layers of the selected webmap on load
[ ] Select reporting layers For Beta, all the editable layers will be selected by default.
[ ] Show feature count for that layer.
[ ] Message when selected webmap has any editable feature layer due to change in layer property after webmap is added in the app, a message will appear in the config and launched app.
[ ] Layers will be shown in the same order as in webmap
[ ] The user can select the layer and will be navigated to the features list of that layer

Feature list

[ ] Show all features in a layer
[ ] Message when no features present in a layer
[ ] Features list will be shown using the popup titles.
[ ] Features will be sorted in reverse order of object ID so that the latest report will be shown at the top.
[ ] When clicking on any of the features in the list user will be navigated to the Feature Details.

Feature Edit Form (Only to create new features)

[ ] Reports header will be shown using the text from the configuration
[ ] Contents of the feature form can be controlled using the form configuration(popup) in the webmap

Feature Details

[ ]  When any feature selected from the map shows the feature details in the sidebar
[ ] When a user clicks on any features in the Feature List show the feature details in the sidebar
[ ]  When a user clicks 'Like' (thumbs up) button, update and display the count. The field name for each layer is configured to store the count. (Not in Beta)
[ ] When a user clicks 'Dislike' (thumbs down) button, update and display the count. The field name for each layer is configured to store the count. (Not in Beta)

Submit reports

[ ] Submit button will be present in the following cases (if the disable new reports option is not selected in the configuration
In the Layers List:
[ ] On clicking Submit report from Layers List, the User will be shown the list of all possible editable layers and after selecting the layer from the list, the user will be navigated to the Feature form of that layer to add a new feature.
[ ] Within a particular layer – On clicking Submit report from the features list, the user will be automatically navigated to the
feature form of that layer to add a new feature
[ ] When the user clicks Share button, they're able to share using the available options.

Configuration for Submit report button

[ ] Report button text
[ ] Disable new reports
[ ] Report submitted message

@sumitzarkar

We'd like both Mobile and desktop versions for beta.
Search widget in editing form and the like/dislike features are moved to V2.

@jmhauck @skrishn
Issues with map-card component
The requirement for the CSR is to provide the map tools (Search and legend) without collapsible as given below

If the enableMapToolsExpand property is set to false we can see the tools without collapsible

However, after clicking on any of the Search/Legend tool the widget is opened in the right top instead of opening on the left
Aslo, the tools get hidden once any widget is opened we don't see option to open other widget or close the existing opened  widget

If the enableMapToolsExpand property is true we can see the tools with collapsible

However, after clicking on the Search or Legend tool it opens to the Upper right corner and the tools get collapsed.
With this configuration we get the opton to open other tool or close the existing if we againg click on the expand collapse icon.

Here is the configurtion we are passing to map-card component
 <map-card
          class="width-full"
          defaultWebmapId={this.defaultWebmap}
          enableBasemap={false}
          enableFloorFilter={false}
          enableFullscreen={false}
          enableHome={this.enableHome}
          enableLegend={true}
          enableMapToolsExpand={true}
          enableSearch={this.enableSearch}
          hidden={false}
          homeZoomIndex={0}
          homeZoomPosition={"top-left"}
          homeZoomToolsSize={"s"}
          mapInfos={this.mapInfos?.filter(mapInfo => mapInfo.visible !== false)}
          mapWidgetsIndex={this.enableHome ? 4 : 3}
          mapWidgetsPosition={"top-left"}
          mapWidgetsSize={"s"}
          stackTools={false}
          theme={this.theme}
          toolOrder={["search", "legend", "fullscreen", "basemap", "floorfilter"]}
        />

Could you please check and let us know your thoughts on this

@sumitzarkar  I changed enableMapToolsExpand to enableSingleExpand.
When this value is true it will support the needs of Manager and the tools will be loaded into a single Expand. When it's false each tool that makes sense to load in an individual Expand will do so.

@jmhauck
Thanks for the update, now it is working as expected.


Add selecting tags on the compare page

Related to #3780, #1352, #12251.
On the /compare page, before you could only select branches in the UI in order to make a pull request.  This PR makes it so you can also select tags to compare them.  The comparison already exists; this just provides an easier UI for navigating to those comparison pages.
When branches are selected and you have permission to create a pull request, the display hasn't changed.

When a tag is selected for either base or head, the display changes to comparing.

This is the dropdown, with both branches and tags, which now matches the dropdown on other pages.

Review
For easier reviewing, I made a separate commit that changes indentation.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@ab77a24). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main   #15723   +/-   ##
=======================================
  Coverage        ?   43.80%
=======================================
  Files           ?      678
  Lines           ?    81897
  Branches        ?        0
=======================================
  Hits            ?    35874
  Misses          ?    40187
  Partials        ?     5836

Continue to review full report at Codecov.

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


Change schedule command with empty tasks to resume

Now tasks are resumed instead of started over when schedule tasks are empty.

Make sense, thx


Add configure-python step to run_infrastructure.py Make jobs

Purpose
@adriaaaa and @conceptualshark both ran into an issue earlier when running make quickstart where virtualenv was not installed (see: https://ethyca.slack.com/archives/C029HFVSC8L/p1646935020342749). We need to be sure that the Python environment is consistent for any Make commands that will invoke run_infrastructure.py
Changes

Adds configure-python PHONY dep. to be called before any Make jobs that use run_infrastructure.py so that we can be sure the Python environment includes virtualenv

Closing this to change tack here.


MM-33335  Use CurrentStatus as source of truth.

Summary
Since we are unable to distinguish between the cases of a brand new incident and a migrated incident with no status updates, the method of using status updates as the source of truth for current status is not viable. So to support the migration case I have simplified and now use the CurrentStatus field in the incident as the source of truth.
Ticket Link
https://mattermost.atlassian.net/browse/MM-33335

@crspeller, leaving you to merge and handle any release branches necessary.


Adds improved default auth to Milvus

Updates Milvus hosting to leverage dynamically generated default password if none provided (similar to other resources) and resulting cascading changes + tests.
Updates tags for contianer image that support setting auth

Description
Milvus added the ability to set the root password. This change adapts to that and follows similar pattern to other config-based auth (e.g., MySql is a good analog). This requires the support of a minimum new Milvus version (2.4.7).
Fixes #4966
Checklist

Is this feature complete?

[ ] Yes. Ready to ship.
[x] No. Follow-up changes expected. - haven't seen a pattern where we've made a change that requires a specific new resource version

Are you including unit tests for the changes and scenario tests if relevant?

[x] Yes
[ ] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[x] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[x] No - follows same pattern as existing pattern/resources

[ ] No

Does the change require an update in our Aspire docs?

[x] Yes

Link to aspire-docs issue: dotnet/docs-aspire#1475

[ ] No

Microsoft Reviewers: Open in CodeFlow

@eerhardt had to redo the PR (my branch was way stale).  Addressed your prior feedback.
Review: this does change resource and enables a null param were there wasn't before. Not sure if we've made a similiar change there -- seeking feedback on desired correct way here.

Review: this does change resource and enables a null param were there wasn't before. Not sure if we've made a similiar change there -- seeking feedback on desired correct way here.

I believe you did it correctly. 👍

Would this allow adding Milvus playground app to the tests like in https://github.com/dotnet/aspire/pull/5244 ? When I had tried it earlier on main it was failing with Parameter resource could not be used because configuration key 'Parameters:milvusauth' is missing and the Parameter has no default value..

Any other feedback @eerhardt?


fix: remove prettier indent from all-contributors file

Seems all-contributors follows a strict no-indent rule. So I removed every indent made by prettier.

Hopefully, this works.

And it did! 🎉


[Feature request] Add support for syncing with Nextcloud News

Newsbeuter version (copy from newsbeuter -v):
newsbeuter 2.9 - http://www.newsbeuter.org/
Copyright (C) 2006-2010 Andreas Krennmair

newsbeuter is free software and licensed under the MIT/X Consortium License.
Type `newsbeuter -vv' for more information.

Compilation date/time: Mar  8 2017 21:56:57
System: Linux 4.11.3-1-ARCH (x86_64)
Compiler: g++ 6.3.1 20170306
ncurses: ncurses 6.0.20170527 (compiled with 6.0)
libcurl: libcurl/7.54.0 OpenSSL/1.1.0f zlib/1.2.11 libpsl/0.17.0 (+libicu/59.1) libssh2/1.8.0 nghttp2/1.23.1 (compiled with 7.53.1)
SQLite: 3.19.3 (compiled with 3.17.0)
libxml2: compiled with 2.9.4

Steps to reproduce the issue:

Attempt to sync with Nextcloud News

Other info you think is relevant:
It would be most excellent if Newsbeuter could sync with Nextcloud News. Nextcloud is the replacement to OwnCloud; the "News" app is a web-based feed aggregator similar to Google Reader, etc. There are over a dozen existing clients, ~3 of them Linux, but none of them command-line based. Adding Nextcloud News support to Newsbeuter would be very useful! Thank you.

Do they support ownCloud News API? We already have ownCloud News support in master.
"Legacy API"seem to be it, but it's hard to check from the phone.
--
Regards,
Alexander Batischev

Ok, I checked and Legacy API is indeed the one used by ownCloud News; we already have an implementation for that.

Oh great! Thanks for that. However, I can't seem to get it working. I have the following in my newsbeuter config.
urls-source "ocnews"
ocnews-login "protist"
ocnews-passwordeval "python -m keyring get owncloud protist"
ocnews-url "https://protist.dynu.com/nextcloud"

However I can't connect.
$ newsbeauter -l 6
Starting newsbeuter 2.10-d1c1...
Loading configuration...done.
Opening cache...done.
Loading URLs from ownCloud News...Authentication failed.

I also tried hard-coding the password with ocnews-password, but that had the same error.

In my previous comment, I updated to master, then changed my config for ocnews, and got the above errors. I now reverted my config to syncing with tt-rss, and I get the Authentication failed errors again. I reverted to newsbeuter 2.9, and tt-rss authentication works again.

Do you have a self-signed certificate there? The domain doesn't resolve for me at the moment, so I can't check myself.

Actually, I shouldn't be so lazy, and just state my hypothesis. So: in master we've added ssl-verifyhost and ssl-verifypeer settings, both set to "yes" by default. Here's the docs.
They don't affect TT-RSS and Newsblur (see #537), but should work fine for ownCloud News (and hence nextCloud News). If your certificate is indeed self-signed, try setting both options to "no" and trying with nextCloud again.

Do you have a self-signed certificate there?

Yes, I do.

The domain doesn't resolve for me at the moment, so I can't check myself.

Oh, sorry, the domain name from my config was just dummy text to maintain privacy.

They don't affect TT-RSS…

I actually found that I did need to set ssl-verifypeer no to get even tt-rss to work.
Having said that, this also worked well for Nextcloud too. (Again, I only needed the one flag for my setup.) Thank you!
However, with the master version, Newsbeuter is ridiculously slow with some commands with Nexcloud. I tried marking articles read with N. For ten articles, it averaged 1.6 seconds each. I re-tested with tt-rss on the same newsbeuter version, and it is near instantaneous.

But you said previously that TT-RSS is very slow! :P
On a serious note, though: I don't have anything to say offhand, so I've filed an issue #567.

Argh… sorry! 😭


Cache charmcraft pack container, skip unstable tests except on schedule

Ported from https://github.com/canonical/mysql-k8s-operator/pull/146

Might be best to label the HA tests as unstable for the time being.

LGTM, but CI linting complains: https://github.com/canonical/postgresql-operator/actions/runs/4204848471/workflow and I can't see the test results when I go to the PRs checks.


docs: add discord badge (with number of online users)

Small one. Just adds the discord badge.

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

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


Single line comment error

\[ x = 1 % comment \] results in an error. The error goes away if a linefeed is placed after the comment.

I believe this was an intentional; see the discussion in #884.  The motivation is that \[ x = 1 % comment \] would also not work in LaTeX, whereas the following does work in LaTeX:
\[ x = 1 % comment
\]

I agree that this could use better documentation and error messages, though.

Well it does work in MathJax, and besides it is the straightforward behavior, so why not have it work in strict: false mode?
In strict: warn mode, let single line comments work and write a console message that tells people it can't be copied verbatim to LaTeX.

@ronkok That seems like a good idea.  It might be a bit tricky to implement because it's a change at the lexer level, but should be possible...

This has turned up a bug in \href: \href{x%y}{hi} works fine if it's a single line, but a multiline input like
\href{x%y}{hi}
bye

causes the comment behavior to trigger, resulting in an unclosed {.  LaTeX doesn't work this way, because \href redefines how % works.  I think we'll need to fix this in the same way that \verb works.


Pkg 4700 12.4 initial

Destination channel: defaults
Links

PKG-4700

Explanation of changes:

Part of CUDA 12.4 build, following conda-forge's pattern which was developed in conjunction with Nvidia. There isn't a need to stage these then release them all at once. They won't cause a problem released one at a time.
Please check the main branch too, this has just been forked
Changes made to adjust feedstocks for differences between conda-forge and defaults. Please see commit messages for description of changes.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_abcta3r1pw/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:163: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:163: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:45: outputs_not_unique: output "libnpp": Output name is not unique
clone/recipe/meta.yaml:163: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:1: missing_tests: output "libnpp": No tests were found.
===== Final Report: =====
4 Errors and 2 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_030yv7jsvk/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:0: no_global_test: Global tests are ignored in multi-output recipes.
clone/recipe/meta.yaml:163: license_file_overspecified: Using license_file and license_url is overspecified.

===== ERRORS =====

clone/recipe/meta.yaml:163: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:163: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:1: missing_tests: output "libnpp": No tests were found.
clone/recipe/meta.yaml:45: outputs_not_unique: output "libnpp": Output name is not unique
===== Final Report: =====
4 Errors and 2 Warnings were found


News: Allow users to request announcements

Use nef not fs  on a json file

@Lord-Haji what would I use to make it nef then?


adding image for merge-vhd example

This description is confusing. An image would help clear up what the author is trying to say.

Docs Build status updates of commit abc8fc0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/images/merge-vhd-example.png
:white_check_mark:Succeeded

docset/windows/hyper-v/Merge-VHD.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit e4b8936:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/images/merge-vhd-example.png
:white_check_mark:Succeeded

docset/windows/hyper-v/Merge-VHD.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

cc @JohanFreelancer9 @dariomws @get-itips @tseward

I am having second thoughts on this one.
While I recognize the value of adding an image that improves explanation, AFAIK there are no images on cmdlet-specific documentation. There are images on other types of articles, like guides or procedures. Shouldn't we check if this is accepted @dariomws @tseward  ?
and also, can we check if the image art complies with the art team_ @e0i ?
Thanks

@get-itips good point -- and this wouldn't sync down to the PoSh help docs via Get-Help.

@skalpin Given that the documentation is also accessible via terminal clients, and that there is no other similar diagram picture in the repository  it has been concluded by the reviewers that it is best to leave the picture out of the PR.
Feel free to reopen the PR without the picture for re-evaluation.
Thank you for taking the time to contribute to the Docs, and stay healthy.

@e0i No worries, I figured an image wouldn't make it through without going through some kind of marketing check.
I'll maybe make another PR to make the wording more clear.

Docs Build status updates of commit e4b8936:
:clock10: Pending: waiting for processors (60 builds ahead of you)
:warning: Docs Build is busy, currently there are 60 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit e4b8936:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/images/merge-vhd-example.png
:white_check_mark:Succeeded

docset/windows/hyper-v/Merge-VHD.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Closing via PR authors' comment.


Quickly adding users by email

Useful for subscribing people who are not cabot users to notifications. But I'm not sure if it's a good feature (I was forced to create this PR).

Closing as no response here.


when running the build of the incubator on linux

There is an issue when with one of your plugins. See logs below.
[37mnpm ERR!<EMAIL_ADDRESS>postinstall: gulp
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'gulp'.
npm ERR! This is most likely a problem with the frontend-incubator-kss-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs frontend-incubator-kss-template
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls frontend-incubator-kss-template
npm ERR! There is likely additional logging output above.

is there a difference in node versions?


About user import [500 Internet Server Error]and wrk2 unable to find Lua Library

I can normally require "socket" when using the Lua command, but an error is reported when generating the load。

It seems you do not have lua-socket installed, what is the output of "dpkg -l lua-socket"? My system shows:
# dpkg -l lua-socket
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name             Version               Architecture Description
+++-================-=====================-============-===========================================
ii  lua-socket:amd64 3.0~rc1+git+ac3201d-6 amd64        TCP/UDP socket library for the Lua language

socket.lua should be under your Lua installation directory:
# find /usr/local/share/lua |grep socket
/usr/local/share/lua/5.1/socket.lua
/usr/local/share/lua/5.1/socket
/usr/local/share/lua/5.1/socket/smtp.lua
/usr/local/share/lua/5.1/socket/url.lua
/usr/local/share/lua/5.1/socket/http.lua
/usr/local/share/lua/5.1/socket/ftp.lua
/usr/local/share/lua/5.1/socket/headers.lua
/usr/local/share/lua/5.1/socket/tp.lua

Thank you for your help. This problem has been solved. How can I solve the "500 internal server error" of registered users

It seems you do not have lua-socket installed, what is the output of "dpkg -l lua-socket"? My system shows:
# dpkg -l lua-socket
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name             Version               Architecture Description
+++-================-=====================-============-===========================================
ii  lua-socket:amd64 3.0~rc1+git+ac3201d-6 amd64        TCP/UDP socket library for the Lua language

socket.lua should be under your Lua installation directory:
# find /usr/local/share/lua |grep socket
/usr/local/share/lua/5.1/socket.lua
/usr/local/share/lua/5.1/socket
/usr/local/share/lua/5.1/socket/smtp.lua
/usr/local/share/lua/5.1/socket/url.lua
/usr/local/share/lua/5.1/socket/http.lua
/usr/local/share/lua/5.1/socket/ftp.lua
/usr/local/share/lua/5.1/socket/headers.lua
/usr/local/share/lua/5.1/socket/tp.lua

看来你没有安装 lua-socket，“dpkg -l lua-socket”的输出是什么？我的系统显示：
# dpkg -l lua-socket
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name             Version               Architecture Description
+++-================-=====================-============-===========================================
ii  lua-socket:amd64 3.0~rc1+git+ac3201d-6 amd64        TCP/UDP socket library for the Lua language

socket.lua 应该在你的 Lua 安装目录下：
# find /usr/local/share/lua |grep socket
/usr/local/share/lua/5.1/socket.lua
/usr/local/share/lua/5.1/socket
/usr/local/share/lua/5.1/socket/smtp.lua
/usr/local/share/lua/5.1/socket/url.lua
/usr/local/share/lua/5.1/socket/http.lua
/usr/local/share/lua/5.1/socket/ftp.lua
/usr/local/share/lua/5.1/socket/headers.lua
/usr/local/share/lua/5.1/socket/tp.lua

Thank you for your help. This problem has been solved. How can I solve the "500 internal server error" of registered users

Please close this issue since it's been resolved and open a new one for that issue


Fix Nan Integer ambiguity error

Had a problem not being able to compile due to an ambiguous (uint32,int32) function call to Nan's Integer functions.

Uhm, that's... surprising. Thanks for providing a patch.
Since I'm also the author of these parts of Nan I'd really like to understand what's going on. Could you take a minute and provide the exact compiler error and information on your environment (OS, platform, architecture, compiler)?

...\node_modules\nan\nan_new.h(200): error C2668: 'NanIntern::IntegerFactoryv8::Integer::New' : ambiguous call to overloaded function (..\src\network_interface.cpp) [...\build\dns_sd_bindings.vcxproj]
...\node_modules\nan\nan_new.h(101): could be
'v8::Localv8::Integer NanIntern::IntegerFactoryv8::Integer::New(uint32_t)'
...\node_modules\nan\nan_new.h(100): or
'v8::Localv8::Integer NanIntern::IntegerFactoryv8::Integer::New(int32_t)'
while trying to match the argument list '(NET_IFINDEX)'
..\src\network_interface.cpp(72) : see reference to function template instantiation 'v8::Localv8::Integer NanNewv8::Integer,NET_IFINDEX(A0)' being compiled with
[
A0=NET_IFINDEX
]

I see. Thanks. VS, x64, NET_IFINDEX... boom. Got it.

Released in v2.2.6.
Thanks again!

Awesome! Glad I could help, and glad it was an extremely easy fix :P


GH-34837: [GLib][Ruby] Add Arrow::{Sparse,Dense}UnionArray#get_value

Rationale for this change
They are missing.
What changes are included in this PR?
The following GLib APIs are added for them:

garrow_union_array_get_type_code()
garrow_union_array_get_child_id()
garrow_dense_union_array_get_value_offset()

Arrow::{Sparse,Dense}UnionArray#{to_records,values} have a backward incompatible change:

Don't include field name:

Before: {"field_name" => value}
After: value

Because I think that "field_name" is useless for many cases. Only value is suitable for many cases.
Are these changes tested?
Yes.
Are there any user-facing changes?
Yes.
This PR includes breaking changes to public APIs.
See the above description for details.

Closes: #34837

+1


Unsigned integer overflow at sox/src/xa.c:164

🐛 Describe the bug
Hi, I've been fuzzing torchaudio project with sydr-fuzz and found error at sox/src/xa.c:164.
I  think that unsigned integer overflow occurs because we get xa struct as (priv_t *) ft->priv and then use xa->header.align and xa->header.sampleRate without any checks.
How to reproduce

Build docker from here and run the container:

 sudo docker build -t oss-sydr-fuzz-torchaudio .
 sudo docker run --privileged --rm -v `pwd`:/fuzz -it oss-sydr-fuzz-torchaudio /bin/bash

Run the target on this input: sydr_afl_s02-id_001452_sync_afl_main-worker_src_001495_int_overflow_2

UBSAN_OPTIONS=print_stacktrace=1,report_error_type=1 /load_audio_afl sydr_afl_s02-id_001452_sync_afl_main-worker_src_001495_int_overflow_2

You will see the following output:

/audio/build/third_party/sox/src/sox/src/xa.c:164:53: runtime error: unsigned integer overflow: 65534 *<PHONE_NUMBER> cannot be represented in type 'unsigned int'
    #0 0x191a0b77 in startread /audio/build/third_party/sox/src/sox/src/xa.c:164:53
    #1 0x18e96c57 in open_read /audio/build/third_party/sox/src/sox/src/formats.c:545:32
    #2 0x9374d6 in torchaudio::sox::apply_effects_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::vector<std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, c10::optional<bool>, c10::optional<bool>, c10::optional<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > const&) /audio/torchaudio/csrc/sox/effects.cpp:94:16
    #3 0x8f8b33 in torchaudio::sox::load_audio_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, c10::optional<long> const&, c10::optional<long> const&, c10::optional<bool>, c10::optional<bool>, c10::optional<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > const&) /audio/torchaudio/csrc/sox/io.cpp:69:10
    #4 0x8f440b in LLVMFuzzerTestOneInput /audio/load_audio.cc:35:9
    #5 0x18e92e7d in ExecuteFilesOnyByOne /AFLplusplus/utils/aflpp_driver/aflpp_driver.c:255:7
    #6 0x18e92c88 in LLVMFuzzerRunDriver /AFLplusplus/utils/aflpp_driver/aflpp_driver.c
    #7 0x18e92848 in main /AFLplusplus/utils/aflpp_driver/aflpp_driver.c:300:10
    #8 0x7f72bfffe082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082) (BuildId: 1878e6b475720c7c51969e69ab2d276fae6d1dee)
    #9 0x833cbd in _start (/load_audio_afl+0x833cbd)

SUMMARY: UndefinedBehaviorSanitizer: unsigned-integer-overflow /audio/build/third_party/sox/src/sox/src/xa.c:164:53 in
/audio/build/third_party/sox/src/sox/src/remix.c:261:20: runtime error: implicit conversion from type 'int' of value -129 (32-bit, signed) to type 'unsigned int' changed the value to<PHONE_NUMBER> (32-bit, unsigned)
    #0 0x1903816a in lsx_channels_effect_fn /audio/build/third_party/sox/src/sox/src/remix.c:261:20
    #1 0x18eec5cc in sox_find_effect /audio/build/third_party/sox/src/sox/src/effects.c:605:38
    #2 0x94598a in torchaudio::sox::SoxEffectsChain::addInputFile(sox_format_t*) /audio/torchaudio/csrc/sox/effects_chain.cpp:243:33
    #3 0x93774e in torchaudio::sox::apply_effects_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::vector<std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, c10::optional<bool>, c10::optional<bool>, c10::optional<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > const&) /audio/torchaudio/csrc/sox/effects.cpp:116:9
    #4 0x8f8b33 in torchaudio::sox::load_audio_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, c10::optional<long> const&, c10::optional<long> const&, c10::optional<bool>, c10::optional<bool>, c10::optional<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > const&) /audio/torchaudio/csrc/sox/io.cpp:69:10
    #5 0x8f440b in LLVMFuzzerTestOneInput /audio/load_audio.cc:35:9
    #6 0x18e92e7d in ExecuteFilesOnyByOne /AFLplusplus/utils/aflpp_driver/aflpp_driver.c:255:7
    #7 0x18e92c88 in LLVMFuzzerRunDriver /AFLplusplus/utils/aflpp_driver/aflpp_driver.c
    #8 0x18e92848 in main /AFLplusplus/utils/aflpp_driver/aflpp_driver.c:300:10
    #9 0x7f72bfffe082 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x24082) (BuildId: 1878e6b475720c7c51969e69ab2d276fae6d1dee)
    #10 0x833cbd in _start (/load_audio_afl+0x833cbd)

SUMMARY: UndefinedBehaviorSanitizer: implicit-integer-sign-change /audio/build/third_party/sox/src/sox/src/remix.c:261:20 in
Execution successful.

Versions
torchaudio version: 30afaa9b2f460ca3baf6ac177bce4f6b5da8b99c
pytorch version: 0f1621df1a0a73956c7ce4e2f72f069e610e0137
sox version: 14.4.2
OS: Ubuntu 20.04

Hi @hkctkuy
Thanks for the interesting report.
The thing is, I am about to land #3497, which switchs libsox integration to runtime linking, and these source code will not be used. Therefore unfortunately these reports become irrelevant to torchaudio soon. They need to be addressed at upstream. (and upstream project has made a lot of changes since 14.4.2, so these might not be relevant.)
Do you find anything needs fix in torchaudio codebase, instead of third party directory? I am aware couple of cases where signed integer and unsigned integer are compared, but did not have time to fix them. It would be nice if you could make PR to fix them.

#3497 has landed, and now torchaudio links to sox dynamically. We no longer compile the specified code by ourselves and therefore this issue is now irrelevant.
Feel free to fuzz the code under torchaudio/csrc, and report issues there. Thanks,


[Angular 10] - Function calls are not supported in decorators but 'NativeScriptRouterModule' was called

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

CLI: 7.0.4
Cross-platform modules: 6.5.15
Android Runtime: 6.5.3
iOS Runtime: 6.5.2
NativeScript-Angular: 10.0
Angular: 10.0

Describe the bug
I've migrated my project from NS 6.5.x and Ng 8.21 to Ng 9 and then to NG 10.
Migration to Ng 9 was ok, I can start my application without Ivy enable.
To migrate to Ng 9 I've followed this wiki:
https://github.com/NativeScript/nativescript-angular/wiki/Updating-and-developing-for-@nativescript-angular-v9-with-Ivy-or-without
Then I made migration to Ng 10, following this post:
https://nativescript.org/blog/upgrading-tips-for-angular-10/
I've fixed all build errors but now I have this and I don't know how to solve:
ERROR in Error during template compile of 'AppRoutingModule'
  Function calls are not supported in decorators but 'NativeScriptRouterModule' was called.

Can you help me? Can I upgrade to Ng 10 without Ns 7 migration.
I would like to migrate to NS 7 later when all plugins I use will offer NS 7 support.

I'm having the same error.
package.json details
    "@angular/cli": "~10.1.0",
    "@angular/compiler-cli": "~10.1.0",
    "@nativescript/angular": "~10.1.0",
    "@nativescript/core": "^7.0.0",

iOS runtime: 6.5.2
This is the specific error I'm getting
ERROR in src/app/app.module.ts(10,33): Error during template compile of 'AppModule'
  Function calls are not supported in decorators but 'NativeScriptRouterModule' was called in 'routesModule'
    'routesModule' calls 'NativeScriptRouterModule'.

This my app-routing.module

import { Routes } from '@angular/router';
import { NativeScriptRouterModule } from '@nativescript/angular';

import { HomeComponent } from '~/app/views/home.component';

const routes: Routes = [
  {
    path: '',
    redirectTo: '/home',
    pathMatch: 'full'
  },
  {
    path: 'home',
    component: HomeComponent
  }
];

export const routesModule = NativeScriptRouterModule.forRoot(routes);

This is the app module where I'm importing routesModule
import { NgModule, NO_ERRORS_SCHEMA } from '@angular/core';
import { NativeScriptModule } from '@nativescript/angular';

import { AppComponent } from './app.component';
import { HomeComponent } from '~/app/views/home.component';
import { routesModule } from '~/app/app-routing.module';

@NgModule({
  bootstrap: [AppComponent],
  imports: [NativeScriptModule, routesModule],
  declarations: [AppComponent, HomeComponent],
  schemas: [NO_ERRORS_SCHEMA]
})
export class AppModule {}

I'm also having this issue. I'm running a building a nativescript angular project where I intend to build a website, iOS and Android from the same code base. I started the project about a year ago and came back to it. First things first, I spent some time bringing all my packages up to date. However, when running ns debug ios I come across this error.
    ERROR in Error during template compile of 'AppRoutingModule'
  Function calls are not supported in decorators but 'NativeScriptRouterModule' was called.
Unexpected value 'undefined' imported by the module 'AppRoutingModule in /Users/user/project/src/app/app-routing.module.tns.ts'
Can't export value NativeScriptRouterModule in<EMAIL_ADDRESS>from AppRoutingModule in /Users/user/project/src/app/app-routing.module.tns.ts as it was neither declared nor imported!
Error during template compile of 'AppRoutingModule'
  Function calls are not supported in decorators but 'NativeScriptRouterModule' was called.
Unexpected value 'undefined' imported by the module 'AppRoutingModule in /Users/user/project/src/app/app-routing.module.ts'
Can't export value NativeScriptRouterModule in<EMAIL_ADDRESS>from AppRoutingModule in /Users/user/project/src/app/app-routing.module.ts as it was neither declared nor imported!
Error during template compile of 'AppRoutingModule'
  Function calls are not supported in decorators but 'NativeScriptRouterModule' was called.
Error during template compile of 'AppRoutingModule'
  Function calls are not supported in decorators but 'NativeScriptRouterModule' was called.

It feels like a typescript error I'm not sure. Any help would be appreciated.
My package.json
{
  "name": "project",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "web": "ng serve --live-reload false --disableHostCheck true",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e",
    "android": "tns run android --bundle",
    "ios": "tns run ios --bundle",
    "mobile": "tns run --bundle",
    "preview": "tns preview --bundle"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "~10.1.1",
    "@angular/common": "~10.1.1",
    "@angular/compiler": "~10.1.1",
    "@angular/core": "~10.1.1",
    "@angular/forms": "~10.1.1",
    "@angular/localize": "^10.1.1",
    "@angular/platform-browser": "~10.1.1",
    "@angular/platform-browser-dynamic": "~10.1.1",
    "@angular/router": "~10.1.1",
    "@nativescript/angular": "10.1.0",
    "@nativescript/core": "7.0.2",
    "@proplugins/nativescript-localstorage": "^2.3.2",
    "bootstrap": "^4.3.1",
    "core-js": "^2.5.4",
    "jquery": "^3.4.1",
    "moment": "^2.20.1",
    "nativescript-geolocation": "5.1.0",
    "nativescript-theme-core": "^1.0.6",
    "ngx-bootstrap": "^6.1.0",
    "reflect-metadata": "~0.1.12",
    "rxjs": "~6.5.2",
    "rxjs-compat": "6.3.3",
    "zone.js": "^0.10.3"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^0.1001.0",
    "@angular/cli": "^10.1.0",
    "@angular/compiler-cli": "10.1.0",
    "@nativescript/ios": "7.0.0",
    "@nativescript/schematics": "10.0.2",
    "@nativescript/types": "~7.0.1",
    "@nativescript/webpack": "~3.0.4",
    "@ngtools/webpack": "~10.1.0",
    "@types/jasmine": "2.8.17",
    "@types/jasminewd2": "~2.0.8",
    "@types/node": "^14.10.0",
    "codelyzer": "^6.0.0",
    "jasmine-core": "~3.5.0",
    "jasmine-spec-reporter": "~5.0.0",
    "karma": "~5.0.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage-istanbul-reporter": "~3.0.2",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "nativescript-dev-sass": "~1.6.0",
    "nativescript-dev-typescript": "~0.8.0",
    "protractor": "~7.0.0",
    "ts-node": "~5.0.1",
    "tslint": "~6.1.0",
    "typescript": "3.9.7",
    "uglifyjs-webpack-plugin": "^1.1.6"
  },
  "main": "main.js"
}

AppRoutingModule looks like this:
import { NgModule } from "@angular/core";
import { Routes } from "@angular/router";
import { NativeScriptRouterModule } from "@nativescript/angular";

import { ErrorComponent, SecureComponent, PublicComponent } from './components';
import { PUBLIC_ROUTES } from './public.routes';
import { SECURE_ROUTES } from './secure.routes';
import { Guard } from './guard';

const APP_ROUTES: Routes = [
    { path: '', component: PublicComponent, children: PUBLIC_ROUTES},
    { path: '', component: SecureComponent, canActivate: [Guard], children: SECURE_ROUTES},
    {
        path: '**',
        component: ErrorComponent
    }
];

@NgModule({
    imports: [NativeScriptRouterModule.forRoot(APP_ROUTES)],
    exports: [NativeScriptRouterModule]
})
export class AppRoutingModule { }

And it is imported into my main module like this:
...
import { AppRoutingModule } from "./app-routing.module.tns";

@NgModule({
    bootstrap: [
        AppComponent
    ],
    imports: [
        NativeScriptModule,
        AppRoutingModule,
        HttpClientModule,
        FormsModule,
        ReactiveFormsModule
    ],
    declarations: [
        AppComponent,
        LoginComponent,
        PublicComponent,
        SecureComponent,
        ErrorComponent,
        GeneralComponent,
        MainComponent,
        MenuComponent,
        StoreComponent,
        ItemComponent,
        HomeComponent,
        HashPipe
    ],
    providers: [
        AuthService,
        AuthRequestService,
        StoreRequestService,
        OrderRequestService,
        StorageService,
        Guard,
        {
            provide: UniversalStorageService,
            useValue: mobileStorage
        },
        {
            provide: HTTP_INTERCEPTORS,
            useClass:  NoopInterceptor,
            multi: true
        }

    ],
    schemas: [
        NO_ERRORS_SCHEMA
    ]
})
export class AppModule { }

My text editor highlight these lines as shown below citing that Class NativeScriptRouterModule.forRoot(APP_ROUTES) is not an Angular Function.

@mapo80 and @armourjami
By upgrading to Angular 9.
The wiki said you need to make the following change:
disable Ivy by adding this to your project's tsconfig.json with the following:
"compilerOptions": {
  ...your various options, etc.
},
"angularCompilerOptions": {
    "enableIvy": false
}

When you remove this
"angularCompilerOptions": {
    "enableIvy": false
}

from your tsconfig.json file the build should work again.
I hope this also solves your issue?

Awesome thanks @DepickereSven. This does solve the issue. Thanks 😁

This fixes the issue, thanks very much.
I want to understand why this workaround fixes the issue, do you know @DepickereSven?

@DepickereSven I need to disable Ivy, because if I enable it my application doesn't work.
If I remove angularCompilerOptions, Ivy is enabled by default but I need to disable Ivy.
Do you know how to solve this with Ivy disabled? Suggestions?
ERROR in Error during template compile of 'AppRoutingModule'
  Function calls are not supported in decorators but 'NativeScriptRouterModule' was called.

@armourjami I've checked and I have this configuration so stack overflow question doesn't solve my problem:
"compilerOptions": {
    "target": "es5"
    ...
}

Suggestions? How to disable Ivy?

@mapo80 to be honest I don't have any clue.
I can't find any information to opt-out of Ivy in Angular 10.
See Angular website: https://angular.io/guide/ivy

I have tried everything but can't solve the problem.
I've read this post but nothing: https://github.com/angular/angular/issues/23609#issuecomment-561615821
Only @NathanWalker can help us!

I made another try, I've used downgraded from Ns 10 to Ns 9 but I've used NS 7 and I don't have this problem.
App doesn't start for other problems but I don't have build problems.
I raise my hands! @NathanWalker, I'll wait for your answer.

I've created a repo to reproduce the issue: https://github.com/mapo80/TestNs7Ng10

@mapo80 I would close this issue and create a new one with your specific problem. Because your issue about "[Angular 10] - Function calls are not supported in decorators but 'NativeScriptRouterModule'" was called has been resolved.

@DepickereSven This issue is solved if Ivy is enabled, if not build continues to fail.

Removing the config
"angularCompilerOptions": {
    "enableIvy": false
}

enables ivy and I think you want Ivy, I don't think that's the issue, there is something else at play here.
I managed to work around it but I can't be specific as to what it was that I did. @mapo80 could you paste you package.json? I'm not promising to solve this but if I compare what you have with what I have, then perhaps it will remind me what I did to get around it?

Guys thanks for your help, I need to disable Ivy but if I disable something goes wrong.
To solve this issue it’s needed to make a new version of @nativescript/angular with nativescript disabled.
To test this bug with Ivy disabled just try to build this simple project:
https://github.com/mapo80/TestNs7Ng10

Ok no problem. However, I did manage to get around that exact issue with Ivy enabled, so it is possible.

Hi,
Does anyone found the right fix instead of enabling Ivy ?
I'm facing also this issue and enabling Ivy is making my app running but wondering the accuracy of this procedure.
In my case the error is thrown by one of my generated lib but there is a lack of debugging to find which code block is origin of this error


Unwrapping a private key results in a pkcs11.exceptions.AttributeTypeInvalid

Attempting to unwrap a private key (use case of moving a private key from one HSM to another) results in a pkcs11.exceptions.AttributeTypeInvalid exception.
Code block which should reproduce the issue:
import pkcs11
hsm=pkcs11.lib('/usr/local/lib/softhsm/libsofthsm2.so')
token=hsm.get_token(token_label='alice-token-1')
session=token.open(user_pin='1111',rw=True)
pubkey,privkey=session.generate_keypair(key_type=pkcs11.KeyType.RSA, key_length=2048, store=True, label='alice-rsa-01', private_template={pkcs11.Attribute.EXTRACTABLE=True})
secretkek=session.generate_key(key_type=pkcs11.KeyType.AES, key_length=256, store=True, label='alice-kek-01')
wrapped=secretkek.wrap_key(privkey)
unwrapped=secretkek.unwrap_key(object_class=pkcs11.ObjectClass.PRIVATE_KEY, key_type=pkcs11.KeyType.RSA,key_data=wrapped, label='check',store=False)
The issue occurs within the UnwrapMixin, where the template is created. Best I can tell reading the pkcs11 documents, RSA private keys should not have the encrypt, wrap, and verify attributes at all, and trying to set them causes the SoftHSM to generate an error.

#105 I've created a pull request with a proposed fix. It may not be the ideal spot to fix this issue, but it allowed me to move past the exception in my work using this module.

Override those attributes the HSM doesn't like in your template with the value pkcs11.DEFAULT, which removes the key from the final merged template.
e.g.
private_template = {
            Attribute.ENCRYPT: DEFAULT,
            Attribute.WRAP: DEFAULT,
            Attribute.VERIFY: DEFAULT,
}

Just tried it on my test case-
unwrapped=secretkek.unwrap_key(object_class=pkcs11.ObjectClass.PRIVATE_KEY, key_type=pkcs11.KeyType.RSA,key_data=wrapped, label='check',store=False, template={pkcs11.Attribute.ENCRYPT : pkcs11.DEFAULT, pkcs11.Attribute.WRAP : pkcs11.DEFAULT, pkcs11.Attribute.VERIFY : pkcs11.DEFAULT})

appears to work.
Sure enough, a closer reading of the docs reveals a reference to this behavior:
https://python-pkcs11.readthedocs.io/en/latest/api.html?highlight=DEFAULT#pkcs11.constants.DEFAULT
Thank you for pointing me in the right direction!

Probably could be better documented. It's a bit of a hack to work around trying to make it work as easily as you like for the most number of HSMs.


Add a link to WebJars

Add a link to WebJars from the introduction section.
Unfortunately, there is no direct way to directly link rot.js on the WebJars site so I've decided to simply link their main page. It will be sufficient for guys who use WebJars :)
We've already used this jar-version of rot.js in the Keter project and it works well.

Thanks!


Entity generator produces wrong code in file "_EntityExtensionsRx.cs.gen"

The problem

Entity generator produces wrong code in file "_EntityExtensionsRx.cs.gen"
Environment

NetDaemon release with the issue: 21.6.0-beta, 21.8.0-beta
Last working NetDaemon release (if known): 21.5.1-beta
Operating environment (Home assistant Add-on/Docker/Dev setup): Dev setup (from https://github.com/net-daemon/netdaemon-app-template)
Link to integration documentation on our website:

Link to or paste code that causes the issue

...

public partial class InputSelectEntity : NetDaemon.Common.Reactive.Services.RxEntityBase
{
    public InputSelectEntity(INetDaemonRxApp daemon, IEnumerable<string> entityIds): base(daemon, entityIds)
    {
    }

    public void Reload(dynamic? data = null)
    {
        CallService("input_select", "reload", serviceData, False);
    }
...

Traceback/Error logs

Error	CS0103	The name 'serviceData' does not exist in the current context
Error	CS0103	The name 'False' does not exist in the current context

Additional information

Fixed in #322


[WIP][POAE7-453]Enable KV store mechanism in old Parquet cache reader

What changes were proposed in this pull request?
Enable external db to store cache locality info and schedule tasks accordingly.
How was this patch tested?
E2E.
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@jikunshang @yma11 @winningsix Please take a review, thanks.
This pr is WIP, have modified original FileScanRDD.scala. Will split it into two prs when it's LGTM.


Ian ruotsala

@ckopecky
honestly, it's borderline (to me) about whether this count as an MVP: I got hung up on the header (dealing with optimizing for semantic vs optimizing for easy layout)

closing this because I am doing a 2nd pull requeset with updated stuff


Airflow 2691 npm webpack

Make sure you have checked all steps below.
JIRA

[ ] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[ ] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9ebb04a). Click here to learn what that means.
The diff coverage is 90.9%.

@@            Coverage Diff            @@
##             master       #5   +/-   ##
=========================================
  Coverage          ?   76.85%
=========================================
  Files             ?      205
  Lines             ?    15514
  Branches          ?        0
=========================================
  Hits              ?    11924
  Misses            ?     3590
  Partials          ?        0

Impacted Files
Coverage Δ

airflow/www_rbac/app.py
100% <100%> (ø)

airflow/www_rbac/static_config.py
90% <90%> (ø)

Continue to review full report at Codecov.

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


About kitti_half and kitti_half_sc

Hi, xingyizhou. There are some question I want to ask.

kitti_half is also use the first half frames for training and the second for validation, if there is odd number in a sequence, how to split it?
what is the meaning of kitti_half_sc , I can not find the definition of this.
Very appreciate for your reoly!!

Thank you for your interests.

The code for the split is here. We use [0, L//2) for training and [L//2, L) for validation.
It means train from "scratch". Actually it uses ImageNet pretrain. It is in contrast to using nuScenes pretrain.

thanks for your reply! @xingyizhou

Sorry to bother u again, sir. Will it support kitti 3D tracking later?


chore: bdd-sbhg-1588301062 to 0.0.1

chore: Promote bdd-sbhg-1588301062 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


fix: extra deps are included

Close #78

The failing E2E tests aren't your fault, I noticed it before as well. I'm not sure if I broke something in my previous PR, or if it happened before that.

Oh, I see. 😅
I'll mess around and see if I can fix it.
I'll let you know if it doesn't seem easy, and move on to the next issue in that case, thanks!

Sounds good, thank you!


Implementation for Flat End Caps on Tube Geometry

This pull request tries to addresses the issues described in #18.
It introduces a prototype for implementing flat end caps on the tube geometry. The end caps are designed to close the ends of the tube geometry, which enhances the overall appearance when using a standard material such as MeshPhongMaterial. However, there are a few issues that need to be addressed before this implementation can be considered complete.
Current Functionality: The current changes successfully add flat end caps to the tube geometry, controlled via a simple boolean option.

Known Issues
Mesh Topology
When switching to wireframe mode, the mesh topology reveals inconsistencies between the first and second end caps.
The second end cap (end) appears correct, featuring 1 center vertex connected to the last radial segment of the tube.
The first end cap (start), however, has redundant vertices. It includes 1 center vertex + (radialSegments + 1) rim vertices, which makes it geometrically inconsistent with the rest of the tube.
UV Textures
The UV mapping for the last segment of the tube (adjacent to the second end cap) is twisted.
The first end cap (start) also displays UV issues, likely caused by the redundant vertices. These issues prevent proper texture mapping on both ends of the tube.
Extensibility
While the current implementation allows toggling flat end caps, it lacks flexibility for future enhancements.
Future end cap types, such as round (semi-hemisphere) end caps,  arrow-shaped end caps or squared (plug) end caps, cannot be easily introduced with the current design.

I have thoroughly investigated potential solutions for the issues above but was unable to resolve them with my current (very limited) knowledge level. I also reviewed the TubeBuilder.js code you provided but could not identify the cause of these problems or a way to fix them. I would appreciate if you could address the current issues (mesh topology und UV texture) and maybe make the implementation more robust for adding other types of end caps in the future. :pray:

To avoid confusion with normals and UVs, the cap should generally not share vertices with the sides. I will try to address these issues.

I submitted another PR. #20


How can we implement a image-in-and-image-out CNN?

In visual object detection task, we should label each pixel with some labeles such as 'road', 'car', 'tree' and so on, as in the figure below.

left: the input image; right: the target.
I think this task can be solved with convolutional neural network (CNN), which shows its power in many image-related tasks.
In the examples folder, the CNN expamples are all about image labelling task which input is a image and output is a single label. How can we employ CNN to the visual object detection task, which requires the output is also a image?

The output of such networks are not images. It's obtained by Image Segmentation, or in other words each pixel is labelled. There are many ways to do it, all of which could be built on top of Keras.
On Wed, Jul 8, 2015 at 6:26 AM, alzhusan<EMAIL_ADDRESS>wrote:

In visual object detection task, we should label each pixel with some labeles such as 'road', 'car', 'tree' and so on, as in the figure below.

left: the input image; right: the target.
I think this task can be solved with convolutional neural network (CNN), which shows its power in many image-related tasks.
In the examples folder, the CNN expamples are all about image labelling task which input is a image and output is a single label. How can we employ CNN to the visual object detection task, which requires the output is also a image?
Reply to this email directly or view it on GitHub:
https://github.com/fchollet/keras/issues/359

I think you do not need an image-output. The output should be a matrix with the same size of the input image and each element in the matrix is a label.

There is an interesting article from Yann LeCun about employing CNN for scene labeling:
http://yann.lecun.com/exdb/publis/pdf/farabet-pami-13.pdf

Hello! Would there be a reference that I could look for the image segmentation by Keras?
I am trying to achieve a similar task, but I am having some difficulty.
Thank you!


CLI interface

Hi, i'm using Rider to write c# code, and i have no ability to generate typescript without Visual Studio. But VS is too slow and it is painfully to start it.
Maybe you can provide some CLI interface to get rid of dependence of VS?

This is a duplicate of #133


Update auth, dynamodb, s3, sqs to 2.17.121

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:dynamodb
software.amazon.awssdk:s3
software.amazon.awssdk:sqs

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

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

Superseded by #821.


Code to Open or Navigate to Another Page or Screen withing the tabris app

Problem description
How can I open another Activity within my Tabriz App ...I need a code snippet to do that as I don't have any idea on it
or I'd say how to navigate to another Page within the app
Note: I'm using .jsx extension

Expected behavior

Environment

Tabris.js version: 3.2.0
Device:  Tecno
OS:  Android 5.1

Code snippet
// A minimal, *self-contained* code snippet to reproduce the problem:

What did you mean by Activity? Tabris has a NavigationView  that allows you to open different pages and navigate through them. Did you mean that?

Let me say...to navigate to another page within the app

If you want to figure it out on your own, please don't open the Spoon section.
There are many ways to display new content. Starting from the new Composite in screen size, ending with hand-made classes based on Composite
The easiest way to open new pages, NavigationView, about it you can read on the appropriate page. And example use you can find here:
Also take a look at the documentation page about Page
I wrote a simple version of the usage in TS, you can see it below

Spoon
You can use NavigationView instead of contentView, and place page content in new Pages
let navigationView = new NavigationView({ left: 0, right: 0, top: 0, bottom: 0, toolbarVisible: false })
  .appendTo(contentView);
let examplePage = new Page({ top: 0, bottom: 0, left: 0, right: 0 });
examplePage.onAppear(({target: page})=> {page.append(....)});
navigatorView.append(examplePage);

The most recent Page that has been append to the NavigationView will be displayed.
Don't forget to .dispose() previous pages to clear the contentView if they are no longer needed

There's also a collection of examples all of which are included in the Tabris.js developer app that you can find in the Google Play store and Apple App Store.


docs: improve READMEs

Summary of Changes

Add a demo GIF
Add more content to the README of the VS Code extension

The failure of the link check is expected.

:tada: This PR is included in version 0.11.0 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.11.0
GitHub release

Your semantic-release bot :package::rocket:


Client generation intermittently fails (silently) in docker container in CI

Bug description
Some helpful context from https://github.com/prisma/prisma/issues/13999

For us, we have a polyglot monorepo that utilizes yarn workspaces. We also have 3 databases, all of which we configure and access with Prisma. Accordingly, we generate multiple prisma clients in one monorepo (with more to come as we add additional services/apps). We utilize the client generation output configuration to plop the generated client into the ./dist of appropriately named and located package e.g. @{company-name}/users-service-orm (effectively wrapping it in our own package and tracking it as part of our package dependency graph).

Above results in 6 prisma-related packages, in particular:
@users/schema   // has schema.prisma
@users/orm      // wrapper around generated client
@blocks/schema  // has schema.prisma
@blocks/orm     // wrapper around generated client
@app/schema     // has schema.prisma
@app/orm        // wrapper around generated client

We build our monorepo with turborepo.  On build of the */schema packages above I would expect to see something like this
@users/schema:build: Environment variables loaded from .env
@users/schema:build: Prisma schema loaded from src/schema.prisma
@users/schema:build:
@users/schema:build: ✔ Generated Prisma Client (3.15.2 | library) to ./../orm/dist in 140ms
@users/schema:build:
@users/schema:build: ✔ Generated Prisma Typebox Generator to ./src/typebox in 172ms
@users/schema:build: You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
@users/schema:build: ```
@users/schema:build: import { PrismaClient } from '../orm/dist'
@users/schema:build: const prisma = new PrismaClient()
@users/schema:build: ```
@users/schema:build: CLI Building entry: src/index.ts
@users/schema:build: CLI Using tsconfig: tsconfig.json
@users/schema:build: CLI tsup v6.1.2
@users/schema:build: CLI Target: ESNext
@users/schema:build: CLI Cleaning output folder
@users/schema:build: ESM Build start
@users/schema:build: CJS Build start
@users/schema:build: ESM ⚡ Build success in 61ms
@users/schema:build: CJS ⚡ Build success in 59ms
@users/schema:build: ESM dist/index.mjs 14.02 KB
@users/schema:build: CJS dist/index.js 14.50 KB
@users/schema:build: CLI 🐢 Building d.ts and d.ts.map
@users/schema:build: CLI 🐢 Build success (albeit slowly)
@users/schema:build: DTS dist/index.d.ts
@users/schema:build: DTS dist/index.d.ts.map
@users/schema:build: DTS dist/seed.d.ts
@users/schema:build: DTS dist/seed.d.ts.map
@blocks/schema:build: Environment variables loaded from .env
@blocks/schema:build: Prisma schema loaded from src/schema.prisma
@blocks/schema:build:
@blocks/schema:build: ✔ Generated Prisma Client (3.15.2 | library) to ./../orm/dist in 252ms
@blocks/schema:build:
@blocks/schema:build: ✔ Generated Prisma Typebox Generator to ./src/typebox in 1.15s
@blocks/schema:build: You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
@blocks/schema:build: ```
@blocks/schema:build: import { PrismaClient } from '../orm/dist'
@blocks/schema:build: const prisma = new PrismaClient()
@blocks/schema:build: ```
@blocks/schema:build: CLI Building entry: src/index.ts
@blocks/schema:build: CLI Using tsconfig: tsconfig.json
@blocks/schema:build: CLI tsup v6.1.2
@blocks/schema:build: CLI Target: ESNext
@blocks/schema:build: CLI Cleaning output folder
@blocks/schema:build: ESM Build start
@blocks/schema:build: CJS Build start
@blocks/schema:build: ESM ⚡ Build success in 123ms
@blocks/schema:build: CJS ⚡ Build success in 120ms
@blocks/schema:build: ESM dist/index.mjs 39.89 KB
@blocks/schema:build: CJS dist/index.js 41.83 KB
@blocks/schema:build: CLI 🐢 Building d.ts and d.ts.map
@blocks/schema:build: CLI 🐢 Build success (albeit slowly)
@blocks/schema:build: DTS dist/index.d.ts
@blocks/schema:build: DTS dist/index.d.ts.map
@blocks/schema:build: DTS dist/seed.d.ts
@blocks/schema:build: DTS dist/seed.d.ts.map
@app/schema:build: Environment variables loaded from .env
@app/schema:build: Prisma schema loaded from src/schema.prisma
@app/schema:build:
@app/schema:build: ✔ Generated Prisma Client (3.15.2 | library) to ./../orm/dist in 407ms
@app/schema:build:
@app/schema:build: ✔ Generated Prisma Typebox Generator to ./src/typebox in 1.42s
@app/schema:build: You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
@app/schema:build: ```
@app/schema:build: import { PrismaClient } from '../orm/dist'
@app/schema:build: const prisma = new PrismaClient()
@app/schema:build: ```
@app/schema:build: CLI Building entry: src/index.ts
@app/schema:build: CLI Using tsconfig: tsconfig.json
@app/schema:build: CLI tsup v6.1.2
@app/schema:build: CLI Target: ESNext
@app/schema:build: CLI Cleaning output folder
@app/schema:build: ESM Build start
@app/schema:build: CJS Build start
@app/schema:build: CJS ⚡ Build success in 160ms
@app/schema:build: CJS dist/index.js 75.07 KB
@app/schema:build: ESM ⚡ Build success in 214ms
@app/schema:build: ESM dist/index.mjs 72.68 KB
@app/schema:build: CLI 🐢 Building d.ts and d.ts.map
@app/schema:build: CLI 🐢 Build success (albeit slowly)
@app/schema:build: DTS dist/index.d.ts
@app/schema:build: DTS dist/index.d.ts.map
@app/schema:build: DTS dist/seed.d.ts
@app/schema:build: DTS dist/seed.d.ts.map

But we see intermittent failures when building the schema packages in CI (GitHub Actions), particularly when building in docker containers.
We will see the build for */schema packages kick off
#21 37.41 @blocks/schema:build: Environment variables loaded from .env
#21 37.44 @blocks/schema:build: Prisma schema loaded from src/schema.prisma
#21 37.65 @app/schema:build: Environment variables loaded from .env
#21 37.66 @app/schema:build: Prisma schema loaded from src/schema.prisma
#21 37.82 @users/schema:build: Environment variables loaded from .env
#21 37.84 @users/schema:build: Prisma schema loaded from src/schema.prisma

But the client generation seems to fail silently.  Immediately after above in logs we see
#21 39.31 @dopt/expression-gen-query:build: CLI 🐢 Build success (albeit slowly)
#21 39.32 @dopt/expression-gen-query:build: DTSdist/constants.d.ts
#21 39.32 @dopt/expression-gen-query:build: DTSdist/constants.d.ts.map
#21 39.32 @dopt/expression-gen-query:build: DTSdist/gen-query.d.ts
#21 39.32 @dopt/expression-gen-query:build: DTSdist/gen-query.d.ts.map
#21 39.32 @dopt/expression-gen-query:build: DTSdist/index.d.ts
#21 39.32 @dopt/expression-gen-query:build: DTSdist/index.d.ts.map
#21 39.32 @dopt/expression-gen-query:build: DTSdist/index.test.d.ts
#21 39.32 @dopt/expression-gen-query:build: DTSdist/index.test.d.ts.map
#21 39.32 @dopt/expression-gen-query:build: DTSdist/utility.d.ts
#21 39.32 @dopt/expression-gen-query:build: DTSdist/utility.d.ts.map
#21 41.48 @blocks/schema:build: CLI Building entry: src/index.ts
#21 41.48 @blocks/schema:build: CLI Using tsconfig: tsconfig.json
#21 41.48 @blocks/schema:build: CLI tsup v6.1.2
#21 41.48 @blocks/schema:build: CLI Using tsup config<EMAIL_ADDRESS>#21 41.49 @blocks/schema:build: CLI Target: ESNext
#21 41.49 @blocks/schema:build: CLI Cleaning output folder
#21 41.50 @blocks/schema:build: ESM Build start
#21 41.51 @blocks/schema:build: CJS Build start
#21 41.52 @blocks/schema:build: ✘ [ERROR] Could not resolve "./typebox"
#21 41.52 @blocks/schema:build:
#21 41.52 @blocks/schema:build:     src/index.ts:1:14:
#21 41.52 @blocks/schema:build:       1 │ export * from './typebox';
#21 41.52 @blocks/schema:build:         ╵               ~~~~~~~~~~~
#21 41.52 @blocks/schema:build:
#21 41.52 @blocks/schema:build: ✘ [ERROR] Could not resolve "./typebox"
#21 41.52 @blocks/schema:build:
#21 41.52 @blocks/schema:build:     src/index.ts:1:14:
#21 41.52 @blocks/schema:build:       1 │ export * from './typebox';
#21 41.52 @blocks/schema:build:         ╵               ~~~~~~~~~~~
#21 41.52 @blocks/schema:build:
#21 41.53 @blocks/schema:build: ESM Build failed
#21 41.53 @blocks/schema:build: CJS Build failed

Where, at this point, the client generation failed silently and the errors we see are related to typebox types (which we generate from the schema as part of prisma generate) not being present.
Said another way, we are missing the following
@blocks/schema:build:
@blocks/schema:build: ✔ Generated Prisma Client (3.15.2 | library) to ./../orm/dist in 252ms
@blocks/schema:build:
@blocks/schema:build: ✔ Generated Prisma Typebox Generator to ./src/typebox in 1.15s
@blocks/schema:build: You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
@blocks/schema:build: ```
@blocks/schema:build: import { PrismaClient } from '../orm/dist'
@blocks/schema:build: const prisma = new PrismaClient()
@blocks/schema:build: ```

How to reproduce
Unlike the issue I filed earlier this week, I've never been able to reproduce this locally so I'm going to have a harder time providing a simple reproduction.  It would involve setting up a mock repo with a ci/cd pipeline and docker builds.  Not impossible but going to take some time.
Expected behavior
Client generation succeeds OR gives meaningful error when it fails.
Prisma information
A simple example of one of our schemas.  The others are quite large.
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
  output   = "../../orm/dist"
}

generator typebox {
  provider = "prisma-typebox-generator"
}

model User {
  id         Int      @id @default(autoincrement())
  identifier String
  workspace  String
  properties Json
  createdAt  DateTime @default(now())

  @@unique([identifier, workspace])
}

Environment & setup
Local Machine
System:
OS: Linux 5.18 Arch Linux
CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
Binaries:
Node: 16.9.1 - /tmp/xfs-3ac83410/node
Yarn: 3.2.1 - /tmp/xfs-3ac83410/yarn
npm: 7.21.1 - ~/.nvm/versions/node/v16.9.1/bin/npm
CI
OS: Ubuntu 20.04.4  LTS
Docker Container in CI
2022-06-28T22:17:30.7786847Z [command]/usr/bin/docker version
2022-06-28T22:17:30.8120751Z Client:
2022-06-28T22:17:30.8121571Z  Version:           20.10.17+azure-1
2022-06-28T22:17:30.8124664Z  API version:       1.41
2022-06-28T22:17:30.8124924Z  Go version:        go1.17.11
2022-06-28T22:17:30.8125208Z  Git commit:        100c70180fde3601def79a59cc3e996aa553c9b9
2022-06-28T22:17:30.8125509Z  Built:             Mon Jun  6 21:36:39 UTC 2022
2022-06-28T22:17:30.8125752Z  OS/Arch:           linux/amd64
2022-06-28T22:17:30.8125979Z  Context:           default
2022-06-28T22:17:30.8126203Z  Experimental:      true
2022-06-28T22:17:30.8126347Z
2022-06-28T22:17:30.8126425Z Server:
2022-06-28T22:17:30.8126598Z  Engine:
2022-06-28T22:17:30.8132416Z   Version:          20.10.17+azure-1
2022-06-28T22:17:30.8132915Z   API version:      1.41 (minimum version 1.12)
2022-06-28T22:17:30.8133566Z   Go version:       go1.17.11
2022-06-28T22:17:30.8134009Z   Git commit:       a89b84221c8560e7a3dee2a653353429e7628424
2022-06-28T22:17:30.8134631Z   Built:            Mon Jun  6 22:32:38 2022
2022-06-28T22:17:30.8135013Z   OS/Arch:          linux/amd64
2022-06-28T22:17:30.8135676Z   Experimental:     false
2022-06-28T22:17:30.8140241Z  containerd:
2022-06-28T22:17:30.8140995Z   Version:          1.5.13+azure-1
2022-06-28T22:17:30.8141455Z   GitCommit:        a17ec496a95e55601607ca50828147e8ccaeebf1
2022-06-28T22:17:30.8142052Z  runc:
2022-06-28T22:17:30.8142396Z   Version:          1.0.3
2022-06-28T22:17:30.8143016Z   GitCommit:        f46b6ba2c9314cfc8caae24a32ec5fe9ef1059fe
2022-06-28T22:17:30.8143471Z  docker-init:
2022-06-28T22:17:30.8144044Z   Version:          0.19.0
2022-06-28T22:17:30.8144608Z   GitCommit:
2022-06-28T22:17:30.8173229Z [command]/usr/bin/docker info
2022-06-28T22:17:30.8948167Z Client:
2022-06-28T22:17:30.8948786Z  Context:    default
2022-06-28T22:17:30.8949889Z  Debug Mode: false
2022-06-28T22:17:30.8950775Z  Plugins:
2022-06-28T22:17:30.8951929Z   buildx: Docker Buildx (Docker Inc., 0.8.2+azure-1)
2022-06-28T22:17:30.8952407Z   compose: Docker Compose (Docker Inc., 2.6.0+azure-1)
2022-06-28T22:17:30.8952665Z
2022-06-28T22:17:30.8953401Z Server:
2022-06-28T22:17:30.8955072Z  Containers: 0
2022-06-28T22:17:30.8955919Z   Running: 0
2022-06-28T22:17:30.8956758Z   Paused: 0
2022-06-28T22:17:30.8957580Z   Stopped: 0
2022-06-28T22:17:30.8958406Z  Images: 19
2022-06-28T22:17:30.8959540Z  Server Version: 20.10.17+azure-1
2022-06-28T22:17:30.8959898Z  Storage Driver: overlay2
2022-06-28T22:17:30.8960924Z   Backing Filesystem: extfs
2022-06-28T22:17:30.8961839Z   Supports d_type: true
2022-06-28T22:17:30.8962819Z   Native Overlay Diff: false
2022-06-28T22:17:30.8963147Z   userxattr: false
2022-06-28T22:17:30.8964540Z  Logging Driver: json-file
2022-06-28T22:17:30.8964870Z  Cgroup Driver: cgroupfs
2022-06-28T22:17:30.8965802Z  Cgroup Version: 1
2022-06-28T22:17:30.8966694Z  Plugins:
2022-06-28T22:17:30.8977465Z   Volume: local
2022-06-28T22:17:30.8978041Z   Network: bridge host ipvlan macvlan null overlay
2022-06-28T22:17:30.8978997Z   Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
2022-06-28T22:17:30.8979471Z  Swarm: inactive
2022-06-28T22:17:30.8984261Z  Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
2022-06-28T22:17:30.8984809Z  Default Runtime: runc
2022-06-28T22:17:30.8985493Z  Init Binary: docker-init
2022-06-28T22:17:30.8985958Z  containerd version: a17ec496a95e55601607ca50828147e8ccaeebf1
2022-06-28T22:17:30.8986637Z  runc version: f46b6ba2c9314cfc8caae24a32ec5fe9ef1059fe
2022-06-28T22:17:30.8987049Z  init version:
2022-06-28T22:17:30.8987597Z  Security Options:
2022-06-28T22:17:30.8987947Z   apparmor
2022-06-28T22:17:30.8988466Z   seccomp
2022-06-28T22:17:30.8988807Z    Profile: default
2022-06-28T22:17:30.8989437Z  Kernel Version: 5.13.0-1031-azure
2022-06-28T22:17:30.8989851Z  Operating System: Ubuntu 20.04.4 LTS
2022-06-28T22:17:30.8990421Z  OSType: linux
2022-06-28T22:17:30.8990774Z  Architecture: x86_64
2022-06-28T22:17:30.8991315Z  CPUs: 2
2022-06-28T22:17:30.8991658Z  Total Memory: 6.784GiB
2022-06-28T22:17:30.8992256Z  Name: fv-az163-352
2022-06-28T22:17:30.8992682Z  ID: 5542:6WF5:GY3A:NAKD:SCLY:FTGP:FDN3:KHA2:KPHH:7CPF:HW34:MIOU
2022-06-28T22:17:30.8993303Z  Docker Root Dir: /var/lib/docker
2022-06-28T22:17:30.8993671Z  Debug Mode: false
2022-06-28T22:17:30.8994222Z  Username: githubactions
2022-06-28T22:17:30.8994650Z  Registry: https://index.docker.io/v1/
2022-06-28T22:17:30.8995225Z  Labels:
2022-06-28T22:17:30.8995564Z  Experimental: false
2022-06-28T22:17:30.8996113Z  Insecure Registries:
2022-06-28T22:17:30.8996458Z   <IP_ADDRESS>/8
2022-06-28T22:17:30.8997002Z  Live Res

Prisma Version
$ npx prisma -v
Environment variables loaded from .env
prisma                  : 3.15.2
@prisma/client          : 3.15.2
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at<EMAIL_ADDRESS>Default Engines Hash    : 461d6a05159055555eb7dfb337c9fb271cbd4d7e
Studio                  : 0.462.0

I think I may have run into this with my team at work. Once we put DEBUG='*' in the environment running prisma generate we were able to see a child process exiting with SIGABRT due to an OOM error. Output follows:
><EMAIL_ADDRESS>prisma-generate
> cd ./api-v2/src/layers/prisma-graphql-server && ./scripts/prisma-generate.sh
2023-12-11T16:40:04.631Z prisma:engines  binaries to download libquery-engine, migration-engine
2023-12-11T16:40:04.637Z prisma:get-platform  Found distro info:
{
  "targetDistro": "rhel",
  "familyDistro": "rhel",
  "originalDistro": "amzn"
}
2023-12-11T16:40:04.637Z prisma:get-platform  Trying platform-specific paths for "rhel"
2023-12-11T16:40:04.638Z prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.3
2023-12-11T16:40:04.639Z prisma:get-platform  The parsed libssl version is: 3.0.x
2023-12-11T16:40:04.640Z prisma:get-platform  Found distro info:
{
  "targetDistro": "rhel",
  "familyDistro": "rhel",
  "originalDistro": "amzn"
}
2023-12-11T16:40:04.640Z prisma:get-platform  Trying platform-specific paths for "rhel"
2023-12-11T16:40:04.641Z prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.3
2023-12-11T16:40:04.641Z prisma:get-platform  The parsed libssl version is: 3.0.x
2023-12-11T16:40:04.675Z prisma:loadEnv  project root found at /builds/antage/performance-heatmap/api-v2/src/layers/prisma-graphql-server/package.json
2023-12-11T16:40:04.688Z prisma:tryLoadEnv  Environment variables not found at null
2023-12-11T16:40:04.688Z prisma:tryLoadEnv  Environment variables not found at undefined
2023-12-11T16:40:04.688Z prisma:tryLoadEnv  No Environment variables loaded
Prisma schema loaded from prisma/schema.prisma
2023-12-11T16:40:04.701Z prisma:get-platform  Found distro info:
{
  "targetDistro": "rhel",
  "familyDistro": "rhel",
  "originalDistro": "amzn"
}
2023-12-11T16:40:04.701Z prisma:get-platform  Trying platform-specific paths for "rhel"
2023-12-11T16:40:04.702Z prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.3
2023-12-11T16:40:04.703Z prisma:get-platform  The parsed libssl version is: 3.0.x
2023-12-11T16:40:04.704Z prisma:get-platform  Found distro info:
{
  "targetDistro": "rhel",
  "familyDistro": "rhel",
  "originalDistro": "amzn"
}
2023-12-11T16:40:04.705Z prisma:get-platform  Trying platform-specific paths for "rhel"
2023-12-11T16:40:04.705Z prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.3
2023-12-11T16:40:04.705Z prisma:get-platform  The parsed libssl version is: 3.0.x
2023-12-11T16:40:04.709Z prisma:getConfig  Using getConfig Wasm
2023-12-11T16:40:04.738Z prisma:getConfig  config data retrieved without errors in getConfig Wasm
2023-12-11T16:40:04.752Z prisma:getDMMF  Using getDmmf Wasm
2023-12-11T16:40:04.754Z prisma:getDMMF  Using given datamodel
2023-12-11T16:40:05.458Z prisma:getDMMF  dmmf data retrieved without errors in getDmmf Wasm
2023-12-11T16:40:05.508Z prisma:generator  prismaCLIDir /builds/antage/performance-heatmap/api-v2/src/layers/prisma-graphql-server/node_modules/prisma
2023-12-11T16:40:05.508Z prisma:generator  prismaClientDir /builds/antage/performance-heatmap/api-v2/src/layers/prisma-graphql-server/node_modules/@prisma/client
2023-12-11T16:40:05.508Z prisma:generator  baseDir /builds/antage/performance-heatmap/api-v2/src/layers/prisma-graphql-server/prisma
2023-12-11T16:40:05.510Z prisma:generator  typescriptPath /builds/antage/performance-heatmap/api-v2/src/layers/prisma-graphql-server/node_modules/typescript
2023-12-11T16:40:05.890Z prisma:GeneratorProcess  2023-12-11T16:40:05.888Z prisma:client:generator  requiredEngine: libqueryEngine
2023-12-11T16:40:07.421Z prisma:getGenerators  neededVersions {
  "8fbc245156db7124f997f4cecdd8d1219e360944": {
    "engines": [
      "libqueryEngine"
    ],
    "binaryTargets": [
      {
        "fromEnvVar": null,
        "value": "rhel-openssl-3.0.x",
        "native": true
      },
      {
        "fromEnvVar": null,
        "value": "linux-arm64-openssl-3.0.x"
      }
    ]
  }
}
2023-12-11T16:40:07.423Z prisma:get-platform  Found distro info:
{
  "targetDistro": "rhel",
  "familyDistro": "rhel",
  "originalDistro": "amzn"
}
2023-12-11T16:40:07.424Z prisma:get-platform  Trying platform-specific paths for "rhel"
2023-12-11T16:40:07.424Z prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.3
2023-12-11T16:40:07.425Z prisma:get-platform  The parsed libssl version is: 3.0.x
2023-12-11T16:40:07.426Z prisma:getGenerators  {
  generatorBinaryPaths: {
    libqueryEngine: {
      'rhel-openssl-3.0.x': '/builds/antage/performance-heatmap/api-v2/src/layers/prisma-graphql-server/node_modules/prisma/libquery_engine-rhel-openssl-3.0.x.so.node',
      'linux-arm64-openssl-3.0.x': '/builds/antage/performance-heatmap/api-v2/src/layers/prisma-graphql-server/node_modules/prisma/libquery_engine-linux-arm64-openssl-3.0.x.so.node'
    }
  }
}
2023-12-11T16:40:08.001Z prisma:GeneratorProcess  2023-12-11T16:40:08.001Z prisma:loadEnv  project root found at /builds/antage/performance-heatmap/api-v2/src/layers/prisma-graphql-server/package.json
2023-12-11T16:40:09.036Z prisma:GeneratorProcess  child exited with code null on signal SIGTERM
2023-12-11T16:40:09.151Z prisma:GeneratorProcess  2023-12-11T16:40:09.151Z prisma:getDMMF  Using getDmmf Wasm
2023-12-11T16:40:09.153Z prisma:GeneratorProcess  2023-12-11T16:40:09.152Z prisma:getDMMF  Using given datamodel
2023-12-11T16:40:09.801Z prisma:GeneratorProcess  2023-12-11T16:40:09.800Z prisma:getDMMF  dmmf data retrieved without errors in getDmmf Wasm
2023-12-11T16:43:11.721Z prisma:GeneratorProcess  <--- Last few GCs --->
2023-12-11T16:43:11.722Z prisma:GeneratorProcess  [57:0x555bede63110]   181283 ms: Scavenge 2027.5 (2085.5) -> 2023.3 (2086.5) MB, 10.4 / 0.0 ms  (average mu = 0.906, current mu = 0.845) allocation failure;
2023-12-11T16:43:11.723Z prisma:GeneratorProcess  [57:0x555bede63110]   181645 ms: Scavenge 2028.5 (2086.5) -> 2025.4 (2089.0) MB, 13.3 / 0.0 ms  (average mu = 0.906, current mu = 0.845) allocation failure;
2023-12-11T16:43:11.723Z prisma:GeneratorProcess  [57:0x555bede63110]   186198 ms: Mark-sweep 2031.1 (2089.0) -> 2022.1 (2104.5) MB, 4214.6 / 0.0 ms  (average mu = 0.691, current mu = 0.378) allocation failure; scavenge might not succeed
2023-12-11T16:43:11.724Z prisma:GeneratorProcess  <--- JS stacktrace --->
2023-12-11T16:43:11.724Z prisma:GeneratorProcess  FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
2023-12-11T16:43:11.725Z prisma:GeneratorProcess   1: 0x7f943c81816c node::Abort() [/lib64/libnode.so.108]
2023-12-11T16:43:11.725Z prisma:GeneratorProcess   2: 0x7f943c6f7b56  [/lib64/libnode.so.108]
2023-12-11T16:43:11.726Z prisma:GeneratorProcess   3: 0x7f943dbd5e14 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/lib64/libnode.so.108]
2023-12-11T16:43:11.726Z prisma:GeneratorProcess   4: 0x7f943dbd61fc v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/lib64/libnode.so.108]
2023-12-11T16:43:11.728Z prisma:GeneratorProcess   5: 0x7f943ddb34e9  [/lib64/libnode.so.108]
2023-12-11T16:43:11.728Z prisma:GeneratorProcess   6: 0x7f943ddcc153 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/lib64/libnode.so.108]
2023-12-11T16:43:11.728Z prisma:GeneratorProcess   7: 0x7f943dda6256 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/lib64/libnode.so.108]
2023-12-11T16:43:11.729Z prisma:GeneratorProcess   8: 0x7f943dda7607 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/lib64/libnode.so.108]
2023-12-11T16:43:11.730Z prisma:GeneratorProcess   9: 0x7f943dd8a923 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/lib64/libnode.so.108]
2023-12-11T16:43:11.731Z prisma:GeneratorProcess  10: 0x7f943e1b67cd v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/lib64/libnode.so.108]
2023-12-11T16:43:11.732Z prisma:GeneratorProcess  11: 0x7f943dac62b9  [/lib64/libnode.so.108]
2023-12-11T16:43:12.152Z prisma:GeneratorProcess  child exited with code null on signal SIGABRT


Add missing tree views

Reverts ManageIQ/manageiq#8959 that introduced issue #9088 . Tree views were deleted prematurely.
Fixes #9088
@miq-bot add_label ui
@h-kataria please review, thanks.

/cc @martinpovolny @himdel @mzazrivec

@ZitaNemeckova  i dont see @bottlenecks_tree or @utilization_tree being set anywhere in code, i think as a fix we should fixed the code to not try to render the views that you just restored.

@h-kataria I agree so I added those two trees back to Trello card and will look more into them soon.

  def util_build_tree(type, name)
    utilization = TreeBuilderUtilization.new(name, type, @sb)
    @right_cell_text = if type == :bottlenecks
                         _("Bottlenecks Summary")
                       else
                         _("Utilization Summary")
                       end
    instance_variable_set :"@#{name}", utilization.tree_nodes
  end

hard to find....


Create a Support-us / donate page

[x] Create a dummy page
[x] Add navlink
[x] Retrieve the data from db (for donation graph)
[x] Add donation graph (goal visualizer, kind of thing)
[x] Add cards for yt channel & zbunker prime
[x] Stylize the page

Below commits already resolved the top 5 issues:

e94222606f9be36a3a8a0787cc34b1b867d8c738
c2517c7425657f2063d626bf7c1713e4389eefed
84e655498df65738015060df5ca70bf3c8d491ef

Reopen this when you want to bring some changes. Until then, everything looks great!


WIP -feature - ok-to-test in github actions

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Implementing ok-to-test on github actions

What is the current behavior? (You can also link to an open issue here)
e2e test don't run on forks

What is the new behavior (if this is a feature change)?
should be able to run e2e on forks

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
NONE

Other information:

/ok-to-test b859565c45ba81d7300cc45d656f66e7b469fde9

/ok-to-test sha=b859565

/ok-to-test sha=7bee1a966150b9f7feca426a2d6bc718d511ec70

/ok-to-test sha=eee38e2efffaa235c99c66254f3d2980eb8e9272

/ok-to-test sha=eee38e2

/ok-to-test sha=a53d593

/ok-to-test sha=a53d593db57cb58562908262a0e7284ca14a1107


New Release old problems.

New version, old problems. When will you finally make mouse support available in third-party apps? When will there be a normal copy-paste in the editors? You are engaged in decorating when the BASIC functions are not implemented.
Why are you like this?

#376 (mouse support in Windows applications.)
You can configure copy/paste however you want
There is no need for you to be unkind. Please follow the community guidelines when submitting issues.


Error code 357 - This is the first ever episode recorded for this child, but reason for new episode is not started to be looked after.

Error information
Error code
357
Description to display
This is the first ever episode recorded for this child, but reason for new episode is not started to be looked after.
DfE Long-form description of error
If this is the first episode ever for this child, reason for new episode must be S.  Check whether there is an episode immediately preceding this one, which has been left out.  If not the reason for new episode code must be amended to S.
DfE suggested coding
First episode <RNE> must be 'S'
For further info, refer to the DfE validation document here

Duplicate of #72


feat: Provide flag for running ddev commands from any directory, not just project, for #2128

TODO

Add tests

The Issue

#2128

Currently to run a command against a project you need to cd to a directory inside that project (with exception of some select commands, which take projects as arguments).
How This PR Solves The Issue
Adds a new --project global flag.
If a project is passed to this flag, commands are run as though the user's current working directory was the project's root dir.
If the project doesn't exist, an error is thrown early.
The flag includes autocompletion of project names.
Manual Testing Instructions
Run ddev --project=<projectName> and you should see all commands available to that project in the list.
Run any of those commands, using the --project flag to run them against any project.
Change directory to one project, and then run ddev --project=<some-other-project> stop - the project you named should be stopped, but the one you're in should not be.
Automated Testing Overview

TBD
Related Issue Link(s)

#2128

Release/Deployment Notes

And custom projects with a --project flag will conflict with the new global flag.

[!CAUTION]
For some people this may be a breaking change!

@rfay In #2128 the idea of having a --root flag was mentioned. The idea is that you can change what the working directory (relative to the project root) is when running the command.
Do you want that flag added as well?
If so, do you mind what it's called? I think --working-dir is more intuitive than --root

@rfay In https://github.com/ddev/ddev/issues/2128 the idea of having a --root flag was mentioned. The idea is that you can change what the working directory (relative to the project root) is when running the command.

Do you want that flag added as well?
If so, do you mind what it's called? I think --working-dir is more intuitive than --root

It definitely doesn't have to be --root, which would be a poor choice. But I don't like --working-dir because we already have a config item for that (which is the relative working dir inside the container). How about --project-dir ?

I don't like --working-dir because we already have a config item for that (which is the relative working dir inside the container).

Isn't that exactly what the purpose of that proposed flag is for? With the exception that it's just for the one command execution and not persistent?
That seems to me like it's a perfect name since it lines up with the purpose of the config that shares the name.
Though I guess it might conflict with the config command?

How about --project-dir?

That sounds to me like it refers to the root directory of a project, so might cause confusion

Oh, that's what --root was intending (I think), the project root, the directory where .git and .ddev live.

Maybe we should start over. Every thing we're talking about here is making ddev run on the host, and giving it context about where it should operate. The two ways we're talking about doing that are giving it a project or giving it a directory to operate in. So the idea behind --root as I understand was to do the same as cd <someprojectdir> && ddev <somecommand>

Hmmm I might leave that flag out of this pr then unless you feel strongly it should be included - mostly because I'm not sure what it should even do 😅

--project makes sense because DDEV has context about what and where projects are. But running in some arbitrary directory sounds like it'd be rare enough and if you're typing out the directory anyway then why not just... cd to it 🤔

I'm OK with that, thanks.

Just a note that the overall idea here is no different from what we already do with commands that take a project arg, like ddev start project1 or ddev logs project1. It's just that we want to provide a way to do that with any command.

Rebased on principle :)

I'm not going to explore this any further - the more I look at this the more convoluted things get - and from my perspective the benefit is not worth the convolution.
Someone else is welcome to pick up where I left off if they feel inspired to do so


Spec compliant parsing of all possible ES5 identifiers

The grammar for ES5 is missing some rather rare characters that can be used as identifier names, like 䩶 (U+4A76).
It still is different from ES6 which uses the Unicode categories ID_Start and ID_Continue for identifierStart and identifierPart (those may be worth including in the ProtoBuiltInRules).
Those additional rules add some (more) complexity to the ES5 grammar and also raise the time for parsing ES5 a bit (es5bench).

Can you point me to the relevant part of the ES5 spec?

I guess the relevant part to point you to is https://es5.github.io/#x7.6 and its reference of UnicodeLetter. Our letter rule is somewhat outdated (I guess) and doesn't seem to include all the characters currently recognized under “Uppercase letter (Lu)”, “Lowercase letter (Ll)”, “Titlecase letter (Lt)”, “Modifier letter (Lm)”, “Other letter (Lo)”, or “Letter number (Nl)” (the latter not being being included in letter but in the ES5 grammar itself as unicodeCategoryNl).
We cannot parse the character mentioned above as an identifier whereas for example acorn can parse it (with the suggested changes it can).

Great, thanks for the details.
I think the best way to fix this is to update the built-in letter rule. I just tried in a bunch of languages, and the 䩶 (U+4A76) character seems to be a valid identifier in at least the following languages: Java, Rust, Ruby, Python3, C#, Go. That makes me think it makes sense for it to be in the default definition of letter.
When I last looked at this, I don't remember if there was a reason I left unicodeCategoryNl out of the built-in letter rule. I just checked, and many languages (at least Java, C#, Python3, and Ruby) seem to support identifiers that begin with the character ᛮ (U+16EE).
So, my feeling is:

"Other letter" (Lo) belongs in the built-in letter rule
"Letter number" (Nl) I'm not sure about, I could go either way but I'd lean slightly towards leaving it as-is for now
It might be a good idea to add built-in rules corresponding to Unicode ID_Start and ID_Continue, as several language grammars seem to use that (e.g. Python3, Rust). Might need slightly more investigation before we implement that though.

Sounds like a better way of doing it, @pdubroy. I will close this request and branch and submit a new one with updated Unicode rules. Thanks!