Angular 9 Lazy Loading with arrow functions no chunks and big main.js

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Description
 A clear and concise description of the problem...
Building on aot with the new arrow functions to import lazy loading modules seems breaking the lazy loading and main.js contains all of them.
🔬 Minimal Reproduction

Just create a new project with the last angular-cli version (9.1.7) and implements a lazy loading module with arrow function type importing.
🔥 Exception or Error
Build stats using arrow functions:

Build stats using # style import:

🌍 Your Environment

Angular CLI: 9.1.7
Node: 10.16.3
OS: darwin x64

Angular: 9.1.9
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.901.7
@angular-devkit/build-angular     0.901.7
@angular-devkit/build-optimizer   0.901.7
@angular-devkit/build-webpack     0.901.7
@angular-devkit/core              9.1.5
@angular-devkit/schematics        9.1.7
@angular/cdk                      9.2.4
@angular/cli                      9.1.7
@angular/http                     7.2.2
@ngtools/webpack                  9.1.7
@nguniversal/builders             9.1.1
@nguniversal/common               9.1.1
@nguniversal/express-engine       9.1.1
@schematics/angular               8.3.26
@schematics/update                0.901.7
rxjs                              6.5.5
typescript                        3.7.5
webpack                           4.42.0

Anything else relevant?

Here my build production configuration:
"production": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.prod.ts"
                }
              ],
              "optimization": true,
              "outputHashing": "none",
              "sourceMap": false,
              "extractCss": true,
              "namedChunks": true,
              "aot": true,
              "extractLicenses": true,
              "vendorChunk": false,
              "buildOptimizer": true,
              "budgets": [
                {
                  "type": "initial",
                  "maximumWarning": "5mb",
                  "maximumError": "20mb"
                }
              ]
            },

What’s the module value in tsconfig.app.json and tsconfig.json?

Same here. I just created a new project using ng new app --commit=false and chunks are not created.
Angular CLI: 9.1.7
Node: 12.0.0
OS: linux x64

Angular:
...
Ivy Workspace:

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.901.7
@angular-devkit/core         9.1.7
@angular-devkit/schematics   9.1.7
@schematics/angular          9.1.7
@schematics/update           0.901.7
rxjs                         6.5.4

tsconfig.json
{
  "compileOnSave": false,
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    "sourceMap": true,
    "declaration": false,
    "downlevelIteration": true,
    "experimentalDecorators": true,
    "module": "esnext",
    "moduleResolution": "node",
    "importHelpers": true,
    "target": "es2015",
    "lib": [
      "es2018",
      "dom"
    ]
  },
  "angularCompilerOptions": {
    "fullTemplateTypeCheck": true,
    "strictInjectionParameters": true
  }
}

tsconfig.app.json
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./out-tsc/app",
    "types": []
  },
  "files": [
    "src/main.ts",
    "src/polyfills.ts"
  ],
  "include": [
    "src/**/*.d.ts"
  ]
}

@karser, how are you creating the lazy chunks? I am unable to reproduce this issue.
Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

Here is the reproducer https://github.com/karser/angular-9-lazy-loading-issue
npm install
ng serve

There are no chunks for lazy loading modules

@karser, in your case the problem is that in app.module.ts you are statically referencing the lazy loaded modules.
|https://github.com/karser/angular-9-lazy-loading-issue/blob/4d92c7e4019b85bffd886f7daac89c4334f6464e/src/app/app.module.ts#L15-L16
The result is, that these modules will no longer be treated as lazy chunks.

Thank you @alan-agius4, I removed these modules from AppModule and lazy loading started working for me.

@ilprima, any update?

I fixed it just downloading my project again from git. Maybe it was a build cache problem


Integration.py

Description
Added deep object compare in util.py and made edits to all functions within cluster_boostrap using deep compare.
Issues Resolved
Closes issue #63, might contain other bugs, unsure.
Pull request by Miriam and Mekaeel
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@miriamcheng hey, can you re-submit this PR against the demos:docbot branch? Right now it's against demos:main

How do I do that? Is it by fixing upstream?

Closing in favor of #77, thank you!


[Jammy] Logsearch (Customer)  deployments

In order to migrate to Jammy stemcells, we want to update our Logsearch customer deployment to use Jammy
Acceptance Criteria

Logsearch customer deployment is updated to use Jammy stemcell

Security considerations
None
Implementation sketch

[ ] Create PR to update Logsearch customer development to use Jammy:  https://github.com/cloud-gov/cg-deploy-logsearch/blob/7c45f5cf6175d2374eddc008e1d85e3b81b26998/logsearch-development.yml#L98
[ ] After successful deployment triggered by merging PR, manually trigger the deployment job again and make sure it passes: https://ci.fr.cloud.gov/teams/main/pipelines/deploy-logsearch/jobs/deploy-logsearch-development
[ ] Observe health of Logsearch customer development

Visit https://logs.dev.us-gov-west-1.aws-us-gov.cloud.gov/. If it is not working, you may need to debug using the logs in the BOSH deployment VMs
Prometheus alerts
Grafana metrics (CPU, memory)

[ ] After 2 days of Logsearch customer development health, create PR to update Logsearch customer staging to use Jammy: https://github.com/cloud-gov/cg-deploy-logsearch/blob/7c45f5cf6175d2374eddc008e1d85e3b81b26998/logsearch-staging.yml#L77
[ ] After successful deployment triggered by merging PR, manually trigger the deployment job again and make sure it passes: https://ci.fr.cloud.gov/teams/main/pipelines/deploy-logsearch/jobs/deploy-logsearch-staging
[ ] Observe health of Logsearch customer staging

Visit https://logs.fr-stage.cloud.gov/. If it is not working, you may need to debug using the logs in the BOSH deployment VMs
Prometheus alerts
Grafana metrics (CPU, memory)

[ ] After 1 week of Logsearch customer staging health, create PR to update Logsearch customer production to use Jammy: https://github.com/cloud-gov/cg-deploy-logsearch/blob/7c45f5cf6175d2374eddc008e1d85e3b81b26998/logsearch-production.yml#L80
[ ] Confirm health of Logsearch customer production

Visit https://logs.fr.cloud.gov/. If it is not working, you may need to debug using the logs in the BOSH deployment VMs
Prometheus alerts
Grafana metrics (CPU, memory)

[ ] After successful deployment triggered by merging PR, manually trigger the deployment job again and make sure it passes: https://ci.fr.cloud.gov/teams/main/pipelines/deploy-logsearch/jobs/deploy-logsearch-production
[ ] Update Logsearch customer pipline to reference Jammy stemcells: https://ci.fr.cloud.gov/teams/main/pipelines/deploy-logsearch/jobs/deploy-logsearch-development/builds/1073

This was deployed successfully to prod. Closing.


Missing hardpoint features

Missing hardpoint features:

[x] Hardpoint animations when capping
[ ] HUD popup when inside a cap area (print below)
[x] Minimap doesnt show icons for the cap areas
[x] Hardpoint doesn't work on Homestead

hardpoint in general honestly needs a rewrite, code is not great

@GeckoEidechse
We can close this now I think.

No the Hud popout is still not there

Checked wrong version it is there lol


Updates from updated copier template

What does this PR do?
Updated the salt extension with the latest copier template
What issues does this PR fix or reference?
Fixes:
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.

[ ] Docs
[ ] Changelog - https://docs.saltproject.io/en/master/topics/development/changelog.html
[ ] Tests written/updated

Commits signed with GPG?
Yes
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.

Running into issue of requirements and the wrong requirements being picked,
macOS 3006 py3.10
287 2024-09-06T20:22:39.2454150Z Collecting pyyaml==5.4.1 (from salt==3006)
288 2024-09-06T20:22:39.2575540Z   Downloading PyYAML-5.4.1.tar.gz (175 kB)
289 2024-09-06T20:22:39.3598350Z   Installing build dependencies: started
290 2024-09-06T20:22:41.1692710Z   Installing build dependencies: finished with status 'done'
291 2024-09-06T20:22:41.1705500Z   Getting requirements to build wheel: started
292 2024-09-06T20:22:41.3293840Z   Getting requirements to build wheel: finished with status 'error'
293 2024-09-06T20:22:41.3328110Z   error: subprocess-exited-with-error

macOS 3007 py3.10
 287 2024-09-06T20:22:31.8550550Z Collecting pyyaml==6.0.1 (from salt==3007)
 288 2024-09-06T20:22:31.8677030Z   Downloading PyYAML-6.0.1-cp310-cp310-macosx_11_0_arm64.whl.metadata (2.1 kB)
 289 2024-09-06T20:22:32.0026300Z Collecting pyzmq==25.1.2 (from salt==3007)

And Salt 3006 for darwin (macOS) actually wants pyyaml 6.0.1 as in 3007 selection above
ci/py3.10/darwin.txt
386 pyyaml==6.0.1
387     # via
388     #   -c requirements/static/ci/../pkg/py3.10/darwin.txt
389     #   -r requirements/base.txt
390     #   clustershell
391     #   junos-eznc
392     #   kubernetes
393     #   pytest-salt-factories
394     #   yamllint
395     #   yamlordereddictloader

pkg/py3.10/darwin.txt
100 pyyaml==6.0.1
101     # via -r requirements/base.txt

This implies will need a requirements file to ensure that the correct verison is picked, since other requirements (in ci) are ensuring pyyaml 6.0.1 is getting picked for 3006, and the extension won't have those other dependencies

