[SPARK-34795][SQL][TEST] Adds a new job in GitHub Actions to check the output of TPC-DS queries

What changes were proposed in this pull request?

This PR proposes to add a new job in GitHub Actions to check the output of TPC-DS queries.
NOTE: I've checked that the new job took 17m 35s in the GitHub Actions env.
Why are the changes needed?

There are some cases where we noticed runtime-realted bugs after merging commits (e.g. .SPARK-33822). Therefore, I think it is worth adding a new job in GitHub Actions to check query output of TPC-DS (sf=1).
Does this PR introduce any user-facing change?

No.
How was this patch tested?

The new test added.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136227/

NOTE: I saw the Xiao's comment in the recent release process and then I made this PR.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40809/

cc @wangyum , @HyukjinKwon because @wangyum made this attempt already before.

https://github.com/apache/spark/pull/31303

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40809/

Yea, but this PR is not for the benchmark purpose.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40809/

I prefer to have this in GA ... cc @wangyum who should be the best person to review.
cc @cloud-fan too

+1 to have this check!

NOTE: I'm checking if the result in the golden files is correct query-by-query.

Test build #136296 has started for PR 31886 at commit 4185e73.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40878/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40878/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40878/

Test build #136296 has finished for PR 31886 at commit 4185e73.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136296/

Test build #136307 has started for PR 31886 at commit 582c480.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40889/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40889/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40889/

Test build #136307 has finished for PR 31886 at commit 582c480.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136307/

Test build #136323 has started for PR 31886 at commit 7738415.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40905/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40905/

Test build #136323 has finished for PR 31886 at commit 7738415.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136323/

okay, @dongjoon-hyun ~ After I finish checking all the TPCDS query results, I'll do that (I'm still checking them)

Test build #136403 has started for PR 31886 at commit 20f9e64.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40987/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40987/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40987/

Test build #136403 has finished for PR 31886 at commit 20f9e64.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136403/

Split off the unrelated part from this PR: https://github.com/apache/spark/pull/31946

Test build #136457 has started for PR 31886 at commit 41101ba.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136457/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41041/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41041/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41041/

Test build #136483 has started for PR 31886 at commit f60a7c4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41067/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41067/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41067/

Test build #136483 has finished for PR 31886 at commit f60a7c4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136483/

Test build #136509 has started for PR 31886 at commit 4eab893.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41094/

Test build #136509 has finished for PR 31886 at commit 4eab893.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41094/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136509/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41094/

Test build #136519 has started for PR 31886 at commit c8c103d.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41104/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41104/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41104/

Test build #136519 has finished for PR 31886 at commit c8c103d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136519/

Test build #136542 has started for PR 31886 at commit fc16a02.

Test build #136542 has finished for PR 31886 at commit fc16a02.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 protected case class QueryOutput(sql: String, schema: String, output: String)

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136542/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41126/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41126/

Test build #136546 has started for PR 31886 at commit e585821.

Test build #136551 has started for PR 31886 at commit 8f30a24.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41130/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41131/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41130/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41131/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41130/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41131/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136546/

Test build #136560 has started for PR 31886 at commit e5428d0.

Test build #136567 has started for PR 31886 at commit 3787f2c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41144/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41144/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136567/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41144/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136551/

Test build #136568 has started for PR 31886 at commit 267dbed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41151/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41152/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41152/

Test build #136560 has finished for PR 31886 at commit e5428d0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41151/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41152/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136560/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41151/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136568/

okay, ready to review. cc: @dongjoon-hyun @HyukjinKwon @wangyum

I support this one but it would be great if this gets some reviews from @wangyum.

I didn't check the result one-by-one. Feel free to proceed to merge when you think this PR is enough, @maropu , @HyukjinKwon , @wangyum .

Test build #136675 has started for PR 31886 at commit 2d891e9.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41257/

Test build #136678 has started for PR 31886 at commit 0a19585.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41257/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41260/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41260/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41260/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41257/

Test build #136675 has finished for PR 31886 at commit 2d891e9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136675/

Please wait me a few hours. I will verify the result first.

Test build #136678 has finished for PR 31886 at commit 0a19585.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

@wangyum, don't worry. There are few more issues to address (https://github.com/apache/spark/pull/31886#discussion_r603307756). It will take more.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136678/

Test build #136715 has started for PR 31886 at commit 841005c.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136715/

Thanks, @HyukjinKwon @wangyum . Merged to master.

If someone finds the failure of the new GA job, please let me know. cc: @dongjoon-hyun @cloud-fan @viirya @gatorsmile

After we resolve the pending issues on databricks/spark-sql-perf, I'm planning to add this job into branch-3.1./3.0, too.

Thanks @maropu.

Thanks @maropu

This is awesome! We should do it 5 years ago. :-)


List Widget with nested fields creates nonfunctional UI in CMS

- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
After configuring a collection based on the YAML in the docs, with a list widget and nested fields, the UI renders a form with nonfunctional fields. The labels do not render, I am only able to enter a single character in the form fields.

- If the current behavior is a bug, please provide the steps to reproduce.
Configure a list widget item with a single sub-field.
- What is the expected behavior?
The UI should render labeled form fields that accept more input than a single character.

- Please mention your versions where applicable.

Netlify CMS version: 2.0.9
Browser version: Chrome 67
Operating System: mac OS
- Please link or paste your config.yml below if applicable.
backend:
  name: github
  repo: aliemteam/aliemcards_cards
  branch: netlifycms
publish_mode: editorial_workflow
media_folder: "cards/media"
public_folder: "media"
slug:
  encoding: "ascii"
  clean_accents: true
collections:
  - name: "cards" # Used in routes, e.g., /admin/collections/blog
    label: "Cards" # Used in the UI
    folder: "/cards" # The path to the folder where the documents are stored
    create: true # Allow users to create new documents in this collection
    slug: "{{slug}}" # Filename template, e.g., YYYY-MM-DD-title.md
    fields: # The fields for each document, usually in front matter
      - {label: "Title", name: "title", widget: "string"}
      - {label: "Created", name: "created", widget: "string"}
      - {label: "Updated", name: "updated", widget: "string", required: false}
      - {label: "Categories", name: "categories", widget: "list"}
      - label: "Card Authors"
        name: "authors"
        widget: "list"
        field:
          - { label: "Name", name: "name", widget: "string" }
      - {label: "Body", name: "body", widget: "markdown"}

Seems related to #1139 and #1574.
Making field plural to fields causes error: TypeError: e.get is not a function triggered by immutable.js according to console.

A workaround for my use case would be to allow custom delimiters for the list widget.

Hoping #1395 will fix this.

Same issue on gatsby

This was addressed in 2.1.2.


Inability to remove dates out of range in DatePanel

We are writing a booking system that requires the users to book, say 1 week in advance, the minDate prop is really convenient and adopting it is a smooth process.
However in some situation where such dates must be changed within the last week, the "invalid" dates doesn't show up in either the DatePanel or the DatePicker and they cannot be removed. On a sidenote it's a good thing that the picker doesn't automatically remove old dates; otherwise there'll be data loss.
My thought is to still show them in the DatePanel and allow only removal so out of range dates can still be displayed/saved if they're already there but not added.

If I understand correctly, you want to display dates that are outside the min/max date in the calendar & datepanel.
To do this, you can set the onlyShowInRangeDates prop to false.
Please try it and let me know if its work or not.
<DatePicker
   onlyShowInRangeDates={false}
/>

If I understand correctly, you want to display dates that are outside the min/max date in the calendar & datepanel.
To do this, you can set the onlyShowInRangeDates prop to false.
Please try it and let me know if its work or not.
<DatePicker
   onlyShowInRangeDates={false}
/>

Yup, it worked perfectly :)
Closing this issue now


Maintaining partial selection on parent when all chlidren are selected

I have a requirement that if a parents children are selected, then the parent should take the partial, '-', selection state. This partial state should apply to its ancestors as well. Is this possible with SlickGrid?
As an example, this is what I need.
parent1(-)
parent2(-)
child1(-)
child2(x)
child3(x)
What has happened here is that both child2 and child3 were selected. So their parent, parent2 should take the partial state along with its parent, parent1. This should only occur when the children are selected. When the parent is selected, all children should be selected and the parent should be fully selected (x).
Thanks

Have a look here: https://github.com/6pac/SlickGrid/issues/165
This repo is no longer maintained.


Added README.md for House Price Prediction

Related Issues or bug

Added Introduction, problem statement , Data set , File Description, Usage , Conclusion etc.

Fixes: #572
Proposed Changes

Update the README.md file to include a comprehensive overview of the project, installation instructions, and usage guidelines.
Enhance the documentation to include troubleshooting tips and common error messages.
Add examples of input features to clarify expected formats for users.
Improve the overall structure of the project for better readability and user experience.

Screenshots

Original
Updated

**

**
**updated screenshot **

@UppuluriKalyani  Kindly Review my PR and approved it.


Migration create command messes up when converting embeddable to table

Describe the bug
Converting embeddable to a separate table with ManyToOne, and also converting a string field to a ManyToOne relationship causes migration:create to constantly create same migration. You can never get to a "schema is up to date" state.
To Reproduce
Steps to reproduce the behavior:

Clone this project: https://github.com/kristijanhusak/mikroorm-migration-issue
docker-compose up -d
docker-compose exec api npx mikro-orm migration:up
docker-compose exec api npx mikro-orm migration:create
docker-compose exec api npx mikro-orm migration:up
docker-compose exec api npx mikro-orm migration:create
See that all migrations created are same and it never gets to the end

Expected behavior
Expected to get to an "up to date" schema.
Additional context
Note that "nuking" the migrations and creating a single one from empty database solves the issue. It seems that converting from embeddable/uuid to ManyToOne leaves some state in db that messes up the migration generator.
You can check the 1st commit where I added the embeddable for image, and uuid for product on customer, and in 2nd I converted it to ManyToOne for both.
Versions

Dependency
Version

node
16.13

typescript
4.3.5

mikro-orm
4.5.10

your-driver
postgresql, 4.5.10