Here is the problem, getting the '.0' rather than the current latest shipping
3006
196 2024-09-06T20:22:28.2100380Z ^[[36mnox > ^[[34mpython -m pip install --progress-bar=off salt==3006^[[0m
197 2024-09-06T20:22:28.7334640Z Collecting salt==3006
198 2024-09-06T20:22:28.7636440Z   Downloading salt-3006.0.tar.gz (20.4 MB)

3007
196 2024-09-06T20:22:28.2100380Z ^[[36mnox > ^[[34mpython -m pip install --progress-bar=off salt==3006^[[0m
197 2024-09-06T20:22:28.7334640Z Collecting salt==3006
198 2024-09-06T20:22:28.7636440Z   Downloading salt-3006.0.tar.gz (20.4 MB)

That should be 3006.10 and 3007.1 respectively


Users can see their grants represented on their profile pages

A substantial portion of this epic story was completed during the pilot with College of Engineering in 2022. The following are the remaining tasks as we are preparing to change the source for grants.

[ ] #67
This is getting addressed in
https://github.com/ucd-library/aggie-experts/issues/143
https://github.com/ucd-library/aggie-experts/issues/144

[ ] #68

[ ] Ensure Archive Grants Feed to Elements is functional. https://github.com/ucd-library/aggie-experts/issues/223

[ ] Advocate for integration with universal identifiers such as FundRef
Initial steps https://github.com/ucd-library/aggie-experts/issues/147

Development work based on UI mock-ups: https://github.com/ucd-library/aggie-experts/issues/151
Definition of Done:

@Vensberg @wrenaria
Here's a sample of how the grants are currently displayed.

Any issues with the content you'd like addressed? I think there's still an open task related to expert titles/roles, where we're trying to determine a good way of standardizing the character case, I imagine whatever the outcome there will affect the mix of uppercase/lowercase seen here.
What should the download contain? I think it's csv right? What type of headers/data should it contain?

Nothing jumps out at me at this point. I need to think more about the type of grant, but this is a good representation as it is.

The download csv should contain
Title | Funding Agency | Grant id {the one given by the agency, not ours} | Start date | End date | Type of Grant | List of contributors (role) {separate contributors by ";"} |

Comparison of MIV fields vs the grant fields that we have
Mandatory fields
Type: Research ; Teaching and Training ; Service ; Academic Support ; Student Support ; Scholarships/ Fellowships ; Other
[Note: our categories are different Academic Support; Default; Instruction ; Research; Service / Other	]
Status: Active ; Submitted; Completed; Not Awarded ; None
[Note: our categories are only Active and Completed]
Grant/Contract/Gift Title [free text]
Amount $
Role: Principal Investigator; Co-Principal Investigator; Co-Investigator; Assistant Researcher; Collaborator; Instructor; Trainer; Other
[Note: our fields are only PI, coPI]
Non-mandatory fields

that we can supply:
Funding Agency:
Grant Number:

that we may supply with Aggie Enterprise
Total number of PIs/Co-PIs
List all PIs and Co-PIs, including yourself

That we cannot supply
Off-Campus Amount:

Either the Start Date or the Submitted/Resubmitted Date must be entered.
Start Date: ...       End Date: ...
and/or Submitted/Resubmitted Date:
Percent Effort:
URL:
Purpose/Goal of the grant:
Contributions to grant or contract:

Definition of Done:

For QC on grants I'd like an updated spreadsheet  with just the users with grants.

@Vensberg I've added this task into the current sprint, I plan to work off of this for the grant csv download.

@UcDust, there are issues with grants data, which is why they are not displaying correctly on the interface. Roger identified them and will be reuploading. After that, the data should be pulled down again and I will QA again.

@UcDust @qjhart I added some renamings that are needed to cross-walk our terminology to MIV. (See Definition of Done added to the original entry). I am not sure who would handle that.

@UcDust , @rakunkel-ucd , @qjhart , RGPO grants don't have a "type". I propose they be labeled as "Research" on import.


Extend Selection in Different "CamelHumps" Mode expands too much (e.g. generic type parameters).

Describe the bug
When 'Use "CamelHumps" words' is ON, 'Extend Selection in Different "CamelHumps" Mode' behaves differently from the IntelliJ 'Extend Selection' when 'Use "CamelHumps" words' is OFF. Specifically generic class definitions like AbstractMyClass<SomeClass>.
To Reproduce
Steps to reproduce the behavior:

Set 'Use "CamelHumps" words' to OFF, and set regular 'Expand selection' to Ctrl-W.
Add this line in a .java file:
public static class MyClass extends AbstractMyClass<SomeClass> {}
click into AbstractMyClass and press Ctrl-W twice.
Result: Only `AbstractMyClass is selected -> correct
Set 'Use "CamelHumps" words' to ON, and set 'Extend Selection in Different "CamelHumps" Mode' to Ctrl-W (click 'Remove' to remove Ctrl-W from the regular 'Expand Selection')
Open a different .java file (important)
Add this line in the different .java file:
public static class MyClass extends AbstractMyClass<SomeClass> {}
click into AbstractMyClass and press Ctrl-W twice.
Result: whole line public static class MyClass extends AbstractMyClass<SomeClass> {} is selected -> unexpected

Expected behavior
In step 7, expected only `AbstractMyClass' to be selected, not the whole line.
Screenshots
IntelliJ 'Use CamelHumps' OFF with IntelliJ 'Expand Selection' (Ctrl-W):

IntelliJ 'Use CamelHumps' ON with String Manipulation 'Extend Selection in Different "CamelHumps" Mode':

Environment :

IntelliJ IDEA 2021.2.3 (Ultimate Edition), Build #IU-212.5457.46, built on October 12, 2021
String Manipulation (<IP_ADDRESS>81.3)

Thanks!

Yes, I verified it now works correctly. Thanks!


Checkbox to compile project twice

LaTeX documents must be compiled twice to set all references correctly. If a bib is used, this will be done correctly. However, if you compile without bib, only one compilation is done at a time. There I would find a checkbox practical that should always be compiled twice.

... or just use latexmk. But for those people who cannot use it, it makes sense I think.


Update use-a-task-sequence-to-manage-virtual-hard-disks.md

Added in a note to state that the feature has been deprecated since 1710
Summarize the change in the pull request title
Describe your change, specifically why you think it's needed.
Fixes #Issue_Number (if necessary)
@Article_Author please review (look at the author metadata tag)

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

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

Looks good @sccmentor, thanks for the revision. :shipit:
#sign-off
Once merged, this should be live with the next daily publishing process. Right now that should be tomorrow (Wednesday, 19 September) around 11:00 Pacific time.


added PR Template

Fixes #40
@kartikayasijaa please review and merge this PR
Also, add labels to this PR

@Abidsyed25 please insert the correct level1 label here too
Thank you!


SWE-bench-lite failing instances inconsistent with logs

The SWE-bench_Lite_golden report states that only 2 tasks, pydata__xarray-4094 and pydata__xarray-4493, are failing evaluation. However, in the logs provided, the following 44 tasks appear to be failing evaluation:
astropy__astropy-6938
django__django-15400
matplotlib__matplotlib-22711
matplotlib__matplotlib-23299
matplotlib__matplotlib-24970
matplotlib__matplotlib-25079
matplotlib__matplotlib-25311
matplotlib__matplotlib-25332
mwaskom__seaborn-2848
pallets__flask-4045
psf__requests-1963
psf__requests-2148
psf__requests-2317
psf__requests-2674
psf__requests-3362
psf__requests-863
pydata__xarray-4094
pydata__xarray-4493
pylint-dev__pylint-7080
pylint-dev__pylint-7114
pytest-dev__pytest-5103
pytest-dev__pytest-5495
sphinx-doc__sphinx-7686
sphinx-doc__sphinx-8474
sphinx-doc__sphinx-8506
sphinx-doc__sphinx-8713
sphinx-doc__sphinx-8721
sympy__sympy-11897
sympy__sympy-12236
sympy__sympy-12454
sympy__sympy-13043
sympy__sympy-13146
sympy__sympy-13647
sympy__sympy-13773
sympy__sympy-13915
sympy__sympy-13971
sympy__sympy-14308
sympy__sympy-14817
sympy__sympy-15308
sympy__sympy-15609
sympy__sympy-16106
sympy__sympy-16281
sympy__sympy-16503
sympy__sympy-18199

Which evaluation report script are you using? I generated the report with the get_model_report function from swebench. My guess is that the failing tests aren't listed in FAIL_TO_PASS or PASS_TO_PASS?

Got it, thanks! I was simply checking for ">>>>> All Tests Passed".


batch notifications when possible

I've been running this for several days on my home installation, and it's definitely improved responsiveness when asking Siri to do something that involves multiple accessories.

I like the idea here. I'm going to leave this pending until I have some time to dig into the implementation - should get to it in the next few days.

👍 it's definitely a bit more complex than the other PRs. One thing that could probably use another pass is the thread safety. Like I said, I'm still a Java greenie, so I wasn't sure here. I used a ConcurrentMap for the pendingNotifications because that's what the other fields are. But if my understanding of synchronized it correct, all accesses to member fields are already protected by that, so we don't need to use that thread safe data structure. It made me wonder if this class started without using synchronized, and then ran in to problems, so additional thread safety measures were added without simplifying other code (see also the double-check on the set when adding a subscription).

as first: batch is very useful and actually required by HAP spec.
but im wondering whether we should reply with "EVENT" to a subscription immediately (as batch or not).
currently we have following sequence of messages (recorded from home app on mac os):
Receive GET /characteristics?id=1958124085.9
Send  HTTP/1.1 200 OK. {"characteristics":[{"value":false,"aid":1958124085,"iid":9}]}
Receive  PUT /characteristics {"characteristics":[{"aid":1958124085,"iid":9,"ev":true}]}
Send EVENT/1.0 200 OK{"characteristics":[{"aid":1958124085,"iid":9,"value":false}]}
Send HTTP/1.1 204 No Content
so,
it as first for value via characteristics and then subscriber to the same characteristic and we replay firt with EVENT and then with No Content.
according to HAP specification, we should first send "no Content" and
"When the value changes, the accessory sends .. EVENT"

This is an interesting point. Technically there's actually a race condition with how the controller gets the current value, then registers for notifications (the value could change between the initial GET, and the notification registration). While the probability is small, it goes up as the number of devices exposed on your bridge goes up, both from more devices, and for it taking longer to process these requests and responses. I read the spec when it says "When the value changes, the accessory sends .. EVENT" as emphasizing not to send EVENTs on a timer or something, but only on actual changes. Not necessarily that you shouldn't send an initial EVENT with the current state of the item.
I do agree that the first EVENT for a subscription shouldn't be sent until after we respond 204 to the request to register it.


edit comment for minimum_master_nodes config

Description
https://github.com/opensearch-project/OpenSearch/blob/6a01d2f95b7e98c601949a58b92b91e3e4022e17/buildSrc/src/main/java/org/opensearch/gradle/testclusters/OpenSearchCluster.java#L410
discovery.zen.minimum_master_nodes is only valid for opensearch 1.x.x
I think it could confuse the user, so I improved the comment.
Issues Resolved
None
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

LGTM, adding @peterzhuamazon @gaiksaya
Thank you

@peterzhuamazon hi!
can you check this pr??

Thanks for opening the PR @10000-ki but I am a bit confused here:
I think that check is only to see if (node.getVersion().onOrAfter("7.0.0")), not related to 1.x or 2.x as the change related to that is:
https://github.com/opensearch-project/OpenSearch/blob/6532caa203955e2ca55cc6f241365b0734d040f3/buildSrc/src/main/java/org/opensearch/gradle/testclusters/OpenSearchCluster.java#L399-L402
Thanks.


Sort function error with Tree table

Recently I used your thankful project. Thanks again.
In tree table with sort, something error occur
scenario is...

In tree table, first click 'sort'. (table header part)
tree Expand, Collapse doesn't work.
when I don't click sort, tree table is work. (Expand, Collapse)
(Your example code same thing happened.)

dev console message here.

I have a several choices.
the first, disable sort function in tree table. using sort function is only enable default table.
I don't know what is best choice. Is it possible to using sort in tree table?
Please commend to me. Thanks.

sort.sorter was missing sort: orderBy in the example. Fixed now. Thanks for the report. 👍


[FEATURE] Windows support of OpenTelemetry addon

Is your feature request related to a problem? Please describe
I want to collect performance metrics for Windows nodes in EKS cluster. However, the aws-opentelemetry-eks addon currently supports only linux nodes. In general, it seems to be feasible to collect metrics from windows nodes: https://aws-otel.github.io/docs/setup/build-collector-on-windows
Describe the solution you'd like
Collect performance metrics from windows nodes.
Describe alternatives you've considered
Install OpenTelemetry Collector manually on windows nodes: https://aws-otel.github.io/docs/setup/build-collector-on-windows

Thanks @schwichti We are currently working on improving the Open Telemetry Add-on overall. I will add the Windows feature to the roadmap.


Non-Versioned Dependency False Alarm

I have just pushed an update to the bfg-repo-cleaner package that addressed, among other things, the lack of a version constraint in the nuspec. However, following the update, the validator still flags the use of an non-versioned dependency. Please see attached screenshots.

Likely a bug...

https://github.com/chocolatey/package-validator/blob/a5ba39c3daf0a19ed71c6624dd1f098ffe1454b4/src/chocolatey.package.validator/infrastructure.app/rules/DependencyWithNoVersionGuideline.cs#L29
Hmmm. We do have some specs for this one...maybe not enough.

@wjk it was due to the spec not covering the scenario of only having a minimum version specified. Also to our misunderstanding of what that scenario would look like (we thought we were covering that scenario). I updated the specs to show this scenario and then fixed the code. See the linked commit.


Blog post modal mobile formatting issues

Line spacing should be reduced and code blocks still overflow horizontally (creating horizontal scroll).

Fixed!


[SILOptimizer] Handle existential_metatype in moveonlytype eliminator

Resolves: https://github.com/swiftlang/swift/issues/74628

@swift-ci please smoke test


TypeScript cannot find name 'module' in unit tests - should now be 'angular.mock.module' ?

I'm not sure exactly when this started, as I've done a few updates, but now TS complains about the line
beforeEach(module('mymodulename'));

with an error like
app/core/mymodulename-service_test.ts(12,14): 2304 Cannot find name 'module'.

I'm editing in Atom, and tslint also highlights the module as not found.

I think (please correct me if I'm wrong) that we need to change module to angular.mock.module so it will find the right 'module' to use - there's a comment in the angularjs/angular-mocks.d.ts file to that effect:

//Use angular.mock.module instead of module, as module conflicts with commonjs.

Making this change eliminated my errors.
I'll submit a PR to change these references.

Oh, interesting. Just played around with this. Looks like you have an updated version of the Angular Mock typings, which doesn't have module supported. ng-poly's old version has support for mock and angular.mock.module. I'll look into bumping the TSD versions soon.
Just be sure to update your tsd.json with the recent SHA in case other folks on your team run into issues.
Thank you for the PR!

I also found the same issue. I had module in my tests now I have to update all of them since I upgraded my angular to 1.5 They have comment below in the type definition file
//Use angular.mock.module instead of module, as module conflicts with commonjs.


SCRD-3455 and SCRD-2228 Change port and remove dayzero names

Change UI port from 3000 to 2209
Reference dayzero-* playbooks instead of installui-* playbooks

This is not yet ready for review/merge until the backend changes have been merged:
https://gerrit.suse.provo.cloud/4640
https://gerrit.suse.provo.cloud/4641

hardware-tested by installing via UI on port 2209 by manually replacing the UI, shim, ardana-service, and ansible changes after ardana-init was run.

Ready for review, but not yet ready for merge until backend changes are committed.  Of course, once the backend changes are committed, the UI will be broken until these changes are committed.

Which exact back-end change does this depend on?

Which exact back-end change does this depend on?

https://gerrit.suse.provo.cloud//#/c/4641/  and https://gerrit.suse.provo.cloud//#/c/4640/  (which has merged and you should be able to ignore if you're testing it out)

tried this out with the corresponding backend changes and it works fine on my local system, don't really have the setup to do a full C9 build to test it... I'm inclined to merge it, @GarySmith did you want to do additional testing? I see you approved it but asked afterwards about the backend changes that match

I don't want to do any more testing, but Jack's comment above said that this should not be merged until the backend change was committed. I asked him in person whether they were committed, and he indicated they were not. So, I just wanted to know what these changes are.

Note also that Jack has not removed the "Do not merge" tag, either

makes sense... 4640 has merged, but 4641 has not. I'll wait for those to land.
@jack-likes-to-code do you want to remove the "do not merge" label ?


Handle partial input.image.source data

The code assumed if input.image.source was present that the data structure would always contain url and revision properties. Those might be omitted as they're user-controlled inputs, e.g. from the ApplicationSnapshot.
If those properties were omitted then the helper function _expected_sources would return empty set as it would try to operate on undefined data, and iterating over an empty set would lead to no checks being performed.
This uses object.get instead of direct access to return a default value if the properties are missing, so that the set should be populated and the checks should fail to match.
ref: https://issues.redhat.com/browse/RHTAPBUGS-883

Codecov Report

Merging #766 (772e1c2) into main (72cff19) will not change coverage.
Report is 4 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #766   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           86        86
  Lines         3316      3324    +8
=========================================
+ Hits          3316      3324    +8

Files
Coverage Δ

policy/release/slsa_source_correlated.rego
100.00% <100.00%> (ø)

policy/release/slsa_source_correlated_test.rego
100.00% <100.00%> (ø)

I want to be sure this is safe to merge so the e2e tests don't fail if we have unpinned policy version in use somewhere. I'll convert this to draft and make modifications to the e2e tests before merging this just to be sure...

Let's wait for https://github.com/redhat-appstudio/e2e-tests/pull/829 to get merged

The change in e2e tests was merged, I think this should be risk free now.


[TASK][CHALLENGE] Support Spark Connect Frontend/Backend

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before creating

[X] I have searched in the task list and found no similar tasks.

Mentor

[X] I have sufficient knowledge and experience of this task, and I volunteer to be the mentor of this task to guide contributors to complete the task.

Skill requirements

Knowledge about Spark Connect
Knowledge about Kyuubi architecture
Knowledge about protobuf
Knowledge about grpc
Knowledge about thrift

Background and Goals
Make Kyuubi server compatible with Spark Connect protocol, so that people can use Spark Connect client to connect to Kyuubi Server.
Implementation steps

Add a new Spark Connect frontend
1.1 Add basic gRpc server as frontend
1.2 Compatible with Spark Connect protocol, see https://github.com/apache/spark/blob/master/connector/connect/common/src/main/protobuf/spark/connect/base.proto
1.3 Support ExecutePlan
1.4 Support AnalyzePlan
1.5 Support Config
1.6 Support AddArtifacts
1.7 Support ArtifactsStatus
1.8 Support Interrupt
1.9 Support ReattachExecute
1.10 Support ReleaseExecute
1.11 Serialize the protobuf based request

Add a new Spark Connect backend
2.1 Imprort Sprak-Connect-Server and rewrite SparkConnectService https://github.com/apache/spark/blob/master/connector/connect/server/src/main/scala/org/apache/spark/sql/connect/service/SparkConnectServer.scala
2.2 Deserialize response to protobuf based

Add IT

Add docs

Additional context
No response

I think this is very challenging, but I want to give it a try. Can you assign it to me and help me

sure, thank you @yehere ! This is a kind of umbrella, we can create sub issue one by one later.

This huge task could be divided into several different level tasks, feel free to go ahead ~ all your contributions will be counted eventually :)

cc @cfmcgrady

sure, thank you @yehere ! This is a kind of umbrella, we can create sub issue one by one later.

I'm also interested in it, hope to work together.

thank you @zhaomin1423 , glad to see you are interested in.

how about co-located mode with kyuubi's sparksql engine? separated service is good and basic, but also needs more resources for more spark instances.

@minyk there are in different process, just like Spark thirftserver and connect server. We are going to add a new module and new server for Kyuubi connect. We can do it together if you are interested in.

@ulysses-you hello,i'm interested with this component,hope work with you

@yaooqinn @pan3793 @ulysses-you
i found spark have package the connect module to maven repository
https://mvnrepository.com/artifact/org.apache.spark/spark-connect-client-jvm_2.13/3.4.0
can we use thoes package to simplify the code?
maybe we could provide a connectingstr to sparkSession like the code description
https://github.com/apache/spark/blob/master/connector/connect/client/jvm/src/main/scala/org/apache/spark/sql/SparkSession.scala
based spark-connect package, we can reduce grpcServer and  proto
what do you think?

I haven't had deep look at it, my current thought is,

for server part, we only need a thin gRPC layer, coping proto files and regenerating gRPC files is fine.
for engine part, we can reuse the connect-server module to simplify the code.

@ulysses-you @pan3793
Understand, I'd like to try this challenging issue, which could go on for a long time, as I need to go through the whole architecture of kyuubi-server and figure out the differences between it and spark-connect, and in the process I might have some discussions with you.
Could youe assigned this issue to me?

Just to clarify here, the intention is to support spark connect client as another connection type to the engine - so you could still use jdbc or notebook (via rest) to the same Spark engine and have all those clients to the same application?

Yes, my initial assumption is to create a 3.4-based sparkSession by providing the configuration item remote connection str and then merging it with thrift service to provide the corresponding engine(so this configuration must force a check of the spark version > 3.4, while spark-connect-client has already written sparkSession to reduce our development process), what do you think?

@tgravescs that's a good question, and we did have an offline discussion about it.
TL;DR, your assumption will be the ultimate version, but not at the beginning.
As you know the current main flow of Kyuubi is:
       ===[http]
client ===[thrift]====> Server ===[thrift]===> Engine
       ===[etc.]               ---[thrift]---> STS/HS2/Impala (we know someone implemented such a feature internally)

The engine itself is kind of a regular Spark app that basically only consumes Spark's public API, making it easily compatible with multiple Spark versions. As connect is a new feature and connect-server is not supposed to be exposed to the user directly(I suppose only gRPC API is public API in this case), pulling connect-server in the current Spark engine module directly would break the current assumption. So in the experimental phase we are going to create a dedicated engine module for the connect engine, we may call it SPARK_CONNECT(the current one is SPARK_SQL)。
Another important case is Server ===[thrift]===> Engine, currently, we use Thrift(more specifically, the HiveServer2 Thrift protocol) as the internal RPC protocol, but for connect, obviously gRPC should be used, and keep two internal RPC protocol is quite complex and redundant, we tend to create a dedicated experimental server that keeps similar architecture but rewrite the RPC implementation.
Once the PoC is completed, we can consider merging servers and engines to achieve the final vision as you said.
       ===[http]
       ===[grpc]
client ===[thrift]====> Server ===[grpc]===> Engine
       ===[etc.]               --[thrift]--> STS/HS2/Impala (we know someone implemented such a feature internally)

Maybe @yaooqinn can share more information

@pan3793 @yaooqinn @ulysses-you @tgravescs
Hello, I have analyzed the processing flow of spark-connect, as shown in the following figure.

SparkSession.builder.remote(host:port).getOrCreate() to create a SparkConnectClient(RPCClient)
spark.sql(xxx), acutually, this method is build a rpcRequest then use RPClient to process with Spark-Connect-Server
Then Spark-Connect-Server receive the request and process it with local sparkSession, finally, return the rpcResponse
The client sparkSession receive the rpcResponse will resolve it then return

As mentioned above, I believe that in the RPC request process of kyuubi based on SparkConnect, we no longer need the involvement of SparkSession, so I have designed the following process:

We will implement a KyuubiSparkConnectClient(RPCClient, based on SparkConnectClient). It will be created when we use EngineRef.getOrCreate to create a KyuubiSparkConnectEngine
Examples, like beeline, when we use beeline to execute sql, it will create a thrift request to the KyuubiSparkConnectFrontendService
The frontendService will not do any thing, just like other engine, then the frontendService will post request to KyuubiSparkConnectService(client: KyuubiSparkConnectClient)
The backendService also like other engine, it will use corresponding operation to handle the request
The operation will process like the follow
5.1 Process the thrift request and tranform it to rpc request
5.2 Call client method to process the request
5.3 Receive the rpc response from the Spark-Connect-Server
5.4 Tranform the rpc response to thrift response

Based the rpc client, we don't need create sparkSession(i.e. local environment don't need spark !!!!)
What do you think?

@pan3793 @yaooqinn Hi! Just to clarify - do I understand correctly, that for the first iteration, we need to somehow allow gRPC-based engines to coexist with Thrift ones (all current engines) in order to add the SPARK_CONNECT engine? That also means, that we will need to rewrite a significant part of the internal communication logic, includingKyuubiSession, SessionManager, etc. or decouple it from Thrift.
Or it is expected to start directly from rewriting the current internal RPC mechanism from Thrift (HS2) to gRPC and changing the internal API (kyuubi frontend server <--> engine), so that it will include logical methods from both the old API and the Spark Connect API?

currently, we use Thrift(more specifically, the HiveServer2 Thrift protocol) as the internal RPC protocol, but for connect, obviously gRPC should be used

for the first iteration, we need to somehow allow gRPC-based engines to coexist with Thrift ones (all current engines) in order to add the SPARK_CONNECT engine? That also means, that we will need to rewrite a significant part of the internal communication logic, includingKyuubiSession, SessionManager, etc. or decouple it from Thrift.

@tigrulya-exe Exactly! I'm doing some experiments in this way, and it does involve lots of refactoring work to support both Thrift and gRPC and reuse code as much as possible. I can not promise an ETA since I'm not sure how much time I can spend on this task in the next few months. But I will open a draft PR once I make the pipeline work (for example, successfully executing select 1 using a spark-connect client), meanwhile, I will separate the refactoring changes and push them to the master branch gradually.

@pan3793 great! I would like to participate in the development process :) Do you already have a list of kyuubi parts/classes/modules to refactor, so we can break this big task down into smaller parts to be able to work simultaneously?
Btw, I also noticed that there is #6412 PR, related to this issue. @davidyuan1223 Hi! Is it still active?

@tigrulya-exe I will share with you more details in the next one or two weeks.

@pan3793 great! I would like to participate in the development process, if it's possible :) Do you already have a list of kyuubi parts/classes/modules to refactor, so we can break this big task down into smaller parts to be able to work simultaneously?
Btw, I also noticed that there is #6412 PR, related to this issue. @davidyuan1223 Hi! Is it still active?

Yeah, it's active, you could see this pr #6412. We first need to verify the feasibility of this solution, but the spark-connect latest version 3.5.1 has some question, so i'm waitting for the new version 3.5.2 release(currently it's released). And i will verify the spark-connect-3.5.2 this week

@pan3793 Hi! I checked your PoC and built it locally. I tried to run some queries using pyspark and they finished successfully, nice work! Now, I suggest creating a list of tasks that are required to complete this solution. These tasks include supporting all gRPC Spark Connect API methods and refactoring the current code to seamlessly integrate the PoC. This will allow us to work simultaneously and add functionality to the master branch more quickly.
Could you please share any changes that break the current thrift-based logic and any things that need to be refactored that you noticed during the implementation of this solution, so we can use this information as a starting point?


Changing solver

I want to change the solver GLGM06 to another solver. I am currently struggling with changing it to another solver.
using LazySets, SparseArrays
using Plots, LinearAlgebra
using ExponentialUtilities, ReachabilityAnalysis
A = [0 0 1.0 0;0 0 0 1.0;0 0 0 0; 0 0 0 0]
B = [1.0 0; 0 1.0; 0 0; 0 0]
δ = 0.1;
μ = 1.05
T = 2.
P = [1.0 0 0 0;0 1.0 0 0]

X0 = Ellipsoid(ones(4), Diagonal([2.0, 0.5, 3.8, .4]))
B = [0 0;0 0;1.0 0; 0 1.0]
U = Ball2(zeros(2), μ);
prob = @ivp(x' = A*x + B*u, x(0) ∈ X0, u ∈ U, x ∈ Universe(4))
sol = solve(prob, alg=GLGM06(δ=δ), T=T);
plot(sol, vars=(1, 2), lab="R", fillalpha=0.1, layout=(1,2))
plot!(P*X0, vars=(1, 2), lab="X0", fillalpha=0.1, subplot=1)

X0=Approximations.overapproximate(X0)
U=Approximations.overapproximate(U)
prob = @ivp(x' = A*x + B*u, x(0) ∈ X0, u ∈ U, x ∈ Universe(4))
sol = solve(prob, tspan=(0.0, T), alg=GLGM06(δ=δ))
plot!(sol, vars=(1, 2), lab="R", fillalpha=0.1, subplot=2)
plot!(P*X0, vars=(1, 2), lab="X0", fillalpha=0.1, subplot=2)

Similar to https://github.com/JuliaReach/ReachabilityAnalysis.jl/issues/595
I guess that the documentation will follow, but maybe you can help me to fix this problem with ORBIT and LGG09

Just replace the keyword argument alg=GLGM06(δ=δ) with the other solver. Some comments:

For ORBIT your X0 needs to be a singleton (contain just a single state).

https://github.com/JuliaReach/ReachabilityAnalysis.jl/blob/2d4298d05c52267fb6d7505d48dcddaf9019c05c/src/Algorithms/ORBIT/ORBIT.jl#L4-L5
Btw @mforets I think "deterministic" and "proper input set" do not go together. What it means is that the solver gives you an analytic simulation, which happens to be exact for deterministic systems. For systems with "proper input set" it gives you one of the possible analytic trajectories.

LGG09 is probably the only algorithm that works with your ellipsoid initial set (maybe even that fails, I did not test it)¹. That solver requires some additional parameters. It will throw appropriate error messages if you forget them. The most important parameter is that you need to specify directions in which you want to compute the bounds of the reachable states. For example, since you want to plot the result in dimensions 1 and 2, you can get interval bounds by passing dirs=CustomDirections([[1.0, 0, 0, 0], [-1.0, 0, 0, 0], [0.0, 1, 0, 0], [0.0, -1, 0, 0]]); for interval bounds you can alternatively use the convenience parameter vars = [1, 2] here, but if you want to obtain more bounds (e.g., diagonal bounds in those dimensions), you need to use dirs as above. You can study the code in the function starting below.

https://github.com/JuliaReach/ReachabilityAnalysis.jl/blob/2d4298d05c52267fb6d7505d48dcddaf9019c05c/src/Algorithms/LGG09/LGG09.jl#L60
¹You can use other solvers if you first overapproximate X0 with another set representation (depending on the solver).

Thanks a lot, I tested ORBIT. As far as I understand it, it takes the initial state (programmed as singleton) and propagates iteratively over the system dynamics. It chooses a random input value specified the variable U (in my case a overapproximated control input, previously defined as Ball2). ORBIT only gives a random trajectory not really a reachable set (which is confusing for me in the documentation). Nevertheless thanks a lot.
using LazySets, SparseArrays
using Plots, LinearAlgebra
using ExponentialUtilities, ReachabilityAnalysis
A = [0 0 1.0 0;0 0 0 1.0;0 0 0 0; 0 0 0 0]
B = [1.0 0; 0 1.0; 0 0; 0 0]
δ = 0.1;
μ = 1.05
T = 2.
P = [1.0 0 0 0;0 1.0 0 0]

X0 = Ellipsoid(ones(4), Diagonal([2.0, 0.5, 3.8, .4]))
B = [0 0;0 0;1.0 0; 0 1.0]
U = Ball2(zeros(2), μ);
prob = @ivp(x' = A*x + B*u, x(0) ∈ X0, u ∈ U, x ∈ Universe(4))
sol = solve(prob, alg=GLGM06(δ=δ), T=T);
plot(sol, vars=(1, 2), lab="R", fillalpha=0.1, layout=(1,4))
plot!(P*X0, vars=(1, 2), lab="X0", fillalpha=0.1, subplot=1)

X0=Approximations.overapproximate(X0)
U=Approximations.overapproximate(U)
prob = @ivp(x' = A*x + B*u, x(0) ∈ X0, u ∈ U, x ∈ Universe(4))
sol = solve(prob, tspan=(0.0, T), alg=GLGM06(δ=δ))
plot!(sol, vars=(1, 2), lab="R", fillalpha=0.1, subplot=2)
plot!(P*X0, vars=(1, 2), lab="X0", fillalpha=0.1, subplot=2)

X0=LazySets.Singleton([2.0; 0.5; 3.8; .4])
U=Approximations.overapproximate(U)
prob = @ivp(x' = A*x + B*u, x(0) ∈ X0, u ∈ U, x ∈ Universe(4))
sol = solve(prob, tspan=(0.0, T), alg=GLGM06(δ=δ))
plot!(sol, vars=(1, 2), lab="R", fillalpha=0.1, subplot=2)
plot!(P*X0, vars=(1, 2), lab="X0", fillalpha=0.1, subplot=2)

X0=LazySets.Singleton([2.0; 0.5; 3.8; .4])
U=Approximations.overapproximate(U)
prob = @ivp(x' = A*x + B*u, x(0) ∈ X0, u ∈ U, x ∈ Universe(4))
sol = solve(prob, tspan=(0.0, T), alg=ORBIT(δ=δ))
plot!(sol, vars=(1, 2), lab="R", fillalpha=0.1, subplot=3)
plot!(P*X0, vars=(1, 2), lab="X0", fillalpha=0.1, subplot=3)

I try LGG09 with ellipsoid but I get an error. I guess I have to define a support function for the initial state sets...

with LGG09
I tested it like this. It computes the reach sets/flowpipes for different directions (support vectors).
abc=BoxDirections(4)
abc=DiagDirections(4)
abc=OctDirections(4)
abc=CustomDirections([[3.4, 6.3, 1.0, 0.0], [-1.0, 2.4, 2.3, 0.0], [2.1, 1.0, 1.0, 1.2], [5.3, -1.0, 1.0, 0.0]]);
X0  = Zonotope(ones(4), Matrix(0.1I, 4, 4))
U = Ball2(zeros(2), μ);
prob = @ivp(x' = Ax + Bu, x(0) ∈ X0, u ∈ U, x ∈ Universe(4))
sol = solve(prob, tspan=(0.0, T), alg=LGG09(δ=δ, template=abc))
plot!(sol, vars=(1, 2), lab="R", fillalpha=0.1, subplot=4)
plot!(PX0, vars=(1, 2), lab="X0", fillalpha=0.1, subplot=4)

For plotting a high-dimensional set (X0 in the last line) you need to manually project (the vars = (1, 2) parameter only works for the solution sets from ReachabilityAnalysis:

plot!(project(X0, [1, 2]), lab="X0", fillalpha=0.1, subplot=4)

I get warnings about an empty result with your CustomDirections, so they are probably not bounding in dimensions 1 and 2. This is tricky to get right, so maybe just use one of the other versions for abc. You can also create custom directions including the box directions (which guarantees boundedness). You can get the box directions via

collect(BoxDirections(4))

Thank you a lot !


Scheduler metrics

Add SchedulerMetricsCollector which gives ability to collect basic metrics about jobs.

Looks good. I would also add a record_submitted(job_id: &str, queued_at: u64, submitted_at: u64) method to the metrics collector so we can measure how long jobs are waiting in queue

Time for how long jobs are waiting in would be useful metric indeed, only record_submitted would not measure that. For completeness sake I added record_submitted and I suggest that we tackle 'jobs waiting in queue' in future task.


make functional router

Summary by CodeRabbit

New Features

Introduced RouterDialogBox for configuring router connections, including host URL, port, and realms.
Added RouterStateProvider and RouterToggleSwitchProvider for managing router state and toggle switch functionality.
Integrated a switch for router control and enhanced AppBar styling in the mobile home screen.

Enhancements

Improved UI elements for dynamic addition and removal of realm controllers.
Enhanced validation and server status display in the router dialog box.

Bug Fixes

Refactored startRouter function to streamline server initialization and return a Server instance directly.

@muzzammilshahid can you see if we can reduce the coderabbit npise somehow?


ApplicationGatewayKeyVaultSecretException

Hi ,
Facing this issue while running Command:
az deployment group create -g rg-bu0001a0008 -f cluster-stamp.bicep -p targetVnetResourceId=${RESOURCEID_VNET_CLUSTERSPOKE_AKS_BASELINE} clusterAdminAadGroupObjectId=${AADOBJECTID_GROUP_CLUSTERADMIN_AKS_BASELINE} a0008NamespaceReaderAadGroupObjectId=${AADOBJECTID_GROUP_A0008_READER_AKS_BASELINE} k8sControlPlaneAuthorizationTenantId=${TENANTID_K8SRBAC_AKS_BASELINE} appGatewayListenerCertificate=${APP_GATEWAY_LISTENER_CERTIFICATE_AKS_BASELINE} aksIngressControllerCertificate=${AKS_INGRESS_CONTROLLER_CERTIFICATE_BASE64_AKS_BASELINE} domainName=${DOMAIN_NAME_AKS_BASELINE} location=centralindia
Error :
{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/[sub]/resourceGroups/rg-bu0001a0008/providers/Microsoft.Resources/deployments/cluster-stamp","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ResourceDeploymentFailure","target":"/subscriptions//resourceGroups/rg-bu0001a0008/providers/Microsoft.Network/applicationGateways/apw-aks-oufhjyt6iiaoe","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"ApplicationGatewayKeyVaultSecretException","message":"Problem occured while accessing and validating KeyVault Secrets associated with Application Gateway '/subscriptions//resourceGroups/rg-bu0001a0008/providers/Microsoft.Network/applicationGateways/apw-aks-oufhjyt6iiaoe'. See details below:","details":[{"code":"0","message":"Operation returned an invalid status code 'NotFound'"}]}]}]}}
Detail Error:
{
"code": "ApplicationGatewayKeyVaultSecretException",
"message": "Problem occured while accessing and validating KeyVault Secrets associated with Application Gateway '/subscriptions//resourceGroups/rg-bu0001a0008/providers/Microsoft.Network/applicationGateways/apw-aks-oufhjyt6iiaoe'. See details below:",
"details": [
{

  "code": "0",

  "message": "Operation returned an invalid status code 'NotFound'"

}

]
}
Please let me know if more details required

Apologies for the slow reply on this. I think our recent changes have resolved this issue, including changing the deployment sequence slightly on a couple of resources and adopting the latest API versions.
I've deployed the baseline dozens of times recently and haven't run into this issue, so I'm going to consider it closed - but feel free to reopen if you see it again. Thanks!


⚠ Processors has degraded performance

In 8f82667, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 61 ms

Resolved: Processors performance has improved in cc57a96.


chore: remove some generated/deduced files

Description
As noted by @chen-keinan in https://github.com/aquasecurity/trivy-operator/pull/319#issuecomment-1184038756 and https://github.com/aquasecurity/trivy-operator/issues/207#issuecomment-1169591044 some of the generated/deduced files do not have to committed to Git. This tries to remove as much as possible, but keeping deploy/static/trivy-operator.yaml - as it is mentioned in the docs as an installation alternative using kubectl.
We can also get rid of the trivy-operator.yaml if the static installation method is updated to use kubectl with kustomize. Which will make the new command
kubectl create -k "https://github.com/aquasecurity/trivy-operator//deploy/static/?ref={{ git.tag }}". WDYT?
Note: I was unable to figure out how the integration tests were actually working before, but somehow they did. Works now also, and uses the same approach described in the contributor docs - which I think is nice.
Checklist

[x] I've read the guidelines for contributing to this repository.
[ ] I've added tests that prove my fix is effective or that my feature works.
[x] I've updated the documentation with the relevant information (if needed).
[ ] I've added usage information (if the PR introduces new options)
[ ] I've included a "before" and "after" example to the description (if the PR is a user interface change).

@erikgb looks good! couple of comments I have I see that  the script update-static.yaml.sh do not generate the static files ( rbac.yaml, config.yaml and policies.yaml) , I usually use it for dev purposes , I do not use the trivy-operator.yaml because I do not want to deploy `trivy-operator' as well (as I run it from IDE).
I think it will be great to have it as part of the script and add it to .gitignore so we  keep it out of source code.
in addition I think we also need update the contribution guide , wdyt?

I have I see that the script update-static.yaml.sh do not generate the static files ( rbac.yaml, config.yaml and policies.yaml) , I usually use it for dev purposes , I do not use the trivy-operator.yaml because I do not want to deploy trivy-operator' as well (as I run it from IDE). I think it will be great to have it as part of the script and add it to .gitignore` so we keep it out of source code.

@chen-keinan The use-case you describe is extremely easy to support with kustomize, ref. https://github.com/aquasecurity/trivy-operator/discussions/239. But we're not there yet, so I'll see what I can come up with.

in addition I think we also need update the contribution guide

What in particular do you think needs to be updated? I scanned through most of it, but couldn't find anything relevant to this.

@chen-keinan PTAL! I've done a minor modification that I think will support your local workflow.

@chen-keinan @josedonizetti The changes in this PR is now included in https://github.com/aquasecurity/trivy-operator/pull/306, so it's up to you if you want to merge this first and then https://github.com/aquasecurity/trivy-operator/pull/306 or just merge https://github.com/aquasecurity/trivy-operator/pull/306. 😄


Feature Request: Support exporting Svelte Code

Please support exporting Svelte Code.
Currently only Angular & React are supported.

Thanks for the request, @boustanihani!
Is this something you'd want to contribute?

Currently no because I'm still a beginner trying to learn svelte :)


We don't have a way to represent cluster-specific status

here yet.

https://github.com/project-chip/connectedhomeip/blob/1202bc79f8a53c0b1515851bae0b9e295c2b79fc/src/app/tests/suites/TestCluster.yaml#L3741-L3744

This issue was generated by todo-issue based on a TODO comment in 1202bc79f8a53c0b1515851bae0b9e295c2b79fc.

This works with chip-tool, and is only used in a few tests. Moving post V1.


Job is "running" while GangAllocation cannot satisfied in time for several times.

Solved by #2135


Update sbt to 1.7.1

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

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

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

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

I believe the CI failure is unrelated to this PR.


add serve command

Codecov Report

Merging #23 into master will decrease coverage by 0.39%.
The diff coverage is 52.38%.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
- Coverage   61.53%   61.14%   -0.40%
==========================================
  Files           7        7
  Lines         507      507
==========================================
- Hits          312      310       -2
- Misses        195      197       +2

Impacted Files
Coverage Δ

lib/parser.js
49.26% <52.38%> (-0.59%)
:arrow_down:

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 3dbb617...719e12b. Read the comment docs.


libnd4j: *pooling2d_bp ops can't handle different stride inputs

See the following test cases. It's failing on the last assertEquals
https://gist.github.com/AlexDBlack/f075d26ed51c74270eee8f5472bbf29a
Why?
If input and output (i.e., input to pool2d and gradient at pooling op input - input and gradI args) have different strides, the offsets won't be correct and
i.e., we're only taking into account 2 of the 3 necessary strides here.
https://github.com/eclipse/deeplearning4j/blob/923ab155837bdbd70973db5fc70362b4cbae3e60/libnd4j/include/ops/declarable/helpers/cpu/convolutions.cpp#L1866-L1873
Specifically, I think changes need to occur here:

iStep2 and iStep3 should be based on input stride - not gradI strides
the index calculation for gI (line 1925) needs to be based on gradI strides, not input strides (as it would be once iStep2/3 are updated)

For optimization, it might make sense to detect when input/gradI strides are the same and do what we currently do, and if not, do extra calculation.
I tried fixing it, couldn't get it to pass.

cc @shyrma

OK, so I'm still seeing this after @shyrma's changes... looked into it for quite a while and I have no idea why it's not passing:/
What I've checked (and everything looks fine)

The C++ implementation for both average and max pooling (multiple times, thoroughly)
My test cases (original ones posted above had an error in kernel size, but now corrected)
Multi-threading (OMP_NUM_THREADS=1 still fails - and it's consistent)
avgpool2d_bp op
Java side (op context, etc)

I've also checked on 2 different computers, same result on both...
The other weird thing is that average pooling fails with permuted input array... which isn't even used for the average pool backprop op. The strides there should make zero difference, yet somehow they leak in and change the result...

Updated test cases:
https://gist.github.com/AlexDBlack/a803cb42a225f3d7fa352b5b0a03f1ff
https://gist.github.com/AlexDBlack/f76c9bf602de5f3ec19f30a88d967a9f
Note image in the second gist... bottom row of expected is bottom right of actual 3x3 blocks... right values, wrong location.

Fixed quite a while ago.


MSON - array|enum samples wrong parsed

according to MSON spec:
https://github.com/apiaryio/mson/blob/master/MSON Specification.md#44-sample
- list: 3, 4 (enum, sample)

Is equivalent to:
- list: *3, 4* (enum)

but if you sent it to snowcrash, following blueprint:
# <API name>
<API description>

# Data Structures

## User (object)
- list1: 3, 4 (enum, sample)
- list2: *3, 4* (enum)

Result is following:
_version: "3.0"
metadata: []
name: "<API name>"
description: "<API description>\n\n"
element: "category"
resourceGroups: []
content:
  -
    element: "category"
    content:
      -
        element: "dataStructure"
        name:
          literal: "User"
          variable: false
        typeDefinition:
          typeSpecification:
            name: "object"
            nestedTypes: []
          attributes: []
        sections:
          -
            class: "memberType"
            content:
              -
                content:
                  name:
                    literal: "list1"
                  description: ""
                  valueDefinition:
                    values:
                      -
                        literal: "3"
                        variable: false
                      -
                        literal: "4"
                        variable: false
                    typeDefinition:
                      typeSpecification:
                        name: "enum"
                        nestedTypes: []
                      attributes:
                        - "sample"
                  sections: []
                class: "property"
              -
               content:
                  name:
                    literal: "list2"
                  description: ""
                  valueDefinition:
                    values:
                      -
                        literal: "*3"
                        variable: false
                      -
                        literal: "4*"
                        variable: false
                    typeDefinition:
                      typeSpecification:
                        name: "enum"
                        nestedTypes: []
                      attributes: []
                  sections: []
                class: "property"

list1 has sample atribute, list2 has no. And valueDefinition are in both cases different too

ping @pksunkara @zdne
please take a look
same result for array

As I said, this is intentional. The AST produced by snowcrash should depict what the user exactly wrote. Even though, they mean the same, they can be represented differently in the AST.
Although, there is a different bug in this too. https://github.com/apiaryio/snowcrash/issues/286

Oh sry for duplicity, issue #286 I miss.
I'm in trouble in refract AST implementation because there is no way to say if value is sample.
Except workarround, while I check last && first value for presence of asterisk, and cut them from literal.
But I mean it is really weird solution!
What do you mean about it @zdne ?

@klokane @pksunkara

The AST produced by snowcrash should depict what the user exactly wrote

Originally this was the case, yes. However as we are moving forward this should not be the case in a future. I would strongly recommend to move away from different AST for different notations of the same thing (as is the case here). Instead – in a future – both should be parsed into the same structure (refract tree). It is the task for a (future) source map to help user – if needed – to figure out whether the sample value comes from one line or multiple lines.
So I do not think this is a bug at the moment, however when we move to parsing into refract I would move away fro this practice (it will also make manipulation with the parse (refract) tree a lot easier).

@klokane as for any issues with refract implementation – can we discuss it over Slack or in person?

@zdne i mean, better will be personal with public output opened for comments

Migrated to apiaryio/drafter#638


[r19.09] aspell: add patch for CVE-2019-17544

Motivation for this change
https://nvd.nist.gov/vuln/detail/CVE-2019-17544
For master, see #71242
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@GrahamcOfBorg build aspell pidgin gtkspell2 gtkspell3


POC swift JS Core. Loading of scripts, libraries and Node Modules

Closes #
https://trello.com/c/vqRdsZQS/98-swift-node-js-complete-task-to-convert-node-js-crypto-module-into-a-swift-playground-file-poc-complete-using-a-non-minified-vers
Added a Project Directory with Playground Proof of Concept to load Javascript / Node JS modules into Swift.

@nicktaras Ah, can I say that the main thing to get it to work is to prepend the extra "namespace" (nodejs) introduced generated while building, requiring no changes to the JavaScript code and JavaScript build scripts?
context.evaluateScript("nodejs.crytpo.Cipher.toString()")

vs what we tried previously:
context.evaluateScript("CryptoJS.HmacSHA1('Message', 'Key'))")

@hboon - Yep, that's correct. Browserify was key to create the js bundle, but also expose the namespace 'node' as the entry point to the library.

@nicktaras thanks! Do we already have the JavaScript code to verify TokenScript signature so we can embed and try it out? Otherwise we can close this for now.

Hi @hboon, sorry for the late reply. Do you mean logic to check the tokenScript xml node that contains the signature?

@nicktaras the logic that extracts the signature and verify that it’s valid. I don’t know if it’s been implemented already. This is why we are doing this right? :)

Closing for now


Is there actually setup instructions someplace??

Where the heck are the instructions at?! The documentation from HASS says to go look at the appdaemon docs, the appdaemon docs say to go look at HASS docs. Specifically, at no point, ever, as far as I can tell, does any bit of top level documentation suggest where the f*** appdaemon.yaml goes... or if it's already made, in which case, where the hell to access it.  HASS is great, but the documentation sucks, frankly.  It often spends time explaining what it can do, but not how to do it, and that's really discouraging.

Hey m8 👋
Thanks for opening up an issue. However, the tone you put up in this issue; makes me not want to help you at all.
Wish you all the best.
../Frenck
(Ps this is not an Home Assistant project)

I sincerely apologize about my tone. I'm just frustrated. That's not an excuse, it's a character flaw, and I understand and respect your decision to not help me. If you choose, you may stop reading at this point, the remainder is my situation and why I'm frustrated, and a hopeful attempt at a positive outcome for my benefit and the benefit of future HASS/AppDaemon users.
I've been going around in circles attempting to figure out how to use appdaemon and i just end up back at the start looking at a page that says to check the other documentation.   It is, in general, adequate documentation -- once you find it. So maybe I should have instead said that the documentation is sometimes difficult to navigate. And this isn't an entirely baseless claim, the AppDaemon add-on is the third instance I have encountered, of what I'll call "shadow documentation", that is to say, the documentation likely exists, somewhere, it's just not immediately obvious where that is.  It's just that I would have expected to find a link within one of the first few pages to which I was exposed, about the requirements to achieve a base, connected, and operational link between Home Assistant and AppDaemon.
The add-on documentation (where the Install button is) says "Please note, the add-on is pre-configured to connect with Home Assistant." Okay, we're installed and connected. Check one and two!
Next, it says "This add-on does not configure the AppDaemon or HADashboard for you."  Oh. That kind of contradicts the previous statement, or at minimum it's a little bit confusing... unless... Oh! Okay, it configures just the connection between the two. Alright, alright that's cool. Now, check two!
Then, it states "The configuration of the AppDaemon can be found in the add-on configuration folder of this add-on." Where's that? I'm still new to Home Assistant and largely of Docker; I get the concept of containers and I understand the idea of using mount points within containers, but I'm not sure where the configuration/folder of this add-on is.  I have the File editor add-on installed, it should be there with the other configuration files, right?  Well, no. It's not there. Alright, let's look at the AppDaemon docs then.
"AppDaemon uses the /conf directory to store its configuration data." Then it goes into how to create and mount it within a container -- but we already have at least the connection between HASS and AppDaemon, so that must already be done, right?  Scan through the rest of that page, I see some path names, so let's ssh in... "ls /conf" -- doesn't exist. "ls ~/.homeassistant/" -- doesn't exist. "ls /etc/appdaemon" -- no.
So, I'm lost.   I hope you can help me and future users by clarifying the steps needed.
Thank you for all your hard work!

If you want to use File Editor:

You may need to toggle the config switch for Enforce Basepath with the Config

Ohhhhhhh!  Awesome!  Thanks!  I hope I don't overstep any boundaries here, but I have gone ahead and created a pull request which adds that tip to the add-on docs.


@callable not properly documented

In developers/fundamentals/avm-concepts/callable-functions/
It is documented that @callable is used to annotate a function as callable from outside of the contract.
This is inexact. Actually, @callable annotates a main function which handles all incoming calls and that main function routes calls. But actually you can override that main function, therefore invalidating the claim that @callable functions are actually callable and non-callable functions are not callable.
I consider this a security issue.

Hey, thanks for the issue!
While I see your point, I think the docs are primarily aimed at the simple case where new developers are using our tooling to generate the main method of their main class. If contract writers are providing their own main, then we're assuming they understand enough to interpret the Blockchain.getData() information as appropriate.
I don't think this poses a security threat, though.
@jennijuju it might be a good idea to make it explicit that the tooling that generates the main method is only activated if no main method is provided, and so new developers relying on @Callable should NOT provide a main method.

Thanks @arajasek and @fulldecent . I will add an explanation/note to make it more clearer.

Documentation is now public, adding a link :-)
https://docs.aion.network/docs/callable-functions


Foreign Key relationships not working in 4.0.1

In 4.0.1 the Foreign Keys on IBM DB2 (IBM i OS) do not show up for tables that do have foreign key relationships.

Can't reproduce.
Please clarify. You don't see foreign keys in table properties? Or no FK navigation in data results?

The foreign keys do not show up in the Database Navigator even though there are foreign keys:

I did confirm that "read table references (foreign keys) is marked:

Perhaps I might be missing something on my JDBC driver settings. Is there a way to debug what DBeaver is trying to do to retrieve the foreign keys from the database to see if perhaps an exception is happening that I don't see in the UI?

Here is what I have for driver properties:

I believe I may have found something. Here is the error log:

Looks like some problem with schema list reading.
Please post debug log (https://github.com/serge-rider/dbeaver/wiki/Log-files)

Logs.zip.zip
Attached are logs

Interesting.

What JDBC driver do you use?
Do you see any catalogs and/or schemas in database navigator?

I'm not familiar with DB2 iSeries. Is schema *USRLIB has some special meaning?

JTOpen 7.1 JDBC Driver
I do see all catalogs and schemas in database navigator.
If I knew what it is doing to try find the foreign keys I could try a few things.
*USRLIBL is the user library list. It's basically a list of schemas for my login to put in the "default" list. I'm not sure why it is even looking at that.

Well, I think it tries to find target table for foreign key and doesn't find it. That's why there are no foreign keys.
So, most likely problem is in schemas/tables reading.
I see lots of errors like this:
Catalog name (ARRTI5) found for schema 'XXXX' while schema doesn't have parent catalog
JDBC driver says that schema XXXX belongs to catalog ARRTI5 but catalog list is empty.
Do you see catalog ARRTI5 in database navigator? Is it a real catalog?
Also I see a bunch of errors Schema '*USRLIBL' not found.
This happens when DBeaver searches for FK target tables. Driver says that target table belongs to schema '*USRLIBL' but there is no such schema.

ARRTI5 is the "database name". Inside that database contains many Schemas.
I'm not sure why *USRLIBL is saying it is a schema.
What query is it trying to use to find foreign keys? select * from  SYSIBM.SYSRELS or SYSIBM.SYSFOREIGNKEYS?

Is there only one database? Could you post a screenshot of database navigator?
It looks like driver mixes schemas and catalogs. In some cases it reports correct schema name, in others it returns catalog (database) name instead of schema.
I can't say what exactly SQL query executed to read metadata. DBeaver uses JDBC driver API to read this information for DB2 iSeries.
I'll try to make some workaround. Or at least add some extra logging.

I found that 3.8.3 works correctly. Attached is log from 3.8.3.
3.8.3 debug logs.zip
I'm going to make connection information and settings exactly same in 3.8.3 and see if I can end up breaking it in 3.8.3 as well. Perhaps there is some combination of settings that messes it up.

So you can see foreign keys in 3.8.3?
Are you 100% sure that you use the same driver version? There are too many differences in these logs.

It is the same driver version. I found the setting in the JDBC driver that causes this.
If you have metadata source = 0, this problem starts occuring.
If you leave metadata source = -1 (default value) then the problem doesn't occur.
Now the question is what why that settings causes the foreign key lookup to break. Is there some JDBC driver verbose logging flag to turn on somewhere?

I just noticed something. The recommended JTOpen driver that DBeaver installs is 7.1, latest version is 9.2.
Trying to see if an update to JTOpen fixes this issue.

Hmm. DBeaver uses Maven artifact for iSeries drivers (jtOpen).
Currently it is dk.kewill.thirdpartymavencentral:jt400-full.
Probably it should be changed on net.sf.jt400:jt400. It has the most recent jtOpen version (9.2).
Could you test it? If it'll work Ok then I'll change default configuration in the next DBeaver version.

Updated to net.sf.jt400, that does have the latest version.
But error still occurs in that version.
I'm not sure where I should report this, to JTOpen folks, and if so what would I say to them for this?

Ok. But what's the point in setting "metadata source" to 0?
As I understood everything is fine with default value.

Interesting. A value of "1" in the metadata source property works as well. So it can be -1, or 1. But not 0.
The problem is, if you leave it at 1 or -1 you loose ability to get column text descriptions. Which I have enabled (feature you added a month or so ago, which is awesome!)

http://javadoc.midrange.com/jtopen/index.html?com/ibm/as400/access/doc-files/JDBCProperties.html
Metadatasource 0 uses the old mechnism to get column titles. I'm guessing I should be using 1, which is the "newer" method to get column descriptions. But not entirely sure. I tried 1 and it doesn't work.

In order to give them more information can you tell me what function in the JDBC driver you are calling to get column comments?

The standard one.
JDBC API function DatabaseMetaData.getColumns, column REMARKS.

Thanks, and which function are you calling to get Foreign keys?

DatabaseMetaData.getImportedKeys

Great, thanks!

Closing issue as it appears to be JTOpen issue.

I think I should reopen this.
I did a bit more digging, and setup the same JDBC connection properties with SQL Workbench, and it is able to show the comments AND foreign keys without issue.
Is it possible to put in more logging statements to find out where this error is happening?
I turned on JDBC tracing and it seems like this might actually be occuring somewhere in DBeaver as shown in the follow log that includes the JDBC trace data.
Look at line 6725. Those errors are not actually coming from JDBC, but rather DBeaver is having a hard time interpreting the results coming back from the JDBC driver.
What I believe is happening, is that for some reason the JDBC driver is returning a schema DBeaver is not expecting. Rather than ignoring it and moving on, it errors and stops processing, and thus no foreign keys are displayed.
Here is a link to the logs: https://drive.google.com/open?id=0B__g7EhWQEETM08tN08wcFJyeU0

Unfortunately logs do not contain anything new. Still the same errors about schema *USRLIBL.
I'm pretty sure that I can make it work but I need to know metadata structure. It obviously differs from what DBeaver expects (and most likely isn't JDBC compliant). But almost any metadata, even corrupted, can be loaded with some workarounds.
I can give you JDBC dumper utility which will tell what exactly is returned by jtOpen driver. Then you can send me this log. Write me on<EMAIL_ADDRESS>(I believe your detailed schema information isn't public).

Fix committed. Actually it is a bug in jtOpen driver (wrong FK schema) so this fix is a workaround.
You can test it in EA version (http://dbeaver.jkiss.org/files/ea/).

Agreed, I will update jtopen bug with more info so they can fix it
Matt

On Mar 2, 2017, at 1:27 PM, Serge Rider<EMAIL_ADDRESS>wrote:
Fix committed. Actually it is a bug in jtOpen driver (wrong FK schema) so this fix is a workaround.
You can test it in EA version (http://dbeaver.jkiss.org/files/ea/).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

So, does it work now?

Sorry for the late reply. The EA version does fix the issue. Thank you so much!


Help me ps

Hello, I use a translator to write right away.... When I open the bot for some reason, it constantly goes out and enters, does not do other actions. In the console writes
Stored settings to config!
Lost, wait count :0
Lost, wait count :1
Lost, wait count :2
Lost, wait count :3
so indefinitely, please tell me how to fix the error
PLS😥

Switch game language to english.

Hello, I want to add pawns to the bot and levels that are not there, can you tell me how? I would also like to change the time of pressing the call, it takes a long time, please explain how to do it. My thanks in advance

Четверг, 18 мая 2023, 14:03 +03:00 от Andrey Belov @.***>:

Switch game language to english.
—
Reply to this email directly,  view it on GitHub , or  unsubscribe .
You are receiving this because you authored the thread. Message ID:  <AxelBjork/Rush-Royale-Bot/issues/66/1552893110 @ github . com>

--
Лев Колмык
Отправлено из Почты  Mail.ru


pyproject: use poetry-core instead of poetry

The PEP517 backend for poetry has been extracted in a separate package as per https://pypi.org/project/poetry-core/

Thanks!


Jesse: Watch www.yourotherfrontdoor.com

Jesse requests the watch of the watch_keyword www\.yourotherfrontdoor\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

www\.yourotherfrontdoor\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


🐛 Crash when pixelFormat="yuv"

What's happening?
Why crash when set prop pixelFormat="yuv" if remove these prop work fine but is needed for frameProcessor for process image in ML Kit
Reproduceable Code
{device != null && isActive && (
        <PinchGestureHandler onGestureEvent={onPinchGesture} enabled={isActive}>
          <Reanimated.View style={StyleSheet.absoluteFill}>
            <TapGestureHandler onEnded={onDoubleTap} numberOfTaps={2}>
              <ReanimatedCamera
                ref={camera}
                style={StyleSheet.absoluteFill}
                device={device}
                format={format}
                fps={fps}
                hdr={enableHdr}
                lowLightBoost={device.supportsLowLightBoost && enableNightMode}
                isActive={isActive}
                onInitialized={onInitialized}
                onError={onError}
                enableZoomGesture={false}
                animatedProps={cameraAnimatedProps}
                enableFpsGraph={true}
                photo={true}
                video={true}
                audio={hasMicrophonePermission}
                frameProcessor={frameProcessor}
                //pixelFormat={"rgb"}
                pixelFormat={'yuv'}
              />
            </TapGestureHandler>
          </Reanimated.View>
        </PinchGestureHandler>
      )}

Relevant log output DEBUG
{ [session/camera-has-been-disconnected: [session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: UNKNOWN_CAMERA_DEVICE_ERROR]
                                                                                name: 'session/camera-has-been-disconnected',
                                                                                _code: 'session/camera-has-been-disconnected',
                                                                                _message: '[session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: UNKNOWN_CAMERA_DEVICE_ERROR',
                                                                                _cause: undefined }

Relevant log output RELEASE
Exception java.lang.IllegalArgumentException: getCameraCharacteristics:1043: Unable to retrieve camera characteristics for unknown device 2: No such file or directory (-2)
  at android.hardware.camera2.CameraManager.throwAsPublicException (CameraManager.java:1750)
  at android.hardware.camera2.CameraManager.getCameraCharacteristics (CameraManager.java:793)
  at com.mrousavy.camera.core.CameraDeviceDetails.<init> (CameraDeviceDetails.kt:26)
  at com.mrousavy.camera.CameraDevicesManager.getDevicesJson (CameraDevicesManager.kt:63)
  at com.mrousavy.camera.CameraDevicesManager.sendAvailableDevicesChangedEvent (CameraDevicesManager.kt:71)
  at com.mrousavy.camera.CameraDevicesManager$callback$1.onCameraUnavailable (CameraDevicesManager.kt:44)
  at android.hardware.camera2.CameraManager$CameraManagerGlobal$7.run (CameraManager.java:2529)
  at android.os.Handler.handleCallback (Handler.java:942)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at android.os.Looper.loopOnce (Looper.java:226)
  at android.os.Looper.loop (Looper.java:313)
  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:228)
  at java.lang.Thread.run (Thread.java:1012)

Device
Samsung Galaxy S21
VisionCamera Version
3.6.4
Can you reproduce this issue in the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[ ] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

I'm also running into this on a Galaxy A14.

I'm also running into this on a Galaxy A14.

mmmm, that works in some phone devices but in others crash....

Why pixelFormat="native" is data Inaccessible in frame processor ??? or it's possible??, if yes, how can I access to that data??

@mrousavy Please!

You tell me if fix that if no I downgrade to V2 because I need a HOTfix urgent

Well, I guess nobody here is responsible for your app crashing like ***.
Stop whining and do something to fix YOUR app.

Well, I guess nobody here is responsible for your app crashing like ***.
Stop whining and do something to fix YOUR app.
Edit: I do remember mrousavy offer paid services of fixing stuff like this, I think you can contact him if you really need such services.

It only fails due to the update of this library, I had v3rc2 with worklets in its infancy and it did not have the errors that I have now,
1.- YOU!? Have you done something to fix it!??, because that's what I do at least so that the OPEN source library listens well brother OPEN code!!!
2.-

@R4tch3t  can you ping me on discord? please join discord community if you are not already in it, and ping me.  i also need to solve that problem, but i don't have a samsung device right now, maybe we can jump in a pair programming session and figure that out

pixelFormat="native"

unfortunately native format can't be read by a frame processor since the layout is private :(

@R4tch3t fyi https://github.com/mrousavy/react-native-vision-camera/pull/2108
can you run the example app from this PR with pixelFormat set to yuv?

@R4tch3t

You tell me if fix that if no I downgrade to V2 because I need a HOTfix urgent....

If you need something "urgent" then pay me to fix it instead of posting spanish screenshots without context.
Also, you checked that you browsed the github repo for duplicates, but there is literally another issue with almost exactly the same title, lol.
Closing as duplicate of https://github.com/mrousavy/react-native-vision-camera/issues/1947.

Thanks @rodgomesc & @zzz08900 for helping out here ❤


linkifyjs/html converting first letter to lowerCase

I have this information saved on my DB
{
    "_id" : "123",
    "user_id" : "123",
    "body_raw" : "$xyz",
    "body" : "<ReactComponent tag=\"xyz\" /> www.github.com",
}

and i have this code to run on each record on my collection
    doc.body = linkifyHtml doc.body,
      target     : '_blank'
      tagName    : 'ReactComponentUrl'
      ignoreTags : ['ReactComponent']
      className  : null
      validate   : email : off

and the result of this is
<reactComponent tag="xyz" /> <ReactComponentUrl href="www.github.com" target="_blank">www.github.com</ReactComponentUrl>

Strange why is lowering the first letter even when i ignore that tag.
Is  there a way to achieve that?
I'm using a react parser to load the components dynamically, like the one ReactComponent

Fixed in v3


from mmdet.core import wrap_fp16_model

ImportError: cannot import name 'wrap_fp16_model' from 'mmdet.core' (/home/fan/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmdet/core/init.py)
Hi, I got this error when i try to run the test.py How can i fix this

Hi @tangentninety , as mentioned by @filaPro , this import problem should have been fixed in mmcv/mmdet. Please check the version of mmcv and mmdet, and then recompile mmdet3d with the latest installed mmcv and mmdet. Otherwise, the old built/compiled files may trigger errors.

Feel free to reopen it if there is any further question.


How set sledOnline parameter?

I also wonder what this setting is used for... I got this "key" information from mDNS packets I get when I change the state of the Sonoff mini switch V2 . with 3.5.0 firmware...
in the info, they suggest to monitor the TXT message from mDNS.. this allows for receiving information when the external switch is used without tosmatizing the device.
"data1={"switch":"off","startup":"stay","pulse":"off","**sledOnline":"on**","fwVersion":"3.5.0","pulseWidth":2000,"rssi":-67}"


Pass a string to scanBlueprints instead of an array

Hi Elliott, looks like there's an issue caused by the plugin in Admin 1.1, opened here: https://github.com/getgrav/grav-plugin-admin/issues/664
This PR fixes it.

Thanks!


chore: typo onErrorBoundaryHandler

Codecov Report

Merging #745 (fcc7710) into release-next (7d10c1e) will increase coverage by 0.05%.
The diff coverage is 80.00%.

@@               Coverage Diff                @@
##           release-next     #745      +/-   ##
================================================
+ Coverage         46.36%   46.42%   +0.05%
================================================
  Files                52       52
  Lines              1320     1314       -6
  Branches            272      271       -1
================================================
- Hits                612      610       -2
+ Misses              708      704       -4

Impacted Files
Coverage Δ

packages/platform-loader/src/TraverseImport.js
88.23% <ø> (ø)

packages/plugin-rax-pha/src/manifestHelpers.js
0.00% <0.00%> (ø)

packages/plugin-rax-app/src/base.js
91.89% <62.50%> (-8.11%)
:arrow_down:

packages/plugin-rax-app/src/constants.js
100.00% <100.00%> (ø)

packages/plugin-rax-app/src/index.js
96.96% <100.00%> (+0.19%)
:arrow_up:

packages/plugin-rax-app/src/setBuild.js
100.00% <100.00%> (+6.81%)
:arrow_up:

packages/plugin-rax-app/src/setDev.js
84.45% <100.00%> (+1.95%)
:arrow_up:

packages/plugin-rax-miniapp/src/index.js
58.82% <100.00%> (+0.61%)
:arrow_up:

packages/rax-babel-config/src/index.js
90.47% <100.00%> (ø)


Cannot access 'org.apache.avro.specific.SpecificRecord' which is a supertype of...

Hi there. I'm re-opening this issue because I have recently encountered it in a multi-Kotlin/Gradle project setup.

Some context:
I have a module that generates a client from an Avro schema, and it's working fine, but when I try to access this dynamically generated client from my Kotlin client code, it says that:

Supertypes of the following classes cannot be resolved. Please make sure you have the required dependencies in the classpath: ... classes where I'm using Avro's models
Cannot access 'org.apache.avro.specific.SpecificRecord (or many others)' which is a supertype of 'ExampleAvroModel'. Check your module classpath for missing or conflicting dependencies.
Type argument is not within its bounds: should be subtype of 'SpecificRecordBase' - in case I was extending some type
...

Environment:

Gradle 8.0
Kotlin 1.8.0
Java 17
Apache Avro 1.11.1
Gradle-Avro Plugin 0.20.0
gradle.plugin.avro-base 1.6.0
Apple M1 Max. Ventura 13.2.1

Example:
interface IKafkaConsumer<T : SpecificRecordBase>  {}

class UserResponseListener(
    private val userResponseMessageListener: userResponseMessageListener,
    private val userMessagingDataMapper: UsertMessagingDataMapper

) : IKafkaConsumer<MessageResponseAvroModel> {

    @KafkaListener(id = "\${placeholder}")
    override fun receive(@Payload messages: List<UserResponseAvroModel>) {
        messages.forEach {
                    when (it.profileStatus)
                     //                ⬆

Cannot access 'org.apache.avro.generic.GenericContainer' which is a supertype of 'UserResponseAvroModel'. Check your module classpath for missing or conflicting dependencies

I suspect that your issues aren't really to do with the plugin, but rather likely dependency configuration or something Kotlin specific. To check whether it's actually the plugin do the following:

Remove the plugin from your project
Generate Java source files from your Avro files using the Apache Avro Tools command line utilities
Put the generated source files under src/main/java or the equivalent in the project where you had been using the plugin
Run the build

If you still get the problem, it's not the plugin. If it works fine, then it's probably the plugin.
Further explanation of how to use Apache Avro Tools can be found here: https://www.michael-noll.com/blog/2013/03/17/reading-and-writing-avro-files-from-the-command-line/

This project is now end-of-life (donated to the Apache Avro project).


fix(react-email): Watcher for subfolders

In the current version (1.7.2), if you were to change a file in (for example) emails/components the watcher would not copy that file to the correct location. This pr fixes this behaviour, see pictures below:
Before changing header.tsx:

After changing header.tsx (old flow):

After changing header.tsx (new flow):

Excellent. This would fix an issue I am having as well.

@bastiaanv Nice, thanks ❤


Generate,Edit,View invoice: UI enhancement

Notion :
https://www.notion.so/saeloun/Generate-Invoice-UI-page-enahcement-385ca68e718e4e13b992902b73777ceb?pvs=4
What :

UI updated for invoice details section on the view invoice page.
UI updated  invoice details section on  the generate invoice page and the edit invoice page.
Updated customInputText common component

Why :

Too much empty space
Bad UI

Preview :

Todos (for testing):

Checked with designs: https://www.figma.com/file/4gdPDRPqGqQqPYsO3Qj8CG/Miru-App?node-id=12636%3A204676&t=vS6Vu8lfZxHq29aP-4

@supriya3105 Here date format is coming from the backend. In designs it is different. should I hardcode it?

@Shruti-Apte The date format should come from the backend.

@Shruti-Apte The date format should come from the backend.

@supriya3105 Yes, It is coming from backend but format is not matching with the designs.

@Shruti-Apte What format are we getting from the backend and what is in the designs ?

@Shruti-Apte What format are we getting from the backend and what is in the designs?
coming from backed MM-DD-YYYY
Designs: MM.DD.YYYY

you can see the difference in view invoice page screenshot and generate invoice page.

@Shruti-Apte What format are we getting from the backend and what is in the designs?
coming from backed MM-DD-YYYY
Designs: MM.DD.YYYY

you can see the difference in view invoice page screenshot and generate invoice page.

@Shruti-Apte Please go ahead with what is coming from the backend. Akash will update the designs .

Merging the PR as it will cause conflict in time PR #1140


New Feature: Enable/Disable Roles

Description
This PR allows enabling/disabling roles. By default all the existing roles are set as 'enabled'.
New APIs created:

enableRole
disableRole

The listRoles API is extended to support a new parameter: state.
Fixes: #8460
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):

How Has This Been Tested?
Create a role, verify role is enabled
Disable role
Add account, verify the disabled role is not listed
How did you try to break this feature and the system with this change?

@blueorangutan package

@nvazquez a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 10701

@blueorangutan package

@nvazquez a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 10708

@blueorangutan package

@nvazquez a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✖ debian ✔ suse15. SL-JID 10711

@blueorangutan test

@nvazquez a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

Both APIs basically do the same thing, they just toggle the same attribute. We should have a single API for this feature, we could call it setRoleState for example.

@JoaoJandre thanks you are right, I even thought on including it as part of the updateRole API but kept it separate following the same pattern for accounts and users, but I'm fine with the unified approach as well

@JoaoJandre can we address the unification of the enable/disable APIs for roles along with accounts and users in a separate PR? Possibly there could be other resources following the same pattern that we could investigate and unify

@JoaoJandre can we address the unification of the enable/disable APIs for roles along with accounts and users in a separate PR? Possibly there could be other resources following the same pattern that we could investigate and unify

@nvazquez I'm ok with the idea. However, we still do not have a proper mechanism for deprecating/changing API's names (see https://github.com/apache/cloudstack/discussions/8970). The discussion has died out a bit, but I think it's still worth it to try to create a consensus on how to do this, vote it and establish as a practice on the project.
Going back to your idea, currently, as we do not have a clear way of changing API names or removing APIs, I would prefer if we introduced these APIs as one consolidated API from the beginning.

@JoaoJandre can we address the unification of the enable/disable APIs for roles along with accounts and users in a separate PR? Possibly there could be other resources following the same pattern that we could investigate and unify

@nvazquez I'm ok with the idea. However, we still do not have a proper mechanism for deprecating/changing API's names (see #8970). The discussion has died out a bit, but I think it's still worth it to try to create a consensus on how to do this, vote it and establish as a practice on the project.
Going back to your idea, currently, as we do not have a clear way of changing API names or removing APIs, I would prefer if we introduced these APIs as one consolidated API from the beginning.

@JoaoJandre I would prefer we do not introduce a new pattern for related entities unless we are sure we will address all of them. I think it is best to leave this PR as is, as it adheres better to related code/interfaces. I don't want to be strict in this perspect but @nvazquez ' argument makes sense to me.