Please try with v5, there wont be any changes to v4, and v5 has rewritten schema diffing.

v5 fixes it, thanks. Do you know when I could expect v5 to become a regular release? I see that there's RC-2 at this point. Just trying to figure out if it's worth it to do the update now or to wait a bit.


⚠ SceneTime has degraded performance

In e7a2bb7, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1285 ms

Resolved: SceneTime performance has improved in 5de1a1c after 8 minutes.


docs(amba): readme & ahb edits

I was unclear about the reference to handshake signals in the readme, but didn't know whether/how I should put the definition here
additional notes for ahb edits in commit description

It's not handshake signals. The APB Bridge initiates a handshake and then verifies the control signals too.
Thanks for the edits. Merged!


Implement and test AttributionCollection

Description
This implements and tests AttributionCollection, a class aimed at associating attribution keys to merge-tree segments. Attribution keys are opaque values that can be used to look up user information: near-future plan is to use sequence numbers as attribution keys, but longer-term we may make this extensible via application-provided attribution information.
attribution information has no impact on whether adjacent segments can be merged. As such, a given segment may have different attribution information for each of its offsets.
#12634 provides a more complete picture of how this component integrates into the broader attribution story.

the collection I'm adding doesn't necessarily have to be used for Attribution, it could be used for any optional augmentation data on the merge-tree. Curious if the reviewer feels like that's an interesting abstraction/extensibility boundary to draw in this realm.


Cannot create virtualenv

Hello,
I bought code app for iPad OS recently. When I run python -m venv dmml’’, I am getting an error returned non-zero exit status 1’’. Attached is the screen shot. The directory dmml is getting created under virtual env. However, I don’t find the entire environment with pip, activate and other commands installed.
Also, I don’t find the source command to activate the specific environment. How will I activate a virtualenv?
Am I making some mistake?
Regards,
Ramki

Virtual environment is not yet supported.


Feature: Ubuntu16.04-- Support the Libvirt Provider

I love the boxcutter images. I use them for all my examples and deployments. To support libvirt I have been mutating the boxes to support the libvirt provider however this is not the ideal solution, since Hashicorp allows for storage of the libvirt provider images it would be great if you can start packing images for that provider and provide a trusted authoritative source for libvirt images.
Mutating images for new providers is not fully sufficient any longer due to issues like this ( https://github.com/vagrant-libvirt/vagrant-libvirt/issues/607 ) it would be ideal to have an image that was natively packed for libvirt.

Please submit a PR with an implementation and we would be more than willing to consider including it.


Add selectrum--completing-read-handler-alist

This addresses #136 and #139 by adding the discussed selectrum--completing-read-handler-alist. Later we could also use this variable to solve #114 where you had the idea to have a customizable list of table symbols that are known to be static.
As discovered in #136 other commands which locate libs suffer from the same issue (for Emacs version < 28). I refactored the code to reuse the code of read-library-name and delegate all those commands to the function which handles shadows in load path correctly. One downside is that currently the different suffixes passed to locate-file-completion-table are ignored (simply passing them to selectrum--locate-library-completions doesn't work) and so the commands don't differentiate bettween .el, .el.gz and .elc. But before you couldn't either so removing the duplicates and showing load path shadows instead is an improvement. Except for load-library where you might want to differentiate between .el and .elc the variants make not much sense to me anyway.
The problem with the completion table seems to be that it doesn't return all those candidates at once. With default completion .elc and .gz variants are only shown after you have already completed to the library name you want and invoke completion again.

Sorry, may not get to this for a while, I just started work etc etc. Don't worry, it'll be in my inbox until then though :)

(Feel free to make executive decisions if you would like, otherwise I'll get to all of these threads eventually.)

Okay, no stress I thought I would notify you because you might have different views how to handle this.  I will investigate this a bit more and try to find a good solution, as this is a private variable it's easy to change how the delegation is handled later on.
I wish you the best for your new job!


Array padding rule

@JKillian has generously offered to finish this 😄

edit by @adidahiya: fixes #1045

I think this should be called array-bracket-spacing like ESLint: http://eslint.org/docs/rules/array-bracket-spacing.
Related: https://github.com/buzinas/tslint-eslint-rules/issues/57

sgtm

I'm fine with array-bracket-spacing, although we could also make one rule that has options for object-brace-spacing, import-brace-spacing, jsx-attribute-brace-spacing and this. Or we can just keep them all as separate rules.

Reporting a failure message that just says

array padding

Isn't very descriptive or helpful. Perhaps something that actually describes what the issue is and how to fix it, like:

Arrays require whitespace between brackets

Also, does this rule consider initializing arrays:  arr = [];
or would you have to initialize like arr = [ ]; ?

👍  for more descriptive error message.
And I think arr = [] should still be allowed; enforcing arr = [ ] feels unnecessary.

Sorry, this is very much not complete. I had told @leeavital he could just throw whatever he had up here and I would finish it, but very clearly I haven't done that yet...

this PR is old, open a new one with rebased commits if you'd like to take up this task


Remove deprecated metrics from sys.nodes

Summary of the changes / Why this improves CrateDB
Checklist

[x] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[x] Documentation has been updated if necessary
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Did we double check that the admin-ui isn't using any of those properties anymore?

Did we double check that the admin-ui isn't using any of those properties anymore?

Good point, I will check. Thank you.

Retest this please


Several Tidy Checks are missing from the list (LLVM 17.0.1)

I've compared the list of available checks from LLVM 17.0.1 with the list in CPT and found the following are missing from CPT.
bugprone-empty-catch
bugprone-multiple-new-in-one-expression
bugprone-non-zero-enum-to-bool-conversion
bugprone-switch-missing-default-case
bugprone-unique-ptr-array-mismatch
bugprone-unsafe-functions
cert-msc24-c
cert-msc33-c
cppcoreguidelines-avoid-capturing-lambda-coroutines
cppcoreguidelines-misleading-capture-default-by-value
cppcoreguidelines-missing-std-forward
cppcoreguidelines-noexcept-destructor
cppcoreguidelines-noexcept-move-operations
cppcoreguidelines-noexcept-swap
cppcoreguidelines-rvalue-reference-param-not-moved
cppcoreguidelines-use-default-member-init
llvmlibc-inline-function-decl
misc-header-include-cycle
misc-include-cleaner
modernize-type-traits
modernize-use-std-print
performance-avoid-endl
performance-noexcept-destructor
performance-noexcept-swap
readability-avoid-unconditional-preprocessor-if
readability-operators-representation

Hi @netx123,
Thank you for letting us know, we definitely will add missing Tidy checks (It might require some time before the next release)
Kind regards,
Marina

Hi @netx123,
We added 52 new checks in Clang Power Tools release v2024.4.0, thank you for your help
Have a nice day,
Marina


disable colorized output?

I run "npm --no-color test" and while npm then doesn't generate colors, it appears to me that Jest CLI still does. I see lots of escape codes in the output in my emacs buffer which I assume are doing coloring (since that is what it looks like outside of emacs in a plain terminal). Might anybody know how I can turn that off? Thanks.

Use the --noHighlight option for running jest.

jest --noHighlight shows unrecognized options noHighlight is it still available?

You can use jest --no-colors now

@thymikee Hi, thanks for your answer, for some reason it still doesn't work when running it from a bash script, also added npm config set color false above but it's adding a bunch of [K and [1A to my output and I can't use it. I'm trying to generate reports periodically with a script in plain text.

With further analysis we noticed the reason is because it's replacing the output in the terminal and those special characters are breaking the output in plain text, I created a new issue #2292


Added me to index.html

@Djdany95  contribute here https://github.com/Ishaan28malik/Get-Dev-Resources


Add vrf support

For your consideration, a quick saturday afternoon hack to add basic support for a vrf option

Howdy. I created a branch that has VRF support. Additionally, fixed some of the bugs and refactored some of the Class methods to be cleaner. RPM also supports 32 and 64bit EOS now.


The request of the event resource in HTML should use the SlipStreamUI module.

[x] Upstream dependency: SlipStream/SlipStreamUI#296

[ ] Currently the JSON does not include the user information, so that the generated HTML looks as unlogged. Include it in the metadata so that the UI can generate the proper HTML.

Related to sixsq/Tasklist#354.

This task was finished on the context of #443.
Closing this issue.


History plugin problems

History plugin may cause a large amount of memory to be consumed, to mitigate the problem a new API call was proposed with the intent to free some of this memory as needed, a PR was made:

https://github.com/EOSIO/eos/pull/8740

Some overflow problems present, originally found by @greymass, a commit with a fix is in:

https://github.com/greymass/eos/commit/e58a0af9199d0474c33987e9622bac218d0fe77c

See #8703

See #8769

Also see: https://github.com/EOSIO/eos/issues/6377 where history and state-history don't play nice with each other.


Add network validation features

Validate:

IP address (IPv4 and IPv6 allowed)
IPv4 address
IPv6 address

Validate and normalize:

48-bit MAC address
64-bit MAC address

Description:
This update enables developers to validate and normalize user-supplied network data, such as IP and MAC addresses.
The normalization feature is only available for MAC addresses, being able to coerce the following non-standard address types into the IEEE 802-2014 standard:

a1:0b:c3:42:e5:1f (Unix)
a10b.c342.e51f (Cisco)
a10b-c342-e51f (Huawei)
a1b2c3d4e5f6 (Windows DHCP)

It also normalizes octets and groups of four hexadecimal digits separated by whitespaces:

a1 0b c3 42 e5 1f
a10b c342 e51f

And octets without leading zeros:

a1-b-c3-42-e5-1f
a1.b.c3.42.e5.1f
a1 b c3 42 e5 1f

All these inputs will return A1-0B-C3-42-E5-1F (IEEE 802-2014 standard).
Related issue: #222
Pull request in developers.home-assistant with documentation: #250
Example code for some_component.py:
import voluptuous as vol

from homeassistant.const import CONF_IP_ADDRESS, CONF_MAC
import homeassistant.helpers.config_validation as cv

DEVICE_SCHEMA = vol.Schema({
    vol.Required(CONF_IP_ADDRESS): vol.ipv4_address,
    vol.Required(CONF_MAC): vol.mac48_address
})

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] Documentation added/updated in home-assistant.io
[x] Tests have been added to verify that the new code works.

Thanks for the contribution!  Normally before submitting a PR to core, we open an architectural issue to discuss proposal first.  One of the things that would come out of that discussion are the use cases for these new validators.  I'm on board with them being added, but want to know where you plan to use them.  We don't want to add code just for the sake of it.  :+1:

Thanks for the contribution! Normally before submitting a PR to core, we open an architectural issue to discuss proposal first. One of the things that would come out of that discussion are the use cases for these new validators. I'm on board with them being added, but want to know where you plan to use them. We don't want to add code just for the sake of it. 👍

Thanks for the quick response. I'm sorry for breaking the protocol. This is one of my first contributions and I still do not know the rules very well. I intend to use this functionality on a remote control platform that I am adapting and I intend to share it as soon as I finish it. But as you said, this functionality has many uses, since almost all components need an IP or MAC address to work. Tomorrow I'll start making the improvements you asked for. Please wait for me to finish them before approving the code.

Is there a problem with our current usage?
from ipaddress import ip_address

DEVICE_SCHEMA = vol.Schema({
    vol.Required(CONF_IP_ADDRESS): ip_address,
})

Is there a problem with our current usage?
from ipaddress import ip_address

DEVICE_SCHEMA = vol.Schema({
    vol.Required(CONF_IP_ADDRESS): ip_address,
})

Yes, I see two problems.

When the argument is invalid, ipaddress.ip_address() raises a ValueError, but to work correctly with voluptuous it must raise a voluptuous.Invalid error.

ipaddress.ip_address() doesn't distinguish between IPv4 and IPv6 addresses, which is sometimes necessary. You must access the returned object to get this information.

The function does a great job, but it needs a wrapper function. That's exactly what I did.

Please open an architecture issue for further discussion.

When the argument is invalid, ipaddress.ip_address() raises a ValueError, but to work correctly with voluptuous it must raise a voluptuous.Invalid error.

It is not correct. ValueError raised inside schema will be wrapped in voluptuous validation error. We have used ip_address and ip_network in multiple integrations, don't have complain about them.

ipaddress.ip_address() doesn't distinguish between IPv4 and IPv6 addresses, which is sometimes necessary. You must access the returned object to get this information.

Actually, in most case, we do not want to distinguish between IPv4 and IPv6. We hope our integration can support both. You can see how we dealt with them in trusted networks auth provider

Please open an architecture issue for further discussion.

Okay, I promise I'll do it next time. Again, this is one of my first contributions and I did not know I needed to do it. I wonder if there is a way to move this discussion we are having here to the right area so we do not have to do it all over again.

When the argument is invalid, ipaddress.ip_address() raises a ValueError, but to work correctly with voluptuous it must raise a voluptuous.Invalid error.

It is not correct. ValueError raised inside schema will be wrapped in voluptuous validation error. We have used ip_address and ip_network in multiple integrations, don't have complain about them.

It didn't pass my test:
import ipaddress

import pytest
import voluptuous as vol

def test_ip_address():
    """Test IP address validation."""
    test = vol.Schema(ipaddress.ip_address)
    invalid = (
        None, True, False, 123, 123.456, 123+456j,
        [], [1, 2, 3, 4], ['a', 'b', 'c', 'd'],
        {}, {'a': 1, 'b': 2, 'c': 3, 'd': 4},
        '', 'abc', '123', '!@#$%', 'abc::123::def', '...', ':::::::',
        '1.2.3', '<IP_ADDRESS>.5', 'abc<IP_ADDRESS>', '<IP_ADDRESS>abc', '.2.3.4', '1..3.4',
        '1.2.3.', '*.2.3.4', '1.*.3.4', '1.2.*.4', '1.2.3.*', 'a.2.3.4',
        '1.b.3.4', '1.2.c.4', '1.2.3.d', '2<IP_ADDRESS>', '1.256.3.4', '1.2.256.4',
        '<IP_ADDRESS>6', '1:2:3:4', '1-2-3-4', '1/2/3/4', '1_2_3_4', '1,2,3,4',
        '1 2 3 4', '1:2:3:4:5:6:7', '1:2:3:4:5:6:7:8:9', 'xyz1:2:3:4:5:6:7:8',
        '1:2:3:4:5:6:7:8xyz', ':2:3:4:5:6:7:8', '1:2:3:4:5:6:7:',
        '*:2:3:4:5:6:7:8', '1:2:3:*:5:6:7:8', '1:2:3:4:5:6:7:*',
        'g:2:3:4:5:6:7:8', '1:2:3:g:5:6:7:8', '1:2:3:4:5:6:7:g',
        '10000:2:3:4:5:6:7:8', '1:2:3:10000:5:6:7:8', '1:2:3:4:5:6:7:10000',
        '<IP_ADDRESS>.<IP_ADDRESS>', '1-2-3-4-5-6-7-8', '1/2/3/4/5/6/7/8',
        '1_2_3_4_5_6_7_8', '1,2,3,4,5,6,7,8', '1 2 3 4 5 6 7 8')
    valid = (
        '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>',
        '2001:db8:85a3:0:0:8a2e:370:7334', 'FE80::B3FF:FE1E:8329')
    for value in invalid:
        with pytest.raises(vol.MultipleInvalid):
            test(value)
    for value in valid:
        assert test(value)

Even if it is being wrapped somewhere else, this is not the correct way to handle it, since ValueError doesn't take any argument, making it impossible for the programmer to send an error message to the user. Believe me, voluptuous.Invalid exception is the right way to work with voluptuous library because it's more suitable for the testing functions and it allows the programmer to set a specific error message for the problem. This is well documented at voluptuous docs.

ipaddress.ip_address() doesn't distinguish between IPv4 and IPv6 addresses, which is sometimes necessary. You must access the returned object to get this information.

Actually, in most case, we do not want to distinguish between IPv4 and IPv6. We hope our integration can support both. You can see how we dealt with them in trusted networks auth provider

Yes, I think supporting both IPv4 and IPv6 is the ideal scenario, but it is not yet a reality. Many programs and devices are not yet ready for IPv6. We need to be flexible to facilitate the transition.
Please, I'm doing my best to help the Home Assistant community. I'm trying to make codes in a clean and organized way, and I'm developing more integrations that depend on this one. Help me to approve it and interesting things will come.

I will recommend you use your validation in your component. We barely accept a core lib changes without use case. If there are more feedback from other developers want same function, we can promote it to core lib.
Again, those discussion should be in the architecture repo. Please do it for further discussion, not next time, this time.

@felipediel yeah, we don't merge core change without a use case. So if no component uses that code, we don't need to provide that feature on the core.


Update IISDeployer and its base class

In addition to these changes, there are a few minor issues @pakrym will help to resolve:

the guid in deploy path is not necessary;
host.json creation.

/cc @Tratcher @pakrym

:+1: @pakrym does this look like what you did?
Please test with the ServerTests repo.

FYI: I think we can avoid writing the hosting.json file. If we really need to pass in those parameters we can do it via command line or environment variable.

Ran with ServerTests, no new test failures.

Ping @Tratcher @pakrym I’d like to have this piece check in early tomorrow and then I’ll sit through the CI.

:shipit:


fix: remove malfunctioning hook

Codecov Report
Base: 90.66% // Head: 90.66% // No change to project coverage :thumbsup:

Coverage data is based on head (6c703b4) compared to base (8d26174).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1220   +/-   ##
========================================
  Coverage    90.66%   90.66%
========================================
  Files          186      186
  Lines         5643     5643
========================================
  Hits          5116     5116
  Misses         527      527

Flag
Coverage Δ

py3.8-ubuntu-latest-pandas
90.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/pandas_profiling/profile_report.py
81.57% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Search key word

The actual feature searches by individual characters, not by words, with unexpected results:

see #96

The search Feature should also consider the Opendata.swiss Keywords entered via the Cube Creator


integrates api data

Delivers the following:

API integration

Issue ticket
https://github.com/King-Benx/meal-capstone-project/issues/3
How to test:

Clone the project git clone git@github.com:King-Benx/your-movies-capstone-project.git
Checkout to the root directory cd your-movies-capstone-project
Checkout to the ft-implement-api git checkout ft-implement-api
Install dependencies npm i
Run the project using webpack npm run dev

Screenshots:

Mobile

Desktop

Hi @King-Benx ,
I have gone through the code and found it perfect. Just go ahead and merge it.


Verifier evaluate fails due to trailing characters

Reported by @uril following the quickstart guide on Azure, he got a message
Attestation failed: Verifier evaluate failed: json parse error\n\nCaused by:\n	trailing characters at line 1 column 420"

Here are the steps he reported doing:

Started a confidential Ubuntu VM on Azure and tested with it - using a container.
Created a container image based on CoCo existing image but built with openssl and added kbs-client (quay.io/uril/coco-kbs-pubkey – currently private)
When attesting, the kbs-client program must be run as root, as it needs access to /dev/tpm0.
Tested it - similar to what I did on my laptop (following kbs/quickstart.md), but without the environment-variable (AA_SAMPLE_ATTESTER_TEST=yes) so it’s actually doing attestation.
Attestation protocol is running but fails for me with an error message:

Attestation failed: Verifier evaluate failed: json parse error\n\nCaused by:\n	trailing characters at line 1 column 420"

I did not find an issue with a similar report. The parsing seems to be done by public_key_from_pem, which is code expanded from an openssl crate. So it looks like there is a bit of fussiness of this parser when there is extra trailing characters.

Indeed, thanks for reporting. That was a problem in the verifier. The Azure CVM platform has been slowly rolled out a change that we didn't account for. It has been fixed in #145


Added support for same region replicas.

This is just to finish up #3 since the original poster doesn't have time to finish it up.
Fixes #2 as well.

@aknysh gets final +2


Feat/payout v0.30

https://github.com/Cerebellum-Network/blockchain-node/pull/152 but in polkadot 0.30

closed due to too leaking features - see https://github.com/Cerebellum-Network/blockchain-node/pull/164


Change majority text

Please update this line "This user have reached majority." to "This user is over 18 years of age."
Thanks 👍

This have been fixed and pushed to staging


Could you offer the training code of this project please?

We have released the code and datasets in this repo: https://github.com/3d-hand-shape/hand-graph-cnn/. But we do not plan to release the training code of this project.


Logging and QMessageBox

WHAT

added logging functionality, added Plogger.py for logging setup.
added pip statements for structlog and logging.
added a qmessage box on error encountered during installation and initial application start.

WHY

logging is useful to track system behavior and monitor any failures.
pip statements in the setup.bat to enable logging.
the qmessage box is an alert during occurrence of an error.

Thank you Sir


added new turkish blog

Hi. I’d usually just fix this myself but I’m not at a computer right now so I can’t. There’s a couple of problems with your submission:

The feed_url parameter is mandatory, please add the location of your RSS feed.
There’s an extra comma at the end of the twitter_url parameter which is causing the JSON to be invalid.

If you fix those minor issues I’ll get it merged straight away! Thanks for the submission!
Sent with GitHawk

Thanks. Unfortunately the feed URL was still incorrect but I fixed it this time as I'm at a computer today 👍 Thanks for the submission!


Cross compiling qttools for qemuarm64 uses host glibc

When building qttools for RISC-V or AArch64 64-bit I see all sorts of float128 errors like this:

| /scratch/alistair/yocto/oe-master/build/tmp-glibc/work/riscv64-oe-linux/qttools/5.13.0+gitAUTOINC+cc9250477e-r0/recipe-sysroot/usr/include/stdlib.h:152:8: error: '_Float128' does not name a type; did you mean '_Float32x'?
|   152 | extern _Float128 strtof128 (const char *__restrict __nptr,
|       |        ^~~~~~~~~
|       |        _Float32x
| /scratch/alistair/yocto/oe-master/build/tmp-glibc/work/riscv64-oe-linux/qttools/5.13.0+gitAUTOINC+cc9250477e-r0/recipe-sysroot/usr/include/stdlib.h:245:4: error: '_Float128' has not been declared
|   245 |    _Float128 __f)
|       |    ^~~~~~~~~

These errors come from the glibc headers and not qttools itself. Looking at the glibc headers all of these float128 defines are protected by
#if __HAVE_FLOAT128
Which is not set for RISC-V, but is set for x86.
It seems like the host libc libraries are being used when building qttools.
These are the steps to reproduce:
git clone git://git.openembedded.org/openembedded-core
cd openembedded-core
git clone git://git.openembedded.org/bitbake
git clone https://github.com/meta-qt5/meta-qt5.git
source oe-init-build-env
bitbake-layers add-layer "$(pwd)/oe-${BRANCH}/meta-openembedded/meta-oe"
MACHINE=qemuarm64 bitbake qttools

The Qt layer uses the "linux-oe-g++" qmake platform specification (see qmake5_base bbclass), which includes "qtbase/mkspecs/linux-g++/qplatformdefs.h" (see https://github.com/meta-qt5/meta-qt5/blob/zeus/recipes-qt/qt5/qtbase/0001-Add-linux-oe-g-platform.patch ).
Maybe those headers define that macro?

The macro is defined from glibc bits/floatn.h so it's not surprising that it's being included, the problem is that the cross compile seems to be using the host.

I can reproduce this with the qemuarm64 machine as well, when I run MACHINE=qemuarm64 bitbake core-image-plasma-mobile I get the same failure.
DITRO_FEATURES += "wayland x11 kde opengl pam polkit xattr ptest ipv4 ipv6
EXTRA_IMAGE_FEATURES = "debug-tweaks x11 tools-sdk dev-pkgs package-management"

Steps to reproduce:
git clone git://git.openembedded.org/openembedded-core
cd openembedded-core
git clone git://git.openembedded.org/bitbake
git clone https://github.com/meta-qt5/meta-qt5.git
source oe-init-build-env
bitbake-layers add-layer "$(pwd)/oe-${BRANCH}/meta-openembedded/meta-oe"
MACHINE=qemuarm64 bitbake qttools

This seems to work again, not sure if it was fixed in meta-qt5 or if it was some host issue (Arch) that has been resolved.


test: run tests on node 18

Codecov Report

Merging #3197 (20d8177) into master (4471bb8) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master     #3197   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          193       193
  Lines        12012     12012
  Branches      2779      2779
=========================================
  Hits         12012     12012

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 4471bb8...20d8177. Read the comment docs.


Loss is zero

Hi Thank you for your great work, recently I train this VQMIVC to jvs dataset. But I got strange loss value please look at this :
epoch:506, global step:201, recon loss:3.645, cpc loss:2.398, vq loss:0.000, perpexlity:1.000, lld cs loss:31.000, mi cs loss:0.000E+00, lld ps loss:0.271, mi ps loss:-0.000, lld cp loss:-63.999, mi cp loss:0.000, used time:0.396s
is that normal that some loss turn into zero?

Hi, in my cases, the mutual information losses were around 0, but not equal to 0. I notice that the perplexity is 1.0, which means only one element in the codebook is used, so the codebook is not well trained. Based on my experience, this is most likely caused by the poor estimation of mutual information and log-likelihood, one way to alleviate this issue is to change the hyperparameters of the CLUB-network, e.g., increase/decrease the hidden layers' dimension or change the mutual information loss weight, it depends on the dataset you used, so they need to be carefully designed.

@Wendison Oh thank you for your brief response. I will try it


[SPARK-16927] [SPARK-16923] Override task properties at dispatcher.

What changes were proposed in this pull request?

enable setting default properties for all jobs submitted through the dispatcher [SPARK-16927]
remove duplication of conf vars on cluster submitted jobs [SPARK-16923] (this is a small fix, so I'm including in the same PR)

How was this patch tested?
mesos/spark integration test suite
manual testing

@skonto Can you take a look at this?

Test build #63287 has started for PR 14511 at commit f42ac25.

Test build #63287 has finished for PR 14511 at commit f42ac25.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63287/
Test FAILed.

retest please

I will have a look shortly

Ok LGTM other than the name of the setting for which I dont have a much better alternative.
@srowen could you check and merge pls?

Test build #63396 has started for PR 14511 at commit d6c25f0.

Test build #63396 has finished for PR 14511 at commit d6c25f0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63396/
Test PASSed.

Test build #63464 has started for PR 14511 at commit 81f2b1c.

Test build #63464 has finished for PR 14511 at commit 81f2b1c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63464/
Test PASSed.

Merged build finished. Test PASSed.

Merged to master


DF-199:Website results - add images to results

Contains backend changes to show image for insight and highlight filteraggregations.
@ababic Thanks for the great Idea of showing the Images :)

Hi @TNA-Allan. In addition to the points above, do we need to do something about the "All results" view too? https://develop-sr3snxi-rasrzs7pi6sd4.uk-1.platformsh.site/search/featured/

Hi @TNA-Allan. In addition to the points above, do we need to do something about the "All results" view too? https://develop-sr3snxi-rasrzs7pi6sd4.uk-1.platformsh.site/search/featured/

Would this be added to the scope of the ticket or new ticket?


Configure task on a build task causes incorrect tasks.json

Example:
		{
			"type": "npm",
			"script": "compile",
			"group": {
				"_id": "build"
			},
			"problemMatcher": [],
			"label": "npm: compile",
			"detail": "tsc -p ./"
		}

To verify:

Open the hello world sample (or any folder with an npm compile script).
Make sure the tasks.json doesn't have an npm compile task already.
Run the command Tasks: Configure Task
Select npm compile
Verify that the tasks.json file opens and there are no squiggles in the newly added npm compile task.


rounding problem with round func

Describe the bug
round(0.0157345, 6) return 0.015734

may due to the float type precision issue

Spark round float/double by converting to BigDecimal, maybe we can copy the convert logic of double and decimal in java.
https://github.com/apache/spark/blob/a056f694386cc074219914debf7023f5935bc37d/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/mathExpressions.scala#L1564


Loading translations client side works how?

Hey, I am currently using next-translate which forces my dynamic pages SSR even if I do not want it because it causes long cold starts in my pages even if they are all client-side.
Therefore, looking for something else. When I use next-international and client side loading of translations, the problem no longer exists. But I would like to understand how client side loading works? Is it using getInitialProps under the hood or else? In what ways it is not good to use or vice versa? Thank you.

When loading initial locale client-side, the requested locale file will be import()ed (basically, run the callback set in createI18n) which will result in a fetch() of the file. You can check this behavior by looking at the network tab, where you should see a locales_LANG_ts.js request.
The use-case for this feature is when you don't want or can't export a getServerSideProps / getStaticProps function on all/some pages.

Thanks for the information! Is client side loading of locale hurts SEO as far as you concern?

Nowadays, I believe crawling bots are smart enough to execute JS and then analyze when the DOM has been updated. SSG will always be faster since it's pre-generated to HTML, but I'm not sure if there is still an impact on SEO.

Thank you!


malfunctioning due to presence of <=

In my project i have used react-html-parser on the user input, so that i can use ,etc while printing them. But there is some issue with <= as when i am writing <= in the text passed to react-html-parser it is only returning text before it. <= along with text after it are missing. Also problem solves when i write it like < = (with space b/w it). Any suggestions on how to get rid of it.
I tried passing "this is awesome <= nothing" to react-html-parser and it returned just this returned Array of length 1 containing  only "this is awesome"

Same problem. Have you managed to fix it?
My case:
I am writing a code "... if (num <= size): ...", it only displays "... if(num ".

@rgvillanueva28 i was not able to fix it.

Well I've used another library but I think you can fix it by encoding the string.
You can use @this site

Thanks @rgvillanueva28 I will try that.

num < size || num === size, I wrote it this way without any errors


ic-action does not support chained derefences

We have been scoping our JS code using the module pattern, in order to avoid polluting the global namespace.
Now we've run into exactly the issue as described here: https://gitter.im/intercooler-js/Lobby?at=5c69ae5480df6804a1bf2170 , i.e. ic-action not supporting method derefencing. I know we can work around it with the event-based approach as described, but it is quite crappy to have all these event handlers all over the show, when ic-action is just so much more elegant and concise.
@chg20 I know you're furiously busy with HTMX ... but is there any chance of getting this squeezed in? 😬

@jvosloo OK, so you want to do something like:

Click Me

Basically support dot-dereferencing in the initial component of the action?

I pushed up a change that should fix this, if you want to grab the source out of dev.
For completeness, in htmx this would be solved with hyperscript:

Click Me

And if I understand alpine.js correctly, it would be:

Click Me

And I should say, nice to see you Johan!  :)

Carson - you're da man, man! 😁
I'm salivating over HTMX, but we're heavily invested in Intercooler .. in fact, we're busy expanding our usage right now again!
I'm hoping you're still going to keep an eye on it for a good while 😅

I'm not entirely sure about the workflow, whether I can close this issue, now that the change is in the development branch?
I guess so :)


UI: Add difficulty and failed_runs to admin_ui

Adding difficulty param in admin UI so we can run the job in a light, medium, or heavy worker (It will change on job_type change event).

Adding failed_runs in cache UI table

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (9d157f3) 91.30% compared to head (837e8d5) 87.17%.
Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2380      +/-   ##
==========================================
- Coverage   91.30%   87.17%   -4.13%
==========================================
  Files         256       77     -179
  Lines       15513     2768   -12745
==========================================
- Hits        14164     2413   -11751
+ Misses       1349      355     -994

Flag
Coverage Δ

jobs_cache_maintenance
94.40% <ø> (ø)

jobs_mongodb_migration
86.11% <ø> (ø)

libs_libcommon
?

services_admin
?

services_api
86.01% <ø> (ø)

services_rows
82.95% <ø> (ø)

services_search
?

services_sse-api
?

services_worker
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix documentation issue

This fix is included in https://github.com/ballerina-platform/ballerina-lang/pull/9592.


Issue with adding two "NIC_Basic" to one node.

I cannot add two "NIC_Basic" components to one node. I get Slice Fail: list index out of range. Not sure if the issue is with fablib or with the base library.
Code to try:
try:
    #Create Slice
    slice1 = fablib.new_slice(name=slice_name)

    #nodes
    n1 = slice1.add_node(name=node1_name, site=site)
    n1.set_capacities(cores=other_cores, ram=other_ram, disk=other_disk)
    n1.set_image(image)

    scheduler_nic1 = n1.add_component(model='NIC_Basic', name="nic1")
    scheduler_nic2 = n1.add_component(model='NIC_Basic', name="nic2")

    #Submit Slice Request
    slice1.submit(wait_progress=True)
except Exception as e:
    print(f"Slice Fail: {e}")
    traceback.print_exc()

Error:
Slice Fail: list index out of range
Traceback (most recent call last):
  File "/tmp/ipykernel_272480/1309156764.py", line 15, in <module>
    slice1.submit(wait_progress=True)
  File "/home/mono/Sachen/Work/FABRIC/fabric_python_api_locally/venv1/lib/python3.9/site- packages/fabrictestbed_extensions/fablib/slice.py", line 381, in submit
    self.update_slice()
  File "/home/mono/Sachen/Work/FABRIC/fabric_python_api_locally/venv1/lib/python3.9/site-packages/fabrictestbed_extensions/fablib/slice.py", line 102, in update_slice
    self.sm_slice = list(filter(lambda x: x.slice_name == self.slice_name, slices))[0]
IndexError: list index out of range

I think this is done be need to test


Decode CRL url first before adding to the list

Handles https://github.com/Jasig/cas/issues/524
I tested this with and without encoded urls and both check out correctly.

@serac please review.

I'd like to see a test case, which would help me understand the problem that's being solved. I recall we had a case where the distribution point URL was encoded and it worked, but maybe I'm remembering incorrectly.

Sure thing. Coming up...

Creating a test cert with encoded distribution points is proving more problematic than I thought. I may have to use mocks in this case. Would that work?

I added a test case with a sample cert whose CRL is encoded.

To elaborate, the original crl is http://localhost%3A8085%2Ftest%20ca.crl which is decoded to http://localhost:8085/test%20ca.crl

@serac Could I assume this pull passes review?

@leleuj you may want to review this

+1


Agility cape does not count for graceful for sherlock master clue

when you get the rellekka rooftop sherlock master step and use agi cape untrimmed, it does not show as complete graceful outfit in the indicator (don't know about trimmed cape)

and maybe also max cape when i think of it


Segmentation fault with gucci commands

Classification
Please delete options that are not relevant.

[]Question
[ ] Deliverability issue
[ ] Crash/Hang/Data loss
[X] Serious bug
[ ] Minor bug
[ ] Vulnerability
[ ] Feature/Enhancement
[ ] Documentation

Reproducibility
Please delete options that are not relevant.

[X] Always
[ ] Sometimes
[ ] Rarely
[ ] Unable
[ ] I didn’t try
[ ] Not applicable

Docker information
docker images hardware/mailserver --digests --filter "dangling=false"
REPOSITORY            TAG                 DIGEST                                                                    IMAGE ID            CREATED             SIZE
hardware/mailserver   1.1-stable          sha256:0af0d6bb7d5de589cb1cf47811f844d7ed43827a3298197fdd4cafee8d2c8ed5   1d08ae0bb068        2 months ago        380MB

Description
Can no longer start mailserver after doing docker-compose pull. My mailserver was doing just fine until the latest update (16 days ago pull request)
Debugging information
docker logs mailserver
[INFO] Search for SSL certificates generated by Traefik
[INFO] acme.json found with ACME v2 format, dumping into pem files
[INFO] Let's encrypt wildcard certificate found
[INFO] Let's encrypt live directory found
[INFO] Using /etc/letsencrypt/live/mail.mydomain.com folder
[INFO] Found DKIM key pair for domain mydomain.com - skip creation
/usr/local/bin/run.sh: fork: Cannot allocate memory
[INFO] Search for SSL certificates generated by Traefik
[INFO] acme.json found with ACME v2 format, dumping into pem files
[INFO] Let's encrypt wildcard certificate found
[INFO] Let's encrypt live directory found
[INFO] Using /etc/letsencrypt/live/mail.mydomain.com folder
[INFO] Found DKIM key pair for domain mydomain.com - skip creation
/usr/local/bin/run.sh: line 253:   130 Segmentation fault      gucci "$1.tpl" > "$1"
/usr/local/bin/run.sh: fork: Cannot allocate memory

Configuration (docker-compose.yml, traefik.toml...etc)
The basic with my own modified domain name and password

How much RAM is available on your server?

/usr/local/bin/run.sh: fork: Cannot allocate memory

It looks to me that you don't have enough free

This issue has been marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


Update registering-new-projects.adoc

Not saying this project is the right one per say, but it was causing me issues to leverage the project as was listed.

@alexbarbato Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


[WIP] Add lxc to all hosts

This will add the lxc package to all of the hosts, because some of
the checks require lxc package.
Connects rcbops/rpc-openstack#2026

Would you mind adding a bit more detail about why this approach was chosen into the commit message? Or are you testing this as a possible solution amongst others?
I realize reworking the tasks to be more specific might be more work, but I feel like that's a better solution. Willing to be outvoted, though, and curious as to what other feedback you've gotten.

@nrb @antonym and I went through the possible changes to make this work. We came up with these:
revert the process_check and all the swift process checks PR
add the lxc package to all hosts
rework the script to drop the lxc library (LXC makes easier to get pid)
@BjoernT seemed to be okay with the lxc package itself, instead of the whole LXC cache.
Still waiting on other feedback, although wanted to propose a solution and see if this could be a fix.
We are also welcoming any suggestions, because the script that is failing runs on all hosts, not just lxc hosts. For example, filebeat is on every container/host. A more challenging solution but duplicate stuff would be to split the process_check script into lxc and non lxc, but we don't think it'd work.

the script that is failing runs on all hosts

Right, but does it fail on all hosts?

A more challenging solution but duplicate stuff would be to split the process_check script into lxc and non lxc

Yeah, this is what I was thinking about. I acknowledge it's more overhead and more work. If installing the package everywhere fixes it and others are fine with that, then cool!

We are getting feedback from Bjoerrn, Nathan and others. That's why I put WIP until I got a consensus.

And no it only fails on the non-lxc hosts.

This python package won't install unless the accompanying LXC packages are installed on the same host. This is a very slippery slope. Please see my comments in https://github.com/rcbops/rpc-openstack/issues/2026

https://github.com/rcbops/rpc-openstack/pull/2058 appears to be a more targeted approach.

Closing this off in favor of https://github.com/rcbops/rpc-openstack/pull/2058


[Bug] Inject script incorrect location for Arch Linux

Inject script looks for /usr/share/discord/resources
On Arch Linux, discord is installed via an AUR package and defaults to /opt/discord
Therefore this injection script method fails. But you probably knew that. <3

Discord on Fedora RPMFusion repository installs to /usr/lib64
Might as well put it here, 🤷

I just went through with this on Arch, i edited the install script to where the location is pointed to in the PKGBUILD in thie: https://aur.archlinux.org/packages/discord/ so for me: ~/Downloads/discord/pkg/discord/opt/discord/resources

Why is it in your downloads folder? Sounds like there's no easy way to make it work for all Linux flavors

I just went through with this on Arch, i edited the install script to where the location is pointed to in the PKGBUILD in thie: https://aur.archlinux.org/packages/discord/ so for me: ~/Downloads/discord/pkg/discord/opt/discord/resources

Some people just want to see the world burn

Why is it in your downloads folder? Sounds like there's no easy way to make it work for all Linux flavors

Just tossing ideas out, what if we used a really obnoxious find or even asked the user? or had a list of typical locations that would be checked? im a noob, back to my nubdroid shib

@rauenzi @xstefen The reason it was in my downloads folder, is because I just clone from the aur and install there. The makepkg script just installed it in that same directory and linked it. Im just too lazy to move because it doesn't really matter to me and I am going to do a yearly reset soon anyways.

Here is a little hack I put together that does install (i guess more consistently)
    } else if (process.platform === 'linux') {         const standardPath = path.join('/usr', 'share', release.toLowerCase().replace(/ /g, '-'), 'resources');         if (!fs.existsSync(standardPath)) return path.join('/opt', 'discord', 'resources');         return path1;     }

ElementaryOS after the last update

Looks like you're using BBD.


Invalid Encrypted Credentials object does not error

Current Behavior
If Node-RED is using encrypted credentials (either system generated or user generated) but for whatever reason the creds object does not contain the $ key the credentials will not be loaded but no error is shown in the logs.
For example https://github.com/flowforge/flowforge/issues/397
Expected Behavior
A warning should be shown in the Node-RED log that encrypted credentials were not found.
Steps To Reproduce
Setup Node-RED with a credentialSecret and create a simple flow that has some credentials in it, for example HTTP Request node with basic auth.
Deploy the flow and then stop node-red
Edit the flows_cred.json file to invalidate the object, eg change the key from $ to foo
Start Node-RED and observe that there are no warnings in the log,
Check the HTTP request node and the credentials values will be missing
Example flow
paste your flow here

Environment

Node-RED version: 2.2.2
Node.js version: 16.x
npm version: 8.x
Platform/OS: MacOS
Browser: Chrome

I have a fix for this, will raise a PR

There are two valid scenarios where the credentials object may not contain a $ key:

The user is moving from unencrypted to encrypted
This is the very first time NR has been run, so the credentials object is empty.

We should not log an error for either of these cases; but I'm not entirely sure how you'd detect the first-run case.


Support iproute2 bpf_map_def layout

This is how aya currently defines bpf_map_def:  https://github.com/alessandrod/aya/blob/bb595c4e69ff0c72c8327e7f64d43ca7a4bc16a3/aya/src/bpf.rs#L52-L60
Many older eBPF programs use an old definition of bpf_map_def that didn't include the id  and pinning fields. Currently aya will fail to parse those programs because of this check: https://github.com/alessandrod/aya/blob/bb595c4e69ff0c72c8327e7f64d43ca7a4bc16a3/aya/src/obj/mod.rs#L512-L517
We could easily support those older programs by relaxing the above check a little - checking that the struct contains up to the map_flags field, and set id  and pinning to 0.

Where are the id and pinning fields coming from? Here's the anonymous struct in the latest 5.12:
	struct { /* anonymous struct used by BPF_MAP_CREATE command */
		__u32	map_type;	/* one of enum bpf_map_type */
		__u32	key_size;	/* size of key in bytes */
		__u32	value_size;	/* size of value in bytes */
		__u32	max_entries;	/* max number of entries in a map */
		__u32	map_flags;	/* BPF_MAP_CREATE related
					 * flags defined above.
					 */
		__u32	inner_map_fd;	/* fd pointing to the inner map */
		__u32	numa_node;	/* numa node (effective only if
					 * BPF_F_NUMA_NODE is set).
					 */
		char	map_name[BPF_OBJ_NAME_LEN];
		__u32	map_ifindex;	/* ifindex of netdev to create on */
		__u32	btf_fd;		/* fd pointing to a BTF type data */
		__u32	btf_key_type_id;	/* BTF type_id of the key */
		__u32	btf_value_type_id;	/* BTF type_id of the value */
		__u32	btf_vmlinux_value_type_id;/* BTF type_id of a kernel-
						   * struct stored as the
						   * map value
						   */
	};

Where are the id and pinning fields coming from? Here's the anonymous struct in the latest 5.12:

iproute2, see https://github.com/alessandrod/aya/pull/14#issuecomment-865325330

Closed by #14


[Feature] Added aggregations without type dimension

Summary
Added aggregations over transactions without type dimension. Renamed aggregations to more appropriate names.
Description
Aggregation have been renamed to use the following pattern: TransactionDimension1Dimension2...Stat.
Meaning if we want aggregation by Type , User and App we should query aggregation TransactionTypeUserAppStat
New aggregations where added that do not have the type dimension. This change facilitates calculations given that we do not have to loop over all different types to get totals.
Related Issue/Bounty
OF-283 - Difficult to get transaction totals
Type of Change
Please check the boxes that apply to your pull request:

[X] Breaking change (fix or feature that would cause existing functionality to change)

All previous queries need to be updated because aggregations have changed names.

hey @tinypell3ts we are blocked on merging this as code owner review is required


Add Z-index to Medium Zoom to prevent hiding

If you have smaller view port, sidebar is open and you open big image in lightbox, it is hidden behind sidebar. Check image:

I fixed it with simple z-index to MediumZoom overlay and image

That's neat, thank you @arxeiss 😍


Chunk missing constructor requirement

Hey! Thanks for this awesome book.
I found a small missing part in Chapter 2(Chunks)
This function is used in the Png unit tests without ever being talked about inside of Chunks:
    pub fn new(chunk_type: ChunkType, data: Vec<u8>) -> Chunk

You should consider adding it to Chapter 2's requirements

It seems this function exists in the given source code but I didn't know there was such source code until I searched for this github repo

I would like to see a test for this if since it's used in the png tests as well. I'd argue that since the user is supposed to work through the code without looking up the source code (unless the user is stuck perhaps) I'd like a bulletin point to ask to create this function and have a test for it.

I added a requirement for a new function along with a test to check that it works. Thanks for reporting this!


⚠ Jenkins Plugins Artifactory has degraded performance

In 815c718, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1185 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 659528e after 12 minutes.


Set default strategy to RollingUpdate for Redis in Kubernetes

Checklist

[x] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[x] PR title is ready for changelog and subsystem label(s) applied

This PR changes the default deployment strategy for Redis in kubernetes.
From Recreate to RollingUpdate.

Closing issues
closes #2371

@vincenzodnp thanks! can you also cherry-pick this against master and send a PR there? I think this makes sense to also have in 1.x

Do we even need to specify a strategy? Rolling update is the default?

@smlx good question, for me both is fine :)

I think by specifying it, we are safe if they change the default.


Merge behavior

Hi There,
what is the way to fix a form which is modified in a unmanaged layer in PROD instance? Is there a way to bypass the "merge behaviour" for forms? Is the only fix to create a new form in DEV to replace the changed form?
Regards
Jaimie

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

ID: 22df4a82-a072-f324-8500-2e62fe120d3a
Version Independent ID: d4fb1c9b-7dfc-5b4a-7e07-f6515b150e25
Content: Solution layers and merge behavior - Power Platform
Content Source: power-platform/alm/solution-layers-alm.md
Service: power-platform
Sub-service: alm
GitHub Login: @Mattp123
Microsoft Alias: matp

Thanks for your comment, @jaimieji. This issue has been assigned to the doc author for review.


How do you use bedrock with plugins that have own libraries from composer?

I wanted to ask if anyone has idea what's the impact of having redundand libraries in bedrock and some plugins, my example:
I have a bedrock setup with some more libraries (for logging and other stuff), now I install MailPoet and WP SMTP, both plugins have own vendor/ folders with own libraries. Is composer taking care of the redundancy and does it load only one of the libraries?

Hi @katsar0v,
It looks like the issue template is missing from this issue. Please take a look at the Contribution Guidelines, which will tell you exactly what your ticket has to contain in order to be processable.
Please do not use the issue tracker for personal support requests. Use Roots Discourse to ask the Roots community for help, or hire someone from the community.

Is there a gitter channel for bedrock? I saw one only for sage

https://discourse.roots.io/ :wave:


Speaker and event details to firestore

Problem
We are moving more data to Firestore
Solution
Speakers and event details now come from Firestore
Test(s) added
None unfortunately
Paired with
Nobody

@rock3r @fourlastor ready for another review. Also, before merging take a look at #453 which adds test for a lot of the Firestore model

Do not merge until #453 is shipped

Tests have been merged, now we can 🚢 once green


Add axis arrows to simulator hands

When controlling the simulator hands there is very little indication of how you're going to move them when you move the mouse. The control hints kindly tell you the current mode and what controls to use to switch back to the HMD, switch hands, switch axis, and switch to rotation. But unless you look at the current axis value and try to comprehend it you basically just end up moving your mouse till you see something happen and go from there.
It would probably be much easier to comprehend if the active hand had straight/curved arrows pointing along the axis that moving your mouse will move the hand. Then without reading text you immediately know which hand is active, whether you are moving or rotating it, and which axis you will move it along. And whenever you press a button to switch hands, switch axis, or switch to rotation you immediately get visual feedback about that.
I might do this myself if I feel like sparing the time... though I think I'm running out of time this weekend.
It's a side discussion but I'm also contemplating whether the mock spheres should use the standard shader instead of Unlit so you get and cast shadows that make it easier to tell where they are.

I like the idea with guides, as long as there is an option for turning it on/off : )

PR https://github.com/thestonefox/VRTK/pull/1602


Add more tests for properties selections and selectionList

Add more integration tests for the PR #498
These tests can be also treated as an incomplete spec of the new property selectionList.

@ndrsn I will push one more commit into this PR tonight. It doesn't need to be megred now. Thanks

Thanks for @velitasali , He found I declared the function fitSelectedColumns two times in the source code.  It doesn't need to be megred now. Thanks

I think if you make this a draft pull request, we can prevent my fat fingers from accidentally hitting the merge button until it's ready :-)

I think if you make this a draft pull request, we can prevent my fat fingers from accidentally hitting the merge button until it's ready :-)

Oh, thanks for your tip. To be honest, I used Github for very long time, but this is my first time to know about it.

@ndrsn  By the way, the code about the selection feature has not reached the end. I will work on the cache of it and optimize the adaptor for old API. And fix bugs if anybody report the bug about it. Then I will create another PR for them. But this optimization needs some time.
But now it can works well and it improves performance although it is not its best performance, I tested it with 1 million rows and its selection experience is very good now
I see that @velitasali has worked on some features related to the selection. I think you can release them and this new selection mechanism in next MINOR version (0.5.0)

All good!
🎉


make "govendor list" output easier to read and parse

@jacobsa mentioned that "govendor list" wasn't the easiest to pick apart with a sed one liner. While you shouldn't need to do that too often, it should be reasonable to do.
I have also noticed the syntax for vendored projects are a bit verbose. That should be cleaned up.
Maybe something like:
v <canonical-path>  (align with space) <"::" vendor path from project root>
v co2/pk2       ::vendor/co2/pk2

Seems sane. Alternatively, a flag that turns off the extra stuff and prints only the package names (perhaps with the one character status)?

I have a flag already -v to list packages that import said dependency. I could only show the vendor path if the -v flag = true. Then normal output would be:
v

Assuming you mean the output would be the following (your comment seems truncated):
v co2/pk2

then I agree. This is actually what I would expect given the presence of the -v flag.

If you wouldn't mind, checkout master and see if that is better.

Looks good to me, thanks!


Homebridge does not pause for button press

Describe The Bug:
When rebooting Homebridge after plug-in installation, Homebridge 1.7.0 will not pause for the user to be able to press the button on the bottom of the Dirigera hub. It just goes past it and never initializes properly.
To Reproduce:
Install the plug-in, enter IP address, and reboot Homebridge 1.7.0. Using Homebridge on Raspberry Pi.
Expected behavior:
Homebridge should pause during load, allow for button press, and continue.
Logs:
[04/01/2024, 13:03:40] [HB Supervisor] Restarting Homebridge...
[04/01/2024, 13:03:40] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[04/01/2024, 13:03:40] [HB Supervisor] Started Homebridge v1.7.0 with PID: 28909
[04/01/2024, 13:03:41] Loaded config.json with 1 accessories and 5 platforms.
[04/01/2024, 13:03:41] Loaded 23 cached accessories from cachedAccessories.
[04/01/2024, 13:03:42] ---
[04/01/2024, 13:03:42] Loaded plugin<EMAIL_ADDRESS>[04/01/2024, 13:03:42] Registering accessory 'homebridge-dummy.DummySwitch'
[04/01/2024, 13:03:42] ---
[04/01/2024, 13:03:43] Loaded plugin<EMAIL_ADDRESS>[04/01/2024, 13:03:43] Registering platform 'homebridge-eufy-security.EufySecurity'
[04/01/2024, 13:03:43] ---
[04/01/2024, 13:03:43] Loaded plugin<EMAIL_ADDRESS>[04/01/2024, 13:03:43] Registering platform 'homebridge-meross.Meross'
[04/01/2024, 13:03:43] ---
[04/01/2024, 13:03:44] Loaded plugin<EMAIL_ADDRESS>[04/01/2024, 13:03:44] Registering platform 'homebridge-simplisafe3.SimpliSafe 3'
[04/01/2024, 13:03:44] ---
[04/01/2024, 13:03:44] Loaded plugin<EMAIL_ADDRESS>[04/01/2024, 13:03:44] Registering platform<EMAIL_ADDRESS>[04/01/2024, 13:03:44] ---
[04/01/2024, 13:03:44] Loading 5 platforms...
[04/01/2024, 13:03:44] [Home Alarm] Initializing homebridge-simplisafe3.SimpliSafe 3 platform...
[04/01/2024, 13:03:44] [EufySecurity] Initializing EufySecurity platform...
[01/04/2024, 13:03:44]  [EufySecurity]  WARN    warning: planned changes, see https://github.com/homebridge-eufy-security/plugin/issues/1
[01/04/2024, 13:03:44]  [EufySecurity]  INFO    Country set: US
[01/04/2024, 13:03:44]  [EufySecurity]  INFO    Finished initializing!
[04/01/2024, 13:03:44] [Meross] Initializing Meross platform...
[04/01/2024, 13:03:44] [Meross] Initialising plugin v10.3.0 | System linux | Node v20.10.0 | HB v1.7.0 | HAPNodeJS v0.11.1...
[04/01/2024, 13:03:44] [Dirigera] Initializing Dirigera platform...
[04/01/2024, 13:03:44] Loading 1 accessories...
[04/01/2024, 13:03:44] [SimpliSafe Trigger] Initializing DummySwitch accessory...
[04/01/2024, 13:03:44] [SimpliSafe Trigger] Setting switch to false
[04/01/2024, 13:03:45] [Meross] Plugin initialised. Setting up accessories....
Setup Payload:
X-HM://0023ISYWY2H6N
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

    ┌────────────┐
    │ xxx-xx-xxx │
    └────────────┘

[04/01/2024, 13:03:45] Homebridge v1.7.0 (HAP v0.11.1) (Homebridge) is running on port 51262.
[04/01/2024, 13:03:46] [Meross] [Counter Light Switch] initialising with options {"connection":"hybrid","inUsePowerThreshold":0,"showAs":"switch"}.
[04/01/2024, 13:03:46] [Meross] [Counter Light Switch] initialised with id [}].
[04/01/2024, 13:03:46] [Meross] [Pantry Light Switch] initialising with options {"connection":"hybrid","inUsePowerThreshold":0,"showAs":"switch"}.
[04/01/2024, 13:03:46] [Meross] [Pantry Light Switch] initialised with id [}].
[04/01/2024, 13:03:46] [Meross] [Master Closet] initialising with options {"connection":"hybrid","inUsePowerThreshold":0,"showAs":"switch"}.
[04/01/2024, 13:03:46] [Meross] [Master Closet] initialised with id [}].
[04/01/2024, 13:03:46] [Meross] [Smart Garage Door Opener] initialising with options {"connection":"hybrid","garageDoorOpeningTime":20}.
[04/01/2024, 13:03:46] [Meross] [Smart Garage Door Opener] initialised with id [}].
[04/01/2024, 13:03:46] [Meross] [Front Porch] initialising with options {"connection":"hybrid","inUsePowerThreshold":0,"showAs":"switch"}.
[04/01/2024, 13:03:46] [Meross] [Front Porch] initialised with id [}].
[04/01/2024, 13:03:46] [Meross] [Smart Desk Lamp] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"connection":"hybrid"}.
[04/01/2024, 13:03:46] [Meross] [Smart Desk Lamp] initialised with id [}].
[04/01/2024, 13:03:46] [Meross] [Foyer Switch] initialising with options {"connection":"hybrid","inUsePowerThreshold":0,"showAs":"switch"}.
[04/01/2024, 13:03:46] [Meross] [Foyer Switch] initialised with id [}].
[04/01/2024, 13:03:46] [Meross] ✓ Setup complete. This plugin has been made with ♥ by bwp91, please consider a ☆ on GitHub if you are finding it useful!
Press the Action Button on the bottom of your Dirigera Hub and then press the Enter button here[04/01/2024, 13:03:47] [Home Alarm] Motion Sensor 'Master BR' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[04/01/2024, 13:03:47] [Home Alarm] Motion Sensor 'Living Room' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[04/01/2024, 13:03:48] [Meross] [Counter Light Switch] has been reported [online].
[04/01/2024, 13:03:48] [Meross] [Pantry Light Switch] has been reported [online].
[04/01/2024, 13:03:48] [Home Alarm] SimpliSafe real time events connected.
[04/01/2024, 13:03:48] [Meross] [Master Closet] has been reported [online].
[04/01/2024, 13:03:48] [Meross] [Front Porch] has been reported [online].
[04/01/2024, 13:03:48] [Meross] [Smart Desk Lamp] has been reported [online].
[04/01/2024, 13:03:48] [Meross] [Smart Garage Door Opener] has been reported [online].
[04/01/2024, 13:03:48] [Meross] [Foyer Switch] has been reported [online].
[01/04/2024, 13:03:55]  [EufySecurity]  INFO    Updating existing accessory: Mailbox
[01/04/2024, 13:04:31]  [EufySecurity]  INFO    Looking for old cached accessories that seem to be outdated...
[01/04/2024, 13:04:31]  [EufySecurity]  INFO    No outdated cached accessories found.

Plugin Config:
            "hubs": [
                {
                    "host": "192.168.1.xxx", (IP removed but is correct)
                    "name": "Home"
                }
            ],
            "platform": "Dirigera"

Screenshots:

Environment:

Plugin Version: 0.1.11
Homebridge Version: 1.7.0
Node.js Version: 20.10.0
NPM Version: 10.2.5
Operating System: Raspbian

yep, that wasn't very smart :)
try 0.1.13 - this time you'll have about 1 min to press the action button)
let me know if it works...
just note..  If it works for you... great! 👍  (but I don't have any intention atm to support devices I don't have).

This fix worked! Thank you - I now have access to my Dirigera lights. I
also copied/pasted the token so it will stay connected. Great little plugin!
On Mon, Jan 8, 2024 at 4:22 PM uboness @.***> wrote:

yep, that wasn't very smart :)
try 0.1.13 - this time you'll have about 1 min to press the action button)
let me know if it works...
just note..  If it works for
you... great! 👍 (but I don't have any intention atm to support devices I
don't have).
—
Reply to this email directly, view it on GitHub
https://github.com/uboness/homebridge-dirigera/issues/1#issuecomment-1881841667,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFDVH6A6727F7UDO36WC7CTYNRPQ3AVCNFSM6AAAAABBNKP56KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRHA2DCNRWG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


abstracting framebuffer

@nbrr

It seems something good to work with. Eventually we shall give it another impl to ensure it is flexible enough.


[bug] Button shows up unstyled, potential Tailwind conflict

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
0.7.1
wagmi Version
0.6.0
Current Behavior
I have tailwind installed and I am experiencing a similar issue to the one mentioned here in #329 regarding tailwind css specificity potentially. The ConnectButton shows up completely unstyled.
Expected Behavior
Normal CSS styling is expected
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

Hi, how do you solve the  issue, I found the same problem

Hi, how do you solve the issue, I found the same problem

Just make sure to import the rainbowkit styles after your other styles like so.
import "../styles/globals.css";
import "../styles/tailwind.css";
import<EMAIL_ADDRESS>


aarch64 support

I recently tried building distributions for aarch64, but the code seems quite specific to x86. Does a port exist/is there one planned for aarch64?

I am unaware of any plans or efforts to port distributions to aarch64. However, the cython implementations should be architecture independent. Distributions ships with three implementations: python, cython, and c++. Probably the first step to supporting aarch64 would be to disable c++ for aarch64 so at least the cython implementation could be built.


Limit dragging to x/y axis

Hello,
Is it feasible to support horizontal/vertical-only dragging like https://github.com/mzabriskie/react-draggable?

Technically, no. Would be willing to accept a PR that allows passing arbitrary props to Resizable/Draggable.

Shouldn't it be just possible by keeping the width of the item as 100% for vertical axis dragging and also disabling the resize of the child component. Am i missing something here ?


Generate DBSubnetGroup resource

https://github.com/aws-controllers-k8s/community/issues/844
Generate DBSubnetGroup resource

Add necessary hooks for create/update/delete methods
Add basic e2e tests for CRUD operations

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


Added "facing_short" variable

I added the variable facing_short, which is just the first character of the direction in upper case (N, E, S or W).
Would you like to add this change to the main repo?

I can also update the wiki as well, if you want to.

Added to wiki, will be in next release

Thanks!


Update tag

Would it be possible to up the tag of Gizmo to v0.0.2? Would love to “properly” update our dependencies to fix the panic on 404s. Thanks

You got it, boss.

https://github.com/NYTimes/gizmo/releases/tag/v0.1.1
This work?

Yep, updated perfectly. Thank you!


Receiver of Asset Issuance does not show up in Recent Activity

For example,
"Was issued 1,000 OPENLTC by openledger-wallet  	22 minutes ago"
-> openledger-wallet was issued 1,000 OPENLTC by openledger-wallet

I actually noticed this too and fixed it in a commit yesterday

e570c1da40de363ec2934ad8537df16b395236ef


TableReport outliers improvement?

Describe the bug
I don't think this is a bug, I'm just creating this issue so that we can observe a different behaviour I just saw.
Here is a series where the outlier detection is slightly off. This is an integer series comprised of {0, 80, 100}. Here, the values are actually categorical because they just distinguish states, and the choice of the state values 0 and 80 is arbitrary (it could have been 0, 1, 2, but for some reason it's 0, 80, 100).
Unless we tune the heuristic a little bit to avoid counting outliers when the cardinality is "very low", I don't see an easy improvement.
WDYT?

The column dataset:
state.csv
Steps/Code to Reproduce
import pandas as pd
from skrub import TableReport

df = pd.read_csv("state.csv")
TableReport(df)

Expected Results
No outliers
Actual Results
Some outliers
Versions
0.4.0 :)))

here is another example from the "titanic" dataset

Yes, that's tricky I agree. The best scenario would be for the user to notice that and convert to string or category dtypes. The main difference between my screenshot and yours is that on mine the outlier segment is bigger than the category displayed on the left, so the outliers are not really outliers, if that makes sense?

what we would like in this case is to realize that the actual values don't matter and treat the variable as categorical as you say. but I'm not sure that its' reasonable to assume that is the case whenever there are few unique values 🤔

Let's wait a bit to get feedback and decide about this.


IE11: setItem(..., null) never resolves

On IE11, the promise returned by localforage.setItem("foo", null) never resolves or rejects.

Similar issue for v1.4.3. Promise never resolves(for each of localforage method). Callbacks don't work. Issue only in IE11.

I found cause of problem: db version should be(for IE) a number. I used string.
Can you update documentation and add error handler if version is not a number?  It will be useful.
Test for IE (nVersion is string. Get error):
try {   var db = null;    var sName = "ADatabase";   var nVersion = "1.0";   if (window.indexedDB) {     var req = window.indexedDB.open( sName , nVersion );     req.onsuccess = function(evt) {         db = evt.target.result;        console.log( db );     } }   } catch( ex ) {     console.log( ex );   }

In the current master (which is going to be v1.5) we are throwing an error when a non numeric version is passed in. So I guess that this case is well covered now.

Arrived here since localForage did not work for my IE11 (11.673.15063.0, Update Versions: 11.0.47) on Windows10.
I am using v1.5 and it's not throwing any errors when passing a string, i.e.
export const viewStorage = localForage.createInstance({
    name: "myViews",
    version: "3",
    size: 4980736, // Size of database, in bytes. WebSQL-only for now.
    storeName: "views" // Should be alphanumeric, with underscores.
});

PS: changing the version to a number fixed the issue for IE11.


Solved merge conflicts and unit test problems

This PR contains the solutions for the PR#68. There were merge conflicts and those are solved now. The unit tests successfully passing through.

Any updates on this PR?

@kbilsted and @jamesbassett: Kindly review please


add support for main in centos:7 + other fixes (main)

I'll wait for @d-w-moore's PR before merging :)

seems good to me


Test pr

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

ignore, closing.


WL-1294: Drop the filtering of the site description.

This disables another fixed issue WL-3633 so if we merge it then we lose iframes again.


[WFLY-7792] Mixed domain with EAP 6.2 slave: data sources operations failed

Jira: https://issues.jboss.org/browse/WFLY-7792

We're dropping support for transforming to versions prior to EAP 6.4.


[Snyk] Security upgrade org.apache.jena:jena-arq from 4.9.0-SNAPSHOT to 4.10.0

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):

jena-db/jena-dboe-base/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue
Score
Upgrade

Uncontrolled Resource Consumption SNYK-JAVA-COMMONSIO-8161190
  50
org.apache.jena:jena-arq:  4.9.0-SNAPSHOT -> 4.10.0  No Known Exploit

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Uncontrolled Resource Consumption

Checkmarx One – Scan Summary & Details – 93c0c55f-f615-4dc5-9de9-5609b45af64d
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2022-46337
Maven-org.apache.derby:derby-<IP_ADDRESS>
Vulnerable Package

CVE-2023-36478
Maven-org.eclipse.jetty:jetty-http-10.0.15
Vulnerable Package

CVE-2023-43646
Npm-get-func-name-2.0.0
Vulnerable Package

CVE-2023-45133
<EMAIL_ADDRESS>Vulnerable Package

CVE-2024-23331
Npm-vite-4.0.4
Vulnerable Package

CVE-2024-37890
Npm-ws-8.12.0
Vulnerable Package

CVE-2024-4068
Npm-braces-3.0.2
Vulnerable Package

CVE-2024-45296
Npm-path-to-regexp-0.1.7
Vulnerable Package

CVE-2024-45296
Npm-path-to-regexp-1.8.0
Vulnerable Package

CVE-2024-45590
Npm-body-parser-1.20.1
Vulnerable Package

CVE-2024-45801
Npm-dompurify-2.4.3
Vulnerable Package

CVE-2024-7254
Maven-com.google.protobuf:protobuf-java-3.23.2
Vulnerable Package

CVE-2022-29622
Npm-formidable-1.2.6
Vulnerable Package

CVE-2023-26159
Npm-follow-redirects-1.15.2
Vulnerable Package

CVE-2023-28155
<EMAIL_ADDRESS>Vulnerable Package

CVE-2023-36479
Maven-org.eclipse.jetty:jetty-servlets-10.0.15
Vulnerable Package

CVE-2023-40167
Maven-org.eclipse.jetty:jetty-http-10.0.15
Vulnerable Package

CVE-2023-42503
Maven-org.apache.commons:commons-compress-1.23.0
Vulnerable Package

CVE-2023-44270
Npm-postcss-8.4.21
Vulnerable Package

CVE-2023-45857
Npm-axios-0.27.2
Vulnerable Package

CVE-2023-46749
Maven-org.apache.shiro:shiro-web-1.11.0
Vulnerable Package

CVE-2023-46750
Maven-org.apache.shiro:shiro-web-1.11.0
Vulnerable Package

CVE-2024-25710
Maven-org.apache.commons:commons-compress-1.23.0
Vulnerable Package

CVE-2024-26308
Maven-org.apache.commons:commons-compress-1.23.0
Vulnerable Package

CVE-2024-28849
Npm-follow-redirects-1.15.2
Vulnerable Package

CVE-2024-29041
Npm-express-4.18.2
Vulnerable Package

CVE-2024-31207
Npm-vite-4.0.4
Vulnerable Package

CVE-2024-34343
Npm-ufo-1.0.1
Vulnerable Package

CVE-2024-4067
Npm-micromatch-4.0.5
Vulnerable Package

CVE-2024-43796
Npm-express-4.18.2
Vulnerable Package

CVE-2024-43799
Npm-send-0.18.0
Vulnerable Package

CVE-2024-43800
Npm-serve-static-1.15.0
Vulnerable Package

CVE-2024-45811
Npm-vite-4.0.4
Vulnerable Package

CVE-2024-45812
Npm-vite-4.0.4
Vulnerable Package

CVE-2024-47068
Npm-rollup-3.11.0
Vulnerable Package

CVE-2024-6531
Npm-bootstrap-5.2.3
Vulnerable Package

Cx14b19a02-387a
Npm-body-parser-1.20.1
Vulnerable Package

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/test/java/org/apache/jena/iri/TestMoreExamples.java: 239
Attack Vector

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/test/java/org/apache/jena/iri/TestCreator.java: 81
Attack Vector

Use_of_Cryptographically_Weak_PRNG
/jena-arq/src/main/java/org/apache/jena/sparql/expr/E_Random.java: 34
Attack Vector

Fixed Issues

Severity
Issue
Source File / Package

CVE-2022-38900
Npm-decode-uri-component-0.2.2

CVE-2007-2379
Npm-jquery-3.6.3

CVE-2014-6071
Npm-jquery-3.6.3

Host Namespace is Shared
/docker-compose.yaml: 20

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/main/java/org/apache/jena/iri/impl/BuildViolationCodes.java: 35

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/main/java/org/apache/jena/iri/impl/BuildViolationCodes.java: 39

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/main/java/org/apache/jena/iri/impl/BuildViolationCodes.java: 38

Networks Not Set
/docker-compose.yaml: 20